These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Product Lifecycle Mgmt (PLM)
- Features
- Production execution
Production execution
Record a valid production interval and send its output to quality review.
OverviewMy production intervals×
Product Lifecycle Mgmt (PLM) · Production execution
New
My production intervals
Production logs
| Id | Work order | Operator | Started at | Ended at | Good units | |
|---|---|---|---|---|---|---|
| IDD-428 | WO-7376 | 07 Oct | 09 Oct | 50 | ||
| IDD-873 | WO-6718 | 26 Oct | 01 Nov | 110 | ||
| IDD-768 | WO-1215 | 24 Oct | 02 Nov | 40 | ||
| IDD-867 | WO-5299 | 16 Oct | 20 Oct | 160 | ||
| IDD-846 | WO-1716 | 12 Oct | 21 Oct | 120 |
6 of 6 records
IDD-428Production logs · PL-21249
Work orderWO-7376
Started at07 Oct
Ended at09 Oct
Good units50
Scrap units180
What you can do
Attribute the interval to the person doing the work
Operator records the production interval against the intended work order, with start and end dates and separate good and scrap quantities. The person’s account mapping establishes the operator identity used by the action. Confirm that mapping during setup so the team can explain who submitted the production evidence and retrieve the correct person’s intervals.
The production recording action requires an end strictly after the start and finite, nonnegative output quantities. It resolves the operator through the linked person and user identity, then routes the work order to quality review and its batch to Pending. Inspection follows that recorded output before accepted finished goods can enter inventory.
How the work is organized
- Valid interval. Enter the actual production boundaries using the agreed date convention. Equal boundaries and a reversed interval fail the rule and need correction before submission can succeed.
- Recorded quantities. Preserve good and scrap quantities separately. Ask Operator to explain both from the production evidence so Quality Inspector can understand the output awaiting review.
- Account mapping. Connect the operating person to the authenticated user. Rehearse own-record access using ordinary accounts and the same relationship that attributes the recording action.
What to agree during setup
Agree how the team submits interval evidence, which people map to active accounts and who helps resolve refused submissions. Check the start and end handling used by your operation before importing historical intervals. Decide what evidence the inspector needs alongside recorded quantities and how the operator supplies it at the end of the run.
Machine or shop-floor input is a connection to set up when required. Agree the source identity and quantity mapping with its owner before enabling submissions. Keep material posting and accepted-output receiving as separate operating actions. Inventory Controller should be able to reconcile consumption before and after an interval is recorded, while Quality Inspector should identify the pending output awaiting a decision.
Check the handoff on an actual case
Use the housing work order and an Operator whose account mapping is confirmed. For the rehearsal, use an interval ending after its start with 18 good units and 2 scrap units. These are recorded production quantities; the inspector still decides the accepted output. Inspect attribution, the work order routed to quality review and the Pending batch available for inspection. Ask Operator to retrieve that interval from their own view and explain the submitted quantities.
Try a reversed interval and a negative output quantity. Each should be refused with its input still understandable. Correct the source through the authorized action before submitting valid evidence. Check a missing person-to-account mapping as well; resolve identity before treating the submission as attributed work.
Inventory Controller then compares the material balance around a valid production submission. The earlier material issue remains the source of its deduction. Quality Inspector examines the Pending output and identifies the accepted-quantity evidence needed for release. Ask both people to explain the handoff against the same work order so recording and acceptance remain clear to the operating team.
What your team sees
- My production intervals — Review the authenticated operator’s start, end and reported quantities.
- Active work orders — Find released work and operating items needing attention.
- Pending batch decisions — Follow recorded output into the inspector’s decision queue.
Follow the work through
Record and accept output covers inspection. Post lot-based materials covers consumption. Review the quantity basis in reports.
What it keeps track of
Data model- Production logs
- Production interval logs.
- People
- People records for Product Lifecycle Mgmt (PLM).
- Users
- Users
- Work orders
- Production work orders.
- Batches
- Produced batches and disposition.
- Items
- Materials, components and finished goods.
- Resources
- Production resources and capacity.
Who uses it
PermissionsSet up Product Lifecycle Mgmt (PLM) your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.