16 Oct 2008 CDR Phil Turner PEO C4I/PMW160

1. Programlogohere Program Executive Office Command, Control, Communications, Computers and Intelligence (PEO C4I) Bringing Commonality to Navy Afloat Networks: Consolidated Afloat Networks and Enterprise Services (CANES) 16 Oct 2008 CDR Phil Turner PEO C4I/PMW160 http//www.peoc4i.navy.mil/CANES Statement A: Approved for public release; distribution is unlimited (16 Oct)

2. Afloat C4I Network Status Multiple networks/C4I apps, with: Independent infrastructures Operating Systems Software Baselines Legacy Non-IP Interfaces Hardware, Software Vendors Inefficient use of server and storage resources: 15-20% average Backbone networks are maxed out No enterprise network management or required security tools Fielding plan alignment is major issue Does not support DoD direction on SOA, Security Dozens of networks, each requiring dedicated support 2

3. Fleet Priority Requirements Increased Computing Capability Enhanced Security posture for afloat networks Keep pace with network technology refresh requirements Break perpetual cycle of COTS obsolescence Cross-domain mission information support - “single pane of glass” Reduced Shipboard Footprint Reduced number of installs (50+ on CVN) Dynamic sharing of storage and process - more efficient use of computing power Improved system management Enable mission flexibility across multiple applications Greater installation efficiencies CVN Secret Enclave ISNS, NITES, GCCS-M, DCGS-N, TBMCS, NAVMACS “If my networks go down during Fleet operations, I immediately issue a CAT IV CASREP.” “It takes a minimum of 24 hours to fully recover from an hour’s worth of outage on any of my networks. This is unacceptable and does not support my operational needs.” CO, USS Theodore Roosevelt 3

4. OPNAV PR09 Investment Review C4I acquisition strategy limits Navy’s ability to gain ROI, rapidly respond to emerging capability requirements Shipboard network funding not aligned to meet Fleet requirements Each program fully funds its computing infrastructure to meet requirements Results in duplication and limited integration across product lines Funding too scattered to provide acceptable ROI Industry has demonstrated key technologies and business strategies to reduce costs and increase capability “On my watch… we will get a handle on IT spending” ADM Roughead, CNO-Feb 2008 OPNAV reallocated $2.3B in PR09 to implement revised approach 4

5. Navy C4I Mandate • CANES Concept – OPNAV N6/DoN CIO, NNWC, and PEO C4I • CNO-directed approach to consolidate multiple afloat networks, provide • secure, reliable common hosting for multiple C4I applications • Technical and programmatic realignment of legacy • infrastructure and services-more efficient, additional capability • CANES Program (FY11 LRIP) • Consolidated afloat network, providing • CCE, Afloat Core Services, CDS, and integrated • Voice, Video, and Data network infrastructure • to 200+ ships and MHQ/MOC • Pre–MDAP/MAIS, projected ACAT 1D CANES Migration (FY08-11) Prototype CCE & ACS technologies – accelerate capability delivery, mitigate technical risks Existing Network POR Modifications to support early C4I application migration LINCOLN SG and CPF MHQ/MOC in 09 CCE: Common Computing Environment CDS: Cross Domain Solution ACS: Afloat Core Services Today By FY11: CCE/CDS and ACS CANES concept, investment strategy reviewed by Navy and DoD leadership EXCOMM May 07, DASN C4I Jun 07, USD(I) Sep 07, CNO Jan 08, ASD(NII)/USD(AT&L) Oct 08 5

6. CANES CANES CANES CANES Part of Overall Navy Approach to C4ISR • Architecture: Provides common services & infrastructure • Consolidated Afloat Network Enterprise Services (CANES) • Next Generation Enterprise Network (NGEN) • NCES • NECC (Future Joint C2 application) • Network Security NGEN Data Strategy: Ensures interoperability Increased bandwidth / throughput + CANES • Governance: • Enables all of the above • Generates liquidity for greater agility BASE • Rapid Capability Development: • MHQ-MOC capabilities • MDA capabilities • Coalition connectivity • Information Ops SPAWAR MHQ/ MOC IMA FISC TRNG CEN “…suspect cargo” NCDOC

