Monday, March 16, 2026

OSHPD / HCAI Fire Alarm Requirements for California Hospitals | Seismic Bracing, NPC, SPC, Permits, and NFPA 72

OSHPD / HCAI Fire Alarm Requirements for California Hospitals | Seismic Bracing, NPC, SPC, Permits, and NFPA 72

OSHPD / HCAI Fire Alarm Requirements for Hospitals

A detailed technical guide covering jurisdiction, design workflow, seismic bracing, fire alarm documentation, NFPA 72 references, field installation, testing, and closeout for California healthcare facilities.

California Healthcare Facilities HCAI / Legacy OSHPD NFPA 72 Cross-References Seismic / OSP / OPM / OPD Plan Review to Closeout
Quick answer: OSHPD is now HCAI, but “OSHPD projects” is still common field language. For many California healthcare projects, fire alarm design and installation require a more formal path for review, permitting, seismic coordination, testing, and closeout than standard commercial work.

What OSHPD Is Called Now

California renamed the former Office of Statewide Health Planning and Development (OSHPD) to the Department of Health Care Access and Information (HCAI). In field conversation, “OSHPD” still gets used all the time, but the current official agency name is HCAI.

Official pages: OSHPD becomes HCAI, HCAI Building Safety.

OSHPD / HCAI Occupancy Classifications

Important: in industry conversation, people sometimes use “OSHPD levels” loosely to describe both facility classifications and seismic performance ratings, but they are distinct regulatory concepts. The occupancy side determines facility type and often the jurisdictional path for plan review and inspection, while SPC and NPC ratings address seismic performance.
The table above
Classification Facility Type Description Jurisdiction Notes
OSHPD 1 General Acute Care Hospitals Buildings providing 24-hour inpatient care, including surgery, intensive care, and emergency services. HCAI has full jurisdiction for plan review, construction observation, and major compliance oversight.
OSHPD 1R Removed from Acute Care Former hospital buildings that no longer provide acute care services but remain on a hospital campus. Always verify the exact current use, facility license status, and project path.
OSHPD 2 Skilled Nursing & Intermediate Care Used for freestanding skilled nursing facilities and related intermediate care uses. Often divided in practice into 2A and 2B construction types, but HCAI remains central to the compliance framework.
OSHPD 3 Licensed Clinics Primary care, specialty, and surgical clinic environments. Jurisdiction is often relinquished to the local building official, while HCAI still sets the standards.
OSHPD 4 Correctional Treatment Centers Health facilities within law enforcement or correctional institutions. Verify the exact review and inspection path from the approved project documents.
OSHPD 5 Acute Psychiatric Hospitals Facilities providing 24-hour inpatient psychiatric care. Like OSHPD 3, jurisdiction may often stay with the local authority even though HCAI standards still matter.

Seismic Performance Categories (SPC / NPC)

In healthcare work, “OSHPD levels” also gets used in conversation to describe seismic performance categories. These do not replace occupancy classifications. Instead, they measure how the building and its critical nonstructural systems are expected to perform during and after an earthquake.

Level Structural Performance Category (SPC) Non-Structural Performance Category (NPC)
1 At risk of collapse and must be removed from service. Non-functional. Systems and equipment do not meet seismic bracing standards.
2 Does not jeopardize life safety, but may be unrepairable. Critical systems braced only in high-hazard areas.
3 Compliant with the 1973 hospital seismic act and likely repairable. Full compliance for critical life-safety systems, including fire alarms.
4 High compliance and expected to become operational shortly after a seismic event. Includes NPC 3 plus cladding and ceiling systems meeting seismic requirements.
5 Immediate occupancy and full post-event functionality. Includes NPC 4 plus on-site backup support for extended continued operation.
Key fire alarm takeaway: because fire alarms are life-safety systems, healthcare facilities typically need NPC 3 or higher performance for continued acute care compliance. That is why seismic bracing and anchorage of fire alarm panels, conduit, trapezes, supports, and attachments matter so much on HCAI work.

Who Issues the Permit for Different OSHPD / HCAI Projects?

For many hospital and healthcare projects, the permit and construction observation path runs through HCAI rather than the local building department. HCAI breaks this into a formal process including project creation, plan review, and permit and construction observation.

When HCAI is typically central

  • General acute care hospital building work
  • Skilled nursing and intermediate care facility work
  • Projects where the HCAI permit path is explicitly required
  • Projects with healthcare seismic and observation obligations tied to HCAI programs

When local authority may still matter

  • Certain clinic and outpatient work
  • Some OSHPD 3 scenarios
  • Scope-specific local fire authority coordination
  • Deferred submittals and fire department signoff points depending on the project setup

Authority Stack for Healthcare Fire Alarm Design

Authority Layer Why It Matters Typical Relevance to Fire Alarm Work
HCAI process and guidance Controls project path, submittals, observation, seismic programs, and healthcare-specific review culture. Permits, comments, deferred submittals, field observation, TIO, and closeout.
California Building Code / Fire Code / Administrative Code Adopted state law framework. Occupancy, egress, healthcare construction administration, and inspection path.
California Electrical Code Wiring methods, separation, and healthcare electrical environment. Raceways, supports, conductor fill, Article 760 issues, and healthcare electrical coordination.
NFPA 72 Fire alarm and signaling design, installation, testing, records, ECS, notification, and pathways. Chapters 10, 12, 14, 17, 18, 21, 23, 24, and 26 depending on scope.
NFPA 99 and project-specific standards Healthcare facility operational and system context. System interfaces, essential systems, and clinical environment expectations.
Manufacturer listing / HCAI preapprovals Listed equipment still has to align with California healthcare seismic and installation rules. OSP, OPM, OPD, anchorage details, support details, and approved methods.

Does the Fire Alarm Design Need an FPE or EE Stamp?

