Tag Structure for Recipes
The tag hierarchy for a fully-configured Recipe Book follows. To help clarify the structure, each tag in this example is named for its type or purpose. Every Recipe Book tag will require a driver (which will require a port) but those are not shown as part of this example.
Recipe Book Tag
May have any name. Must be linked to the PLC through a communication driver. Defines the overall structure and communication parameters for a set of recipes. Recipe Book Tag
Batch Complete
An I/O tag created and configured automatically if a Done address is provided in the Recipe Book.
Batch Number
An I/O tag created and configured automatically if a Batch Number address is provided in the Recipe Book.
Ingredients
A Context tag created and configured automatically. Holds all the Recipe Ingredient Tags for the recipes.
Ingredient Tag (n)
The set of ingredients that make up a recipe. May be created individually, but often created automatically by importing a recipe from a database, spreadsheet or PLC. Typically named for the ingredient, although the display name for each ingredient is a property of this tag. (Recipe Ingredient Tag)
Ingredient Value Tag
An I/O tag, created and configured automatically. Holds the value to be written for the parent ingredient. Values are stored in a defined CSV file and set or changed for each batch.
Never edit Ingredient Value tags directly. Work only with the parent Recipe Ingredient tag.
If the Ingredient stores text, the Ingredient value will show the matching phrase key when viewed in the Tag Browser.Recipe Name (*)
A Recipe Ingredient tag created and configured automatically. Like an ingredient, values for a batch are stored in a defined CSV file and set or changed for each batch.
Recipe Version (*)
A Recipe Ingredient tag created and configured automatically if the Recipe Book is configured to allow multiple versions. Like an ingredient, values for each version of a recipe are stored in a defined CSV file and set or changed for each batch.
(*) The Batch Number / Name / Version ingredient tags might be used if you want to write the current batch number / name / version into the PLC. This is useful if the PLC can display such information on a panel. This will happen only if these ingredient tags are given addresses. Otherwise these tags do nothing other than display their current values on the recipe page.
Recipe Trigger Tag
An optional tag that can be configured to start a batch automatically based on rules that you define. (Recipe Trigger Tag)
Start Batch
An I/O tag created and configured automatically if a Start address is provided in the Recipe Book.