Olhos em ativos remotos — e nas pessoas próximas a eles.

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.

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.

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.

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.