Information Services
Disaster Response and Recovery Plan
Central Washington University
400 East University Way
Ellensburg, Washington 98926-7436
509.963.2333
Updated by
Networks & Operations
Updated October 2013
Revision History Page
Rev #
1
2
2.1
2.2
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
3.8
3.9
Change
Initial Release DRP - Networks & Operations
Update DRP - Networks & Operations
Reviewed DRP - Networks & Operations
Reviewed DRP - Networks & Operations
Rewrite of DRRP - Networks & Operations
Minor Updates DRRP - Networks & Operations
Updated Personnel Names DRRP – Networks &
Operations
Minor Updates DRRP – Networks & Operations
Personnel Updates – Networks & Operations
New Recovery Team -- Networks & Operations
Staffing, Building Updates – Networks & Operations
Staffing Updates – Networks & Operations
Staffing Updates – Networks & Operations
Department Renamed – Networks & Operations
Date
1-Jun-1993
1-Nov-1996
2-Aug-2008
3-Aug-2008
6-Mar-2008
6-Aug-2008
7-Apr-2008
7-Aug-2008
8-Feb-2008
14-Apr-2008
August-2009
January-2012
August-2013
September-2013
Official copies of this document are located at the following locations:
-
Information Services Department Office
Computer Support Services Managers Office
Central Computer Facility Operations Office
Hebeler Tape Vault
Office and Home of AVP for Information Technology
Network and Operations Directors Office
IT Security Administrators Office
2
NAMES
Alviso, Jose
Dept.
N&O
NUMBER
1743
Andrin, Marion
Aux
1891
Anderson, Lidia
Ashbrooks,
Steve
Beintema, Jami
EAS
3046
Telecom
IS
3442
2333
Beintema, Larry
Breckon, Ron
Brower, Doug
Brown, Rock
Burk, Nicole
Carlson, Barry
Case, Felicia
N&O
N&O
EAS
EAS
EAS
EAS
Aux
2905
3694
2356
2999
3046
2904
2903
Cathcart, Jason
N&O
1223
Cusumano, Pete
DeLuca, Greg
Dohrman, Gayle
Douglas, Steven
Firman, Marla
Gerdes, Jason
Germain, Dave
Germain, Terilee
Gladen, Jeff
Glessner, Bill
Haberman,
Susie
Halvorson,
Colleen
Hart, David
Hendrickson,
Teri
Hernandez, Uriel
Hernandez, Jill
Hill, Nathan
Herrera, Steven
CaTS
N&O
EAS
N&O
CSS
N&O
CSS
N&O
CSS
N&O
3834
2970
3054
1232
1250
2995
2996
2946
1606
3694
EAS
2944
Hunt, Debbie
Hutchins, Lynn
Jackson, Nancy
Jakeman, Jared
Jones, Frank
Jones, Keith
Klampher, Tina
Knackstedt, Jeff
Lei, Vera
Lunstrum,
Lucinda
McGuire, Tim
Miller, Bill
Osguthorpe,
Jared
Patterson,
Randy
Pierce, Tad
Pratz, Chris
Pruitt, Jim
Shoda, Gene
CaTS
N&O
3499
2932
Telecom
EAS
EAS
Aux
EAS
3422
2967
1268
2942
1209
EAS
EAS
Telecom
EAS
CaTS
Proj.
Mgmt.
CSS
CSS
EAS
Cell Phone
Dept.
EAS
NUMBER
3048
Varga, Steve
EAS
2953
Vincent, Kathy
CSS
2544
899-1865
Wang, Crystal
Wang, Xinbao
EAS
EAS
2643
2945
899-0347
Webber, Maury
Wixson, Heidi
Young, Ken
CaTS
EAS
CaTS
3752
2969
3491
425-471-1593
859-2884
856-6581
859-1112
431-5030
899-1696
899-0999
NAMES
Velasquez, Charles
OTHER IMPORTANT NUMBERS
ISD Main Directory
(Direct
ISD Help Desk
1102)
ISD - Main Office Front
Desk
MS 7436
ResNet Help Desk
Aux. Services
MS 7589
Computer Center
MS 7444
Telecommunications
MS 7437
Telephone Repair Line
Conference Room
IT Project Room
ISD Auto Attendant
Blackboard
TDD
206-218-6541
(P)
509-306-2128
Cell Phone
859-3986
425-4711227
2924
2001/3491
2333
2200
2936
3694
3425
2007
1645
1477
2924
2001
3323
PPP Dial-in Modem
VAX Dial-in Modem
8000
3998/3999
FAX NUMBERS
ISD
CSS & CaTS
Telecommunications
1385
2445
1241
BUILDING MONITORS
Sandy Sperline (Bouillon Hall - 2nd floor)
Ron Breckon (Computer Center)
2989
3694
112/128 STUDENTS/TEMPS
CSS Student
Student (Help Desk )
3376
3043
202 STUDENTS/TEMPS
Student (Front Office)
2769
3015
2288
3333
1615
2856
2191
2778
2352
2972
EAS
EAS
CSS
2626
2329
3490
EAS
2954
Telecom
Aux
CS
CSS
AVPIS/CIO
3653/3649
2997
1581
3472
2777
899-0136 BB
856-6219 BB
899-4818
899-2827
899-0092
899-3220
899-0145
ResNet
ResNet Help
2200
3
Richardson,
Wade
Ringer, Jason
Rodriguez, Noah
Shelton, Debby
Smith, Zachary
Sperline, Sandy
Swayze, Stacy
Thomas, Jamie
Timmons, Chris
Tran, Kim
Telecom
EAS
N&O
Telecom
N&O
CSS
CSS
EAS
N&O
EAS
3424
2394
2934
3428
2864
2989
1572
1205
2947
2994
856-6867
626-393-4069
607-4756
607-1618
856-7894
4
Information Services (IS Department)
Disaster Response and Recovery Plan
TABLE OF CONTENTS
Section
1
2
3
4
Title
Introduction
Scope
Assumptions
Definitions
Page
5
5.1
5.2
5.3
5.4
5.5
5.6
5.7
5.8
Team Members and Contact Information
Aux Services Recovery Team
Data Center Recovery Team
Desktop Recovery Team
Messaging/Networks & Web Recovery Team
PeopleSoft Recovery Team
ResNet Recovery Team
Telecommunications Recovery Team
CWU Critical Support Contacts
6
6.1
6.2
6.3
6.4
6.5
7
Disaster Preparedness
Data Recovery Information
Central Data Center and Server Recovery Information
Network and Telecommunication Recovery Information
Application Recovery Information
Desktop Equipment Recovery Information
Disaster Recovery Processes & Procedures
7.1
7.2
7.3
7.4
8
Emergency Response
Incident Command Team
Disaster Recovery Teams
General System Application Recovery
Network and Telecommunication Guidelines
19
19
20
20
20
20
21
21
21
22
25
27
A
B
C
D
E
F
G
H
J
K
L
Appendices
IT Directory and Contact List
CWU Critical Contacts
Asset Management Information
Backup Tape Retention Periods
Recovery Priority List
Vendor Information
Network Diagrams
Excerpt from Emergency Preparedness Plan
Business Impact Matrix
Threat and Vulnerability Matrix
Tape Inventory
28
30
31
32
35
39
47
48
50
51
53
5
6
7
8
10
11
12
13
14
15
16
17
18
5
1.0 INTRODUCTION
Central Washington University is a four year institute of higher education. Faculty, staff and students all rely
heavily on the Information Technology (IT) infrastructure and services to accomplish their jobs, and as an
integral part of the learning environment/curriculum at the university.
As a result of this reliance, IT services are considered a critical component in the daily operations at Central
Washington University, requiring a comprehensive Disaster Response and Recovery Plan (DRRP) to assure
that these services can be re-established quickly and completely in the event of a disaster of any magnitude.
Response to and recovery from a disaster at Central Washington University is managed by the Emergency
Council Members, named in section 2 of the Emergency Preparedness Plan. Their actions are governed by
the Central Washington University Safety and Emergency Preparedness plan located at
http://www.cwu.edu/police/sites/cts.cwu.edu.police/files/documents/safetyatcwubrief.pdf.
This IT DRRP presents the requirements and the steps that will be taken in response to and for the recovery
from any disaster affecting IT services at Central Washington University, with the fundamental goal of allowing
basic business functions to resume and continue until such time as all systems can be restored to pre-disaster
functionality.
At this time Central Washington University does not run on redundant servers which would minimize potential
business disruption in the event of a disaster, nor does the university possess a redundant “warm-site” or “hotsite” for quick recovery of the Data Center. Should more resources become available this plan will be reevaluated and updated accordingly.
This plan is reviewed and updated yearly by August by IS/Networks & Operations staff and approved
by the Assistant VP for Information Technology.
A hard copy of this plan is stored in the following areas:
- Hebeler vault
- IS/Networks & Operations (Terilee Germain’s Office)
- Bouillon 218 Comm Room
- Computer Center
- Auxiliary Wall Safe
6
2.0
SCOPE
Due to the uncertainty regarding the magnitude of any potential disaster on the campus, this plan will
only address the recovery of systems under the direct control of the Department of Information
Technology Services and that are critical for business continuity. This includes the following major
areas:






PeopleSoft Systems (payroll, AP/AR, financial aid, finance, safari)
Central Computer Facility (Wildcat Shop)
Electronic Mail and Web Services
Desktop Equipment, Labs, Classrooms
Data Networks and Telecommunications (networks, file services, telephony)
Auxiliary Computing (Conference Center, Facilities, Parking, University Store, CBORD Dining
Services, Housing, Health, ResNet, Student Recreation)
This plan covers all phases of any IT related disaster occurring at Central Washington University.
These phases include:




Incident Response
Assessment and Disaster Declaration
Incident Planning and Recovery
Post incident Review
At this time Central Washington University does not run on redundant servers nor possess a
redundant “warm-site” or “hot-site” for training or testing purposes. Should these resources become
available this plan will be updated to fully detail training and testing of this plan.
7
3.0
ASSUMPTIONS
This disaster response and recovery plan is based on the following assumptions:

Once an incident covered by this plan has been declared a disaster, the appropriate priority will be
given to the recovery effort and the resources and support required as outlined in the IT DRRP will be
available.

The safety of students, staff and faculty are of prime importance and the safeguard of such will
supersede concerns specific to hardware, software and other recovery needs.

Depending on the severity of the disaster, other departments/divisions on campus may be required to
modify their operations to accommodate any changes in system performance, computer availability
and physical location until a full recovery has been completed. Information Technology Services will
encourage all other departments to have contingency plans and Business Continuity Plans for their
operations, which include operating without IT systems for an extended period of time.

