Use cases

Preventive maintenance scheduling in Cohiva Control

In short

Preventive maintenance in Cohiva Control runs on schedules that generate work orders automatically on a time or meter interval. Generation is idempotent, so a re-run never creates duplicate work orders, and PM compliance is tracked against the schedule, so you can see whether planned maintenance is actually happening.

Preventive maintenance scheduling in Cohiva Control

Preventive maintenance is the difference between fixing things on a plan and fixing them after they break. The hard part is not deciding to do it; it is making sure the planned jobs actually get raised and done, reliably, across a fleet of assets and a busy team. Cohiva Control handles that by generating preventive maintenance work orders automatically from schedules, and by tracking whether those schedules are being met.

Schedules that raise work automatically

You set up a preventive maintenance schedule against an asset and define its interval. When a job is due, Cohiva Control generates the work order for you. There is no reliance on someone remembering to raise the next service, and no separate calendar to keep in step with the maintenance system. The schedule is the source of truth, and the work orders flow from it.

Time or meter intervals

Not every asset wears on a calendar. Some wear with use. Cohiva Control supports both, so a schedule can trigger on a time interval, such as every three months, or on a meter interval, such as every set number of hours run or units produced. For a pump, a compressor or a piece of production machinery with a reliable meter, a usage-based schedule matches the maintenance to how hard the asset actually works rather than to a fixed date.

Idempotent generation: no duplicates

Automated generation has a classic failure mode: running twice and creating two work orders for the same due event. Cohiva Control’s generation is idempotent, which means a second run for the same event does not create a second work order. A retry after an interruption, or a scheduled run that overlaps with another, will not flood your queue with duplicates. The team sees one job for one due event, which keeps the work list honest.

PM compliance you can see

A schedule that exists is not the same as maintenance that happens. Cohiva Control tracks PM compliance against the schedule, so you can see whether planned maintenance is being completed on time or slipping. That visibility turns preventive maintenance from an intention into something you can manage, report on and improve. If compliance is dropping on a class of asset, you can see it and act before it shows up as failures.

How it connects to the rest of the system

Preventive maintenance does not work in isolation. Schedules run against assets in the register, and the work orders they generate move through the same server-enforced state machine, with an append-only history, as any other work order. The meters that drive meter-based schedules are the same meters used by the units of production depreciation method, so usage is captured once and serves both maintenance and finance. And if a contractor is assigned to a preventive maintenance job, the contractor-compliance gate checks their documents first and hard-blocks anyone who is not compliant.

The payoff

Done well, preventive maintenance reduces unplanned failures, extends asset life and smooths the workload. Cohiva Control makes it dependable by removing the manual step of raising the work, preventing duplicate jobs, and showing you whether the plan is actually being followed. The result is a preventive maintenance program you can trust rather than hope in.

Part of the Cohiva platform

Cohiva Control is part of the Cohiva platform. Leisure operators often run it with Cohiva Complex, and finance teams connect it to Cohiva Crunch for the general ledger. Explore the platform at www.cohiva.app.

Frequently asked questions

How are preventive maintenance work orders created?
Automatically, from a schedule. You define the interval, by time or by meter, and Cohiva Control generates the work order when it is due, so planned jobs are raised without anyone remembering to do it.
Can schedules run on usage rather than the calendar?
Yes. A schedule can trigger on a meter interval, such as hours run or units produced, as well as on a time interval. Meter-based schedules suit assets whose wear tracks usage.
What stops duplicate work orders?
Generation is idempotent. If the generation process runs again, it does not create a second work order for the same due event, so a retry or an overlapping run does not flood the queue with duplicates.
Can I tell whether PM is actually being done?
Yes. PM compliance is tracked against the schedule, so you can see how planned maintenance is performing rather than assuming it is happening because a schedule exists.
How does this connect to the asset register?
Schedules run against assets in the register, and the meters that drive meter-based schedules are the same meters used for units of production depreciation, so usage is recorded once and serves both.