ANSI/TIA-942-C ↗Paid
TIA
Document: standard · C (2024)
Status: current · as of
Authoritative for: Facility infrastructure and Rated levels.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Library
Read these too
This guide connects the disciplines; it does not replace the specialist references. The committee standards own the classes and requirements you certify against, the OEM documentation governs the build once a platform is chosen, the institutions and analysts produce the measurements and forecasts the register cites. For every entry below: what it is authoritative for, and the moment to leave this site and open it. Document identities below come from Appendix A, with an edition, dated publication status and applicable boundary. Access for the other references was checked 2026-09-05; paid does not mean avoidable.
facility requirements
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
ANSI/TIA-942-C AI addendum ↗Access terms not published
TIA
Document: standard · TIA-942-C-1 (Addendum 1: AI); call for interest 2026-02-26
Status: draft · as of
Authoritative for: AI facility cabling, power and cooling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ANSI/BICSI 002 ↗Paid
BICSI
Document: standard · 2024
Status: current · as of
Authoritative for: Facility design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ANSI/BICSI 009 ↗Paid
BICSI
Document: standard · 2024
Status: current · as of
Authoritative for: Facility operations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Uptime Institute
Document: standard · edition not stated online
Status: current · as of
Authoritative for: Facility topology outcomes.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Uptime Institute
Document: standard · effective 2013-04-01
Status: current · as of
Authoritative for: Facility management behaviors.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-1 ↗Paid
CENELEC / BSI
Document: standard · 2019
Status: current · as of
Authoritative for: Facility classification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-2-4 ↗Paid
CENELEC / BSI
Document: standard · 2023
Status: current · as of
Authoritative for: Telecom cabling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-3-1 ↗Paid
CENELEC / BSI
Document: standard · 2026
Status: current · as of
Authoritative for: Management and operation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2021
Status: current · as of
Authoritative for: Facility classification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2024
Status: current · as of
Authoritative for: Building construction.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2021
Status: current · as of
Authoritative for: Power distribution.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2021
Status: current · as of
Authoritative for: Environmental control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: specification · 2018
Status: current · as of
Authoritative for: Telecom cabling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2024
Status: current · as of
Authoritative for: Physical security.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: specification · 2018
Status: current · as of
Authoritative for: Management and operation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-2-1 ↗Paid
CENELEC / BSI
Document: standard · 2021
Status: current · as of
Authoritative for: Building construction.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-2-2 ↗Paid
CENELEC / BSI
Document: standard · 2019
Status: current · as of
Authoritative for: Power supply and distribution.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-2-3 ↗Paid
CENELEC / BSI
Document: standard · 2019
Status: current · as of
Authoritative for: Environmental control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-2-5 ↗Paid
CENELEC / BSI
Document: standard · 2021
Status: current · as of
Authoritative for: Physical security.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NERC CIP-014 ↗Free
NERC / FERC
Document: standard · -3 in force; -4 approved 2026-09-10, effective 2028-10-01
Status: current · as of
Authoritative for: Physical security of transmission substations; a Transmission Owner/Operator duty (Chapter 4.3).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NERC / FERC
Document: standard · -1 final-ballot texts (October 2026); FAC-001-5 and FAC-002-5 revised alongside
Status: draft · as of
Authoritative for: Computational Load Sites ≥50 MW at ≥100 kV: interconnection, modeling, data, protection, disturbance monitoring; no ride-through curve. Ballot passed 2026-10-15 (Chapter 4.3).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (effective 2026-09-17)
Status: current · as of
Authoritative for: Ride-through and recovery for computing load only; cooling exempt. An industry spec, not a regulation: in the US, ERCOT NOGRR282 and SPP rules bind (Chapter 4.10; tests: 13.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (AMD, Google, Meta, NVIDIA)
Document: specification · Revision 0.7.0 (effective 2026-08-27)
Status: current · as of
Authoritative for: Design targets for 2027–28 ML halls: 8,000 lb rack, 12 ft transport aisle, 25 kW/ft average (15 kW/ft air plus 25 kW/ft liquid capacity), 350 kW/ft peak (Chapter 6.1).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ERCOT / PUCT
Document: regulation · PUCT-approved 2026-07-09; effective 2026-08-01
Status: current · as of
Authoritative for: New Large Computational Loads ≥75 MW (≥50% power electronic): ≥90% of load back within 2 s of voltage above 0.90 pu; operating or approved by 2025-11-14 exempt (Chapter 4.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
SPP / FERC
Document: regulation · RR696 (revision 2025-09-23); applies to requests from 2026-01-15
Status: current · as of
Authoritative for: Loads ≥10 MW at ≤69 kV or ≥50 MW above: ride through 0.50–Chapter 4.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
EirGrid / CRU
Document: regulation · CRU decision 2026-09-22; in force from about 2026-10-27
Status: current · as of
Authoritative for: Transmission-connected demand: fault ride-through, ±1 Hz/s RoCoF withstand, active-power recovery; non-compliance without a derogation breaches the Code (Chapter 3.2).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NERC / FERC
Document: regulation · Board-approved 2026-10-08; FERC filing due 2026-12-31
Status: draft · as of
Authoritative for: Registers Computational Load Owners and Operators for sites ≥50 MW connected at ≥100 kV; a proposal until FERC approves it (Chapter 4.3).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NERC
Document: guideline · Level 3 Essential Actions alert (2026-05-04)
Status: current · as of
Authoritative for: Seven essential actions for planners, transmission entities, balancing authorities and reliability coordinators; not mandatory, nothing set on data centers directly (Chapter 4.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
thermal references
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
ASHRAE
Document: guideline · Online; revision ID not published
Status: current · as of
Authoritative for: Datacom engineering reference.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 5th (2021)
Status: current · as of
Authoritative for: Air A1–A4/H1 and facility-water W classes.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 3rd (2018)
Status: historical · as of
Authoritative for: IT power trends.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2nd (2009)
Status: historical · as of
Authoritative for: Facility design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2nd (2013)
Status: historical · as of
Authoritative for: Liquid-cooling system design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2008
Status: current · as of
Authoritative for: Structure and vibration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2nd (2009)
Status: historical · as of
Authoritative for: Facility efficiency.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2008
Status: historical · as of
Authoritative for: High-density design cases.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2nd (2014)
Status: current · as of
Authoritative for: Contamination control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2010
Status: current · as of
Authoritative for: Energy measurement.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2011
Status: current · as of
Authoritative for: Efficiency practices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2014
Status: current · as of
Authoritative for: PUE interpretation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2015
Status: historical · as of
Authoritative for: IT efficiency metrics.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2016
Status: current · as of
Authoritative for: IT and facility interfaces.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2019
Status: current · as of
Authoritative for: DCIM integration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE / IES
Document: standard · 2025
Status: current · as of
Authoritative for: Building energy code floor, including minimum chiller efficiencies; data-center IT energy performance falls under Standard 90.4.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: standard · 2025
Status: current · as of
Authoritative for: Data-center energy performance.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: standard · 2020 + Addendum b (approved 2026-02-27)
Status: current · as of
Authoritative for: Laboratory rating tests for data-center cooling equipment. Addendum b adds a rating method for liquid-to-liquid CDUs (Chapter 5.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: standard · 2021
Status: current · as of
Authoritative for: Building-water Legionella risk.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: standard · 2024
Status: current · as of
Authoritative for: Building commissioning process.
Reach for it when: Specifying or checking requirements within this document’s boundary.
PNNL / ASHRAE / NEMA
Document: guideline · Online; revision ID not published
Status: current · as of
Authoritative for: AI facility energy and water practices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Cooling Environments)
Document: report · v1.00 (2026-10-12)
Status: current · as of
Authoritative for: Cooling-method selection by efficiency, economics and physics limits; projects a single-phase cold-plate limit near 4,000 W per reticle-class die (Chapter 5.1).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Open Accelerator Infrastructure)
Document: guideline · 2023-03-03 update
Status: current · as of
Authoritative for: Cold-plate loop design for 8-OAM training systems: 7.5–12 °C coolant rise, about 1.25–2.0 L/min per kW with PG25 (§1.3). A TCS guideline, not a facility-water target (Chapter 5.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Cooling Environments, Heat Reuse sub-project)
Document: guideline · V 1.00 (September 2024); restated on OCP's blog 2026-05-20
Status: current · as of
Authoritative for: Local-government levers for heat reuse: matching heat users, incentives, agreements before permit approval (Chapter 15.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2019
Status: current · as of
Authoritative for: Whole-building commissioning.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2025
Status: current · as of
Authoritative for: HVAC commissioning.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2023
Status: current · as of
Authoritative for: Building-water Legionella management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: guideline · 2017 SI; Sound and Vibration
Status: historical · as of
Authoritative for: Octave/A-weighting, level summation and propagation; no project noise limits.
Reach for it when: Specifying or checking requirements within this document’s boundary.
installation and safety references
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
NFPA 70 ↗Paid
NFPA
Document: standard · 2026
Status: current · as of
Authoritative for: Electrical installations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 70E ↗Paid
NFPA
Document: standard · 2027
Status: current · as of
Authoritative for: Electrical work safety.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 75 ↗Paid
NFPA
Document: standard · 2024
Status: current · as of
Authoritative for: IT equipment fire protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 76 ↗Paid
NFPA
Document: standard · 2024
Status: current · as of
Authoritative for: Telecom facility fire protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 72 ↗Paid
NFPA
Document: standard · 2025
Status: current · as of
Authoritative for: Fire alarm and signaling: detection, notification and the alarm path (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 13 ↗Paid
NFPA
Document: standard · 2025
Status: current · as of
Authoritative for: Sprinkler system installation, including pre-action systems (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 2001 ↗Paid
NFPA
Document: standard · 2025
Status: current · as of
Authoritative for: Clean-agent fire extinguishing systems (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 1 ↗Paid
NFPA
Document: standard · 2027
Status: current · as of
Authoritative for: Fire Code adopted in some states instead of the IFC; carries the ESS requirements there (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
International Code Council (ICC)
Document: standard · 2027 (Section 1207 Electrical Energy Storage Systems); 2024 or 2021 edition where adopted; Section 1206 in 2018-edition states
Status: current · as of
Authoritative for: US model fire code that gives ESS rules legal force where adopted: Section 1207 sets the stored-energy thresholds and recognizes UL 9540A testing (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 855 ↗Paid
NFPA
Document: standard · 2026
Status: current · as of
Authoritative for: Stationary energy-storage installation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 110 ↗Paid
NFPA
Document: standard · 2025
Status: current · as of
Authoritative for: Emergency and standby power systems.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 37 ↗Paid
NFPA
Document: standard · 2024
Status: current · as of
Authoritative for: Installation and use of stationary combustion engines and gas turbines (Chapter 4.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 56 ↗Paid
NFPA
Document: standard · 2027
Status: current · as of
Authoritative for: Cleaning and purging of flammable-gas piping, new or existing; forbids using flammable gas to clean pipe (Chapter 4.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 59A ↗Paid
NFPA
Document: standard · 2026
Status: current · as of
Authoritative for: Production, storage and handling of LNG; thermal-radiation and vapor-dispersion siting distances, as adopted by the state or local fire code (Chapter 4.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 70B ↗Paid
NFPA
Document: standard · 2026
Status: current · as of
Authoritative for: Electrical equipment maintenance programs.
Reach for it when: Specifying or checking requirements within this document’s boundary.
NFPA 780 ↗Paid
NFPA
Document: standard · 2026
Status: current · as of
Authoritative for: Lightning-protection installation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 60038 ↗Paid
IEC
Document: standard · 2009 + AMD1:2021; ed. 7.1
Status: current · as of
Authoritative for: System voltage values.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 60255 ↗Paid
IEC
Document: standard · Series; -1:2022 base
Status: varies by part · as of
Authoritative for: Protection relays.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 60309 ↗Paid
IEC
Document: standard · Series; -1:2021 + COR1:2023 base
Status: varies by part · as of
Authoritative for: Industrial plugs and sockets.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 60320 ↗Paid
IEC
Document: standard · Series; -1:2021 base
Status: varies by part · as of
Authoritative for: Equipment couplers.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 60364 ↗Paid
IEC
Document: standard · Series; -1:2025 base
Status: varies by part · as of
Authoritative for: Low-voltage installations. Europe applies the parts as the CENELEC HD 60364 series, through each country's national standards.
Reach for it when: Specifying or checking requirements within this document’s boundary.
BS 7671 ↗Paid
IET / BSI
Document: standard · 2018+A4:2026 (published April 2026); A2:2022+A3:2024 withdrawn 2026-10-15
Status: current · as of
Authoritative for: UK wiring regulations; Amendment 4 adds rules for battery energy storage and ICT functional earthing (Appendix G).
Reach for it when: Specifying or checking requirements within this document’s boundary.
CSA Group
Document: standard · 2024 (26th edition)
Status: current · as of
Authoritative for: Canadian electrical installation code, adopted and amended by each province or territory (Appendix G).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Standards Australia / Standards New Zealand
Document: standard · 2018 + Amd 1:2020, Amd 2:2021, Amd 3:2023
Status: current · as of
Authoritative for: Australian and New Zealand electrical installation rules, applied through state, territory and national law (Appendix G).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NR-10 ↗Free
Brazil Ministry of Labour and Employment
Document: regulation · As amended by Portaria SEPRT 915/2019 (in force until 2027-05-31); new text by Portaria MTE 737/2026 in force from 2027-06-01
Status: current · as of
Authoritative for: Safety in electrical installations and services (electrical work safety) (Appendix G).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61000-4-7 ↗Paid
IEC
Document: standard · 2002 + AMD1:2008 (consolidated 2.1)
Status: current · as of
Authoritative for: Harmonic and interharmonic measurement method.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61000-4-30 ↗Paid
IEC
Document: standard · 2025; corrected 2026-07
Status: current · as of
Authoritative for: Power-quality measurement.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62368-1 ↗Paid
IEC
Document: standard · 4.0 (2023; corrected 2025-08)
Status: current · as of
Authoritative for: Safety of ICT and audio/video equipment, including energy-source classes.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61439 ↗Paid
IEC
Document: standard · Series; -1:2020 base
Status: varies by part · as of
Authoritative for: Low-voltage assemblies.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61508-6 ↗Paid
IEC
Document: standard · 2010; ed. 2.0
Status: current · as of
Authoritative for: Functional-safety application guidance.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61511 ↗Paid
IEC
Document: standard · 2026 SER pack; part editions vary
Status: varies by part · as of
Authoritative for: Process safety systems.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61643 ↗Paid
IEC
Document: standard · Series; -01:2024 base
Status: varies by part · as of
Authoritative for: Surge-protective devices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61643-01 ↗Paid
IEC
Document: standard · 2024; ed. 1.0
Status: current · as of
Authoritative for: Surge-protection general requirements.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61643-11 ↗Paid
IEC
Document: standard · 2025; ed. 2.0
Status: current · as of
Authoritative for: AC surge-protective devices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61643-41 ↗Paid
IEC
Document: standard · 2025; ed. 1.0
Status: current · as of
Authoritative for: DC surge-protective devices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 61850 ↗Paid
IEC
Document: standard · 2026 SER pack; part editions vary
Status: varies by part · as of
Authoritative for: Utility-automation communications.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62040-3 ↗Paid
IEC
Document: standard · 2021; ed. 3.0
Status: current · as of
Authoritative for: UPS performance and test methods, including the VFI/VI/VFD classification used to compare double-conversion and eco modes (Chapter 4.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62053-22 ↗Paid
IEC
Document: standard · 2020; ed. 2.0
Status: current · as of
Authoritative for: Static active-energy meters.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62271 ↗Paid
IEC
Document: standard · 2026 SER pack; part editions vary
Status: varies by part · as of
Authoritative for: High-voltage switchgear.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62305 ↗Paid
IEC
Document: standard · 2026 SER pack; parts 1–4:2024
Status: varies by part · as of
Authoritative for: Lightning protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62305-2 ↗Paid
IEC
Document: standard · 2024 + COR1:2024; ed. 3.0
Status: current · as of
Authoritative for: Lightning-risk management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62305-3 ↗Paid
IEC
Document: standard · 2024; ed. 3.0
Status: current · as of
Authoritative for: Physical lightning protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62682 ↗Paid
IEC
Document: standard · 2022; ed. 2.0
Status: current · as of
Authoritative for: Alarm-system management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 54 ↗Paid
CEN / BSI
Document: standard · Series; -1:2021 introduction
Status: varies by part · as of
Authoritative for: Fire detection and alarms.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 13445 ↗Paid
CEN / BSI
Document: standard · Series; -1:2026 general
Status: varies by part · as of
Authoritative for: Unfired pressure vessels.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 13480 ↗Paid
CEN / BSI
Document: standard · Series; -1:2024 general
Status: varies by part · as of
Authoritative for: Metallic industrial piping.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASME B31.3 ↗Paid
ASME
Document: standard · 2024
Status: current · as of
Authoritative for: Process piping: design, materials, fabrication, examination and pressure testing (Chapter 5.13).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASME B31.5 ↗Paid
ASME
Document: standard · 2022
Status: current · as of
Authoritative for: Refrigeration piping and heat-transfer components (Chapter 5.13).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASME B31.9 ↗Paid
ASME
Document: standard · 2025
Status: current · as of
Authoritative for: Building services piping, such as chilled- and condenser-water systems in commercial and institutional buildings, within its size, pressure and temperature limits (Chapter 5.13).
Reach for it when: Specifying or checking requirements within this document’s boundary.
EU
Document: regulation · Directive 2014/68/EU (consolidated text 2026-05-30)
Status: current · as of
Authoritative for: EU conformity assessment for pressure equipment and assemblies above 0.5 bar, graded into Categories I–IV (Chapter 5.13).
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 15978 ↗Paid
CEN / BSI
Document: standard · 2026
Status: current · as of
Authoritative for: Building environmental assessment.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 16750 ↗Paid
CEN / NSAI
Document: standard · 2017 + A1:2020
Status: current · as of
Authoritative for: Oxygen-reduction fire prevention.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ETSI
Document: standard · V2.1.1 (2012-02); replaced by Part 3 V2.3.1 (2023)
Status: superseded · as of
Authoritative for: DC power interface up to 400 V at telecom/ICT equipment input.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 668 ↗Paid
ISO
Document: standard · 2020 + Amd1:2022
Status: current · as of
Authoritative for: Freight-container dimensions.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 1996-2 ↗Paid
ISO
Document: standard · 2017 (Edition 3)
Status: current · as of
Authoritative for: Environmental noise: determining sound pressure levels; informative Annex K gives an objective tonal screen.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 8528-5 ↗Paid
ISO
Document: standard · 2025
Status: current · as of
Authoritative for: Generator-set performance classes and load-step response.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 10816 ↗Paid
ISO
Document: standard · Series; editions vary by part
Status: varies by part · as of
Authoritative for: Machine vibration evaluation. Parts 1 to 5 are withdrawn and replaced by the matching ISO 20816 parts, so specify ISO 20816 where a part exists; the pump part (2009) stands.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 14001 ↗Paid
ISO
Document: standard · 2026; ed. 4
Status: current · as of
Authoritative for: Environmental management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 14040 ↗Paid
ISO
Document: standard · 2006 + Amd1:2020
Status: current · as of
Authoritative for: Life-cycle assessment.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 14067 ↗Paid
ISO
Document: standard · 2018; second edition in development (ISO/WD 14067.2)
Status: current · as of
Authoritative for: Product carbon footprint (quantification and communication); how IT-equipment footprints are assessed outside a building LCA.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 14520 ↗Paid
ISO
Document: standard · Part 1: 2023 (ed. 4); agent parts dated separately (e.g. Part 5: 2024, Part 17: 2022)
Status: varies by part · as of
Authoritative for: Gaseous (clean-agent) fire-extinguishing systems: design and installation; the international counterpart of NFPA 2001 (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC 17025 ↗Paid
ISO/IEC
Document: standard · 2017
Status: current · as of
Authoritative for: Testing and calibration laboratory competence.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 45001 ↗Paid
ISO
Document: standard · 2018 + Amd1:2024
Status: current · as of
Authoritative for: Occupational health and safety.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ANSI/TIA-607 ↗Paid
TIA
Document: standard · E (2024)
Status: current · as of
Authoritative for: Telecom bonding and grounding.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 80 ↗Paid
IEEE
Document: standard · 2013; incorporates Cor1:2015
Status: inactive-reserved · as of
Authoritative for: Substation grounding.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 81 ↗Paid
IEEE
Document: guideline · 2025 (supersedes IEEE 81-2012)
Status: current · as of
Authoritative for: Guide for measuring earth resistivity, ground impedance and earth surface potentials of a grounding system (Wenner four-pin surveys for grid design) (Chapter 4.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1100 ↗Paid
IEEE
Document: standard · 2005
Status: inactive-reserved · as of
Authoritative for: Equipment powering and grounding.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 142 ↗Paid
IEEE
Document: standard · 2007
Status: inactive-reserved · as of
Authoritative for: Industrial grounding.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 3003.1 ↗Paid
IEEE
Document: standard · 2019
Status: current · as of
Authoritative for: Grounding of industrial and commercial power systems.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1547 ↗Paid
IEEE
Document: standard · 2018 + 1547a:2020
Status: current · as of
Authoritative for: Distributed-energy interconnection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1668 ↗Paid
IEEE
Document: recommended practice · 2017
Status: active · as of
Authoritative for: Voltage-sag and short-interruption ride-through testing for end-use equipment below 1,000 V; the ride-through curve SPP's HILL requirement builds on (Chapter 4.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1584 ↗Paid
IEEE
Document: standard · 2018
Status: current · as of
Authoritative for: Arc-flash calculations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 2030.7 ↗Paid
IEEE
Document: standard · 2017
Status: current · as of
Authoritative for: Microgrid controllers.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 2030.8 ↗Paid
IEEE
Document: standard · 2018
Status: current · as of
Authoritative for: Microgrid-controller tests.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 242 ↗Paid
IEEE
Document: standard · 2001
Status: inactive-reserved · as of
Authoritative for: Industrial protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 2800 ↗Paid
IEEE
Document: standard · 2022
Status: current · as of
Authoritative for: Transmission-connected inverter resources.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 2883 ↗Paid
IEEE
Document: standard · 2022
Status: current · as of
Authoritative for: Storage sanitization.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 2883.1 ↗Paid
IEEE
Document: recommended practice · 2025
Status: active · as of
Authoritative for: Applying IEEE 2883 sanitization methods across provisioning, reuse, resale and disposal.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 3002.2 ↗Paid
IEEE
Document: standard · 2018
Status: current · as of
Authoritative for: Load-flow studies.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 3002.3 ↗Paid
IEEE
Document: standard · 2018
Status: current · as of
Authoritative for: Short-circuit studies.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 3004 ↗Paid
IEEE
Document: standard · Series; editions vary by part
Status: varies by part · as of
Authoritative for: Equipment protection.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 399 ↗Paid
IEEE
Document: standard · 1997
Status: inactive-reserved · as of
Authoritative for: Industrial power-system analysis.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 450 ↗Paid
IEEE
Document: standard · 2020
Status: current · as of
Authoritative for: Stationary lead-acid battery maintenance.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1188 ↗Paid
IEEE
Document: recommended practice · 2025
Status: active · as of
Authoritative for: VRLA battery maintenance and testing.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 519 ↗Paid
IEEE
Document: standard · 2022
Status: current · as of
Authoritative for: Harmonic control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE C57.110 ↗Paid
IEEE
Document: recommended practice · 2018
Status: active · as of
Authoritative for: Transformer capability under nonsinusoidal currents; apply its method to the transformer you are offered.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE PC57.110 ↗Access terms not published
IEEE
Document: revision project · PAR approved 2026-02-12
Status: active PAR; not a published replacement · as of
Authoritative for: Two-winding transformer scope; excludes rectifier transformers per the public project description. Draft clauses are not public.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE P80 ↗Access terms not published
IEEE
Document: guideline · PAR 2025-09-10; draft ID not public
Status: draft · as of
Authoritative for: Substation grounding revision.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO 20816 ↗Paid
ISO
Document: standard · Series; Part 1:2016
Status: varies by part · as of
Authoritative for: Machine vibration; select machinery part. Excludes floor/pipe-support limits.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ANSI/TIA-568 ↗Paid
TIA
Document: standard · Part 3 revision E (568.3-E)
Status: current · as of
Authoritative for: Structured cabling; 568.3 covers optical fiber components and polarity methods A, B, C, U1 and U2.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 9540A ↗Paid
UL Standards & Engagement
Document: standard · 6th ed. (2026-03-13)
Status: current · as of
Authoritative for: Thermal-runaway fire test for BESS, including the large-scale fire test (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 9540 ↗Paid
UL Standards & Engagement
Document: standard · 3rd ed. (2023-06-28); revised 2025-03-07
Status: current · as of
Authoritative for: Safety listing of a complete energy-storage system. A UL 9540A fire-test report is not a UL 9540 listing (Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 1449 ↗Paid
UL Standards & Engagement
Document: standard · 5th ed. (2021); ANSI-approved revision 2025-10-21
Status: current · as of
Authoritative for: North American surge-protective device standard. Its scope names AC and PV DC applications, so a non-PV 800 VDC SPD needs its own evaluation (Chapter 4.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 2877 ↗Paid
UL LLC (UL Solutions)
Document: specification · Outline of Investigation (Power Supplies, Medium Voltage); certification program launched 2026-09-24
Status: current · as of
Authoritative for: Power supplies with input above 1,000 V up to 38 kV; the basis for certifying medium-voltage solid-state power units. No certified product was named at launch (Chapter 4.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 4501 ↗Paid
UL LLC (UL Solutions)
Document: specification · Outline of Investigation; certification program launched 2026-09-29
Status: current · as of
Authoritative for: Direct-to-chip liquid-cooling parts (cold plates, manifolds, quick disconnects): coolant compatibility, pressure, leak integrity, durability, flow, interoperability (Chapter 5.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UL 2140 ↗Paid
UL LLC (UL Solutions)
Document: specification · Outline of Investigation, Edition 1 (2026-08-31)
Status: current · as of
Authoritative for: Factory-built prefabricated power-distribution assemblies, certified as a whole with factory follow-up (Chapter 6.4).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Data Center Facility, Energy sub-project; OCP Ready)
Document: report · Rev 1.0, Version 1.0 (January 2026)
Status: current · as of
Authoritative for: Data-center ESS requirements: BESS testing, detection, suppression, ventilation, lithium handling (Chapter 4.5; fire code in Chapter 6.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
US DOT PHMSA
Document: regulation · current eCFR
Status: current · as of
Authoritative for: Transportation of natural gas by pipeline: minimum federal safety standards; usually governs the operator's lateral and meter station (Chapter 4.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
US DOT PHMSA
Document: regulation · current eCFR
Status: current · as of
Authoritative for: LNG facilities that are part of a gas pipeline system; excludes LNG facilities used by an ultimate consumer (Chapter 4.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
efficiency metrics
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
ISO/IEC
Document: standard · 2016; ed. 2 project (AWI) under way
Status: current · as of
Authoritative for: KPI boundaries.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2026
Status: current · as of
Authoritative for: PUE.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2016
Status: current · as of
Authoritative for: Renewable energy factor.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2017 + Amd 1:2025
Status: current · as of
Authoritative for: Server energy efficiency.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2017 + Amd 1:2025
Status: current · as of
Authoritative for: Server utilization.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2021
Status: current · as of
Authoritative for: Energy reuse factor.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2023
Status: current · as of
Authoritative for: Cooling efficiency ratio.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2022
Status: current · as of
Authoritative for: Carbon usage effectiveness.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC
Document: standard · 2022
Status: current · as of
Authoritative for: Water usage effectiveness.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-1 ↗Paid
CENELEC / BSI
Document: standard · 2016
Status: current · as of
Authoritative for: KPI boundaries.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-2 ↗Paid
CENELEC / BSI
Document: standard · 2016 + A1:2019
Status: current · as of
Authoritative for: PUE; A1:2019 aligned it with the 2016 edition of ISO/IEC 30134-2.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-3 ↗Paid
CENELEC / BSI
Document: standard · 2016 + A1:2019
Status: current · as of
Authoritative for: Renewable energy factor.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-6 ↗Paid
CENELEC / BSI
Document: standard · 2020
Status: current · as of
Authoritative for: Energy reuse factor.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-7 ↗Paid
CENELEC / BSI
Document: standard · 2020
Status: current · as of
Authoritative for: Cooling efficiency ratio.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-8 ↗Paid
CENELEC / BSI
Document: standard · 2022
Status: current · as of
Authoritative for: Carbon usage effectiveness.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EN 50600-4-9 ↗Paid
CENELEC / BSI
Document: standard · 2022
Status: current · as of
Authoritative for: Water usage effectiveness.
Reach for it when: Specifying or checking requirements within this document’s boundary.
hardware and fabric specifications
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
OCP
Document: specification · 1.1
Status: current · as of
Authoritative for: Rack interface.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · Rev 1.0.0 (2026-06-12); Meta contribution
Status: current · as of
Authoritative for: In-rack AC-to-50 V power shelf: 1 OU, six 12 kW PSUs, 60 kW at N+1 on dual 230–277 V cords.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (2026-02-20); Meta contribution
Status: current · as of
Authoritative for: In-rack DC-to-48 V shelf for ±400 VDC input: 1 OU, six 18 kW PSUs, 100 kW input.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.1 (effective 2026-05-05)
Status: current · as of
Authoritative for: Wide-rack interface.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.1 (effective 2026-05-05)
Status: current · as of
Authoritative for: Meta wide-rack design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: guideline · 0.1
Status: draft · as of
Authoritative for: IT canister design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · Revision 1
Status: current · as of
Authoritative for: Cold-plate qualification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · Revision 2
Status: current · as of
Authoritative for: Cooling-loop qualification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (effective 2026-02-26)
Status: current · as of
Authoritative for: 2 MW row CDU design (Google contribution): 3 °C approach, 500 GPM, DI water or PG25. Design targets, not a vendor unit's rating.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · v2.0.0 (effective 2026-09-22)
Status: current · as of
Authoritative for: Hand-mate and blind-mate liquid couplers, sizes 02–08, single-phase water/glycol; consolidates and stays backward compatible with the v1 UQD and UQDB specifications.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (Steering Committee approval 2026-10-08; cover misprints 2024)
Status: current · as of
Authoritative for: NVIDIA's MGX Quick Disconnect, sizes 02–04, water/glycol: MGX 1.2's busbar coolant connection and fanless I/O bays (trays use UQD 2.0.0). Mates within the MQD family only.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: guideline · Revision 2.0, v1.0.0 (2026-09-15)
Status: current · as of
Authoritative for: PG25/PG55 fluid properties, wetted materials, filtration, flushing and in-use limits (Table 14). Replaces the 2022 guidance.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · v1.3 (effective 2026-08-06)
Status: current · as of
Authoritative for: Fresh-fluid limits and certificate of analysis for treated-water cold-plate coolants.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (effective 2026-09-03)
Status: current · as of
Authoritative for: Cold-plate qualification tests: leak, pressure decay, burst, thermal resistance, pressure drop, flatness, retention and temperature cycling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (effective 2026-02-02)
Status: current · as of
Authoritative for: Rope leak sensors: mechanical, signal interface, onboard power, firmware configuration and false-alarm reduction.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (2026-10-08); supersedes v0.7.0
Status: current · as of
Authoritative for: Sidecar power rack that takes AC and delivers differential 800 VDC (±400 VDC about a midpoint); rated 800 kW to 1.1 MW at 480 VAC.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · Rev 0.3.0 (effective 2026-06-22); Google, Microsoft, NVIDIA
Status: current · as of
Authoritative for: Black-box MV-to-800 VDC SST requirements: 5 MW at 13.8 kV, 5/10 MW at 34.5 kV; efficiency, grounding, overload and ride-through.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Data Center Facility, Power Distribution sub-project)
Document: report · v1.1.0 (2026-09-02); v1.0 2026-03-04
Status: current · as of
Authoritative for: LVDC distribution up to 1,500 VDC; proposes an 800 VDC voltage band with 840 VDC (U5) as the protection ceiling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · MGX 1.2, revision 1.2.0 (effective 2026-10-06); rev. 1.1 (2024-08-29) is the GB200 NVL72 contribution
Status: current · as of
Authoritative for: MGX rack/tray interfaces: ORV3-based 19-inch frame, 48 VDC liquid-cooled busbar to 5,000 A, racks to 250 kW. Excludes power shelves and CDUs; not fully compatible with rev. 1.1.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · v2.7 (revision 2025-10-24; document dated 2026-01-08); Meta, Microsoft, Google, HPE and Dell
Status: current · as of
Authoritative for: Hyperscaler requirements for PCIe NVMe SSDs beyond the NVMe standards: media-bytes-written (WAF), latency monitor, telemetry, firmware update; FDP optional (Chapter 9.3, 9.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · v1.1 (2024-11-14); Seagate contribution to the Composable Memory Systems sub-project
Status: current · as of
Authoritative for: Redfish APIs for composing pooled CXL memory regions from a Composable Memory Appliance; the CMS appliance charter targets under 400 ns round trip (Chapter 9.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
JEDEC (JC-45)
Document: standard · Version 1.00 (published June 2026)
Status: current · as of
Authoritative for: Electrical and mechanical requirements for LPDDR5/5X SOCAMM2 modules used as main memory in data-center and AI servers. Download needs registration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
JEDEC
Document: standard · Published 2025-04-16
Status: current · as of
Authoritative for: HBM4 device standard: 2,048-bit interface, 4- to 16-high stacks of 24 or 32 Gb dies (up to 64 GB per stack); Vera Rubin’s memory (Chapter 7.6). Download needs registration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
PCI Express Base Specification ↗Member access
PCI-SIG
Document: specification · 7.0 (2025-06-11); the first PCIe 6.0 enterprise SSDs entered volume production in 2026
Status: current · as of
Authoritative for: Host I/O link; 7.0 runs 128 GT/s PAM4 with FLIT encoding, up to 512 GB/s bidirectional at x16 (Chapter 9.3).
Reach for it when: Specifying or checking requirements within this document’s boundary.
CXL Consortium
Document: specification · 4.0 (2025-11-18)
Status: current · as of
Authoritative for: Cache-coherent memory and accelerator attach over PCIe signaling; 3.x added multi-host memory sharing, and 4.0 doubles the rate to 128 GT/s (Chapter 9.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: guideline · 1.2 (2025-08)
Status: current · as of
Authoritative for: Hardware security appraisal.
Reach for it when: Specifying or checking requirements within this document’s boundary.
CHIPS Alliance / OCP
Document: specification · 2.1; main spec v1.0
Status: current · as of
Authoritative for: Silicon root of trust.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (NVMe Project; reference code in CHIPS Alliance Caliptra)
Document: specification · 1.0 (2025-09); 1.1 at release candidate 4 (effective 2026-06-03)
Status: current · as of
Authoritative for: SSD media-encryption-key management on Caliptra: keys isolated from drive firmware; compatible with TCG Opal, Enterprise and Key Per I/O (Chapter 11.5).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.0.0 (2026-10-07); editors Intel and NVIDIA
Status: current · as of
Authoritative for: Host-to-BMC sideband (GPIO, I2C, UART, SPI, TPM, IPMI) as channels over one link such as USB; no native encryption, so use an SPDM session or channel protection (Chapter 11.4).
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · v0.96.0 (2026-10-09), for contribution to OCP; endpoint discovery deferred to the next version
Status: draft · as of
Authoritative for: Vendor-neutral fault management for CPUs, GPUs and accelerators: UEFI CPER error records and CPAD actions over Redfish, PLDM or other transports (Chapter 10.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Ultra Ethernet Consortium
Document: specification · 1.0 (2025-06-11)
Status: superseded · as of
Authoritative for: First public release of the Ethernet transport for AI/HPC.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Ultra Ethernet Consortium
Document: specification · 1.1 (2026-10-12)
Status: current · as of
Authoritative for: Ethernet transport for AI/HPC: Unified Local scale-up profile, in-network collectives, CSIG signaling, programmable congestion control; check which profiles a product supports.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IBTA InfiniBand Architecture Volume 1 ↗Member access
IBTA
Document: specification · Release 2.1
Status: current · as of
Authoritative for: Transport and architecture.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IBTA InfiniBand Architecture Volume 2 ↗Member access
IBTA
Document: specification · Release 2.1
Status: current · as of
Authoritative for: Physical links.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 802.3 ↗Free
IEEE
Document: standard · 2022
Status: current · as of
Authoritative for: Ethernet MAC and PHY.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 802.3df ↗Free
IEEE
Document: standard · 2024
Status: current · as of
Authoritative for: Ethernet high-speed PHY amendment.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE P802.3dj ↗Paid
IEEE
Document: standard · D3.3
Status: draft · as of
Authoritative for: Next Ethernet PHY amendment.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 802.1Qbb ↗Paid
IEEE
Document: standard · 2011
Status: superseded · as of
Authoritative for: Priority flow control. Folded into the 802.1Q bridging standard in 2014; 802.1Q-2022 is the current revision (Chapter 8.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 802.1Q ↗Free
IEEE
Document: standard · 2022 (approved 2022-09-21)
Status: current · as of
Authoritative for: Bridges and bridged networks; since the 2014 revision it carries priority flow control (formerly 802.1Qbb) and ETS (formerly 802.1Qaz) (Chapter 8.6).
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 1588 ↗Paid
IEEE
Document: standard · 2019
Status: current · as of
Authoritative for: Packet-network clock synchronization.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP (Time Appliances Project)
Document: report · v0.9.1 (2026-10-01)
Status: draft · as of
Authoritative for: Where shared time helps (observability, latency attribution, time-triggered functions) and where it does not (collective, checkpoint, causal-trace correctness); not a spec.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OIF 800ZR ↗Free
OIF
Document: specification · OIF-800ZR-01.0 (2024)
Status: current · as of
Authoritative for: Coherent optical interoperability.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink 200G ↗Free
UALink Consortium
Document: specification · 1.0
Status: current · as of
Authoritative for: Initial scale-up protocol.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink Common ↗Free
UALink Consortium
Document: specification · 2.0
Status: current · as of
Authoritative for: Common scale-up semantics.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink Consortium
Document: specification · 2.0
Status: current · as of
Authoritative for: Data-link and physical layers.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink Consortium
Document: specification · 1.0
Status: current · as of
Authoritative for: Data-link and physical layers.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink Chiplet ↗Free
UALink Consortium
Document: specification · 1.01
Status: current · as of
Authoritative for: Chiplet integration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 1.1.0 (effective October 2026; released 2026-10-09); 1.0.0 released 2026-02-10
Status: current · as of
Authoritative for: ISA-neutral chiplet types and inter-chiplet interfaces, with memory traffic over UCIe 1.1 streaming or BoW; compliance levels 0, 1 and full. Not a PHY or package spec.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OCP
Document: specification · 2.0 (2023-03-01)
Status: current · as of
Authoritative for: Open die-to-die chiplet PHY: slices, wires, modes and reach. The memory addendum and the transaction/link-layer spec are separate documents.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UCIe Consortium
Document: specification · 3.0 (2025-08-05)
Status: current · as of
Authoritative for: Die-to-die chiplet interconnect; 3.0 adds 48 and 64 GT/s, runtime recalibration and 100 mm sideband reach (Chapter 7.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
UALink Consortium
Document: specification · 1.0
Status: current · as of
Authoritative for: Fabric management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Open Compute Project
Document: specification · 1.0 (effective 2026-02-09; released 2026-03-10)
Status: current · as of
Authoritative for: Ethernet scale-up switch/network side; endpoint transport is SUE-T. ESUN 1.1 announced as close, not published.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Open Compute Project (contributors Broadcom, Arista)
Document: specification · 1.0.0 (effective 2026-10-08)
Status: current · as of
Authoritative for: Scale-up endpoint transport (load/store/atomics over ESUN, UEC UFH or UDP/IP); does not certify any XPU implementation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Open Compute Project (contributors Meta, Microsoft, Alibaba)
Document: specification · Revision 1.0.0 candidate (2026-09-13; 0.9.0 2026-08-06)
Status: draft · as of
Authoritative for: Switch platform management layer: power, hardware access, inventory, thermal, firmware recovery, diagnostics; in OCP Foundation review, not a published OCP spec.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE P802.1Qdw ↗Access terms not published
IEEE
Document: standard · PAR approved 2022-09-21; no draft produced; withdrawal requested 2026-03-05
Status: withdrawal requested · as of
Authoritative for: Source flow control project; no published standard. Successor: P802.1EJ Backward Notification (PAR approved 2026-09-25; ballot draft targeted 2028-07).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Individual authors; IETF Datatracker
Document: specification · draft-ravi-ippm-csig-01 (2024-02-02)
Status: historical · as of
Authoritative for: Expired 2024-08-05; experimental proposal, not an RFC. UE 1.1 (2026-10-12) now includes CSIG congestion signaling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OIF ELSFP 2.0 ↗Free
OIF
Document: specification · OIF-ELSFP-02.0 (2025-01)
Status: current · as of
Authoritative for: External laser interface; does not qualify optical-engine FRUs.
Reach for it when: Specifying or checking requirements within this document’s boundary.
OIF
Document: specification · OIF-CMIS-05.4 (May 2026)
Status: current · as of
Authoritative for: Host-to-module management for pluggable and on-board optics (QSFP-DD, OSFP), including VDM diagnostics such as media-side pre-FEC BER (Chapter 13.7).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Open CPX MSA (promoters Ciena, Coherent, Marvell, Molex, Samtec, TeraHop)
Document: specification · Rev 1.0 (approved 2026-09-16)
Status: current · as of
Authoritative for: Co-packaged/near-package socket and module: 6.4 or 7.2 Tb/s (32 or 36 × 212.5 Gb/s), internal or external laser; modules not expected to be hot-pluggable.
Reach for it when: Specifying or checking requirements within this document’s boundary.
UET 1.0.3 ↗Free
Ultra Ethernet Consortium
Document: specification · UE 1.0.3 transport layer (2026-07-16); superseded by UE 1.1 (2026-10-12)
Status: superseded · as of
Authoritative for: Transport portion of UE specification; profile support separately qualified.
Reach for it when: Specifying or checking requirements within this document’s boundary.
TIA FOTC
Document: report · Undated; IEEE 802.3bs-2017 application
Status: current · as of
Authoritative for: Four SMF lanes per direction; eight fibers; application note.
Reach for it when: Specifying or checking requirements within this document’s boundary.
TIA FOTC
Document: report · Undated; IEEE 802.3df-2024 application
Status: current · as of
Authoritative for: Eight SMF lanes per direction; sixteen fibers; application note.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE 802.3bs ↗Paid
IEEE
Document: standard · 2017; incorporated into IEEE 802.3-2022
Status: superseded · as of
Authoritative for: 200/400 Gb/s Ethernet amendment, including DR4.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEEE P802.3dv ↗Access terms not published
IEEE
Document: standard · PAR approved 2026-09-25; no draft yet
Status: draft · as of
Authoritative for: 400 Gb/s per lane signaling: electrical and SMF optical links to 500 m; no published standard.
Reach for it when: Specifying or checking requirements within this document’s boundary.
security and law
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
IEC 62443-3-3 ↗Paid
IEC / ISA
Document: standard · 2013
Status: current · as of
Authoritative for: Control-system security requirements.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC 27001 ↗Paid
ISO/IEC
Document: standard · 2022 + Amd 1:2024
Status: current · as of
Authoritative for: Information-security management.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ISO/IEC 42001 ↗Paid
ISO/IEC
Document: standard · 2023
Status: current · as of
Authoritative for: AI management system.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EU AI Act ↗Free
EU
Document: regulation · Regulation (EU) 2024/1689
Status: current · as of
Authoritative for: AI-system and GPAI obligations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
U.S. Copyright Office
Document: report · Copyright and Artificial Intelligence, Part 3: Generative AI Training (pre-publication version, 2025-05-09)
Status: draft · as of
Authoritative for: US agency analysis of fair use for AI training data, including acquisition from pirated sources; guidance, not binding law (Chapter 10.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NIS2 ↗Free
EU
Document: regulation · Directive (EU) 2022/2555
Status: current · as of
Authoritative for: Cybersecurity duties for in-scope entities.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EED ↗Free
EU
Document: regulation · Directive (EU) 2023/1791; Delegated Reg. (EU) 2024/1364
Status: current · as of
Authoritative for: Energy efficiency; data centers at ≥500 kW IT must report. Commission adopted rating-scheme act C(2026) 3472 on 2026-09-21; under Parliament and Council scrutiny, not in force.
Reach for it when: Specifying or checking requirements within this document’s boundary.
EnEfG ↗Free
Germany
Document: regulation · Act of 13 November 2023 (BGBl. 2023 I No. 309)
Status: current · as of
Authoritative for: German PUE, ERF and renewable-electricity duties (§11). Amendment bill Drs. 21/8027 (2026-09-16) pending, not enacted.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62443-2-1 ↗Paid
IEC
Document: standard · 2024; ed. 2.0
Status: current · as of
Authoritative for: IACS asset-owner security program.
Reach for it when: Specifying or checking requirements within this document’s boundary.
IEC 62443-3-2 ↗Paid
IEC
Document: standard · 2020; ed. 1.0
Status: current · as of
Authoritative for: IACS system-design risk assessment, zones and conduits.
Reach for it when: Specifying or checking requirements within this document’s boundary.
ASHRAE
Document: standard · ASHRAE 135-2024 (current; BACnet/SC added by Addendum 135-2016bj, approved 2019-11-18, consolidated in 135-2020)
Status: current · as of
Authoritative for: BACnet over WebSockets and TLS with device certificates (Chapter 11.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Modbus Organization
Document: specification · MB-TCP-Security v36 (2021-07-30)
Status: current · as of
Authoritative for: Modbus over TLS with X.509v3 certificates, port 802 (Chapter 11.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NIST SP 800-88 ↗Free
NIST
Document: guideline · Rev. 2 (2025-09); supersedes Rev. 1
Status: current · as of
Authoritative for: Media sanitization methods: Clear, Purge and Destroy (Chapter 14.9).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NERC CIP-002 ↗Free
NERC / FERC
Document: standard · CIP-002-5.1a in force; CIP-002-8 enforceable 2028-07-01
Status: current · as of
Authoritative for: Sorts BES Cyber Systems into high, medium and low impact, which decides how much of CIP-003 to CIP-013 and CIP-015 applies. CIP-014 sets its own scope (Chapter 4.3).
Reach for it when: Specifying or checking requirements within this document’s boundary.
AICPA
Document: guideline · 2017 criteria with revised points of focus (2022)
Status: current · as of
Authoritative for: Auditor attestation on a service organization’s controls (security, availability, processing integrity, confidentiality, privacy); an opinion, not a certification (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
GSA FedRAMP
Document: regulation · 20x Classes A–C open, Class D in Phase 4; new Rev5 applications close 2027-06-11
Status: current · as of
Authoritative for: US federal cloud-service authorization; 20x assesses automatable Key Security Indicators instead of a control-count package (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
US Department of War
Document: regulation · Program rule effective 2024-12-16; Phase II third-party certification suspended 2026-07-13
Status: current · as of
Authoritative for: Cybersecurity levels for defense contractors; Level 2 assesses the 110 NIST SP 800-171 Rev 2 requirements, and Phase I self-assessment still applies (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NIST SP 800-53 ↗Free
NIST
Document: guideline · Rev. 5, release 5.2.0 (2025-08-27)
Status: current · as of
Authoritative for: Security and privacy control catalog behind FedRAMP baselines and the SL3/SL5 model-weight proposals (Chapter 11.8).
Reach for it when: Specifying or checking requirements within this document’s boundary.
NIST
Document: guideline · 2.0 (CSWP 29, 2024-02-26)
Status: current · as of
Authoritative for: Six functions (Govern, Identify, Protect, Detect, Respond, Recover) for organizing a security program; incident-response guidance SP 800-61r3 maps onto them (Chapter 11.12).
Reach for it when: Specifying or checking requirements within this document’s boundary.
EU
Document: regulation · Regulation (EU) 2024/2847
Status: current · as of
Authoritative for: Products with digital elements: exploited-vulnerability and severe-incident reports from 2026-09-11 (24 h, then 72 h); most other duties from 2027-12-11 (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
ANSSI (France)
Document: certification scheme · Référentiel v3.2 (2022-03-08)
Status: current · as of
Authoritative for: French cloud qualification incl. immunity-from-non-EU-law criteria (ch. 19.6) (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
BSI C5 ↗Free
BSI (Germany)
Document: standard · C5:2026 (final, 2026-03; recommended for audit periods ending on or after 2027-06-01); C5:2020 until then
Status: current · as of
Authoritative for: Cloud Computing Compliance Criteria Catalogue; required for cloud processing of health/social data under §393 SGB V since 2024-07-01 (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
EUCS ↗Free
ENISA / European Commission (Cybersecurity Act)
Document: certification scheme · Candidate scheme
Status: draft · as of
Authoritative for: EU cloud certification scheme, not adopted; sovereignty criteria dropped in 2024 (Chapter 11.11).
Reach for it when: Specifying or checking requirements within this document’s boundary.
MITRE ATT&CK ↗Free
MITRE
Document: knowledge base · v20.0 (2026-10-13)
Status: current · as of
Authoritative for: Adversary tactics and techniques for enterprise IT (Chapter 11.12).
Reach for it when: Specifying or checking requirements within this document’s boundary.
MITRE
Document: knowledge base · ATT&CK v20.0 (2026-10-13; ICS domain)
Status: current · as of
Authoritative for: Industrial-control-system technique matrix (Chapters 11.10 and 11.12).
Reach for it when: Specifying or checking requirements within this document’s boundary.
MITRE ATLAS ↗Free
MITRE
Document: knowledge base · Data release v2026.09 (2026-09-15)
Status: current · as of
Authoritative for: Adversarial Threat Landscape for Artificial-Intelligence Systems: attacks on models and training pipelines (Chapter 11.12).
Reach for it when: Specifying or checking requirements within this document’s boundary.
Reference designs and platform documentation
Vendor material is authoritative about the vendor's own product and nothing else. The guide compares across vendors on fixed axes; when you have chosen one, its documentation governs the build.
Schneider Electric
Authoritative for: Engineered facility reference designs for AI halls (RD100, RD48 and successors) and a broad catalog of facility trade-off calculators: build vs colo, cooling architecture, economizer PUE by location, UPS economics, distribution efficiency.
Reach for it when: A bounded, engineered configuration to start from, and a calculator that matches the exact architectural fork you are weighing.
What this guide adds: Vendor-neutral comparison, the workload and economics context, and the register's dated provenance.
Vertiv
Authoritative for: Configured power, cooling and rack reference designs for named accelerator generations (GB300-class and beyond).
Reach for it when: The physical-infrastructure bill of materials for a named platform.
Eaton
Authoritative for: Electrical distribution, grid-interaction and modular power engineering material for high-density AI loads.
Reach for it when: Electrical product choices and the engineering behind them; separate the engineering papers from the marketing.
Complements Part 4
NVIDIA
Authoritative for: Rack, network, storage and management integration for a named generation; the executable basis for building and accepting an NVIDIA cluster.
Reach for it when: The supported topology, BOM and acceptance requirements once the platform is NVIDIA.
AMD
Authoritative for: Cluster design, networking with multiple fabric partners, BOMs, acceptance guidance and the facility interface for MI3xx platforms.
Reach for it when: The supported implementation once the platform is AMD; the counterpart to the SuperPOD guides.
Networking and fabrics
Part 8 is a map. These are the territory: firsthand production accounts, a peer-reviewed textbook, and the consortium specifications.
Pearson / Cisco Press (2026) — Subramaniam, Styszynski, Tambakuwala; technical reviewer credited
Authoritative for: Structured, vendor-agnostic AI networking education — scale-up and scale-out fabrics, transports, congestion control, optics, operations — with worked material and review questions.
Reach for it when: Learning AI networking properly, or checking Part 8 against a peer-reviewed treatment.
What this guide adds: The links from fabric decisions to cooling, power, procurement, commissioning and cost.
Complements Part 8
Meta
Authoritative for: A firsthand account of two 24k-GPU clusters, one RoCE and one InfiniBand, both tuned to equivalent performance on GenAI workloads — the primary evidence against any universal transport ranking.
Reach for it when: Whether Ethernet can carry your training workload, and what the tuning actually involved.
Energy, grid and flexibility
For demand forecasts, interconnection data and flexibility programs, go to the institutions that produce them. Part 3, 4 and 15 explain what they mean for a specific site.
International Energy Agency (2025 report; 2026 follow-up)
Authoritative for: Global data-center electricity demand scenarios, supply implications and methodology; the reference forecast most policy discussion cites.
Reach for it when: Demand-growth numbers you will be asked to defend; scenario ranges rather than a single trajectory.
Lawrence Berkeley National Laboratory
Authoritative for: Energy assessment tools, the US data-center energy report, and the annual Queued Up interconnection-queue dataset the guide's queue figures come from.
Reach for it when: The primary queue statistics and the methodology caveats that go with them.
EPRI DCFlex ↗Free + paid tiers
Electric Power Research Institute
Authoritative for: Applied research and utility demonstrations of data-center load flexibility, the utility-side view of curtailable interconnection.
Reach for it when: Turning a flexibility idea into a program a utility will recognise.
Sijbrandij Foundation
Authoritative for: A phased power co-development framework and a coalition directory for getting large loads energized faster.
Reach for it when: A structured process for the utility and generation conversations in Part 3.
Complements Part 3
Economics, benchmarks and market data
The guide's calculators are screening tools. These are the measured or modelled sources you underwrite against.
SemiAnalysis — research, InferenceX, ClusterMAX ↗Free + paid tiers
SemiAnalysis
Authoritative for: Original supply-chain (CoWoS, HBM), rack-teardown and fabric-economics research; InferenceX serving benchmarks by model, stack, precision and SLO; ClusterMAX GPU-cloud ratings. Institutional TCO models are licensed separately.
Reach for it when: Procurement or investment-grade economics, and measured serving envelopes instead of the guide's illustrative throughput constants.
What this guide adds: A common vocabulary across facilities and finance, and the register's separation of what is measured from what is modelled. About a tenth of the register's referenced claims cite SemiAnalysis — treat it as one evidentiary source, not a cross-check of itself.
Epoch AI
Authoritative for: A transparent 1 GW cost model with stated inputs, and a documented dataset of named clusters, hardware and milestones with explicit scope definitions.
Reach for it when: A cost-model boundary you can audit, and cluster facts with record-level provenance.
MLCommons
Authoritative for: Governed, reproducible performance (and optional power) measurements with rules, metadata and code links.
Reach for it when: Comparing accelerators within a benchmark's bounds before believing any vendor ratio, including the ones quoted here.
Microsoft Research · UT Austin (2026)
Authoritative for: An analytical model that treats hardware refresh as an optimisation variable across build, refresh and inference operations.
Reach for it when: Refresh and lifecycle economics beyond the fixed-exit-multiple screen in the project-finance calculator.
JLL · CBRE
Authoritative for: Regional vacancy, pricing, pipeline and lead-time conditions by market, published on a cadence.
Reach for it when: Market-specific availability and price before a siting decision; the guide's regional pages summarise, these are the source.
Whole-system reasoning and learning
If you want to understand why the machine behaves the way it does rather than what to buy, start here.
Barroso, Hölzle, Ranganathan — Google (2018)
Authoritative for: The original warehouse-scale-computer argument: co-design, cost models, failure handling and energy proportionality, from the people who ran it.
Reach for it when: Enduring architecture and economics reasoning; the component numbers are dated, the reasoning is not.
Google DeepMind authors (2025, revised online)
Authoritative for: Systems mathematics of training and inference: arithmetic intensity, parallelism, rooflines, KV-cache and batching, with derivations and exercises (TPU-centred, GPUs included).
Reach for it when: Any time the guide asserts a bandwidth-bound or compute-bound regime and you want the derivation.
Stanford University (Spring 2026)
Authoritative for: Hands-on implementation of the software stack this guide describes, with lectures, assignments and profiling exercises.
Reach for it when: Competence rather than orientation on Parts 9 and 10.
Various
Authoritative for: Structured education, supervised assessment and credentials (ATD, DCDC, CDCDP and others) with professional networks behind them.
Reach for it when: Developing a team; this guide is free pre-reading, not a credential.
Following the field
The numbers here move monthly. These are the original-reporting sources the register is checked against between publishes.
Data Center Dynamics ↗Free + paid tiers
DCD
Authoritative for: Daily project, facility, power and market reporting; DCD Academy courses.
Reach for it when: What happened this week; the register lags it by design.
Data Center Richness ↗Free + paid tiers
Substack newsletter
Authoritative for: Named-analyst commentary on facilities, investment and the operators building them.
Reach for it when: Perspective on the deals and developers behind the capacity numbers.
Primary sources
Authoritative for: The dated status of interconnection processes, alerts and rulemakings — the only correct source for 'where is Batch Zero this week'.
Reach for it when: Any process status you would put in a schedule; the guide records the sequence, the notice is the fact.
Missing something that belongs here? Tell us through the contact form. The bibliography behind individual figures lives on the register; Appendix E maps the learning and community landscape in more depth.