On healthcare work, the better question is not “Does this always need one exact stamp type?” but “Who is the registered design professional in responsible charge for this exact scope and submittal?”

In practice, fire alarm design responsibility on HCAI work is often carried through the engineer or design professional of record, commonly involving an Electrical Engineer (EE), a Fire Protection Engineer (FPE), or coordinated work under the larger project design team.

Best practice: verify whether the fire alarm scope is engineer-of-record design, delegated design, or a hybrid submittal path. Do not assume a one-size-fits-all stamp rule.

Plan and Submittal Requirements for HCAI Fire Alarm Work

HCAI’s standard process requires project creation through the eServices Portal, upload of construction documents, review, comment resolution, permit issuance, construction observation, and closure. The permit page also notes that a Testing, Inspection and Observation (TIO) Program must be submitted before a permit can be issued.

Document What It Should Do Why It Matters on HCAI Work
Code summary / basis of design Identify occupancy, project type, governing codes, and facility classification assumptions. Keeps reviewers from having to guess the project identity.
Floor plans with device layout Show every initiating device, control interface, NAC or speaker coverage area, modules, and major pathway. Core drawing set for review and field observation.
Riser diagram Show panel architecture, node relationships, power supplies, transponders, amplifiers, pathway classes, and interfaces. Vital for review, troubleshooting, and acceptance.
Sequence of operations matrix Translate cause and effect into a reviewable control logic format. Prevents scope gaps between trades.
Voltage drop and battery calculations Demonstrate reliable operation under adopted rules and manufacturer parameters. Critical for review and acceptance testing.
Cut sheets and listings Show model numbers, listings, compatibility, and key product data. Essential for review and field verification.
Seismic support details Show cabinet anchorage, bracing, supports, and preapproved details where used. Healthcare work in California demands real seismic coordination.
Deferred submittals if allowed Identify which items are deferred and who reviews them. Needs alignment with HCAI office and field expectations.
TIO documentation Define who inspects, tests, observes, and signs what. Permit prerequisite and closeout backbone.

Useful official pages: HCAI Standard Project Process, Plan Review Processes and Goals, Building Permits and Construction Observation.

Advanced Engineering Workflow Diagram

This version uses centered labels, shorter text blocks, and cleaner arrow paths so text stays inside the intended boxes.

1. Scope Definition Facility type, project type, jurisdiction, phasing, and existing system constraints 2. Code Basis CBC, CFC, CAC, CEC, NFPA 72, NFPA 99, and HCAI program rules 3. Design Responsibility Alignment EOR, EE, FPE, delegated design, manufacturer limits, and review path 4. Preliminary Design Device strategy, pathway strategy, interfaces, phasing, and shutdown constraints 5. Technical Package Plans, riser, sequence, calculations, cut sheets, notes, and seismic details 6. HCAI Project Creation + Upload eServices project setup, document upload, and discipline review start 7. Review Comments Architectural, electrical, fire and life safety, and structural or seismic comments resolved 8. Permit + TIO Permit issuance after approvals and testing, inspection, and observation alignment 9. Installation + Observation Install, support, brace, label, inspect, and manage approved field changes 10. Testing + Documentation Pretest, acceptance testing, records, point lists, battery, and voltage confirmation 11. Final Signoff + Closeout Final compliance, as-builts, approvals, project closeout, and turnover

Install to Signoff Workflow for the Field

Phase What the Fire Alarm Team Should Verify Typical Failure Mode if Ignored
Preconstruction Approved documents, permit status, phasing restrictions, infection control coordination, and outage planning. Installing from a non-final set and getting hit by comments later.
Rough-in Raceways, supports, wall ratings, above-ceiling conflicts, seismic bracing approach, and pull box access. Conduit work that clashes with ceilings, med gas, duct, or support rules.
Device install Mounting heights, location intent, room function, ceiling treatment, and patient care sensitivity. Approved symbol on paper, wrong real-world location in the room.
Panel and power Branch circuit source, breaker identification, clearances, cabinet anchorage, and remote supply layout. Late-stage power issues and relocation requests.
Programming / cause-effect Matrix confirmation, interface verification, phasing logic, trouble routing, and supervisory mapping. System “works” in isolation but fails the healthcare sequence intent.
Pretest Point list, labels, addresses, candela and speaker taps, battery, voltage drop assumptions, and record documents. Acceptance test turns into live improvisation.
Final / turnover As-builts, O&M manuals, test records, owner training, and signoff documents. System passes but turnover package is incomplete.

Field Installation Requirements: Wiring, Conduit, Devices, and Placement

Wiring Methods

  • Use the adopted California Electrical Code and NFPA 72 pathway requirements as the baseline.
  • Coordinate healthcare electrical-space requirements early, especially where branch power and transfer equipment are involved.
  • Keep supports, boxes, and raceways coordinated with ceiling systems, ductwork, med gas, plumbing, and seismic support locations.
  • Do not let field routing break the pathway intent or future service access.

Device Placement

  • Match device location to the actual room function, not just the room name on an old background.
  • Patient rooms, staff work areas, corridors, mechanical rooms, and specialty spaces can all change application decisions.
  • Coordinate ceiling treatments, soffits, beams, lifts, med gas booms, and infection-control restrictions before finalizing spot locations.

Deferred Submittals

Deferred does not mean casual. It means controlled. Verify what is deferred, who reviews it, and how it gets approved and documented in the field.

OSHPD / HCAI Seismic Bracing for Fire Alarm Conduit and Panels

On California hospital work under HCAI, fire alarm systems and their supporting nonstructural elements are subject to a stricter seismic framework than ordinary commercial projects. In practical terms, that means the fire alarm designer and installer need to think about more than just device layout and pathway routing. The support method, attachment detail, cabinet anchorage, and deferred submittal path all matter.

