UL 1981 Compliance Option Setup and User Guide

Transcription

1 2013 UL 1981 Compliance Option Setup and User Guide PERPETUAL INNOVATION

2 Lenel OnGuard 2013 UL 1981 Compliance Option Setup and User Guide, product version 6.6. This guide is part 1 of a 1-document suite, item number DOC-620, revision 3.007, July Copyright Lenel Systems International, Inc. Information in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Lenel Systems International, Inc. Non-English versions of Lenel documents are offered as a service to our global audiences. We have attempted to provide an accurate translation of the text, but the official text is the English text, and any differences in the translation are not binding and have no legal effect. The software described in this document is furnished under a license agreement and may only be used in accordance with the terms of that agreement. Lenel and OnGuard are registered trademarks of Lenel Systems International, Inc. Microsoft, Windows, Windows Server, and Windows Vista are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Integral and FlashPoint are trademarks of Integral Technologies, Inc. Crystal Reports for Windows is a trademark of Crystal Computer Services, Inc. Oracle is a registered trademark of Oracle Corporation. Other product names mentioned in this User Guide may be trademarks or registered trademarks of their respective companies and are hereby acknowledged. Portions of this product were created using LEADTOOLS LEAD Technologies, Inc. ALL RIGHTS RESERVED. OnGuard includes ImageStream Graphic Filters. Copyright Inso Corporation. All rights reserved. ImageStream Graphic Filters and ImageStream are registered trademarks of Inso Corporation.

3 Table of Contents System Requirements Hardware Conventions Used in this Documentation Standby System Database Backup and Restoration Configure Database Backup and Restoration UL 1981 Security Levels UL 1981 User Create a UL 1981 User Receiver Accounts Configure the Receiver Accounts Form UL 1981 Compliant Alarms Configure Alarms to be UL 1981 Compliant Configure Alarm Priorities Enable Audio Alarms Alarm Audit Trail Acknowledge Alarms Show or Hide Events Marked In Progress UL 1981 Reports Run a UL 1981 Report Run an Event Report Run an Alarm Resolution Report Report Accounts by Type and Designated Response Time View Active and Inactive Accounts Print a Report Runaway System Configure Automatic Runaway System Suspension Suspend and Restore an Account Backing Up Your Database to File Back Up to a File on SQL Server 2008 Database UL 1981 Compliance Option Setup and User Guide 3

4 Table of Contents Back Up to a File on SQL Server Express Edition Backing Up to CD/DVD Backing Up to Tape Back Up to Tape on SQL Server Database Back Up to Tape on SQL Server 2008 Express Edition Restoring Databases Restore the Database on SQL Server Restore the Database on SQL Server Desktop Engine Index UL 1981 Compliance Option Setup and User Guide

5 CHAPTER 1 Introduction To comply with UL 1981 requirements, OnGuard now automates the processes regarding change-ofstatus signals that are generated by receivers. If there is a failure of the automated system, the receiving equipment is configured to record change-of-status signals and displays visual signals that identify the source and type of signal that requires the user s attention.when there is a failure of the automation system, the change of status signals that are displayed at the receiver shall be handled in accordance with the applicable UL requirements until automation has been restored. UL 1981 OnGuard users are operators dedicated to handling alarm signals. For further information on obtaining UL 1981 site certification for your UL 1981 installation, see the UL 1981 Site Certification Program Industry Bulletin PDF file located in the documents directory of the OnGuard workstation. System Requirements Minimum system requirements for an OnGuard system are: OnGuard versions 6.1, 6.3, 6.4 (including hot fix versions), or 6.5 Windows 7, Server 2003, or 2008 Microsoft MSDE, SQL Express, SQL 2008, or Oracle Pentium IV dual core processor 2 GB RAM DVD-ROM USB port 1024x768 color display 6 GB of available space Network requirements: 100BASE-T or greater Failover software NEC ExpressCluster Software version X R2 or later UL 1981 Compliance Option Setup and User Guide 5

6 Hardware The Bosch D6600 and D6100 are the only receivers approved for use in the UL 1981 OnGuard system. The D6600 or D6100 receiver is required to serve as a watchdog timer and shall be located in the area of the operators. All hardware used in the rest of the system must be UL listed. A UL 1981 compliant OnGuard system must use the UL Certified Bosch D6600 or D6100 Receiver either by using a direct serial connection, or an Ethernet IP connection using the approved Lantronix SDS1100 units (refer to the OnGuard Hardware Installation Guide for SDS1100 installation details). It is also allowable to receive signals from other UL294/1076-complaint hardware directly to the PC (not through the D6600 or D6100) as long as the UL 1981 alarms have priority over alarms from other devices. Following this guideline will not adversely affect the system s the UL 1981 compliance. In the event of an unexpected failure with the server or network, OnGuard and the Bosch D6600 or D6100 receiver must act as a watchdog timer. For this reason, to be in accordance with UL 1981 standards, the Bosch D6600 or D6100 receiver must physically be located in the same area as the operators. An unexpected failure can be defined as a loss of network communication between the receiver and the server. In the event of a failure, refer to the backup procedure in the UL 1981 operations manual. Note: When setting up the Bosch D6600 or D6100 Receiver, program the receiver with a Retry Number configuration of 0. Refer to the Bosch Conettix D6600/D6100i Program Entry Guide for more information. Conventions Used in this Documentation The text in this documentation is formatted to make it easy for you to identify what is being described. Where a term is defined, the word is represented in italics. Field names are shown in bold. Menus and menu choices are shown in bold italics. All menu choices have accelerator keys, which enable you to select the menu choices using the keyboard. The underlined letter represents the accelerator key for that menu item. Accelerator keys are written, for example, <Alt>, <C>. Keyboard keys are represented in angle brackets. For example: <Tab>, <Ctrl>. Keyboard key combinations are written in two ways: <Ctrl> + <Z> means hold down the first key and press the second <Alt>, <C> means press the first key, then press the second Buttons on the screen are represented in square brackets; for example: [Modify], [Cancel]. 6 UL 1981 Compliance Option Setup and User Guide

