ReplacesMRI EvolutionJoblogicElogs
Work Orders
vs the CAFM work-order log
The core work-order record — reactive and planned in one audited stream, each job on a per-order SLA clock measured on a UK-holiday-aware calendar, assigned only to engineers whose certifications are valid. Every state change is written to a tamper-evident hash chain.
Why it wins
- Per-work-order SLA clock (Europe/London, bank-holiday aware) — not one global timer
- Cert-aware assignment: an out-of-date certification blocks the job automatically
- Reactive and planned maintenance in one tenant-scoped, audited record
- Every state change hash-chained into a 7-year immutable audit trail
How it compares
Measured on publicly available data against the named market leader(s) it replaces. Every row links its source.
| IMAISA | The market leader | |
|---|---|---|
| SLA measurement | A per-work-order clock on a UK bank-holiday-aware calendar | SLA tracking against contract terms; a per-order holiday-aware clock is not advertisedsource for the SLA measurement comparison |
| Assignment safety | An expired certification blocks the assignment automatically | Certificates recorded on the record; not used to gate the assignmentsource for the Assignment safety comparison |
| Audit trail | Tamper-evident hash chain, 7-year immutable | Job history and logbook; no tamper-evident audit claim publishedsource for the Audit trail comparison |
Per-WOSLA clock, holiday-aware
Cert-gatedassignment
7 yrimmutable audit
RLStenant-isolated
Engineered across 4 architecture decision records (0053, 0054, 0079, 0211) — a deliberately-built module, not a checkbox.