Cross-engine data collaboration apparatus and manufacturing execution system

Abstract

This disclosure provides a cross-engine data collaboration device and a manufacturing execution system. The cross-engine data collaboration device is positioned between the transaction engine and the production engine, and includes: a data access module for receiving source business data output by a source capability agent; a collaboration processing module for determining a target capability agent belonging to a different engine from the source capability agent based on the source business data and preset cross-engine collaboration rules, and converting the source business data into collaborative business data adapted to the target capability agent; a task routing module for generating collaborative tasks based on the collaborative business data and sending the collaborative tasks to the target capability agent; and a result coordination module for receiving the execution results generated by the target capability agent executing the collaborative tasks and associating the execution results with the corresponding collaborative tasks. Using the above technical solution, bidirectional data collaboration between the transaction engine and the production engine can be achieved.

Description

Technical Field

[0001] This disclosure relates to the field of semiconductor technology, and more particularly to a cross-engine data collaboration device and manufacturing execution system. Background Technology

[0002] In the daily operation and management of semiconductor manufacturing plants, differences in architecture design, network partitioning, data standards, and business links between enterprise transaction processing systems (such as office automation systems and enterprise resource planning systems, ERP systems) and production execution systems (such as production execution systems, MES systems, and equipment automation systems, EAP systems) lead to obstructed cross-system data flow and disconnected business collaboration.

[0003] Under the current operating model, core aspects such as cross-system business process advancement, production instruction issuance and feedback heavily rely on manual offline recording, cross-departmental communication (such as email, online chat software) and manual verification. This not only causes significant delays in information transmission and greatly reduces the efficiency of business processing and production scheduling, but also makes it easy for various errors to be introduced due to human operation, directly affecting the accuracy of production instruction execution.

[0004] At the same time, information gaps also prevent production management from grasping the equipment operating status and production site data in real time and accurately, making it difficult to achieve refined scheduling and efficient utilization of equipment. Ultimately, this restricts the stable improvement and continuous optimization of production yield, becoming a major bottleneck for Fab cost reduction, efficiency improvement and intelligent operation. Summary of the Invention

[0005] In view of this, embodiments of the present disclosure provide a cross-engine data collaboration device and a manufacturing execution system, which can realize bidirectional data collaboration between the transaction engine and the production engine.

[0006] In a first aspect, embodiments of this disclosure provide a cross-engine data collaboration device disposed between a transaction engine and a production engine, wherein the transaction engine includes at least one transaction capability agent, and the production engine includes at least one production capability agent, and the cross-engine data collaboration device includes: The data access module is used to receive source business data output by the source capability agent, wherein the source capability agent is the transaction capability agent or the production capability agent; The collaborative processing module is used to determine the target capability agent that belongs to a different engine from the source capability agent based on the source business data and the preset cross-engine collaborative rules, and to convert the source business data into collaborative business data that is compatible with the target capability agent. The task routing module is used to generate collaborative tasks based on the collaborative business data and send the collaborative tasks to the target capability agent; The result coordination module is used to receive the execution result generated by the target capability agent in executing the collaborative task, and associate the execution result with the corresponding collaborative task.

[0007] Optionally, each of the transaction capability agents corresponds to at least one transaction business system, and each of the production capability agents corresponds to at least one production business system; The transaction capability proxy and the production capability proxy are respectively used for: Acquire business data generated by the corresponding transaction business system and production business system, and convert the business data into source business data that the cross-engine data collaboration device can recognize; The system receives the collaborative task, calls the local interfaces of the corresponding transaction business system and production business system according to the collaborative task, and returns the execution result to the cross-engine data collaboration device.

[0008] Optionally, the transaction capability agent includes at least one of the following: Office automation capability proxy corresponding to office automation system, enterprise resource planning capability proxy corresponding to enterprise resource planning system, document management capability proxy corresponding to document management system, and production transaction management capability proxy corresponding to production transaction management system; The production capacity agency includes at least one of the following: Manufacturing execution capability proxy corresponding to the manufacturing execution system, equipment automation capability proxy corresponding to the equipment automation system, process or formula management capability proxy corresponding to the process management system or formula management system, yield management capability proxy corresponding to the yield management system, fault detection and classification capability proxy corresponding to the fault detection and classification system, and equipment capability proxy corresponding to the production equipment.

[0009] Optionally, the data access module is further configured to determine the source engine identifier, source capability identifier, and business event type corresponding to the source capability proxy; The cross-engine collaboration rules include the correspondence between the source engine identifier, source capability identifier, and business event type, and the target engine identifier, target capability identifier, and target operation type. The collaborative processing module is used to query the cross-engine collaborative rules based on the source engine identifier, the source capability identifier, and the business event type, determine the target engine identifier, the target capability identifier, and the target operation type, and determine the target capability proxy based on the target engine identifier and the target capability identifier.

[0010] Optionally, the collaborative processing module is used to convert the source business data into standard collaborative data that conforms to a preset cross-engine unified data model according to the source data mapping rule corresponding to the source capability identifier; and to convert the standard collaborative data into collaborative business data that conforms to the data specification of the target capability proxy according to the target data mapping rule corresponding to the target capability identifier and the target operation type.

