1015 DWiz_DCMO_EAConf_Wednesday_May_2

Transcription

DoD Enterprise Architecture
Conference
Bringing it all together!
May 2, 2012
Dennis E. Wisnosky
DoD BMA CTO & Chief Architect
DoD Semantic Technology Clip
Department of Defense
DCMO CTO/CA
Missions
Mi
i
off th
the D
DoD
D
Warfighter
Business
Intel Mission
Mission Area Mission Area
Area
Enterprise Information Environment
Mission Area
Dennis E. Wisnosky, DoD BMA CTO &
Chief Architect in the Office of the
Deputy Chief Management Officer (DCMO)
Heading, Altitude, Airspeed!
DWiz DoD DCMO BMA CTO & CA
2
Semantic Web: Heading, Altitude and Airspeed
I don’t want BIG DATA!
I want little data!
((near)) E
Exponential
i l
connections (n2 – n)
I wantt what
h t I want,
t
I want what I need,
I want to know it is right,
I want it when I need it.
(near) Linear connections (2n-1)
Force Directed Graph
The Journey!
3
The Need for Change in the 21st Century
“Pentagon Bureaucracy - It disrupts the defense of the United States
and places the lives of men and women in uniform at risk.
…..the
the Department of Defense will shift our focus and
our resources from bureaucracy to battlefield, from tail
to tooth.” SecDef, 10 Sept. 2001
Business Management
Modernization Program
2002 - BMMP and the BEA was to
drive-in cost accountabilityy
and drive-out redundancy.
This called for an Architecture
4
DoD Business Enterprise Architecture (BEA)
Progression
Blueprinting
Branch office-based;
readable
d bl b
but not
analyzable; stovepiped
BEA 1.0 – 2.4
“Boil the Ocean”
BEA - Stovepiped
Business Mission-based;;
readable within a Business
Mission;
not analyzable; not
BEA d3.0
- 9.0
i
integrated
with
i h solution
l i
“Prioritized”
architectures
BEA - Semantic
End-to-End based;
analyzable; executable;
federated with &
consumable
by solution
BEA
10.0 and
later
architectures
“Executable”
5
Strategy and Roadmap for DoD Business
Operations Transformation
Past
Present
Future
(BMA Federation Strategy version 2.4a)
(BOE Execution Roadmap)
(BMA Technical Transition Plan version 1)
DoD Strategic Mgmt. Plan (SMP)
DCMO/CIO Policies
BEA 3.0
P f
Performance
Measures
M
CIO – DIEA, Segment Archi.
CV & Primitives
Initial
Arch. Fed.
BOE
Experience
MDR
Biz. Intelligence
Federation
Implementation
Plan
BOE
Vision
2009
Roadmap:
Architecture
Governance
Socialization
Services
Infrastructure
Vision & Strategy
Planning & Roadmap
Infrastructure
Governance
BOE Service
Enablement
Common Vocabulary
(Ontologies)
Execution
Enterprise
Standards
RDF
OWL
SPARQL
other
Rules/Workflow
DCMO/CIO
SOA
Implement.
Strategy
(Business Infrastructure) NCES/CES
DBSMC/IRBs
Data Integration
Business Intelligence
Domains
HRM/ Med
FM
Logistics
RPILM
WSLM/
MSSM
Semantic Information
Data Sharingg and BI
Enablement
2005
BEA 9.x &
y
Beyond
Security
2012
ThirdCIO/DISA
time is
a charm!
– Federal
Cloud
DCMO/DCIO; EGB; BECCM
6
Transformation from DoDAF Products to
Data, all to answer Warfighter Needs
BEA 3.0
Past
(BMA Federation Strategy version 2.4a)
2005
BEA 3.0
BOE
Vision
GAO – “More was accomplished in 6 months
than in 4 years.”
We had to enable the
Architectures
7
Service Enablement for the Business
Operating Environment
Present
(BOE Execution Roadmap)
DCMO/CIO Policies
CIO – DIEA, Segment Archi.
CV & Primitives
Arch. Fed.
MDR
Biz. Intelligence
Federation
Implementation
Plan
2009
BOE Service
Enablement
Virtual Interactive Processing System (VIPS)
And then the data
8
Shared Understanding through Semantic
Technologies
Future
(BMA Technical Transition Plan version 1)
DoD Strategic Mgmt
Mgmt. Plan (SMP)
Semantic Information
Data Integration
Business Intelligence
Common Vocabulary
(Ontologies)
Data Sharing andd BI
Enablement
E
Performance Measures
Enterprise
Standards
Enterprise Information Web (EIW)
RDF
OWL
SPARQL
other
Rules/Workflow
BEA 9.x
9x&
Beyond
Security
2012
And Federation across the DoD
9
Federation and Compliance through
Semantic Architecture
Investment Review Board Investment
Review Board
Dashboards
iEHR EA Ont
VIPS Ont
Implemented by
IPPS Ont
HRM EA Ont
DIEA Ont
BEA O t
BEA Ont
Graph Stores (ADS)
Complies
to
Complies to
G
hS
Graph Stores (ADS)
iEHR Svcs Ont
Graph Stores (ADS)
Graph Stores (ADS)
Graph Stores (ADS)
Human Resources Management Enterprise Architecture (HRM EA) Process
Graph Stores (ADS)
Graph Stores (ADS)
Electronic Health Record Enterprise Architecture (iEHR EA)
Defense Information Enterprise Data
Architecture (DIEA)
Virtual Interactive Processing System Architecture (VIPS)
Service Integrated Personnel and Pay System Architecture (IPPS)
Process
Process
Business Enterprise Architecture: BEA
Data
Process
Data
Mapping Ont.
Process
Data
Data
Process
Process
Data
Data
Mapping Ont.
Mapping Ont.
Mapping Ont.
Mapping Ont.
Mapping Ont
Mapping Ont.
i
Mapping Ont.
Embedded in DoD Policy
Enterprise Architectures
iEHR Services Architecture
Solution Architectures
10
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.
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
o
o
o
o
o
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
Here comes the Deep Dive!
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
Benefits of OWL based Ontologies?
•
OWL is an industry standard to express Ontologies:
–
–
–
–
•
http://www.starlab.vub.ac.be/teachin
C
Contains
i a rich
i h set off constructs and
d ddata types
– g/Ontologies_Intr_Overv.pdf
Is extendable and provides a path for modular development & reuse
–
–
•
WC3 open specification
Support from Open Source and COTS tool vendors
Tools exist to create/visualize OWL files
files, and process OWL rules
Active growing community continues to submit new, rich, supporting
specifications/capabilities; i.e. R2ML, RIF, SPIN, RDFa, etc.
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 easilyy shared, makingg 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 goal of establishing DoD architectures that are people
readable, machine readable andOntologies
executable we need!
DCMO Foundational Ontologies Vision
Notional View of Foundational Ontologies
BPMN 2.0
BEA
DM2
H2R
P2P
Architecture Content through Standard Data Descriptions
Descriptions– Not Pictures
A Semantic BEA Built of Process/Activities, Semantic Data and Rules
Progress!
“With data, you can populate as many models as you need!”
Foundational Ontologies
Implementation
•
Phase I DCMO Ontology Architecture(DM2 2.02, BPMN 2.0, BEA 9.0)




