Meeting the Army’s Needs in a Joint Environment

1. Meeting the Army’s Needs in a Joint Environment HTTPS://WEST.ESPS.DISA.MIL/ECS

2. What is “Unified Capabilities?” A secure suite of communications and collaboration services available to the Soldier and Army business user on any trusted device, anywhere in the world. HTTPS://WEST.ESPS.DISA.MIL/ECS

3. A suite of services? OK. So, what’s in and what’s out? HTTPS://WEST.ESPS.DISA.MIL/ECS

4. Service Areas 10 Service Areas with over 50 Primary Capabilities Globally Accessible to all CAC Holders Utilizes same tools as tactical / deployed environments Standardizes enabling management capabilities Integrated services using single identity HTTPS://WEST.ESPS.DISA.MIL/ECS

5. What does UC do for me? • Today: Where do I find that document? • UC: Robust Content Management. Email, documents, voicemails, chat logs, and more are collected, categorized and searchable in the DoD Private Cloud. • Today: Why can’t I collaborate with my mission partners from Army, DoD, and other Services? • UC: Globally accessible by all CAC holders. Soldiers can connect with all 3.9 million DoD personnel. • Today: These tools are different from when I was deployed. • UC: Train as you fight. Soldiers use the same tools in garrison as deployed. • Today: Is this an official record? • UC: Built-In, Policy-Compliant Records Management. All records are automatically collected, sorted, and scheduled for disposition. • Today: My connection won’t support all these enterprise services! • UC: Infrastructure Modernization. The Army is funding infrastructure improvements at bases worldwide to support UC requirements. HTTPS://WEST.ESPS.DISA.MIL/ECS

6. Purpose & Agenda • Purpose: • Provide information on Army Unified Capabilities (UC) Vision and Portfolio • Layout program and approach • Agenda: • Army Unified Capabilities (UC) Portfolio • Army UC and the Joint Information Environment (JIE) • Transition Timeline • Functional Army Approach & Acquisition Oversight • Discussion HTTPS://WEST.ESPS.DISA.MIL/ECS

7. Army UC Portfolio A secure suite of communications and collaboration services available to the Soldier and Army business user on any trusted device, anywhere in the world. USER FACING ENABLING Find. Connect. Share. HTTPS://WEST.ESPS.DISA.MIL/ECS

8. Where does the portfolio come from? DoD Guidance: DODI 8100.04, Unified Capabilities Requirements (UCR), Unified Capabilities Master Plan (UC MP) Army Information Management (AIM) Requirements HTTPS://WEST.ESPS.DISA.MIL/ECS

9. DoD Unified Capabilities Requirements • Background • Technical / engineering view of UC Requirements • Most detailed for infrastructure and Voice over IP (VoIP) components • Highlights • Undergoing update from UCR 2008 Change 3 to UCR 2013 • Defines protocol and performance requirements for UC systems • Provides technical basis for UC Approved Products List (APL) testing and approval by the Joint Interoperability Test Command (JITC) Way Ahead • Updated UCR will be broken down into multiple documents, a framework and supporting detailed requirements • Provide Army comments NLT 16 JUL 2012 UCR 2008 Change 3 UCR 2013

10. Army Information Management (AIM) Requirements Management Plan (RMP) • Background • User-focused and collected requirements • CIO/G-6 to conduct the annual AIM Requirements review and facilitate BSIT validation to support future POM and CBA activities • Most detail for collaboration and communication requirements Way Ahead • Obtain approval for AIM RMP, AUG 12 • Execute Plan, 4QFY12 – FY13 Highlights • Describe and define the overall approach to managing future iterations of AIM Requirements AIM v.32 APR 2012 AIM 1.0 OCT 2012 • Conduct Elicitation Activities • ALARACT to solicit SIPR and new 1.0 requirements • CIO/G-6 SMEs to head focused reviews for capability areas to vet current and provide new requirements, MAY-JUN 12 HTTPS://WEST.ESPS.DISA.MIL/ECS

11. So how does Army UC fit into the Joint environment? Joint Information Environment (JIE) SHARE Foundational Services & Applications HTTPS://WEST.ESPS.DISA.MIL/ECS

12. Joint Information Enterprise End State • Objective: • Improve mission effectiveness • Improved cyber security • IT efficiencies Deployed Environment Mission Applications Data Computing “Enterprise Information Environment” Coalition Forces DCO Enterprise Email Close Combat TM AFATDS APEX Data AT21 Computing iEHR Navy ERP Airman Fundamentals Defense Travel Applications “Enterprise Information Environment” ?? Mobile (TDY/Deploy) Future devices Work Home Access at the Point of Need