[0011] Optionally, the data access module is further configured to determine the source capability proxy identifier corresponding to the source capability proxy, and the source service object identifier corresponding to the source service data; The collaborative processing module is also used to generate cross-engine collaborative objects, which include at least a collaborative identifier, the source capability proxy identifier, the target capability proxy identifier corresponding to the target capability proxy, the source business object identifier, the target operation type, and the collaborative business data; The task routing module is used to generate a collaborative task carrying the collaborative identifier based on the target capability agent identifier, the target operation type, and the collaborative business data, and send the collaborative task to the target capability agent; The result coordination module is used to maintain the task communication status and task service status for each of the coordination identifiers. In response to receiving the task acceptance confirmation returned by the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried by the task acceptance confirmation, updates the task communication status to the received status, and keeps the task business status in the incomplete status. In response to receiving the execution result returned by the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried by the execution result, updates the task business status based on the execution result, associates the execution result with the source business object identifier, and sends the task business status or the execution result to the source capability agent based on the source capability agent identifier.

[0012] Optionally, in response to the cross-engine collaboration rule indicating that the source service data corresponds to multiple target capabilities, the collaboration processing module is used to determine multiple target capability proxies that provide the multiple target capabilities respectively, and convert the source service data into collaborative service data adapted to each of the target capability proxies respectively; The task routing module is used to generate multiple collaborative tasks that correspond to the multiple target capability agents and carry the same collaborative identifier, and send each of the collaborative tasks to the corresponding target capability agent. The result coordination module is used to associate the multiple collaborative tasks, the task acceptance confirmations returned by the multiple target capability agents, and the execution results returned by the multiple target capability agents with the same cross-engine collaborative object based on the same collaborative identifier. In response to the completion of all the collaborative tasks, the result coordination module updates the collaborative status corresponding to the same collaborative identifier to the collaborative completion status.

[0013] Optionally, the cross-engine data collaboration device also includes a registration module; The registration module is used to receive capability description information reported by the transaction capability agent and the production capability agent, and generate capability agent registration data based on the capability description information; the capability description information includes at least the capability agent identifier, the engine identifier, the capability identifier, the supported operation type, the interface address, and the agent running status; The collaborative processing module is used to filter capability agents from the capability agent registration data that meet the following conditions based on the target engine identifier, the target capability identifier, and the target operation type: the engine identifier matches the target engine identifier; the capability identifier matches the target capability identifier; the supported operation type includes the target operation type; and the agent's running status is an available state. The collaborative processing module is also used to determine the filtered capability agents as the target capability agent; The task routing module is used to determine the corresponding interface address from the capability agent registration data based on the capability agent identifier of the target capability agent, and send the collaborative task to the target capability agent through the interface address.

[0014] Optionally, the data access module receives source business data, which is encapsulated according to a preset standardized data format and communication protocol, output by the transaction capability agent or the production capability agent through at least one of a standardized API interface and a message queue. The task routing module sends collaborative tasks, encapsulated according to the standardized data format and the communication protocol, to the target capability agent through at least one of the standardized API interface and the message queue.

[0015] Secondly, embodiments of this disclosure also provide a manufacturing execution system, including: The cross-engine data collaboration device described in any of the foregoing embodiments; A transaction engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one transaction capability agent. A production engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one production capacity agent. The production equipment is communicatively connected to the production engine.

[0016] Compared with the prior art, the technical solution of the present disclosure has the following advantages: The cross-engine data collaboration device provided in this embodiment is positioned between the transaction engine and the production engine, enabling business data interaction between them through a unified cross-engine data collaboration layer. Specifically, the data access module receives source business data output from the source capability agent. The collaboration processing module, based on the source business data and preset cross-engine collaboration rules, determines the target capability agent from capability agents belonging to different engines than the source capability agent and converts the source business data into collaborative business data adapted to the target capability agent. The task routing module generates collaborative tasks based on the collaborative business data and sends the collaborative tasks to the target capability agent. After executing the collaborative task, the target capability agent returns the execution result, and the result coordination module associates the execution result with the corresponding collaborative task. Thus, a unified data access, data transformation, task transmission, and result feedback channel can be established between the independent transaction engine and the production engine through the cross-engine data collaboration device, thereby achieving bidirectional data collaboration between the transaction engine and the production engine. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this disclosure, the drawings used in the description of the embodiments of this disclosure or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is a schematic diagram of the structure of a cross-engine data collaboration device provided in an embodiment of this disclosure; Figure 2 This is an interactive diagram illustrating the first type of cross-engine data collaboration in this embodiment of the disclosure; Figure 3 This is a schematic diagram of the second type of cross-engine data collaboration in this embodiment of the disclosure; Figure 4 This is a schematic diagram of the third type of cross-engine data collaboration in this disclosure embodiment. Detailed Implementation

[0019] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the spirit or scope of the embodiments disclosed herein. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0020] Currently, the operation system of semiconductor factories has formed two independent modules in terms of architecture design and actual implementation: transaction processing and production site. Within these two modules, there are problems such as inconsistent data standards, incomplete interface integration, and disconnected business links. Cross-system and cross-module collaboration is severely lacking, resulting in limited overall operational efficiency.

[0021] The transaction processing module relies on independent OA, ERP, DOC and PTMS systems. The data interoperability between these systems is poor, requiring manual data entry, instruction transmission and process connection.