HCAI separates its seismic preapproval programs by purpose. The OSHPD Preapproval of Manufacturer’s Certification (OPM) is used for the seismic design of supports and attachments for nonstructural components, including electrical raceway bracing. The OSHPD Preapproved Details (OPD) program provides HCAI preapproved standard details. The OSHPD Special Seismic Certification Preapproval (OSP) program applies to nonstructural components that require special seismic certification, such as certain control panels and equipment.

Important: for seismic bracing of fire alarm raceways and supports, think OPM / OPD. For specially certified equipment or certain wall-mounted control panels, think OSP. Do not treat those programs as interchangeable.

1) Importance Factor and Why Hospital Fire Alarm Work Gets More Stringent

For HCAI hospital projects, nonstructural components tied to life safety and essential building function are generally designed under the more demanding healthcare seismic rules. HCAI OSP documentation for wall-mounted fire alarm control panels shows an Importance Factor (Ip) of 1.5, which is the level typically associated with critical nonstructural hospital components. That is one reason healthcare fire alarm seismic support and anchorage details are reviewed much more closely than standard commercial work.

Field takeaway: on HCAI hospital work, do not assume the fire alarm panel, remote power supply, conduit trapeze, or support detail can be handled with a generic commercial seismic approach. Match the approved drawings and the applicable HCAI preapproval path.

2) Suspended Above-Ceiling Fire Alarm Conduit

Suspended fire alarm conduit above a hospital ceiling should be treated as part of the building’s nonstructural distribution system and supported from the structure using an approved seismic support approach. The commonly cited California thresholds for exempting some raceway runs from separate seismic bracing are tied to MEP distribution-system interpretation language, including the familiar 12-inch hanger length threshold and the 10 pounds-per-foot trapeze threshold.

These concepts align with the seismic design framework used in the California Building Code (CBC) and ASCE 7 for nonstructural components, which form the structural basis for many HCAI seismic review decisions.

  • Independent support: fire alarm raceways should be supported from the structure, not from the ceiling grid or ceiling support wires.
  • Short drops: where each hanger in the run does not exceed 12 inches from the raceway support point to the structure, the run may fall within the commonly cited exemption framework used for MEP distribution systems.
  • Longer drops: when the drop exceeds that threshold, separate seismic restraint design is generally needed.
  • Grouped conduits on trapeze: if multiple conduits are carried on a trapeze and the assembly exceeds the commonly cited 10 lb/ft threshold, the trapeze should be treated as a seismically braced support assembly rather than an ordinary hanger arrangement.

In practice, hospital fire alarm designers usually specify rigid bracing details, strut-framed support assemblies, or approved cable-bracing assemblies where permitted by the approved design. The right answer is not “whatever usually works,” but “whatever matches the approved seismic support detail, the project engineer’s design assumptions, and the HCAI-accepted submittal.”

3) Bracing Direction, Clearance, and Assembly Behavior

Once a raceway support assembly requires seismic restraint, the design should address movement in both principal directions rather than treating the conduit as if it only needs one-direction restraint. On real hospital jobs, that means thinking about transverse and longitudinal restraint, attachment capacity, brace spacing, and coordination with all the other overhead systems competing for the same ceiling space.

  • Rigid bracing: often preferred where approved, commonly using steel strut systems that can resist both tension and compression.
  • Cable bracing: can be used where permitted, but generally must work in opposing pairs because cable acts in tension rather than compression.
  • Separation: brace wires and struts should be laid out so the intended clearance to adjacent unbraced systems is maintained and components do not strike one another during seismic movement.
Design caution: do not let the BIM model or above-ceiling congestion quietly erase the seismic intent. A perfectly legal brace detail on paper can still become a bad installation if it crowds ductwork, med gas, cable tray, lighting, or other unbraced components.

4) Wall-Mounted Fire Alarm Panels and Conduit

Wall-mounted fire alarm control panels are usually handled differently from suspended raceway. HCAI OSP examples for fire alarm control panels show rigid wall-mounted configurations, and those approvals make clear that the installed mounting configuration must be similar in strength and stiffness to the tested configuration.

Conduits mounted directly to structural walls are often treated very differently from independently suspended runs because the wall itself provides continuous support. Even so, the attachment to the wall or structure still has to match the approved detail, anchor type, and substrate assumptions. If the raceway or cabinet crosses a seismic separation joint or another location where differential movement is expected, the design should address movement explicitly instead of pretending the building will move as one rigid block.

5) Approved Anchors, Preapprovals, and Deferred Submittals

HCAI’s preapproval structure is designed to streamline this work when the design team uses accepted details and accepted manufacturers’ seismic support systems. That is why hospital contractors often rely on OPM assemblies for support and attachment design, and OPD details where applicable, instead of reinventing the bracing package on every job.

  • OPM: voluntary HCAI preapproval program for the seismic design of supports and attachments for nonstructural components, including electrical raceway bracing.
  • OPD: HCAI preapproved standard architectural and engineering details.
  • OSP: voluntary HCAI preapproval program for special seismic certification of nonstructural components that require it.
  • Anchors: attachment details should match approved substrate assumptions, manufacturer data, and the specific accepted seismic detail for the project condition.

Fire alarm seismic bracing should be shown on the approved construction documents when it is part of the design package, or submitted through the project’s deferred submittal path when that approach is allowed. HCAI’s Fire and Life Safety FAQ confirms that the field Fire and Life Safety Officer decides what fire alarm deferred submittal documents can be reviewed in the field, using the FREER Manual as a guide.

6) Practical Design Rules for Fire Alarm Teams

  • Support fire alarm raceways from the structure using an approved support method and detail path.
  • Do not assume all conduit runs are exempt from seismic bracing just because they are small.
  • Check hanger length, total trapeze weight, brace direction, and brace clearance early.
  • Use OPM / OPD details for raceway support and attachment design where appropriate.
  • Use OSP only where the equipment itself requires special seismic certification.
  • Match the installed field condition to the approved detail, tested configuration, and substrate assumptions.
  • Coordinate seismic joints, flexible fittings, and movement allowances wherever the pathway crosses a separation condition.
  • Do not leave seismic bracing to a last-minute means-and-methods conversation if the approved design already controls it.

