Line 04
Maintenance optimisation for bulk terminals — Headway Terminal
Treats the terminal as the series line it is: critical equipment ranked by throughput impact, with the intervention window matched to the vessel line-up and train arrivals.
Context
A bulk terminal is a series line: car dumper or hopper, conveyor, stockyard, reclaimer, ship loader. When one link stops, the terminal stops — and the cost is not the repair, it is the vessel waiting at anchorage and the train held at the gate.
So the decision is not settled by the criticality of each machine in isolation. It is settled by the question that joins the three ends: given the line-up of the coming days and the schedule of inbound trains, in which window does each intervention cost the least throughput.
It is the same decision architecture used on track, carried through to the ship’s hold. And it is where the railway stops being an adjacent subject: the terminal’s stockyard buffer is what absorbs — or fails to absorb — the variability of the traffic arriving.
What you get
What you get
Throughput-impact ranking
Equipment ordered by unavailability risk combined with the effect of a stoppage on the whole loading line — not by the criticality of the machine alone.
Window matched to the line-up
Intervention plan allocated to the gap between vessels and train batches, with the cost of each hour of downtime explicit in tonnes not loaded.
Forecast per loading line
Unavailability forecast per link in the series — dumper, conveyor, reclaimer, ship loader — from SCADA, historian and stoppage history.
Effect on the rail side
Translation of terminal downtime into train queue, yard occupancy and wagon cycle — the calculation terminal and railway usually make separately.
Explainability and audit trail
Rationale per recommendation, model version, input data and the decision recorded by the client, retrievable at any time.
When this applies
Situations in which this line of work is the right starting point.
- Unplanned equipment downtime has already cost a vessel in waiting or a train held at the gate.
- Terminal maintenance is scheduled by calendar, without looking at the line-up of the coming weeks.
- The terminal has SCADA and a historian, but intervention decisions are still made in meetings.
- Terminal and railway hold different readings of the same queue.
FAQ
Frequently asked questions
Does it cover container terminals?
No. The scope is solid bulk — iron ore, grain, fertilisers and similar. Containers run on a different systems stack with equipment telemetry closed inside the OEM. Liquid and chemical terminals are also out of scope.
Does it include berth allocation?
Not as a starting point. The scope runs from the rail signal to the stockyard buffer. Full berth allocation depends on third-party data — line-up, pilotage, port authority — outside the buyer’s control, and does not enter without an explicit decision.
Do we need the railway instrumented first?
No. The work runs standalone at the terminal. Where the feeding network is also instrumented the gain is larger, because the train queue stops being an assumption and becomes data.
Related services
Track maintenance optimisation
Ranks inspection, tamping, grinding and component renewal by risk and operational criticality, within the budget and the windows the operation actually has.
See service 03Rolling stock optimisation
Treats the fleet as a system: prioritises critical components, sequences the workshop by effect on availability and sizes the spare parts stock that sustains the plan.
See serviceNext step
How much of your maintenance budget is well allocated?
The conversation starts with the problem, not the platform: which decision is made today without enough data, and what the order of magnitude would be if it improved. Thirty minutes, no corporate deck.