Invensys Systems, Inc.

Siemens Aktiengesellschaft

Aveva Software, LLC

James Eric O'Hearn

Nicolas Pouyez

Diana Ivanov

Thomas Andrew Troy

Keith Richard Frantz

Raghavendran Gobalakrishnan

Richard William Boyle

Melvin Philip Norbeck

Daniel Van Klaveren

Adam R Haskell

Jeffrey Bernard Nuse

Patrick Parsy

Christian-Marc Pouyez

Mario Brenes

Keynon Basinger

Nicholas Beets

Stephane Bischoff

Ravi Kumar Herunde Prakash

A manufacturing execution system (MES) that provides tools for modeling and determining information about physical production lines made up of arrangements of entities. The MES includes configuration tools for modeling the entities in a physical production line. The MES also includes configuration tools for modeling the physical production line. Entity data models and line data models conform to the data structure of respective model templates. Line data models include line definition models and line layout models. Line layout models include an entity link model for each of the entities in the physical production line. The MES includes tools for dynamically determining the bottleneck for the physical production line. Other production metrics are also calculated using the MES.

Line management in manufacturing execution system

Some embodiments include utilization of a first interface to query a data source using a first configuration and to return a first data set including a plurality of records, each of the plurality of records comprising data of a plurality of fields of the first data set, and reception of the first data set from the data source. Also included may be utilization of a second interface to query the data source using a second configuration and to return a second data set for each of the plurality of records, at least one field of the second configuration being associated with one of the plurality of fields of the first data set, each utilization using the received data of the one of the plurality of fields of a respective record that is associated with the at least one field of the second configuration, and reception of a respective second data set from the data source for each utilization of the second interface. Moreover, a class-based component model representing tag-based data and non-tag-based data may be populated with data of the respective second data sets.

Interface chaining to populate a class-based model

A software agent is described that receives an information request to retrieve information based on a name defined by a configured manufacturing data model. The agent serves the request by relating data coming from one or multiple backend systems and adding contextual data (Metadata). A result set is prepared to correspond to the format and filtering criteria defined in the information request, and the agent produces a response in a normalized format. The response contains the requested data and metadata used for navigation and contextualization purposes. The response in the normalized format is transmitted by the agent synchronously or asynchronously based on criteria specified in the request.

Retrieving and navigating through manufacturing data from relational and time-series systems by abstracting the source systems into a set of named entities

Growing community of inventors

Mission Viejo, CA, United States of America

James Eric O'Hearn