Conduit Seismic Bracing Detail Gallery

The examples below show conceptual and real-world seismic bracing conditions for conduit and trapeze-supported assemblies. The gallery is arranged in two rows with equal-size images for easier comparison.

Layout note: all four images are locked to the same visual height for a cleaner side-by-side comparison. This gallery uses object-fit:contain; so the full technical image stays visible even if some cards show extra padding around the image.

NFPA 72 Cross-References for Hospital Fire Alarm Design

This section is a practical chapter-level summary for designers and should not be used as a substitute for the adopted code text, California amendments, and project-specific governing documents.

For healthcare projects, the NFPA 72 chapters below are commonly at the center of design review, installation, testing, and closeout. Always verify the adopted edition and exact project requirements.

NFPA 72 Topic Why It Matters on Hospital Work Designer’s Practical Use
Chapter 10 Fundamentals Listings, documentation, circuit and equipment basics, and the general framework. Baseline compliance and product suitability.
Chapter 12 Circuits and Pathways Pathway class, routing intent, and survivability issues. Critical for hospitals with phasing and continuity expectations.
Chapter 14 Inspection, Testing, and Maintenance Testing, maintenance, records, and documentation. Use during turnover planning and acceptance prep.
Chapter 17 Initiating Devices Detector and initiating-device application rules. Smoke detectors, duct detectors, heat detectors, pull stations, and modules.
Chapter 18 Notification Appliances Audible and visible notification principles and application. Candela, audibility, and patient-space coordination.
Chapter 21 Emergency Control Function Interfaces Outputs to other building systems. Elevator recall, smoke control, door release, dampers, and shutdowns.
Chapter 23 Protected Premises Alarm Systems Core protected-premises architecture and system-level requirements. Panel architecture, interconnected units, and protected-premises logic.
Chapter 24 Emergency Communications Systems Voice and ECS topics where applicable. Larger campuses and relocation messaging.
Chapter 26 Supervising Station Alarm Systems Transmission, supervising station, and signal handling path. Monitoring path design and documentation.

OSHPD / HCAI Fire Alarm System Matrix

System Element Typical Hospital Relevance Design Checkpoints Field / Review Checkpoints
Fire alarm control panel / network node Main system brain, campus or building node, often integrated with remote supplies and interfaces. Architecture, survivability intent, location, power, room suitability, and network strategy. Anchorage, clearances, labeling, programming, and as-built consistency.
Remote power supplies / transponders Distributed power and control in large campuses or phased remodels. Load strategy, circuit classes, battery, and maintenance access. Mounting, branch power source, address mapping, and final load verification.
Smoke detectors Core initiating devices in many patient-care and support environments. Application by room function, ceiling geometry, environmental suitability, and sequence impact. Final location, ceiling conflicts, and address match.
Duct detectors HVAC shutdown and smoke management coordination. Control sequence, test access, and sampling tube configuration. Access panel location, labeling, and shutdown verification.
Heat detectors Mechanical, electrical, or support spaces where smoke application is unsuitable. Temperature type, room condition, and spacing strategy. Correct model and final location.
Manual pull stations Manual initiation path where required. Placement relative to exits, travel path, and healthcare operations. Height, signage, accessibility, and corridor conflicts.
Horn / strobe devices General notification in non-voice applications or local area signaling. Candela strategy, audibility, and circuit loading. Mounting height, candela setting, and final visibility.
Speakers / speaker strobes Common in larger or more complex hospital systems. Voice coverage logic, wattage tap assumptions, and zoning. Tap settings, programming, and amplifier loading.
Sprinkler monitoring interfaces Flow, tamper, valve supervisory, and waterflow location logic. Point naming, zone mapping, and sequence. Supervision, mapping, and acceptance readiness.
Elevator recall / shunt interfaces Highly sensitive life-safety interface. Exact control sequence, initiating devices, and disconnect logic. End-to-end functional testing and labeling.
Smoke control / dampers / fans Complex healthcare sequence territory. Cause-effect matrix, status monitoring, and interface ownership. Wire-by-wire verification and witness testing.
Supervising station transmission Off-site signal routing and monitoring continuity. Transmission method, signal categories, and documentation. Account setup, signal verification, and naming accuracy.
Cabinet anchorage / seismic support Major California healthcare issue. Detail source, OPM / OPD support details, and OSP only where the equipment itself requires special seismic certification. Installed anchors, supports, and cabinet configuration must match the approved detail and accepted project conditions.
As-builts / turnover docs Final owner usability and closeout quality. Record format and update strategy during construction. Point lists, labels, directories, and drawings must match reality.

Hospital Fire Alarm Riser Diagram Template

This is a cleaned visual template for article use or as a downloadable designer handout. It is intentionally generic and should be customized to the project’s exact manufacturer, pathway class, and interface architecture.

Main FACP / Node Annunciator / CPU / Network Core Branch Power / Battery / Monitoring Remote Power Supply A NAC / Speaker / Strobe Circuits Remote Node B Modules / SLC / Local Interfaces Voice / Amp Rack Amplifiers / Paging / ECS Field Interfaces Waterflow / tamper / valve supervision Elevator recall / shunt interfaces Door release / smoke control / dampers Initiating Devices Smoke / heat / duct / manual stations Monitor / control modules Specialty inputs per approved plans Notification Horn / strobe / speaker / speaker-strobe Zoning by compartment / floor / phase Supervising Station Remote monitoring / signal receipt

