Enterprise Architecture

Transcription

1 Enterprise Architecture Management Plan DoD Conference 3 May 2012 Brian Wilczynski Director, Architecture & Interoperability Office of the DoD CIO brian.wilczynski@osd.mil

2 DoD Enterprise Business Warfighting g Intelligence Information Enterprise Army DON Air Force Dept of Air Force DIA NGA NRO NSA DLA DISA COC COMS Reference Models OMB F DARS Tools DITPR Tech Stds DISR Arch Guidance DODAF Laws, Regs, and Policy Laws Regs Policy 2

3 Reference Architecture Description Enterprise-wide Access to Network and Collaboration Services Reference Architecture Overview and Summary Information (AV-1) Strategic Purpose Principles Department of Defense Enterprise-wide Access to Network and Collaboration Services (NCS) Prepared by the Office of the DoD CIO Reference Architecture Version 3.0 December Architecture Product Identification 1.1 Name: Enterprise-wide Access to Network and Collaboration Services (NCS) 1.2 Lead Organization: Department of Defense Deputy Chief Information Officer. The Enterprise Services Review Group (ESRG), as the architecture owner, is responsible for architecture content and will provide overall coordination to ensure appropriate stakeholders and subject-matter experts are available; the Enterprise Reference Architecture Cell (ERAC), with oversight from the Architecture and Standards Review Group (ASRG), will support the development of appropriate architecture artifacts. 1.3 Approval Authority: DoD CIO Enterprise Guidance Board (EGB) 2 Purpose and Perspective 2.1 Purpose. A Reference Architecture (RA) abstracts and normalizes the institutional understanding of capabilities at the enterprise level, and provides a common set of principles, technical positions, and patterns for use within the DoD to guide development of Enterprise, Segment, or Solution architectures. AV-1 (Overview and Summary) OV-5a (Activity Decomposition) Vocabulary Patterns OV-1 (Concept Consumer & Provider) OV-6c (Event-Trace Description) AV-2 2(Integrated t Dictionary) OV-6a (Operational Rules Model) GROUP TYPE NAME Technical DESCRIPTION Positions OMB Policy M This guidance requires agencies to review new and existing electronic transactions to ensure that authentication processes provide the appropriate level of assurance. It establishes and describes four levels of identity assurance for electronic transactions requiring authentication. Assurance levels also provide a basis for assessing Credential Service Providers (CSPs) on behalf of Federal agencies. This document will assist agencies in determining their e- government needs. Agency business-process owners bear the primary responsibility to identify assurance levels and strategies for providing them. This responsibility extends to electronic authentication systems. OMB Policy M This memo requires the use of a shared service provider to mitigate the risk of commercial managed services for public key infrastructure (PKI) and electronic signatures. OMB Policy M This memorandum provides implementing instructions for HSPD-12 and FIPS-201. OMB Policy M This memorandum provides updated direction for the acquisition of products and services for the implementation of Homeland Security Presidential Directive-12 (HSPD-12) Policy for a Common Identification Standard for Federal Employees and Contractors and also provides status of implementation efforts. Presidential Policy HSPD-12 HSPD-12 calls for a mandatory, government- Directive wide standard for secure and reliable forms of ID issued by the federal government to its employees and employees of federal contractors for access to federally-controlled facilities and networks. NIST Guidance SP This document provides the organizational codes for federal agencies to establish the Federal Agency Smart Credential Number (FASC-N) that is required to be included in the FIPS 201 Card Holder Unique Identifier. SP is a companion document to FIPS 201. StdV-1 (Standards Profile) 3

