❑Mandatory Alarm Condition Codes
•As previously noted, an Alarm Condition Code record describes an Event and/or Alarm Condition, identifies the required Operator Skill needed to process the Alarm Condition, set the Priority level for the monitoring response, and define the Report Printing Options for the Event or Alarm Signal.
✓Several Alarm Condition Codes come predefined and should not be deleted.
✓Each of these are identified with a trailing (* = System Required) asterisk.
•The chart below lists the required Alarm Condition Codes used by MKMSCS and SPA for the designated purpose:
Alarm Condition Code |
* Alarm Code Description |
---|---|
AT* |
Account placed on test |
ET* |
Edited Test Time |
FC* |
Failed to Close |
FO* |
Failed to Open |
FR* |
Failed to Restore |
FT* |
Failed to Test |
IA* |
Invalid Alarm |
IC* |
Invalid or Off time Closing |
IO* |
Invalid or Off time Opening |
OT* |
Account off test |
RA* |
Runaway Alarm |
TA* |
Time Added in Daily Activity |
TD* |
Time Deleted in Daily Activity |
TM* |
Time Modified daily activity |
WT* |
Account ready to go Off Test |
ZT* |
Zone placed on Test |
Mandatory Alarm Condition Codes
❑Mandatory Panel Zones
•Whenever a new Communicator Format is added, these Mandatory Alarm Condition Codes (listed below) are also created (automatically) as Signal IDs in the Panel Zones Form for that Communicator Format - with the information described below.
Signal ID |
* Alarm Code Description |
Response |
Verify |
OCTAR |
Panel Zone Description |
---|---|---|---|---|---|
AT* |
Account placed on test |
Yes |
No |
Alarm |
Account On Test |
ET* |
Edited Test Time |
Yes |
No |
Alarm |
Edited Test Time |
FC* |
Failed to Close |
Yes |
No |
Alarm |
Failed To Close |
FO* |
Failed to Open |
Yes |
No |
Alarm |
Failed To Open |
FR* |
Failed to Restore |
Yes |
No |
Alarm |
Failed to Restore |
FT* |
Failed to Test |
Yes |
No |
Alarm |
Failed To Test |
IA* |
Invalid Alarm |
Yes |
No |
Alarm |
Invalid Alarm |
IC* |
Invalid or Off time Closing |
Yes |
No |
Alarm |
Invalid Closing |
IO* |
Invalid or Off time Opening |
Yes |
No |
Alarm |
Invalid Opening |
OT* |
Account off test |
Yes |
No |
Alarm |
Account Off Test |
RA* |
Runaway Alarm |
Yes |
No |
Alarm |
Run Away Alarm |
TA* |
Time Added in Daily Activity |
Yes |
No |
Alarm |
Time Schedule Added in Daily Activity |
TD* |
Time Deleted in Daily Activity |
Yes |
No |
Alarm |
Time Schedule Deleted in Daily Activity |
TM* |
Time Modified daily activity |
Yes |
No |
Alarm |
Time Schedule Modified in Daily Activity |
WT* |
Account ready to go Off Test |
Yes |
No |
Alarm |
Warning - Acct Coming Off Test |
ZT* |
Zone placed on Test |
Yes |
No |
Alarm |
Zone Placed On Test |
Special Alarm Condition Codes listed above are created in the Panel Zones Form
✓Other Special Panel Zones - These Panel Zones should also be defined for each Communicator Format :
▪Signal ID = A105 Alarm Code = System Messages OCTAR = Alarm Description = Runaway alarm (Received too many signal in a short time period)
▪Signal ID = A107 Alarm Code = System Messages OCTAR = Alarm Description = No CSID or SI on Alarm Signal
▪Signal ID = A108 Alarm Code = System Messages OCTAR = Alarm Description = Invalid Caller ID (Phone number not in CSID caller list)
oThree Signal ID = A108 records must be entered with the following Physical Zones and Descriptions:
Physical Zone |
Descriptions (add this text to above "Invalid Caller ID" message |
0 |
There is no phone in the subscriber panel |
1 |
There is at least one phone number in the panel |
2 |
There is no account with that CSID Or the account is offline Or the subscriber is a deleted account (Old Subscriber = ‘T’) |
▪Signal ID = A121 Alarm Code = System Messages OCTAR = Alarm Description = Manual Customer Note
▪Signal ID = A127 Alarm Code = System Messages OCTAR = Alarm Description = Invalid SIA package or Unable to process SIA package
▪Signal ID = A128 Alarm Code = System Messages OCTAR = Alarm Description = Temp Note Added/Modified/Deleted
▪Signal ID = A130 Alarm Code = System Messages OCTAR = Alarm Description = Account canceled via Dealer Client or Millennium
▪Signal ID = A131 Alarm Code = System Messages OCTAR = Alarm Description = Account set to offline
▪Signal ID = A132 Alarm Code = System Messages OCTAR = Alarm Description = Account set to online
➢Note: See the Special Panel Zones chapter for additional information.
Third Edition UL® 1981 Standard 11.1.9 - The automation system shall be able to automatically identify an alarm system as a runaway system (also see 5.47 - Runaway System) when the number of signals from that system exceeds the pre-programmed number wit the pre-programmed time frame; the following shall occur:
a)It shall immediately and automatically display a message on the operator terminal; and
b)The message shall indicate "runaway" system and identify the details of the alarm system such as type of signal, account number, location, contact person, and similar information.
•When a Subscriber CSID is entered in Subscriber Panels section in the Monitoring Tab within the Edit View of the Subscribers Form, a Communicator Format is normally identified for that CSID
✓So, these Mandatory Panel Zones associated with that Communicator Format are automatically "connected" to that CSID.
✓However, if no Communicator Format is identified for that CSID in the Subscriber Panels section:
▪The Signal ID and Alarm Code Description entries listed in the chart above must instead be defined as CSID Zones
▪The appropriate Response instructions (see the Operator Guided Response and Action Plans chapters for more information) must also be identified for each Account (CSID) that has not been assigned a Communicator Format.
•As noted above, these same Signal IDs and Alarm Code Descriptions must also be defined as Alarm Condition Codes to ensure that MKMSCS and SPA can properly track, manage and report the failure to occur of a Scheduled Event.
✓These are normally included in the initial installation, but it's a good idea to confirm that all of them were installed successfully.
❑Some Alarm Condition Codes may also be mandatory for the proper operation of SPA - The Signal Processing Application.
Alarm Conditions Form - MSG entry
•The current SPA Message requirement is:
▪MSG = System Messages