[0022] Taking the film casting business as an example, after initiating the film casting process in the OA system and completing the full process approval, it is necessary to manually create the corresponding order film casting plan in the ERP system and then manually execute the film casting operation. This not only causes a serious disconnect between the business process and the actual production task, but also creates operational redundancy due to multiple manual interventions, which directly leads to low business flow efficiency, longer process cycle, and is also prone to instruction deviation due to human operation errors.

[0023] The production site module is based on the basic collaboration between the MES system and the EAP system, and is equipped with the YMS system and FDC system to realize the monitoring and management of the entire production process. However, the various production systems have only completed basic function docking and have not achieved deep data integration and business collaboration.

[0024] For example, the basic information of wafer lot and the measurement data of each process collected in real time in the MES system cannot be directly synchronized to the database of the YMS system. They need to be processed and converted in format before they can be queried and analyzed in the YMS system. This not only causes the data updates between systems to be out of sync and the data consistency to be difficult to guarantee, but also easily causes problems such as query lag and response delay in the YMS system due to redundancy in the data processing link, which directly affects the timeliness and accuracy of yield analysis and process optimization.

[0025] Therefore, current cross-system operations rely on manual information transmission and repeated parameter configuration, which not only increases labor costs but also makes it easy for human error to cause instruction deviations and data errors.

[0026] Based on this, this disclosure provides a cross-engine data collaboration device, which is positioned between the transaction engine and the production engine, enabling business data interaction between the two engines through a unified cross-engine data collaboration layer. Specifically, the data access module receives source business data output by the source capability agent. The collaboration processing module, based on the source business data and preset cross-engine collaboration rules, determines the target capability agent from capability agents belonging to different engines than the source capability agent, and converts the source business data into collaborative business data adapted to the target capability agent. The task routing module generates collaborative tasks based on the collaborative business data and sends the collaborative tasks to the target capability agent. After executing the collaborative task, the target capability agent returns the execution result, and the result coordination module associates the execution result with the corresponding collaborative task. Thus, a unified data access, data conversion, task transmission, and result feedback channel can be established between the independent transaction engine and the production engine through the cross-engine data collaboration device, thereby achieving bidirectional data collaboration between the transaction engine and the production engine.

[0027] To enable those skilled in the art to have a clearer understanding of the technical concepts, principles, advantages, etc. contained in the embodiments of this disclosure, a detailed description will be provided below with reference to the accompanying drawings, specific embodiments, and specific application scenarios.

[0028] See Figure 1 , Figure 1 This is a schematic diagram of the structure of a cross-engine data collaboration device provided in an embodiment of this disclosure.

[0029] The cross-engine data collaboration device 100 is located between the transaction engine 10A and the production engine 10B.

[0030] Transaction Engine 10A refers to the runtime environment that supports enterprise transaction processing capabilities. Transaction Engine 10A may include at least one transaction capability agent. A transaction capability agent is an interface component, service component, or robot program that encapsulates one or more business capabilities in the transaction system.

[0031] Production Engine 10B refers to the operating environment that carries manufacturing production processing capabilities. Production Engine 10B may include at least one production capacity agent. A production capacity agent is an interface component, service component, or robot program that encapsulates one or more production capabilities in the production system.

[0032] In this embodiment, each of the transaction capability agents corresponds to at least one transaction business system, and each of the production capability agents corresponds to at least one production business system.

[0033] In this case, the transaction capability proxy and the production capability proxy are respectively used to: obtain business data generated by the corresponding transaction business system and production business system, and convert the business data into source business data that can be recognized by the cross-engine data collaboration device; and receive the collaboration task, call the local interface of the corresponding transaction business system and production business system according to the collaboration task, and return the execution result to the cross-engine data collaboration device.

[0034] In the case of acting as a source capability agent, the transaction capability agent or production capability agent obtains the business data generated by the corresponding transaction business system, production business system or production equipment, converts the business data into source business data that can be recognized by the cross-engine data collaboration device, and then sends the source business data to the data access module.

[0035] When acting as a target capability proxy, the transaction capability proxy or production capability proxy receives collaborative tasks sent by the task routing module, calls the local interface of the corresponding transaction business system, production business system, or production equipment according to the collaborative task, and returns the execution result obtained through the local interface to the cross-engine data collaboration device. Thus, the cross-engine data collaboration device can interact with different transaction business systems, production business systems, or production equipment through each capability proxy without needing to directly adapt to the local interfaces of each business system or production equipment.

[0036] In this embodiment, the transaction capability proxy includes at least one of the following: Office Automation Bot (OA Bot) corresponding to Office Automation System, Enterprise Resource Planning Bot (ERP Bot) corresponding to Enterprise Resource Planning System, Document Management Bot (DOCBot) corresponding to Document Management System, and Production Transaction Management Bot (PTMS Bot) corresponding to Production Transaction Management System.

[0037] Production capacity agency includes at least one of the following: Manufacturing Execution Capability Agent (MES Bot) corresponding to Manufacturing Execution System, Equipment Automation Capability Agent (EAP Bot) corresponding to Equipment Automation System, Process or Recipe Management Capability Agent (PMS Bot) corresponding to Process Management System or Recipe Management System, Yield Management Capability Agent (YMS Bot) corresponding to Yield Management System, Fault Detection and Classification Capability Agent (FDC Bot) corresponding to Fault Detection and Classification System, and Equipment Capability Agent (Equipment Bot) corresponding to Production Equipment.

