Energía y Servicios PúblicosEstudio de caso anonimizado — identidad del cliente confidencial.
Energía y Servicios Públicos · Estudio de caso

Personas adecuadas, zona correcta, contabilizadas — con un botón de coacción que sabe dónde estás.

Un operador de energía o servicios públicos debe hacer cumplir las zonas de permiso de trabajo en subestaciones activas y proteger a los trabajadores solitarios en zonas remotas o peligrosas.

ESTUDIO DE CASOZonas con permiso de trabajoEnergía y Servicios Públicos · Estudio de casoUWBPosición en directo · UWB100%Zona de permiso de trabajoUbicaciónCoacción por trabajador solitarioLista para auditoríaContratista /
Resultados

Lo que el programa ofrecía.

100%

Cumplimiento de la zona de permiso de trabajo, registrado.

Ubicación

Trabajo solitario con la posición para responder.

Lista para auditoría

Responsabilidad del contratista / visitante en el lugar.

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.

El reto

La entrada no autorizada en zonas alrededor de equipos activos es un evento de seguridad; No se puede localizar a los trabajadores solitarios en sitios remotos rápidamente si algo sale mal.

Nuestro enfoque

  • Zonas de permiso de trabajo geocercadas con verificación de acceso.
  • Etiquetas de trabajador solitario con coacción y detección de hombre en caída.
  • Ubicación en tiempo real para la respuesta a emergencias.
  • Responsabilidad del contratista y del visitante en el lugar.
  • Integra con EHS, control de acceso y despacho.

Tecnología e integración

Pila desplegada: Zonas UWB / BLE, LoRaWAN para sitios de área amplia, wearables robustos.

Integración: EHS, control de acceso, despacho / SCADA.

Relacionado: Energía y servicios públicos RTLS · Seguridad en subestaciones · Lista de verificación de proveedores

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.

¿Mismo problema en tu planta?

Vamos a analizar los números reales de tu operación.

Treinta minutos en tu caso de uso, entorno y objetivos — neutral para el proveedor, sin margen de revendedor.

Reserva una llamada gratuita de 30 minutosVer la lista de verificación de selección de proveedoresDescargar la guía del comprador

Última actualización: