Securing the Global Mission: Enabling Effective Information Sharing (DoD MPE-IS)
2 likes689 views
The document outlines the Mission Partner Environment Information System (MPE-IS), aimed at enhancing joint force adaptability and information sharing across various domains and geographic boundaries. It emphasizes the transition to virtualized capabilities for faster mission network creation, cost reduction, and alignment with mission partner systems like NATO's Federated Mission Networking. The future vision includes a standardized suite of services and automated federations, enhancing operational agility and cross-domain capabilities by FY24.
Securing the Global Mission: Enabling Effective Information Sharing (DoD MPE-IS)
- 1. 4/20/2017 May 26, 2015 Mission Partner Environment Information System (MPE-IS) “Globally integrated operations, increasing the overall adaptability of the force to cope with uncertainty, complexity and rapid change.” JF2020
- 2. 4/20/2017 Sharing Information with Mission Partners 2
- 3. 4/20/2017 Background • Capstone Concept for Joint Operations (CCJO): Joint Force 2020, 28 September 2012 “In this concept, Joint Force elements, globally postured, combine quickly with each other and mission partners to integrate capabilities fluidly across domains, echelons, geographic boundaries, and organizational affiliations.” • CJCS JIE White Paper, 22 January 2013 “JIE is critically important to achieving this vision” • DOD CIO, December 2014: “Let’s Accelerate MPE…” • 15-Star Memo to DOD CIO: “…Single MPE to be fully operational by FY16…”
- 4. 4/20/2017 MPE-IS SEC/REL Cloud Bottom-line Up Front (BLUF) • MPE-IS globally postures the Joint Force to swiftly form, evolve, dissolve and reform information-sharing environments across DOD and mission partners • MPE-IS simplifies and standardizes information sharing through virtualization technologies – Transitioning from physical to virtual capabilities enables rapid mission network creation – Standardization reduces hardware, software and labor costs to stand-up new mission networks – A shared suite of core services (e.g., email, chat, voice, VTC, etc.) – Provides a standardized suite of cybersecurity defense • MPE-IS aligns mission partner sharing to a common capability – Capitalizes and/or recapitalizes on existing mission partner systems and initiatives – Aligns with NATO’s Federated Mission Networking (FMN) capabilities – All Commercial Off-the-Shelf products 4
- 5. MPE-IS: The Future of C2 Networking 5 • Physically Separate Resources (Compute, Storage, & Network) • Variations in Software, Hardware, Security, etc. • No License or Infrastructure Sharing • Manually Intensive • Low Agility • Private Cloud Architecture • Mission Enclave networks are virtualized • Application Pooled Licenses across enclaves • Compute resources shared across enclaves • Storage resources pooled across enclaves • High Agility Current C2 Networks MPE-IS Cloud (Multiple Enclaves)
- 6. Shared MPE-IS MPE-IS SEC/REL Domain Vision Today: Regional & Physical – SIPRNET – Independent – Non-Standard Baselines – Mixed Security – Manual Federations – Type I Encryption Only – Labor-Intensive Standup – Thick Clients Only 6 FY18-24: Global & Virtual – Off-SIPRNET – Robust “Shared” Service Suite & Automated Federations – Standardized E2E Baseline – Approved Security – On-Demand Provisioning – CSfC with Some Type 1 – “Global” Fight-Tonight Capability Across All Domains – “Zero, Thin, MEC, & Mobile” Clients FY16-18: Regional & Virtual – Off-SIPRNET – “Shared” Basic Services & Manual Federations – Standardized Virtual Data Center Baseline – Approved Security – Partial Automated Provisioning – Type 1 w/ Commercial Solutions for Classified (CSfC) – “Regional” Fight-Tonight SEC/REL – Migration to “Zero, Thin, Multi-Enclave Client (MEC)” FY16: Email w/attachments, Chat, Voice, VTC, ISR (FMV), COP, Web/File Share, GAL, Office Automation, Print, Classification Tool (Available now) FY17+: OMS and Language Translation (Available Aug 17)
- 7. MPE-IS Target Architecture Single MPE-IS Node 7 MPE-IS Virtual Data Center MPE-IS Contingency Capacity MPE-IS Mission Enclave - F VDI Mission Specific Services Core Services (Email, Chat, VTC, VOIP) Support Services (ITSM, Office OA, Print) US Provided US User Mission Partner User US User Mission Partner Cross Domain Services MPE-IS Mission Enclave - B Mission Specific Services Core Services (Email, Chat, VTC, VOIP) Support Services (ITSM Office OA, Print) MPE-IS Mission Enclave – A Mission Specific Services Core Services (Email, Chat, VTC, VOIP) Support Services (ITSM office, OA, Print) US BICES-X MAC - D Core Services (Email, Chat, VTC, VOIP) US BICES-X MAC - C Core Services (Email, Chat, VTC, VOIP) C2, Logistics, Weather, etc US BICES US SIPR US BICES-X: TNE CD Transfer Services (chat, email) MLS File Share MPGW-X MPE-IS Mission Enclave - E VDI Mission Specific Services Core Services (Email, Chat, VTC, VOIP) Support Services (ITSM, Office OA, Print) Mission Partner Support Services Support Services US User Mission Partner User VDI VDI Mission Partner Thin, Thick, or Zero MEC, Thin, Thick, or Zero Thin, Thick, or Zero Thin, Thick, or Zero Thin, Thick, or Zero MEC, Thin, Thick, or Zero MEC, Thin, Thick, or Zero MEC, Thin, Thick, or Zero CMNT with CFSC and Type 1 MPGW-X • Global Resiliency (COOP) • Can Accommodate More than C2 (e.g. ISR)
- 8. 4/20/2017 Next Steps • Test MPE-IS Capabilities • Manage MPE-IS Development and Builds • Continue System Maturity • Rationalize and Converge Legacy Systems • Expand and Increase Commercialization 8