Collect the signals that explain what production is actually doing.
Production data acquisition collects machine state, cycle counts, sensor values, alarms, process measurements, downtime, rejects, and other operating signals so teams can analyze performance with real production evidence.
Measure the system in terms production teams can act on.
Demand, cycle behavior, available time, good output, constraints, downtime, and actual production data should remain connected.
Use the metric to guide a decision, not just report a number.
Each measurement is useful only when it helps clarify capacity, flow, loss, scheduling, or improvement priorities.
CRIT-ACapture the Right Signals
Collect data that explains state, count, fault, quality, and process conditions rather than every available tag.
Related Guide →CRIT-BTimestamp Events Consistently
Event timing should make it possible to reconstruct sequence, downtime, cycle behavior, and machine interactions.
Related Guide →CRIT-CPreserve Context
Product code, shift, recipe, operator state, and work order can be necessary to interpret production values correctly.
Related Guide →CRIT-DUse Data for Action
Collected information should support maintenance, quality, scheduling, or improvement decisions instead of becoming an unused archive.
Related Guide →Relevant production measurement resources.
References are selected from the approved TempoJS industrial link inventory.