Fleet Management Software for Ports and Container Logistics
A terminal tractor might cover fifty kilometres in a day and never leave the fence, running three shifts against a crane that does not care what your maintenance calendar says. KO Fleetz manages equipment on that basis: hours not distance, shifts not journeys, and a workshop that has to fix things between vessels.
Operational reality
What makes ports & container logistics different
The quay sets the clock
A vessel has a berth window and the crane works to it. Every piece of horizontal transport underneath exists to keep boxes moving under that hook. A hostler down mid-exchange is not a maintenance ticket, it is a gang standing still.
The equipment never stops
Three shifts, seven days, and the machine accrues engine hours at a rate a road vehicle would need years to match. A service interval expressed in months means almost nothing when the unit runs twenty hours out of twenty-four.
The odometer is a joke
Hostlers, reach stackers and empty handlers work in loops of a few hundred metres. Distance is trivial and the duty is brutal: constant shunting, full lock turns, hydraulics under load, fifth wheel and lift gear working every single cycle.
Positioning inside a terminal is a different problem
Yard blocks are tens of metres apart and stacked containers are metal walls. Satellite fixes wander between rows and cannot tell you which slot a box went into. The terminal system knows that; the tracker never will.
A closed estate has closed logistics
Fuelling, washing, the workshop and the spares store are all inside the gate. There is no fuel card, no external garage, no roadside assistance. If a part is not on the shelf, the machine waits, and the vessel does not.
Outside the gate is a different business
Drayage hauliers arrive against a booking slot, queue, get turned, and leave. Their economics are gate turn time and how many round trips a truck can make in a day. Inside and outside the fence share a container and no other assumption.
Empties eat capacity
A box that has been stripped has to be repositioned somewhere, and the move earns nothing. It still consumes a driver, a machine, a slot and diesel, and it is the least examined line in most container operations.
A shift measured against a vessel
The berthing plan is the plan. Once the vessel is alongside, everything below the crane is a queue discipline problem: hostlers cycling between the quay and the stack, a straddle or a gantry taking the box off, and a target exchange rate the whole terminal is judged against. There is no route to optimise. There is a loop, repeated for hours, and the only variables that matter are how many machines are actually available and how long each cycle takes.
Between vessels is when the terminal fixes things, and that window is the scarcest resource on the estate. A workshop inside the fence has to plan its interventions around a berthing schedule set by shipping lines, which means the service that is due gets done when the quay is quiet or it does not get done at all. Equipment reporting its own hours and fault codes turns that window from a guess into a queue, because you can walk in already knowing which four units need a bay and which parts to have on the shelf.
Outside the gate the same container becomes a road haulier's problem and every assumption changes. The truck arrives against a booking, waits in a lane, gets processed, and leaves. Nothing about that day resembles the loop inside the fence: it is a small number of long-ish trips whose profitability turns almost entirely on how long the gate took. Fleets serving terminals need both views, and they need to stop pretending one set of measures describes them both.
Feature mapping
Which modules matter here, and why
Not every fleet needs every module. This is what actually earns its place in this industry.
Terminal equipment fails from cycles, not from kilometres. A hostler's fifth wheel and lift ram work every single move, a reach stacker's boom and spreader take a full load hundreds of times a shift, and all of it happens where an external garage cannot reach. Servicing has to run off the hour meter and slot into the gap between vessels, with the parts already on the shelf when the machine rolls in.
Utilisation in a terminal is a shift question, not a monthly one. The number that matters is how much of a gang's window each machine was available and cycling, and whether availability sagged on nights. Aggregate that to a month and it disappears; the terminal has already been judged on the exchange rate it managed while one specific vessel was alongside.
For the drayage side, the gate is the entire business. A truck's day is a small number of round trips, and the thing deciding whether it managed three or two is how long it sat in a queue outside somebody else's fence. Turn time has to be measured against the terminal, per visit, or the haulier is negotiating rates on a feeling.
Inside the fence, tracking is about zones and gates rather than maps: which area of the estate a unit is working, when it crossed onto the workshop apron, whether it has been parked at the far end of a stack since the back shift. Outside, the same technology times the queue, and that timestamp is what a haulier takes into a conversation about turn time.
A terminal fuels its own machines from its own tanks inside its own gate, so consumption never touches a card network and never appears on a statement anyone can audit. Litres per hour against work done is the only usable measure, and it is the one that spots a unit whose burn has quietly climbed while nobody was reconciling anything.
Outcomes
What changes
- Availability judged against the gang, not the month
- Per shift
- Intervals matched to how terminal plant wears
- Hours, not kilometres
- Workshop work planned into the berthing gap
- Between vessels
- Turn time recorded per visit on the drayage leg
- Gate to gate
What sits either side of a container fleet
The terminal operating system is the authority on the box, the yard slot, the vessel plan and the work instruction, and nothing here competes with it; KO Fleetz takes the machine's side of that story and hands back hours, availability and faults. Equipment manufacturers publish engine hours, load cycles and diagnostics from hostlers, stackers and handlers. Gate and vehicle booking systems supply the appointment a drayage truck is running to. Weighbridges provide mass at the gate. On-site fuel dispensing, workshop stores and parts suppliers feed the maintenance and consumption ledger.
Explore integrationsFrequently asked questions
No, and it should not try. The box belongs to your terminal operating system, which knows its number, its status, its yard position, its release and the vessel it is going on. That is a specialised discipline with decades of software behind it. KO Fleetz tracks the equipment that moves the box: the hostler, the stacker, the handler, the road tractor. The two meet where a machine's hours and availability affect whether the yard plan is achievable, and that is exactly where the integration belongs.
Block, sometimes. Slot, no. Rows of stacked steel reflect signal and the rows are only metres apart, so a satellite fix inside a stack will drift between them and you should not build a process on it. Use zones drawn at a scale the technology can actually deliver: quay apron, stack area, workshop, gate, reefer plugs. If you need slot-level truth, that comes from the terminal system's own positioning, which is engineered for it. Anyone selling container-slot accuracy from a plain GPS tracker is overselling.
Engine hours, and increasingly the work itself. A hostler running twenty hours a day accumulates duty at a rate no distance figure will ever reflect, and the components that fail are the ones tied to cycles: the lift ram, the fifth wheel, a transmission taking constant direction changes. Intervals are set against the hour meter, read from the machine's own telematics where available, and the platform forecasts the due date from the actual accrual rate so the workshop can claim a gap in the berthing schedule ahead of time.
The outside-the-gate half, and it is a genuinely different product to the inside-the-fence half. Your economics are round trips per truck per day, and the variable deciding them is turn time at a facility you do not control. Geofenced arrival and departure at the gate gives you a per-visit record of what each terminal actually cost you, which is the basis for both planning and a rate conversation. Empty repositioning, trip profitability and standard road maintenance all apply normally. Yard equipment management does not.
It measures your truck, not the box, and the difference is the whole answer. Demurrage and detention on a container are charged against free days by the line and the terminal, and that clock lives in your TOS or your forwarder's system. What KO Fleetz gives you is how long your vehicle and driver were held at a gate or a customer's yard, evidenced by timestamps neither party wrote down. Those are related pressures and they are not the same meter. Do not let a vendor blur them.
Absolutely not, and any suggestion otherwise should end the conversation. A TOS plans the vessel, allocates the yard, sequences the work and instructs the equipment. It is the operational core of the terminal and it is not a fleet system's job. KO Fleetz sits underneath it, holding the asset register, the hour meters, the service history, the workshop and the fuel, and answering the question the TOS assumes: whether the machine the plan just tasked is actually fit to run this shift.
Take one berthing schedule and one workshop backlog
We will line the hour meters up against the vessel gaps and show you which services were never going to fit.