Free NICET FAS Level II Exam Flashcards

Compare the actual site with the approved documents, identify conflicts and access constraints, and escalate design or code questions instead of improvising. The work plan should turn verified conditions into safe, sequenced tasks.

A circuit is the electrical arrangement, a pathway is the route that carries signals or power, and a raceway is one physical wiring method that can contain conductors. Confusing them can produce the wrong supervision or installation decision.

The listing applies with the manufacturer's published instructions. Substituting terminals, wire types, spacing, or mounting methods can invalidate compatibility or listing conditions even when the equipment appears to operate.

An IDC receives initiating-device changes, an SLC exchanges data with addressable devices, and a NAC powers notification appliances. Identify the circuit's function before choosing conductors, modules, supervision, or test methods.

Confirm device and control-unit compatibility, a unique programmed address, correct circuit connection, location text, and the intended system response. A device that communicates but has the wrong label or logic is not correctly commissioned.

It lets the control equipment monitor wiring continuity beyond the last connected device. Installing it at the panel instead of the electrically remote end can hide an open field conductor.

Only when the pathway class, equipment listing, manufacturer's instructions, and design documents permit it. A branch that still operates may nevertheless defeat required fault monitoring or isolation behavior.

Pathway class describes operation and fault behavior; survivability describes the pathway's ability to keep functioning during fire exposure. A fault-tolerant topology does not automatically provide fire-resistive protection.

Required separation reduces shock, fault-transfer, and induced-noise risks. Route and support conductors according to the applicable wiring rules rather than treating all low-voltage cabling as interchangeable.

Use the specified conductor and connector, preserve polarity where required, avoid damaged strands, apply the listed termination method, label consistently, and strain-relieve the cable. Good continuity alone does not prove a compliant termination.

Provide the required fault-current and reference paths without creating unintended parallel paths or ground faults. Follow the equipment instructions and electrical code; never use field grounding as a trial-and-error noise fix.

Restore the assembly with an approved firestop system matching the penetration and construction. Filling the opening with an arbitrary sealant can compromise the building's fire-resistance rating.

Do not relocate it silently. Document the obstruction, compare code and design intent, and obtain the required approval before changing placement; the final documents must reflect the approved location.

Compatible appliances, control protocol, circuit loading, and programmed zones must work together. Mixing unsupported devices or sync methods can create unsynchronized output even when each appliance activates.

Define which system supplies the initiating action, power, supervision, and final control; then verify the intended fail-safe state and sequence. A relay contact alone does not establish a complete, supervised interface.

The equipment must be protected, accessible, visible as required, and provided with working clearances and environmental conditions consistent with its listing. A convenient mounting spot may still prevent safe testing or maintenance.

Commissioning is the broader process of verifying that components, programming, interfaces, documentation, and performance meet project requirements. Acceptance testing is the formal demonstration to the approving parties; it should not be the first full-system check.

Activate the input and compare every expected output with the approved sequence of operations, including annunciation, notification, transmission, and interfaces. Device activation by itself verifies only part of the sequence.

Inspection looks for visible condition and compliance, testing exercises a function and observes its response, and maintenance preserves or restores operation. Recording one activity does not establish that the other two occurred.

An impairment prevents a system or function from performing as intended. A deficiency can adversely affect performance but does not yet rise to an impairment. Classify the condition under the applicable rules because notifications, safeguards, restoration, and reporting differ.

Testing can activate occupant notification, supervising-station signals, elevators, HVAC, or suppression interfaces. Coordinated notice prevents unwanted dispatches and unsafe surprises without bypassing required safety controls.

Coordinate with the responsible parties and supervising station, place only the necessary functions in an approved test condition, and keep accountability for each bypass. Never solve the problem by leaving communications disabled without control.

Restore all bypassed and disconnected functions, clear test modes, verify normal status and signal transmission, notify affected parties, and document restoration. Finishing the device work does not finish the job.

Use the currently adopted code or standard together with manufacturer instructions and AHJ requirements. Do not infer an interval from habit; different equipment and conditions can have different frequencies.

