Transcript Oracle Enterprise Architecture Oracle Enterprise Architecture United States Department of Defense Office of the Deputy Chief Management Officer Dennis E.

Oracle
Enterprise
Architecture
Oracle Enterprise
Architecture
<Insert Picture Here>
United States Department of Defense
Office of the Deputy Chief Management Officer
Dennis E. Wisnosky
Chief Architect & Chief Technical Officer
Business Mission Area
Challenges Driving EA Thinking
• Describe the Basic Set of Challenges (Business
and Technical) that you started with
• What were the current state problems and who
were the stakeholders?
• Why did Enterprise Architecture become a
relevant approach or tool?
DoD Management Challenges
2
DoD Management Challenges
Current Issues=Economic Imperative!
10/3/2011
DWiz DoD DCMO BMA CTO & CA
3
57% of DoD I.T. Costs are in Infrastructure
Issue: Infrastructure
DoD Contractors Build
Separate
Infrastructures &
Dictionaries
SOURCE: http://www.whitehouse.gov/omb/e-gov/
Issue: Redundancy
DoD Projects Have Own Data
Issue: Data
10/3/2011
DWiz DoD DCMO BMA CTO & CA
EA Mandated
4
Enterprise Architecture Mandated
NDAA 2005 Title 10
USC Sec. 2222
OMB A-130
Management of Federal Information Resources
As part of the EA effort, agencies must use or
create an Enterprise Architecture Framework.
The Framework must document linkages
between mission needs, information content,
and information technology capabilities. The
Framework must also guide both strategic and
operational IRM planning.
http://www.whitehouse.gov/omb/circulars_a130_a130trans4
10/3/2011
Accordingly, Section 2222 of the FY 2005 NDAA
directed that the Department institutionalize
the BEA and provide Congress an enterprise
transition plan that details a schedule for
divesting legacy business systems and fielding
new enterprise solutions. Section 2222 also
established a new governance process for
business systems in the Defense Business
Systems Management Committee (DBSMC).
This senior board, chaired by the Deputy
Secretary, certifies that each new business
system investment of more than $1 million is
both compliant with the BEA, and is needed to
support a priority national security capability.
The scope of Section 2222 requirements was
later expanded as part of the FY 2010 NDAA
to ensure that appropriate Business Process
Reengineering occur for each defense
business system investment.
http://dcmo.defense.gov/history.html
DWiz DoD DCMO BMA CTO & CA
5
Future-State Architecture Vision
• What was the overall Enterprise Architecture
vision established for your IT organization
• What was the business case for realizing that
vision?
• What were the expected returns from that vision?
Strategy & Roadmap for DoD Bus. Ops. Transformation
6
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)
BEA 3.0
Performance Measures
CIO – DIEA, Segment Archi.
CV & Primitives
Initial
Arch. Fed.
BOE
Experience
Version
2.4a
MDR
Biz. Intelligence
Federation
Implementation
Plan
BOE Vision
Roadmap:
Architecture
Governance
Socialization
Services
Infrastructure
Vision & Strategy
Planning & Roadmap
Infrastructure
Governance
Data Integration
BOE Service
Enablement
Business Intelligence
10/3/2011
RDF
OWL
other
Rules/Workflow
Execution
DBSAE
SOA
Imp.
Strategy
(BTI) NCES/CES
DBSMC/IRBs
Enterprise
Stds.
Common Vocabulary
(Ontologies)
Domains
HRM/ Med
FM
Logistics
RPILM
WSLM/
MSSM
Semantic
Information
Data Sharing and
BI Enablement
DCMO/CIO Policies
BEA 8.x
& Beyond
Security
CIO/DISA – Federal Cloud
DCMO/DCIO;
VisionEGB;
for BECCM
DoD Solution Architectures
DWiz DoD DCMO BMA CTO & CA
7
7
A Vision for DoD Solution Architectures
User executes
BP
DoD EA
OMG Primitives
Conformance class
2.0
BP models
uniformly
described
BP executes via BEA directly
Query BEA directly:
Acq Domain
Vocabulary
Business Enterprise
Architecture: BEA
 Enterprise
Warfighter Domain
Vocabulary
analytics
 Compliance
 IRB/portfolio
