UNC Charlotte Facilities Management 16 July 2012 Facilities Information Systems. Building Automation Systems (BAS) Critical Alarm Standards



Similar documents
College / Admin Unit Space Auditor Training. Instructor: Ray Dinello, Director Facilities Information Systems

Managed Support Policy

NH-HMIS Disaster Recovery Plan

RSA SecurID Tokens Service Level Agreement (SLA)

Market Data Transparency Service Level Agreement

Administering Cisco ISE

[name of project] Service Level Agreement

Office of Information Technology Hosted Services Service Level Agreement FY2009

Enterprise UNIX Services - Systems Support - Extended

TSC Problem Management. Procedures

Smart Business Architecture for Midsize Networks Network Management Deployment Guide

Standard Operating Procedure-Speciation Data Processing Disaster Recovery Plan

Helpdesk and Technology Support Procedures

Service Level Agreement (SLA)

i. Maintenance of the operating system, applications, content on the server, or fault tolerant network connections

Domain Name Service Service Level Agreement (SLA) Vanderbilt Information Technology Services

Dynatrace Support Policy

Terminology page. All available site plans can be seen here:

How To Write A Service Level Agreement For The National Patient Information Reporting System

Appendix A. Customer Support Service Level Agreement

Security Access Control System Operations Manual

ManageEngine Desktop Central Training

National Patient Information Reporting System: National Data Warehouse. Service Level Agreement

UCLA Communications Technology Services

PSU Hyland OnBase Document Imaging and Workflow Services Level Memorandum of Understanding

UCLA Information Technology Services

UTCVM PHARMACY STANDARD OPERATING PROCEDURES

Monitoring Windows Event Logs

For more information, please visit the IST Service Catalog at

Grandstream Networks, Inc. How to Use Office Time and Holiday on UCM6100

ensurcloud Service Level Agreement (SLA)

The Service Provider will monitor the VM for the Customer and provide notifications on an opt in basis, which is strongly recommended.

Department of Information Technology

SUBJECT: Network Support Partnership Silver Support Level for FY 2013

CENG Information Technology Services University of North Texas

Operating Level Agreement for NYU Login Service

SupportDesk Extensions Installation Guide Extension Service - Versions

Delegated Administration Quick Start

flex support Service Overview

SPOK HEALTHCARE CONSOLE. Improving the Way Your Hospital Contact Centre Manages Critical Communications

Indiana Office of Technology (IOT) Delivery Services Enterprise Service Level Agreement (Version 7.0)

Backup Notification in Client Profiles for Windows

Eloquent Librarian Planning Guide

Systems Support - Standard

Managed Security Services Service Level Agreement Current. Managed Security Services SLA

EventTracker: Integrating Imperva SecureSphere

MANAGED FIREWALL SERVICE. Service definition

Cloud Services Catalog with Epsilon

PATROL From a Database Administrator s Perspective

NIH Web Collaboration Service-Level Description

Technical Support System

Environmental Management System

How To Manage An Ipa Print Service At A College Of Korea

SERVICE DESK ANALYST Tier II Support (Information Technology)

Installation Manual Version 8.5 (w/sql Server 2005)

APPENDIX 8 TO SCHEDULE 3.3

Unit Network Infrastructure Maintenance. Standard Service Agreement (SA)

Service Level Agreement Guide. Operations Center 5.0

Customer Support Guide Book

Template 1 - Call Center

ACDI s Professional Support Services

STATEMENT OF WORK. This Statement of Work (SOW) describes database programming and administration services defined as follows:

ENVIRONMENTAL HEALTH AND SAFETY. Fire Protection System Impairment Procedure

Service Level Agreement. Server Hosting

CJIS Online Security Awareness Training. Vendor Guide

Capacity Management PinkVERIFY

APPENDIX 8 TO SCHEDULE 3.3

ENABIL Managed Services

Optimizing Business Continuity Management with NetIQ PlateSpin Protect and AppManager. Best Practices and Reference Architecture

