Next Generation Cockpit Capability Collaboration Event Outcomes

1. PEO-RW Next Generation Cockpit Capability Collaboration Event 16 July 2019 sofwerx.org/cockpit

2. Blue Sky Working Group Brief Outcomes

3. GREEN TEAM 0-2 years Capability: • MH-60 DAP - Integrated HMD (360 vision, PPLI info, advisory data, weapons data) • Continue to integrate - Data from sensors (i.e. threats) digitally shared between aircraft • APAS - Increased Flight Control augmentation/haptic feedback/control laws • Continue - Mature Tactical Operating Picture, built from many available sources • Limited with federated systems - Data portability utilizing open standards Strategic Objective: • Integrate capabilities now • Lessons learned inform future requirements Tactical Objectives: • Bring key tools to fight in the short term • Incremental vision toward long term goals • Inform CDD requirements • Identify integration issues • Initiate POM process Integration Strategy • Tailor existing funds toward key objectives • OTAs • Leverage existing IDIQ contracts

4. GREEN TEAM 2-5 years Capabilities: • Integrated HMD (360 vision, PPLI info, advisory data, weapons data) • Add 360 vision • Sensor stitching/fusion (EO/IR) • Data from sensors (i.e. threats) digitally shared between aircraft • Interoperable comms with Joint/Partner forces and key civil organizations • Increased Flight Control augmentation/haptic feedback/control laws • Mature Tactical Operating Picture, built from many available sources • Data portability utilizing open standards • Obstacle data collection, rapid updateability Strategic Objective: • Mature technologies to usable TRL • Align funding for more in depth capabilities • Continue lessons learned inform future requirements Tactical Objectives: • Continue incremental vision toward long term goals • Finalize CDD requirements • Reduce/drive down integration issues • Manage POM process • Transition to open standards/architecture Integration Strategy • Manage strategic funds toward key objectives • Transition to Programs of Record where able

5. GREEN TEAM 5+ years Capabilities: • Integrated HMD (360 vision, PPLI info, advisory data, weapons data) • Sensor stitching/fusion (EO/IR) • Data from sensors (i.e. threats) digitally shared between aircraft • Radios that are completely interoperable with Joint/Partner forces and key civil organizations • Cognitive Decision Aiding (Routing, etc.) • Increased Flight Control augmentation/haptic feedback/control laws • Air Launched Effects (ALE) control from cockpit • Mature Tactical Operating Picture, built from many available sources • Data portability utilizing open standards • Obstacle data collection, rapid updateability Strategic Objective: • S&T efforts mature into usable TRL • Manage Integration and Architecture • Enter Spiral Development process to maintain overmatch capabilities Tactical Objectives: • Transition to continuous develop-integrate-field cycle • Utilize CDD requirements to continue funding • Implement new capabilities within open standards/architecture • Establish RFP for selection of partners Integration Strategy • Infrastructure for engineering collaboration between government and industry partners • Identify service requirements that fit SOA

6. Red team 0-2 Years: • Put in place the requirements, standards, KPPs, etc… to get the ball rolling for all of the technologies we want to investigate • HMI interface studies • Concept testing, verification, demonstration, cost benefit analysis – user feedback on proposed technology solutions • Initiate Autonomy – cognitive offloading, functional automation • Government defined quality attributes – affordability, reusability, portability, replacability • Federated approach to initial capability • Antenna placement optimization • Teaming datalinks (LPI/LPD) (LOS) • Partitioning of flight critical/mission software/hardware • MBSE – technology enabler • Funding for a cockpit/crewstation “Sandbox” that enables demonstration and test of innovative/relevant technologies • Provisioning list of existing GFE and enhancing technologies – determine sunset strategy for legacy federated systems • Industry demo/partnership/IR&D/Cost-share

7. Red team 2-5 Years: • New OS/OFP (Open Systems based, cyber security, anti-tampering) • Open System Interfaces – software message function and “outer edges”, hardware (i.e. government owned ICD), data artifacts/deliverables • Develop/test/demonstrate 3D Audio/video, larger displays, HMD, HUD, voice recognition, customizable/tailorable display content, multiple methods of I/O • Continue Autonomy – cognitive offloading, functional automation • Fly-by-oil flight control augmentation • Integrate the federated technologies • High-performance computing – processing, storage, memory • Teaming datalinks (LPI/LPD) (BLOS) • Data Fusion/correlation – processing hardware, storage, software • Stand up the cockpit/crewstation “Sandbox” that enables demonstration and test of innovative/relevant technologies • Initiate active cyber monitoring

