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 is expressed in counters — a running counter, a custom counter in a unit you choose and a lifetime counter — alongside the intervals that govern it: your preventive interval, your service interval, and the manufacturer’s. Keeping all three means you can see how far your practice has drifted from the handbook, and decide whether that is deliberate.
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 — and a completed plan means something specific rather than a tick against a heading.
History in one place
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. That is what makes the useful questions answerable: whether failures cluster before a service or after it, and whether the machine you service most is the machine that stops most.
The machine that needs servicing is rarely the one whose date came up. It is the one that has been running hardest.
Why usage beats the calendar, and why three intervals beat one — read the full argument.