BACKUP SOLUTIONS FOR SCHOOLS. Advice and Guidance. ICT Services 42 New Union Street Coventry CV1 2HN

Welcome to a whole new level of interactive home security

ediscovery Implementation Services Statement of Work To be Executed under State Blanket Contract ITS53 Cat2B

MTRS 2.0 Transaction Reporting Gateway Guide

FACILITIES MANAGEMENT DEPARTMENT QUICK REFERENCE Guide to Services

Novo Knowledge Base Software

Change Submitter: The person or business requesting or filing the Request For Change (RFC) notice.

Fire Station IP Alerting System

Departmental On-Site Computing Support (DOCS) Server Support SLA

STL Microsoft Dynamics CRM Consulting and Support Services

Department of Public Utilities Customer Information System (BANNER)

PORTAL. Admin USER GUIDE

What s New Guide. Active Administrator 6.0

HEP Courses Service Service Definition

Managed Storage Service Level Agreement (SLA)

ELECTRONIC POSITIVE RESPONSE

Redundant Servers. APPolo Redundant Servers User Guide. User Guide. Revision: 1.2 Last Updated: May 2014 Service Contact:

Employee Management Certification Exam. P130 Employee Management: Basic

INCIDENT MANAGEMENT & REQUEST FULFILLMENT PROCESSES. Process Owner: Service Desk Manager. Version: v2.0. November 2014 Page 0

Exhibit to Data Center Services Service Component Provider Master Services Agreement

LANDESK Service Desk Manual Support Analyst Role

ICT Helpdesk. User Guide. 24 th May Page 1

Cloud Computing project Report

Transcription:

UNC Charlotte Facilities Management FM/FIS SOP 200A 16 July 2012 Facilities Information Systems Building Automation Systems (BAS) Critical Alarm Standards NOTICE: This standard operating procedure is available to view digitally on the Facilities Management ARCHIBUS website: http://facilities.uncc.edu/informationsystems/archibus/archibus OPR: FM/FIS (Pamela Duff) FM/FIS BAS Analyst (David Champion) FM/FIS (Ray Dinello) Pages 5, Draft # 3 I. PURPOSE. This standard operating procedure (SOP) is a user reference for the UNC Charlotte Facilities Management Division personnel. The purpose of this SOP is to establish a reference and a standard system guideline for Building Automation Systems in relation to the operation, security, monitoring, and system data update and maintenance of Building Automation alarms console and alarms contact information for UNC Charlotte Campus buildings. This SOP also establishes policy and procedure on how Facilities Management personnel, Police and Public Safety and assigned responsible personnel manage Building Automation alarm console data updates for system notifications within ARCHIBUS Web Central. II. SCOPE. Develop and implement standard operating procedures for Building Automation Systems access, alarms monitoring and maintenance for UNC Charlotte facilities. Provide processes and procedures for alarms set up, monitoring, access control and security for Building Automation Systems databases and management. Provide consolidated information and clarify processes and terminology on responsibilities and Building Automation Systems established standards. This SOP applies to all Building Automation System (BAS) personnel, Police and Public Safety, Building Alarms Contact System Administrative and UNC Charlotte Facilities Management personnel. PPS Role Name Building Alarms Contact Administrators Facilities Operations Supervisor and Manager Responsibilities Monitors and Responds to alarm notifications via alarm console during designated hours by contacting call tree individuals; documents contacted individual Update call tree contact data and provides threshold set points for building alarms notifications. Insures updated information for police monitoring and notifications Reviews, manages and responds to alarms within their assigned Zone during normal operating hours. Facilities Operations Controls Personnel Manage updates to system controls hardware Completes alarm configurations as established, provide system updates for software, database and application; sets up hardware initially, limits and maintains security access controls and provides technical and customer support as needed; Enforces security and manages who accesses BAS database; responsible for controlling access and tracking all FIS Personnel/System Admin BAS assets. BAS: Roles, Responsibilities and Descriptions Page 1 of 5