The content of this plan may be modified and substantial deviation may be required in the event of
unusual or unforeseen circumstances. These circumstances are to be determined by the specific
Disaster Response and Recovery Teams under the guidance and approval of the Incident Director and
Incident Command Team.
8
4.0
DEFINITIONS: The following definitions pertain to their use in this IT Disaster Recovery Plan.
Auxiliary Services Recovery
Team:
Individuals responsible for the recovery and testing of Auxiliary Computing
technology. Team lead is the Manager of Auxiliary Computing. (Nathan
Hill)
Backup/Recovery Tapes:
Copies of all software and data located on the central servers, which are
used to return the servers to a state of readiness and operation that existed
shortly prior to the incident/disaster.
Catastrophic Disaster:
A catastrophic disaster will be characterized by expected downtime of
greater than 7 days. Damage to the system hardware, software, and/or
operating environment requires total replacement / renovation of all
impacted systems.
Cold Recovery Site:
Alternate Data Center which has adequate power and networking
infrastructure to support the critical IT systems used by the university. A
cold site does not have backup servers and other IT equipment and
software already in place. CWU does not have a designated Cold Recovery
Site at this time.
Database Recovery Team
Individuals responsible for the recovery and testing of CWU Databases.
Team lead is DBA Admin. (Vacant)
Data Center Recovery Team:
Individuals responsible for the establishment of an operational data center,
either by returning the primary center to operational status or by bringing a
Cold Site online for use. Team lead is the Director of Networks and
Operations. (Jason Cathcart)
Desktop Recovery Team:
Individuals responsible for the recovery and testing of desktop computers
and services, classrooms and labs in the affected areas at Central
Washington University. Team lead is the Manager of Computer Support
Services. (Chris Pratz)
Disaster Recovery Team
(DRT):
The DRT is a team of individuals with the knowledge and training to recover
from a disaster. For IS, there are 6 teams for specific IT areas to be
addressed.
Disaster:
Any IT incident which is determined to have potential impacts on the
business continuity and ongoing operations of Central Washington
University.
Emergency Response Team
(ERT):
The ERT is the first to respond to an incident, to secure and contain the
situation. The ERT may consist of firemen, police, security, and other
specialized individuals.
Equipment Configuration
Database:
A database (either soft or hardcopy) which documents the configuration
information necessary to return any IT hardware (server, network, desktop)
to pre-disaster configurations. This includes hardware revisions, Operating
System revisions, and patch levels.
Incident Command
Headquarters
Location where the ICTs meet and coordinate all activities with regard to
assessment and recovery. For the CWU IS Department, the headquarters
are located at:
Primary: IS Conference Room (Bou-202)
Secondary: Barge Conference Room (Barge 412)
Backup 1: Library Classroom Lab (Lib 154)
Backup 2: Shaw Smyser Lab (SS214)
9
Incident Command Team
(ICT):
Incident Director (ID):
The ICT is a group of IT individuals with combined knowledge and expertise
in all aspects of the IT organization. It is the responsibility of the ICT to
perform the initial assessment of the damage, to determine if a formal
“disaster” declaration is required and to coordinate activities of the various
IT DRTs.
The Incident Director leads all efforts during the initial assessment of the
incident, in conjunction with the Incident Command Team (ICT). If a
disaster is declared, the ID is responsible for overall coordination of all IT
related recovery activities. For Central Washington University, the Incident
Director is the Assistant VP of Information Technology. (Gene Shoda)
Incident:
Any non-routine event which has the potential of disrupting IT services to
Central Washington University. An incident can be a fire, earthquake,
significant hardware failure, flood, volcano ash, virus, Trojan horse, etc.
Major Disaster:
A major disaster will be characterized by an expected downtime of more
than 48 hours but less than 7 days. A major disaster will normally have
extensive damage to system hardware, software, networks, and/or
operating environment.
Messaging/Networks & Web
Recovery Team:
Individuals responsible for the recovery and testing of messaging systems at
CWU including email, calendaring, and Web technologies. Responsible for
the recovery and testing of the data networks and file servers. Team lead is
the Director of Network and Operations. (Jason Cathcart)
Minor Disaster:
A minor disaster will be characterized by an expected downtime of no more
than 48 hours, and minor damage to hardware, software, and/or operating
environment from sources such as fire, water, chemical, sewer or power etc.
PeopleSoft Recovery Team:
Individuals responsible for the recovery and testing of the PeopleSoft
systems. Team lead is Director of Application Services. (Vacant)
Resnet Recovery Team:
Individuals responsible for the recovery and testing of the Resnet Services.
Team lead is the Director of Networks and Operations. (Jason Cathcart)
Routine Incident:
A routine incident is an IT situation/failure that is limited in scope and is able
to be addressed and resolved by a specific team or individual as part of their
normal daily operations and procedures. Incidents which are not of
magnitude to be classified as formal disasters and considered “routine”
incidents and are handled accordingly.
Telecommunications
Recovery Team:
Individuals responsible for the recovery and testing of voice networks.
Team lead is the Supervisor of Telecommunications. (Nancy Jackson)
Web Services:
All services related to Central Washington University’s Internet and Intranet
Web activities and presence. The primary Web Service provided by CWU is
the homepage at www.cwu.edu.
10
5.0
TEAM MEMBERS & CONTACT INFORMATION:
5.0.1 Incident Director:
Name:
Home Phone:
Cell Phone:
Home Email:
Gene Shoda
5.0.2 Incident Command Team: All Contact Information is located in Appendix A
Name:
Gene Shoda, Assistant VP for Information Technology
Jason Cathcart, Director Networks & Operations (Alternate
Incident Director)
Vacant, Director Enterprise Application Services
Chris Pratz, Manager of Computer Support Services
Nancy Jackson, Manager of Telecommunications
Nathan Hill, Manager of Auxiliary Computing
5.0.3 CWU Management Team: All Contact Information is located in Appendix B
Name:
James Gaudino, President CWU
Marilyn Levine, Provost/VP for Academic and Student Life
George Clark, VP for Business and Financial Affairs
John Swiney, VP for Student Affairs and Enrollment Management
Linda Schactler, VP for University Relations
11
5.1 AUXILIARY SERVICES RECOVERY TEAM:
All Contact Information is located in Appendix A
The Auxiliary Services Recovery Team is composed of the IT Specialists within Information Technology
Services that support the Auxiliary systems. The primary function of this small working group is the
restoration of the Auxiliary applications to the most recent pre-disaster configuration in cases where data or
operational loss is significant. In less severe circumstances the team is responsible for restoring the systems
to an operational status as necessitated by any hardware failures, network outages or other circumstances
that could result in diminished system performance.
The team should be mobilized in the event that the Auxiliary systems experiences a significant interruption in
service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess
of what is experienced on a normal day-to-day basis.
The Manager of Auxiliary Services has the responsibility to keep the IT Incident Director up to date regarding
the nature of the disaster and the steps being taken to address the situation. The coordination of the Auxiliary
Services recovery effort will be accomplished with other recovery efforts on campus by the IT Incident
Director.
System Name:
Housing
Dining (Kronos)
Computrition
CBORD
Facilities
Health
Resnet
Student Recreation
Store-POS
Conference Center
Work Order System Aux
Trade Book
Quasar.cts.cwu.edu
Nathan Hill (Recovery Team Lead)
Marion Andrin
Nathan Hill
Larry Beintema
Tad Pierce
Ed Castaneda
Nathan Hill
Nathan Hill, Felicia Case
Nathan Hill
Tad Pierce, Nathan Hill
Felicia Case
Nathan Hill
Nathan Hill
DBA Team
12
5.2 DATA CENTER Recovery Team:
All Contact Information is located in Appendix A
The Data Center Recovery Team is composed of personnel within Information Technology Services that
support Central Washington University’s central computing environment and the primary data center where all
central IT services, the Networks Operations Center (NOC) and other central computing resources are
located. The primary function of this small working group is the restoration of the existing data center or the
activation of the secondary data center depending on the severity of the disaster. This team’s role is to
restore the data center to a condition where individual recovery teams can accomplish their responsibilities
with regard to server installation and application restoration.
The team should be mobilized only in the event that a disaster occurs which impacts the ability of the existing
central computing facility to support the servers and applications running there.
The Director of Network and Operations has the responsibility to keep the IT Incident Director up to date
regarding the nature of the disaster and the steps being taken to address the situation. The coordination of
this recovery effort will normally be accomplished prior to most other recovery efforts on campus as having a
central computing facility is a prerequisite for the recovery of most applications and IT services to the campus.
System Name:
Operations Coordinator
Networks
Networks
Operations Support
Web Management
Netware Servers
Blackboard
Communications
Infrastructure
Jason Cathcart (Recovery Team
Lead)
Ron Breckon
Chris Timmons (Alternate Team Lead)
David Hart
Bill Glessner
Larry Beintema
Greg Deluca
Larry Beintema
Steve Ashbrooks
13
5.3 DESKTOP Recovery Team:
All Contact Information is located in Appendix A
The Desktop Recovery Team is composed of personnel within the Information Technology Department that
support Central Washington University’s desktop hardware, client applications, classrooms, labs and
academic development systems. The primary function of this small working group is the restoration of Central
Washington University’s desktop systems, classrooms and labs to usable condition. During the initial
recovery effort, the team is not responsible for restoration of any data the user may have on their desktop
computer. Central Washington University recommends all users store data files on the file servers, which are
backed up nightly, to support data recovery.
The team should be mobilized in the event that any component of the network or telecommunication
infrastructure experiences a significant interruption in service that has resulted from unexpected/unforeseen
circumstances and requires recovery efforts in excess of what is experienced on a normal day-to-day basis.
The Manager of Computer Support Services has the responsibility to keep the IT Incident Director up to date
regarding the nature of the disaster and the steps being taken to address the situation. The coordination of
this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.
System Name:
IT Specialist
IT Specialist/Primary
PCs
MACs
Labs
Classroom Technology
Alternates
Chris Pratz (Recovery Team Lead)
Dave Germain (Alternate Team
Lead)
Bill Miller
Tina Klampher
Jeff Knackstedt
Jim Pruitt, Jeff Knackstedt
Sandy Sperline
Stacy Swayze
14
5.4 MESSAGING/NETWORKS AND WEB Recovery Team:
All Contact Information is located in Appendix A
The Messaging/Networks and Web Recovery Team is composed of personnel within Information Technology
Services that support Central Washington University’s network infrastructure including all cable plants,
switches, routers, network applications, file servers, electronic email servers and web services. The primary
function of this small working group is the restoration of Central Washington University’s LAN and servers to
the most recent pre-disaster configuration in cases where data and network loss is significant. In less severe
circumstances, the team is responsible for restoring the system to an operational status as necessitated by
any network hardware failures or other circumstances that could result in diminished performance.
The team should be mobilized in the event that any component of the network infrastructure experiences a
significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires
recovery efforts in excess of what is experienced on a normal day-to-day basis.
The Director of Network and Operations has the responsibility to keep the IT Incident Director up to date
regarding the nature of the disaster and the steps being taken to address the situation. The coordination of
this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.
System Name:
Networks
Web Services
Email Services
Networks
Servers
Alternates
Cable Plants
Jason Cathcart (Recovery Team Lead)
Chris Timmons (Alternate Team Lead)
Larry Beintema
Bill Glessner
David Hart
Greg Deluca
Terilee Germain
Steve Ashbrooks
15
5.5 PEOPLESOFT Recovery Team:
All Contact Information is located in Appendix A/B
The PeopleSoft Recovery Team is composed of the IT Specialists within Information Technology Services that
support the PeopleSoft system as well as the User Application Specialists and a Network Specialist. The
primary function of this small working group is the restoration of all modules of the PeopleSoft application to
the most recent pre-disaster configuration in cases where data loss is significant. In less severe
circumstances the team is responsible for restoring the system to an operational status as necessitated by
any hardware failures, network outages or other circumstances that could result in diminished system
performance.
The team should be mobilized in the event that the PeopleSoft HRSA and/or FM systems experience a
significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires
recovery efforts in excess of what is experienced on a normal day-to-day basis.
The Director of Application Services has the responsibility to keep the IT Incident Director up to date regarding
the nature of the disaster and the steps being taken to address the situation. The coordination of the
PeopleSoft recovery effort will be accomplished with other recovery efforts on campus by the IT Incident
Director.
System Name:
DBA
DBA
PSApps
Security
Web Services
Payroll
HR
SA
FMS
Data Validation:
Admissions
HR/Payroll
SA
FMS
Vacant (Recovery Team Lead)
Jason Ringer (Alternate Team Lead)
Jason Osguthorpe
Jamie Schademan
Larry Beintema
Susan Haberman
Crystal Wang
Kathy Gaer
Adrian Naranjo
Jillian Hernandez, Tami Morrill
Tim McGuire
16
5.6 RESNET SERVICES RECOVERY TEAM:
All Contact Information is located in Appendix A
The Resnet Services Recovery Team is composed of the IT Specialists within Information Technology
Services that support the Resnet services. The primary function of this small working group is the restoration
of the Resnet services to the most recent pre-disaster configuration in cases where data loss is significant. In
less severe circumstances the team is responsible for restoring the networks to an operational status as
necessitated by any hardware failures, network outages or other circumstances that could result in diminished
system performance.
The team should be mobilized in the event that the Resnet services experiences a significant interruption in
service that has resulted from unexpected/unforeseen circumstances and requires recovery efforts in excess
of what is experienced on a normal day-to-day basis.
The Director of Networks and Operations has the responsibility to keep the IT Incident Director up to date
regarding the nature of the disaster and the steps being taken to address the situation. The coordination of
the Resnet Services recovery effort will be accomplished with other recovery efforts on campus by the IT
Incident Director.
System Name:
Networks
Auxiliary Services
Telecom
Nathan Hill (Recovery Team Lead)
Chris Timmons, Jason Gerdes
Nathan Hill, Jose Alviso
Nancy Jackson, Randy Patterson
17
5.7 TELECOMMUNICATIONS Recovery Team:
All Contact Information is located in Appendix A
The Telecommunications Recovery Team is composed of personnel within the Information Technology
Department that support Central Washington University’s voice networks. The primary function of this small
working group is the restoration of Central Washington University’s voice networks to the most recent predisaster configuration in cases where voice network loss is significant. In less severe circumstances, the team
is responsible for restoring the voice network to an operational status as necessitated by any failures or other
circumstances that could result in diminished performance.
The team should be mobilized in the event that any component of the network infrastructure experiences a
significant interruption in service that has resulted from unexpected/unforeseen circumstances and requires
recovery efforts in excess of what is experienced on a normal day-to-day basis.
The Manager of Telecommunications has the responsibility to keep the IT Incident Director up to date
regarding the nature of the disaster and the steps being taken to address the situation. The coordination of
this recovery effort will be accomplished with other recovery efforts on campus by the IT Incident Director.
System Name:
PBX
Networks
Networks
Nancy Jackson (Recovery Team Lead)
Randy Patterson (Alternate Team Lead)
Wade Richardson
Steve Ashbrooks
18
5.8 CWU CRITICAL SUPPORT CONTACTS:
All Contact Information is located in Appendix B
On Campus Contacts:
President's Office
Provost
Business and Financial Affairs
Student Affairs and Enrollment Management
University Relations
Facilities Management
Public Safety and Police Services
Health Center
University Housing
James Gaudino, President
Marilyn Levine, VP
George Clark, VP
John Swiney, VP
Linda Schactler, VP
Bill Yarwood, Bob Tosch,
Michael Luvera, Director
Jackson Horsley, Medical Director
Richard DeShields, Director
Off Campus Contacts:
Fairpoint Communications
K20 Administrative Contact
City of Ellensburg (Inet)
K20 Internet Circuit
Charter Communications
K20 Point-To-Point Circuits
Bill Malasich, Patrick Murphy
Steve Paulson
Bob Johnson
noc@wa-k20.net
Ron Graaff
Washington State DIS Helpdesk
19
6.0
DISASTER PREPAREDNESS
A critical requirement for disaster recovery is ensuring that all necessary information is available to assure that
hardware, software, and data can be returned to a state as close to “pre-disaster” as possible. Specifically,
this section addresses the backup and storage policies as well as documentation related to hardware
configurations, applications, operating systems, support packages, and operating procedures.
6.1 Data Recovery Information:
Backup/Recovery disks and tapes are required to return systems to a state where they contain the information
and data that was resident on the system shortly prior to the disaster. At Central Washington University full
backups of all servers are performed weekly. Those servers not in the full backup list have an incremental
done. Backup/Recovery tapes are stored in the locations and for the retention periods outlined in Appendix D,
and are summarized in the table below:
Backup Period
Daily Backup
Weekly Backup
Monthly Backup
Yearly Backup
Storage Location
Backup Unit
Wildcat Shop
Central Washington University
Backup Unit
Wildcat Shop
Central Washington University
CWU Vault
Hebeler Hall
Central Washington University
CWU Vault
Hebeler Hall
Central Washington University
Authorized Personnel
Networks and Operations Personnel
Networks and Operations Personnel
Operations Personnel
Operations Personnel
NOTE: Central Washington University does not have systems in place to backup and restore information/data located on individual
desktop systems throughout the campus. Only the servers located in the Data Center and auxiliary Data Centers are backed up, as
such only data resident on these systems will be able to be recovered. In the event that a disaster occurs on the campus which
destroys personal computers, the information located on these computers will be extremely difficult or impossible to recover. If
recovery is possible, it will require outside vendor involvement at great expense to the user.
The Information Technology Services recommends and will encourage the use of network drives (on servers) to store all important
files. The recovery of data not backed up to a network drive and/or full system backups are not covered under this plan.
A cloned disaster recovery backup unit is in place in Bouillon 218 in a secured and alarmed communications
room. This unit is for the purpose of off-site cloning of tapes. Networks & Operations Staff is responsible for
the daily cloning of tapes for the purpose of disaster recovery.
20
6.2 Central Data Center and Server Recovery Information:
In the event of any disaster which disrupts the operations in the Data Center, reestablishing the Data Center
will be the highest priority and a prerequisite for any IT recovery. As such, Information Technology Services is
required to have detailed information and records on the configuration of the Data Center and all servers and
ancillary equipment located in the Data Center and auxiliary Data Center located in the SURC building.
Detailed information is documented in the online database located at
http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied monthly to CD and
stored in the Hebeler vault with the backup tapes. The operations staff is responsible for keeping the
hardware inventory up to date.
6.3 Network & Telecommunication Recovery Information:
In the event of any disaster which disrupts the network and/or telecommunications, reestablishing the
connectivity and telephony will be a high priority and a prerequisite for any IT recovery. Recovery of these
services will be accomplished in parallel or immediately following recovery of the Data Center. As such,
Information Technology Services is required to have detailed information and records on the configuration of
the networking equipment. Detailed information of switches and routers is documented in the online database
located at http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied monthly to
CD and stored in the Hebeler vault with the backup tapes. The networking staff is responsible for keeping the
networking inventory up to date.
6.4 Application Recovery Information:
Information necessary for the recovery and proper configuration of all application software located on the
central servers is critical to assure that applications are recovered in the identical configuration as they existed
prior to the disaster. Detailed information on critical central applications will be documented in the online
database located at http://www.cwu.edu/~its/security/hardware.php. This database is updated and copied
monthly to CD and stored in the Hebeler vault with the backup tapes. Server administrators are responsible
for keeping the application inventory up to date.
6.5 Desktop Equipment Recovery Information:
Information necessary for the recovery and proper configuration of all desktop computers and printers
supported by Computer Support Services is critical to assure that client systems can be restored to a
configuration equivalent to pre-disaster status. Detailed information on client systems (both PC and MAC) is
documented at http://www.cwu.edu/~its/security. This web site is backed up nightly.
21
7.0
7.1
DISASTER RECOVERY PROCESSES AND PROCEDURES:
Emergency Response: The requirement for an Emergency Response Team (ERT) involvement and
the membership of the ERT will be dependent on the size and type of the incident. In addition, the
actions of the ERT will be accomplished prior to the execution of this plan. Examples of situations which
will normally result in the involvement of the ERT include:



Severe structural damage to the facility where personal safety is in question, and where analysis
must be completed to assure the building is acceptable for access. This would include, but is not
limited to, damage from an earthquake or tornado.
Environmentally hazardous situations such as fires, explosions, or possible chemical or biological
contaminations where the situation must be contained prior to building occupancy.
Flooding or other situations which may pose the risk of electrical shock or other life-threatening
situations.
Examples of situations which will normally not result in the involvement of the ERT include:


Major system/hardware failures that do not pose a hazard to personnel or property.
Utility outages (electrical, etc.) which are remote to the Data Center being affected.
NOTE: For any situation/incident which requires the involvement of an ERT; the IT Incident Director, Incident Command Team, nor
any Recovery Team member will access the facility until the ERT leader has authorized access. The Emergency Preparedness Plan
is located at: http://www.cwu.edu/~police/docs/emergency-preparedness-plan.pdf.
7.2 Incident Command Team: The role of the IT Incident Command Team (under the direction of the
Incident Director) is to coordinate activities from initial notification to recovery completion. Primary initial
activities of the team are:
Incident Occurrence: Upon the occurrence of an incident affecting the IT services at Central Washington
University, the President & Assistant Vice President of Information Technology will be notified by campus
security and/or other individuals. Personnel reporting the incident will provide a high-level assessment as
to the size and extent of the damage. Based on this information, the AVP of IT will assume his/her
responsibilities as the Incident Director, and will contact the other members of the ICT, and provide them
with the following basic information:




Brief overview of the incident, buildings affected, etc.
Which Incident Command Headquarters (ICH) will be used
Scheduled time to meet at the ICH for initial briefing
Any additional information beneficial at this point. No other staff members are to be contacted at
this point, unless directed by the Incident Director.
Incident Command Headquarters (ICH) locations are:




Primary ICH:
Secondary ICH:
Backup ICH 1:
Backup ICH 2:
IS Department Conference Room (Bouillon 202)
Barge Conference Room (Barge 412)
Library Classroom Lab (Library 154)
Shaw Smyser Lab (SS214)
Should all of these facilities be rendered unusable, it is assumed that the disaster was “catastrophic” in
nature and that the technology recovery effort will be secondary to other concerns. At this point, the IT
Incident Director will work closely with overall CWU Disaster Recovery Management to determine the
22
appropriate course of action. The ID is responsible for locating an alternate site for the team and reevaluating the best strategy for recovery.
Incident Assessment: The Incident Command Team (ICT) will receive an initial briefing from the Incident
Director (ID) and any other personnel invited to the meeting (ERT personnel, etc.) The ICT will assess the
situation, perform a walk-through of affected areas as allowed, and make a joint determination as to the
extent of the damage and required recovery effort. Based on this assessment, the team will make a
determination as to whether the situation can be classified as “routine” and handled expeditiously via
normal processes, or if a formal IT disaster needs to be declared.


ROUTINE: Area(s) affected by the incident are identified and the appropriate personnel are
contacted to report to work to evaluate and resolve the situation.
DISASTER: The Incident Director contacts the CWU Management Team Lead (CWU President or
designee) and notifies him/her of the situation, and that an IT Disaster has been declared. The ICT
identifies which areas of the IT infrastructure is affected, and contacts the members of the specific
Disaster Recovery Teams. Team members are provided with the following information:
o
o
o
Brief overview of what occurred
Location and time for teams to meet
Additional information as required. Team members are not to discuss any information
provided with other personnel employed or not employed at CWU.
Once an IT disaster has been declared, and the preceding steps to notify the CWU Management Team
and the Recovery Teams have been accomplished, ongoing responsibilities of the Incident Command
Team and Director include:









