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
- Target planning
Target planning
Give each resource and product a dated output target and a planned time basis for the production review.
OverviewProduction targets by date×
Production Dashboard · Target planning
New
Production targets by date
Production targets
| Name | Target date | Resource | Product | Target good units | Planned minutes | |
|---|---|---|---|---|---|---|
| Target 969 | 22 Oct | RSR-8477 | ITM-2184 | 100 | 100 | |
| Target 965 | 20 Oct | RSR-2451 | ITM-1464 | 40 | 45 | |
| Target 737 | 18 Oct | RSR-6761 | ITM-6724 | 80 | 90 | |
| Target 904 | 20 Oct | RSR-5495 | ITM-2584 | 60 | 45 | |
| Target 974 | 16 Oct | RSR-3077 | ITM-3627 | 120 | 90 |
6 of 6 records
Target 969Production targets · PT-75839
Target date22 Oct
ResourceRSR-8477
ProductITM-2184
Target good units100
Planned minutes100
What you can do
Give the shift a clear comparison point
A production review needs the intended output before the team can explain the result. Each production target connects resource and product with target date, target good units and planned minutes. Production Planner owns the operating plan, while Production Operator uses the guarded target capture action to submit the agreed inputs. The saved evidence gives the later shift result a specific planning basis.
Use the product reference and its unit consistently. A target for a component on a press cannot be compared with a finished product from a packing station just because their names look similar. The linked resource and product carry the meaning; a target’s name helps people find it but cannot replace those references.
How the work is organized
The target capture action resolves the authenticated actor through the staff record’s linked user account and checks the actual resource and product references before saving the target. It validates target date, target good units and planned minutes and returns attributed immutable evidence for review. Submission does not approve a batch or release a work order.
- Planning basis. Production Planner agrees the product, resource and production date that the target represents.
- Attributed capture. Production Operator submits the selected references and values through the guarded workflow.
- Reviewed correction. A later correction appends successor evidence while the earlier target remains available for explanation.
What to agree during setup
Choose how your team names a target, which production day target date represents and which resource owns the work. Agree whether planned minutes represent the intended run or a broader planning allowance; the field name alone cannot answer that operating question. Document how shifts that cross midnight link back to their intended target date.
Review target correction behavior before enabling aggregate comparisons. Agree how the comparison selects the effective target after a correction. Test that selection against the saved evidence and make the revised planning basis clear to the people reading the result. Do not add earlier and corrected target quantities together as if both were separate commitments.
Check the handoff on an actual case
The team plans a component run on a press for the next production day. Production Planner agrees its good-unit target and time allowance. Production Operator selects the actual press and component in the target capture action, then checks the saved resource, product and target date before handing the evidence to the planner.
During preparation, the planner discovers that the intended run belongs to another date. Use the correction path and keep the original evidence. Rehearse selecting the corrected target when recording shift actuals; the production review must explain the revised basis without counting both versions.
Also submit a target with a missing resource and another with an unresolved product reference. Confirm the workflow rejects those inputs before creating usable evidence. Review validation outcomes for unacceptable quantities or minutes with the operating owner rather than assuming that every decimal value is a legitimate plan.
What your team sees
Configure these views for the agreed operating scope:
- Production targets by date — Review targets through the coming week with the selected resource, product, good-unit target and planned minutes.
- Shift output review — Follow the shift results linked to the target whose plan the team is reviewing.
Follow the work through
target to shift review connects the saved planning basis with actual output. Agree the comparison and correction rules in implementation before expanding the pilot.
What it keeps track of
Data model- Production targets
- Planned good units and minutes per resource, product and date.
- Resources
- Production work centers and machines.
- Items
- Materials, components and finished goods.
- People
- Production staff and their linked platform user accounts.
- Shift actuals
- Shift-level actual output recorded against a production target.
Who uses it
Permissions- Production Planner
- , Production Operator, Quality Reviewer, Manager.
- Production Planner
- Owns the plan; Production Operator captures evidence.
- Quality Reviewer
- Reads within review authority.
- Manager
- Reviews the operating basis 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.