TechNet Land Forces South

Transcription

1 TechNet Land Forces South Army Data Center Consolidation Plan (ADCCP) Overview COL Chris E. Miller MARCH Tucson, AZ Engagement Theater Session IV 28 March 2012/1600 hrs

2 Purpose To provide background on data center consolidation and the path which the Army is taking to meet Presidential Guidance and the Office of Management Budget s Federal Data Center Consolidation Initiative (FDCCI) while recognizing and adapting to processing realities in the field. 2

3 The Technology Dilemma We have to be better at being able to reach out, harness technology and get it into the hands of our soldiers quickly. GEN Peter W. Chiarelli, Former Vice Chief of Staff of the Army 5 March

4 Modernizing Army Systems the Army s sweeping network modernization effort, its number one priority in modernization, will require a fundamental cultural change Chief Information Officer CIO/G-6, LTG Susan S. Lawrence 4 4

5 Agenda Focusing on the End State Executive and Congressional Interest The Way Forward: Data Center Consolidation Application Rationalization Summary 5

6 Why Consolidate Our Data Centers? Presidential Memo 10 June 2010 Subject: Disposing of Unneeded Federal Real Estate Increasing Sales Proceeds, Cutting Operation Costs, and Improving Energy Efficiency Stop Expanding Data Centers in order to address the growth of data centers across the Federal Government, agencies shall immediately adopt a policy against expanding data centers beyond current levels, and shall develop plans to consolidate and significantly reduce data centers within 5 years. Agencies shall submit their plans to OMB for review by August 30,

7 Congressional Interest Limitations on Obligations of Funds (FY2012 NDAA Language) During the period beginning on the date of the enactment of this Act and ending on May 1, 2012, a department, agency, or component of the Department of Defense may not obligate funds for a data server farm or data center unless approved by the Chief Information Officer of the Department of Defense or the Chief Information Officer of a component of the Department to whom the Chief Information Officer of the Department has specifically delegated such approval authority. After May 1, 2012, a department, agency, or component of the Department may not obligate funds for a data center, or any information systems technology used therein, unless that obligation is in accordance with DOD wide performance plan required by the Act. Approvals for funding Prior to May 1, 2012 An approval of the obligation of funds may not be granted unless the official granting the approval determines, in writing, that existing resources of the agency, component, or element concerned cannot affordably or practically be used or modified to meet the requirements to be met through the obligation of funds. After May 1, 2012 An approval of the obligation of funds may not be granted unless the official granting the approval determines that: (1) existing resources of the Department do not meet the operation requirements to be met through the obligation of funds; and (2) the proposed obligation is in accordance with the performance standards and measures established by the Chief Information Officer of the Department in the DOD Performance Plans. Reports of Approvals Not later than 30 days after the end of each calendar quarter, each Chief Information Officer of a component of the Department who grants an approval based on the authority delegated by the Chief Information office of the Department during such calendar quarter shall submit to the Chief Information Officer of the Department a report on the approval or approvals so granted during such calendar quarter. Delegation of Authority memo is forthcoming. 7

8 The Magnitude of the Problem Over 435 Army data centers: Occupying more than 1.2 million square feet of floor space. Containing over 26,000 servers. Housing almost 9,000 racks (which, if placed side by side, would reach over 4 miles) Over 10,500 application records. And we know we don t know everything yet! As of 5 March

9 The Target for Data Center Closures Close 185 Army Data Center s by FY Data Centers by Category CAT 2 CAT 3 CAT 4 CAT 7 CAT 9 CAT 2: Sustain CAT 2 CAT 3 Close CAT 3 CAT 4: Deployed CAT OEF 4 CAT 7 CAT 7 Pending CAT 9 CAT 9 Recategorized Doing 1 task 185 times Close in FY FY11 FY12 FY13 FY14 FY15 Closed Series1 9

10 The Installation Approach To meet the Army's goal of 185 data center closures by FY2015, the CIO/G-6, NETCOM/9 th SC (A) and 7 th SC (T) have recommended taking an Installation Approach. The Installation Approach uses the Center of Excellence (CoE) Discovery teams more effectively by having them discover existing data center information including; capacity, facility, storage, network, and application level data on an installation concurrently, allowing commands to make more informed decisions to support a simultaneous, rapid collapse of the data centers on an installation. The Installation approach is not meant to move away from the command plans that were briefed at the ADCCP Summit in December 2011, or slow the pace of scheduled closures, but a means for our organizations to work together to best utilize resources and further the goals of data center consolidation. 10

11 Installation Approach Discovery Goals Across the installation, we are going to look at: Facility Infrastructure Utilized and Available Capacities Network and Storage Capacities Application level data Other Data Centers identified 11

12 Pre-Site Visit Prerequisites To be completed prior to Site Visit, Center of Excellence will coordinate with onsite POCs: High-level Installation Network Diagrams High-level individual data centers Network Diagrams Routers, switches and Firewalls Access Control Lists (ACL) Existing List of Network Management Systems(NMS) Review of current DISA topology 12