[0038] Accordingly, the cross-engine data collaboration device 100 may include: Data access module 110 is used to receive source business data output by the source capability agent, wherein the source capability agent is the transaction capability agent or the production capability agent; The collaborative processing module 120 is used to determine the target capability agent that belongs to a different engine from the source capability agent based on the source business data and the preset cross-engine collaborative rules, and to convert the source business data into collaborative business data that is compatible with the target capability agent. The task routing module 130 is used to generate a collaborative task based on the collaborative business data and send the collaborative task to the target capability agent; The result coordination module 140 is used to receive the execution result generated by the target capability agent in executing the collaborative task, and associate the execution result with the corresponding collaborative task.

[0039] In some embodiments, the data access module 110 can communicate with each transaction capability agent and each production capability agent to receive source business data output by any capability agent. In a cross-engine collaboration process, the capability agent that outputs the source business data is designated as the source capability agent, and another engine, different from the engine to which the source capability agent belongs, is designated as the target engine.

[0040] In this embodiment, the source business data may include a data header and a data body. The data header may include a message identifier, a source engine identifier, a source capability proxy identifier, a data model version, a data operation type, and a data generation time; the data body may include a business object identifier, an object type, an object status, an object version, and the corresponding business content.

[0041] Specifically, when the transaction capability agent in the transaction engine detects that the corresponding transaction business system generates business data that needs to be transmitted to the production engine, the transaction capability agent sends the business data as source business data to the cross-engine data collaboration device 100.

[0042] The data access module 110 receives source business data and identifies the transaction capability proxy that provides the source business data as the source capability proxy. The collaborative processing module 120 queries preset cross-engine collaborative rules based on the business information carried in or parsed from the source business data to determine the production capability proxy in the production engine that can process the source business data, and uses the determined production capability proxy as the target capability proxy.

[0043] Subsequently, the collaborative processing module 120 transforms the source business data according to the data structure that the target capability agent can recognize, obtaining collaborative business data. The task routing module 130 encapsulates the collaborative business data and the target operation corresponding to the target capability agent into a collaborative task, and sends the collaborative task to the target capability agent. The target capability agent calls the corresponding production business system or production equipment to execute the collaborative task, returns the execution result to the cross-engine data collaboration device, and the result coordination module then associates the execution result with the corresponding collaborative task.

[0044] Similarly, when the output of the production capability agent in the production engine needs to be transmitted to the source business data of the transaction engine, the collaborative processing module can determine the target capability agent from the transaction capability agent and transmit the source business data generated by the production engine to the transaction engine according to the same processing procedure, thereby realizing bidirectional data collaboration between the transaction engine and the production engine.

[0045] Therefore, the transaction engine and the production engine do not need to build point-to-point interfaces for each pair of business systems. They can complete business data access, collaboration goal determination, data adaptation, task distribution and execution result feedback through the cross-engine data collaboration layer, reducing direct dependencies between systems and improving the collaboration efficiency between the transaction processing module and the production site module.

[0046] In some embodiments, the data access module receives source business data output by the transaction capability agent or the production capability agent, which is encapsulated according to a preset standardized data format and communication protocol, through at least one of a standardized API interface and a message queue; the task routing module sends a collaborative task encapsulated according to the standardized data format and the communication protocol to the target capability agent through at least one of the standardized API interface and the message queue.

[0047] By adopting at least one communication method among standardized API interfaces and message queues, it is possible to reduce the adaptation of dedicated interfaces between different systems while retaining both synchronous and asynchronous transmission methods; combined with acknowledgment, retry, persistence, and dead letter handling mechanisms, the compatibility and stability of data transmission between agents with different capabilities can be improved.

[0048] In some embodiments, the data access module is further configured to determine the source engine identifier, source capability identifier, and business event type corresponding to the source capability proxy; the cross-engine collaboration rule includes the source engine identifier, source capability identifier, and business event type, and the correspondence between them and the target engine identifier, target capability identifier, and target operation type; the collaboration processing module is configured to query the cross-engine collaboration rule according to the source engine identifier, the source capability identifier, and the business event type, determine the target engine identifier, the target capability identifier, and the target operation type, and determine the target capability proxy according to the target engine identifier and the target capability identifier.

[0049] Specifically, after receiving the source business data, the data access module determines the source capability proxy based on the sender of the source business data and obtains the source engine identifier and source capability identifier corresponding to the source capability proxy. The source engine identifier is used to distinguish whether the source capability proxy belongs to the transaction engine or the production engine; the source capability identifier is used to represent the business capabilities output by the source capability proxy. The data access module can also determine the business event type corresponding to the current source business data based on the event fields, operation fields, or business status fields carried by the source business data.

[0050] Cross-engine collaboration rules can be pre-stored as rule records, each including matching conditions and collaboration results. The matching conditions must include at least the source engine identifier, source capability identifier, and business event type, while the collaboration results must include at least the target engine identifier, target capability identifier, and target operation type. The collaboration processing module uses the source engine identifier, source capability identifier, and business event type corresponding to the current source business data as query conditions to determine the matching rule record from the cross-engine collaboration rules, and then obtains the target engine identifier, target capability identifier, and target operation type from that rule record.

