Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.

Abstract: 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.