13 Onsite Discovery Activities Conduct Onsite In-Brief Representatives of all Commands with Data Centers on the Installation, Data Center Owners, IMCOM, DPW, Garrison Commander, HQDA CIO/G-6, and NETCOM Manual Data Collection (2 weeks) Physical Discovery Data Facility Condition, HVAC, Power, Cable Infrastructure, Floor/Rack Space, Network Connections, COOP, Physical Security, Environmental Factors, Technical support availability, Network traffic flows, Virtualization Services High Level Application Data: Functional Description, Technical High-Level Description, Storage Allocation, Ports and Protocols, High-Level Network Topology 13

14 Onsite Discovery Activities (cont d) Conduct Preliminary Analysis (1 week) Validation of tracking tool data Work with on-site experts to capture additional information required to support a recommendation for Installation Data Center Consolidation Identification of constraints/limitations with existing infrastructure Development of potential courses of action Conduct Onsite Out-Brief Representatives of all Commands with Data Centers on the Installation, Data Center Owners, IMCOM, DPW, Garrison Commander, HQDA CIO/G- 6, and NETCOM Will include a recommendation for Installation Data Center Consolidation Discussion of issues and challenges 14

15 Installation Approach: End State TRADOC FXXX_ST_TRA_02 NETCOM FXXX_ST_NEC_01 HQDA G3 FXXX_ST_HG3_01 TRADOC FXXX_ST_TRA_01 AMC FXXX_ST_AMC_01 AMC FXXX_ST_AMC_03 Single Installation Processing Node (Data Center) AMC FXXX_ST_AMC_02 ATEC FXXX_ST_ATC_01 15

16 Application Rationalization & Disposition Inventory BIN War Fighting Mission Area Business Mission Area Enterprise Information Mission Area Rationalize: Kill Retire Modernize Sustain Categorize ERP s SharePoint Exchange Mail MS Project Server AtHOC OCS RM Online Distance Learning ETC Manufacturing Syst C4IM Services Thin Client ETC AD Controllers Switches/Routers TLA DNS Servers IPS Print Servers SONET ETC Enterprise Servicing Applications Local Servicing Applications Local Servicing Infrastructure CBA Cost Utilization Architecture Bandwidth Risk Disposition Enterprise Servicing Applications CDAE DCCE MWR.COM.COM.ORG.EDU Consolidation Local Servicing Infrastructure White-Listed Apps 16

17 Rationalization and Categorization Timeline Task.5 Suspense 1. Rationalize Requirement: Identify each application as: kill, modernize, or sustain; and 2. Categorization Requirement: Identify each application as enterprise servicing or local servicing of Applications listed in the ADCCP Tracking Tool (C-1 List) which are hosted in data centers closing in FY Rationalize Requirement: Identify each application as: kill, modernize, or sustain; and 2. Categorization Requirement: Identify each application as enterprise servicing or local servicing of Applications listed in the ADCCP Tracking Tool (C-1 List) which are hosted in data centers closing in FY Rationalize Requirement: Identify each application as: kill, modernize, or sustain; and 2. Categorization Requirement: Identify each application as enterprise servicing or local servicing of Applications listed in the ADCCP Tracking Tool (C-1 List) which are hosted in data centers closing in FY Rationalize Requirement: Identify each application as: kill, modernize, or sustain; and 2. Categorization Requirement: Identify each application as enterprise servicing or local servicing of Applications listed in the ADCCP Tracking Tool (C-1 List) which are hosted in data centers closing in FY15. Complete Rationalization and Categorization of 100% Applications listed in the ADCCP Tacking Tool (C-1 List). 19 APR MAY MAY JUN JUN 2012 Notes: 1. The completion of Rationalization and Categorization is required for the Army s OMB report due to DOD in August. The elimination of applications is required to achieve the ADCCP efficiency goals. 17

18 Savings & Efficiencies Paths to Progress $ Software as a Service (SaaS) Platform as a Service (PaaS) Infrastructure as a Service (IaaS) $ Server Consolidation Cultural Change 18 18

19 The Paradigm Shift 19

20 Using ADCCP as the Path to the Cloud Infrastructure as a Service Platform as a Service Software as a Service DISA, Commercial, & IPN Hosting Enterprise Server Common Operating Environment Local applications Converted to Enterprise Applications 20

21 The Goal Army Application Hosting Transformation Application Hosting Business Management Army Common Operating Environments Application Portfolio Rationalization 21

22 Points of Contact CIO/G-6 ADCCP Team: COL Chris Miller/Mr. Neal Shelley/LTC Jeff Gribschaw (571) (703) (571) HQDA CIO/G-6 Cyber Directorate: Mr. William Biggs (703) Army Cyber Command: COL William Max Duggan (703) ADCCP Project Office (Software Engineering Center Support): Dan Andrew (443) ADCCP Links ADCCP Tracking Tool - ADCCP AKO Site: - ADCCP EXORD: MilboST: Closure Report Formats: 22