7. Fundamental Change in C4I Portfolio Management Current C4I Apps Future C4I Apps + CANES • NAVSSI • NG2CP • NIAPS • NITES • NTCSS • OOMA • SSEE INC F • TBMCS • TMIP • TRIM • USW-DSS • WEBSKED • others • AIS • CFn • CND • CNI • DCGS-N • DIOS • FAS/CAS • GCCS-M • IONAS • JMPS • JSS • MEDAL 34 C4I Apps will depend on CANES to deliver network infrastructure: Cornerstone of PEO C4I’s Synchronized Fielding Plan

8. 1995 1999 2001 2006 2007 2011 MAIS Review Council Authorized Optimization of NTCSS Apps BPI plan - OOMA Development Began FOC Fielding Decision Multiple DT/OT Events 1999 2004 2005 2009 ORD OPEVAL Full-Rate Production FOC Jul 05 Jun 06 Apr 08 QRA #1 MS C CNO Guidance Ph-1/2A Fielding Facilitating C4I ApplicationsSpeed to Capability • OOMA • Client-Server • Multiple Tests/Certs • ACAT I Program • GCCS-M 4.0 • Client-Server • Multiple Tests/Certs • Interdependencies Rapid • AIS • RDC Approach • Reused ONR Software • Initial Delivery < 2 Years Capability Feb 06 Jul 06 Oct 06 • MDA DS COI • Initial Delivery < 5 Mths • Less Than $500k • Accessible Via Browser Insertion MDA DS COI Standup Start RDC MDA DS Prototype Spiral 1

9. FY08 Apr Apr Oct Oct Jan Jan July July Successful application integration requires detailed technical effort across PEOs ISNS Test Events CCE Specification CCE Delivery to IWS Blade Allocation Ship Rack Run Time Env Load SOA Specification SOA (with licenses) Beta 1 Beta 2 Ship Install Drawing for Review SSAA Procedures for ISNS Apps ISNS Sys Int Test USW DSS Test Events B2P Lab Integration @ Progeny SOA Int & Test TWO8 LOE (w SOA) TW08 (w SOA) B2 Lab Integration and String Testing ISNS Int & Test System V&V DT/OA Installation • USW-DSS identified in 2007 as high priority Early Adopter for CANES • Fielding Plan Alignment • Detailed Technical Interchanges • MOA signed between PEO C4I and PEO IWS to implement • 18 month effort to support LIN SG in 09

10. ISNS/SCI Early Adopters (EA)and the Migration to CANES FY 06 FY 07 FY 08 FY 09 FY 10 FY 11 FY 12 FY 13 FY 20 Lincoln Strike Group and CPF MOC SIT I COMPOSE CND NTCSS DMS Proxy OOMA GCCS-M ARRS NITES JMPS-E JMPS TMIP-M JSS AIS NIAPS ERMS MEDAL CFn SIT II ACS SIT III DCGS-N USW-DSS I II III Stand alone HW environments Common Computing Environment CANES LRIP CANES Independent SOA environments Common Afloat Core Services SIT Dates SIT I: 5/4/08 – 6/30/08 SIT II: 10/08 – 12/08 SIT III: 1/09 – 3/09 ISNS Inc 1/SCI CANES Application migration already underway via the EA effort - provides Process, Governance, Engineering lessons learned – critical risk reduction for CANES

11. C4ISR Acquisition Landscape • Pending DoDI 5000.02 release • Keep programs prior to MS B longer • Competitive Prototyping • Greater interaction with industry • Earlier review of programs (MDD, MS A) • OSD and OSD concern over technical readiness and cost control issues • Perceived SOA technical risks • POM10, budget pressures, transition

12. Overall Program Approach FY08 FY09 FY10 FY11 FY12 FY13 FY14 FY15 MDD MS B MS C LRIP FRP MDD MS B SDD MS C 12

13. Acquisition Roadmap ISNS Increment 2 ADM (Pre acq activities) Nov 06 PEO C4I Acquisition Coordination Team (ACT) Mar 07 DASN C4I, PMW 160 ACT Sep 07 ASD (NII) MDAP/MAIS list released Dec 07 Gate 3 Review with CNO/VCNO Jan 08 CANES Program Element established May 08 USD(PA&E) AoA guidance approved Mar 08 USD (AT&L) MDAP list released May 08 USD/ASD Directors CANES Program Review (SES Level) Aug 08 CANES OSD Stakeholder Focused Issue Group (FIG) #1 Aug 08 CANES FIG #2 Sep 08 CANES Acquisition OIPT with OSD Senior Leadership Oct 08 Gate 4/5 Review with ASN (RDA) 7 Nov 08 Material Development Decision with USD (AT&L) Nov 08 13