[0051] For example, when the source engine identifier indicates a transaction engine, the source capability identifier indicates an order publishing capability, and the business event type indicates that an order has been published, the matched cross-engine collaboration rules can indicate that the target engine is a production engine, the target capability is a production work order processing capability, and the target operation is creating a production work order. Based on this, the collaboration processing module determines the target capability proxy that can provide production work order processing capability from the production engine.

[0052] The target engine identifier is used to define the engine to which the target capability agent belongs, the target capability identifier is used to define the business capabilities that the target capability agent needs to have, and the target operation type is used to define the operation that the target capability agent performs after receiving a collaborative task.

[0053] By employing these three layers, the ability to determine target capabilities based solely on system names or fixed interface addresses can be avoided. Consequently, the source business system only needs to output its own generated business events, without needing to know the specific target system and its interface address in another engine beforehand. The cross-engine data collaboration device can automatically establish the correspondence between source business events and target business operations based on cross-engine collaboration rules, improving the configurability of cross-engine business routing.

[0054] Furthermore, the collaborative processing module is used to convert the source business data into standard collaborative data that conforms to a preset cross-engine unified data model according to the source data mapping rules corresponding to the source capability identifier; and to convert the standard collaborative data into collaborative business data that conforms to the data specification of the target capability proxy according to the target data mapping rules corresponding to the target capability identifier and the target operation type.

[0055] Specifically, the collaborative processing module determines the source data mapping rules corresponding to the source capability proxy based on the source capability identifier. The source data mapping rules describe the correspondence between data fields in the source business data and standard fields in the cross-engine unified data model. Following the source data mapping rules, the collaborative processing module extracts the data fields participating in this cross-engine collaboration from the source business data and converts the extracted data fields into the data structure required by the cross-engine unified data model, thus obtaining standard collaborative data.

[0056] Standard collaborative data can include data portions describing business objects and data portions describing business operations. Business object data represents the business objects and their attributes processed in this cross-engine collaboration, while business operation data represents the operations to be performed on the business object and the parameters required to perform those operations. Standard collaborative data does not depend on specific transaction or production business systems, thus serving as an intermediate data carrier between the source and target data models.

[0057] After obtaining the standard collaborative data, the collaborative processing module determines the target data mapping rules based on the target capability identifier and the target operation type. The target data mapping rules describe the correspondence between standard fields in the standard collaborative data and the data specifications of the target capability agent. The collaborative processing module then reorganizes the standard collaborative data according to the target data mapping rules to obtain the collaborative business data required for the target capability agent to execute the target operation.

[0058] For example, a field representing the same business object in the source business system might be named as "First Field Name," while the target business system requires the use of "Second Field Name." The collaborative processing module first maps the "First Field Name" to a standard field name in the unified data model, and then maps the standard field name to the "Second Field Name," without needing to establish a separate set of direct conversion rules between the source and target business systems.

[0059] Therefore, when adding a new business system or adjusting the data structure of an existing business system, it is only necessary to establish or modify the data mapping relationship between the business system and the cross-engine unified data model to achieve data collaboration with other already connected business systems, thereby reducing the number of data mapping combinations between different business systems.

[0060] In some embodiments, the data access module is further configured to determine the source capability proxy identifier corresponding to the source capability proxy and the source service object identifier corresponding to the source service data; the collaboration processing module is further configured to generate a cross-engine collaboration object, the cross-engine collaboration object including at least a collaboration identifier, the source capability proxy identifier, the target capability proxy identifier corresponding to the target capability proxy, the source service object identifier, the target operation type, and the collaboration service data; the task routing module is configured to generate a collaboration task carrying the collaboration identifier according to the target capability proxy identifier, the target operation type, and the collaboration service data, and send the collaboration task to the target capability proxy; the result coordination module is configured to, for each collaboration identifier The system maintains the task communication status and task service status separately. In response to receiving a task acceptance confirmation from the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried in the task acceptance confirmation, updates the task communication status to the received status, and keeps the task service status in the incomplete status. In response to receiving an execution result from the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried in the execution result, updates the task service status based on the execution result, associates the execution result with the source service object identifier, and sends the task service status or the execution result to the source capability agent based on the source capability agent identifier.

[0061] Specifically, when the data access module receives source service data, it determines the source capability proxy identifier that sent the source service data, and obtains or generates a source service object identifier from the source service data. The source service object identifier is used to distinguish different service objects generated by the source service system, so that the execution result can be returned to the corresponding source service object.

[0062] After identifying the target capability proxy and completing data transformation, the collaboration processing module generates a collaboration identifier for this cross-engine collaboration and a corresponding cross-engine collaboration object. The cross-engine collaboration object records the source capability proxy identifier, target capability proxy identifier, source business object identifier, target operation type, and collaboration business data. The task routing module retrieves the target capability proxy identifier, target operation type, and collaboration business data from the cross-engine collaboration object, generates a collaboration task, writes the collaboration identifier into the collaboration task, and sends it to the target capability proxy.

[0063] After receiving a collaborative task, the target capability agent can first return a task acceptance confirmation carrying a collaborative identifier to the result coordination module. The result coordination module then queries the corresponding cross-engine collaborative object based on the collaborative identifier and updates the task communication status of that collaborative task to the received status. Since the task acceptance confirmation only indicates that the target capability agent has received the collaborative task, the task business status remains incomplete at this time.

