OPERATIONAL SUPPORT FUNCTION Emergency Level Notifications. Office of Emergency Management

Transcription

1 City of Toronto Emergency Plan OPERATIONAL SUPPORT FUNCTION Emergency Level Notifications Office of Emergency Management Version 5.0 December 2013

2 Revision History Revision Number Name of Contributor Summary Of Changes Revision Date 1.0 Office of Emergency Management Updated as required February Wayne Banon (OEM) Updated as required August 19, Loretta Chandler & Wayne Banon (OEM) Converted existing OSF to New Template Updated as required Revised with EMWG input 4.0 Wayne Banon (OEM) As per Ombudsman Report Emergency Levels Table Level 2 OEM Must Notify DCM Cluster 'B') Level 3 OEM Must Notify DCM 'B', EMWG, TEMPC & Control Group and Key Divisions 5.0 Wayne Banon (OEM) Revisions as per changes to City's Emergency Plan December 28, 2012 February 25, 2013 December 19,

3 3 Table of Contents 1.0 Introduction Purpose Scope Concept of Operations General Emergency Level Notifications Emergency Level Classifications Level 0 Normal Level 1 Minor Incident Level 2 Major Incident Level 3 Emergency Incident Notifications Office of Emergency Management's 'Standby' Mailbox Telephone Number Office of Emergency Management's 'Standby' OEM Activation Event Summary Form Authority to Activate the Emergency Operations Centre Office of Emergency Management Immediate Response Councillor Notification & Roles in an Emergency Roles and Responsibilities Primary / Lead Agency / Division Office of Emergency Management 'Standby' Office of Emergency Management (OEM) Coordinator Supporting Agency / Division Toronto Emergency Management Program Committee TEMPC Control Group Emergency Management Working Group (EMWG)... 18

4 Strategic Communications APPENDIX 'A': Toronto Emergency Management Program Committee (TEMPC) Members APPENDIX 'B': TEMPC Control Group Members APPENDIX 'C': Emergency Management Working Group (EMWG) APPENDIX 'D': Emergency Management Working Group (EMWG)... 22

