NV Fire Alarm study materials
NV Fire Alarm study resources

NV Fire Alarm: Plan Review and System Documentation

NV Fire Alarm · Work through your exam, one topic at a time.

All guide sections

Plan Review and System Documentation

What this domain covers

The submittal package, what reviewers check, and the closeout documents that make a system acceptable at final inspection.

Core rules

  • NFPA 72 Chapter 7 requires submittal documents that typically include scaled drawings, a riser diagram, device legend and symbols, the sequence of operations matrix, battery and voltage-drop calculations, manufacturer data sheets, site-specific software documentation, and evidence of installer qualifications.
  • The sequence of operations is the heart of the review: it must state what happens for each alarm, supervisory, and trouble condition, including fire-safety functions, timing, and annunciation.
  • At completion, deliverables include the record of completion, record of inspection and testing, as-built drawings, and operation and maintenance manuals; the owner is trained and the records are kept on site.
  • Nevada submissions go to the authority having jurisdiction - the State Fire Marshal or a delegated local fire department - and work may not start before approval. Final acceptance testing precedes the certificate of occupancy.

Worked example

A reviewer returns a plan because the corridor notification appliances are shown without candela and no battery calculation is attached. Reasoning: without candela the reviewer cannot check spacing against the table or confirm visual coverage; without the calculation the secondary power cannot be verified. The response is to add candela values, a coverage layout, and a calculation listing standby and alarm loads with the 1.2 factor - not to argue that the equipment is listed.

Traps that cost marks

Generic manufacturer cut sheets instead of project-specific data; a sequence of operations that omits supervisory or trouble responses; missing voltage-drop calculation on long NACs; submitting one revision and installing another; forgetting owner training and as-builts.