Abstract: A production information reporting/recording system is disclosed herein including a number of features to ensure efficient, flexible and reliable recording of production data in a manufacturing system. Such features include validating the content of event messages to ensure compliance of event report information with a standard. The system also supports caching IDs associated with particular aspects of an event message (e.g., a production request, a process segment) as well as a unique ID corresponding to the ID assigned by the production event database to reduce the need to access the database when assigning unique database IDs to received events. The production event messaging system also supports both asynchronous and synchronous transactional messaging between the sources of events and the production database service.

Abstract: A production information reporting/recording system is disclosed herein including a number of features to ensure efficient, flexible and reliable recording of production data in a manufacturing system. Such features include validating the content of event messages to ensure compliance of event report information with a standard. The system also supports caching IDs associated with particular aspects of an event message (e.g., a production request, a process segment) as well as a unique ID corresponding to the ID assigned by the production event database to reduce the need to access the database when assigning unique database IDs to received events. The production event messaging system also supports both asynchronous and synchronous transactional messaging between the sources of events and the production database service.

Abstract: A production information reporting/recording system is disclosed herein including a number of features to ensure efficient, flexible and reliable recording of production data in a manufacturing system. Such features include validating the content of event messages to ensure compliance of event report information with a standard. The system also supports caching IDs associated with particular aspects of an event message (e.g., a production request, a process segment) as well as a unique ID corresponding to the ID assigned by the production event database to reduce the need to access the database when assigning unique database IDs to received events. The production event-messaging system also supports both asynchronous and synchronous transactional messaging between the sources of events and the production database service.