Showing posts sorted by relevance for query fire alarm plan submittal. Sort by date Show all posts
Showing posts sorted by relevance for query fire alarm plan submittal. Sort by date Show all posts

Thursday, October 22, 2026

Fire Alarm Plan Submittal Checklist: Drawings & AHJ Review

Technical editorial note: Verify the adopted code edition, project conditions, equipment listing, and local AHJ requirements before using this guidance for design or permitting.

What belongs in a fire alarm plan submittal?

A complete fire alarm plan package documents what is being installed, where it is installed, how it is powered, how it operates, and how it will be tested. The exact deliverables vary by jurisdiction and scope. Use the project AHJ’s checklist first; the framework below is a professional preflight checklist, not a substitute for local permit instructions.

Fire alarm plan submittal checklist showing project details, drawing requirements, engineering calculations, and supporting documents
Figure 1. Illustrated overview of typical fire alarm plan submittal components.

Start with the administrative sheet

Include project name and address, occupancy and use, building description, applicable codes and editions, scope of work, system classification, designer information, and required approvals. Identify whether work is new, an alteration, an expansion, or replacement of existing equipment. Mark the limits of work clearly.

Floor plans and device schedules

Show floor plans at an accepted scale, with room names, device locations, mounting information where relevant, and a consistent legend. Cross-check device quantities against the bill of materials. Include address or zone identification when required. Identify existing-to-remain equipment separately from new equipment and removals.

Riser and pathway documentation

A riser should communicate the system architecture, panel and power supply relationships, interface modules, network connections, and circuit or pathway designations. Show circuit types, wiring information, and survivability features when applicable. Coordinate drawing notes with equipment listings and manufacturer instructions.

Battery, voltage-drop, and amplifier calculations

Provide secondary-power calculations using the required standby and alarm durations for the applicable system. Verify device loads and battery derating per listed equipment instructions. For notification circuits, document actual supply voltage, wiring resistance, current, and worst-case endpoint voltage. Where voice systems are used, provide amplifier and speaker circuit loading information as applicable. Do not assume a single numerical voltage-drop limit applies to every listed system.

Sequence of operations and interfaces

Include a project-specific cause-and-effect matrix. Coordinate waterflow, supervisory, smoke detection, notification, supervising-station signals, elevator functions, HVAC shutdown, smoke control, and door interfaces when part of the scope. Every input and output must agree with the drawings and the programmed system.

Cut sheets and equipment approvals

Supply legible manufacturer data identifying the exact models and relevant listings. Highlight selected options when a sheet covers multiple products. Confirm power supply compatibility, detector bases, notification appliance synchronization, environmental ratings, and mounting limitations. Do not substitute generic product-family literature for an exact model where it obscures the design.

Illustrated fire alarm plan review process from design package preparation through AHJ review and permit approval
Figure 2. Typical plan-review workflow; actual permit procedures vary by jurisdiction.

Pre-submittal quality-control walkthrough

Perform a drawing-to-schedule count, circuit-to-calculation reconciliation, matrix-to-interface review, and code-reference audit. Confirm revision dates and sheet references match. Check that plan notes do not contradict calculations or the riser. Assign one person to perform an independent completeness review before upload.

Review itemStatusReviewer note
Project scope and code edition☐
Scaled floor plans and legend☐
Device schedule and quantities☐
Riser and pathway details☐
Secondary-power calculations☐
Voltage-drop / amplifier calculations☐
Sequence of operations matrix☐
Manufacturer cut sheets☐
Interdisciplinary interfaces☐

Common plan-review comments

Frequent preventable issues include missing matrix rows, unmatched device quantities, incomplete circuit information, incorrect or unverified code editions, unlabeled existing equipment, and omitted interface details. These are illustrative review risks, not a statistical ranking of actual AHJ comments.

Scope note: The tables below are educational examples, not approved design sequences. The adopted codes, approved drawings, equipment listings, manufacturer instructions, and AHJ determine the actual project requirements. Do not infer a universal output from a device type alone.

Fire alarm plan submittal: 25-point preflight checklist

