NAMUR
6.2 Recipe Management
The recipe orders the procedural elements, among other things. Similarly, the path orders the equipment entities. The degree of flexibility of the path depends on the requirements of the range of products being manufactured.
This is an iterative process. If some equipment entities exist, then the recipe engineer fits them in as available process functions and asks the entity engineer to design new entities as required. If the facility is presently a green field with grass roots, then the recipe engineer begins the design by discovering the required process functionality and requesting it. The entity engineer designs entities that are constrained by tech- nology, availability, and cost. This means that they may not exactly meet the process functionality requirements. The engineers meet to resolve the differences and pro- duce a set of recipe building blocks that will work in a particular cell. Each recipe phase, operation, or unit procedure that connects to an equipment entity must match an equipment phase, operation, or unit procedure. These blocks are used to build Master recipes from Site or General recipes.
Similar engineering is required at the site and general recipe levels. Although there are no equipment entities, the process designers must make an effort to choose process functions that are available at the target facility or facilities. Meetings with the engi- neers who do master recipe building blocks are required in order to reduce the work that is necessary to translate a site or general recipe into a master recipe. Careful engi- neering may allow future translations to be automated, if the relationship between a process function and an equipment phase can be reduced to an algorithm.
If possible, the equipment entities should be designed to maximize the things that can be done with each entity. If the design staff can develop a complete list of process functions that might be encountered at a particular facility or cell, then work can begin on creating equipment entities in isolation from recipe development. Manage- ment may order the construction of a facility to make a class of product before recipe development has even started.
It is a rare engineer who builds something that cannot be improved. Version 1 is never the last version. For this reason, the engineers at a facility will have work to do as improvements become evident, but only if they cut costs.
response set necessary to control the flow of master recipes. A specific interoper- ability standard is still required.
Figure 11-3 is redrawn from 88.01 Figure 21. It shows the functions within the Recipe Management activity and the delivery to Process Management.
Figure 11-3 Recipe Management
The functions of Recipe Management follow:
6.2.1 Manage General Recipes
This function creates and maintains general recipes. Each product recipe is stored on paper or in a file in a way that allows it to be referenced by other functions within Recipe Management and anyone else with a need to know.
Specific equipment is unknown at this level if the process cells have different kinds of equipment. Equipment requirements are specified by physical properties such as working pressure and temperature as well as wetted surface requirements for contam- ination and corrosion.
This function may have the following capabilities:
• Select and arrange procedural elements to build the recipe procedure.
• Incorporate formula information, with amounts normalized to a unit amount of product.
• Specify generic equipment requirements.
• Manage the recipe change process.
6.2.2 Define General Recipe Procedural Elements
This function defines, creates, and maintains procedural elements for general and site recipes. Each procedural element is stored on paper or in a file in a way that allows it to be referenced by other functions within Recipe Management and anyone else with a need to know. The interactive tasks necessary to define procedural elements were described above in Section 6.1.3, “Process and Control Engineering.” See 88.00.03 for more thorough coverage of recipes. 88.01 only set out to define the models and terms associated with recipes.
This function may have the following capabilities:
• Name each procedural element as the key to finding an element.
• Name each adjustable parameter, such as a formula value.
• Describe the process functionality and the use of parameters for each element.
• If lower elements are used (as phases in an operation), select and arrange those elements.
• Create and do file management for the elements.
• Maintain a directory of procedural elements.
• Manage the procedural element change process, including performing a thorough review of the effects of the change.
6.2.3 Manage Site Recipes
The capabilities for this activity are similar to those for a general recipe. The site recipe is a modified copy of the general recipe, with no creative additions. That is, there are no additions unless the procedures for material preparation and addition have to be changed because the site can save money by purchasing local materials and processing them. Some vendors or users may require the site recipe procedure to be identical to the general recipe procedure. This will require different general recipes for the same product, one for sites without local materials and one for each site with different local materials.
6.2.4 Manage Master Recipes
This function creates and maintains master recipes. Each product recipe is stored on paper or in a file in a way that allows it to be referenced by other functions within Recipe Management and anyone else with a need to know.
If a general or site recipe exists then the creation of a master recipe is constrained to translating the intent of the generic recipe into a recipe that can be implemented by the equipment within a specific process cell. This requires matching master recipe procedural elements to general recipe procedural elements. This work may require engineering, or it may be automated if the two sets of elements can be aligned.
This function may have the following capabilities:
• Select and arrange procedural elements to build the recipe procedure.
• Incorporate formula information, with amounts normalized to a unit amount of product.
• Specify available equipment requirements.
• Create and do file management for the recipes.
• Respond to requests for recipes in a standard manner, with standard error messages.
• Maintain a directory of master recipes.
• Manage the recipe change process.
6.2.5 Define Master Recipe Procedural Elements
This function is similar to the one for the general recipe elements except for the names and the use of specific equipment entities. Each master recipe building block must have a counterpart in an equipment entity at the point in the procedural ele- ment hierarchy where a recipe procedural element is implemented by an equipment procedural element. Automatic translation of a general to a master recipe procedure requires that one or a set of master recipe building blocks must have the same process functionality as the matching general recipe building block. Engineering is required for each translation if this is not possible.
Using building blocks to construct procedures makes it possible to put any block any- where, except for the few rules stated in the description of recipes. The best way to assure that a procedure assembled from blocks will actually work is to hire competent recipe authors. A strong review process that will question anything that does not look right is essential, because humans are not infallible. This function may define con- straints for the assembly of blocks, but this will likely result in a false sense of security, because the constraints can’t cover everything.
This function may have the following capabilities:
• Name each procedural element as the key to finding an element.
• Name each adjustable parameter, such as a formula value.
• Describe the process functionality and the use of parameters for each element.
• If lower elements are used (as phases in an operation), select and arrange those elements.
• Create and do file management for the elements.
• Maintain a directory of procedural elements.
• Manage the procedural element change process, including performing a thorough review of the effects of the change.