1. Panel 5: The Latest in OA Innovation and C4ISR 4 November, 2014 Mike Rice President / Senior Systems Engineer R2E Inc

2. Q1: What are the latest innovations driving open architecture solutions in C4ISR?  “Re-think” our traditional approach to platforms (ships, aircraft, submarines, unmanned vehicles, land vehicles, etc.) and their payloads (sensors, combat control, weapons control, weapons, C4ISR, etc.). Change begins at the “top” of the leadership pyramid.  Consideration given to adaptability, modularity, scalability, and commonality; emphasis on those characteristic so that “affordable relevance over the life-cycle” can be realistically achieved. “To ensure our Navy stays relevant, these platforms have to adapt to changing fiscal, security, and technological conditions they will encounter over their lives. It is unaffordable, however, to adapt a platform by replacing either it or its integral system each time a new mission or need arises.” ---ADM Jonathan Greenert, Chief of Naval Operations “Making the move to modularity will further allow us to maximize the service lives of our ships as we will be able to upgrade the combat systems equipment, to more easily and affordably keep pace with rapidly advancing technology.” ---VADM Thomas S. Rowden, Director, Surface Warfare Division (OPNAV N96) U.S. Naval Institute Proceedings magazine, January 2014

3. Q1: What are the latest innovations driving open architecture solutions in C4ISR?  C4I Afloat Network Enterprise System (CANES)  CANES addresses critical afloat network challenges Legacy network reliability and availability Information Assurance (IA) & Computer Network Defense (CND) challenges Training & Network Operations standardization  What is CANES? (Cost containment for existing Afloat Networks) Consolidation of Afloat Networks / Low Risk  COTS Hardware and Software  Open Standards  Government owned data rights Approved Cross Domain Solutions Constant competition to drive down cost  Status Quo Multiple security vulnerabilities Multiple unique networks & h/w variants Multiple Operating Systems and versions Multiple protocols and legacy interfaces Inefficient use of server/storage resources

4. Q2: How is industry working closely with government to continue introducing open architecture systems into C4ISR and the acquisition process?  Offering Network / Computing solutions based upon open standards.  Providing competitive computing resources from readily available COTS manufacturers.  Identifying opportunities for quantity buys and non-end of life commodities.  Developing means to isolate failures, providing redundancy and safe failover.  Providing useful design data sufficient for re-procurement purposes.  Limiting the use of proprietary, Intellectual Property Rights protected end-items (Hardware / Software)

5. Q3: What are the best practices?  Government:  Use of technical reference model (NTRM)  Use of Roadmaps – systems’ evolution  Portfolio management across product lines  C4ISR Master Plan – governance of PoR acquisitions coordinated with PPBE cycle / operational capability needs  Employment of open standards / repository of standards profiles (DISR)  Establishment of Net-Centric Enterprise Solutions for Interoperability (NESI) : registration, discovery and compliance  Use of DOD PM Contract Guidebook  Industry:  ???

6. Q4: What can be learned from the commercial Sector?

7. Q5: How far should the government go to capture data rights?