Records · for the DCIM owner, the change approver and the commissioning lead
The record of what is connected to what is checked against the hall's own readings every day.
Every decision about a hall rests on a record: which breaker feeds which rack on which phase, which coolant branch serves which row, which leak sensor covers which zone. That record is right on the day it is drawn and drifts from then on. VARCOTT reads the white-space record from your DCIM and change workflow, checks it against telemetry every day so a wrong record is found before a wrong decision, predicts a move, add or change before it is made and confirms it after, and verifies the commissioning of a liquid-cooled hall against the model, with the calibrated model as the deliverable.
A record is right on the day it is drawn, and nothing in the hall tells anyone when it stops being right.
Halls change in small steps: a breaker replaced, a whip moved to the next panel, a rack added on a different phase than the drawing shows, a coolant branch re-routed during a repair. Each step is recorded by the person who made it, or not, and the record and the hall part company a little at a time.
In August 2025 a state data center was down for two days because, after a breaker was replaced, two critical network switches turned out to be on a different breaker than the electricians assumed; in the words of the official who explained it, when you shut off the main, you believe that everything behind that main is off. A colocation operator adding racks every quarter can see its record accuracy slip within two quarters of commissioning. One inventory vendor reports that its audits find about a fifth more assets on the floor than on record. And in a liquid-cooled hall the identifiers that join the facility to the GPU side, which rack is which in the building system and in the cluster manager, must be coordinated by hand before deployment, according to the GPU vendor's own integration guide.
Today the record is kept true by discipline: the move, add and change procedure, the DCIM analyst who approves each change against the capacity figure in the system, the periodic audit with a clipboard. Those catch what people remember to report. They do not catch what the hall knows and nobody wrote down.
02 · The daily check
The hall's own readings say what is connected to what, and VARCOTT compares them with the record every day.
If the record says panel 7 feeds racks 41 to 48 on phase A, then the current the panel's meter sees on phase A should equal the sum of what those racks draw. If a coolant branch serves a row, the flow the unit sees should be the sum of the branches, and the return temperature should follow the racks' heat. VARCOTT sums the rack draws and flows up the tree the record describes and compares the sums with every meter that exists.
Fig 1The daily checkreference hall · one row panel09:30 · panel 7 · meter 1.95 MW · record 2.48 MW · group 3 whip contradicted
A reference hall, illustrative numbers: at 08:30 a whip is moved to the neighbouring panel and the record is not updated; the meter and the record's sum part company, and after five minutes outside the meter's band the whip is flagged as contradicted.
Where the sums and the meters agree, the record is confirmed, and the confirmation is dated. Where they disagree, either the record is wrong or a sensor is wrong, and that device is flagged as contradicted until someone resolves it; no capacity is credited on it in the meantime, and the change workflow sees the flag before any change is approved against it. The record of the white space, panels, phases, breakers, whips, busway tap-offs, power shelves, coolant distribution units, manifolds, branches, quick disconnects and leak zones, therefore carries a status per connection: confirmed by the readings, contradicted by them, or not yet checked, with the date and the readings behind it. That status is offered to your DCIM as a feed or file it imports, so its data accuracy figure comes by connection rather than by survey.
03 · Changes and commissioning
A change is predicted before it is made and confirmed after, and a new hall is commissioned against the model that will then run it.
Before a move, add or change
A rack added to row 3 moves power and cooling at once: the panel's phase balance, the breaker margin, the branch flow, the neighbours' flow. VARCOTT takes the proposed change from your change workflow, applies it to the model of the hall, and returns what every affected device will read afterwards: the panel loading per phase, the flow to each branch, the coolant distribution unit's margin, at today's conditions and at the hottest hour on record. The DCIM analyst approves the change against those numbers instead of against a capacity figure typed at design.
After the change
When the change is made, the daily check compares the predicted readings with the measured ones. A change that lands where the model said it would is confirmed and closed in the record. A change that reads differently is flagged with the readings that differ, which is how a rack landed on the wrong phase or a branch left on the wrong manifold is found on the first day rather than at the next audit.
Commissioning a liquid-cooled hall
Commissioning guidance for liquid-cooled halls asks owners to require, at handover, the as-built documentation, an approved alarm matrix with its test evidence, and proof that the cooling distribution behaves as designed. VARCOTT verifies the integrated systems test against the model: every staged energisation, every flow balance, every alarm test is compared with what the model expected, and the differences are the finding list. The deliverable at handover is the calibrated model of the hall, which is the same model that will then check the record every day and compute the hall's limits.
For a hall built from a reference design
The rack, its power shelves, the coolant distribution unit and the leak response of a liquid-cooled AI hall follow published designs, so the record for those classes starts from a template per platform generation and is fitted to your hall's plant, redundancy and controls. The identifiers the GPU vendor's integration guide asks the site to coordinate by hand, between the building system and the cluster manager, are coordinated once in the record and verified by the daily check.
04 · Who owns the record
Say the daily check finds that panel 7 does not feed what the record says it feeds.
Three things are true before anyone edits anything.
Nothing was changed in your DCIM
VARCOTT does not edit the record. It flags the connection as contradicted, with the readings that contradict it, and leaves the correction to your move, add and change procedure. Your DCIM stays the system of record; VARCOTT gives it a status per connection and the evidence behind it.
The contradicted connection stops counting
Until it is resolved, no headroom is credited on that panel, the change workflow sees the flag before any change is approved against its figure, and the alarms on it carry a data-quality flag. A wrong record is dangerous only while it is trusted; the flag removes the trust without removing the record.
It stays in your hall
It runs on your own hardware, inside your network, reads the DCIM, the building management system, the power monitoring and the coolant unit controllers, and writes to none of them. The status per connection and the evidence are offered to your DCIM in the form it imports; the record belongs to you.
05 · Where this comes from
The daily check rests on the same model as the capacity study and the alarm list: the devices of the hall modelled from their makers' data and solved together as one system, and every reading compared with what that coupled model says it should be. The cooling-loop model is verified test by test against the Lawrence Berkeley National Laboratory's Modelica Buildings library; the power-distribution model is built the same way. The founder built the white-space power record for Fortune 500 data centers in 2013, panels, slots, breakers, phases and groups kept true to the site, and this is that record one generation of density later, with the hall's own readings as its witness.
VARCOTT is founded by David Perez, an electrical engineer who has written power software for mission-critical facilities since 2013: the white-space power management of Fortune 500 data centers, and one of the first live electrical digital twins in data centers.
06 · Next step
Start with one hall.
The first step is the record of one hall checked against its readings for one month, scoped in one call, from your DCIM export, your one-lines and loop drawings, and a historian export. The first deliverable is the list of connections the readings confirm and the list they contradict.