To improve situational awareness, Federal, Provincial Territorial and Municipal emergency management agencies and the private sector are collaborating on the MASAS initiative. This initiative is currently facilitated by GeoConnections, a national program led by Natural Resources Canada. MASAS is a systems of systems, based on standards enabling participating emergency management agencies to publish and access emergency event information. It Enables emergency management personnel to view emergency information in a geospatial context. MASAS is focused on connecting systems to enable information exchange between emergency management agencies. An approach towards a National All Hazards Situational Awareness Spatial Capability
BCeMAP is a Multi- Agency Situational Awareness tool that provides a framework for geospatial intelligence, data fusion and visualization. In conjunction with Emergency Management British Columbia, GeoBC and multiple stakeholders it is used to gain a timely accurate understanding of emergency management operations and the events that impact them. The BC Emergency Event Map system (BCeMap) is intended to: Provide real-time dissemination of a province-wide emergency event map to trusted partners in British Columbia, including local, regional, provincial and national emergency management organisations, other public safety agencies and critical infrastructure operators. Provide a Common Operating Picture that integrates incident, geographic, infrastructure, threat and hazard information to provide common situational awareness to multiple agencies while planning for and responding to emergency events of all types. Provide the ability to access and disseminate geospatial incident information to other trusted federal and provincial partners. This may include dissemination of information to other geospatially enabled systems
Through the direct integration of Emergency Management Data, Municipal Data, Critical Infrastructure, Threat and hazard Data and Response data we can now start to answer a number of questions in the management of consequences spatially. The spatial representation gives emergency managers context around the events that occur. By giving information around the status of the event: Where is the storm, where is the fire, where is the epicenter, where is the inundation zone, what area is damaged. Whats affected? Who is at risk? Whats the closest muster zone, these are all questions that we can obtain answers for by utilizing BCeMAP, but you may ask yourself well how is this done By using open standards and existing technology.
Interagency Collaboration driven by 2010 Olympics Cost Sharing Model e.g. data collection in particular air photos GeoBC provided service to multiple level of government by collecting and making data accessible. Required partnerships amongst various agencies representing the private sector and governments at all levels. All data in centralised area and accessible through a common viewer that essentially provides a common operational picture thus situational awareness This is the first time that data was collected in Lower Mainland with full participation from multiple agencies Good model for future especially when all agencies (govt and private) are working with reduced budget
When fusing threat or hazard information with response data emergency management operations get detailed context about events that impact them. This allows emergency management professional to manage these consequences to potentially improve planning, response and mitigation of these events. It provides a Common Operational Picture for Enhanced Situational Awareness that facilitates Strategic Planning while improving Operational Support and Consequence Management
Due to the evolution of standards-based interoperability architectures, geographic information technology and the web we have been able to pull and create information in way that can be Published, Aggregated and consumed by users to gain a an improved understanding of what is occurring around us. This is Situational Awareness!!
GeoBC utilised shared services model to provide GIS services including hosting of the app and publishing data from EMBC We have an ELA with ESRI Canada The BCeMap is based on new technologies (e.g. ArcGIS server and Flex viewer) that have not been implemented within the provincial government. a need to develop standards for development and hosting of BCeMap application. Tight time lines for 2010 Olympics (showcase) GeoBC relaxed the standards to accommodate the tight timelines to allow the delivery of the application as a demonstration system Relax the existing database modelling standards The acceptance of two .NET components contrary to our existing Java Development Standards The tiers in the above diagram mean the following: Source Tier – Internal or external data sources or services providing content to BCeMap Web Services: Components (mappings, configurations, custom code, etc.) to be developed specifically for BCeMap also contain Existing software libraries (APIs), components or tools Application Tier : Existing corporate services to be integrated with Existing software libraries (APIs), components or tools (mappings, configurations, custom code, etc.) to be developed specifically for BCeMap Client Tier– standard technology COTS platforms supported by GeoBC integrated Existing corporate services BCeMap is based on a multi-tier service architecture. At the client tier, all access to the BCeMap application – including static and dynamic content, map viewing, access to data feeds, etc. – will be from a standard web browser such as Internet Explorer or Mozilla Firefox. Map Server(ArcGIS Server) – provides all the services necessary to support the mapping functions of BCeMap such as panning, zooming, layer control, tile caching to optimize performance, spatial overlay, etc. Feed Aggregator – reads data from a variety of external source feeds in different formats, integrates them into a common representation, and exposes them in standard formats for consumption by the BCeMap application. The source tier represents the range of types of data feeds and sources to be accessed and consumed by the BCeMap application. There are two types of data: Base Data: This data will be provided primarily as a tiled cache and/or WMS/WFS (All standard WMS/WFS features/functions must be supported (ie.GetFeatureInfo)) External Feeds: These sources are external to GeoBC (e.g. BC Hydro, Ministry of Transportation and Infrastructure, etc.), and are in variety of formats – some standard, others custom. Standard formats such as WMS and GeoRSS will pose little or no problem for integration with BCeMap. Custom formats and the CAP (Common Alerting Protocol) and the WSDL formats will require effort to integrate into the Feed Aggregator. Data stored in the Feed Aggregator will be published using Open Protocols, including WMS, WFS or JSON.
Enhancement of Emergency Management Information System (EMIS) being implemented by Emergency Management BC Timely and real time sharing of event location and description Sharing of information between Public Safety Agencies & CI Owners Support local, provincial and federal Emergency Operation Centers by providing Situational Awareness Share incident information with other jurisdictions e.g. Alberta, New Brunswick Rapidly configured and interoperable Simple deployment using custom tools that are interoperable between systems using a ArcGIS Server 9.3.1 framework Highly accessible with associated security protocols performance without caching Readily accessible datasets for analysis, and report usage Used for tactical planning Daily use for ADM/Deputy Ministerial briefings
BCeMap Common Operating Picture
British Columbia Emergency Map Viewer BCeMAP Gurdeep Singh Portfolio Manager, Emergency Management and Public Safety Integrated Land Management Bureau, GeoBC Kristopher Hayne Business Area Expert Emergency Management BC, Emergency Coordination, Telecommunications and Specialty Systems April 15, 2010
<ul><li>Project Background </li></ul><ul><li>What is BCeMAP? </li></ul><ul><li>Management of Consequences </li></ul><ul><li>GeoBC Enterprise Data Collection and Access </li></ul><ul><li>Integrating Dynamic Data </li></ul><ul><li>Integrating Existing Technology </li></ul><ul><li>Demo </li></ul><ul><li>Benefits </li></ul><ul><li>Acknowledgements </li></ul><ul><li>Stakeholders </li></ul>
Project Background <ul><li>MASAS: Systems of Systems </li></ul><ul><li>Within MASAS, each agency: </li></ul><ul><li>Controls what they share </li></ul><ul><li>Decides on relevant content that </li></ul><ul><li>is shared </li></ul><ul><li>Uses their existing systems to </li></ul><ul><li>Publish and consume </li></ul>BCeMAP… Multi – Agency Situational Awareness System (MASAS)
What is BCeMAP? <ul><li>BCeMAP is Intended to Provide: </li></ul><ul><ul><li>Real time dissemination </li></ul></ul><ul><ul><li>Common Operating Picture </li></ul></ul><ul><ul><li>Access and dissemination </li></ul></ul><ul><ul><li>Role Based </li></ul></ul>Consequence Management … Multi – Agency Situational Awareness Tool
Management of Consequences By asking the following... Enterprise Data Collection ... <ul><ul><li>What happened? </li></ul></ul><ul><ul><li>When did it happen? </li></ul></ul><ul><ul><li>Where did it happen? </li></ul></ul><ul><ul><li>What was the cause? </li></ul></ul><ul><ul><li>What population is affected? </li></ul></ul><ul><ul><li>How many dead? </li></ul></ul><ul><ul><li>How many injured? </li></ul></ul><ul><ul><li>How many missing? </li></ul></ul><ul><ul><li>What is the extent of damage? </li></ul></ul>Base Data Threat or Hazard data Data Atlas A002 B070 A002 B070 EMIS (Response & Recovery) Management of Consequences Situational Awareness Common layer of location - based information that provides reference and context Location - based infrastructure information of key sectors e.g. Energy/utilities, transportation, Government facilities Transportation, Flood Zones, muster zones, disaster response routes Involves the fusion of threat and hazard information weather hazards Involves the fusion of threat and hazard information, e.g. Env Canada, DriveBC, CI, Wildfire Viewing and dissemination of real - time and near real - time incident information. e.g. resource locations, near real - time satellite imagery Viewing and dissemination of real - time and near real - time incident information. e.g. ETeam, Earthquakes, CAD, MASAS.
Enterprise Data Collection and Access Emergency Response Data Providers Security Data Providers Tactical Support Project Funding Data Provider Data Providers Data Providers and facilitate agreements Data Providers Data Providers Project Funding Specific Projects
Integrating Dynamic Data (Feeds) Threat and Response Data... <ul><ul><li>Environment Can Weather Alerts </li></ul></ul><ul><ul><li>DriveBC </li></ul></ul><ul><ul><li>NRCan Earthquakes </li></ul></ul><ul><ul><li>EMIS - Eteam </li></ul></ul><ul><ul><li>National MASAS </li></ul></ul><ul><ul><li>MoF Wildfire Management Branch </li></ul></ul>How? Through Open Standards ...
Integrating Dynamic Data Through Open Standards… <ul><ul><li>GeoRSS </li></ul></ul><ul><ul><li>Extensible Markup Language </li></ul></ul>Canadian Profile of the Common Alerting Protocol (CAP-CP) <ul><ul><li>Canadian EM Symbology </li></ul></ul>Utilizing Existing Technology…
Utilizing New Technology Through GeoBC… Demo… Authentication and Browser (Security) Application Server (BCeMAP) Feed Aggregator (FME) ArcGIS Server Data (Feeds, LRDW) Data (WMS, GeoRSS)
Benefits <ul><li>Single Authoritative Source of Data for Emergency Response </li></ul><ul><li>Enhancement of Emergency Management Information Service (EMIS) </li></ul><ul><li>Common Operational Picture </li></ul><ul><li>Interagency Collaboration and Communication </li></ul><ul><li>Leverage the Work to Develop and Integrate Common Standards </li></ul><ul><li>Geospatial Information Legacy of 2010 Games </li></ul>
Stakeholders BC Hydro Capital Regional District Fraser Valley Regional District City of Vancouver E-Comm Department of National Defense NC4 Ministry of Transportation Environment Canada New Brunswick EMO GeoConnections Ministry of Health Services Ministry of Forests