Invensys Systems, Inc.

Schneider Electric Software, LLC

Aveva Software, LLC

Eric Paul Grove

Steven Michael Weinrich

Christopher Justin Miller

Donald R Tunnell, Jr

James C Long

George E Bachman

Don R Tunnell

William Yiu Leung Chan

Diana Ivanov

Nicolas Pouyez

Paul W LeMert

Robert A DeRemer

Julia Wright

Lorin V Grubb

Anthony Keith Crouch

Robert D Hallquist, Jr

Philippe Lalonde

Edward R Mundorf

Edward S Urbalejo

A recipe management system includes a versioning system that tracks the revision history of templates and their child instances. Modifications to templates and instances create new records with new primary key identifiers and version identifiers. However, each new version of a template or instance has the same root identifier as the prior versions. When a template is modified, a flag is set in its child instances, but they are not modified automatically. When an instance is modified, it has no effect on the parent template. At runtime, a recipe model is loaded to an equipment model to execute a recipe on a piece of equipment. Only approved versions of equipment models are used during execution, even if newer versions exist. During execution, new equipment models can be created. The recipe management system includes an execution engine that can be hosted as a standalone executable or in a system platform.

Recipe management system

An industrial control system stores three types of models. Models of a first type are associated with models of a second type. When a model of the first type is associated with a model of a third type, the set of models of the second type that are associated with the model of the first type is established. The industrial control system can provide an indication of the set of models of the second type. The industrial control system also establishes the set of models of the first type that are associated with the set of models of the second type. The industrial control system provides an indication of the set of models of the first type. In some embodiments, the industrial control system is a recipe management system and the models of the first, second, and third types are capability models, equipment models, and recipe models.

Adaptive filtering in industrial control system

A recipe management system executes a recipe on a piece of equipment in a process plant using one or more capabilities of the piece of equipment. A configuration system creates models of the capabilities, piece of equipment, and recipe and associates the capability models with the equipment model and recipe model. The recipe model can be used to execute the recipe on any piece of equipment with the capabilities with which it is associated. The equipment model can be used to execute any recipe that uses no capabilities other than those with which it is associated.

Recipe management system with interoperable models

An industrial control system includes a download verification subsystem to execute a verification test using the parameters stored in a configuration database before an execution subsystem downloads the recipe parameters to the input/output addresses of a piece of equipment to determine a first verification value. The download verification subsystem executes the verification test using the recipe parameters downloaded to the piece of equipment to determine a second verification value. The download verification subsystem compares the first and second verification values to determine whether the recipe parameters were downloaded to the input/output addresses of the piece of equipment successfully.

Parameter download verification in industrial control system

A system is disclosed that simplifies configuring an MES entity corresponding to a SCADA system object representing plant equipment. The system includes an equipment model builder (EMB) that receives a set of configured UCO information for a modeled piece of plant equipment in a SCADA system. The EMB extracts relevant MES information from the utilization capability object and invokes an application interface on an MES database to create a corresponding entity (e.g., a database element). Another aspect of the disclosed system and methods involves the enhancement of a SCADA system object, through a new MES facet, to support acquiring and reporting equipment status received via the SCADA system to a corresponding MES entity. A raw reason code configuration interface is provided by UCO configurator computer software executed on a computer. Each raw reason code is associated with a prioritized logical expression defining circumstances under which the reason code becomes true.

System for maintaining unified access to SCADA and manufacturing execution system (MES) information

A system and method are described that simplify defining/designing graphical display interfaces for graphically displaying related data elements. The displays provide both depictions of the data elements and the relationships between the data elements in accordance with a pre-defined data element display scheme including both element template (for particular data element types) and relationship view (spatial relationships within a display) definitions. A relationship view displays a set of provided data elements of specified type according to the element template and relationship view definitions.

Graphically displaying manufacturing execution system information data elements according to a pre-defined spatial positioning scheme

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. Furthermore, the system supports including extensions to a base production message schema through the inclusion of metadata that designates a particular production server to parse and apply/store the extension information.

Supporting both asynchronous and synchronous data transfers between production event information sources and a production information database

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. Furthermore, the system supports including extensions to a base production message schema through the inclusion of metadata that designates a particular production server to parse and apply/store the extension information.

Supporting extensions to production event message schemes via production database server versioning

Caching identifications and associated production database guids for expedited acquisition of linking information contained within multiple distinct production database tables

The invention provides improved methods and apparatus for workflow editing. Such methods and apparatus permit, for example, user-defined and/or other tasks to be combined in any combination or combinations to specify a workflow. The tasks can be linked for direct, serial processing and/or for conditional processing that includes branching and/or looping. The invention also improved methods and apparatus of workflow definition and processing with extensible actions. The invention provides, further, improved methods and apparatus for workflow definition and processing which utilize workflow variables for communication of data and control information among tasks within a workflow. The invention provides, still further, improved methods and apparatus of workflow definition and processing with enhanced messaging. The invention provides, still yet further, improved methods and apparatus for workflow definition and processing which permit definition of hierarchically enumerated data types and for for definition of 'plans' to collect, e.g., for storage, data such as the aforementioned hierarchical data types.

Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with unified messaging interface

Growing community of inventors

Dallastown, PA, United States of America

Eric Paul Grove