[0064] After the target capability agent calls the local interface of the target business system or production equipment, it generates an execution result based on the return content of the local interface and writes the collaboration identifier into the execution result. The result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried in the execution result, and updates the task business status according to the execution success, execution failure, or processing status indicated by the execution result. At the same time, the result coordination module associates the execution result with the source business object based on the source business object identifier recorded in the cross-engine collaboration object, and sends the task business status or execution result to the source capability agent based on the source capability agent identifier.

[0065] Therefore, the same collaborative identifier can be used to connect source business data, collaborative tasks, task reception confirmation and execution results to form a complete collaborative processing record. By maintaining the task communication status and task business status separately, the mistaken assumption that the target business has been completed when the message has been delivered can be avoided, thus improving the accuracy of cross-engine collaborative status judgment.

[0066] In some embodiments, in response to the cross-engine collaboration rule indicating that the source service data corresponds to multiple target capabilities, the collaboration processing module is configured to determine multiple target capability proxies that provide the multiple target capabilities, and convert the source service data into collaborative service data adapted to each of the target capability proxies; the task routing module is configured to generate multiple collaborative tasks corresponding to the multiple target capability proxies and carrying the same collaboration identifier, and send each of the collaborative tasks to the corresponding target capability proxies; the result coordination module is configured to associate the multiple collaborative tasks, the task acceptance confirmations returned by the multiple target capability proxies, and the execution results returned by the multiple target capability proxies with the same cross-engine collaboration object according to the same collaboration identifier; in response to the completion of all the multiple collaborative tasks, the result coordination module updates the collaboration status corresponding to the same collaboration identifier to the collaboration completion status.

[0067] Specifically, a source business data can correspond to multiple target capabilities based on cross-engine collaboration rules, so that the same source business event can trigger multiple target business systems to perform corresponding operations respectively.

[0068] Accordingly, the collaboration processing module queries cross-engine collaboration rules based on the source engine identifier, source capability identifier, and business event type. When the query result includes multiple target capability identifiers, the collaboration processing module determines the corresponding target capability proxy based on each target capability identifier. Since the data specifications of different target capability proxies may differ, the collaboration processing module determines target data mapping rules for each target capability proxy and converts the same source business data into collaborative business data adapted to each target capability proxy.

[0069] The collaborative processing module generates a cross-engine collaborative object and a collaborative identifier for the source business data. The task routing module generates multiple collaborative tasks based on the target operation type and collaborative business data corresponding to each target capability agent. Each collaborative task points to its corresponding target capability agent, but all carry the same collaborative identifier to indicate that multiple collaborative tasks originate from the same source business event.

[0070] Each target capability agent returns task acceptance confirmation and execution result. The result coordination module, based on the same coordination identifier, associates multiple coordination tasks and their corresponding task acceptance confirmations and execution results with the same cross-engine coordination object. The result coordination module can record the task communication status and task business status of each coordination task, and determine whether each coordination task has been completed. When multiple coordination tasks have returned execution results indicating completion, the result coordination module updates the coordination status corresponding to that coordination identifier to the coordination completion status.

[0071] If some collaborative tasks have been completed while others are still incomplete, the collaborative state can remain in the state of collaborative execution. This allows the source capability agent to know that the entire cross-engine collaboration is not yet complete, rather than judging the overall collaborative state based solely on the execution result of one collaborative task.

[0072] This allows for unified grouping and status tracking of multiple target tasks generated from the same source business data, improving the integrity of one-to-many cross-engine business collaboration.

[0073] In one alternative embodiment, the cross-engine data collaboration device further includes a registration module.

[0074] The registration module is used to receive capability description information reported by the transaction capability agent and the production capability agent, and generate capability agent registration data based on the capability description information; the capability description information includes at least a capability agent identifier, an engine identifier, a capability identifier, supported operation types, an interface address, and an agent running status; the collaboration processing module is used to filter capability agents from the capability agent registration data that meet the following conditions based on the target engine identifier, the target capability identifier, and the target operation type: the engine identifier matches the target engine identifier; the capability identifier matches the target capability identifier; the supported operation types include the target operation type; and the agent running status is available; the collaboration processing module is also used to determine the filtered capability agents as the target capability agent; the task routing module is used to determine the corresponding interface address from the capability agent registration data based on the capability agent identifier of the target capability agent, and send the collaboration task to the target capability agent through the interface address.

[0075] The cross-engine data collaboration device maintains the business capabilities and current availability provided by transaction capability agents and production capability agents through the registration module, so as to dynamically determine the target capability agent that actually receives the collaboration task based on the target capability.

[0076] Specifically, when transaction capability agents and production capability agents connect to the cross-engine data collaboration device, they report capability description information to the registration module. This capability description information includes the capability agent identifier, the engine identifier, the capability identifier, supported operation types, interface addresses, and agent running status. The registration module distinguishes different capability agents by their capability agent identifiers and writes the capability description information reported by each capability agent into the capability agent registration data.

[0077] When the capabilities, interface addresses, or operational status provided by a capability agent change, the capability agent can resubmit the updated capability description information. The registration module then updates the corresponding record in the capability agent registration data based on the capability agent identifier. In this way, the capability agent registration data can reflect the capability agents currently connected to the cross-engine data collaboration device and the capabilities they can provide.

