NICET FAS Level III: Circuit Decisions That Count

Study FAS III by practicing defensible design decisions: classify circuits and document why, calculate voltage drop segment by segment, build battery calculations you can defend line by line, chain spacing adjustments in order, separate survivability from redundancy, and review records the way a careful reviewer would trace a design.

Class A versus Class B: what actually changes when you convert a circuit

A Class B circuit ends at an end-of-line resistor and reports an open as a trouble signal; a Class A circuit loops back to the panel and continues operating past a single open. Conversion changes wiring, supervision behavior, and documentation, not device function.

Trace both paths on paper before comparing them. In Class B (circuit style B), current leaves the panel, passes every device, and terminates in an end-of-line resistor; a break anywhere opens the circuit and the panel loses the supervisory current, so it annunciates trouble. In Class A (circuit style A), the conductor returns to the panel, the panel isolates the break, and devices stay powered from both directions. Note what does not change: a single ground fault produces trouble on either style, and a fire that destroys both conductors in one raceway defeats both.

The conversion decision is an engineering trade, not an upgrade reflex. Returning the loop costs conductor and labor, and a Class A designation must appear consistently on drawings, in calculations, and on the completion record. Work through the table below, then state the reason for your choice in writing; a classification that cannot be explained in one sentence is a weak answer in review.

Scenario: a renovation converts an existing Class B initiating device circuit to Class A by adding a return conductor, but the return is pulled through the same conduit run as the outgoing cable. The plausible mistake is calling the circuit 'upgraded' on the record of completion. The better decision is to recognize that a single event crushing that conduit can sever both directions at once, so the loop provides little real benefit routed that way. Rerouting the return along a separate physical path, or honestly documenting Class B with the existing routing, is the defensible outcome because the classification should describe what the wiring can actually survive.

NAC voltage drop: why checking only the end-of-line device hides undervoltage

Voltage accumulates loss along every segment, and each segment carries a different current. A single end-of-line estimate using total length and total current can look compliant while an appliance mid-circuit, or under the wrong assumptions, sits below its listed operating voltage.

Work the circuit as a chain of segments. For each segment, use the current actually flowing through it (everything downstream of that point), the resistance of both conductors (out and back), and record the running voltage. Compare the voltage at each appliance, not just the last one, against the manufacturer's listed operating range for the selected candela rating. Two datasheet facts drive the outcome: appliance minimum voltage, and resistance per unit length of the conductor size you chose.

Worked example (labeled, simplified): a 24.0 V notification appliance circuit on 18 AWG wire carries 1.5 A through a 100 ft segment with 0.4 ohms of round-trip resistance, dropping 0.6 V. At the junction, 1.0 A continues 200 ft to the last strobe through 1.6 ohms round trip, dropping another 1.6 V, leaving 21.8 V at the final appliance. The plausible mistake: the designer multiplies wire resistance by the one-way distance only, roughly halving the computed loss, and concludes every appliance sits comfortably above its minimum. The better decision is a two-conductor, segment-by-segment table showing 21.8 V at the end; if that is below the listed minimum for the chosen candela, upsize the conductor or recheck the appliance selection. It matters because an appliance below its listed range may not produce its rated light output, and a reviewer checking your table can catch that on paper.

Build the habit that survives exam pressure: a four-column table (segment, current, resistance, running voltage) filled in order. Add your safety margin explicitly rather than assuming it, and remember the worst case is usually the battery at the end of a discharge event, which links this calculation directly to your secondary power work.

Secondary power: building a battery calculation you can defend line by line

A defensible battery calculation itemizes every connected device's standby and alarm current from datasheets, multiplies by the required durations, sums both, applies a stated margin, and confirms the result against an available battery size and the charger's capacity.

The structure is always the same even when durations differ by occupancy or system type: standby current times standby duration, plus alarm current times alarm duration, plus a stated safety margin. The discipline is in the itemization. Pull standby and alarm current for the control panel, each annunciator or remote display, and any other constantly connected load, and include the notification appliance load under alarm. Verify against the code edition your program references, because durations and margin conventions are exactly the kind of detail that shifts between editions.

Worked example (labeled, simplified assumptions: a protected premises system with a 24-hour standby and 5-minute alarm requirement; confirm the requirement for your edition and system type): panel standby 0.45 A plus annunciator standby 0.10 A gives 0.55 A; 0.55 A for 24 hours is 13.2 Ah. Alarm current of 1.20 A for 5 minutes is 0.10 Ah. Subtotal 13.3 Ah; a 20 percent margin brings it to about 16.0 Ah, pointing to the next standard battery above that value. The plausible mistake: forgetting the annunciator and the alarm-phase appliance load, or applying margin to only one term. The better decision is a line-item table with each current source named and both durations shown, because an undersized battery means the system dies during an outage before the required duration, and a reviewer can reproduce every line of your work in minutes.

Spot detector spacing: ceiling height, beams, and HVAC in one problem

Spacing is a chain of adjustments, not one lookup. Start from the nominal smooth-ceiling spacing listed for the detector, apply wall and beam reductions in order, then check ceiling height effects and air movement from HVAC before finalizing any location.