8. Red team 5+ Years: • Training – not just the user but training the autonomous system • Sensor/mission quantity/quality data collection • Fly-by-wire flight controls • Implement 3D Audio/video, larger displays, HMD, HUD, voice recognition, customizable/tailorable display content, multiple methods of I/O • Implement active cyber monitoring

9. {TEAM ORANGE} 0-2 Years: • Identify and pursue ‘Quick Wins’ RFI’s, anticipate and allow failures • Dynamic re-tasking, routing, communications capabilities, HUD (desirements OML) • Targeted technology demonstrations that inform decisions makers and Industry Investment • SIMO SIL (High Fidelity Flyable Simulator) • Mission or Future Force Assessment (Ramp Composition and Scenario) • Legacy Fleet to Future force considerations (service life extensions/modernization) • Interoperability plan • MDS determinations and attributes, Family of Systems Functional Allocation • Requirements development (ICRD, DCDD, AFC Buy-in: Influence FARA/FLRAA/MOSA/ALE) • Bin and Prioritization capability requirements • Flow Function and define architecture (address ‘ilities’) • Alignment between Cockpit (TAPO), Training(TDSC), Publications (TAPO Pubs) for each build • Resource discussions and POM Build • Assessments of technical Feasibility (TRL) • ROM’s • Contracts (CRADA/OTA/Traditional Vehicles) • Provide S&T development vehicle outside critical path of ongoing sustainment builds • Approach OEMs to open data rights to enable industry modeling (CAD, Wiring, Thermal, etc.) • Evaluate existing process of certification, qualification, test that incorporate existing data & lessons learned to reduce the duration of this phase and task

10. {TEAM ORANGE} 2-5 Years: • [Ongoing] ‘Quick Wins’ RFI’s, anticipate and allow failures • Targeted technology demonstrations that inform decisions makers and Industry Investment • Provide data set to industry for modeling (CAD, Wiring, SW Interfaces, Thermal) • Fielding prototypes and demonstrations • Roadmap Tech Insertions • Designate SIMO tail number for T&E • [Ongoing] Mission or Future Force Assessment (Ramp Composition and Scenario) • Legacy Fleet to Future force considerations (service life extensions/modernization) • [Ongoing] Requirements refinement (ICRD, DCDD, AFC Buy-in: Influence FARA/FLRAA/MOSA/ALE) • Refine Industry Tradespace (Ex: Prioritize and Vocalize where the 80% solution is acceptable) • POM Defense • Assessments of manufacturing capability (MRL) • [Ongoing] Contracts (CRADA/OTA/Traditional Vehicles) • Beta test proposed changes to system certification and test (small scale integration opportunities)

11. {TEAM ORANGE} 5+ Years: • [Ongoing] ‘Quick Wins’ RFI’s, anticipate and allow failures • Fielding prototypes and demonstrations • Implement, document, and educate USG/industry on value added process changes • [Ongoing] Requirements refinement (CPD, DCDD, AFC Buy-in) • Influence FARA/FLRAA/MOSA/ALE) • TTP adjustments/development based on prototype capability initial user assessment • EMD/IOC

12. {TEAM Yellow} 0-2 Years: Requirement definition • Establish formal cockpit requirements (CDD) with TI process accounted for • Establish clear enclaves for software development to separate flight critical test/qual path vs. mission augmentation (could be included in FACE or as a stand-beside system) • Establish industry accessible testbed for rapid innovation and concept testing • Establish new interface technology standards • Touch, gaze/staring, voice, gesture • Heads-up display, windshield display, high-res traditional display, 3D/holographic display • UI standards: symbology/661, gazes/stares, voice vocabulary • Determine if Government should own interface standards, and if so, how Technology Exploration for 3-5-5+ year technologies • AI, ML, cyber, Cognitive Decision Systems • New Display Technologies Technology Insertion • Leverage mature technologies for incremental upgrade of fleet (i.e., ICS, tablet docking, sensors)

13. {TEAM Yellow} 2-5 Years: Requirements Evolution • Develop system specifications with industry participation (i.e., SOSA model) • Incorporate 0-2-year Technology Exploration outputs to refined requirements • Establish hardware requirements for next-generation AI/ML/CDS processing systems • Active defense acquisition process, source selection activities, etc. Prototyping Activities • Build new systems identified by Requirements, test in SIL, and evaluate on test aircraft • Establish man-machine / manned-unmanned teaming platforms and test facility • To enable rapid development, issue contracts that cover long-lead production components during R&D Technology Exploration for 5+ year technologies (continue to fund and steer) • Autonomy systems, quantum technologies • Continue exploration of AI, ML, cyber, Cognitive Decision Systems, new display technologies Technology Insertion • Leverage mature technologies for incremental upgrade of fleet (i.e., 3D audio, wireless, data management)

