What this looks like when it works
Every zone entry logged against the live permit.
Lone-worker duress with position for response.
Contractor / visitor accountability on site.
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.
The challenge
Unauthorised zone entry around live equipment is a safety event; lone workers in remote sites can’t be located quickly if something goes wrong.
Our approach
- Geofenced permit-to-work zones with access verification.
- Lone-worker tags with duress and man-down detection.
- Real-time location for emergency response.
- Contractor and visitor accountability on site.
- Integrate with EHS, access control and dispatch.
Technology & integration
Stack deployed: UWB / BLE zones, LoRaWAN for wide-area sites, ruggedised wearables.
Integration: EHS, access control, dispatch / SCADA.
Related: Energy & utilities RTLS · Substation safety · 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: Paper/PDF permits and verbal confirmation that a zone is clear.
- Method: Geofenced HV zones reading live permit state; lone-worker duress on the same identity graph; muster time measured to verified headcount.
- Period: Substation cluster pilot across planned outages, then network standard.
- Excluded: Door access logs that are not joined to permit validity.
Programme pattern for this vertical
Utilities and energy operators join locating to digital permit-to-work so presence in a bay or substation zone corroborates — or challenges — permit validity. Typical stack: BLE/UWB zone presence, rugged badges, integration to PTW and access control.
Start with high-risk substations or plant areas where paper permits already fail audits.
Outcomes to expect — and how they are earned
Expected outcomes: fewer permit mismatches, faster visitor/contractor accountability, cleaner audit trails for HSE. Accuracy needs are zone-level more often than survey-grade.
Lessons from comparable programmes
Lessons: if PTW is not the system of record, locating becomes theatre; train contractors; define offline permit behaviour.
Deeper problem framing
Paper or semi-digital permits diverge from who is actually in the bay. Contractors arrive on wrong permits; visitors badge through without task linkage. Incidents later show 'system said OK'.
Approach
Zone presence as corroboration not replacement of PTW; join identity to permit validity; offline behaviour defined; train contractors; start on highest-risk nodes.
Outcomes and measurement
Permit mismatch rate, time-to-detect invalid presence, audit retrieval time. Zone-level accuracy usually suffices.
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
Inventory permit types and failure modes first. Instrument 1–2 high-risk areas; corroborate presence to PTW validity; define offline rules. Train contractors with short modules and gate checks.
Acceptance tests: detect invalid presence within agreed minutes; retrieve audit packs for a simulated incident; prove low nuisance-alarm rates. Scale site-by-site with local champions.
Vendors selling presence without PTW API depth are selling badges — score them down.
Buyer checklist, vendor challenges and engagement shape
For permit-to-work joins, score vendors on PTW API depth and offline behaviour, not on map aesthetics.
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
Utilities and energy operators join locating to digital permit-to-work so presence in a bay or substation zone corroborates — or challenges — permit validity. Typical stack: BLE/UWB zone presence, rugged badges, integration to PTW and access control.
Start with high-risk substations or plant areas where paper permits already fail audits.
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
Inventory permit types and failure modes first. Instrument 1–2 high-risk areas; corroborate presence to PTW validity; define offline rules. Train contractors with short modules and gate checks.
Acceptance tests: detect invalid presence within agreed minutes; retrieve audit packs for a simulated incident; prove low nuisance-alarm rates. Scale site-by-site with local champions.
Vendors selling presence without PTW API depth are selling badges — score them down.
Buyer checklist, vendor challenges and engagement shape
For permit-to-work joins, score vendors on PTW API depth and offline behaviour, not on map aesthetics.
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:
Network safety and access
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
Permit and substation reality
People accountability and asset jobs scoped to live network rules.
OT-aware shortlists
Independence matters when OEMs push their own locating stack.
Design to the control room
Events for the operators who already own the alarm philosophy.
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.