Apply reductions in a fixed order so nothing is skipped: first the listed nominal spacing, then halve the distance from walls, then apply the beam rules (depth and spacing of beams each compress coverage), then adjust for ceiling height. A detector whose listed spacing is 30 ft under a smooth ceiling does not keep that coverage under solid joists or near a partition, and stacking two reductions compounds quickly. Document each adjustment with the rule that produced it, because a spacing number without its basis cannot be reviewed or defended.

Air movement is the second half of the problem. A spot detector beside a supply diffuser can have smoke swept away from it, so placement near HVAC outlets needs justification or relocation. Smoke moving through return ducts is addressed by duct detection at the duct, not by room detectors, and duct detectors sample airflow rather than protecting the room the duct passes through. Also keep the two device families separate in your head: heat detectors use their own spacing and reduction tables, which are not interchangeable with smoke detector rules even when both appear on the same ceiling plan.

Mini-scenario: a layout puts a smoke detector directly beside a ceiling supply diffuser because that grid point 'looked covered.' The plausible mistake is treating the spacing table as the only constraint. The better decision is relocating the detector away from the diffuser's throw and recording the reason, since an air-swept location can delay detection regardless of how compliant the spacing looks on the drawing.

Survivability versus redundancy: two different questions people blend

Survivability asks how long a circuit keeps functioning under fire exposure; redundancy asks whether duplicate equipment or paths tolerate a fault. They are independent properties, and a design can have either, both, or neither.

Pathway survivability is achieved by a method, such as fire-resistive cable, a listed protective system, protected construction, or a performance-based alternative, and the method you rely on must be the one recorded. Emergency voice and in-building fire alarm pathways typically face stricter survivability expectations than ordinary circuits, so identify which category each pathway belongs to before choosing a method. A surge protector, a spare fuse, or a second power supply is redundancy equipment; none of it raises a pathway's fire-exposure rating.

Mini-scenario: a designer adds a redundant power supply to a notification circuit and then lists that pathway as having enhanced survivability. The plausible mistake is treating added equipment as added fire resistance. The better decision is to either specify and record a recognized survivability method for the pathway, or to describe the power supply accurately as redundancy and leave the survivability classification unchanged. The distinction matters because a reviewer evaluates the recorded method against the requirement, and a mislabeled pathway fails that comparison even when the hardware itself is good.

Documentation review: tracing one device from drawing to calculation to record

Level III work involves reviewing layouts and completion records, so practice a tracing routine: pick a single device and verify that its location, circuit class, load contribution, and record entry all agree, then repeat across the system.

The cross-check that catches the most is consistency between documents. The circuit class on the drawing should match the classification in the calculations and the entry on the record of completion. The appliance count in the battery calculation should match the device schedule. A revision should propagate: a detector moved 40 feet changes conductor length, which changes voltage drop, which can change the candela selection. Revisions that update the drawing but not the calculations are the classic paper failure.

Build a review sequence you can run the same way every time: (1) check circuit classifications and their stated reasons, (2) recompute voltage drop from the drawing's own wire runs, (3) re-add the battery calculation from the device schedule, (4) verify every spacing deviation has a stated basis, (5) confirm the record of completion reflects the as-built condition. Because NICET's FAS program details, including which code edition applies and how levels are structured, live on NICET's program pages, treat the issuer's site as the authority for program specifics and administrative details rather than secondhand summaries.

An adaptable six-week sequence with a scoring rubric

Run three two-week blocks: circuit calculations first, then layout and spacing, then documentation review. Each block ends with a timed self-test you build from your own or invented drawings, scored against the rubric below as learning milestones, not pass predictions.

Weeks 1-2, circuit math: one voltage drop table and one battery calculation per session, alternating between your own projects and invented, clearly labeled examples; speed comes from repetition of the table format, not from memorizing answers. Weeks 3-4, layout: take a single floor and place initiating and notification devices, writing the adjustment chain for each spacing decision and the class and survivability basis for each circuit. Weeks 5-6, integration: run the documentation review routine from the previous section against your own week 3-4 output, then redo one full set from scratch under time pressure.

Exercise with expected observations: take one de-identified floor plan on paper and design the initiating and notification circuits end to end. When you finish, you should be able to point to, in writing, every item in the rubric. If any line is blank, that blank is your next study session, not a reason to move on.

Self-check rubric (score each item present or absent): segment-by-segment voltage drop table with per-segment currents and the last appliance above its listed minimum at worst case; battery calculation with every device's standby and alarm current itemized, both durations shown, and the margin stated; spacing adjustments each traced to a stated rule in order; circuit class and survivability method written once per circuit with a one-sentence reason; drawing, calculation, and record entries mutually consistent after your final revision. Treat a complete rubric as readiness evidence for your study plan; it is a milestone, not a passing prediction.

• Voltage drop: per-segment current, both conductors, running voltage at each appliance
• Battery: itemized standby and alarm currents, both durations, stated margin, real battery size
• Spacing: nominal, wall, beam, and height adjustments applied in order and written down
• Classification: class and survivability method named with a reason, consistent across documents
• Revisions: a moved device forces recalculation of length, drop, and load totals

References and further reading

Use these references to explore the concepts and check the latest information from the relevant organizations.

• nicet.org

Continue your preparation

• Nicet Fire Alarm Systems Level Iii Fas Iii
• Study Guides