2 october 2007 improving rapid emergency first response with soa 4 th soa for e-government...
TRANSCRIPT
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
1
Improving Rapid Emergency Response Systems
with Integrated Web Service Architecture:
Semantic Interoperability, Service Orientation & Event Driven
Architectures
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
2
Conclusions & Challenges
EGov REQUIRES Open Standards OMB Mandates Adoption of Voluntary Consensus Standards Standards MUST Meet Use-Case-based Requirements
SOA for EGov MUST be Practical Standards for Intra-Agency/Dept., Inter-Agency/Dept. &
Inter-Jurisdiction Needed Standards SHOULD Provide Conformance Criteria & Testing
if Possible Results SHOULD be Measurable Regular Pulse Checks & Satisfaction Surveys Needed
SOA for EGov SHOULD Develop Culture of Continuous Improvement—Steady, Consistent, Dependable
Event-Driven Architecture Necessary for Emergency Response Systems MUST be Designed with Specific Message Exchange Patterns
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
3
Collaboratory Begins with “SWANS” Conference – 7-8 April 2005
Handful of Companies Loosely Organized by SOAP-Based Web Services.
Verizon Backbone from Municipal to State to Federal Jurisdictions Supports Network.
Alert and Warning Systems Connected to E911 Telephone Geocode System to VoiceXML Automated Notification Application
OASIS Common Alerting Protocol (CAP) 1.0 Introduced.
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
4
Collaboratory Pilot Expanded at SICoP Public Meeting at the DoN CIO XML Business
Standards Council 20 October 2005
SOA Introduced
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
5
Collaboratory Pilot Expanded at SICoP Public Meeting at the DoN CIO XML
Business Standards Council
Companies Added
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
6
Collaboratory Grows, Evolves at 4th Semantic Interop for E-Gov Conference
9-10 February 2006 Demonstration Refined
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
7
Collaboratory Grows, Evolves at 4th Semantic Interop for E-Gov Conference
Practical Use of Ontology Highlighted
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
8
Collaboratory Pilot Continues to Evolve at 1st SOA for E-Government Conference
23 May 2006 SOA Registry-Repository Added
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
9
Collaboratory Pilot Continues to Evolve at 1st SOA for E-Government Conference
SOA Registry-Repository Explained
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
10
What are ‘Open’ Standards &Why are ‘Open” Standards Important?
OPEN Means Openly Developed Public Visibility From Inception
Open Charter-Writing Process Goals, Objectives, Audience & Principles Explicit
Open Decision-Making Processes All Documents, Minutes, Discussions, Email Lists Available Votes Recorded and Posted
OPEN Means Public Review & Comment Public Review Invites Testing through Implementation All Public Comments MUST be Addressed/Answered
OPEN Means Public Can Criticize, Stimulate Revisions
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
11
Importance of Open StandardsOverview of OASIS Emergency Management
Technical Committee
OASIS Common Alerting Protocol (CAP) 1.0 Approved March 2004
OASIS CAP 1.1 Approved October 2005 Lessons Learned:
Important to Provide Guidance for Implementation
Important to Develop Feedback Process for Next Versions
OASIS Emergency Data Exchange Language Evolves from CAP Experience
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
12
Importance of Open StandardsOverview of OASIS Emergency Management
Technical Committee
OASIS Emergency Data Exchange Language Distribution Element (EDXL-DE) 1.0 Approved May 2006
EDXL-Hospital Availability Exchange (EDXL-HAVE) moving to 2nd 60-Day Public Review October 2007
EDXL-Resource Messaging (EDXL-RM) Moving to 2nd 60-Day Public Review November-December 2007
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
13
Importance of Open StandardsOverview of OASIS Emergency Management
Technical Committee OASIS Emergency Data Exchange Language FAMILY
Follows Pattern of ebXML, Web Services Security Specifications, and Others EDXL Not Clearly Understood at Start Standards Writing is also an Evolving Set of Practices Need to Document Lessons Learned
EDXL Reference Information Model (EDXL-RIM) will include Lessons Learned and Formalize the Methods and Techniques Developed for EDXL-DE, EDXL-HAVE and EDXL-RM for Next EDXL Specifications
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
14
IPAWS Infrastructure from 3rd SOA for E-Government Conference
David Ellis’ Presentation: Trans-enterprise Service Grid
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
15
IPAWS Infrastructure from 3rd SOA for E-Government Conference
David Ellis’ Presentation: Trans-enterprise Service Grid
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
16
IPAWS Infrastructure from 3rd SOA for E-Government Conference
David Ellis’ Presentation: EDXL-DE is Key for ROUTING
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
17
Lessons in Building Standards from EDXL Family Evolution
Alerting and Warning Lessons from CAP
In Absence of other Needed Standards, Practitioners WILL Attempt to USE Existing Standard for Needed Functions
Be Clear About WHAT a Standard CAN or IS INTENDED to do
Routing and Secure Network Considerations Lessons from EDXL-DE
Develop Requirements Systematically with Practitioners & Subject Matter Experts
Carefully Select Use-Cases for Defining Requirements
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
18
Lessons in Building Standards from EDXL Family Evolution
Reporting Lessons from EDXL-HAVE
Resist Persuasive Arguments that ANY Candidate Specification is Ready for Approval as Standard
Start with Requirements from Use-Cases that can be Traced through Specification
Messaging (Event-Driven Message Exchange Patterns) Lessons from EDXL-RM
Formalize Requirements in Separate Document (Started with a Candidate Specification, then Extracted Requirements)
Specifications are Concrete Expressions of Abstract Principles
2 October 2007
Improving Rapid Emergency First Response with SOA4th SOA for E-Government Conference
19
Conclusions & Challenges
EGov REQUIRES Open Standards OMB Mandates Adoption of Voluntary Consensus Standards Standards MUST Meet Use-Case-based Requirements
SOA for EGov MUST be Practical Standards for Intra-Agency/Dept., Inter-Agency/Dept. &
Inter-Jurisdiction Needed Standards SHOULD Provide Conformance Criteria & Testing
if Possible Results SHOULD be Measurable Regular Pulse Checks & Satisfaction Surveys Needed
SOA for EGov SHOULD Develop Culture of Continuous Improvement—Steady, Consistent, Dependable
Event-Driven Architecture Necessary for Emergency Response Systems MUST be Designed with Specific Message Exchange Patterns