Automated Signal Processing - Enhanced

This Help File Page was issued on 09/30/2017

This Help File Page was last Modified on 02/23/2022

<< Click to Display Table of Contents >>

Navigation:  Central Station Monitoring > Central Station General Maintenance Entries >

Automated Signal Processing - Enhanced

This Help File Page was issued on 09/30/2017

This Help File Page was last Modified on 02/23/2022

Previously, the Automated System Actions ("MKSASP") application was the Action Plan Processing Engine, which ran as a Windows® Service that could execute - in the background - a specific set of predefined instructions (the Action Steps associated with an Automated System Action Plan) - with no Operator action required.

As of Millennium Series MKMS v 5.1.35.8300 and MKMSCS v 5.1.35.7200 or later, Micro Key is using the MKS Customer Connect Service for these Automated System Action Plans (ASP), plus the Low Level Processing (LLP), and Automatic Action Procedures (AAP); along with Twilio (www.twilio.com) to remotely provide the associated cloud based SMS and IVR (Text and Voice) communication services

 

Understanding the capabilities of the revised Enhanced Automatic Signal Processing feature:

When an Alarm Signal of any kind is inserted into the Alarm Stack prior to being presented to an Operator for Processing,

The system determines whether or not the signal should be automatically processed

If it is to be automatically processed, the system chooses which of the three available automatic signal processing strategies should be used.

These are:

i.Automated System Action Plan (ASP) using Email and/or Pager communication

ii.Low Level Processing (LLP) using interactive Voice (IVR) or interactive Text (SMS)

iii.Automatic Action Procedures (AAP) using all communication options

 

I.The Automated System Action Plan Action Steps (ASP) will be performed for a Subscriber (executed only for the first matching case within the processing priority order listed below) when the Central Station Monitoring module receives a Signal and:

1.The Alarm Condition Code for that Signal has an Automated System Action Plan assigned to it, or

2.An Automated System Action Plan and designated Alarm Condition Code combination is assigned to the Subscriber record that was entered to represent an Alarm Dealer one of whose Subscribers transmitted that Signal, or

3.An Automated System Action Plan and designated Alarm Condition Code combination was entered in the Action Plans tab on the Central Station Data Form in which case, for any Signal with that combination transmitted by the Subscriber - regardless of which Subscriber Panel CSID sent it, or

4.The CSID Zone record which matches that Signal has an Automated System Action Plan assigned to it.

 

Typically, Automated System Action Plans are used to Automate the Notification process when only the Subscriber, one of their People To Call in the Subscriber's Call List, or in the Subscriber's Alternate Call List, and/or if their Alarm Dealer needs to know when a designated Alarm Condition Code and/or CSID Zone was received at the Central Station.

All Action Steps performed for any Signals processed in this manner are stored in the associated Subscriber's Alarm History file.

 

Implementing the Automated System Actions (ASP) service:

First, in Company Settings

Set the ASP Worker Enabled option to True (ASPWorkerEnabled = "T") .

Set ASP Expire Minutes option - the Signal Not Processed Expiration Time - to the desired value (ASPExpireMinutes = "3").  

oThis will be the time after which the Alarm Signal, if not completed, will be returned to the Alarm Stack with a Pending Status.

Set Automated Users to match the SPA specific setting and matches the associated Employee Code(s) entered in the Automated Action Plans employee codes (separated by commas) field on the System tab in the Setup Form within SPA (see the General - Column 1 section in that System tab Chapter Topic for more information).

Executes using the internal "aspProcessAlarms" stored procedure.

 

There are 8 possible types of entries which should be completed before ASP may be used:

1.Create a fictitious Employee (as shown below) to be used to Login to the ASP service, and for identifying the Operator of record when posting the executed Action Steps in the Subscriber's Alarm History file (an example of which is shown below).

 

HelpFilesActionPlansMKSASPEmployee

Employee Form - ASP - Automated System Action Plan Employee

 

Only fields that are highlighted as Mandatory fields need to be completed.

The Employee's Code is used to identify the "Operator" who performed the Automated System Action Plan Action Steps when this information is stored in the Subscriber's Alarm History file.

 

HelpFilesActionPlansMKSASPSignalDetail

Alarm History detail - showing Automated System assigned Employee Code

 

2.Define the appropriate Resolution Code(s) that will be assigned to the special Automated System Action Plan Action Step which Completes the Signal.

 

HelpFilesActionPlansMKSASPResolutionCode

Resolution Codes Form - ASP - Resolution Code for Automated System Action Plan

 

Only one Resolution Code must be entered, but more than one may be defined, based on the number of specific Resolution Descriptions that are desired.

 

3.Implement ASP functionality using the special Employee Code entered in step 1. above.

 

4.Identify each Action Plan that will contain the necessary "Automated System" Action Steps.

 

HelpFilesActionPlansMKSASPActionPlan

Action Plans Form - Automated System Action Plan

 

