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
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.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
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.
Document: standard · Addendum 1; project
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.
Document: standard · 2024
Status: current · as of
Authoritative for: Facility design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2024
Status: current · as of
Authoritative for: Facility operations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
Document: standard · 2019
Status: current · as of
Authoritative for: Facility classification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2023
Status: current · as of
Authoritative for: Telecom cabling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: standard · 2021
Status: current · as of
Authoritative for: Facility classification.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2024
Status: current · as of
Authoritative for: Building construction.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2021
Status: current · as of
Authoritative for: Power distribution.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2021
Status: current · as of
Authoritative for: Environmental control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: specification · 2018
Status: current · as of
Authoritative for: Telecom cabling.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2024
Status: current · as of
Authoritative for: Physical security.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: standard · 2021
Status: current · as of
Authoritative for: Building construction.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: standard · 2019
Status: current · as of
Authoritative for: Environmental control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2021
Status: current · as of
Authoritative for: Physical security.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
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.
Document: guideline · 5th (2021)
Status: historical · 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.
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.
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.
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.
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.
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.
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.
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.
Document: guideline · 2010
Status: current · as of
Authoritative for: Energy measurement.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: guideline · 2011
Status: current · as of
Authoritative for: Efficiency practices.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: guideline · 2014
Status: current · as of
Authoritative for: PUE interpretation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
Document: guideline · 2019
Status: current · as of
Authoritative for: DCIM integration.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: standard · 2020
Status: current · as of
Authoritative for: Cooling-equipment rating tests.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
Document: guideline · 2025
Status: current · as of
Authoritative for: HVAC commissioning.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
Document: standard · 2026
Status: current · as of
Authoritative for: Electrical installations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Document: standard · Series; -1:2025 base
Status: varies by part · as of
Authoritative for: Low-voltage installations.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Document: standard · Series; editions vary by part
Status: varies by part · as of
Authoritative for: Machine vibration evaluation.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
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.
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 (4.10).
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: standard · 2017
Status: current · as of
Authoritative for: Microgrid controllers.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
Document: standard · 2022
Status: current · as of
Authoritative for: Storage sanitization.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
Document: standard · 2022
Status: current · as of
Authoritative for: Harmonic control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: recommended practice · 2018
Status: active · as of
Authoritative for: Transformer capability under nonsinusoidal currents; use the offered transformer and applicable method. Catalog scope opened; paid clauses are a separate access requirement.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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. Catalog opened; draft clauses not accessed, access terms not established.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
Document: standard · 2016
Status: current · as of
Authoritative for: KPI boundaries.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2026
Status: current · as of
Authoritative for: PUE.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
Document: standard · 2016
Status: current · as of
Authoritative for: KPI boundaries.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
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.
Document: specification · 1.0
Status: current · as of
Authoritative for: Wide-rack interface.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: specification · 1.0
Status: current · as of
Authoritative for: Meta wide-rack design.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
Document: specification · v0.7.0
Status: current · as of
Authoritative for: Sidecar rack and power base.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: specification · MGX rack/trays rev. 1.0
Status: current · as of
Authoritative for: NVIDIA MGX contributed rack/tray interfaces.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: specification · 2.0; 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.
Document: specification · 1.0
Status: superseded · as of
Authoritative for: Ethernet transport for AI/HPC.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: specification · 1.0.3
Status: current · as of
Authoritative for: Ethernet transport for AI/HPC.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
Document: standard · D3.2
Status: draft · as of
Authoritative for: Next Ethernet PHY amendment.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: standard · 2011
Status: superseded · as of
Authoritative for: Priority flow control.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
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.
Document: standard · PAR approved 2022-09-21; no current draft
Status: draft · as of
Authoritative for: Source flow control project; no published standard.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
Document: specification · UE 1.0.3 transport layer (2026-07-16)
Status: current · 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.
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.
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.
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.
Choose the applicable document and edition before writing acceptance criteria. Publication status does not establish local adoption or product compliance.
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.
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.
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.
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.
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.
Document: regulation · Directive (EU) 2023/1791
Status: current · as of
Authoritative for: Energy efficiency and reporting.
Reach for it when: Specifying or checking requirements within this document’s boundary.
Document: regulation · 13 November 2023
Status: current · as of
Authoritative for: German energy-efficiency duties.
Reach for it when: Specifying or checking requirements within this document’s boundary.
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.
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.
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.
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.
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.
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.
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.
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.
Part 8 is a map. These are the territory: firsthand production accounts, a peer-reviewed textbook, and the consortium specifications.
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.
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.
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.
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.
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.
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.
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.
The guide's calculators are screening tools. These are the measured or modelled sources you underwrite against.
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.
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.
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.
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.
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.
If you want to understand why the machine behaves the way it does rather than what to buy, start here.
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.
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.
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.
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.
The numbers here move monthly. These are the original-reporting sources the register is checked against between publishes.
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.
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.
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.