14. Afloat Core Services (ACS) • ACS integration contract decoupled from SD contract • Due to nature of ACS as an emergent concept and architecture • Large number of PEO C4I and other COI applications and hardware interfaces that Afloat Core Services is anticipated to support • Avoid concurrent source selection efforts • Leverage lessons learned from NCES SOA contract • ACS contract provides CANES Core Services infrastructure to support application migration • ACS integration contractor responsible for integrating NCES and open standards compliant products into a CANES Afloat CS stack • Leveraging the “Adopt, Buy, Create” process and ongoing DoD level development work on Core Services • Core Services are a component of the overall system architecture and fundamentally a system application/enhancement • CS Version 1.0/1.5 provides an initial, technically mature core services stack- government will provide to the SD developer for incorporation into the network 14

15. NCES ARMY FCS AOC WS CANES ARMY SOA-F ARMY BCCS DCGS MCEITS NECC Multi-Service SOA Consortium Objective - Defining & Implementing the Joint Federated SOA SOA Interface Working Group Experimentation Working Group Architecture Working Group DCGS – Distributed Common Ground System; BCCS – Battle Command Common Services; AOC WS – Air Operations Center – Weapons System FCS –Future Combat Systems; MCEITS – Marine Corps Enterprise Information Technology Services; DoD SOA Approach Based on App and Infrastructure Programs Collaborating on Enterprise Service Standards, Protocols, Specifications, and Reference Implementations Reduces technical risk of Afloat Core Services 15

16. Increment 1 Contract Strategy Developed Functional Baseline & SDS Develop Solicitation FY09 FY11 FY08 FY10 MS C MDD MS B SRR SIT X2 OA X2 Government E2E Lab S Test X2 US TestX2 EVM baseline Oct 08 Release draft RFP and technical components of PR Vendor provided Allocated Baseline EDM Drop CA + 4 mo EDM Drop CA + 8 mo EDM Drop CA + 12 mo IOT&E FY12, FRP FY13 CANES System Developer 1 FY11 and 12 LRIP Installs Down-Select Draft RFP PEO /SSA Review RFP Process Source Selection PEO/SSA Review CANES System Developer 2 2 mo 1.5 mo 1.5 mo 9 mo 4 mo 14 mo Government Oversight Government Oversight Afloat CS development: ISNS INCR I Mod 5 ACS v1.0 ACSv1.5 ACSv2.0 CANES Afloat CS PEO /SSA Review Develop Solicitation RFP Process CS RFP may catch up to System Developer RFP. Source Selection PEO/SSA Review PCs & S/W Licenses procured using Navy and DoD enterprise contracts 2 mo 5 mo 2 mo Complete - Separate incremental ACS acquisition IAW AoA and AFEI/NDIA study recommendations - - Prototyping prior to Source Selection - USD (AT&L) 16

17. CANES Requirements Flowdown SRR SFR GIG ICD GIG EIEMA CDD Acq Strat USD AT&L ASD (NII) ASN (RDA) AOA Government SDS SEP/TEMP Func Spec Arch Spec Government Complete, reviewed with industry Item Specs Product Specs Industry Industry to complete as part of RFP response Item Interface Specification Prototype • Clear industry understanding of government requirements Concept Technology System 17

18. Questions/Backup • ADM Roughead’s CNO testimony to Senate Armed Services Committee on 2009 Budget Priorities • 28 Feb 08 “The CANES system achieves an open, agile, flexible and affordable network architecture that will move us forward. CANES embraces cross domain solutions that enable enhanced movement of data. It is a revolutionary change in our information technology infrastructure and it is absolutely vital for us to excel in 21st century warfare” 18

19. Industry Engaged on CANES 5 Requests for Information CDS/MLS – 43 responses Core Services – 30 responses Contracting Approach – 20 responses ILS – 19 responses Prototyping – release pending 18 architecture, ILS, and engineering docs released to industry over past six months for review and comment - monthly updates on program status 1st Industry Day: Jul 07 133 companies attended – 300 attendees Answered over 200 written and oral questions from industry 2nd Industry Day: Mar 08 120 companies attended – 511 attendees Answered over 120 written and oral questions from industry ASN (RDA) CHSENG briefed Acquisition Reform and SDS process 3rd Industry Day: Jun 08 Outbrief of System Requirements Review with Industry – 235 attendees 48 One-on-one meetings with industry: Apr-Aug 08 Positive feedback on SDS approach and level of Gov’t information available General concurrence on providing prototype as part of RFP response 28 Core Services specific one-on-ones completed: Jul 08 4th Industry Day: scheduled for 20 Nov Discussion of draft RFP, program status, way ahead for ACS 19

