industry
Out of signal is the normal case.
Remote sites, permit-to-work that cannot be improvised, and crews who will not see a network again until the shift ends.
what is different here
The connection drops. The job does not.
-
Crews leave before the job pack is final
Whatever is not on the device when they leave the yard is not available for the next twelve hours.
in Etaprise → the full pack synced before departure
-
Permits are managed on paper
A permit-to-work that lives in a folder cannot be checked against who is actually on site right now.
in Etaprise → permits attached to the work order
-
Nobody knows what happened until they return
Status is a phone call when someone reaches a high point. Planning tomorrow starts when the last van gets back.
in Etaprise → updates queue offline and sync on return
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.
Remote sites, permit-controlled work and crews out of contact for days. The sequence below assumes connectivity is the exception rather than something to design around later.
-
weeks 1–3
Offline job packs
Get work orders, site history and documentation onto devices that will lose signal. Prove the sync behaviour on a real trip before anything else is rolled out.
-
weeks 2–5
Permits and isolation
Build permit-to-work, isolation and confined space forms with the checks that must block completion. On this work the blocking behaviour is the feature.
-
weeks 4–8
Competency enforcement
Certifications and site inductions loaded and enforced at assignment, so a crew is never dispatched to work they are not ticketed for at that facility.
-
ongoing
Assets, scheduling and cost
Well site and facility equipment history, then scheduling that reasons about multi-day trips and travel windows rather than same-day rounds.
On site
questions from this sector
The objections we hear, answered plainly.
That is the design assumption. Everything needed is on the device, work is completed offline, and it syncs on return. What you do not get is live status while they are out: no product can give you that without a satellite link.
Permits are forms with hard blocking conditions and named approvers, held against the job and the asset. It enforces the process you define; it does not supply a permit regime.
Yes. Scheduling handles work measured in trips, with travel and accommodation windows treated as part of the job rather than overhead the plan ignores.
Yes, where you manage their qualifications in the system. If you do not hold their tickets, the system cannot enforce them, and it will show that gap rather than assume compliance.
further reading
Further reading
Bring us a week of your jobs.
Give us a rota and a site list and we will show it running offline.
Book a demoother industries