Information system reformation is inevitable as technology evolves and business environments change. Sometimes an information system reformation should be able to respond to changing needs very quickly. However, a complete information system reformation in one go is expensive and difficult to implement. Integration is a solution that can give more time to make the necessary changes.
A good example of utilising integration in an information system reformation is of the customer register implemented by Mtech together with ProAgria and Faba. The customer register was technically outdated and it did not meet all business needs. It was reformatted into a modular solution that uses APIs.
Dozens of applications use the customer register’s data, and the data flow needed to be 100% secure even during the restructuring process. Updating the interfaces of all applications in one go would have been a too big risk.
The interfaces of the applications were gradually changed one by one. This requires that the necessary data is transferred from the reformed customer register to those systems that have not yet been modified. The flow of data during the modificaton was secured with message-based integration, which allowed customer data to be transferred with a small time delay to systems whose interfaces have not yet been reformed. In this way, modifications to old applications can be done gradually and monitored process and, business risks remain low.
Are you wondering about the lifecycle stage of your company’s information systems? Soon we will also be writing in our blog about determining the lifecycle stage of information systems and how to find the required solutions.
Learn more about integrations:
- the use of integrations
- combining data repositories
- getting cost savings with the help of interface solutions
- how integrations create better user experience
- standardisation of data in connection with the system integration implementation