[0078] After obtaining the target engine identifier, target capability identifier, and target operation type based on cross-engine collaboration rules, the collaborative processing module queries the capability agent registration data. First, it filters capability agents whose engine matches the target engine based on the target engine identifier; second, it filters capability agents that can provide the target capability based on the target capability identifier; third, it filters capability agents that support the corresponding target operation based on the target operation type; finally, it excludes capability agents that are unavailable based on their running status. The collaborative processing module then identifies the filtered capability agents as the target capability agents.

[0079] The task routing module retrieves the corresponding interface address of the target capability proxy from the capability proxy registration data based on the capability proxy identifier of the target capability proxy, and sends the collaborative task to the target capability proxy through the retrieved interface address. In this way, cross-engine collaborative rules only need to define the target capability to be invoked, without having to directly record the interface address of a specific capability proxy.

[0080] This allows for the separation of business capabilities from the specific capability proxy instances that carry those capabilities. When a capability proxy is added, replaced, deactivated, or its interface address changes, there is no need to modify the cross-engine collaboration rules; simply updating the capability proxy registration data is sufficient to continue routing the target capability, thus improving the ease of system expansion and maintenance.

[0081] To better illustrate and understand the working mechanism of the cross-engine data collaboration device in the embodiments of this disclosure, specific examples are provided.

[0082] See Figure 2 , Figure 2 This is a schematic diagram of the first type of cross-engine data collaboration in this disclosure embodiment.

[0083] The resource planning from the ERP Bot and the task requirements from the PTMS Bot are transmitted to the MES Bot via the cross-engine data collaboration device 100. The MES Bot then formulates a production plan and transmits production-related information to the EAP Bot.

[0084] The EAP Bot automatically translates protocols and parses instructions, directly sending standardized instructions to the corresponding production equipment, ensuring that the instructions are 100% matched with the MES Bot requirements, and achieving precise automation from decision-making to execution.

[0085] See Figure 3 , Figure 3 This is a schematic diagram of the second type of cross-engine data collaboration in this embodiment of the disclosure.

[0086] The EAP bot captures real-time data on equipment operating status and production completion, synchronizing it to the MES bot. The MESBot updates the work-in-process (WIP) status instantly and feeds back data such as production progress, equipment capacity, and task progress to the ERP bot and PTMS bot through a cross-engine data collaboration layer, enabling visualized tracking of production status and eliminating management blind spots.

[0087] See Figure 4 , Figure 4 This is a schematic diagram of the third type of cross-engine data collaboration in this disclosure embodiment.

[0088] Equipment Bot collects real-time equipment operating status data and, combined with the maintenance plan model transmitted by PMS Bot through the cross-engine data collaboration device 100, dynamically optimizes equipment maintenance time and content, ensuring that maintenance plans are dynamically matched with production schedules and reducing unplanned downtime.

[0089] This application describes multiple embodiment schemes provided by the present disclosure. The optional methods described in each embodiment scheme can be combined and cross-referenced with each other without conflict, thereby extending to a variety of possible embodiment schemes. These can all be considered as the embodiment schemes disclosed and made public by the present disclosure.

[0090] This disclosure also provides a manufacturing execution system corresponding to the cross-engine data collaboration device of any of the above embodiments, which will be described below. It should be noted that the content of the cross-engine data collaboration device described below can be referred to in correspondence with the content of the cross-engine data collaboration device described above.

[0091] In some embodiments, the manufacturing execution system may include: Cross-engine data collaboration device as described in any of the foregoing embodiments; A transaction engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one transaction capability agent. A production engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one production capacity agent. The production equipment is communicatively connected to the production engine.

[0092] The specific details regarding the structure, connection relationships, functions, and working principles of the cross-engine data collaboration device can be found in the descriptions and accompanying figures above, and will not be repeated here.

[0093] While the embodiments disclosed herein are as described above, the invention is not limited thereto. Any person skilled in the art can make various modifications and alterations without departing from the spirit and scope of the invention; therefore, the scope of protection of the invention should be determined by the scope defined in the claims.

Claims

1. A cross-engine data collaboration device, characterized in that, Located between the transaction engine and the production engine, the transaction engine includes at least one transaction capability agent, and the production engine includes at least one production capability agent. The cross-engine data collaboration device includes: The data access module is used to receive source business data output by the source capability agent, wherein the source capability agent is the transaction capability agent or the production capability agent; The collaborative processing module is used to determine the target capability agent that belongs to a different engine from the source capability agent based on the source business data and the preset cross-engine collaborative rules, and to convert the source business data into collaborative business data that is compatible with the target capability agent. The task routing module is used to generate collaborative tasks based on the collaborative business data and send the collaborative tasks to the target capability agent; The result coordination module is used to receive the execution result generated by the target capability agent in executing the collaborative task, and associate the execution result with the corresponding collaborative task.

2. The cross-engine data collaboration device according to claim 1, characterized in that, Each of the aforementioned transaction capability agents corresponds to at least one transaction business system, and each of the aforementioned production capability agents corresponds to at least one production business system; The transaction capability proxy and the production capability proxy are respectively used for: Acquire business data generated by the corresponding transaction business system and production business system, and convert the business data into source business data that the cross-engine data collaboration device can recognize; The system receives the collaborative task, calls the local interfaces of the corresponding transaction business system and production business system according to the collaborative task, and returns the execution result to the cross-engine data collaboration device.

