Maintenance that counts what the machine did
Calendar-based maintenance services machines that have barely run and misses the one that ran three shifts a day all quarter. The interval that matters is usually usage, and usage is exactly what a maintenance spreadsheet does not know.
A Capitán maintenance plan belongs to a resource and tracks its counters — a running counter, a custom counter of your choosing and a lifetime counter — alongside the intervals that govern it: your preventive interval, your service interval, and the manufacturer’s. Due dates come from what the equipment has actually done.
Due work raises itself
When a plan comes due it can create the work order rather than waiting to be noticed, and it records when it was last done and when it is next expected. Notification state is tracked too, so a reminder is sent once rather than every time a job runs past its date.
Plans that mirror real equipment
Maintenance plans nest, so a machine with a quarterly service containing several sub-tasks is modelled as that rather than as five unrelated reminders. The resource being maintained is the same record the shop floor reports against — so a machine’s maintenance history sits beside its output, its downtime and its faults instead of in a separate register.
The machine that needs servicing is rarely the one whose date came up. It is the one that has been running hardest.
Because counters can be fed from equipment that reports its own data, a plan can be driven by real cycles or hours rather than by someone updating a number — see integrations.
