Modem II/SIA Codes



Some alarm installers use the code BA (interpreted by our cs as a Burg) to report a general ALARM condition to the CS. This can include any zone (such as Fire,Freezer, or Trouble). In order to make the event display correctly to the operators, sometimes the event must be overridden in the code page if they are not reprogrammed to report the proper codes.

EXAMPLE: if you have a Code BA "Burg" with a zone description of Smoke
Detector, you must override that event to report as a fire alarm.

Code:"none" Event Type: "Burg" Action: ">0" Zone: "1"


You do not want to do a general override on all burgs, just the override as described for the zones that are labeled Fire Heat or Smoke (check activity to see if they report the way they are supposed to.)

**Note: DO NOT use the code BA in the override, this could cause some major problems on the account as anything that reports SIA format with a BA in the code will override all code BA's to whatever you have in the override.

EXAMPLE:
Code: "BA" Event Type: "Burg" Action: ">0" Zone: "1"

*** This will override ALL code BA's to be Fire alarms zone 1's ***


Processing

Modem II:

If you receive a BAxx via Modem II then the "xx" will be looked-up in the Code List as part of the Code Lookup process (below). If xx is not found in the Code List, then the pre-defined Event Type for BA will be used (Alarm) and the xx will be considered the Zone #. You can then use Action Overrides to change how an Alarm on zone xx should be handled. i.e. BA12 = Burglary Zone 12. You would create a new Code record with a Code of 12 and ZorU of 12 and choose the Event Type you would like it to be interpreted as. Enter the Zone Description in the Description field or add it to the Zone List.

SIA:

The Code, Area, ZorU, and Alarm/Restore are looked-up in the code list. If no match, then the Code, Area, and Alarm/Restore will be looked up. If either match, the Event Type, Actions, Description and Message on the record found will be used. Processing will then skip Code Lookup and continue with Action Overrides (below). Then, if there is a Code listed, the Event Type, Area, ZorU, Description, Action, and Message will be used.

Look for Code Message:

Then, the Code is looked up with an Event Type of Message and matching Area and ZorU for an Action and/or Message to use. ZorU should be blank for All zones/users.

ACTIONS:To view a complete list of the available actions, click here.

The Actions are used by the Operator to handle the signal. If "L" is in the actions box, the signal will be Automatically Logged Off. The only time you would put an "L" in the action is if you do NOT want the Operator to handle the event.

Special case is if the account is a Two-Way panel that has a signal that needs to be disconnected the then logged-off without any other actions. You can then enter "DL" which will "automatically disconnect" the two-way then "automatically log" the signal without operator intervention.

Another case you would use "L" would be to automatically generate a Service Request then log the signal "QL" without any operator intervention.

Note: "L" will not be allowed unless it is combined with another "automatic" action. I.e. We can not V(erify) and automatically L(og) the signal off at the same time, an Operator must Log off the signal after Verifying, so you cannot use the "L" in the Actions if you want the operator to do anything on the signal.


To view a list of the codes that are used by our computer for SIA/Modem II format lookup, please click here.

Adding Temporary Action/Message for a specific Event Type:

LEAVE THE CODE BLANK, choose the Event Type, and enter the actions/message/end time (leave end time blank for it to be permanent). If you want this to occur for All Areas then leave Area as 0, otherwise the message will only be used for the specific Area entered. If you want this to occur only for a specific Zone or User then enter the ZorU.

(I.e. Code=BLANK, Event Type=Burg, Actions=VR, Area=0, ZorU=BLANK (to override all burgs)or as in the example below, "5" in the ZorU will override the actions for just zone 5)
Example:

<% if server_port <> 443 then %> <% end if %>

Web View

OPI View


Logging a zone:

To set a zone to log, enter the Event Type, Area, and Zone that you want to log, and set the Actions to "L(og)."
Example:

<% if server_port <> 443 then %> <% end if %>

Web View

OPI View


Action Overrides for Event Types:

Once the Event Type has been identified, the code list will be searched for that Event Type and Area and ZorU (Code should be blank) to see if there is an Action and/or Message that should be used. Area 0 in the code list will be found for All Areas.

You can enter a Start and Stop Date and/or Time if you only want the override to be in effect for a Range of Days (enter Date And Time) or a Range of Hours in a Day (just enter the Time). If a Date is entered with the Time, then the override will only be active between the Start Date/Time and the Stop Date/Time. If just the Time is entered in either field then the override will be active Every Day but only between the Start Time and Stop Time.

If you enter a Date in one of the fields then you should also enter a Date in the other field (do not just enter the Time in one field when there is a Date in the other). I.e. Always enter a Start AND Stop Date and/or Time, leaving one of them blank, or entering a Date in one and a Time in the other will work, but may cause confusion as to the actual Dates and Times that the System will use. It is best to be specific to avoid misunderstandings.

You can also enter a Message on this Override record which will be displayed with the Pending Event.

DO NOT attempt to put a Start and Stop time on a standard Code definition. Only use Start and Stop times for Action Overrides. Enter the code like normal (including the Zone and Area) to define the initial signal, then create another record to override the actions with the Start and Stop times for that Event Type by Zone and Area.

If you want to disregard all burgs/fires/panics, etc. check the area that they are coming in on, put the Event Type in, and leave the zone blank. Then change the action to "L(og)". This will log all alarms that come in with the event type that you have listed. If it is a 2-way account, make the Action "D(isconnect)L(og)" this will tell the computer to disconnect the 2-way and log the event with no operator help. Changing an event type to something other than what is reported requires a different procedure.

<% if server_port <> 443 then %> <% end if %>

Web View

OPI View

Changing the Event Type for SIA/Modem II:

Sia/Modem II reports codes such as "BA" for Burg. To change the Event Type for the code received, you have to leave the code blank,put the Event Type (Burg), and change the Action to ">##". The number you place in the Actions box will be the Event Type number code that can be found next to the Event Type in the drop down box. You do not want to change the Event Type that the code reports by changing the Event Type box. You will change the Event Type by placing the Event Type number in the actions box, you can view the Event Type numbers in the List menu located at the top of your screen. This will also work to override DMP Codes.

<% if server_port <> 443 then %> <% end if %>

Web View

OPI View



Please send any questions or comments regarding Data Entry to: DataEntry@AZSecurity.com.