Attachment__2_-_Statement_of_Objectives_(SOO)_for_SR20_(T-53)_P3D_Model.pdf

PDF 155 KB Posted

Attached to
T-53 Aircraft Training Model Federal contract opportunity
Solicitation number
FA700019QA074
Issued by
Department of the Air Force Headquarters Air Force Academy

About this file

Statement of Objectives

View the file

Other files for this federal contract opportunity

Other files attached to T-53 Aircraft Training Model, newest first.
File Type Posted
Industry_Questions.docx DOCX document
Updated_T-53_Aircraft_Training_Model_Combo.pdf PDF
-_DFARS_252.225-7020_Trade_Agreements_Cert.docx DOCX document
Industry_Questions.docx DOCX document
T-53_Aircraft_Training_Model_Combo.pdf PDF
Attachment__1_-_Brand_Name_Justification_&_Approval_(J&A)_Redacted.pdf PDF
Attachment__3_-_Provisions_and_Clauses.pdf PDF

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment #2

STATEMENT OF OBJECTIVES (SOO)

USAFA Cirrus SR-20 (T-53A)

12 June 2019

1. Purpose. To effectively transform USAFA’s airmanship training programs, the Academy’s Airmanship Next initiative requires a PREPAR3D-based (P3D) aircraft simulation model for the Cirrus SR-20 (referenced below as the T-53A).

2. Scope or Mission. There currently are no simulation models for the T-53A (with Perspective avionics suite) available for use in P3D; however, Airmanship Next requires a T-53A model be developed to support interactive and virtual-reality (VR)-based courseware development and training. Specifically, this model must include: 1) Accurate aerodynamic flight modeling for all phases of flight, to include left turning tendencies associated with low airspeed, high power setting, high Angle of Attack maneuvering; cruise; climb; descent; glide; stall; slow-flight; Chandelle; Lazy Eight; and abnormal procedures listed in the existing operations publications (e.g. landing without elevator control, flap failure, etc.); 2) Accurate USAFA cockpit replications and interaction with associated flight controls, switches, knobs, and buttons to support realistic aircraft appearance and functionality; 3) Realistic sounds; and 4) Accurate avionics and systems replication and functionality, to include realistic systems behaviors for abnormal procedures listed in the aircraft’s operating publication (e.g., engine failure/fire, electrical fire, and spin with Cirrus Aircraft Parachute System [CAPS] deployment).

3. Place of Performance. The Contractor is expected to deliver a model in accordance with the Key Performance Indicators detailed below. The Contractor will also be required to provide any modifications or improvements to the software in alignment with the standard software warranty for the development of a virtual reality simulator model.

Although the model may be developed at any location, performance verification activities shall occur at USAFA, CO on P3D-based systems; there is no expectation for USAFA personnel to travel to the Contractor’s location.

4. Background. USAFA's Airmanship Next initiative directly aligns with AETC's efforts to “revolutionize Air Force pilot training” via its Pilot Training Next (PTN) organization. USAFA’s and AETC’s PTN leadership and subject matter experts have committed to utilizing PREPAR3D as its core software for courseware development and training.

5. Key Performance Indicators (KPIs) for Cirrus SR-20 (T-53A).

5.1. Accurate aerodynamic flight modeling for all phases of flight

a. Straight, level, and un-accelerated flight modelling

(1) Threshold (T) ±5 Knots Indicated Airspeed (KIAS) for all altitudes, and power settings

(2) Objective (O) ±3 KIAS for all altitudes, and power settings

b. Climbs and descents (to include glide performance with a simulated seized engine/no propeller rotation and failed engine with a windmilling propeller) up to ~ 3000 fpm

(1) (T) ±8 KIAS for all altitudes, attitudes, and power settings

(2) (O) ±5 KIAS for all altitudes, attitudes, and power settings

c. Dynamic and abnormal maneuvering (to include Chandelle, Lazy eight, and stalls, in flaps zero, flaps 50 and flaps 100% settings) mirroring actual aircraft performance

(1) (T) ± 12 KIAS

(2) (O) ± 10 KIAS

5.2. Accurate USAFA T-53A cockpit replication and interaction from both the right-and left-seat cockpit positions.

a. Flight Controls, Handles, Levers, Switches, Knobs, and Buttons

(1) (T) All manipulate-able cockpit items modelled according to actual aircraft functionality. CAPS replication must include predicted aircraft behavior before and after chute deployment.

(2) (O) All manipulate-able cockpit and exterior inspection items modeled according to actual aircraft functionality. CAPS replication must include predicted aircraft behavior before and after chute deployment.

b. Displays, Indicators, Gauges, and Placards

(1) (T) All indicators, gauges and placards are displayed according to actual aircraft functionality.

(a) Same color scheme

(b) Same numbering scheme

(c) Same display characteristics

(2) (O) Same as above, and includes characteristics which improve impressiveness such as wear and tear comparable to operational fleet, glare, etc.

5.3. Realistic sounds

a. (T) Aircraft sounds are aircraft specific

b. (O) Aircraft sounds are provided as WAV/MP3 files along with model delivery

5.4. Accurate avionics and systems functionality

a. (T) All aircraft engine-/fuel-/oil-/electric-related, navigation, control, and performance instrumentation and displays respond timely and accurately to user inputs and/or selected scenarios for abnormal procedures (e.g., navigation display immediately shows accurate depiction of desired airspace after appropriate button or switch is engaged; engine-related instrumentation and displays indicate an engine failure after a console operator or pilot selects a pre-programmed scenario). See Section 10 (Avionics Details – T-53A & Garmin 1000) for desired button actuations and displays for the Garmin 1000.

