Roadmap Alignment Information Exchange Framework (IEF)

1. Roadmap AlignmentInformation Exchange Framework (IEF) September 2012 Presented by: Mike Abramson President, Advanced Systems Management Group Co-chair OMG C4I Domain Task Force Chair Information Exchange Framework (IEF)

2. Information Exchange Framework (IEF) • A little History (IEF is and evolution not a revolution) • IEF Objectives • Alignment with ISE Roadmap • Challenges

3. The Starting Point (Multi-National Data Sharing effort 1992-2000) Larger Group of National and International Partners Accomplishment: Demonstration of Common Data Model and Exchange Mechanisms Other Government Departments (OGDs) Private Volunteer Organizations (PVOs) Complex Information and Service Domains Non-Government Organizations (NGOs) Other Allies Reach back to National Domain Challenges: Stage complex information holdings into the coalition, while enforcing information security policy and SOPs Establish the ability to support multiple communities of interest with different information needs Non-NATO Coalition Army Tactical Command and Control System (ATCCIS) Other Levels of Government

4. Evolution of a Concept • Allied nation seeking to develop data interoperability • Data replication around a common data model • Data Exchange Mechanism (DEM) and Message Exchange Mechanism (MEM) • US, UK, Germany, Spain, Canada, …. • Generic Hub 1, 2 & 3; LC2IEDM; C2IEDM • International Testing • Absorbed by the Multilateral Interoperability Programme (MIP) in 2001 • Ongoing Program with 25+ participating members • Data Exchange Mechanism (DEM: Binary Data Exchange) • JC3IEDM , MIP Information Model (MIM) • MIP Exchange XSD • STANDAG 5525 • Shared Operational Picture Exchange Services (SOPES: C4I DTF) • Policy Driven Information Sharing • 3 Core Elements • SOPES Information Exchange Data Model (IEDM) V1.0 (2010) • SOPES Information Exchange Mechanism (IEM) • SOPES Policy Management Service (PMS)

5. C4I Life-cycle Concept (originally present in 2004/05)

6. OMG Gets Involved • US Delegation to MIP sponsored the development of the Shared Operational Picture Exchange Services (SOPES) Information Exchange Data Model (IEDM) • Goal: The use of the JC3IEDM as a commercial Standard by OGDs and NGOs • Reusable data patterns for developing JC3IEDM information sharing • Support for filtering and redaction • SOPES moves to MARS PTF (2006) • During the socialization of SOPES it was identified that many domains have the same challenges and requirements (Not only a C4I Problem: see past presentations) • IEM and PMS form the basis for the Information Exchange Framework (IEF) • Elements • Information Exchange Policy Vocabulary (IEPV) - Revised submission Aug 2012 • Limited to Information Packaging Requirements Specification • Information Exchange Policy Enforcement Service(s); • Renamed Information Exchange Policy-based Packaging Service(s) to reflect the correct scope of the Service(s) • Current RFP • Several additional services on the IEF roadmap

7. SOPES IEDM Specification Statistics • 16 Situation Awareness Domains • 192 Defined Data Patterns • 271 Wrappers and Corresponding JC3IEDM Entities • SOPES IEDM supports selective information sharing from and common information store • SOPES IEDM provides data patterns that support tear-lines, redaction and transformation • SOPES IEDM provides greater flexibility and agility Transactional Packages • Action (46) • Capability (6) • Context (13) • ControlFeature (6) • Facility (22) • GeographicFeature (5) • Holding (2) • Location (22) • Materiel (9) • MeteorologicalFeature (2) • ObjectItem (11) • ObjectType (7) • Organisation (19) • Person (7) • Plans & Orders (12) • Report (2) Modeling approach documented in Annex A of the specification JC3IEDM/SOPES Offers a rich set of Operational planning and Situational Awareness (SA) semantics

8. Information Exchange Framework Exchange Mechanisms and Services Policy Management Information Models IEF Objectives (words have changed with the times the intent has not) • Information Sharing and Safeguarding (ISS) Services based on open standards and architectures • Standards based process, using architecture (modelled), to translate Information sharing and safeguarding policy into executable and machine enforceable rules • Separation of policies (business rules and instructions) from Software Applications/Services to promote flexibility, agility and extensibility • Platform Independent Solution Specifications • Flexible and agile lifecycle for ISS agreements • Capture and maintenance of institutional knowledge and the ability to share the knowledge with mission partners • Mechanisms (Services) for enforcing the Policy Specifications • Policy Management • Policy Development (Architecture Models) • Policy Administration in operations • Domain Specific Information Models • Data or Domain Model • Policy Model

