DRAFT_HUD_PPA_Draft_SOO_07262018.pdf

STATEMENT OF OBJECTIVES (SOO)

For Prototype Project Award (PPA)

Heads Up Display (HUD) 3.0 Program

Section 1: Scope Determination

The HUD 3.0 program is suitable for execution under Other Transaction Authority per 10 USC 2371B (Section 815 of FY16 National Defense Authorization Act (NDAA)). There is an operational need for the HUD 3.0 capability to regain overmatch against peer and near peer threats, as well as the need for improved training and simulation tools to provide the warfighter with the ability to train and rehearse using the same equipment utilized in actual operations. Rapid and agile prototyping is necessary to achieve this capability. A limited number of production equivalent systems will be procured over a 24 month period, beginning with a commercial proof of concept, evolving to a tailored military solution to prove out manufacturing feasibility. An iterative test-fix-test approach will be utilized to rapidly incorporate changes into the design with the end state of developing a system suitable to transition to production at the completion of the project period.

Section 2: Program Objective

The Government seeks proposals for establishing a set of core solutions to achieve the capabilities required for the HUD 3.0 program. Sample hardware will be submitted and evaluated during the proposal phase for this Prototype Project. The objective of the HUD 3.0 Prototype Project is to rapidly develop, test, and manufacture a single platform that Soldiers can use to Fight, Rehearse, and Train.

This platform will provide increased lethality, mobility, and situational awareness with the following features:

• Head Borne Vision System (no helmet mount assembly; low profile, conformal system providing 24/7 squad situational awareness in all operating environments; see thru, wide field of view display; ballistic and hearing protections with 3D sound field)

• Day/Night Rapid Target Acquisition (RTA) from Family of Weapon Sights-Individual (FWS-I) and Family of Weapon Sights–Crew Served (FWS-CS)

• Machine Learning Capabilities/Artificial Intelligence (AI)

• Synthetic Training Environment (STE) Squad Capability (One World Terrain, Training Simulation

Software, Training Management Tools)

• An Adaptive Squad Operating System

• Nett Warrior/Android Tactical Assault Kit (ATAK) Connectivity (operating on Secure But

Unclassified (SBU) portion of the Integrated Tactical Network (ITN) using current military radios;

operation expected in contested and denied environments with minimum capability to see/shoot/move/navigate)

• Fused Day/Night Vision Capabilities

• Intra-Soldier Wireless (ISW) Connectivity

• Squad Lethality Ratings/Metrics (real-time measure of squad & soldier performance;

physiological feedback to include concussions, heart rate, breathing rate, readiness)

• Mixed/Live Reality for Combat Training and Rehearsals including Navigation, Targeting, Phase

Line (Symbology), and Automatic Target Recognition (ATR)

• Government Owned Soldier/Squad Architecture (collaboratively developed by Government and industry over 24 months with key interfaces across squad identified, developed, validated, and implemented; tactical power architecture and management system)

• Data to be modular open source, unclassified or perishable (PLI) and stored in the Cloud

The HUD 3.0 Prototype Project seeks to provide an Integrated Visual Augmentation System (IVAS) and integrated STE Squad capability within the Squad Architecture in support of Army, Marines, and Special Operations Forces within 24 months. The PPA shall deliver a standalone STE Squad capability and IVAS within 12 months, and STE Squad capability integrated into IVAS within 24 months. This overall HUD 3.0 capability shall be suitable to begin production as early as 4Q20 to ensure clear overmatch in Close Combat engagements and drastically increase Squad Lethality.

This PPA will conduct an accelerated development effort for the IVAS and STE Squad capabilities with a plan to deliver multiple Capability Sets (CS) over a 24 month period which will be evaluated in various operational settings. This approach will allow simultaneous maturation of technology and manufacturing through multiple builds and Soldier Touch Point (STP) engagements. Design Reviews (DR) and Build Readiness Reviews (BRR) will serve as Knowledge Points informed by User Juries (UJ) and STP Test Reports (TR). The STPs will provide information to incrementally refine the IVAS and STE Squad capabilities with the objective to achieve a fieldable HUD 3.0 system by 4Q20, followed by transition to a production contract. The end state for the first fieldable HUD 3.0 design to be completed at the end of the 24 month project period is as follows:

• IVAS will provide overmatch warfighting capability plus a Close Combat STE Squad capability with Synthetic Training Environment (STE) core capabilities.

• IVAS will provide a single integrated digital, low profile, conformal day/night device that allows Soldiers and Squads to Fight, Rehearse and Train in any operational environment.

• IVAS will provide an architecture that allows these capabilities to be delivered/integrated at the speed of war/threat, technology, and industry.

Section 3: Background

The HUD 3.0 capabilities are required to support operational needs identified in the 2018 National Defense Strategy (NDS). Near peer threats have capabilities that match or exceed those of U.S. forces.

Adversaries can detect, target, and lethally engage before U.S. forces become aware of their presence.

The Close Combat Force suffers the highest casualty rate in combat. Current and future battlefields will be fought distributed in urban and subterranean environments where current capabilities are not sufficient. The HUD 3.0 capabilities will significantly enhance soldier sensing in all environments, increase lethality by enhancing the ability to detect, decide, and engage before the enemy, and allow U.S. forces to conduct “25 bloodless battles before the 1st battle” providing increased sets and repetitions in complex environments utilizing its STE Squad capability. Accelerated development of these capabilities is necessary to recover and maintain overmatch.

