ISO/IEC 22237 — Data Center Infrastructure

ISO/IEC 22237
Accreditation Readiness

A complete, engineering-first approach to preparing your data center for ISO/IEC 22237 (Parts 1–7). Includes design review, documentation alignment, gap analysis, and pre-audit checkpoints.

ISO 22237 data center

Typical ISO-aligned facility with redundant infrastructure.

What is ISO/IEC 22237?

ISO/IEC 22237 is the global standard for the design, construction, power, cooling, cabling, security, and operation of data centers. It replaces the older EN 50600 framework and has become the most widely accepted benchmark for critical facility resilience, safety, and efficiency.

Unlike traditional engineering specifications, ISO/IEC 22237 evaluates how your facility truly performs: redundancy, maintainability, clear separation of power paths, environmental stability, structured cabling discipline, and operational maturity.

7-Part Framework

Covers facility, power, cooling, cabling, security, management and operations in a holistic way.

Vendor-Neutral

Independent of OEMs. Evaluates resilience and design quality — not product brands.

Globally Recognized

Accepted by hyperscalers, colocation providers, BFSI, telecom, and enterprise data centers.

Why ISO/IEC 22237 Matters

As digital infrastructure becomes mission-critical, this standard gives owners and operators a consistent way to evaluate resilience, safety, uptime tolerance, and operational maturity.

1. Proves Infrastructure Resilience

Clear criteria for redundancy (N, N+1, 2N), maintainability, segregation of paths, fault tolerance.

2. Strengthens Design Quality

Poor layouts, unsafe battery rooms, undersized cooling, and chaotic cabling are quickly exposed.

3. Standardizes Operations

Auditors look for logs, SOPs, PM schedules, change control, and evidence discipline.

4. Builds Customer Confidence

Demonstrates that your facility follows global best practices end-to-end.

ISO vs TIA-942 vs Uptime

ISO/IEC 22237 is often compared with TIA-942 and Uptime Tier certifications. Each serves a different purpose — and many facilities pursue more than one.

Framework Primary Focus What It Certifies Who Uses It
ISO/IEC 22237 Infrastructure + Operations Entire data center Enterprises, BFSI, Telecom, Colocations
TIA-942 Technical infrastructure Design + Facility Integrators, OEMs, Consultant-led projects
Uptime Tier Topology + Resilience Design or Facility Tier Hyperscalers, colocation operators

Note: NorthAudit is independent and vendor-neutral. No affiliation with ISO, TIA or Uptime.

Who Should Pursue ISO/IEC 22237?

ISO/IEC 22237 fits teams responsible for design, commissioning, compliance, and operations of critical digital infrastructure.

Data Center Owners

New builds, expansions, audits, and modernization.

MEP & ICT Consultants

Design alignment before installation or commissioning.

Operations Teams

Documentation, logs, evidence, and SOP discipline.

Project & PMO Teams

Alignment between vendors, integrators, and consultants.

Not sure how ISO 22237 applies to your facility?

Start with a quick 20-question check — aligned with Parts 1–7.

Free ISO/IEC 22237 Check → Compare ISO vs TIA vs Uptime →

ISO/IEC 22237 — Technical Breakdown

ISO/IEC 22237 is divided into seven tightly connected parts. Together, they form the world’s most comprehensive model for building and operating resilient data centers. Below is a practical, engineering-first breakdown of what each part covers — and what auditors look for.

Part 1 — General Concepts

Part 1 defines the entire backbone of ISO/IEC 22237. It sets the terminology, risk categories, classification concepts, and high-level design boundaries for the rest of the standard.

Key Themes

  • Defining availability classes
  • Risk profile of the site
  • Environmental & geographical considerations
  • Segregation of critical systems
  • Foundation for Parts 2–7

What Auditors Look For

  • Clear availability target (A1–A4)
  • Site risk study (flood, earthquake, proximity risks)
  • Documented resilience objectives
  • Logical separation of critical spaces

Example — Availability Classes (simplified)

A1: Basic availability
A2: Improved resilience
A3: High resilience (dual paths recommended)
A4: Fault tolerant (multiple independent systems)
    

Part 2 — Building Construction

This part deals with the physical structure of the data center — walls, floors, loading, fire zones, cable pathways, and separation of hazards.

Critical Engineering Areas

  • Fire rating of walls, doors, slabs
  • Raised floor loading & seismic stability
  • Pathway segregation (power vs data)
  • Battery room construction & ventilation
  • Leak containment zones

Common Non-Compliances

  • Shared pathways for power & fiber
  • Unsealed fire penetrations
  • Overloaded raised floors
  • UPS/Battery rooms without proper exhaust

Visual — Typical Separation Layout

+-----------------------+-----------------------+
| Power Pathway        | Data Pathway           |
| (UPS, Panels, Cabling)| (Fiber, Copper)       |
+-----------------------+-----------------------+
      

Part 3 — Power Distribution

The heart of ISO 22237. Covers redundancy, switching, segmentation, grounding, and fault containment.

Auditor Checklist

  • Dual power paths (A/B)
  • Redundancy class (N, N+1, 2N)
  • ATS/STS switching performance
  • Proper earthing & bonding
  • Short-circuit withstand levels

