Semantic Service Oriented Architecture

1. LCDR Sam Chance 443-694-5293 sgchance@gmail.com Semantic Service Oriented Architecture The SSOA Program A Semantically Powered Architecture to Enable Inter-Agency Capabilities Sharing February 9-10, 2006 Mike Seebold 443-910-5876 seeboldm@ctc.com

2. SSOA Problem Domain Analysts Lack Awareness of Available Capabilities (Services) • Sheer Volumes of Services Compounds the Problem • Word of Mouth Awareness Typical • Available [XML] Web Services Solution Powerful, but… • Lacks Ability to Easily Discover Services • Location Dependent; “Stale” references possible • Weak, or no, Semantics • When Found, Services Typically not Readily Interoperable, Brittle • Machine Interpretable Standards Immature, not Implemented • Resulting Processes are Human-Centric, Ad-hoc and Intermittently Repeated • Analysts Spend Too Much Time on IT Related Tasks • Policy Compliance Unmanageable • Creative Approaches to Get Job Done May Inadvertently Violate Policy • Results in Fragmented, Sub-Optimal Analysis • Long Standing Problem – Analysts aren’t Able to Focus on Analysis

3. SSOA Provides Significant Value SSOA Will Augment XML Web Services by Supporting a SOA that is: • Based on an Extended Jini™ Based Infrastructure from Valaran that • Enables Spontaneous Networking & Services Interchange – Location Independent • Provides Automated, State-based Recovery from Failures – Self-Healing • Supports Dynamic Scaling and Service Provisioning – Enterprise Solution • Designed and Implemented Based on Current and Emerging Standards • Enabling Seamless Interoperability Across Services – Preventing Custom Interfaces • Separating Interface from Implementation – Abstraction From IT • Exploiting Emerging Semantic Computing Technologies • Allows Intelligent Agents to Dynamically Substitute Services – Adaptive • Learns Analyst Preferences & Captures Best Practice By Unobtrusive Observation – Predictive • Pushes Relevant Services to End Users when New Services Come Online – Awareness • Supports Dynamic, Adaptive Workflow Composition & Execution – Automation • Demonstrating Ability to Share Resources Across Disparate Organizations • Enhances Current SOA Projects by Acting as Risk Reduction Task – Strategic

4. Status to Date – Great Deal of Interest • SSOA-1 Development • CTC is Prime Contractor • Acquire & Integrate COTS Components: • Valaran Corporation, Agent Logic & Ontology Works • 12 Month Project In Process • Initial Demo Ahead of Schedule (6 Months), Final Deliverable at 12 months • SSOA-2 Development • CTC is Prime Contractor and Integrator • Extending Existing SSOA Platform: • Valaran Corporation, Agent Logic, Ontology Works, SandPiper Software, Siderean, University of North Carolina • 12 Month Project In Process • Beginning Process for Two New SSOA Projects • Additional Agencies • More Advanced Cognitive Agent Functions • Security & Deployment Issues

5. SSOA Major System Components • Semantic Service Bus (SSB) • Provides Infrastructure for Distributed Services Operations • Ensures Reliability and Availability of all Services • Defines and Enforces Standard Interfaces and Layer of Abstraction • Semantic Service Registry (SSR) • Provides Machine Interpretable Service Descriptions (Semantics) • Enables Event Processing Agents to Discover New and Relevant Services • Semantic Process Registry (SPR) • Provides Repository for Workflows • Supports Best Practice Sharing for SSOA Users • Semantic Metadata Registry (SMDR) • Provides Ontology Repository • For all Knowledge Objects (e.g. Service Descriptions, Meta-Data Elements, Key-Word List, etc) • Facilitates Ontology Sharing, Merging and Alignment • Event Detection and Response (EDR) Service • Event Monitoring and Alerting Functions • Business Process Description and Event Processing Agent Execution • “Nervous System” of SSOA

6. Semantic & AgentComponents SPR EDR Services SSR SMDR Intelligent Event Processing Agents SSOA System View Business Services Dynamically Exchanged (Sharing/Awareness)

7. Register Services Discover Services Publish, Find, then Bind Invoke Services SSOA Technical Foundations • Service Oriented Architecture (SOA) • Semantics Based Computing • Standards Based Design (SBD) • ISO 11179 Metadata Registries Standard • ISO 19763 Meta-Model Framework Standard • ISO 24707 Common Logic Standard • OMG Ontology Definition Meta-Model Standard • W3C Semantic Web Services Framework

8. EDR: Event Detection and Response • Provides Event Detection for Operators • Monitors Sources/Sensors for State Changes • Communicates Alerts to Humans and/or other Agents • Executes Automated Business Processes • Exposed as Service on SSB • Reduce Network Traffic From Agent Logic

9. SSR SSB & SSR Components From Valaran, Inc.

10. SMDR Based on XMDR Project • Multi-Agency, Collaborative Project • Extend Semantics Management Capabilities of ISO/IEC 11179 • Cross-Domain, Various Structures • Test & Demo Extended Capabilities of Reference Implementation (RI) • Produce Design for Operational 11179 Registries • Adapt & Adopt Emerging (Semantic) Technologies • Propose Revisions to 11179 Parts 2 & 3 (Ver. 3) • Help Resolve Registration & Interrelation Issues for Complex Metadata Standards www.xmdr.org

11. Event Detection & Response Process Execution XMPR XMDR

12. C C C C M M M M K K K K Notional SSOA Operations <xmdr> Proxy Proxy Proxy <ssr> Proxy Proxy Proxy

15. ARCHANGEL

16. Technical Discussions Questions?

17. Backup Charts

18. SSOA 1 Use Case: Combat Search & Rescue • Relevant Use Case to Many Key Decision Makers • Is Only One of Many Potential Use Cases to Showcase SSOA • Demonstrating SSOA’s Service Discovery Abilities • Enabling Multi-Site Collaboration Between Multiple Actors in Process • Providing Real-Time Access to all Relevant Services in an Effort to Significantly Reduce Overall Processing Time From Receipt of Request to Launch Order • Leveraging Event Detection and Response Service Focused on: • Multi-Source Information & Service Aggregation • Intelligent User Notification and Alerting • 3rd Party Workflow Execution • SSOA 2 Use Case • Currently Planned to Focus on Entity Extraction Use Case