Advanced Data Entry for Dealers

Central One makes the subscriber database available to dealers via the internet.  Each dealer or dealer employee has a unique employee number and password for logging in to the system.  Access to edit the subscriber database can be enabled or disabled for any employee number.  This document explains the use of the signal information and special instructions screens. 

Signal Information Screen:

The top half of the signals screen shows a scrolling list of the signals that have been defined for the account.  Use the up and down arrow keys to move up and down the list.  Up to 128 signals can be defined.  The bottom half of the screen will show the properties of the signal that is highlighted in the top half.  To edit the properties of the highlighted signal press the enter key, then use the up and down arrows to move from field to field.  When you finish entering or editing a signal, press the escape key to return to the list at the top of the screen.

The order that signals appear on the screen is significant.  When a signal is received the software searches the list from the top down until it finds a matching code and zone.  If no match is found, the software searches the signal list found in the template account (if any).  If no match is found in a template the software checks the default table for the format in which the signal was received.  The Contact ID, SIA, ITI and Radionics Modem 3 formats have extensive defaults described in Central One bulletins.  Other formats such as pulse formats have no defaults so the invalid signal procedure table in the dealer’s database record is consulted.  If no default is found the signal is considered invalid and is logged.

To insert a signal into the list at a specific point highlight the signal that is to follow the new signal and press the insert key.  To delete a signal from the list, highlight it and press the delete key.  A confirmation prompt will follow.

