A data-driven and templated configuration-based manufacturing execution system platform

Abstract

This invention discloses a manufacturing execution system (MES) platform based on data-driven and templated configuration, relating to the field of MES technology. It includes: receiving data operation requests sent by a front-end interface. By setting a unified universal interface endpoint as the sole entry point for back-end data operations, the platform receives data operation requests from the front-end interface, generates control data based on the control code, and returns both business data and control data to the front-end interface. This allows the front-end interface to perform differentiated display and interactive control based on the control data. This solves the technical problems of low development efficiency in traditional MES architectures, such as requiring dedicated application code to be written for each business function in both the front-end and back-end to implement CRUD operations, requiring independent API interface development for each new business function, resulting in large amounts of code, repeated compilation and deployment, and difficulties in parallel development.

Description

Technical Field

[0001] This invention relates to the field of manufacturing execution system technology, and in particular to a manufacturing execution system platform based on data-driven and templated configuration. Background Technology

[0002] In modern industrial manufacturing, Manufacturing Execution Systems (MES), as the core information system connecting enterprise planning and management with shop floor production execution, undertake key functions such as production scheduling, process management, quality traceability, and material control. They play a crucial role in improving production efficiency, ensuring product quality, and optimizing resource allocation. Their operation and control are based on the collaborative principles of information technology and industrial automation. By integrating equipment, material, and process data from the production site, they achieve visualized control and precise scheduling of the entire production process. MES are widely used in semiconductor packaging and testing, flexible circuit board manufacturing, electronic assembly, and automotive parts processing, and are key equipment supporting lean manufacturing and process manufacturing enterprises in achieving lean production and digital transformation.

[0003] Currently, while traditional Manufacturing Execution Systems (MES) possess basic operational management functions, significant technical bottlenecks remain. Most systems employ a traditional layered architecture: a three-tier structure comprising a front-end presentation layer, a back-end business logic layer, and a data access layer. Each business function requires dedicated application code to implement CRUD operations in the back-end. Adding or changing a business function necessitates a complete development process, including database design, back-end API development, front-end interface development, and integration testing, resulting in long development cycles and substantial code writing. Some systems lack a unified interface management mechanism, requiring the development of dedicated interface programs for each heterogeneous system, leading to poor system scalability and complex maintenance. Furthermore, some systems lack the ability to control the front-end through back-end data, with business logic scattered across the front-end interface and back-end code. Changes in business requirements necessitate simultaneous modifications to both front-end and back-end code and redeployment, hindering rapid response to the personalized needs of different customers and factories and impacting system development efficiency and flexibility. Summary of the Invention

[0004] The purpose of this invention is to provide a manufacturing execution system platform based on data-driven and templated configuration, which solves the technical problems mentioned in the background art.

[0005] To achieve the above objectives, the present invention provides the following technical solution: a manufacturing execution system platform based on data-driven and templated configuration, comprising: Receive data operation requests sent by the front-end interface; wherein, the data operation request includes operation type, target data table identifier, operation data content, user identity information and control code; Load the pre-configured permission rules based on the user's identity information; Based on the operation type and the target data table identifier, and combined with the pre-configured data table structure information, a database operation statement is dynamically generated, and the permission rule is injected into the database operation statement. Execute the database operation statements to obtain business data; Control data is generated based on the control code, and the business data and the control data are returned together to the front-end interface; The manufacturing execution system platform receives data operation requests from all business functions through a unified universal interface endpoint. The universal interface endpoint is the only entry point for backend data operations in the platform. The control code is used to define the display rules and interaction control rules of the front-end interface.

[0006] Compared with related technologies, the manufacturing execution system platform based on data-driven and templated configuration provided by this invention has the following advantages: 1. This invention provides a manufacturing execution system platform based on data-driven and templated configuration. By setting a unified universal interface endpoint as the sole entry point for backend data operations, it receives data operation requests sent by the frontend interface, generates control data according to the control code, and returns both business data and control data to the frontend interface. This allows the frontend interface to perform differentiated display and interactive control based on the control data. This solves the technical problems of low development efficiency in traditional MES architectures, such as the need to write dedicated application code for each business function in the frontend and backend to implement CRUD operations, the need for independent API interface development for each new business function, large amount of code development, the need for repeated compilation and deployment, and the difficulty of parallel development.