III. RESPONSIBILITIES. The UNC Charlotte Facilities Management Building Automation Analyst is responsible for maintaining database security and access to JACE infrastructure, maintaining inventory of BAS assets, and tracking and documenting changes to infrastructure. Facilities Management Zone Supervisors or assigned department personnel are primarily responsible for maintaining the alarm notifications information, processes, and ensuring alarm responses are handled efficiently and that any system problems are reported as needed. Police and Public Safety operators are responsible for notifications of alarms utilizing the contacts call tree provided during established monitoring timeframes (afterhours, weekends and holidays). UNC Charlotte Facilities Management Facilities Information Systems personnel in coordination with the various UNC Charlotte departments and in accordance with UNC Charlotte Policy Statement 102: Data and Information Access and Security are responsible for safeguarding and maintaining all data within the BAS system. IV. ALARMS CONSOLE PROCEDURES: 1. Call Tree Notifications: A primary and secondary contact will be established for each building. 1.1. The Call tree will list operational information on who will be contacted. Three contacts will be provided for Facilities Management personnel and three for the department associated to the specific alarm. 1.2. The call tree for each alarm will indicate contact name and phone numbers. 1.3. Each alarm will indicate responsibility parties to be contacted: department, Facilities Management or Both. 1.4. An email notification will be sent to all contacts when the alarm is generated. 2. Adding and Updating Contacts to BAS Alarms Contact Module: Assigned personnel will access to update their building alarms contacts information to insure that accurate information is maintained for alarm contacts and responses. 2.1. When individuals are added automatic to an alarm call tree, they will be sent an email notification. 2.2. A link to the general basic instructions concerning alarms and responsibilities will be provided. 2.3. All Facilities Management personnel contact information is defaulted in the system for alarms requiring response. V. ALARMS MONITORING RESPONSIBILITIES 1. Normal Operating Hours: During Normal Operating Hours the Zone personnel will monitor alarms. 1.1. ZONE personnel: During normal operational hours, the Zone Manager and Shop Supervisor, as back up, along with the Director of Facilities Operations will be the main point of contact for outages and to communicate to others when problems affect buildings. 1.2. FIS and the Controls Shop will manage alarm systems interface, databases and notifications related to alarms. 1.3. Facilities Management Maintenance and Operations Supervisor or Administrative Assistant will notify all campus building liaisons of all scheduled or unexpected outages. Page 2 of 5

2. After Hours Notifications Procedures: Police will monitor the Alarm Console outside of normal operations hours. 2.1. Afterhours, Monday through Friday, from 4:30 PM each evening to 7:00 AM in the morning, and during weekends, and holidays, etc. 2.2. A 30-minute leeway will occur for alarm monitoring. A sound file will inform at the beginning of the monitoring timeframe and at the end of the monitoring period. 2.3. Notifications will occur/display on the alarm console screen; however, the alarms will only be audible during the monitoring timeframe. 2.4. When an alarm is generated, the PPS operator will indicate calls made for the alarm utilizing the call tree information provided for that alarm. The PPS operator may add comments and indicate any additional information as needed for the alarm. 2.5. An Alarm Watch with a date and time schedule will be established for holidays and weekend monitoring 2.6. The schedule will indicate responsibilities for each role. 3. Alarm Notification Protocol: 3.1. If no response to the alarms within specified period (determined by alarm thresholds), the Facilities Operations Director, Area Manager, the Supervisor/on-call person will be notified. 3.2. Alarms that are indicated as department responsibility will indicate department contacts for police contacts; however, FM will be in a standby mode but the department will be responsible for any needed contacts/response 3.3. Alarm notification contact audits will occur periodically to insure that all call tree data is accurate. 4. Alarm Notification Reports: 4.1. Reports will allow police and public safety to review all alarms acknowledged. 4.2. A log file will document notes and responses. 4.3. Alarm Contacts report provides building contact information and alarms data to be available as needed. Page 3 of 5

Appendix A: After Hours (Nights, Weekends, Holidays) Alarm Notifications Work Flow Page 4 of 5

Appendix B: Work Hours Alarm Workflow Page 5 of 5