Study guide

12.2 Zone Schedules & Legends

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

12.2 Zone Schedules & Legends

Key Takeaways Explain This Topic AI

Device schedules list type, location, circuit, address/zone, candela or wattage, base type, and other attributes the plan symbol cannot carry alone.

Conventional systems organize initiation by zone/IDC maps; addressable systems organize by node/loop/point maps—schedules must use the correct model.

A complete legend defines every symbol and abbreviation used on the drawings; incomplete legends are a common AHJ rejection reason.

Wire gauge and cable-type schedules (or notes) document pathway conductors so installers and calc sheets share one assumption set.

  • Schedule, legend, plan, and riser must agree—conflicts are defects, not “field flexibility.”
  • Last updated: August 2026

12.2 Zone Schedules & Legends

Quick Answer: Plans show where ; schedules and legends define what each symbol is and how it is wired and identified. Build a device schedule (type, candela, base, circuit, address/zone), a zone or node map that matches conventional vs addressable architecture, a complete legend , and wire/cable gauge notes that feed installation and Chapter 13 calcs. If schedule and plan disagree, the set is not ready.

Section 12.1 covered symbols, risers, and plan orientation. This section is the tabular and legend layer of blueprint 2.3.3 —the content AHJs and estimators read when symbols alone are insufficient.

Why Schedules Exist

A floor plan symbol answers location. It rarely carries every attribute needed to buy, install, program, and calculate the system:

  • Attribute Why a schedule (or structured note) helps
  • Device type / model family Photo vs heat vs multi-criteria; speaker-strobe vs horn-strobe
  • Candela / setting Notification performance and load
  • Speaker wattage tap EVACS loading

Base type Standard, relay, isolator, sounder base, CO base, etc.

  • Circuit ID SLC/NAC/IDC affiliation
  • Address or zone Programming and testing identity
  • Height / mounting Wall strobe height, detector special mounting
  • Interface tag AHU-3, Elevator 2, Riser 1 waterflow
  • Remarks Weatherproof, explosion-proof, dormant until phase 2

Without schedules, installers guess candela, programmers invent descriptors, and voltage-drop authors invent loads.

Device Schedule Anatomy

There is no single mandatory table format, but Level II-ready schedules typically include columns such as:

  • Column Example values Notes
  • Mark / ID SD-214, L1D042, P-12 Must match plan callout
  • Type Photo smoke, fixed heat 135°F, manual pull Align with legend text
  • Location Floor 2 corridor outside 214 Human-readable
  • Circuit SLC-1, NAC-3, IDC-2 Align with riser
  • Address / zone 1-042 / Zone 4 Architecture-specific
  • Candela / W 75 cd wall; 1/4 W tap Notification / speaker
  • Base / options Isolator base; relay base Affects parts and SLC behavior
  • Manufacturer/model As submitted Must match cut sheets
  • Remarks Weatherproof; phase 2 shell Scope control
  • Candela and base type—frequent omissions

Notification appliance schedules that list “strobe” without candela and wall vs ceiling are incomplete for serious review. Detector schedules that omit isolator/relay/sounder base hide SLC segment design and auxiliary functions. Level II reviewers treat those blanks as defects, not optional polish.

Counts and roll-ups

Useful schedules also support counts by type and by circuit :

  • Number of speaker-strobes on NAC-2 at each candela
  • Number of addressable points on SLC-1 (including modules)
  • Conventional device counts per IDC for wire and EOL planning

Those roll-ups become inputs to battery, voltage-drop, and amplifier calcs in Chapter 13 and related design sheets.

  • Zone Maps vs Node/Point Maps
  • Conventional: zone (IDC) thinking

A zone schedule / zone map for conventional initiation typically shows:

  • Zone number and signal type (alarm zone, supervisory zone, etc.)
  • Description ("Floor 2 smoke," "Sprinkler riser 1 waterflow," "Valve tampers")
  • Device types included and approximate count
  • FACU terminal or IDC number
  • EOL location note

Annunciation may be by zone LED or zone text—not by individual detector identity. Drawings should not pretend each conventional smoke has a unique digital address.

Addressable: node / loop / point thinking

Addressable documentation replaces pure zone lists with point maps :

  • Loop/SLC number and pathway class
  • Point address and device type
  • Software zone or group assignment (for programming logic and selective evacuation)
  • Module points tied to mechanical or suppression interfaces

Software zones on addressable systems are logic groups—they are not the same thing as a conventional IDC. Exam stems often test whether you know that an addressable “Zone 3” in programming may be a display/control group , while the physical pathway is still SLC-1 Class A with individual addresses.

  • System style Primary identity on drawings Typical “zone” meaning
  • Conventional IDC / zone number Physical initiating circuit
  • Addressable Loop + device address Often a software group or geographic label for logic/annunciation
  • Hybrid Both Label clearly—never assume one scheme