7 CHAPTER 2 Configuring OnGuard for UL 1981 Compliance Configuring OnGuard to comply with the UL 1981 standard involves creating UL 1981 users, configuring UL security levels, configuring receiver accounts, alarm priorities, database backups, configuring runaway systems and configuring audible alarms. If OnGuard Database Setup is run on a new installation when a UL 1981 license is installed, the database is populated with UL users (OnGuard Users), UL security levels (OnGuard Permission groups), and UL Reports. IMPORTANT: UL 1981 OnGuard installations must be on redundant servers. Standby System UL 1981 compliance requires that a secondary computer must also be present and powered up in the same location as the receiver. This secondary computer must be an exact duplicate of the primary computer with the same IP address and name configured. This will allow the secondary computer to be used in case the primary machine failed in no less than six minutes as noted by the UL 1981 standard. In the event of a primary computer failure, you must stay within a 6 minute window and complete the following. The RS-232 cable connected to the receiver must be switched over, the PC must be powered up and functional, and the network must be active. The database must also be backed up within a 24 hour time frame in the event that the primary fails. It is suggested that the backup reside on the standby computer but if not there must be a regular backup plan in place such as a zip drive or CD/DVD. Optimally, the backup should be sent directly to the secondary computer. Figure 1 on page 8 and Figure 2 on page 8 show hardware redundant system configurations, consisting of OnGuard version 6.1.xxx and later Alarm Monitoring Automation Systems that include: Microsoft Server 2005 or 2008 or later Client workstations running Windows XP or Windows 7 ExpressCluster X Redundant Server Software UL 1981 Compliance Option Setup and User Guide 7

8 FIGURE 1. UL 1981 Redundant System Network Diagram with Ethernet Connection to Bosch Receiver All LAN network connections 10/100/1000BASE-T MS Server, SQL and OnGuard Redundant Servers Switch Lantronix SDS1100 Ethernet Bosch Model D6600 or D6100 DACR/IP Serial Client Workstations FIGURE 2. UL 1981 Redundant System Network Diagram with Serial Connection to Bosch Receiver All LAN network connections 10/100/1000BASE-T MS Server, SQL and OnGuard Redundant Servers Switch Serial Client Workstations Bosch Model D6600 or D6100 DACR/IP Database Backup and Restoration UL 1981 compliance requires that daily back-up copies (within a 24-hour time period) of the system database must be created for restoring purposes. The most recent back-up should be kept on-site in the event that problems occur with the system. An exception to the daily back-up does exist. For those systems that serve not more than 1000 active alarm system or not more than 5000 inactive alarm systems need to be backed up a minimum of once a month. IMPORTANT: Archives of the database should not be deleted and must be retained for a period of one year. 8 UL 1981 Compliance Option Setup and User Guide

9 UL 1981 Security Levels Configure Database Backup and Restoration For more information, refer to Chapter 4: Database Backup and Restoration on page 21. UL 1981 Security Levels There are four security levels defined by the UL 1981 standard that contain permissions for different operators of the OnGuard software. Only users with these security levels are allowed to handle alarm signals in a UL 1981 installation. The four security levels are predefined in the OnGuard UL 1981 database and are as follows: UL Level 1 System. Shall permit acknowledgment of operator actions in response to signals received from alarm systems. It shall also permit printing or electronic copying of alarm system records. This level shall not affect the ability of the automation system to perform its alarm system monitoring functions. UL Level 2 System. Shall permit temporary (24 hours maximum) suspension of the automation system's designated activity for specific functions of an alarm system. The preprogrammed condition shall automatically be restored within a predetermined time of change of function. Suspension may be repeated at the discretion of the central-station staff with this security level. UL Level 3 System. Shall permit permanent record changes to the automation system's alarm system data base such as adding, deleting, or suspending accounts for longer than 24 hours. UL Level 4 System. Shall provide the ability to change central-station operator IDs, or changes to time and date. The user shall not be able to change the time and/or date of change-of-status signals that are received and processed, including dispatch, arrival, and similar information. UL 1981 Compliance Option Setup and User Guide 9

