United States Department of Defense Office of the Deputy Chief Management Officer Dennis E. Wisnosky Chief Architect & Chief Technical Officer Business.

<Insert Picture Here>

United States Department of DefenseOffice of the Deputy Chief Management Officer

Dennis E. WisnoskyChief Architect & Chief Technical OfficerBusiness Mission Area

OracleOracle Enterprise Architecture Enterprise ArchitectureOracleOracle Enterprise Architecture Enterprise ArchitectureOracle Enterprise Architecture

2 2

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

3 3

DoD Management Challenges

DWiz DoD DCMO BMA CTO & CA10/3/2011

Current Issues=Economic Imperative!

4 4

57% of DoD I.T. Costs are in Infrastructure

SOURCE: http://www.whitehouse.gov/omb/e-gov/

DoD Projects Have Own Data

DoD Contractors Build Separate

Infrastructures & DictionariesIssue:

Redundancy

Issue: Data

Issue: Infrastructure

DWiz DoD DCMO BMA CTO & CA10/3/2011 EA Mandated

5 5

Enterprise Architecture Mandated

OMB A-130Management 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

NDAA 2005 Title 10

USC Sec. 2222Accordingly, 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 & CA10/3/2011

6 6

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

7

HRM/ MedFM

LogisticsRPILMWSLM/MSSM

Strategy and Roadmap for DoD Business Operations Transformation

Performance Measures

Semantic Information

CV & Primitives

Past (BMA Federation Strategy version 2.4a)

Present(BOE Execution Roadmap)

BEA 3.0

BOE Vision

DCMO/CIO Policies

CIO – DIEA, Segment Archi.

Arch. Fed.

MDR

Federation Implementation Plan

CIO/DISA – Federal Cloud

BEA 8.x & Beyond

Business Intelligence

(BTI) NCES/CES

BOE Service Enablement

Domains

ExecutionDBSAE SOAImp. Strategy

Future(BMA Technical Transition Plan version 1)

Initial BOE Experience

DBSMC/IRBs DCMO/DCIO; EGB; BECCM

Version 2.4a

DoD Strategic Mgmt. Plan (SMP)

Common Vocabulary (Ontologies)

RDF OWL other

Enterprise Stds.

Vision & Strategy

Planning & Roadmap

Infrastructure

Governance

Data Integration

Biz. Intelligence

Rules/Workflow

Da

ta S

ha

ring

an

d

BI

En

ab

lem

en

t

Roadmap: Architecture Governance Socialization Services Infrastructure

Security

DWiz DoD DCMO BMA CTO & CA10/3/2011 7Vision for DoD Solution

Architectures

8

A Vision for DoD Solution Architectures

Query BEA directly:Acq Domain Vocabulary

HR Domain Vocabulary

Log Domain Vocabulary

Fin Domain Vocabulary

Real Prop Domain Vocabulary

Business Enterprise

Architecture: BEA

Airman Sailor

Svc Member

position

billet

OUIDdept

User executes BP

BP executes via BEA directly

Enterprise

analytics

Compliance

IRB/portfolio

management

BP models uniformly described

(GFMDI)(EDIPI)

DoD EA

SameAs

SameAs

SameAsSameAs

Warfighter Domain Vocabulary

SameAs

OMG Primitives Conformance class

2.0

10/3/2011 DWiz DoD DCMO BMA CTO & CA 8

Business Case - EIW

9 9

Department of Defense Enterprise Information Web (EIW)

DWiz DoD DCMO BMA CTO & CA10/3/2011

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)

PoD Progression

Data Source: CII (USA)

Proxy Server

Dashboard

SQL

Source Mappings

AKO/DKO

DMDC

Firewall

DMZ

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

CommonVocabulary

SPARQL

SPARQL

Domain Ontology

Mapping Ontology

Source Ontology

SPARQL

Domain Ontolog

y

Mapping Ontolog

y

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

SQL Extensibility and Reuse

•PDA Metrics Added•USMC MCTFS Mappings reused•NO changes to schemas or other queries 10DWiz DoD DCMO BMA CTO & CA10/3/2011 Dramatic Benefits

11 11

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

DWiz DoD DCMO BMA CTO & CA10/3/2011

12 12

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

13 13

DoD Architecture Progression

Blueprinting 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

Branch office-based; readable but not

analyzable; stovepiped

DWiz DoD DCMO BMA CTO & CA10/3/2011 Semantic BEA Roadmap

BEA

Tool

sEq

uipp

ing

the

Wor

kfor

ceG

uida

nce

3QFY11 4QFY11 1QFY12 2QFY12 3QFY12 4QFY12 1QFY13 2QFY13

BEA Technical Architecture Design

(TAD) Implement TAD (PfM)

Collaboration w/HR&PDA EIW Teams

NOTIONALSemantic BEA Roadmap

BEA 9.0

1st Draft BEA Ontology

1st Draft BEA Transition Plan

(BTP)

HR EIW Mapping Ontology

BEA 10.0

Mapping Ontology 8 Mapping Ontology 9 Mapping Ontology 10

BEA Baseline Ontology

Final BTP

BEA Threads/Compare RDF Data Layer

BEA Graphical Model GUI Phase I BEA Federated Secure

SPARQL Module BEA Reusable Semantic Toolkit

BEA Reusable Semantic Toolkit POD 1

BEA COOP Architecture Enterprise Failover/Scalability

Use of E2E Business Models & Ontology Memo

DoDI 8330 – BPMN Primitives Application Across the BMA

DoDI 8321 – Semantic Web Application Across the BMA

DoDI Business Enterprise Services Development and Implementation

Course Catalogue Complete

Courses Outlined and Storyboarded

Course Materials Finalized

Semantic Training Platform Stood up

BPMN Training Platform Stood up

Semantic & BPMN Training Offered

Semantic & BPMN Training Offered Semantic & BPMN

Training Offered

Semantic & BPMN Training Offered

Semantic & BPMN Training Offered

BEA 8.1BEA 8.2

BEA RDF Store

PfM Ontology

Final CM Process

Final BDM

2nd Draft BTP

Draft BDM

Draft CM Process

These capabilities will adjust based on

collaborative effortsCollaboration w/HR&PDA EIW Teams

DITPR & SNaPIT Mapping Ontologies

DIEA Mapping ontology

FM Mapping ontology

RPILM Mapping ontology

BEA eTools 2.0 Hosting Solution (wRDF Store)

DoD Business Operations Technical Transition Plan v0.99

14DWiz DoD DCMO BMA CTO & CA10/3/2011

Apr. 4 Memo

15 15

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

• 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 modelsDCMO Memo signed 4 April 2011

Subject: End-to-End (E2E) Business Models in the DoD Business Architecture Clear and Unambiguous

InstructionsDWiz DoD DCMO BMA CTO & CA10/3/2011 15

16 16

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

17 17

Our Technology Toolbox is Evolving

WILL EVOLVE TO TOOLS THAT…

PRODUCE & USE NON-PROPRIETARY, OPEN STANDARDS &

PROTOCOLS

DWiz DoD DCMO BMA CTO & CA10/3/2011

Model Driven Implementation

18 18

Model Driven Implementation

DWiz DoD DCMO BMA CTO & CA10/3/2011 Thank you!

19 19

Thank you!

Questions?

[email protected]

DWiz DoD DCMO BMA CTO & CA10/3/2011