Limited integration of lethality and mobility capabilities currently constrain the warfighter in combat.

HUD 3.0 will provide integration of Head-Body-Weapon to provide significant enhancement of detection, targeting, engagements, and AI that match the speed of war. Current training simulations provide limited representative terrain, structures, and locations. The STE Squad capability will provide infinite availability of identical terrain, structures, and locations for squad close combat rehearsals prior to actual engagements in those environments. Different operational weapons and equipment are currently used to train versus fight. HUD 3.0 will allow the warfighter to “Train as You Fight”, with identical training/operational weapons and equipment in any terrain.

Section 4: Design, Analysis, and Test

Four Capability Sets (CS) shall be delivered to the Government during the 24 month Prototype Project and shall be evaluated during multiple STPs. STPs will occur in controlled environments initially and progress to Arctic, Desert, Jungle, Urban and Subterranean environments – capability of prototype builds will shape each event. The Government will prepare a Test Report following each STP event to document findings for vendor action and incorporation into subsequent Capability Sets. The following table describes the STPs which correlate to each CS:

Element STP 1 STP 2 STP 3 STP 4 Headset COTS Plus - Modified

COTS headset w/ integrated COTS thermal camera

Conformal low profile head mounted design w/ day/night see-through immersive reality display, off-axis GFE thermal and low-light-level sensors

HUD 3.0 w/ waveguide optics and improved (2nd run) GFE thermal and low-light-level sensors w/ FOV >50 degrees per eye

HUD 3.0 w/ waveguide optics and latest GFE thermal and low-light-level sensors w/ FOV >50 degrees per eye

On-body Computer

Commercial version of on-body computer w/ ATAK

HUD 3.0 Body Pack w/

ATAK

HUD 3.0 Body Pack w/

ATAK, ISW

HUD 3.0 Body Pack w/

ATAK, ISW

Power Power source for commercial product

Conformal Wearable Battery

Conformal Wearable Battery

Conformal Wearable Battery

Controller Controller for commercial product

Tactile, voice, and gesture control

Tactile, voice, and gesture control

Tactile, voice, and gesture control

Comms Scenario

N/A Open Contested Denied

Formation Size

Individual/ Squad Platoon Company Battalion

Other Capabilities

Software: Software: Software: Software:

-Display Nett Warrior Data 2-D (T) 3-D (O)

-3-D Nett Warrior data (for Situational Awareness)

-3-D Nett Warrior data (for Situational Awareness)

-3-D Nett Warrior data (for Situational Awareness)

-Voice comms & voice to text

-Voice comms & voice to text

-Voice comms & voice to text

-Change detection -Change detection -Target Cueing -Target Cueing -Comms automation

(for example, set up call groups)

-Comms automation (for example, set up call groups)

-Automated data throttle for comms denied scenario

-Foreign language translation/auto-display

Augmented Reality: Augmented Reality: Augmented Reality: Augmented Reality:

-2-D Navigation -3-D Navigation -3-D Navigation + user designated routes -3-D Navigation + user designated routes

-Simulated RTA video display

-Rapid Target Acquisition -Rapid Target Acquisition

-Rapid Target Acquisition

-Simulated SUAV video display

-User Interface Control -User Interface Control -User Interface Control

-External Sensors Compatibility

-External Sensors Compatibility

-External Sensors Compatibility

-Shared SA/C2 and Squad and below-level maneuver graphics

-Shared SA/C2 and Platoon and below-level maneuver graphics

-Shared SA/C2 and Company and below-level maneuver graphics

-Post-mission AAR -Post-mission AAR -Weapons field of fire, range, and obscuration overlay

Artificial Intelligence:

Artificial Intelligence: Artificial Intelligence: Artificial Intelligence:

-Collaborative Planning (Platoon and below)

-Collaborative Planning (Company and below)

-Collaborative Planning (Battalion and below)

-Squad duty position configurations and performance

-Squad and below configurations and performance

-Platoon and below configurations and performance

-Company and below configurations and performance

-Auto-target detection -Auto-target detection and classification

-Auto-target detection and classification

-Pre-mission planning workflow

-Pre-mission planning workflow

-Pre-mission planning workflow

-Post-mission resource re-distribution

-Post-mission resource re-distribution

-Route selection overlay

-Route selection overlay

-Assess threat (weapon/no weapon)

-Hostile fire locator -STE Machine Learning-enabled OPFOR

Miscellaneous: Miscellaneous: Miscellaneous: Miscellaneous:

-Compatible w/ existing helmets -Compatible w/ existing helmets

-Compatible w/ existing helmets

-Compatible w/ existing helmets

-Ballistic eye protection -Ballistic eye protection -Laser Eye protection -Laser Eye protection -3-D sound field hearing + hearing protection (e.g., TCAPS)

-3-D sound field hearing + hearing protection (e.g., TCAPS)

Soldier Performance

-Research M&S capabilities, Identify/prioritize M&S gaps. Establish Performance Data Lake. Begin collecting existing Soldier performance

-Analytics dashboard, structure and scope/fidelity of Model, M&S roadmap.

-System capable of utilizing Army/ DoD sponsored models and simulations, existing

-Collection of HUD 3.0 initial sensor capability.

Capture and re-create Squad activity in virtual environment using Soldier and equipment sensors. DOE to support additional

