1 / 25

Implementing the DoD Business Mission Area (BMA) Vision

Implementing the DoD Business Mission Area (BMA) Vision. June 26, 2012. Deedee Akeo, Senior Enterprise Architect, DCMO. Department of Defense. Establishing the Foundation. Department of Defense. Svc Member. Airman. Sailor. BMA Vision using Semantic Standards.

vevina
Download Presentation

Implementing the DoD Business Mission Area (BMA) Vision

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. Implementing the DoD Business Mission Area (BMA) Vision June 26, 2012 Deedee Akeo, Senior Enterprise Architect, DCMO Department of Defense

  2. Establishing the Foundation Department of Defense

  3. Svc Member Airman Sailor BMA Vision using Semantic Standards Relationship described in OWL Data described in RDF W3C Open Standards Legend: DoD Authoritative Data Source User executes BP DoD EA OMG Primitives Conformance class 2.0 NCES BP models uniformly described BP executes via BEA directly Business Enterprise Architecture: BEA Acq Domain Vocabulary SameAs Query BEA directly: DIEA Domain Vocabulary • Enterprise analytics • Compliance • IRB/portfolio management SameAs DM2 Real Prop Domain Vocabulary Log Domain Vocabulary SameAs SameAs SameAs Fin Domain Vocabulary (GFMDI) (EDIPI) HR Domain Vocabulary OUID position billet dept 2 Department of Defense For Official Use Only 2

  4. A Standards-Based Approach Department of Defense

  5. Establishing the Foundation DM2 Ontology BPMN Ontology BEA Ontology LRPs/Bus Rules BEA Content Standard E2Es Standard Bus Process Standard Data Elements Air Force Army Navy Log Domain Ontology HR Domain Ontology Real Prop Domain Ontology • Metadata/Vocabularies converted to ontology • Domain Ontology's extend BEA core ontology • Components map to BEA and extended ontology's • Supported by Equipping The Workforce (ETW) Practicum Department of Defense

  6. BMA Foundational Ontologies Notional View of Foundational Ontologies BPMN 2.0 BEA DM2 H2R P2P Department of Defense

  7. Foundational Ontologies Implementation • Phase I DCMO Ontology Architecture(DM2 2.02, BPMN 2.0, BEA 9.0) • Ontologies created by Small Working Teams (Engineers, Ontologist, SMEs,…) • DM2 Working Team (included representatives from DoD CIO DM2 WG) • BPMN 2.0 Working Team; BEA Working Team • Created DM2 v2.02 Ontology • Based on DM2 Logical and Conceptual Models • Replaced IDEAS constructs with OWL constructs • Created BPMN 2.0 Ontology • Contains BPMN Analytic Conformance • BPMN 2.0 specifications used to create ontology • Plan to submit to OMG as an industry standard • Created BPMN 2.0 to DM2 Mapping Ontology • Maps some BPMN concepts and relationships to DM2 OWL • Mapping achieved via OWL sub-classing and chaining axioms • Created BEA Ontology • BEA Ov-6c uses BPMN 2.0 concepts and relationships directly • Other BEA views (e.g. OV2, OV5a, OV5b, SV1, Svc, CV-2) map to DM2 directly via sub-classing Upper ontology to all architecture ontologies DM2 BPMN-to-DM2 BEA (non-BPMN) BPMN 2.0 Query BEA on DM2 or BPMN terms BEA class replacements Department of Defense

  8. Status of BEA Ontology Framework Release I Delivery • BEA 9.0 data was migrated into DCMO Phase I Foundational Ontologies and tested with SPARQL queries • A “BEA Ontologies” repository has been established on Forge.mil https://software.forge.mil/sf/docman/do/listDocuments/projects.bea/docman.root.bea_ontologies • Version 1.0.0 of DM2 v2.02, BPMN 2.0, and 1.0.0 BEA ontologies have been submitted to the “BEA Ontologies” directory • Ontology versioning is currently specified via owl:versionInfo tag • A “BEA Ontology Framework Usage Guide” and readme file are also provided on Forge.mil Department of Defense

  9. DoD BEA/ DIEA Federation Pilot Department of Defense

  10. Pilot Objectives • Semantic Architecture Federation • Enable disparate sources of architecture to be logically integrated and accessed as a virtual single store, using semantic technology • Make Compliance Easier • Enable a single user perspective on disparate compliance data Department of Defense

  11. Ontology Mapping • Uses DM2 and semantic technology • Demonstrates • Enterprise information search capability with DM2 • Utilizing OWL language and infrastructure to define information models (DM2, BEA, DIEA) and execute queries • Mapping “upper ontology” to “lower ontology's” e.g. “what possible information exists that is within the scope of the concept of a DM2 Activity” User Interface DM2 Ontology BEA Ontology DIEA Ontology OWL to RDB map OWL to RDB map RDB RDB Department of Defense

  12. DM2/BEA/DIEA Ontology Mapping BEA DIEA Department of Defense

  13. Federation Demonstrated 1. DM2 DM2 Ontology 2. DM2->BEA 3. BEA->DIEA r2rml r2rml DIEA Architecture Data (RDB) BEA Architecture Data (RDB) BEA-DIEA physical links Department of Defense

  14. Pilot Summary & Lessons Learned • Demonstrated feasibility of federating architectures to support compliance • Mechanically it is feasible, semantics provides easier infrastructure for scoping and linking • Ontological “similarity” is necessary for meaningful federation “you can’t just connect stuff” – Humans must do this • Demonstrated ontology based-distributed and federated query • SPARQL queries used to query repositories • Human and machine readable, easier to understand and execute • Demonstrated use of DM2 encoded in OWL • DM2 concepts sub-classed to create BEA/DIEA concepts • Establish semantic technology environment for more complex federation use-cases - Pieces available, compliance use case not fully tested Department of Defense

  15. Next Steps • Incorporate BPMN 2.0 OWL-DL as an addition to the OMG standard • Develop and incorporate DM2 v2.03 OWL-DL in DoDAF v2.03, Volume 3 • Build target BEA RDF deployment platform • Continue to equip the workforce (ETW) • Component implementation of semantic standards • Leverage BMA Foundational Ontologies Department of Defense

  16. http://dcmo.defense.gov Department of Defense

  17. DoD Federated/Net-centricity and DCMO Approach “Enterprise Architecture Federation Strategy” on Semantic Alignment excerpt: A key goal of net-centricity is to enable semantic understanding of data so that interoperability can be achieved between any applications that have the ability to access and interpret the structural and semantic rules associated with data. “Net-centric Data Strategy” on Interoperable excerpt: Data Interoperability - The ability to share information among components while preserving its accuracy, integrity and appropriate use. The ability of two or more systems or components to exchange information and to use the information that has been exchanged. Goal: Decentralize data management to communities of interest (COIs) to allow prioritization and collaboration based on immediate operational needs while providing enterprise infrastructure for self-synchronization on a larger scale • DCMO- DoD Federated/Net-centric approach through semantic specifications: • Use of semantic standards to realize DoD federated understanding of data • OWL (Web Ontology Language) • OWL-DL (Descriptive Logic) • SPARQL 1.1 (OWL Query Language) • BPMN2.0/BPMN 2.0 primitives (Business Process) • Standards adopted by DoD in the DISR • A standards based semantic understanding between enterprise applications supports the shift from a stale data warehousing approach to federated dynamic retrieval of authoritative data sources approach Department of Defense

  18. DoDAF and the DM2 Objectives: • Provide a common way to express architectures for DoD and other US NATO partners • Provide a common means for sharing architectural data Existing DoDAF DM2 2.02 Model • DM2 model is based on IDEAS architectural framework • Conceptual Data Model(CDM): Captures high level architecture concepts and relationships • Logical Data Model(LDM): Captures architecture detailed relationships on additional domains (Security, Locations, Process, etc.) • Physical Exchange Specification(PES): Provides a schema and approach to exchange DM2 data across the enterprise in DM2 representation *DoDAF Conformance is achieved when: • The data in a described architecture is defined according to the DM2 concepts, associations, and attributes • The architectural data is capable of transfer in accordance with the PES *As defined in: DoD Architecture Framework Version 2.0, Volume 1: Introduction, Overview, and Concepts Manager’s Guide Department of Defense

  19. DoDAF Conceptual Model Department of Defense

  20. DoDAF DM2 Logical Model Department of Defense

  21. DCMO DM2 OWL-DL Approach • The goal was to describe DM2 completely in OWL open specification based constructs • Started with classes from the DM2 conceptual model • Expanded conceptual class model using details from DM2 logical model • All DM2 IDEAS based constructs that could be expressed in OWL were replaced with standard OWL constructs; e.g. • ideas:Thing => owl:Thing • Ideas:Name => rdfs:label • ideas:Type => owl:Class • All DM2 IDEAS based constructs that were not required to express BEA were not included Department of Defense

  22. DM2 Ontology Sample Snapshot Department of Defense

  23. Semantic BEA Approach • Created DM2 Ontology • Based on DM2 Logical and Conceptual Model • Replaced IDEAS constructs with OWL constructs • Created BMPN 2.0 Ontology • Use BPMN 2.0 specifications as guidelines to create ontology • Ontology closely resembles specifications • Flesh out BPMN Ontology with Signavio generated XML data • *Plan to programmatically migrate BPMN xml generated from tool, into “BPMN RDF” • Created BPMN Ontology Mappings (Rules) • Mapped appropriate BPMN 2.0 classes to DM2 classes (sub-classing) • Mapped appropriate DM2 properties to BPMN properties (rules & chaining axioms) • Transformed BEA BPMN related data (SPIN & SPARQLMotion) • BEA BPMN data: (Ov-6c, *E2E) • Replaced BEA BPMN related concepts with BPMN 2.0 Ontology concepts • Transformed BEA non-BPMN data (SPIN & SPARQLMotion) • Non-BPMN data: (OV2, OV5a, OV5b, SV1, Svc, CV-2) to BEA Core Ontology • Mapped concepts to DM2 directly or indirectly(through non-BPMN ontology) Department of Defense

  24. Benefits of OWL based Ontologies? • OWL is an industry standard to express Ontologies: • WC3 open specification • Support from Open Source and COTS tool vendors • Tools exist to create/visualize OWL files, and process OWL rules • Active growing community continues to submit new, rich, supporting specifications/capabilities; i.e. R2ML, RIF, SPIN, RDFa, etc. • Contains a rich set of constructs and data types • Is extendable and provides a path for modular development & reuse • Captures both data, and rules that can be quickly adjusted in a controlled fashion vs. capturing rules in code with a long change/deploy process • Formal logic and supports reasoning • Interoperability: • OWL files are easily shared, making structures visible and well understood • SPARQL query specifications provide solution to dynamic federated queries • Same concepts with different terms across federated ontologies can be resolved via OWL “sameAs” constructs Advances to goal of establishing DoD architectures that are people readable, machine readable and executable Department of Defense

  25. Semantic Standards • OWL2 (OWL-DL) • Why OWL2 over OWL1? • Increased expressiveness • property chains, disjoint properties, etc. • extended datatypes and data ranges • enhanced annotation capabilities • Why OWL Description Logic(DL) • Maximum expressiveness • Reasoning with completeness and decidability • SPARQL 1.1 • Why SPARQL 1.1? • Useful new features; e.g. “Aggregate” Department of Defense

More Related