Building permits and inspections

Once land use approvals are in place, the project needs permission to build. Building permits confirm that the design complies with the building, fire, plumbing, electrical and energy codes, and inspections during construction confirm that what is built matches the approved design. For a data center, the permitting stage is unusually complex: the buildings are large and often classified unusually, the electrical and mechanical systems are enormous, there are fuel tanks and battery rooms, and owners want to build in phases and start some work before the whole design is finished. This lesson covers the codes that apply, how data centers are classified, the permit process including phased and fast-track permits, the specific code issues data centers raise, inspections and occupancy, and practical ways to keep permits off the critical path.

The codes

In the US, building regulation is adopted by states and local governments. Most adopt the International Code Council's model codes, the International Building Code (IBC), International Fire Code (IFC), International Mechanical Code, International Plumbing Code and International Energy Conservation Code (IECC), with local amendments, though some states and cities write their own. Electrical installations follow the National Electrical Code (NFPA 70). The local building department, sometimes with the state, issues permits and inspects, and the fire marshal reviews fire protection and hazardous materials.

Data centers also draw on standards that codes reference or that owners adopt:

• Electrical: NEC Article 645 (information technology equipment rooms), Article 700 to 702 (emergency and standby systems), Article 480 and 706 (batteries and energy storage).
• Fire: NFPA 75 (protection of IT equipment) and NFPA 76 (telecommunications facilities), NFPA 72 for fire alarms, NFPA 13 for sprinklers, NFPA 855 for energy storage and NFPA 30 and 37 for fuel and engines (DCE-440).
• Energy: the IECC or ASHRAE 90.1 for the building, and ASHRAE 90.4, Energy Standard for Data Centers, which sets maximum mechanical and electrical loss components, when adopted by the jurisdiction (the IECC references it for large data centers).
• Structural: ASCE 7 for loads, including seismic design categories based on site hazard and risk category, which may be raised for facilities that must remain operational (DCE-430).

Classifying a data center

Codes assign each building, or part of a building, an occupancy classification that drives fire separation, construction type, maximum area and height, sprinkler requirements, egress and more. Data centers do not fit neatly into the traditional categories:

• The data halls are usually classified as Group B (business) or Group S-1 or S-2 (storage), and sometimes F-1 (factory), depending on the authority's interpretation; many jurisdictions now have written policies.
• Offices, loading docks and storage areas may have different classifications, requiring fire separations or treating the building as mixed use.
• Battery rooms, generator rooms, fuel storage and electrical rooms bring hazardous materials and high-energy equipment provisions.

Because classification has large cost implications, it should be agreed with the authority early, ideally in a pre-application meeting with a written code analysis, rather than discovered during plan review.

The permit process

A building permit application includes architectural, structural, mechanical, electrical, plumbing and fire protection drawings and specifications, a code analysis, energy compliance documentation, and supporting reports such as the geotechnical report. Plan reviewers in each discipline check the submission and issue comments, the design team responds, and once all disciplines are satisfied the permit is issued, often with conditions. Separate permits or approvals are typically required for:

• Electrical work, usually through the same building department, with plan review for large services.
• Plumbing, mechanical systems, elevators, fire alarms and sprinklers.
• Fuel storage tanks, through the fire marshal under the fire code and NFPA 30, and environmental tank registration.
• Pressure vessels and boilers, where present.
• Demolition, excavation and shoring, and work in public roads.
• Signs, fences and temporary construction buildings.

Phased and fast-track permits

Owners rarely wait for a complete design before building. Many authorities issue phased permits: a site work and excavation permit, then foundations, then structure and shell, then interior and mechanical-electrical systems, each based on the drawings completed for that stage. Phasing allows construction to start months earlier, but it carries risk: later design changes can conflict with work already built under an earlier permit, and the authority may impose conditions. Some jurisdictions offer expedited review for a fee, third-party plan review by qualified private reviewers, or dedicated staff for major projects, which large data center developers often fund.

Code issues specific to data centers

• Large open floor areas and travel distances: data halls can be hundreds of meters long, so egress design must meet maximum travel distances while preserving security, often with controlled exits that release on fire alarm.
• Sprinklers versus alternatives: owners often prefer pre-action sprinkler systems (pipes dry until detection) to protect IT equipment from accidental discharge, and may add clean-agent gaseous suppression in critical rooms; codes and insurers set the minimum (DCE-440).
• Battery energy storage: lithium-ion UPS batteries raise thermal runaway and explosion concerns, addressed through listings, test data (UL 9540A), separation, ventilation, detection and maximum quantities (DCE-340).
• Fuel: large diesel quantities in day tanks and bulk tanks require fire code compliance for tank construction, location, secondary containment, venting and fill points, and limits on quantities inside buildings.
• Electrical: very large services, medium-voltage equipment, arc-flash hazard and selective coordination requirements (DCE-310).
• Roof equipment and seismic or wind restraint of mechanical units and cable trays.
• Energy code compliance for buildings whose dominant load is IT equipment, where prescriptive rules written for offices may not fit, so performance or alternative paths are used.

Where the design departs from the code's prescriptive requirements, the IBC allows alternative materials, design and methods of construction (Section 104.11 in recent editions) when the building official finds the proposal at least equivalent in quality, strength, effectiveness, fire resistance, durability and safety. Data centers frequently use performance-based fire and egress designs approved this way.

Inspections and occupancy

Inspections occur at defined stages: footings and foundations before concrete, structural framing, underground and in-wall services before cover (as in ELEC-130), fire-rated assemblies and penetrations, mechanical and electrical rough-in, and final inspections for each discipline. Fire protection systems require acceptance testing witnessed by the authority, including sprinkler hydrostatic tests and fire alarm verification. Some codes require special inspections, carried out by qualified independent inspectors engaged by the owner, for critical structural work such as concrete strength, welding and high-strength bolting.

When construction is complete and inspections are passed, the building official issues a certificate of occupancy. A temporary certificate of occupancy can allow the first data hall to operate while the rest is under construction, provided life safety systems, exits and fire separations serving the occupied part are complete and accepted.

Commissioning (DCE-450), which tests every system under load to prove it performs as designed, is separate from code inspections but runs in parallel with them at the end of construction, and the final inspections are often scheduled to coincide with integrated systems testing.

Keeping permits off the critical path

• Hold pre-application meetings with the building and fire officials, with a written code analysis.
• Agree on classifications, alternative solutions and phasing in writing early.
• Submit complete, coordinated packages; incomplete submissions generate comment cycles that cost more time than they save.
• Track every permit and approval in a register with owners, dates and dependencies.
• Fund expedited or third-party review where available, and maintain a respectful working relationship with reviewers and inspectors, who will see the project many times.
• For repeated campus buildings, seek approval of a standard design that later buildings can reference, shortening subsequent reviews.

Lesson 9 covers the separate approvals needed for power and fuel infrastructure, which often set the critical path even when the building permits are ready.