Wat het programma heeft geleverd.
Naleving van de vergunning-tot-werkzone, geregistreerd.
Eenzame werknemer met positie om te reageren.
Verantwoordelijkheid van aannemer / bezoekers ter plaatse.
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.
De uitdaging
Ongeautoriseerde zonetoegang rond actief materieel is een veiligheidsincident; Eenzame werknemers op externe locaties kunnen niet snel worden gevonden als er iets misgaat.
Onze aanpak
- Geofenceed vergunning-tot-werk-zones met toegangsverificatie.
- Lone-worker tags met dwang en man-down detectie.
- Realtime locatie voor noodhulp.
- Verantwoordelijkheid van aannemers en bezoekers ter plaatse.
- Integreer met EHS, toegangscontrole en dispatch.
Technologie & integratie
Stack ingezet: UWB / BLE-zones, LoRaWAN voor locaties met grote gebieden, robuuste wearables.
Integratie: EHS, toegangscontrole, dispatch / SCADA.
Gerelateerd: Energie & nutsbedrijven RTLS · Veiligheid van onderstations · Leverancierschecklist
Programmapatroon voor deze 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, risico en wat we weigeren te claimen
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.
Implementatiesequentie en 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.
Koperschecklist, leveranciersuitdagingen en engagementvorm
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; leveranciersneutraal 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.
Laatst bijgewerkt: