A detailed research process of PLM-based manufacturing enterprise application system integration
With the development of information technology, manufacturing companies have undergone tremendous changes. At present, more and more application software is used by manufacturing enterprises, and technologies such as CAX (CAD, CAM, CAPP, and CAE), PLM, and ERP have also been continuously promoted and applied. These application systems have a heterogeneous environment, which is used to process heterogeneous information in product definition, process description and production control, and store various data information in different physical systems, which makes them urgently require each network to realize each The integration of enterprise application systems enables information sharing and integration among enterprises. However, the information systems and databases of various enterprises are not the same, which brings problems to the sharing and exchange of information. For this purpose, this article proposes an integration of PLM-based inter-enterprise systems to achieve the sharing and integration of enterprise information. The application system integration of the manufacturing enterprise is a system integration based on the information model of the product life cycle. Define all product data in the product life cycle, and these data are stored in different application systems. In order to make the product information model transparent to all users, these decentralized systems must be integrated into a whole. These systems mainly include CAX, PLM and ERP. The necessity for the integration based on PLM system can be summarized as the following three aspects: First of all, the emphasis of each system is different in the entire life cycle of the product. The CAx system is mainly used for product design, analysis and manufacturing, the PLM system is used to manage product-related data and processes, and the ERP system focuses on implementation management Enterprise human, financial, material, information and other enterprise resources; secondly, due to the different application scope and focus of these systems, the inconsistency of their information models has resulted in "information islands" between application systems, which have not realized enterprise information resources To maximize reuse and sharing, it is a waste of information resources for the enterprise; Finally, the enterprise's product life cycle management is the main development direction of enterprise informatization. Any existing single system cannot complete the entire product life cycle management of the manufacturing enterprise, so it is necessary to use the existing information resources of the enterprise for system integration, which is also an economically feasible way to achieve. 2.1 Issues to be considered for system integration When an enterprise integrates an application system, it is necessary to consider not only the technical factors of the existing system, but also the organization structure, staffing, technical conditions, and integration costs that the enterprise can afford. The higher the degree of integration, the higher the expenditure will be, and the greater the impact on the relevant business departments of the enterprise. In general, system integration requires several considerations: First, to define the data of an object, the information definition and description methods in different application systems are different, and unified definition and description of data are required ; The second is the problem of data control, that is, which data is generated by which personnel. And who controls the information resources that need to be shared; the last is the realization of the integration of heterogeneous computer application systems. 2.2 Structural framework of system integration According to the different ways of system integration, this paper proposes PLM's PLM application system integration framework. The following describes the system framework in detail. The CAX system has the characteristics of diversity and heterogeneity, and the existing different PLM systems also use different system architectures and external interfaces. Therefore, Web-based platform-independent technologies must be used to achieve the integration of the general CAX and PLM systems. Since WebService is completely independent of the Web platform, it defines the communication between applications on the Web, and has nothing to do with the underlying implementation of each application. Therefore, the Web Service platform was selected to implement the integration of CAX and PLM systems. The requirement of platform independence makes us have to shield the bottom implementation details of different systems. Different systems provide a unified calling interface. The Facade design pattern has exactly the above advantages. Therefore, the bottom interfaces of the CAX and PLM systems are encapsulated into Web in Facade mode. Service, in order to shield the underlying interface of the outside, only expose the API required for mutual call, the PLM system can call the Web Service that encapsulates the CAX interface through the Web. Conversely, CAX can also call PLM's WebService, the two call each other through the web, the relationship is equal. The PLM system and the CAX system are the client and server of the Web Service, and the client and server communicate with each other using the SOAP protocol. The two systems use the XML format for information exchange, and each of them converts their internal data format into an XML data format through a data exchange encapsulation interface and sends a request. After receiving the XML format data, it also receives the received XML through the data exchange encapsulation interface. Data is parsed into its own internal format. The most important data integration of ERP and PLM integration is BOM. A product needs to undergo engineering design, process design, and manufacturing before it can finally form a product. In this design process, the BOM table also changes from the engineering bill of materials EBOM to the manufacturing bill of materials MBOM. In PLM, BOM is expressed in the form of product structure tree, which mainly includes material information and product structure information. These are the data that PLM needs to import into ERP. In ERP, the most fundamental role of BOM is to calculate material requirements, costs, and capabilities. For unified integration, we must first resolve the inconsistency of the BOM table. We can establish the equipment BOM (ABOM) as the intermediate stage of the two, including not only the product assembly files, but also the product process equipment, consumables, special tools and technical documents. Because PLM and ERP often come from different manufacturers, the use of XML to transfer BOM information is an effective way. Through the establishment of APIs provided by the ERP system and the PLM system, the information that the system needs to provide is imported or exported, and converted into a unified XML file for information transmission. 3.1 Web Service Technology Through Web services, enterprises can publish shared information and outsourcing information, and their information can be used by Web programs or applications of other companies. Web service features are as follows. 1) Intact encapsulation, for users, it can and can only see the list of functions provided by the object. 2) Loose coupling For loose coupling, especially for Web services in the Internet environment, a message exchange protocol suitable for the Internet environment is required. XML / SOAP is currently the most suitable message exchange protocol. 3) The software platform is independent and highly integrated. Select Web Service platform as the integration platform of PLM and other system integration frameworks. The platform guarantees the dynamic connection between programs through a series of standards and protocols. The most basic protocols include: SOAP, WSDL, UDD I. SOAP (Simple Object Access Protocol) is a protocol for web services message communication, which is the core content; WSDL (Web Services DescripTIon Language) is a web services definition language used to explain SOAP messages and how to exchange these messages; UDDI (Universal DescripTIon, Discovery, and IntegraTIon) are used to centrally store and search WSDL description files, and act as a directory server. After encapsulating the low-level interface, write a web service application on a unified high-level data exchange interface. Since different systems provide a unified high-level data exchange interface, the web service only interacts with the high-level data interface, so you can write a general web service service The program is applied to the integration of different CAPP and PDM systems. By writing common Web Service applications for PLM and other systems, and calling their respective Web Services on the Web, seamless integration of PDM and other systems is achieved. 3.2 XML technology Because the data format of CAX (CAD / CAM / CAPP) and ERP and other systems are different, it is necessary to provide an intermediate general data format to achieve information integration between the two systems. As an efficient, simple and highly open, compatible and cross-platform data storage and data exchange standard, XML has increasingly shown its powerful advantages. The advantages of XML are: (1) A good data format facilitates the design of markup languages ​​related to specific fields, and at the same time facilitates the exchange of data between heterogeneous systems. (2) Good scalability and flexibility XML's scalability and flexibility allow it to describe data in different kinds of application software, and can integrate data from different sources, which facilitates the establishment of data. (3) It is convenient for the network to transmit XML with good compression performance, and will not add too much burden to the network transmission. (4) The highly structured XML document uses a custom logo to decompose the document into elements with a certain meaning, and can be accompanied by additional information (attributes) to each element, thereby becoming a hierarchical data structure. Because XML has so many advantages, XML is selected as the intermediate format to realize data exchange between PLM application system integration. Each independent system converts its own data into the intermediate format of XML, realizes data exchange and information sharing through the integrated framework, and realizes the platform independence and strong portability of the integrated framework. We take the data exchange between CAPP and PLM system as an example to illustrate: CAPP and PLM system exchange data in the form of BOM. CAPP obtains EBOM and its attributes from the PLM system. The main exchange data between the CAPP system and the PDM system is the BOM (Bill OfMaterial, bill of materials) table. CAPP obtains the design BOM and design attributes from the PDM. PDM obtains the process from the CAPP BOM and assembly BOM, the product structure tree is the central content of the BOM table. Here is an example of a product structure tree implemented in XML: The data exchanged between the systems are all encapsulated in XML format, and the XML format and internal data format are converted between each other through their respective data exchange encapsulation interfaces. With the further development of informatization, information integration in the manufacturing industry will become an imperative development trend, making full use of limited enterprise resources to maximize the use of various resources, which is also the responsibility of every designer and enterprise manager. wish. In this paper, through the integration of PLM-based enterprise applications, the design, analysis, manufacturing and management links are organically combined to achieve a certain degree of information sharing and exchange. Due to the complexity of the system, there are still some aspects of this solution, such as service security, which need further in-depth discussion and research. 12V100Ah Lithium Ion Battery,Deep Cycle Solar Battery,2V 100Ah Lifepo4 Battery,12V 100Ah Lifepo4 Battery Pack Jiangsu Zhitai New Energy Technology Co.,Ltd , https://www.jszhitaienergy.com
