MKSASP - Automated System Action Plan Service

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

<< Click to Display Table of Contents >>

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

MKSASP - Automated System Action Plan Service

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

Micro Key Solutions Automated System Actions ("MKSASP") application is an Action Plan Processing Engine, which runs as a Windows® Service that can 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.

These Automated System Action Plan Action Steps 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, this feature is 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.

Note: All Action Steps performed for any Signals processed by the MKSASP application are stored in the associated Subscriber's Alarm History file.

 

Implementing the Automated System Actions ("MKSASP") application:

There are 8 possible types of entries that should be performed before this application may be used:

1.Create a fictitious Employee (as shown below) to be used to Login to the MKSASP application, 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 - 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 - 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.Install MKSASP application using the special Employee Code entered above.

The MKSASP application is installed as a Windows® Service on each PC within the Network that will be using this application as follows:

"c:\program files\mks\mkms\MKSASP.EXE" /Install /Oper=???   (??? =  The Employee Code entered in Step 1. above)

 

4.Identify each Action Plan that will contain the "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 with the Automated System Actions ("MKSASP") application.

 

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 by the MKSASP application 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 application.

 

HelpFilesActionPlansMKSASPCSIDZone

CSID Zone Form - with Automated System Action Plan

 

Note: The information below is specific to those Signals which are to be processed by the MKSASP application:

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.

OCTAR 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 MKSASP application.

Action Plan - Because there is a Response Needed for this Alarm Signal - which will be provided by the MKSASP application - 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.

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 MKSASP application.

 

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.