The one principle that makes it work
Ask "how does a CMMS work?" and the honest answer is not a feature list — it is a single design principle: every element is a linked record on one engine. The asset, its spares, its preventive schedule, each work order, each spare issue and each KPI are not separate files; they are connected rows that reference one another. Because they are linked, an event in one place propagates everywhere it should: issue a spare against a job and stock falls, cost accrues to the asset, and the maintenance history grows — all from one action.
That is the difference between a CMMS and a folder of spreadsheets. The spreadsheets hold the same facts, but nothing connects them, so the numbers never reconcile and nobody trusts them. The rest of this guide walks the chain link by link. For the conceptual overview first, see the pillar, what is CMMS software.
Step 1 — the asset register
The chain starts with the asset register: the single authoritative list of the machines and equipment you maintain. Each asset is a record carrying its make, model, serial, capacity and specifications, its location and parent line, its criticality rating, its AMC and warranty dates, and — crucially — a printed barcode or QR tag. That tag is what makes the system usable at the machine: a technician scans the serial on a phone and the asset's card and full history open right there, a pattern called scan-to-card.
Nothing downstream can work without this foundation, which is why most plants begin by importing an existing asset list from Excel and cleaning it up. Get the register right and every later step has something solid to attach to; get it wrong and the whole chain wobbles. See Asset Register & Tracking and Barcode & QR.
Step 2 — link spares and PM plans
With assets registered, two things are attached to each one. First, its spare bill of materials — the list of spare parts that fit this specific machine, each with a reorder level on the critical ones. Second, its preventive-maintenance schedule — the plan for recurring work, defined either by a calendar interval (every 30 days, every quarter) or by a usage count (every 500 running hours, every 100,000 cycles, every 10,000 km), with a checklist template of the tasks to perform.
These two links are what let the system act intelligently later. Because the spare BoM is attached, a work order already knows which parts a repair needs and whether they are in stock. Because the schedule is attached, the system knows what is due and when. This is the moment a static register becomes an active system. See Spare Parts & BoM and Preventive & Planned.
Step 3 — due detection
Now the system does something a spreadsheet cannot: it watches. For a calendar-based plan it tracks the due date; for a usage-based plan it tracks the meter — running hours, cycles or kilometres entered against the asset. When the due date arrives or the meter crosses the threshold, the asset surfaces on a PM-due dashboard and, optionally, triggers an alert to the planner over email, SMS or WhatsApp.
The parallel path is the reactive one: a production supervisor reports a breakdown, and the downtime clock starts immediately. Either way, the system has now detected that work is needed — proactively from a schedule, or reactively from a failure — without anyone having to remember. Gauge calibration rides the same mechanism: a calibration-due recall is functionally a PM schedule for measuring instruments, surfaced on the same due list. See Calibration & Gauge.
Want to watch a schedule raise its own work order?
In 30 minutes we can show due detection, an auto-generated work order and a spare issue on your own assets — cloud or on-premise.
Step 4 — work orders raise themselves
Detection is only useful if it produces action, and this is where a CMMS earns its keep. When a preventive schedule falls due, the system can generate a work order automatically — pre-filled with the asset, the checklist tasks from the schedule template, and an assignee — so the job exists without anyone typing it. A reported breakdown becomes a work order the same way, carrying the fault and the downtime clock.
From here the work order follows its lifecycle — Draft, In-Progress, Completed, Closed — with every transition written to a status history and audit trail. This is the same document engine that carries tickets across the platform, which is why the maintenance work order inherits approvals, audit and reporting for free. The full mechanics of that lifecycle are covered in the maintenance work order process.
Step 5 — execute and issue spares
The technician now executes the work order, and every action feeds the chain. Checklist items are recorded as OK, not-OK or a measured value; a not-OK finding can spawn a corrective work order. Labour time is logged. And when a part is needed, it is issued from stores against this specific work order — the issue decrements stock and attaches the spare's cost to the job.
This is the link that makes the numbers honest. Because the spare came off the shelf against a named work order on a named asset, per-asset spare consumption and maintenance cost are accurate rather than estimated. If a required part is not in stock, a maintenance purchase can be raised to procure it, connecting the repair to Fast Inventory & Purchase. For breakdowns, the downtime stop-time is logged here, closing the interval that the KPIs will use. See Asset Inward & Repairs.
Step 6 — KPIs recompute
Closing the work order is where the whole chain pays off. The moment it moves to Closed, the job joins the asset's maintenance history and the reliability numbers recompute — automatically, from the data captured along the way, not from anyone's manual tally:
| KPI | Computed from | Tells you |
|---|---|---|
| MTTR | Breakdown down/restored timestamps | How fast you recover — maintainability |
| MTBF | Uptime between consecutive failures | How seldom it fails — reliability |
| Availability | MTBF ÷ (MTBF + MTTR) | The uptime a plant head cares about |
| PM compliance | Planned vs completed PM work orders | Is the preventive programme actually run |
| Maintenance cost | Labour + spares rolled up per asset | Which machines are money pits |
These land on a live machine-status board — every asset shown running, under breakdown or idle — and on MTTR/MTBF dashboards that plot trends per machine. Layered on top, Dhruv AI can summarise breakdown and downtime patterns in plain language and cluster free-text cause remarks into named recurring themes.
The loop closes and repeats
The chain is really a loop. What Step 6 reveals — which assets fail most, which spares are consumed, where downtime concentrates — feeds back into Step 2: better preventive schedules, sharper reorder levels, and criticality ratings that reflect reality. Each turn of the loop makes the next one calmer. That feedback is the deepest reason a CMMS beats a set of records that merely store the past: it uses the past to shape the next schedule.
How Fast Maintenance implements the chain
Fast Maintenance Software implements exactly this chain on the shared Fast Suite platform, built by Improsys in Pune, cloud or on-premise:
Because it is one platform, the chain runs the same for manufacturing plants, facilities and utilities and equipment and fleet — and it aligns with TPM and ISO 55000 practice for the audit evidence covered in the benefits guide. See indicative pricing; confirm figures with your CA.
Frequently asked questions
How does CMMS software work?
A CMMS works by linking five things into one chain. First, an asset register holds every machine as a record with specs, criticality and a barcode/QR tag. Second, each asset is linked to its spare parts (a spare bill of materials) and to preventive-maintenance schedules. Third, when a schedule falls due or a breakdown is reported, the system generates a work order or ticket against the asset. Fourth, the technician executes it — checklist, repair, spares issued from stores against the job, downtime captured. Fifth, closing the work order updates the asset's history and recomputes MTTR, MTBF, availability and PM compliance. Because every step is a linked record, the numbers reconcile automatically.
How does a CMMS generate work orders automatically?
A CMMS stores a preventive schedule against each asset, defined by a calendar interval (every N days) or a usage count (every N running hours, cycles or km). The system watches the due date or the meter reading and, when the threshold is reached, the asset appears on a PM-due dashboard and a work order can be generated automatically — pre-filled with the asset, the checklist tasks and an assignee — and an alert pushed by email, SMS or WhatsApp. This is what turns a schedule from a wall planner someone must remember into work that raises itself on time.
How does a CMMS calculate MTTR and MTBF?
A CMMS computes MTTR and MTBF from the timestamps on breakdown tickets. Each breakdown records a time down and a time restored; the repair duration between them, averaged over the failures in a period, gives MTTR. The uptime between consecutive failures, averaged, gives MTBF. Availability is derived as MTBF divided by the sum of MTBF and MTTR. Because these come from data captured as work happens — not entered by hand — the dashboards stay current and can plot MTTR-over-time and MTBF-over-time per machine to show whether reliability is improving.
What data does a CMMS need to work?
A CMMS needs three foundations to start: a clean asset register (the machines you maintain, with specs, location and criticality), a spare-parts list linked to those assets (the spare bill of materials with reorder levels), and preventive schedules on the assets that warrant them. From there it captures transactional data as work happens — breakdown reports with downtime, work orders, spare issues, labour time. Most plants import an existing asset and spare list from Excel to begin, then keep it current as the single source of truth.
Does a CMMS work on a mobile phone at the machine?
Yes. A key part of how a modern CMMS works is scan-to-card: each asset carries a printed barcode or QR tag, and scanning it on a phone opens that asset's card and history right at the machine. A technician can see the spare bill of materials, log a breakdown, record a checklist reading or close a job without walking back to a terminal. This is what makes the record accurate — it is captured at the point of work, not written up later from memory.