4 Reference Architecture Enterprise-wide Access to Network & Collaboration Services RA (NCS RA) I Reference Architectures Brief Description Guides, standardizes, and enables the implementation of authentication and authorization capabilities to access collaboration services in support of secure information sharing across the Department. Remarks Approved Aug 2010 Active Directory Guides the transformation of legacy Windows networks that use AD Approved Feb 2011 Optimization RA (ADORA) to improve security, facilitate secure info sharing across networks, and achieve efficiencies through network consolidation. IT Infrastructure Optimization RA (ITIORA) Guides the optimization of the DoD IT Infrastructure with a focus on Defense ITIL services and management processes. Waiting Approval Core Data Center RA (CDC Defines & standardizes necessary attributes for Core DoD Under development; RA) computing Centers integrating DoD cloud and server virtualization Formal review planned concepts. for Mar-Apr 2012 Network Optimization RA (NORA) Unified Capabilities RA (UC RA) Future Mission Network RA (FMN RA) Guides the implementation of joint networks using network Under development; virtualization or federation techniques and leveraging regional Formal review planned boundary protection (TLA) concepts. for Mar-Apr 2012 Guides implementation and acquisition plans for phasing in voice and video over IP services, and other UC operating on converged networks. Analyzes services (C4 infrastructure and enterprise) required to support FMN, evaluate as is programs and initiatives ability to support these services, and develop DoD-level to be recommendations Under development; Formal review planned for Mar-Apr 2012 Under Development 4

5 CV-2: Capability Taxonomy 5

6 Reference Architecture DoD I 6

7 A Few Conference Themes What must architects respond to: Operational Context Interoperability Shared/Common infrastructure Joint Information Enterprise (JIE) Future Mission Network (FMN) Information/Data sharing Agility Mapping (MG Rudesheim) 7

8 MITRE Assessment Stakeholder interviews i conducted d in November 2011 Outbriefs conducted in December 2011 Follow on tasks include the development of an Management Plan Develop Enterprise Roadmaps 8

9 Summary of Stakeholder Comments from Interviews Approaches are largely driven from the bottom up Outcomes not clearly defined/prioritized More emphasis on the overall --- all Mission Areas Published RAs should be updated and require expansion in some technology areas In-work RAs are needed, but cultural and policy issues need to be considered along with technology Focus on transition plans Provide better capability to discover and share architecture content Establish an Agile Architecting ti methodology/approach h Focus on consolidation and interoperability 9

10 Drivers (Guiding Development and Use) Developing the Management Plan Federal DoD Program Framework Strategy, Strategy, Mandates, Mandates, Guidance Guidance Development Required Outcomes Management Plan Contents of the Management Plan Stakeholder and Use Analysis Development Process Architecture Framework and Patterns Governance Plan Communications Plan Metrics Workforce Today (As-Is) Time Phased Transition Future (To-Be) Repositories: Standards, etc. Use Requirements Programming, Planning, and Budgeting Acquisition Key Initiatives (e.g. IT Consolidation) Policy Compliance 10

11 Synchronizing Delivery of Solutions Common Situation - Uncoordinated Acquisition and Fielding Acquire FOC FIX Delivery Starts Acquire A Better Way - Integrated Roadmaps FOC Enterprise Mission Area and Component Architectures Integrated Requirements Coordinated Budgets Coordinated Contracting Coordinated Acquisition Integrated Fielding Coordinated Development, Delivery & Fielding Integrated Roadmaps Guide Joint Interoperable Solutions -- Faster and at Lower Cost 11

12 Federation - Managing the Seams DCMO Develop JS Develop USD (I) Develop & Approve & Approve & Approve Business Warfighting Intelligence Architecture Architecture Architecture DoD CIO CO Integrate Information Enterprise Architecture DoD CO CIO Develop & Approve Department Of The Army Department Of The Navy Department Of The Air Force Dept of Air Force DIA NGA NRO NSA DLA DISA COC COMS Components Align Reference Models OMB F DARS Tools DITPR Tech Stds DISR Arch Guidance DODAF Laws, Regs, and Policy Laws Regs Policy DoD CIO Provide 12

13 Enterprise Roadmaps Mission Owner s Products Based on Mission Processes Enterprise Product DoD Time Phased Transition Plan Capabilities Roadmaps JPR Systems Roadmaps coordinated and integrated yields Today (As-Is) Time Phased Transition Future (To-Be) Capability and system changes should be captured in enterprise roadmaps Roadmaps should be used to support decision making by: Providing executive view across capabilities and systems for senior leaders Identifying and tracking key decision points involving multiple capabilities and systems Supporting and reflecting enterprise level investment tradeoff decisions Mission Area and Component products are integrated into an enterprise roadmap by the DoD CIO to maximize re-use, interoperability, and investment management 13

14 Near-Term Strategy Complete I v2.0 and current Reference Architectures (RA) Pursue continued RA development in a decentralized manner Shift focus toward cross-mission Area integration managing g the seams Review current approach to governance and adjust to align with strategic objectives 14