-Incorporates Adaptive Soldier Architecture data, incorporate rudimentary AI feedback from STE training. Virtual evaluation environment (Decision Support Tool) V&Ved (to an agreed studies/research data, execute evaluations, studies, and data collection to close gaps.

-System capable of utilizing Army/ DoD sponsored models and simulations, existing Soldier and Squad performance research data (studies, experiments, sprints, unit demographics, etc), and feedback/ measurements (warfighter movement speeds, orientation, duration, proximity within the unit) from Soldier worn sensors during the “train, rehearse, fight” cycle, then ordered in a central database type system, batch or real-time updates, for recall and comparison with similar unit types to asses, inform, and optimize Soldier and Squad performance to inform potential Soldier and Squad level Measures of Performance (MOP) and Measures of Effectiveness (MOE) (threshold).

System capable of providing an equipment and mission optimization tool with real time updates to provide users with courses of action, training

Soldier and Squad performance research data (studies, experiments, sprints, unit demographics, etc), and feedback/ measurements (warfighter movement speeds, orientation, duration, proximity within the unit) from Soldier worn sensors during the “train, rehearse, fight” cycle, then ordered in a central database type system, batch or real-time updates, for recall and comparison with similar unit types to asses, inform, and optimize Soldier and Squad performance to inform potential Soldier and Squad level Measures of Performance (MOP) and Measures of Effectiveness (MOE) (threshold).

-System capable of providing an equipment and mission optimization tool with real time updates to provide users with courses of action, training scenarios, individual training techniques, performance improvement plans, etc… based real-time and previously categorized data (objective).

evaluations, studies, and data collection to close gaps. Utilization of Machine Learning to identify correlations with performance data.

-System capable of utilizing Army/ DoD sponsored models and simulations, existing Soldier and Squad performance research data (studies, experiments, sprints, unit demographics, etc), and feedback/ measurements (warfighter movement speeds, orientation, duration, proximity within the unit) from Soldier worn sensors during the “train, rehearse, fight” cycle, then ordered in a central database type system, batch or real-time updates, for recall and comparison with similar unit types to asses, inform, and optimize Soldier and Squad performance to inform potential Soldier and Squad level Measures of Performance (MOP) and Measures of Effectiveness (MOE) (threshold).

-System capable of providing an equipment and mission optimization tool with real time updates to provide users with courses of action, training scenarios, individual training techniques, upon level of fidelity).

Utilization of Machine Learning to identify Proposed MOPs / MOEs.

SLR and Initial Squad Performance Baseline published.

-System capable of utilizing Army/ DoD sponsored models and simulations, existing Soldier and Squad performance research data (studies, experiments, sprints, unit demographics, etc), and feedback/ measurements (warfighter movement speeds, orientation, duration, proximity within the unit) from Soldier worn sensors during the “train, rehearse, fight” cycle, then ordered in a central database type system, batch or real-time updates, for recall and comparison with similar unit types to asses, inform, and optimize Soldier and Squad performance to inform potential Soldier and Squad level Measures of Performance (MOP) and Measures of Effectiveness (MOE) (threshold).

-System capable of providing an equipment and mission optimization tool with real time updates to provide users with courses of action, training scenarios, individual training techniques, performance improvement plans, etc… based real-time and scenarios, individual training techniques, performance improvement plans, etc… based real-time and previously categorized data (objective).

performance improvement plans, etc… based real-time and previously categorized data (objective).

previously categorized data (objective).

Adaptive Soldier/ Squad Architecture

Configuration Database (CD): - Initial physical data, performance specifications, capabilities & comprehensive interface control documentation for infantry squad

Architecture Assessment Tool (AAT): -Demonstrate initial predictive analytics model -Hybrid application functionality on all required platforms

-Soldier Architecture for Soldier Performance and Equipment, -Squad-on-Squad performance data collection to update Architecture Tool -Demonstrate STE Squad Capability with expanded Training Simulation Software

(TSS)

-Configuration Management Plan (CMP): Initial Draft

CD:

-Comprehensive physical data, performance specifications, capabilities & comprehensive interface control documentation for infantry squad -Full redundancy (backup & recovery); concurrency control sub-systems are operational; access management (read/write) process in place; hosting strategy provided for Govt concurrence

AAT:

- Squad Architecture output, Squad performance baseline and Soldier Lethality Rating -STE Squad Capability for Battle Drills 1-11 and Marine Corps Squad & Fire Team T&R tasks and Scalable TSS, OWT, and

TMT.

-Hosting and access management strategy

Element STP #1 STP #2 STP #3 STP #4

STE

Squad Training

Capability

TSS: Demo of military content & application (avatars, models, and behaviors)

OWT: 50m mesh inside and outside, supports terrain of current location

TMT: Basic scenario editor (planning/executing) with AAR rewind/edit

OE Wraps: Daylight operations, Desert, Coniferous Forest

AAR: Capture 3D video with editing tool

SQD CAP: Demo scale from 1-4 warfighters & 2 trainers, initial FoT

Squad CAP: Fire team capability sample of squad training capability

Personnel: 14(2)

Equipment:

OPFOR: Virtual Small Arms, SAF provides effects on user/enemy

TSS: BLUFOR SQD & OPFOR

models

OWT: Include postage stamp terrain that Soldier can be geo-imported, 100m inside/outside Mesh, import soldier location into OWT geo-location

TMT: Customized data content displayed by trainer, basic scenario editor (planning/executing) with rewind/edit

OE Wraps: Mountains, Wetlands/Littoral, DUT

AAR Data Capture: Did hit, should hit data, sectors of fire (flagging), line-of-sight tracking, target acquisition time, speed of engagement.

SQD CAP: 11 Squad Collective Capabilities (React to Direct Fire Contact (07-3-D9501), Conduct a Squad Assault (07- 4-D9515),Break Contact (07- 3-D9505),React to Ambush (Near) (07-3-D9502),Enter and Clear a Room (07-4- D9509)Knock Out a Bunker (07-3-D9406), Enter a Trench to Secure a Foothold (07-3- D9510), Conduct the Initial Breach of a Mined Wire Obstacle (07-3-D9412), React to Indirect Fire (07-3- D9504),React to a Chemical Attack (03-3-D0001))

Equipment: M4/16, M27, M249, M203/320, M9/17, Grenades/Smoke/ Flash Bang

OPFOR: AT weapons

TSS: OPFOR and BLUFOR SAF interoperable with voice commands, full FoF, FoT, Civ models

OWT: 200M meshing collection of terrain from HUD to OWT, 600m Field of View (FoV) for enablers, Thermal/IR models Binaural audio

TMT: Scenario editor populates BLUFOR, OPFOR, civilian models Initial ability to collect Soldier biometric tracking tool

OE Wraps: Artic

AAR data capture:

Squad CAP: 39 (10) Platoon size element with multiple squads executing simultaneously, FO, Medevac functionality, Virtual drone functionality, Common Call for Fire, CAS, 9 line Medevac

Equipment: M240B, Grenades/Smoke/Flash Bang, Javelin, AT4, SUAV

Sqd Tools: Shotgun, Claymore, door breach charges, breaching equipment for a mine-wired obstacle

TSS: Organic squad w/ AI SAF & wrap at PLT level, NETT Warrior interoperability, Interactive voice commands, employment of AI route selection capability

OWT: Scalable terrain w/ 1k observation of effects & enablers

TMT: Scalable scenario editor/AAR with local repository & AAR Analysis Tool, Selected Individual Task development toolkit

USMC Squad CAP: 8 Marine Corps Squad Collective Capabilities (Cordon and Search (INF- MAN-4213), Patrolling ops (INF-MAN-4301), Lead traffic control PT (0311- MOUT-2002), Conduct recon patrol (INF-MAN- 4302), Conduct ground attack (INF-MAN-4001), Clear a room (INF-MAN- 3002), Integrate fires (INF- FSPT-4001), Provide offensive and indirect fires

(INF-MGUN-4001)/ (INF-

MORT-4002; 60mm Mortars)/ (INF-MORT- 4003; 81mm Mortars))

Equipment: Enabler requests for medevac, artillery/CAS/UAS, observe red IDF effects

• CS #1 (50 systems). CS #1 shall provide a commercial proof of concept integrating a commercial thermal sensor, establish squad performance Data Lake, and demonstrate initial STE Squad Capability development efforts. Two UJ events will be conducted during the build out of CS #1 to provide early user input regarding the system design. CS #1 shall be delivered within 4 months of initial PPA and will be evaluated during STP #1.

• CS #2 (300 systems). CS #2 shall represent the final form factor design of the new military goggle, integrate ATAK software for Augmented Reality (AR) and initial HUD 3.0 architecture as baseline capability, and demonstrate STE Squad collective capability to include Squad training capability for squad collective tasks identified below, Organic Squad Weapons, Training Simulation Software (TSS), One World Terrain (OWT), and a Training Management Tool (TMT). A DR will be conducted upon completion of the CS #2 system design, followed by two UJ events during software and process development. A BRR will be conducted prior to the build out of CS #2. Systems from CS #2 shall be delivered within 11 months of initial PPA and will be evaluated during STP #2.

• CS #3 (600 systems). CS #3 shall include a wide field of view display, ballistic and laser protection, Soldier Architecture for Soldier Performance and Equipment, Squad-on-Squad performance data collection to update Architecture Tool, and demonstrate STE Squad collective capability with expanded TSS as well as the following enablers: Forward Observer (FO), Medical Evacuation (MEDEVAC), Platoon Unmanned Aerial Sensor (Plt UAS), squad-level quadcopter UAS, and Squad and Platoon Weapons. The vendor shall integrate low light level and thermal sensors provided as Government Furnished Equipment (GFE). A DR will be performed prior to the start of software and process development, and a BRR will be conducted prior to CS #3 build out. Multiple UJ events are anticipated throughout the design and build process to provide frequent user feedback regarding the emerging system design. CS #3 shall be delivered within 17 months of initial PPA and will be evaluated during STP #3.

• CS #4 (1600 systems). CS #4 shall represent the first fieldable military HUD system demonstration, with Squad Architecture output from the Architecture Tool, Squad performance baseline and Soldier Lethality Rating from Data Lake information, STE Squad collective capability and Marine Corps Training and Readiness (T&R) Tasks Fire Team, and Scalable TSS, OWT, and TMT. The vendor shall integrate improved low light level and thermal sensors provided as GFE.

A DR shall be conducted prior to software and process development, and a BRR shall be conducted prior the CS #4 build out. Multiple UJ events are planned during development and build to provide real time user feedback for incorporation into the system. CS #4 shall be delivered within 21 months of initial PPA and will be evaluated during STP #4.

