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.
- Production Dashboard
- Features
- Shift performance
Shift performance
Compare recorded shift output and run minutes with the same resource, product and dated target.
OverviewShift output review×
Production Dashboard · Shift performance
New
Shift output review
Shift actuals
| Name | Target | Shift code | Good units | Scrap units | Run minutes | |
|---|---|---|---|---|---|---|
| Actual 827 | PT-7295 | SC-835 | 70 | 290 | 90 | |
| Actual 347 | PT-5050 | SC-869 | 140 | 60 | 120 | |
| Actual 576 | PT-3127 | SC-194 | 160 | 960 | 120 | |
| Actual 563 | PT-8337 | SC-898 | 70 | 360 | 5 | |
| Actual 629 | PT-7035 | SC-414 | 190 | 160 | 90 |
6 of 6 records
Actual 827Shift actuals · SA-63588
TargetPT-7295
Shift codeSC-835
Good units70
Scrap units290
Run minutes90
What you can do
Explain the gap behind the shift result
Each shift result records good units, scrap units and run minutes against a selected target, with shift code and recording date providing the reporting context. The target points to the selected target’s resource, product and target date. This lets the planning team compare recorded output with the intended run without guessing which machine or product a shift summary describes.
Production Operator submits the actuals through the shift capture action. Production Planner reviews the resulting evidence and decides which operational follow-up is needed. Use Business Overview to orient the daily discussion, then prepare detailed comparison views around the records used in your operating cycle.
How the work is organized
A shift summary and a production interval describe different populations. Production logs can explain the good and scrap units recorded during work on a work order. A shift actual summarizes the shift against its target. Adding both populations into the same output total would count production again.
- Target selection. Resolve the actual linked production target before accepting a shift summary.
- Output capture. The shift capture action validates shift code, good units, scrap units, run minutes and recording date and saves attributed evidence.
- Comparison basis. Compare effective actuals with the linked target and keep missing evidence visible during review.
What to agree during setup
Define shift code labels your operators recognize and the production day each code belongs to. Use consistent shift labels so the team can recognize the same operating period in each result. Agree how a shift crossing midnight uses recording date while retaining the correct target date through its target reference.
Choose the correction-selection rule before calculating totals. The shift capture action appends attributed successor evidence when results change. Verify which result is effective with the people responsible for the comparison. A missing shift summary remains unrecorded; it cannot silently become a zero-output result.
Check the handoff on an actual case
An operator finishes a component run on the afternoon shift. They select the target for that resource, product and production day, enter good units, scrap units and run minutes, then inspect the returned evidence. Production Planner checks that the target is the intended plan before comparing the result with target good units and planned minutes.
The operator later discovers an omitted scrap quantity. Submit the corrected successor through the shift capture action and preserve the earlier evidence. Recalculate the comparison using the effective result. The correction should change the explained output population without making the same shift appear as another completed run.
Rehearse a target reference that cannot be resolved and an invalid capture date. Confirm the rejected submission does not enter the comparison. Then test a target with no linked actual and a target with zero planned minutes. Show missing evidence explicitly and leave the time ratio undefined when its denominator is zero.
What your team sees
Configure the review around the same planning basis:
- Shift output review — Inspect the target, shift code, good units, scrap units, run minutes and recording date together.
- Production targets by date — Verify the planned output and minutes behind the selected shift comparison.
- Production interval history — Investigate recorded intervals without adding their output to the shift total again.
Follow the work through
Use target to shift review to rehearse missing results and corrections. The reports page defines the denominator and record population for each comparison.
What it keeps track of
Data model- Shift actuals
- Shift-level actual output recorded against a production target.
- Production targets
- Planned good units and minutes per resource, product and date.
- Resources
- Production work centers and machines.
- Items
- Materials, components and finished goods.
- Production logs
- Operator production intervals with good and scrap units.
Who uses it
Permissions- Production Operator
- , Production Planner, Quality Reviewer, Manager.
- Production Operator
- Captures results; Production Planner leads the operational review.
- Quality Reviewer
- Reads eligible evidence.
- Manager
- Reviews the output comparison with the planner.
Set up Production Dashboard your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.