[0007] 2. This invention provides a manufacturing execution system platform based on data-driven and templated configuration. It integrates multiple database adapters into a universal interface endpoint and supports both Restful Web API and SOAP Web Service protocols. A three-layer authentication system, linking interface keys with security codes and verification codes, authenticates data operation requests. Based on user identity information, it loads functional, row-level, and column-level permission rules. Functional permissions are implemented through menu configuration and role binding; row-level permissions are implemented by dynamically injecting filtering conditions into the WHERE clause of database operation statements; and column-level permissions are implemented by dynamically adjusting the field list in the SELECT clause of database operation statements. The universal interface endpoint assigns interface keys to the warehouse management system and receives its business operation requests, enabling the warehouse management system to share the platform's permission rules and data table operation capabilities. This solves the technical problems of traditional MES architectures, such as the need to develop dedicated interface programs for each heterogeneous system interface, the requirement for separate interface program development when integrating WMS and MES, inconsistent permission systems between the two systems, coarse-grained permission control (limited to functional module level control), and the inability to achieve fine-grained row and column-level permission management.

[0008] 3. This invention provides a manufacturing execution system platform based on data-driven and template-based configuration. It allows for free assembly of workstation templates based on task groups, and the underlying framework supports both discrete and process manufacturing industries. After generating a process flow model by acquiring process flow configuration information through a visual process modeling interface, it associates the model with a universal interface endpoint. This allows each process node in the process flow model to perform data read / write operations through the universal interface endpoint. Furthermore, by acquiring the current workstation identifier and the current task identifier, it matches the corresponding SOP display content from a pre-configured SOP template library and displays it synchronously with the current workstation's operation interface. This solves the technical problems of traditional MES systems requiring customized development for different manufacturing industries and factory production lines, requiring modification of backend code and redeployment for process flow changes, and requiring operators to manually search for paper or electronic SOP documents when performing tasks, as well as the inability of SOPs to automatically switch when switching workstations. Attached Figure Description

[0009] Fig. 1 This is an extended flowchart of the core main processing flow of the present invention; Fig. 2 This is an extended flowchart of the key functional modules of the present invention; Fig. 3 This is an extended flowchart to expand the application capabilities of this invention. Detailed Implementation