Army and Marine Corps seek a mixed reality simulation training capability to train dismounted Squad close combat tasks and Squad collective tasks (i.e. React to Direct Fire Contact (07-3-D9501), Conduct a Platoon Assault (07-3-D9514), Conduct a Squad Assault (07-4-D9515), Break Contact (07-3-D9505), React to Ambush (Near) (07-3-D9502), Knock Out a Bunker (07-3-D9406), Enter and Clear a Room (07-4- D9509), Enter a Trench to Secure a Foothold (07-3-D9510), Conduct the Initial Breach of a Mined Wire Obstacle (07-3-D9412), React to Indirect Fire (07-3-D9504), React to a Chemical Attack (03-3-D0001), Battle Drill 11: React to an IED (05-3-D1703); and USMC Squad Collective Cordon and Search (INF-MAN- 4213), Patrolling Ops (INF-MAN-4301) Lead Traffic Control PT (0311-MOUT-2002), Conduct Recon Patrol (INF-MAN-4302), Conduct Ground Attack (INF-MAN-4001), Clear a Room (INF-MAN-3002), Integrate Fires 123456 (INF-FSPT-4001)). This training capability shall be scalable from individual Soldier/Marine through Squad sized formations of up to 15 personnel (Army Squad of 9 or Marine Corps Squad of 13, plus 2 trainers) with organic (M-4, M-27 Infantry Automatic Rifle (IAR), M-9/17, M-249, M203, and M- 240B) and simulated (Hand Grenades (Frag, Smoke, Flash Bang), M72A7 Light Anti-Armor Weapon, AT-4, M3 MAAWS (Carl Gustav), Javelin, Mortars 60 & 81mm) weapons. HUD 3.0 will provide the Army/Marine Corps with a Squad collective training capability comprised of the following:

The vendor shall develop TSS comprised of a common synthetic environment that presents operational variable elements and their interrelated effects that make up the Operational Environment (OE) (military, social (pattern of life), information, infrastructure, physical environment, and time) to execute multi-domain operations that include land, air, and maritime domains. A global terrain and atmospheric effects to provide and present a 200m square meshed battlespace maneuver box for the intended training event while correctly accounting for atmospheric effects. The TSS must accurately represent the four warfighting functions (movement and maneuver, fires, protection, and mission command) consistent with the unit and force type (i.e., combat arms, combat support, combat service support) associated with those functions, to include the ability for users to observe each other’s hand and arms signals and other cues, enabling non-verbal communication between Soldiers/Marines within the system. The three dimensional models of persons, vehicles, systems, equipment, and objects with attendant dynamics, behaviors, and characteristics for the intended training event and objectives must correctly account for and consider vulnerabilities to damage, sensor capabilities, thermal signatures, and other model attributes. Munitions external and terminal ballistics must portray correct behavior of direct and indirect fire munitions while in flight (external ballistics) and at impact and fuse function (terminal ballistics); atmospheric, weapon, and terrain influences must also affect munition behaviors and their effects (e.g., spin drift, smoke dispersion, cratering). AI in automated entities (mounted/ dismounted, friendly/enemy/neutral, civilians) must have correct and consistent adjudication of all interactions among all entities, live and simulated while participating in the synthetic environment. The TSS must replicate the visual and audio effects of company organic and non-organic direct and indirect fire supporting arms assets. It must accurately model the fragmentation effects, ballistics, and surface danger zones (SDZs) of all munitions per standards presented in the Department of the Army Pamphlet (DA Pam) 385-63 Range Safety, in order to prevent negative training. TSS must facilitate a two way data exchange with the TMT construct for the purposes of scenario development and After Action Review (AAR) with interoperability with current mission command information systems (e.g., Nett Warrior/ATAK). TSS must deliver an open, well-defined documentation of an API that provides external simulations to gain control of and pass data & processing (ie: AI Machine Learning) while maintaining acceptable HUD TSS performance.

The vendor shall develop an OWT to provide the ability to ingest layered foundation terrain data with elevation (inc imagery), roads (OSM), buildings (Bing, Vricon, drone), Vegetation (MODIS), Clutter (PMGS), and water (NOAA). The Government furnished models will be provided in the form of Object (OBJ)/Filmbox (fbx) files to support and facilitate scenario generation. A 200m x 200m meshed area with <1cm geo-specific resolution with at least 5 levels of detail to produce a 3rd person vantage of up to 100m above the ground (i.e. first-person to real-time strategy). The addition of navigation meshes and colliders will enable Non-Player Character (NPC) path-planning and munition interaction with the terrain. OWT will provide the geo-referenced data in the form of Military Grid Reference System (MGRS) to be able to place objects on the local coordinate system and display the grid locations. OWT will be able to support single terrain datasets (no additional clipping, culling, paging, tiling) of at least 1km squared, paging and tiling of datasets from LFS/Cloud to device hardware of arbitrary size, interior building navigation, collision and path-planning, the ability to place objects into the training area to facilitate training (Bunkers, buildings, trees, etc.), change the textures of existing structures, and provide a correlated environment between the live training environment and the HUD TSS.

The vendor shall develop TMTs with a capability tool to access, query, and retrieve authoritative and other data needed to plan and design training scenarios to meet the required training objectives. This tool will allow the trainer and scenario creator to build a scenario for execution in the simulation.

