View
214
Download
2
Category
Preview:
Citation preview
Dennis E. Wisnosky, DoD BMA CTO &
Chief Architect in the Office of the Deputy Chief
Management Officer
Realizing Efficiency & Interoperability: SOA & Semantic Technology in the Business Mission Area (BMA), U.S. DoD
November 17, 2011
DoD Semantic Technology Clip h@p://www.youtube.com/watch?v=OzW3Gc_yA9A
DCMO CTO/CA
11/17/2011 DWiz DoD DCMO BMA CTO & CA 2
Intel Mission Area
Enterprise InformaSon Environment Mission Area
Business Mission Area
Warfighter Mission Area
Dennis E. Wisnosky, DoD BMA CTO & Chief Architect in the Office of the
Deputy Chief Management Officer (DCMO)
Missions of the DoD
DoD Management Challenges
DoD Management Challenges
11/17/2011 DWiz DoD DCMO BMA CTO & CA 3
A More Reasoned Approach
HRM/ Med FM
Logistics RPILM WSLM/ MSSM
Strategy and Roadmap for DoD Business Opera=ons Transforma=on
Performance Measures
Semantic Information
CV & Primitives
Past (BMA Federation Strategy version 2.4a)
Present (BOE Execution Roadmap)
BEA 3.0
BOE Vision
DCMO/CIO Policies CIO – DIEA, Segment Archi.
Arch. Fed.
MDR
Federation Implementation Plan
CIO/DISA – Federal Cloud
BEA 8.x & Beyond
Business Intelligence
(BTI) NCES/CES
BOE Service Enablement
Domains
Execution DBSAE SOA Imp. Strategy
Future (BMA Technical Transition Plan version 1)
Initial BOE Experience
DBSMC/IRBs DCMO/DCIO; EGB; BECCM
Version 2.4a
DoD Strategic Mgmt. Plan (SMP)
Common Vocabulary (Ontologies)
RDF OWL other
Enterprise Stds.
Vision & Strategy
Planning & Roadmap
Infrastructure
Governance
Data Integration
Biz. Intelligence
Rules/Workflow
Dat
a S
harin
g an
d B
I Ena
blem
ent
Roadmap: Architecture Governance Socialization Services Infrastructure
Security
The Journey
DoD Architecture Progression
BlueprinSng BEA -‐ Stovepiped BEA -‐ SemanSc
Business Mission-‐based; readable within a Business Mission; not analyzable; not
integrated with soluSon architectures
End-‐to-‐End based; analyzable; executable;
integrated with & consumable by
soluSon architectures
Branch office-‐based; readable but not
analyzable; stovepiped
11/17/2011 DWiz DoD DCMO BMA CTO & CA 5
Enabling Strategic Management
Enabling Strategic Management
Enterprise E2E and OSD
Policies
OperaSonal Process and Service Policies
BEA Ontology SemanSc DescripSon
ADS
Strategic ObjecSves
4.0 Preserve and Enhance the All-‐Volunteer Force
2.0 Support ConSngency Business OperaSons
4.2.10 Percentage of the Dept. AD who meet objecSves for Sme deployed vs Sme at home
Army Dwell Time E2E USMC Dwell Time E2E
CII ODSE CII ODSE
DoD Personnel Management E2E
Dwell Time
11/17/2011 DWiz DoD DCMO BMA CTO & CA 6 Vision for DoD Solution Architectures
A Vision for DoD Solu=on Architectures
11/17/2011 DWiz DoD DCMO BMA CTO & CA 7
Query BEA directly: Acq Domain Vocabulary
HR Domain Vocabulary
Log Domain Vocabulary
Fin Domain Vocabulary
Real Prop Domain Vocabulary
Business Enterprise
Architecture: BEA
Sailor
Svc Member OUID
User executes BP
BP executes via BEA directly
Ø Enterprise
analy=cs
Ø Compliance
Ø IRB/porMolio
management
BP models uniformly described
(GFMDI) (EDIPI)
DoD EA
SameAs
Warfighter Domain Vocabulary
OMG PrimiSves Conformance class
2.0
Data described in RDF RelaSonship described in OWL W3C Open Standards Legend: DoD AuthoritaSve Data Source An Aha Moment
11/7/2011 DWiz DoD DCMO BMA CTO & CA 7
Ontology – Based Informa=on Integra=on & Analy=cs
HR Dataset
What Pay Grade is Col. Blatt?
Graph1
hasName Education Institution
Pay Grade hasGrade
O6
Col. E.J. Blatt
hasName
Central High School
hasName
person
University Michigan
Defense Acquisition U.
11/17/2011 DWiz DoD DCMO BMA CTO & CA 8
Ontology – Based Informa=on Integra=on & Analy=cs
How much Dwell Time does Col. Blatt have?
Graph2
person Dwell Time
24 months hasValue
Col. E.J. Blatt
hasName Deployment
History
hasDwellTimeStatus
11/17/2011 DWiz DoD DCMO BMA CTO & CA 9
Ontology – Based Informa=on Integra=on & Analy=cs
Graph3 Who has a Pay Grade of “O6” and has at least 24 months of Dwell Time?
HR Dataset hasName
Education Institution
Pay Grade hasGrade
O6
Col. E.J. Blatt
hasName
Central High School
hasName
person
University Michigan
Defense Acquisition U.
Dwell Time
24 months hasValue
Col. E.J. Blatt
hasName Deployment
History
hasDwellTimeStatus person
11/17/2011 DWiz DoD DCMO BMA CTO & CA 10 Standards Based Architecture
Standards-‐based Architecture -‐ Primi=ves
foun
datio
n fo
r
PrOnto Ontology (Lexicon)
PriMo Modeling Guide
Different Frameworks
inpu
t for
influ
ence
s
info
rmed
by
Standards Best Practices
Standard Language (terms and defini=ons)
Standard Symbols
Resistor symbol
Capacitor symbol
This agreed upon representation of electrical engineering allows a common understanding…
Engineering Language and Symbols:
Music Scale symbols
Notes symbols
This agreed upon representation of music allows a common understanding…
Music Language and Symbols:
Archite
cture Prim
i=ves
Architecture Primi=ves
• DoDAF 2.0 serves as the foundaSon for architecture primiSves • Use Cases being developed and used to drive pilots
Style Guide
Dic=onary
The Semantic BEA 11/17/2011 DWiz DoD DCMO BMA CTO & CA 11
Other Disciplines can do it!
The Seman=c BEA
Human Readable
Machine Readable
Executable
11/17/2011 DWiz DoD DCMO BMA CTO & CA 12
Apr 4 Memo
Seman=c BEA Benefits
• Visibility: pull & display (vice store!) enterprise informa=on directly from the authorita=ve data sources
• Agility: plug-‐and-‐play federated environment so new systems or analy=cal needs can come online and go offline without disrup=ng the overall environment
• Access: build federa=on into the solu=on
• Standards: leverage BPM and Seman=c Web technology standards (RDF/OWL) developed by DARPA and approved by W3C and OMG
• Savings: People readable Architecture, Machine readable Architecture, Executable Architecture, Long-‐term re-‐use of authorita=ve data RDF/ OWL
BPMN
11/17/2011 DWiz DoD DCMO BMA CTO & CA 13
Apr 4 Memo
End-‐to-‐End (E2E) Business Models in the DoD Business Architecture
• In order to facilitate integraSon of the systems and business architecture within the E2E lifecycle models, the BEA will be described in an ontology using a common language – {World-‐Wide Web ConsorSum (W3C) open standards Resource DescripSon Framework (RDF)/Web Ontology Language (OWL) and modeling notaSon (Business Process Modeling NotaSon (BPMN) 2.0 AnalySc Conformance Class (PrimiSves)}
• The E2E Framework shall be used to drive BEA content within the federated BEA ontology
• Future releases of the BEA will be synchronized with our highest priority system acquisiSon and modernizaSon efforts related to criScal acSviSes within the Hire-‐to-‐ReSre (H2R) and Procure-‐to-‐Pay (P2P) lifecycle models
DCMO Memo signed 4 April 2011 Subject: End-‐to-‐End (E2E) Business Models in the
DoD Business Architecture Clear and Unambiguous Instructions 11/17/2011 DWiz DoD DCMO BMA CTO & CA 14
DCMO DoD Business Opera=ons Technical Transi=on Plan
• Today’s state is defined by point soluSons, redundant technologies and duplicate capabiliSes that exist under management silos and compete for resources
• The purpose is to provide a plan — a set of iniSaSves beginning with the move to a dynamic BEA — to achieve a transiSon to a future state where SOA services and systems use enterprise services, share their informaSon securely for appropriate use and provide enterprise capabiliSes in agile and cost-‐effecSve ways
• Systems and services then use the common or standard vocabularies set out in the architectures to express the data that they exchange in order to integrate
• They use this vocabulary in accord with standard ontologies that define the semanScs of the vocabulary, and which is published such that all recipients of the exchanged data can make reference to them so as to be able to determine the meaning of the data they receive when needed
• Systems and services are built using the common set of standards and pa@erns for integraSon defined in the architectures and related guidance for interconnecSon so they can make effecSve use of capabiliSes provided by other systems and services, eliminaSng ad hoc, costly and laborious interface development to adapt one to the other
DCMO DoD Business Opera=ons Technical Transi=on Plan
6/7/2011 15 DWiz DoD DCMO BMA CTO & CA This Changes Everything
Interoperability requires Data Interfaces
• AlternaSve 1: Proprietary Point-‐to-‐Point interfaces – Scaling: n * (n-‐1) interfaces for n fully connected systems – System changes/upgrades potenSally affect n-‐1 systems
• AlternaSve 2: Interface Standards – Scaling: n interfaces for n fully connected systems – Standard as least common denominator may lead to gaps
• AlternaSve 3: Seman=c Data standards – Scaling: n data descripSons for n fully connected systems – Standard descripSon allows for specialized capabiliSes
11/17/2011 DWiz DoD DCMO BMA CTO & CA
✗
✗
✔
16
And Process Interfaces!
Interoperability requires Process Interfaces
• AlternaSve 1: Proprietary Point-‐to-‐Point interfaces – Scaling: n * (n-‐1) interfaces for n fully connected systems – System changes/upgrades potenSally affect n-‐1 systems
• AlternaSve 2: Standard Process Protocols – Scaling: 1 Protocol for all process invocaSons (e.g. HTTP) – FuncSonality-‐agnosSc protocol puts burden on data
• AlternaSve 3: Seman=c Process Services – Each process represents a service – Scaling: n service descripSons for n available processes
11/17/2011 DWiz DoD DCMO BMA CTO & CA
✗
✗
✔
17 Interoperability!
Seman=c Data Strategy
4 Nov 11 Jonathan Underly -‐ EIW Manager 18
Target State Seman=c BEA
(near) Exponential Integration problem (n2 – n)
(near) Linear Integration problem (2n-1)
Inflexible Data model Total interoperability for 100 systems > $4B*
Promotes opera=onal silos Promotes data duplica=on
Current State System of Systems
Infinitely extensible data model Total interoperability for 100 systems < $40M*
Promotes cross-‐domain reasoning Encourages data reduc=on
BEA
* Assumes $400K/interface Our Toolbox Must Change!
Our Technology Toolbox is Evolving
WILL EVOLVE TO TOOLS THAT…
PRODUCE & USE NON-‐PROPRIETARY, OPEN STANDARDS &
PROTOCOLS
11/17/2011 DWiz DoD DCMO BMA CTO & CA 19
Walking the Talk - EIW
Department of Defense Enterprise Informa=on Web (EIW)
Jonathan Underly – EIW PM
11/17/2011 DWiz DoD DCMO BMA CTO & CA 20
BLUF
Boiom Line Up-‐Front (BLUF)
§ The DoD Enterprise InformaSon Web (EIW) is pioneering the adopSon of SemanSc Technology and approaches that can be the way forward for enterprise business intelligence and soluSon architectures in the DoD.
11/17/2011 DWiz DoD DCMO BMA CTO & CA 21
A New Approach to Personnel Visibility
A New Approach to Personnel Visibility (PV)
The HR Enterprise Informa=on Web (EIW) is a mechanism for reaching into Authorita=ve Data Sources (ADS) to sa=sfy enterprise informa=on needs. It accomplishes three things:
1. Reports near real-‐=me, authorita=ve informa=on on-‐demand 2. Supports enterprise informa=on standards (Open; HRM ES) 3. Supports IT flexibility/agility
Single view Mul=ple Sources
Federator
DMDC Data Stores
Services Data
External Data
HR Data Store
HR Data Store
HR Source
HR Data Store
Domain O
ntology
HR Source HR
Source HR Source
Aggrega=on
11/17/2011 DWiz DoD DCMO BMA CTO & CA 22
Proof of Delivery (PoDs) Every 90 Days
Lessons Learned
Ont
olog
y D
evel
opm
ent HR Ontology Development
HRM Enterprise Standards Modeling & Enterprise AnalyScal Needs Discovery
Qtr 1
FY11
Qtr 1 Qtr 2 Qtr 3
FY10
Qtr 2 Qtr 3 Qtr 4 Qtr 1
FY12
Qtr 4
Tech
nolo
gy D
evel
opm
ent
ADS/BPA Modeling: CII
ADS/BPA Modeling: SeparaSons
ADS/BPA Modeling: “Member Profile”
ADS/BPA Modeling: Increment 5-‐N
ADS/BPA Modeling: Federated Ontology
Legend: ADS/BPA = AuthoritaSve Data Source/Business Process Area
We Are Here
Delivery every 90 Days
EIW Roadmap – Phased Approach
ADS/BPA Modeling: Military Leave
Distributed FederaSon
11/17/2011 DWiz DoD DCMO BMA CTO & CA 23
PoD Progression
24
Data Source: CII (USA)
Proxy Server
Dashboard
SQL
Source Mappings
AKO/DKO
DMDC
Firewall DMZ
HTTPS Port 443 for web traffic
Web Service Call
PoD 1: Models inform the locaSon and extracSon of data
Composite App Srvr
Ab IniSo App Srvr Triple Store
SQL
RDF Load Triple Store Loader (SemanSc Mapping)
SPARQL Source Ontology
Web/App Server
POD2: • Model Driven
AnalyScs • Model Driven ETL • Triple Store
Data Source: MCTFS (USMC) SQL
PoD3: Store and query
multiple test data sets in a triple
store
PoD4: • Access data from relational
store at run time using semantic query engine
• SPARQLizer alpha release with D2RQ mappings
PoD5: • Access data from relational store at
run time; • SPARQLizer 1.0 release, support
SQL equivalent commants • Added Ad-hoc & Faceted Search
capability • More demographic reports
SPARQLizer SPARQLizer
SPARQL
SQL SQL
Common Vocabulary
SPARQL
SPARQL
Domain Ontology
Mapping Ontology
Source Ontology
SPARQL
Domain Ontology
Mapping Ontology
SPARQL
SPARQL
SPARQL
SPARQL
Federator
Dashboard Gadget Gadget Gadget
SPARQL SPARQL External Data Source(s)
Gadget
PoD6: • Seman=c Federa=on of local data • Aggregated Svc Member
Demographics • Open Social gadgets
SPARQLizer
PDA Metrics
SQL Extensibility and Reuse
• PDA Metrics Added • USMC MCTFS Mappings reused • NO changes to schemas or other
queries Long Term Roadmap 11/17/2011 DWiz DoD DCMO BMA CTO & CA 24
Execu=ng in the DoD Cloud
HR Domain Vocabulary
Log Domain Vocabulary
Equipment Manifest
User in Texas executes BP Model
to produce a Personnel roster that matches a
given Log Manifest
BP model accesses Rules Ontology & executes the applicable policy modeled
in SVBR and RIF
DoD EA
BP model accesses IDAM Ontology at DMDC in
Monterey, CA
N
Y
SameAs
BP model accesses supporSng data via BEA (using SPARQL
and R2RML)
LOG ADS built on Triple Store in
Ohio
MCTFS built on relaSonal DB in
Virginia
BEA
Roster of Personnel with matching skill set to Manifest
produced
IdenSty verified
Rules Ontology Policy
BEA returns supporSng data
(using SPARQL and R2RML)
Acronym Legend: IDAM = Iden=ty Access Management; DMDC = Defense Manpower Data Ctr; SVBR = Seman=cs of Business Vocabulary and Rules; RIF = Rules Interchange Format; BEA = Business Enterprise Architecture; SPAQL = query language for Seman=c graphs; R2RML = mapping language for ontology-‐to-‐rela=onal data sources; USMC MCTFS = Marine Corps Total Force System; ADS = authorita=ve data source; LOG = logis=cs 11/17/2011 DWiz DoD DCMO BMA CTO & CA 25
We are Expecting Enormous Benefits
BEA
Tools
Equipp
ing th
e Workforce
Guidance
3QFY11 4QFY11 1QFY12 2QFY12 3QFY12 4QFY12 1QFY13 2QFY13
BEA Technical Architecture Design
(TAD) Implement TAD (PfM)
CollaboraSon w/HR&PDA EIW Teams
11/17/2011 DWiz DoD DCMO BMA CTO & CA 26
Seman=c BEA Roadmap
BEA 9.0
1st Draw BEA Ontology
1st Draw BEA TransiSon Plan
(BTP)
HR EIW Mapping Ontology
BEA 10.0
Mapping Ontology 8 Mapping Ontology 9 Mapping Ontology 10
BEA Baseline Ontology
Final BTP
BEA Threads/Compare RDF Data Layer
BEA Graphical Model GUI Phase I BEA Federated Secure
SPARQL Module BEA Reusable SemanSc Toolkit
BEA Reusable SemanSc Toolkit POD 1
BEA COOP Architecture Enterprise Failover/Scalability
Use of E2E Business Models & Ontology Memo
DoDI 8330 – BPMN PrimiSves ApplicaSon Across the BMA
DoDI 8321 – SemanSc Web ApplicaSon Across the BMA
DoDI Business Enterprise Services Development and ImplementaSon
Course Catalogue Complete
Courses Outlined and Storyboarded
Course Materials Finalized
SemanSc Training Plaxorm Stood up
BPMN Training Plaxorm Stood up
SemanSc & BPMN Training Offered
SemanSc & BPMN Training Offered SemanSc & BPMN
Training Offered
SemanSc & BPMN Training Offered
SemanSc & BPMN Training Offered
BEA 8.1 BEA 8.2
BEA RDF Store
PfM Ontology
Final CM Process
Final BDM
2nd Draw BTP
Draw BDM
Draw CM Process
These capabiliSes will adjust based on
collaboraSve efforts CollaboraSon w/HR&PDA EIW Teams
DITPR & SNaPIT Mapping Ontologies
DIEA Mapping ontology
FM Mapping ontology
RPILM Mapping ontology
BEA eTools 2.0 HosSng SoluSon (wRDF Store)
DoD Business OperaSons Technical TransiSon Plan v0.99
Model Driven Implementation
Model Driven Implementa=on
11/17/2011 DWiz DoD DCMO BMA CTO & CA 27
And, if this logic does not Work
Flight Deck Management Challenges
11/17/2011 DWiz DoD DCMO BMA CTO & CA 28
h@p://www.youtube.com/watch?v=qh42k3Kvxck
Thank you!
Thank you!
11/17/2011 DWiz DoD DCMO BMA CTO & CA 29
QuesSons?
Dennis.Wisnosky@osd.mil
For the rest of the story! The image cannot be displayed. Your computer may not have enough memory to open the image, or the image may have been corrupted. Restart your computer, and then open the file again. If the red x still appears, you may have to delete the image and then insert it again.
h@p://www.commondefensequarterly.com/ 11/17/2011 DWiz DoD DCMO BMA CTO & CA 30
Recommended