14. {TEAM Yellow} 5+ Years: Requirements Evolution / Technology Insertion • Establish AI and autonomy requirements for first Technology Insertion • Establish requirements for holographic / 3d / AR displays Build • Incorporate prototype flight test feedback into V1 LRIP/FRP, begin production Prototyping Activities • Build and test first autonomy system in SIL and flight test platform • Build and test holographic / 3d / AR displays and flight test • Build first quantum demonstrator (Comms? Crypto? Compute? ___?) Technology Exploration • Full-immersion technologies (vs. discrete displays/controls) • Continue to fund next-horizon exploratory activities • Let’s be honest, still need to explore quantum, holography, 3d displays at this point…

15. White 5+ Years: New RW platform • Fly by wire • Non-Conv RW Controls • Autonomous Flight Legacy RW platform upgrades • Integrate advanced AI/ML algorithms to improve SA and Decision Making Common to both • MOSA • Battle station vs Pilot station (AI/ML) • Configurable displays (HMD, Virtual Displays, Windscreen) • Fused sensors / comms (AI/ML enhanced) • Framework for rapid new tech integration • Robust resilient networked comms • Concurrent modeling & sim environment • Integrate advanced AI/ML algorithms to improve SA and Decision Making

16. White 2-5 Years: Development (to achieve 5yr plan) • Data driven decision making utilizing Testbed • Displays, cueing, fly by wire, non-conv controls • Evaluate initial prototypes of new tech • Leverage SIL and Modeling & Sim env • Virtual and Live flight testing • Advanced Teaming • Human Factors requirements / standards implemented • User involved in development and test • Digital comms / networking test and evaluation • AI datasets formulation / Training TTP implementation • Cyber / MLS / RMF plan established • Database optimization (maintain world model, trusted algorithms to determine keep data) Current Tech Improvements • APAS • Integrate wide touchscreen displays • Intra-aircraft wireless networking • Deploy baseline parameters • Fusion sensors • Fusion engine • Deploy windscreen display tech • Integrate voice to text display • Digital comms / networking test • Integrate ASE/DaVE/Targeting sensors to a common packge/system

