1 / 31

Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

This presentation explores how service aggregations in emergency management can be achieved through the use of registry-repositories in a SOA ecosystem. It discusses the OASIS open standards, CAP and EDXL specifications, and the role of the SOA Registry-Repository in the emergency management ecosystem. The Integrated Response Services Consortium (IRSC) and its evolution are also highlighted.

vaughns
Download Presentation

Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Service Aggregations in Emergency Management:Registry-Repositories in a SOA Ecosystem 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  3. Integrated Response Services 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 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  5. IRSC Evolution • Fast Forward to October 2007 • 4th SOA for E-Gov Conference Kick-Starts IRSC 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 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 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 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 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 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 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 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 • MOA*: DHS*+EIC*+OASIS EM TC • Practitioner Steering Group > EM TC • EDXL-HAVE: Hospital Availability Exchange (Finished 2nd Public Review) • EDXL-RM: Resource Messaging (Finished 2nd Public Review) • More Specifications in Process Pipeline *MOA=Memorandum of Agreement; DHS= Dept. of Homeland Security; EIC=Emergency Interoperability Consortium; OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  14. 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 Family • Level of Abstraction Above Concrete Specs • Will Codify EDXL Family Solutions to Common Problems • Jurisdiction-Specific Terminologies/Taxonomies • Contact & Jurisdiction Information • Location & Scheduling Information OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  15. 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

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

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

  18. 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

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

  20. Modeling & Simulation Testing Scenario • Tracking Message Flow in GGSN* “Common Operating Picture” Service *GGSN=Golden Gate Safety Network 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  22. 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  23. Modeling & Simulation Testing Scenario • Using Common Operating Picture to Automate Messaging in EDXL-RM Web App 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 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 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

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

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

  29. 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 OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  30. Credits • Development and Hosting of IRSC SOA Registry-Repository Servers including Development of Web Services Interfaces: • Danny Thornton, SOA IT Consultant, Scalable Architectures, LLC. • 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, Starbourne Communications Design OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

  31. IRSC Members Partial Listing • Broadstrokes, Inc. - http://www.broadstrokesinc.com – Contact: Adam Hocek ahocek@broadstrokesinc.com tel: (646) 862-1842 • CIM Engineering, Inc – http://cim3.com – Contact: Peter Yim peter.yim@cim3.com • Golden Gate Safety Network – http://maplab.org/aar/ Includes: San Francisco Communications & Map Lab Project – Contact David Coggeshall ibcomm@aol.com • IntegrityOne Partners - http://www.ionep.com – Contact: David. R.R. Webber david.webber@ionep.com • Michelle Raymond, Knowledge Services http://ontolog.cim3.net/cgi-bin/wiki.pl?MichelleRaymond • MyStateUSA, INC. - http://mystateusa.com1458 S. Eagle Flight Way, Boise, Idaho 83709 – Contact: Claudia Bitner, President/CEO claudia@mystateusa.com Office: 208.377.1960 - Fax: 208.322.5965 – Cell: 208.724.5353 – Contact: Tom Ferrentino - tferrentino@mystateusa.com Tom Ferrentino tel: (716) 913-4453 • NuParadigm Companies – http://nuparadign.com 12977 North Forty Drive Suite 200, Saint Louis, MO 63141 – Contact: Harry R. Haury, CEO 636-537-5558 x226 office 314-799-8844 cell • OSS Nokalva, Inc. - http://www.oss.com One Executive Drive Suite 450, Somerset, NJ 08873 USA – Contact: Alessandro Triglia, Staff Member Phone: 732-302-9669 Fax: 732-302-0023 • Sandia National Laboratories – http://sandia.gov – Contact: David Ellis dellis@sandia.gov • Scalable Architectures LLC - http://www.ScalableArchitectures.com Milpitas, CA – Contact: Danny Thornton, SOA IT Consultant 408-857-0421 • Starbourne Communications Design – http://starbourne.com 1361-A Addison Street, Berkeley, CA 94702-1716 – Contact: Rex Brooks, President/CEO rexb@starbourne.com 510-898-0670 • Tall Tree Labs, SemTalk USA http://talltrees.com – Contact: Dr. Robert Smith, PhD bob@1talltrees.com • Warning Systems, Inc. - http://warningsystems.com/ – Contact: Elysa Jones, CTO, COO ejones@warningsystems.com OASIS Symposium 2008: Service Aggregations in Emergency Management: Registry-Repositories in a SOA Ecosystem

More Related