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.
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.
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 item | Status | Reviewer 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
| Category | Items to verify before uploading | Typical reviewer question |
|---|---|---|
| Code basis | 1. Address and scope; 2. occupancy/use; 3. adopted editions and amendments; 4. existing/new scope boundaries | What criteria govern this design? |
| Plans | 5. legible scale; 6. room labels; 7. device legend; 8. mounting/coverage notes; 9. addresses and device schedule | Can every device be located and counted? |
| System architecture | 10. riser; 11. circuits/pathways; 12. cable type; 13. panel/power supplies; 14. interface locations | How is each device connected and powered? |
| Calculations | 15. battery; 16. NAC voltage drop; 17. amplifier load where applicable; 18. circuit capacity | Do actual connected loads match the schedules? |
| Operation | 19. input/output matrix; 20. interface narrative; 21. transmission/monitoring method | What happens for each initiating condition? |
| Product/closeout | 22. manufacturer data; 23. listing/compatibility; 24. test/inspection plan; 25. revision coordination | Can 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
| Comment | Likely cause | Prevention |
|---|---|---|
| Device counts differ | Floor plan and schedule revised independently | Count and reconcile every device ID before export |
| Incomplete battery calculation | Remote supplies or interfaces omitted | Use separate calculations for each power source |
| Unclear elevator interface | Generic relay symbol without sequence | Coordinate detector and elevator group mapping |
| Missing control sequence | Matrix only covers alarms | Include supervisory, trouble, restoration and relevant interlocks |
| Cut sheet conflicts with plans | Model changed without schedule update | Validate model numbers, listings and quantities |
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.
No comments:
Post a Comment