The system of record for the data centre.
One record of every site, hall, rack, power path, customer, contract, ticket, change and credit. One ID each, kept for life. Four products read and write it, so nothing else has to agree.
One record, built in six moves.
DIL does not replace what you run. It reads it, reconciles it, and becomes the copy everyone trusts.
One object. All its links.
rk_2b14 · A single, persistent identity
01
Connect what you already run.
Connectors read your BMS, EPMS, DCIM, ITSM, finance and identity systems. Each has an owner, a mapping and a mismatch report. Nothing is ripped out.
- BMS
- EPMS
- DCIM
- ITSM
- ERP
- SSO
| Source | Owner | Objects | Last sync | Mismatches |
|---|---|---|---|---|
| EcoStruxure BMS | M. Keller | 1,204 | 2 min | 0 |
| ION EPMS | M. Keller | 388 | 2 min | 3 |
| Nlyte DCIM | L. Moreau | 2,910 | 6 min | 12 |
| ServiceNow | J. Park | 740 | 1 min | 0 |
| NetSuite | Finance | 212 | 1 h | 1 |
02
Reconcile to one ID.
The same rack arrives spelled five ways. DIL resolves it to one object with one ID, keeps the aliases, and shows you what still disagrees.
- One ID
- Aliases kept
- Mismatch report
03
Link the chain.
A reading becomes an alarm, an incident, a change and a credit. Every link is on the same rack and the same contract, so the story replays end to end.
- Reading
- Alarm
- Incident
- Change
- Credit
Each link carries who, when and why. Nothing is re-keyed between them.
04
Share the queue.
Incidents and changes live in DIL, not in a product. Facilities, the NOC, sales and finance see the same item with the fields their role needs.
- One queue
- Roles
- Customer view
05
Prove it, any time.
Every approval, override and edit is kept, with who and when. Audit packs for any hall, customer or period are a query, not a hunt.
- Attributed writes
- Audit pack
- Exports
| When | What | Who | Approval |
|---|---|---|---|
| 12 Jul 09:14 | Breaker 2B-07 set-point | M. Keller | CHG-5102 |
| 30 Jul 14:02 | Feeder 2 maintenance | L. Moreau | CHG-5180 |
| 18 Aug 11:31 | Override · UPS B bypass | M. Keller | Reason kept |
| 02 Sep 16:45 | Capacity reservation · NW | J. Park | CHG-5531 |
06
Extend it.
Dashboards, scheduled reports and a documented API over the same record. Your data stays exportable, in full, whenever you ask.
- API
- Reports
- Webhooks
- Full export
What makes the record hold.
Three properties, and the four products inherit all of them.
01
One object, one ID
Every site, hall, rack, power path, person, contract and ticket is one object. Products reference it; they never copy it.
- Aliases keptOld names stay searchable.
- Mismatch reportWhat still disagrees, and whose it is.
- Kept for lifeDecommissioned is a state, not a deletion.
02
Linked, not joined later
Readings, alarms, incidents, changes and credits are written as links at the moment they happen.
- Chain of recordSensor to bill, replayable.
- Shared queueOne incident, every role.
- Customer scopeTheir floor and nothing else.
03
Attributed and consistent
Every write carries who, when and why. Reads are strongly consistent across the four products.
- ApprovalsWindows, sign-offs, overrides.
- Audit packsA filter, not a hunt.
- ExportsFull, on demand, yours.
Running more than one hall on more than one tool? Bring your connector list and we will map it to the record in a working session.
Speak to our experts →Works with the stack you already run.
Read first, write where you let it. Each connector ships with an owner, a mapping and a mismatch report.
Building & power
BMS and EPMS, for readings, alarms and set-points.
Inventory
DCIM and asset systems, for racks, assets and cabling.
Tickets & monitoring
Where incidents and alerts live today.
Money & people
Finance, CRM and identity.
Design partner places are open
Map your floor. Keep the record.
Design partner places are open for operators running 2 MW and up.