10 UL 1981 User UL 1981 compliant OnGuard users are created much in the same way as regular OnGuard users except that they are flagged as being UL 1981 users on the Users folder and are assigned one of the UL 1981 security levels. IMPORTANT: To be UL 1981 Compliant one UL 1981 OnGuard user must be logged into the system at all times. The last user to log out of the system will receive a message warning them they are the last user. Create a UL 1981 User 1. In System Administration, select from the Administration > Users. 2. On the Users form, click [Add]. 3. On the General sub-tab, enter the user s first and last name, and then select the UL 1981 user check box. 4. Click the Internal Account sub-tab. 5. Enter the User name and Password, and then confirm the password. 6. Click [OK]. Notes: The password must contain at least six alphanumeric characters and cannot be the same as the user name. UL 1981 requires that users renew their passwords at least every 90 days. The system notifies users who have permission to change their passwords when the passwords will expire, and then gives them the option to change the password themselves. The system also notifies users who do not have permission to change their passwords when their passwords have expired, and that they must contact the System Administator to have their accounts re-activated. The ability for users to change their own passwords is configured in System Administration by selecting Administration > Users, and then selecting the System Permission Groups tab. Expand Software options, and then turn on or off the View/ Access permissions for Change password. 7. On the Users form, select the Permission Groups sub-tab. 8. Choose a UL 1981 security level. For more information, refer to UL 1981 Security Levels on page 9. Receiver Accounts Receiver accounts are used to represent panels in a receiver setup. While a receiver must be configured, receiver accounts (panels) can be added optionally. Because the receiver is between the receiver account and the access control software, there needs to be some way to represent which receiver account an event originated from. To solve this problem, an account number is entered in the receiver account, and that number is reported to the access control software. When an event occurs for an account, Alarm Monitoring is provided with a name and other information to display. For receiver accounts that are not entered in the database initially, the access control software will automatically add them with the account number as the default name. You can then go back later and change the name. 10 UL 1981 Compliance Option Setup and User Guide

11 Receiver Accounts Configure the Receiver Accounts Form 1. In System Administration, from the Additional Hardware menu, select Receivers. 2. Click the Receiver Accounts tab. 3. Click [Add]. 4. If segmentation is not enabled, skip this step. If segmentation is enabled: a. The Segment Membership window will open. Select the segment that this receiver account will be assigned to. b. Click [OK]. 5. In the Name field, type a name for the receiver account. 6. In the Account number field, type the account number as reported from the receiver. Each receiver has a unique account number. 7. On the Details sub-tab, fill in any options associated with the receiver account. No options are required, but you can enter the Phone number, Address, City, State, Zip code, and any Additional comments. 8. On the Options sub-tab: Note: a. You can select an Assigned template. An assigned template is used to specify custom mappings for event codes reported from the receiver for the given receiver account to access control system event definitions. If an assigned template is not selected, the access control system will use a default template. b. You can also select if an event is expected to occur. If an event is expected, enter the number of Hours and Minutes that the event will go on for. c. Select the Account group that the receiver account will belong to, if any. Receiver Account Groups are added on the Receiver Account Groups form in the Receivers folder. If segmentation is enabled, the Receiver Account Group must be in the same segment as the Receiver in order to be available for selection in the Account group drop-down list. 9. On the UL Account Details tab: UL 1981 Compliance Option Setup and User Guide 11

12 Note: a. In order to comply, the Account types for UL accounts must have the UL Fire and/or UL Burglary selection enabled here. The OnGuard alarm report cannot define a UL account that has UL Burglary and also non-ul certificated signals (such as Fire signals) when these signals share the same account number. One solution is to have alarm inputs not intended to be on a UL certificate (for example, UL2050 certificated burglary and fire alarm zones from the same receiver account) sent to separate control panels, or partition these signals onto different areas (accounts) of the control panel for non-ul alarm signals. This will allow filtering of the alarm report for certificated systems. b. Use the Receiver drop-down box to select the receiver that the receiver account will report events to. c. Select the Account active field if the receiver account will regularly report open or close events. Leave it unchecked if it will not. d. Select the Central Station holds key field if physical keys are kept on premises of the central station. e. In the Designated response time, specify the amount of time the user has to respond after being dispatched. f. Use the Line security drop-down box to select the type of line security that the receiver account will use. g. Use the Mask open/mask events during timezone drop-down box to select the timezone masking options. This will determine when the receiver mask events. 10. Click [OK]. UL 1981 Compliant Alarms UL 1981 requires that all signal events be acknowledged and have responses noted, except for routine arming/disarming signals within the time profile. UL 1981 requires that there be audible signals accompany alarms. You can use any audio you wish to accomplish this. Alarms must also be configured in a certain priority level. The following alarm types must be configured from highest priority to lowest and are listed below in descending order of priority: Fire alarm - highest priority. Hold-up or panic alarm Medical alarm Industrial supervision if a danger can result Burglar alarm Other - lowest priority. Notes: Both alarm and restoral signals shall be recorded. Hold-up, medical, and industrial alarm types are not prohibited from having equal priority. Configure Alarms to be UL 1981 Compliant 1. In System Administration, from the Monitoring menu select Alarms. 12 UL 1981 Compliance Option Setup and User Guide

