industry
The site is a moving stretch of road.
Crews and plant travelling along a corridor, closures booked weeks in advance, hold points that stop the work, and variations that only get paid if somebody evidenced them.
what is different here
There is no customer site. There is chainage.
-
The asset is a corridor, not an address
Work happens between two chainages that move week by week. Systems built around a customer premises have nowhere sensible to put it.
in Etaprise → work located along the corridor, section by section
-
A variation without evidence is unbilled work
Day works get agreed at the face and written up days later, by which point the photographs, the dockets and the hours have to be reconstructed.
in Etaprise → the variation captured and priced where it happened
-
Plant servicing has to fit around closures
The machine is needed while the lane is shut and free only when it is open, and the traffic management booking was made a fortnight ago.
in Etaprise → servicing planned against the closure calendar
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.
A job that is a line on a map, quality records that gate progress, and commercial exposure that builds up in day works. The sequence establishes where work sits before it tries to prove what was done there.
-
weeks 1–3
The corridor and its lots
Set up the job as sections and lots along a chainage rather than as a site address, so a crew, a form and a photograph can all point at the same piece of road.
-
weeks 2–5
ITPs and hold points
Inspection and test plans built as forms with the hold and witness points that must block progress. On this work the blocking behaviour is the point, not an inconvenience.
-
weeks 4–8
Day works and variations
Labour, plant hours and materials captured against a variation at the moment of instruction, with the photographs and the signature attached, so the claim is assembled rather than rebuilt.
-
ongoing
Plant, closures and re-planning
Plant servicing scheduled against booked closures, and a wet week re-planned in one pass so you can see what moved, what the traffic management booking cost and what still has to be caught up.
questions from this sector
The objections we hear, answered plainly.
Assets can be sections of a corridor rather than customer premises, so a job, an inspection record and a defect all attach to the stretch of road they belong to. Crews still get a point to navigate to; the record does not pretend the job was at a building.
ITPs are built as forms against a lot, with hold and witness points that stop completion until the named party has signed. It enforces the plan you define; it does not supply a specification or decide what your client will accept.
The schedule is rebuilt in one pass and shows which activities moved and by how long. It cannot recover a booked lane closure that lapsed, but it makes the consequence of the weather visible on the day rather than at the end of the month.
Closures are held as fixed windows the schedule has to work inside, so crews and plant are planned around them rather than the other way round. Booking the closure with the road authority stays where it is today.
further reading
Further reading
Bring us a week of your corridor.
Give us one ITP and one variation you had to argue for. We will run both.
Book a demoother industries