Integrated Response Services Consortium Integrated Emergency Response NetCentric

Integrated Response Services Consortium Integrated Emergency Response Net-Centric Pattern v 1. 0 A Service Oriented Architecture Reference Architecture March 2009 Integrated Response Services Consortium 1

Fundamental Pattern: OASIS Reference Model for SOA u http: //www. oasis-open. org/specs/index. php#soa-rm March 2009 Integrated Response Services Consortium 2

Description: Integrate Services for Optimal Emergency Response (ER) u Subdomains: n n u End to End Emergency Lifecycle: n n u Emergency Management Healthcare Planning & Preparation Response & Mitigation Demobilization & After Action Analysis Changes to Planning & Preparation Goal: Continuous Improvement March 2009 Integrated Response Services Consortium 3

Problem Statement u u u SOA for ER Has Shown Major Flaws: Katrina, Indonesian Tsunami, etc. Planning for Last Disaster & Managing Emergencies w/One. Time Emergency Measures Unacceptable SOA for ER SHOULD Develop Culture of Continuous Improvement—ER REQUIRES Open Standards n n u SOA for ER MUST be Practical n n u Global Mandate for Voluntary Consensus Standards Needed Standards MUST Meet Use-Case-based Requirements Standards MUST be REQUIRED from International to Local Level Standards SHOULD Provide Conformance Criteria & Testing Results SHOULD be Measurable Regular Pulse Checks & Satisfaction Surveys Needed Event-Driven Architecture Necessary for Emergency Response Systems n MUST be Designed with Specific Message Exchange Patterns March 2009 Integrated Response Services Consortium 4

Participants u u u Standards Developing Organizations (SDOs) such as OASIS Emergency Management Technical Committee Members & Member Companies Governmental Agencies, such as Dept of Homeland Security, Local County Public Safety Agencies Non-Governmental Organizations (NGOs), such as Emergency Interoperability Consortium Private Companies such as Warning Systems, Inc. , My. State. USA Social Networking Organizations Local Neighborhood Associations March 2009 Integrated Response Services Consortium 5

Pre-Conditions u Registration in SOA-Registry-Repositories such as Your. Global. Grid Providing Visibility for Service Producers and Consumers n Service Registrations MUST include: 6 Service Descriptions with Appropriate Details, such as Service Endpoint Addresses and WSDLs 6 Service level Agreements, Contracts and Policies that Govern Service Use 6 Appropriate Information to Ensure Successful Use of Service March 2009 Integrated Response Services Consortium 6

Structure: Principal Concepts u Figure 3 from OASIS SOA Reference Model: March 2009 Integrated Response Services Consortium 7

Structure: SOA u Slide shows Development of SOA over time (Companion document contains detailed explanations with diagrams of the Reference Architecture) March 2009 Integrated Response Services Consortium 8

Behavior u Slide shows Behavior of Systems in Pattern (Companion document contains detailed explanations with diagrams of the Reference Architecture) March 2009 Integrated Response Services Consortium 9

Post-Conditions u Metrics from System Components can be Scored in the Exercise Control System from the National Institute of Standards and Technology (NIST) (Modeling and Simulations Group) March 2009 Integrated Response Services Consortium 10

Example Project: Show Need for New Open Standard for Display of Building Floorplans for ER in Medical Facility March 2009 Integrated Response Services Consortium 11

Open Floorplan Display Project u Details to Come March 2009 Integrated Response Services Consortium 12

Implementation Guidance, Verification and Conformance, Appendices and Supporting Information u Included in Companion Document: n Integrated Emergency Response Net-Centric Pattern v 1. 0 March 2009 Integrated Response Services Consortium 13