Seguridad de contratistas y trabajadores solitarios en 38 subestaciones.

Identidad del cliente reservada por confidencialidad. Las cifras reflejan resultados de despliegues RTLS/RFID comparables; sus propios números dependen del caso de uso, el entorno y la ejecución.

Lo que entregamos.

• Detección SOS por trabajador solitario y falta de hombre
• Zonas de exclusión de alta tensión geocercadas
• Contratista registrado in situ con conciliación de salidas

La pila detrás

TSO/DNO programmes focus on contractor control, inductive hazard zones, and emergency accountability across many small sites. Tags and processes must work for infrequent visitors, not only employees.

Central security operations need exception queues; local site leads need simple devices and clear SOPs.

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.

Design the multi-site operating model before RF: central SOC queue, local device kits, induction workflow, permit join. Pilot 3–5 representative substations (urban, rural, indoor GIS).

KPIs: visitor compliance, time-to-locate on drill, kit loss rate. Expand only when logistics works. Public/regulatory evidence packs should be reproducible, not screenshot-based.

Reject commercial office badge analogies in the RFP response scoring.

For multi-substation estates, evaluate device logistics and central exception queues as carefully as radio choice.

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.