Each signal has twenty nine properties.  The following is a summary of each signal property.  Many of the properties will be discussed in greater detail later in this section.

  1. Code is the alarm code or event code received from the communicator.  The code typically indicates the type of alarm (fire, panic, burglary, etc.) being received.  You must understand the communication format used by the alarm panel in order to anticipate the code that will be received.  Pulse format 4X2 signals send a four digit account number, a one digit code and a one digit zone.  Contact ID sends a three digit code and a three digit zone.  SIA format sends two letters as code and a variable length zone number.  The letters are converted by central station software to numbers as follows:  AA = 1, AB = 2, AC = 3, etc.  Bulletin 1033 contains a complete listing of SIA code translations.  Valid codes are from 0 to 65534.  Code 65535 is a wild card and matches any code value received from a panel.  The use of a wildcard is common for networked systems discussed later.
  2. Zone is also a value received directly from the communicator.  The zone typically indicates the location within the premises or the type of device that triggered the alarm.  The software allows a signal to define a range of zones.  The default range is 0 to 65535 (hex FFFF) which includes all possible zone numbers.  The use of a range of zone numbers allows you to be either general or specific in your signal definitions and descriptions.  More on this later.
  3. The alarm type is a three letter mnemonic that identifies the kind of alarm represented by the code and zone received.  This mnemonic determines the rank or priority of the signal (under U.L. guidelines) and the default procedure that will be followed when the code – zone combination is received.  The first time you enter a mnemonic for a signal you will see several properties for the signal automatically set.  If you have already defined a procedure for the alarm type the default properties will come from the first matching alarm type in the signal list.  If not, Central One standard defaults will apply.  Standard defaults for the FIR alarm type depend upon whether “NFPA” appears in the permanent instructions field on the previous data entry screen.
  4. The audible property should be set to “Y” for audible or “N” for silent.  This information appears in alarm history and is conveyed when alarms are dispatched.
  5. The zone comments field typically contains a textual description of the zone such as the location or description of the alarm device.  This field can also be used to transfer signals to another account.  We call this translating the signal.  To do this place a “@” character at the beginning of the field followed by the account number where you want the signal to go.  You must define the signal in the receiving account.  This technique is frequently used in connection with networked fire alarm systems where a single panel reports alarms for several buildings at different addresses.
  6. The O/C area field allows you to specify the partition that the signal belongs to if the panel does not transmit partition information.  When partition information is received it is used and this field is ignored.  Systems can be divided into up to eight partitions or areas.  Special instructions, callouts and business hours schedules.
  7. The panel zone field is seldom used.  Any number entered in this field is added to the zone number actually received.  Let’s say you are using 4X2 and send 31 (code 3 zone 1) through 39 for zones 1 through 9, 30 for zone 10 and 41 through 46 for zones 11 through 16.  By entering a 10 in the panel zone field for code 3 zone 0 and code 4 zones 1 through 6 the alarm history will show the zones as 1 through 16 as a subscriber would expect.
  8. The next six fields determine the steps that an operator will follow when the signal is received.  Default values are placed in these fields when the alarm type is entered.  For a typical alarm the procedure is (1) make a verify call, (2) dispatch the police, and (3) notify a callout.  You accomplish this by putting a “1” in the “Verify (step):” field, a “2” in the “Dispatch Agency #1 (step):” field, and a “3” in the “Callout (step):” field.  Leave a “0” in the three other fields (“Dispatch Agency #2 (step):”, “Dispatch Guard/Runner (step):”, and “Notify Dealer (step):”) so the operator will not take those actions.
  9. The “Agency #1:” and “Agency #2:” fields allow you to enter the number of the agency to be dispatched.  If you leave these values blank or zero, the monitoring software will use the police, fire, medical or guard agency designated for the account (shown on the bottom line of the screen) based on the alarm type.  Typically it is best to leave these fields blank and let the agencies default.
  10. The “Guard/Runner:” field allows you to enter the number of the guard or runner agency to be dispatched.  This monitoring software will use the guard agency designated for the account if this field is left blank or zero.
  11. The E.T.A. field goes with the “Guard/Runner:” field.  Both the dispatch agency and guard/runner agencies use the same database and numbering scheme.  The main difference is that guard/runner response is associated with the E.T.A. field.  If used, the central station will track the arrival and completion times of the guard or runner and record that information in the alarm history.  If an arrival time is too long or too short there will be an entry in the subscriber trouble report (too short means the responder did not really go).
  12. When “Y” for yes is entered in the “Must Restore?” field the subscriber trouble report will include any alarm that fails to restore.  The report will include the alarm for ten days and then, restored or not, drop the reporting will stop.
  13. When a time is entered in the “Within (hh:mm:ss):” field the monitoring software schedules a status check to see if the alarm has restored when time is up.  If not, a new signal with FTR pin status is generated.  If you want a special procedure followed in the event of a failure to restore you must make up a code (any code not sent by the panel) and enter it in the “FTR =” field.  Then create a signal with the same event code and define the procedure.  If you do not define a new code then the same procedure that applied when the signal was received will apply again.
  14. If you enter “Y” for yes in the “Hold Alarm Pending Restore?” field the monitoring software will cancel the original alarm and wait until the “[Must Restore] Within” time expires.  If the alarm restored nothing will happen.  If not a new signal with FTR pin status for the original signal’s code and zone will be generated.  It is a common practice with older fire alarm systems to put a ten or fifteen minute hold on trouble signals.  Any trouble signal that restores within this time will not result in operator action.
  15. If you enter “Y” for yes in the “Service Memo?” field the signal will be considered a trouble signal.  It will be identified on all event reports with plus signs so that it stands out.  It will be included on trouble signal reports.  If the alarm type is TBL or SUP there is no need to also use this field.  These signals are treated as trouble anyway.
  16. If you enter “Y” for yes in the “Email Dealer?” field then every time this signal is received an email will be sent to the address defined for signals in the dealer database.  Signals that require operator attention are transmitted immediately.  When the operator completes the event a follow up email is sent showing the full disposition.  There is no charge for email to the dealer.
  17. If you enter “Y” for yes in the “Backup Only?” field then the signal will be held for two minutes each time it is received.  If a signal with the same alarm type is received while this signal is holding then this signal will be cancelled.  If no other signal with the same alarm type is received then this signal is presented to the operator for the action specified in the step fields and the service memo flag will be set so the signal appears on trouble reports (indicating a failure of the primary transmitting device).  Signals with this property set to yes do not update the account’s “date and time of last non-system signal” field and therefore do not count as satisfying the accounts periodic test requirements.
  18. The “Xlate Area:” field contains the number of an area or partition that contains a business hours schedule that will be used to vary the operator action based on a schedule.  This seldom used feature was created to accommodate old bank alarms that sent only one event code.  During business hours the event was a hold-up.  After hours it was a burglary.
  19. The “Code Word?” field determines whether a person at the premises is required to give a valid cancel code to cancel the alarm.  Generally, medical and non-required fire alarms should require no code.  Security alarms should.
  20. The “Pin Status = “ fields support formats that send, in addition to code and zone, a pin status of TBL, CAN, RES, BYP, FAR, or FTR.  For example the Radionics BFSK format can send code 1 alarm, code 1 trouble, and code 1 restore.  If you leave nothing in these (Pin Status) fields the steps for the signal will be followed only when code 1 alarm is received.  Code 1 trouble and code 1 restore will simply be logged.  If you want operator action on the trouble condition simply make up a new event code (one not used by the panel) and enter it in the “TBL = “ pin status field.  Then create a new signal with the event code you made up and give it whatever instructions and properties you like.

 

