Method and system for managing data in a manufacturing execution system

• US 10,210,284 B2
• Filed: 07/23/2015
• Issued: 02/19/2019
• Est. Priority Date: 07/23/2014
• Status: Active Grant

• Current Assignee: Siemens AG
• Original Assignee: Siemens AG
• Inventors: Cereghino, Marco
• Primary Examiner(s): Fleurantin, Jean B
• Application Number:
  US14/807,270
• Publication Number:
  US 20160026735A1
• Time in Patent Office: 1,307 Days
• Field of Search: 707769
• CPC Class Codes: G06F 16/18 File system types
• CPC Class Codes: G06F 16/90335 Query processing
• CPC Class Codes: G06Q 10/06 Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
• CPC Class Codes: G06Q 50/04 Manufacturing
• CPC Class Codes: Y02P 90/30 Computing systems specially adapted for manufacturing

Abstract

A method and a system for managing data of a database in a MES system enables improved horizontal scalability of the client-server applications. The manufacturing execution system manages and controls the planning and execution of a production process of a product. Resources and clients generate and request data related to the production process. A relational database system includes a write database and a read database. A central service bus links the resources to the write database. A logical worker entity handles commands from the resources and clients queued in the central service bus, thereby interpreting the actions related to the write database, collecting the data required to complete the actions, and launching the execution of the command. A logical reader entity captures all data requests from the resources and clients, launching the requests for data from the read database and sending the data back to the requesting resource or client.

Claims

1. A method of managing data in a manufacturing execution system, the manufacturing execution system managing and controlling the planning and the execution of a production process for a product, the method comprising the following steps:

a) providing a plurality of resources and clients involved in an execution of the production process, thereby generating data and requesting data related to the production process;

b) providing a relational database system for storing the data related to the production process, the relational database system containing a separate write database and a separate read database, wherein the separate write database and the separate read database are provided as structured data files according to a data model of the manufacturing execution system;

c) providing a central service bus linking the plurality of resources to the write database;

d) providing a logical worker entity configured to handle commands from the resources and clients queued in the central service bus, thereby interpreting the actions related to the write database, collecting data required to complete the actions and launching an execution of the command; and

e) providing a logical reader entity configured to capture all data requests from the resources and clients, thereby launching the requests to fetch data from the read database and sending said data back to the resource and client requesting said data.

2. The method according to claim 1, wherein the plurality of resources and clients are selected from the group consisting of machines, working personal, users, production line managers, applications, and libraries.

3. The method according to claim 1, which comprises using with the logical worker entity a bus having at least one structure selected from the group consisting of a logical bus structure and a physical bus structure to access the write database and using with the logical reader entity a bus having at least one structure selected from the group consisting of a logical bus structure and a physical bus structure to access the read database, wherein the bus used by the logical worker entity is different from the bus used by the logical reader entity.

4. The method according to claim 1, which comprises handling with the logical worker entity write requests to the write database and handling with the logical reader entity read requests from the read database, each using its own bus structure including at least one bus structure selected from the group consisting of a logical bus structure and a physical bus structure.

5. The method according to claim 1, wherein at least one entity selected from the group consisting of the logical worker entity and the logical reader entity benefit from an optimistic lock approach when accessing the relational database system.

6. The method according to claim 1, wherein the business logic of the production process is decoupled from a data model in the logical worker entity.

7. The method according to claim 1, which comprises resolving with the central service bus conflicts related to a concurrent execution of request/answer tasks invoking a contribution of at least one database selected from the group consisting of the read database and the write database.

8. A system for managing data in a manufacturing execution system, the manufacturing execution system managing and controlling the planning and execution of a production process for a product, the system comprising:

a) a plurality of resources and clients involved in an execution of the production process for generating and requesting data related to the production process;

b) a relational database system configured to store the data related to the production process, said relational database system including a separate write database and a separate read database, wherein the separate write database and the separate read database are provided as structured data files according to a data model of the manufacturing execution system;

c) a central service bus for linking the plurality of resources to said write database;

d) a logical worker entity configured to handle commands from said resources and clients queued in said central service bus, thereby interpreting actions related to the write database, collecting data required to complete the actions, and launching an execution of the command; and

e) a logical reader entity configured to capture all data requests from said resources and clients, thereby launching the requests to obtain data from said read database and sending the data back to a respective said resource and client requesting the data.

9. The method according to claim 8, wherein said plurality of resources and clients are selected from the group consisting of machines, working personal, users, production line managers, applications, and libraries.

10. The system according to claim 8, wherein said logical worker entity uses a bus having at least one structure selected from the group consisting of a logical bus structure and a physical bus structure to access said write database and said logical reader entity uses a bus having at least one structure selected from the group consisting of a logical bus structure and a physical bus structure to access said read database, wherein the bus used by said logical worker entity is different from the bus used by said logical reader entity.

11. The system according to claim 8, wherein said logical worker entity is configured to handle write requests to said write database and said logical reader entity is configured to handle read requests from said read database, each of said logical worker entity and aid logical reader entity using its own bus structure including at least one bus structure selected from the group consisting of a logical bus structure and a physical bus structure.

12. The system according to claim 8, wherein at least one entity selected from the group consisting of said logical worker entity and said logical reader entity benefit from an optimistic lock approach when accessing said relational database system.

13. The system according to claim 8, wherein a business logic of the production process is decoupled from a data model in said logical worker entity.

14. The system according to claim 8, wherein said central service bus is configured to resolve conflicts related to a concurrent execution of request/answer tasks invoking a contribution of at least one database selected from the group consisting of said read database and said write database.