What is a production run?
A production run defines when a product runs on a line. Starting a run activates the check groups in each area and begins scheduling timed checks, so operators know exactly what to complete and when. Ending the run closes it out and sends it to history with its report.
Start and end a run
Web app
Log in to the web app.
Select Production, then select your site and line.
Select the product you're running, and optionally enter the number of units and operators.
Select Start run.
To finish, open the run that's in progress and select End run.
What are checks during a run?
Once a run is underway, operators complete checks in their area. Some are batch checks you trigger at a moment such as a batch change, and others are timed production checks the system prompts on a schedule. The area screen is built for fast entry, so completing a check takes seconds.
Complete a check
Web app
Log in to the web app and open your area.
For a batch check, select the batch check group and start a new batch. For a timed check, select the check that's due.
Enter a response for each check item. As you type, the screen shows whether the result is within spec, non-conforming, or critical.
Select Save.
How do checks raise issues?
When a check result breaches an out-of-spec or critical limit, Production automatically creates an issue and fires an alert. The issue captures the failure in context, the check, the recorded value, the acceptable range, the line, the product, and the time, so the right people can pick it up and resolve it. This closes the loop, so a bad result is tracked through to resolution rather than slipping by.
Please note that issues route to people based on how you've set up your alerts and issue categories.
Review and act on an issue
Web app
Log in to the web app and open the alert, or go to Issues.
Select the issue to open it and review the details, the check, the recorded value, the acceptable range, the line, the product, and the time.
Start an investigation or inspection, create actions to assign follow-up work, then close the issue once it's resolved.
Mobile app
Open the alert from your device, or tap Issues.
Tap the issue to review the failure details.
Investigate, create actions, and close the issue once the deviation is handled.
This keeps the deviation, the investigation, and the resolution linked in one place.
What are run history and AI reports?
Every completed check is stored in history, giving managers a full audit trail across shifts, lines, and time periods. When a run ends, Production generates an AI report that summarizes the run in plain language, flags anomalies, and analyzes patterns across your check data, including trends across multiple runs, such as the same issue recurring over several runs of a product.
View runs, reports, and data
Web app
Log in to the web app.
Select Production, then open history and select the run you want to review. You'll see the checks completed and any failures, along with the run's AI report, which summarizes the run, highlights breaches and near-misses, and surfaces trends across runs.
To analyze the data yourself, select to download it from the run.
Please note that the run report is read-only. It's a record of what happened during the run, so it can't be edited after the fact. The downloaded data is formatted for analytics and interrogation, so it looks different from the on-screen report.
