Powered
Electrical/control power is available. The machine may still be idle.
“Runtime” can mean powered, running, loaded, productive, cycling, or something else. Define the state first, reuse trustworthy existing signals where possible, and add instrumentation only when the decision still cannot be answered.
Electrical/control power is available. The machine may still be idle.
A defined machine motion or run state is active. It may not be loaded.
The machine is doing work above a defined load threshold. It may still produce no good product.
The machine is producing acceptable output under the agreed definition.
Discrete machine cycles or events are counted. One cycle does not automatically equal one good unit.
A defined expected-production period is lost. Planned stops and non-scheduled time should not be mixed blindly.
This selector does not design a control system. It shows the minimum evidence route that is usually worth checking before new hardware is proposed.
This calculator uses only the hours you enter. It does not infer causes, production quality, planned time, or OEE.
Often the best starting point when an existing state is documented and actually represents the physical condition required.
Useful for commanded/run state, but it does not by itself prove load, material flow, or good production.
Can indicate contactor/relay state. It may represent energisation rather than actual shaft motion or useful work.
Can help distinguish off, idle, and loaded states after validation, but thresholds and operating variation can create ambiguity.
Useful for discrete events where one verified event has a clear operational meaning; good output may still require a quality signal.
Observe the process first, define the state boundary, then specify the minimum sensing and data path required.