1. Delivering an Information Advantage
Architecture Policy, Processes and Tools
Integrated EA Conference 2009
Brian Wilczynski
Director
Enterprise Architecture and Standards
Office of the DoD Deputy Chief Information Officer

2. DoD CIO IM/IT Strategic Plan Delivering an Information Advantage
Vision
Lead The DoD Enterprise To Achieve An Information Advantage For Our People And Mission Partners
Mission
Lead the information age transformation to enhance the Department of Defense’s effectiveness and efficiency
Strategic End
An agile enterprise empowered by access to and sharing of timely and trusted information 2

3. Integrated Enterprise Architecture
VERSION 15
3/25/ :44
Integrated Enterprise Architecture
Architecture Policy/Mandates
“Develop, maintain, and facilitate the
implementation of a sound and integrated
IT architecture for the executive agency” – Clinger-Cohen Act
Office of Management and Budget Circular A-130
“Management of Federal Information Resources”
DoD Directive
“ASD NII / DoD CIO”
DoD Directive
“Management of the DoD Information Enterprise”
NAF
FJAWG
Federation Strategy
Reference Model Maintenance Process
SD-106 Policy Documents
DoD Directive 8210.x
“Architecture in the Department of Defense”
Defense Acquisition System
Interoperability and Supportability
Joint Capability Integration 3 3

4. Enterprise Architecture & Standards Supporting the CIO Mission
Lead The DoD Enterprise To Achieve An Information Advantage For Our People And Mission Partners
CIO Vision &
Mission
Net-Centric Transformation
Information as a Strategic Asset
Interoperable Infrastructure
CIO Strategic
Goals
Return on Investment
IT Work Force Development
Assured Information Access
DoD Architecture Framework
v2.0 (DoDAF)
Federated Joint Architecture Working Group (FJAWG)
DoDD 8200
Architecture within DoD
DoD Architecture Registry System (DARS)
Core Enterprise Services to the Tactical Edge
DoDI 8210.xx
Architecting DoD Enterprise
DoDM 8210.xx
DoD Architecture Federation
DoD Information Enterprise Architecture v1.1
International Defense Enterprise Architecture Specification (IDEAS)
Initiatives
Outreach
EA Conferences * Summit * Vendors * DKO
Maritime Domain Awareness
DoD Architecture Strategy 4

5. Delivering an Information Advantage
Architectural and Decision Making Processes
Joint
Capabilities
Integration and
Development
(JCIDS)
IT Architectures
are required and are
essential parts of each decision-making process
DEFINE
CJCSI C, CJCSM
Define the Force and
Force Capabilities
Planning
Programming
Budgeting
Execution
(PPBE)
Defense
Acquisition
BUILD
DODD ,
DODI
BUILD
DODD ,
DODI
Acquire and Equip
the Force and
Force Capabilities
Allocate Resources for
the Force and
Force Capabilities
Interoperability and
Supportability
Assess and Certify System Interoperability
DODD , DODI , CJCSI E 5 5

6. Delivering an Information Advantage
Provide an Integrated Compliance Toolset
DARS
Federated Catalog
Data Sources
DoDAF
MetaModel (DM2)
Tuple Type
Tuple Type
Federal &
Local Govt
Obj Exchg
Exchange
Specification
DoD
Data
Tags
DoDAF
FEA
Web Services
OO / UML, UPDM, IDEF
Coalition
XML, XMI
Tools
USAF
DISR
Databases
ARMY
NAVY
IDEAS
JCME
(JFCOM)
USMC
DITPR
FSAM
E-ISP
VUE-IT
External
Data Standards
Data Mining
Exchange Standards
Modeling Tools 6

7. “Fit for Purpose” Architecture Descriptions

8. DoDAF 2.0 Viewpoints Capability Viewpoint Operational Viewpoint
VERSION 15
3/25/ :44
DoDAF 2.0 Viewpoints
Overarching aspects of architecture context that relate to all views
All Viewpoint
Articulate the data relationships and alignment structures in the architecture content
Data and Information Viewpoint
Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts
Standards Viewpoint
Systems Viewpoint
Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions
Services Viewpoint
Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions
Operational Viewpoint
Articulate operational scenarios, processes, activities & requirements
Capability Viewpoint
Articulate the capability requirement, delivery timing, and deployed capability
Describes the relationships between operational and capability requirements and the various projects being implemented; Details dependencies between capability management and the Defense Acquisition System process.
Project Viewpoint CT 8 8

9. DoDAF Metamodel (DM2) 9

11. IEA Priorities
Data and Services Deployment (DSD) – Decouple data and services from the applications and systems that provide them, allowing them to be visible, accessible, understandable and trusted. Lay the foundation for moving the DoD to a Service-Oriented Architecture (SOA).
Secured Availability (SA) – Ensure data and services are secured and trusted across DoD. Allow users to discover data and services and access them based upon their authorization.
Computing Infrastructure Readiness (CIR) – Provide the necessary computing infrastructure and related services to allow the DoD to dynamically respond to computing needs and to balance loads across the infrastructure.
Communications Readiness (CR) – Ensure that an evolvable transport infrastructure is in place that provides adequate bandwidth and end-to-end, seamless net-centric communications capability across all GIG assets.
NetOps Agility (NOA) – Enable the continuous ability to easily access, manipulate, manage and share any information, from any location at any time.

12. DoD Architecture Federation
DoD Enterprise Architecture
Tools
Ref Models
Tech Stds
Arch Guidance
Laws, Regs, and Policy
DITPR
DoD EA RM
DISR
DODAF
Laws
Regs
Policy
Force Application
TAMD
Building Partnerships
BEA
Joint Capability Areas
Command & Control
GLOBAL C2
JIAMDO C2
Net-centric
NC CPM Arch
IEA
GIG IA Architecture
Battlespace Awareness
Protection
Logistics
RP&ILM
MS&SM
JDDA-E
Force Support
HRM
HRM Architecture
Corporate Management & Support
WSLM FM
SOCOM
DISA
DLA
NSA
NRO
NGA
DIA
Other
Dept of Army
Dept of Navy
Dept of Air Force
Army
Architecture
DON
Architecture
Air Force
Architecture
Solution Architectures

13. Lessons Learned
Architecture must be a senior-level leadership priority.
Architecture becomes relevant when it is integrated into the major decision-making processes of an organization.
Architecture needs to be described within the terms of the consumer.
Complexity needs to be understood and managed.