The prescribed method challenges the intended sensing or operating function without damaging the device. Pressing a test switch or forcing an output may test electronics while bypassing the actual detection path.

A functional test confirms that the detector can respond and initiate the intended signal. A sensitivity evaluation determines whether its response threshold remains within the permitted range; one result does not substitute for the other.

Waterflow represents a condition requiring an alarm response, while an off-normal control valve represents a supervisory condition. Swapping the signal types changes urgency and can produce the wrong emergency action.

A normally isolated conductor has an unintended connection to ground. Isolate sections systematically and correct the physical fault; disabling ground-fault monitoring only hides a condition that can combine with another fault.

Preserve event history, identify timing and environmental patterns, inspect likely connections, and isolate the pathway in controlled steps. Resetting repeatedly destroys evidence without correcting the cause.

Open-circuit voltage can look acceptable even when a battery cannot support load. Evaluate condition using the required visual, charger, connection, and capacity or load-related checks specified for the system.

A verified backup provides a recovery point and helps identify unauthorized or unintended logic changes. Record the version and change scope; a system that boots successfully may still have the wrong sequence.

Identify the system and device, date, activity, observed result, deficiency or impairment, corrective action, remaining work, and responsible personnel. Vague notes such as 'tested OK' cannot reconstruct scope or exceptions.

Document it clearly, notify the responsible party through the required process, identify any impaired function, and establish appropriate interim controls and follow-up. Silence can leave the owner assuming the system is fully restored.

Shop drawings communicate the proposed installation and coordination details; record drawings document what was actually installed. Approved changes belong in the record set so future testing and modification begin from reality.

Reconcile contract documents, specifications, adopted codes, AHJ criteria, equipment listings, and manufacturer data. A single source rarely defines the entire project obligation.

Verify construction, dimensions, hazards, environmental conditions, existing systems, power, interfaces, access, and routing constraints. It prevents a technically neat drawing from being unbuildable or incompatible with the site.

Building-code triggers and fire alarm requirements depend on how spaces are classified and used. A room name on an old plan may not reflect the current occupancy or the required protection.

Use a consistent legend and identifiers that distinguish device type, function, circuit, and mounting information. Similar-looking symbols without a legend create installation and inspection errors.

A riser shows system relationships, circuit origin and destination, interconnections, and vertical distribution. The floor plan shows physical locations and routing; both views should agree.

It maps each initiating event to required control, notification, transmission, and interface outputs. This gives programmers, installers, and testers one traceable definition of expected behavior.

They connect each load to its source and show the basis for circuit capacity and power calculations. Without them, reviewers cannot readily verify spare capacity, distribution, or calculation inputs.

Multiply each current by its required operating duration, total the ampere-hours for each operating mode, then apply the required sizing margin and select a listed capacity that fits the enclosure and charger limits.

Use the worst credible combination of source voltage, conductor resistance, circuit length, and connected load, then verify the most remote appliance still receives at least its listed minimum voltage.

Required standby and alarm operation can change with system type and service, such as voice or releasing functions. Applying one memorized duty cycle to every project can undersize the power supply.

Verify the devices, control equipment, power supplies, modules, and communication methods are listed or approved to operate together for the intended function. Matching voltage does not establish compatibility.

Include prerequisites, responsible parties, access, outages, other trades, inspections, tests, restoration, and handoffs. Coordination exposes dependencies before they become unsafe delays or rework.

Match the task to demonstrated competence, explain scope and hazards, provide the correct documents and tools, define checkpoints, and verify the result. Delegating the task does not transfer accountability for coordination.

State completed work, remaining work, deviations, blockers, safety or system impacts, decisions needed, and the next action with ownership. Early, specific reporting lets the project correct course.

Report the condition accurately, refuse to falsify records or approvals, and escalate through the proper authority. Schedule or cost pressure does not override public safety or professional integrity.

The responsible parties must review and approve changes, and affected drawings, calculations, programming, tests, and records must be updated. An undocumented successful workaround becomes a future maintenance and liability problem.