Deployment blueprint
Where there is no continuous sewerage network, tankering is the network. A late tanker floods a basement; a half-full one burns fuel that the next call needed. We give dispatch live position and live tank level, so the assignment fits the vehicle that can actually complete it.
Built for this scale
The challenges
Demand is spiky, geography is unforgiving, and the regulator wants proof of where every load ended up.
Challenge
A planner working from a wall map produces allocations that look reasonable and quietly cost money: longer journeys, more fuel, one crew idle while another finishes late. On a religious holiday or during heavy rain, when the volume doubles, the method stops working at all.
Challenge
Controllers can see where a tanker was supposed to be. A breakdown, a long queue at the facility, or a driver taking a different route only becomes visible when the customer rings to ask why nobody has arrived.
Challenge
Proving to an environmental regulator that every load reached an authorised facility on time is hard enough with paper records. Preventing an in-transit discharge before it happens is impossible with them.
Challenge
With no digital channel, every request, chase, and payment goes through the call centre. It copes on an average Tuesday and jams on the day half the district needs a tanker at once.
How it would work
The workflow runs from the resident's request to the authorised discharge. A customer app takes the order, shows an ETA, keeps the history, and handles payment. Incoming orders become dispatch candidates, sequenced by proximity, tank capacity, current fill level, and which disposal site is approved for that load. That sequence is rebuilt continuously as breakdowns, queues, and new orders arrive. With level sensors and telematics on the fleet, a controller choosing between two vehicles knows what each one can still carry.
The architectural point
Routine tankering and emergency response are two modes of one platform, not two systems. Same crews, same in-cab devices, same dispatch desk, same picture on the wall; when a storm lands, what changes is the priority queue and how often you report. That is what lets the operation pivot into flood response over a weekend without standing up a parallel command structure. The alternative is asking people to learn a second system they will only ever open under maximum stress.
Platform capabilities
Resident ordering, capacity-aware dispatch, live monitoring, and discharge enforcement on one stack.
Where every tanker is, how much capacity it has left, which exceptions are open, and what the next best assignment would be — on one screen.
ExploreAssignment sequenced by proximity, tank capacity, current level, and authorised disposal point, re-planned every time the queue moves and not just once at shift start.
ExploreApproved facilities are geofenced; an off-route emptying attempt raises an exception with position and timestamps, leaving a clean trail for the regulator.
ExploreCustomers request a tanker the way they request a ride — address, time window, payment, history, live ETA, and recurring schedules.
Collection-volume trends, response times, and service history sit alongside the customer and billing record, not off in a separate reporting tool.
Routine queues hold, flood-response jobs take priority, and reporting switches to the cadence the authority needs while the event is still running.
Hardware in the field
In-cab terminals, telematics, and tank-level sensing on every vehicle in the fleet.
Driver authentication, dispatch, navigation, proof-of-discharge capture, and exception handling on a device that survives the cab.
ExplorePosition, engine hours, odometer, and driving behaviour streaming continuously — which is also what turns a service schedule into a real one.
ExploreTank fill level per vehicle, live, so dispatch can give the job to a vehicle that will actually finish it.
ExploreIntegrations
Wired into the places the work already touches: the customer channel, the finance system, and the regulator's reporting.
Balances, order history, and online payment reconcile with the existing back-office, so the app is another way in and not a second set of books.
Discharge events, facility evidence, and severe-weather operations data export in the form the regulator asks for.
Dispatcher and supervisor access follows the existing directory and organisational structure.
In emergency mode, live vehicle positions and job status can be shared with municipal and civil-defence partners without duplicate data entry.
FAQ
Short answers here — the detailed version is a conversation whenever you're ready.
Discuss your deployment
Sovereign-data-friendly. Enterprise multi-org architecture. Built to integrate with the devices, SIM providers, and back-office systems you already run.