Non-Compliant Examples

  • Single-line power entry feeding both paths
  • No discrimination study
  • IT racks with single PDUs
  • Improper neutral bonding

Engineering Notes

ISO expects each power path to run independently. Cross-coupling is allowed only with proper interlocks.

  A-PATH                    B-PATH
+----------+          +----------+
| UPS A    |          | UPS B    |
| PDU A    |          | PDU B    |
| Rack PDU |          | Rack PDU |
+----------+          +----------+
    

Part 4 — Environmental Control (Cooling)

This part regulates cooling capacity, redundancy, containment, airflow, and control systems. A major cause of data center failures is cooling-related — ISO is very strict here.

What Auditors Check

  • N+1 cooling redundancy
  • CRAC/CRAH airflow direction & bypass control
  • Hot-aisle / cold-aisle containment
  • Chiller plant redundancy
  • Humidity & temperature stability

Common Failures

  • CRACs facing wrong direction
  • Mixed containment (partial hot/cold)
  • No bypass air control
  • Chilled-water loop without redundancy
  • Leaking or uncalibrated sensors
COLD AISLE → RACKS → HOT AISLE
 |                              |
CRAC/CRAH ← RETURN AIR ← HOT AISLE
      

Part 5 — Telecommunications Cabling

Covers structured cabling, pathways, fiber/copper segregation, redundancy, and labeling requirements.

Critical Checklist

  • Dual diverse fiber entry
  • Separate routing for A/B pathways
  • Labeling & color coding
  • Cable tray loading (40–60%)
  • No power in telecom pathways

Non-Compliant Signals

  • Fiber & power sharing trays
  • Improper bend radius
  • No labeling templates
  • Mixed cable types without separators

Part 6 — Security Systems

Part 6 ensures that the entire facility has a layered security model — physical, electronic, and procedural.

Required Controls

  • Multi-factor access control
  • CCTV with 90-day retention
  • Segregated zones (MZ, IAZ, CRZ)
  • Visitor logs & escort policy
  • Intrusion detection

Typical Gaps

  • Blind spots in CCTV
  • Shared access cards
  • No segregation between UPS & IT areas
  • Unsecured roof or external MEP access

Part 7 — Management & Operations

Arguably the toughest part. Even if your design is perfect, a weak operations program will fail the audit.

Required Documents

  • SOPs & EOPs
  • Change management register
  • Maintenance logs
  • Incident & RCA reports
  • Risk register

Evidence Expectations

  • Calibration certificates
  • Training logs
  • Shift handover records
  • Redundancy test logs

Audit Red Flags

  • Logs created just before the audit
  • No ownership of evidence items
  • Missing preventive maintenance
  • No RCA framework
Operations Quality = Evidence × Consistency × Ownership
    

How NorthAudit Runs ISO/IEC 22237 Readiness

Our ISO/IEC 22237 engagements are structured to minimise disruption while giving a very clear, clause-aligned picture of your current state, gaps and remediation path.

1 · Discovery

Scope, target availability class, current drawings, installed systems, and planned timelines.

2 · Document Intake

Collect key artefacts: layouts, SLDs, PM schedules, logs, SOPs, vendor submittals, test reports.

3 · Technical & Operational Review

Engineering review of infrastructure plus operations, mapped to Parts 1–7 of the standard.

4 · Scorecard, Gaps & Pre-Audit Pack

You receive a standards-mapped scorecard, gap list, closure plan and evidence pack structure.

Readiness Scorecard & Heatmap

Instead of a vague “pass/fail” view, we provide a clause-aligned scorecard where each domain is rated against ISO/IEC 22237 expectations. This helps management understand exactly where to invest effort.

Domain Coverage Readiness Band Typical Outputs
Facility & Building Parts 1–2 Green / Amber / Red Zoning, loading, fire separations, physical risks
Power & Earthing Part 3 Green / Amber / Red Redundancy map, discrimination gaps, resilience notes
Cooling & Environment Part 4 Green / Amber / Red Capacity vs IT load, containment, sensor placement
Cabling & Pathways Part 5 Green / Amber / Red Dual routes, loading, labeling, physical separation
Security & Access Part 6 Green / Amber / Red Zoning, CCTV coverage, access policy gaps
Operations & Evidence Part 7 Green / Amber / Red SOPs, logs, PM compliance, test documentation

Illustrative heatmap (simplified)

Domain                    Status
-----------------------------------------
Facility & Building       🟢 Green
Power & Earthing          🟠 Amber
Cooling & Environment     🟠 Amber
Cabling & Pathways        🔴 Red
Security & Access         🟢 Green
Operations & Evidence     🟠 Amber
    

Gap Classification Model

Not every gap is equal. We classify findings based on impact, likelihood and remediation effort, so you can decide where to act first without getting lost in a long list of observations.