Securing all IT facilities involved in the incident to prevent personnel injury and minimize additional
hardware/software damage.
Supervise, coordinate, communicate, and prioritize all recovery activities with all other internal /
external agencies. Oversee the consolidated IT Disaster Recovery plan and monitor execution.
Hold regular Disaster Recovery Team meetings/briefings with team leads and designees.
Appointing and replacing members of the individual recovery teams who are absent, disabled, ill or
otherwise unable to participate in the process.
Provide regular updates to the CWU Management Team on the status of the recovery effort. Only
the CWU Management Team and/or their designees will provide updates to other campus and
external agencies (media, etc.)
Approve and acquire recovery resources identified by individual recovery teams.
Interface with other activities and authorities directly involved in the Disaster Recovery (Police,
Fire, Department of Public Works, CWU Teams, etc.)
Identify and acquire additional resources necessary to support the overall Disaster Recovery effort.
These can include 1) acquiring backup generators and utilities, 2) arranging for food/refreshments
for recovery teams, etc.
Make final determination and assessment as to recovery status, and determine when IT services
can resume at a sufficient level.
7.3 Disaster Recovery Teams: Seven Disaster Recovery Teams are organized to respond to disasters of
various type, size, and location. Any or all of these teams may be mobilized depending on the parameters
of the disaster. It is the responsibility of the ICT to determine which Disaster Recover Teams to mobilize,
following the declaration of a disaster and notification of the Central Washington University Management
Team.
Each team will utilize their respective procedures, disaster recovery information, technical expertise, and
recovery tools to expeditiously and accurately return their systems to operational status. While recovery
23
by multiple teams may be able to occur in parallel, the Data Center and Network/Telecommunications
infrastructure will normally be assigned the highest priority, as full operational recovery of most other
systems can not occur until these areas are operational.
7.3.1 Auxiliary Services Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery to Auxiliary Services.
3. Identify other individuals required to assist in recovery of these applications, and report this information
to the ID for action.
4. Restore degraded system functions at backup site and inform user community of the restrictions on
usage and/or availability.
5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact
information)
6. Coordinate Auxiliary Services recovery with other recovery efforts.
7. Execute plan to the Auxiliary Services to full function.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the Auxiliary Services to pre-disaster functionality.
7.3.2 Database Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery to Database services.
3. Identify other individuals required to assist in recovery of these applications, and report this information
to the ID for action.
4. Restore degraded system function at backup site and inform user community of the restrictions on
usage and/or availability.
5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact
information)
6. Coordinate Database services recovery with other recovery efforts.
7. Execute plan to restore Database services to full function.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the Database services to pre-disaster functionality.
7.3.3 Data Center Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery of Central Data Facility. Determine if use of
alternate/cold site is required.
3. If the alternate data center site is required, execute all necessary steps to notify appropriate personnel
and secure backup facility.
4. Identify other individuals required to assist in recovery of data center, and report this information to the
ID for action.
5. Develop overall recovery plan and schedule, focusing on highest priority servers for specific
applications first. (Appendix E documents the priority areas of the campus for IT service recovery)
6. Coordinate hardware and software replacements with vendors. (See Appendix F for vendor and
contact information)
24
7. Recall backup/recovery tapes from on campus or off-campus storage, as required to return damaged
systems to full performance.
8. Oversee recovery of data center based on established priorities.
9. Coordinate data center recovery with other recovery efforts on campus.
10. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
11. Verify and certify restoration of the data center to pre-disaster functionality.
7.3.4 Desktop Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage at all areas affected, and make recommendations for recovery.
3. Identify other individuals required to assist in recovery of desktop services, and report this information
to the ID for action.
4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus
infrastructure/desktop services first. (Appendix E documents the priority areas of the campus for IT
service recovery)
5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and
contact information)
6. Oversee recovery of desktop computing services (workstations, printers, etc.) based on established
priorities.
7. Coordinate recovery with other recovery efforts on campus.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the desktops to pre-disaster functionality.
7.3.5 Messaging Recovery/Network and Telecommunications Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery.
3. Identify other individuals required to assist in recovery of services, and report this information to the ID
for action.
4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus
infrastructure first. (Appendix E documents the priority areas of the campus for IT service recovery)
5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and
contact information)
6. Oversee recovery of messaging, telecommunications and network services based on established
priorities.
7. Coordinate messaging, network and telecommunications recovery with other recovery efforts on
campus.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the Messaging, Network and Telecommunications infrastructure to predisaster functionality.
7.3.6 PeopleSoft Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery to PeopleSoft services.
3. Identify other individuals required to assist in recovery of these applications, and report this information
to the ID for action.
25
4. Restore degraded system function at backup site and inform user community of the restrictions on
usage and/or availability.
5. Coordinate software replacement with vendor as required. (See Appendix F for vendor and contact
information)
6. Coordinate PeopleSoft services recovery with other recovery efforts.
7. Execute plan to restore PeopleSoft services to full function.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the PeopleSoft services to pre-disaster functionality.
7.3.7 Resnet Services Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery.
3. Identify other individuals required to assist in recovery of services, and report this information to the ID
for action.
4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus
infrastructure first. (Appendix E documents the priority areas of the campus for IT service recovery)
5. Coordinate hardware and software replacement with vendors. (See Appendix F for vendor and
contact information)
6. Oversee recovery of resnet services based on established priorities.
7. Coordinate resnet recovery with other recovery efforts on campus.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the Messaging, Network and Telecommunications infrastructure to predisaster functionality.
7.3.8 Telecommunications Recovery Team:
1. Take appropriate steps to safeguard personnel and minimize damage to any related equipment and/or
software.
2. Assess damage and make recommendations for recovery.
3. Identify other individuals required to assist in recovery of these services, and report this information to
the ID for action.
4. Develop overall recovery plan and schedule, focusing on highest priority areas of the campus
infrastructure first. (Appendix E documents the priority areas of the campus for service recovery.)
5. Coordinate hardware/software replacement with vendor as required. (See Appendix F for vendor and
contact information)
6. Oversee recovery of voice network services based on established priorities.
7. Coordinate the voice network recovery with other recovery efforts.
8. Provide scheduled recovery status updates to the Incident Director to ensure full understanding of the
situation and the recovery effort.
9. Verify and certify restoration of the voice network to pre-disaster functionality.
7.4 General System/Application Recovery Procedures/Outline: The following steps are guidelines to be
followed for the overall restoration of systems located at Central Washington University. While each
Recovery Team has specific duties and responsibilities as outlined in Section 7.3, coordination between
the various teams is required to restore operations to the users. While the coordination and extent of
personnel involved will depend on the type and severity of the disaster, the following steps may be
required:
26
NOTE: It is implied in the procedure/outline below that steps are simply provided as a guideline. The magnitude and type of
disaster, and the number of systems affected will require that certain steps be augmented (at the discretion of the Disaster Team
Lead and Incident Command Team), and that other steps will not be applicable to the situation at hand.
1. Determine extent of damage and make determination as to the following:
a. Primary Data Center operational/recoverable?
i. YES: Remain in primary data center and initiate DRP accordingly.
ii. NO: Contact personnel responsible for Backup Data Center and take necessary
steps to ready the facility.
b. Network Operations Center operational/recoverable?
i. YES: Utilize existing NOC for recovery.
ii. NO: Contact personnel responsible for Backup NOC and take necessary steps to
redirect network routes and ready the backup facility.
c. Determine extent of applications affected
i. Peoplesoft System
ii. Messaging (Email, Scheduling)
iii. Web Services (cwu.edu)
d. Determine extent of desktop/client systems affected throughout the campus
2. Secure facility as necessary to prevent personnel injury and further damage to IT systems.
a. Shutdown any active components.
b. Physically secure facilities (Data Center, Communication Rooms, etc.) as necessary to
prevent unauthorized access.
3. Retrieve most recent on-site or off-site back-up media for previous three back-ups. Prepare backup media for transfer to primary or secondary data center, as determined during the initial
assessment.
4. Verify operational ability of all equipment on-site in the affected area (servers, network equipment,
ancillary equipment, etc.). If equipment is not operational initiate actions to repair or replace as
needed.
5. Test systems, and communication equipment as required to validate physical operation and
performance.
a. Server testing
b. Network testing
c. Desktop/Client testing
6. Upon restoration of the Data Center and servers to operational state:
a. Load Operating System and test/validate
b. Load Application Software and test/validate
c. Load Data and verify integrity
7. Verify overall performance of specific system(s) and report readiness to Incident Command Team,
Management Team, and user community.
27
8.0 Network & Telecommunication Recovery Guidelines:
Servers and central application software are located in a central facility which can easily be assessed and
secured for damage. Data networking and telecommunications, however, has equipment located in every
facility on Central Washington University as well as in the Data Center. Remote equipment is located in
Communication Closets, often in multiple sites in a single building. In addition, data and telecommunication
cabling runs throughout the campus and buildings, making it susceptible to varying levels of damage.
Depending on the type and scope of the disaster, the IT Network and Telecommunication Recovery Team will
be involved in the following activities to adequately assess the overall damage and impact to the campus, and
to assure a comprehensive plan for recovery:
1) Earthquake
a) Perform comprehensive cable, fiber, and communications line testing
b) Assess all communication closets and racks/equipment for damage
2) Fire
a) Evaluate all cable and fiber in the vicinity of the fire for potential destruction or deterioration
b) Test primary copper data feeds for destruction of deterioration
c) Evaluate and test/assess all electronic equipment (hubs, switches, routers, etc.) that have been
exposed to water or other agents.
d) Assess all equipment with air filtration systems to assure adequate ventilation remains.
3) Water/Flood
a) Evaluate all cable and fiber in the vicinity of the water/flood for potential destruction or
deterioration
b) Test primary copper data feeds for destruction of deterioration
c) Evaluate and test/assess all electronic equipment (hubs, switches, routers, etc.) that have been
exposed to water or other agents.
d) Assess all equipment with air filtration systems to assure adequate ventilation remains.
Central Washington University network diagrams are included in Appendix G.
28
APPENDIX A: Central Washington University: Information Technology Services Directory/Contact List.
Last Name
First
Name
CWU
Phone
CWU Email
CWU Cell
Home
Phone
Ahmad
Max
2939
max.ahmad@cwu.edu
Allen
Don
2393
don.allen@cwu.edu
Alviso
Jose
1743
alvisoj@cwu.edu
Andrin
Marion
1891
andrinm@cwu.edu
Ashbrooks
Steve
3442
ashbroos@cwu.edu
899-1865
965-4219
Beintema
Larry
2905
beintema@cwu.edu
899-0347
968-9320
Beintema
Jami
2333
beintemj@cwu.edu
Breckon
Ron
3694
breckonr@cwu.edu
Brower
Doug
2356
brower@cwu.edu
Brown
Rock
2999
brownroc@cwu.edu
Carlson
Barry
2904
bcarlson@cwu.edu
Case
Felicia
2903
felicia@cwu.edu
Cathcart
Jason
1223
cathcarj@cwu.edu
Cusumano
Pete
3834
cusumanp@cwu.edu
DeLuca
Greg
2970
gdeluca@cwu.edu
201-6144
Douglas
Steve
1232
dougr@cwu.edu
856-6581
Firman
Marla
1250
firmanm@cwu.edu
Gerdes
Jason
2995
Germain
Dave
Germain
Home Email
925-9092
dadeodon@gmail.com
962-3188
marionpich@yahoo.com
933-1010
Home
Cell
607-1495
961-8878
breckons@elltel.net
859-2301
johann@bach.net
312-9732
933-4606
859-2884
jgerdes@cwu.edu
932-5361
431-5030
2996
germaind@cwu.edu
962-5241
citizengermain@gmail.com
899-0055
Terilee
2946
terilee@cwu.edu
962-5241
terilee@fairpoint.net
899-1696
Gladen
Jeff
1606
gladenj@cwu.edu
925-2473
jgladen@elltel.net
Gladen
Kristi
2392
gladenk@cwu.edu
899-0044
925-2473
kgladen@elltel.net
Glessner
Bill
3694
beegee@cwu.edu
899-0999
962-6566
Haberman
Susan
2944
haberman@cwu.edu
Halvorson
Colleen
3499
halvorsc@cwu.edu
Hart
David
2932
hartd@cwu.edu
Hendrickson
Teri
3422
hendricksont@cwu.edu
Hernandez
Uriel
2967
hernandu@cwu.edu
Hill
Nathan
2942
hillna@cwu.edu
Jackson
Nancy
3333
jacksonn@cwu.edu
Jones
Frank
2856
jonesfr@cwu.edu
Jones
Keith
2191
Klampher
Tina
Knackstedt
306-2128
925-1713
bobhaberman@elltel.net
925-6961
galtj@elltel.net
962-5339
899-5015
899-5063
899-0136
925-3835
njj706@gmail.com
899-4617
jonesk@cwu.edu
856-6219
962-5707
jonesk@elltel.net
856-5333
2778
klamphtl@cwu.edu
899-3836
925-2013
899-4818
Jeff
2352
knackstj@cwu.edu
899-2768
962-8165
306-9637
Lei
Vera
2972
leiv@cwu.edu
Lonowski
Dale
2407
lonowsda@cwu.edu
933-4002
Miller
Bill
3490
millerwd@cwu.edu
n/a
dalerainy@yahoo.com
859-2903
899-0243
29
2954
osguthorpej@cwu.edu
Osguthorpe
Jared
Patterson
Randy
Pierce
Tad
2997
piercel@cwu.edu
Pratz
Chris
1581
cpratz@cwu.edu
899-3220
n/a
Pruitt
Jim
3472
pruittj@cwu.edu
899-0145
962-8342
Rahm
Carmen
2925
rahmc@cwu.edu
899-0038
962-1547
Richardson
Wade
3424
richardw@cwu.edu
856-6867
697-3370
930-7823
Ringer
Jason
2394
ringerj@cwu.edu
698-5033
949-5056
Rodriguez
Noah
2934
rodriguezn@cwu.edu
Shelton
Debby
3428
sheltond@cwu.edu
925-4115
shelton56@hotmail.com
899-1479
Sperline
Sandy
2989
sperlins@cwu.edu
968-9825
ssperline@hotmail.com
929-0552
Swayze
Stacy
3466
swayzes@cwu.edu
Timmons
Chris
2947
cwt@networks.cwu.edu
925-7897
cwt@elltel.net
856-7884
Varga
Steve
2953
shv@cwu.edu
963-9073
vargahenry@netscape.net
Vincent
Kathy
2544
vincentk@cwu.edu
Wang
Xinbao
2945
wangx@cwu.edu
Wang
Crystal
2643
wangc@cwu.edu
Webber
Maury
3752
webberm@cwu.edu
Wixson
Heidi
2969
wixsonh@cwu.edu
962-6107
Young
Ken
3491
youngke@cwu.edu
933-1773
3653/3649
pattersr@cwu.edu
856-7116
925-4391
899-2527
674-9632
899-2101
foreacres@elltel.net
360-2712992
925-4374
607-0347
kgyoung@charter.net
899-1035
30
APPENDIX B: Central Washington University Critical Support Contacts List.
First
Name
Last Name
CWU
Phone
CWU Email
Gaudino
James
2150
gaudino@cwu.edu
Clark
George
2323
clarkg@cwu.edu
Levine
Marilyn
1400
levinem@cwu.edu
Horsley
Jackson
1874
horsleyj@cwu.edu
Swiney
John
3031
swineyj@cwu.edu
DeShields
Schactler
Richard
Linda
McGuire
2785
1384
deshielr@cwu.edu
schactler@cwu.edu
Tim
2329
mcguiret@cwu.edu
Gaer
Kathy
2201
gaerk@cwu.edu
Morrill
Tami
3016
morrillt@cwu.edu
Tosch
Robert
2916
toschr@cwu.edu
CWU Cell
Home
Phone
Home Email
Home Cell
330-5546528
925-1877
201-0459
962-9022
859-4919
tim@gowestmail.com
312-0405
962-9876
9626667
899-0635
962-4581
The Central Washington University Personnel Directory (2006-2007) and contact information is included with
the hardcopy version of this plan. Copies of the plan are located in the ITS Office (Bouillon 202), the
Computer Center and the Vault (Hebeler).
Name
Charter Communications
City of Ellensburg (Inet)
Fairpoint
Communications
K20 Administrative
Contact
K20 Internet Circuit
K20 Point-to-Point
Circuits (Data/Video to
Campus Centers)
Contact
Ron Graaff
Bob Johnson
Patrick Murphy
Steve Paulson
Washington K20
Network
Operations
Center
Washinton State
DIS Helpdesk
(DIS DL
Helpdesk)
Phone
509 962-4801
509 728-2662
509 925-8537
509 962-0331
509 929-3881
Fax
Rgraaff@chartercom.com
johnson@kittcom.org
pmurphy@fairpoint.com
206 221-3221
888 934-5551
888 241-7597
Email
spaulson@cac.washington.edu
888 934-5557
noc@wa-k20.net
Helpdesk.DIS.WA.GOV
31
APPENDIX C: Central Washington University – Asset Management Information
The following printouts, asset management information, and documents are included with the hardcopy
version of this plan. Detailed information is documented in the online database located at
http://www.cwu.edu/~its/security/hardware.php.