Recommended Notes Beside the Riser

  • Identify all panel, node, amplifier, and remote power supply model numbers.
  • State the pathway class and any survivability assumptions used in design.
  • Reference the sequence matrix sheet for all emergency control functions.
  • Reference the calculation sheets for battery and voltage drop.
  • Clarify what is existing, new, relocated, or future.
  • Identify any deferred submittal scope.
  • Reference seismic anchorage and support detail numbers where relevant.

Fire Alarm Designer Cheat Sheet for OSHPD / HCAI Projects

Downloadable use: this section is formatted so readers can print the page to PDF or save it as a project handout.

FIRE ALARM DESIGNER CHEAT SHEET

California Healthcare Projects | HCAI / Legacy OSHPD

Topic Quick Check Why It Matters
Agency name OSHPD is now HCAI Use current agency links and terminology in the article and submittal narrative.
Project path Confirm whether the job follows HCAI permit, review, and observation process. Do not build the schedule around a standard commercial assumption.
Facility type Confirm hospital, SNF / ICF, clinic, correctional treatment, or psych context. Drives jurisdiction, review path, and code expectations.
Design responsibility Confirm EOR, EE, FPE, and delegated design boundaries. Prevents stamp and scope confusion.
Core drawing set Plans, riser, sequence, calculations, cut sheets, and seismic details. This is the minimum serious-project toolkit.
TIO Confirm Testing, Inspection, and Observation documentation early. Permit issuance depends on it.
Deferred items Know what is deferred and who reviews it. Prevents approval limbo.
Seismic Check OSP, OPM, OPD, and approved support / anchorage details. Healthcare seismic requirements are unforgiving.
Calculations Align installed settings with battery and voltage drop assumptions. Bad math becomes bad acceptance day.
Interfaces Elevator, smoke control, doors, sprinkler, dampers, nurse call, and generators. Most expensive bugs hide in the interfaces.
Testing Pretest every sequence before witness testing. Acceptance should feel surgical, not theatrical.
Turnover As-builts, point list, records, O&M, and training. Closeout quality shapes owner trust.
Topic Official Link Suggested Use in the Article
OSHPD renamed to HCAI HCAI rename page Intro and terminology section.
Building Safety landing page HCAI Building Safety General authority overview.
Standard project process HCAI Standard Project Process Workflow and submittal sections.
Plan review processes and goals Plan Review Processes and Goals Review process discussion.
Building permits and construction observation Permits and Construction Observation Permit, TIO, and field observation sections.
Codes and regulations Codes and Regulations Global code reference area.
Fire and Life Safety FAQs Fire and Life Safety FAQs Deferred submittal discussion.
OSP preapproval OSP Program Seismic certification for applicable equipment.
OPM preapproval OPM Program Seismic supports, attachments, and raceway bracing.
OPD preapproved details OPD Program Seismic support and standard detail section.
Seismic performance ratings Seismic Performance Ratings Hospital seismic context section.

Final Takeaway

HCAI fire alarm projects demand tighter coordination than typical commercial work. The teams that do well are the ones that align scope, jurisdiction, design responsibility, calculations, interfaces, seismic details, and testing records early, then keep every field change tied to the approved process.

Technical disclaimer: this article is an educational guide, not project-specific engineering. Always verify the adopted code edition, current HCAI requirements, facility license category, approved drawings, review comments, manufacturer data, and the exact accepted detail for the specific project.

Suggested internal links for Fire Alarms Online: [Your elevator recall article] | [Your NFPA 72 notification article] | [Your healthcare / smoke control article] | [Your fire alarm voltage drop calculator page]

Wednesday, March 4, 2026

Edwards Edge vs EST4 (and Edge vs IO Series): UL 864 9th Edition, Listings, Commissioning

A practical, AHJ-friendly deep dive for designers, installers, NICET candidates, and plan reviewers. Covers platform fit, integrated hardware, listings framework, UL 864 9th Edition architecture impacts, commissioning, troubleshooting, and EDGE-CU programming workflow.

Primary: Edwards Edge vs EST4, UL 864 9th Edition Secondary: Edge vs IO Series, CSFM listed panel, FDNY COA Audience: contractors, engineers, AHJs, NICET

Submittal reality check: verify listings and approvals (UL/ULC/CSFM/FDNY COA/FM) by exact model number, configuration, accessories, compatible devices, and any listed limitations. This guide provides the framework and field logic.

What the Edge Platform Is (and what it replaces)

The Edwards Edge is Edwards’ new small-to-medium addressable fire alarm control panel platform and is positioned as a direct replacement for the IO Series. It is designed to reduce install complexity, provide more onboard capability, and modernize daily operations for technicians and inspectors.

Practical takeaway: Edge is the “modern IO replacement lane.” EST4 remains the “large scale and deeper ecosystem lane.”

Edge Panel Architecture and Onboard Capabilities

Edwards Edge fire alarm panel architecture diagram showing CPU, power supply, NAC circuits and relays
Internal architecture of the Edwards Edge addressable fire alarm control panel showing integrated power supply, NAC circuits, battery capacity, and onboard relays.


Edge ships as an integrated assembly (CPU side and power supply side together), which reduces field assembly and speeds installs. The platform also adds meaningful onboard capability compared to many legacy small/medium systems.

Onboard FeatureWhat You GetWhy It Matters
Integrated SLCOnboard SLC loopFewer expansion parts for many projects.
4 NACsFour onboard NAC circuitsCommon small/mid notification loads stay in one cabinet.
NAC as AUXNACs can be configured as 24V AUX (resettable/non)Cleaner power strategy when you need 24V field power.
3 RelaysAlarm, Supervisory, Trouble relaysDirect interface for common outputs and building functions.
10-inch DisplayLarge display for visibilityBetter field usability, faster event review.
Battery SupportUp to 65Ah batteries (larger cabinet may be required)More standby headroom when required by design.
Inner Door OptionsUp to 72 switches/LEDs on inner door expansion slotsStrong annunciation and control options when required.

