Study guide
10.2 Cut Sheets, Calculations & Sequence of Operation
NICET Fire Alarm Systems Level II Exam
Track your progress as you read
Finished sections get a check mark.
1 Exam Overview & Open-Book Strategy
1.1 Exam Facts, Eligibility & Logistics 1.2 Open-Book References & On-Screen Navigation 1.3 Certification Path & Performance Measures
2 Installation: Work Planning
2.1 Work Plans from Field Conditions 2.2 Drawings, Specs & Code Interpretation 2.3 Jobsite Safety & Trade Coordination
3 Installation: Circuits, Pathways & Survivability
3.1 Pathway Classes A, B, C, D, E, N & X 3.2 Survivability Pathway Levels 0–3 3.3 NEC Article 760, NPLFA/PLFA & Raceways 3.4 SLC Topology, T-Taps & Supervision
4 Installation: Equipment
4.1 Initiating Devices (Level II Applications) 4.2 Notification Appliances & NAC Design 4.3 Control/Monitor Modules & FACU Hardware 4.4 Voice EVACS Speakers & Intelligibility Basics
5 Installation: Commissioning
5.1 Acceptance Testing & Commissioning Sequence 5.2 Record of Completion & As-Builts 5.3 Functional Verification of Interfaces
6 Installation: System Interfaces
6.1 Elevator Recall Phase I & II 6.2 Shunt Trip & Heat Detector Placement 6.3 HVAC Shutdown & Duct Smoke Detectors 6.4 Suppression Interconnections (Waterflow, Tamper, Releasing, Clean Agent, Hood)
7 Maintenance: Periodic Testing
7.1 ITM Framework (NFPA 72 Chapter 14) 7.2 Device Test Methods & Frequencies 7.3 Interface, Waterflow & Tamper Tests 7.4 EVACS, Elevator & Special Function Tests
8 Maintenance: Impairments & Troubleshooting
8.1 Impairment Programs & AHJ Notification 8.2 Troubleshooting SLC, NAC & Power Faults 8.3 Corrective Actions & Retest Requirements
9 Maintenance: Documentation
9.1 Required Records & Retention 9.2 Inspection & Test Reports 9.3 Record Drawing Updates After Changes
10 Submittals: Shop Drawing Packages
10.1 Shop Drawing Package Contents 10.2 Cut Sheets, Calculations & Sequence of Operation 10.3 AHJ Submittal Expectations
11 Submittals: Site Survey
11.1 Occupancy, Construction & Fire Protection Features 11.2 Layout Constraints & Field Verification 11.3 Pathway Routing & Survivability Field Checks
12 Submittals: Basic Technical Drawings
12.1 Symbols, Risers & Floor Plans 12.2 Zone Schedules & Legends 12.3 Drawing Notes for Voltage Drop & Conduit Fill
13 Submittals: Power Supply & Loading
13.1 Standby & Alarm Load Basis (24 h + 5/15 min) 13.2 Battery Sizing with 20% Aging Derating 13.3 Voltage Drop Calculations 13.4 Conduit Fill & Wire Sizing (NEC Chapter 9)
14 Layout Knowledge: Supervising Station
14.1 Supervising Station Types (Chapter 26) 14.2 Transmission Paths & 90-Second Alarm Window 14.3 Protected Premises vs Supervising Station Roles
15 Management & Supervision
15.1 Coordinate Work Activities 15.2 Reporting Progress & Problems 15.3 Ethics & NICET Code of Conduct 15.4 Safety Leadership & Multi-Trade Coordination
10.2 Cut Sheets, Calculations & Sequence of Operation
Key Takeaways Explain This Topic AI
Cut sheets (product data) must match the manufacturer and model numbers shown on drawings and schedules; mismatched or generic catalog pages are a common rejection reason
Battery and voltage-drop calculations support the drawings—they use the same device counts, currents, circuit assignments, and length assumptions reflected in the package (detailed methods in Chapter 13)
A sequence of operation (cause-and-effect matrix) defines alarm, supervisory, trouble, and emergency control function behavior so programming and testing match design intent
Compatibility lists and listing constraints matter when panels, devices, power supplies, and communicators are mixed—submittals should show an intended listed system approach
Last updated: August 2026
10.2 Cut Sheets, Calculations & Sequence of Operation
Quick Answer: Drawings show where and what symbols ; cut sheets prove which listed products ; calculations prove power and circuit performance ; the sequence of operation proves what the system does on each event. All four must tell the same story. Level II technicians assemble matching model numbers, project-specific calcs, and a clear alarm/supervisory/trouble/emergency-control matrix—not a random stack of PDFs.
Section 10.1 listed package contents. This section is the technical glue : product data, calculations, sequence of operation (SOO), and compatibility.
- Cut Sheets (Equipment Product Data)
- Purpose
Cut sheets (data sheets / product data submittals) allow reviewers and installers to verify:
- Listing marks and applicable standards (e.g., UL/ULC categories relevant to the product type)
- Electrical ratings (voltage, current draw standby/alarm, NAC capacity, battery charger ratings)
- Environmental limits (temperature, humidity, outdoor ratings)
Features claimed on drawings (candela options, multi-candela, speaker watt taps, detector type, CO vs smoke, etc.)
Installation constraints that affect layout (spacing guidance references, mounting orientations, compatibility notes)
Matching model numbers
- Drawing / schedule shows Cut sheet must
- Exact manufacturer + model (including key suffixes) Be for that model family/configuration
Multi-candela appliance “set to 75 cd” Show that candela is a listed setting and current draw used in calcs matches that setting
- Specific detector type (photo, heat ROR/FT, duct, beam) Match type and listing
- Communicator / network module model Match the path technology proposed
Bad practice: Submitting a 40-page full catalog with a sticky note “see horns.” Reviewers should not hunt. Good practice: Submit the specific data sheet (or clearly bookmarked excerpt) for each unique model, with the selected options highlighted.
Scenario: Schedule lists Manufacturer A horn-strobe model HS-75. Cut sheet attached is Manufacturer B’s generic brochure. Battery calc uses currents from Manufacturer C’s white paper. The package is inconsistent and will draw comments—or field procurement of the wrong device.
- What to highlight on cut sheets for Level II packages
- Model number block matching the schedule
- Standby and alarm currents used in battery calcs
- Candela/watt settings and corresponding currents for VD calcs
- Compatibility statements (which panels/modules are listed for use together)
Special application notes (sleeping rooms low-frequency, outdoor, hazardous, explosion-proof) when those symbols appear on plans
- Power-limited / circuit class information when the sheet provides listing constraints used in design notes
- Substitution control
If purchasing substitutes a “similar” model after approval:
- Treat it as a design/document change , not a free swap
- Update schedules, calcs, and cut sheets
- Resubmit when AHJ/contract requires approval of substitutions
Never leave approved cut sheets in the cabinet while installing a different listed product without reconciliation
Calculations That Support Drawings
Chapter 13 teaches battery sizing and voltage-drop methods in depth. For submittal assembly, master the relationship between calcs and drawings.
Battery calculations (package role)
Battery calcs answer: Will secondary power support required standby and alarm durations with required design factors?
Package expectations:
- Calc element Must align with
- Device quantities by type BOM / device schedule totals
- Standby unit loads Cut-sheet standby currents
- Alarm unit loads Cut-sheet alarm currents at selected settings
Standby & alarm time bases System type/features and NFPA 72 required capacities for the design (e.g., common protected-premises secondary power concepts such as 24 h standby plus alarm duration appropriate to the system—confirm exact requirements for the system type in the adopted NFPA 72)
Aging / design factor Project method (commonly a 20% capacity increase/derating practice for batteries—apply per design standard/manufacturer and Ch 13 methods)
Selected battery amp-hour rating Equal or greater than required capacity
Exam trap: Believing battery calcs are optional “because the panel has a charger.” The charger does not replace documented secondary capacity design.
Voltage-drop calculations (package role)
Voltage-drop calcs answer: At alarm load, will the last appliance on the circuit still receive adequate voltage?
Package expectations:
- Calc element Must align with
- Circuit ID and appliance list Plan/riser NAC (or equivalent) assignments
- Appliance current at setting Cut sheet + schedule candela/watt
- Wire size and length Spec notes and planned routing (field length changes require recalc)
- Source voltage assumption Panel/booster ratings and design method
- Result vs minimum appliance voltage Listing/manufacturer minimums used by the designer
If plans show three NACs but only one VD sheet for “typical circuit,” the package is weak unless the designer proves the worst case and the circuits are truly similar.
Cross-reference discipline (Ch 13 link)
When you study Chapter 13 methods, always loop back here:
Change a candela setting on the schedule → update cut-sheet highlight, battery table row, and VD circuit row.
Add a booster power supply on the riser → new battery calc (or expanded calc) and new circuit VD sheets.
Lengthen a homerun after field survey → update VD; do not keep the schematic 50 ft assumption if the building needs 350 ft.
Level II assembly rule: Calculations are not a separate universe. They are numeric twins of the drawings and product data.
- Sequence of Operation (SOO / Cause-and-Effect)
- Purpose
The SOO states how the system shall behave . Without it, programmers invent logic, testers guess pass criteria, and AHJs cannot confirm emergency control functions.
Matrix structure
A practical SOO is often a matrix or structured table:
- Input event Alarm Supervisory Trouble Notification SS signal Elevator HVAC Doors Other ECF
- Manual pull Yes — — General or zone per design Alarm Per design Per design Per design …
- Smoke detector (area) Yes — — … Alarm Recall if lobby/elevator related per design … … …
Duct smoke Often supervisory or alarm per design/code path Common supervisory for HVAC — May be limited Supervisory or alarm per design — Shutdown AHU — …
- Waterflow Alarm — — … Alarm — — — …
- Tamper / valve supervisory — Yes — Often none or limited Supervisory — — — …
- Low battery / NAC open — — Yes Silenceable trouble indicators per design Trouble — — — …
Your project matrix must match the features drawn . If the riser shows elevator interface modules, the SOO must describe Phase I recall initiation logic at the design level. If kitchen hood suppression is monitored, define alarm/supervisory behavior and any output functions.
Alarm vs supervisory vs trouble (do not blur)
- Condition type Typical meaning in SOO language
- Alarm Fire or life-safety emergency input requiring occupant notification and alarm transmission as designed
Supervisory Off-normal supervisory condition (e.g., valve tamper, certain duct/supervisory points) needing staff response but not full fire-evacuation logic unless design says otherwise
Trouble Fault in wiring, power, communications, or equipment integrity
Exam trap: A stem where waterflow is treated only as trouble, or tamper only as alarm, contrary to standard design intent. Know the categories; confirm the project’s matrix for odd AHJ-driven variations.
Emergency control functions (ECF)
SOO rows should address emergency control functions when the project includes them, for example:
- Elevator recall and related hoistway/machine room detection logic (see interfaces chapter concepts)
- HVAC shutdown / smoke control related outputs as designed
- Door holder release / stair door unlock as designed
- Suppression releasing or monitoring interlocks
- Occupant notification voice messages or tone patterns when EVACS is provided
Level II depth: you can read and assemble an SOO that matches devices on the drawings. Detailed elevator/HVAC design rules live in interface and code sections—but a package without ECF narrative when interfaces are drawn is incomplete.
Programming and test linkage
SOO says Programming must Testing must
Waterflow → general alarm + SS alarm Map waterflow point to alarm group Flow water, verify evacuation and SS receipt
- Tamper → supervisory only Map to supervisory, not general alarm Close valve switch, verify supervisory path
- Lobby smoke → elevator recall Map to recall group / relay logic Functional recall test with coordination
If the SOO and program disagree, acceptance is not complete even if every detector LED lights.
Compatibility Lists & Listed System Approach
Fire alarm components are not freely mix-and-match. Compatibility and listing practice generally require that initiating devices, control units, power supplies, and certain modules be used in listed compatible combinations per manufacturer compatibility documentation.
- What submittals should show
- Primary control unit model and software/firmware identity if required for the feature set
- Device models intended for that control unit’s SLC/NAC architecture
- Manufacturer compatibility publication excerpt or statement when mixed components are proposed
- Communicator/transmission equipment compatibility with the supervising-station path design
Releasing device compatibility when suppression releasing is in scope (high-risk area—follow listing rigorously)
Scenario: Drawings specify Panel Brand X. Cut sheets include Brand Y detectors not on Brand X’s compatibility list. The AHJ (or a competent reviewer) flags listing risk. Fix: change devices to compatible models or change panel approach—with full package update.
Power supplies and boosters
Booster/NAC extender supplies must be part of the same coherent design: cut sheets, battery calcs per supply, VD per output, and riser location. Do not add a booster in the field for “voltage drop relief” without updating the package.
Common Inconsistency Patterns (Catch Before Submittal)
- Pattern Why it fails
- Schedule model ≠ cut sheet model Product identity broken
- Candela on plan ≠ candela in VD current Circuit may be undersized on paper or overstated
- Device count on battery sheet ≠ BOM Secondary power proof invalid
- SOO omits elevator though modules shown Incomplete operational design
- Riser shows dual-path SS; cut sheets show single path only Transmission design unclear
- Spec says low-frequency sounders in sleeping areas; cut sheets are standard 3 kHz only Feature mismatch
- Class A drawn; BOM quantities for EOL hardware imply Class B only Pathway class inconsistency
- Level II Document Set for These Elements
Recommended order when building the package internals:
- Freeze device schedule (models + settings + quantities)
- Attach matching cut sheets; highlight currents/settings
- Draft SOO from interfaces and notification strategy
- Compute battery and VD from schedule + routing assumptions
- Reconcile riser circuit IDs to calc sheets
- Run compatibility check against manufacturer documentation
- Only then issue for PE/designer review and AHJ submittal
- Exam Focus
Choose answers where cut sheets match model numbers , calcs use the same counts/settings as drawings , and SOO distinguishes alarm, supervisory, trouble, and emergency control functions . Prefer packages that include compatibility evidence for the intended equipment set. Reject generic catalogs, orphaned calcs, and “program it later without a matrix.”