How Do You Schedule Maintenance From Machine Runtime?
Schedule maintenance from machine running hours by defining what counts as runtime, recording it in a durable counter, and comparing that counter with an agreed service threshold. When the threshold is reached, create or update a maintenance request against the correct asset. Advance the service baseline only after the relevant work is recorded as complete.
The calculation is straightforward. The important decisions concern which hours count, how readings survive interruptions, and who confirms that the work was done.
Which machine hours should count towards maintenance?
Start with the maintenance instruction for the component or task. Agree the counter definition with the maintenance lead and, where necessary, the equipment supplier. Do not assume that every task on a machine should use the same counter.
| Counter basis | Proposed counting rule | Question to settle |
|---|---|---|
| Powered-on time | Count while the agreed power-status signal is active | Should idle time with power available count? |
| Running time | Count while operation is confirmed | Which signal proves operation? |
| Loaded time | Count while the machine is operating under the agreed load condition | What defines loaded operation? |
| Component runtime | Count while a particular component operates | Does its usage differ from the main machine? |
Treat these as definitions to agree, rather than universal maintenance rules. A start command alone should not be accepted as proof of operation without checking what it means on that machine.
For loaded time, specify the signal, threshold and treatment of brief changes. If the signal is missing or invalid, show the reading as uncertain and raise it for review. Do not silently treat missing data as zero usage.
Keep maintenance counters separate from production measures unless their definitions match. Our guide to what the OEE number hides provides context for discussing plant measures.
What should you agree before configuring the counter?
Write a short counter specification that operations and maintenance can both review:
- The asset and component being measured.
- The operating condition that starts and stops counting.
- The source signal and the system holding the authoritative total.
- The unit, displayed precision and service interval.
- What happens during signal loss, power loss or a controller restart.
- Who may correct a reading and what evidence they must record.
- Which system creates the maintenance request and records completion.
Store elapsed time consistently and round only for display. Avoid calculating the next threshold from a rounded dashboard value.
Give each maintenance task its own baseline. Completing one task should not reset the schedule for unrelated work on the same machine.
Put these decisions in the functional design specification, including the interface and failure behaviour.
How do you turn running hours into a service trigger?
For a schedule measured from the last completed service, use:
Hours since service = current cumulative runtime − runtime recorded at service completion
The task becomes due when those hours reach the agreed interval. You can also define an earlier planning notice, leaving the due threshold unchanged.
Consider this illustrative example:
| Item | Illustrative value |
|---|---|
| Cumulative runtime at completed service | 8,200 hours |
| Agreed interval | 500 hours |
| Next due reading | 8,700 hours |
| Current cumulative runtime | 8,640 hours |
| Hours remaining | 60 hours |
In this example, a planning notice could prompt preparation before the due reading. Choose that notice according to the time needed for people, parts and access.
Show both the due reading and remaining hours. A forecast date may help planning, but label it as an estimate based on expected use. The runtime threshold remains the agreed trigger.
What happens when maintenance is early or late?
Choose the scheduling policy before the first work order closes.
Under a completion-based schedule, the next interval starts at the actual runtime when service finishes. In the illustrative example, work completed at 8,720 hours would put the next due reading at 9,220 hours.
Under a fixed schedule, thresholds remain anchored to an agreed sequence. The next due reading might remain 9,200 hours, despite the late completion.
Neither policy should be selected by accident. Confirm the appropriate rule for each task against the maintenance requirements. Record any authorised exception.
Keep overdue work visible until it is completed or formally resolved. An acknowledgement, assigned technician or ordered spare should not mark it complete. Define how unresolved work is escalated and who decides whether operation may continue.
How should you handle counter resets and replacements?
Prefer a cumulative usage total that ordinary maintenance does not reset. Record a separate service baseline for each task.
If a device counter resets or is replaced, preserve continuity through an explicit adjustment record. Capture the last accepted reading, the new starting reading, the reason and the person approving the change.
For example, if a replacement counter starts at zero, retain the accepted earlier total separately and add subsequent usage to it. Keep the original readings available so the adjustment can be checked.
Distinguish between replacing the measuring device and replacing the component being maintained. A new meter does not mean the machine has no previous usage. A new component needs its own installation record and baseline.
Before accepting the design, test:
- Power loss and restart.
- A reading lower than the previous accepted reading.
- Counter rollover at its configured limit.
- Replacement or restoration of the device.
- Missing readings followed by reconnection.
Quarantine unexplained jumps or decreases for review. Any estimated usage should remain visibly identified as an estimate.
What must the completed-work record contain?
A completed record should explain what happened and establish the next baseline. Include the asset, task, work-order reference, completion time, actual completion runtime, work performed and completion approval.
Record deferred items separately. If the task is only partly finished, keep the outstanding work visible and follow the agreed rule for whether a new baseline is permitted.
Do not substitute the runtime when someone later enters the paperwork for the runtime when the work finished. If the actual reading is unavailable, record that gap and obtain an authorised decision.
Retain both the previous and new baseline. A correction should explain the change rather than overwrite its history without a trace.
How should readings reach the maintenance system?
Agree which system owns each decision. One practical arrangement is for the plant system to supply accepted runtime readings and for the maintenance system to own schedules, work orders and completion records.
Alternatively, the plant system may calculate that work is due and send a request. In that arrangement, define how accepted completion returns to the counter display.
For either approach, specify:
- A stable asset identifier and counter definition.
- Reading value, unit, observation time and validity status.
- A unique reference for each maintenance occurrence.
- Confirmation that a request was accepted.
- Retry behaviour and a visible queue for failed transfers.
Repeated delivery of the same request should update the same occurrence rather than create another work order. Check this during testing.
After an outage, reconcile pending requests and accepted readings. Keep “data received”, “work requested” and “work completed” as separate states.
What are the common mistakes?
Counting power availability as loaded operation. Check the selected signal against observed machine states.
Resetting every schedule after one service. Maintain a separate baseline for each task.
Closing work when the alert is acknowledged. Require the agreed completion record.
Allowing an outage to clear overdue status. Preserve accepted totals, thresholds and outstanding work.
Treating runtime as the only maintenance requirement. Confirm whether calendar, condition, cycle-count or other requirements also apply. Runtime scheduling should sit alongside those requirements.
A maintenance reminder should create and track work. Any proposed automatic stop or safety-related response needs a separate design with a qualified assessor.
What should you prove before handover?
Walk through a complete maintenance occurrence with operations and maintenance present. Confirm counting, threshold detection, request acceptance, duplicate handling, completion and the next due reading.
Then repeat the relevant steps through a restart and a communication outage. Check the records in the maintenance system, including corrections and failed transfers. Handover is ready when the team can explain both the normal sequence and the recovery process.
Frequently asked questions
Should I use loaded hours or powered-on hours?
Use the basis specified or agreed for that maintenance task. Define it explicitly and verify the source signal against actual operation.
Should the hour counter reset after maintenance?
Prefer to retain cumulative runtime and record a separate completion baseline. If a device must reset, preserve continuity and the adjustment history.
Can different tasks have different intervals?
Yes. Give each task its own interval, completion record and scheduling policy, even when several tasks share one runtime counter.
What if the maintenance system is unavailable?
Retain readings and pending requests, show the transfer failure, and reconcile after recovery. Keep overdue work visible throughout.
To decide when runtime-based schedules are enough and when condition data is worth adding, see predictive vs preventive maintenance.
Planning runtime-based maintenance? Explore our automation services or contact us to discuss counter definitions, maintenance records and system handover.