9. IEPV Objectives (RFP #1) • Formal Vocabulary for specifying the rules for aggregating instance data to meet the semantic requirements of an information exchange agreement. • Integrate data aggregation and information protection at the generation point for the data. • Based on reusable data patterns • Architecture Models • Specify the rules for: • Aggregation of instance data from multiple sources • Filter/Redact data to meet agreement requirements • Transform Data from source to agreed domains • Tagging Data Aggregates • Format data to community specifications and standards • Direct Support for MDA • Simple Extensible Notations • Capture and maintenance of institutional knowledge and the ability to share the knowledge with mission partners

10. IEPPS Objectives (RFP #2) • A specification for a mechanism/service with the capacity to enforces the policies define by IEPV version 1 • Define APIs for • Information Store • Policy Management • User Applications • Logging Functions/Services • Security Functions/Services • Operational Use Cases • Support for: • Request – Response • Publish – Subscribe • Event Driven (multicast, broadcast, peer-to-peer)

11. MARS IEF Early Concepts • Three Primary RFPs • Policy Vocabulary • Policy Enforcement • Policy Management • Serve multiple domain • C4I • Finance • Health • Other • Domain Specific Information • Information Model • Information Semantics • Information Policy Instances aligned to the to the domain model and semantics

12. IE Policy-based Packaging Services

13. IEF Key Concepts • Reusable Information Patterns Describing the rules for: • Information Sharing Contract • Message • Semantic • Data Transactional Patterns • Data Aggregation and Marshalling • Data Transformation • Domain Filters (Static and Dynamic (alterable at Runtime) • Semantic Guards (protected Semantic Patterns) • Simple Extensible Notations • Transformable into Executable Rules (MDA Process) • UML Profile for IEPV • Direct Alignment to Architecture Frameworks • Open Standards / Open Architecture / Open Source

14. IEPV/IEPPS Objectives • Focus on information content and Rules rather than mechanisms for discovery and distribution • Align information sharing and safeguarding to architecture • Separate business rules from the software services that enforce them, providing: • increased flexibility, adaptability and agility • Increased the retention of institutional knowledge and Memory • Increase traceability and audit-ability of information sharing and protection solutions • Provide Information Sharing and Safeguarding Policy Enforcement Support for multiple communities (NIEM, Hl7, EDXL, XBRL, CAP, MIP, …) • Enable Model Driven Architecture (MDA) services for Information Sharing and Safeguarding • Enable the use of reusable data and information patterns

15. IEPV Products • Content and Packaging Policy Vocabulary Models • Data Patterns for the aggregation of information content • Patterns for aggregation/collation of message content • Message • Digest • Information packages • Information payloads • Attachments • UML Profile for Modelling Packaging Policies • Domain Model for the storage of the Policy Models • OWL Representation

16. And the IEF continues to evolve Not identified as an IEF Element but needed for IEF to Work Original IEF Elements IEF additions as of December 2011 IEF policy areas

17. Latest List of Policy Enforcement Services • Current IEF Focus • Policy-based Packaging Services (IEPPS) • Focussed on packaging data  Information  Messages in a manner that is: • Context Sensitive • Transformed for Use • Redacted for Release • IEPV Elements (current IEPV Focus) • Vocabulary Model (Visual Ontology Model (VOM)) • UML Profile for IEPV (PSM) • Domain Model for IEPV Policy • OWL Representation (PSM) • Future IEF or related standards efforts • Policy-based Authorization Services (IEPAS) • Policy-based Information Release Services (IEIRS) ------------------------------------- • Policy-based Security Services (IEPSS) • Policy Based Credentialing Services (IEPCS) • Policy-based Identity Services (IEPIS) • Policy-based Distribution Services (IEPDS) • UML Profile for DDS / DDS (definitely a target) • But there are others • Proposes future PSMs: • XACML • SAML • Ponder • Other • Each will Require: • Policy Vocabulary • UML Profile Linked to AF • Language PSMs • Enforcement Service Specification

18. Policy/Rule Life-cycle (Policy-based Packaging) Post Mission Analysis Source Requirement Legislation/International Agreement Government Policy Regulation Agency Policy Operating Procedures Service Level Agreements Architecture 2 Architecture Driven Transformation AF Domain Model 1 Change Recommendations Testing, Validation and Certification Architecture Framework (AF) DODAF/UPDM/IEPV Policy Management Governance Policy Enforcement Point Policy Decision/Enforcement Point 1 2

19. Positioning the IEPPS Enforce IEPPS Policies Exchange Semantics, Syntax, Structure, Vocabulary Metadata and Message Publishing Enforce Access and Distribution Policies Enforce IEPPS Policies LEXS CAP, EDXL, MIM, NIEM, HL7 Information System Information System IEF - IEPPS IEF - IEPPS Shared Middleware or Registry/Repository Infrastructure Security Services Identity, Credentials and Access Services IEPV Decision and Enforcement Point Policy Management Services

20. MDA for IEF Architecture and Engineering Domain Operational Domain

21. IEF (IEPV / IEPPS) Alignment to ISE Capabilities IEPV / IEPPS enables the specification and enforcement of aggregation and dissemination rules for the publishing of discovery data. Discovery Identity IEPV / IEPPS enables the specification and enforcement of aggregate and dissemination rules for identity information tailored to the needs of the individual services. Security \ Encryption IEPV Policies can include instructions directing datasets to be encryptedduring construction or as a final step before release. The policies can identify type of encryption to be performed. However the IEPPS will require an interface to the encryption services. Federation IEPPS service specification is expected to enable federated / distributed operation; each IEPPS can instantiate a specialized set of policies that will enable the storage, transformation, forwarding, … of received information. Audit IEPPS specifies the requirement for logging during the aggregation and publishing processed at various levels to support auditing. The MDA process evolving out of the IEPV can provide full traceability from operation (rules and instructions) back through architecture to originating policy. Aggregation IEPV specifies the rules for aggregating (including filtering, redaction and transformation) of data to support information sharing agreements; Policy decisions and enforcement are performed by the IEPPS or equivalent reasoning or reasoning service. Messaging IEPV specifies the aggregation, structuring and formatting policies to support messaging services; IEPPS or equivalent service deliver formatted messages to the messaging or dissemination services. Mediation The data patterns defined in IEPV can be used to breakdown and message to its base components and then reassembled using a separate pattern to translate it domain and structure for a separate format. The same process can be used to redact information when crossing domains. IEPPS can be interfaced for various forms of data store. The policies in the IEPPS can be used to transform received messages from semantic in transit to the semantics of the information system store. Storage Collaboration Only as data sharing applies. IEPV provides a modeling approach (UML Profile) that can enable MDA transformation to convert model elements into machine enforceable rules and instructions. The approach provide full traceability between policy and strategy and operational rules and instructions. Policy IEPV vocabulary provides for the marking of data and data composites during the aggregation process. The vocabulary also be used to develop metadata for section headers, message headers and discovery information. Data/Metadata IEPV provides the vocabulary to support the modeling of transformations in the aggregation and de-aggregation (marshaling) processes. Structural transformation is performed by moving data elements from one pattern to another defined in the policies instantiated in and instance of the IEPPS. Transformation The IEPPS will have and interface to directory services. Directory Others… Others…

22. Looking down the Road OBJECTS COTS Tools Policies Service Models Shared Architecture SOPES Profile UPDM 2.0 UPDM 3.0 / UAF SOPES v1.0 UML For NIEM IEPV DODAF Conformant Model JC3IEDM V3.1c SOPES 2.0 MIM IEPD MIM Packaging Policy Model MIM Policy Model This strategy would also test NIEM, ISE, IEF, UPDM standards in the evolution of a complex domain and a large international community – Multilateral Interoperability Program (MIP). IEPPS IEPPS MIP Information Model MIP MDA MIM Data Model

23. Take-away • IEF has a strong alignment with ISE capability objectives • IEF is focused on aligning standards and community specifications to deliver capability • IEF seeks to exploit architecture (modeling) in order to: • Expedite the development, testing and deployment of IE Policy & Capability • Adapt to changing IE needs • Retain institutional memory • The goal should be not only be the development of new standards but also the alignment of existing capability • Need opportunities to test, demonstrate and pilot IEF concepts and standards

24. 24 Questions and Answers Information Exchange Framework Roadmap March 2011 Mike Abramson, President Advanced Systems Management Group (ASMG) Ltd. Co-Chair C4I DTF Co-Chair Emergency Management SIG Chair IEF WG 265 Carling Ave, Suite 630, Ottawa, Ontario, K1S2E1 Fax: 613-231-2556 Phone: 613-567-7097 x222 Email: abramson@asmg-ltd.com

25. A little History OMG C4I DTF RFI Summer/Fall 2001

26. IEPV Alignment to UPDM 2.0 <UPDM2element> OperationalExchange <UPDM2element> Exchange {DODAF Alias = “ActivityResourceOverlap”} <SOPES 1.0> Contract {OperationalExchangeKind = InformationExchange} <SOPES 1.0> Semantic <SOPES 1.0> WrapperAttribute 1..* conveys * <UPDM2element> OperationalExchangeItem {framework – “MODAF 1.2”} references identfies 0..* 1 <SOPES 1.0> Transactional <SOPES 1.0> WrapperAttribute 1..* 0..* references 1 0..* <UPDM2element> InformationElement {DODAF Alias = “Information”} <SOPES 1.0> WrapperAttribute <SOPES 1.0> Wrapper 1..* <UPDM2element> InformationElement {DODAF Alias = “Information” <UPDM2element> InformationElement {DODAF Alias = “Information” representedBy 1..* * * relatedTo

27. SOPES/IEF Revised December 2011