b. (O) Same as above, and includes all display combinations for every emergency procedure scenario identified in the 557th Flying Training Squadron’s T-53A Technical Order and/or Checklist.

6. Additional Information.

a. The model must interface with all facets of P3D’s Sim Director functionality as stock models would (e.g., xml or C++ files for gauge interface), and FSUIPC add-on.

b. The contractor shall list all technical data, if any, in which the contractor has granted the Government data rights in a special licensing agreement and the Government shall use the data within the Government only, without releasing the technical data outside of the Government, as described in the clause at DFARS 252.227-7015, Technical Data-Commercial Items (Feb 2014).

c. The contractor will deliver engine and flight performance models for both the normally aspirated stock T-53 engine, and for any turbo-normalized, turbo-charged or enhanced T-53 engine and/or propeller modifications that mayoccur within 3 years from contract awarding.

d. Technical Orders and checklists referenced in this Statement of Objectives are available to the Contractor from the Government, upon request.

7. Product Management. The Contractor shall collaborate with USAFA subject matter experts to develop a working-group development schedule during the two weeks after contract award. This schedule, at a minimum, shall include one, two-day performance-verification engagement at USAFA, where USAFA subject matter experts and designated representatives will verify product performance. Additionally, the Contractor shall, at a minimum, manage/conduct a one-hour meeting with USAFA subject matter experts on a weekly basis, either in person or via telecommunications, to ensure aircraft modeling is accurate and prevent unnecessary delays. Finally, the Contractor shall manage/conduct a monthly status meeting with identified USAFA representatives in person or via telecommunications.

8. Avionics Details – T-53A & Garmin Perspective:

T-53A Cockpit

The items below will reference the T-53A’s GARMIN Perspective displays. The pilot’s display, on the left of the instrument panel, is the PFD (Primary Flight Display). The second display, on the right side of the instrument panel, is the MFD (Multifunction Display).

a. When BAT 2 master switch is positioned to ON, the PFD and MFD will turn

on. The PFD should display a screen with system readings, including Essential Bus Voltage. The voltage should read between 23-25.5 Volts during normal operation.

Interior Inspection, step 15: check Essential Bus Voltage between 23 to 25.5 Volts.

b. When the BAT 2 and BAT 1 master switches are positioned to ON, the MFD should turn on a display the startup screen. The MFD button on the far right will sequence the MFD to the FUEL page (the far right button on the MFD panel needs to operate in VR software).

G i 1000 Garmin Perspective

(1) Before Starting Engines, step 7: Fuel Selector – Set as ‘Required’ (the FMS/XPDR/COM/NAV control on the center console needs to operate in VR software, as well as the two MFD buttons on the far right of the MFD panel).

(2) Before Starting Engines, step 8: MFD – Select Engine Page (the button on the far right of the MFD panel needs to operate in VR software). Selecting the ENGINE page on the MFD should display all the engine instruments. The second MFD button from the right will be labeled FUEL; pressing the FUEL button will swap to the Fuel page from step 7 (the second button from the right needs to operate in VR software).

c. Display the combined Map and Engine page on the MFD: When the Engine page is displayed, selecting the ENGINE button on the MFD will switch to the Map and display the decluttered Engine Gauges on the left side of the MFD screen (the far left button on the MFD needs to operate in VR software).

d. Selecting multiple ranges on the Map: When the Map is displayed on the MFD, rotating the RANGE control on the center console will change the range mode of the Map (the RANGE control needs to operate in VR software).

e. Before Taxi checklist, Radios/Avionics – Set. Selecting/changing radio frequencies using the PFD controls.

(1) The COM1 and COM2 selections on the upper-right corner of the PFD can be selected using the COM control on the PFD panel (the COM control needs to operate in VR software). The COM control has two selectors: the larger knob controls the first three digits of the radio frequency, the smaller knob controls the last three digits of the frequency. Pressing the center of the COM control with change the selection from COM1 to COM2, and vice versa.

(2) To change a standby frequency to the active frequency, press <-> button above the COM control on the PFD panel.

(3) To adjust volume of the selected radio, rotate the VOL control above the COM control on the PFD panel.

f. Before Taxi checklist, Altimeters – Set: On the PFD, rotating the BARO control on the PFD panel will adjust the altimeter setting displayed below the altitude reading on the PFD (the BARO control needs to operate in VR software)

g. Before Takeoff checklist, step 4: Transponder – Set: There are several buttons on the PFD panel that lead to setting the Transponder: first, select the XPDR button (fifth button from the right), this will change the next set of buttons available on the PFD. Next, select the CODE button (fifth button from the right), also available is the BACK button (far right button) which will lead back to the previous button selections. After selecting CODE, the PFD buttons will switch to individual numbers, 1 through 9, then 0. Pressing four individual numbers, i.e. 1-2-3-4, will set 1234 into the transponder code. After pressing the fourth digit, the button selections will switch to the default selection. For this function, the following buttons need to operate in VR software: XPDR, CODE, BACK, and buttons for 1, 2, 3, 4, 5, 6, 7, 8, 9, and 0.

h. Caution and Warning Annunciators and Advisories: When a Caution (yellow annunciator), Warning (red annunciator), or Advisory (white annunciator) appears on the PFD, the far right button on the PFD panel will silence or clear the annunciator (this button needs to operate in VR software).

i. Ability to add and modify local waypoints to simulate our local training area (this does not have to be integrated into the Garmin Perspective FCP functionality)

j. FCP keypad functionality

k. Timer functionality

l. Engine Lean "Assist" display and functionality

m. Heading, Course, and Altitude Select with push (z-axis) snap function

File details come from the government source that posted it.