Full Edge vs IO Series Comparison (retrofit reality)

Comparison chart Edwards Edge vs IO Series vs EST4 fire alarm control panels
Feature comparison between Edwards Edge, Edwards IO Series, and Edwards EST4 fire alarm control panels highlighting architecture, NAC capacity, and system capabilities.

Edge is intended to replace the IO Series, but retrofits require smart planning. Some IO items transfer cleanly and others do not. The key is aligning the proposed Edge model with the existing IO footprint and migration goals.

CategoryEdwards EdgeEdwards IO Series
Platform RoleNew small/medium platform, IO replacementLegacy small/medium platform
SLC StrategyIntegrated onboard SLCOften required loop expanders
NAC/AUX4 NACs, convertible to 24V AUXMore reliance on add-on NAC modules
Retrofit ModelsEDGE-ML-R/G (new installs + IO-64 replacements) and EDGE-ML-RRK (IO-500/IO-1000 retrofit kit)Existing installed base
Program MigrationIO-1000 programs may be importable (version dependent); IO-64 must be rebuiltIO-CU programming environment
Compatibility WatchoutsIO loop expanders not compatible; Edge uses Edge-specific cardsLegacy expanders and accessories
Retrofit planning tip: Quote labor differently for IO-64 (rebuild) vs IO-1000 (potential migration).

Edge vs EST4: Pros/Cons and “When to Choose Which”

Edwards Edge: Pros

  • Integrated capability tuned for small to mid-size installations and IO replacements.
  • Cleaner commissioning workflow centered around EDGE-CU and modern diagnostics.
  • Better field usability through a larger interface and clearer event handling.

Edwards Edge: Cons

  • Market familiarity varies by AHJ and region (verify acceptance expectations early).
  • Retrofit compatibility must be confirmed before assuming reuse of legacy hardware.

Edwards EST4: Pros

  • Enterprise-scale ecosystem and established deployments for large, accessory-rich projects.
  • High AHJ familiarity in many jurisdictions due to broad install base.

Edwards EST4: Cons

  • More complexity depending on module selection and project scope.
  • Overkill risk on smaller projects where Edge fits better.
Rule of thumb: Choose Edge for IO replacements and small/mid new installs. Choose EST4 for large-scale applications and deep expansion needs.

Listings and Approvals Framework (UL, ULC, CSFM, FDNY, FM)

Plan review success comes down to documentation. Use this framework in your submittal package and always verify approvals by exact model number.

Listing / ApprovalWhere It Typically MattersWhat to Include in Submittal
UL 864Most US jurisdictionsExact control unit and accessory listing references.
ULCCanada (or specs requiring ULC)ULC listing confirmation for panel + accessories.
CSFMCaliforniaCSFM listing number and scope/limitations for configured equipment.
FDNY COANew York CityFDNY acceptance documentation for the exact configured system.
FM ApprovalIndustrial or insurer-driven specsFM approval scope and applicability to your configuration.
Best practice: Add a dedicated “Listings/Approvals Appendix” page in your submittal. Reviewers love tidy packages.

UL 864 9th Edition Impact on Panel Architecture

UL 864 9th Edition is an equipment standard that influences how modern panels are engineered internally. In the field, it typically shows up as more deterministic event handling, stronger software integrity behavior, and clearer supervision and timing discipline.

  • Deterministic response behavior: faster event processing and prioritization when multiple events occur.
  • Software integrity: stronger watchdog and controlled-state fault handling.
  • Communications supervision: more formalized “path health” logic for IP and network reporting.
  • Noise immunity: better resilience through design discipline (filtering/layout/shielding).
  • Output timing: more disciplined NAC behavior and synchronization expectations.
Spec language starter: “Provide a UL 864 listed control unit and accessories capable of deterministic event processing and supervised communications, installed per NFPA 72.”

Edge Commissioning Workflow (step-by-step)

Step by step Edwards Edge fire alarm panel commissioning workflow
Commissioning workflow for the Edwards Edge fire alarm control panel including firmware loading, EDGE-CU programming, device configuration, and system verification.


  1. Install and power the panel (verify AC, batteries, and field wiring).
  2. Load firmware (download separately and update as required).
  3. Launch EDGE-CU and connect to the panel.
  4. Import IO programs if applicable, otherwise build the configuration.
  5. Configure devices and addresses (labels, descriptions, points).
  6. Set central station reporting (CID assignments and communication path tests).
  7. Verify panel operations (event queue, reports, basic commands).
  8. Find Device diagnostics to speed device-level troubleshooting.

Edge Panel Troubleshooting and Diagnostics Guide

Start with event priority

Before resetting anything, review current events and event history. Prioritize alarms first, then supervisory, then trouble conditions.

Use Find Device before you go hunting

The Find Device function helps locate devices by address and quickly confirms device type, label, and status. This reduces “walk-the-building” time during inspections and service calls.

Common trouble conditions (quick triage)

ConditionLikely CauseFast Checks
SLC TroubleOpen, short, device faultCheck wiring, isolate segments, confirm addressing, review recent changes.
NAC TroubleOpen circuit, EOL issue, wiring faultVerify EOL, polarity, terminations, and removed/failed appliances.
Battery TroubleLow voltage, end-of-life, charger issueLoad test batteries, confirm charger output and battery wiring.
Ground FaultConductor contacting groundIsolate circuits one-by-one to identify the grounded path.
Comm TroubleDialer/IP path issue or config mismatchVerify account setup, CID mapping, supervision, and test signals end-to-end.

Access levels and service login

User ID: 00#
Password: 1234
  
Best practice: Document what you see before clearing. Event history is how you prove cause and prevent repeats.

EDGE-CU Programming Guide

Edge programming is performed using EDGE-CU. Your goal is a clean database: clear device labels, predictable logic, and correct CID mapping. That’s what makes future service calls fast and painless.

