Statement_of_Work.docx

Contract Number: TBD Task: F-15E Mixed Reality (MR) Unclassified Flight Simulator Date: Current as of 17 June 2019

4 TS, Seymour Johnson Air Force Base

STATEMENT OF WORK

1.0 Scope of Work

1.1 The contractor shall provide all personnel, supervision, logistics, tools and materials to modify the Virtual Reality (VR) equipment at Seymour Johnson Air Force Base (SJAFB) in accordance with the tasks and objectives found in this Statement of Work (SOW).

1.2 Background:

1.2.1 The purpose of this task is to obtain solutions to design and implement a Mixed Reality (MR) F-15E flight training upgrade utilizing the current twelve (12) Virtual Reality (VR) simulators.

1.2.2 The F-15E Formal Training Units (FTUs) have a need for students to learn by utilizing current technology in a Virtual Reality and Mixed Reality space in order to enhance student learning to reduce student re-fly rates.

1.2.3 F-15E FTU aircrew have limited time to practice and understand 3D concepts due to high demand of the Mission Training Center (MTC) simulators and syllabus timeline and pre-requisites. This forces students to just be introduced to flight tasks weeks before accomplishing them in the aircraft. MR/VR Simulators would allow increase training effectiveness of our FTU students by practicing hours prior to their syllabus flight.

2.0 Deliverables

2.1 Hardware

2.1.1 Contractor shall provide MR goggle capability in order to see Virtual reality outside the “canopy” and real world inside the cockpit so a user can see their hands, kneeboard cards and the switches they are utilizing with simulation above the cockpit railing, with minimum resolution of 1920X1200. This will be done via modification of existing commercial items. The demarcation between Virtual Reality and Real world will be at the canopy railing and/or where the real world starts in order for aircrew to see their hands and interaction with the touch screen (or similar method of input – see 2.1.3 below).

2.1.2 Contractor shall provide the capability for users to see (real or virtual) both inside and outside the cockpit, their hands, kneeboard cards and the switches they are utilizing. FCP and RCP shall be linked via software, but not physically.

2.1.3 Contractor shall provide a method of input (e.g. similar to a touchscreen in addition to/or simulated switch panels) capable of simulating the front cockpit (FCP) and rear cockpit (RCP) of an F-15E Strike Eagle at the unclassified level in real time accurately. Minimum functional input devices in the cockpit are detailed in Appendix 8.2 below. The listed input devices shall have the Ability to perform as designed in the F-15E. Contractor shall assume any F-15E cockpit input devices not listed below shall still be provided, however, they are not required to function. The input mentioned above devices will allow students the ability to build muscle memory for their flight training. All locations of devices shall be determined and accurately replicated using commercial/unclassified sources. For example, after takeoff, students will “touch” the landing gear handle on the touch screen (or other provided input method) as found in the same location of the actual aircraft to bring the landing gear up. This requirement allows our students to develop constructive skills and develop muscle memory within the F-15E FCP or RCP. If a touchscreen is the solution proposed, the touch screen will be in the physical side of MR so as to facilitate the students using their real hands for interaction with the touch screen. The size of the screen shall be a minimum of 21” diagonal but shall not exceed 27” diagonal.

2.1.4 Correctly mapped Hands on Throttle-and-Stick (HOTAS) to simulate the F-15E HOTAS in both the FCP and RCP. Throttle and stick shall be provided by Government. Contractor shall upgrade/map existing HOTAS to specific actions and HOTAS shall be mapped accurately.

2.1.5 System requirements:

2.1.5.1 Visibility resolution of an F-15E

2.1.5.1.1 Detection: 2.0 - 7.0 Nautical Miles (NM)

2.1.5.1.2 Recognition: 1.0 - 2.0 NM

2.1.5.1.3 Identification: 0.0 - 1.0 NM

2.1.5.2 Visibility resolution for pixel criteria

2.1.5.2.1 Detection: 4 - 16 pixels across the target

2.1.5.2.2 Recognition: 16 -32 pixels across the target

2.1.5.2.3 Identification: no less than 32 pixels across the target

2.1.5.3 Sim Latency

2.1.5.3.1 Optimized to have a maximum Motion-to Photon latency of 20ms (maximum perceivable latency)

2.2 Software

2.2.1 The software shall have a user interface that enables unique user profiles which can be accessed by each student using a secure log-in user name and password. The unique user profiles shall track and collect all student data and store them into a Learning Management Software (LMS) for data analytics, which shall be provided by the Government. At a minimum this software shall collect student name, mission set (scenario), and time (hr:min) spent within each scenario.

