Recipes
What are Recipes?
A recipe is used to group Control Parameters for a recipe to produce a material or a procedure. It is associated with an Asset Class as an optional fiter.
It contains rules, each with conditions that define when the rule should apply. These conditions can be configured using combinations of different Assets, Materials, and other criteria.
Each rule also includes values that will be set for the corresponding Control Parameters, which are triggered and sent when the conditions are met.
Where do these values get sent?
These are sent to Ignition via the TilliT Ignition Module. See Ignition Module for more.
Important note
Before creating Recipes
Control Parameters must be configured before creating Recipes.
Navigation
Go to Settings > Recipe Management > Recipes
Creating Recipes
Click on Create and fill out the modal
Name*
Name of the recipe
Asset Class
If orders are started on asset(s) not included in this asset class, the rules within the recipe will not be considered.
Recipe Key*
The ID of the recipe, cannot be changed once set.
Description
Description of the recipe
Creating Rules
Click on the recipe that you want to create rules for.
Fill in the modal for the first step, once you choose the Control Parameter, the fields to enter its value should appear.
Name
Name of the Rule
Control Parameter
The Control Parameters that this rule applies to.
Phase
The Phase that a specific value of the Control Parameter is supposed to be used for.
Priority
Priority for which rule to apply if their conditions are the same.
Numeric/String/Boolean Value
Depending on how you configure the Control Parameters, the field will have a different data type in its name. This is where you will enter the expected Control Parameter for your asset to have.
Upper Limit
The maximum limit that this CP should realistically be, without being considered failing. See Process variable for an additional example of this concept.
Lower Limit
The minimal limit that this CP should realistically be, without being considered failing. See Process variable for an additional example of this concept.
Click continue to go to the next step.
This is where you add the conditions for your rules. So how does this work?
Every time a new order starts running or on a changeover start, TilliT will immediately match your asset with a rule that apply.
For example - Wheel Speed
After this recipe is LIVE. TilliT immediately starts checking for orders that:
Have the Attribute Bottleneck with the value equal to True
Glass Supplier of the order is TIL Bottle Export
Asset(s) that are running the order belong to the "Fillers" Asset Class.
If there is an order that qualifies for those conditions. The target value that will be sent to that asset is 50 for the Wheel Speed they are expected to be running at. Other values configured such as Upper Limit, and Lower Limit will also be sent.
Creating Phases
What happens when an asset needs to change the its control parameters values throughout production? That's where Phases come in.
You can send multiple values of the same Control Parameters with Phases.
All Rules created are automatically in Phase 1.
Example: Different pressures for different phases
Using the Order Preview, we can see that there will be two values for the Control Paramters "Pressure" that will be sent to the assets that match the rules for this running order.
However, if they were both in Phase 1, then only one will take precedence and show up.
All of these values are sent at the same time when a suitable order starts running. It is up to the machine to interpret the phases and configure those values accordingly.
Testing your Control Parameters
With this feature, you can test to see if your rules are going to be applied correctly as expected. This will pull all available Recipes and Rules to compare, not just the one opened in your user interface.
When a recipe is still a draft, denoted by the status bar on top of the screen or the presence of the "Promote to Live" button. You can then click on the Order Preview in order to test for a particularly order, which Rules' values will be sent to its asset(s)
Click on "Select an Order".
Then type to choose an Order you want to test the rules for.
You will then be able to see which Recipes and Rules will apply for this particular order, including the values that would be sent, the lower and upper limit.
Publishing to Live
You must publish the recipe to LIVE, see top left corner, in order for the Recipe and its Rules to be computed.
Avoiding duplicating Rules
It is important to note that Recipes are simply a way to group the rules, it is not necessary to create the same rule for every single Recipe as rules from different Recipes can be sent.
Example
You have a default recipe for the Blanching procedure. These include rules that generaly should be sent to the blanching machine under any orders.
However, sometimes, you have specific blanching Control Parameters values that you'd like to send to the blanching machine in the event of making that Product A.
This is when you should be creating a new recipe that includes only the specific rules for the Product A.
Let's see what this would look like in the Order Preview:
The Rules that will be sent are:
Default Temperature value from our Default Blanching Recipe
Wheel Speed value from our Product A - Blanching Recipe
This saved you from having to creating Temperature rules over and over again in every recipe.
Versioning
When the recipe is live
When the recipe is live, you cannot edit the LIVE version, but need to create a new version. Click on "Create new version".
After clicking on this, you will be shown a new recipe page that denotes as a Draft.
Note that you can change the name and all other details of the Recipe, except the "Recipe Key", which is set on creation. This lets the system know which Recipe to replace when you "Promote to Live".
Each Recipe Key can only have:
1 LIVE version
1 DRAFT version
What happens if you try to create a new version where a draft is already in place? It will lead you to the current draft.
Last updated