industry
The service window is whenever it is not earning.
Depots, linehaul and last mile, a workshop competing with the run schedule, and a delivery that does not become an invoice until somebody finds the paperwork.
what is different here
The fleet has to run and be maintained at the same time.
-
A vehicle is either on a run or in the workshop
Servicing gets pushed back a week at a time because the trailer is loaded, until the deferral becomes a breakdown on the linehaul.
in Etaprise → service intervals planned against the run schedule
-
Rostered is not the same as able to drive
Hours, rest and licence class decide who can take the run. The roster is built in one place and those rules are checked in another.
in Etaprise → licence and availability checked at assignment
-
Proof of delivery lives away from the invoice
The signature is captured on one system and billing runs off another, so invoicing waits on somebody matching the two.
in Etaprise → the POD attached to the job that bills
On site
the setup
The modules that carry most of the weight here.
The other eleven are still there. Sector setup changes which forms attach to a job, which certifications gate an assignment, and what a closed job has to prove, not which software you are running.
what a rollout looks like
In order, and with honest timings.
Assets that only stop moving when they are not earning, drivers governed by hours rules, and a billing trigger that sits in the cab. The sequence puts the register and the workshop first, because scheduling maintenance against a run plan needs both to already be true.
-
weeks 1–3
Fleet and depot register
Prime movers, trailers, forklifts and depot plant with their service intervals, registrations and inspection dates, held against the depot that actually maintains them.
-
weeks 2–5
Workshop and defect jobs
Pre-trip defects, scheduled services and roadside call-outs raised as work orders against the vehicle, so a fault reported at 5am has somewhere to go before dispatch.
-
weeks 4–8
Drivers, carriers and delivery evidence
Licence classes and endorsements enforced at assignment, subcontracted carriers issued work the same way, and proof of delivery captured on the job that will be billed.
-
ongoing
Maintenance against the run plan
Once the register and the workshop are live, servicing can be scheduled into the gaps the run plan leaves, and the cost of deferring it becomes something you can see rather than argue about.
questions from this sector
The objections we hear, answered plainly.
Then those are the windows scheduling works with. Availability is a property of the vehicle, not an assumption about business hours, so a service can be placed in the hours the unit is back at the depot and idle rather than in the hours the workshop happens to be staffed.
It enforces the availability and qualification rules you configure, so a driver without the licence class or outside their available window is not offered the run. It is not a fatigue management system of record, and where you already run one, that stays the authority.
Subcontracted carriers are issued work orders and return the same evidence as your own crews. Live position and status depend on whether their drivers use the app; where they do not, you get the completion and the proof rather than the tracking.
Signature, photographs, timestamp and any exception noted at the door are held on the job itself, so the record that triggers billing and the record that proves the delivery are the same one. Where an ERP owns invoicing, that job carries the evidence across to it.
further reading
Further reading
Bring us a week of your runs.
Give us a depot roster and a service list, and we will schedule the workshop around the runs.
Book a demoother industries