Study guide
2.2 ANSI/BICSI 002 Availability and Reliability Classifications (Class 0 through Class 4)
BICSI DCDC Data Center Design Consultant
Track your progress as you read
Finished sections get a check mark.
1 Introduction
About the BICSI DCDC Exam (DCDC-004)
2 Chapter 1: Project Initiation & Design Requirements
1.1 Owner's Project Requirements (OPR) and Basis of Design (BOD) 1.2 Stakeholder Coordination and Needs Assessment 1.3 Applicable Codes, Standards, and Regulatory Frameworks
3 Chapter 2: Data Center Models & Reliability Classifications
2.1 Data Center Business Models: Enterprise, Colocation, Cloud, Edge, and Modular 2.2 ANSI/BICSI 002 Availability and Reliability Classifications (Class 0 through Class 4) 2.3 Comparative Reliability Frameworks: Uptime Institute Tiers and TIA-942 Ratings
4 Chapter 3: Site Selection & Environmental Feasibility
3.1 Geographic and Environmental Risk Assessment 3.2 Proximity Hazards, Flight Paths, EMF, and Vibration Analysis 3.3 Utility Infrastructure Assessment 3.4 Site Access, Zoning, Permitting, and Physical Boundary Constraints 3.5 Site Research, Site Surveys, and Multi-Site Evaluation 3.6 Site Selection Financial Analysis, Incentives, and the Feasibility Report
5 Chapter 4: Capacity Planning, Financial Modeling & Risk Assessment
4.1 IT Load Forecasting and Power/Cooling Density Projections 4.2 Financial Modeling: CapEx, OpEx, Total Cost of Ownership (TCO), and ROI 4.3 Efficiency Metrics: PUE, WUE, CUE, and Energy Star Benchmarking 4.4 Risk Assessment Methodologies: Single Points of Failure, Fault Trees, and Reliability Calculations
6 Chapter 5: Architectural Spaces & Structural Layout
5.1 Structural Requirements: Floor Loading, Ceiling Clearances, and Seismic Bracing 5.2 Data Center Spatial Allocation: Computer Room and Support Spaces 5.3 Raised Floor Systems, Airflow Management Tiles, Slab Floors, Ramps, and Airlock Vestibules 5.4 Personnel Requirements, Support Space Adjacencies, and Circulation
7 Chapter 6: Mechanical Cooling & Thermal Management
6.1 Heat Load Calculations: Sensible vs Latent Heat and Refrigeration Capacity 6.2 Cooling Technologies: DX, Chilled Water, Evaporative, and Economizers 6.3 Airflow Containment Strategies: Hot/Cold Aisle, CAC vs HAC, and Airflow Management 6.4 Environmental Criteria and Close-Coupled/Liquid Cooling: ASHRAE TC 9.9, In-Row, RDHx, and Liquid/Immersion
8 Chapter 7: Electrical Distribution & Power Conditioning
7.1 Utility Service Entrance, Transformers, Switchgear, and Transfer Switches 7.2 Standby and Emergency Generator Systems: Fuel Systems, Paralleling Switchgear, and Load Testing 7.3 Uninterruptible Power Supply Systems, Battery Chemistries, and Runtime Sizing 7.4 Power Distribution Architectures, Redundancy Topologies, and Earthing/Bonding
9 Chapter 8: IT Infrastructure & Network Topologies
8.1 Server, Compute, and Storage Architectures: EIA-310, Blade, and Hyperconverged Systems 8.2 Network Topologies: Traditional 3-Tier vs Spine-Leaf Clos Architecture 8.3 Switching Architectures: Top-of-Rack, Middle-of-Row, and End-of-Row
10 Chapter 9: Fire Protection & Building Automation Systems
9.1 Fire Detection Systems: High-Sensitivity Smoke Detection (HSSD/VESDA) and Multi-Criteria Sensing 9.2 Fire Suppression Systems: Clean Agents and Pre-Action Sprinklers 9.3 Room Integrity, Pressure Relief Venting, and Enclosure Testing 9.4 Building Automation Systems, Environmental Monitoring, and DCIM
11 Chapter 10: Communications Connectivity & Structured Cabling
10.1 Structured Cabling Standards and Functional Spaces per ANSI/BICSI 002 and TIA-942 10.2 Transmission Media: Balanced Twisted-Pair Copper and Optical Fiber 10.3 High-Density Optical Fiber Connectivity, Multi-Fiber Push-On (MPO/MTP), and Polarity Methods 10.4 Cable Pathways, Cable Trays, Fill Ratios, Bend Radius, and Separation from Power 10.5 Site Communications Requirements, Access Provider Diversity, and RCDD Coordination
12 Chapter 11: Operational Procedures & Maintenance Programs
11.1 Operational Documentation: Standard Operating Procedures, Methods of Procedure, and Emergency Operating Procedures 11.2 Change Management and Configuration Management Processes 11.3 Maintenance Strategies: Preventive, Predictive, and Corrective Maintenance 11.4 Data Center Assessments: Optimization Studies, Current-State Evaluation, and the Findings Report
13 Chapter 12: Capacity, Lifecycle & Safety Management
12.1 Continuous Capacity Management: Space, Power, Cooling, and Network Utilization 12.2 Equipment Lifecycle, Asset Tracking, and Decommissioning Workflows 12.3 Electrical Safety, Arc Flash Hazards (NFPA 70E), Lockout/Tagout, and Live Work
14 Chapter 13: Concentric Physical Security & Access Control
13.1 Layered Defense-in-Depth Architecture: Perimeter, Facility, Internal, Whitespace, and Cabinet Levels 13.2 Physical Barriers, Fencing, Gates, Bollards (ASTM Crash Ratings), and Vehicle Mitigation 13.3 Electronic Access Control Systems, Mantraps, Anti-Tailgating, and Biometric Authentication
15 Chapter 14: Surveillance, Threat Assessment & Disaster Recovery
14.1 Video Surveillance Systems: Camera Siting, Resolution, Lighting, and Retention Policies 14.2 Threat and Vulnerability Assessments, Insider Threat Mitigation, and Physical Security Audits 14.3 Disaster Recovery and Business Continuity: RPO, RTO, and Backup Site Topologies 14.4 Security Audits, Verification of Findings, Countermeasure Selection, and Cost-Benefit Analysis
16 Chapter 15: Construction Administration & Project Delivery
15.1 Project Delivery Methods and Procurement Strategies for Mission-Critical Facilities 15.2 Construction Administration: Submittal Reviews, Requests for Information, and Change Orders 15.3 Field Observation, Quality Assurance/Quality Control, Punch Lists, and Record Documentation
17 Chapter 16: Data Center Commissioning & Integrated Systems Testing
16.1 Commissioning Process, Standards, and Levels 1 through 3: Factory Testing to Component Startup 16.2 Level 4 Functional Performance Testing of Mechanical and Electrical Subsystems 16.3 Level 5 Integrated Systems Testing, Black Start, and Operational Turnover
2.2 ANSI/BICSI 002 Availability and Reliability Classifications (Class 0 through Class 4)
Key Takeaways Explain This Topic AI
ANSI/BICSI 002 selects one of five Availability Classes (0 through 4) in four steps: operational level (annual hours available for planned maintenance shutdown), operational availability rating (allowable annual downtime), impact of downtime (Isolated to Catastrophic), and the resulting Class matrix.
Class 2 facilities provide component redundancy ( N + 1 N+1 N + 1 ) across active equipment but utilize a single distribution path, meaning routine maintenance on distribution switchgear or piping requires an operational shutdown.
Class 3 establishes Concurrent Maintainability through independent redundant pathways, guaranteeing that any active component, breaker, transformer, or chilled water pipe can be removed from service without dropping the critical IT load.
Class 4 achieves autonomous Fault Tolerance through 2 N 2N 2 N or 2 ( N + 1 ) 2(N+1) 2 ( N + 1 ) active distribution topologies and strict physical compartmentalization, preventing any single worst-case unplanned failure from disrupting operations.
Last updated: October 2026
2.2 ANSI/BICSI 002 Availability and Reliability Classifications (Class 0 through Class 4)
The design of a mission-critical data center requires balancing operational risk against engineering cost. Under ANSI/BICSI 002 ( Data Center Design and Implementation Best Practices ), facility availability and reliability are categorized into five Availability Classes : Class 0, Class 1, Class 2, Class 3, and Class 4 . The standard deliberately avoids the word "tier," and it applies the same 0 to 4 scale to sub-groups: facility systems (Class F0 to F4), cable plant (C0 to C4), network infrastructure (N0 to N4), data processing and storage (S0 to S4), and applications (A0 to A4).
A fundamental strength of the ANSI/BICSI 002 standard is its multidisciplinary methodology. Unlike frameworks that focus strictly on electrical and mechanical equipment, ANSI/BICSI 002 applies availability criteria across all physical domains: architectural, structural, electrical, mechanical, telecommunications cabling, fire protection, and electronic security. A facility with a fault-tolerant electrical plant remains vulnerable if its telecommunications pathways share a single outside plant trench or if its cooling system cannot withstand routine pipe maintenance.
Determining the Availability Class: The Four-Step Method
ANSI/BICSI 002 (Appendix B) does not start from a topology. It starts from the owner's operational facts and quantifies three factors, then combines them.
Step 1: Operational level. How many hours per year can the IT functions be shut down for planned maintenance?
- Operational Level Annual Hours Available for Planned Maintenance Shutdown Operating Profile
- 0 More than 400 Less than 24 hours a day, less than 7 days a week
- 1 100 to 400 Less than 24 hours a day, less than 7 days a week
- 2 50 to 99 Up to 24 x 7, up to 50 weeks per year
- 3 0 to 49 24 x 7 for 50 weeks or more; no maintenance downtime during working hours
- 4 0 24 x 7 x 52 weeks; no scheduled maintenance downtime
Step 2: Operational availability rating. Index the operational level against the allowable maximum annual downtime:
Operational Level More than 5,000 min (below 99%) 500 to 5,000 min (99% to 99.9%) 50 to 500 min (99.9% to 99.99%) 5 to 50 min (99.99% to 99.999%) 5 min or less (99.999% or more)
- Level 0 0 0 1 2 2
- Level 1 0 1 2 2 2
- Level 2 1 2 2 2 3
- Level 3 2 2 2 3 4
- Level 4 3 3 3 4 4
Step 3: Impact of downtime. Classify the consequence as Isolated (single function, non-critical objectives), Minor (single site or minor delay to key objectives), Major (regional, part of the enterprise), Severe (multiregional, major portion of the enterprise), or Catastrophic (service quality across the entire enterprise).
Step 4: Availability Class. Combine the rating with the impact:
- Impact of Downtime Rating 0 Rating 1 Rating 2 Rating 3 Rating 4
- Isolated Class 0 Class 0 Class 1 Class 3 Class 3
- Minor Class 0 Class 1 Class 2 Class 3 Class 3
- Major Class 1 Class 2 Class 2 Class 3 Class 3
- Severe Class 1 Class 2 Class 3 Class 3 Class 4
- Catastrophic Class 1 Class 2 Class 3 Class 4 Class 4
Worked example: A claims-processing platform runs 24 x 7 for 51 weeks and allows 30 hours of planned shutdown per year (Level 3). The business can tolerate up to 200 minutes of total downtime per year (the 50 to 500 minute column), giving an operational availability rating of 2. An outage would disrupt several regions (Severe). Rating 2 + Severe = Class 3 . Only a Catastrophic impact at rating 3 or higher, or a Severe impact at rating 4, leads to Class 4.
Each Class is then delivered through four areas of concern: component redundancy, system redundancy, quality (standard commercial for Class 0/1, premium quality components from Class 2, and for Class 4 different lots, models, or manufacturers to avoid common faults), and survivability (hardening against physical forces, security breaches, and natural disasters).
The Five ANSI/BICSI 002 Availability Classes Class 0: No Supplementary Equipment (Single Path, No Alternate Power Source)
- Class 1: Basic Capacity (Single Path, N Capacity, Planned Maintenance Downtime)
- Class 2: Redundant Components (Single Path, N+1 Components, Path Maintenance Downtime)
- Class 3: Concurrently Maintainable (Dual Paths, N+1 Capacity, No Downtime on Planned Maintenance)
- Class 4: Fault Tolerant (Dual Active Paths, 2N or 2(N+1), Autonomous Fault Isolation)
- Class 0: Basic Infrastructure (No Redundancy)
Objective: Support the basic requirements of the IT functions without supplementary equipment; capital cost avoidance is the main driver.
Topology: A single distribution path without an alternate power source (no standby generator). Class F0 may also lack a UPS or proper IT equipment grounding, so it has multiple single points of failure.
Operational Impact: A failure of any component, power feed, cooling unit, or network link causes immediate downtime. Routine maintenance requires taking the critical load offline.
Application: General office server rooms, network closets, development and test laboratories, and non-critical data processing where downtime of hours or even days has little impact on the mission.
Class 1: Single Path, Basic Capacity
Topology: Single distribution path with dedicated capacity components ( N N N ) sized to support 100% of the critical IT load.
Electrical and Mechanical Infrastructure: Includes a basic uninterruptible power supply (UPS) system and standby generator, but contains no redundant capacity components (no spare UPS module, no spare generator, no standby chiller).
Operational Impact: The facility is vulnerable to disruptions caused by equipment failure. Performing routine maintenance on major equipment (e.g., servicing the primary UPS inverter, overhauling generator switchgear, or flushing chiller heat exchangers) requires a complete facility shutdown.
Risk Profile: High risk of downtime from planned and unplanned events, but remedial maintenance can be performed during nonscheduled hours.
Class 2: Single Path with Component Redundancy
Topology: Single distribution path with redundant active capacity components ( N + 1 N+1 N + 1 ).
Electrical and Mechanical Infrastructure: Features redundant capacity units, such as an N + 1 N+1 N + 1 modular UPS array, an additional backup diesel generator, and N + 1 N+1 N + 1 computer room air handler (CRAH) units or water chillers.
The Distribution Bottleneck: While an individual component failure (e.g., a single UPS module tripping offline or a cooling pump bearing failure) will not disrupt the load, the facility relies entirely on a single distribution pathway (single main switchboard, single utility transformer, single feeder busway, and single chilled water supply/return header).
Operational Impact: Routine servicing of redundant components can occur online. However, servicing or repairing any element of the distribution path—such as thermal scanning and torquing busway joints, replacing a main circuit breaker, or repairing a chilled water supply header—requires dropping the critical load.
Risk Profile: Moderate risk of downtime from planned and unplanned events; redundancy and premium quality are applied to the parts most likely to fail (UPS, controls, cooling, generators, transfer switches, and outside services such as access provider circuits).
Class 3: Concurrently Maintainable
Topology: Multiple distribution paths with redundant capacity components ( N + 1 N+1 N + 1 ), configured such that one distribution path is active while an alternate or standby path is available, or dual paths operate simultaneously with N + 1 N+1 N + 1 capacity.
Core Engineering Principle: Concurrent Maintainability . Every capacity component (transformer, generator, UPS, battery string, chiller, cooling tower, pump) and every distribution element (switchboard, feeder conduit, busway, power distribution unit [PDU], pipe segment, and isolation valve) can be isolated, removed, serviced, repaired, or replaced on a planned basis without interrupting the critical IT load .
Operational Impact: Planned maintenance never requires taking the data center offline. However, Class 3 systems are not fully fault tolerant . If an unplanned equipment failure or operational error occurs on the active path while the alternate path is disassembled for scheduled maintenance, the critical IT load may experience an outage.
Risk Profile: Maintenance and repair are performed during full production time with no opportunity for curtailed operations; the design adds reliability against natural and human-caused disasters, planned maintenance, and repair activities.
Class 4: Fault Tolerant
Topology: Multiple active, independent, physically segregated distribution paths configured as 2 N 2N 2 N or 2 ( N + 1 ) 2(N+1) 2 ( N + 1 ) systems.
Core Engineering Principle: Fault Tolerance . The infrastructure must detect, isolate, and withstand any single worst-case unplanned equipment failure, distribution fault, control failure, or single operational mishap without impacting the critical IT load. In addition, the facility provides concurrent maintainability across all systems.
Key Architectural and Control Requirements:
Automation and Staffing: All recognizable single points of failure from the utility connection to the critical load are eliminated. Systems are typically automated (intelligent controls, zone-selective interlocking, selective coordination) to reduce the chance of human error, and the facility is staffed 24/7 with rigorously trained personnel.
Physical Compartmentalization: Compartmentalization and fault tolerance are prime requirements. Path A and Path B equipment is separated into independent fire-rated compartments so that a fire, arc flash, battery thermal runaway, or pipe rupture in Room A cannot propagate into or contaminate Room B.
Continuous Cooling: UPS-backed pumps, fans, and controls, often combined with thermal energy storage (TES), are common tactics to prevent whitespace thermal runaway while chillers restart after a utility loss.
Quality and Survivability: Premium components (different lots, models, or manufacturers to avoid common faults or recalls), and systems that are self-supporting in any event and protected against the highest levels of natural forces.
Multidisciplinary Requirements Across Availability Classes
The following matrix summarizes typical design tactics associated with each Class. ANSI/BICSI 002 states the exact requirements in its electrical (F), mechanical (F), cabling (C), and network (N) class tables, so treat this as a study aid rather than a checklist:
Subsystem Domain Class 1 (Basic) Class 2 (Redundant Components) Class 3 (Concurrently Maintainable) Class 4 (Fault Tolerant)
Electrical: Topology Single Path ( N N N ) Single Path ( N + 1 N+1 N + 1 ) Dual Paths (1 Active, 1 Alternate, or Dual Active N + 1 N+1 N + 1 ) Dual Active Paths ( 2 N 2N 2 N or 2 ( N + 1 ) 2(N+1) 2 ( N + 1 ) )
Electrical: Generators Single generator ( N N N ) Redundant generators ( N + 1 N+1 N + 1 ) Redundant generators ( N + 1 N+1 N + 1 ) with dual distribution Independent generator plants ( 2 N 2N 2 N or 2 ( N + 1 ) 2(N+1) 2 ( N + 1 ) ) in separate enclosures
Electrical: UPS Architecture Single standalone UPS module ( N N N ) Parallel redundant UPS ( N + 1 N+1 N + 1 ) on single bus Dual path distribution to dual-corded IT equipment Completely independent 2 N 2N 2 N UPS plants with static transfer switches for legacy single-cord IT
Mechanical: Cooling Equipment Single DX unit or chiller ( N N N ) Redundant cooling units ( N + 1 N+1 N + 1 ) Redundant cooling units ( N + 1 N+1 N + 1 ) with dual distribution loops True 2 N 2N 2 N cooling systems with automated isolation valving
Mechanical: Piping Architecture Single supply/return pipe loop Single supply/return pipe loop Looped or dual piping with sectionalizing isolation valves Dual independent, physically separated piping loops (Run A / Run B)
Mechanical: Thermal Ride-Through None None Considered for high-density loads Continuous cooling (UPS-backed pumps and controls, often with thermal storage)
On-Site Supply (fuel, water; Table 5-3) 8 hours (none required for F0) 24 hours 72 hours 96 hours
Telecom: Access Providers One service feed Service from two or more access provider central offices recommended Diverse service feeds from different central offices Diverse feeds from different central offices with redundant entrance rooms
Telecom: Pathway Diversity Single pathway/trench Single pathway/trench Diverse outside plant (OSP) pathways separated by at least 20 m (66 ft) Diverse OSP pathways, redundant main distribution, and redundant backbone paths
Architectural: Compartmentalization Standard commercial building shell Dedicated equipment room Segregated mechanical and electrical rooms Separate fire/blast-rated rooms for Path A and Path B equipment
Engineering Calculations: Availability and Annual Downtime
In mission-critical engineering, availability is defined mathematically as the steady-state probability that a system is operating satisfactorily when required for use.
Mathematical Formulation
Availability ( A A A ) is calculated as a function of Mean Time Between Failures (MTBF) and Mean Time To Repair (MTTR) :
A = MTBF MTBF + MTTR A = \frac{\text{MTBF}}{\text{MTBF} + \text{MTTR}} A = MTBF + MTTR MTBF
Where:
MTBF represents the average operational operating hours between unscheduled system breakdowns.
MTTR represents the average time in hours required to identify, isolate, repair, and restore the failed system to full operation.
To translate mathematical availability into expected operational impact, annual downtime in minutes is computed across a standard calendar year (365 days × \times × 24 hours × \times × 60 minutes = 525,600 minutes/year):
Annual Downtime (minutes) = ( 1 − A ) × 525 , 600 \text{Annual Downtime (minutes)} = (1 - A) \times 525,600 Annual Downtime (minutes) = ( 1 − A ) × 525 , 600
Quantitative Benchmarking Across Availability Levels
Availability Level Terminology Decimal Availability Annual Downtime (Minutes) Annual Downtime (Hours)
99.0 % 99.0\% 99.0% "Two Nines" 0.990 0.990 0.990 5 , 256.0 min 5,256.0\text{ min} 5 , 256.0 min 87.6 hours 87.6\text{ hours} 87.6 hours
99.9 % 99.9\% 99.9% "Three Nines" 0.999 0.999 0.999 525.6 min 525.6\text{ min} 525.6 min 8.76 hours 8.76\text{ hours} 8.76 hours
99.99 % 99.99\% 99.99% "Four Nines" 0.9999 0.9999 0.9999 52.56 min 52.56\text{ min} 52.56 min 0.876 hours 0.876\text{ hours} 0.876 hours ( ≈ 53 min \approx 53\text{ min} ≈ 53 min )
99.999 % 99.999\% 99.999% "Five Nines" 0.99999 0.99999 0.99999 5.256 min 5.256\text{ min} 5.256 min 0.0876 hours 0.0876\text{ hours} 0.0876 hours ( ≈ 5.3 min \approx 5.3\text{ min} ≈ 5.3 min )
99.9999 % 99.9999\% 99.9999% "Six Nines" 0.999999 0.999999 0.999999 0.526 min 0.526\text{ min} 0.526 min ≈ 31.5 seconds \approx 31.5\text{ seconds} ≈ 31.5 seconds
Note that a BICSI Class is not a guaranteed availability percentage. The legacy figures often quoted for Uptime Institute tiers (99.671%, 99.741%, 99.982%, 99.995%) are not ANSI/BICSI 002 values. Availability also depends on operations, so the standard's downtime bands are inputs to the Class selection rather than outputs of a topology.
- Practical Design Scenarios and Exam Traps
- The "Redundant Components on a Common Bus" Fallacy
A frequent error on data center design projects—and a staple examination trap—is misclassifying an N + 1 N+1 N + 1 system as concurrently maintainable. Consider an electrical topology featuring three 500 kVA UPS modules operating in parallel to support a 1,000 kVA critical load ( N = 2 N=2 N = 2 , capacity = 2 + 1 = 3 2+1 = 3 2 + 1 = 3 modules). All three modules terminate into a single common output switchboard with a single maintenance bypass circuit.
Analysis: While an individual UPS module can be isolated for servicing, the common output switchboard represents a single point of failure (SPOF). To perform thermographic re-torquing, breaker replacement, or busbar maintenance on this switchboard, the entire critical load must be de-energized.
Classification: This architecture is strictly Class 2 , not Class 3. To achieve Class 3 Concurrent Maintainability, the distribution must provide dual independent distribution paths (e.g., dual switchboards, dual busways, or tie-breakers with bypass cabling) allowing one complete distribution path to be isolated without dropping the downstream dual-corded servers.
Chilled Water Ring Topologies and Sectionalizing Valves
In mechanical cooling, achieving Class 3 concurrent maintainability requires more than having N + 1 N+1 N + 1 chillers. The chilled water piping loop must incorporate sectionalizing isolation valves arranged in a reverse-return ring or dual-header layout. If an isolation valve fails or a pipe spool develops a flange leak, operators must be able to isolate that specific segment via local shutoff valves while chilled water continues circulating through the alternative branch of the ring to feed active CRAH units.