What this looks like when it works
Audit / stock-take time vs manual counts.
High-90s asset audit accuracy — with method, not a radio guarantee.
Typical payback on efficiency & loss avoidance.
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
Manual stock-takes are slow, error-prone and pull personnel off task. Lost or unaccounted assets carry security as well as cost consequences, and audit-readiness is a recurring fire-drill.
Our approach
- Classify assets by sensitivity and define chain-of-custody checkpoints.
- Portal and handheld Passive RFID for gate, store and vehicle reads.
- Rules for unauthorised movement and missing-item alerts.
- Tamper-evident, ruggedised tagging suited to the environment.
- Exception-based dashboards so staff act only on anomalies.
Technology & integration
Stack deployed: Passive RFID portals + handhelds, ruggedised/tamper-evident tags; UWB or GPS for vehicle and yard location where needed.
Integration: Asset management / ERP, accountability and audit systems, secure on-prem options.
Related: Vendor checklist · Defence RTLS · 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: Serialized kit accountability by spreadsheet at embarkation; gaps found at destination.
- Method: RFID/RTLS custody events at pack, embark, and receive; audit samples vs system of record; air-gap options where required.
- Period: Exercise or deployment cycle with a controlled kit list.
- Excluded: “100% audit accuracy” as a radio claim — we report high-90s with method, consistent with RFID physics.
Programme pattern for this vertical
Deployable kits need rugged identity that survives theatre moves, with rapid inventory on receipt and pack-out. RFID portals and handhelds dominate; RTLS appears in fixed depots.
Offline-capable clients matter.
Outcomes to expect — and how they are earned
Outcomes: faster deployment readiness checks, fewer missing line items, repeatable pack verification.
Lessons from comparable programmes
Lessons: tag durability; master data hygiene; train for austere power/network.
Deeper problem framing
Deployable kits fail pack-out completeness under time pressure. Austere networks break SaaS assumptions.
Approach
Rugged RFID; offline clients; master-data hygiene; receipt/pack verification drills.
Outcomes and measurement
Pack completeness, time-to-ready, recount labour.
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
Kit BOM hygiene; rugged tags; offline pack verification; austere power drills; receipt scans. Train for theatre timelines.
KPIs: pack completeness, time-to-ready.
Buyer checklist, vendor challenges and engagement shape
For deployable kits, prove offline pack verification under austere power in the pilot script.
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 deployable kits, prove offline pack verification under austere power in the pilot script.
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:
Mission constraints first
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
Air-gap and clearance are requirements
Discovery treats network, accreditation and custody as hard gates, not afterthoughts.
No reseller bias under pressure
When timelines compress, independence is what stops the default vendor winning by default.
Evidence the board and auditor can read
Measurement method agreed up front so readiness claims survive scrutiny.
Measurement
Baseline: accountability drill times, serialized-part audit gaps, and “unable to locate” tickets. Pilot: one unit/area with identity + location reconciled to the approved system of record. Steady-state: muster/accountability completion, custody exceptions, and audit findings. Only programme-type ranges are published; classified detail stays offline.