What this looks like when it works
Fewer lost / unaccounted tools and small plant.
Right-size hired plant from real usage data.
Verified muster within the drill SLA — not a claimed radio perfect.
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
Tool and plant shrinkage is a recurring cost; idle hired plant burns budget; manual head-counts are slow in an evacuation.
Our approach
- Passive RFID / BLE tags on tools, small plant and equipment.
- Gate and zone reads for cross-site movement and loss alerts.
- Utilisation analytics to cut unnecessary hire.
- Workforce wearables for mustering and access.
- Integrate with asset / hire and site-access systems.
Technology & integration
Stack deployed: Passive RFID + BLE asset tags, gateway readers, rugged wearables; GPS for plant in transit.
Integration: Asset / plant-hire management, site access, EHS.
Related: · Construction site safety · RFID consultant
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: Plant utilisation from operator estimate; tools lost between plots; headcount by clipboard at induction.
- Method: GNSS/telematics on plant between sites; RFID/UWB for tools and on-plot mustering; induction-gated zones.
- Period: One active megaproject plot for a construction phase, then programme template.
- Excluded: Office-only dashboards that site supervisors never open in the field.
Programme pattern for this vertical
Plant and workforce visibility on large civils sites tracks machines and people for utilisation and safety. GNSS/RTK outdoors plus BLE/UWB in structures is common.
Maintenance and hire desks need the utilisation truth.
Outcomes to expect — and how they are earned
Outcomes: lower idle plant cost, fewer 'where is the crew' delays, safer exclusion zones.
Lessons from comparable programmes
Lessons: hire-fleet tag ownership; supervisors must open the tool in the field; avoid fake precision.
Deeper problem framing
Idle hired plant burns cash. Crew location guesses waste critical path time.
Approach
GNSS/RTK outdoors; BLE/UWB in structures; hire-fleet tag ownership; supervisor field UX.
Outcomes and measurement
Idle hours, crew wait minutes, exclusion-zone breaches.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Implementation sequence and change management
Hire-fleet tag clause in supplier contracts; supervisor mobile UX; GNSS/RTK + indoor hybrid; idle-hour reviews in weekly commercial meetings.
KPIs: idle hours, crew wait, exclusion breaches.
Buyer checklist, vendor challenges and engagement shape
For plant/workforce, write hire-fleet tag ownership into supplier contracts before tagging begins.
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.
Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early — surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.
Governance, risk and what we refuse to claim
Composite example only. Your payback depends on adoption, integration quality and exception labour — not tag unit cost. Named references under NDA on engagement.
We challenge any vendor who asks you to accept demo-day averages as production truth.
Buyer checklist, vendor challenges and engagement shape
For plant/workforce, write hire-fleet tag ownership into supplier contracts before tagging begins.
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.
Training and communications plan: who explains purpose to operators, how often refreshers run, how contractors are inducted, and how successes are fed back without turning safety systems into league tables. Budget a champion network on each shift. Platforms do not adopt themselves. Where unions or works councils exist, share the purpose statement and retention rules early — surprise monitoring is how programmes die. Finally, schedule a formal gate review against the written criteria; celebrate a no-go if evidence is weak. Expanding failure is not delivery.
Last updated:
Site labour and plant
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
Who is on site, what is utilised
Time-on-site and plant jobs get distinct metrics.
Rugged, vendor-neutral kit
Selection survives weather, temporary networks and changing contractors.
Into the systems PMs already use
No orphan safety dashboard if it can feed existing tools.
Measurement
Baseline: plant/tool find-time samples, mustering drills, and permit exceptions. Pilot: one zone or tower with RTLS/RFID tied to the site system of record. Steady-state: mean time-to-find, muster completion time, and open safety tickets. Bands are programme-type for live sites.