Advanced Protection Logic Lynx Touch & Lyric Series

Transcription

1 Advanced Protection Logic Lynx Touch & Lyric Series Requirements: APL capable LYNX Touch Series or Lyric control panel GSM or CDMA, ILP5 IP Communicator, or WiFi IP Communicator Enabling APL via Panel programming: Please refer to control panel programming guide for entry options.. 1) In the Communicator programming section, enable APL by selecting and toggling APL option to Enabled. Select Save, then the back arrow to exit this section. 2) In the Reporter programming section, Primary CS Info page, toggle the Communicator Type and Phone Type to select the desired communication path(s). a. If using the Alarmnet communicator only (no phone line), toggle Phone Type to None and Communicator Type to select the AlarmNet Communicator type. b. If a phone line is also being used for reporting, toggle Phone Type to the desired format option and Communicator Type to select the AlarmNet Communicator type. Also toggle Dynamic Priority to either Redundant Reports or Preferred Radio. Do not select Telco First. i. If two-way voice and APL are being used, you must select Preferred Radio and set a delay under Dynamic Delay. ii. Increasing Dynamic Delay may be necessary to prevent undesired redundant reporting. 3) In order for APL logic to be used, the panel must be programmed with an entry delay and/or dialer delay applicable to the zone being reported. APL will not be employed if there are no programmed delays (no entry delay/no dialer delay) that would affect the normal reporting of the zone. a. Entry delays are programmed in the System Settings program section b. Dialer delay is enabled in Reporter/Options program section - 1 -

2 Enabling APL via AlarmNet360: APL can be enabled in the communicator via Alarmnet Direct Programming. Note this enables APL in the communicator only. Other programming selections must be made in the control panel as described in the steps above. 1) Access the account on the Show Programmed Devices page 2) Select Edit in the Actions drop down box and hit Go 3) On the account summary page, find the section labeled Enable Advanced Protection Logic and select the edit icon 4) Toggle APL on, then select Next at the bottom of the programming wizard 5) Continue with other pages of the wizard until the end is reached, then select Finish. Once you are back on the Show Programmed Devices page select Send Data, wait for three minutes then refresh the page to confirm successful program transfer

3 Basic Operation: System is armed Zone affected by entry delay and/or dialer delay is faulted starting the programmed entry delay (for Entry/Exit points) or putting the panel in alarm (for perimeter points) A corresponding Contact ID alarm message is immediately transmitted to AlarmNet. This message will include a logic bit that sets an APL delay. AlarmNet will hold this report and will not route this report to the Central Station until the end of the APL delay. Length of this APL delay is determined by Entry Delay (if any, depending on zone type of the faulted zone) + dialer delay + 75 secs (for potential network delay) The snapshot above shows an alarm condition reported on zone 2 with a 135 second APL delay. (135 second delay=30 second entry delay + 30 second dialer delay + 75 seconds.) This report will be held at AlarmNet for 135 secs and is not routed to the Central station at this point. Normal disarm: If the system is disarmed within the panel programmed delay(s), the corresponding alarm report (previously transmitted to AlarmNet as explained above) is aborted and is not sent to the Central Station. Note that an alarm on the zone may have occurred locally, but the CS will not receive the alarm report because the system was disarmed prior to the expiration of dialer delay. Example snapshot of an aborted APL-delayed report from AlarmNet Trace Tool: After successful disarming, the alarm condition is transmitted a second time (note retry count is 0002), but this time the report includes a logic bit to abort the routing of the original report to the CS. This report is therefore aborted and is not routed to the Central Station. Notice the message description AbortDelayedAlarm. NOTE: If the system is not disarmed prior to the expiration of the panel programmed delay(s), the original alarm report will be forwarded to the Central Station at the end of the APL delay

4 No disarm due to real alarm or panel compromise: If Alarmnet does not receive this abort notification within the APL delay as described above, AlarmNet will forward the corresponding Alarm report to the Central Station. Example snapshot from AlarmNet Trace Tool: Note this is not a new message. AlarmNet held the original report until the end of the APL delay, then forwarded the original report to the Central Station. NOTE: If the system is not disarmed prior to the expiration of the panel programmed delay(s), the original alarm report will be forwarded to the Central Station at the end of the APL delay even if the system had been disarmed during the APL delay. Refer to the timeline below for an illustrative explanation. 135 second APL Delay 30 second entry 30 second dialer delay additional 75 second delay If disarm occurs within this window, the alarm report will NOT be routed to the central station If disarm occurs within this window, OR if disarm doesn t occur at all, the alarm report WILL be routed to the central station at the end of this window Cancellation of the APL logic during panel programmed delay(s): If a subsequent alarm condition (such as an alarm on another zone, panel tamper, panic, etc) is triggered within the panel programmed delay time, the panel immediately reports these conditions. This will cause a cancellation of the APL logic and AlarmNet will route the original APL-delayed report to the CS along with the subsequently generated alarm reports. Refer to the illustrative timeline on the next page

5 Buffering of subsequent alarm reports during the additional 75 second delay window: ANY alarms (including Panics or Fire) triggered after the expiration of the panel programmed delay time(s), but before the end of the APL delay will be buffered by the panel/communicator and will be routed to the Central Station after the APL delay time has expired. Refer to the illustrative timeline below. 135 second APL Delay 30 second entry 30 second dialer delay additional 75 second delay If a subsequent alarm occurs within this window, the APL logic will be cancelled and all reports are routed immediately. If a subsequent alarm occurs within this window, the panel/communicator will buffer the reports and route them at the end of this window No communication response: In the event that the AlarmNet servers do not receive anything else from the communicator within 15 minutes of the routing of an APL-delayed report to the CS, a new contact ID message (E316 Tamper) is generated by AlarmNet and is also routed to the Central Station. Because this code is generated by AlarmNet, it will not be seen on the ANI trace tool, but can be seen on AlarmNet Direct Device status page and in TAC tools-alarm search if it was reported. The 316 CID code will not be generated if: 1) the communicator is not set up for AlarmNet supervision, 2) the APL-delayed report was aborted (due to normal disarm) 3) a subsequent report (such as an alarm or panel tamper) forces cancellation of the APL logic - 5 -

6 APL reports as seen on AlarmNet Direct-TAC tools-alarm Search: Normal Alarm routing (No APL-delay logic): Aborted APL-delayed alarm (no CS routing due to normal disarm): Delivered APL-delayed alarm (no disarm/panel potentially compromised): APL delay logic cancelled (due to subsequent alarm within panel programmed delay(s): - 6 -