Maintenance tracking software plans the upkeep of a business’s own machines, facilities and equipment; breakdown tracking software follows a failure on that equipment from the moment it is reported until it is closed. In practice they are two sides of the same system, known as a CMMS (computerised maintenance management system). The goal fits in one sentence: reduce breakdowns through predictable maintenance instead of rushing after them, and make the cost of every stoppage visible. Factories, hotels, hospitals, shopping centres, schools or a multi-branch retail chain — anywhere that operates its own equipment has the same need.
How is maintenance software different from field service software?
Both open work orders, assign technicians and consume parts, which is why they get confused. The difference is who owns the equipment. Field service management software is the system of a company that services customer-owned equipment on site: the call comes from a customer, the job is invoiced, and travel time and appointment windows matter. Maintenance and breakdown software is for a business’s own assets: the request comes from inside, the job is not invoiced but booked as a cost, and the real measure is not appointment compliance but how long the equipment was not running. A customer support ticket queue is another topic again, covered in our helpdesk system post.
Field service software manages revenue; maintenance software manages downtime. Success in the first is the number of completed visits; in the second, it is the time that passes without a breakdown.
Everything starts with the asset record
The core record in a maintenance system is not the work order but the asset. Every work order is linked to an asset, and every asset to a location. The location hierarchy must be set up from the start: site, building, floor, line or room, asset. In a hotel, "the air conditioner in room 304 on the 3rd floor"; in a factory, "press number 2 on line B". Without this hierarchy, reports are grouped as "air conditioner faults" and you cannot see which building or which brand causes problems.
- Identity: asset code, brand, model, serial number, installation date, warranty end.
- Location: a single place in the site-building-floor-line hierarchy; when moved, it moves with its history.
- Criticality: how much its downtime affects production or customers (high, medium, low).
- Maintenance plan: which task is done at which interval, and whether it is calendar-based or meter-based (running hours, cycle count).
- Documents: manual, diagram, maintenance instructions, accessible to the technician from a phone on site.
Preventive maintenance: calendar or meter?
Preventive maintenance has two triggers. Calendar-based maintenance happens at fixed intervals: fire extinguisher checks, generator tests, air conditioner filter cleaning. Meter-based maintenance depends on usage: a compressor is serviced at a set number of running hours, a press at a set number of cycles. A system that only uses the calendar over-services lightly used machines and is late for heavily used ones. If meter readings are entered by hand, the plan becomes unreliable within a few months; where possible, readings should come automatically from the machine’s control system or a meter. For the link with the production line, see our post on production tracking software (MRP).
type Plan = {
assetId: string;
task: string;
everyDays?: number;
everyHours?: number;
lastDoneAt: Date;
lastDoneHours: number;
};
type Asset = { id: string; runningHours: number };
export function isDue(plan: Plan, asset: Asset, today: Date): boolean {
if (plan.everyDays !== undefined) {
const next = new Date(plan.lastDoneAt);
next.setDate(next.getDate() + plan.everyDays);
if (today >= next) return true;
}
if (plan.everyHours !== undefined) {
if (asset.runningHours - plan.lastDoneHours >= plan.everyHours) return true;
}
return false;
}One detail is critical: the next service is calculated from the date and meter reading when the work was actually done, not from the planned date. Otherwise a service done two weeks late makes the next one arrive two weeks early, or lets delays accumulate.
Breakdown reporting and the work order flow
The most used screen in breakdown tracking software belongs not to the technician but to the person who notices the fault. The more effort reporting takes, the more faults are passed on by phone, verbally and off the record. The most practical solution is a QR code stuck on the equipment: scanning it fills in the asset and location automatically, and the reporter only adds a photo and a short description. The breakdown lifecycle should also follow fixed steps:
- Report: who, which asset, when, photo; this record marks the moment downtime started.
- Prioritisation: by the asset’s criticality and impact; not every breakdown is urgent.
- Assignment: a technician by skill, or an external contractor; contractor jobs are tracked in the same record.
- Intervention: work done, parts used, time spent, root cause code.
- Closure: the moment the asset runs again is recorded; downtime is the time between these two timestamps.
The root cause code is the most skipped field and the most valuable one. A closure that says "fixed" does not prevent the next breakdown; a code chosen from a list, such as "bearing wear", "operator error" or "power fluctuation", shows six months later which fault keeps recurring and why.
Spare parts and the stock link
In most businesses the maintenance store is separate from the main warehouse and unrecorded, so a critical part is either missing when the breakdown happens or there are three of them. Parts should be deducted from stock the moment they are booked to a work order, and each part should know which assets it is used on. That makes it possible to set minimum stock levels for critical equipment. We cover general stock logic in stock tracking software or custom software.
What to measure: downtime, MTBF, MTTR
The number of completed work orders does not show how well the maintenance team performs. Three measures are enough: total downtime (how long the equipment did not run), MTBF (mean time between failures, higher is better) and MTTR (mean time to repair, lower is better). The preventive maintenance ratio can be added: planned jobs as a share of all jobs. All of these are calculated from the two timestamps and the root cause code above; without recording discipline, none of them can be calculated. For dashboards, see our post on business intelligence and reporting dashboards.
Off-the-shelf or custom software?
For a single-site business with standard equipment, an off-the-shelf maintenance package is often enough. Custom software usually comes to the fore in the following situations; if at least two apply, consider it seriously:
- There are multiple sites or branches, and parts, technicians and reporting are managed centrally.
- Meter data is to be collected automatically from machines or sensors.
- Maintenance costs need to flow into the ERP or accounting by asset and cost centre.
- The approval flow is company-specific: contractor work or parts purchases above a certain amount require approval.
The fourth question is always data export: asset history becomes the business’s most valuable maintenance knowledge over the years and must be portable when the system changes. For the decision framework see custom software or an off-the-shelf solution, and for the relationship with ERP see what is ERP.
Conclusion
The value of maintenance and breakdown tracking software lies not in the number of screens but in recording discipline: asset records are built on a location hierarchy, maintenance is planned by calendar and meter, breakdowns are reported in seconds with a QR code, and every closure carries a root cause code. Once these four rules are in place, downtime becomes measurable, and what is measured can be reduced. If you are planning a maintenance system for your facilities, see our corporate solutions page or get a quote.