What this looks like when it works
Unplanned downtime.
Maintenance from condition data.
Lone-worker monitoring in the field.
Composite worked example — figures are ranges from comparable programmes, not attributed named-client results. Named references available under NDA. We model your own numbers when you engage. KPI figures are typical ranges across comparable deployments; your own numbers depend on use case, environment and execution.
The challenge
Remote, hard-to-reach assets mean costly field visits, reactive maintenance, and limited ability to locate or protect lone workers.
Our approach
- LoRaWAN for long-range, low-power asset and condition sensing.
- GPS tracking for mobile assets and field crews.
- Active RFID for higher-value asset visibility on site.
- Condition-based and predictive-maintenance triggers.
- Lone-worker safety and remote operational dashboards.
Technology & integration
Stack deployed: LoRaWAN sensors, GPS trackers and active RFID, with intrinsically-safe (ATEX/IECEx) hardware where required.
Integration: EAM / CMMS (e.g. IBM Maximo), SCADA-adjacent reporting, and HSE systems.
Outcome: “Long-range sensing improved safety and remote operational awareness.”
Related: Oil & gas RTLS · Industrial IoT · Vendor checklist
Baseline, method, period — and what we excluded.
These pages are composite worked examples, not named-client scorecards. Figures are ranges from comparable RTLS/RFID programmes and published industry sources where noted.
- Baseline: Remote workers checked by voice schedule; asset visits poorly evidenced.
- Method: Lone-worker check-in/duress; geofenced sites; visit evidence for critical assets.
- Period: Field cluster across rotation cycles.
- Excluded: Office RTLS accuracy claims.
Programme pattern for this vertical
Upstream and midstream sites combine hazardous-area people tags, lone-worker timers, and vehicle or tool custody across sprawling pads. Architecture is usually hybrid: Ex-certified wearables, sparse outdoor locating, and satellite/LTE backhaul for remote assets.
Permit-to-work and SIMOPS interfaces prevent 'green badge' presence from overriding a cold permit.
Outcomes to expect — and how they are earned
Programmes earn value through faster muster, reduced lone-worker uncertainty, and fewer truck rolls for 'where is that asset' hunts. Cyber and Ex constraints dominate design more than centimetre accuracy.
Lessons from comparable programmes
Lessons: certify the actual SKU; design for Zone maps you have, not marketing Zone 2 everywhere; tabletop spoofed-location scenarios with OT security.
Deeper problem framing
Pads and pipelines combine lone-worker risk, contractor churn, Ex constraints and poor connectivity. Asset hunts drive expensive truck rolls. Office RTLS playbooks do not translate.
Approach
Hybrid Ex wearables, sparse outdoor locating, permit joins, offline-capable check-in; certify SKUs; design for uncertain location bands; OT security on day one.
Outcomes and measurement
Faster muster, fewer lone-worker escalations without resolution, fewer search truck rolls. Measure battery logistics and permit mismatch rates.
Governance, risk and what we refuse to claim
These pages remain composite worked examples — not named-client results. We will not attribute percentages to a confidential site. When you engage, we rebuild baselines from your incidents, labour samples and system logs.
We refuse vanity accuracy claims without a coverage map, and we refuse programmes that silently add productivity surveillance onto a safety business case without a fresh DPIA or labour consultation.
Implementation sequence and change management
Start with a plot-plan Ex zone map and connectivity reality check. Shortlist dual-certified people tags; place infrastructure in safer zones. Join permit-to-work early so presence cannot greenwash a cold permit.
Pilot on one pad cluster; measure truck rolls avoided and lone-worker resolution time. Expand with OT segmentation and recorded vendor access. Tabletop a spoofed-location evacuation scenario with the CISO.
Challenge 'office RTLS' resellers entering upstream accounts without Ex schedules or NEC/ATEX mapping experience.
Buyer checklist, vendor challenges and engagement shape
For remote oil and gas, require Ex certificate schedules and permit-system interface tests before paying for a field-wide rollout.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Programme pattern for this vertical
Upstream and midstream sites combine hazardous-area people tags, lone-worker timers, and vehicle or tool custody across sprawling pads. Architecture is usually hybrid: Ex-certified wearables, sparse outdoor locating, and satellite/LTE backhaul for remote assets.
Permit-to-work and SIMOPS interfaces prevent 'green badge' presence from overriding a cold permit.
Governance, risk and what we refuse to claim
These pages remain composite worked examples — not named-client results. We will not attribute percentages to a confidential site. When you engage, we rebuild baselines from your incidents, labour samples and system logs.
We refuse vanity accuracy claims without a coverage map, and we refuse programmes that silently add productivity surveillance onto a safety business case without a fresh DPIA or labour consultation.
Implementation sequence and change management
Start with a plot-plan Ex zone map and connectivity reality check. Shortlist dual-certified people tags; place infrastructure in safer zones. Join permit-to-work early so presence cannot greenwash a cold permit.
Pilot on one pad cluster; measure truck rolls avoided and lone-worker resolution time. Expand with OT segmentation and recorded vendor access. Tabletop a spoofed-location evacuation scenario with the CISO.
Challenge 'office RTLS' resellers entering upstream accounts without Ex schedules or NEC/ATEX mapping experience.
Buyer checklist, vendor challenges and engagement shape
For remote oil and gas, require Ex certificate schedules and permit-system interface tests before paying for a field-wide rollout.
Buyer checklist before you sign: (1) written system of record for events; (2) acceptance tests with 95th-percentile performance under real interference; (3) integration owner named in IT/OT; (4) privacy or labour consultation path if people are tagged; (5) cybersecurity zoning sketch; (6) five-year TCO including batteries, spares, recalibration and SLA escalations; (7) exit/export terms so you are not hostage to a cloud tenant; (8) a pilot that can fail without political punishment.
Vendor claims to challenge in this pattern: brochure accuracy without production load; 'compliance included' without artefacts; ROI that assumes perfect adoption in 30 days; references that cannot be called under NDA; install partners who have never worked your vertical's overlays; shared support accounts; and any design that dumps locating onto a flat plant or clinical VLAN.
How TRACIO typically engages: stage-1 architecture and measurement design; vendor-neutral shortlist and RFP language; pilot acceptance criteria; then optional implementation oversight or programme rescue if a prior pilot stalled. We stay independent of hardware margin. Composite pages like this one exist so you can prepare the workshop — your numbers replace every planning band when we model payback.
Risk register themes that recur: mute fatigue on alerts; shadow spreadsheets reappearing beside the platform; battery logistics understaffed; master data too weak to support identity; works-council or IG review starting too late; and success declared on demo day before night-shift reality.
Document baseline windows explicitly: what you measured, for how long, which shifts, and what you excluded. Investment committees and auditors both punish fuzzy before/after stories. If your baseline is weak, spend two to four weeks fixing measurement before ordering anchors or portals. That discipline is cheaper than a stranded deployment and is the difference between a locating programme and a technology souvenir.
Last updated:
Hazardous-area accountability
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
Permit-to-work and people
Discovery starts with who must be accounted for and under which permit.
Neutral in a sales-heavy category
No reseller margin means the stack can change when the site demands it.
Integrate to OT carefully
IEC 62443-aware design into the systems HSE already audits.
Measurement
Baseline: lone-worker check-in gaps, permit-to-work exceptions, and time-to-muster. Pilot: one site or substation with RTLS/wearables tied to the EHS workflow. Steady-state: check-in compliance, muster time, and open permit exceptions. Safety claims stay within what the site’s EHS lead will sign.