Presentation

Interoperable Business
Operations Through Shared
Understanding
Dennis E. Wisnosky, DoD
BMA CTO &
Chief Architect in the
Office of the Deputy Chief
Management Officer
July 13, 2011
DoD Architecture Progression
Blueprinting
Branch office-based;
readable but not
analyzable;
stovepiped
7/13/2011
BEA - Stovepiped
Business Mission-based;
readable within a
Business Mission;
not analyzable; not
integrated with solution
architectures
DWiz DoD DCMO BMA CTO & CA
BEA - Semantic
End-to-End based;
analyzable;
executable; integrated
with & consumable by
solution architectures
Linked Data
2
Ontology – Based Information Integration &
Analytics
Central High School
University Michigan
hasName
O6
HR
Dataset
Col. E.J. Blatt
hasName
Education Institution
hasName
Defense Acquisition U.
Pay Grade
Graph1
person
What Pay Grade is Col. Blatt?
7/13/2011
DWiz DoD DCMO BMA CTO & CA
3
Ontology – Based Information Integration &
Analytics
How much Dwell Time does Col. Blatt have?
Graph2
person
Deployment
History
hasDwellTimeStatus
Dwell Time
Col. E.J. Blatt
24 months
7/13/2011
DWiz DoD DCMO BMA CTO & CA
4
Ontology – Based Information Integration &
Analytics
Central High School
University Michigan
hasName
HR
Dataset
O6
Col. E.J. Blatt
Education Institution
hasName
hasName
Defense Acquisition U.
Pay Grade
person
Graph3
Who has a Pay
Grade of “O6” and
has at least 24
months of Dwell
Time?
person
Deployment
History
7/13/2011
Col. E.J. Blatt
hasDwellTimeStatus
Dwell Time
However,
24 months Size = Complexity
DWiz DoD DCMO BMA CTO & CA
5
Size + Federation = Complexity
Service
Requirements
OSD
Requirements
Agency
Requirements
1,000s of
Systems and Interfaces
7/13/2011
DWiz DoD DCMO BMA CTO & CA
Data Interfaces!
6
Interoperability requires Data Interfaces
• Alternative 1: Proprietary Point-to-Point interfaces
✗
– Scaling: n * (n-1) interfaces for n fully connected systems
– System changes/upgrades potentially affect n-1 systems
• Alternative 2: Interface Standards
✗
– Scaling: n interfaces for n fully connected systems
– Standard as least common denominator may lead to
gaps
✔
• Alternative 3: Semantic Data standards
– Scaling: n data descriptions for n fully connected systems
– Standard description allows for specialized capabilities
Process Interfaces!
7/13/2011
DWiz DoD DCMO BMA CTO & CA
7
Interoperability requires Process Interfaces
• Alternative 1: Proprietary Point-to-Point interfaces
✗
– Scaling: n * (n-1) interfaces for n fully connected systems
– System changes/upgrades potentially affect n-1 systems
• Alternative 2: Standard Process Protocols
✗
– Scaling: 1 Protocol for all process invocations (e.g. HTTP)
– Functionality-agnostic protocol puts burden on data
✔
• Alternative 3: Semantic Process Services
– Each process represents a service
– Scaling: n service descriptions for n available processes
Service Classification Requires Capability Taxonomy
7/13/2011
DWiz DoD DCMO BMA CTO & CA
8
Taxonomy
Level 0
Enterprise Architecture
OV-1
Provides Context
Show Focus Areas
Level 1
End-to-End Processes
Level 2
Business Process Area
H2R
Value Chain
…
O2C
B2C
Show Dependencies
P2P
Organized around Outcomes
Determine
Need
Select
Supplier
Purchase
Good/Svcs
Value
Chain Segments
Receive
Pay
Show
High-LevelSupplier
Info Flow
Good/Svcs
Organized around Key Concepts
Business Process Map
Shows Activities, Decisions,
Services, and Responsibilities
Organized around Objectives
Level 3
Business Process
Precision Through Decomposition
7/13/2011
DWiz DoD DCMO BMA CTO & CA
9
Precision through Decomposition
Level of Ambiguity
Policy Level
Level 1
End-to-End Processes
Level 2
Business Process Area
H2R
Determine
Need
O2
C
P2P
Select
Supplier
Purchase
Good/Svcs
…
Refinement and Specification
Level 0
Enterprise Architecture
B2C
Receive
Good/Svcs
Pay
Supplier
Level 3
Business Process
Implementation Level
7/13/2011
DWiz DoD DCMO BMA CTO & CA
Executing in Cloud
10
Executing in the DoD Cloud
DoD EA
BP model accesses Rules
Ontology & executes the
applicable policy modeled
in SVBR and RIF
Identity
verified
BP model accesses
supporting data via
BEA (using SPARQL
and R2RML)
Y
User in Texas
executes BP
Model to produce
a Personnel roster
that matches a
given Log Manifest
BP model
accesses IDAM
Ontology at
DMDC in
Monterey, CA
N
Roster of Personnel
with matching skill
set to Manifest
produced
BEA
Rules
Ontology
HR Domain
Vocabulary
BEA returns
supporting data
(using SPARQL and
R2RML)
Log Domain
Vocabulary
Equipment
Manifest
MCTFS built on
relational DB in
Virginia
LOG ADS built on
Triple Store in
Ohio
Model Driven Implementation
Acronym Legend: IDAM = Identity Access Management; DMDC = Defense Manpower Data Ctr; SVBR = Semantics of Business Vocabulary and Rules; RIF = Rules
Interchange Format; BEA = Business Enterprise Architecture; SPAQL = query language for Semantic graphs; R2RML = mapping language for ontology-to-relational data
sources; USMC MCTFS = Marine Corps Total Force System; ADS = authoritative data source; LOG = logistics
11
7/13/2011
DWiz DoD DCMO BMA CTO & CA
Model Driven Implementation
7/13/2011
Clear and Unambiguous Instructions
DWiz DoD DCMO BMA CTO & CA
12
DCMO DoD Business Operations Technical
Transition Plan
•
Today’s state is defined by point solutions, redundant technologies and
duplicate capabilities that exist under management silos and compete for
resources
•
The purpose is to provide a plan — a set of initiatives beginning with the
move to a dynamic BEA — to achieve a transition to a future state where
SOA services and systems use enterprise services, share their information
securely for appropriate use and provide enterprise capabilities in agile
and cost-effective 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 semantics 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
patterns for integration defined in the architectures and related guidance
for interconnection so they can make effective use of capabilities provided
by other systems and services, eliminating ad hoc, costly and laborious
interface development to adapt one to the other
DCMO DoD Business Operations
Technical Transition Plan
7/13/2011
Clear and Unambiguous Guidance
DWiz DoD DCMO BMA CTO & CA
13
End-to-End (E2E) Business Models in the
DoD Business Architecture
DCMO Memo signed 4 April 2011
Subject: End-to-End (E2E) Business Models in the
DoD Business Architecture
7/13/2011
•
In order to facilitate integration 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 Consortium (W3C) open
standards Resource Description Framework
(RDF)/Web Ontology Language (OWL) and
modeling notation (Business Process Modeling
Notation (BPMN) 2.0 Analytic Conformance
Class (Primitives)}
•
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 acquisition
and modernization efforts related to critical
activities within the Hire-to-Retire (H2R) and
Procure-to-Pay (P2P) lifecycle models
DWiz DoD DCMO BMA CTO & CA
Semantic BEA Roadmap
14
Semantic BEA Roadmap
3QFY11
4QFY11
1QFY12
Draft BDM Final BDM
BEA
1st
Draft BEA
Transition Plan 2nd Draft BTP
(BTP)
1st Draft BEA
BEA Baseline
Ontology
Ontology
BEA 8.2 HR EIW Mapping
Ontology
DIEA Mapping
ontology
BEA 8.1
Final BTP
FM Mapping
ontology
PfM Ontology
DITPR & SNaPIT
Mapping
Ontologies
Final CM
Process
BEA RDF
Store
BEA Technical
Architecture Design
(TAD) Implement TAD
(PfM)
7/13/2011
Course Catalogue
Complete
3QFY12
4QFY12
Mapping Ontology 8
1QFY13
2QFY13
Mapping Ontology 9
Mapping Ontology 10
BEA 9.0
BEA 10.0
RPILM Mapping
ontology
BEA
Threads/Compare
RDF Data Layer
BEA Graphical Model
GUI Phase I
BEA Federated Secure
SPARQL Module
BEA Reusable
Semantic Toolkit
BEA eTools 2.0
Hosting Solution
(wRDF Store)
Collaboration w/HR&PDA EIW Teams
Collaboration w/HR&PDA EIW Teams
Course Materials
Courses Outlined Finalized
Semantic Training
and Storyboarded
Platform Stood up
BPMN Training
Platform Stood up
Guidance
Equipping the
Workforce
Tools
Draft CM
Process
2QFY12
Semantic & BPMN
Training Offered
Semantic & BPMN
Training Offered
Semantic & BPMN
Training Offered
BEA Reusable
Semantic Toolkit BEA COOP
Architecture
POD 1
Enterprise
Failover/Scalability
These capabilities will
adjust based on
collaborative efforts
Semantic & BPMN
Training Offered
Semantic & BPMN
Training Offered
DoD Business
Operations Technical
Transition Plan v0.99
DoDI 8321 – Semantic
Web Application Across
the BMA
Use of E2E Business
DoDI 8330 – BPMN
Models & Ontology
Primitives
Memo
Application Across
the BMA
DoDI Business
Enterprise Services
Development and
Implementation
DWiz DoD DCMO BMA CTO & CA
Highlighting…
15
Enterprise
Information
Web
(EIW)
Jonathan Underly
(BTA)
Case Study 1
Wed. July 13th
James Steiner
(Oracle)
3rd Keynote
Wed. July 13th
7/13/2011
MaryJo Zaborowski
(Lilly)
Opening Keynote
Thurs. July 14th
Kerrie Holley
(IBM Fellow)
Case Study 2
Wed. July 13th
Lloyd Dugan
(BMA)
Case Study 5
Wed. July 13th
DWiz DoD DCMO BMA CTO & CA
Bill Guinn
(Amdocs)
3rd Opening Keynote
Thurs. July 14th
Chris Moran
(IMSC)
Competency 3
Thurs. July 14th
16
DoD
Semantic
Training
Amy Anda
(BTA)
Competency 1
Thurs. July 14th
Thomas Erl
(SOA Systems)
Afternoon Keynote
Thurs. July 14th
Aneesh Chopra
Federal CTO
2rd Opening Keynote
Wed. July 13th
7/13/2011
DWiz DoD DCMO BMA CTO & CA
General James
Cartwright
Afternoon Keynote
th
Wed.
July 13Room
Demo
17
7/13/2011
http://www.bta.mil/2TRa1n3/posters/poster.html
DWiz DoD DCMO BMA CTO & CA
For the rest of the story!
18
For the rest of the story!
http://www.commondefensequarterly.com/
7/13/2011
DWiz DoD DCMO BMA CTO & CA
Thank you!
19
Thank you!
Questions?
Dennis.Wisnosky@osd.mil
7/13/2011
DWiz DoD DCMO BMA CTO & CA
20