[0010] The technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0011] Example 1: Please see Figs. 1-3 This invention provides a technical solution: a manufacturing execution system platform based on data-driven and templated configuration, comprising: Receive data operation requests sent from the front-end interface; the data operation request includes operation type, target data table identifier, operation data content, user identity information and control code; Load pre-configured permission rules based on user identity information; Based on the operation type and target data table identifier, and combined with the pre-configured data table structure information, database operation statements are dynamically generated, and permission rules are injected into the database operation statements. Execute database operation statements to obtain business data; Control data is generated based on the control code, and both business data and control data are returned to the front-end interface. Among them, the Manufacturing Execution System platform receives data operation requests from all business functions through a unified universal interface endpoint. The universal interface endpoint is the only entry point for backend data operations in the platform, and the control code is used to define the display rules and interaction control rules of the front-end interface. In this implementation, the front-end interface is a templated page that does not contain business logic judgments or data processing rules. All business rules are predefined by the back-end database layer through configuration. Upon receiving a user operation, the front-end interface encapsulates the operation data into an HTTP request according to the predefined control code rules in the back-end and sends it to the universal interface endpoint through a unified API entry point. Upon receiving the data operation request, the universal interface endpoint first parses five key fields in the request body: operation type, target data table identifier, operation data content, user identity information, and control code. Then, based on the user identity information, it calls the permission verification module to load the corresponding permission rules for that user. After successful permission verification, based on the operation type and target data table identifier, combined with the pre-configured data table structure information, the SQL dynamic assembly module generates the corresponding database operation statement. After executing this statement to obtain the business data, the universal interface endpoint further generates control data based on the control code carried in the request. This control data includes the display status and interaction enable information of each UI component in the front-end interface. Finally, the business data and control data are encapsulated together in JSON format and returned to the front-end interface. After receiving the returned results, the front-end template page automatically identifies and parses the control data, and completes the differentiated display and user interaction control of the page according to the display rules and interaction control rules defined in the control data; Taking the data table operation template page as an example, after logging into the system, each front-end page is associated with three fixed parameters: user ID, page ID, and language ID. It retrieves backend data through the configured interface address and interface key. The backend database layer provides business data and control codes through stored procedures or SQL statements. The stored procedures or SQL statements filter the business data based on the user ID, page ID, and language ID. The control codes are used to control read / write permissions and data display at the row, column, and cell levels in the tables on the front-end page. For data table operation templates or dynamic form templates, when the front-end interface performs data operations, it sends fixed and custom parameters back to the back-end. After the universal interface endpoint receives and verifies the parameters, it writes the operation data into the corresponding business data table. For report presentation templates, the back-end executes business data queries based on the passed query condition parameters and controls the rendering and presentation of the front-end page through control codes, enabling multi-level decomposition and viewing of any data in the front-end data table. The universal interface endpoint has multiple built-in database adapters, each designed to connect to different database types, including at least one of MSSQL, MySQL, Oracle, and PostgreSQL. It supports both RestfulWebAPI and SOAPWebService interface protocols. The universal interface endpoint authenticates data operation requests using an interface key, which is associated with a security code and a verification code. The security code determines the database connection permissions and expiration time, while the verification code is used to match and verify the interface key upon receiving a data operation request. In this implementation, the universal interface endpoint incorporates multiple database adapters, including MSSQL, MySQL, Oracle, and PostgreSQL adapters. Each adapter implements connection pool management, SQL dialect conversion, and data type mapping functions according to the corresponding database's JDBC or ODBC driver specifications. When the universal interface endpoint receives a data operation request, it automatically routes to the corresponding database adapter to establish a connection and execute the operation based on the database source identifier carried in the target data table identifier. The universal interface endpoint also provides both RestfulWebAPI and SOAPWebService interface protocols. Third-party systems can choose either protocol to call based on their own technology stack, and both protocols share the same set of business processing logic. For security authentication, the universal interface endpoint adopts a three-layer key authentication system: the first layer is the interface key (Key), which assigns a unique encrypted string to each connected system or service and associates it with a specific database; the second layer is the security code (SCode), used to determine the permission scope and valid expiration time of the database connection; the third layer is the check code (CheckCode). Each time a data operation request arrives, the universal interface endpoint matches the Key carried in the request with the Check Code for verification. Only after a successful match can the subsequent business processing flow proceed.

[0012] Load pre-configured permission rules based on user identity information, including: Determine the user's role information based on the user's identity information; Load function-level permission rules, row-level permission rules, and column-level permission rules based on role information; Among them, function-level permission rules are used to control the functional modules that users can access and the types of operations that can be performed; row-level permission rules are used to control the range of data rows that users can access by injecting filter conditions into the WHERE clause of the database operation statement; and column-level permission rules are used to control the data fields that users can see by adjusting the field list in the SELECT clause of the database operation statement. In this implementation plan, permission rules are divided into three levels: functional, row, and column, and are managed uniformly by a configuration center. Functional permission rules control the functional modules and types of operations a user can access; changes to permissions take effect immediately without requiring a system restart. Row-level permission rules are implemented by dynamically injecting filtering conditions into the WHERE clause of the SQL statement: the system automatically generates corresponding data range filtering conditions based on the currently logged-in user's department, workshop, production line, etc., and appends them to the SQL statement. For example, a query request from the workshop director of workshop A will automatically have the condition "WHERE workshop_id='A'" appended, ensuring that they can only see data from workshop A. Column-level permission rules are implemented by dynamically adjusting the field list in the SELECT clause of the SQL statement: based on the current user's role permissions, the system filters out the list of fields visible to that user from all fields in the data table, queries only these fields and returns them; invisible fields are directly omitted from the returned results. For example, a production work order query request from a regular operator does not include cost-related fields, while an administrator can view all fields.

