1 of 23

1
Environmental Emergency Management System (E2MS)
GERCIAN February 24, 2005 Meeting
2
Agenda

• Welcome E2MS Mission
• E2MS Purpose
• E2MS Project Team
• Project Status Overview
• E2MS Functional View
• Ops Maintenance View
• Next Steps

3
EC and Environmental Emergencies

• Requirement
• One common set of tools for all EC Regions
  REETs (Regional Environmental Emergency Teams).
• A system of record for all REETs.
• Consolidation of resources to focus on a system
  with a National view.
• Leverage data and services of participant
  organizations through CGDI OGC alignment.
• The Result
• An Operational E2MS (Environmental Emergency
  Management System)

4
E2MS PurposeOverview

• The Quality Value
• Availability
• Reliability
• Accessibility
• Trustability
• Affordability
• Capability

• Case Management
• Information Interchange
• Part of system of record

Data Layers / Interfaces - Base Data - Model
Data - Imagery - Incidents - Thematic Data

• Security
• Hierarchical administration
• User groups and profiles
• ECONET
• Public Internet

Before During After Timeline
5
E2MS PurposeIngest Serve Data

• Environment Canada
• NEMISIS
• NPRI
• CEPA E2
• CWS (SARA)
• Weather
• Shoreline Sensitivity
• Incident Database

• Other Government Organizations
• Natural Resources Canada
• Agriculture Canada, Canadian Food Inspection
  Agency
• Canadian Hydrographic Service
• Department of Fisheries and Oceans
• Health Canada
• DND
• PSEPC

• QA/QC Process
• Maintain Data Integrity

6
E2MS High Level Services Model
7
E2MS Solution Collaboration Engine
Catalog NRCan Map Marine Charts Etc,
HC Map Server
DFO Map Server
EC E2MS Server
EC Server
EMO Map Server
Feature Server
8
E2MS Project Team
E2MS Steering Committee EEP Regional Managers
9
Project WBS ScheduleltStatusgt
Phase 1
-Requirements Specification - Architecture
Analysis
Phase 2
- Functional specifications
Phase 3
- Development - Deployment
Phase 4

• Knowledge Transfer
• Acceptance

Updated Timeline
Dec
Jan05
Feb
Mar
Apr
May
Jun
July
Aug 05
10
Common Operating Picture (COP)
11
Web Site
12
Home Page
13
Map Viewer Page
14
Portfolio Form
15
Security Module

• The E2MS security model is composed of 4
  sub-systems
• System Access
• Functionality
• Portfolio
• Data

16
Portfolio and Data

• Portfolio
• General Access (available to all named users)
• Incident
• Exercise
• Training
• P2R2 (Prevention, Preparedness, Response,
  Recovery)
• Data
• Portfolio
• Security Level (Users / Organizations)

17
Security Sub-systems
18
System Architecture
19
Operations Maintenance

• Users
• Environmental Emergencies Program and
  Collaborators
• System of record for REET
• Support lead agency
• Support on scene responders and commanders
• Leverage other EC capabilities, example modeling.
• Data
• Strong data management
• Data dissemination process
• Data security
• Reliable availability 7X24
• Focus on management of Environmental Emergencies
• Prevention, Preparedness, Response and Recovery

20
Next Steps Post Release 1

• Data Management
• Release 2 August 05
• Operational Maintenance Model
• From Project to Program
• EE Community of Practice Meeting

21
Any Questions
22
E2MS Project Authority

• For further information
• Mary-Ann Spicer-Robinson
• Manager, Response
• Environmental Emergencies Branch
• Environment Canada
• Phone [phone]
• Mary-Ann.Spicer_at_ec.gc.ca