Technical Colocation RFP: specify power, cooling, cross‑connects and SLAs without losing control

When the customer’s equipment arrives and the room can’t sustain the power density of the next server generation, the migration grinds to a halt and vendors point to vague contract language. That impasse forces on‑site redesign, extends cutover windows and increases operational risk for critical applications. The practical thesis here: include measurable technical requirements and acceptance tests in the RFP so that assumptions become verifiable obligations before signature.

This document delivers copy‑ready RFP clauses, field validation criteria for electrical and cooling systems, a checklist for cross‑connects, and a technical annex template to demand FAT/SAT evidence. It is intended as a reusable base your procurement and infrastructure teams can adapt for rack migrations with high density per U or for compliance‑sensitive operations.

What specific migration deadlock does a technical RFP prevent?

Imagine the infrastructure team about to load racks: cabinets are populated, PDUs are shared across multiple tenants without clear ownership, and the available cooling relies on nominal room airflow rather than targeted per‑U delivery. The likely consequence is site rework—rewiring PDUs, relocating loads, or throttling equipment. A technical RFP avoids these outcomes by defining reserved per‑rack capacity, PDU segregation, monitoring endpoints and acceptance tests that demonstrate the environment meets operational conditions.

How to specify electrical capacity per rack and PDU distribution rules

Structure your electrical section into three layers: contracted reservation (what the client gets), distribution rules (how power is routed and protected), and verification (how the provider proves compliance). Each layer must contain testable criteria and required deliverables during commissioning.

• Contracted capacity per rack and per U: require the RFP to state reserved power per rack and, when relevant, a per‑U allocation. The annex should describe how transient peaks are handled and the procedure for requesting temporary or permanent increases.
• PDU topology and segregation: demand dedicated PDUs per rack or per cabinet bank, clear labeling, and dual feed where the design requires redundancy. Define rules for physical separation of critical circuits and for how shared PDUs are allocated and billed.
• Monitoring and telemetry: require continuous telemetry export (API access) from PDUs and UPS systems, including sampling frequency, event logs and alarm thresholds. Specify the minimum set of metrics to be forwarded during FAT/SAT for verification.

Copy‑ready clause — electrical (model)

“The Provider shall deliver dedicated electrical provisioning per rack as defined in Annex A. PDUs must be documented, labeled and segregated according to the topology in Annex A. Critical circuits shall support dual feed where specified. The Provider will expose PDU and UPS telemetry via an API for client verification. Prior to final acceptance (SAT), the Provider shall submit full electrical measurement reports and power quality test results in the format defined in the Technical Annex.”

Which metrics and tests to require during commissioning (FAT/SAT)?

Acceptance tests must reflect expected operational conditions, not only nominal component ratings. Split the program into FAT (component factory tests) and SAT (installed system verification) and require evidence in a standardized report format.

• Continuity and segregation tests for PDU circuits per rack;
• Progressive load tests per U to reproduce expected density and identify thermal or electrical bottlenecks (illustrative procedures should be adapted in Annex A);
• Power quality measurements: THD, power factor and observation of transient disturbances;
• UPS transfer tests, including observation of transfer behavior under load;
• Generator start and recovery sequencing if the site uses on‑site generation;
• Airflow and temperature capture per U under representative load, including thermography evidence;
• Remote monitoring validation: confirm sampling rates, time stamps, alarm forwarding and data retention.

Require that each SAT deliverable contain raw logs, equipment lists, photos of test setups and an executive pass/fail with remediation items. Allow a defined remediation window before final acceptance to correct non‑conformities.

Cooling: how to demand support for high density per U

For high‑density deployments, cooling design must be explicit in the RFP. The provider should describe the cooling architecture and define limits and procedures that prevent hotspots when racks approach the declared per‑U power envelope.

• Density bands and limits: state the expected power density per U or per rack in Annex A and require the provider to map those densities to cooling capabilities and to specify any limits beyond which additional engineering is needed.
• Airflow and thermal testing: include thermography, per‑U temperature probes and simulated load testing during SAT to demonstrate stable conditions under sustained load.
• Contingency and mitigation: require documented throttling or workload relocation policies, manual and automated steps the provider will take in the event of reduced cooling capacity, and time windows for execution.

Copy‑ready clause — cooling (model)

“The Provider shall maintain temperature and airflow conditions compatible with the density bands in Annex A. A SAT thermal report, including per‑U temperature readings, thermography and hotspot analysis under representative load, is mandatory prior to acceptance. The Provider will maintain a documented contingency plan for thermal events and will execute remediation actions within the timeframes defined in the SLA Annex.”

