Lease boundaries with expiry
Versioned, offline, scoped by role.
Industries · Resource · Whitepaper
The wellsite is the far edge.
Exploration and production crews operate at the end of the road, on leases whose boundaries are legal instruments, in an environment where the credible emergencies are chemical, mechanical and remote-medical rather than recreational.
01 / Problem statement
What actually goes wrong.
Three properties distinguish upstream field work from every recreational use case.
Lease geometry governs everything. Surface rights, subsurface rights, access agreements and seismic permits are separate polygons with separate expiry dates. A crew on the wrong side of one is a legal exposure, and the boundary is often not in any public dataset.
The hazards are not terrain. H₂S release, wellhead pressure, road-train traffic on a lease road and a chemical exposure requiring a sealed vehicle are the credible incidents. None of them are addressed by an avalanche layer.
Medical distance is measured in hours. A remote wellsite is a helicopter from definitive care. The relevant question is not whether there is a hospital but whether there is one with the specific capability, and whether the weather permits the flight.
02 / Mechanism
How NavTrax addresses each one.
Each entry names the mechanism rather than the benefit, so it can be evaluated rather than believed.
- Lease and permit layers
- Published as organization layers with expiry as an attribute, so an access agreement that lapses next week is visible on the map this week.
- Seismic line networks
- Cut lines as a routeable network, which is how crews actually move across a lease, and which no public router carries.
- Sealed-vehicle protocol
- A chemical or gas detection triggers a documented sequence — close vents, seal cabin, alert, sealed-air timer, threat-radius overlay — with the radius drawn on the map.
- Capability-matched medical routing
- The medical layer distinguishes facilities by capability. The contingency plan for a crush injury names a different facility than the one for a chemical burn.
- Multi-channel lone-worker escalation
- Check-ins escalate over mesh and satellite, with an audit record, because a lease road has no cellular and a missed check-in is a regulatory event.
- Air-gapped option
- For operators whose security policy forbids a cloud dependency, the same platform runs with no external connectivity and syncs by signed bundle.
03 / Capabilities
In the field, this is what you have.
Seismic line routing
The network crews actually use, as a routeable graph.
Gas and chemical response
Sealed-vehicle sequence with a threat-radius overlay drawn from the detection.
Capability-matched MEDEVAC
Facility capability, flight weather and the window, in the contingency plan before the incident.
Fleet and crew telemetry
Vehicle fault codes, tire pressure and fuel range alongside crew position and vitals.
Regulatory audit trail
Every check-in, position and alert attempt recorded and exportable.
04 / Reference
| Incident | Signal | Mechanism | Audit |
|---|---|---|---|
| Gas release | Detector or manual | Sealed-vehicle protocol, threat radius | Yes |
| Crush injury | Manual SOS | Capability-matched MEDEVAC, on-device triage | Yes |
| Vehicle breakdown | OBD-II fault | Crew alert over mesh, recovery routing | Yes |
| Missed check-in | Schedule elapsed | Escalation: group, mesh, satellite | Yes |
| Lease boundary crossing | Geofence | Immediate alert, position logged | Yes |
| Weather closure | Forecast threshold | Shift advisory to every crew device | Yes |
05 / Process
Traced, node by node.
Hours from care. Minutes to escalate.
Industry modules are Elite. Air-gapped deployment and audit logging are Enterprise.