13 UL 1981 Compliant Alarms 2. On the Alarm Definitions tab, select the alarm you wish to modify from the Alarm listing window. Click [Modify]. 3. To be UL 1981 compliant, alarms must be acknowledged and must have a response noted. On the Alarm Definitions screen, make sure that the Must acknowledge and the Must enter response on acknowledge check boxes are selected for all alarms generated by connected devices. 4. Click [OK]. 5. Assign the Supplemental Alarm event to all alarms in the alarm priority list except for the Fire alarm. a. Selecting one of the following alarms: Burglary Supervisory alarm Hold-up or panic alarm Medical alarm Industrial supervision alarm Burglar alarm Other alarm. b. Click [Modify] c. Selecting Supplemental Alarm event from the Event listing window. 6. Click [OK]. 7. Repeat steps 5-6 until all alarms in the list are linked to the Supplemental Alarm event. Configure Alarm Priorities 1. In System Administration, from the Monitoring menu select Alarms. 2. On the Alarm Definitions tab, click [Add]. 3. To be UL 1981 compliant, alarms must be acknowledged and must have a response noted. On the Alarm Definitions screen, make sure that the Must acknowledge and the Must enter response on acknowledge check boxes are selected. 4. In the Priority field, type a number that s in the range of 0 through 255. Remember that this number specifies the minimum in range that s limited by the next higher color. 5. Click the [Select] button next to the Assigned Color display. 6. On the Color form, do one of the following: a. Select one of the Basic Colors by clicking on it b. Click [Define Custom Colors >>] to expand the window. Then: click on the color palette to select a precise color, or specify the color by entering red, green, blue, hue, saturation, and luminance values 7. Click [OK] to close the Color form. The selected color will be displayed in the Assigned Color field. 8. Click the [Select] button next to the Acknowledged Color display, then repeat step Click [OK] to close the Color form. The selected color will be displayed in the Acknowledged Color field. 10. Click [OK]. Enable Audio Alarms 1. In System Administration, from the Monitoring menu select Alarms. 2. On the Audio tab, click [Add]. UL 1981 Compliance Option Setup and User Guide 13

14 3. In the Name field, type a unique, descriptive name for this audio clip record. 4. Specify whether this clip is to be used for Instruction or Notification. 5. Do one of the following: a. Use the [Browse] button to import an existing audio file b. Use the following buttons to create your own audio clip from within the application (your computer must be equipped to record audio): [Record] starts recording the audio clip [Play] plays the audio clip [Stop] stops the audio clip recording or playback operation [Rewind] rewinds the audio clip to its beginning 6. Click [OK]. 7. On the Alarm Configuration tab, select the alarm you wish to add audio to. 8. Click [Modify]. 9. Use the Audio instruction or Audio notification drop-down boxes to add the audio that was created. 14 UL 1981 Compliance Option Setup and User Guide

15 CHAPTER 3 Operator Instructions for OnGuard UL 1981 Users UL 1981 users in OnGuard are dedicated to handling signals that come through Alarm Monitoring. The following sections reflect the procedures for UL 1981 OnGuard users. Alarm Audit Trail Acknowledging alarms allows you to create an alarm audit trail by updating the notes with continual information and noting dispatch and arrival times of the operator. The definition of the alarm states acknowledged and in progress differ between the UL standard and Lenel. In the OnGuard software and in this documentation acknowledged refers to an alarm that has been resolved and in progress refers to an alarm that has been noted but has not been fully resolved and still requires attention. Acknowledge Alarms IMPORTANT: To be UL 1981 compliant an alarm must be marked in progress or be acknowledged before it is deleted. However, the signal can be deleted without executing alarm handling procedures. In this case, the event must first be acknowledged first and given a resolution as to reason for deletion 1. Display the Alarm Acknowledgment window by double-clicking an alarm in Alarm Monitoring. 2. If the alarm has text instructions associated with it the information displays in the Instructions sub-window. Click [Print] to print the instructions. 3. If the alarm has voice instructions click [Audio]. 4. To select pre-configured acknowledgment note(s) click [Select]. The Select Acknowledgment Notes dialog appears. Select the name of the pre-configured note and click [OK]. 5. To add notes to the alarm, type your comments and click in the Notes sub-window. If this is a canceling alarm, any notes carried forward from the associated initiating alarm gets displayed in the Original Notes field. This report shall include the following items in the Notes field, as applicable: **** The name and address of the subscriber (fire/burglar); UL 1981 Compliance Option Setup and User Guide 15