Server Asset Management Information
Network Active Hardware Asset Management Information
Application Software Configuration Information
Desktop Equipment Asset Management Information
32
APPENDIX D: Central Washington University – System Backup/Tape Retention Periods
All servers in the Computer Center are backed up on this schedule:
http://beintema.cts.cwu.edu/~beintema/networker_schedule.html
Retention information is located in section 6.1 of this document.
Schedule of Legato networker host saves
S - skip I - incremental F - full
Full saves start at 12:10 a.m., usually done by 8am
Incrementals start at 2:00 a.m., usually done by 5am
===================================================
Hostname
Sun Mon Tue Wed Thu Fri
aeolus.lab.cwu.edu
F
I
I
I
I
I
alecto
I
I
I
I
I
I
alipes2.cts.cwu.edu
S
F
I
I
I
S
ananke
F
I
I
I
I
I
anat.cts.cwu.edu
S
F
I
I
I
I
aphrodite
S
I
I
I
I
I
apollo.saffrs.cwu.edu
I
S
F
I
I
I
apps-01.aux.cwu.edu
F
I
I
I
I
I
arges.cts.cwu.edu
I
I
I
I
S
F
aries.cts.cwu.edu
S
S
S
S
S
S
aris
S
S
S
I
S
S
aristotle.lab.cwu.edu
I
I
I
I
I
F
asherah.cts.cwu.edu
S
I
I
I
I
I
athena.cwu.edu
S
I
I
F
I
I
atlas.cts.cwu.edu
I
S
F
I
I
I
azure.cts.cwu.edu
S
I
I
I
F
I
barchetta.lib.cwu.edu
S
S
S
S
S
S
bbdata.cts.cwu.edu
I
I
I
I
I
F
bbweb.cts.cwu.edu
I
S
I
I
I
F
beintema.cts.cwu.edu
S
I
I
I
I
F
blackbaud.unadv.cwu.edu
I
I
I
I
I
F
bonsai.cts.cwu.edu
F
I
I
I
I
I
boreas
F
I
I
I
S
S
bruker05.chemistry.cwu.edu
S
I
I
I
I
F
capricorn.cts.cwu.edu
S
S
S
S
S
S
ccs.aux.cwu.edu
F
I
I
I
I
I
ccstst.aux.cwu.edu
F
I
I
I
I
I
cerise.aux.cwu.edu
S
I
I
I
I
I
chinstrap.lib.cwu.edu
S
S
S
S
S
S
clmdb.cts.cwu.edu
S
F
I
I
I
I
clmtest.cts.cwu.edu
S
F
I
I
I
I
clmweb.cts.cwu.edu
S
F
I
I
I
I
clotho
I
I
I
I
I
F
columba.cts.cwu.edu
S
S
S
S
S
S
courses2.cwu.edu
S
S
S
S
S
S
crimson.cts.cwu.edu
S
S
F
I
I
S
cyan.cts.cwu.edu
I
S
I
F
I
I
cygnus.cwu.edu
I
S
F
I
I
I
daffy.cts.cwu.edu
S
I
I
I
I
I
dbackup0.cts.cwu.edu
S
I
S
F
S
I
dbackup1.cts.cwu.edu
S
S
F
S
I
S
dbtest.cts.cwu.edu
S
S
S
S
S
S
demeter
I
S
F
I
I
I
diana
F
I
I
I
I
I
diebolddb.aux.cwu.edu
I
S
F
I
I
I
Sat
I
F
I
S
I
F
I
S
I
S
F
S
F
I
I
I
S
S
S
I
S
S
I
I
S
S
S
F
S
I
I
I
I
S
F
I
I
I
F
S
I
S
I
S
I
33
donald.cts.cwu.edu
dynobites.aux.cwu.edu
eldorado.chemistry.cwu.edu
etclib.ed.cwu.edu
eunomia.cts.cwu.edu
ezp.lib.cwu.edu
fileproxy.cwu.edu
flex.aux.cwu.edu
fmail.cts.cwu.edu
fuschia.cts.cwu.edu
galileo.phyplt.cwu.edu
gizmonic.cts.cwu.edu
gridiron.cts.cwu.edu
gridlock.cts.cwu.edu
gw-gate2.cwu.edu
gw-stu1.cwu.edu
gw-stu2.cwu.edu
gw-stu3.cwu.edu
gw-stu4.cwu.edu
gw-stu5.cwu.edu
gw-stu6.cwu.edu
hcc.aux.cwu.edu
hccaud.aux.cwu.edu
hermes
horizon.cts.cwu.edu
housing.aux.cwu.edu
hubris.cts.cwu.edu
hypnos
indigo.cts.cwu.edu
keybox.cts.cwu.edu
kronos.aux.cwu.edu
kryten.cts.cwu.edu
labstats.cts.cwu.edu
lavender.cts.cwu.edu
library
lister.cts.cwu.edu
localhost6.localdomain6
logopolis.hpc.cwu.edu
magenta.cts.cwu.edu
maroon.aux.cwu.edu
mauve.cts.cwu.edu
megaera.cts.cwu.edu
mercury2.cts.cwu.edu
microsapp.aux.cwu.edu
microsdb.aux.cwu.edu
midas.adm.cwu.edu
min.cts.cwu.edu
mingo.lib.cwu.edu
mira.cts.cwu.edu
mot.resnet.cwu.edu
mtrainier.cts.cwu.edu
mysql.cts.cwu.edu
n.cwu.edu
nergal.cts.cwu.edu
nsc0.cwu.edu
nsc0.resnet.cwu.edu
nsc1-831.cwu.edu
nsc1.resnet.cwu.edu
nyx
ochre.cts.cwu.edu
S
S
S
I
I
S
F
F
S
S
F
S
F
I
S
S
S
F
I
I
S
F
F
I
F
S
S
S
I
S
S
S
F
S
I
S
S
S
I
I
F
S
I
S
S
S
F
S
I
F
S
S
S
S
I
F
I
S
F
S
I
I
S
F
I
F
S
I
I
I
I
F
I
S
I
I
I
I
I
S
I
I
I
S
I
S
I
F
S
F
F
I
I
I
F
I
S
I
I
I
I
I
I
I
I
F
I
S
I
I
F
I
F
I
S
I
F
F
I
I
I
F
S
S
I
I
I
I
I
F
I
I
I
F
I
I
I
I
I
F
I
I
I
S
I
S
I
I
I
I
I
I
I
F
I
I
S
I
I
I
I
F
I
F
F
I
I
S
I
I
I
I
I
S
F
I
I
I
I
I
I
S
S
I
I
I
S
I
I
I
I
I
I
I
I
I
I
I
F
I
I
I
I
F
I
S
I
I
I
I
I
I
I
I
I
I
S
I
F
S
I
I
S
I
I
I
I
S
S
I
I
I
I
I
I
I
I
I
I
I
I
I
S
S
I
I
I
I
I
I
I
I
I
I
I
I
F
I
I
I
F
I
I
S
I
S
I
I
F
I
I
I
I
I
I
I
S
I
S
I
I
I
I
I
I
I
I
S
F
I
I
I
I
I
I
I
I
I
I
I
I
I
S
I
I
I
S
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
I
S
F
I
I
I
I
I
I
I
I
I
S
I
I
S
I
I
S
I
I
I
S
S
I
I
I
I
I
I
I
I
I
I
I
I
F
I
S
S
F
I
I
S
F
I
S
S
S
I
F
F
I
S
S
I
I
S
S
S
S
S
S
I
I
I
I
F
S
I
S
F
S
F
I
F
S
I
F
I
I
I
I
S
I
S
S
F
I
F
I
S
S
I
S
F
34
otm.cts.cwu.edu
pa.cts.cwu.edu
panteknicon.cts.cwu.edu
pc78221.d.cwu.edu
plato.lab.cwu.edu
pollux.cts.cwu.edu
poseidon
prometheus.cts.cwu.edu
qadesh.cts.cwu.edu
r25.cts.cwu.edu
resheph.cts.cwu.edu
resnet.cwu.edu
rima.cts.cwu.edu
rimmer.cts.cwu.edu
ronald.cts.cwu.edu
scarlet.cts.cwu.edu
screencast.clt.cwu.edu
sheena.cts.cwu.edu
smail.cts.cwu.edu
socrates
spectrum.ed.cwu.edu
streamer0.cts.cwu.edu
studentmedia.cwu.edu
telemgr.cts.cwu.edu
telos.cts.cwu.edu
telsrv.cts.cwu.edu
tethys
themis.cwu.edu
tiamat.cts.cwu.edu
tisiphone
trix.aux.cwu.edu
uhnsp.aux.cwu.edu
uhnsptst.aux.cwu.edu
umber.cts.cwu.edu
vmail.cts.cwu.edu
w3cache0.cts.cwu.edu
wmail.cts.cwu.edu
worf.cts.cwu.edu
zephyrus
zeus.cwu.edu
S
S
S
S
S
S
I
F
F
S
F
F
F
S
S
I
S
F
S
S
S
S
S
S
S
S
I
I
F
S
I
S
F
S
S
F
S
S
S
I
F
F
I
S
I
S
S
I
I
F
I
I
S
I
I
S
S
I
I
I
S
S
I
I
S
I
S
S
I
I
S
F
I
I
I
I
I
I
I
I
I
I
I
S
I
S
F
I
I
I
I
I
S
I
I
I
I
I
I
I
F
I
I
I
F
I
F
F
I
I
F
I
I
I
I
I
I
I
I
S
I
I
I
S
I
S
I
I
I
I
I
I
I
I
I
I
F
I
I
I
I
S
I
I
S
I
I
I
I
I
I
I
I
I
I
I
I
F
F
I
I
I
I
S
I
S
I
I
I
I
I
I
S
I
I
F
I
I
I
I
I
S
I
I
S
I
I
I
I
I
I
I
I
I
I
I
I
I
I
F
I
I
I
S
I
S
I
I
S
I
S
I
S
I
I
I
S
I
I
F
I
F
I
I
I
I
I
I
S
I
I
I
I
I
I
I
I
I
I
I
I
I
F
S
F
S
I
S
I
I
I
S
S
F
F
I
I
I
F
I
I
S
F
F
S
F
I
I
I
F
I
I
S
F
F
S
F
I
I
I
Servers:
Server information is documented in the online database located at
http://www.cwu.edu/~its/security/hardware.php.
Hardware Database:
The hardware database is updated/reviewed every month by the Networks & Operations staff. The database
is copied to CD monthly and stored in the vault located Hebeler.
When major configuration changes take place, new CDs will be created upon its completion.
35
APPENDIX E: Central Washington University: IT Recovery Priority List
The following priorities have been established by the Director of Information Technology Services and by
CWU Senior Management for the recovery of IT Services to the university.
IT Infrastructure Priorities: This establishes the internal priorities for recovering the major infrastructure
components for IT services. These priorities are based on the relationship between these systems, and
the pre-requisite nature of many of the items in order to be able to return full services to the campus.
1.
2.
3.
4.
5.
6.
Data Center
Network Services (as prioritized below)
Messaging Services (email/calendaring)
Web Services
Peoplesoft Applications
Online Course Delivery and Classroom Technology
36
Central Washington University Functional Priorities for IT Recovery: This establishes the priorities for
recovering IT services for specific customers and facilities across the campus. While the Data Center,
Peoplesoft, Web, and Messaging Services are centrally located, and will normally be recovered for all users
simultaneously, recovery of network and desktop services will be accomplished based on the following
priorities, in order to return critical campus systems and facilities to operational status at the earliest possible
time.
Priority
Administrative System
L
M
L/M
M
L
C
H
H/C
M
Alumni
Blackboard
Conference Center (CCS)
Course Management R25
Daycare Management
Diebold/CBORD
Dining Services (DINE,Computrition)
Electronic Mail
Facilities Planning (Facility MAX)
M
H
File Services
Finance (FMD)
H
L
H
L
L/M
L/M
L
H
H/C
H
L
C
L/M
C
Financial Aid (HRSA)
Health Services
Housing
Institutional Research
Instructional Computing (MTIS)
Library
Parking (CPAS)
Payroll (Safari)
ResNet
Safari / HR
Student Recreation (Class)
Telecommunications
University Store (Sequoia,IBIDie)
Web Services
Primary Staff
Jim Armstrong
Delayna Breckon
Xinbao Wang
Janie Charlton
Tad Pierce
Dan Layman
Bill Glessner, Greg DeLuca
Jason Cathcart,
Greg DeLuca, Terilee
Germain
Shirley Pruitt
Jillian Hernandez, Tami
Morrill
Jackson Horsley
Richard DeShields
Mark Lundgren
Jane Chinn
Ping Fu
Trish Swanson
Darcy Hansen
Jason Gerdes
Bob Ford
Nancy Jackson
Steve Wenger
Linda Schactler
Classifying computer application systems:
Critical – Must be processed in normal mode; no degradation is acceptable.
High – Only high priority; e.g., high dollar item transactions or critical reports will be processed.
Medium – Processing will be carried out on a “time available” only basis.
Low – Processing will be suspended, but data collection will continue.
Full – No processing or data collection will be carried out until normal computer capacity is restablished.
37
Facility Priorities:
Priority
Building Name
Priority
Building Name
M
1800 Building
L
Lyon (Yakima)
L
Archives
L
Mail and Duplicating
H
Barge
C
Manastash
H
Barto
L/M
McConnell
H
Beck (Resnet Sector Building)
H
Meisner
M
Black
M
Michaelsen
C
Boiler Plant
H/C
Mitchell (Sector Building)
C/H
Bouillon (Sector Building)
M
Moses Lake
H
Brooklane
H
Munson
H
Button
M
Music
H
Carmody-Munro
L
Naneum
M
CHCI
M
Nicholson
C
Computer Center
H
Old Boiler Plant
M
Dean
M
Olympic (Pierce)
M
Deccio (Yakima)
M
Dorothy Purser (PE)
M
Des Moines
M
Peterson (ROTC)
M
Farrell
H
Wendell Hill (SVS)
M
Flight
L
Pool
H
Green (Resnet Sector Building)
M
Power Tech
L
Grounds
M
PresRes
C
Health Center
M
Psychology
M
Hebeler
M
Randall
L
H
Residential Housing
M
Hertz
Higher Education Center
(Highline)
C/H
Science (Sector building)
M
Hogue
M
Shaw-Smyser
L/M
International
C
Student Union & Recreation Center
H
Jansen
L
SUB (OLD)
C
Jongeward
M
Sue Lombard
H
Kamola
L
Surplus
H
Kennedy
H
Tunstall
M
L and L
L
Warming Hut
C/H
Library (Sector Building)
M
Wenatchee
M
Lind
H
Wilson
M
Lynnwood
Classifying buildings:
Critical, needed for maintenance of public health and safety, communications.
High, needed for income maintenance for students, employees; payments to vendors; requirements for
compliance or regulation; effect on state government cash flow; effect on production and delivery of
services (housing, dining, student services).
38
Medium, needed for mission of university, delivery of classes.
Low, everything else.
39
APPENDIX F: Central Washington University: Vendor Information
VENDORS
City of Ellensburg #621
420 N. Pearl St.
Ellensburg, WA 98926
Mgr
Contact Info.
Term
Description
Cont
I-Net O&M Expenses
(Quarterly)
5240
7/1/09
–
6/30/10
Provide Computer output
to microfilm services &
courier
(Microfiche Agreement)
1584
6164
2666.3
4
quarterl
y
Noah
phone 9627203
Gene
phone 800-776-2451,
fax 916-924-1398
cell 916-785-6048 Marty
Skognes
marty@comstorinc.com
Gene
Jennifer Van Dijik 425-5126622
7/17/20
097/16/20
10
Annual Support
Maintenance
*Gene does not want to
Encumber
Cascade Copiers
#1629
801 W. Yakima Ave.
Yakima, WA 98902
Marla
phone 509-575-0734
fax 509-575-3080
curtis.bell.jr@imagistics.com
1/05 12/09
Imagistics im3510 digital
copier/
printer system
(Networked)
Dimension Systems
(Cisco) #14173
17311 135th Ave NE
Suite B500
Woodinville, WA 98072
Noah
phone 425-502-0258
fax 425-402-0633
Lana Greene
9/4/04 9/3/05
SMARTNET 8x5 NBD
Support Renewal
3467
Dimension Sys (Sun
Microsystems) #14173
17311 135th Ave NE
Suite B500
Woodinville, WA 98072
Noah
Ramona Estay
425-402-0258
5/1/04 4/30/05
Sun Spectrum Silver
Renewal
(Software support)
3530
Comstor #691
2219 N. Dickey Road
Spokane, WA 99212
Connx Solutions Inc
#3933
1800 112th Ave NE
Suite 150
Bellevue, WA 98004
40
Graymatter Software
#1198
100 South King Street
Suite 570
Seattle, WA 98104-2885
HP (Digital Equipment
Corp. or Compaq) #683
1124 Tower Road
Schaumburg, IL 60173
JRB Software
Mail Abuse Prevention
System (MAPS) #11873
950 Charter Street
Redwood City, CA
94063
Mini Tab #1953
1829 Pine Hall Road
State College, PA
16801-3008
Noah
Doug Parsons #303051
800-477-0348 X120, 206-3298800
fax 206-860-9441
Noah/
P&M
phone 916-785-6485
916-785-6048
fax 916-924-1398
jerry.piepmeier@hp.com
Noah/
David H
7/1/04 6/30/05
Script Server Annual
Maintenance for the
Large Mixed VAX &
Alpha Cluster License
with Network Module
Enabled
3067
7/1/04 6/30/05
VAX Software Maint.
Renewal
1276
renewal for JRButils
software
registration
None
643-332-5996
Noah
Heather Bryning
phone 650-779-7084
3/1/05 2/28/06
Renewal of Subscription
to RBL + Master Service
and PebPlus.Mailabuse.org zone
6301
Sandy
Sperline
Lu Ann Mann
phone 814-238-3280
fax 814-238-4291
7/1/09 6/30/10
Renew Licence
Agreement
1438
Renew Licence
Agreement/
Annual Maintenance
Renewal
for Directory Alert
Software
Academic Licensing
renewal. Netware NFS
Services 3.0
Maintenance
Netvision #12491
1500 N Technology Way
Building D, Suite 3300
Orem, UT 84097
Noah
Heather Anderson
phone 801-764-0400 x145
fax 801-764-0600
5/1/04 4/30/05
Novell Inc. #2156
1800 South Novell Place
Provo, UT 84606
Noah/
Tech
Fee
phone 800-453-1267 x15235
fax 801-861-5235
10/1/04
9/30/05
Oracle #2198
1910 Oracle Way
Reston, VA 20190
Noah/
ASSP
Gavin Ostrom
916-315-6582
fax 781-238-9895
5/23/04
5/22/05
Product Support Fee
Limited Site Licenses
(10 Systems)
4435
Noah
Michelle Haley
800-722-7770, 508-879-6994
fax 508-879-0042
haley@process.com
7/1/04 6/30/05
Multinet Univ. Alliance
Annual Maint. 25 CPU's
PMDF Access & LAN
Tru 64/UNIX Maint.
3312
Process Software
(PMDF, Multinet) #2392
959 Concord St
Framingham, MA 01701
5222
4811
41
Process Software
(Precise Mail) #2392
959 Concord St
Framingham, MA 01701
Process Software
(SOPHOS) #13072
6 Limball Lane
Lynnfield, MA 01940
Quest #2428
PO BOX 51739
Los Angeles, CA 90051
R&D Performance
Group (Support)
#13398
1180 Patricia St Ste 102
Simi Valley, CA 93065
Right Systems Inc.
(Packeteer) #10698
PO BOX 11036
Olympia, WA 985081036
Noah
Michele Haley
800-722-7770, 508-879-6994
fax 508-879-0042
haley@process.com
10/20/0
410/19/0
5
Anti-Span Gateway
annual softwware
subscription
Noah
phone 888-767-4679
fax 781-245-8620
Craig McKeown
7/1/04 6/30/06
Sophos Antivirus 2000
User SAVI License. For
Use with PMDF
Gene
phone 614-726-4823
fax 614-726-3884
Joann Sizemore
3/31/09
3/31/10
Toad Formerly (Lecco
SQLab Expert Pro
Edition for Oracle) per
seat (12)
6663
Noah
Katie Nielsen 800-521-9966
fax 805-520-4169
9/10/04
- 9/9/05
Networker Open VMS
Client Support Renewal
None
Mark Westling
3609560414x8200
7/1/04 6/30/05
Renewal of Packeteer
Cust. Support Program
None
phone 214-210-6222
214-210-6246
fax 214-210-6211
David Evett/Don Genton
1/29/05
1/31/06
Legato Updates for
NetWorker Server
6082
SPSS Base, Advanced
Models, Trends, Answer
Tree
3576
Noah/
Chris T.
3312
HP #2825
715 N Glenville Dr #450
Richardson, TX 75081
Noah
SPSS-PC #2770
233 S Wacker 11th Floor
Chicago, IL 60606-6307
Dave S.
Tech
Fee
Steve Prior
800-543-2185 x3943
fax 312-264-3943
University of WA #3123
PO BOX 355870
Seattle, WA 98195
Noah
phone 814-238-3280
fax 814-238-4383
7/1/04 6/30/05
PNW IGAPOP K20
Utilization
None
Noah
Brenda Mofford
877-438-8776
Multiple
Times
Yearly
Multiple Contracts for
Secure Site Service
(SSL Certificate)
None
Noah
Pamela Seymour
phone 816-753-0848
fax 816-753-5454
1/4/05 1/3/06
Annual Unlimited Usage
Campus Site License for
IMSL Fortran 90 & C
1616
Noah/
Larry
phone 650-475-5019
fax 650-475-5001
8/31/04
9/1/05
GSX3-L-U-AE License
for
Linux 2 cpu
None
3/1/05 2/28/06
Magnitude base 110V
6258
Verisign, INC.
75 Remittance Dr.
Suite 1689
Chicago, IL 60675-1689
Visual Numerics #3193
PO BOX 297852
Houston, TX 772970852
HP #8963
3145 Porter Dr Bldg F
Palo Alto, CA 94304
XIOTech #10343
6455 Flying Cloud Dr
Eden Prarie, MN 55344
Noah
42
T2 Systems
7835 Woodland Drive
Suite 250
Indianapolis, IN 46278
Steve B/
Nate Hill
Deborah Eugene
Sales 317-524-7445
support 800-434-1501
support@t2systems.com
Parking: T2 Systems
Flex System
Marion
Andrion
phone: 908-725-8869
fax: 908-725-9396
Tech Contact: 908-725-8869
Charlie Boone ext 205
Josh Prokrasov ext 206
support@adirondacksolutions.c
om
Housing
Kronos Incorporated
18200 NE Union Hill Rd
Ste 100
Redmond, WA 98052
Nate Hill
Tech Contact: Kronos Global
Support 800-394-4357
Solution nbr: 6051679
support@kronos.com
Dining [Kronos
Employee Timekeeping
& Payroll System]
Computrition Inc
19808 Nordhoff Place
Chatsworth, CA 91311
Larry
Beintem
a/
Judy
McNeil/
Tad
Pierce
Adirondack Solutions,
Inc.
P.O.Box 8102
Bridgewater,NJ 08807
www.adirondacksolution
s.com
Support 866-789-2977
cs_support@cbord.com
The CBORD Group
61 Brown Road
Ithaca, NY 14850
www.cbord.com
Tad
Pierce
Inland Business
Products
111 N. Vista, Bldg 4D
Spokane, WA 99212
www.ibpspokane.com
Tad
Pierce
Asset Solutions
Division
33330 Oakwell Court
Suite 200
San Antonio, TX 78218
Tech Contact: Beth
800-222-4458
cust # 1593
Ed
Castane
da
Sales: Don Rae
office:509-628-2315
cell 509-539-0159
efax 413.653.3860
phone 800-825-5703
Tech Contact: Tod Curtis
tcurtis@ibpspokane.com
Tech Support 800-268-0325
facilitysupport@assetworks.com
www.assetworks.com/facilitysup
port
5287
Dining [Computrition
Food Management
System] Windows fat
client w/ Oracle
CBORD Campus Card
System and Micros Cash
Register System
[formerly Diebold]
4726
Connection Card:
IDworks Card Production
Sys
6299
FMD & Auxiliary: FMAX
Work Order
Management
http://www.assetworks.c
om/page/facilitiesmanagement-support
43
Nuesoft Technologies
1685 Terrell Mill Road
Marietta, GA 30067
www.nuesoft.com
Active Networks
6400 Roberts Road
Suite 30
Burnaby, BC
Canada V5G 4C9
Resnet Server
Applications
Sequoia Retail
Systems
1927 Landings Drive
Mountain View, CA
94043
www.sequoiars.com
Information Resource
Technology, Inc
9825 Perry Hwy
Wexford, PA 15090
www.ibid.com
Software Licenses
Campus Agreement
phone: 800-401-7422 ext 210
Steve B/
Nate Hill
Nate Hill
Tech Support:
800-401-0785
NueMDsupport@nuesoft.com
Expire
s
7/13/09
and will
not be
reneww
ed
Tech Support:
800-663-4991
classsupport@active.com
Nate Hill
Tad
Pierce/N
ate Hill
Health Center: Nuesoft
Medicat Xpress
7137
Student Recreation:
Class Software
7659
Locally written Resnet
Applications
Call Tracker
CopyCat Inventory
509-963-2942
HillNa@cwu.edu
phone 650-237-9000
fax 650-237-0428
Tech Support:
POS 800-536-5644
ePos 800-818-5018
Wildcat Shop: Sequoia
Retail Systems
6418
support@sequoiars.com
Marion
Andrin
Custom Developed
Online Applications:
Housing Re-Application,
Residence hall
Programs, Hall incident
Reporting, Orientation
Registration, Student
Conduct Report, Parent
Family Program
509-963-1891
AndrinMa@cwu.edu
CSS
9/30/04
1122 FTE
None
Office Professional
Windows Professional
Frontpage
Select Agreement with
Microsoft
CSS
CSS
CSS
9/30/04
9/30/04
9/30/04
$21.92 ea includes Word,
Excel, Power Point, Access
$16.04 ea
$4.21 ea
None
None
None
Ofice Family Subscription
CSS
Monthly
/ July 04
$4.16 ea
None
$2.49 ea
None
Macintosh Apps
Subscription
Windows Servers
Subscription
Server Apps Subscription
Windows Client Business
Subscription
CSS
Monthly
/ July 04
Monthly
/ July 04
$4.16 ea
None
CSS
Monthly
/ July 04
$4.98 ea
None
CSS
Monthly
/ July 04
$2.49 ea
None
CSS
44
Windows 2003 Server Std.
Subscription
CSS
Monthly
/ July 04
(not sure on cost, this was
added at last minute)
None
Windows 2003 Server Ent.
Subscription
CSS
Monthly
/ July 04
(not sure on cost, this was
added at last minute)
None
Vendor
Mgr
Contact Info
ACCOUNT
NUMBER
Service
Address
Contract
Service
Type
Curcuit
Numbers
Qwest
P.O.Box 12480
Seattle, WA
Telecom
800-777-9594
509-4538664 283B
206-T315605 682B
206-T315687 673B
509-7622135 974BG
206-8248800 718B
YVCC
Ellensburg 911
Ellensburg 911
Modem
Moses Lake
Modem
Des Moines
509-4538664
206-T315605
206-T315687
509-7622135
206-8248800
Qwest
Department 047
Denver, CO
80271
Telecom
888-429-0977
QIA14001WA1109
QIA15266WA0908
QIA15387WA0108
QIA13998WA1109
QIA14002WA1109
QIA14003WA1109
Lynnoood
Maintenance
YVCC
Maintenance
81C
Maintenance
6441
6704
6538
Voice Mail
5935
DesMoines
None yet
Wenatchee
None yet
Global/Matrix
Greg Meyers
P.O. Box 742501
Telecom
888-411-0111
52031711990000
800 Line
(866)2984968
(877)6498707
(800)7524378
(800)2903327
(800)2987682
(877)8462287
(800)2801186
(800)7524379
800 Line
(877)8803583
800 Line
(800)540-
800 Line
800-236-2233 - Ext 2266
Admissions
CWU
Foundation
Greg Meyers
Development
800 Line
Library
800 Line
Aerospace
800 Line
Alumni
800 Line
Bookstore
Conference
Center
Res Life &
New Student
Services
800 Line
Wenatchee
800 Line
45
6537
University
Emergency
Information
800 Line
Army ROTC
800 Line
Anthropology
Career
Technology
Conference
Bridge
800 Line
10114223
Facilities
Pager
10105460
Housing
Pagers
509-9250660
509-8560357 &
509-8560438
03 0260
1000902293
04
Edmonds
Campus
Access
Line
425-7120183
03 0487
1084445493
03
Wenatchee
Campus
Access
Line
509-6670579
800 Line
800 Line
(866)4198512
(877)2769298
(877)8372915
(877)4243989
(877)6677535
Telewaves
P.O.Box 2909
Yakima, WA
98907
Telecom
800-662-4077
Verizon
POBox 1003
MS: WA0102MJ
Everett, WA
98206
Telecom
800-483-6000
800-483-2000 Repair
AT&T Mobility
Redmond
Telecom
Bruce Erickson
206-245-7568
990151123
Cellular
FAN 49040
800-999-5445-support
Chris McLeod
425-580-5565
Cell 425-495-9118
Fairpoint
Communications
P.O.Box 308
Ellensburg, WA
98926
509-925-1425
0100223045
- Main
Account
509-933-7419
0100223070
- Housing
P.O.Box 70821
Charlotte, NC
Telecom
Main
Trunking
46
Account
Bill Malesich
300-0042 KCWU
Circuit
100-8911 911
Transport
DIS
P.O.Box 42439
Olympia, WA
98504-2439
Telecom
360-902-3528
Long
Distance
3750A
(360) 902-3527 Mary Jackson
AT&T
P.O.Box 78225
Phoenix, AZ
85062-8225
Telecom
800-847-3595
056 578
3032 001
Yakima
Access
Line
131 1805838 799
Continuing
Ed
800 Line
Housing
800 Line
509-4538664
800-822-3000 Repair
AT&T
P.O.Box 78522
Phoenix, AZ
85062-8522
Telecom
800-524-2333
800-222-3000 Service
(800)7204503
(888)2984663
800-222-0400 Orders
Nextel
1620 North Mamer
Road
Suite C-400
Spokane, WA
99216
Telecom
888-404-8830
586518425
Cellular
509-879-0406 Jennifer
Workman
Verizon Wireless
P O Box 96082
Bellevue, WA
98009
Telecom
800-922-0204
7714119210001
Cellular
Paul Cox
509-670-6006
47
APPENDIX G: Central Washington University: Network Diagrams
Printouts of the Central Washington University network architecture diagrams are included with the
hardcopy version of this plan.
48
APPENDIX H: Excerpt from the Emergency Preparedness Plan
SECTION 2
Emergency Preparedness Organizational Chart
Board of Trustees
*
President
*
Emergency Coordinator
(Executive Assistant to the President)
*
Emergency Council
Council Members
Response Coordinator (Director of Public Safety and Police Services)
Emergency operations center/communications systems (Radios)
Field operations (Police Services)
Coordination with responding agencies
Security/access for restricted and sensitive areas
Short and advanced warning notice/call list
Search and rescue
Facilities Coordinator (Director of Facilities Management)
Building/grounds assessment, inspection, and operations
Utility assessment, inspection, and operations
Field operations (Facilities Management Services)
Coordination to Telco, Data, and Video Systems
Emergency sanitation facilities
Arrange for temporary classroom facilities
Coordination of utilities with outside agencies
Finance Coordinator (VP for Business and Financial Affairs)
Registration of emergency workers
Cash and negotiables safeguarding
Record keeping
Emergency purchases and leasing
Data safeguarding
Academic Coordinator (Provost)
Coordinate on-going teaching/classroom operations
Arrange for temporary classroom equipment
Arrange for temporary faculty resources
Student Affairs (VP for Student Affairs and Enrollment Management)
Student support and counseling
Emergency Shelter
Emergency feeding
Sign-up and organize emergency workers/message runners
Mass casualty/medical services center/liaison
Disabled people
49
Community Relations (VP for University Relations)
Media Liaison
Public relations
Emergency message/contact center
Organize video documentation of damage
Business Services (Director of Business Services and Contracts)
Emergency proclamations
Emergency contracts
Risk Management
Supply and procurement
50
Appendix J – Business Impact Matrix
CWU IT
System
Business
Impact
Matrix
Alumni*
Blackboard
Campus
Security
(CAMPSA)
*
Central
Stores
Conference
Center
(CCS)*
Course
Manageme
nt (R25)
Daycare
Manageme
nt*
Diebold/CB
ord*
Dining
Services
(DINE,Com
putrition)*
Electronic
Mail
Facilities
Planning
(WOS)*
File
Services
Finance
(FMD)
Financial
Aid (HRSA)
Health
Services
Housing/Re
snet
Institutional
Research*
Instructiona
l
Computing
(MTIS)
Library*
Parking
(CPAS)*
Safari
(Payroll/AP
/AR)
Telecommu
nications
University
Store
(POSS/Cen
store)*
Web
Services
Web
Services
Income
maintenance
for citizens
Income
maint. for
gov.
employees
Payme
nts to
vendor
s for
G&S
Requireme
nts for
compliance
or
regulation
Effect of
state
governmen
t cash flow
Recovery
Costs
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
H
L
L
L
L
M
L
L
H
L
L
H
L
L
H
H
H
H
H
H
H
M
L
L
L
L
L
L
L
H
M
M
L
L
L
L
L
L
L
L
L
L
L
L
L
H
L
L
L
H
L
L
L
L
L
L
L
M
L
H
L
H
L
H
L
H
M
L
L
L
H
L
L
L
L
L
H
L
H
L
H
L
H
H
H
L
H
L
L
L
L
L
H
H
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
M
M
L
L
L
L
L
M
H
H
H
L
L
L
L
L
L
L
L
L
M
M
H
H
M
H
L
H
H
H
H
H
H
L
H
H
H
H
H
H
L
H
M
H
H
H
H
L
M
H
H
H
M
M
L
L
L
M
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
L
H
L
L
L
L
L
L
H
L
L
L
H
H
H
H
H
H
H
H
H
H
L
H
L
L
L
L
M
L
L
L
L
L
L
L
L
L
M
L
L
L
L
L
H
L
L
H
H
L
H
H
L
L
L
Maintenance
of Public
health and
safety
Effect on
product and
delivery of
services
Volume
of
activity
Effect
on
public
image
Inter-system
dependency
51
Appendix K - Threat and Vulnerability Matrix - Physical
THREAT
VULNERABLE
RESULT
AREAS
Electrical outages
Computer Center
-Equipment Damage
Fluctuations
Networks
-Denial of Service
LANs
-Data Destruction
Telephone Service
-Data Corruption
Telecommunicatio
Main Computing
-Denial of Service
n Network Failure
Networks
LANs
Telephone Service
Hardware Failure
Computer Center
-Denial of Service
Networks
-Data Destruction
LANs
-Data Corruption
Telephone Service
-Equipment Loss
System Software
Failure
Alteration of
Software
Application
Software Failure
Main Computing
Networks
-Denial of Service
-Data Destruction
-Data Corruption
Applications
-Denial of Service
-Data Destruction
-Data Corruption
Fire
Computer Center
Networks
LANs
Telephone Service
-Denial of Service
-Data Destruction
-Equipment Loss
-Facility Loss
Water Damage
Computer Center
Networks
LANs
Telephone Service
Databases
Software
System integrity
-Denial of Service
-Data Destruction
-Equipment Loss
-Facility Loss
-Data Corruption
-Data Destruction
-Denial of Service
-Confidentiality
breach
Computer Center
Networks
LANs
Telephone Service
-Denial of Service
-Equipment Loss
-Facility Loss
-Data Destruction
-Data Corruption
File Alteration (Accidental or
Intentional)
Disclosure
System user error
Employee Sabotage
Unauthorized Use
Viruses
Physical Security
Unauthorized Use
Fraud
External Sabotage
Hackers
PROTECTIVE
MEASURES
UPS System
System Backups
Generator
Staff Training
Alternate routing
UPS System
Generator
Staff Training
On-Site Engineer
Hardware contracts
24-hour support by
Networks & Operations
System Backups
Staff Training
Software support by
vendor
System Backups
Staff Training
24-hour support by
applications
System Backups
Staff Training
Fire alarm systems
Halon systems
Employee training
Access control
Structural Design
Off-site backups
Contingency Plan
Structural Design
Off-site backups
Contingency Plan
Off-Site backups
Security auditing
Login authentication
Audit trails
Access control
Security monitoring
System Backups
Staff Training
Access control
Structural design
Employee training
System Backups
Login authentication
RISK
High
High
High
Low
Medium
High
High
High
Medium
52
THREAT
Civil Disturbances
Dam Collapse
Earthquake
Flood
Lightening
Smoke, dirt, dust
Snow/Ice Storm
Volcano
Windstorm
Bomb Threats
Building Collapse
Epidemics
Explosions
Hostage Taking
Hurricanes
Landslides
Liquid leakage
Nuclear Reactor
Accident
Panic Crushes
Sandstorms
Strike
Terrorism
Thermo-Nuclear
Disaster
Tidal Waves
Tornado
Toxic Spills
Tsunami
Theft
VULNERABLE
AREAS
RESULT
PROTECTIVE
MEASURES
Staff Training
Structural design
System Backups
Contingency Plan
RISK
Computer Center
Networks
LANs
Telephone Service
-Theft
-Denial of Service
-Equipment Loss
-Facility Loss
-Data Destruction
Computer Center
Networks
LANs
Telephone Service
-Denial of Service
-Equipment Loss
-Facility Loss
-Destruction of data
Structural design
System Backups
Contingency Plan
Low
Computer Center
Databases
-Confidentiality
breach
-Equipment Loss
Access control
Login authentication
Separation of duties
Staff Training
High
Medium
53
Appendix L – Tape Inventory
Here are the current inventory procedures for backup tapes.
Operations staff take tapes over daily and bring back the ones that are being replaced.
(These are the LMS nightly processing backups).
Operations takes the weekly VMS cumulative backup tape over on Mondays. It dismounts
Sunday and a new, prestaged backup initiates Monday morning at 6:30 am. Again, Operations
returns the tape being replaced. weekly backups are retained for 30 days and the monthly
backups for 365 days. Only the most current monthly backup is stored in the vault, older
monthlies are stored in the on site tape repository.
Networks & Operations staff (Larry Beintema) uses the oldest monthly backups (created 1
year earlier) from Legato as scratch tapes for the current monthly backup. Operations brings
them over the Monday after the first weekend of the month and returns the newly created
backups the following morning.
Operations takes backup tapes from the email machines and the VCS console to the vault
on Monday and brings the tapes being replaced back.
There are currently old tapes that were created with 5 and 10 year retentions stored in the
vault and they are returned and scratched as they expire.
Each of the above backups has their own space in the vault so they are easily identified and
retrieved when necessary.
54