Business management · Asset Maintenance (EAM)
Maintenance management on the same asset record you already use: asset hierarchy, criticality from a matrix, a service request opened by whoever saw the problem, a work order with tasks, technician hours and parts issued from inventory, preventive plans by time and by meter, inspection routes, maintenance contracts with SLAs and a technician app that works offline.
The problem and the fix
If any of these situations sounds familiar, it is because they happen in almost every graduation company, until the right system comes in.
Maintenance is remembered once the equipment has already failed, in the middle of the operation.
Preventive plan by date and by hour meter or odometer, with the due date counted per asset and the work order generated automatically inside the configured horizon.
The maintenance record is a single line, and nobody knows what was done or who did it.
A work order with staged tasks, checklists, hours logged per technician and parts consumed, each with its cost, building the asset's history.
The part used in maintenance disappears from inventory with no issue posted, and the balance never matches.
Work order material is reserved and issued through the same path as production, honoring the binned warehouse when it is active.
Nobody knows which equipment breaks down most, or how much each one costs to keep running.
MTBF, MTTR, availability, backlog, plan adherence and maintenance cost as a share of asset value, with failures classified by mode and cause.
The technician writes in a notebook because there is no signal in the shed.
Technician app with an offline queue: checklists, photos, hours, materials and meter readings stay on the device and upload when the connection returns.
In practice
Everyday situations at graduation companies, from the problem to the result, using the modules on this page.
The generator needs servicing every 250 hours, and nobody tracks the hour meter.
The reading is entered in the app during the routine inspection. Once the trigger is crossed, the preventive work order is created with the plan's tasks and the material required.
The service happens before the failure, and the same reading feeds units-of-production depreciation.
The album printer fails for the third time this half-year.
Each breakdown became a corrective work order with failure mode and cause. The metrics show MTBF falling and accumulated cost going past what is reasonable.
The decision to replace the equipment is made with numbers behind it, and the breakdown is recorded as work center downtime in production planning.
The supplier promises to respond in 4 hours and resolve in 24, but nobody measures it.
The contract carries the deadlines, and they are frozen into the work order at the moment it is linked. Response and resolution are time-stamped by the operation itself.
The contract renewal is discussed against the compliance history, not against the memory of the last argument.
How it works
Every step is a real module, and what comes out of one goes into the next without anyone typing it again.
Module by module
8 modules and 40 features on this page, all running on the same class, graduate and event records.
The equipment and its parts, on the asset record that already exists.
Whoever saw the problem opens it, whoever plans decides.
The maintenance job with stages, people, parts and cost.
What to do, when and on which asset.
The round that finds the problem before the breakdown.
The supplier measured against what they signed.
The numbers that decide between repairing again and replacing.
Maintenance happens far from the desk.
Compare the modules and choose the setup that fits your operation.