16 * The type of alarm (burglary, hold-up, fire); **** The designated response time (burglar); **** Whether there is standard or encrypted line security. When provided, it shall be indicated; * The time the alarm was received by the automation system (fire/burglar) *** The time the police/fire department was notified, and the police/fire department identification number (fire/burglar); *** The time the alarm investigator No. 1 was dispatched, and the investigator s name and employee ID (fire/burglar); *** The time the alarm investigator No. 2 (if any) was dispatched, and the investigator s name and employee ID (burglar); *** The time the alarm investigator No. 1 arrived (fire/burglar); *** The time the alarm investigator No. 2 arrived (if dispatched) (burglar); **** The elapsed time between the receipt of the alarm signal at the central-station automation system and the investigator s arrival at the protected premises; ** The method used to verify the alarm investigator s arrival such as radio, telephone, or other means (fire/burglar); **** Whether the central-station holds keys; ** Whether the keys were used or not used (fire/burglar); *** The time the subscriber was notified, the name of the notified subscriber (2 or 3 lines might be required for multiple notifications) (burglar/fire); ** The disposition of the alarm (fire/burglar); and ** Whether a sounding device is provided on the alarm system (optional). *Automatically entered. **Must be manually entered per event. ***Manual data entry with automatic timestamp. ****Automatically added based on previous user entered data. 6. On the occasion where an operator is dispatched to an alarm: a. When an operator is dispatched to the site of the alarm, click [Dispatch] and add additional notes. b. When an operator who is dispatched arrives at the alarm, click [Arrive] and add any additional notes you may have. Note: If your System Administrator has configured the alarm to be marked in progress before being acknowledged continue to step 7. If not, move on to step If you are unable to acknowledge an alarm click [In Progress]. This marks the alarm as being in progress and acts as a state in between an unacknowledged and acknowledged alarm. 8. When an alarm is marked In Progress you are able to update the notes by clicking [Update]. Each update is time stamped with the date and time. 9. Click [Acknowledge] to acknowledge the alarm. If your System Administrator has configured this alarm type for Require Login On Ack. you must first log in before this alarm can be acknowledged. If this is an initiating alarm, the corresponding canceling alarm may not be displayed until you acknowledge this alarm. Whether this happens depends upon how your system is set up. 16 UL 1981 Compliance Option Setup and User Guide

17 UL 1981 Reports Your System Administrator may have set up some types of alarms to be automatically deleted from the Main Alarm Monitoring window after you acknowledge them. If this is not the case, delete the alarm manually. 10. You can acknowledge multiple alarms without closing the Alarm Acknowledgment window. Repeat step 2 through 9 for each alarm you display in the Alarm Acknowledgment window. Use the navigation buttons to move through the list of alarms. 11. To close the Alarm Acknowledgment window, click [Close]. Show or Hide Events Marked In Progress 1. In Alarm Monitoring, select Options and select Show Alarms Marked in Progress. 2. Selecting this option will show all alarms that are marked in progress. Deselecting this option will hide all alarms that are marked in progress. UL 1981 Reports UL 1981 reports must be stored for a minimum of one year to be compliant with UL 1981 standards. Run a UL 1981 Report 1. In System Administration, from the Administration menu, select Reports. 2. Select the UL 1981 tab. 3. On the Date/Time sub-tab, specify a date/time interval for gathering data. Only data gathered during the specified period will be included in the report. To limit each date in the range to the specified time interval, select the Apply start and end time to each day check box. 4. On the Receiver Account sub-tab, select which receiver account the report will be gathered for. 5. On the Receiver Account Attributes sub-tab, configure the information as you see fit. 6. The filters required for UL 1981 compliancy are located on the Receiver Account Attributes tab. Those filters are UL Fire and UL Burglary. This filter will match the type of report generated. Those events are generated by accounts configured as UL accounts as outlined in step 9 of Configure the Receiver Accounts Form on page Click [Preview] to preview the report. To print a report, refer to Print a Report on page 18. Run an Event Report 1. Select Reports from the Administration menu. The Reports folder opens. 2. Select the Event Reports tab. 3. In the reports listing window, select the icon that corresponds to the report you wish to run. 4. Complete the Date/Time Filter section to specify a date/time interval for gathering data. Only data gathered during the specified period will be included in the report. To limit each date in the range to the specified time interval, select the Apply start and end time to each day check box. 5. In the Access Panel Filter section, select the icon(s) corresponding to the panel(s) whose data you wish to include in the report. If you don t select any panels, or click [Report All], data for all panels will be reported. 6. In the Event Filter section, select an Event Type. 7. In the Event listing window, select the icon(s) corresponding to the event(s) whose data you wish to include in the report. UL 1981 Compliance Option Setup and User Guide 17

