EMSI Framework & Semantic Interoperability Demonstration “ Outlining a Framework and Roadmap for System Interop

1. EMSI Framework & Semantic Interoperability Demonstration“Outlining a Framework and Roadmap for System Interoperability” – EMSI 2010 - 2014 April 2010 Presented by: Mike Abramson President, Advanced Systems Management Group Co-chair OMG C4I Domain Task Force

2. Semantic Interoperability Demonstration • Challenges in developing interoperable information systems • Components of interoperability • Shared Operational Picture Exchange Services (SOPES) • Information Exchange Framework (IEF) • Semantic Specifications (SOPES, MIP, NIEM, EDXL, ….) • Interoperability Demonstration based of SOPES and IEF Objective • Policy Driven Information Sharing • MDA process for developing: • Executable Information sharing rules • Executable information protection rules • Communities of Interest • Demonstration Model Examples

3. Challenges • Increasing complexity of the information environment • Reduction in the perceived quality of Information: • Accuracy: semantics to accurately convey the perceived situation. • Relevance: information tailored to specific requirements of the mission, role, task or situation at hand. • Timeliness: information flow required to support key processes, including decision making. • Usability: information presented in a common, easily understood format. • Completeness: information that provides all necessary (or available) information needed to make decisions. • Brevity: information tailored to the level-of-detail required to make decisions and reduces data overload. • Trustworthiness: information quality and content can be trusted by stakeholders, decision makers and users. • Protected: Information is protected from inadvertent or Malicious Release or use. • Greater need to support decision makers with quality information • Increased Operational Tempo • Highly dynamic and fluid events and operational environments • Inability of any communities to articulate a definitive set of information sharing requirements

4. Information versus information Protection • Information Security • Safe-guard information at-rest and in-transit • Focus on network and boundary security techniques and technologies • Information Protection (enforcement of IM Security Rules) • Safe-guard information (/data) during the aggregation and marshalling of information • Determination of sensitivity of aggregate information • Semantic and data validation • Tag and Label Processing • Sensitivity filtering • Release-ability of semantic instances vs. subscriber accreditations • Etc ...

5. Information Interoperability (circa 2003) Multiple Peer-to-Peer Gateways Organization ≈ Capability ≈ System ≈ Service

6. Interoperability Approach Objectives • Based on OPEN Standards • Supported by Architecture Driven Strategies (UPDM, MDA) • Separation of Business Rules from Software Applications/Services • Platform Independent Solution Specifications

7. Applying Model Driven Architecture(SOPES Conceptual Architecture (2004)) SOPES IEDM Open Standard Worldwind open Source Enterprise Architect V7.1 ($200-300) COIL Prototype Log4J open Source JC3IEDM (International Spec.) Serialized Objects COIL Prototype PrismTech DDS Open Source Open Standard COIL Prototype Window Native

8. Demonstration Objectives Outline a strategy that would deliver: • A Flexible, Agile and Sustainable Capability for Multi-Agency Shared Operating Picture and Situational Awareness • Alignment of existing capability C2 Information Sharing Capability • Standardized Business Rules (SOPES IEDM) • Standardized Messaging (NIEM:SAR, CAP-CP, SOPES XML, MIP PDU) • Standard Situational Awareness DB (JC3IEDM) • Standardized Distribution Mechanisms (DDS, SOA, Web Service, ...) • Other (presentation, processing, ...) • Architecture / Model Driven Information Sharing and Protection • DODAF, UPDM • Info Sharing /Info Protection modeling and transformation • Emergency Response / Public Security Scenario and models • Existing Scenario (e.g., Harbour Siren, MSOC, …) – To be selected • Based on Propose EISE demonstration

9. Assumptions and Constraints • The majority of described elements can be put together using existing or evolving open standards and integration software elements (Glueware) • Where current Glueware could be developed into a standards in implemented as COTS (IEF information Exchange Service demonstrated through ASMG’s Common Object Interoperability Layer) • Described elements align with previously stated C4I direction; • Described elements can be prototyped and demonstrated within six (6) to twelve (12) months; • Where feasible a prototype could be developed using high levels of standards based open-source or shareware products • Demonstrate the use and effectiveness of the SOPES IEDM Specification

10. Demo Scenario • Fire on a Navy Ship / Collaborative Response • Demonstrate Selective Information replication across 4 government agencies • Demonstration the ability to modify distribution patterns during Operations (using architecture generated information) to support changing operational context • Demonstrate support for multiple data formats simultaneously PDU (primary Distribution, CAP (main Body), SOPES XML)

11. 14 Communities of Interest(Based on Information Sharing Requirements) Demonstration has 4 Operational Nodes participating in multiple Separate Information Sharing Agreements (ISAs) ISAs link operational nodes into communities Operational Nodes can participate in multiple agreements representing virtual networks (Operations Needs, Privacy or Security Levels) ISAs change based on operational context NDHQ Maritime Operating Centre Modified During Demo RCMP OP Centre RCMP OP Centre

12. Specifying Information Exchanges

13. Alternate Approach

14. Defining a Contract

15. Setting up a Contract

16. Setting up a Dynamic Filter

17. Semantic: Organization_SA (SOPES Exemplar)

18. Semantic: Unit_SA

19. Semantic: CR_Unit_GIS

20. Setting up a Dynamic Filter

21. Setting up a Dynamic Filter

22. Core Concepts • Reusable Information Patterns • Simple Extensible Notations • Transformable into Executable Rules • Targeting Open Standards

23. 26 Questions and Answers Semantic Interoperability Demonstration April 2010 Mike Abramson, ASMG Ltd. 265 Carling Ave, Suite 630, Ottawa, Ontario, K1S2E1 Fax: 613-231-2556 Phone: 613-567-7097 x222 Email: abramson@asmg-ltd.com