Standards Based Architectures
in Support of DoD Business
Operations – Primitives &
Common Vocabulary
Dennis E. Wisnosky,
DoD BMA CTO &
Chief Architect in the
Office of the Deputy Chief
Management Officer
March 22, 2010
DCMO CTO/CA
Missions of the DoD
Warfighter
Mission
Area
Business
Mission
Area
Intel
Mission
Area
Enterprise Information Environment
Mission Area
Dennis E. Wisnosky, DoD BMA CTO &
Chief Architect in the Office of the
Deputy Chief Management Officer (DCMO)
3/22/10
DWiz DoD DCMO BMA CTO & CA
1
ACDM
Mission: To be the premier professional organization that shares and refines
the disciplines that accomplish Configuration, Data, and Change
Management necessary for the delivery and support of products and
services in a competitive and regulated global business environment.
“…ensure that the disciplines of CM and DM
continue to gain momentum and respect as
value-added adjuncts to the business process…”
~ Cynthia Hauer,
President, ACDM
(http://www.acdm.org/execboard.php)
RPA Perform Physical Asset Accountability – BEA 7.0
Performer
Processes
& Activities
Data Objects (Business
Rules, Resources)
Information
Exchanges
3/22/10
DWiz DoD DCMO BMA CTO & CA
2
Big Picture!
3/22/10
DWiz DoD DCMO BMA CTO & CA
3
Strategy and Roadmap for DoD Business Operations Transformation
Past
Present
Future
(BMA Federation Strategy version 2.4a)
(BOE Execution Roadmap)
(BMA Architecture Strategy version 3.0)
DoD Strategic Mgmt. Plan (SMP)
DCMO/CIO Policies
BEA 3.0
CIO - DIEA
CV & Primitives
Arch. Fed.
Performance Measures
Initial BOE
Experience
BI
MDR
BI
Version2.
4a
Federation
Implementation
Plan
BOE Vision
Data Integration
Roadmap
BOE Service
Enablement
Planning & Roadmap
Infrastructure
Governance
HRM/ Med
FM
Logistics
RPILM
WSLM/
MSSM
Common Vocabulary
Execution
DBSAE SOA
Imp.
Strategy
(BTI) NCES/CES
DBSMC/IRBs
3/22/10
Stds.
RDF
OWL
Semantic Mediation & Data
Virtualization
Domains
Vision & Strategy
Semantic Information
Enterprise Standards
BEA 8.x
Cloud Strategy
CIO/DISA – Federal Cloud
DCMO/DCIO; EGB; BECCM
DWiz DoD DCMO BMA CTO & CA
4
Common Vocabulary
Functional / Requirements
• Governance
• Identify Conflicts
• Resolve Conflicts
• Review Vocabulary
• Approve Vocabulary
Building the
Vocabulary
• Alignment
• Unify Format
• Parse Input
• Cleanse Vocabulary
• Match Terms
• Publish Results
Legacy Systems
3/22/10
BEA Common
Business Vocabulary
• Architecture
• C.A.R.P. / AV-2 Template
• Match Terms
• Build Models / Primitives
• Validate Models
Using the
Vocabulary
Common Semantics
Common Vocabulary
RDF Store
Technical / Systems
DWiz DoD DCMO BMA CTO & CA
• Mediation & Virtualization
• Routing
• Content-based
Addressing
• Protocol Adaptation
• Messaging
Mediation
Virtualization
5
E2E Model Hierarchy
Enterprise Level
Operational Level
3/22/10
DWiz DoD DCMO BMA CTO & CA
6
Details!
3/22/10
DWiz DoD DCMO BMA CTO & CA
7
Ability to Communicate
Enterprise Architecture is primarily about
People talking to each other...
3/22/10
DWiz DoD DCMO BMA CTO & CA
8
Ability to Communicate
...so we can build
Systems and Services that talk to each
other
3/22/10
DWiz DoD DCMO BMA CTO & CA
9
Why is this hard?
3/22/10
3/17/10
4/13/2015
DWiz DoD DCMO BMA CTO & CA
10
Enterprise Architecture
Many Frameworks
Many Views
Many Techniques
– UML, IDEF, BPMN, RAD, EPC, PowerPoint and
many, many others...
3/22/10
DWiz DoD DCMO BMA CTO & CA
11
We don’t speak the same language!
We don’t see the same things
in pictures!
3/22/10
DWiz DoD DCMO BMA CTO & CA
12
Address Standards…
 The problem first started on the USGA Website.
– It would not accept:
• # Xxxx ### Street Name (correct)
• # X. ### (No spaces)
• #X### (Numbers only)
– It would accept ##### Street Name (doesn’t exist)
 Several searches were conducted using search
engines specializing in maps. Some could find the
address most could not (examples on following
slides).
– Issue: All these sites are translating the natural language
differently.
– Issue: The United States Postal Service guide to
address standards is 208 pages long. Does this
constitute a standard?
3/22/10
DWiz DoD DCMO BMA CTO & CA
13
All are in the business of maps
but come up with different results…
Mapquest was unable to find
the Address typed correctly
# Xxxx ### Street Name
City
State
Street Name
City, State Sip
### Street Name
Street Name
However, when the first #
Xxxx combination was
dropped 2 addresses were
suggested
City, State Sip
City
State
The USGA site
separates address
into 2 fields: House
number, Street Name
** Yahoo maps
was unable to
find anything
in any format.
3/22/10
This is why it would
only accept #####
not #X###. To
specific.
DWiz DoD DCMO BMA CTO & CA
14
Google can find it…
With incorrect information
The address is searchable in Google. In
both these examples part of the address was
wrong and it was still found.
Below: Left of the & south (this was added
back in by Google).
# Xxxx ### Street Name City, State Zip
#X## Street Name City, State Zip
Other Suggestions
#X## Street
Name City,
State Zip
Right: Put city as Chicago and it recognized
it should be Naperville.
XXX Street Name City, State
#X## Street Name City, State Zip
##### Street Name City, State
Other Suggestions
Street Name City, State Zip
The address
##### which
was accepted
by USGS could
not be found.
3/22/10
Street Name
City, State
Zip
DWiz DoD DCMO BMA CTO & CA
15
Google Earth knows me precisely
3/22/10
DWiz DoD DCMO BMA CTO & CA
16
Building Common Vocabularies
What is the
architecture
supposed to
achieve?
Capability
Vocabulary
Define Capabilities
Items:
• Objectives
• Features
• Services
Capability
View
3/22/10
Which
processes/
activities will
provide the
capabilities?
Activity
Define
Activities
Vocabulary
Items:
• Verbs
Which data/
resources will
be consumed
or produced?
Resource
Define
Resources
Vocabulary
Items:
•Nouns
Process
View
Data &
Rule View
DWiz DoD DCMO BMA CTO & CA
Who/What
will be
involved?
Performer
Define
Performers
Vocabulary
Items:
• Roles
• Systems
• Actors
Process
View
17
Building, Managing and Maintaining the
DoD CV
BECCM
DoD COI’s
Build and
Manage
CV
DoD CV
BEA Team
3/22/10
DWiz DoD DCMO BMA CTO & CA
18
COI Operational Governance
DoD Governance of DoD Core Data, Universal Core
Warfighter
Communities
of Interest
Business Enterprise Common Core Metadata COI, Common Core
(BECCM COI)
FM COI
HRM COI
Data Governance
Data Governance
FM COI Info
Models
HRM COI Info
Models
RP&ILM COI
Data Governance
RP&ILM COI Info
Models
Intelligence
Communities
of Interest
WSLM COI
MSSLM COI
Data Governance
Data Governance
WSLM COI Info
Models
MSSLM COI Info
Models
HR EIW
Accept & Expose
data using
Enterprise
Standards
3/22/10
DWiz DoD DCMO BMA CTO & CA
19
We don’t speak the same language!
We don’t see the same things
in pictures!
3/22/10
DWiz DoD DCMO BMA CTO & CA
20
Other Disciplines Can Do It
Not This
3/22/10
But This:
DWiz DoD DCMO BMA CTO & CA
21
Standards-based Architecture - Primitives
Standards
informed
by
•DoDAF 2.0 serves as the
foundation for architecture
primitives
•Use Cases being developed and
used to drive pilots
3/22/10
Architecture Primitives
Capacitor symbol
PriMo
Modeling Guide
foundation
for
Resistor symbol
PrOnto
Music Language and
Symbols:
Music Scale symbols
Notes symbols
This agreed upon representation
of music allows a common
understanding…
Ontology (Lexicon)
input for
Engineering Language
and Symbols:
This agreed upon representation
of electrical engineering allows a
common understanding…
influences
Best Practices
Architecture Primitives
Standard
Symbols
Different
Frameworks
DWiz DoD DCMO BMA CTO & CA
Standard
Language
(terms and
definitions)
22
Patterns & Primitives
 Provides basic definitions
of the architecture model
semantics
 Provides elementary rules
for the connectivity of
primitive constructs
 Provides foundation
building blocks for
constructing architecture
products
 Caveat: A common
vocabulary by itself does
not guarantee high quality
products
3/22/10
PriMo
PrOnto
DWiz DoD DCMO BMA CTO & CA
 A style guide provides
subjective advice that will
ensure the design of high
quality products
 A style guide advises on
– Choice of words
• Which constructs
are appropriate
in a given
situation
– Choice of grammar
• How to combine
constructs to
maximum effect 23
Example
Application:
Joint Close Air
Support
3/22/10
3/17/10
4/13/2015
DWiz DoD DCMO BMA CTO & CA
24
24
Vocabulary-based Primitives
Joint Close
Air Support
3/22/10
DWiz DoD DCMO BMA CTO & CA
25
3-Level Hierarchy: Milestones
1: Milestones
2: Collaboration
3: Procedures
3/22/10
DWiz DoD DCMO BMA CTO & CA
26
Enterprise Information
Warehouse/Web
3/22/10
DWiz DoD DCMO BMA CTO & CA
27
Problem Statement
 Personnel Visibility (PV) Problem: DoD currently lacks the enterprise level information
to quickly and accurately account for personnel, manage troop strength, and war plan
– Impact: challenges the objective of having the right personnel in the right place at
the right time to fight battles and win wars.
– Sample COCOM personnel visibility needs:
• Requirement 28.0: Provide timely and accurate information on the location, status, and
identity of units, personnel, equipment, and supplies with emphasis on Personnel
including patients.
• Requirement 124.0: Identify the availability of personnel within the active forces, or
within the reserves and other sources when analyzing mobilization alternatives, to
satisfy filler, replacement and force expansion personnel requirements.
 Federation Problem: PV requires data from within and across many distinct system
and organizational boundaries (domains)
– It is often not possible to federate and integrate applications across domains
– Domain transactional systems constantly changing.
– Changes in relational architecture are expensive
3/22/10
DWiz DoD DCMO BMA CTO & CA
28
Big Picture
 Use HR Domain Ontology (HR “dictionary” or
common vocabulary) to support a run-time
federated information environment
– Create a virtual web of DoD authoritative source HR
systems
• Create a single “view” of distinct data
– Answer any HR information requirements with existing
HR systems or show the gaps
– Plug-and-play federated environment so new systems
can come online and go offline without disrupting the
overall environment
3/22/10
DWiz DoD DCMO BMA CTO & CA
29
What are we doing?
1. Building an ontology (using W3C standards) of the DoD HR Domain



An ontology is a conceptual model that is executable (queryable);
The ontology unambiguously describes information in the DoD HR
Domain
It builds a common vocabulary that will support information integration
(federation)
2. Building ontologies to describe the different information consumers
and providers in the HR Domain


Consumers - CHRIS's, Processes, COCOM 129's
Providers – HR Systems
3. Using the HR Domain Ontology to show how the different
information consumers and providers relate to a common model
(vocabulary)

Mapping CHRIS's to concepts in the HR Ontology

Mapping DIMHRS to concepts in the HR Ontology


3/22/10
Gap Analysis - Showing how CHRIS's relate to DIMHRS
More complex than simply gap or no gap
DWiz DoD DCMO BMA CTO & CA
30
Semantic Technology Standards
 RDF – Resource Description Framework
– Graph based information model; triples (node-edge-node)
– Make arbitrary assertions about things
 URI – Uniform Resource Identifier
– Universal identifiers that can be used to uniquely identify
something (concept or thing) across any application
 RDFS/OWL – RDF Schema/Ontology Web Language
– Standard language for defining a vocabulary (aka ontology) to
describe things
 SPARQL – SPARQL Protocol and RDF Query
Language
– Query language for RDF data
3/22/10
DWiz DoD DCMO BMA CTO & CA
31
Project Execution Model
3/22/10
DWiz DoD DCMO BMA CTO & CA
32
Multiple Sources
HR EIW
DMDC Data Stores
Proofs of Delivery Modeling
Component
Data Stores
Data Data DataData
Store Store Store
Store
12/10
Phase 2
Increment 1
Publish Stds
Increment 2
Publish Stds
Increment 3
Transition
9/12
Phase 3
9/15
Sustainment
Map OSD HR to Service Ontologies
Compensate
Develop, etc
Publish Stds
mashup
External Data
Services
6/10
Phase 1
3/22/10
DoDI Personnel
Data Store
Common Vocabulary
HR
Data Store
HR
Data Store
HR
Data Store
The HR EIW is a mechanism for reaching into
service applications to satisfy enterprise HR
information needs. It accomplishes three
things:
– Reports real-time, authoritative HR
information on-demand.
– Supports HR enterprise information
standards.
– Supports IT flexibility.
9/09
Single View
Federated Ontology
DIMHRS & CHRIS Alignment
Publish Stds
Increment 4-n
Modeling
RDF Store
Delivered 18 Dec 09
Process/Rules Mgt
SME RDF Modeling
12/31
RDF Info Services
3/31
Adv Mash-ups
Sustainment
SPARQL Federation
6/30
12/10
DWiz DoD DCMO BMA CTO
& CA
9/12
33
Status
3/22/10
DWiz DoD DCMO BMA CTO & CA
34
Backend PoD1 Architecture
S3
S4
Target
Database
DIMHRS
Objectives Achieved:
D
M
Firewall
D
C
Web Service
DKO CAC Authentication
Data Virtualization
ETL Process
DMDC MOU
P&R HR Ontology Models
DIMHRS Reuse
Data Virt
ETL
S1
S2
App
Server
Ab Initio
Server
Composite
Server
DMZ
App
Server
Proxy
Server
HTTPS Port 443 for web traffic
SOAP/XML
XML File
Web Service Call (bind)
DKO
EIW POD: Transition
Voluntary Retirement
HTTPS
Port 443 open for web
traffic to DMDC
(1/1/2008 – 11/1/2009)*
HTML
3/22/10
DWiz DoD DCMO BMA CTO & CA
35
EIW Operational Governance
Screen dump of Knoodle/M30
3/22/10
36
DWiz DoD DCMO BMA CTO & CA
36
Agile, Adaptive, Net-Centric
Stove Pipes
Tiered
Accountability
Global Collaboration
Service
providers
Contractors
In DoD
Allies
Was
3/22/10
IS
DWiz DoD DCMO BMA CTO & CA
“To Be”
37
All of the pieces together!
Topic is identified
Agreement?
Referral from
BECCM COI
merge
HR
Data Store
Send Issue to
BECCM COI
BECCM
HR
Data Store
HR
Data Store
Enterprise-level
Decision
3.0 Oversight
Decision
Enterprise-level
Decision
DCMO
DoDI Personnel
Data Store
Common Vocabulary
Who will work
on Issue?
2.0 Assess
Issue
7.0 Discuss
Recommendation
BECCM Mediation
Receive Issue
from COI
COI
WG
Yes
Approved?
4.0 Formulate
Scope and
Guidance
Enterprise-level
Decision
5.0 Designate
SMEs
Send Issue to
COI
WG
BECCM Consensus Process
8.0 Update all
appropriate
Documents
Yes
No
Enterprise Data
Issue Notification
DCMO/PSA
Domain COI/PSA
Data Presentation
1.0 Common
Vocabulary
Process
No
6.0 BECCM WG
Process
Data
Store
Data
Store
Data
Store
Data
Store
Governance Processes
Composite
Service
Primitives & Design Patterns
Infra-structure
Service
Interoperable and Federated
3/22/10
Bus
ine
ss
Ser
vic
e
Composite
Service
Bus
ine
ss
Ser
vic
e
Infra-structure
Service
Bus
ine
ss
Ser
vic
e
Infra-structure
Service
Bus
ine
ss
Ser
vic
e
Bus
ine
ss
Ser
vic
e
Infra-structure
Service
Bus
ine
ss
Ser
vic
e
Infra-structure
Service
Bus
ine
ss
Ser
vic
e
Services Layer
Bus
ine
ss
Ser
vic
e
Composite
Service
Infra-structure
Service
End-to-End Processes
DWiz DoD DCMO BMA CTO & CA
38
SAVE THE DATE ~ APRIL 21-22 2010
Hosted by Mr. Dennis Wisnosky
BMA Chief Technical Officer &
Chief Architect, OSD DCMO
Sheraton Crystal City Hotel
1800 Jefferson Davis Highway
In 2009, the DoD SOA Symposium demonstrated
that SOA must be considered a Team Sport,
involving all elements of people, process,
technology and especially Trust. This 2nd Annual
DoD SOA Symposium is focused on the Discipline
necessary within each individual team member and
the team as a whole to be successful. It will provide
Government and Industry professionals with the
experiences of individual and team’s successes that
are a result of best practice strategies for business
intelligence, program management, information
access, Discipline, and much more.
http://www.soasymposium.com
Featuring
Thank you!
Questions?
Dennis.Wisnosky@osd.mil
Backup
3/22/10
DWiz DoD DCMO BMA CTO & CA
41
Where Else Being Done?
 eSpace
– Traditional EII technology (i.e. MetaMatrix RedHat, Composite, Ab Initio,
etc.) providing real-time integration of signal intelligence data
• RDF-like virtual layer to provide user-driven analytical capability
 DCGS
– RDF Warehouse (i.e. Oracle, Mulgara, etc.) to provide scalable integrated
access to tactical intelligence data
• Context-driven analysis
• Semantic Wiki for user information input
• Warehouse loaded from traditional databases, web services, and
document entity extraction tools
 VISION
– Joint federated SOA based on common vocabulary translation and
formal business process modeling and execution.
 Others Include
3/22/10
–
–
–
–
–
–
–
NIH
DIA
AF EVT & TIPT
BBC
Essential Open Source Project
Univ of Texas M.D. Anderson Cancer Center
DWiz DoD DCMO BMA CTO & CA
Chevron
42
Ontologies
“A formal, explicit specification of a shared conceptualization”
- Wikipedia
 An ontology is a machine-readable description of a
domain
– Model: Information model, Metadata model, Logical
model
– Vocabulary
 Defines classes, properties, and instances which
exist in the domain and the relationships between
them
– What types of things exist? Classes
– What types of relationships exist between things?
Properties
– What is the meaning of a given term? Relationships
between Classes and Properties
3/22/10
DWiz DoD DCMO BMA CTO & CA
43
RDF (Resource Description Framework)
“The Resource Description Framework (RDF) is a language for
representing information about resources in the World Wide Web.”
W3C RDF Primer
– RDF enables the description of things (resources) in the form
of graphs
– Each RDF statement (triple) consists of 3 parts: subject,
predicate, object
– A triple forms a node-edge-node structure in a graph
– No schema necessary to describe things
– Subject – Predicate – Object is the only schema
Predicate
Format:
Subject
Example:
Mike has brown hair
Mike
hairColor
Object
Brown
Translation
3/22/10
DWiz DoD DCMO BMA CTO & CA
44