Data-centric and process-centric integration are both parts of the integrated structure that Carrier has defined. He defined in 1999 that data-centric is the automation and integration of data, and those data can be exchanged between the information system. Process-centric, on the other hand, is more of involving data and applications together at all levels. Linthicum, Morgenthal and La Forge believes that process-centric integration is the highest level of integration for the business. They are two different integration and organizations can choose what kind of integration structure to use based on what the goal of the organization is since there are pros and cons to both of the integration. Some of the good things about data-centric integration
…show more content…
What are the top two strengths and weaknesses of the integration architecture solution proposed in the case study from IT and business perspective? Why? The strength of the integration architecture solution proposed in the case study is that it is the global application integration solution. Therefore, it is geographically divided into 3 big integrated subsystems. They are Europe, America, and Pacific-Asia. They all have different applications and processes from all subsidiaries that are based in its region, and this solution can integrate them together. Therefore, it will be easier to maximize the performance of the integrated system in the business processes, including the functionality, ERP, and e-business applications. After the systems work out, the systems can be phased out and transferred to the regional ERP. This will benefit these three because the time will be reduced and the process will be so much easier than doing them one by one. Also, it is easier for the regional subsystems to integrate all applications since the systems can be customized automated and integrated with custom applications and e-business solutions. However, the weakness of the integration architecture solution is that the global AI system requires a lot of business re-engineering. The article says that TABCO incorporation thinks that 60% of the overall time has to be something with defining the new system and 90% of the custom systems will be phased out. This will result in a lot of labor …show more content…
This project’s goal was to see if the application integration can be used to compile the various types of applications together, such as legacy systems, e-business solutions, databases and ERP applications. The downside of the project was that the IT department spent 60% of total pilot implementation time on system’s design and 40% on system’s development. It took a long time as a number of systems have to be changed or phased out to support an integrated process. Also, it was difficult to collaborate to automate and redesign the
What are the top two strengths and weaknesses of the integration architecture solution proposed in the case study from IT and business perspective? Why? The strength of the integration architecture solution proposed in the case study is that it is the global application integration solution. Therefore, it is geographically divided into 3 big integrated subsystems. They are Europe, America, and Pacific-Asia. They all have different applications and processes from all subsidiaries that are based in its region, and this solution can integrate them together. Therefore, it will be easier to maximize the performance of the integrated system in the business processes, including the functionality, ERP, and e-business applications. After the systems work out, the systems can be phased out and transferred to the regional ERP. This will benefit these three because the time will be reduced and the process will be so much easier than doing them one by one. Also, it is easier for the regional subsystems to integrate all applications since the systems can be customized automated and integrated with custom applications and e-business solutions. However, the weakness of the integration architecture solution is that the global AI system requires a lot of business re-engineering. The article says that TABCO incorporation thinks that 60% of the overall time has to be something with defining the new system and 90% of the custom systems will be phased out. This will result in a lot of labor …show more content…
This project’s goal was to see if the application integration can be used to compile the various types of applications together, such as legacy systems, e-business solutions, databases and ERP applications. The downside of the project was that the IT department spent 60% of total pilot implementation time on system’s design and 40% on system’s development. It took a long time as a number of systems have to be changed or phased out to support an integrated process. Also, it was difficult to collaborate to automate and redesign the