18 If you select <All> in the Event Type field, data for all events will be reported. If you click [Report All], data for all events of the selected Event Type will be reported. 8. Click either the [Print] or [Preview] button depending on which function you wish to perform. Note: Only data that s currently in the database can be included in the report. Events or other transactions deleted because of space limitations or elapsed time are no longer available. Run an Alarm Resolution Report 1. Select Reports from the Administration menu. The Reports folder opens. 2. Select the Alarm Acknowledgment Reports tab. 3. In the listing window, select the report you wish to run. 4. Complete the Date/Time Filter section to specify a date/time interval for gathering data. Only data gathered during the specified period will be included in the report. To limit each date in the range to the specified time interval, select the Apply start and end time to each day check box. 5. In the Filter by drop-down list, select the device whose data you wish to include in the report. If you don t select any device, or if you click [Report All], data for every device will be reported. 6. In the Filter listing window, select the device(s) whose data you wish to include in the report. 7. Click either the [Print] or [Preview] button depending on which function you wish to perform. Note: Only data that s currently in the database can be included in the report. Events or other transactions deleted because of space limitations or elapsed time are no longer available. Report Accounts by Type and Designated Response Time 1. In System Administration, from the Administration menu select Reports. 2. On the UL 1981 tab, select the Receiver Account Attributes sub-tab. 3. In the Account types listing window, select the account types that you wish to report. 4. Select the Burglary alarm designated response time to the amount that you wish. 5. Configure the other sub-tabs as you see fit. 6. Click [Print] to print the report or [Preview] to preview the report. View Active and Inactive Accounts 1. In System Administration, from the Administration menu select Reports. 2. On the UL 1981 tab, select the Receiver Account report from the Report listing window. 3. Click [Preview]. The section and report footers of the report will show the number of active and inactive accounts. Print a Report 1. In System Administration, from the Administration menu select Reports. 2. Select the report that you wish to print from the report listing window. 3. Click [Print]. The Print Report Options window opens. 4. In the Print Destination section, select whether to print to a preview window, export directly to a file or print directly to a printer. 5. If you selected Print Directly to a Printer in the Print Destination section, select a printer in the drop-down list and choose whether to Prompt for Number of Pages. 18 UL 1981 Compliance Option Setup and User Guide

19 Runaway System Note: If the Linkage Server is running under a local system account it may not have permission to access a network printer (depending on its configuration). If this is the case you must select a local or default network printer. Contact your System Administrator to determine what account the Linkage Server is running under and the printers it can access. 6. In the Report Subtitle section, type the report subtitle. The subtitle will be displayed below the report title on the report. 7. Click [OK]. The options selected in the Print Destination section will determine where the report is sent. Runaway System An alarm system is considered runaway when the alarm system receives a greater number of signals than the system is programmed to received within a set amount of time. For example, an alarm system may define a runaway system as one that transmits more than 20 signals of the same type within 30 minutes. If a runaway system occurs a Runaway System alarm will be generated for the receiver account it is connected to. An Indefinite Suspension Initiated alarm will also be generated indicating that the receiver account has been suspended. A user has to restore the receiver account before it can receive more alarms. Configure Automatic Runaway System Suspension 1. In System Administration, from the Administration menu select System Options. 2. On the General System Options form, click [Modify]. 3. Configure the Runaway system detection fields by configuring how many events in how many seconds signify a runaway system. 4. Click [OK]. Suspend and Restore an Account IMPORTANT: In order to manually suspend or restore accounts a user must have the Suspend receiver accounts and Restore receiver accounts permissions enabled. These permissions can be configured by navigating, in System Administration, to Administration > Users > Monitor Permission Groups > Control. 1. In Alarm Monitoring, right-click the receiver account. 2. In the right-click menu, select: a. Suspend - There are two types of suspension: Temporary - Temporary suspension allows the user to specify how long to suspend event reporting for the Receiver account. The allowed range of values for this are from 1 to 24 hours. When this option is selected a Temporary Suspension Initiated alarm will be generated. If you later decides to restore the temporary suspension then a Suspended Account Manual Restore alarm is generated. If the temporary suspension expires without the user restoring it a different Temporary Suspension Expired alarm is generated. UL 1981 Compliance Option Setup and User Guide 19

20 Indefinite - If selected, an Indefinite Suspension Initiated alarm is generated. If the user later decides to restore the indefinite suspension then a Suspended Account Manual Restore alarm is generated. b. Restore - Restores the receiver account and allows it to accept alarms. 3. The account is now suspended or restored. Repeat the process for any additional accounts. 20 UL 1981 Compliance Option Setup and User Guide

21 CHAPTER 4 Database Backup and Restoration You can back up your database using any of the following methods: Backing up to a file on a hard drive or network connection. Backing up to a tape drive. Backing up to a CD or DVD. The chapter also deals with how to restore the backup if needed. The procedures are broken into sections based on the backup option and the type of database you are using. Consult your Database Administrator for the preferred backup method. Note: Some of the procedures in this chapter require the use of SQL Server Management Studio. If have SQL Server 2008 Express Edition and you do not have the SQL Server Management Studio Express application, you can install the application from the Supplemental Materials disc. Backing Up Your Database to File This section includes information on how to: Back Up to a File on SQL Server 2008 Database on page 21 Back Up to a File on SQL Server Express Edition on page 23 Back Up to a File on SQL Server 2008 Database The following section will show you how to back up your SQL Server database to a file. Configure Microsoft SQL Server for Automatic Database Backup to a File 1. Click the Windows Start button, then select All Programs > Microsoft SQL Server 2008 > SQL Server Management Studio. 2. Log into SQL Server Management Studio. 3. Navigate to the SQL Server Agent in the Object Explorer. a. Right-click the SQL Server Agent and select Start. UL 1981 Compliance Option Setup and User Guide 21