Through the interface (e.g., monitor/keyboard) the trainer and or scenario creator will be able to choose the terrain, the desired weather conditions, friendly, opposing, and non-combatant forces to be placed appropriately on the terrain, and the time of day needed for the training event. Any systems, equipment, and objects, both static and dynamic are selected and placed appropriately on the terrain with applicable movement waypoints defined and linked to appropriate automated entities. Scenario trigger capabilities will be available to establish conditions identified and structured to cause those triggers to activate, thus initiating events, given the actions (or inaction) of the intended initiator (user, automated entity, or some other event). When the scenario creator is satisfied that all elements of the operational environment relevant to the training event and the training objectives are captured, the TMT produces a simulation scenario file. At the appointed time and place for the training event, the user runs and executes the simulation scenario file. After the training scenario is complete, an AAR will be conducted. The AAR will display a moveable God’s eye view, Soldiers view (First & third person viewpoint during replay), weapons orientation view, Pause function to facilitate correction during execution (in-stride AAR), Hit counts per user (rounds fired, critical hits vs non-critical hits), Time to completion (applicable to the standards), Bookmark function (to skip to relevant points in the training event), Shareable replay (for distribution and best practices), Capture voice traffic (radio and non-radio), Biometrics (heart rate, blood pressure), and the ability to export training data to external systems (e.g., Army Future DTMS systems or Marine Corps future training information management systems).

In order to execute squad training at the point of need a local network and additional hardware with interfaces (i.e. server, local network, incremented or simulated squad organic weapons to execute squad collective training tasks) will be required.

The vendor shall develop Squad Architecture and Performance tools to include a Configuration Database, Architecture Assessment Tool, and Squad Performance Model. The Configuration Database shall provide a Soldier-level and Squad-level architecture that documents all existing and future Soldier and Squad variations as follows:

• Includes all performance capabilities and interface controls between Soldier and Squad systems and external systems.

• Includes interface definitions between components.

• Includes a configuration management capability for base architecture and all future architecture developments.

The vendor shall develop and maintain a secure Data Lake. The Data Lake acts as a data source for the Configuration Database, Architecture Assessment Tool and Squad Performance Model to capture and recreate squad actions in M&S environment.

• Sensor Data from the HUD into the Data Lake o GPS o Biometric Data o Head, Weapon, & Body Orientation o Eye tracking

• Data provided by the Government into the Data Lake o Soldier Proficiencies o Demographic Data o Equipment Capabilities o Marksmanship o Physical Performance o Feedback from STE o Existing Studies

The Architecture Assessment Tool shall provide a computer tool which leverages AI/ML to store, maintain and continuously develop and improve the Adaptive Soldier Architecture to include the following capabilities:

• Accessible to authorized users world-wide and able to interact/share data with other Army/Joint Program databases and tools

• Provide authoritative information regarding current systems, system-of-system configurations and formations that facilitates informed architecture decisions. Provides associated Lethality information from Squad Performance Model.

• Enables aggregation of components into systems and systems into higher level formations.

Provides virtual integration environment for new/ existing components

The Squad Performance Model shall provide a performance model that allows for the evaluation of data from the Data Lake into the Adaptive Soldier Architecture Analysis Tool and outputs Soldier and Squad Lethality ratings (see figure below). The vendor shall develop and validate an optimization and assessment tool with the ability to predict Soldier/Squad performance and inform future investments to:

• Evaluate and utilize (as appropriate) Army/ DoD sponsored models and simulations.

• Evaluate and utilize (as appropriate) existing Soldier and Squad performance research data

(studies, experiments, sprints, unit demographics, etc).

• Identify and address gaps in experimentation methodologies, and Soldier and Squad performance research data which would inform the Squad Performance Model.

• Utilize feedback/ measurements from the HUD system during the “train, rehearse, fight” cycle in

Squad Performance Model.

• Identify and recommend Soldier and Squad level Measures of Performance (MOP) and

Measures of Effectiveness (MOE).

Section 5: Configuration Management

The vendor shall establish a configuration management process with a structured approach to controlling the hardware and software configuration integrity of the production systems, maintaining interchangeability of hardware, and assuring the functional baseline of the HUD 3.0 is maintained throughout the project. HUD 3.0 Squad Architecture will be collaboratively developed by Government and Industry in 24 months and owned by the Government. Government Purpose Rights will be procured to support Organic Industrial Base (OIB) Support and competitive procurement of spare parts for sustainment and allow for third party maintenance and upgrade of HUD 3.0 software. Interface Control Documents (ICDs) shall be submitted by the vendor at the spare part/assembly-level that assure 100% form, fit, and function interchangeability for the HUD 3.0 system with sufficient information to enable third party development of interoperable systems.

The vendor shall prepare and submit a Configuration Management Plan (CMP) which describes their CM program, how it is organized, how it will be conducted, and the methods, procedures and controls relative to the HUD 3.0 systems. The content of the CMP shall define the technical and administrative guidelines for change control, status accounting, and audits of the total hardware and software configurations. The contractor shall establish a CM process to manage the software technical baseline and provide the Government a complete audit trail of plans, decisions and software design modifications. The Contractor will submit electronic engineering change control documents for DD Form 1692 Engineering Change Proposal (ECP), DD Form 1695 Notice of Revision, and DD Form 1696 Specification Change Notice. The CMP is a project deliverable.

The Government provided and maintained HUD 3.0 System and major component Performance Specification and ICD shall represent the HUD 3.0 Functional Baseline. The Contractor shall allocate the requirements stated in the functional baseline, with Government approval, down to individual draft Product Baselines prior to commencement of testing. The final Product Baseline shall be established for the HUD 3.0 at the successful completion of all testing including the final Production Qualification Test (PQT) and the Physical Configuration Audit (PCA)/Functional Configuration Audit (FCA). The Product Baseline shall be maintained by the vendor and provided to the Government as a project deliverable.

