Meridian Integrations

Integrations offer numerous benefits that significantly enhance organisational efficiency and performance. By seamlessly connecting disparate systems, integrations improve data accuracy by eliminating manual data entry and minimising errors, ensuring consistent data across all platforms. They streamline workflows and automate repetitive tasks, which boosts productivity and reduces turnaround times.Specifically, let’s discuss Meridian integrations with SAP. We will explore two types to illustrate the potential of integrating Meridian with your SAP data. The first type is a sophisticated, off-the-shelf integrated module that synchronises your asset data from SAP into Meridian, enabling you to seamlessly create tag/document relationships.The second type is a basic export-import process where the destination system transfers and uses Functional Location data, allowing you to allocate a Functional Location to a document.

Asset Management Module

The Meridian Asset Management Module acts as a secure bridge between asset information in a maintenance management system and document information in a Meridian Enterprise vault. Users from either system can access and link to data in the other system. However, it’s important to note that the ownership remains distinct: assets (referred to as tags in Meridian Enterprise) are managed by the maintenance management system, and documents are controlled by Meridian Enterprise. This ensures precise and defined control over the data, giving you the confidence that your data is safe.Here is an example of the end-user experience with this type of integration:

Here is an example of the end-user experience with this type of integration.

*Figure 1 – Link to related documents in Meridian*

*Figure 2 – Related asset documentation is returned in Meridian Explorer*

Export-Import of Funtional Location Data

A more bespoke type of integration involves utilising data from one system within another. For SAP, we are specifically referring to the Functional Location data. In the example, documents are required to store the Functional Location they are associated with; not having common lookup data or old data can cause data inconsistencies, which is one of the driving forces for this type of integration. Within this type of integration, there are several levels of automation.

1. A mechanism is created for the destination system to query the SAP Functional Location data as a lookup. The benefit of this level is once it is set up and working you will always be using the most up-to-date Functional Location data.

2. Regularly, an automated export of the SAP data is created, and then an automated import of that data is done in the Meridian Lookup database.

3. A manual export/import process is regularly performed.

Whichever method is adopted, the end result of giving the Meridian users access to assign a Functional Location to their documents.

Here is an example of the end-user experience with this type of integration.

*Figure 3 – Hierarchical Functional Location data presented in Meridian*

As you can see from the two examples, integrations can mean different things to different people; I hope I have to whet your appetite to know where you can integrate your Meridian environment.

Feel free to reach out and contact Onset Design so we can discuss how we can help you with your integration needs.