Special Instructions Screen:

Access to the special instructions screen is not given to new dealers.  Once a dealer has a complete understanding of the use of the special instructions screen and agrees to use the screen in a way that is consistent with Central One policy (bulletin 3000) remote editing rights are granted.  Whenever a special instruction screen is modified by a dealer a flag is set so that the data entry department may review the instructions for compliance.  Most monitoring instructions can be automated or have a specific place in the database.  The use of textual special instructions should be avoided whenever possible.  When special instructions must be used they should be phrased in a manner consistent with operator training practices.

There are four sets of special instruction fields.  These fields are guaranteed to be presented to the operator together and in the same order that they appear on the data entry screen.  The first field contains the text of the instruction.  The next two fields allow you to enter a start and end date for the instruction.  If the start date is omitted the instruction is effective immediately.  If the end date is omitted the instruction is permanent.  The “Cancel alarm?” field must be “Y” if the instruction is to automatically cancel alarms and “N” if it isn’t.  The eight “Applicable area(s):” fields allow partitioned systems to have instructions that pertain only to specific partitions.  The “Applicable alarm type(s):” field consists of a list of alarm type mnemonics, optionally followed by zone lists.  For example, “PAN BUR 3,7-10” would make the instruction apply to all panic signals and burglary signals on zones 3, 7, 8, 9, and 10.  If you leave the “Applicable alarm type(s):” field blank the instruction will apply to all signals.

Some proper uses for the special instructions screen include:

1.      When the directions to premises field is not adequate.  The directions field was never intended to contain long, free form directions.  It was intended to identify the name of the sub-division or development where the premises is located or the name of the nearest major cross street.  Long directions are not needed or even accepted by most modern law enforcement call centers.  They know the streets of their jurisdiction.  But when long directions are required, the special instructions fields (four fields of fifty characters each) provide adequate space.

2.      When additional information is required to call the main or alternate numbers, such as menu options and extensions that need to be dialed.

3.      “DND PD without callout approval.”  This instruction assumes that you have put the callout step ahead of the police dispatch step in each of the signal definitions.  In the absence of this instruction the central station operator will dispatch the police if no one from the callout list could be contacted.  This instruction is usually limited to BUR alarm types so “BUR” should appear in the “Applicable Alarm Type(s):” field.

4.      You may place an email address in the “Instruction:” field.  This will cause any signals covered by the instruction to be instantly emailed.  If the instruction required operator action a follow up email will be sent showing the full disposition when the event is completed.

5.      Zone “Anding”.  This feature allows you to prevent a dispatch from a single trip from a motion detector or other false alarm prone device.  It is covered in detail later in this section.

6.      Information not needed for central station operations.  Most dealers have their own filing system and customer database and do not need to use special instructions in this way.  However it is acceptable to enter information, such as “panel in master bedroom closet”, etc., in a special instruction field and put “N” for no in all eight of the “Applicable Area(s):” fields so that the instruction will not be displayed to an operator when handling an alarm.

Using special instructions to cancel alarms:

            You have an NFPA fire alarm account (designated by “NFPA” appearing in the permanent comments field of the database) that sends contact id.  You want the default procedure to apply to fire alarms but you do not want a runner dispatched on trouble signals.  Enter “log trouble signals” in the “Instruction:” field.  Enter “Y” for yes in the “Cancel alarms?” field.  Enter “TBL” in the “Applicable alarm type(s):” field.  Make sure all of the area fields contain “Y” for yes and the start and end date fields are all zeroes.  When a trouble signal is received in Contact ID, SIA or Modem format the monitoring software will see that the account is NFPA and set up a runner response procedure.  It will then cancel and log the trouble signal on the strength of this instruction.  Using a special instruction in this circumstance relieves you from the need to define every possible trouble signal that the panel might send.

            You have a swinger on zone seven and took corrective actions but you are not sure you were able to isolate the cause.  The subscriber is facing false alarm fines and wants to avoid dispatching the police if this zone falses again.  One option is to remove the police dispatch step on the signals screen.  This would cause the operator to make verify calls and callout notifications but not dispatch the police if the zone trips.  A disadvantage is that you must remember to restore the dispatch step when you are satisfied that the problem is corrected.  If you (and the subscriber) wish to ignore the zone for a period of time to be sure it is fixed the best method is to use a special instruction.  Enter “service watch” or some similar text in the “Instruction:” field.  Put a reasonable end date in the “Through:” date field so that the zone will not be ignored after a reasonable period of days and you will not be required to remember to restore the zone to service.  Enter “Y” for yes in the “Cancel Alarms?” field.  Enter “BUR 7” in the “Applicable Alarm Types:” field.  Note that you could use an alert message to accomplish the same thing.

