MKS Help

UL® Installation Reference

This Help File Page was last Modified on 12/22/2015

Hide Navigation Pane

UL® Installation Reference

This Help File Page was last Modified on 12/22/2015

Previous topic Next topic No directory for this topic No expanding text in this topic  

UL® Installation Reference

This Help File Page was last Modified on 12/22/2015

Previous topic Next topic Topic directory requires JavaScript JavaScript is required for expanding text JavaScript is required for the print function Mail us feedback on this topic!  

The Micro Key Solutions applications, along with a Sybase SQL Anywhere Database application, that will be used by UL® 1981 Listed Central Stations are:

1) MKMS.exe ("MKMS"), 2) MKMSCS.exe ("MKMSCS"), 3) MKSSounds.exe (MKSSounds), 4) MKSSYSSTATUS.exe (MKSSysStatus), and 5) SPA.exe ("SPA").

 

1.MKMS - This is the Alarm Company Management program used - in relation to UL® Monitoring - primarily for:

a.Maintenance of key Codes

b.New Account entry

c.Entering and maintaining the Monitoring related Subscriber data

d.Producing the required UL® Central Station related Reports

 

2.MKMSCS - This is the actual Second Edition UL® 1981 Classified Central Station Alarm Monitoring alarm processing application which:

a.Maintains the Alarm Stack

b.Displays the Active Signals that require Processing

c.Controls the Operator Guided Response or defined Action Plan for an Active Signal

d.Tracks and Stores and Reports all of the Operator's Alarm Processing Steps that were performed

e.Automates the supervision of Active Systems

 

3.MKSSounds - This MKS Sounds application must be installed in the MKS\MKMS folder on each Work Station which may Process Signals, and must be started before MKMSCS is started, to properly produce the required Alarm and Warning Sounds

 

4.MKSSysStatus - This MKS Systems Status application ("SysStatus") must be installed in the MKS\MKMS folder and will supervise (among many other processes) the proper operation (and if it occurs, the failure) of the Backup Server, and if implemented, a tertiary MKMSCS Monitor (also see the UL Settings, Signal Processing & Reporting Procedures chapter for additional information).

a.The latest version of SysStatus (i.e. 1.1.0.7 or later) updates the Status of each Server every 15 seconds (instead of every Minute in the previous version)

SysStatus sends the required Signal to SPA before 90 Seconds as elapsed (the UL® Requirement) on a Failure

This produces the necessary A143 Signal ( see b. below) which tells the Operator that a Process Has Failed (and the Computer Name of that failure)

 

b.The special SPA record defined in the Subscribers Form with Subscriber Panels CSID of SPA (see the Special Subscriber Entries and the Signal Processing Errors chapters for additional information) must have a CSID Zone record for each of the following system monitoring event Signals to be properly supervised:

 

Signal ID = A141        Alarm Code = System Messages        OCTAR = Alarm        Description = System monitoring event (failed)

oThree Signal ID = A141 records must be entered with the following Physical Zones and Descriptions:

Zone 1: CPU

Zone 2: Memory

Zone 3: Hard drive space

Signal ID = A142        Alarm Code = System Messages        OCTAR = Alarm        Description = System monitoring event (restored)

oThree Signal ID = A142 records must be entered with the following Physical Zones and Descriptions:

Zone 1: CPU

Zone 2: Memory

Zone 3: Hard drive space

Signal ID = A143        Alarm Code = System Messages        OCTAR = Alarm        Description = Unresponsive process detected by SysStatus

 

c.SysStatus sends a Signal (which is an A143 for a Process Failure) with the Computer Name (and IP Address) when a Server is "down".

 

d.Therefore, if the Server's Computer Name is set as MKS1 (primary) and MKS2 (secondary), the Operator would know which Server went down without having to know the actual IP Address(es) for those Servers

This is beneficial because most Central Station Operators would generally not know (and so would have no need to understand) the IP Address Scheme to figure out which Server was down.

See the MKS Systems Status chapter for detailed information.

 

 

5.SPA is the Signal Processing Application which:

Note: An IP Connection for Sur-Gard Sys III Receivers for UL® applications cannot be used unless Serial is active as a backup.

 

a.Translates Receivers outputs to properly identify the specific Signal that needs to be processed

b.Translates SysStatus outputs to properly supervise certain system components and ancillary applications

c.Processes Passive Signals and records that information

d.Is used by MKMSCS to interpret the Signals sent by the Subscribers

e.Populates the Alarm Stack

f.Manages the On Hold and Account Testing timers

 

6.Special Firewall Settings - Specific settings for the Windows® Firewall which are relevant to each Receiver (These instructions are provided as a result of fail-over testing where, in some cases, the Firewall prevented SPA from re-connecting to the receiver(s), thus blocking those ports):

It is important to note that even if the Windows® Firewall is turned off, these rules must still be set to prevent the Windows® Firewall from blocking those Signals that can come in to the Signal Processing Application ("SPA.exe").

Therefore, Windows® Firewall must have exceptions created through the Windows Firewall with Advanced Security dialog when your Company is using IP Receivers for Incoming and Outgoing TCP and UDP Ports. 

Select Control Panel > Windows Firewall > Advanced Settings > Inbound Rules >

Select New Rule...

 

HelpFilesULSetPortsInboundOutbound

Windows Firewall with Advanced Security dialog - Inbound Rule - New Rule... option

 

Select Protocol and Ports > TCP

Select Special local ports:

Enter 1025

 

HelpFilesULSetPorts

Windows Firewall with Advanced Security dialog - New Inbound Rule Wizard - Protocol and Ports option

 

Repeat for Outbound Rules

 

HelpFilesULSetPortsNewRule

Windows Firewall with Advanced Security dialog - Outbound Rule - New Rule... option

 

 

7.Identify Primary and Backup Servers - Manual to show and define language that shows which server via IP is either back-up(s) or primary so when the error message is displayed, the operator will know which one of the servers is no longer in service.

a.Each Server must be assigned a Computer Name [e.g., MKS1 (primary), MKS2 (secondary)]

b.The MKS Systems Status application ("SysStatus") must be installed.

c.The special SPA record defined in the Subscribers Form must have the appropriate CSID Zone records defined (see #4., a. above).

d.In the event of a Server Failure, SysStatus sends a Signal to SPA (which is an A143 for a Server Failure) with the Computer Name (and IP Address).

e.That Signal is presented to the Operator as an Alarm Event.

f.Referring to step a. above, if the Server's Computer Name is set as MKS1 (primary) and MKS2 (secondary), the Operator would know which Server went down without having to know the actual IP Address for those Servers

 

These applications, where required, are installed in the C:\Program Files\MKS\MKMS folder (or in the C:\Program Files(x86)\MKS\MKMS folder on 64bit machines).

 

Throughout this Electronic Manual (dated on or after April 24, 2012) there are:

Dedicated UL® 1981 Second Edition chapters,

Specific references to UL® 1981 Second Edition

Within the remaining chapters, the User will find the necessary features to meet the requirements enumerated in the Second Edition UL® 1981 Standard.  

This information will be used by those Alarm Companies which are required to properly set-up and operate their Central Station in compliance with the Second Edition UL® 1981 Standard.

Special information is provided specifically for compliance with 20(8) in the UL Settings, Signal Processing & Reporting Procedures chapter.