10.1 Shop Drawing Package Contents

10.1 Shop Drawing Package Contents

Quick Answer: A fire alarm shop-drawing package is the coordinated set used for AHJ/owner review and for installation—not a single floor plan. Typical contents: cover sheet, floor plans with devices, riser diagram, typical details, battery calculations, voltage-drop calculations, equipment data sheets (cut sheets), sequence of operation, and bill of materials / device schedule, plus legends, notes, and code-edition identification. NICET Level II blueprint 2.3.1 (submittal preparation) tests your ability to assemble project information into that package. You support design and document control; you do not invent seal authority you do not hold.

Domain 2.3 Submittal Preparation & System Layout is roughly 20–30% of the Level II exam. Chapter 10 starts that domain: what a complete package looks like before you dive into cut sheets and calcs (10.2), AHJ expectations (10.3), site survey (Ch 11), drawing graphics (Ch 12), and power loading (Ch 13).

Why Package Completeness Matters

Shop drawings answer three questions for three audiences:

A pretty floor plan without battery calcs, without a sequence of operation, or with cut sheets that do not match the model numbers on the drawings is an incomplete submittal—even if device spacing looks right.

Exam trap: Treating “shop drawings” as only architectural-style floor plans and ignoring calculations, product data, and operational narrative.

Typical Package Contents (Level II Inventory)

Exact sheet titles vary by firm CAD standard and AHJ checklist, but Level II candidates should recognize this core inventory:

Cover sheet discipline

A useful cover sheet is more than a logo. Include:

