-------------------------------------------------------------------------- Using Zone Lists with SIA and Contact ID Bulletin 1035 1/18/03 Copyright (C) 1999, Coastal Security Systems, Inc. All Rights Reserved. -------------------------------------------------------------------------- SIA, Ademco Contact ID and Radionics Modem alarm communication formats provide the central station with sufficient information so that standardized procedures can be followed. There is no need to define these signals in a subscriber's account unless some other procedure or a zone description is required. In some cases the dealer will accept the default procedure but wishes to add zone description text to the subscriber's account. This is accomplished by entering alarm code zero, the zone number (or range), the alarm type and the description into the subscriber's database record. The alarm type is required to be entered but it is not used. The system will use the alarm type from the default SIA or Contact ID tables. Only the zone description will be used when a signal is received. The procedure will come from the defaults described in bulletin 1023. Zone descriptions from the account are not used when certain signals, such as bell tamper or open/close signals are received. In those cases where a non-standard procedure is required by a dealer both the alarm CODE and ZONE number fields must match the signal exactly. It is not sufficient to send a list of zones and descriptions. You must send alarm codes as shown in the following example: CODE ZONE DESCRIPTION 134 1 front and garage doors 131 2 living and dining room sliders 131 3 master bedroom glass breaks 132 4 media room dual tech 135 5 safe in mbr closet As you can see there are four different alarm codes (131, 132, 134, and 135) being used in the example. The central station must enter both the alarm code and zone number in the database in order to define a procedure different from the default (verify - dispatch - callouts, in the case of burglary signals). If you have created your own standard for pulse format signals you can define those signals and establish your own default procedures in the invalid signal procedure table in your dealer record. Once you have done this you can use zone descriptions in the subscriber accounts just as if you were using SIA, contact id or modem. A typical standard would be: Code Type Description Procedure 1 FIR-A verify, dispatch fire department, notify callout 2 PAN-S verify, dispatch police 3 BUR-A verify, dispatch police, notify callout 8 TBL-S low battery log 9 RES-S log Once you have created this standard you could create an account that sends 4X2 format, codes 18 for fire, 31 for burg front door, 32 for burg perimeter, 33 for burg gun cabinet, 81 for low battery and 99 for restore and all you need to advise the central station is: Zone Description 1 front door 2 perimeter 3 gun cabinet