Select a Canadian data-centre site from verified constraints

State what the site must host, when it must be ready, how quickly demand will grow and what service interruption the organization can tolerate. Separate steady IT load, peak load, deployment waves, commissioning load and recovery load. Record latency limits, data-location requirements, application dependencies, staffing hours and the recovery point and recovery time expected for each important service. A short list built before these facts are written tends to reward attractive claims rather than operational fit.

Sources: National Institute of Standards and Technology

Map every dependency that can defeat the recovery plan. That includes identity systems, network control, storage replication, cloud services, telecommunications, fuel delivery, staff access and vendor support. A second facility has limited value if it shares the same failure path or cannot run the required applications with current data. NIST contingency guidance starts with business impact and recovery priorities because equipment choices should follow the service that must be restored.

Sources: National Institute of Standards and Technology

Build a geographic screen from user latency, legal requirements, labour access, travel time, weather exposure, emergency access and distance from other critical sites. A metro can contain downtown carrier hotels, suburban colocation buildings and large campuses with very different power and access conditions. Treat the metro label as a research boundary. Open the individual directory records and the operator source before assigning a role to a building.

Sources: Canadian Internet Registration Authority, Natural Resources Canada

Do not assume that greater distance always creates better resilience. Two sites can be far apart and still depend on the same cloud region, carrier backbone, control platform or support team. Two sites in one metro can have different utilities and network paths, but that must be proved. Record the hazard or dependency the separation is meant to address, then ask for evidence that the proposed design removes or controls it.

Sources: National Institute of Standards and Technology, Canadian Centre for Cyber Security

Ask for requested capacity, available service voltage, application milestone, study status, point of connection, customer-owned work, utility work, protection requirements and forecast energization sequence. Distinguish an operator's existing service from power reserved for a new hall or future campus phase. A marketing total may describe a fully built campus. It does not prove that the first project block can be energized on the required date.

Sources: Hydro-Québec, Hydro One, BC Hydro

The provincial process matters. Ontario can require policy review as well as utility and IESO technical work. Alberta is managing large-load applications through an evolving allocation and technical process. British Columbia uses an allocation framework for certain new high-load projects before ordinary connection work is complete. Quebec classifies large-power service by tariff and customer conditions. Record the controlling process and date because a comparison can become stale while the project is still being evaluated.

Sources: Government of Ontario, Alberta Electric System Operator, Government of British Columbia, Hydro-Québec

List the networks, cloud on-ramps, internet exchanges, dark-fibre options and managed services the workload actually needs. For each one, ask whether it is already present, available by new build, delivered through a partner or only nearby. A facility being in the same city as an internet exchange does not establish a connection. A carrier logo does not state the meet-me room, service handoff, path, contract owner or installation interval.

Sources: Canadian Internet Registration Authority, Equinix

Ask for route drawings and demarcation details under the correct confidentiality process. Confirm where diverse paths stop being diverse, which provider controls each segment, how cross-connects are ordered, and which maintenance events can affect both paths. Keep logical network separation in the design as well. The Canadian Centre for Cyber Security describes zoning as a way to group services under defined security policies and control traffic at zone boundaries.

Sources: Canadian Centre for Cyber Security

Record floor loading, clear height, delivery path, loading access, freight elevator limits, rack dimensions, cable routes, work areas, storage rules, fire-protection interfaces, security boundaries and hours of access. For new construction, add land control, zoning, permits, geotechnical work, drainage, water, noise, fuel systems, utility corridors and the schedule for authority reviews. The purpose is not to replace qualified design work. It is to expose missing studies before the commercial comparison hardens.

Sources: ASHRAE

Match the thermal plan to the IT equipment, not to a generic room temperature. ASHRAE guidance treats equipment inlet conditions, measurement locations, airflow patterns and manufacturer heat-load information as connected design inputs. Ask how the proposed room will handle the current rack mix, the expected density, partial loading, maintenance conditions and later equipment generations. A claim about cooling capacity needs the operating assumptions behind it.

Sources: ASHRAE

Translate every critical design answer into the document that will control delivery. Record the ordered power, measurement method, installation responsibilities, target dates, acceptance conditions, cross-connect scope, access rights, maintenance notice, service credits, renewal terms, change process and exit obligations. A technically suitable building can still be a poor fit if the contract leaves the required service optional or assigns an unmanageable dependency to the customer.

Sources: National Institute of Standards and Technology

Separate current fact, supplier commitment, project assumption and open question in the comparison file. Date each item and name the person or document that supplied it. Do not convert a sales discussion into a commitment. When two sources conflict, keep both until the responsible party resolves the difference in writing. The cleanest short list is not the one with the most green cells. It is the one with the fewest unowned critical questions.

Sources: Hydro One, BC Hydro

Bring facilities, network, security, application, finance, procurement, legal and operations owners into one review. Walk through normal operation, maintenance, utility loss, network loss, equipment failure, emergency access and recovery at the alternate location. Confirm which risks are accepted, transferred, reduced or still open. A single weighted score can hide a fatal condition, so keep non-negotiable gates beside scored preferences.

Sources: National Institute of Standards and Technology, Canadian Centre for Cyber Security

Before approval, confirm the latest source dates and revisit any item tied to a queue, tariff, construction milestone or supplier availability. Keep the directory record as the public starting point, then store project-specific evidence in the organization's controlled system. Do not place security drawings, access details, credentials or confidential capacity documents into public notes or a browser-only planning tool.

Sources: Alberta Electric System Operator, Government of British Columbia