14. Joint Information Enterprise End State From Stovepipes to Enterprise From Unique to Common From Local to Global From Proprietary to Open From Huge to Modular From Inaccessible to Interoperable From Disparate to Homogeneous From non Standard to Standardized From Vulnerable to Secure Coalition Forces Deployed Environment Mission Applications Data Computing “Enterprise Information Environment” Navy ERP APEX AFATDS Data DCO AT21 Computing iEHR Airman Fundamentals Enterprise Email Defense Travel Close Combat TM Applications “Enterprise Information Environment” ?? Mobile (TDY/Deploy) Future devices Work Home Access at the Point of Need

15. Army UC Supports JIE Share From Stovepipes to Enterprise From Unique to Common From Local to Global From Proprietary to Open From Huge to Modular From Inaccessible to Interoperable From Disparate to Homogeneous From non Standard to Standardized From Vulnerable to Secure HTTPS://WEST.ESPS.DISA.MIL/ECS

16. UC Portfolio - Today A secure suite of communications and collaboration services available to the Soldier and Army business user on any trusted device, anywhere in the world. Find. Connect. Share. HTTPS://WEST.ESPS.DISA.MIL/ECS

17. Functional Approach Example:Enterprise Collaboration Services (ECS) Cyclical capabilities assessment process to meet the Army’s current and future needs Requirements Cost-Benefit Analysis • Army Information Management Requirements • v0.32, CAC-endorsed, NOV 2010 • ECS CBA • v1.1, DASA-CE validated, JUL 2011 • v2.0, DASA-CE validated, JAN 2012 Increment 1 Outcomes (FY12) • NIPRNet Business Portal • Internet-facing Portal • 100K Army users • OAA, Army Publishing Directorate “Content Management System “ to Enterprise Service • Begin AKO Transition Increment 2 (FY13-14) Army Governance • SIPRNet Business Portal • 1.4 Army Users • OAA, Army Publishing Directorate “Content Management System “ Upgrades Complete • Complete AKO Transition • ECS Concept of Operations • v1.0, APR 2011 • v2.0, ECS Tiger Team, JAN 2012 Resource Recovery • ECS Resource Recovery Plan • v1.0, APR 2012 Increment 3 (FY15) • Services funded through POM • Knowledge Management and Application Innovation Test and Validation • ECS Test and Validation Plan • v1.0, Use Cases FEB 2012 Execution • ECS Service Level Agreement • v1.0, APR 2012 HTTPS://WEST.ESPS.DISA.MIL/ECS

18. Army Enterprise Service & Infrastructure Acquisition - Oversight Structure Roles and Responsibilities • PEO-EIS • Acquisition Lead • CIO/G-6 • Functional Capability Manager for Business Systems Process BSIT Business Systems Information Technology Acquisition Strategy ASARC Army Systems Acquisition Review Council 16 April 2012 Acquisition Decision Memorandum 31 JUL 2012 Acquisition Strategy Draft for Staffing Purpose: Approval of Requirements Document and Cost Benefit Analysis OPR: CIO/G-6 Purpose: AEA Approval of Service and Infrastructure Acquisition Strategy OPR: PEO-EIS Purpose: Approve Acquisition Strategy and provide Acquisition Authority Decision OPR: PEO-EIS  Cost Review Board TBD, if needed ASARC 22 JUN 2012 3 Star 9-13 APR 2012 PEO/PM PEO/PM • Monitor Cost, Schedule, Performance Metrics in accordance with Acquisition Decision Memorandum (ADM) requirements • Service Level Agreement Validation • Completion of documentation consistent with Milestone Decision Authority (MDA) direction 2 Star 17 FEB 2012 • Acquisition Development • Acquisition Strategy • Establish Cost, Schedule, Performance Metrics • Once reqmt approved, finalize AcqStrat and begin working level review (4 wks) • Then formal staffing at DA (3 wks) • Acquisition Authority Decision • Approves Acquisition Strategy • Cost, Schedule, Performance • Monitoring Plan • Periodic Program Assessment Reviews • ASARC can follow (3 wks) after DASM review • ADM, formal approval, (3-4 wks) Army IT Council of Colonels 08 DEC 2011 DeputyforAcquisitionSystemsManagement 15 May 2012 • This review is conducted to assess the readiness to proceed to the ASARC • Once alternatives validated, AcqStrat approved and PA&E/G-8 attests to affordability, DASM review could follow in a month • Requirement Identification/Validation • Develop Analysis of Alternatives, Cost Benefit Analysis • Acquisition Strategy cannot be released until BSIT approval. Early Adopters 34 Army Activities with over 170,000 Army Early Adopters cannot transition until ADM is achieved.

19. Recap • Single suite of integrated services for communicating and collaborating from the tactical edge to the enterprise • Globally accessible to all CAC holders • Improved security model reducing cyber vulnerability • Faster, more resilient IT capability delivery • Modernizes Army P/C/S infrastructure to support enterprise services • Allows Army to leverage commercial best business practices • Aligned with JIE Share efforts • Follows new acquisition oversight process

20. Unified Capabilities (UC) Program Points of Contact Stay engaged! UNCLASSIFIED LANDWARNET 2011