Severity Description Typical Example Action Priority
Critical Immediate risk to uptime, safety or compliance. Single power path feeding both A/B PDUs, no redundancy test history. Fix before inviting any Certification Body.
Major Significant non-conformity; design or operations require change. Mixed cable routing, insufficient cooling redundancy, missing logs. Plan and close before audit date.
Minor Deviation that does not immediately threaten availability. Label inconsistencies, sub-optimal containment details. Address as part of continuous improvement.
Observation Improvement suggestion, often future-proofing. Optional monitoring points, more granular logs. Track in risk register or improvement backlog.
Priority = Severity × (Likelihood of Occurrence) × (Remediation Effort Weighting)
      

Documentation Master List (High-Level)

ISO/IEC 22237 certification is heavily evidence-driven. Below is a simplified view of the documentation set we expect a mature facility to maintain. During an engagement, we tailor this list to your scope, region and certification body.

Category Examples Linked Parts
Design & Layouts Architectural plans, SLDs, cabling schematics, rack layouts, airflow diagrams. Parts 1–5
Policies & SOPs Operations SOPs, EOPs, access policy, vendor policy, incident management. Part 7
Registers & Logs Risk register, PM logs, change log, incident log, shift handover records. Part 7
Testing & Commissioning FAT/SAT reports, integrated system testing records, redundancy test logs. Parts 2–4
Security & Access CCTV layout & retention policy, access reports, visitor logs, badge policy. Part 6
Compliance & Approvals Statutory approvals, OEM certifications, calibration certificates. Multiple parts

During a NorthAudit engagement, we provide a structured “evidence map” that links each document to specific clauses, so your team can respond faster when auditors ask “show me this”.

Design & MEP Review Scope

We combine ISO clause-level review with practical MEP and ICT engineering checks. The goal is to find issues on drawings and installed infrastructure before an external auditor or a live incident discovers them.

Power & Earthing

  • SLDs, breaker sizing & discrimination
  • Generator–UPS–PDU path review
  • Earthing topologies, bonding and touch voltages

Cooling & Environment

  • Chiller/CRAC capacities & redundancy
  • Containment, airflow & return paths
  • Environmental monitoring placement

Cabling & White Space

  • Pathway separation and loading
  • Rack layout, U-space planning, density
  • Patch management practices

Operations & Evidence Checklist (Summary)

The most common reason facilities struggle in ISO/IEC 22237 audits is not design — it is day-to-day operations and missing evidence. We help your team build a realistic, sustainable evidence routine.

Daily / Weekly Evidence

  • Shift logs and handover notes
  • Basic patrol checklists (room status)
  • Alarm & event acknowledgement records
  • Physical access reports (exceptions flagged)

Monthly / Quarterly Evidence

  • Preventive maintenance logs (with sign-off)
  • Redundancy test records (genset, UPS, chillers)
  • Calibration certificates of critical sensors
  • Updated risk register and mitigation actions
Strong audit performance rarely comes from last-minute preparation.
It comes from small, consistent, well-documented actions across the year.
    

Want a clause-aligned ISO 22237 readiness score?

Share your drawings and key documents. We’ll revert with a structured view of strengths, gaps and next steps.

Why NorthAudit for ISO/IEC 22237 Readiness

ISO/IEC 22237 readiness is a specialised discipline. It requires deep engineering context, an operator’s mindset, and familiarity with how Certification Bodies interpret the standard. We bridge all three.

Engineering-First Approach

We review chillers, UPS systems, cable pathways, switching logic, and layouts with the same seriousness as documentation. This is not a paperwork-only engagement.

Clause-Level Mapping

Every gap, recommendation, and remediation action is linked to a clause in Parts 1–7. This removes ambiguity and accelerates audit approvals.

Auditor-Grade Evidence Packs

Policies, SOPs, logs, templates, risk registers and test records are structured exactly how Certification Bodies expect to see them — saving days of back-and-forth.

Most importantly, we operate independently — no vendor influence, no certification sales, no hidden agenda. The only goal is clear, practical, verifiable alignment with ISO/IEC 22237.

ISO/IEC 22237 — Frequently Asked Questions

Do we need all seven parts for certification?

Yes. ISO/IEC 22237 certification covers the full set (Parts 1–7). However, your scope may exclude certain spaces (e.g., non-critical rooms), which we clarify during discovery.

Is ISO/IEC 22237 the same as EN 50600?

ISO/IEC 22237 is the internationalised version of EN 50600 — with alignment between both. Many European facilities start with EN 50600 and transition to ISO for global acceptance.

How long does readiness typically take?

For a live facility with moderate complexity: 4–6 weeks. For new builds under commissioning: 6–12 weeks. The timeline depends primarily on documentation and closure effort.

Can we skip some evidence if systems are new?

No. New systems still require logs, test records, calibration certificates, and commissioning packages. ISO focuses on evidence, not age of equipment.

Will you represent us during the audit?

Yes. We brief Certification Bodies and remain available throughout audit week for clarifications, evidence coordination and technical guidance.

Do you engage with OEMs on our behalf?

Only when required (e.g., to close documentation gaps or obtain certifications). All engagement is vendor-neutral.

Ready to prepare your facility for ISO/IEC 22237?

Start with a free checklist, or share your drawings and policies for a structured readiness assessment.

Start with Free ISO/IEC 22237 Checklist → Send Your Scope → Compare ISO, TIA & Uptime →

More Resources