Mitigating Cross-application Changes
With SmartFactory RMS, version 2.1.0 released in April 2022, our vision is to use recipe management as the “point of truth” for runtime recipe control and mitigate cross-application changes. Now, a short form recipe name (e.g., Recipe_Product_A) is the common identifier, yet at a system level, the recipe name and directory (as defined on the equipment) dictate the fully qualified recipe:
Recipe Directory + Recipe Name (short form) = Fully Qualified Recipe
In MES-centric environments, qualified recipes are included in MES route definitions. While effective, this method may require changes in both the RM system and MES if either the recipe directory or recipe names are modified on the equipment. The challenge is that organizationally, people responsible for creating and modifying recipes on equipment and those responsible for MES routes are often on different teams with different execution timelines.
- External Short Form Mode. External short form mode inherits the short form recipe name from the MES definition and provides a recipe directory conversion modeling interface in RM to generate the fully qualified name. Decoupling the recipe directory from the MES definition enables organizational responsiveness, such as adding or modifying folder names on the equipment based on product changes or when introducing new technology.
- External Context Resolution. This feature enhances flexibility by using MES contextual information to resolve the fully qualified name at runtime. For example, a key combination of Operation + Equipment + Product could be modeled to obtain the appropriate recipe (e.g., Recipe Directory + Recipe_Product_A). Decoupling both the recipe directory and recipe name from the MES route definition enables flexibility for individual organizational preferences.
To learn more about SmartFactory Recipe Management 2.1.0