[0013] Control data is generated based on the control code, including: The display status information and interaction enable information of each component in the front-end interface are determined based on the control code. The status information and interaction enable information will be displayed as control data; In this implementation plan, the control code is a set of structured instruction data dynamically defined by the backend based on user identity, business status, and scenario requirements when processing business logic. It is organized in JSON format and includes fields such as component identifier, component type, display status, and interaction enable status. After the universal interface endpoint completes database operations and obtains business data, it determines the display status and interaction enable status of each UI component in the frontend interface based on the control code carried in the request and the current user identity information, and assembles this status information into control data. After the control data and business data are returned to the frontend, the control code parsing engine built into the frontend template page automatically identifies the meaning of each field in the control data and completes the differentiated rendering and interaction control of the interface components according to the rules defined in the control data.

[0014] The platform also includes a templated interface generation step: In response to the selection of a pre-set business template by business personnel, a configuration interface is displayed; the pre-set business templates include dynamic form templates, data table operation templates, and report presentation templates. The configuration information is obtained through the configuration interface; the configuration information includes the target data table mapping relationship, field display rules, and interaction logic. The front-end interface is automatically generated based on the configuration information, and data operations on the front-end interface are realized through the universal interface endpoint. Pre-built business templates also include workstation templates; The platform also includes: Obtain multiple workstation templates; Based on the task group configuration information, multiple workstation templates are assembled to generate the workstation operation interface; Among them, the workstation template is a pre-configured operation interface template for the corresponding production workstation, and the task group configuration information is used to define the combination relationship and execution order between multiple workstation templates; In this implementation plan, the pre-configured business templates include three types: dynamic form templates, data table operation templates, and report presentation templates. Dynamic form templates support configuring data entry interfaces of arbitrary complexity, including various control types such as text input, dropdown selection, date selection, file upload, and batch import, suitable for maintaining technical data tables such as BOM tables, process parameter tables, and quality inspection standard tables. Data table operation templates are based on the automated mapping concept of "table to interface," directly mapping any business data table to an operable interface. The system automatically generates complete CRUD (Create, Read, Update, Delete) functions for the target data table, including data browsing, conditional filtering, single-row editing, batch import / export, and file attachment management. Report presentation templates support presenting complex data query results in various formats such as tables, charts, and dashboards. After business personnel complete the setting of the target data table mapping relationship, field display rules, and interaction logic in the configuration interface, the system automatically generates the corresponding front-end interface code based on the configuration information and implements data operations on the interface through a universal interface endpoint, without requiring any programming code. Workstation templates are pre-configured operation interface templates for corresponding production workstations. Each workstation template encapsulates the operation interface layout, data fields, interaction logic, and validation rules for that workstation. The platform supports acquiring multiple workstation templates simultaneously. Business personnel define the combination relationships and execution order between workstation templates through the task group configuration interface. The system assembles multiple workstation templates into a complete workstation operation interface based on the task group configuration information. The same set of workstation templates can generate workstation operation interfaces suitable for different production lines and products based on different task group configuration information. This mechanism enables the platform to simultaneously support the production management needs of both discrete manufacturing and process manufacturing industries. Multinational manufacturing companies can use this mechanism to uniformly manage production workstations of different factories and different manufacturing modes on a single platform. For general business requirements, after obtaining the business requirements, system engineers first create a business data table on the backend. Then, based on this data table, they write a stored procedure that conforms to the interface specification. This stored procedure contains data query SQL statements and control code generation logic. Once the stored procedure is written, the backend work is complete. Subsequently, the system engineer creates an operation page on the frontend, selects the STO template page, and performs simple, routine configuration—including configuring the data interface address and interface key. After the frontend configuration is complete, the entire business function is built, without requiring any code writing. For even simpler business requirements, SQL query statements can be used directly instead of stored procedures, as a stored procedure is essentially a combination and encapsulation of multiple SQL statements. The frontend template page can communicate with the backend either through the RESTful Web API interface or by directly connecting to the backend database layer.

[0015] The platform also includes a process modeling step: Process flow configuration information can be obtained through a visual process modeling interface; the process flow configuration information includes process node information, flow conditions between nodes, and flow paths. Generate a process flow model based on the process flow configuration information; Associate the process flow model with the universal interface endpoint so that each process node in the process flow model can perform data read and write operations through the universal interface endpoint. In this implementation plan, the visual process modeling center provides a drag-and-drop process modeling interface. Business users can build the process model by dragging and dropping process nodes and defining the flow conditions and paths between nodes, achieving a WYSIWYG modeling experience. After modeling is completed, the system automatically associates each process node in the process model with a universal interface endpoint, enabling each process node to perform data read and write operations through the universal interface endpoint during execution—for example, reading work order information at the start of a process, writing process parameters and detection data during process execution, and updating the work order status after the process is completed. When the process needs to be changed, business users can directly modify the process configuration in the modeling interface without modifying any code or redeploying the system.

