implementing the dod business mission area (bma) vision june 26, 2012 department of defense deedee...

Implementing the DoD Business Mission Area

(BMA) VisionJune 26, 2012

Department of Defense

Deedee Akeo, Senior Enterprise Architect, DCMO

Establishing the Foundation

2Department of Defense

3

BMA Vision using Semantic Standards

For Official Use Only3

Query BEA directly:

Acq Domain Vocabulary

HR Domain Vocabulary

Log Domain Vocabulary

Fin Domain Vocabulary

Real Prop Domain

Vocabulary

Business Enterprise

Architecture: BEA

Airman Sailor

Svc Member

position

billet

OUID

dept

User executes

BP

BP executes via BEA directly

Enterprise

analytics

Compliance

IRB/portfolio

management

BP models uniformly described

(GFMDI)(EDIPI)

DoD EA

SameAs

Sam

eAs

SameAsSameAs

DIEA Domain Vocabulary

SameAs

OMG Primitives Conformance

class 2.0

3

DM2


4

A Standards-Based Approach


5

Establishing the Foundation

Real Prop Domain OntologyLog Domain Ontology

BEA Content

BEA OntologyLRPs/Bus Rules

Standard E2EsStandard Bus ProcessStandard Data Elements

BPMN Ontology

DM2 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

HR Domain Ontology

Air ForceNavyArmy


6

BMA Foundational Ontologies

P2P

H2R

DM2BEA

Notional View of Foundational Ontologies

BPMN2.0


7

• 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

Foundational Ontologies Implementation


DM2

BPMN-to-DM2

BPMN 2.0BEA (non-BPMN)

BEA class replacements

Query BEA on DM2 or BPMN

terms

Upper ontology to all architecture

ontologies

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

https://software.forge.mil/sf/docman/do/listDocuments/projects.bea/docman.root.bea_ontologies

DoD BEA/ DIEA Federation Pilot

9Department of Defense

10

• 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

Pilot Objectives


11

• 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”

Ontology Mapping

BEA Ontology DIEA Ontology

User Interface

RDB RDB

OWL to RDB map OWL to RDB map

DM2 Ontology

e.g. “what possible information exists that is within the scope of the concept of a DM2 Activity”


DIEA

BEA

DM2/BEA/DIEA Ontology Mapping


13

Federation Demonstrated

DM2 Ontology

1. DM2

2. DM2->BEA

3. BEA->DIEA

BEA-DIEA physical links

r2rml r2rml

BEA Architecture Data(RDB)

DIEAArchitecture Data(RDB)


14

• 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

Pilot Summary & Lessons Learned


15

• 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

Next Steps


16

http://dcmo.defense.gov


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.

DCMO- DoD Federated/Net-centric approach through semantic specifications:Use of semantic standards to realize DoD federated understanding of data

o OWL (Web Ontology Language)o OWL-DL (Descriptive Logic)o SPARQL 1.1 (OWL Query Language)o BPMN2.0/BPMN 2.0 primitives (Business Process)o 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

“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


18

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

DoDAF and the DM2


19

DoDAF Conceptual Model


20

DoDAF DM2 Logical Model


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.o ideas:Thing => owl:Thing o Ideas:Name => rdfs:labelo ideas:Type => owl:Class

– All DM2 IDEAS based constructs that were not required to express BEA were not included

22

DM2 Ontology Sample Snapshot


23

• 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)

Semantic BEA Approach


24

• 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

Benefits of OWL based Ontologies?


25

• OWL2 (OWL-DL) Why OWL2 over OWL1?

o Increased expressivenesso property chains, disjoint properties, etc.o extended datatypes and data rangeso enhanced annotation capabilities

Why OWL Description Logic(DL)o Maximum expressivenesso Reasoning with completeness and decidability

• SPARQL 1.1 Why SPARQL 1.1?

o Useful new features; e.g. “Aggregate”

Semantic Standards


implementing the dod business mission area (bma) vision june 26, 2012 department of defense deedee...

Documents

working team bea

architecture ontologies

dm2 logical

dm2 owlmapping

bpmn concepts

ontology domain ontologys

bpmn termsupper ontology

teamcreated dm2 v2