Inside a recipe, a recipe value can use the default value or it can be overridden in the recipe as shown in the image below. Notice the Agitator Speed and Ingredient 2 of the Thick Blend recipe have been overridden. If it uses the default value, it will be updated when the default value is changed. Once a recipe value has been overridden in a recipe, that value persists even if the master value is changed. At any time the recipe value can be reverted back to the default value.

All of this is done in the recipe editor or by using script functions. The image below shows the default values in the recipe editor where the default values can be edited. Also see Sub Recipes for more details of how default values are used with sub recipes. 

Default Values in the Recipe Editor

Tag Path

A tag path for a default recipe value can be assigned in the MES Equipment Manager → Settings and Changeover section → Value → Add/Edit Default Recipe Value by dragging a tag from the Tag Browser pane into the Tag Path field of the Default Recipe Values dialog box (either for a new or existing default value entry). The field will contain the entire tag path, as shown to the right.

A tag path can also be selected using the Tag Path Browser, by clicking the  icon, then navigating and selecting the tag to use.

Complete Tag Path in Tag Path field

Tag Path Browser

If a tag is dragged and dropped directly into the empty area of the Default Recipe Values table (no add/edit dialog box required), a new Default Recipe Value entry will be created. The Tag Drop Name Format dialog box will appear when the tag is dropped, to allow the user to select the desired text format for the Name field. 

Once a selection is made, the new Default Recipe Value entry will be displayed in the table, as shown to the right. The Name field will be populated with the format selection choice (the Tag Path field will always have the entire tag path).

Multiple tags can be selected and dragged over at once and dropped into the table area. For each different level of tag-folder nesting, the user will be prompted with the Tag Drop Name Format dialog box (see above) to select the naming format for all tags at that folder level. A second prompt will ask if the same naming scheme should be applied to all tags at the current Tag's nested level (responding Yes prevents the the Tag Drop Name Format dialog box from re-appearing for each remaining tag at that folder level).

If non-unique naming or previously-assigned tags are involved, the appropriate warning message will appear (and the affected tag will not become a new Default Recipe Value entry).

Creating a Default Recipe Value by dragging a tag

Sub Recipe Mask

Sub Recipe Mask with Non-Consecutive Asterisk Mask Characters

Sub recipes are derived from the product code and the sub recipe mask. The sub recipe mask specifies the digits to extract from the product code to determine the sub recipe. Once the sub recipe value is determined like the 76 in the image, the recipe values are looked up in the sub recipes folder of the Default Values for the line, cell, cell group or location, and are written to tags.

See Sub Recipe Mask for more information on how to configure production items to use sub recipes.

Sub Recipes are enabled by adding a value to the Sub Net Mask field for the Production Model. Sub Recipes are managed using the Recipe Editor component by enabling Default Values in the properties and adding sub recipes to production items.

The image steps through the flow of selecting sub recipes and setting the associated tag values. The product code can be selected by starting a production run using the OEE module, executing a operations segment using the Track & Trace module or by using script functions.methods.

If a sub recipe is not found, the default will be used.