[0016] Dynamically generate database operation statements, including: The corresponding database statement type is determined based on the operation type; the operation types include data query operation, data insertion operation, data update operation, and data deletion operation. When the operation type is a data query operation, a pre-configured query template is obtained based on the target data table identifier. The query template contains preset JOIN relationships and default filter conditions. Combine the query template with the data to be manipulated to generate database operation statements; In this implementation scheme, the universal interface endpoint determines the corresponding database statement type based on the operation type: a SELECT statement is generated for a data query operation, an INSERT statement for a data insert operation, an UPDATE statement for a data update operation, and a DELETE statement for a data delete operation. When the operation type is a data query operation, the system first retrieves a pre-configured query template from the configuration center based on the target data table identifier. This query template contains preset JOIN relationships and default filtering conditions. The system then combines the query template with the operation data content in the request, and adds row-level permission filtering conditions to the WHERE clause and adjusts the field list in the SELECT clause according to the current user's permission rules, ultimately generating a complete executable SQL statement.

[0017] The platform also includes integration steps with a warehouse management system (WMS): Assign interface keys to the warehouse management system via a universal interface endpoint; Based on the interface key, receive business operation requests from the warehouse management system through the universal interface endpoint; Among them, the warehouse management system shares the platform's permission rules and data table operation capabilities through a universal interface endpoint; In this implementation plan, the Warehouse Management System (WMS) can be flexibly integrated with the Manufacturing Execution System (MES) platform via a universal interface endpoint. The platform assigns a unique interface key to the WMS through the universal interface endpoint, which is associated with the endpoint's security code and verification code. When sending business operation requests, the WMS must include this interface key. Upon receiving the request, the universal interface endpoint first verifies the key's permission scope and validity period based on the security code, and then matches and verifies the key against the verification code. Only after all verifications are successful can the endpoint receive and process the WMS's business operation request. The WMS can be deployed independently, interacting remotely with the platform via the universal interface endpoint; alternatively, it can be integrated with the platform and deployed in the same server environment, sharing the universal interface endpoint. Regardless of the deployment method, the WMS shares the platform's unified permission rules and data table operation capabilities through the universal interface endpoint, eliminating the need for developing a separate backend API interface for the WMS.

[0018] The platform also includes standardized operating procedure (SOP) generation steps: Get the current workstation identifier and the current task identifier; Based on the current workstation identifier and the current task identifier, match the corresponding SOP display content from the pre-configured SOP template library; The SOP content will be displayed synchronously with the current workstation's operation interface; The SOP (Standard Operating Procedure) includes process steps, operating parameters, and operating precautions. In this implementation plan, the standardized work instruction (SOP) function automatically integrates with the MES workstations. After obtaining the current workstation identifier and the current task identifier, the system matches the corresponding SOP display content from a pre-configured SOP template library. The SOP template library supports various SOP document formats, including illustrated step-by-step instructions, operation process parameter tables, and equipment operation video links. The matched SOP display content is synchronously displayed on the current workstation's operation interface—when the operator performs a production task on the workstation's operation interface, the SOP content is automatically displayed in a designated area of ​​the interface and automatically updates as the workstation operation interface switches. When the operator completes the task at the current workstation and moves to the next workstation, the SOP content synchronously switches to the operation instructions corresponding to the next workstation, eliminating the need for the operator to manually search for or switch SOP documents, thus providing high ease of use for the operator.

[0019] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, the phrase "comprising an element defined as..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes the element.

[0020] Although embodiments of the invention have been shown and described, it will be understood by those skilled in the art that various changes, modifications, substitutions and variations can be made to these embodiments without departing from the principles and spirit of the invention, the scope of which is defined by the appended claims and their equivalents.

Claims