CategoryItems to verify before uploadingTypical reviewer question
Code basis1. Address and scope; 2. occupancy/use; 3. adopted editions and amendments; 4. existing/new scope boundariesWhat criteria govern this design?
Plans5. legible scale; 6. room labels; 7. device legend; 8. mounting/coverage notes; 9. addresses and device scheduleCan every device be located and counted?
System architecture10. riser; 11. circuits/pathways; 12. cable type; 13. panel/power supplies; 14. interface locationsHow is each device connected and powered?
Calculations15. battery; 16. NAC voltage drop; 17. amplifier load where applicable; 18. circuit capacityDo actual connected loads match the schedules?
Operation19. input/output matrix; 20. interface narrative; 21. transmission/monitoring methodWhat happens for each initiating condition?
Product/closeout22. manufacturer data; 23. listing/compatibility; 24. test/inspection plan; 25. revision coordinationCan the installed system be verified against the plans?

Worked example: reconcile a NAC schedule to voltage drop

Assume an illustrative 24 V nominal circuit with four devices drawing 0.08 A each. The total device current is 4 × 0.08 = 0.32 A. If the listed supply permits a maximum 0.50 A on that circuit, the connected current is below that example limit. This does not prove the circuit is acceptable: the designer must also evaluate the supply's actual voltage range, device minimum operating voltage, wiring resistance, conductor lengths, topology, inrush or synchronization requirements, and the manufacturer's approved calculation method. The drawing schedule, calculation, and bill of materials must use the same device models and quantities.

Worked example: reconcile battery calculations

A calculation might show 0.45 A standby and 1.80 A alarm for a hypothetical system. Using illustrative only durations of 24 hours standby and 5 minutes alarm yields (0.45 × 24) + (1.80 × 5/60) = 10.95 Ah before any applicable capacity, temperature, aging, or manufacturer factors. Those durations are not universal. The approved design must use the correct required operating durations, current data, and equipment instructions.

Sequence of operations cross-check

For every control module, identify its triggering event, normal/fail-safe state, controlled equipment, relay interface, responsible contractor, and acceptance-test witness. An HVAC shutdown output shown on a matrix but missing from the riser is a coordination defect even if the rest of the package looks complete.

Common AHJ review comments and fixes

CommentLikely causePrevention
Device counts differFloor plan and schedule revised independentlyCount and reconcile every device ID before export
Incomplete battery calculationRemote supplies or interfaces omittedUse separate calculations for each power source
Unclear elevator interfaceGeneric relay symbol without sequenceCoordinate detector and elevator group mapping
Missing control sequenceMatrix only covers alarmsInclude supervisory, trouble, restoration and relevant interlocks
Cut sheet conflicts with plansModel changed without schedule updateValidate model numbers, listings and quantities
Fire alarm submittal coordination diagram connecting design inputs, fire alarm drawings, engineering coordination, plan review, and revisions
Figure 3. Coordination between design disciplines, the submittal package, and AHJ review.

Who determines the required drawing package?

The project AHJ and applicable permit rules control submittal requirements. For a concrete reference, see the San Francisco Fire Department fire alarm submittal bulletin; do not apply its local rules nationwide.

Frequently asked questions

Are stamped drawings always required? Requirements depend on jurisdiction, scope, and applicable professional licensing rules. Is one AHJ checklist valid everywhere? No. Should a resubmittal show changes? Follow the AHJ’s revision and clouding instructions.

Related Fire Alarms Online resources

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.
🔥 FIRE ALARMS ONLINE • FIELD TECH TOOL
AI-POWERED POCKET RECORDER
Stop Trying to Remember Everything
From the Job Walk
Capture job walks, coordination meetings, troubleshooting conversations and field notes with Pocket. Record the conversation, then turn it into searchable transcripts, summaries and action items you can reference later.
✓ Job Walks    ✓ Coordination Meetings    ✓ Service Calls
✓ Project Notes    ✓ Troubleshooting    ✓ Action Items
See Pocket & Current Offer →
Affiliate disclosure: Fire Alarms Online may earn a commission if you purchase through this link, at no additional cost to you.

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, October 28, 2026

NFPA 72 Cybersecurity Requirements (2025): SL1–SL3, Firewalls & Field Checklist

Fire Alarm Design • NFPA 72 (2025 Edition) • Updated October 2026

Fire alarm cybersecurity is now part of the technical code conversation, not merely an IT department concern. The 2025 edition of NFPA 72 significantly expands Chapter 11, addressing security levels for network-connectable interfaces, external connections, software security updates, support tools and documentation. The practical challenge is determining what applies to the actual system without treating every fire alarm panel, gateway and device as though they have identical exposure.

This guide is written for fire alarm designers, technicians, project managers, contractors and building owners who need a useful starting point for coordinating a secure life-safety installation. It separates 2025-edition code concepts from additional cybersecurity best practices and explains where California's 2026 code cycle fits.

