An equipment purchase creates a power-planning decision before it reaches the rack. Give the electrical reviewer separate phase readings, the installed PDU’s outlet map, and a description of the workload being added. Those records help establish where the proposed equipment can be connected and what still needs investigation.
Identify the PDU and its outlet arrangement
Begin with the rack identifier and the exact power distribution unit model. Collect its ratings, outlet numbering, branch arrangement and manufacturer documentation. Keep the documentation beside the connection inventory so the person reviewing a proposed addition can check how each outlet is supplied.
Outlet position alone can be misleading. Raritan’s cabinet load-balancing explanation describes both grouped and staggered outlet arrangements. Some arrangements use phase pairs such as L1/L2. Copying the map from a nearby cabinet can therefore create a wrong connection record, even when both PDUs have a similar appearance.
Record what is known and flag any uncertain mapping for verification by the site’s electrical team. Keep a photograph of accessible identification labels if the site permits it. Verification that involves electrical access or a connection change belongs in the site’s approved work process.
Collect readings that describe the work being done
Retain the separate input phase-current readings available from the installed monitoring equipment. Preserve the measurement name and units: a reading for an input line, a branch and an individual outlet describes a different point in the distribution path. Combining them under a single “rack load” field removes information the reviewer needs.
Equipment demand also changes. Raritan’s load-balancing guidance explains that device consumption varies with its workload and that equipment with multiple power supplies adds complexity to the distribution review. A quiet-period observation gives limited evidence for a busy processing window.
For the review, pair the readings with a short operating log. Include the observation period, the jobs running, known maintenance, and any data gaps. Identify whether a recorded value is an instantaneous sample, an average or a maximum over an interval. A reviewer should be able to tell whether the evidence covers the conditions expected after the addition.
If the monitoring system lacks the necessary measurement, record that gap and assign someone to resolve it. Avoid turning an unavailable value into a zero or an assumed spare-capacity figure.
Attach a connection proposal to the equipment request
The following record is a practical way to bring the evidence into deployment planning. Prepare one entry for each proposed device and supply connection:
- Equipment: asset identifier, model, intended rack position and the work it will perform.
- Proposed connection: PDU identifier, outlet and documented branch or phase assignment.
- Demand evidence: manufacturer data or measured observations, with the configuration and workload stated.
- Existing demand: the monitoring period used for comparison and any operating conditions it excludes.
- Review owner: the person responsible for checking electrical limits and the site’s operating requirements.
Keep estimates distinguishable from measurements. If procurement changes the device configuration, or the intended workload changes before installation, return the proposal for review. The approved record needs to describe the equipment that will actually arrive.
This also gives the deployment team a place to resolve incomplete details before assigning a maintenance window. Purchasing, facilities and IT can work from the same device and connection identifiers.
Review the limiting path before approving the addition
Separate phase loading matters because demand can be uneven across a three-phase PDU. Raritan’s phase-overload guidance calls for planning around that distribution before server deployment.
Have the electrical reviewer compare the proposal with the installed equipment’s limits and the site’s approved design. Record which constraints were checked, what operating conditions were assumed, and whether additional measurements are required. Use the actual electrical arrangement when evaluating a device with more than one supply connection.
A useful decision states the permitted connection, any conditions attached to approval, and the evidence still outstanding. If the proposal cannot be accepted, record the specific constraint so procurement and deployment planning can respond to it. Avoid leaving “power checked” as the only explanation.
Retain the readings after installation
After approved work, update the connection inventory and save observations under the operating conditions named in the plan. Compare them with the expectations that supported approval. Record unexpected differences and their owner before closing the deployment task.
Keep the previous mapping, the accepted replacement record and the change identifier together. The next person reviewing an equipment addition will then have a dated account of the installed connections and the demand already observed.
Sources
- Raritan — Data Center Cabinet Load BalancingPublication date not stated. Retrieved October 17, 2026.
- Raritan — Load Balancing: What Is It?Publication date not stated. Retrieved October 17, 2026.
- Raritan — Avoid Overloading Phases Within a PDUPublication date not stated. Retrieved October 17, 2026.