17. White 0-2 Years: Development (to achieve 5yr plan) • Establish Testbed for development • Displays, cueing, • Establish SIL and Modeling & Sim env • Virtual and Live flight testing • Advanced Teaming • Human Factors study / requirements update • Fly by wire • Non-Conv RW Controls • MOSA - US Gov establish architecture standards, interfaces (commercially accept standards • User involved in development and test • Digital comms / networking development • AI datasets formulation / Training TTP development for sensor, comms, advanced teaming enhancement Current Tech Improvements • Capture baseline parameters for current sensor, comm, avionics, and all equipment to feed translation software • Prioritize parameter data • Integrate 3D Audio / Cueing • Integrate color displays/HMD with moving map • Evaluate/integrate windscreen display tech • Integrate voice to text display • Digital comms / networking development

18. Team Black 0-2 Years: Strategically- • Complete Human Factors and HCI Surveys- update Performance Measure for the future cockpit • Mid/Long Term requirements development • Research lab engagement/ maximize investment in research across DoD enterprise • Nest efforts with broader Joint, Conventional, and Future Vertical Lift efforts across DoD Tactically- • Expand use of Open SILs (e.g. Future Open Rotorcraft Cockpit Environment) • Develop a SOA unique Open SIL • Engagement with Rapid Equipping Force to move market ready technology into the Force • Prioritize items on “Desirements” tab for quick turn capability adds • Resolve display cockpit display hardware concerns • PiPcabability • 3D Audio • Pilot Prioritized Presentation/Interface (User Defined)

19. Team Black 2-5 Years: Strategically- • Refine existing & develop new requirements (must be on-going process) • Move Research Lab work toward integration • Research lab engagement/ maximize investment in research across DoD enterprise • Nest efforts with broader Joint, Conventional, and Future Vertical Lift efforts across DoD • Cont. Investment in Human Factors and HCI Surveys- update Performance Measure for the future cockpit Tactically- • Distributed Open SILs to expand technology development funnel (e.g. Synthetic Environment (L,V,C)) • Open SIL concept expanded to coalition partners • Constant Engagement with Rapid Equipping Force to move market ready technology into the Force • Sync the Prioritized items on “Desirements” with Open SIL efforts

20. Team Black 5+ Years: Strategically- • Technologies moved to TRL 6 moving toward fielding • Refine existing & develop new requirements (must be on-going process) • Nest efforts with broader Joint, Conventional, and Future Vertical Lift efforts across DoD • Cont. Investment in Human Factors and HCI Surveys- update Performance Measure for the future cockpit Tactically- • Sync the Prioritized items on “Desirements” with Open SIL efforts • Fielding 0-2 long lead technologies • SIL Capabilities advanced to support balance between increasing system complexity and human performance • Constant Engagement with Rapid Equipping Force to move market ready technology into the Force

21. Purple • 0-2 Years: • Tactically • Use rapid prototyping and testing to evaluate technologies, speed deployment and shape requirements - Use labs and sims to test at the right level of integration • Seek and try existing industry technologies and products - adopt/adapt COTS rather than building special purpose (items meet the needs of multiple customers) - Realize that small quantities result in expensive items and customer service challenges • Gap analysis between a COTS architecture and CAAS, ideally addressing CAAS shortcomings – can you build a helicopter with COTS • Have intelligence data packets integrate seamlessly into current displays – automatically post onboard intelligence information to the network • Automate loading of mission planning into the aircraft • Strategically • Fund S&T activities • Define capabilities vs hard requirements (what to you want the system to do vs red with white stripes) • Architecture: Core system that runs the critical functions of the aircraft • Develop requirements for the open standards to be used in future cockpits • Break the zero risk tolerance assumption - Current process is methodical, risk averse acquisition -> slow, expensive, inflexible – exploring the trade space between speed, risk and cost • Set audacious goals with an awareness that changes may be needed in process and historical silos will be needed

22. Purple • 2-5 Years: • Tactically • Establish partitioned architecture (such as flight critical, mission critical, non-critical, aux, test) to reduce difficulty, time and cost of new elements • Approve systems for information display (HUD, HMD, 3D, Audio, 3D Audio, and Haptic) with open interfaces to provide options for easy implementation of new systems • Identify low risk automation opportunities and build trust in the automation – spiral approach – philosophy: have the autonomy be the best copilot ever • Add systems that provide pilot decision aid/support/prioritization • Revise training (e.g. VR for flight sim) • Try large, high resolution displays that can be flexibly segmented in place of current multiple small portrait displays • Strategically • Let the computers do what they do well with having the pilots do what they can do well • Find a way to certify that incorporates the multiple existing standards environment rather than insisting on MIL certs and standards • Find ways to reduce the cost of the tech data package for certification • Develop metrics and parameters for the costs of risks (GM analogy – cheaper to pay the claims than to pay the engineering costs) in order to make it more cut and dry to accept risk

23. Purple • 5+ Years: • Tactically • Require compliance with Government established open OS / Plug and Play standards, common connectors and interfaces • Reduce information presented to the essential (example: can I remove legacy detailed engine information when I have a FADEC) • Quantify the costs of insisting on meeting MIL standards vs accepting risk of existing products • Robust voice-to-text that can be implemented on aircraft (processing power, crew, radio) • Strategically • Mission sets roadmap that includes what ifs to inform design • Take pilot cognitive capacity into account when designing the cockpit • Reform processes to meet operational needs and timeframes • Monitor AI and ML developments to see if maturity is appropriate for aircraft (e.g. brittleness, computational power requirements, development of appropriate training sets) • How best to use, manage and display all the data we have • Automatic vehicle health monitoring and data collection for improved and proactive maintenance

24. {BLUE} 0-2 Years: Common Tasks (Tactical) • Definition of system architecture requirements • Definition of system user capabilities requirements • Define architecture milestones / Roadmaps • Analysis of functional dependencies • Define a process for identification, demonstration, fast track development of technologies . Document proposed acquisition plan / process/ funding • Issue task orders, award contracts (STTR, SBIR, CRADA, OTA, RFP Awards for key early components for development/test • Functional demonstrations (Hardware/Software) • Define and Create a common government owned component test environment 0-2 Years: Common Tasks (Strategic) • Establish key relationships between entities (Government, Academia, Industry, PIA’s etc.) • Research and evaluate emerging technologies as they might apply to the project

25. {BLUE} 2-5 Years: • Continue to issue task orders to evaluate and test key capabilities • Issue RFP for Open Architecture software and hardware development • Issue RFP/award contracts for LRIP units of desired hardware • Develop SIL for lab integration and testing • Integrate hardware and software on an aircraft • Conduct initial test flights (DT) – test, fix, test – multiple iterations expected • Conduct IOT&E and Operational Evals • Award production contracts

26. {BLUE} 5+ Years: • Convert existing airframes through a Block Mod process • Continue to develop and integrate emerging/matured equipment