Code-edition alert: NFPA 72's current published edition is 2025, but that does not make its provisions universally enforceable on every project or automatically retrofit every existing installation. Confirm the governing code of record, local amendments, occupancy, permit scope, equipment listings and AHJ direction before making a compliance decision.

What Changed in NFPA 72 Chapter 11?

Fire alarm network security architecture showing control panel, remote connections and security boundaries

Conceptual fire alarm network security architecture.

NFPA 72's 2022 edition included cybersecurity discussion, with much of the practical material located in informative annex guidance. The 2025 edition substantially develops Chapter 11 into a set of normative provisions addressing the network-connected parts of fire alarm and signaling systems. The code now calls attention to interface security, physical access to network pathways, external network gateways, security-update support and evidence of compliance.

That distinction matters because a modern fire alarm system may include an addressable control unit, a proprietary panel network, a building IT connection, a cellular/IP communicator, a cloud service and a technician's programming computer. These components do not necessarily share the same exposure or the same security-level classification.

Start with the actual architecture

Before assigning responsibilities or specifying cybersecurity features, map what is installed and how it communicates. A basic inventory should identify:

  • Fire alarm control units, network nodes, annunciators and workstations.
  • Proprietary wired or wireless signaling interfaces and IP-based network links.
  • Communicators, external gateways, monitoring connections and remote service paths.
  • Connections to building automation, security or other building systems.
  • Programming laptops, manufacturer service software and removable or temporary network connections.
  • Who owns each connection, who can authorize changes and who retains the records.

Important distinction: A proprietary signaling line circuit is not automatically the same thing as a public internet connection. Conversely, a network that appears private can acquire new exposure when an outside gateway or remote-service path is added. Review each interface and its real connection path.

NFPA 72 Security Levels: SL1, SL2 and SL3

Illustrative comparison of fire alarm cybersecurity security levels SL1 SL2 and SL3

Illustrative comparison only; verify specific code requirements.

Chapter 11 addresses security levels for interfaces used to communicate with network-connectable equipment. The following is an educational classification guide based on the 2025 edition's interface categories; it is not a certification, a blanket system rating or a substitute for the actual standard and manufacturer documentation.

Level / interface categoryTypical exampleWhat to confirm
SL1
Non-IP wired interface
Proprietary wired communication between listed fire alarm components.Interface type, approved protection method and manufacturer-supported evidence.
SL2
Non-IP wireless, or IP interfaces not connected to publicly accessible networks
Listed networked equipment using an isolated or dedicated private IP network.Actual network boundaries, wireless exposure, access control and approved security level.
SL3
IP interface connected to a publicly accessible network
An external network-facing gateway or remote communications interface.Where public connectivity begins, gateway/firewall protection and the scope of the compliant interface.

Do not assume that the presence of one external communicator makes every initiating device, notification appliance or proprietary circuit an SL3 interface. Classification and evidence must be established for the applicable equipment and communications interfaces under the adopted code and the approved system design.

Likewise, Chapter 11 includes an important limited case: systems with neither network-connectable equipment nor an uploadable software configuration are not assigned a minimum cybersecurity level under the referenced 2025 provision. This is not a universal exemption for any panel that happens to be disconnected from the internet today.

What Does Chapter 11 Mean for Fire Alarm Installations?

1. Protect connections to external networks

The 2025 edition addresses external data connections using a gateway or firewall intended to pass trusted traffic. The exact approved method depends on the connected equipment, its listing, the applicable security level and the actual network topology. A switch, router or ordinary IT firewall should not be represented as a certified fire alarm cybersecurity solution merely because it is installed between two cables.

Illustrative communication path
Fire alarm control unit → approved internal network → protected external interface / gateway → authorized outside service or supervising-station path
Diagram shows a conceptual handoff, not a manufacturer wiring detail or approval of any specific product.

2. Secure unused data ports and physical pathways

Unused physical data ports are part of the risk picture. The 2025 Chapter 11 material addresses methods such as physical protection, administrative disabling or suitable authentication. It also contains specific physical-pathway protection provisions for certain higher-security-level applications in publicly accessible locations. These are not reasons to improvise enclosure modifications or install unapproved cable protection. Use the actual edition text and listed equipment instructions.

3. Treat programming laptops as system support tools

A fire alarm service laptop may have the authority to change system configuration. Its operating system, access controls, software versions, storage and remote-support applications therefore deserve attention. Chapter 11 expressly addresses system support tools and their interfaces. Coordinate any security controls with the manufacturer so the measures do not block required diagnostics, interfere with listed operation or prevent timely emergency service.

