30 april 2008 oasis symposium 2008: service aggregations in emergency management:...

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

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

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


4

IRSC Evolution Pilot Group Continues through Cycles of

Emerging Technologies, Standards Development


5

IRSC Evolution Fast Forward to October 2007 4th SOA for E-Gov Conference Kick-Starts IRSC


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

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

IRSC SOA-RR Provides Framework for Ecosystem Sun Service Registry & freebXML Registry 3.0 Large & Complex


9

IRSC SOA-RR Provides Framework for Ecosystem Steep Learning Curve Discourages Uptake


10

IRSC SOA-RR Provides Framework for Ecosystem WebForm-based Application Interface Improves Usability


11

IRSC SOA-RR Provides Framework for Ecosystem WebForm-based Application Interface Improves Usability


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

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;


14

EDXL Family Evolution: Discover Problems

CAP Reveals Systemic Problem 1st 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

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/TaxonomiesContact & Jurisdiction InformationLocation & Scheduling Information


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

IRSC Fits EDXL into SOA Ecosystem IRSC SOA-RR Implement EM TC Stds + Web Service Stds- EDXL-RM Web Service


18

IRSC Fits EDXL into SOA Ecosystem IRSC SOA-RRs Implement EM TC Stds + Web Service Stds-EDXL-HAVE Web Service


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

Modeling & Simulation Testing Scenario Based on 2006 “Golden Guardian” Exercise: SF Earthquake-Inject 125 of 495


21

Modeling & Simulation Testing Scenario Tracking Message Flow in GGSN* “Common Operating Picture” Service

*GGSN=Golden Gate Safety Network


22

Modeling & Simulation Testing Scenario Tracking Message Flow in GGSN* “Common Operating Picture” Service


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

Modeling & Simulation Testing Scenario Using Common Operating Picture to Automate Messaging in EDXL-RM Web App


25



26



27



28

Adding Value with Aggregated Services IRSC Member Broadstrokes Provides Automated Reverse 911 Telephone Notification


29

Adding Value with Aggregated Services Public Preparedness Portal Can Provide Multiple Views of Situation. Available IRSC Services


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

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

http://www.scalablearchitectures.com/

http://maplab.org/aar/

http://broadstrokesinc.com/

http://broadstrokesinc.com/

http://starbourne.com/


32

IRSC Members Partial Listing

Broadstrokes, Inc. - http://www.broadstrokesinc.com – Contact: Adam Hocek [email protected] tel: (646) 862-1842

CIM Engineering, Inc – http://cim3.com – Contact: Peter Yim [email protected]

Golden Gate Safety Network – http://maplab.org/aar/ Includes: San Francisco Communications & Map Lab Project – Contact David Coggeshall [email protected]

IntegrityOne Partners - http://www.ionep.com – Contact: David. R.R. Webber [email protected]

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 [email protected] Office: 208.377.1960 - Fax: 208.322.5965 – Cell: 208.724.5353 –Contact: Tom Ferrentino - [email protected] 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 [email protected]

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 [email protected] 510-898-0670

Tall Tree Labs, SemTalk USA http://talltrees.com – Contact: Dr. Robert Smith, PhD [email protected]

Warning Systems, Inc. - http://warningsystems.com/ – Contact: Elysa Jones, CTO, COO [email protected]

mailto:[email protected]



http://ontolog.cim3.net/cgi-bin/wiki.pl?MichelleRaymond

http://mystateusa.com/


30 april 2008 oasis symposium 2008: service aggregations in emergency management:...

Documents

soa ecosystem slide

ecosystem soarr

oasis symposium

th soa

irsc soarr

service providers

oasis reference architecture

oasis reference model