Automated System - Be sure to Check the Automated System box when this Action Plan should be processed as an Automated System Action.

 

5.Create the required Action Steps, particularly the finalizing Complete or On Hold properties (see the "Using the Action Plan - Properties dialog" section in the Defining an Action Plan chapter for more information.

 

HelpFilesActionPlansMKSASPActionPlanCompleteProperties

Action Plans Form - Complete tab on the Action Plan Properties dialog

 

6.Enter any Alarm Condition Code which should always be processed as an MKSASP by assigning that (those) record(s)  the appropriate Automated System Action Plan.

 

HelpFilesAlarmConditionAutomatedSystemEntry

Alarm Conditions Form - Automated System Action Plan entry

 

Action Plan - Using the Drop-Down Selection List provided, Choose the appropriate Automated System Action Plan.

 

7.Assign the Automated System Action Plan - and optionally a Signal ID and/or Physical Zone - to any CSID Zone(s) that should be processed by the MKSASP service.

 

HelpFilesActionPlansMKSASPCSIDZone

CSID Zone Form - with Automated System Action Plan

 

Important Note: The information below is specific to those Signals which are to be processed by the ASP service:

Signal ID - Enter the specific Signal Identifier for this Signal and/or

Physical Zone - Optionally, enter the Zone Code, if one will be transmitted along with the Signal Identifier.

Alarm Code - Use the Drop-Down Selection List provided to Choose the appropriate Alarm Condition Code.

OCT AR Code - Use the Drop-Down Selection List provided to Choose Alarm.

Response Needed? - Check this box when the Response is to be provided by the ASP service.

Action Plan - Because there is a Response Needed for this Alarm Signal - which will be provided by the ASP service - a predefined Automated System Action Plan is required.

oUse the Drop-Down Selection List to Choose the appropriate Automated System Action Plan for processing this Alarm Signal.

Available To Call - This Available To Call list of Contacts contains the People To Call associated with for the CSID for which this CSID Zone is created, plus any others Contacts available from the Global Call List members (see above), and represents the default order in which Operator Notifications should proceed until someone is successfully notified (see the "Available To Call" discussion in the CSID Zones chapter).

Call Order - Set the Call Order with the People To Call who are to be notified of this Signal.

 

8.Enter a Condition Code and a predefined Automated System Action Plan (more than one set may be entered) in the Action Plans tab on the Central Station Data Form for any Subscriber who will be using this feature in the ASP service.

 

HelpFilesCentralStationDataActionPlanTab

Edit View - Monitoring tab - Action Plans entry

 

A Condition Code and Automated System Action Plan combination entered in the Action Plans tab for the Subscriber will take precedence over all of that Subscriber's Accounts (CSIDs).

In the same manner, a Condition Code and Automated System Action Plan combination - entered in the Action Plans tab for the Subscriber record which represents an Alarm Dealer - will take precedence over all of that Dealer's Accounts.

 

II.Interactive Low Level Signal Processing (LLP) using Contacts and employing Interactive Voice (IVR) and/or Interactive Text (SMS) functionality

Implementing the Low Level Signal Processing (LLP) service

First, in Company Settings

Set the LLP Worker Enabled option to True (LLPWorkerEnabled = "T") .

Set LLP Expire Minutes option - the Signal Not Processed Expiration Time - to the desired value (LLPExpireMinutes = "3").  

oThis will be the time after which the Alarm Signal, if not completed, will be returned to the Alarm Stack with a Pending Status.

Set the LLP Priority option to a value (LLPriority = "7") representing the the maximum level, at or above, which these signal may be precessed.

 

1.Requires an Action Plan with the appropriate Action Steps defined.

2.The Interactive Text (SMS) and Interactive Voice (IVR) functions require the appropriate Predefined Messages to be defined.

3.Requires that the Subscribers' People To Call telephone numbers be identified in a Third Party Service definition as subscribed users (e.g., Registered Subscribers and Registered Users)

4.Executes using the internal "llpProcessAlarms" stored procedure.

 

III.Automatic Action Processing (AAP) requires an Automatic Actions definition for Automatic Action Command Signal execution.

First, in Company Settings

Set the AAP Worker Enabled option to True (AAPWorkerEnabled = "T") .

Set AAP Expire Minutes option - the Signal Not Processed Expiration Time - to the desired value (AAPExpireMinutes = "3").  

oThis will be the time after which the Alarm Signal, if not completed, will be returned to the Alarm Stack with a Pending Status.

 

HelpFilesAutomaticActionsForm

Automatic Actions Form

 

1.Will attempt to process designated alarm signals using SMS or IVR communications based on the defined Automatic Action

2.Contacts (People To Call, plus any others Contacts available from the Global Call List) do not have to be Registered Users

3.Supports all Automatic Action Commands (see Supported Action Pattern Codes in the Understanding MKS Customer Connect chapter for that list)

 

 

02/22/2022