4. Maintain a controlled security-update process

Chapter 11 addresses manufacturer threat evaluation, notification of security updates, installation of required security updates and the end of manufacturer support. Do not confuse a manufacturer's recurring threat-evaluation obligation with an instruction for owners to install every firmware release every quarter. The applicable requirements depend on the specific provision and the manufacturer's determination.

For each proposed change, record the device and software version, the reason for the update, approval, installation date, backup or recovery plan and the verification performed afterward. An update confined to an external gateway can have different reacceptance implications from a change to the fire alarm control unit's executive or site-specific software. Determine required testing from the adopted NFPA 72 provisions, manufacturer instructions and the actual functional impact of the change.

5. Keep cybersecurity evidence with the project documentation

The 2025 edition calls for identification of the standards and security levels used for Chapter 11 compliance in system documentation. The chapter also addresses evidence of compliance. The goal is an auditable record that helps the owner and AHJ understand what was installed, how it was evaluated and who will maintain it.

Document safely: Record the existence and ownership of privileged accounts, access methods and protected network boundaries, but do not put live passwords, recovery codes, private keys or sensitive network secrets into publicly distributed fire alarm drawings. Maintain restricted security records through an approved owner-controlled process.

Sample Fire Alarm Cybersecurity Coordination Matrix

Use this as a planning aid during design meetings and acceptance preparation. The assignments below are suggested coordination roles, not universal code-assigned responsibilities.

Item to coordinateSuggested leadDeliverable to retain
Applicable edition, local amendments and project scopeDesigner / AHJ / ownerCode basis and approved design criteria
Network architecture and external access pathsFire alarm vendor + ITControlled network/interface diagram
Equipment and interface security-level evidenceManufacturer / integratorApplicable product documentation or acceptable evidence
Gateway, firewall and network boundary configurationIT + listed system integratorApproved configuration and change record
Remote access and user lifecycleOwner / IT / service providerAccess authorization and revocation procedure
Software versions, updates and support statusManufacturer + service contractorVersion inventory, notices and maintenance log
Acceptance and post-change verificationQualified testing partiesTest records, deficiencies and restoration evidence

2026 California Code Note: What Edition Applies?

The 2025 California Building Standards Code became effective January 1, 2026. The California Office of the State Fire Marshal confirms that the 2025 California Fire Code's fire alarm installation provisions reference NFPA 72, 2025 edition. This is an important development for California design and submittal work, particularly when evaluating new systems with network-connectable equipment.

However, the effective date of the state code is not proof that every existing fire alarm system must immediately be retrofitted to all new-edition provisions. Existing-building rules, the permitted scope of work, applicable state-agency provisions, local amendments, and AHJ interpretation still matter. Certain specialized applications may have different referenced editions or amendments. Check the actual adopted provisions for the project.

For an authoritative California source, see the California Office of the State Fire Marshal's information bulletins, including Bulletin 26-002, which explicitly identifies the NFPA 72 (2025) reference. That bulletin concerns a separate Chapter 26 auxiliary service provider provision and should not be mistaken for a blanket cybersecurity ruling.

Cybersecurity Best Practices Beyond the Minimum Code

The following are recommended risk-reduction practices supported by broader operational-technology guidance from CISA and NIST. Do not label each item as a specific NFPA 72 mandate unless the applicable code text actually requires it:

  • Limit remote access: Provide access only where operationally necessary, through approved pathways and for authorized roles.
  • Use strong authentication: Prefer unique accounts and phishing-resistant multifactor authentication where supported by the approved architecture.
  • Segment networks: Keep life-safety network traffic appropriately separated from general enterprise traffic while preserving listed operation and required communications.
  • Manage vendor access: Document service providers, approvals, temporary accounts and the process for revoking access.
  • Track security notices: Keep manufacturer advisories, firmware support dates and change history available to authorized maintainers.
  • Plan for failure: Confirm what happens to required fire alarm functions if the external IT network, gateway or internet connection is unavailable.

CISA's Internet Exposure Reduction Guidance (June 4, 2025) and NIST's Guide to Operational Technology Security, SP 800-82 Revision 3 provide useful security context. These resources are not substitutes for NFPA 72, listed fire alarm equipment instructions or the AHJ.

Fire Alarm Cybersecurity Field & Owner Handoff Checklist

Fire alarm cybersecurity commissioning and owner handoff checklist