22 b. You will be asked whether you are sure that you want to start the service, click [Yes]. c. Right-click the SQL Server Agent and select Properties. 4. The SQL Server Agent Properties window is displayed. a. Select the Auto restart SQL Server if it stops unexpectedly and Auto restart SQL Server Agent if it stops unexpectedly check boxes. b. Click [OK]. 5. Expand the Management folder in the Object Explorer. 6. Right-click on the Maintenance Plans folder and select Maintenance Plan Wizard. 7. The SQL Server Maintenance Plan Wizard is displayed. Click [Next]. 8. On the Select Plan Properties window: a. In the Name field, enter a name for the maintenance plan. b. Click [Change]. 9. The Job Schedule Properties window is displayed. a. For Name, enter a name for the schedule. b. Set the frequency for the backup to occur. c. Click [OK]. d. Click [Next] in the Select Plan Properties window. 10. On the Select Maintenance Tasks window, select the Back Up Database (Full) check box. Click [Next]. 11. On the Select Maintenance Task Order window, click [Next]. 12. In the Define Back Up Database (Full) Task window, click the Databases drop-down. 13. In the Databases drop-down popup: a. Select the check box for the OnGuard database. b. Click [OK]. 14. In the Define Back Up Database (Full) Task window: a. Select the Back up databases across one or more files radio button. b. From the If backup files exist drop-down, select Overwrite. c. Click [Add]. 15. In the Select Backup Destination window, click [...]. 16. In the Locate Database Files window: a. Enter a file location and name for the backup in the File name field. b. Click [OK] in the Select Backup Destination window. c. Click [Next] in the Define Back Up Database (Full) Task window. 17. On the Select Report Options window, click [Next]. 18. On the Complete the Wizard window, click [Finish]. 19. Once the Maintenance Plan Wizard Progress has completed, click [Close]. 20. In the Administrative Tools section of Control Panel, open Services. Right-click the SQL Server Agent (MSSQLSERVER) service and select Properties. 21. The SQL Server Agent (MSSQLSERVER) Properties window is displayed. a. In the Startup type drop-down, select Automatic. b. Click [OK]. 22 UL 1981 Compliance Option Setup and User Guide

23 Backing Up to CD/DVD Back Up to a File on SQL Server Express Edition 1. Click Start, then select All Programs > OnGuard 2012 > Service and Support > Database Backup. 2. The Database Backup window displays. Click [Connect] and connect to the AccessControl database. 3. Verify the Backup radio button is selected in the Database operation section. 4. Select the File radio button in the To/From section and click [Browse] and navigate to the directory or network connection you would like to save the backup file to. 5. Enter a name for the file and click [Save]. 6. Verify the Overwrite backup set radio button is selected and click [Run]. 7. Click [OK] after the database is successfully backed up. 8. Exit the Database Backup application. Backing Up to CD/DVD The process of backing up to CD/DVD is the same for SQL Server Standard and Express Editions. You can use other CD/DVD burning programs but you must consult their specific documentation on how to do so. To back up your database to CD or DVD using Windows, follow these steps: 1. Back up your database to a file. For more information, refer to Backing Up Your Database to File on page Right-click on the file(s) to be backed up and click [Send to]. Choose the CD or DVD writable drive on your computer. 3. You receive a message that files are waiting to be backed up. 4. Click on the My Computer icon on your desktop and double-click the CD or DVD drive that you saved the files to. You should see the files you want to burn. 5. Make sure the proper media is in the drive and click File in the menu bar and select Write these files to CD/DVD. 6. The CD/DVD writing wizard opens. Follow the on screen instructions to burn your files to CD/ DVD. When the CD or DVD is written, store it in a safe location. You will need the files saved on the disc to restore the database if something ever happens to it. You should back up your database as often as you can. Backing Up to Tape This section includes: Back Up to Tape on SQL Server Database on page 24 Back Up to Tape on SQL Server 2008 Express Edition on page 25 Verify that the Backup (to Tape) is Set Up Correctly on page 25 UL 1981 Compliance Option Setup and User Guide 23

24 Back Up to Tape on SQL Server Database Before conducting the backup, make sure that there is a tape in the drive that is labeled and is of a supported media format for the drive that you are using. 1. Start the Windows Backup software. To do this: In Windows XP and Windows Server 2003, click the Start button, and then navigate to All Programs > Accessories > System Tools > Backup. In Windows 7 or Windows Server 2008 R2 open Control Panel and open the Backup and Restore Center. In Windows Server 2008, open Control Panel and navigate to Admin Tools > Windows Server Backup. 2. If the Wizard starts, click the Advanced Mode link. 3. Click the Backup tab. 4. Navigate to the file that you want to back up. 5. In the Backup media or file name drop-down, select Accesscontrol Backup. 6. Select Travan in the Backup destination drop-down. a. Click [Start Backup]. b. The Backup Job Information window opens. c. In the Backup description field, type Accesscontrol Backup. d. In the If the media is overwritten, use the label to identify the media field, type Accesscontrol Backup. e. Click [Schedule]. 7. A message is displayed. Click [Yes] to save the backup selections now. 8. The Save Selections window opens. a. Specify a name and location for the backup. The recommended filename is AccessControl.bks, and that file can be saved in the C:\ root directory. b. Click [Save]. 9. The Set Account Information window opens. a. In the Password field, type admin. b. In the Confirm password field, retype the password. c. Click [OK]. 10. The Scheduled Job Options window opens. a. In the Job name field, type a descriptive name for the job. b. Click [Properties]. 11. The Properties are displayed in the Schedule Job window. a. In the Schedule task drop-down, select Daily. b. In the Start time field, select a time that is 30 minutes later than the time that the SQL backup job is set to start. For example, if the SQL backup job is set to start at 1:00 am, then the start time should be 1:30 am. c. Verify that 1 is selected in the Schedule Task Daily section. d. Click [OK]. 12. In the Schedule Job window, click [OK]. 13. Click the Schedule Jobs tab and verify that the calendar is full of scheduled jobs. 24 UL 1981 Compliance Option Setup and User Guide