2.2.2 The flying software shall mimic the F-15E Aerodynamic Flight Models to the max extent. The flying software shall mimic the F15E feedback and aerodynamic results to pilot inputs to best simulate an F-15E flight model. This will be obtained utilizing a 360 degree field of view.

2.2.3 The software shall be capable of linking four (4) or more jets in the same virtual reality gaming space that is built with Distributed Interactive Simulation (DIS) code and compatible with other DIS networks such as the USAF Distributed Mission Operations Network.

2.2.3.1 Each of the four (4) jets shall include the ability to add flying ‘trails’, indicating previous flight path, with minimum of two selectable colors (red and blue). This shall include the capability for the instructor/admin to review the trails with the student.

2.2.3.2 Ability to link FCP and RCP together to simulate that they are flying in the same jet within the same VR environment.

2.2.3.3 Ability to select either FCP or RCP on startup or toolbar so the user can start or switch different crew positions to practice both as required. This would include the ability such as the touch screen displays (or similar input method) as discussed in Paragraph 2.1.2 for either a FCP or RCP for maximum options with the simulators.

2.2.3.3.1 To further explain “maximum options”, use the example of 4 MR simulators in the same virtual space. There could be 2 pilots and 2 Weapon Systems Officers (WSOs) training, 3 pilots and 1 WSO training etc. Having the ability to select which cockpit the touch screen will display will allow for the multiple student configurations.

2.2.3.4 The software shall allow fly, record, and playback up to 4 or more simulators. During playback, the capability for multiple perspectives of the events to include Pilot or Weapons Systems Officer (WSOs) cockpit view, and a free-looking camera perspective to run around the space of the recorded fight to maximize student understand and learning. Examples include: Gods Eye view, Stadium view, Geospatial Static View, and view from an inputted range from a particular aircraft with ability to move around the aircraft at that range.

2.2.3.5 Each simulator shall have an option to toggle on and off a Helmet Mounted Display (HMD) overlay on the goggles to allow similar functionality to the F-15E Joint Helmet Mounted Cueing System (JHMCS). Night Vision Goggle (NVG) capability is NOT required.

2.2.3.6 Inside the recorded flight replay system, the software will allow one (1) student/jet to re-fly the exact same mission. This will allow the student to watch a particular engagement (AKA, a “recorded fight”) and then execute the engagement against recorded bandit(s). This will allow the student to see how certain mechanics/actions s/he inputs affect the geometry and the results of the fight. For example:

2.2.3.6.1 Student A watches an Offensive Basic Fighter Maneuvering (OBFM) fight against another F-15E.

2.2.3.6.2 Student A then starts at the beginning of the fight, while now “flying” the offensive F-15E. The defensive jet does not change its profile. The student flying the offensive jet will attempt to recreate the fight they just saw. They can evaluate whether their actions were correct compared to the pre-recorded fight.

2.2.3.6.3 If not, they have the ability to watch the pre-recording again, practice the fight again until the practice matches the “perfect fight” recording.

2.2.4 The software shall include Janes Weapon Engagement Zone (WEZ) and weapon simulation for both Air to Air (A/A) and Air to Ground (A/G) weapons for the F-15E inventory.

2.2.4.1 At a minimum these weapons shall include:

2.2.4.1.1 A/A: AIM-9M, AIM-9X, AIM-120B, AIM-120C, AIM-120C5.

2.2.4.1.2 A/G: BDU-33, BDU-50, MK-82, MK-84, GBU-12, GBU-54, GBU-24, GBU-38, GBU-31.

2.2.5 The software shall include relevant world maps with visual references to include best available resolution and instrument approaches for the local area around Seymour Johnson AFB, Mt Home AFB, RAF Lakenheath as well as their appropriate bombing ranges and standard alternates, utilizing Commercial Off The Shelf environments.

2.2.5.1 Ranges: Dare County Range (R-5314), BT-9 and BT-11 (R-5306A), Townsend (R-3007), Poinsett (R-6002), Gamecock C, Farmville MOA, Bulldog MOA, Buckeye MOA, Sailor Creek Range (R-3202), Juniper Butte (R-3204A/B), Holbeach (EGD207), Donna Nook (EGD307), Garvie Island (EGD803)

2.2.5.2 Alternates with working instrument approaches and ground references: KNKT, KLFI, KNTU, KSSC, KISO, KBOI, EGUL, EGUN, KHIF, KTWF, KLVS

2.2.6 The ability to make multiple mission types shall be included with the software for student use.

2.2.7 The system shall be available to upgrade in the future to include capturing student biometrics recording output as well as all student data.

