What this looks like when it works
Serial–CMDB match.
Faster cycle counting.
Change-window serial mismatches.
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. KPI figures are typical ranges across comparable deployments; your own numbers depend on use case, environment and execution.
The challenge
Manual cage counts are slow, and inbound serials that never land in the CMDB drive failed changes, ghost spares and audit risk.
Our approach
- Passive RFID for dock receipt, cage inventory and spare-pool identity.
- BLE / Wi-Fi RTLS for high-value asset and people visibility on the floor.
- Change-window verification so the serial on the ticket matches the serial on the rail.
- Continuous reconciliation of tagged kit against DCIM / CMDB.
- Operational views for match rate, retrieval time and change success — in systems the team already uses.
Technology & integration
Stack deployed: Passive UHF (RAIN) RFID, BLE and Wi-Fi RTLS across the data hall and spare cages.
Integration: DCIM / CMDB, ITSM change tickets, and operations views.
Outcome: “Dock-to-rack identity cut ghost spares and made change windows boring — in a good way.”
Related: Data centres RTLS · Serialized chain-of-custody · Compare technologies
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: Asset receives at dock; rack location updated days later in CMDB/DCIM.
- Method: RAIN identity dock-to-cage-to-rack; CMDB reconciliation age and mismatch rate.
- Period: One hall or intake lane through a refresh wave.
- Excluded: Serial presence in a spreadsheet that is not the system of record.
Programme pattern for this vertical
Data-centre receiving programmes track serialized assets from dock to rack with RFID/barcode hybrid and sometimes cage-level RTLS.
CMDB/DCIM must be the system of record.
Outcomes to expect — and how they are earned
Outcomes: fewer lost assets in staging, faster install audits, better reconciliation for finance.
Lessons from comparable programmes
Lessons: no spreadsheet SOR; stage cage discipline; vendor box re-labelling chaos.
Deeper problem framing
Serialized IT assets vanish between dock and rack. Spreadsheets pretend to be CMDB.
Approach
Dock-to-cage-to-rack scans; CMDB/DCIM SOR; stage discipline; re-label chaos handling.
Outcomes and measurement
Lost-in-staging rate, install audit time, finance reconciliation.
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
CMDB as SOR mandate; dock/cage/rack scan points; staging SLA; finance reconciliation join; re-label playbooks.
KPIs: lost-in-staging, install audit time.
Buyer checklist, vendor challenges and engagement shape
For dock-to-rack, mandate CMDB/DCIM as system of record and kill staging spreadsheets in the charter.
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.
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 dock-to-rack, mandate CMDB/DCIM as system of record and kill staging spreadsheets in the charter.
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.
Last updated:
Hall identity and CMDB
Independent advisory means the radio is chosen last — after the job, the constraints and the system of record are clear.
Dock-to-rack and spare pools
Serial truth against DCIM/CMDB before another monitoring pane.
Metal-dense selection
On-metal RFID and portal design beat office-grade BLE fantasies.
Independence in the hall
No platform of our own; you buy hardware direct.
Measurement
Baseline: CMDB vs cage spot-checks and change tickets closed with “wrong serial / not found.” Pilot: one hall or spare cage with dock receipt RFID and CMDB write-back for 4–6 weeks. Steady-state: serial–CMDB match rate, mean spare-retrieval time, and change-window serial mismatches. KPI bands are typical for this shape of programme.