Direct answer
Collect production data only when it supports a decision. Start with good count, reject count, planned time, running time, blocked, starved, fault and changeover states. Use consistent definitions before calculating OEE or integrating a line with MES, ERP or reporting systems.
Key takeaways
- Define the operational question before selecting software.
- Create trustworthy state and count definitions.
- Build from local visibility to connected systems.
- Use governance, change control and routine review.
Set a measurable objective
Decide whether the priority is output, downtime, giveaway, traceability, schedule adherence, maintenance or labour. The same signal can be interpreted differently without agreed state definitions.
- Name the decisions the data must support
- Define machine and line boundaries
- Agree good, reject and rework counts
- Set shift, product and order context
Measure the current production condition
Distinguish planned stops, breakdown, waiting for product, waiting for downstream, changeover and quality hold. Validate automatic signals against observation before using them for management decisions.
- Time-synchronise connected equipment
- Prevent double-counting at transfers and rework
- Record reason codes at the right level
- Check data loss during network or control restarts
Plan the work in a controlled sequence
A reliable machine dashboard may deliver value before MES integration. Add historian, line reporting, order data and enterprise links only when ownership, cybersecurity and support are clear.
- Start with a stable local data model
- Pilot reports with operators and supervisors
- Define APIs, protocols and data ownership
- Test failure, buffering and recovery scenarios
Hold the improvement after handover
Keep data definitions, calculations, user access, backups and software versions controlled. Review whether metrics drive action rather than merely creating dashboards.
- Publish metric definitions and exclusions
- Audit manual reason-code quality
- Control user access and remote connections
- Review improvement actions against the data
Comparison table
| Stage | Customer decision | Evidence |
|---|---|---|
| Objective | Define the operational question before selecting software. | A numerical target and owner |
| Baseline | Create trustworthy state and count definitions. | Representative production records |
| Action | Build from local visibility to connected systems. | A timed plan with responsibilities |
| Control | Use governance, change control and routine review. | Approved standard work and review data |
Free working templates
Download these files and adapt them to the actual machine, product, site and acceptance plan.
Related buyer guides and tools
Relevant machinery and support routes
Use the guide to define the requirement, then compare the specialist routes below against representative product, packaging and output evidence.