A deployment scenario, not a named customer. This describes how these rollouts run in practice and what to measure, drawn from how the software is built and how these operations work. It does not report one organisation's results. For customer references, ask our team — we will introduce you to someone running it.
The situation
The operator runs a process plant with approximately multiple production assets. Maintenance was multiple technicians working from paper job cards, with the schedule held largely in the head of the maintenance lead.
This works until it does not. It depends on continuity of people, it produces no history, and it cannot answer the question a plant manager actually asks: is this machine getting worse?
What was actually going wrong
- No asset register. The list of machines existed in several places and agreed in none.
- Preventive work slipped silently. A monthly job missed in a busy week was not missed by anything that would notice.
- Meter readings were inconsistent, so usage-based schedules could not be trusted.
- Spares consumption was untracked against the machine that consumed them.
- No failure history, so repeat failures looked like bad luck rather than a pattern.
What changed
The operator deployed BeyondBoxAI Asset and Plant Maintenance over multiple weeks.
- An asset register built first, each machine tagged with a QR code fixed to it.
- Work orders raised, assigned and closed in the system, with parts and hours recorded against the asset.
- Preventive schedules by calendar and by meter, with "unknown" treated differently from "not due" — a schedule whose meter has not been read is flagged rather than assumed compliant.
- Mobile capture at the machine, so the record is made where the work happens.
The register came first deliberately. Scheduling against an asset list nobody trusts produces confident nonsense.
What to measure
| Measure | Why it matters | Where the figure comes from |
|---|---|---|
| Preventive jobs completed on time | The number that tells you whether the rollout worked | Work order history |
| Unplanned stoppages per month | The number that tells you whether the rollout worked | Production log |
| Mean time to repair | The number that tells you whether the rollout worked | Work order timestamps |
| Assets with a complete service history | The number that tells you whether the rollout worked | Asset register |
See the product, or read what a CMMS is.
BLOG · 3 MIN READ
BLOG · 4 MIN READ