Programming checklist

  • Create a new project and select the correct panel model.
  • Confirm firmware/software compatibility.
  • Configure SLC devices (address, type, label, function).
  • Configure NACs (notification mode or AUX power mode as required).
  • Confirm relay behaviors (alarm/supervisory/trouble and any project interfaces).
  • Assign unique CID codes as required for central station reporting.
  • Upload configuration, test, then save a backup of the final configuration file.

IO migration notes

  • Some IO configurations may be importable (version dependent).
  • Plan IO-64 replacements as “rebuild from scratch.”
  • Plan IO-1000 replacements as “verify migration path.”
Programming best practice: Labels and CID mapping are not paperwork, they are service speed.

Spec Comparison Charts (embeddable)

A) Spec-Sheet Chart (checkbox placeholders)

Spec CategoryEdwards EdgeEST4
UL 864☐ Verified per exact model☐ Verified per exact model
ULC (Canada)☐ If applicable☐ If applicable
CSFM (California)☐ Verify listing number☐ Verify listing number
FDNY COA (NYC)☐ Verify COA number☐ Verify COA number
FM Approval☐ If required by spec☐ If required by spec
Commissioning speedStreamlined onboardingMature but configuration-dependent
Ecosystem depthGrowingExtensive

B) UL 864 9th Edition architecture impact chart

Impact AreaEdge trendEST4 consideration
Event response behaviorModern deterministic handlingVerify configuration and revision alignment
Software integrityGuarded logic and fault behaviorDepends on configured components
Communications supervisionFormal path health logicOften modular, confirm supervision method
Noise immunityDesign discipline for harsh environmentsConfirm revision level where needed
NAC timing/syncDisciplined output timingConfirm compatibility matrix

FAQ

Is the Edwards Edge panel listed and approved everywhere?

Listings/approvals are configuration-specific. Verify UL/ULC/CSFM/FDNY COA/FM by exact model and accessories for your submittal package.

Can I reuse IO loop expanders on Edge?

Plan for replacement and verify compatibility early. Loop expander assumptions are a common retrofit pitfall.

Can I import existing IO programming?

Some IO programming may be importable (version dependent). Treat IO-64 replacements as rebuilds and IO-1000 replacements as potential migration candidates.


Fire Alarms Online: code-driven fire alarm design guidance, install workflows, and NICET study resources.

Saturday, February 14, 2026

2025 California Carbon Monoxide Requirements – CBC 915, CFC 915 & NFPA 72 (2022)

The 2025 California Building Standards Code (Title 24) updates include important clarifications and enforcement emphasis for carbon monoxide (CO) alarms and detection systems.

This article breaks down:

  • When CO alarms/detection are required under 2025 CBC Section 915 and 2025 CFC Section 915
  • How the IFC Section 915 model requirements (the backbone of many state fire codes) broaden the “when required” scope beyond just dwelling units
  • Power and interconnection rules
  • Enclosed parking garage CO sensor requirements and how California coordinates to CMC 403.7.2
  • How NFPA 72 (2022) applies for inspection, testing, and maintenance where applicable

When Are Carbon Monoxide Alarms / Detection Required? (Two-Lane Approach)

CO requirements get mis-described a lot because designers mix “dwelling unit alarm rules” with “broader building CO detection rules.” To keep your plans plan-check-proof, think in two lanes:

Lane 1: Dwelling Units & Sleeping Units (CBC 915 focus)

Under 2025 CBC Section 915, CO alarms are commonly required in dwelling units/sleeping units when CO exposure risk sources are present, such as fuel-burning appliances and attached garages communicating with the dwelling unit. (CBC 915 framework.)

Common residential triggers include:

  • Fuel-fired appliances
  • Gas fireplaces
  • Fuel-burning forced-air furnaces
  • Attached garages that communicate with the dwelling unit
Combination smoke and carbon monoxide alarm installed on ceiling per California code requirements
Listed combination smoke and carbon monoxide alarms are permitted when installed in accordance with CBC 915 and CFC 915 requirements.


Lane 2: Broader “Interior Space” Requirements (CFC 915 / IFC 915 scope)

Important: The IFC Section 915 (model code basis for many state fire codes, including California’s structure) is broader than only dwelling-unit triggers. It addresses CO detection requirements for new and existing buildings where interior spaces are exposed to CO sources (direct sources, adjacent spaces with communicating openings, and forced-air-related source conditions). In other words: your project may require CO detection even when it doesn’t look like a classic “residential attached garage” situation.

Plan-review tip: On commercial/mixed-use jobs, describe CO detection requirements as: “Provide CO detection where required by CFC 915 for interior spaces exposed to CO sources, and provide CO alarms where required by CBC 915 for dwelling/sleeping units.”

Required Locations (CBC 915.2 concept + CFC/IFC placement logic)

Dwelling units (CBC approach): When required, CO alarms are typically installed:

  • Outside each separate sleeping area in the immediate vicinity of bedrooms
  • On every occupiable level of the dwelling unit, including basements
  • Additional devices may be required where fuel-burning appliances are located within bedrooms or attached bathrooms (project/AHJ dependent)

Broader interior spaces (CFC/IFC approach): Where CO detection applies to interior spaces exposed to CO sources, design should address:

  • Spaces containing CO-producing equipment (direct source locations)
  • Adjacent spaces with communicating openings where CO could migrate
  • Forced-air pathways that can distribute CO to other areas

Always coordinate exact device placement with manufacturer instructions, the adopted code language, and AHJ expectations.


Power & Interconnection (CFC 915.4 + CBC 915 structure)

Power Source (CFC 915.4.1)

CO alarms shall receive primary power from building wiring where such wiring is served from a commercial source, with battery backup where required.

Interconnection (CFC 915.4.4 / CBC 915 framework)

Where more than one CO alarm is required, alarms must be interconnected so activation of one activates all required alarms within the applicable unit/area. California’s 2025 cycle specifically retains clarifying language around interconnection implementation.

