Machine Runtime Utilization Calculator

Use one process, asset or item scope, reporting period, cutoff, measurement unit, and written classification rule across both values. Runtime and availability use the same asset and clock boundaries. Overlaps, standby, blocked, starved, and microstop states follow one written rule. Reconcile the numerator to the eligible denominator rather than combining separately filtered reports. A changed population can move the percentage even when underlying operations did not change.

This isolates time running within availability; it is not OEE, performance speed, output yield, scheduled utilization, or economic capacity use. Compare periods or targets prepared from the same rules, not an assumed universal benchmark. Product mix, sampling, schedule changes, reporting delay, exclusions, automation, and event granularity can move the value. Review absolute observations and reason-level evidence beside the percentage before deciding on corrective work.

No. This calculator applies disclosed arithmetic to values you supply; it is not an audit, quality release, maintenance authorization, supplier ruling, forecast, or process certification. High runtime can coexist with slow production, defects, or unnecessary output and is not automatically desirable. Retain source records, version the metric definition, test late-arriving events, and obtain accountable review before using the result for incentives, acceptance, or contractual action.