Skip to main content

How to Start a Production Run from a Plan

Learn how to turn a production plan into a real, scheduled production run.

I
Written by Ivan Jelinic
Updated over a month ago

Overview

Once you've created a Production Plan, the next step is to launch a Production Run. A production run is a real-world execution of that plan—scheduled on the calendar, named, and linked to a start date and time. Each work order step from the plan is automatically scheduled with durations, locations, and dependencies intact.

This tutorial walks you through how to create a new run, what happens when you do, and how to view it on the Planning calendar.


Prerequisites

  • You must have Admin privileges to create a production run.
    If you don’t see the Add Production Run button, contact your system administrator or Elevated Signals Support.

  • You must have at least one Production Plan created.
    If you haven’t done that yet, see How to Create a Production Plan.


Step-by-Step Instructions

1. Open the Planning Module

  • Click View Page to open the Planning calendar.

  • The calendar will default to Week View.
    Use the toggle on the right-hand side to switch between Day, Week, or Month views as needed.


2. Click "Add Production Run"

  • In the top right corner, click Add Production Run.


3. Select Your Production Plan and Customize Details

  • In the modal that opens:

    • Choose a Production Plan from the dropdown (e.g. Kombucha Production)

    • Enter a custom name for this run (e.g. Ginger Zing Production)

    • Select the Start Date and Time (e.g. May 1, 8:00 AM)


4. Click "Create"

  • Once all fields are filled, click Create to generate your production run.

The system will now schedule each step from your plan into the calendar, based on the durations and dependencies you set earlier.


5. View the Run on the Calendar

  • You’ll see the newly created production run appear on the calendar as a chain of scheduled work orders.

  • If multiple runs exist, filter the left-hand sidebar by production run name to focus on just one.


6. Review Any Conflicts

  • If any steps in the run overlap with existing tasks (e.g. location conflicts), they’ll be flagged automatically but the run will still be created.

  • Conflicts appear as icons or labels on the calendar, and can also be filtered for review.


What You’ve Done

  • Launched a new production run from a saved plan

  • Scheduled a series of dependent work orders

  • Viewed the run in the calendar

  • Identified potential scheduling conflicts

Did this answer your question?