Preventive schedules per equipment
By running hours or by date
Powered by STOS, the Smart Terminal Operating System
Keep the equipment that moves the boxes available
A reach stacker out of service stalls the yard, and the cost lands on operations rather than on the workshop. Maintenance plans the work that prevents that, records the work that could not be prevented, and shows what downtime is actually costing per machine.
How the module runs
● 5 stages
Schedule
01Job card
02Work done
03Spares booked
04Closed
05
Why it exists
Downtime is an operations problem, not a workshop one
Handling equipment is usually maintained reactively and recorded on paper, which means nobody can answer two questions that matter: which machine is costing the most, and whether a machine should be repaired again or replaced. Maintenance answers both by keeping the schedule, the job and the parts against the asset for its whole life.
What Maintenance covers
Breakdown job cards raised from the yard and tracked to completion
Spare-part consumption booked against the job and the machine
Equipment downtime reporting
By unit and by cause
Service history retained for the life of each asset
Cost per machine
So repair or replace is an informed decision
Planned work
Work that stops a breakdown
Preventive maintenance is scheduled against the asset and raised automatically when it falls due.
PM schedules
Schedules per equipment on running hours or on a calendar, whichever suits the asset.
Due and overdue
What is due now and what has been allowed to slip, so planned work is not quietly skipped.
Checklists
The task list that goes with each schedule, so the same service means the same work every time.
Unplanned work
What the yard reports
A breakdown is raised where it happens and tracked through to a closed job, not phoned through and forgotten.
Job cards
Raised against the machine with the fault reported, the work carried out and who did it.
Spare parts
Parts consumed booked against the job and the machine, so the cost sits with the asset.
Downtime
Time out of service captured against the job, with a cause, so patterns are visible.
Asset view
The whole life of each machine
Every job, part and hour of downtime accumulates against the asset, which is what makes the replace decision possible.
Service history
Every job on the machine, in order, retained for the life of the asset.
Downtime reporting
By unit and by cause, so the worst machine and the most common failure are both visible.
Cost per machine
Labour and parts totalled per asset, against its availability.
Roles
Who sees what
Access is granted per module and per role, so two people signed into the same platform see different work.
| Role | What the role works with |
|---|---|
| Yard operator | Reporting a fault against the machine that has it |
| Workshop technician | Job cards, work carried out, parts consumed |
| Workshop supervisor | Schedules, assignment, overdue planned work |
| Engineering manager | Downtime by cause, cost per machine, replace or repair |
| Administrator | Asset register, schedule templates, role access |
How it fits
The machine in Maintenance is the machine in the yard
Maintenance runs on the same identity service and the same equipment register as STOS core, so the reach stacker a job card is raised against is the reach stacker operations assigned to a move.
- Single sign-on with STOS core and every other module
- One equipment register shared with yard operations
- Spare parts purchased through the Procurement module
- Roles granted per module, so access is specific rather than blanket
FAQ
Questions buyers actually ask
Yes. A schedule is set against the asset on either basis, because a crane that works two shifts and one that works occasionally should not be serviced on the same calendar.
Parts consumption is booked against the job and the machine in Maintenance, and the replenishment is raised through the Procurement module, so the same part has one cost and one approval trail.
It reports downtime by unit and by cause and totals labour and parts per machine. That is what makes a repair-or-replace case arguable rather than anecdotal.
Yes, like every add-on module. Terminals usually add it once the equipment fleet is large enough that reactive maintenance stops being affordable.
Ask for a walkthrough and we will show the module and map it against your own equipment list.
See Maintenance on your own terminal data
Bring your own customers, tariffs and volumes and we will walk the module end to end on a live system.