1

Mark TaylorManager SLIP Emergency Management ProgramFESAApril 2007

EEmergency mergency MManagementanagement

Status April 2007Status April 2007

2

Agency Incident Management System

i.e. WebEOC

Establishing an Emergency Management Spatial Capability for WA

“Same Information at the Same Time”

Public Notificationi.e. APECS

Agency Incident Management System

i.e. WebEOC

Agency GISSLIP Enabling Framework

Agency Computer Aided Dispatch

SLIP-EM Mapping

3

Achievements

• Governance under SEMC

• Detailed user requirements • Data requirements,

• Data capture and sharing protocols

• Common operating picture(s)

• Pilot system trialed for 3 of (23) State Hazards• Bushfire (FESA, DEC and Local Government)

• HAZMAT (FESA)

• Land Search and Rescue (WA Police)

• CT and CIP coordinated national development

• Emergency Services Directory

4

Achievements

• Governance under SEMC

• Detailed user requirements • Data requirements,

• Data capture and sharing protocols

• Common operating picture(s)

• Pilot system trialed for 3 of (23) State Hazards• Bushfire (FESA, DEC and Local Government)

• HAZMAT (FESA)

• Land Search and Rescue (WA Police)

• CT and CIP coordinated national development

• Emergency Services Directory

5

Achievements

• Governance under SEMC

• Detailed user requirements • Data requirements,

• Data capture and sharing protocols

• Common operating picture(s)

• Pilot system trialed for 3 of (23) State Hazards• Bushfire (FESA, DEC and Local Government)

• HAZMAT (FESA)

• Land Search and Rescue (WA Police)

• CT and CIP coordinated national development

• Emergency Services Directory

6

Common Operating Picture

a) Consistent Symbology

7

Common Operating Picture

a) Consistent Symbology

b) Customised views/products for specific hazards & roles

8

Data (via SLIP)

a) Consistent terminology

b) Authoritative Source

c) Consistent Currency

d) Fit for purpose / best available

9

Integration/Seamless interoperability

a) Modelling software (plume, fire spread, weather forecast, etc)

b) ICS (Incident Management System, Public Alert Communication)

10

Integration/Seamless interoperability

a) Modelling software (plume, fire spread, weather forecast, etc)

b) ICS (Incident Management System, Public Alert Communication)

c) Spatially linking operational documentation

BEST-Care Site Plan

11

Common Toolsets

a) Consistency

b) Simplicity

12

Processes

Near-real time incident data sharing (aerial surveillance, field surveys, agency based GIS services, etc)

13

ProcessesNear-real time incident data sharing (aerial surveillance, field surveys, agency based GIS services, etc)

Alignment with AIMS (authorisation, authentication, auditing)

14

Operational staff, management media, support agencies, stakeholders can view the information via a standard web browser using the role based login viewing information that is pertinent, customised and authorised for release

15

Success Reliant on Availability of InformationBase MappingBase MappingImagery, Street Directory, ESD’sContours

Operational MappingOperational MappingHospital, Hydrants, Community and Welfare Centres, Airfields, EM Offices

InfrastructureInfrastructurePower, Gas, Water

Hazardous RisksHazardous RisksSpecial Risk and Dangerous Good SitesRisk Mitigation Plans

Environmental RisksEnvironmental RisksFlora, Fauna, Water Catchments, Contaminated Sites

Social RisksSocial RisksSchools, Day and Aged Care, Sporting, Retail and Cultural Centres

“Benefit from Real Time Sharing of Information”Incident DataIncident Data

Fire Shapes, Chemical/Smoke Plumes, Road Blocks, Containment Zones

Environmental DataEnvironmental DataWeather Forecasts, Lightning Strikes, River Monitoring

16

Current Status• Funding Submission unsuccessful (incl. ESD)

• Existing funds to maintain service 2007/08 • Existing three scenarios with limited deployment

• Develop 3rd ESD over South Coast

• Expectation for Operational Use• Need to ensure long term reliability and extension

• Requires formal training programs and exercise regime

• Support and resourcing to build into operations

• Issues• Staff secondments (WALIS, DoIR and DOW)

• Long term sustainability of ESD

17

Current Status1. Operational strength for SLIP-EM services

2. Operational Deployment of SLIP-EM – Field operations– Coordination (response and recovery)– Briefing/Debriefing (operations and exercises)– Cross agency coordinated sharing (operational protocol)

3. Establishment of Formal Training Programs and Testing

4. Data Improvement programs (i.e. ESD)

5. Establishment of SLIP Data Access Agreements and Data

Improvements

– SLIP-EM

– Agencies systems (CAD/GIS/IMS)

6. Linkage to Agency Incident Management Systems

7. Remote Data Access (offline and partial online)