Request for Follow-on_Saudi CH47F-UH60M FTDs_Final_11Aug2026.pdf

UNCLASSIFIED

Request for Information (RFI)

11 August 2026

Royal Saudi Land Forces Aviation Corps (RSLFAC) CH‑47F and UH‑60M Flight Training Devices (FTDs)

1.0 Introduction & Purpose

The Army Contracting Command (ACC), in coordination with the Capability Program Executive Simulation, Training, Test & Threat (CPE ST3), is issuing this Follow-On Request for Information (RFI) to refine requirements for the Royal Saudi Land Forces Aviation Corps (RSLFAC) CH-47F and UH-60M Flight Training Devices (FTDs). This RFI follows the previously published Sources Sought Notice (SSN) and seeks clarification only in areas where SSN responses revealed gaps or inconsistencies.

This effort includes contractor-led interoperability between the new CH-47F FTD and two legacy training devices: the CAE UH-60L Operational Flight Trainer (OFT) and the containerized, mobile trailer–based Boeing AH-64Ev4 Longbow Crew Trainer (LCT).

This mobile configuration may introduce additional physical and integration challenges beyond the standard technical interfaces.

This RFI is for information only and does not constitute a solicitation.

2.0 Background

The RSLFAC SSN issued on 11 Jun 2026 requested information regarding the development of two Level-7-equivalent FTDs and required vendors to submit detailed descriptions of capabilities, past performance, subsystem experience, Contractor Logistic Support (CLS) approach, environmental hardening, and Rough Order of Magnitude (ROM) pricing. SSN responses sufficiently addressed many areas; however, several critical items were not fully understood or consistently addressed, particularly the full technical scope of contractor-led interoperability, the requirement for the contractor to obtain all Original Equipment Manufacturer (OEM) interface data, technical data, protocols, and licensing (no Government Furnished Information will be provided), integration considerations for a mobile, containerized AH-64Ev4 LCT, the required open architecture to support future simulator integration, long-lead procurement timelines, build location assumptions, Agama, visa, and in-country access requirements, and the hybrid Agile/Waterfall execution model required by the Government. This RFI seeks concise information to refine specific requirements before finalizing the solicitation.

3.0 Requested Information from Industry

Industry is requested to provide responses to all questions below. Responses should be factual, concise, and reflect the company’s actual capability and program approach.

1. Describe your detailed technical approach to achieving interoperability between the CH-47F FTD, CAE UH-60L OFT, and Boeing AH-64Ev4 LCT. Your response must clearly explain:

2. The specific architecture, protocols, Federated Object Models (FOMs), gateways, message translation layers, and middleware you propose for achieving real time interoperability across all three devices.

a. How your design accommodates the containerized, trailer-based AH-64Ev4 LCT, including any unique constraints introduced by mobile configuration (networking, cabling, access, power, environmental stability).

3. Your plan for obtaining all interface definitions, data exchange protocols, software, technical data, and licensing required from CAE, Boeing, or any other OEM

4. The Government will not provide Government Furnished Information (GFI). Describe your complete plan for obtaining all OEM interface definitions, data-exchange protocols, software, technical data, and licensing required from CAE, Boeing, or other sources. Include timelines, assumptions, risks, mitigation strategies, and OEM cooperation expectations.

5. Confirm whether you currently have enforceable agreements (Nondisclosure Agreements, Associate Contractor Agreements, licenses) with both CAE and Boeing for interoperability. If not, describe how and when you will obtain them.

6. Provide the major cost drivers behind your interoperability ROM.

7. Indicate whether your build approach is fully CONUS, partial CONUS with final assembly in Saudi Arabia, or fully in-country. Explain schedule implications, facility requirements, and related risk.

8. Identify major long-lead items and describe procurement timelines, supply-chain constraints, and recommended Government actions to reduce schedule risk.

9. Provide a realistic timeline for interoperability integration.

10. Identify any requirements that remain ambiguous, unpriceable, or unnecessarily risky, and provide suggested clarifications.

11. What is your honest assessment of the hybrid Agile/Waterfall development approach? How would you enable greater Government participation and insight, and where does Agile add value versus where Waterfall is required for hardware-based development?

12. Before cockpit hardware exists, what systems do you test software against (System Integration Lab, desktop simulation, emulators, reuse baselines)? Describe the progression from desktop → testbed → cockpit → Acceptance Test Procedures/Factory Acceptance Test.

13. How do you prevent scope-creep across both simulators, especially under hybrid Agile and OEM-dependent interoperability? Describe how you maintain requirements baseline control and manage changes.

14. Describe your full plan for obtaining all in-country access, work visas, Agama clearances, and Living Quarters Allowance for personnel.

15. The Government anticipates a Firm-Fixed-Price contract structure. If you believe an alternative contract type or segmentation would reduce risk or improve execution (e.g., for OEM-dependent interoperability), provide a rationale. The Government will make the final determination.

16. Describe any existing, relevant capabilities that you would be prepared to demonstrate to the Government at your facility on relatively short notice (e.g., within 30–60 days). Identify which systems, subsystems, or software components would be part of the demonstration (such as a live interoperability gateway, an existing FTD, a Modular Open Systems Approach (MOSA) compliant software environment, or other applicable capabilities). Note that this request is for market research purposes only and does not constitute a formal demonstration requirement

4.0 Response Instructions

The response to this RFI, including any capabilities statement, shall be electronically in either Microsoft Word (docx) or Portable Document Format (PDF), via email to:

Ms. Rosa Rivera (Contract Specialist) rosa.rivera53.civ@army.mil, Mr. Jason Holden (Contracting Officer) jason.n.holden.civ@army.mil , and Mr. David Coe (APM) david.e.coe.civ@army.mil.

Submit response no later than 12:00 Eastern Standard Time (EST) on 25 August 2026 and reference this RFI number in subject line of e-mail and on all enclosed documents.

Information and materials submitted in response to this request WILL NOT be returned.

DO NOT SUBMIT CLASSIFIED MATERIAL.

Disclaimer

THIS RFI IS FOR INFORMATIONAL PURPOSES ONLY. THIS IS NOT A REQUEST FOR

PROPOSAL (RFP), REQUEST FOR QUOTE (RFQ), OR INVITATION FOR BID (IFB) TO BE

SUBMITTED. IT DOES NOT CONSTITUTE A SOLICITATION AND SHALL NOT BE CONSTRUED

AS A COMMITMENT BY THE GOVERNMENT. RESPONSES IN ANY FORM ARE NOT OFFERS

mailto:rosa.rivera53.civ@army.mil mailto:jason.n.holden.civ@army.mil mailto:david.e.coe.civ@army.mil

AND THE GOVERNMENT IS UNDER NO OBLIGATION TO AWARD A CONTRACT AS A RESULT

OF THIS ANNOUNCEMENT. NO FUNDS ARE AVAILABLE TO PAY FOR PREPARATION OF

RESPONSES TO THIS ANNOUNCEMENT. ANY INFORMATION SUBMITTED BY

RESPONDENTS TO THIS TECHNICAL DESCRIPTION IS STRICTLY VOLUNTARY.