Critical Incident Management Plan Version 2
Critical Incident Management Plan Version 2
Critical Incident Management Plan Version 2
ITResourcesCriticalIncidentResponsePlan
1. Purpose
2. Definitions
5. Procedures
6. Infrastructure & Setup of a Command Centre a) Equipment Required b) Location of the Centre
ITResources
1. Purpose
To ensure the University is able to respond effectively and efficiently to an emergency situation occurring on or off campus a Critical Incident Management plan has been developed. This prepares the University for a timely response to critical incidents, reduces impact and assures the continuation of operations and restoration of normal activity as quickly as possible. IT Resources provide Information Communications Technology infrastructure and services to the University Community in support of the Universitys mission. In this role, IT Resources provides critical services in support of teaching, learning, and research and general business needs such as communications and information management. IT Resources have developed a Critical Incident response plan, in association with the University. This plan has been developed to prepare our key personnel to provide and coordinate an effective response to ensure minimal disruption to business operations in the event of emergency.
Assumptions
1. 2. 3. 4. Incident occurs during business hours Staff resources are available Electronic communications are available (emails and phones are working) Command Centre only established in Hobart Sandy Bay Campus
2. Definitions
Term/Abbreviation Critical Incident Definition Any incident which include: Cause of death or serious injury to persons on or near University property Significantly damage property or equipment contained on University premises Severe impact on the effective operation of the campus and in result negative media attention Result in adverse legal consequences for the University and or employees The name given to those key personnel responsible for implementing the Critical Incident Management Plan
ITResources
Page1of 11
John Parry Adrian Dillon John Miezitis Virginia Ryan The Command Centre is the location selected by the Critical Incident Management Team to be used by them to develop responses and manage the recovery process in a long term crisis situation. The person responsible for coordinating the initial University campus response to a Critical Incident or emergency.
Command Centre
ITResources
Page2of 11
3. CriticalIncidentManagementPlanOverview
ITResources
Page3of 11
Contact Name
Julian Direen Technical Support Andrew Jenkins Bruce Morgan Russell Facer or Tony Dillon Karen Murfett
Phone No.
03 6226 3647 1800 060 889 0409 992 707 03 6245 0155 0408 882 390 03 6270 4111 03 6234 9349 13 1548 03 6273 0155 0408 412 068
Greg Hall
Internal Contacts
Hobart Campus Emergency Coordinators Asset Management (All Campuses) ITR OH&S Officer Security Launceston Campus Emergency Coordinators ITR OH&S Officer Security Cradle Coast Campus Campus Emergency Coordinators ITR OH&S Officer Security Frank Hay Mark Stemm 03 6324 3900 03 6324 4907 03 6324 3336 Peter Rowland Troy Finearty Greg Dicinoski Barry Russell Kathryn McGuinness 03 6226 1932 03 6226 2694 03 6226 2166 03 6226 2688 03 6226 6351 03 6226 7600
ITResources
Page4of 11
5. Procedures
C om m unicationsProcessC hartforC riticalIncidentR esponse
R es p on sib le o ffic er
R e fe rto m a nag em e nt
ITResources
Page5of 11
CommunicationsProcessChartforCriticalIncidentResponse Level1IncidentExample
Minornetworkoutageto section
Criticalincidentoccurs
JohnMiezitis(Comms)
Responsibleofficer
Incidentisidentified andclassified
Incidentexistsonlistof predefinedCIs
Comparetolistof predefinedincidents
Referto management
Enactcommunications strategy.
ITResources
Page6of 11
CommunicationsProcessChartforCriticalIncidentResponse Level2IncidentExample
SmallFireinNodeRoom intheFacultyofBusiness, SandyBayCampus
Criticalincidentoccurs
AdrianDillon(SandyBay Coordinator)
Responsibleofficer
Referto management
Enactcommunications strategy.
ITResources
Page7of 11
Incidentisidentified andclassified
CommunicationsProcessChartforCriticalIncidentResponse Level3IncidentExample
SeriousFireinthe CorporateServices Building(DataCentrestill operational)
Criticalincidentoccurs
AdrianDillon&JohnParry
Responsibleofficer
Incidentisidentified andclassified
Incidentexistsonlistof predefinedCIs
Comparetolistof predefinedincidents
Referto management
Notifyappropriate EmergencyContacts
Internal Response
ITRfollowexternal response
External Response
ITResources
Page8of 11
Activation Coordination
John Parry Adrian Dillon Jennifer Nield Virginia Ryan John Buttery Michael Harlow Mark Zimmerli Brett Clifford
John Miezitis Virginia Ryan Colin Broadbent Andrew FenneyWalch Nick Grundy Dave Watson Michael Bonsey
Deployment
Level 2 Incident Local room in Corporate Services Building Level 1, Resolve Meeting Room Or Level 2, Meeting Room 3 Alternatively a lab within the University Campus Hbt / Lton / CCC Level 3 Incident Local room if available (Executive Meeting Rooms Lton/Hbt) Move to Launceston (off campus) Offsite location (non University)
ITResources
Page9of 11
EquipmentRequired Seats&Tables FirstAidKit Whiteboards GeneralStationery Pens Paper Writingpads Staplers Folders Tea&Coffee TelephoneConnection Mobiles PABX POTS FaxMachine PABX POTS 5xDesktopComputers Wireless DSL LAN Photocopier Printers USBCable Paper(A3&A4) Television/Radio Powerboards&extension cords Torches&batteries VideoConferencing Equipment
JohnMiezitis
ITResourceOffice
JenniferNield/JoCowen
ITResourcesorsource fromUniversityLabs
Procurement/DMS
ITResourcesorsource fromUniversityLabs
Procurement/DMS
Procurement
ITResources
KathrynMcGuinness
ITResources
Page10of 11
7. DamageAssessment&Recovery
Adocumenthasbeenpreparedtorecord,classifyanddocumentrecoveryfroma CriticalIncident.Thisdocument,theITResourcesCriticalIncidentReport, classifieseachincidentaccordingtothreatlevelandtype, detailsareasand resourcesaffected,andalsodetailsrecoveryandmitigationprocesses. TheITResourcesCriticalIncidentreportwillbemadeavailabletoallmembers oftheCriticalIncidentManagementControlTeam.Thereportisattachedasan appendixtothisreport.
ITResources
Page11of 11