5 5 Operational Support Function Emergency Level Notifications Primary / Lead Agency / Division: Office of Emergency Management (OEM) Supporting Agencies / Divisions: (ABCD's) Toronto Emergency Management Program Committee (TEMPC) TEMPC Control Group Emergency Management Working Group Strategic Communications External Supporting Agencies: N/A 1.0 Introduction Under the direction of the Toronto Emergency Management Program Committee s (TEMPC) Control Group (CG), the Office of Emergency Management's (OEM) primary responsibilities focus on the City s emergency management program, the implementation of the City s Emergency Plan and the operation of the Emergency Operations Centre (EOC) during a Major Incident or Emergency Incident affecting all, or a large portion of the City. Daily activities involve the City s emergency management program as defined in the Ontario Emergency Management and Civil Protection Act (Reg. 380/04). The Emergency Management and Civil Protection Act Ontario (1990, c. E.9) defines emergency as "a situation or an impending situation that constitutes a danger of major proportions that could result in serious harm to persons or substantial damage to property and that is caused by the forces of nature, a disease or other health risk, an accident or an act whether intentional or otherwise". 1.1 Purpose The purpose of this Operational Support Function is to outline the response capabilities of the Office of Emergency Management in the event of an emergency in the City of Toronto. It outlines Office of Emergency Management s scalable response based on the magnitude of the event or impending situation. This OSF also provides guidance on emergency notification protocols. As a guideline, it provides the Office of Emergency Management with a general basis for notification and contacts to be made during emergencies of varying magnitude and complexity.

6 6 1.2 Scope The scope of this document is limited to the decision making processes and notification steps taken by the Office of Emergency Management. This guideline is limited to the OEM s response capabilities and activities applicable to the operation of the City s Emergency Operations Centre and the OEM response during a Major Incident or Emergency Incident in the City of Toronto. This document provides the OEM with a general basis for notification and contacts to be made during emergencies of varying magnitude and complexity. 2.0 Concept of Operations 2.1 General Operational Support Functions are supporting documents to the City of Toronto Emergency Plan (COTEP). While these are stand-alone documents not contained in the Emergency Plan they contain the structure and framework for integrated support by Lead and Supporting Agencies, Boards, Commissions and Divisions (ABCD's) in the most frequently grouped operational functions responding to emergencies. Figure 1 illustrates the relationship between the Toronto Emergency Plan, this Emergency Level Notifications OSF, and the other OSFs and Risk Specific Plans (formerly Emergency Operating Procedures EOPs).

7 7 City of Toronto Emergency Plan Operational Support Functions and Risk Specific Plans Identification of Lead Agencies Toronto Emergency Plan Operational Support Functions (OSF s) Risk Specific Plans (RSP s) Emergency Level Notifications OEM Emergency Information Strategic Communications Nuclear OEM Toronto Public Health Plan for an Influenza Pandemic Toronto Public Health Emergency Operations Centre OEM Evacuation Police Service Power Disruption (Electricity) OEM Toronto Hydro Fuel Distribution Fleet Services Incident Management System OEM Mass Casualty Emergency Medical Services Floods Toronto & Region Conservation Authority Animal Care & Relief Municipal Licensing & Standards Mass Fatality Police Service Damage Assessment Toronto Building Psychosocial Response & Recovery Toronto Public Health Debris Management Solid Waste Management Shared Fleet Management Fleet Services Donations Management Office of Partnerships Traffic Management Transportation Services Emergency Human Services OEM Volunteer Management Human Resources Figure 1

8 8 2.2 Emergency Level Notifications Most emergencies are managed at the scene by Emergency Services (Police, Fire & EMS) and the City Divisions and Agencies (Water, Transportation, etc.) and are considered routine operations. (Emergency Level 0 Normal). See Table 1. Emergencies of greater magnitude do happen and require an emergency management response structure beyond normal daily operations. The response required must be appropriate to the magnitude of the incident as defined in the Emergency Levels classification. (Emergency Level 1 Minor Incident; Emergency Level 2 Major Incident and Emergency Level 3 Emergency Incident).

9 9 Table 1: Emergency Level Notifications Levels LEVEL 0 NORMAL LEVEL 1 MINOR INCIDENT LEVEL 2 MAJOR INCIDENT LEVEL 3 EMERGENCY INCIDENT Operational Implications Business as Usual Normal Operations Site: Managed by Emergency Services / Divisions Site: Managed by Emergency Services / Divisions Site: Site Incident Commander may request support from OEM 'Standby' Site: May request the activation of the EOC EOC: May be Activated EOC: Is Activated Emergency poses a danger of major proportions to life and property, and / or threatens social order and ability to govern, and / or a declaration of an emergency by another level of government. OEM Support EOC Notification Business as Usual Normal Operations OEM support available 24 / 7 via 'Standby' At the Request of the Site Incident Commander OEM 'Standby' has the ability to: Facilitate access to City Divisions, External Agencies and / or Facilitate integration of City Divisions /External Agencies into IMS structure and / or Attend Site as a Liaison Officer OEM 'Standby' Coordinator remains as Liaison Officer at the Site. Operationally Ready Operationally Ready Operationally Ready OEM 'Standby' may Monitor OEM Director may Activate the EOC EOC Activated No OEM Notification Required No OEM Notification Required Once Notified, OEM: Must Notify City Manager, Deputy City Manager, Cluster 'B' if OEM support is required May Notify Emergency Management Working Group (as required) May Notify Other Key Divisions / Agencies (as required) Once Notified, OEM: Must Notify City Manager, Deputy City Manager, Cluster 'B' Must Notify EMWG / TEMPC / Control Group Must Notify Other Key Divisions / Agencies

10 Emergency Level Classifications To identify the most appropriate Office of Emergency Management response to an incident it is useful to designate an Emergency Risk Level. The response required must be appropriate to the magnitude of the incident as defined in the Emergency Level Classification Level 0 Normal Normal operations Mobilize resources to meet standards Business as usual for emergency services and operational Divisions. At this Level, there is a low risk to City operations Level 1 Minor Incident A small event that can be managed with existing emergency services resources and minimal support from other ABCDs. At this Level, there is a low to moderate risk to City operations. Generally, this type of incident will impact a single facility or community and may or may not require response by agencies beyond emergency services. This Level would be considered a contained incident i.e. there are controls in place to respond to an irregularity, and the community is expected to cope. Minor Incidents are generally limited to One Site Responders experience some difficulty mobilizing resources to meet standards Two or more Agencies involved Level 2 Major Incident At this Level there is moderate to high risk to people, property and / or City operations. Multiple facilities and / or business / economic stakeholders may be impacted with a response needed across more than three ABCD's. These incidents are usually within the capabilities of the City of Toronto and may include a response by external agencies. This could be considered an uncontained incident within the City i.e. controls have failed or are failing to cope. At this Level the Mayor may declare an emergency. Major Incidents may involve Two or more Sites Require three or more ABCD's to coordinate response activities to meet standards Limited Evacuations or Shelter in Place High Media attention Office of Emergency Management: o Must Notify Deputy City Manager, Cluster 'B' o May Notify EMWG and Other Key Divisions / Agencies (as required)

11 Level 3 Emergency Incident An emergency of this level requires City-wide coordination and has high media interest which extends the City of Toronto's emergency response resources to its extremes. At this level the incident is impacting the wider organization and extraordinary resources are required. A Level 3 Emergency usually involves Multiple Sites Regional disaster beyond City of Toronto boundaries Multiple ABCD's response and external partners Extensive Evacuations or Shelter in Place High Media attention Office of Emergency Management: o Must Notify Deputy City Manager, Cluster 'B' o Must Notify EMWG, TEMPC, Control Group and Other Key Divisions / Agencies (as required) 2.4 Notifications In the event of an emergency of sufficient magnitude to be classified as a Level 2 or Level 3 incident, as described in Emergency Level Notifications Table (Table 1), the Office of Emergency Management 'Standby' Coordinator will initially be contacted by the Toronto Police Communications Centre or a member / representative of the Toronto Emergency Management Program Committee as their Divisions are often directly involved in site response, e.g. Toronto Water, Transportation Services. Upon receiving an emergency notification the 'Standby' Coordinator will liaise with the notifying Service, Division / Agency and utilize the Emergency Levels Notification Table (Table 1) as a tool to assist in establishing the immediate notifications that may be necessary and / or appropriate and further notifications that may be required in the following 1 to 24 hours Office of Emergency Management's 'Standby' Mailbox Telephone Number The Office of Emergency Management s 'Standby' Coordinator can be reached 24 Hours a Day / 7 Days a Week by calling the designed number.

12 Office of Emergency Management's 'Standby' OEM Activation Event Summary Form The Office of Emergency Management s 'Standby' Coordinator is responsible for completing the 'Standby' OEM Activation Event Summary Form when they are Notified of a Level 2 or Level 3 emergency incident by one of the Emergency Services or Divisions. A copy of the "OEM Activation Event Summary Form" is found in Appendix 'D' of this OSF. Details obtained of the Call and Event include Caller Information o Contacted by: Name and Telephone Number o Date & Time Incident Information o Type / Scale o Address Incident Details o Who is On Scene o Who has been Notified o Estimated Duration o OEM Requested to Site? Other Information (Type / Duration or EHS Response OEM Activation: Next Steps Authority to Activate the Emergency Operations Centre This Emergency Level Notifications Operational Support Function identifies the circumstances under which the EOC will be activated. Any member of the TEMPC, Control Group or Working Group has the authority and responsibility to request an activation of the EOC and otherwise initiate the implementation of the Emergency Plan. Requests to activate the EOC are directed to either the Director of the Office of Emergency Management or to the OEM's 24 hour a day, 7 days a week 'Standby' Coordinator. The Emergency Level Notifications Operational Support Function identifies the criteria and triggers which the Emergency Operations Centre (EOC) will be activated. During a "Level 2 - Major Incident", the Site Incident Commander may request support from the Office of Emergency Management (OEM), including requesting the activation of the EOC. During a "Level 3 - Emergency Incident", the OEM will activate the EOC. Criteria and triggers for activating the EOC are based on the Emergency Levels Protocol and a culmination of the following decision factor guidelines contributing to heightened media attention:

13 13 Public Health & Safety (Actual or Potential) Essential Lifelines (Critical Infrastructure) Municipal Services Continuity Operational Efficiency The EOC may be activated with or without a Declaration of an Emergency or Provincial Emergency; however, it will be activated once a Declaration has been made. Additional details about the activation and operation of the City's Emergency Operations Centre can be found in the following Emergency Operations Centre (EOC) Operational Support Function, and Incident Management System (IMS) Operational Support Function Office of Emergency Management Immediate Response The Office of Emergency Management s immediate emergency response is dependent on the complexity and risk presented by an emergency as defined in the Emergency Levels Decision Factors Guideline (Table 2). The Table outlines OEM's scalable response based on the magnitude of the event or impending situation. Table 2 is to be used as a general guideline only. It is not possible to consider all the variables of complexity involved in any specific event, such as time of day, time of year, geographic location(s), etc. As a guideline, it is not intended to quantify the extent of the City s response, the extent of the risk, the affect on the rest of the City and surrounding area or the degree of public concern. As emergency responses progress, the assigned emergency level may change as additional information and details are received. Specific circumstances will require ad hoc decisions to be made at the time of the event. This is a normal and expected element of response.

14 14 Table 2: Emergency Levels Decision Factor Guidelines Levels/Issue LEVEL 0 NORMAL Public Health and Safety (Actual or Potential) Death or Serious Injury Risk OR Evacuation or Shelter in Place, providing care for: 1 to 30 Persons for 1 to 4 Hours Essential Lifelines (Major Utilities) Failure affecting less than 5,000 Households for: Less than 4 Hours Municipal Services Continuity Interruption for: Less than 1 Hour Operational Efficiency Mobilize resources to meet standards Events House Fire Motor Vehicle Accident Road Closures LEVEL 1 MINOR INCIDENT LEVEL 2 MAJOR INCIDENT LEVEL 3 EMERGENCY INCIDENT Up to 5 Deaths or Serious Injuries, OR Evacuation or Shelter in Place, providing care for: 30 to 100 Persons, OR Suspected unusual number of cases of communicable disease infections among general population 6 to 10 Deaths or Serious Injuries at One Location OR Evacuation or Shelter in Place, providing Mass Care for: 100 to 1,000 Persons OR Confirmed unusual number of cases of communicable disease infections among general population More than 6 to 10 Deaths or Serious Injuries at Multiple Locations, OR Evacuation or Shelter in Place, providing Mass Care for: > 1,000 Persons from Multiple Dwellings, OR Extreme number of cases of communicable disease infections or confirmed Pandemic situation Failure affecting 5,000 to 10,000+ Households for: 4 to 12 Hours Failure affecting 5,000 to 10,000+ Households for: 12 to 24 Hours Failure affecting 10,000+ Households for: Longer for 24 Hours Interruption for: 1 to 24 Hours Interruption for: 1 Day to 1 Week Extended interruption for: Underdetermined length of time Difficulty in mobilizing resources to meet standards 2 or more agencies Requires coordination of 3 or more ABCD's to meet standards Requires coordination of all available resources Localized Power Failures January 2009 May 2010 July 2010 H.S.E. Hickson Chemical Court Fire (1998) Finch Avenue Bridge Washout (2005) 2 Secord Avenue (2008) Queen Street Fire (2008) Wellesley High-rise Fire (2010) Northeast Power Outage (2003) SARS (2003) Sunrise Propane Explosion (2008) G-20 (2010)

15 Councillor Notification & Roles in an Emergency In addition to the Emergency Levels Decision Factors Guideline the Toronto Emergency Management Program Committee approved a notifications protocol for the Mayor and City Councillors. Most emergencies are managed at the Site by Emergency Services and City Divisions and are considered routine operations. Some Divisions already have pre-established notification procedures with Councillors. For example, Toronto Fire Services and Shelter, Support and Housing Administration (Emergency Human Services) have canvassed Members of Council to develop preestablished notification protocols for routine operations. Emergencies of greater magnitude do happen and require an emergency management response structure beyond Normal Daily operations. The response required and / or requested by City of Toronto Councillors must be appropriate to the magnitude of the incident as defined in the Emergency Levels classification. It is important for Councillors to understand and support the coordinated and timely management of information. Every effort should be made to maintain a streamlined information management process and avoid the passing of inaccurate, conflicting and / or misleading information to the Public, City Staff, and the Media. Table 3 outlines the scalable response based on the magnitude of the event or impending situation. The table outlines how Councillors will be notified during emergencies and their roles during the incident in its initial and subsequent stages.

16 16 Table 3: Councillor Notification & Roles in an Emergency Emergency Levels LEVEL 0 NORMAL LEVEL 1 MINOR INCIDENT LEVEL 2 MAJOR INCIDENT LEVEL 3 EMERGENCY INCIDENT Operational Implications Business as Usual Normal Operations Site: Managed by Emergency Services / Divisions Site: Managed by Emergency Services / Divisions Site: Site Incident Commander (IC) may request support from OEM 'Standby' Site: May request the Activation of Emergency Operations Centre EOC: May be Activated Emergency Operations Centre (EOC): is Activated Emergency poses a danger of major proportions to life and property, and / or threatens social order and ability to govern, and / or a declaration of an emergency by another level of government Notifications Roles Sample Events Division(s) on Site will continue to follow established Internal Notification / Escalation Procedures Division(s) on Site will continue to follow established Internal Notification / Escalation Procedures Division(s) to Notify Deputy City Managers (DCMs) of the incident and confirm Direction and Future Notifications Division(s) to Notify Strategic Communications of incident Strategic Communications to Notify Mayor and Members of Council of Incident OEM to Notify DCM, Cluster 'B' who in turn Notifies the City Manager and Mayor DCM, Cluster 'B', City Manager and Mayor discuss Direction and Next Steps City Clerk's Office to Notify affected City Councillors, as required DCM, Cluster 'B' and OEM to Notify Members of Control Group / Emergency Management Working Group If Mayor declares an emergency, City Clerk's Office to Notify Members of Council No Action required Generally No Action required Strategic Communications to Notify Mayor and affected Members of Council of Incident Site to provide updates to Councillors and 311 Toronto as needed Councillor Roles: Assist relaying information to residents Attend Community or Evacuee Meetings Reassure constituents Support action taking place in community Liaise back through Mayor concerns from within Wards Follow leadership and requests of Mayor Strategic Communications communicates critical information from the Emergency Operations Centre (EOC) and City officials to Members of Council, 311 Toronto, City staff, community leaders, residents, businesses and the media If Mayor declares an emergency, City Clerk's Office to Notify Members of Council Severity House Fire Vehicle Accident Road Closure Localized Power Failure Yonge & Gould Fire (2011) Queen Street West Fire (2008) H.S.E. Hickson Fire Chemical Court (1998) Finch Avenue Bridge Washout (2005) 2 Secord Avenue (2008) Wellesley High- Rise Fire (2010) G-20 Summit (2010) Sunrise Propane Explosion (2008) Northeast Power Outage (2003) SARS (2003)

17 Roles and Responsibilities 3.1 Primary / Lead Agency / Division Office of Emergency Management The role of the OEM is to strengthen the City's ability to prepare, respond and recover from major emergencies. The OEM is responsible for coordinating preparedness, mitigation, response and recovery activities for any major emergency or disaster (manmade or natural) affecting the City of Toronto. This is achieved through: Maintaining the City's Emergency Plan Acting as curator of this Operational Support Function Ensuring that this OSF complies with the City's Emergency Plan, and all other Operational Support Functions (OSFs), Risk Specific Plans and other relevant City of Toronto, Provincial and Federal emergency management legislation Ensuring Emergency Operations Centre Readiness Supporting implementation of the City Incident Management System at both site and Emergency Operations Centre levels Conducting Training Developing a multi-year comprehensive exercise program Conducting a Hazard Identification and Risk Assessment Delivering Public Education and Outreach 'Standby' Office of Emergency Management (OEM) Coordinator An OEM Staff member is available 24 hours / 7 days a week via 'Standby' Telephone Number for all incident support. OEM 'Standby' Coordinator has the ability to: Facilitate access to City Divisions / External Agencies; and / or Facilitate integration of City Divisions / External Agencies into IMS structure; and / or Attend Incident Site as a Liaison Officer 3.2 Supporting Agency / Division Toronto Emergency Management Program Committee The City of Toronto Emergency Management Program Committee (TEMPC) provides the City with an effective vehicle for developing and maintaining a comprehensive emergency management program, as defined under the Emergency Management Act. See Appendix 'A' for complete list of TEMPC Members.

18 TEMPC Control Group In the event of an emergency, the Toronto Emergency Management Program Committee convenes as it becomes reactive. Of the 28 members listed, the first 16 members would form the TEMPC Control Group to oversee the City's emergency response. The Mayor or designate will act as Chair of the Control Group as specified in the existing Code Chapter. The Control Group is responsible for managing the strategic response to an emergency and providing support to the site operations. Additional representation of organizations will be determined by the nature of the emergency. See Appendix 'B' for complete list of the Control Group Members Emergency Management Working Group (EMWG) The Emergency Management Working Group (EMWG) supports the efforts of the TEMPC through the development of plans and procedures that are coordinated among the Agencies, Boards, Commissions, and Divisions of the City. See Appendix 'C' for complete list of EMWG Members Strategic Communications The Strategic Communications Division is responsible for implementation and oversight of the City of Toronto's communications activities. The Division will provide advice to the City's Agencies, Boards, Commissions and Corporations (ABCCs) as required, or as directed by the City Manager. Strategic Communications is responsible for communicating critical information before an impending incident (if applicable), during and after a major disaster or public emergency on behalf of the Emergency Operations Centre (EOC) and City officials to 311 Toronto, City staff, Members of Council, community leaders, residents, businesses and the media. Additional information about this protocol can be obtained from the Strategic Communications Division's Emergency Information & Media Relations Operational Support Function.

19 19 APPENDIX 'A': Toronto Emergency Management Program Committee (TEMPC) Members 1. Mayor 2. Deputy Mayor 3. City Manager 4. The Deputy City Manager, Cluster 'A' 5. The Deputy City Manager, Cluster 'B' 6. The Deputy City Manager and Chief Financial Officer Cluster 'C' 7. Chief of Police 8. Fire Chief and General Manager of Fire Services 9. Chief and General Manager of Emergency Medical Services 10. Medical Officer of Health 11. Director of Strategic Communications 12. Executive Director of Human Resources 13. Chief Executive Officer of Toronto Transit Commission 14. General Manager of Transportation Services 15. General Manager of Toronto Water 16. General Manager of Shelter, Support and Housing Administration 17. City Solicitor 18. City Treasurer 19. Chief Corporate Officer 20. Chief Building Official and Executive Director of Toronto Building 21. General Manager of Parks, Forestry and Recreation 22. General Manager of Solid Waste Management Services 23. Executive Director of Facilities Management 24. Chief Information Officer 25. Manager of Insurance and Risk Management 26. Director of Office of Emergency Management 27. City Clerk 28. Toronto Hydro

20 20 APPENDIX 'B': TEMPC Control Group Members 1. Mayor 2. Deputy Mayor 3. City Manager 4. The Deputy City Manager, Cluster 'A' 5. The Deputy City Manager, Cluster 'B' 6. The Deputy City Manager and Chief Financial Officer, Cluster 'C' 7. Chief of Police 8. Fire Chief and General Manager of Fire Services 9. Chief and General Manager of Emergency Medical Services 10. Medical Officer of Health 11. Director of Strategic Communications 12. Executive Director of Human Resources 13. Chief Executive Officer of Toronto Transit Commission 14. General Manager of Transportation Services 15. General Manager of Toronto Water 16. General Manager of Shelter, Support and Housing Administration 17. Director of Office of Emergency Management

21 21 APPENDIX 'C': Emergency Management Working Group (EMWG) Depending on the emergency incident, staff from various City Divisions will form the Emergency Management Working Group (EMWG) and will sit in the Operations Section of the Emergency Operations Centre. This includes staff representatives from the following City Agencies, Boards, Divisions and Commissions: 1. Office of Emergency Management (Chair) 2. Toronto Police Service 3. Toronto Fire Services 4. Toronto Emergency Medical Services 5. Toronto Public Health 6. Strategic Communications 7. Toronto Water 8. Transportation Services 9. Shelter, Support and Housing Administration 10. Toronto Building 11. Toronto Transit Commission 12. Purchasing and Materials Management 13. Facilities Management 14. Engineering and Construction Services 15. Solid Waste Management Services 16. Parks, Forestry and Recreation 17. Toronto Office of Partnerships 18. Finance and Administration 19. Human Resources 20. Information and Technology 21. City Clerk's Office Toronto 23. Toronto Hydro

22 22 APPENDIX 'D': Emergency Management Working Group (EMWG) OEM ACTIVATION Event Summary Form OEM Staff: Date: (dd/mm/yyyy): Caller Information Contacted by: (Name & Division / Agency): Phone #'s: Time of Call: (24hr) Incident Information Type/Scale of Incident: (e.g. power failure, fire) Address(es) of incident or major intersections Postal Code (for CCAC inquiry) Size/Type of Building (Residential single/townhouse/multi-unit; Toronto Community Housing) Estimated number of potential evacuees Time incident occurred (24 hr) How long before OEM notified? Incident Details Who is 'on-scene' e.g. 1 st responders, City Divisions, Hydro? Who has been notified? Is Incident Command established? Location/address of Incident Command Estimated duration of response Yes No Is OEM requested to attend site? Yes No Other Information (Type / Duration of EHS response):

23 23