Events; 1: About Events; 2: Types Of Events; 3: Event Handling - Honeywell NOTIFIER NCA-2 Instruction Manual

Operation
Walk Test Reports
This printer functions prints a report of the last walk test performed.
******WALK TEST RESULTS*********************************************************
TEST TROUBLE
TEST FIRE ALARM
TEST FIRE ALARM
TEST ACTIVE

*****EVENTS*********************************************************************

4.3 Events
4.3.1 About Events
An event is any change in the status of a device, a transfer of information between a device and the NCA-2, or a transfer of information
between two devices. Some of these events are considered background and housekeeping events and are not seen by the user under nor-
mal circumstances. These events may appear, however, during a Walk Test operation.
The events that are of primary concern to the operator are those identified as Off-Normal Events. An off-normal event is an event which
indicates activity or change in condition that requires the attention and/or response of an operator. Examples of possible off-normal
events are:
• Activation or change in condition of a monitoring device (Smoke Alarms, Fire Alarms, etc.).
• System troubles, such as network problems, device supervision problems, etc.
4.3.2 Types of Events
Events which come into the NCA-2 and are displayed on the LCD screen can be divided into the following fundamental categories:
• Fire Alarm Events - Events issued by fire alarm initiating devices such as pull stations, smoke detectors, and sprinkler systems.
• Mass Notification Events - Events issued by Mass Notification initiating devices. These events include MN Alarms, MN
Supervisories, and MN troubles.
• Pre-Alarm Events - Prealarms are precursors to fire alarms; a fire detector device issues this event when its level surpasses the
programmed limit.
• Security Events - Events issued by security devices such as motion detectors, glass break detectors, and door contacts.
• Supervisory Events - Supervisory alarms are special alarms to indicate an action that has functionally disabled a key device (for
either fire protection or security). An example would be an event generated if the water valve is shut off for a sprinkler system.
• Trouble Events - Trouble events indicate a functional problem with a device on the network. Examples of trouble events include a
device going off-line, a battery low or no power event, a clogged head on a smoke detector, etc.
• Other Events - Events which do not fit the other categories, such as Critical Process or Life Safety.
• Disabled/Enabled Events - Events resulting from enabling or disabling a device.
4.3.3 Event Handling
When an off-normal event is sent to the NCA-2 from an FACP or ACS device, it must be acknowledged either at the NCA-2 or locally at
the panel. Acknowledging an event performs the following functions:
• Silences the Piezo sounder on the NCA-2.
• Transfers the event to the NCA-2's History buffer.
• Sends a network event to the associated panel.
How to Acknowledge an Event
When an event comes in, the NCA-2's alarm will sound a specific pattern depending on the event type. The event type will be displayed
in the upper left corner of the screen. The ACKNOWLEDGE option will appear, also displaying the event type. This option will flash
along with the appropriate LED indicator. Once you press the ACKNOWLEDGE soft key (or the ACKNOWLEDGE Fixed Function
key, the upper left message will change to "acknowledged."
NOTE: If the device initiating the event has become disabled in such a manner that it can no longer communicate over the network, the
NCA-2 message will display "Local Acknowledge" in the upper left corner, indicating the event has been acknowledged at the NCA-2 only.
For details on operator response to various events, refer to the pertinent FACP or ACS manual.
Figure 4.30 on page 53 and Figure 4.31 on page 53 are examples of screens displaying an incoming event and an acknowledged event,
respectively.
Events can be scrolled by pressing the appropriate hard key. Events are displayed and logged in the history. When additional unacknowl-
edged events exist, the first four screen lines advance to the next highest priority unacknowledged event, and this process repeats. After
the history log is full, the next event that gets logged causes the least recent event in the log to be dropped.
52
NO ANSWER DETECTOR 73
Z003 SMOKE(IOM)
ROOM 101
Z001 HEAT(ANALOG)
ROOM 221
Z001 SECURITY
LAB
Z004 CONTROL
Figure 4.29 Printer Functions: Walk Test Report
02:54:04P TUE MAR 19,2019 N001L01D073
1ST FLOOR
02:54:31P TUE MAR 19,2019 N001L01D003
2ND FLOOR
02:54:59P TUE MAR 19,2019 N001L01M004
3RD FLOOR
02:55:09P TUE MAR 19,2019 N001L01M005
NCA-2 Manual — P/N 52482:M5 03/20/2019
Events