After a deployment, operators inherit equipment that will change. Workloads move, connections are revised and components are replaced. Keeping the operating record aligned with that work gives the next person a reliable place to begin an investigation.
Choose one rack and follow its records
Start with a rack your team already operates. Ask a colleague who did not install it to find the equipment list, the current configuration and the most recent approved change. Have them identify the person responsible for each record. Write down any step that depends on calling the installer or searching a private message history.
This small exercise exposes practical gaps. A rack name may appear differently in the monitoring system and the installation drawing. A replacement server may still have its predecessor’s description. An accurate drawing may be stored where the receiving team cannot access it. Record the specific discrepancy and who can resolve it.
The review below is a proposed operating exercise. Adapt its scope to the equipment and responsibilities your team actually owns.
Give each measurement a defined job
For each reading you use, write the operating question beside it. An inlet-air reading can help assess conditions reaching equipment. A reading elsewhere in the cooling path describes a different location. The Department of Energy’s data-center design guide relates environmental assessment to equipment inlet conditions and recommends establishing measurement needs around the intended evaluation.
Our suggested record has a short set of fields: equipment identifier, measurement location, unit, source, observation time and reviewer. Add the comparison the reviewer intends to make, such as a manufacturer specification or a prior observation under a documented workload. Mark any missing field as an open item.
For example, a record called “rack temperature” needs clarification if the probe position is unknown. Ask where it was measured before using it to decide whether the equipment receives appropriate inlet air. A clear location makes later readings easier to compare.
Check the connections behind the equipment list
Use the same rack to review the connection records available to operations. Choose one documented server and trace its recorded network endpoints and power connections through the existing drawings and labels. Follow the site’s access and inspection procedures for any physical verification.
Keep discrepancies concrete. “Network record needs updating” gives the next person little to work with. A useful entry identifies the cable, the two endpoints shown in the record, the observed mismatch and the person assigned to reconcile it. Preserve the old record until the approved correction is traceable.
When planning another device, assemble its proposed location and connection requirements alongside the installed power-distribution information. The responsible electrical team can then assess the addition using the actual equipment and operating conditions.
Keep changes connected to their acceptance evidence
A firmware update, configuration revision or hardware replacement should leave a record that explains what changed and how the team assessed it. NIST SP 800-128 describes configuration control, evaluation of changes and retention of previous baselines. Its focus is information-system security; the following questions are our practical adaptation for an operating review.
- Which configuration and equipment did the work affect?
- Where are the checks used to accept the result?
- Who reviewed those checks, and which items remain unresolved?
- Where is the previous baseline, and what restoration procedure applies?
Consider a replacement that is recorded as complete while its monitoring record still refers to the removed component. The work log needs a follow-up action to reconcile that identity. Keeping the replacement and the unresolved record together prevents the open item from disappearing between teams.
Make the next review possible
End the exercise with a short action register. Each entry should name the equipment, the missing or conflicting information, the responsible person, the next review date and the evidence needed to close it. Group related entries when they share an owner, while preserving the individual equipment references.
Have the receiving operator repeat the original lookup after the corrections. They should be able to locate the current equipment record, explain the measurements being used and find the accepted change history. That repeat check gives the team a concrete way to assess whether the documentation work helped.
Valen Systems develops Arcturus for data-center infrastructure management. For a discussion about your monitoring requirements, bring one equipment record and an operating question your current measurements leave unanswered. That provides a specific starting point for deciding what needs to be observed and reviewed.
Sources
- DOE — Best Practices Guide for Energy-Efficient Data Center Design, July 2024Publication date not stated. Retrieved October 17, 2026.
- NIST SP 800-128 — Guide for Security-Focused Configuration Management of Information SystemsPublication date not stated. Retrieved October 17, 2026.