All data can be linked, but do you want this too?
Many organizations want to use one source system for all their data, so that no manual work has to be done to have the data available in other systems. This not only concerns data within the organization itself, but also information from the cloud and from third parties (think of suppliers, logistics parties, market places, etc.).
However, it is often not standard possible to get all data in one system and this is not necessary either.
The point is that the right data is available, in the right system, at the right time. This can also be useful for audits, for example.
When linking systems it is wise to take a number of things into account.
Don’t just link everything. When organizations consider application links, they often have the idea that all systems need to be linked. However, it is wise to first check whether (time) gains are achieved by linking the systems together.
Profit can only be gained if there is a high degree of mutation of the data, for static information an annual import may be much cheaper than an automated link. So only make a link if fast availability and accuracy of data plays a role. If changes have to be implemented in time, for example due to productivity or security, then a real-time application link is necessary.
Consider, for example, product and price information that must always be up-to-date in the MDM system, ERP system, the web shop and at market places.
Or think of a new employee who is hired. A link between the HR system, card system and network can ensure that network and physical access are switched on at the push of a button.
Find out how authorizations are granted. For example, by linking information about the role and function of an employee from the HR system, it is also possible to automatically grant authorizations within applications to employees.
This way you ensure that you always comply with privacy legislation.
Input and output
Check whether the application you want to connect to can only receive information or send information. If you want to work with an Enterprise Service Bus (ESB), it is important that the ESB understands which changes have taken place. If an application cannot provide this information, a solution must be found for this.
Using an Identity & Access Management system as an intermediate layer could be an option. Another option is to set up the ESB in such a way that it regularly retrieves information from the application. The time interval for this is predefined.
Reliability of the source file
Perhaps an open door, but of course it is only useful to retrieve data from a source file that generates reliable data in order to prevent contamination of other systems and applications.
A well-known saying in IT is: The special thing about standards is that there are so many.
Many systems and applications communicate in their own language. With data integration, it is important to ensure that the data is delivered in the correct standard in the application in which you want to use it. A good ESB solution offers opportunities for transformation
Many suppliers of applications offer to organize the integration between their system and that of the customer. These are often expensive processes and, after completion of the project as an organization, you have a huge number of points of contact for all applications and systems used.
If you want to connect multiple systems as an organization, it is probably cheaper and more efficient to use an independent integration partner.
If you have business-critical information that needs to be constantly up-to-date, it is advisable to link the data from various systems so that you always work with the most accurate data. If you also consider the above points in your consideration, nothing will stand in the way of seamless integration.