1. A manufacturing execution system platform based on data-driven and templated configuration, characterized in that: include: Receive data operation requests sent by the front-end interface; wherein, the data operation request includes operation type, target data table identifier, operation data content, user identity information and control code; Load the pre-configured permission rules based on the user's identity information; Based on the operation type and the target data table identifier, and combined with the pre-configured data table structure information, a database operation statement is dynamically generated, and the permission rule is injected into the database operation statement. Execute the database operation statements to obtain business data; Control data is generated based on the control code, and the business data and the control data are returned together to the front-end interface; The manufacturing execution system platform receives data operation requests from all business functions through a unified universal interface endpoint. The universal interface endpoint is the only entry point for backend data operations in the platform. The control code is used to define the display rules and interaction control rules of the front-end interface.

2. The manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The universal interface endpoint has multiple built-in database adapters, each used to connect to different database types, including at least one of MSSQL, MySQL, Oracle, and PostgreSQL. The universal interface endpoint supports both Restful Web API and SOAP Web Service interface protocols. It authenticates data operation requests using an interface key, which is associated with a security code and a verification code. The security code determines the database connection permissions and expiration time, while the verification code is used to match and verify the interface key upon receiving the data operation request.

3. The manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: Based on the user identity information, pre-configured permission rules are loaded, including: Determine the user's role information based on the user's identity information; Load function-level permission rules, row-level permission rules, and column-level permission rules based on the role information; The function-level permission rules are used to control the functional modules and types of operations that users can access. The row-level permission rules are used to control the range of data rows that users can access by injecting filtering conditions into the WHERE clause of the database operation statement. The column-level permission rules are used to control the data fields that users can see by adjusting the field list in the SELECT clause of the database operation statement.

4. The manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: Control data is generated based on the control code, including: The display status information and interaction enable information of each component in the front-end interface are determined based on the control code. The display status information and the interaction enable information are used as the control data.

5. A manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The platform also includes a templated interface generation step: In response to the selection of a preset business template by a business user, a configuration interface is displayed; wherein, the preset business templates include dynamic form templates, data table operation templates, and report presentation templates; The configuration information is obtained through the configuration interface; wherein, the configuration information includes the target data table mapping relationship, field display rules and interaction logic; The front-end interface is automatically generated based on the configuration information, and data operations on the front-end interface are implemented through the universal interface endpoint.

6. A manufacturing execution system platform based on data-driven and templated configuration according to claim 5, characterized in that: The pre-set service templates also include workstation templates; The platform also includes: Obtain multiple of the aforementioned workstation templates; Based on the task group configuration information, multiple workstation templates are assembled to generate a workstation operation interface; The workstation template is a pre-configured operation interface template for the corresponding production workstation, and the task group configuration information is used to define the combination relationship and execution order between multiple workstation templates.

7. A manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The platform also includes a process modeling step: Process configuration information is obtained through a visual process modeling interface; wherein, the process configuration information includes process node information, flow conditions between nodes, and flow path; A process flow model is generated based on the process flow configuration information; The process flow model is associated with the universal interface endpoint so that each process node in the process flow model can perform data read and write operations through the universal interface endpoint.

8. A manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The dynamically generated database operation statements include: The corresponding database statement type is determined based on the operation type; wherein, the operation type includes data query operation, data insertion operation, data update operation, and data deletion operation; When the operation type is a data query operation, a pre-configured query template is obtained according to the target data table identifier. The query template includes preset JOIN relationships and default filtering conditions. The query template is combined with the operation data content to generate the database operation statement.

9. A manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The platform also includes integration steps with a warehouse management system (WMS): The universal interface endpoint is used to assign an interface key to the warehouse management system. Based on the interface key, the business operation request of the warehouse management system is received through the universal interface endpoint; The warehouse management system shares the platform's permission rules and data table operation capabilities through the universal interface endpoint.

10. A manufacturing execution system platform based on data-driven and templated configuration according to claim 1, characterized in that: The platform also includes a standardized operating procedure (SOP) generation process: Get the current workstation identifier and the current task identifier; Based on the current workstation identifier and the current task identifier, match the corresponding SOP display content from the pre-configured SOP template library; The SOP content is displayed synchronously with the operation interface of the current workstation. The SOP (Standard Operating Procedure) includes process steps, operating parameters, and operating precautions.

Images