Zone-Based Planning Workbook

What Is Zone-Based Planning?

Zone-based planning is a methodology that decomposes a data center deployment into discrete capacity zones, each with defined power density, cooling load, physical footprint, and connectivity requirements. Rather than treating the entire facility as a monolithic buildout, zone-based planning enables phased delivery, independent commissioning, and targeted system design per zone.

GridCore applies zone-based planning across all three deployment models: container, modular building, and building + skid. The zone definitions remain consistent while the physical implementation adapts to the selected architecture.

Core Concepts

Zone Types

A typical GridCore deployment defines three primary zone categories:

• IT Zones contain rack rows, in-row cooling, and structured cabling. These zones define the compute and storage capacity of the facility and are the primary driver of power and cooling requirements.
• Infrastructure Zones house electrical distribution, mechanical plant, and controls equipment. These zones support the IT zones but are physically separated for serviceability, noise isolation, and code compliance.
• Support Zones include staging areas, loading docks, office/NOC space, and ancillary rooms. While not directly part of the IT or infrastructure systems, they are essential for operations and must be planned alongside capacity zones.

Zone Attributes

Each zone in a GridCore deployment is defined by the following attributes:

Step-by-Step Zone Planning Process

Step 1: Define Total Program Capacity

Begin by establishing the total IT load target for the deployment program. This is typically expressed in megawatts (MW) of IT load and determines the number and size of zones required. Account for planned growth phases and establish capacity buffers for future expansion.

Step 2: Decompose into Zone Blocks

Divide the total capacity into zone blocks based on deployment model constraints. Container-based deployments typically use 200-500 kW per zone. Modular buildings range from 500 kW to 2 MW per module. Building + skid deployments may define zones up to 5 MW each, depending on the building envelope configuration.

Step 3: Assign System Requirements Per Zone

For each zone, enumerate the required systems from the GridCore integrated systems catalog. Every IT zone requires electrical distribution, cooling, fire protection, and connectivity. Infrastructure zones require their own electrical feeds, monitoring connections, and access provisions.

Step 4: Map Utility Interconnections

Document how zones connect to shared utility infrastructure. This includes medium-voltage switchgear, chiller plants, generator yards, and telecommunications demarcation points. Zone-to-zone interfaces must be defined at both the physical and logical layers.

Step 5: Assign Delivery Phases

Group zones into delivery phases based on business priority, site readiness, and utility availability. Each phase should be independently commissionable, meaning all systems within the phase can be tested and brought online without dependency on later phases.

Zone Planning by Deployment Model

Container Deployments

Container zones are the most standardized. Each container represents a single IT zone with integrated cooling and power distribution. Infrastructure zones are typically shared across multiple container zones via a central utility yard. Support zones are minimal and may be limited to a staging pad and monitoring shelter.

Modular Building Deployments

Modular buildings allow more flexible zone boundaries. A single module may contain one or two IT zones plus a dedicated infrastructure bay. Modules can be stacked or linked to create larger zone complexes. Support zones are typically included as purpose-built modules in the overall assembly.

Building + Skid Deployments

Building + skid deployments offer the largest zone sizes and most flexible layout options. IT zones are defined within the building envelope, with infrastructure delivered on pre-engineered skids parked adjacent to or within the building. Support zones are fully enclosed and can include multi-story office and operations spaces.

Common Pitfalls

• Under-specifying infrastructure zones: Teams frequently allocate insufficient space and capacity for electrical and mechanical infrastructure relative to IT zones. A good rule of thumb is to allocate 40-50% of total floor area to infrastructure and support zones combined.
• Ignoring phase boundaries: When zones from different phases share utility infrastructure, commissioning the first phase may require partial installation of later-phase systems. Plan phase boundaries to minimize these dependencies.
• Treating all zones identically: Different zones may have different power densities, cooling requirements, or compliance obligations. Avoid applying a one-size-fits-all zone template without validating per-zone conditions.