19.2 Maintenance, Inspection, and False Alarm Reporting
Key Takeaways
- Module 5.V's reporting half requires a false-alarm log with at least time, user, zone or point, weather, restore, signal type, and corrective action — not a panel reset with the word false written on a ticket.
- Municipal false-alarm dollar amounts vary by local ordinance; New York does not publish a statewide false-alarm fine schedule in GBL §69-vvv.
- GBL §69-vvv(1) lets a municipality hold the alarm company only when the false alarm is attributed to a deficiency in the alarm system or an error of the alarm system company or central station; owner-, lessee-, or occupant-caused events may still be fined against those persons.
- GBL §69-vvv(2) states that an operator or agent is not liable for municipal false-alarm fines not attributed to operator error, improper installation, defective provided, installed, or leased equipment, or a wear-and-tear deficiency after equipment that was not deficient when installed or provided.
- Security false dispatches go to police; fire unwanted or nuisance alarms go to the fire department and the AHJ. Module 5.V prevention is maintenance: clean detectors, replace aging PIRs, keep sensitivity in the listed range, and train users.
Module 5.V is not only contracts. The same 3-hour block in 19 NYCRR 196.8 is Maintenance, Inspection and False Alarm Reporting. Chapter 12 spent Module 3's 0.75 hour on prevention by design and placement: user error, pets, HVAC drafts, abort/cancel, and swinger shutdown as security programming. This Independent OpenExamPrep section is the service half: what you log after a dispatch, how municipal ordinances assess fines, how General Business Law §69-vvv assigns company versus occupant liability, how fire unwanted alarms differ from security false dispatches, and how maintenance — cleaning, aging-device replacement, listed sensitivity, and user training — stops the next one.
Do not memorize a fake statewide dollar table. New York does not publish a statewide false-alarm fine amount. Cities, towns, and villages write their own ordinances. Learn what to write down and who the statute lets the municipality bill.
What to log after a false or unwanted alarm
A report that says "false alarm, reset panel" is not a report. Qualifying-course reporting, and any municipal or central-station form you will actually fill out, needs facts a later technician and a later reviewer can use.
Log at least:
- Date and time of the signal (panel history and central-station stamp — they sometimes differ)
- User (who was on site, who cancelled, who had the code, cleaning crew, tenant)
- Zone or point (addressable text, not "something in the hallway")
- Weather (wind on a gate, freeze, thunderstorm, humidity — outdoor contacts and passive infrared (PIR) detectors care)
- Restore (when the point restored, when the panel was reset, when monitoring was taken off test)
- Signal type (alarm, supervisory, trouble, panic/holdup)
- Whether the account was on test
- Cause if known, and corrective action
- Any municipal notice or incident number
Those fields are how you later apply §69-vvv. Without a zone and a user, every dispatch looks like a "system deficiency." With them, a janitor walking a motion at 05:00 is occupant-caused, and a dirty smoke at 02:14 after two skipped cleanings is a maintenance story.
Keep the false-alarm log with the 195.10 transaction file for three years (longer if a Department of State matter or lawsuit is pending). It is a business record of the service call. It is also evidence of attribution. Chapter 17.3 already taught that ITM results go to the owner; a false-alarm report is the same idea applied to a dispatch.
Municipal ordinances — local dollars, not a DOS price list
Municipalities may require alarm permits, may escalate fines after repeated dispatches, and may refuse response after a stated number of false alarms. Those dollar amounts vary by locality. Do not study an invented "first offense $50, third $250" as New York State law. The DOS Security or Fire Alarm Installer exam is not a village fee schedule. If a question names a city ordinance, read that ordinance. If it asks for a statewide fine, the honest answer is that GBL §69-vvv does not set one.
GBL §69-z still lets local law govern inspection of fire alarms by a fire marshal. A local false-alarm ordinance is a related municipal power. Your statewide license does not freeze those local fees, and it does not create a secret DOS fine.
GBL §69-vvv in the reporting and maintenance setting
GBL §69-vvv (Fines for false alarms) is the statewide attribution rule. Chapter 12 introduced the 2025 text, which carries a most-recent-revision date of December 12, 2025. Here you use it after the signal, when someone is holding a municipal bill and you are deciding whether the maintenance file shows a company-side deficiency or an occupant cause.
§69-vvv(1). A municipality may require an alarm system company to pay false-alarm fines, fees, or other penalties only when the false alarm is attributed to a deficiency in the alarm system or an error of the alarm system company or central station. Nothing in the section prevents the municipality from imposing those penalties when the false alarm is attributable to, or caused by, the property owner, lessee, occupant, or other person.
§69-vvv(2). An alarm company operator or alarm agent shall not be liable for municipal civil penalties and fines for false alarms not attributed to:
- alarm company operator error
- improper installation by an agent or operator
- defective equipment provided or installed by an agent or operator
- defective equipment leased by an operator
- equipment that was not deficient upon installation or provision for use but later resulted in a deficiency due to normal wear and tear
Teach subsection 2 as the statute writes it: a double negative plus a list. Do not invent a rule that wear and tear always bills the company, and do not invent a rule that wear and tear always shields the company. Subsection 1 still lets a municipality hold the company when the false is attributed to a deficiency in the alarm system or an error of the company or central station. Owners, lessees, and occupants can still be fined for their causes. The wear-and-tear clause is why Section 19.1 sells battery, detector-cleaning, and PIR-replacement programs: aging equipment that was sound at commissioning can later become the deficiency in the log.
How a maintenance log changes the story
| Logged facts | Typical attribution under §69-vvv teaching | Maintenance follow-up |
|---|---|---|
| Tenant armed interior motion with the dog inside | Occupant-caused; municipality may fine owner, lessee, or occupant | User training; night arming without that motion (programming is Section 19.3) |
| Central station dispatched after a valid cancel | Error of the company or central station | Report, correct monitoring protocol, document |
| Surface contact you left on a bouncing gate last month | Improper installation or system deficiency | Repair; this is not "the owner's weather" |
| Outdoor PIR that was sound at commissioning, now eight years old, falseed in a storm | Wear-and-tear / deficiency language is why the statute names aging equipment — and why a replacement program exists | Replace the aging device; do not claim the statute automatically assigns the fine |
| Photoelectric smoke packed with drywall dust after a renovation, never cleaned | Deficiency the maintenance program was supposed to prevent | Clean or replace; put ITM back on the calendar |
The exam wants you to report the facts, apply subsection 1's company-only-if-deficiency-or-error rule, and keep wear-and-tear in the statutory list without a statewide dollar figure.
Fire unwanted alarms versus security false dispatches
The same statute says false alarms. Operations are not the same.
A security false alarm typically produces a police false dispatch. Abort, cancel, swinger shutdown, and opening/closing schedules (Section 19.3) are the security tools. The log still needs time, user, zone, weather, and restore.
A fire unwanted alarm typically produces a fire-department response. Commonly taught NFPA 72 language talks about unwanted alarms, including nuisance alarms (cooking, steam, dust, aerosols) as distinct from a real fire. The AHJ and the fire department care about impairments, test mode, and whether you notified monitoring before you smoked a detector. Putting a required fire system "on bypass" to stop nuisances is an impairment, not a courtesy (Chapter 18). Cleaning, sensitivity within the listed range, and replacing a detector that will not stay in range are the maintenance answers. Turning the smoke off is not.
This statewide sitting is not an FDNY Certificate of Fitness exam. New York City may run a stricter local false-alarm or fire-prevention process. GBL §69-z preserves local fire-marshal inspection. It does not rewrite §69-vvv's attribution rule, and it does not let you treat a fire nuisance as a burglary swinger.
Prevention by maintenance — the Module 5.V angle
Chapter 12's prevention list was mostly design: do not aim a PIR at a register; use a wide-gap contact; give the user an abort. Module 5.V's prevention list is upkeep:
- Clean smoke detectors on the ITM calendar; dust and insects are classic nuisance sources
- Replace aging PIRs, outdoor contacts, and takeoff cords before they swing
- Keep detector sensitivity in the listed and marked range — adjust or replace; do not crank it down below listing to silence a building
- Train users: how to cancel, whom to call, how cleaning crews get a code, how to request a test window
- Run the battery and spare-parts programs from Section 19.1 so low voltage and dying heads are not the 2 a.m. cause
If the contract skipped cleaning for two years, the "deficiency in the alarm system" sentence in §69-vvv(1) is no longer a surprise. Maintenance is how the licensed firm keeps that sentence off the municipal notice.
In practice
Three reports, same combination panel. 02:14 fire: dirty warehouse smoke, no cleaning since acceptance — log time, point, restore, dust found; treat as a system or maintenance deficiency story and clean or replace. 05:02 burg: night cleaner, no code, walked a motion — log user and zone; occupant-caused; train and issue a limited user code (Section 19.3). 18:40 burg: central station sent police after the owner cancelled — log the cancel time and the dispatch; company or central-station error under §69-vvv(1). None of those reports has a statewide fine amount on it.
On the exam
Traps invent a DOS dollar schedule, bill the company for every occupant trip because the firm monitors the account, treat fire nuisance alarms as "just burglary swinger," or skip the log because the panel was reset. Choose complete logs, local ordinances without a statewide price, §69-vvv attribution, fire versus police response, and cleaning, replacement, and training as the maintenance cure.
A municipal false-alarm notice arrives after an overnight dispatch. Which log set matches Module 5.V reporting rather than a reset-only ticket?
A maintenance log shows that an outdoor gate contact your firm mounted last month has been bouncing in the wind, and the municipality bills the alarm company for the resulting dispatch. Which General Business Law §69-vvv attribution fits those logged facts?
Which statement matches Module 5.V maintenance prevention and the fire-versus-security reporting split, rather than Chapter 12's design-placement hour?