Creating New Cookbooks
    • Dark
      Light

    Creating New Cookbooks

    • Dark
      Light

    Article summary

    Overview 

    The Cookbook setup process has two phases, each with a few steps.

    The first phase is to create the Cookbook outline, which breaks down into multiple Recipe groupings for product-specific Recipes. This process is designed to help you with your initial setup, as well as introduce you to settings that are common across all Recipes.

    Working with Cookbooks 

    You can access Cookbooks using the Sight Machine platform’s top navigation bar. When you go to the Cookbooks page, you see a list of all the existing books. You also have the option to create a new Cookbook.

    If you select an existing book, you access the Recipe Groups that it contains. You also have the option to go to the Operator CoPilot for that Cookbook. For more information about Operator CoPilots, see Using the Operator CoPilot Application.

    The Cookbook setup process consists of the following phases, each with a number of steps:

    Understanding Cookbooks

    The general goal of a cookbook is to help you configure your machines—by adjusting settings known as levers—to maximize a Key Performance Indicator (KPI) or outcome.

    • KPI / Outcome: The result you're trying to maximize (e.g., OEE, good tons of cookies produced, availability).
    • Levers: Independent variables or controllable settings on your line that you can tweak to affect the outcome (e.g., oven temperature, amount of flour, cook time).
    • Tags: A more generic term for any column of data being ingested; this includes both Levers and Outcomes.
    • Conditions: Factors that you cannot control, like ambient temperature or humidity, but that still affect the optimal lever settings. Cookbooks allow you to specify ranges for these conditions and will provide different optimal recommendations for each range.

    How to Create New Cookbooks 

    1. Define Scope and Identify Product:
      • On the Cookbooks page, click Create New Cookbook, then select the Assets (machines/lines) that will be optimized, and finally identify the data field that determines the product type you intend to run.

    2. Name and Finalize:
      • Confirm or update the title to clearly describe the Cookbook, and then click Create to launch your new optimization tool.

    Machine Type - Cookbooks

    The new Machine Type - Cookbooks feature fundamentally changes how you optimize the performance of similar assets across your production lines. Instead of setting up a separate cookbook for every individual machine, you can now analyze and optimize multiple machines of the same type simultaneously.

    How to Use Machine Type Cookbooks

    1. Create a New Cookbook

    • Navigate to the Cookbooks feature in Factory Analyze. Select the Create New Cookbook button.  
    • Select the Machine Type Cookbook option.


    2. Configure Assets and Fields

    • Select Assets: Choose all the machines of a single type (e.g., all 'Filler' machines) that you want to optimize. The system will restrict your selection to a single machine type.

    • Select Levers, Outcomes, and Conditions: Configure your optimization using the un-nested field pickers. The settings you select will apply to all machines of the chosen type.

    3. Review Results

    • The Recommendations and Lever Insights pages are generally identical to the Line Cookbook format.
    • In the Runs table, you will see a new Machine Name column indicating which specific machine the run data came from.
    • The Copilot view is also identical but includes a Machine Picker to select which individual machine's current lever values you want to display and track against the optimal recommendations.

    Feature Benefits

    Optimize machine types by creating a single cookbook for all machines of the same type across the factory. Centralized optimization uses aggregated data from similar machines to recommend statistically robust settings. This approach eliminates the need for separate line cookbooks, reducing configuration work. Run-level results clearly show which machine contributed data, adding context to recommendations.

    Portability and Cloning

    • Cookbooks cannot be directly copied.
    • Users can clone a cookbook and then re-select the appropriate machines for the new context.