Maintenance and asset management
The asset register and its work history: what you own, what has broken, and what was done about it.
01 What it holds
The data inside it
Assets and their hierarchy, planned maintenance schedules, work orders, failure codes, spare parts and the labour booked against each job.
Asset, Location, Work order, Work request, Failure code, Spare part, PM schedule, Meter reading
02 Getting the data out
Extraction, and the keys that decide whether it joins
Standard APIs and database access. The challenge is rarely extraction; it is that asset identity and failure coding vary by site and by the era in which each site was commissioned.
Asset identifiers rarely match the MES, the historian or the finance fixed asset register, and the same physical machine often exists three times under three schemes.
03 What goes wrong
The failures that look like success
Each of these produces a number that is plausible, reconciles to something, and is wrong. They are worth reading before the first extract, not after the first dispute.
Asset identity fragmented
The single largest barrier to any maintenance analysis: failure history does not accumulate against the machine that keeps failing.
Response, wait and repair collapsed into one duration
Most of MTTR is waiting for a part or a technician. A single elapsed figure sends the improvement effort to the wrong place.
Planned maintenance compliance overstated
Jobs closed in bulk at period end look like compliance and are not.
Spares consumption disconnected from stock
Parts used are recorded on the work order and issued from inventory in another system, so stocking policy is set without knowing real consumption.
04 Joins that matter
What this system is worth joining to
| Join to | What it lets you answer |
|---|---|
| MES | downtime events to the work orders that resolved them |
| ERP | spares consumption, labour cost and capital replacement decisions |
| Historian | condition data ahead of failure |
05 Metrics it feeds
The numbers that come out of it
06 Questions
Frequently asked
What is the fastest improvement in maintenance data?
Splitting MTTR into waiting and working. It almost always shows that the constraint is the spares policy or technician coverage rather than repair skill.
Repair or replace — what data answers it?
Cumulative maintenance cost and downtime contribution per resolved asset, against replacement cost. All three exist; the asset identity join is what makes the comparison possible.
Connect this system without replacing it
SCIKIQ reads it in place, resolves the entities inside it and governs what the fields mean.