The Product Baseline is defined by the system, spare parts lists, and specifications down to the spare parts level, which shall all be in vendor formats.

The vendor shall submit Performance Specifications for the system and its major components that capture the performance of their fieldable HUD 3.0 design. Following completion of PCA and the final operational evaluation, the HUD 3.0 IPPT shall finalize the performance specifications. These specifications shall become Government documents and may be used in conjunction with the contractually required spare parts ICDs to support competitive procurement of spared items during the life cycle of the proposed HUD 3.0. The Performance Specifications are a project deliverable.

Any changes to the Product Baseline shall result in a common configuration for Government operational use and maintenance activities that provides interchangeability and interoperability to the spare replaceable part level. The Product Baseline shall be documented in the vendor’s configuration status accounting database. Any changes to the Product Baselines shall be made via ECP and shall identify any impact to the Government controlled Functional Baseline and ICD. Changes to each system’s software configuration baseline shall be properly identified, recorded, evaluated, approved or disapproved, incorporated and verified as appropriate IAW MIL-HDBK-61A and EIA-649. For each serial numbered system, the allocated baseline will include the relevant functional and product baseline, and any discriminating information down to the spare level (serial numbers, item revision and/or lot number, software/firmware versions, date of manufacture).

For all applicable engineering documents, dimensioning and tolerances shall be IAW ASME Y14.5-2009 or equivalent. Electrical characteristics and performance parameters of parts, modules, assemblies, and units shall be expressed as numerical values with tolerances specifying upper and lower (or maximum and minimum) limits. Drawings and all drawing associated files shall not contain any copyright or proprietary markings and shall be in CAD format, PRO/Engineer preferred. Specifications shall be compatible with Windows 10, and Microsoft Office 2013 products.

The contractor shall prepare and submit Interface Control Documents/Drawings (ICDs) at the spare part/assembly-level that assure 100% form, fit, and function interchangeability for the fieldable HUD 3.0 design. The HUD 3.0 ICDs are a project deliverable. The ICDs shall contain sufficient information to permit successful completion of the FCA and sufficient information to enable development of interoperable systems. The ICDs shall include, but are not limited to:

• Configuration and interface dimensional data applicable to the envelope, mounting and interconnection of the related items

• Complete interface engineering requirements (e.g. mechanical, electrical, electronic, optical, human) which affect the physical or functional characteristics of co-functioning items

• Any other characteristics, including material and finishes, which cannot be changed without affecting system interfaces or interfering down to the spareable level

• Complete list of software commands and protocols required to facilitate communication between the HUD 3.0 end items

The list of ICDs to be supplied will include, but is not limited to:

• All physical, human-systems interface (HSI), data, power, other interfaces between components, equipment on the Soldier

• All physical, HSI, data, power, other interfaces between Soldiers and Squad-organic equipment

• All data, voice interfaces between Soldiers

The vendor shall host and support an FCA for the HUD 3.0 down to the spareable level that successfully completes qualification testing. The FCA shall also include any special and common tools, and fixtures required to support/sustain the HUD 3.0. The FCA shall include all hardware and software developed for this project and any hardware or software that is to be modified as a result of this project. The vendor shall prepare an FCA Plan that shall be approved by the IPPT prior to the commencement of the FCA.

The HUD 3.0 FCA Plan is a project deliverable. The FCA shall be conducted no later than 60 days after the contractor submits the final FCA Plan, and shall be conducted on all interface, mating and interconnection dimensions. In the event the audit finds evidence the drawings do not adequately represent the equipment design and details of construction, acceptance of the equipment on order may be stopped until corrective action acceptable to the Government has been accomplished. The vendor shall prepare an FCA Report as a project deliverable recording the results of the FCA.

For all requested configuration changes, the contractor shall prepare and submit ECPs, Value Engineering Change Proposals (VECPs), and Requests for Variance (RFVs) to the IPPT for concurrence. A separate ECP shall be submitted for each engineering change that has its own distinct objective and is against a Government approved baseline, with appropriate Notices of Revision, Specification Change Notices, and technical manual change pages, as necessary in accordance with the CMP. The vendor shall include a tolerance analysis as backup data for all configuration control document submittals. Each configuration control document submitted is a project deliverable.

The vendor shall conduct engineering analyses, studies, and maintenance/supply support related to the repair and/or improvement of the HUD 3.0 as Technology Insertion Engineering Change Proposals (TIECP) as necessary. These analyses and studies may be used to implement improvements under this contract to the performance, quality, and maintainability of the systems and/or related maintenance equipment. The Government will define the analyses, studies, or maintenance support to be conducted.

The vendor shall develop a Statement of Work that includes all related engineering, program management, quality, and logistics tasks, and specific pricing, required to implement the repair/improvement effort. Task orders will be awarded on an as needed basis after the Government approves the repair/improvement Statement of Work and an agreement is reached on a negotiated price. The TIECP will be priced as a CLIN on the contract and will be ordered if deemed in the best interest of the Government.

The vendor shall ensure that the HUD 3.0 presents no uncontrolled safety hazards to operators or maintainers, and shall submit a Safety Assessment Report (SAR) for the HUD 3.0 that identifies all safety features of the system, specific controls or precautions to be followed during use, and shall provide verification of compliance to safety requirements identified in the SOO. The vendor shall provide updates to the SAR for all configuration changes that occur. If toxic/hazardous materials are utilized, the contractor shall provide the technical information required to complete Part II of the DRMS Form 1930, Hazardous Waste Profile Sheet. The HUD 3.0 SAR is a project deliverable.