Combination Smoke/CO Devices

Combination smoke/CO alarms are permitted where properly listed/approved and installed per manufacturer instructions and adopted code requirements.


Enclosed Parking Garages – CO Sensors and Ventilation Control (CFC 915.6.1 + CMC 403.7.2)

Enclosed parking garage carbon monoxide sensor controlling exhaust ventilation per CFC 915.6.1
Carbon monoxide sensors installed in enclosed parking garages to control ventilation systems in coordination with CFC 915.6.1 and CMC 403.7.2.


This is where a lot of projects get tripped up.

  • Model code note: The IFC framework ties enclosed garage gas detection to mechanical ventilation code references (model mechanical code structure).
  • California note: In the 2025 cycle, California explicitly coordinates enclosed garage detector maintenance expectations through CFC 915.6.1 with reference to CMC 403.7.2.

Key takeaway: Treat enclosed garage CO sensors primarily as a mechanical ventilation control / IAQ scope unless the AHJ/EOR requires FACU integration. If integrated into the fire alarm system, document supervision, pathway, and point type clearly.


NFPA 72 (2022) – How to Reference It Without Getting Burned

Older references commonly point to NFPA 720 for CO detection. NFPA has stated that NFPA 720 requirements were incorporated into NFPA 72.

Safe spec language:

  • Install per the adopted California codes (CBC/CFC) and manufacturer instructions.
  • Where CO detection/notification equipment is part of a signaling system, perform inspection/testing/maintenance per NFPA 72 (2022) as applicable.

2022 vs 2025 Code Comparison (CBC/CFC CO Requirements)

Topic 2022 Cycle (General) 2025 Cycle (What to watch) Plan-Check Proof Note
Scope / “When Required” Commonly described as dwelling-unit driven in many field guides. Must describe both: dwelling/sleeping units (CBC) AND broader interior-space CO exposure conditions (CFC/IFC framework). Write the “two-lane” note on the cover sheet.
Power Hardwired where served by commercial power; battery backup where required. Same concept; cite CFC 915.4.1 explicitly for reviewer confidence. Call out power method and any remodel constraints.
Interconnection Interconnect multiple required alarms. California emphasizes implementation clarity; cite CFC 915.4.4 for consistency. State “hardwired or listed wireless” and show it on plans.
Enclosed Parking Garages Often treated as mechanical/energy controls work, coordinated across disciplines. CFC 915.6.1 coordinates maintenance expectations to CMC 403.7.2 in California. Add a garage SOO and fail-safe behavior.
NFPA Reference NFPA 720 often cited historically. NFPA states CO requirements are incorporated into NFPA 72; cite NFPA generally unless quoting licensed text. Write “NFPA 72 (2022) where applicable + manufacturer instructions.”

Plan Review Notes (Copy Into Drawings)

CARBON MONOXIDE (CO) – 2025 CBC / 2025 CFC GENERAL NOTES

1. Provide CO alarms and/or CO detection where required by the adopted codes:
   • 2025 CBC Section 915 for dwelling units and sleeping units (life-safety CO alarms).
   • 2025 CFC Section 915 for interior spaces exposed to CO sources (CO detection scope).
   Reference IFC Section 915 as the model basis for broader CFC 915 scope where applicable.

2. Power: CO alarms shall receive primary power from building wiring where served by a commercial source, with required secondary power/battery backup. (CFC 915.4.1)

3. Interconnection: Where multiple CO alarms are required, alarms shall be interconnected so that activation of one activates all required alarms within the applicable unit/area. (CFC 915.4.4 / CBC 915 framework)

4. Combination Smoke/CO Alarms: Combination devices shall be listed/approved and installed in accordance with adopted code requirements and manufacturer instructions.

5. Enclosed parking garages (where applicable):
   CO/NO2 detectors used for ventilation control shall be coordinated with mechanical design.
   In California, detector maintenance expectations coordinate through CFC 915.6.1 with CMC 403.7.2.

6. Inspection, testing, and maintenance:
   Perform per adopted code requirements, manufacturer instructions, and NFPA 72 (2022) where applicable.
   Note: NFPA states NFPA 720 requirements were incorporated into NFPA 72.

Garage CO Sensor Sequence of Operations (Typical)

ENCLOSED PARKING GARAGE – CO SENSOR CONTROL (TYPICAL)

GENERAL
- Provide CO (and where applicable NO2) sensors for ventilation control.
- Coordinate with mechanical ventilation controls per CMC 403.7.2.
- Maintain per CFC 915.6.1 and manufacturer requirements.

CONTROL LEVELS (VERIFY WITH EOR / MECH DESIGN)
Low CO Setpoint (typical 25–35 ppm; adjustable):
- Enable exhaust fans at LOW SPEED (Stage 1).
- Enable supply/make-up air as required.
- Send RUN status to BAS if provided.

High CO Setpoint (typical 50–100 ppm; adjustable):
- Enable exhaust fans at HIGH SPEED (Stage 2).
- Flag high-level condition to BAS (supervisory/trend).
- Continue ventilation until levels fall below reset threshold.

RESET / PURGE DELAY
- After CO drops below LOW setpoint, continue fans for timed purge (typical 5–15 minutes) then return to standby.

FAIL-SAFE
- On sensor fault, power loss, or communications loss, command minimum fan operation (Stage 1) and report TROUBLE/FAULT to BAS.

MAINTENANCE
- Test/calibrate per manufacturer interval.
- Maintain per adopted code requirements and NFPA 72 (2022) where applicable.

Keywords: 2025 California carbon monoxide requirements, CBC 915 carbon monoxide alarms, CFC 915 carbon monoxide detection, IFC 915 carbon monoxide code, CMC 403.7.2 garage ventilation control, NFPA 72 (2022) carbon monoxide.