2.2.8 Contractor shall provide standard business hour customer service support for twelve (12) months for technical assistance for all software/hardware concerns. Contractor shall provide a Point of Contact and phone number within ten (10) days of successful installation of upgrade.

2.2.9 Contractor shall perform all modifications on Seymour Johnson AFB.

3.0 Deliverable Distribution / Data Rights

3.1 Government purpose rights shall be provided for all modifications and deliverables of technical data and computer software funded under the transaction agreement for at least a five-year period. Student Data is solely the property of the Government. Reference Federal Acquisitions Regulation (FAR) section 52.227-19 “Commercial Computer Software License” and Defense Federal Acquisitions Regulation (DFAR) section 252.227-7015 “Technical Data--Commercial Items” of the solicitation clauses for further details.

4.0 Deliverable Schedule

4.1 All current systems can be shut down for training for a maximum of 30 days

5.0 Government Furnished Information, Equipment and Facilities

5.1 Records Documents and Work Papers

5.1.1 All records, files, documents and work papers provided by the Government or generated in support of this work effort are Government property and shall be marked, maintained, and disposed of in accordance with Government policies and publications. The government shall provide the following documents as required to:

5.1.1.1 Any available technical documentation related to the unclassified system of the F-15E identified in Paragraph 2.0. Documentation can include, but is not limited to: technical manuals, system level drawings, wiring diagrams and unclassified weapons systems.

6.0 Travel

6.1 Travel shall be required to Seymour Johnson AFB, NC to address the schedule in section 4. Additional travel is permitted but shall not be incorporated into the price of the quote. The contractor shall provide the Contracting Officer at least fifteen (15) calendar days of advance notice for planned travel, to include purpose, agenda, and any specific support required of the Government.

6.2 Travel must be pre-approved by the Contracting Officer (and pre-coordinated through the 4th Training Squadron).

6.3 An electronic trip report shall be prepared and sent via email for all travel to government/contractor facilities. The report shall contain as a minimum: travelers, site visited, purpose of visit, details of work accomplished, problems encountered, and final effort status and identify any remaining deliverables.

7.0 Security Requirements

7.1 The contractor shall take appropriate measures to ensure the protection of data to the specified level for the duration of the contract.

7.2 All efforts required for this task are expected to be UNCLASSIFIED and shall not require contract personnel to obtain a security clearance.

7.3 The contractor shall follow all appropriate security procedures regarding identification badges, entry control cards, and vehicle passes.

7.4 The contractor must return all issued badges and passes to the Government at the end of the contract before final payment is made.

7.5 The contractor shall adhere to all security measures IAW Homeland Security Presidential Directive 12 (HSPD-12).

8.0 Appendices

8.1 Acronyms and Abbreviations:

A/A -- Air to Air A/G -- Air to Ground ARO – After Receipt of Order HMD -- Helmet Mounted Device FCP – Front Cockpit JHMCS -- Joint Helmet Mounted Cueing System JPAS – Joint Personnel Adjudication System MTC – Mission Training Center (Boeing 360 Projector Simulator) RCP – Rear Cockpit WEZ -- Weapon Engagement Zone WSO -- Weapons Systems Officer (Rear Cockpit crew position of F-15E)

8.2 Minimum Functional Input Devices

FCP Main Panel:

Lock/Shoot Lights Head up display combining glass Upfront control panel Master Caution light Fire Warning/Extinguishing Panel Multi-Purpose Display (MPD) Hydraulic pressure indicators Engine monitor indicator Fuel quantity indicator Jet fuel starter control handle/brake hold switch Multi-Purpose Color Display (MPCD) Armament control panel Landing gear control handle Pitch ratio select switch Pitch ratio indicator Emergency brake/steering control handle Caution lights panel Arresting hook control switch Flap position indicator Emergency gear landing handle FCP Left Console:

Control augmentation system control panel Sensor panel Fuel control panel FCP Right Console:

Environmental Control System (ECS) panel Air condition control panel Engine control panel RCP Main Panel:

Warning/caution/advisory lights panel

MPD

MPCD

Landing gear position lights Flap position indicator Upfront control panel RCP Left Console:

Sensor Panel RCP Right Console:

Countermeasure dispenser Tactical electronic warfare system

Electron menus for MPD/MPCD:

Horizontal Situation Indicator (HSI) Attitude Situation Indicator (ADI) RADAR Warning Receiver (RWR) Air to Air Radar (A/A RDR)

8.3 Pictures of current set-up

Picture #1:

Picture #2:

Attachments:

1. List of Current Equipment image2.jpeg image1.jpeg