The SAR shall identify toxic materials used in the design and production of the systems and components, any possible alternative materials, and recommended actions to eliminate or reduce the use of hazardous materials. The SAR shall address any exposure concerns to personnel during operational or maintenance procedures to include fabrication, transportation, setup and tear down, or resulting from damage to the equipment. The vendor shall identify any material used in the system design that requires disposal as a hazardous waste. Radioactive material shall NOT be utilized in the system design and production without prior approval by the Government. The SAR shall specifically describe control measures taken to ensure that the hardware is free of any radioactive materials, including optical glass and lens coatings.

The vendor shall schedule sufficient time in the program schedule to permit a safety inspection of the system by the Government prior to Soldier involved technical or user testing and associated training, or project completion. The inspections will be used to verify the information contained in the SAR. The vendor must allow sufficient time to correct any unresolved high or medium risk hazards prior to testing or delivery of the system to the Government.

The vendor shall obtain a Common Access Card (CAC) sponsored by the US Army HUD 3.0 Project Officer. Once the CAC has been issued, CECOM Directorate for Safety via the COR/COTR will provide the vendor with the proper account information for entry into the eHATS system. The vendor shall enter all system hazards into the CECOM Hazard Tracking System (eHATS), located on-line at:

https://cecomsafety.apg.army.mil/safety/ehts/visor_frames_list.asp. The hazard tracking log created from this site shall be attached to the SAR.

The contractor shall implement a hazardous material and pollution prevention program ensuring compliance with all Local, State, and Federal laws.

The sensitive nature of these systems require constant surveillance and tracking during shipping IAW DoD 4500.9 Part II Transportation Regulation, AR 190-51 Chapter (3) Paragraph 3-6. This AR is the overriding controlling authority. The following documents provide additional guidance: AR 710-2, AR 735-2, DA Pam 710-2-1, and DOD 5100.76-M (Physical Security of Sensitive Items).

The Packaging and Labeling requirements shall be in accordance with MIL-STD-129 and MIL- STD-130, respectively, for commercial packaging of similar items. Marking and labeling shall comply with DFARS Clause 252.211-7003 (c)(1) regarding Item Unique Identification (IUID). The HUD 3.0 shall be marked externally with the NSN, part number, contractor name, XX/XXX-YY designation, production date, serial number, and IUID. The HUD 3.0 shall be marked in compliance with the IUID standards outlined in MIL- STD-130 using construct #2. Markings shall be designed to be legible and permanent for the entire life of the system. The HUD 3.0 transit/storage container shall be marked with the NSN, part number, and serial number IAW MIL-STD-129.

The vendor shall submit a preliminary Production Manufacturing Plan (PMP) for HUD 3.0 production systems at PAC, and shall update the PMP prior the CS #4 BRR. The PMP is a project deliverable. The plan must provide sufficient narrative to enable an evaluation of the vendor’s ability to produce the HUD 3.0 at the rates required as part of this project and shall address the following:

• Manufacturing layout (including methods, manufacturing/test equipment, manpower)

• Production rates (initial rate, normal monthly rate based on 1 shift/8 hours per day/5 days a week, minimum monthly economical rate, and maximum monthly production capacity)

• Ramp-up activities, equipment/production station investment, and lead time needed to achieve normal production and surge production rates

• Identification of potential bottlenecks and limiting factors to production

• Existing manufacturing facilities

• Use of subcontractors and/or partners, both domestic and offshore, to provide components and/or subassemblies at production rates (initial monthly, normal monthly, minimum economical, maximum monthly, surge)

• Funding – When materials are to be ordered

• Testing – Procedures, failure reporting, analysis and trends

• Production - Manufacturing screening, product assurance, production control, yield thresholds, assembly flow charts

• Logistics – Manpower, support/test equipment, spares, Bill of Materials list for product baseline configuration with Original Equipment Manufacturer part numbers & supplier reference, training materials, technical manuals, critical processes, receiving inspection requirements

• Design – Requirements, traceability to specifications and testing, BIT/BITE, engineering release plan, design reviews and release process

• Management – Overall product strategy, personnel required, data management, risk, production breaks

Section 6: Quality Control

The vendor shall establish, maintain, and operate a Quality Management System (QMS) for HUD 3.0 in accordance with ISO 9001:2015, or an equivalent quality system. The vendor shall ensure the provisions, practices and protocols of their QMS extend into and include HUD 3.0 and unique areas. The vendor shall maintain a calibration system in accordance with ANSI/NCSL Z540.3-2006 or equivalent to ensure that all test/inspection, measurement, and diagnostic equipment, including all accessories and ancillary test equipment, are properly calibrated, identified by appropriate labeling, and are traceable to national measurement standards.

The vendor shall establish appropriate procedures for managing and controlling their supply base to ensure the quality and quantities of the materials/products and services provided do not adversely affect the program performance. Suppliers of key/critical components or processes shall be identified including names and contact information of key supplier personnel. The Government reserves the right to review/audit any suppliers of key/critical components.

The vendor shall maintain no fewer than five (5) vendor-owned HUD 3.0 systems as standards to support Government/vendor correlation testing for low light level (center resolution, luminance gain (2E-6 and 2E-4), saturation, equivalent background input, signal-to-noise ratio, halo, and modulation transfer function) and thermal…