Cross‑connects and peering: what to request and how to validate it

Interconnection requirements must be specific: specify fiber or copper types, acceptable lead times for cross‑connect provisioning, and tests to validate link performance. Predictable latency and physical path separation are negotiation points for latency‑sensitive applications.

• Demand link certification during SAT, including attenuation, continuity and connector condition reports;
• Require a physical patch panel map with demarcation points and labeling as‑built prior to acceptance;
• If peering or carrier diversity matters, require a statement of carrier presence and the location of demarcation points, plus the option to perform measured latency tests between specified racks (illustrative testing procedures belong in the annex).

How to draft SLAs that protect critical operations without blocking deals

Separate objective, testable metrics from acceptable exceptions and craft a proportional remedy regime. SLAs should include proof channels and escalation paths rather than absolute or vague statements.

• Core metrics: electrical availability for contracted capacity, cooling availability for declared density bands, incident response times for severity levels, and provisioning lead times for cross‑connects;
• Proof mechanisms: monitoring logs, SAT/FAT reports and ticket histories. Require API or dashboard access for client audit where feasible;
• Remediation and penalties: define graduated remedies such as service credits, mandatory corrective actions within set windows, and termination rights for repeated breaches. Keep thresholds realistic so commercial offers remain viable.

SLA clause model (example)

“Electrical and cooling availability for contracted deliverables are defined in the SLA Annex. Verified downtime will be subject to service credits according to the table in the SLA Annex, with escalation on recurrence. The Provider will deliver monthly operational reports and grant client access to monitoring data for audit purposes.”

Essential checklist for electrical and cooling items to include in the RFP

1. Define reserved power per rack and per U in Annex A;
2. Specify PDU topology, labeling, dual feeds where applicable and segregation rules;
3. Mandate continuous telemetry endpoints and minimum metrics;
4. Require power quality testing and reporting (THD, power factor, transients);
5. State per‑U temperature limits and require airflow testing under load;
6. Demand as‑built documentation and FAT/SAT reports with raw evidence;
7. Set measurable SLAs, proof mechanisms and a graduated penalty/remediation framework.

Commissioning tests: an SAT report template to require

Insist that each SAT deliverable follow a template: test purpose, test owner, procedure steps, equipment used, raw logs, photos, time stamps, interpretation of results, pass/fail criteria and remediation actions. This standardization makes vendor responses comparable and speeds legal and technical review.

Contract clause language: enforceable elements legal teams can use

Provide clear definitions (e.g., “contracted rack power,” “SAT,” “FAT”), reporting obligations, audit rights and remediation windows. Use the copy‑ready clauses above as a technical annex to the contract; legal should adapt timeframes and thresholds to governance constraints.

Technical annex summary to attach to the RFP

Include the following as an executable annex: one‑line electrical per rack, UPS topology and redundancy statement, PDU models and port mapping, declared per‑U power limits, cooling topology and density mapping, FAT and SAT procedures with pass/fail criteria, required report formats, list of monitoring APIs and endpoints, and acceptance remediation process. Require signature on the annex as part of final acceptance.

Frequently asked questions

What does N+1 mean and when should I insist on 2N?

N+1 means one spare component is available to cover a single failure in a subsystem; 2N duplicates the entire subsystem. Require 2N when the business cannot tolerate unplanned downtime. N+1 can be acceptable where maintenance windows and clear SLAs mitigate risk. Choose based on impact tolerance and procurement budget.

How do I include high‑density per U requirements?

Specify target per‑U power in Annex A, require the provider’s cooling plan mapped to those density bands, and mandate SAT airflow and thermography tests. Use explicit pass/fail criteria for hotspot presence and remediation timelines.

Which tests validate the environment after installation?

Key SAT tests include circuit and PDU verification, progressive load per U, THD and power factor measurement, UPS transfer behavior under load, thermal tests under representative load, and validation of telemetry and alerting. Require standardized SAT reports with raw evidence.

Next step and commercial call to action

Use the copy‑ready clauses and the annex structure above to build an RFP that eliminates assumptions and converts obligations into verifiable acceptance criteria. To obtain the technical annex ready for inclusion in your RFP and to request a tailored review, download the annex and request an RFP review with a MVX specialist via Fale com um especialista. Learn more about the offering at Colocation MVX and see infrastructure details at Infraestrutura MVX.

CTA: Download the technical annex and request an RFP review with a MVX specialist (/pt/contact).