1 / 23

OMG/SOPES – Information Interoperability Strategy

OMG/SOPES – Information Interoperability Strategy. February 2010 Presented by: Mike Abramson President, Advanced Systems Management Group Co-chair OMG C4I Domain Task Force. ASMG. Founded 1995

bena
Download Presentation

OMG/SOPES – Information Interoperability Strategy

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. OMG/SOPES – Information Interoperability Strategy February 2010 Presented by: Mike Abramson President, Advanced Systems Management Group Co-chair OMG C4I Domain Task Force

  2. ASMG • Founded 1995 • Common User Core lead for DND (1996-1999) • ATCCIS and MIP lead for DND (1998-2001) • BOWMAN/CIP – Contracted to specify and demonstrate a sustainable IM and Interoperability Strategy (2001-2004) • OMG - Co-chair C4I DTF Lead: SOPES/IEF • FELEX - Lead - Information Architecture (2005-2008) • MSOC - Lead - System Architecture (2008-Present) • EISE – Lead - Information Architecture , Aggregation and Protection (2007-2009) • EMSIF - Lead – Framework Development 2009-2010

  3. Interoperability (ATCCIS/MIP) Private Volunteer Organizations (PVOs) Other Government Departments (OGDs) Staging information from one operational Domain to another in a secure and trusted Manner was considered and National Issue Non-Government Organizations (NGOs) Non-MIPNations Reach back to National Domain Non-MIPCoIs JC3IEDM Data Exchange Mechanism Message Exchange Mechanism Other Levels of Government

  4. ATCCIS Challenges (circa 1998) • Challenges • All Data Contract (no mechanism to selectively replicate data) • No information and security protocols • Small changes had major impact • DND/ASMG successfully test Block 2 Prototype March 1998/99 • Defined a Security Architecture for MIP 2000 • ASMG embarks on the development of a model (rule/metadata) driven solution • Demonstrated at MIP 2001 • Demonstrated for GD UK July 2002 (BOWMAN/CIP)

  5. SOPES History • 9/11 Triggered discussions within the C4I DTF • June 2002 - SOPES RFI • C2IEDM Offered and an Option by NC3A • June 2004 - SOPES RFPs • Information Exchange Data Model • Information Exchange Mechanism • Information Exchange Policy Management • June 2006 – IEF takes over elements of SOPES • Information Exchange Mechanism • Information Exchange Policy Management • January 2007 – US DOD CIO/NII sponsors JC3IEDM as SOPES IEDM • Expected Finalization of SOPES IEDM: June 2010

  6. ASMG at OMG • Joined 2002 in response to the SOPES RFI • Co-Chair C4I Domain Task Force (2004) • Champion: SOPES • Participant: UPDM Information Exchange Framework Data Tagging and labelling Information Assurance • Co-Chair Emergency, Crisis and Major Event Management (ECMEM) Special Interest Group

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

  8. The Operational Challenge • Rigid and brittle information systems; lacking information quality; and security • Growing requirement for dynamic and adaptive information systems • Adapt to the changing context of the operational environment with embedded security • Adapt to changing coalitions, interagency coalitions and Communities of Interest • Adapt to dynamic real-world events in near real-time • Provide event (new data) change global update • Poor Information Quality and Availability • Growing requirement for significant improvements in information quality • Accurate: information that conveys the true situation. • Relevant: information tailored to specific requirements of the mission, role, task or situation at hand. • Timely: information is provided in time to make decisions. • Useable: information presented in a common, easily understood format. • Complete: information that provides all necessary (or available) information needed to make decisions. • Brief: information tailored to the level-of-detail required to make decisions and reduces data overload. • Trusted: information quality and content can be trusted by stakeholders, decision makers and users. • Secure: Information is protected from inadvertent or malicious release to unauthorized participants. • Overly Complex IT environments • Collapse the number single domain networks into one virtual MLS domain

  9. SOPES: Interoperability Target (Circa 2003) • Selective replication of information (data in context) based on: • Communities of Interest • Filters Semantics • Transactional Data Patterns • Documented and auditable (traceable) description of: • Data aggregation Rules • Data Marshalling Rules • Information Protection Rules • Data Transformation Rules (/patterns) • Dynamic and Static Domain Filters • Communities of Interest and Information Sharing Agreements • Architecture Driven (TOGAF, DODAF, UPDM (UML Class Diagrams)) • Model Driven Rule Transformation • Policy (Rule) Enforcing Data Services • Dynamically Adaptable to Operational Changes • Middleware Agnostic

  10. Elements of and Information Exchange Specification (Circa 2004) Domain Artifacts Examples MIP PDU, XSD NIEM XSDs C2 Core / UCore XSD CAP CP XSD OMG SOPES XSDs Rearranging the Stovepipes Not Directly Supported by Architecture Frameworks OMG SOPES IEDM MIP JC3IEDM

  11. SOPES Conceptual Architecture (Design to Audit; circa 2003)

  12. ASMG Developed Cabability ASMG Delivers the following Capability

  13. SOPES Conceptual Architecture (Design to Audit; circa 2003) User Developed Analysis Tools Information Exchange Model: - Aggregation Rules - Marshalling Rules - Transformations - Dynamic and Fixed Filters - Semantic Guards User Developed Operational Applications DEMONSTRATIONS: 2000 :MIP, 2002/03: BOWMAN CIP Storage of Architecture Models Generation of Executable Rules 2006: OMG Executable Version of Operational Information Exchange Rules Runtime Control over Information Sharing: - COI Configuration - Information Release Control - Policy/Rule Assignment - Policy Activation / Deactivation Policy / Rule Enforcement Services / Trusted Data Service Application Programme Interface (API) to the Data Service User Selected Infrastructure User Selected Infrastructure User Selected Infrastructure

  14. Alignment to DODAF (Circa 2006) • Modeling practices align with DODAF 1.5 and 2.x • A few new stereotypes on UML Class Diagrams (Simple profile extension) • Used in an evolving standard (SOPES IEDM) • Reusable Data patterns for the JC3IEDM • Described in Annex 1 to the SOPES IEDM Specification (http://www.omg.org/spec/SOPES/)

  15. SOPES: Aligned To Architecture Constructs (2009) SOPES AF VIEWS SOPES AF VIEWS SOPES AF VIEWS

  16. SOPES: Process for Policy/Rule Management (Circa 2008) • Derived from operational models • Separation of operational rules from the enforcement applications • Update / extension of rules from controlled stores • Automated transformation of models into executable rules • Aligned to standards architecture, modelling, development, etc … best practices • Architecture / Metadata Driven

  17. SOPES Information Exchange Data Model • SOPES targets the use of the JC3IEDM for: • National Joint Operations • Peacekeeping • Reconstruction Operations • Sustainment Operations • Homeland Defence and Security • Emergency, Crisis and Major Event Management • Extended joint interoperability • Deliver re-useable architecture products that facilitates the use and fielding of the JC3IEDM consistent with DODAF, MODAF, DNDAF and NAF • Promote the develop of products and services within off-the-shelf C4I products

  18. Specification Outline • Section 1: Scope • Section 2: Conformance Criteria • Section 3: Normative References • Section 4: Additional Information • Section 5: SOPES Overview • Section 6: SOPES Background • Section 7: Design Rationale • Section 8: Usage Scenarios • Section 9: SOPES IEDM Details • Section 10: Transactional Models • Section 11: Exemplar Semantics • A: Modeling Profile Description • B: Wrapper Class Descriptions • C: Transactions and OCL • D: XML Schema Descriptions • E: JAVA PSM • F: Glossary

  19. SOPES Specification Statistics • 16 Transactional Packages • 184 Defined Transactions (Data Patterns) • 271 Wrappers and Corresponding JC3IEDM Entities Transactional Packages • Action (45) • Capability (2) • Context (12) • ControlFeature (5) • Facility (21) • GeographicFeature (5) • Holding (2) • Location (22) • Materiel (8) • MeteorologicalFeature (2) • ObjectItem (12) • ObjectType (6) • Organisation (20) • Person (7) • Plans & Orders (13) • Report (2)

  20. Simple Diagrams Define the Data Patterns • Basic UML Class Diagrams are used for the entire process • Similar to other Information Modelling approaches • Details applied based on audience need • Supported by numerous tools costing • $0 – Open Source (OpenAmeos) • $200-300 (Enterprise Architect) • $1000-2000 (Artisan, No Magic) • $2000+ (Rational)

  21. Risks / Benefits to the Approach Risks / Mitigation • Risk: Pieces Missing • IEM and Policy Management Standards • COTS Information Exchange Service • AF Tools • Mitigation: • Standards effort simple waiting for sponsorship (interest is growing) • Prototypes of the core capability exist • SOPES Modeling targeted for DODAF 2.x and UPDM 2.0 (Tools will rapidly follow); Simple ULM diagrams in existing tools will suffice Benefit • Builds on current stated directions (JC2IEDM) • Leverages legacy investments by the international community • Aligns the core pieces of a sustainable • At worst: DND effectively documents is Interoperability requirements • Breaks the perennial search for an all encompassing Silver Bullet "Any intelligent fool can make things bigger, more complex, and more violent. It takes a touch of genius -- and a lot of courage -- to move in the opposite direction." "We can't solve problems by using the same kind of thinking we used when we created them.“ “Insanity: doing the same thing over and over again and expecting different results.” Albert Einstein

  22. Applying the SOPES Approach • Develop a prototype based on the SOPES concept (< 12 months) • Experiment with policy based services • To evolve information sharing agreements fro JOINT Operations • To evolve and maintain Joint CoIs • To evolve dynamic control over information sharing • Work with EISE to develop C&A and TRA processes for interoperable information systems • Work with like minded OGDs, Allies and Coalition Partners to develop the SOPES Approach and Operational Capability • Use OMG membership to push the development of the missing standards • Promote the Development of COTS solutions

  23. Michael Abramson ASMG Ltd, President SOPES Lead Co-Chair OMG C4I Domain Task Force Abramson@asmg-ltd.com Advanced Systems Management Group Ltd 265 Carling Ave, Suite 630, Ottawa 613-567-7097 x222 Q&A

More Related