Scenario: A renovation adds addressable detection but leaves conventional NAC circuits. The schedule must show addressable point IDs for smokes and circuit/NAC IDs for horns-strobes. A single “Zone 2” column for everything confuses both the programmer and the AHJ.

Legend Completeness

The legend is the dictionary of the drawing set.

What belongs in a complete legend

Every device symbol used on any sheet (smoke, heat, duct, pull, beam, flame, modules, appliances, panels, boosters, EOL markers, cloud revision marks if used as symbols)

  • Line types (existing to remain, new, demo, future, match line)
  • Abbreviations (FACU, SLC, NAC, IDC, EVACS, SS, AHU, EOL, CD, WP)
  • General notes pointers ("See FA-001 for mounting heights")
  • Symbol variants (ceiling vs wall strobe; weatherproof pull)
  • Incomplete legend failures
  • Failure Result
  • Symbol on plan, missing from legend Installer/AHJ cannot confirm device type
  • Legend shows old symbols after CAD library change Schedule says speaker-strobe; legend still shows horn
  • Abbreviations undefined (e.g., “ISOL,” “SOB”) Base types misordered
  • One legend only on Sheet 1, not referenced Later sheets printed alone are unreadable

Best practice: full legend on a general sheet and a condensed legend on busy plans, or a clear “LEGEND ON FA-000” note on every plan sheet.

Wire Gauge and Cable Schedules

Basic technical drawings should state what conductors are assumed—not leave wire size as tribal knowledge.

Typical content

  • Item Example Used for
  • Circuit class of service SLC, NAC, speaker, 24 V aux Separation and method
  • Cable type FPLP, FPLR, CI cable, twisted pair per manufacturer NEC 760 + survivability
  • Conductor size 16 AWG, 14 AWG, 12 AWG Voltage drop, terminations
  • Pairs / conductors 1-pair, 2-conductor, 4-conductor Pulls and T-taps
  • Raceway assumption EMT, IMC, cable tray Conduit fill notes
  • Color code (if project standard) Per spec Consistency

Wire schedules may be a table, a general note block, or both. What matters is one authoritative assumption set shared by:

  • Installers ordering cable
  • Voltage-drop calculations (resistance per foot depends on AWG)
  • Conduit-fill calculations (Chapter 9 of the NEC uses conductor dimensions)

Trap: Plans say “14 AWG NAC” in a general note while the voltage-drop sheet used 12 AWG to “make the drop pass.” That is a documentation integrity failure—not clever engineering. Either change the design wire size everywhere or fix the layout/load.

Cross-Document Consistency Checks (Level II Review Habit)

Before submittal or rough-in, walk this checklist:

Count: Devices on plans ≈ devices on schedule (explain residuals: spares, future, demo).

Identity: Every schedule Mark appears once on a plan (or is explicitly “spare in box”).

Circuit: Schedule circuit IDs exist on the riser.

Type: Legend wording matches schedule type matches cut sheet.

Notification attributes: Candela/wattage present for appliances that need them.

Architecture: Conventional zones vs addressable points used correctly.

Wire: Gauge/type notes match calc sheet inputs.

Interfaces: Waterflow/tamper/elevator/HVAC tags match the sequence of operation matrix.

Scenario: Schedule lists 40 × 75 cd strobes on NAC-1. Plan shows 40 symbols but 10 are tagged NAC-2. Riser loads NAC-1 with 40. Voltage drop and battery alarm load will not match the real building. Consistency checks catch this before copper is pulled.

Zone/Node Maps for Annunciation and Control

Beyond parts lists, schedules support operational geography :

  • Which devices light which annunciator LEDs or text lines
  • Which floors evacuate or relocate together (EVACS)
  • Which points drive elevator recall vs HVAC shutdown

A simple zone map graphic (building outline with zone boundaries) helps conventional systems and some AHJs. Addressable projects often use point lists by floor plus a cause-and-effect matrix (Chapter 10 package content). Level II drawing work keeps those operational maps aligned with physical circuit drawings.

Exam Focus

Expect stems that:

  • Ask what belongs in a device schedule vs only on a symbol
  • Distinguish conventional zone identity from addressable point identity
  • Flag an incomplete legend
  • Tie wire gauge notes to voltage-drop assumptions
  • Identify plan/schedule/riser conflicts as submittal defects

Prefer answers that demand complete, coordinated tabular data—not “the symbol is enough” or “the field will decide candela.”