Creating Recipe Groups

After you create your Cookbook, the second phrase of the Cookbook setup process is to fill in the details that are specific to each Recipe Group. There are a number of discrete steps involved in this phrase.

To create Recipe Groups:

  1. In the Recipe Groups panel, select the Recipe Group that you want to set up.

To select Outcomes:

  1. Select the data fields that represent the results that you want to achieve.

    Outcomes can be results that you want to increase/maximize or decrease/minimize. Outcomes also contain a weighting. For outcomes that you care most about, provide more weighting. Weighing is relative so if you have one outcome with a weight of 1 and another with a weight of 4, the first outcome will be weighted with .25 or ¼.

To set Levers:

  1. Levers are the parameters that you can control or that you want to monitor. Levers are recommended to operators in the Operator CoPilot application. For more information, see Using the Operator CoPilot Application.

To set Conditions:

  1. Conditions are the factors that you cannot control, such as which supplier’s material you are using or the result of an upstream process. Each unique combination of conditions creates a recipe.When the condition field that you select has continuous data, you have the option to group the ranges of the condition.NOTE: This range configuration interface can appear in the Cookbook creation step as well, for Recipe Groups that are defined based on continuous data vs. categorical data. The conditions and ranges that you configure create discrete groups of data that are clustered into runs and classified as part of a given recipe.

    In the example above, the initial ranges selected do not offer useful segments to optimize, so the feedback to the process engineer here is to iterate in Draft mode. The process engineer can delete a Condition to try a different one, or test different range values. The process engineer can also add more ranges by selecting the plus (+) icon in the upper-right, until there is a strong representation of the different conditions likely to be encountered in the production process.
    To add multiple conditions, search for and add any additional conditions that may impact your production process.

To add Run Settings:

  1. Run settings allow you to further refine and optimize calculations. You can better define the boundaries of a run, determine how many runs to consider in your calculation, and decide which runs should not be considered because too short of a duration would not be a reliable benchmark.
    Select a run boundary field if you find this helpful. However, boundaries are currently limited to categorical values. A change in the value of a run boundary determines the start and end of each run.

    For example, if production is paused for shift changes, you may want to distinguish production before and after shift changes as different runs.
    Make sure to click Update after you have changed the boundary settings to provide the latest results for validation.

To add Filters:

  1. Filters also offer more control to filter out data within a run.

To set Time Ranges:

  1. The time range is available in Draft mode only and helps you select small subsets of data to quickly verify your recipe formula.

    After you deploy the Recipe Group, the Cookbook scans all available historical data and finds the best runs for each Recipe Group to use, based on the operating conditions that were encountered.

To work with the Runs Display table:

  1. To inspect the specific runs comprising the recommended setpoint values -- which are based on the average, upper control limit, and lower control limit (2 sigma) of the Top Runs Considered -- select the Recipe Group. This behavior is consistent in both Draft and Deployed modes.

    For example, consider the Recipe Groups below:
    If you select the first row, you see a table of those specific runs: