1. OEE Tracking Dashboard
  2. Features
  3. Production execution
Feature · Production execution

Production execution

Release eligible work and retain the operator evidence behind production output.

OverviewItems and Details
OEE Tracking Dashboard · Production execution

Items and Details

Items

New
Item codeNameItem typeUnitStandard costActive
IC-351Item 866MaterialUNT-400840Yes
IC-751Item 420ComponentUNT-814800Yes
IC-522Item 390Finished goodUNT-933530Yes
IC-368Item 321MaterialUNT-694740Yes
IC-156Item 155ComponentUNT-246240Yes
6 of 6 records
IC-351Items · ITM-47773
Material
NameItem 866
UnitUNT-400
Standard cost840
ActiveYes
Example screen with sample data

What you can do

Keep the production run connected to its work order

Production Planner releases work against a product, customer order and resource. The release command checks the order state, planned quantity, resource availability and planned dates before saving the release result. Production Operator then records the actual production interval and good and scrap units against that work order.

These records give the team production context alongside its OEE review. Work orders and production windows each identify a resource and time basis. Use those details to establish which run is under discussion, especially when a machine carries successive jobs during the same day. The operator’s production log identifies who recorded the run.

How the work is organized

  • Release preparation. Production Planner checks Draft work in the release inbox and confirms the intended order and resource. The guarded command freezes the release input so a repeated request cannot silently change the plan already released.
  • Run recording. Production Operator enters the interval and unit counts. The recording command resolves the acting person, validates the log against work-order eligibility and advances released production to In Progress.
  • Batch identity. The initial production record creates the batch identity once. Retrying the same command returns the saved result without making another batch for the same event.

What to agree during setup

Agree who can release work and how the team confirms that a customer order is eligible. Check that each operator’s account maps to the correct person before recording production. Set a practical convention for naming work orders and logs so a reviewer can follow the run without relying on memory.

Decide how the team prepares a work order for Quality Review and how incomplete output is handed over. A successful log does not settle the final acceptance decision. Production Planner should establish the required output scope and bring disputed counts to Quality Reviewer before treating the job as ready for completion.

Check the handoff on an actual case

Rehearse a Draft work order for Press A with an eligible customer order and agreed planned dates. Production Planner releases it, then repeats the identical command. Confirm that the result remains the original release. Try changing the planned quantity on that same release input and make sure the conflict is resolved before the operator proceeds.

Production Operator next records a valid interval with good and scrap units. Check the attributed person, the move to In Progress and the initial batch. Repeat the same production command and confirm that no extra batch appears. Review an interval whose end precedes its start and ensure that the operator cannot use it as valid run evidence. These checks make the handoff understandable before the first live shift.

What your team sees

  • Production Release Inbox — Draft work orders awaiting the planner’s readiness check and release action.
  • My Production Logs — The operator’s attributed intervals and good and scrap counts.
  • Work Order Schedule — Released work and production under review alongside planned start and end dates.

Follow the work through

Start with planning and release, then capture run evidence. Review roles before the first shift.

What it keeps track of

Data model
Work orders
Released production work for a product, order and resource.
Orders
Customer orders that drive work orders and production demand.
Order lines
Item-level lines belonging to a customer order.
Items
Materials, components and finished goods produced or purchased.
Resources
Production resources and machines with daily capacity.
Production logs
Operator-captured production intervals with good and scrap units.
People
App users with their production role titles.
Batches
Produced lot identities and their quality disposition.

Who uses it

Permissions
Production Planner
, Production Operator, Quality Reviewer, Manager, Admin.
The planner releases work, the operator records the run, and the reviewer assesses output evidence before acceptance.

Set up OEE Tracking Dashboard your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started