RTLS briefs for the people who actually decide.

Industry and solution pages still matter — roles above are entry points. If you are an SI partner or OEM, start at partners and independence.

Every engagement still follows gate-driven scoping: use case, live-floor evidence, integration and security, then scale. Role pages only change which risks and KPIs sit at the top of the agenda — so a CFO, CISO and EHS lead can each find their brief without reading the whole library first.

Each role page frames the same independent advisory for the questions that role brings into the room — board gates, privacy purpose, clinical hunt-time, OT segmentation, procurement hygiene. Industry and solution pages still matter; roles are entry points.

Case studies are composite worked examples unless an NDA reference is shown. Named references are available under NDA. SI and OEM partners: start at partners and independence.

The same RTLS or RFID programme looks different from each seat. Boards and CFOs buy risk-adjusted cash outcomes. COOs and plant directors buy throughput and WIP truth under production load. Procurement buys scoreable RFPs and exit rights. CISOs and IT/OT buy segmented estates and maintainable integrations. EHS and clinical leaders buy hunt-time, mustering and flow with privacy constraints. DPOs buy purpose limitation. Facilities buy actionable occupancy. SI and OEM partners buy an advisor who will not compete on hardware.

Hardware vendors typically pitch platform breadth and accuracy. System integrators pitch delivery capacity and preferred stacks. Large consultancies pitch transformation and operating-model change. Independent advisory sits on the buyer side: technology-last, gate-driven, no SKU to protect.

• Baseline the KPI on your site before tagging at scale.
• Demand production-load pilots with written go/no-go criteria.
• Model five-year TCO including tags, integration, support and change orders.
• Integrate location events into systems of record early — maps alone are not value.
• Separate people-tracking purposes from asset tracking; involve privacy early when identities are in play.
• Keep architecture neutral enough to swap radios or vendors without redesigning the business case.

• Technology chosen before the outcome and environment are named.
• Lab accuracy that fails in metal, multipath or clinical RF noise.
• Integration and change management left as phase 2.
• Year-1 discounts recovered through lock-in pricing.
• No named owner for the KPI after go-live.

Use the role briefs below to pressure-test vendor, SI and consultancy pitches against the questions that seat actually owns.

• What accuracy will we get in our environment under load — method and evidence?
• What is all-in five-year TCO, and what triggers more cost as we grow?
• Who owns integration to our systems, in writing?
• Do we own our location data in an open format on exit?
• Does the seller earn margin on hardware, AMR fleets or licences in this recommendation?
• What does a time-boxed production pilot with kill criteria look like?

TRACIO is an independent locating advisor for RTLS, RFID and related IoT. We do not sell hardware, AMR fleets or a platform of our own. Each persona page frames the same method — diagnose, architect, pilot, scale with gates — for the decisions that role brings into the room. Start with your seat; bring industry and solution pages when the use case is clear.

Expect three pitch styles when a locating programme (RTLS, Passive RFID, BLE, UWB or hybrid) enters the enterprise. Hardware and platform vendors lead with radio accuracy, tag form factors and a software suite — often bundling AMR or automation SKUs that expand the basket. System integrators lead with install capacity, preferred OEM partnerships and a turnkey SOW; the risk is a requirements document that quietly encodes one stack. Large consultancies lead with operating-model change and multi-workstream programmes; locating can become a workstream among many, with thin RF ownership.

Independent advisory inverts the order: name the KPI and environment, gate a production-load pilot, then shortlist technology. Use the role pages to make each seat ask the questions that seat owns — finance on TCO and exit, ops on exceptions, security on zones, privacy on purpose, procurement on scoreability.

TRACIO stays on the buyer side across all of those conversations: no hardware catalogue, no AMR fleet, no platform licence of our own.

Each role page frames the same independent advisory for the questions that role brings into the room — board gates, privacy purpose, clinical hunt-time, OT segmentation, procurement hygiene. Industry and solution pages still matter; roles are entry points.

Case studies are composite worked examples unless an NDA reference is shown. Named references are available under NDA. SI and OEM partners: start at partners and independence.