department of defense enterprise information web...
Post on 07-May-2018
220 Views
Preview:
TRANSCRIPT
Bottom Line Up-Front (BLUF)
The Enterprise Information Web (EIW) is pioneering the adoption of Semantic Technology and approaches that can be the way forward for enterprise business intelligence and solution architectures in the DoD.
March 2012 2Jonathan Underly ‐ EIW PM
Ontology – Based Information Integration & Analytics
March 2012 3
HR Dataset
What Pay Grade is Col. Blatt?
Graph1
hasNameEducation Institution
Pay Grade
O6
Col. E.J. Blatt
hasName
Central High School
hasName
person
University Michigan
Defense Acquisition U.
Jonathan Underly ‐ EIW PM
Ontology – Based Information Integration & Analytics
March 2012 4
How much Dwell Time does Col. Blatt have?
Graph2
person Dwell Time
24 monthsCol. E.J. Blatt
Deployment History
hasDwellTimeStatus
Jonathan Underly ‐ EIW PM
Ontology – Based Information Integration & Analytics
March 2012 5
Graph3Who has a Pay Grade of “O6” and has at least 24 months of Dwell Time?
HR Dataset hasName
Education Institution
Pay Grade
O6
Col. E.J. Blatt
hasName
Central High School
hasName
person
University Michigan
Defense Acquisition U.
Dwell Time
24 monthsCol. E.J. Blatt
Deployment History
hasDwellTimeStatusperson
Jonathan Underly ‐ EIW PM
A Vision for DoD Solution Architectures
March 2012 6
Business Enterprise Architecture (BEA)
Query BEA directly:Enterprise
analytics
Compliance
IRB/portfolio
management
DoD EA
HR Domain Vocabulary
Acq Domain Vocabulary
Log Domain Vocabulary
Fin Domain Vocabulary
Real Prop Domain Vocabulary
Svc Member OUID(GFMDI)(EDIPI)
Warfighter Domain Vocabulary
E2E BP executes via BEA directly
BP models uniformly described
OMG Primitives Conformance class
2.0
Data described in RDF Relationship described in OWLW3C Open Standards Legend: DoD Authoritative Data Source
User executes End‐to‐End Business Process
(E2E BP)
EIW is Currently in this domain
Jonathan Underly ‐ EIW PM
EIW History
March 2012 7
Post-DIMHRS Personnel Visibility Problem PersistsPersonnel Visibility Interoperability/Federation
DoD currently lacks the enterprise level capability to quickly and accurately account for personnel, manage troop strength, and
plan
Standards & transactional systems in constant state of change
Relationally-based architectures expensive to change/maintain
Problem: Personnel visibility (PV), accurate and timely pay Alternative: Build an enterprise ERP for HR functionality across DoD
Measure Outcome
Agility 10 year program, system did not pass Integration Testing and Acceptance Testing
Interoperability 100+ planned point‐to‐point interfaces to legacy systems; 1/3 successfully built and
tested
Savings >$$$$$$$$ spent, system not fielded
Jonathan Underly ‐ EIW PM
A New Approach to Information Visibility
March 2012 8
The Enterprise Information Web (EIW) is a mechanism for reaching into Authoritative Data Sources (ADS) to satisfy enterprise information needs. It accomplishes three things:
1. Reports near real‐time, authoritative information on‐demand
2. Supports enterprise information standards (Open, HRM ES, SFIS, Etc)
3. Supports IT flexibility/agility
Single viewMultiple Sources
Federation
DMDC Data Stores
Services Data
External Data
HR Data Store
HR Data Store
HRSource
HR Data Store
Common Vocabulary
HRSource
HRSource
HRSource
Aggregation
Jonathan Underly ‐ EIW PM
Enabling Strategic Management
9
Enterprise E2E and OSD
Policies
Operational Process and Service Policies
BEA Ontology Semantic Description
ADS
Strategic Objectives
4.0 Preserve and Enhance the All‐Volunteer Force
2.0 Support ContingencyBusiness Operations
4.2.10 Percentage of the Dept. AD who meet objectives for time deployed vs time at home
Army Dwell Time E2E USMC Dwell Time E2E
CII ODSECII ODSE
DoD Personnel Management E2E
Dwell Time
Who we are
March 2012 13
Intel Mission Area
Enterprise Information EnvironmentMission Area
Business Mission Area
Warfighter Mission Area
Missions of the DoD
TI&E
EIW
Jonathan Underly ‐ EIW PM
DoD Management Challenges
March 2012 14
Early Attempts at DoD Enterprise ArchitectureJonathan Underly ‐ EIW PM
DoD Architecture Progression
March 2012 15
Blueprinting BEA ‐ Stovepiped BEA ‐ Semantic
Core Business Mission (CBM) based; readable within CBM;not analyzable; not integrated with
solution architectures
End‐to‐End based; analyzable;
executable; integrated with & consumable by solution architectures
Branch office‐based; readable but not
analyzable; stovepiped
Jonathan Underly ‐ EIW PM
Courses of Action (COA) Considered
March 2012 17
COA Description Pro Con
Status quo Manual aggregation and gathering of information in
disparate systems
Process known Labor intensive (eg: daily JPERSTAT report consumes 70 person‐hrs); uncertain data
lineage
DIMHRS Single military personnel and pay system
Efficient; accurate DIMHRS not fielded; Political change curve
substantial
Traditional Warehouse
Set up a traditional network of data stores to pull and store personnel and pay related
information
Known model and technology stack
Duplicates data; costlyto develop & to
maintain; very costly to modify
SemanticApproach
Semantically describe personnel and pay information assets, pull,
aggregate and display (vice store)
Federated data = data lineage; powerful
analytics; virtual data (no duplication); easier to modify and maintain;
highly extensible
Maturing technology;Technology change
curve exists
Jonathan Underly ‐ EIW PM
EIW Benefits
March 2012 19
Interoperable Systems
Data Lineage Traceability
Compliance Assessment
Arbitrary Extensibility
Cross‐Service Analytics
Fact‐based Portfolio Analysis
Capability System Y/N
Leave PersPay1 Y
Leave PersPay2 Y
Leave PersPay3 N
Data Concept System Std
Airman Svc Mem Pers Sys
Soldier Svc Mem Pers Sys
Lawyer Svc Mem Pers Sys
RDF/ OWL
Common Language
Domain Ontology
Policy
Mapping Ontology
Source Ontology
Data
With this
Come These
Jonathan Underly ‐ EIW PM
21
EIW ROADMAP – PHASED APPROACH
LESSONS LEARNED
Ont
olog
y D
evel
opm
ent HR Ontology Development
HRM Enterprise Standards Modeling & Enterprise Analytical 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: Separations
ADS/BPA Modeling: Increment 5‐N
Legend: ADS/BPA = Authoritative Data Source/Business Process Area
We Are Here
Delivery Every 90 Days
ADS/BPA Modeling: Military Leave
Jonathan Underly ‐ EIW PM
ADS/BPA Modeling: “Member Profile”
RDF Modeling
RDF Triplestore
RDF Store Extension
SPARQL End‐points
Sparqlizer
Local Federation
Distributed Federation
RDF Modeling
PKI Enablement
Net Worthiness
ADS/BPA Modeling: Federated Ontology
PoD Progression
March 2012 22
Data Source: CII (USA)
Proxy Server
Dashboard
SQL
Source Mappings
AKO/DKO
DMDC
FirewallDMZ
HTTPS Port 443 for web traffic
Web Service Call
PoD 1:Models inform the location and extraction of data
Composite App Srvr
Ab Initio App Srvr Triple Store
SQL
RDF LoadTriple Store Loader(Semantic Mapping)
SPARQLSource Ontology
Web/App Server
POD2:• Model Driven
Analytics• 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
SQLSQL
CommonVocabulary
SPARQL
SPARQL
Domain Ontology
Mapping Ontology
Source Ontology
SPARQL
Domain Ontology
Mapping Ontology
SPARQL
SPARQL
SPARQL
SPARQL
Federator
DashboardGadget Gadget Gadget
SPARQLSPARQL External Data Source(s)
Gadget
PoD6:• Semantic Federation of local data• Aggregated Svc Member
Demographics• Open Social gadgets
SPARQLizer
PDA Metrics
SQLPoD 6.1 Extensibility and Reuse
• Enteprise Perform. Metrics Added• USMC MCTFS Mappings reused• NO changes to schemas or other
queries
PoD 7• Added Military Leave test data from all
services and DFAS• Dependent join for Federator• UI gadget development: model‐driven Uis• R2RML migration completed
PoD8• Added Navy dwell time data• BEA policy dashboards• PKI authentication
PoD9• Added Navy dwell time data• BEA policy dashboards• PKI authentication
Jonathan Underly ‐ EIW PM
EIW Alignment to DoD Information Priorities
March 2012 23
DoD Strategy Alignment Status
DoD Information Enterprise Strategic Plan
DoD and mission partners will obtain an information advantage when timely, secure and trusted information is available to all decision makers
EIW has demonstrated the capability to federate locally distributed data; currently working on dispersed distributed data sets
DoD Strategic Management Plan
Improve IT Acquisition Performance
Agile method to rapid capability deployment; Surfacing authoritative data in the H2R E2E BP; Exposed data to support SMP performance measure “Meet End‐Strength Goals”
DoD Net‐Centric Data Strategy
Visible, Accessible, Understandable, Trusted, Interoperable, Responsive
EIW enables all these goalssave Trusted, currently planned for PoD 8 & 9
Jonathan Underly ‐ EIW PM
March 2012 24
Executing Interrelated Processes 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
BP model accesses supporting data via BEA
(using SPARQL and R2RML)
LOG ADS built on Triple Store in Ohio
MCTFS built on relational DB in Virginia
BEA
Roster of Personnel with matching skill set to Manifest produced
Identity verified
Rules Ontology
BEA returns supporting data (using SPARQL and
R2RML)
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 = logisticsJonathan Underly ‐ EIW PM
EIW Ontology Architecture
March 2012 25
Domain Ontology
Mapping Ontology
Source Ontology
Data Source
Mapping Ontology
Source Ontology
Data Source
Machine readable policy with automated
lineage to the supporting source
data
Jonathan Underly ‐ EIW PM
The Root of PV: Information Federation
March 2012 26
HIRE TO RETIRE End‐to‐End
Army
AF
Navy
USMCDFAS
PV
JS; COCOMS; OSD
NSIPS
MILPDSeMILPO
Sailor
SoldierAirman
MCTFS
Marine
DJMS
Service Member
PV consists of many domains within
domains
Each Service is a domain. Each Service
fields its own applications and creates its own information to execute its mission
It is currently prohibitively expensive to federate and integrate applications within &
across domains
DoD will not solve PV problem until we solve the INFORMATION
FEDERATION problem
Jonathan Underly ‐ EIW PM
top related