MKS Help

UL® Settings, Signal Processing & Reporting Procedures

This Help File Page was last Modified on 02/06/2016

Hide Navigation Pane

UL® Settings, Signal Processing & Reporting Procedures

This Help File Page was last Modified on 02/06/2016

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

UL® Settings, Signal Processing & Reporting Procedures

This Help File Page was last Modified on 02/06/2016

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 purpose of this chapter is to identify certain steps which are required when implementing the Second Edition UL® 1981 Standard, specifically for compliance with 20.8(a-q), and 24.3, Passwords:

Passwords - The Employee's Password (Documented here, and in the associated chapters throughout this Electronic Manual) should contain 6 characters with:

One (1) alpha,

One (1) numeric,

Contain no word from the Employee's Name or their User Name,

Contain no consecutive numeric (e.g., "3456", "1234") or alphabetic sequences (e.g., "abcd", "wxyz")

Contain no repeating (e.g., "2222", "aaaa", "1111", "zzzz") characters.

 

Setting the Audit Access Right - Certain Form Names (those that represent the Subscriber record itself, and most subordinate Forms which may be accessed from within the Edit View of the Subscriber Form), and/or Access Rights that are established using the User Access Rights, and/or the Employee Groups, and/or the Security tab on the Employee Forms for assigning Access Rights to certain other Forms, must Check (turn on) the Audit Access Right for the following Form Names which have access granted to any Employee using those User Access Rights, and/or the Employee Groups, and/or the Security tab on the Employee Forms:

Employee

Employee Groups  

User Access Rights

Subscribers Form (the Edit View of the Subscriber Form):

Acquisitions

Service

Accounts Receivable

Monitoring tab:

Central Station

Subscriber Action Plans

Subscriber Panel

Temp Notes

Subscriber Holidays

Event (Account Testing)

CSID Zone (Unverified Zones)

People to Call (Reorder Numbers)

Call Number

Call List

Medical Information

Area

Conditions Contact List

Unverified Zones

Loss Prevention

Floor Plan

 

Special Settings - The data entry requirements for a Subscriber with a UL® Classified (Certificated) installation:

1.Security Company - If required, identify what Security Company will be providing Investigator Response Services for each Subscriber (documented in the Central Station Data chapter).

2.O&C Supervised - Specify what type of supervision, if any, is required (documented in the Central Station Data chapter and the Events chapter)

3.Supervised Events - Explain how to adjust the supervisory "Windows" properly to have a sufficient grace period before and after their regularly scheduled opening and closing times (documented in the "UL® Supervised Open and Closing Events" section of the Events chapter).

4.UL Classification - Identify the UL® Classification (documented in the Central Station Data chapter).

5.UL Response Time - Identify the required Investigator Response Time in minutes (documented in the Central Station Data chapter).

6.Restored Signals - In addition to the Failed to Restore Signal (which is assigned the FR* Alarm Condition Code in the Panel Zones and/or the CSID Zones Forms) resulting from a previously reported System Fault or Trouble Signal that has not been corrected within the designated Restoral Information Minutes entry, for those Subscribers who are designated as UL® Classified Accounts, a Restoral Signal resulting from the correction of that System Fault must also be acknowledged by an Operator when that associated Restoral Signal is received (documented in the "UL® Restoral Considerations" section of the Restoral Information chapter) and so must be defined, as well.

 

Operator Procedures - The steps required by an Operator when processing an Alarm Signal received from a Subscriber identified as having a UL® Classified (Certificated) installation (documented in "The Operator Procedures" section in this chapter and again in each of the associated chapters - as noted below - throughout this Electronic Manual).

 

Reporting Requirements - The instructions for how the required Alarm Ticket Report are provided (documented in "The The Reporting Requirements" section in this chapter, and again in each of the associated chapters throughout this Electronic Manual).  

 

Note: The procedures within this Electronic Manual that reference the Second Edition UL® 1981 Standard are those dated on or after April 24, 2012.

 

The Special Settings Requirements: Most of the Alarm Ticket Report requirements enumerated in items 20.8(a-q) Second Edition UL® 1981 Standard are produced by default.

But, there are a few Special Settings within the database that will need to be properly configured to automatically produce the required Alarm Ticket Report for a Subscriber with a UL® Grade (Certificated) installation.