Real Prop Domain
Vocabulary
Log Domain
Vocabulary
management
Fin Domain
Vocabulary
(EDIPI)
Svc Member
W3C Open Standards Legend:
Data described in RDF
HR Domain
Vocabulary
(GFMDI)
OUID
Business Case
- EIW
DoD Authoritative Data Source
Relationship described in OWL
8
Department of Defense Enterprise
Information Web (EIW)
Bottom Line Up-Front (BLUF)
The DoD 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.
Proof of Delivery (PoDs)
10/3/2011
DWiz DoD DCMO BMA CTO & CA
9
PoD Progression
Web Service Call
PoD5:
Dashboard
• Access data from relational store at
AKO/DKO
Dashboard
Gadget
Gadget
SPARQL
HTTPS
Port 443 for web traffic
DMZSPARQL
Firewall
D
M
D
C
SPARQL
SPARQLizer
SPARQL
Source
Mappings
Proxy
Server
SPARQL
SPARQL
SPARQL
SQL
Data Source:
CII (USA)
SQL
SQL
SPARQL
Triple Store
SQL
Triple Store Loader
(Semantic
Mapping)
PDA Metrics
10/3/2011
DWiz DoD DCMO BMA CTO & CA
• Store
Model
Driven
and
PoD
1:query
Analytics
Common
multiple
test the
data
Models
inform
• Model Driven ETL
Vocabulary
location
and
sets in
a triple
• Triple Store
extraction
of data
store
Domain
Domain
Ontology
Ontology
SPARQLizer
MCTFS (USMC)
PoD4:
• Access
from support
relational
SPARQLizer
1.0data
release,
store at run
time using
SQL equivalent
commants
semantic
engine
Added Ad-hoc
& query
Faceted
Search
External
Data
• SPARQLizer alpha release
capability
POD2:
PoD3:
Source(s)
with D2RQ
mappings
More demographic
reports
SPARQL
Web/App Server
Source
Ontology
•
•
SPARQL
Federator
SQL
•
SPARQL
Composite
Ab Initio
App Srvr Data
SPARQLizer
Source:App Srvr
SQL
run time;
Gadget
Gadget
Mapping
Mapping
Ontology
Ontology
Source
PoD6:
Extensibility
and Reuse
Ontology
RDF Load
• Semantic
Federation
PDA Metrics
Added of local data
• Aggregated
SvcMappings
Member reused
USMC MCTFS
Demographics
• NO
changes to schemas or other
•Dramatic
Open SocialBenefits
gadgets
queries
10
Dramatic Benefits
• Visibility: pull & display (vice store!) enterprise information
directly from the authoritative data sources
• Agility: plug-and-play federated environment so new systems
or analytical needs can come online and go offline without
disrupting the overall environment
• Access: build federation into the solution
• Standards: leverage BPM and Semantic 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
authoritative data
RDF/ OWL
BPMN
10/3/2011
DWiz DoD DCMO BMA CTO & CA
11
Transformation Roadmap & Governance
• Key phase of transformation from capabilities that
are going to be enabled over time
• Project work streams in motion right now
• Program governance and steering
• Stakeholders and governing bodies
Architecture Progression
12
DoD Architecture Progression
Blueprinting
Branch office-based;
readable but not
analyzable;
stovepiped
10/3/2011
BEA - Stovepiped
BEA - Semantic
Business Mission-based;
readable within a
Business Mission;
not analyzable; not
integrated with solution
architectures
End-to-End based;
analyzable;
executable; integrated
with & consumable by
solution architectures
Semantic BEA Roadmap
DWiz DoD DCMO BMA CTO & CA
13
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
Draft CM
Process
Tools
BEA Technical
Architecture Design
(TAD) Implement TAD
(PfM)
10/3/2011
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
FM Mapping
ontology
PfM Ontology
DITPR & SNaPIT
Mapping
Ontologies
Final CM
Process
3QFY12
BEA 8.2 HR EIW Mapping
Ontology
DIEA Mapping
ontology
BEA 8.1
Final BTP
BEA RDF
Store
Course Catalogue
Complete
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
Apr. 4 Memo
14
End-to-End (E2E) Business Models in the
DoD Business Architecture
• 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
DCMO Memo signed 4 April 2011
Subject: End-to-End (E2E) Business Models
in the DoD Business Architecture
10/3/2011
• 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
Clear and Unambiguous Instructions
DWiz DoD DCMO BMA CTO & CA
15
15
Lessons Learnt from your Experience
• Key lessons about how to practically and
effectively get an architecture program established
• Who are the key players for successful execution?
• What are good places to start?
• How do you keep the interest in architecture up
and sustained?
• How do you measure Transformation success?
Toolbox Must Change
16
Our Technology Toolbox is Evolving
WILL EVOLVE TO TOOLS
THAT…
PRODUCE & USE
NON-PROPRIETARY,
OPEN STANDARDS &
PROTOCOLS
Model Driven Implementation
10/3/2011
DWiz DoD DCMO BMA CTO & CA
17
Model Driven Implementation
10/3/2011
DWiz DoD DCMO BMA CTO & CA
Thank you!
18
Thank you!
Questions?
[email protected]
10/3/2011
DWiz DoD DCMO BMA CTO & CA
19