Key takeaways
- Define the IT load and operating requirements before selecting infrastructure.
- Trace power and cooling from their source to the equipment they support.
- Plan commissioning, maintenance access and future expansion during design.
Start with a load narrative
Ask the IT team to describe initial equipment, expected growth, rack density assumptions and deployment phases. Distinguish installed nameplate ratings from the demand assumptions engineers will use. Record which loads are critical and what interruptions the business can tolerate. A future capacity target should have a date and decision trigger; otherwise it can become an expensive design assumption that nobody owns.
The U.S. Department of Energy's data center design guide addresses the relationship between IT conditions, air management, cooling and electrical systems. Use that integrated perspective to frame the design discussion. It does not replace equipment-specific requirements, engineering calculations or the applicable codes for the actual project.
Trace the electrical path end to end
Have the electrical engineer document the proposed service, switchgear, distribution, UPS arrangements and rack-level connections. Confirm the status of utility discussions and identify what remains subject to utility review. Existing equipment labels or spare floor area are not a capacity commitment. Show the routes, clearances and replacement access needed for major components, including work outside the data hall.
Discuss backup generation and fuel arrangements where required by the owner's program. Identify permitting, environmental, acoustic and site questions with the appropriate specialists. Do not treat a generator selection as an isolated purchase: distribution, controls, testing and the intended operating sequence must be coordinated. The design must explain how systems behave during normal operation, maintenance and the events the owner requires them to address.
Define redundancy in operational terms
Labels such as redundant or resilient are not sufficient acceptance criteria. Ask what can be taken out of service, for how long and while supporting which load. Identify shared dependencies that could undermine the intended arrangement. Maintenance procedures, controls and physical separation may matter as much as equipment counts. Have the engineering team document the agreed basis rather than inferring a certification or availability level from a component list.
For a hypothetical tenant starting with one equipment row and planning a second, the team might compare infrastructure installed now with space and pathways reserved for later. Neither option is automatically better. The decision depends on expected growth, upgrade access, shutdown constraints and the owner's investment priorities. This example does not describe an HQ installation.
Coordinate heat removal with the IT plan
Mechanical design should follow the actual equipment and load assumptions. Review airflow or liquid-cooling interfaces, heat-rejection arrangements, environmental controls and service access with the equipment suppliers. Identify where piping, ductwork, cable trays and electrical distribution compete for space. A coordinated section drawing can reveal conflicts that are difficult to see on separate floor plans.
The DOE guide emphasizes air management as part of efficient design. For planning purposes, ask how supply and return paths will be maintained as racks fill and cables accumulate. Avoid copying temperature limits or cooling strategies from a different facility without checking the equipment and design criteria. The acceptance plan should explain what will be measured and under which operating conditions.
Reserve routes for installation and replacement
Trace the physical path from delivery point to final position for large equipment. Confirm door openings, turning space, floor and structural considerations, rigging requirements and temporary storage. Review future replacement as well as first installation. A component that fits during an open-shell build may be difficult to remove after partitions and adjacent equipment are installed.
Separate construction access from operational access where the facility will be occupied. Coordinate cable pathways, labeling and documentation with the owner's standards. These decisions affect how later teams diagnose problems, expand systems and maintain the environment after the construction team leaves.
Define testing before procurement
Create a commissioning plan with responsibilities, prerequisites and acceptance evidence. Include equipment startup, controls checks, functional testing, documentation and operator training appropriate to the scope. Identify who writes and approves integrated test procedures and how operational risks will be managed. Do not improvise interruption tests around live systems.
The ASHRAE, PNNL and NEMA data center framework is a planning resource, not a mandatory code. Use applicable guidance with the project's licensed professionals to organize integrated decisions, while keeping code compliance and owner acceptance requirements separately documented.
Planning checklist
- Approved IT load assumptions and growth phases.
- Utility status and electrical distribution basis.
- Cooling concept and equipment interface information.
- Maintenance, delivery and replacement access.
- Procurement responsibilities and commissioning acceptance criteria.
Frequently asked questions
Should equipment selection come before the room layout?
They should develop together. Equipment requirements inform the layout, while building constraints may limit feasible selections.
Does redundant equipment guarantee uninterrupted operation?
No. System configuration, shared dependencies, maintenance, controls and operating procedures all affect performance. Avoid promising an uptime outcome without a defined and validated basis.
