1. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 1 Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

2. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 2 Summary  OASIS Open Standards Enable Service Aggregations ebXML Registry Repository Specifications SOA Reference Architecture CAP & EDXL Specifications  SOA Registry-Repository (SOA-RR) Provides Structure for Emergency Management Ecosystem Local-Regional-State-National-International  Cross Boundary SOA Requires Commitment to Continuous Improvement Information Sharing Practices Evolving

3. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 3 Integrated Response Service Consortium (IRSC) Evolves  Pilot Group Begins with “SWANS” Conference – April 2005 (Semantic Web Applications for National Security)  Handful of Emergency Mgt-Related Companies Loosely Organized by Web Services Showcase: OASIS Common Alerting Protocol v1.0 Network Backbone Service Connects Municipal to State to Federal Jurisdictions  Evolving to Reflect Emergency Mgt SOA Ecosystem Govt Agencies, Standards, Vendors, Public IT + Physical infrastructure

4. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 4 IRSC Evolution  Pilot Group Continues through Cycles of Emerging Technologies, Standards Development

5. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 5 IRSC Evolution  Fast Forward to October 2007  4 th SOA for E-Gov Conference Kick-Starts IRSC

6. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 6 OASIS SOA Evolution Context  Spring 2008 OASIS Reference Architecture for Service Oriented Architecture v1.0 Public Review  October 2006 OASIS Reference Model for Service Oriented Architecture v1.0 Approved  May 2005 OASIS ebXML Registry Services (RS) & Registry Information Model (RIM) v3.0 April 2002 ebXML RS & RIM v1.0  August 2003 Web Services for Remote Portlets v1.0 (WSRP) – First OASIS Web Service Standard  Range of Web Service Standards Security, Framework, Messaging, Policy, etc

7. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 7 IRSC SOA-RR Provides Framework for Ecosystem  SOA-RR uses Sun Service Registry based on OASIS ebXML RS/RIM & freebXML Registry 3.0  IRSC SOA-RR “Federated” by Domains Emergency Management Health Informatics  Each Registry-Repository to Contain Main Components of SOA Ecosystem: Services, Service Providers, Standards, Standards Development Organizations Guidance, Best Practices, Cookbooks Transaction Histories

8. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 8 IRSC SOA-RR Provides Framework for Ecosystem  Sun Service Registry & freebXML Registry 3.0 Large & Complex

9. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 9 IRSC SOA-RR Provides Framework for Ecosystem  Steep Learning Curve Discourages Uptake

10. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 10 IRSC SOA-RR Provides Framework for Ecosystem  WebForm-based Application Interface Improves Usability

11. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 11 IRSC SOA-RR Provides Framework for Ecosystem  WebForm-based Application Interface Improves Usability

12. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 12 OASIS Emergency Mgt Standards Process  What’s Important: Open: Public Record Visible/Transparent Public Reviews Must Address All Comments Must have Testable Conformance Requirements Must have Working Implementations Commitment to Regular Improvements through Versioning at Appropriate Intervals

13. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 13 OASIS Emergency Mgt Standards Process  Current Standards CAP v1.1, Collecting Feedback for Next Version Emergency Data Exchange Language-Distribution Element (EDXL- DE) v 1.0: Message Routing – Adoption Outreach & Education  EDXL Growing into Overall Umbrella Unifying EM TC Standards Process MOU*: DHS*+EIC*+OASIS EM TC Practitioner Steering Group > EM TC EDXL-HAVE: Hospital Availability Exchange (Finished 2 nd Public Review) EDXL-RM: Resource Messaging (Finished 2 nd Public Review) More Specifications in Process Pipeline *MOU=Memorandum of Understanding; DHS= Dept. of Homeland Security; EIC=Emergency Interoperability Consortium;

14. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 14 EDXL Family Evolution: Discover Problems  CAP Reveals Systemic Problem 1 st Message Standard Leads to Unintended Usage Vendors, Agencies Use What They Have for What They Need  EDXL-DE Addresses Emergency Message Routing Slow Adoption Outreach: Slow Uptake Improvements Underway  EDXL-HAVE & EDXL-RM Reveal More Systemic Problems Need Better Requirements Process Need Unifying Foundation

15. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 15 EDXL Family Evolution: Solve Problems  EM TC, EDXL Stds Address Entire Emergency Lifecycle Routing, Message Exchange Patterns (MEP) Preparedness, Response, Remediation, Demobilization  EDXL-RIM: Reference Information Model Unifies EDXL Level of Abstraction Above Concrete Specs Will Codify EDXL Family Solutions to Common Problems Jurisdiction-Specific Terminologies/Taxonomies Contact & Jurisdiction Information Location & Scheduling Information

16. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 16 IRSC Fits EDXL into SOA Ecosystem  Framework for Service Aggregation at Need  Implements OASIS SOA Reference Architecture  SOA-RR Planned to Implement OASIS EDXL-RIM Level of Abstraction Below Purely Abstract Reference Model fits SOA Reference Architecture Will be Semantic Web-Ready  SOA-RR Planned for Wider IT Ecosystem Open Ontology Repository Network Will Make More Domains Available

17. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 17 IRSC Fits EDXL into SOA Ecosystem  IRSC SOA-RR Implement EM TC Stds + Web Service Stds- EDXL-RM Web Service

18. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 18 IRSC Fits EDXL into SOA Ecosystem  IRSC SOA-RRs Implement EM TC Stds + Web Service Stds-EDXL-HAVE Web Service

19. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 19 Purpose: Improve Emergency Response  Correctly Automate Everything that doesn’t Require Human Decision-Making  Provide Continuous Improvement for Decision Support & Response Services that Require Human Decision-Making  Modeling, Simulation & Testing Required

20. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 20 Modeling & Simulation Testing Scenario  Based on 2006 “Golden Guardian” Exercise: SF Earthquake-Inject 125 of 495

21. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 21 Modeling & Simulation Testing Scenario  Tracking Message Flow in GGSN* “Common Operating Picture” Service *GGSN=Golden Gate Safety Network

22. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 22 Modeling & Simulation Testing Scenario  Tracking Message Flow in GGSN* “Common Operating Picture” Service

23. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 23 Modeling & Simulation Testing Scenario  Full Message Exchange Pattern: EDXL-RM RequestResource Message (HAZMAT) EDXL-RM ResponseToRequestResource EDXL-RM RequisitionResource EDXL-RM CommitResource EDXL-RM RequestReturn EDXL-RM ReleaseResource  Current Practice: Radio with Manually Keyboarded Tracking System Multiple Disparate IT Systems Across Jurisdictions No Common Messaging Stds, Naming Conventions, etc

24. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 24 Modeling & Simulation Testing Scenario  Using Common Operating Picture to Automate Messaging in EDXL-RM Web App

25. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 25 Modeling & Simulation Testing Scenario  Using Common Operating Picture to Automate Messaging in EDXL-RM Web App

26. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 26 Modeling & Simulation Testing Scenario  Using Common Operating Picture to Automate Messaging in EDXL-RM Web App

27. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 27 Modeling & Simulation Testing Scenario  Using Common Operating Picture to Automate Messaging in EDXL-RM Web App

28. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 28 Adding Value with Aggregated Services  IRSC Member Broadstrokes Provides Automated Reverse 911 Telephone Notification

29. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 29 Adding Value with Aggregated Services  Public Preparedness Portal Can Provide Multiple Views of Situation. Available IRSC Services

30. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 30 Summary  OASIS Open Standards Enable Service Aggregations ebXML Registry Repository Specifications SOA Reference Architecture CAP & EDXL Specifications  SOA Registry-Repository (SOA-RR) Provides Structure for Emergency Management Ecosystem Local-Regional-State-National-International  Cross Boundary SOA Requires Commitment to Continuous Improvement Information Sharing Practices Evolving

31. 30 April 2008 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem 31 Credits  Development and Hosting of IRSC SOA Registry- Repository Servers including Development of Web Services Interfaces: Danny Thornton, President-CEO, Scalable Architectures, Inc.  Development of Geospatial Map-Based “Common Operating Picture” including Coordination with EDXL-RM Application: David Coggeshall, President-CEO San Francisco Communications  Reverse 911 Web Service: Adam Hocek, President-CEO Broadstrokes, Inc.  Presentation Preparation and Delivery and EDXL-RM Application Sample Interface: Rex Brooks, President-CEO, Stabourne Communications Design