Application conception of SOA in a typical enterprise application case

Recently participated in a typical enterprise application. The project consists of MES, EAI, AND Bi.

MES:
MES Manufacturing Execution System (Manufacturing Execution System ). MES is a new concept proposed by the US management world in the 1990s S. Mesa (mes International Federation) defines MES: MES can optimize and manage the entire production process from the order to the product completion through information transmission. In the event of real-time incidents in the plant, MES can promptly respond to and report such incidents and use the current accurate data to guide and process them.
This project mainly implements the insite TAP system of camstar, just like implementing ERP, there will be some customized development for customers.
This part is beyond my knowledge and skills, so I will not comment too much.

EAI:
Integrate the original ERP system with MES, and integrate MES and equipment control system. MES and ERP are mainly integrated in business, including converting ERP orders into mes tickets and manufacturing batches in MES. Then, the MES information needs to be summarized into a business data of ERP.
This project uses a data integration solution that provides a stage server as a data switch between the two systems. A set of data schema is defined independently on the stage server. Both MES and ERP use this set of independent data schema to input and output data.
I suggest using EAI tools such as BizTalk to ensure the flexibility of Data ing and the transactional nature of business execution. In addition, BizTalk provides a good basic framework, which eliminates the need for manual development.
Similarly, MES and the device control system adopt a similar method for integration.

BI:
This project collects mes ODS (offline data store) from multiple factories and a set of ERP integrated data for query and analysis, and generates various reports.
Theoretically, we need to put the data into Warehouse through the ETL process, and then construct datamart Based on the topic, and then use the corresponding Bi front-end tools for data query and analysis, and report generation and delivery.
This project uses the Bi front-end tool to directly query multiple data sources to implement the basic report function. In this way, if the enterprise's requirements change, isn't it necessary to re-develop a report?

SOA
For such a typical enterprise application, I think that using SOA can solve the current needs well and lay a good foundation for expansion in the future.
First, we need to build an ESB. The construction of ESB may have different functional and performance requirements based on the industry type, scale, and distribution of the system.
Provides SOA service interfaces for various systems and connects them to the ESB. ERP services are generally provided by ERP suppliers, mes services also need to be provided by their suppliers, and other systems are similar. However, a unified SOA standard must be met.
The implementation is to adapt the services connected to the ESB (hook up other services ). After the services of the two systems are attached, You can collaborate with each other. Through SOA, various business systems exchange not independent data, but inter-service calls.
For bi applications with data as the core, I think they can also be integrated into the entire SOA system. First, we can regard the original ETL tool as an independent system. The service provided to the entire SOA is the ETL service; warehouse and datamart can also evolve from a data source to a system that can independently provide services. In this way, you only need to connect the ETL, warehouse, and datamart services to EBS, And the Bi front-end tool can easily obtain the required services from EBS, there is no need to consider what these services provide. Even if there is no warehouse or datamart, you can also call the services of the business system to generate reports. In the future, you only need to replace the service as needed.

(PS: The above text is just a whim, and it is not detailed enough. Please do not be honest !)