Recipe Versioning for Template Changes and Approved Equipment Models
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing recipe management systems in process control environments face challenges with user-friendly configuration, data integrity issues due to multiple communication layers, and the need for versioning to manage template changes and dependencies, leading to obsolete instances and equipment models.
Innovation Solution
A versioning system within a recipe management system that stores and manages template and instance models with version identifiers, allowing for modifications and updates while maintaining data integrity and ensuring only approved equipment models are used for recipe execution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If spreadsheet-based user interfaces are used for recipe configuration, then users can define and create recipe templates, but the system is not user-friendly
Solution Approach 1:
The patent replaces traditional spreadsheet-based graphical user interfaces with a web-based interface that uses standardized HTML tables. This substitution allows the system to maintain recipe configuration capabilities while improving accessibility, consistency, and ease of use across different platforms and devices.
Solution Approach 2:
The patent implements a universal recipe management system that can handle multiple recipe types (batch recipes, continuous recipes, on-off recipes) and multiple equipment types through a single unified interface. The system provides consistent functionality across different recipe configurations, eliminating the need for application-specific interfaces.
2Reliability
If application-specific execution engines are used to execute control recipes, then recipes can be executed in process plants, but data integrity is lost due to multiple communication layers
Solution Approach 1:
The patent extracts the recipe execution functionality from application-specific execution engines and implements it directly within the web browser using HTML tables and web-based processing. This eliminates the need for intermediate communication layers and standalone executable engines, thereby preserving data integrity while reducing system complexity.
3Adaptability or versatility
If template changes are made in recipe management systems, then templates can be updated, but all dependent instances become obsolete
Solution Approach 1:
The patent implements a versioning system that provides feedback mechanisms to track template-instance relationships. When templates are updated, the system automatically notifies dependent instances and provides options to update or maintain version compatibility. This feedback loop prevents instance obsolescence by maintaining awareness of template changes across the system.
Solution Approach 2:
The patent implements preliminary versioning and dependency tracking when templates are created or modified. The system pre-identifies all instances that depend on a template and prepares them for potential updates. This preliminary action allows for controlled propagation of template changes without causing unexpected instance obsolescence.
4Ease of manufacture
If configuration tools access equipment model during runtime, then configuration can be performed, but runtime system is adversely affected
Solution Approach 1:
The patent segments the system into configuration mode and runtime mode with distinct access controls. Configuration tools can access and modify equipment models during configuration phase, but these changes are separated from the runtime execution environment. This segmentation allows configuration accessibility while protecting runtime system stability through clear mode boundaries.
Data Source
AI summary
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.