maintenance-work-order-triage-5M
An ultra-lightweight model for maintenance work order triage
2 min read
The model reads short equipment maintenance requests and instantly outputs two parameters: urgency (ranging from immediate shutdown to routine monitoring) and the specialized department (mechanics, electricians, hydraulics, and others). Built on a compact google/bert_uncased_L-4_H-128_A-2 encoder with two classification heads, it weighs just 18.28 MB with 4.78M parameters. Unlike the larger maintenance-work-order-triage-13M version, this model runs 3.6 times faster—about 1.8 ms per request on a standard CPU without a GPU or cloud connection. It is useful for manufacturing plants and engineers looking to automate primary ticket sorting on low-end hardware or edge devices.
Key features
- High speed: Processes a single request on a CPU in 1.799 ms with no GPU required.
- Two tasks at once: Determines the priority (4 classes) and the required maintenance department (6 classes), returning calibrated confidence for each output.
- Two operating modes: A balanced mode and a safety mode that catches up to 84% of critical failures (
STOP_NOW). - Smart escalation: Sends ambiguous or incomplete requests for manual review (
ESCALATE) instead of guessing.
What you can do
- Pre-sorting in asset management systems: Integrate as a local assistant for SAP PM, Maximo, or another ticketing system so planners only need to confirm pre-tagged requests.
- Edge deployment: Run directly on a production terminal, mobile device, or low-power PC in a secure, air-gapped environment without internet access.
- Emergency filtering: Enable safety mode to quickly highlight critical failures that demand immediate response.
Example
No code snippet card is included—here is an example of the model operating in balanced mode:
Input: "Hyd hose burst on press 3, oil spraying across walkway"
Result: priority STOP_NOW (confidence 0.97), department HYDRAULIC_PNEUMATIC (confidence 0.97).
For the request "Gearbox oil level low, top up", the model outputs PLAN (0.93) and LUBRICATION (0.98).
Read more
DetailsTested on 1,500 real requests: macro-F1 for priority is 0.8265 (0.83), for department 0.8008 (0.80), and critical case recall is 64% in standard mode and 84% in safety mode.
Resources: 4.78M parameters, size 18.28 MB, latency 1.799 ms on CPU.
Limitations: English language only, short texts (mostly up to 8 words) describing a single malfunction; it does not replace human operators or industrial safety systems.
Training: Full fine-tuning on the MaintNorm and MaintIE datasets augmented with synthetic factory work orders.










Comments