Emergencies Don’t Wait

transcript

1 May 2008 5th SOA for E-Government Conference: BPM Choreography in OASIS SOA Reference Architecture

BPM Choreography in OASIS SOA Reference Architecture:

SOA Registry-Repository forEmergency Management & Health Informatics Domains

Using OASIS Emergency Management Specifications, OASIS Content Assembly Mechanism and Intel MashMaker

Emergencies Don’t Wait

SOA Automation Can Save Lives Automate Anything not Requiring Human Decision

Choosing the Right Combination of Options Varies by Locality, Region, State

Open Standards Necessary, but… Standards & Technology are Moving Targets Must Watch Versioning Carefully

Commitment to Continuous Improvement Needed

Integrated Response ServicesConsortium (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

IRSC Evolves

Pilot Group Continues through Cycles of Emerging Technologies, Standards Development

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 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 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;

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

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

OASIS Content Assembly Mechanism (CAM) & Integration Technologies Aid Implementation

OASISCAM

Templates

OntologyClassification

Discovery

DomainVocabulary

CCTSNDR

W3C XSD

Schema

- WHAT?

Provides lexicon of information content

Describes structure constructs

Arranges groups of information

Simple content typing

Software tooling interfaces

- HOW? WHY?

Provides actual use patterns (templates)

Supports context handling and rules

Rendering outputs and documentation for verification

Enables integration testing / certification

Versioning

- WHO?

- Alignment of meaning and terms

- Consistent domain definitions

Modelling methods and practice

Business information content building blocks

- WHERE?

Shared resources of semantic definitions

Code lists

Dynamic rendering

Distributed versioning control

Role and access security management

- WHEN?

Alerts

Process control

Workflow

Automated interfacing

Business Intelligence

MachineBased

Reasoning

Shared

SemanticsebXML

- WHERE?

Domain classification systems

Ontology and reasoning definitions

Associations and linkages

Search and drilldown

Modelling tools

CAM Eclipse Environment

1 Content (EDXL)

2 Rules (CAM + XSLT)

3 Report (HTML)

CAM Deployment Options

B2B Web services

jCAMenginejCAM

engine

Templates

MessageSystemXMLJava

APIReceive

Process

Validate Server

TemplatesRequest

htmlResponseJavaAPIProcess

StructureRulesContext

Standalone

Eclipse

Template

XMLhtml

Rendered Report

EDXL EDXL

Rendered Report

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

SOA-RR Provides Service Visibility as defined by the OASIS SOA Reference Model and Reference Architecture Awareness: Provide Centralized (Mediated) Search & Access

of Service Descriptions for Specific Domains Willingness: Service Descriptions Contain Information that

Allows a Consumer to Determine the Applicability of a Provider’s Service

Reachability: Service Descriptions Provide Information to Establish Automated or Other Types of Communication with the Service

IRSC SOA-RR Provides Framework for Ecosystem Advertising SOA Services: Service Descriptions

(Based on On-Going Work on the OASIS Reference Architecture for Service Oriented Architecture.)

SOA-RR Provides Underlying Support for Ontologies Sun Service Registry Supports OASIS ebXML Registry-

Repository Standard Can be Loaded with

Classification Schemes Relationships

Can Include Links to Ontologies, Ontology Evaluations, Open Ontology Repository Initiative*

Can Provide for Ontology Reasoners, Inference Engines*Open Ontology Repository Initiative is Theme of National Institute of Standards and

Technology (NIST) Ontology Summit at Interoperability Week 2008

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

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

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

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

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

From Real World Event Triggerto Automated Process/Workflow

Translating Scenarios into Simulations to

Test & Refine IRSC SOA-RR Approach

Real World Trigger: Severe Thunderstorms Using Intel MashMaker*: Letting the Web do the Work

Mobile County, Alabama

* http://mashmaker.intel.com

Real World Trigger: Severe Thunderstorms Using Intel MashMaker: Letting the Web do the Work

Mobile County, Alabama

Real World Trigger: Severe Thunderstorms Using Intel MashMaker: MashMaker Interface

Real World Trigger: Severe Thunderstorms MyStateUSA: Local-State-National Network Hub; IRSC Member

Real World Trigger: Severe Thunderstorms MyStateUSA: Administration Page

Real World Trigger: Severe Thunderstorms Making the Mashup: Putting NOAA-NWS & MyStateUSA Together

Real World Trigger: Severe Thunderstorms Working the Mashup: Building the Alert: Adjusting the Views

Real World Trigger: Severe Thunderstorms Working the Mashup: Building the Alert: Getting MyState Map Tool

Real World Trigger: Severe Thunderstorms Working the Mashup: Building the Alert: Using the Map Tool

Note: Map Tool opens in a new window.

Business Process Model (BPM) for Alert Simplified SOA-Based Process & Message Flows Using CAP Aggregating & Coordinating Multiple Services by Prearrangement Facilitated by SOA-RR

Principles of Collaboration, Cross-Organizational Boundary Information & Experience Sharing

SOA-RR Provides Framework for SOA Ecosystem Provides Visibility & Pertinent Information

Agreements Needed Across Boundaries SOA-RR Provides Means to Achieve Shared

Governance Goal: Successful Consumption of Services

Emergencies Don’t Wait

SOA Automation Can Save Lives Automate Anything not Requiring Human Decision

Choosing the Right Combination of Options Varies by Locality, Region, State

Open Standards Necessary, but… Standards & Technology are Moving Targets Must Watch Versioning Carefully

Commitment to Continuous Improvement Needed

Credits Development and Hosting of IRSC SOA Registry-Repository Servers

including Development of Web Services Interfaces: Danny Thornton, SOA IT Consultant, Scalable Architectures, LLC.

Assistance Integrating Intel MashMaker in SOA-RR Robert Ennals, Intel Corporation http://mashmaker.intel.com

Coordination with MyStateUSA Network Services: Claudia Bitner, President-CEO MyStateUSA INC Tom Ferrentino, MyStateUSA INC.

Provision of SemTalk BPM Tool Dr. Robert Smith, PhD, President-CEO SemTalkUSA

Presentation Preparation and Delivery and EDXL-RM Application Sample Interface: Rex Brooks, President-CEO, Starbourne Communications Design

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

Emergencies Don’t Wait

Documents