10.2 Cut Sheets, Calculations & Sequence of Operation

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

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

1. Model number block matching the schedule
2. Standby and alarm currents used in battery calcs
3. Candela/watt settings and corresponding currents for VD calcs
4. Compatibility statements (which panels/modules are listed for use together)
5. Special application notes (sleeping rooms low-frequency, outdoor, hazardous, explosion-proof) when those symbols appear on plans
6. 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:

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:

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:

1. Change a candela setting on the schedule → update cut-sheet highlight, battery table row, and VD circuit row.
2. Add a booster power supply on the riser → new battery calc (or expanded calc) and new circuit VD sheets.
3. 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:

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)

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

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

1. Primary control unit model and software/firmware identity if required for the feature set
2. Device models intended for that control unit’s SLC/NAC architecture
3. Manufacturer compatibility publication excerpt or statement when mixed components are proposed
4. Communicator/transmission equipment compatibility with the supervising-station path design
5. 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)

Level II Document Set for These Elements

Recommended order when building the package internals:

1. Freeze device schedule (models + settings + quantities)
2. Attach matching cut sheets; highlight currents/settings
3. Draft SOO from interfaces and notification strategy
4. Compute battery and VD from schedule + routing assumptions
5. Reconcile riser circuit IDs to calc sheets
6. Run compatibility check against manufacturer documentation
7. 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.”