Hello,

I would like to post what is a recipe, an important concept in the process industry especially, and how it is defined in Apriso.

First of all, I want to take a look at what a Recipe is. As we all know, finished goods in the discrete industry are physically countable and easily identifiable, and production follows the predefined Process(Routing). In contrast, the process industry relies on formulas and recipes to manage the specifications for the production of intermediates, semi-products (co-products), and finished products. These recipes will include the definition of the product's ingredient, Quality Control Test, Manufacturing Instructions, and UOMs in the Specifications.

In the international standard ISA-88, you can see more details about the Recipe.

ISA-95,the international standard for the integration of enterprise and control systems, focuses more on the movement of data or information within the company beyond the production line/factory. In other words, the required materials/intermediate products are defined through the BOM, and the process sequence is defined through the Process (or Routing). And according to the defined order, actual production is made, and various information and data collected during the execution process are transmitted to each other in different layers.
A standard addressing batch process control, ISA-88 focuses on batch models and terminology.

In ISA-88, a hierarchically structured physical model is defined from Enterprise to the Control module, which is also used in ISA-95. And it is one of the key concepts of ISA-88 to separate product information (recipe) and equipment capability based on such modeling. This separation also allows the manufacturing process to create more flexible and attractive scenarios. This means that engineers can control or design equipment based on the overall functionality and performance of the equipment rather than based on the product or product requirements. Similarly, the recipe manager can manage recipes, such as additional changes, without the request of an automation engineer.  In other words, a recipe can be defined as information required only for the production of a specific product, independent of equipment capability. And it is very important for process manufacturers to maintain and manage numerous recipes to make their products.

Now, let's take a closer look at the recipe. 

First, let's take a quick look at the Equipment Entity. According to the physical separation, technically lower levels are divided into Process Cell/Unit/Equipment Module/Control Module. In effect, Control is part of the Equipment, defined only as the backbone of the control application in the Physical Model.

And Recipe can be divided into equipment-independent recipes based on Process Model and equipment-dependent recipes based on Procedural Control Model. A recipe that is equipment-independent includes a general recipe(enterprise-wide information) and Site Recipe (site-specific information derived from the general recipe). And the equipment-dependent recipes include MR(Master Recipe: the process cell-specific information) and CR (Control Recipe: batch-specific information). Such MR/CR is defined as a recipe for each step in functional sequencing in Procedure, and structurally includes Header information (Identification, version control), Formula (Process inputs/outputs/parameters), necessary equipment, or additional information.

Additionally, the distinction between equipment and process is described in detail in Chapter ISA88.01.

• Equipment Capabilities is an Equipment control that provides the generic purpose and process-independent inherent services that can be used for production.
• Product Knowledge refers to leveraging previous equipment services to achieve production goals by executing predefined, parameterized rules (recipes) with process control.
• These two pieces of information must be independent or weakly coupled.

As a result, recipe development is possible without the help of a control system program or engineer. (it allows recipe development without the services of a control systems engineer ‘No control system programming’ required). In addition, the scope of responsibility is well separated, making validation easier and increasing the portability of recipes between systems.

Next, I will post how to set up a recipe in Apriso.