What’s inside: routing · step-by-step flow
The question this file answersWhen a machine stops at night, how does my maintenance lead find that message among the leaking-tap requests?
Fits: plants where daily reporting and plant admin are rebuilt by hand.
Typical pattern, not a measured desk; the manufacturing playbook covers production reporting, not maintenance requests; no request volume exists. A leaking pump, a planned service and a breakdown arrive in one WhatsApp group or shared inbox; whoever reads it decides the order. It hurts at night, when nobody is reading.
At the shift handover the maintenance lead sees the night's breakdowns at the top with history attached, the repairs queued in one list and the planned jobs already on the calendar, instead of scrolling a chat thread. Safety calls and the call to the OEM are still made by a person.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same sorting build as supplier follow-up — no published figure for maintenance requests
Before: a leaking pump, a planned service and a true breakdown share one WhatsApp group. After: planned work comes off the calendar, repairs queue, breakdowns reach a person with asset history. No percentage — the reporting figure lives on its own file.
Gartner Manufacturing Analytics (2023) measures production reporting; maintenance request handling is a different desk, so its 60–70% stays on the reporting file and this one carries no percentage. Not an OEE or uptime claim.
Your maintenance module or CMMS stays — SAP, Infor, Dynamics or whatever holds your asset list. This is the same sorting-and-routing build as our supplier follow-up file, turned towards maintenance requests:
The genuine breakdown. Safety. Spares that do not exist. The call to the OEM.
Not an OEE or uptime claim.
A breakdown written casually — 'line 3 is being weird' — can be classified as a repair; the classifier is set to over-escalate, so the on-call person will see some false alarms at first. If asset history lives in paper logbooks rather than a system, there is nothing to attach; that register is audit work first.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Manufacturing.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.