Brian Wilczynski Director Enterprise Architecture and Standards Office of the DoD Deputy Chief Information Officer brian

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

2. DoD CIO IM/IT Strategic PlanDelivering 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 http://www.defenselink.mil/cio-nii/docs/DoDCIO_Strat_Plan.pdf

3. 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 5144.1 “ASD NII / DoD CIO” DoD Directive 8000.01 “Management of the DoD Information Enterprise” DoD Directive 8210.x “Architecture in the Department of Defense” Defense Acquisition System Interoperability and Supportability Joint Capability Integration 3

4. Enterprise Architecture & StandardsSupporting 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 DoDD 8200 Architecture within DoD DoD Architecture Framework v2.0 (DoDAF) Federated Joint Architecture Working Group (FJAWG) DoDI 8210.xx Architecting DoD Enterprise Core Enterprise Services to the Tactical Edge DoD Architecture Registry System (DARS) DoDM 8210.xx DoD Architecture Federation International Defense Enterprise Architecture Specification (IDEAS) DoD Information Enterprise Architecture v1.1 Initiatives DoD Architecture Strategy Maritime Domain Awareness Outreach EA Conferences * Summit * Vendors * DKO

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 3170.01C, CJCSM 3170.01 Define the Force and Force Capabilities Planning Programming Budgeting Execution (PPBE) Defense Acquisition BUILD DODD 5000.1, DODI 5000.2 BUILD DODD 7045.14, DODI 7045.7 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 4630.5, DODI 4630.8, CJCSI 6212.01E 5

6. USMC USAF JCME (JFCOM) NAVY 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 Web Services FEA DoDAF OO / UML, UPDM, IDEF Coalition XML, XMI Tools DISR Databases ARMY IDEAS FSAM E-ISP VUE-IT DITPR External Data Standards Exchange Standards Modeling Tools Data Mining

7. “Fit for Purpose” Architecture Descriptions

8. Capability Viewpoint Articulate the capability requirement, delivery timing, and deployed capability Operational Viewpoint Articulate operational scenarios, processes, activities & requirements Project Viewpoint 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. Standards Viewpoint Articulate applicable Operational, Business, Technical, and Industry policy, standards, guidance, constraints, and forecasts Data and Information Viewpoint Articulate the data relationships and alignment structures in the architecture content All Viewpoint Overarching aspects of architecture context that relate to all views Services Viewpoint Articulate the performers, activities, services, and their exchanges providing for, or supporting, DoD functions Systems Viewpoint Articulate the legacy systems or independent systems, their composition, interconnectivity, and context providing for, or supporting, DoD functions DoDAF 2.0 Viewpoints

9. DoDAF Metamodel (DM2)

10. www.defenselink.mil/cio-nii/sites/diea

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 NC CPM Arch Net-centric IEA Battlespace Awareness GIG IA Architecture Protection Logistics JDDA-E RP&ILM MS&SM Force Support HRM HRM Architecture Corporate Management & Support FM WSLM Dept of Army Dept of Navy Dept of Air Force SOCOM Other DIA NGA NRO NSA DLA DISA 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.