3. The cross-engine data collaboration device according to claim 2, characterized in that, The transaction capability proxy includes at least one of the following: Office automation capability proxy corresponding to office automation system, enterprise resource planning capability proxy corresponding to enterprise resource planning system, document management capability proxy corresponding to document management system, and production transaction management capability proxy corresponding to production transaction management system; The production capacity agency includes at least one of the following: Manufacturing execution capability proxy corresponding to the manufacturing execution system, equipment automation capability proxy corresponding to the equipment automation system, process or formula management capability proxy corresponding to the process management system or formula management system, yield management capability proxy corresponding to the yield management system, fault detection and classification capability proxy corresponding to the fault detection and classification system, and equipment capability proxy corresponding to the production equipment.

4. The cross-engine data collaboration device according to claim 1, characterized in that, The data access module is also used to determine the source engine identifier, source capability identifier, and business event type corresponding to the source capability proxy; The cross-engine collaboration rules include the correspondence between the source engine identifier, source capability identifier, and business event type, and the target engine identifier, target capability identifier, and target operation type. The collaborative processing module is used to query the cross-engine collaborative rules based on the source engine identifier, the source capability identifier, and the business event type, determine the target engine identifier, the target capability identifier, and the target operation type, and determine the target capability proxy based on the target engine identifier and the target capability identifier.

5. The cross-engine data collaboration device according to claim 4, characterized in that, The collaborative processing module is used to convert the source business data into standard collaborative data that conforms to a preset cross-engine unified data model according to the source data mapping rules corresponding to the source capability identifier. And according to the target data mapping rules corresponding to the target capability identifier and the target operation type, the standard collaborative data is converted into collaborative business data that conforms to the data specification of the target capability agent.

6. The cross-engine data collaboration device according to claim 4, characterized in that, The data access module is also used to determine the source capability proxy identifier corresponding to the source capability proxy, and the source service object identifier corresponding to the source service data; The collaborative processing module is also used to generate cross-engine collaborative objects, which include at least a collaborative identifier, the source capability proxy identifier, the target capability proxy identifier corresponding to the target capability proxy, the source business object identifier, the target operation type, and the collaborative business data; The task routing module is used to generate a collaborative task carrying the collaborative identifier based on the target capability agent identifier, the target operation type, and the collaborative business data, and send the collaborative task to the target capability agent; The result coordination module is used to maintain the task communication status and task service status for each of the coordination identifiers. In response to receiving the task acceptance confirmation returned by the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried by the task acceptance confirmation, updates the task communication status to the received status, and keeps the task business status in the incomplete status. In response to receiving the execution result returned by the target capability agent, the result coordination module determines the corresponding cross-engine collaboration object based on the collaboration identifier carried by the execution result, updates the task business status based on the execution result, associates the execution result with the source business object identifier, and sends the task business status or the execution result to the source capability agent based on the source capability agent identifier.

7. The cross-engine data collaboration device according to claim 6, characterized in that, In response to the cross-engine collaboration rule indicating that the source service data corresponds to multiple target capabilities, the collaboration processing module is used to determine multiple target capability proxies that provide the multiple target capabilities, and convert the source service data into collaborative service data adapted to each of the target capability proxies; The task routing module is used to generate multiple collaborative tasks that correspond to the multiple target capability agents and carry the same collaborative identifier, and send each of the collaborative tasks to the corresponding target capability agent. The result coordination module is used to associate the multiple collaborative tasks, the task acceptance confirmations returned by the multiple target capability agents, and the execution results returned by the multiple target capability agents with the same cross-engine collaborative object based on the same collaborative identifier. In response to the completion of all the collaborative tasks, the result coordination module updates the collaborative status corresponding to the same collaborative identifier to the collaborative completion status.

8. The cross-engine data collaboration device according to claim 4, characterized in that, It also includes a registration module; The registration module is used to receive capability description information reported by the transaction capability agent and the production capability agent, and generate capability agent registration data based on the capability description information; the capability description information includes at least the capability agent identifier, the engine identifier, the capability identifier, the supported operation type, the interface address, and the agent running status; The collaborative processing module is used to filter capability agents from the capability agent registration data that meet the following conditions based on the target engine identifier, the target capability identifier, and the target operation type: the engine identifier matches the target engine identifier; the capability identifier matches the target capability identifier; the supported operation type includes the target operation type; and the agent's running status is an available state. The collaborative processing module is also used to determine the filtered capability agents as the target capability agent; The task routing module is used to determine the corresponding interface address from the capability agent registration data based on the capability agent identifier of the target capability agent, and send the collaborative task to the target capability agent through the interface address.

9. The cross-engine data collaboration device according to claim 1, characterized in that, The data access module receives source business data, which is encapsulated according to a preset standardized data format and communication protocol, output by the transaction capability agent or the production capability agent through at least one of a standardized API interface and a message queue. The task routing module sends collaborative tasks, encapsulated according to the standardized data format and the communication protocol, to the target capability agent through at least one of the standardized API interface and the message queue.

10. A manufacturing execution system, characterized in that, include: The cross-engine data collaboration device as described in any one of claims 1 to 9; A transaction engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one transaction capability agent. A production engine, which is communicatively connected to the cross-engine data collaboration device, includes at least one production capacity agent. The production equipment is communicatively connected to the production engine.

Images