Each applicable 20.8(a-q) Second Edition UL® 1981 Standard that necessitates a special setting is listed below.

The required instructions for these Special Settings are explained in detail.

Links to the appropriate chapter(s) within this Electronic Manual are also provided.

These Links offer the complete instructions for all of the information that may be entered into the associated Forms.

 

Special Settings: The following information will explain how to identify line security, and record the method used to verify the alarm investigator's arrival, whether the central station holds keys, whether the keys were used by the investigator, and if a sounding device is provided on the alarm system:

d) "Whether there is standard or encrypted line security. When provided, it shall be indicated"

If the line security for the Account is encrypted, within MKMS open a Subscribers Form and locate that Account.

Select the Edit View Icon, Choose the Monitoring tab to display their Central Station Data.

oTowards the bottom of that Monitoring tab is the Subscriber Panel(s) section where each CSID used by this Account will be listed.

oLocate each CSID with encrypted line security.

 

HelpFilesSubscriberPanelsConnectionIDEncryptedLine

Subscribers Form - Edit View - Monitoring tab - Subscriber Panels section - Panel connection ID - Encrypted Line

 

Panel Connection ID - In the Panel connection ID field within the Subscriber Panel(s) section, (see mouse pointer in the illustration above) using the Drop-Down Selection List provided, Choose the Encrypted Line option.

 

Note: See items e), f) and g) in the "The Operator Procedures" section below which explain how to:

orecord the time an event was received,

orecord when Police or Fire responders were dispatched,

orecord when any alarm investigator was dispatched.

 

l) "The time the alarm investigator No. 1 arrived (fire / burglar)"

The method used to require the Operator to verify the alarm investigator's arrival is triggered by an entry in the UL Classification field in the Central Station Data section of the Monitoring tab in the Edit View of the Subscribers Form, Choose

oThe Priority Level set for the Alarm Condition of the incoming signal which must be either 1, 2, 3, or 4.

 

HelpFilesAlarmConditionCodeUL

Alarm Condition Form - Priority field

 

oSelecting the proper UL® Classification (see the yellow highlight and the mouse pointer in the illustration below) for the Subscriber, in combination with having the triggering Priority Level (i.e., 1, 2, 3, or 4) assigned to the Alarm Condition Code (see the yellow highlight and the mouse pointer in the illustration above) of the alarm event being reported, will force the application when completing an alarm to ask the Operator for the “Investigator’s arrival verified by?" by prompting the Operator for a typed response in an Arrival Response dialog box.

 

Special UL fields

 

HelpFilesCentralStationData-SpecialULFields

Subscribers Form - Edit View - Monitoring tab - UL Classification - UL Response Time - Keys Held - Sounder fields

 

The Investigator Arrival entry is automatically time-stamped (and the elapsed time from Dispatch calculated) when it is saved by Clicking the OK button.

 

HelpFilesOption_ i And j-A

Investigator Arrival dialog - Elapsed Time calculated automatically

 

m) "Whether the central-station holds keys"

Keys Held - In the same Central Station Data section, Check the Keys Held box, if appropriate (that field is also shown in the Special UL fields illustration above).

oWhen this central-station does in fact have keys for this protected premises information, it will be included on the Alarm Ticket Report.

 

q) "Whether a sounding device is provided on the alarm system (optional)"

Sounder - In the same Central Station Data section, Check the Sounder box (that field is also shown in the Special UL fields illustration above), if appropriate.

oThis sounding device information will be included on the Alarm Ticket Report.

 

n) "Whether the keys were used or not used (fire / burglar)"

Selecting the proper UL® Classification in the the Central Station Data section and assuming the Alarm Condition of the incoming signal is assigned the triggering Priority Level (1, 2, 3, or 4), will force the application - when completing an alarm - to ask the Operator "Were keys used?" and prompt that Operator with a 'YES' or 'NO' selection.

 

HelpFilesConfirmWereKeysUsed

 

The Operator Procedures:

Special Procedures: The following Operator actions will record the required Times, record the method used to verify the alarm investigator's arrival, and identify whether the keys were used by the Investigator:

e) "The time the alarm was received by the automation system (fire/burglar)"

This information is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

 

f) "The time the police / fire department was notified, and the police / fire department identification number (fire/burglar)"

