Data centresComposite worked example — a pattern across programmes, not one client.
Data centres · Case study

Dock-to-rack identity that matches the CMDB.

For colo and enterprise halls where inbound kit, spare cages and change windows never quite agree with the system of record. TRACIO designed a vendor-neutral identity and location feed into DCIM and ITSM — without another dashboard to live in.

Case studies and programme figures on this page are composite worked examples — patterns from comparable deployments, not attributed results for a named client. Named references are available under NDA when you engage.

Request a named reference under NDA

___BLOCK14___CASE STUDYSerial–CMDB matchData centres · Case studyPassive RFIDlive position · Passive RFID95–99%Serial–CMDB match50–70%Faster spareFewerChange mismatches
What this looks like when it works

What this looks like when it works

95–99%

Serial–CMDB match.

50–70%

Faster cycle counting.

Fewer

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

How we measured it

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.
Same problem on your floor?

Let’s scope the real numbers for your operation.

Thirty minutes on your use case, environment and targets — vendor-neutral, no reseller margin.

Book a 30-minute scoping callGet the vendor selection checklistDownload the buyer’s guide

Last updated:

How TRACIO worked the problem

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.