Example checklist for cybersecurity coordination and documentation.

This checklist is a practical review tool, not an NFPA-issued inspection form.

  1. Confirm the adopted NFPA 72 edition and any applicable state or local amendments.
  2. Identify every fire alarm control unit, gateway, network device and remote interface.
  3. Record whether each interface is non-IP wired, wireless, private IP or publicly connected.
  4. Obtain manufacturer evidence for the relevant security levels and installed equipment.
  5. Review external network protection and approved traffic paths with IT and the system integrator.
  6. Verify that unused physical data ports are protected as required for the installation.
  7. Identify who can access or reprogram the system, and who authorizes those privileges.
  8. Review the service laptop and support-tool controls with the manufacturer and service team.
  9. Record current software/firmware versions and the manufacturer's security-update support path.
  10. Establish how update notices are received, approved, installed and documented.
  11. Determine the acceptance or reacceptance testing needed after any system changes.
  12. Confirm the required fire alarm functions remain available during permitted network disruptions.
  13. Provide the owner with controlled documentation, training and access-revocation procedures.
  14. Record unresolved items, the responsible party and the agreed corrective action.

Common Mistakes That Cause Problems

OversimplificationBetter approach
"Every IP-connected fire alarm device must be SL3."Evaluate the actual interface and whether it connects to a publicly accessible network.
"The IT department installed a firewall, so we're code-compliant."Verify the approved architecture, equipment compatibility, required protection and compliance evidence.
"Every security update needs the exact same reacceptance test."Identify whether executive or site-specific fire alarm software or required functions changed.
"Cybersecurity only matters during construction."Assign ongoing responsibility for credentials, updates, support status and documentation.
"California's 2026 code cycle automatically forces all existing panels to be replaced."Check the actual code of record, scope, existing-building provisions and AHJ determination.

Frequently Asked Questions

Does NFPA 72 (2025) require cybersecurity for fire alarm systems?

The 2025 edition includes substantive cybersecurity provisions in Chapter 11. Applicability depends on the adopted edition, the system's equipment and interfaces, and the relevant provisions. It is not accurate to apply one universal requirement to every existing panel regardless of its architecture.

What is the difference between SL1, SL2 and SL3?

Chapter 11 describes interface categories ranging from non-IP wired communication to certain private-network and publicly connected interfaces. The appropriate security level must be supported by the approved design and applicable evidence; it is not determined simply by counting Ethernet cables.

Does a cellular communicator mean the entire fire alarm system is SL3?

Not necessarily. The externally connected interface needs evaluation, but that does not automatically assign the same classification to every internal proprietary device or circuit. Confirm the manufacturer-supported architecture and adopted requirements.

Are fire alarm contractors required to use MFA?

Multifactor authentication is a strong security practice, particularly for remote and privileged access, and is recommended by CISA where supported. Do not cite MFA as a universal, stand-alone requirement for every fire alarm product without checking the exact applicable NFPA 72 provisions, equipment and project requirements.

Can a cybersecurity patch be installed remotely?

Some cybersecurity software changes may be permitted through remote access under the applicable NFPA 72 provisions and manufacturer instructions. Determine the approved access method and any testing or documentation requirements before proceeding.

Does NFPA 72 (2025) automatically apply to older California systems?

No blanket retrofit conclusion follows solely from the January 1, 2026 code effective date. The scope of work, adopted regulations, existing-building provisions, amendments and AHJ requirements must be evaluated.

Authoritative References and Further Reading

  1. NFPA: NFPA 72, National Fire Alarm and Signaling Code — current and prior editions, amendments and free-access options.
  2. California Building Standards Commission: 2025 California Building Standards Code — official state code access and effective date.
  3. CAL FIRE Office of the State Fire Marshal: Information Bulletins — Bulletin 26-002 confirms the California NFPA 72 (2025) code reference.
  4. Automatic Fire Alarm Association: NFPA 72 (2025) changes presentation — useful historical explanatory material; prepared before final publication and not a substitute for final adopted text.
  5. NIST SP 800-82 Rev. 3: Guide to Operational Technology Security — September 2023.
  6. CISA: Internet Exposure Reduction Guidance — June 4, 2025.

Technical and editorial note: This is an educational draft for professional review. Exact section wording, adopted editions, local amendments, manufacturer listing requirements, applicable security-level evidence, software update responsibilities and testing obligations must be checked against the governing documents before publication or field application. This article does not certify any system, approve an installation, authorize network changes or replace qualified design and AHJ review.