•
Created DM2 v2.02 Ontology


•
•
DM2
Contains BPMN Analytic Conformance
BPMN 2.0 specifications used to create ontology
Plan to submit to OMG as an industry standard
BPMN-to-DM2
BEA (nonBPMN)
Created BPMN 2.0 to DM2 Mapping Ontology


Upper ontology to
all architecture
ontologies
Based on DM2 Logical
g
and Conceptual
p
Model
Replaced IDEAS constructs with OWL constructs
Created BMPN 2.0 Ontology



•
Ontologies created by Small Working Teams
DM2 Working Team (included representative from DM2 WG)
BPMN 2.0 Workingg Team; BEA Workingg Team
Groups consisted of diverse members; Engineering, Ontologist, SMEs,…
BPMN 2.0
BEA class
replacements
Query BEA on
DM2 or BPMN
terms
Maps some BPMN concepts and relationships to DM2 OWL
Mapping achieved via OWL sub-classing and chaining axioms
Created BEA Ontology


BEA Ov
Ov-6c
6c uses BPMN 2.0
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
Watch for DoDAF 2.03!
With DoDAF 2.03 the Architectural Basis is Set
• CIO and DCMO are collaborating on OWL based DM2 in DoDAF
2.03 package
An OWL semantic standards based alternative to the existing DM2
semantic framework that provides a means of achieving DoD CIO
goals for Federation and Net-centricity. At the same time
providing the foundation for achieving the DCMO semantic path
to Federation,
F d i andd the
h for
f basis
b i for
f complying
l i with
i h the
h DCMO
mandated standards approach.
Join us – Today at 5:30pm
Brickell/Flagler Ballroom
DoD CIO-DCMO Federation Pilot,
DM2 Ontology, & Semantics
And in real life!
15
Taking it out to the Warfighter
Now that we know we can make Authoritative Data accessible and
understandable for humans to analyze and machines to manipulate – we need
to take it out to the tactical edge.
We have shown we can discover and consume data to:
• Provide data analytics - EIW
• Solve Problems – IRB Support
To get it to the Warfighter in a form that is usable in his environment we need
to add:
•Sensory Awareness
•Who are you
•Where are you
•What do you want (in your own words)You have it in your pocket!
16
We have the technology now
Thi k Apple
Think
A l iPhone
iPh
Si i!!
Siri!!
ource: Tom Gruber, Inventor of Siri
ttp://www.tomgruber.org
Aroundme
Sky Map
Evi
View Graph Engineering Example!
17
The next phase – Getting EIW to the Warfighter
Voice -Recognition
T ti l - Edge
Tactical
Ed
Web Services
DoD EA
Ontologies
(OWL)
Event
Document
Analytics
Store
Store
Store
Alerting
Subsystem
Information Extraction and Automated Semantic Reasoning
CONUS
Data Accessor
Data Accessor
Data Accessor
Open Source Data
Mission Area Data
Sensor Data
• News Feeds
• Public Web Pages
• RSS
• Authoritative Data
Sources
• Mission Planning
• Intel
• Location/Time
• Accelerometer
xml csv
raw
I don’t want Big Data!
• Instrumentation
18
Meeting the Data Mandate for the Warfighter
“ f
“…..from
b
bureaucracy
to
t b
battlefield,
ttl fi ld from
f
t il to
tail
t ttooth”
th”
I don’t want BIG DATA!
I want my data!
I want what I want,
I want what I need,
I want to know it is right,
I want it when I need it.
Semantics relates unstructured data to structured,,
Semantics delivers the right structure,
Semantics reduces the Warfighter Information Overload.
Thank you!
19
Thank you!
Questions?
Dennis Wisnosky@osd mil
[email protected]
20
htt //d
http://dcmo.defense.gov
d f
21

1015 DWiz_DCMO_EAConf_Wednesday_May_2

Transcription

Similar documents

Presentation

A Common Vocabulary for SOA - Reducing Risk and Costs While

Present

Department of Defense (TRICARE)

HOW IT WORKS:

9th DoD/VA and Gov Health IT Post Summit Report

9300 Low Res.

An Introduction to ESF #8 Patient Movement

Navy advancement center announces enlisted examination answer