Zone Anding:

High end alarm panels have zone anding features built in.  The advantage of using the alarm panel’s feature is that the alarm will not sound until the conditions for an alarm have been satisfied.  If your panel does not offer this feature or if you want the alarm to sound but you do not want a central station response until the conditions have been satisfied, zone anding can be accomplished using the special instructions fields of the Central One database.

An instruction may be entered into any of an account’s four special instruction fields.  The syntax for the command is “AND: [zonelist] WITH: [zonelist]”.  A zone list consists of a list of zone numbers, separated by commas, a range of zone numbers, separated by a dash, or a combination of both.  For example, “1, 3, 7-12, 14, 16-22, 29” would be acceptable.  It is not possible to include zone zero in a list.

Here is how zone anding works:

Here are some examples where the instruction is “And: 1  With: 2”:

10:00 a.m. BUR Zone 3 is received.  It is presented to the operator because anding does not apply to zone 3.

10:05 a.m. BUR Zone 1 is received.  Alarm history is checked to see if zone 2 was received in the last two minutes.  It was not so the signal is cancelled.

10:06 a.m. BUR Zone 2 is received.  Alarm history is checked and, because zone 1 was received in the last two minutes, the signal is presented to the operator.

Note:  The result would have been the same if the instruction read, “And: 2 With 1”.  When the zone number is found in either field the other field provides the list of zones to search for in the alarm history.

Here is an example where the instruction is “And: 2,4,6,8  With: 2,4,6,8”:

BUR Zone 2 is received.  Alarm history is checked to see if any of zones 2, 4, 6 or 8 were received in the last two minutes.  If so the new signal is presented to the operator.  If not, the signal is cancelled.  Two consecutive trips of zone 2 will result in operator action because zone 2 appears in both fields.

When should zone anding be used?

Every zone that consists of motion detectors is a good and proper candidate for zone anding.  The use of zone anding will prevent the dispatching of police in response to a single trip from a motion detector.  It is important to configure panels so that multiple trips are reported to the central station, up to a reasonable swinger shut down limit of three or more trips per zone.

Networked Systems:

            It has become common to use a single fire alarm control panel to protect a group of systems, sometimes in separate buildings with separate addresses.  Separate addresses require separate accounts and Central One offers a special low rate for fire alarm accounts that are members of a networked system.  For policy on networked systems please read bulletin 3001.

            When creating a networked system it is advantageous to keep the zone numbers for each separate account in a contiguous range.  Let’s say you are protecting three buildings, A, B, and C.  The panel is going to be installed in building A and will be account number 9990001.  Building A has devices on zones 1 through 3.  Building B has devices on zones 4 through 6,  Building C has devices on zones 7 through 9.  The signals in account 9990001 (building A) would be set up as follows:

Account 9990001:

Code

From Zone

To Zone

Alarm Type

Zone Comments

113

1

1

FIR

Water flow

110

2

2

FIR

General Fire

203

3

3

SUP

Gate Valve Tamper

65535

4

6

SPC

@9990002

65535

7

9

SPC

@9990003

            Zones 1 through 3 are set up and procedured in account 9990001.  Zones 4 through 6 are relayed to account 9990002.  Zones 7 through 9 are relayed to account 9990003.  Placing 65535 in the code field causes any alarm code to match.  It is a wild card value.  In order to relay signals from one account to another you must place the “@” symbol in the first character of the “Zone Comments” field, followed by the account number where the signal should go.  You must define the relayed signals in the destination accounts, as in:

Account 9990002:

Code

From Zone

To Zone

Alarm Type

Zone Comments

113

4

4

FIR

Water Flow

110

5

5

FIR

General Fire

203

6

6

SUP

Gate Valve Tamper

Account 9990003:

Code

From Zone

To Zone

Alarm Type

Zone Comments

113

7

7

FIR

Water Flow

110

8

8

FIR

General Fire

203

9

9

SUP

Gate Valve Tamper