Emergency Operations Plan
University Information Technology Services
Emergency Operations Plan
Prepared by Victor Font UITS Business Continuity / Disaster Recovery Coordinator January 2013
Emergency Operations Plan
Table of Contents
Executive Summary ................................................................................................................................................. 3 UConn’s Emergency Support Functions ......................................................................................................... 3 UITS Emergency Operations Plan ..................................................................................................................... 4 Plan Activation ....................................................................................................................................................................... 4 Area Lead Roles and Responsibilities .......................................................................................................................... 4 Transfer of Leadership Duties ......................................................................................................................................... 5 Personnel Welfare ................................................................................................................................................................ 6 Defining Emergency Services (“Essential”) Personnel .......................................................................................... 6 UITS as a Utility – Support Services ........................................................................................................................ 7 UITS – Service Center ..................................................................................................................................................... 7 Defining Closing ............................................................................................................................................................... 7 Guidance to Emergency and Non-‐Emergency Personnel .............................................................................. 7 Equipment Loan Program ................................................................................................................................................. 8 Critical Infrastructure Protection Plan ........................................................................................................................ 9 Appendix A—Emergency Support Function Responsibilities ........................................................... 10 Appendix B—EOP Checklists ........................................................................................................................... 11 Area Lead Role Assignments ......................................................................................................................................... 11 Emergency Personnel Assignment ............................................................................................................................. 12 Logistics Checklist ............................................................................................................................................................. 14 Operations Checklist ........................................................................................................................................................ 15 Finance Checklist ............................................................................................................................................................... 15 Help Desk Checklist .......................................................................................................................................................... 15 Communications Checklist ............................................................................................................................................ 16 Appendix C—UITS Personnel .......................................................................................................................... 17 Document Change History ................................................................................................................................. 23
2
Emergency Operations Plan
Executive Summary This document provides guidelines for conducting emergency operations within UITS in the event a situation occurs whereby University leadership activates the Emergency Operations Center (EOC) in the Department of Public Safety. UConn’s EOC functions in accordance with the State of Connecticut’s State Response Framework1 (SRF). The Connecticut Department of Emergency Services and Public Protection (DESPP) and Division of Emergency Management and Homeland Security (DEMHS) in partnership with other CT State Agencies and Non-Governmental Organizations involved in emergency preparedness and response activities developed the SRF in accordance with the National Incident Management System (NIMS) and in compliance with Section 28-5(b) of the Connecticut General Statutes which reads in part: “The commissioner shall direct the preparation of a comprehensive plan and program for the civil preparedness of the state… …all government agencies, state or local, and all civil preparedness forces in the state shall carry out the duties and functions assigned by the plan and program as approved…” The SRF describes the interaction of state government with local, federal and tribal governments, nongovernmental response organizations and other private sector partners, the media, and the public in implementing emergency response and recovery functions in times of crisis. In general, the SRF describes how the State of Connecticut and its partners will work together to support local governments and their residents in responding to disasters and emergencies. The SRF imposes responsibilities on the Department of Higher Education (DHE) that include but may not be limited to: •
Coordinating shelter, mass feeding, non-surgical medical care, and temporary housing at state colleges, regional community colleges, and the University of Connecticut depending upon student populations.
UConn’s Emergency Support Functions To meet the requirements of the SRF, UConn’s Department of Public Safety has prioritized the University’s emergency support functions and designated each unit’s primary responsibilities, actions required during operational periods, deactivation, and recovery expectations. The key focus areas are human and animal safety and communications. UITS is designated as Emergency Support Function #2 responsible for maintaining the Communications Network. Appendix A— Emergency Support Function Responsibilities, issued by the Department of Public Safety, details 1
Version 2.0 Published August, 2011 3
Emergency Operations Plan the University’s expectations of UITS during EOC operational periods.
UITS Emergency Operations Plan To meet UConn’s requirements and its primary emergency operations support responsibilities, UITS has established this Emergency Operations Plan (EOP) based on federal and state guidelines that is a standardized incident management approach structured to facilitate activities in five major functional areas: Command, Operations, Planning, Logistics and Finance/Administration. All of the functional areas may or may not be used based on the incident severity and needs. The EOP is designed to address each of UITS’s five primary responsibilities: • • • • •
Coordinates between Telecommunications and Network Services and the EOC for all Campus telecommunications, and network services. Plans for and establishes alternate and emergency telecommunications and Network and in support of the emergency response operations Plans for the emergency installation of Campus telecommunications data networking for critical operations and programs Provides technical support to EOC Manages the utilization of the Volunteer Ham Radio Services when available
Plan Activation The UITS EOP is automatically activated when the University activates the EOC in the Department of Public Safety in response to a natural or manmade event. The UITS EOP remains in effect until the University deactivates the EOC. As soon as possible following the initial EOC briefing by the Department of Public Safety, UITS will convene a briefing for the Leadership Team and select individuals such as the UITS BCP/DR Coordinator and technical specialists as needed, depending on the nature, scope, complexity, and location(s) of the incident(s). During the briefing, the CIO or designee will assign individuals to the defined area lead roles and responsibilities. Appendix B—EOP Checklist will assist the UITS Leadership team and designated area leads in planning the incident response.
Area Lead Roles and Responsibilities •
Incident Lead/EOC Liaison—The incident lead is usually the CIO, a member of the UITS Leadership Team, or the BCP/DR Coordinator, but may be any one the CIO or Leadership Team designates. The incident lead serves as the liaison to the EOC and is expected to attend all EOC briefings, lead all UITS briefings, and remain on-site in the
4
Emergency Operations Plan EOC for the duration of the operational period except when relived for rest periods or to conduct UITS briefings. This person, with the assistance of the communications lead, is also responsible for producing and distributing the After Action Report. •
Operations Lead—The operations lead is responsible for managing all incident tactical activities and data center operations either at the primary data center location on the Storrs campus or at an alternate facility.
•
Communications Lead—The communications lead is responsible for interfacing with University communications, other UConn departments, and IT staff with incident-related information requirements. The communications lead assembles accurate, accessible, and complete information on the incident’s cause, size, and current situation; the resources committed; and other matters of general interest for both internal (UITS) and external (University) audiences. All public communications are handled by University Communications. The communications lead may also perform a key public informationmonitoring role, such as implementing measures for rumor control.
•
Logistics Lead—The logistics lead provides for all the support needs for the incident, such as ordering resources and arranging facilities, transportation, supplies, and food service for incident personnel.
•
Finance/Administration Lead—The finance lead provides financial and/or administrative services to support incident management activities. Large or evolving scenarios may require significant funding originating from multiple sources.
•
Help Desk Lead—The help desk lead is responsible for coordinating and responding to inquiries received through the UITS Call Center.
Transfer of Leadership Duties The process of moving the responsibility for incident leadership from one area lead to another is called “transfer of leadership duties.” It should be recognized that transition of leadership duties on an expanding incident is to be expected. It does not reflect on the competency of the current area lead. There are five important steps in effectively assuming leadership of an incident in progress. •
Step 1: The incoming area lead should, if at all possible, personally perform an assessment of the incident situation with the existing area lead.
•
Step 2: The incoming area lead must be adequately briefed. This briefing must be by the current area lead, and take place face-to-face if possible. The briefing should cover the following: o Incident history (what has happened)
5
Emergency Operations Plan o o o o o o o o o o
Priorities and objectives Current plan Resource assignments Incident organization Resources ordered/needed Facilities established Status of communications Any constraints or limitations Incident potential Delegation of Authority
•
Step 3: After the incident briefing, the incoming area lead should determine an appropriate time for transfer of leadership duties.
•
Step 4: At the appropriate time, notice of a change in area lead should be made to: o Command Staff members (if designated). o All incident personnel.
•
Step 5: The incoming area lead may give the previous area lead another assignment on the incident. There are several advantages of this: o The initial area lead retains first-hand knowledge at the incident site. o This strategy allows the initial area lead to observe the progress of the incident and to gain experience.
Personnel Welfare During a serious situation, addressing personnel and family matters often takes priority over resuming business. Planning for such matters may involve pre-identification of temporary housing, workspace, and staffing. In some situations, the organization may need to use personnel from associated organizations or contract with vendors or consultants if both primary and alternate team members are unavailable or unable to fulfill responsibilities. Preparations should be made during contingency planning development for this possibility to ensure that the vendors or consultants can achieve the same access as the team members can in the event of a disaster.
Defining Emergency Services (“Essential”) Personnel “Non-emergency” employees are those employees whose presence is not critical to the health, safety and security of the University. Emergency Services employees include those in 24/7 agencies, e.g., public safety officers, medical personnel, residential facility personnel, as well as employees in critical service positions, e.g., maintenance and security positions.
6
Emergency Operations Plan At UITS some staff members are considered critical to the operation of the University and are therefore considered “emergency/essential” employees. Department Directors may designate staff occupying specified positions as mandatory for duty in any emergency event. • •
Their assigned duties and responsibilities must be accomplished following the evacuation of non-essential personnel during a declared emergency. They are to ensure uninterrupted performance and provide immediate and continuing support of the University’s operations and/or system support functions.
UITS as a Utility – Support Services •
Is responsible to ensure sufficiently trained staff is available in the area of the emergency event to meet reasonably anticipated problems that would have a negative impact on the ability of the EOC to continue a safe and secure operation. Staff should have contact names and numbers immediately available should they experience a disruption of service or other problems related to the technologies.
UITS – Service Center •
•
• •
Ensures all Service Center components (personnel, support services, and business) are available 24/7 as the emergency event dictates. This may require the physical presence of a representative in the regional EOC while in other cases “on call” status may suffice. Personnel are expected to be available should they receive a call to assist. o Report to work site o Work from home In the event of an emergency the hotlines will be rolled over to the operations center. A recording will be placed on the main help number to instruct callers of the current process.
Defining Closing • • • •
Weather Related resulting in early dismissal, delayed start, non-essential do not report Power Outage resulting in early dismissal, delayed start, non-essential do not report Emergency resulting in evacuation of non-essential, delayed start If the Governor declares the state’s roads closed, the general rule is work from home. However, emergency personnel must receive a letter from UConn designating their emergency status to protect them from ticketing and insurance problems
Guidance to Emergency and Non-‐Emergency Personnel •
“Emergency” staff for the most part is pre-determined; however, the critical event may dictate the designation of additional staff as “emergency.” In such cases, their supervisors or designees will personally inform them. 7
Emergency Operations Plan •
•
•
It is recognized that should a critical event occur during routine business hours, staff remain on duty and therefore must make themselves available when and if called upon to respond. Should staff not be available to respond, the staff member would record as time off (vacation, holiday, etc.). In the event of a critical event occurring after hours, where staff members are asked to report as essential personnel, defined guidelines for compensation are followed (on call, report, etc.). As required by the University’s Emergency Closing Policy, all University employees should be accessible during their regularly scheduled workday even if released for weather or other emergency events and should check University email frequently. Please make sure that your supervisor has current contact information on file for you.
Staff shall be kept informed as to the changing circumstances surrounding the critical event. This may be done through various communication mechanisms (i.e., staff meetings, text messages, email, etc.).
Equipment Loan Program UITS has a pool of 12 Macintosh (dual boot – Mac/Windows) laptops and 2 portable projectors for loan to IT staff for the following purposes: • • •
• • •
Business Continuity: The ability to move off-site and continue business in an emergency situation, such as building evacuation or power outage. In-house Training: Schedule a conference room and ‘x’ number of computer(s) to hold a training event. Temporary Swap: Swap out a computer to reduce down time and maintain productivity for an individual, should her/his computer fail. Note any data files stored on the local hard drive will not be copied to the laptop. Testing: Software and application upgrade compatibility. Travel: Bring a laptop with you when attending a conference/workshop, for the length of the event. Work from Home: Bring a laptop home to complete work activities, study for certification, or take a course.
The loan is for a maximum of two weeks, which can be extended for another two weeks as long as someone else doesn’t require the equipment. UITS Service Center staff members, Laurie Bassett and Nancy Hoddy, manage the Loan Program. Under extreme conditions, emergency personnel may not be able to report for on-site duties. If this can be anticipated, the logistics lead will arrange for and issue laptops and/or 4G mobile access devices (if available) to emergency personnel to facilitate their ability to work from a remote location.
8
Emergency Operations Plan
Critical Infrastructure Protection Plan In the event of a data center outage during the operational period, the Critical Infrastructure Protection Plan (CIPP) will be activated. In preparation for a data center disruption, the Operations Lead will ensure that personnel required by the CIPP remains on standby available to respond if necessary. Steps such as refreshing content in the cloud will commence as soon as practical.
9
Emergency Operations Plan
Appendix A—Emergency Support Function Responsibilities ESF #2 Communications Network (UITS) Primary Responsibilities • Coordinates between Telecommunications and Network Services and the EOC for all Campus telecommunications, and network services. • Plans for and establishes alternate and emergency telecommunications and Network and in support of the emergency response operations • Plans for the emergency installation of Campus telecommunications data networking for critical operations and programs • Provides technical support to EOC • Manages the utilization of the Volunteer Ham Radio Services when available Actions 1. Report to the EOC. Establish communication with the Telecommunications and UITS Help Desk. Provide a report of the status of Campus telecommunications, network services and central computing. 2. Evaluate the overall emergency response operations for damage, impacts to Campus computing, network and telecommunications and identify needs between the EOC and incidents on Campus. 3. Working with the members of the EOC, plan for telecommunications and network support to all operations at the Campus. The EOC will determine priority for service. 4. Provide technical support to Media Communications/Human Resources with the recording of emergency messages on the Campus information line. 5. Provide support with emergency installation of critical data networking and wire and cable infrastructure to support emergency operations and high priority business and service resumption as planned by the EOC. If emergency contract services are needed, coordinate with Purchasing to arrange emergency contracts and agreements for service. 6. Manage the utilization of the Ham radio services on behalf of the EOC. This service can be used to relay messages to other public EOCs or any Ham radio station that is on the air. Ham radio is worldwide and can be used to get messages to key individuals who are not on Campus. 7. Coordinate the details of these plans and tasks with the Telecommunications and Network Services, Help Desk and incorporate into the Incident Action Plan. Provide ongoing communication and coordination between these areas and the EOC. 8. Staff the EOC as long as emergency telecommunications, network services and central computing are needed in the emergency response. Deactivation and Recovery 9. Participate in the EOC post-incident debriefing meetings to identify areas of improvement for EOC Operations and coordination of field emergency operations.
10
Emergency Operations Plan
Appendix B—EOP Checklists Area Lead Role Assignments Responsible Party: CIO or UITS Leadership Team Emergency Operations Leadership Team Key Personnel Contact Information Incident Lead/EOC Liaison Work Insert number Insert Name and Title Home Insert number Insert Street Address Cellular Insert number Insert City, State and Zip Code Email Insert email address Operations Lead Work Home Cellular Email Communications Lead Work Home Cellular Email Logistics Lead Work Home Cellular Email Finance/Administration Lead Work Home Cellular Email Help Desk Lead Work Home Cellular Email While some members of the UITS Leadership Team may not have an assigned role, they may remain on site and serve as alternate area leads to relieve the primary area leads for meal or rest breaks, or to man the EOC if the EOC Liaison is conducting a briefing for UITS staff.
11
Emergency Operations Plan
Emergency Personnel Assignment Emergency Personnel Key Personnel Operations Staff Insert Name and Title Insert Street Address Insert City, State and Zip Code Operations Staff
Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work
Operations Staff
Operations Staff
Operations Staff
Operations Staff
Server Support Group
Server Support Group
Server Support Group
Server Support Group
Server Support Group 12
Contact Information Insert number Insert number Insert number Insert email address
Emergency Operations Plan Emergency Personnel Key Personnel
Contact Information Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email
Server Support Group
Help Desk
Help Desk
Help Desk
Help Desk
Help Desk
Help Desk
Other
Other
Other
13
Emergency Operations Plan Emergency Personnel Key Personnel
Contact Information
Other
Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email
Other
Other
Logistics Checklist Task Arrange Facilities
Transportation
Food Service
Description Book rooms at Nathan Hale Inn. Request that meals and parking are covered. If rooms unavailable at Nathan Hale Inn, contact Residential Life Office to arrange for dorm rooms or other campus housing. (Temporary housing may also be available in the Student Union and/or Athletic facilities.) Arrange for cots or air mattresses, blankets and pillows for MSB if temporary housing is unavailable. Contact transportation services to ensure availability of emergency pickup for emergency personnel and transportation to/from temporary on campus housing Contact dining services to determine meal procedure for emergency personnel. 14
Contact(s) Nathan Hale Inn 860-427-7888
Logan Trimble 860-486-5249 [email protected]
William Wendt 860-486-0032 [email protected]
Janet Franiere 860-486-4804 [email protected]
C Pierce 860-486-3128 [email protected]
Completed
Emergency Operations Plan Task
Supplies Update Personnel Contact List
Loaner Equipment
Facilities
Description Communicate procedure to communications lead for distribution. Ensure adequate supplies of bottled water, flashlights, lanterns, batteries, and snacks. Ensure that the contact list for all UITS employees is current. Arrange for and issue laptops and/or 4G mobile access devices (if available) to emergency personnel to facilitate their ability to work from a remote location if necessary.
Contact facilities to ensure storm drains around the MSB building remain clear and that emergency pumps are available in the event of flooding in the data center or on the MSB roof
Contact(s)
Logistics Lead
Logistics Lead
Logistics Lead
Ronald Gaudet 860-486-3139 [email protected] Anthony Weston 860-486-8042 [email protected] Kenneth Crowell 860-486-3632 [email protected]
Operations Checklist Assure building security is set to holiday schedule.
Finance Checklist Increase ProCard limit to $25,000 to facilitate emergency purchases if necessary.
Help Desk Checklist Ensure adequate staffing to respond to inquiries during operational period.
15
Completed
Emergency Operations Plan
Communications Checklist Volunteer Ham Radio Services: UConn’s Amateur Radio Club should be contacted upon activation of the EOC. In addition, John Wrynn is a licensed ham radio operator and owns a 2meter band walkie-talkie. John should also be placed on standby to facilitate ham radio communications should the Amateur Radio Club be unavailable to assist. Name Michael Nigrelli N1GRE Dominick Spina KB1WOH Rajeev Bansal
UConn Amateur Radio Club Key Contacts Role Email Phone [email protected] President 978-766-8371 [email protected] [email protected] Treasurer 203-417-8384 [email protected] Faculty Advisor [email protected] 860-486-3410
All event related communications are to be documented on the following form which will be included as an addendum to the after action report. [Event Name] Communications Log Operational Period: yyyy-‐mm-‐dd to yyyy-‐mm-‐dd Message
(Include actual message or message summary)
Sent Via
Sent To
16
Sent When
(Email, text, phone, alert.uconn.edu, Rave, etc.)
Emergency Operations Plan [Event Name] Communications Log Operational Period: yyyy-‐mm-‐dd to yyyy-‐mm-‐dd Sent Via
Message
(Include actual message or message summary)
Sent To
(Email, text, phone, alert.uconn.edu, Rave, etc.)
Sent When
Appendix C—UITS Personnel The following table notes all UITS employees, as of December 2012. Each director should review with managers and staff the role and responsibility of each employee and designate each employee as either: Ad Hoc Emergency/ Must Report or Ad Hoc Emergency / As Needed.
Last
First
Work Area
Director
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Adam
Debra
CRM - User Service
Sorrentino
Meinweiser
X
Albright
Jeffrey
Network Engineering and Design
Babbitt
Nye
X
Albright
Seann
Network Engineering and Design
Nye
X
Allen
Robert
Enterprise Applications
Babbitt RomanoConnors
Wisniewski
X
Teal
Teal
X
Bull
Irmscher
X
Teal
Desautels
Sorrentino
Meinweiser
X
Babbitt RomanoConnors Bull
Williams
X
Kriedeman
X
Bull
X
Garcia RomanoConnors
Rodriguez
X
Kazerounian
X
Teal
Desautels
Allison
Edith
Alvarez
Hortencia
Aparo
Thomas
Archambault
Andre
Technical Infrastructure Enterprise Storage Administration - Business Office Technical Infrastructure - Data Center Operations CRM - Telephone Services
Austin
Todd
Network Engineering and Design
Avery
Kathleen
Enterprise Applications - Kuali
Babbitt
John
Network Engineering and Design
Bachand
Jane
Bacon
Andrew
Baglan
Lily
ITQ & DM - Service Management Enterprise Applications - Web Application Development Technical Infrastructure - Data Center Operations
17
X
X
X
X
Emergency Operations Plan
Last
First
Work Area
Director
Baker
Doug
Baker
Linda
Technical Infrastructure - Linux Server Support CRM - User Services
Bardot
Marybeth
CRM - User Services
Bassett
Laurie
Bazzani
Janice
Bhatt
Rushikuma
Bhunia
Girija
Blessington
John
Boggis
Joshua
Bordick
Lara
Brown
Eileen
Bull
Nancy
Caprera
Linda
Carcano
Raymond
Carpenter
Melinda
Carty
Andrew
Casaol
Herman
Case
William
Cavanaugh
Michelle
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Teal
Smith
X
Sorrentino
Meinweiser
X
Sorrentino
Meinweiser
X
CRM - Telephone Services Enterprise Applications - Training & Communications Enterprise Applications - WDIT University Applications ITQ & DM - Data Warehousing Technical Infrastructure - Data Center Operations Technical Infrastructure - Unified Comm. Server Support Enterprise Applications - WDIT FAMIS Network Engineering and Design
Sorrentino RomanoConnors RomanoConnors Garcia
Meinweiser
X
Wisniewski
X
Kazerounian
X
Garcia
X
Teal
Desautels
Teal
Teal
X
Kazerounian
X
Williams
X
VP and CIO Enterprise Applications PeopleSoft Connecticut Education Network Network Operations Administration - HR
Choi RomanoConnors
Choi
X
Wisniewski
X
Taylor
Taylor
X
Bull
Enderle
X
Sorrentino
Sorrentino
X
Teal
Wrynn
X
Teal
Desautels
X
Garcia
McBrien
X
Wisniewski
X
Teal
X
Enderle
X
Kriedeman
X
RomanoConnors Babbitt
X
X
Ceccarelli
Gail
Cerrigione
Christopher
CRM - User Services Technical Infrastructure Windows Server Support Technical Infrastructure Computer Scheduling ITQ & DM - Reporting Tool Support Enterprise Applications - Change Control and Bundling CIO - vPC
Chartier
Carolyn
Administration - HR
Chudnow
David
Enterprise Applications - Kuali
Copley
Georgianne
ITQ & DM - IT PMO
Bull RomanoConnors Garcia
Garcia
X
Costanzo
Lorraine
Security - Administrative Support
Pufahl
Pufahl
X
Czemske
Christine
Administration - Business Office
Bull
Irmscher
X
Dean
Philip
Sorrentino
X
Jason
Teal
Wrynn
X
DelGrego
William
CRM - User Services Technical Infrastructure Windows Server Support Network Engineering and Design
Sorrentino
Deary
Babbitt
Farese
X
DePalma
Andrew
Garcia
Garcia
X
Desautels
Jo-Ann
Teal
Teal
X
Deschenes
Ellen
Teal
Allison
X
Desloge
Cindy
Bull
Irmscher
X
Desmarais
Paul
Teal
Teal
X
Desmarais
Kathleen
Dexter
Marie
RomanoConnors RomanoConnors
RomanoConnors RomanoConnors
DiGrazia
Mick
ITQ & DM - Service Management Technical Infrastructure Scheduling, Ops & Data Center Infra. Technical Infrastructure Enterprise Storage Administration - Business Office Technical Infrastructure Mainframe Server Support Enterprise Applications Administrative Support Enterprise Applications Mainframe Application Support Security - Awareness and Compliance
Pufahl
Pufahl
18
RomanoConnors Bull
X X X
Emergency Operations Plan
Last
First
Work Area
Director
Do
Cuong
Enterprise Applications - FAMIS
Donovan
Janine
Dunnigan
Brian
Dupont
Christopher
Dziekan
Richard
RomanoConnors Bull RomanoConnors
X
Irmscher
X
Kazerounian
X
Teal
Gwinnell
X
Teal
Desautels
Elwell
Valorie
Enderle
Laurie
Erickson
Doug
Network Engineering and Design
Babbitt
Farese
Jeffrey
Network Engineering and Design
Farnham
Thomas
CRM - User Services
Farrands
Danielle
Fazzina
Angelo
Fatu
Vlad
Ferretti
Matthew
Administration – Business Office Technical Infrastructure - Unified Comm. Server Support Network Engineering and Design Technical Infrastructure Computer Scheduling Enterprise Applications - WDIT University Applications Technical Infrastructure Mainframe Server Support Security - Disaster Recovery Enterprise Applications PeopleSoft
Veronica
Flynn
Nancy
Font
Victor
Garcia
Lisa
Garcia
RomanoConnors Bull
Bull
X
Nye
X
Babbitt
Babbitt
X
Sorrentino
Meinweiser
X
Bull
Irmscher
Teal
Boggis
X
Babbitt
Babbitt
X
Teal
Desautels
X
RomanoConnors
Kazerounian
X
Teal
Desmarais
X
Pufahl RomanoConnors
Pufahl
X
Wisniewski
X
RomanoConnors
X
Kazerounian
X
Kriedeman
X
Bull RomanoConnors J. Pollack
X
Teal
Desautels
X
Teal
Teal
X
Babbitt
Farese
X
Teal
Gwinnell
X
Babbitt
Nye
X
Teal
Desmarais
X
Taylor
Taylor
X
Kazerounian
X
Wisniewski
X
Bull
Garrett
Steven
Enterprise Applications - WDIT HuskyCT
Gedarovich
James
Enterprise Applications - Kuali
Ghaemolsabahi
Haleh
Gile
Maryann
Gill
Jonathan
RomanoConnors RomanoConnors Bull RomanoConnors Teal
Gunn
Gregory
Gwinnell
John
Hamley
Jason
Hammond
John
Hanyckyj
Elijah
Harland
Lawrence
Harris
Sheila Louis
Hernandez
Kathryn
Herrara
Byron
Hoddy
Nancy
Hoel
Ross
Administration - Business Office
Hogan
Jo-Anne
CRM - User Services
19
X X
ITQ & DM
Herman
X
Wisniewski
Michael
CIO Enterprise Applications - Data Management Services Technical Infrastructure - vPC Technical Infrastructure Computer Scheduling Technical Infrastructure - Unix Server Support Network Engineering and Design Technical Infrastructure - Unix Server Support Network Engineering and Design Technical Infrastructure Mainframe Server Support Connecticut Education Network Marketing and Outreach Enterprise Applications - WDIT Workflow/Mobile Development Enterprise Applications PeopleSoft - CS Special Projects Technical Infrastructure - Data Center Operations CRM - Telephone Services
Ad Hoc Emergency / As Needed
Kazerounian
Administration - Business Office Enterprise Applications - WDIT Web Application Development Technical Infrastructure - Unix Server Support Technical Infrastructure - Data Center Infrastructure Enterprise Applications PeopleSoft Administration - HR
Ferriss
Manager
Ad Hoc Emergency / Must Report
RomanoConnors RomanoConnors
X X
Teal
Desautels
X
X
Sorrentino
Meinweiser
X
Bull
Irmscher
X
Sorrentino
Meinweiser
X
Emergency Operations Plan
Last
First
Work Area
Director
Kristy
Enterprise Applications - WDIT Workflow/Mobile Development Enterprise Applications PeopleSoft CIO - Administrative Support
RomanoConnors RomanoConnors Bull
Denise
Administration - Business Office
Jackson
Linda
Enterprise Applications - Kuali
Bull RomanoConnors
Jancewicz
Russell
Hu
Ying
Huber
Richard
Hughes Irmscher
Technical Infrastructure - Linux Server Support Enterprise Applications - Web Application Development Technical Infrastructure Mainframe Server Support
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Kazerounian
X
Wisniewski
X
Bull
X
Bull
X
Kriedeman
X
Teal
Smith
X
RomanoConnors
Kazerounian
X
Teal
Desmarais
X
RomanoConnors Williams
Jatkowski
Musa
Johnson
Julie
Kazerounian
Jila
Enterprise Applications - WDIT
Keegan
Glenn
Network Engineering and Design
RomanoConnors Babbitt
Kent
Robert
Network Engineering and Design
Babbitt
Farese
X
Khairallah
John
Babbitt
Williams
X
Khairallah
Meghan
Teal
Boggis
X
Kocsondy
Ryan
Network Engineering and Design Technical Infrastructure - Unified Comm. Server Support West Hartford Operations
Pamela
Enterprise Applications - Kuali
Bull RomanoConnors
X
Kriedeman
Bull RomanoConnors RomanoConnors
Wisniewski
X
Pufahl
Pufahl
X
Garcia
McBrien
X
Gile
X
Rodriguez
X
Kazerounian
X
Kwon
Bruce
Lang
Michael
Long
Michael
Loux
Jonathan
Lovelace
Maurice
Enterprise Applications PeopleSoft Security - Network and Information ITQ & DM - Reporting Tool Support Enterprise Applications - Data Management Services ITQ & DM - Service Management
Lowe
Janet
Enterprise Applications - WDIT
Lysak
Keith
MacDonald
Neil
Madam
Kiran
Mandeville
James
Maresca
Steve
Marquis
Dylan
Technical Infrastructure - Data Center Operations Network Engineering and Design
RomanoConnors Garcia RomanoConnors Teal
Desautels
X X
X
X
X
Babbitt
Williams
X
Garcia RomanoConnors
Garcia
X
Dexter
X
Pufahl
Pufahl
X
Teal
Smith
X
Gile
X
Wisniewski
X
Garcia
McBrien
X
Marquis
Joan
Masso
James
McBrien
Terrence
McCormick
David
ITQ & DM - Data Warehousing Enterprise Applications Mainframe Applications Security - Network and Information Technical Infrastructure - Linux Server Support Enterprise Applications - Data Management Services Enterprise Applications PeopleSoft ITQ & DM - Reporting Tool Support ITQ & DM - PMO
Garcia
Garcia
X
McNamara
Thomas
Network Engineering and Design
Babbitt
Williams
X
Meinweiser
Patricia
X
Ruben
Kazerounian
X
Metivier
Pamela
Wisniewski
X
Mikolinski
Lisa
Sorrentino RomanoConnors RomanoConnors Sorrentino
Sorrentino
Mercado
Customer Relations Management Enterprise Applications - WDIT University Applications Enterprise Applications PeopleSoft CRM - User Services
Sorrentino
X
20
RomanoConnors RomanoConnors
Emergency Operations Plan
Last
First
Work Area
Director
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Millan
Veronica
CRM - User Services
Sorrentino
Sorrentino
X
Miller
June
Sorrentino
Meinweiser
X
Mindek
James
Taylor
Taylor
X
RomanoConnors
Wisniewski
X
Taylor
Taylor
X
Teal
Gwinnell
X
Miras-Alonso
Enrique
Morales
Rafael
Morin
Pierre
Morrell
Robert
CRM - User Services Connecticut Education Network Marketing and Outreach Enterprise Applications PeopleSoft Connecticut Education Network Network Operations Technical Infrastructure - Unix Server Support CRM - User Services
Sorrentino
Sorrentino
X
Msaddi
George
CRM - User Services
Sorrentino
Sorrentino
X
Nguyen
Van
CRM - User Services
Sorrentino
Sorrentino
X
Norris
Joel
X
Antoinette
Wisniewski
X
Nye
Lance
Babbitt
X
Oatley
Michael
Bull RomanoConnors Babbitt RomanoConnors
Kocsondy
Nunes
Kazerounian
X
O'Connor
Ryan
Sorrentino
Sorrentino
X
O'Donnell
Diana
Garcia
Garcia
X
Orcutt
Michael
Teal
Allison
X
Pagano
Andrew
Babbitt
Williams
X
Pai
Sandhya
Teal
Smith
X
Parciak
Paul
Teal
Desautels
X
Pare
Suzanne
West Hartford Operations Enterprise Applications PeopleSoft Network Engineering and Design Enterprise Applications - WDIT Workflow/Mobile Development Customer Relations Support User Services ITQ & DM - PMO Technical Infrastructure Enterprise Storage Network Engineering and Design Technical Infrastructure - Linux Server Support Technical Infrastructure - Data Center Infrastructure CRM - User Services
Sorrentino
Sorrentino
X
Patel
Ronak
Bull
Kocsondy
X
Pelletier
Daniel
Teal
Desautels
X
Pennington
Michael
Taylor
Taylor
X
Pomerleau
Armand
West Hartford Operations Technical Infrastructure - Data Center Infrastructure Connecticut Education Network Network Operations Network Engineering and Design
Babbitt
Williams
X
Portuguez
Rick
CRM - User Services
Sorrentino
Sorrentino
X
Postler
Dale
Network Engineering and Design
Babbitt
Williams
X
Pufahl
Jason
Bull
Bull
X
Raczkowski
Melanie
Taylor
Taylor
X
Radziwillowicz
Anna
Security Connecticut Education Network Business Operations ITQ & DM - PMO
Garcia
Garcia
X
Rae
Laurel
CRM - Telephone Services
Meinweiser
X
Raines
David
Enterprise Applications - Kuali
Sorrentino RomanoConnors
Kriedeman
X
Taylor
Taylor
X
Teal
Smith
X
Garcia
Garcia
X
Bull
X
Kazerounian
X
Kazerounian
X
Sorrentino
X
Rego
Wendy
Rifkin
Jonathan
Rodriguez RomanoConnors
Sherry
Connecticut Education Network Business Operations Technical Infrastructure - Linux Server Support ITQ & DM - Service Management
Debora
Enterprise Applications
Bull
Rowland
Robert
Roy
Joshua
Roy
Mark
Enterprise Applications - WDIT University Applications Enterprise Applications - WDIT Web Application Development ITQ & DM - PMO
RomanoConnors RomanoConnors Sorrentino
21
Emergency Operations Plan
Last
First
Saba
Mitchell
Sanku
Sirisha
Schaffhauser
John
Sevilla
Elena
Shiling
Benjamin
Simmon
Kelli
Simon
Richard
Slonski
Shawn
Smith
Matthew
Sorrentino
Katherina
Soucy
Kevin
Stedman
Jill
Work Area
Director
Enterprise Applications - Kuali
RomanoConnors RomanoConnors RomanoConnors
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Kriedeman
X
Wisniewski
X
Wisniewski
X
Teal
Smith
X
Babbitt
Nye
Babbitt
Farese
X
Teal
Wrynn
X
Babbitt
Williams
Teal
Teal
X
Bull
Bull
X
Teal
Desautels
X
Teal
Desautels
X
Gile
X
Stone
Nancy
Sulamn
Gregory
Enterprise Applications PeopleSoft Enterprise Applications PeopleSoft Technical Infrastructure - Linux Server Support Networking – Audio Visual Services Network Engineering and Design Technical Infrastructure Windows Server Support Network Engineering -- PIP Technical Infrastructure - Linux Server Support Customer Relations Management Technical Infrastructure - Data Center Operations Technical Infrastructure Computer Scheduling Enterprise Applications - Data Management Services Network Engineering and Design
Williams
X
Taylor
Patrick
CRM - User Services
Sorrentino
Sorrentino
X
Taylor
Scott
Connecticut Education Network
Bull
Bull
X
Teal
Richard
Bull
X
Joseph
Teal
Wrynn
X
Tomecko
Constance
Garcia
McBrien
X
Volkert
William
X
Hengameh
Kazerounian
X
Waleszczyk
Tammy
Wisniewski
X
Warren
Constance
Babbitt RomanoConnors RomanoConnors Sorrentino
Williams
Vosough
Technical Infrastructure Technical Infrastructure Windows Server Support ITQ & DM - Reporting Tool Support Network Engineering and Design Enterprise Applications - WDIT HuskyCT Enterprise Applications PeopleSoft CRM - User Services
Bull
Theriault
Meinweiser
X
Watrous
Michael
Network Engineering and Design
Nye
X
Weingart
Richard
Enterprise Applications - Kuali
Kriedeman
X
Wentworth
Robert
Kocsondy
X
Wiggins
Mark
Teal
Smith
X
Williams
Michael Angie
Woodaman
Brien
Babbitt RomanoConnors Babbitt
Babbitt RomanoConnors Nye
X
Wisniewski
Wrynn
John
Teal
Teal
X
Wu
Shuihua
West Hartford Operations Technical Infrastructure - Linux Server Support Network Engineering and Design Enterprise Applications PeopleSoft Network Engineering and Design Technical Infrastructure Windows Server Support Enterprise Applications - WDIT Workflow/Mobile Development
Babbitt RomanoConnors Bull
RomanoConnors
Kazerounian
X
Zhang
Yi
RomanoConnors
Kazerounian
X
Enterprise Applications - WDIT Web Application Development
22
RomanoConnors Babbitt
X X
Emergency Operations Plan
Document Change History DOCUMENT CHANGE HISTORY Plan Version No. Ver. 1.0/ Rev. 01
Release Date
Summary of Changes
Section No./ Paragraph No.
Changes Made By
01/15/13
Initial Draft
Entire Document
BCP/DR Coordinator
Ver. 1.0/ Rev. 02
02/13/13
Added learning items from Blizzard of 2013. (Nathan Hale meals, parking, and MSB building security)
Entire Document
BCP/DR Coordinator
Ver. 1.0/ Rev. 03
03/04/2013
Updated during table top exercise Entire Document
BCP/DR Coordinator
23
Emergency Operations Plan
Prepared by Victor Font UITS Business Continuity / Disaster Recovery Coordinator January 2013
Emergency Operations Plan
Table of Contents
Executive Summary ................................................................................................................................................. 3 UConn’s Emergency Support Functions ......................................................................................................... 3 UITS Emergency Operations Plan ..................................................................................................................... 4 Plan Activation ....................................................................................................................................................................... 4 Area Lead Roles and Responsibilities .......................................................................................................................... 4 Transfer of Leadership Duties ......................................................................................................................................... 5 Personnel Welfare ................................................................................................................................................................ 6 Defining Emergency Services (“Essential”) Personnel .......................................................................................... 6 UITS as a Utility – Support Services ........................................................................................................................ 7 UITS – Service Center ..................................................................................................................................................... 7 Defining Closing ............................................................................................................................................................... 7 Guidance to Emergency and Non-‐Emergency Personnel .............................................................................. 7 Equipment Loan Program ................................................................................................................................................. 8 Critical Infrastructure Protection Plan ........................................................................................................................ 9 Appendix A—Emergency Support Function Responsibilities ........................................................... 10 Appendix B—EOP Checklists ........................................................................................................................... 11 Area Lead Role Assignments ......................................................................................................................................... 11 Emergency Personnel Assignment ............................................................................................................................. 12 Logistics Checklist ............................................................................................................................................................. 14 Operations Checklist ........................................................................................................................................................ 15 Finance Checklist ............................................................................................................................................................... 15 Help Desk Checklist .......................................................................................................................................................... 15 Communications Checklist ............................................................................................................................................ 16 Appendix C—UITS Personnel .......................................................................................................................... 17 Document Change History ................................................................................................................................. 23
2
Emergency Operations Plan
Executive Summary This document provides guidelines for conducting emergency operations within UITS in the event a situation occurs whereby University leadership activates the Emergency Operations Center (EOC) in the Department of Public Safety. UConn’s EOC functions in accordance with the State of Connecticut’s State Response Framework1 (SRF). The Connecticut Department of Emergency Services and Public Protection (DESPP) and Division of Emergency Management and Homeland Security (DEMHS) in partnership with other CT State Agencies and Non-Governmental Organizations involved in emergency preparedness and response activities developed the SRF in accordance with the National Incident Management System (NIMS) and in compliance with Section 28-5(b) of the Connecticut General Statutes which reads in part: “The commissioner shall direct the preparation of a comprehensive plan and program for the civil preparedness of the state… …all government agencies, state or local, and all civil preparedness forces in the state shall carry out the duties and functions assigned by the plan and program as approved…” The SRF describes the interaction of state government with local, federal and tribal governments, nongovernmental response organizations and other private sector partners, the media, and the public in implementing emergency response and recovery functions in times of crisis. In general, the SRF describes how the State of Connecticut and its partners will work together to support local governments and their residents in responding to disasters and emergencies. The SRF imposes responsibilities on the Department of Higher Education (DHE) that include but may not be limited to: •
Coordinating shelter, mass feeding, non-surgical medical care, and temporary housing at state colleges, regional community colleges, and the University of Connecticut depending upon student populations.
UConn’s Emergency Support Functions To meet the requirements of the SRF, UConn’s Department of Public Safety has prioritized the University’s emergency support functions and designated each unit’s primary responsibilities, actions required during operational periods, deactivation, and recovery expectations. The key focus areas are human and animal safety and communications. UITS is designated as Emergency Support Function #2 responsible for maintaining the Communications Network. Appendix A— Emergency Support Function Responsibilities, issued by the Department of Public Safety, details 1
Version 2.0 Published August, 2011 3
Emergency Operations Plan the University’s expectations of UITS during EOC operational periods.
UITS Emergency Operations Plan To meet UConn’s requirements and its primary emergency operations support responsibilities, UITS has established this Emergency Operations Plan (EOP) based on federal and state guidelines that is a standardized incident management approach structured to facilitate activities in five major functional areas: Command, Operations, Planning, Logistics and Finance/Administration. All of the functional areas may or may not be used based on the incident severity and needs. The EOP is designed to address each of UITS’s five primary responsibilities: • • • • •
Coordinates between Telecommunications and Network Services and the EOC for all Campus telecommunications, and network services. Plans for and establishes alternate and emergency telecommunications and Network and in support of the emergency response operations Plans for the emergency installation of Campus telecommunications data networking for critical operations and programs Provides technical support to EOC Manages the utilization of the Volunteer Ham Radio Services when available
Plan Activation The UITS EOP is automatically activated when the University activates the EOC in the Department of Public Safety in response to a natural or manmade event. The UITS EOP remains in effect until the University deactivates the EOC. As soon as possible following the initial EOC briefing by the Department of Public Safety, UITS will convene a briefing for the Leadership Team and select individuals such as the UITS BCP/DR Coordinator and technical specialists as needed, depending on the nature, scope, complexity, and location(s) of the incident(s). During the briefing, the CIO or designee will assign individuals to the defined area lead roles and responsibilities. Appendix B—EOP Checklist will assist the UITS Leadership team and designated area leads in planning the incident response.
Area Lead Roles and Responsibilities •
Incident Lead/EOC Liaison—The incident lead is usually the CIO, a member of the UITS Leadership Team, or the BCP/DR Coordinator, but may be any one the CIO or Leadership Team designates. The incident lead serves as the liaison to the EOC and is expected to attend all EOC briefings, lead all UITS briefings, and remain on-site in the
4
Emergency Operations Plan EOC for the duration of the operational period except when relived for rest periods or to conduct UITS briefings. This person, with the assistance of the communications lead, is also responsible for producing and distributing the After Action Report. •
Operations Lead—The operations lead is responsible for managing all incident tactical activities and data center operations either at the primary data center location on the Storrs campus or at an alternate facility.
•
Communications Lead—The communications lead is responsible for interfacing with University communications, other UConn departments, and IT staff with incident-related information requirements. The communications lead assembles accurate, accessible, and complete information on the incident’s cause, size, and current situation; the resources committed; and other matters of general interest for both internal (UITS) and external (University) audiences. All public communications are handled by University Communications. The communications lead may also perform a key public informationmonitoring role, such as implementing measures for rumor control.
•
Logistics Lead—The logistics lead provides for all the support needs for the incident, such as ordering resources and arranging facilities, transportation, supplies, and food service for incident personnel.
•
Finance/Administration Lead—The finance lead provides financial and/or administrative services to support incident management activities. Large or evolving scenarios may require significant funding originating from multiple sources.
•
Help Desk Lead—The help desk lead is responsible for coordinating and responding to inquiries received through the UITS Call Center.
Transfer of Leadership Duties The process of moving the responsibility for incident leadership from one area lead to another is called “transfer of leadership duties.” It should be recognized that transition of leadership duties on an expanding incident is to be expected. It does not reflect on the competency of the current area lead. There are five important steps in effectively assuming leadership of an incident in progress. •
Step 1: The incoming area lead should, if at all possible, personally perform an assessment of the incident situation with the existing area lead.
•
Step 2: The incoming area lead must be adequately briefed. This briefing must be by the current area lead, and take place face-to-face if possible. The briefing should cover the following: o Incident history (what has happened)
5
Emergency Operations Plan o o o o o o o o o o
Priorities and objectives Current plan Resource assignments Incident organization Resources ordered/needed Facilities established Status of communications Any constraints or limitations Incident potential Delegation of Authority
•
Step 3: After the incident briefing, the incoming area lead should determine an appropriate time for transfer of leadership duties.
•
Step 4: At the appropriate time, notice of a change in area lead should be made to: o Command Staff members (if designated). o All incident personnel.
•
Step 5: The incoming area lead may give the previous area lead another assignment on the incident. There are several advantages of this: o The initial area lead retains first-hand knowledge at the incident site. o This strategy allows the initial area lead to observe the progress of the incident and to gain experience.
Personnel Welfare During a serious situation, addressing personnel and family matters often takes priority over resuming business. Planning for such matters may involve pre-identification of temporary housing, workspace, and staffing. In some situations, the organization may need to use personnel from associated organizations or contract with vendors or consultants if both primary and alternate team members are unavailable or unable to fulfill responsibilities. Preparations should be made during contingency planning development for this possibility to ensure that the vendors or consultants can achieve the same access as the team members can in the event of a disaster.
Defining Emergency Services (“Essential”) Personnel “Non-emergency” employees are those employees whose presence is not critical to the health, safety and security of the University. Emergency Services employees include those in 24/7 agencies, e.g., public safety officers, medical personnel, residential facility personnel, as well as employees in critical service positions, e.g., maintenance and security positions.
6
Emergency Operations Plan At UITS some staff members are considered critical to the operation of the University and are therefore considered “emergency/essential” employees. Department Directors may designate staff occupying specified positions as mandatory for duty in any emergency event. • •
Their assigned duties and responsibilities must be accomplished following the evacuation of non-essential personnel during a declared emergency. They are to ensure uninterrupted performance and provide immediate and continuing support of the University’s operations and/or system support functions.
UITS as a Utility – Support Services •
Is responsible to ensure sufficiently trained staff is available in the area of the emergency event to meet reasonably anticipated problems that would have a negative impact on the ability of the EOC to continue a safe and secure operation. Staff should have contact names and numbers immediately available should they experience a disruption of service or other problems related to the technologies.
UITS – Service Center •
•
• •
Ensures all Service Center components (personnel, support services, and business) are available 24/7 as the emergency event dictates. This may require the physical presence of a representative in the regional EOC while in other cases “on call” status may suffice. Personnel are expected to be available should they receive a call to assist. o Report to work site o Work from home In the event of an emergency the hotlines will be rolled over to the operations center. A recording will be placed on the main help number to instruct callers of the current process.
Defining Closing • • • •
Weather Related resulting in early dismissal, delayed start, non-essential do not report Power Outage resulting in early dismissal, delayed start, non-essential do not report Emergency resulting in evacuation of non-essential, delayed start If the Governor declares the state’s roads closed, the general rule is work from home. However, emergency personnel must receive a letter from UConn designating their emergency status to protect them from ticketing and insurance problems
Guidance to Emergency and Non-‐Emergency Personnel •
“Emergency” staff for the most part is pre-determined; however, the critical event may dictate the designation of additional staff as “emergency.” In such cases, their supervisors or designees will personally inform them. 7
Emergency Operations Plan •
•
•
It is recognized that should a critical event occur during routine business hours, staff remain on duty and therefore must make themselves available when and if called upon to respond. Should staff not be available to respond, the staff member would record as time off (vacation, holiday, etc.). In the event of a critical event occurring after hours, where staff members are asked to report as essential personnel, defined guidelines for compensation are followed (on call, report, etc.). As required by the University’s Emergency Closing Policy, all University employees should be accessible during their regularly scheduled workday even if released for weather or other emergency events and should check University email frequently. Please make sure that your supervisor has current contact information on file for you.
Staff shall be kept informed as to the changing circumstances surrounding the critical event. This may be done through various communication mechanisms (i.e., staff meetings, text messages, email, etc.).
Equipment Loan Program UITS has a pool of 12 Macintosh (dual boot – Mac/Windows) laptops and 2 portable projectors for loan to IT staff for the following purposes: • • •
• • •
Business Continuity: The ability to move off-site and continue business in an emergency situation, such as building evacuation or power outage. In-house Training: Schedule a conference room and ‘x’ number of computer(s) to hold a training event. Temporary Swap: Swap out a computer to reduce down time and maintain productivity for an individual, should her/his computer fail. Note any data files stored on the local hard drive will not be copied to the laptop. Testing: Software and application upgrade compatibility. Travel: Bring a laptop with you when attending a conference/workshop, for the length of the event. Work from Home: Bring a laptop home to complete work activities, study for certification, or take a course.
The loan is for a maximum of two weeks, which can be extended for another two weeks as long as someone else doesn’t require the equipment. UITS Service Center staff members, Laurie Bassett and Nancy Hoddy, manage the Loan Program. Under extreme conditions, emergency personnel may not be able to report for on-site duties. If this can be anticipated, the logistics lead will arrange for and issue laptops and/or 4G mobile access devices (if available) to emergency personnel to facilitate their ability to work from a remote location.
8
Emergency Operations Plan
Critical Infrastructure Protection Plan In the event of a data center outage during the operational period, the Critical Infrastructure Protection Plan (CIPP) will be activated. In preparation for a data center disruption, the Operations Lead will ensure that personnel required by the CIPP remains on standby available to respond if necessary. Steps such as refreshing content in the cloud will commence as soon as practical.
9
Emergency Operations Plan
Appendix A—Emergency Support Function Responsibilities ESF #2 Communications Network (UITS) Primary Responsibilities • Coordinates between Telecommunications and Network Services and the EOC for all Campus telecommunications, and network services. • Plans for and establishes alternate and emergency telecommunications and Network and in support of the emergency response operations • Plans for the emergency installation of Campus telecommunications data networking for critical operations and programs • Provides technical support to EOC • Manages the utilization of the Volunteer Ham Radio Services when available Actions 1. Report to the EOC. Establish communication with the Telecommunications and UITS Help Desk. Provide a report of the status of Campus telecommunications, network services and central computing. 2. Evaluate the overall emergency response operations for damage, impacts to Campus computing, network and telecommunications and identify needs between the EOC and incidents on Campus. 3. Working with the members of the EOC, plan for telecommunications and network support to all operations at the Campus. The EOC will determine priority for service. 4. Provide technical support to Media Communications/Human Resources with the recording of emergency messages on the Campus information line. 5. Provide support with emergency installation of critical data networking and wire and cable infrastructure to support emergency operations and high priority business and service resumption as planned by the EOC. If emergency contract services are needed, coordinate with Purchasing to arrange emergency contracts and agreements for service. 6. Manage the utilization of the Ham radio services on behalf of the EOC. This service can be used to relay messages to other public EOCs or any Ham radio station that is on the air. Ham radio is worldwide and can be used to get messages to key individuals who are not on Campus. 7. Coordinate the details of these plans and tasks with the Telecommunications and Network Services, Help Desk and incorporate into the Incident Action Plan. Provide ongoing communication and coordination between these areas and the EOC. 8. Staff the EOC as long as emergency telecommunications, network services and central computing are needed in the emergency response. Deactivation and Recovery 9. Participate in the EOC post-incident debriefing meetings to identify areas of improvement for EOC Operations and coordination of field emergency operations.
10
Emergency Operations Plan
Appendix B—EOP Checklists Area Lead Role Assignments Responsible Party: CIO or UITS Leadership Team Emergency Operations Leadership Team Key Personnel Contact Information Incident Lead/EOC Liaison Work Insert number Insert Name and Title Home Insert number Insert Street Address Cellular Insert number Insert City, State and Zip Code Email Insert email address Operations Lead Work Home Cellular Email Communications Lead Work Home Cellular Email Logistics Lead Work Home Cellular Email Finance/Administration Lead Work Home Cellular Email Help Desk Lead Work Home Cellular Email While some members of the UITS Leadership Team may not have an assigned role, they may remain on site and serve as alternate area leads to relieve the primary area leads for meal or rest breaks, or to man the EOC if the EOC Liaison is conducting a briefing for UITS staff.
11
Emergency Operations Plan
Emergency Personnel Assignment Emergency Personnel Key Personnel Operations Staff Insert Name and Title Insert Street Address Insert City, State and Zip Code Operations Staff
Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work
Operations Staff
Operations Staff
Operations Staff
Operations Staff
Server Support Group
Server Support Group
Server Support Group
Server Support Group
Server Support Group 12
Contact Information Insert number Insert number Insert number Insert email address
Emergency Operations Plan Emergency Personnel Key Personnel
Contact Information Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email
Server Support Group
Help Desk
Help Desk
Help Desk
Help Desk
Help Desk
Help Desk
Other
Other
Other
13
Emergency Operations Plan Emergency Personnel Key Personnel
Contact Information
Other
Work Home Cellular Email Work Home Cellular Email Work Home Cellular Email
Other
Other
Logistics Checklist Task Arrange Facilities
Transportation
Food Service
Description Book rooms at Nathan Hale Inn. Request that meals and parking are covered. If rooms unavailable at Nathan Hale Inn, contact Residential Life Office to arrange for dorm rooms or other campus housing. (Temporary housing may also be available in the Student Union and/or Athletic facilities.) Arrange for cots or air mattresses, blankets and pillows for MSB if temporary housing is unavailable. Contact transportation services to ensure availability of emergency pickup for emergency personnel and transportation to/from temporary on campus housing Contact dining services to determine meal procedure for emergency personnel. 14
Contact(s) Nathan Hale Inn 860-427-7888
Logan Trimble 860-486-5249 [email protected]
William Wendt 860-486-0032 [email protected]
Janet Franiere 860-486-4804 [email protected]
C Pierce 860-486-3128 [email protected]
Completed
Emergency Operations Plan Task
Supplies Update Personnel Contact List
Loaner Equipment
Facilities
Description Communicate procedure to communications lead for distribution. Ensure adequate supplies of bottled water, flashlights, lanterns, batteries, and snacks. Ensure that the contact list for all UITS employees is current. Arrange for and issue laptops and/or 4G mobile access devices (if available) to emergency personnel to facilitate their ability to work from a remote location if necessary.
Contact facilities to ensure storm drains around the MSB building remain clear and that emergency pumps are available in the event of flooding in the data center or on the MSB roof
Contact(s)
Logistics Lead
Logistics Lead
Logistics Lead
Ronald Gaudet 860-486-3139 [email protected] Anthony Weston 860-486-8042 [email protected] Kenneth Crowell 860-486-3632 [email protected]
Operations Checklist Assure building security is set to holiday schedule.
Finance Checklist Increase ProCard limit to $25,000 to facilitate emergency purchases if necessary.
Help Desk Checklist Ensure adequate staffing to respond to inquiries during operational period.
15
Completed
Emergency Operations Plan
Communications Checklist Volunteer Ham Radio Services: UConn’s Amateur Radio Club should be contacted upon activation of the EOC. In addition, John Wrynn is a licensed ham radio operator and owns a 2meter band walkie-talkie. John should also be placed on standby to facilitate ham radio communications should the Amateur Radio Club be unavailable to assist. Name Michael Nigrelli N1GRE Dominick Spina KB1WOH Rajeev Bansal
UConn Amateur Radio Club Key Contacts Role Email Phone [email protected] President 978-766-8371 [email protected] [email protected] Treasurer 203-417-8384 [email protected] Faculty Advisor [email protected] 860-486-3410
All event related communications are to be documented on the following form which will be included as an addendum to the after action report. [Event Name] Communications Log Operational Period: yyyy-‐mm-‐dd to yyyy-‐mm-‐dd Message
(Include actual message or message summary)
Sent Via
Sent To
16
Sent When
(Email, text, phone, alert.uconn.edu, Rave, etc.)
Emergency Operations Plan [Event Name] Communications Log Operational Period: yyyy-‐mm-‐dd to yyyy-‐mm-‐dd Sent Via
Message
(Include actual message or message summary)
Sent To
(Email, text, phone, alert.uconn.edu, Rave, etc.)
Sent When
Appendix C—UITS Personnel The following table notes all UITS employees, as of December 2012. Each director should review with managers and staff the role and responsibility of each employee and designate each employee as either: Ad Hoc Emergency/ Must Report or Ad Hoc Emergency / As Needed.
Last
First
Work Area
Director
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Adam
Debra
CRM - User Service
Sorrentino
Meinweiser
X
Albright
Jeffrey
Network Engineering and Design
Babbitt
Nye
X
Albright
Seann
Network Engineering and Design
Nye
X
Allen
Robert
Enterprise Applications
Babbitt RomanoConnors
Wisniewski
X
Teal
Teal
X
Bull
Irmscher
X
Teal
Desautels
Sorrentino
Meinweiser
X
Babbitt RomanoConnors Bull
Williams
X
Kriedeman
X
Bull
X
Garcia RomanoConnors
Rodriguez
X
Kazerounian
X
Teal
Desautels
Allison
Edith
Alvarez
Hortencia
Aparo
Thomas
Archambault
Andre
Technical Infrastructure Enterprise Storage Administration - Business Office Technical Infrastructure - Data Center Operations CRM - Telephone Services
Austin
Todd
Network Engineering and Design
Avery
Kathleen
Enterprise Applications - Kuali
Babbitt
John
Network Engineering and Design
Bachand
Jane
Bacon
Andrew
Baglan
Lily
ITQ & DM - Service Management Enterprise Applications - Web Application Development Technical Infrastructure - Data Center Operations
17
X
X
X
X
Emergency Operations Plan
Last
First
Work Area
Director
Baker
Doug
Baker
Linda
Technical Infrastructure - Linux Server Support CRM - User Services
Bardot
Marybeth
CRM - User Services
Bassett
Laurie
Bazzani
Janice
Bhatt
Rushikuma
Bhunia
Girija
Blessington
John
Boggis
Joshua
Bordick
Lara
Brown
Eileen
Bull
Nancy
Caprera
Linda
Carcano
Raymond
Carpenter
Melinda
Carty
Andrew
Casaol
Herman
Case
William
Cavanaugh
Michelle
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Teal
Smith
X
Sorrentino
Meinweiser
X
Sorrentino
Meinweiser
X
CRM - Telephone Services Enterprise Applications - Training & Communications Enterprise Applications - WDIT University Applications ITQ & DM - Data Warehousing Technical Infrastructure - Data Center Operations Technical Infrastructure - Unified Comm. Server Support Enterprise Applications - WDIT FAMIS Network Engineering and Design
Sorrentino RomanoConnors RomanoConnors Garcia
Meinweiser
X
Wisniewski
X
Kazerounian
X
Garcia
X
Teal
Desautels
Teal
Teal
X
Kazerounian
X
Williams
X
VP and CIO Enterprise Applications PeopleSoft Connecticut Education Network Network Operations Administration - HR
Choi RomanoConnors
Choi
X
Wisniewski
X
Taylor
Taylor
X
Bull
Enderle
X
Sorrentino
Sorrentino
X
Teal
Wrynn
X
Teal
Desautels
X
Garcia
McBrien
X
Wisniewski
X
Teal
X
Enderle
X
Kriedeman
X
RomanoConnors Babbitt
X
X
Ceccarelli
Gail
Cerrigione
Christopher
CRM - User Services Technical Infrastructure Windows Server Support Technical Infrastructure Computer Scheduling ITQ & DM - Reporting Tool Support Enterprise Applications - Change Control and Bundling CIO - vPC
Chartier
Carolyn
Administration - HR
Chudnow
David
Enterprise Applications - Kuali
Copley
Georgianne
ITQ & DM - IT PMO
Bull RomanoConnors Garcia
Garcia
X
Costanzo
Lorraine
Security - Administrative Support
Pufahl
Pufahl
X
Czemske
Christine
Administration - Business Office
Bull
Irmscher
X
Dean
Philip
Sorrentino
X
Jason
Teal
Wrynn
X
DelGrego
William
CRM - User Services Technical Infrastructure Windows Server Support Network Engineering and Design
Sorrentino
Deary
Babbitt
Farese
X
DePalma
Andrew
Garcia
Garcia
X
Desautels
Jo-Ann
Teal
Teal
X
Deschenes
Ellen
Teal
Allison
X
Desloge
Cindy
Bull
Irmscher
X
Desmarais
Paul
Teal
Teal
X
Desmarais
Kathleen
Dexter
Marie
RomanoConnors RomanoConnors
RomanoConnors RomanoConnors
DiGrazia
Mick
ITQ & DM - Service Management Technical Infrastructure Scheduling, Ops & Data Center Infra. Technical Infrastructure Enterprise Storage Administration - Business Office Technical Infrastructure Mainframe Server Support Enterprise Applications Administrative Support Enterprise Applications Mainframe Application Support Security - Awareness and Compliance
Pufahl
Pufahl
18
RomanoConnors Bull
X X X
Emergency Operations Plan
Last
First
Work Area
Director
Do
Cuong
Enterprise Applications - FAMIS
Donovan
Janine
Dunnigan
Brian
Dupont
Christopher
Dziekan
Richard
RomanoConnors Bull RomanoConnors
X
Irmscher
X
Kazerounian
X
Teal
Gwinnell
X
Teal
Desautels
Elwell
Valorie
Enderle
Laurie
Erickson
Doug
Network Engineering and Design
Babbitt
Farese
Jeffrey
Network Engineering and Design
Farnham
Thomas
CRM - User Services
Farrands
Danielle
Fazzina
Angelo
Fatu
Vlad
Ferretti
Matthew
Administration – Business Office Technical Infrastructure - Unified Comm. Server Support Network Engineering and Design Technical Infrastructure Computer Scheduling Enterprise Applications - WDIT University Applications Technical Infrastructure Mainframe Server Support Security - Disaster Recovery Enterprise Applications PeopleSoft
Veronica
Flynn
Nancy
Font
Victor
Garcia
Lisa
Garcia
RomanoConnors Bull
Bull
X
Nye
X
Babbitt
Babbitt
X
Sorrentino
Meinweiser
X
Bull
Irmscher
Teal
Boggis
X
Babbitt
Babbitt
X
Teal
Desautels
X
RomanoConnors
Kazerounian
X
Teal
Desmarais
X
Pufahl RomanoConnors
Pufahl
X
Wisniewski
X
RomanoConnors
X
Kazerounian
X
Kriedeman
X
Bull RomanoConnors J. Pollack
X
Teal
Desautels
X
Teal
Teal
X
Babbitt
Farese
X
Teal
Gwinnell
X
Babbitt
Nye
X
Teal
Desmarais
X
Taylor
Taylor
X
Kazerounian
X
Wisniewski
X
Bull
Garrett
Steven
Enterprise Applications - WDIT HuskyCT
Gedarovich
James
Enterprise Applications - Kuali
Ghaemolsabahi
Haleh
Gile
Maryann
Gill
Jonathan
RomanoConnors RomanoConnors Bull RomanoConnors Teal
Gunn
Gregory
Gwinnell
John
Hamley
Jason
Hammond
John
Hanyckyj
Elijah
Harland
Lawrence
Harris
Sheila Louis
Hernandez
Kathryn
Herrara
Byron
Hoddy
Nancy
Hoel
Ross
Administration - Business Office
Hogan
Jo-Anne
CRM - User Services
19
X X
ITQ & DM
Herman
X
Wisniewski
Michael
CIO Enterprise Applications - Data Management Services Technical Infrastructure - vPC Technical Infrastructure Computer Scheduling Technical Infrastructure - Unix Server Support Network Engineering and Design Technical Infrastructure - Unix Server Support Network Engineering and Design Technical Infrastructure Mainframe Server Support Connecticut Education Network Marketing and Outreach Enterprise Applications - WDIT Workflow/Mobile Development Enterprise Applications PeopleSoft - CS Special Projects Technical Infrastructure - Data Center Operations CRM - Telephone Services
Ad Hoc Emergency / As Needed
Kazerounian
Administration - Business Office Enterprise Applications - WDIT Web Application Development Technical Infrastructure - Unix Server Support Technical Infrastructure - Data Center Infrastructure Enterprise Applications PeopleSoft Administration - HR
Ferriss
Manager
Ad Hoc Emergency / Must Report
RomanoConnors RomanoConnors
X X
Teal
Desautels
X
X
Sorrentino
Meinweiser
X
Bull
Irmscher
X
Sorrentino
Meinweiser
X
Emergency Operations Plan
Last
First
Work Area
Director
Kristy
Enterprise Applications - WDIT Workflow/Mobile Development Enterprise Applications PeopleSoft CIO - Administrative Support
RomanoConnors RomanoConnors Bull
Denise
Administration - Business Office
Jackson
Linda
Enterprise Applications - Kuali
Bull RomanoConnors
Jancewicz
Russell
Hu
Ying
Huber
Richard
Hughes Irmscher
Technical Infrastructure - Linux Server Support Enterprise Applications - Web Application Development Technical Infrastructure Mainframe Server Support
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Kazerounian
X
Wisniewski
X
Bull
X
Bull
X
Kriedeman
X
Teal
Smith
X
RomanoConnors
Kazerounian
X
Teal
Desmarais
X
RomanoConnors Williams
Jatkowski
Musa
Johnson
Julie
Kazerounian
Jila
Enterprise Applications - WDIT
Keegan
Glenn
Network Engineering and Design
RomanoConnors Babbitt
Kent
Robert
Network Engineering and Design
Babbitt
Farese
X
Khairallah
John
Babbitt
Williams
X
Khairallah
Meghan
Teal
Boggis
X
Kocsondy
Ryan
Network Engineering and Design Technical Infrastructure - Unified Comm. Server Support West Hartford Operations
Pamela
Enterprise Applications - Kuali
Bull RomanoConnors
X
Kriedeman
Bull RomanoConnors RomanoConnors
Wisniewski
X
Pufahl
Pufahl
X
Garcia
McBrien
X
Gile
X
Rodriguez
X
Kazerounian
X
Kwon
Bruce
Lang
Michael
Long
Michael
Loux
Jonathan
Lovelace
Maurice
Enterprise Applications PeopleSoft Security - Network and Information ITQ & DM - Reporting Tool Support Enterprise Applications - Data Management Services ITQ & DM - Service Management
Lowe
Janet
Enterprise Applications - WDIT
Lysak
Keith
MacDonald
Neil
Madam
Kiran
Mandeville
James
Maresca
Steve
Marquis
Dylan
Technical Infrastructure - Data Center Operations Network Engineering and Design
RomanoConnors Garcia RomanoConnors Teal
Desautels
X X
X
X
X
Babbitt
Williams
X
Garcia RomanoConnors
Garcia
X
Dexter
X
Pufahl
Pufahl
X
Teal
Smith
X
Gile
X
Wisniewski
X
Garcia
McBrien
X
Marquis
Joan
Masso
James
McBrien
Terrence
McCormick
David
ITQ & DM - Data Warehousing Enterprise Applications Mainframe Applications Security - Network and Information Technical Infrastructure - Linux Server Support Enterprise Applications - Data Management Services Enterprise Applications PeopleSoft ITQ & DM - Reporting Tool Support ITQ & DM - PMO
Garcia
Garcia
X
McNamara
Thomas
Network Engineering and Design
Babbitt
Williams
X
Meinweiser
Patricia
X
Ruben
Kazerounian
X
Metivier
Pamela
Wisniewski
X
Mikolinski
Lisa
Sorrentino RomanoConnors RomanoConnors Sorrentino
Sorrentino
Mercado
Customer Relations Management Enterprise Applications - WDIT University Applications Enterprise Applications PeopleSoft CRM - User Services
Sorrentino
X
20
RomanoConnors RomanoConnors
Emergency Operations Plan
Last
First
Work Area
Director
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Millan
Veronica
CRM - User Services
Sorrentino
Sorrentino
X
Miller
June
Sorrentino
Meinweiser
X
Mindek
James
Taylor
Taylor
X
RomanoConnors
Wisniewski
X
Taylor
Taylor
X
Teal
Gwinnell
X
Miras-Alonso
Enrique
Morales
Rafael
Morin
Pierre
Morrell
Robert
CRM - User Services Connecticut Education Network Marketing and Outreach Enterprise Applications PeopleSoft Connecticut Education Network Network Operations Technical Infrastructure - Unix Server Support CRM - User Services
Sorrentino
Sorrentino
X
Msaddi
George
CRM - User Services
Sorrentino
Sorrentino
X
Nguyen
Van
CRM - User Services
Sorrentino
Sorrentino
X
Norris
Joel
X
Antoinette
Wisniewski
X
Nye
Lance
Babbitt
X
Oatley
Michael
Bull RomanoConnors Babbitt RomanoConnors
Kocsondy
Nunes
Kazerounian
X
O'Connor
Ryan
Sorrentino
Sorrentino
X
O'Donnell
Diana
Garcia
Garcia
X
Orcutt
Michael
Teal
Allison
X
Pagano
Andrew
Babbitt
Williams
X
Pai
Sandhya
Teal
Smith
X
Parciak
Paul
Teal
Desautels
X
Pare
Suzanne
West Hartford Operations Enterprise Applications PeopleSoft Network Engineering and Design Enterprise Applications - WDIT Workflow/Mobile Development Customer Relations Support User Services ITQ & DM - PMO Technical Infrastructure Enterprise Storage Network Engineering and Design Technical Infrastructure - Linux Server Support Technical Infrastructure - Data Center Infrastructure CRM - User Services
Sorrentino
Sorrentino
X
Patel
Ronak
Bull
Kocsondy
X
Pelletier
Daniel
Teal
Desautels
X
Pennington
Michael
Taylor
Taylor
X
Pomerleau
Armand
West Hartford Operations Technical Infrastructure - Data Center Infrastructure Connecticut Education Network Network Operations Network Engineering and Design
Babbitt
Williams
X
Portuguez
Rick
CRM - User Services
Sorrentino
Sorrentino
X
Postler
Dale
Network Engineering and Design
Babbitt
Williams
X
Pufahl
Jason
Bull
Bull
X
Raczkowski
Melanie
Taylor
Taylor
X
Radziwillowicz
Anna
Security Connecticut Education Network Business Operations ITQ & DM - PMO
Garcia
Garcia
X
Rae
Laurel
CRM - Telephone Services
Meinweiser
X
Raines
David
Enterprise Applications - Kuali
Sorrentino RomanoConnors
Kriedeman
X
Taylor
Taylor
X
Teal
Smith
X
Garcia
Garcia
X
Bull
X
Kazerounian
X
Kazerounian
X
Sorrentino
X
Rego
Wendy
Rifkin
Jonathan
Rodriguez RomanoConnors
Sherry
Connecticut Education Network Business Operations Technical Infrastructure - Linux Server Support ITQ & DM - Service Management
Debora
Enterprise Applications
Bull
Rowland
Robert
Roy
Joshua
Roy
Mark
Enterprise Applications - WDIT University Applications Enterprise Applications - WDIT Web Application Development ITQ & DM - PMO
RomanoConnors RomanoConnors Sorrentino
21
Emergency Operations Plan
Last
First
Saba
Mitchell
Sanku
Sirisha
Schaffhauser
John
Sevilla
Elena
Shiling
Benjamin
Simmon
Kelli
Simon
Richard
Slonski
Shawn
Smith
Matthew
Sorrentino
Katherina
Soucy
Kevin
Stedman
Jill
Work Area
Director
Enterprise Applications - Kuali
RomanoConnors RomanoConnors RomanoConnors
Manager
Ad Hoc Emergency / Must Report
Ad Hoc Emergency / As Needed
Kriedeman
X
Wisniewski
X
Wisniewski
X
Teal
Smith
X
Babbitt
Nye
Babbitt
Farese
X
Teal
Wrynn
X
Babbitt
Williams
Teal
Teal
X
Bull
Bull
X
Teal
Desautels
X
Teal
Desautels
X
Gile
X
Stone
Nancy
Sulamn
Gregory
Enterprise Applications PeopleSoft Enterprise Applications PeopleSoft Technical Infrastructure - Linux Server Support Networking – Audio Visual Services Network Engineering and Design Technical Infrastructure Windows Server Support Network Engineering -- PIP Technical Infrastructure - Linux Server Support Customer Relations Management Technical Infrastructure - Data Center Operations Technical Infrastructure Computer Scheduling Enterprise Applications - Data Management Services Network Engineering and Design
Williams
X
Taylor
Patrick
CRM - User Services
Sorrentino
Sorrentino
X
Taylor
Scott
Connecticut Education Network
Bull
Bull
X
Teal
Richard
Bull
X
Joseph
Teal
Wrynn
X
Tomecko
Constance
Garcia
McBrien
X
Volkert
William
X
Hengameh
Kazerounian
X
Waleszczyk
Tammy
Wisniewski
X
Warren
Constance
Babbitt RomanoConnors RomanoConnors Sorrentino
Williams
Vosough
Technical Infrastructure Technical Infrastructure Windows Server Support ITQ & DM - Reporting Tool Support Network Engineering and Design Enterprise Applications - WDIT HuskyCT Enterprise Applications PeopleSoft CRM - User Services
Bull
Theriault
Meinweiser
X
Watrous
Michael
Network Engineering and Design
Nye
X
Weingart
Richard
Enterprise Applications - Kuali
Kriedeman
X
Wentworth
Robert
Kocsondy
X
Wiggins
Mark
Teal
Smith
X
Williams
Michael Angie
Woodaman
Brien
Babbitt RomanoConnors Babbitt
Babbitt RomanoConnors Nye
X
Wisniewski
Wrynn
John
Teal
Teal
X
Wu
Shuihua
West Hartford Operations Technical Infrastructure - Linux Server Support Network Engineering and Design Enterprise Applications PeopleSoft Network Engineering and Design Technical Infrastructure Windows Server Support Enterprise Applications - WDIT Workflow/Mobile Development
Babbitt RomanoConnors Bull
RomanoConnors
Kazerounian
X
Zhang
Yi
RomanoConnors
Kazerounian
X
Enterprise Applications - WDIT Web Application Development
22
RomanoConnors Babbitt
X X
Emergency Operations Plan
Document Change History DOCUMENT CHANGE HISTORY Plan Version No. Ver. 1.0/ Rev. 01
Release Date
Summary of Changes
Section No./ Paragraph No.
Changes Made By
01/15/13
Initial Draft
Entire Document
BCP/DR Coordinator
Ver. 1.0/ Rev. 02
02/13/13
Added learning items from Blizzard of 2013. (Nathan Hale meals, parking, and MSB building security)
Entire Document
BCP/DR Coordinator
Ver. 1.0/ Rev. 03
03/04/2013
Updated during table top exercise Entire Document
BCP/DR Coordinator
23