When and to whom an Operator requests a Dispatch of Police or Fire Responders is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

All UL® Certificated Accounts require a Resolution, Disposition or Reason for the Alarm incident or investigation, (e.g., False Alarm, or Actual Alarm, Subscriber Error, etc.) be recorded.

This requirement is implemented by requiring that the appropriate Resolution Code be identified before the Alarm Signal is Completed by the Operator.

 

g) "The time the alarm investigator No. 1 was dispatched, and the investigator's name and employee ID (burglar)"

 

HelpFilesOptions_ gAndh

 

When an Alarm Investigator (e.g., Security Company) is Dispatched, the Operator must enter a Note using the available Notes tab on the Signal Processing Form, and include that Investigator's Name and Employee ID (see typical example of a Note entry in the illustration above).

The Note, and the time of this action is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

 

h) "The time the alarm investigator No. 2 (if any) was dispatched, and the investigator's name and employee ID (burglar)"

If a second Alarm Investigator is Dispatched, the Operator must enter a Note using the available Notes tab on the Signal Processing Form, and include that second Investigator's Name and Employee ID (see typical example in the illustration above).

The Note, and the time of this action is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

 

l) "The time the alarm investigator No. 1 arrived (fire / burglar)"

The Investigator Arrival Note, and the time of this action, along with the elapsed time from Dispatch is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

j) "The time the alarm investigator No.2 arrived (if dispatched) (fire / burglar)"

The Investigator Arrival Note, and the time of this action, along with the elapsed time from Dispatch is captured, recorded in the Signal History table, and included in the Alarm Ticket Report automatically.

 

HelpFilesOption_ i And j

Note entry of Investigator Dispatch - Investigator Arrival dialog - Current Signal's History notation

 

While Processing the Alarm, when an Alarm Investigator (either #1 or #2) arrives on Premises:

 

HelpFilesSignalProcessingFormActionsButtonInvestigatedOption

Signal Processing Form - Actions button - Investigated option

 

oThe Operator will Select the Actions button to open the Actions button Menu

oOn that Menu, Select the Investigated option

oType in the Name of the arriving Alarm Investigator in the Investigator Arrival dialog

oClick the OK button

 

The Investigator Arrival Note is automatically time-stamped when saved by Clicking the OK button.

oThe time of arrival, and the elapsed time between Investigator Dispatch and Arrival is calculated and both are included in the Alarm Ticket Report automatically.

oA Verification Method dialog may be displayed to capture how the Operator Confirmed the Investigator's Arrival.

 

HelpFilesVerificationMethodInvestigatorsArrivalVerifiedBy

Verification Method

 

The remaining requirements in the 20.8 Second Edition UL® 1981 Standard are accommodated automatically in the Alarm Ticket Report.

Before completing the alarm, the Operator may make note of the Alarm Event's incident number (which is also saved automatically in the Signal History table), if and when they want to print the UL® Alarm Ticket Report at a later time.  

 

The Reporting Requirements:

The Alarm Ticket Report is a detailed report of exactly what was done while an Operator processed of an Alarm Signal.

The Special Settings Requirements and Operator Procedures (documented above to comply with the Second Edition UL® 1981 Standard) must be followed when Processing Alarm Signals with a Priority Level from 1 to 4 for those Subscribers with a UL® Classification assigned in the Central Station Data section.

The Alarm Ticket Report for the currently displayed alarm event may be printed at any time while that alarm event is still being Processed by selecting the Print Alarm Ticket option accessed using the Actions button

 

HelpFilesSignalProcessingActionsMenuPrintAlarmTicketOption

 

To access the Alarm Tickets Report dialog (within MKMS):

1.From the Backstage Menu System Select Reports and Choose Monitoring and Select the Alarm Ticket option

2.From the Quick Access Menu, Select Reports and Choose Monitoring and Select the Alarm Ticket option

 

HelpFilesPrintAlarmTicketDialog

Alarm Tickets dialog

 

When the Alarm Tickets Report dialog is presented:

Report For - Choose the One Alarm Only option.

Incident Number - Enter the Incident Number to be reported.

Print - Click the Print button to produce the report.

 

HelpFilesAlarmTicketULExample

Alarm Ticket - Preview - UL  Status & Dispatch information