25 Backing Up to Tape Verify that the Backup (to Tape) is Set Up Correctly After the backup schedule has been set up, you can run your backup immediately. You should do this rather than waiting until the first scheduled backup to occur. 1. Open Control Panel, and then double-click Scheduled Tasks. 2. Right-click on the task, and then select Run. 3. After a short delay, the backup runs. Verify that the Backup Ran 1. Start the Windows Backup software. To do this: a. In Windows XP and Windows Server 2003, click the Start button, and then navigate to All Programs > Accessories > System Tools > Backup. In Windows 7 or Windows Server 2008 R2, open Control Panel and open the Backup and Restore Center. In Windows Server 2008, open Control Panel and navigate to Admin Tools > Windows Server Backup. b. Click the Restore and Manage Media tab. c. The backup is listed. Back Up to Tape on SQL Server 2008 Express Edition If you are using SQL Server 2008 Express Edition then you cannot have your database backed up automatically. Instead, follow this procedure to back up the database manually. Note: This procedure can also be used to manually back up SQL Server 2008 databases. Before conducting the backup, make sure that there is a tape in the drive that is labeled and is of a supported media format for the drive that you are using. 1. Start the Windows Backup software. To do this: In Windows XP and Windows Server 2003, click the Start button, and then navigate to All Programs > Accessories > System Tools > Backup. In Windows 7 or Windows Server 2008 R2, open Control Panel and open the Backup and Restore Center. In Windows Server 2008, open Control Panel and navigate to Admin Tools > Windows Server Backup. 2. If the wizard starts, click the Advanced Mode link. 3. Click the Backup tab. 4. Navigate to the file that you want to back up. In most cases, this will be the accesscontrol_backup file that is in the C:\Program Files\OnGuard\database_backup directory. 5. Select Accesscontrol Backup in the Backup media or file name drop-down list. 6. Select Travan in the Backup destination drop-down. 7. Click [Start Backup]. 8. The Backup Job Information window opens. a. In the Backup description field, type Accesscontrol Backup. b. In the If the media is overwritten, use the label to identify the media field, type Accesscontrol Backup. 9. Click [Start Backup]. 10. The backup will run. The Backup Progress window displays, and the backup is complete. UL 1981 Compliance Option Setup and User Guide 25

26 Restoring Databases This section includes: Restore the Database on SQL Server 2008 on page 26 Restore the Database on SQL Server Desktop Engine on page 27 Restore the Database on SQL Server 2008 To restore a SQL Server 2008 database from a tape drive complete the following steps. If you are restoring from a file on either a network connection, CD, or DVD then skip to step Restore the database in the tape drive to a file by running the Windows Backup software. For more information, refer to Restore the Database from a Tape Drive on page 26. If you backed up to a CD or DVD then you can skip this step and go on to the next step. 2. Restore the file to the database via the SQL Server Management Studio. For more information, refer to Restore Microsoft SQL Server 2008 Database from a File on page 26. Restore the Database from a Tape Drive 1. Insert the tape that contains the database that you wish to restore into the proper drive. 2. Start the Windows Backup software. To do this: In Windows XP and Windows Server 2003, click the Start button, and then navigate to All Programs > Accessories > System Tools > Backup. In Windows 7 or Windows Server 2008 R2, open Control Panel and open the Backup and Restore Center. In Windows Server 2008, open Control Panel and navigate to Admin Tools > Windows Server Backup. 3. If the wizard starts, click the Advanced Mode link. 4. Click the Restore and Manage Media tab. 5. Select Travan, and then navigate to the database that you wish to restore. 6. Click [Start Restore]. Restore Microsoft SQL Server 2008 Database from a File 1. Click the Windows Start button, then select All Programs > Microsoft SQL Server 2008 > SQL Server Management Studio. 2. The SQL Server Management Studio window displays. a. Navigate to OnGuard database. b. Right-click on the OnGuard database and select Tasks > Restore > Database. 3. The Restore database window displays. a. For the To database and From database drop-downs, select the OnGuard database. b. Click the Options page from the Select a page list view. 4. The Options page is displayed. a. Select the Overwrite the existing database check box. b. Click [OK]. 5. A success message is displayed. Click [OK]. 26 UL 1981 Compliance Option Setup and User Guide