Maintenance intelligence · runs in the browser

The numbers hold up. The work orders prove it.

MIA reads the work order export from your CMMS, flags anything it can’t classify, and answers your questions in plain English — with the backing work orders attached. Nothing to install.

Book a demo See how it works

Works with any CMMS export · CSV / XLSX · no IT project

Asset

PACKLINE-A07

Downtime · 12 mo

139.4 HRS

Work orders · 12 mo

Weekly downtime hrs · trailing 12 wk

Recurrence — gearbox fault

21 WO

WO-24118Gearbox replaced6.5 HRS
WO-24102Guide rail jam1.2 HRS
WO-24095E-stop reset0.4 HRS

Evidence — 52 work orders attached

Source — workorders.csv · 1,204 rows · read in the browser

01 · The four questions

Your exec team asks the same four questions every month.

You know the plant better than anyone in that room. But turning last month’s work orders into numbers that hold up takes your weekend. MIA answers each question from your own export — and shows the work orders it counted.

Q-01

How much downtime did we have?

One number for the period, split by line and by asset — counted from the stoppage records in your export, not estimated.

Site downtime · last month142.7 HRS · 38 stoppagesEvidence — 38 work orders attached+ WO list

WO-24118PACKLINE-A07 — gearbox replaced6.5 HRS
WO-24107CONV-03 — belt tracking fault2.8 HRS
WO-24102PACKLINE-A07 — guide rail jam1.2 HRS
WO-24089CP-02 — vacuum pump seized9.0 HRS
WO-24076CONV-03 — motor overload trip3.4 HRS
…and 33 more stoppages · 119.8 HRS

Q-02

Why were we down?

Causes ranked by hours lost, in the words your technicians wrote on the work orders.

Top cause · last monthConveyor jams — 11 stoppages · 31.5 HRSEvidence — 11 work orders attached+ WO list

WO-24102Guide rail jam1.2 HRS
WO-24097Carton jam at infeed2.1 HRS
WO-24085Belt slip — product pileup4.6 HRS
WO-24071Jam — misfed film3.0 HRS
WO-24064Roller seized, line stalled5.8 HRS
…and 6 more jams · 14.8 HRS

Q-03

How many overtime hours, and why?

Overtime from the labor lines on your work orders, tied to the jobs that consumed it.

Overtime · last month212.5 HRS · 96.0 on emergency workEvidence — 27 work orders attached+ WO list

WO-24118Gearbox replaced — weekend call-in16.0 OT
WO-24089Vacuum pump seized — shift held over12.5 OT
WO-24113Compressor trip — Saturday9.0 OT
WO-24078Boiler feed pump — call-in8.5 OT
WO-24066Palletizer fault — held over7.0 OT
…and 22 more work orders · 159.5 OT HRS

Q-04

Why so many work orders on that one asset?

The history of the asset everyone is asking about — and whether it keeps failing the same way.

PACKLINE-A07 · 12 mo52 WO — 21 on the same gearbox faultEvidence — 52 work orders attached+ WO list

WO-24118Gearbox replaced6.5 HRS
WO-24110Gearbox noise reported0.5 HRS
WO-24102Guide rail jam1.2 HRS
WO-24095E-stop reset0.4 HRS
WO-24088Gearbox oil leak1.5 HRS
…and 47 more on this asset · 21 gearbox-related

Every figure arrives with the work orders behind it.

02 · How it works

Export in. Answer out. Evidence attached.

Upload your export

The work order file your CMMS already produces — CSV or Excel. No integration, no IT ticket, no software on your laptop. It runs in the browser.

MIA reads it — and flags what it can't

Statuses, work types, asset names, in your plant's own spelling. Anything it can't classify, it stops and asks you about instead of guessing.

Ask. Get the answer, with evidence.

A plain-English answer, and under every number, the exact work orders it was counted from. If someone challenges the figure, you open the list.

The full loop, including the messy parts →

03 · When the data is messy

When your data can’t support an answer, MIA says so.

Most reporting tools compute a number from whatever is in the column and leave you to defend it. MIA reads your export first and tells you what it will support: which questions it can answer, which it can’t yet, and exactly what would unlock the rest.

It quotes your plant’s own words back to you — the status nobody remembers inventing, the work type spelled three ways — with row counts, so every line is checkable against the file you sent. A number MIA can’t back never reaches the page.

Readiness check

workorders.csv

Downtime hours — supported
1,204 rows · hours recorded on 38 of 38 stoppages
Work type — 2 terms MIA can’t read
“EMERG.” · 168 rows / “CALL OUT” · 46 rows — tell MIA what they mean and they count
Overtime — not in this export
no labor-hours column — add it to the export and this unlocks

Nothing above reaches a report as a number

04 · Ways to work together

Three ways in. Same engine, same evidence.

Mode 01

Done-for-you analysis

Send the export; get back the analysis and a walkthrough of what it found — downtime, causes, overtime, the assets that deserve attention. You present it; the evidence is already attached.

Book a demo →

Mode 02

Self-serve

Upload your own export and ask your own questions, whenever the exec meeting is coming. Same engine, same evidence, your keyboard.

Book a demo →

Mode 03

Managed weekly reporting

A standing report from your latest export, ready before the meeting that needs it — every week, every figure carrying its work orders.

Book a demo →

What each way looks like in practice →

Book a demo

Bring one export. Leave with answers.

Thirty minutes, in the browser, on your own data — or ours, if yours isn’t handy. You’ll see what MIA can answer from your export and what it flags first.

Book a demo

Nothing to install · runs in the browser