1. Project name, address, and occupancy description as known
2. Drawing list (sheet numbers and titles) with current revision
3. Applicable codes/standards and editions (for current NICET FAS II references, think NFPA 72 (2022), NFPA 70 (2020), and awareness of IBC (2021) where the exam allows it—always match the adopted editions on a real job)
4. Designer of record / installing contractor / owner contacts as required by local process
5. Seal/stamp space when a PE (or other licensed designer) is required by jurisdiction or contract
6. Submittal purpose note (e.g., “For permit,” “Resubmittal #2—responds to comments dated …”)

Scenario: A package is submitted with beautiful plans but no code-edition note. The AHJ reviews against a newer local amendment set than the designer assumed. Half the comments are edition conflicts that a clear cover sheet and notes block would have prevented.

Floor plans with devices

Plans should allow a stranger to find every life-safety device. Minimum concept set:

• North arrow, scale, and match lines for multi-sheet floors
• Room names/numbers consistent with architectural backgrounds
• Device symbols with unique IDs or callouts that tie to schedules
• FACU, remote annunciators, printers, radio/DACTs, and power supplies shown—not only smokes and horns
• Interfaces called out (elevator lobbies, duct detectors, sprinkler risers, kitchen hood, door holders) at least by symbol/note
• Notification appliance candela or wattage settings when they affect design compliance and voltage drop

Field failure: Plans show generic “S” smoke symbols with no address or circuit, while the schedule is blank. Installers invent addresses; as-builts never catch up.

Riser diagram

The riser is the system nervous system map:

• Control units and subpanels/nodes
• Signaling line circuits and notification circuits as design entities (Class A/B/N/X as applicable—detail in Ch 3/12)
• Secondary power locations
• Pathway to supervising station
• Major emergency control outputs (elevator, HVAC, door release, suppression releasing) at a system level

Risers do not replace floor plans; they explain connectivity plans cannot show in one view.

Typical details

Details answer “how high,” “how mounted,” and “how protected.” Examples:

• Manual station mounting height and reach ranges per accessibility rules used on the project
• Wall vs ceiling notification appliance orientation notes
• Weatherproof or hazardous-location appliance notes where applicable
• Detector placement relative to supply diffusers (high-level awareness; spacing rules deepen in layout chapters)
• Fire-stopping / penetration notes when the fire alarm drawings carry them

Calculations (preview—full method in Ch 13)

Level II submittal work expects battery and voltage-drop calculations to support the drawings. Package completeness means the calcs:

• Use device counts and currents consistent with the schedules and plans
• State standby and alarm time bases required by the system type/features
• Show wire size and length assumptions for NAC (and similar) circuits
• Are revised when device counts or cable routes change before resubmittal

Do not attach a generic manufacturer blank with no project numbers.

Equipment data sheets, SOO, and BOM

These three close the loop between “drawn” and “buy/build/program”:

• Cut sheets prove the listed product exists and matches the model string on the drawings
• Sequence of operation proves the system will do more than “sound horns”—it defines supervisory vs alarm vs trouble and emergency control functions
• Bill of materials proves quantities and settings (candela, candela switches, speaker watt taps) match the design intent used in calcs

Section 10.2 expands these items.

NFPA 72 Documentation Expectations at Level II Depth

NFPA 72 requires documentation so systems can be installed, inspected, tested, maintained, and modified correctly. For Level II, remember the roles of document types, not only form titles:

Documentation content commonly associated with design/installation packages includes (concept list):

• Floor plan layouts and equipment locations
• Riser and wiring/pathway information sufficient for the system class and architecture
• Equipment data (manufacturer, model, listing)
• Battery and voltage-drop calculations as applicable
• Sequence of operation / input-output matrix
• Compatibility information for system components where required by listing practice
• Software or configuration identity when programmable systems are used (at least by project closeout; often needed earlier for review of EVACS/complex matrices)

Level II “assemble project information” depth means you can:

1. Collect architectural backgrounds, device counts, manufacturer selections, and field survey notes into a coherent package
2. Spot internal inconsistencies (schedule says 75 cd, plan note says 15 cd, cut sheet shows a different model)
3. Include the calcs and SOO the drawings imply
4. Track revisions when reviewers or field conditions change scope
5. Know when a PE seal, engineer of record revision, or designer approval is required before you change layout criteria

You are not expected on every stem to act as the licensed designer of record. You are expected to know what a complete package contains and when something is missing.

IBC Fire Alarm Plan Review Awareness

Model building/fire codes (IBC/IFC framework and local adoptions) typically require construction documents for fire alarm systems to be submitted for permit/plan review before installation. Level II awareness points:

Scenario: A contractor installs devices from a sales sketch while the official submittal is still in review. The AHJ rejects the package and requires different candela and additional pull stations. Half the install is rework. Level II lesson: approved (or explicitly allowed deferred) documents drive the field, not the truck stock.

Shop Drawings vs Record Drawings

Never leave the job with only the original unrevised shops if the field moved devices, added boosters, or changed addresses. Submittal packages start the document chain; commissioning and maintenance continue it.

Level II Assembly Workflow (Practical)

1. Confirm project codes/editions and AHJ submittal checklist.
2. Gather architectural backgrounds, fire protection features, and survey notes (Ch 11).
3. Build device schedules and plans together so counts never diverge.
4. Draft riser and pathway class/survivability notes with the design approach.
5. Select listed equipment; attach matching cut sheets.
6. Write SOO matrix for alarm, supervisory, trouble, and emergency control functions.
7. Run battery and voltage-drop calcs from the same schedule/lengths used on drawings.
8. Assemble cover sheet, index, BOM, and revision block.
9. Internal consistency check before first submittal.
10. After comments, cloud revisions and respond item-by-item (Section 10.3).

Consistency Checklist Before Submittal

• Every plan symbol appears in the schedule/BOM (and vice versa within scope)
• Model numbers on plans/schedules match cut sheets
• Battery load table device counts match schedule totals for powered devices
• Voltage-drop circuits match NAC (or equivalent) assignments on riser/plans
• SOO includes sprinkler waterflow/tamper, elevator, HVAC, doors, and suppression interfaces that the drawings show
• Cover sheet lists current sheet index and code editions
• Revision number is unique and dated
• Compatibility/listing notes exist for mixed-component systems where required

Exam Focus

Prefer answers that define a complete multi-document package (plans + riser + details + calcs + cut sheets + SOO + BOM/cover), that treat Level II work as assembling consistent project information under design authority, and that distinguish shop from record drawings. Reject “floor plans only,” “calcs optional if the panel is listed,” and “install first, submit later” as default practice.