20. CDD Objective and Threshold Capabilities

21. Capabilities Voice Services IP Telephony Mobile and Stationary Secure and Un-Secure Video Services Video Teleconferencing Video/Graphics Distribution Data Services Network Support Information Management Core Infrastructure Services Network Access (IPv4/IPv6 Capable) Information Delivery Systems Management Performance, Availability, & Service Level Mgmt Fault, Problem, Incident, & Service Desk Mgmt Configuration, Change, & Release Mgmt Security Mgmt, IA, CND Capacity Mgmt Scalable, agile, and affordable Common Computing Environment (CCE) Increased interoperability federating NCES Core Services to tactical edge (ACS) Cross Domain Solutions (CDS) CANES is PEO C4I strategy to Consolidate, Enhance existing networks Network Consolidation Application providers will no longer need to manage multiple complex network integration points Foundation of PEO C4I Open Architecture Approach 21

22. CANES Constellation Net FCS SOSCOE DODIIS/Alien MCEITS NGA net "The DoD is too large an organization to attempt to encompass all of its activities in a single enterprise architecture“ - Mr. Dennis Wisnosky, Chief Architect and Technical Officer for DoD's Business Mission Area DoD C4ISR Enterprise

23. DoD Enterprise(Joint Capability Area Perspective) Net-Centric and Command & Control Joint Capability Areas AIR FORCE ARMY MARINE CORPS NAVY Net-Centric Enterprise Services Net-Enabled Command Capability & Service-Oriented Applications Strategic & Operational Environment NMCI / NGEN IIB ENCLAVES ARMY SOA-F MCEITS Joint Standards and Specifications Net-Enabled Command Capability & Service-Oriented Applications Tactical Environment UNIFIED BATTLE COMMAND CANES MCEITS AOC WS NCES Interoperates with Tactical Environment Common Services using Joint Standards, Specifications, and Reference Implementations 23 UNCLASSIFIED 23

24. Technical Approach of CANES Mandated by OSD Guidance and Policy QDR: “collection and dissemination of information should be managed by portfolios of capabilities that cut across legacy stove-piped systems…the Global Information Grid optimizes the processes for collecting, processing, storing, disseminating, managing and sharing information within the Department and with other partners…shift toward a Department-wide enterprise net-centric approach.” ICD GIG ES: “GIG ES requires solutions that enable secure, relevant, consistent, trusted and accurate information across and between multiple information formats, classification, national and multi-national COIs…open standards and Net-Ready interfaces to permit the cross-flow of information between systems and business processes…the primary benefits to the user/entity from the GIG ES service oriented architecture are: (1) Reliable, timely access to information across all DoD disciplines with requisite QoS to support the COI/domain mission requirements; (2) Organization-wide collaboration among Defense partners; (3) Secure organization exchange across security domains of products and data across the DoD… “ ICD GIG MA: “The GIG is a key enabler of network-centric warfare and is essential for information and decision superiority…improve interoperability of systems, and increase optimization of bandwidth capacity thereby dramatically improving the warfighting capabilities of joint forces” LOI GCCS-M & NCES: “The NCES program will implement a suite of Core Enterprise Services (CES) using a service oriented architecture. These services are targeted to provide DoD "enterprise" users and Communities of Interest (COI) with ready access to a broad array of services on both classified and unclassified networks.” GCCS FoS & NECC Synchronization MEMO: “…establish effective communication channels between the NCES program and Navy Enterprise Networks Programs to enable GCCS-M to take advantage of NCES-provided services” PDM III DoD CES Study & Report: “…conduct a study to assess the gaps and overlaps between DoD Component enterprise service programs…accelerate the provisioning and adoption of CES across DOD…identified a gap providing CES to warfighters at the tactical edge in the near term…there is currently no resourced plan that identifies how warfighters who are not reliably connected to DISN POPs…” GIG CES Implementation MEMO: “…these services and capabilities represent a fundamental shift to a service-oriented paradigm requiring a ubiquitous network environment, richly populated with information of value, readily available, secure, reliable, and scalable throughout DoD…” 24