Build · DCIM

One record of the physical estate, under change control.

Sites, floors, halls, rows, racks and devices, down to ports, power ports, PDU outlets and every cable. Every DCIM edit carries a change request: standard for pre-approved record work, an open CR at the site, or a new one raised for approval.

Who opens it

Every rack, port and cord as a record.

DCIM holds the physical estate down to the outlet, and every edit to it carries a change request.

Datacenter engineering asksWhich outlet is this PSU plugged into?

The power chain from the PSU cord to the PDU outlet, the feed, the busway and the UPS module.

Capacity planner asksIs there 4U and 6 kW free in this hall?

Free units and free power per hall, net of the units already reserved.

Change manager asksWhich change request moved this server?

The change request on the move, with the work it covered and who approved it.

On the screen

What the screen holds.

A rack elevation with both PDUs, the cable path of one port, the change request and the power chain behind it.

Also on the screen

Hierarchy to the port

Site → floor → hall → row → rack → device → ports, bays, power ports and console.

Catalogue and explorer

Device and module types, saved views and CSV export.

See your own estate in it.

Bring the fault your team keeps dealing with. We walk it end to end on a demo estate shaped like yours, then agree what a one-site pilot should prove.