F-35 RADAR Model for use in the Joint Simulation Environment

The Joint Simulation Environment (JSE) is supporting ongoing F-35 Developmental and Operational Test. In support of these tests, the APG-81 RADAR Simulation model needs to keep pace as the aircraft capabilities are upgraded. This model needs to be used in conjunction with the F35 In-a-Box (F35 IAB) and/or a Prime Mission Equipment ICP in the NAWC AD Hardware in the Loop (HWIL) facility.

The Government is seeking sources who can leverage the F-35 RADAR models currently being developed by for inclusion in F35 IAB by Northrop Grumman Corporation (NGC). The result must include using these builds as code and wrapped into a standalone executable to deliver insight to validate the model's level of fidelity as required.

This F-35 RADAR model must interface with the prime mission equipment (PME) F35 Integrated Core Processor (ICP) and the F35 In-A-Box (F35 IAB) rehosted OFP simulation. This model, in support of F35 IAB, must execute external of the F35 IAB hardware and have an upgraded interface to the EW Model. In support of the ICP aircraft hardware, this model must also execute external but require additional aircraft-like' HWIL interface hardware to connect to the ICP.

The contractor needs to be intimately familiar with the aircraft RADAR system, have access to data for the system and the rights to use that data including but not limited to:

• its interfaces (e.g., between RADAR and EW subsystem);
• timing requirements

in order to build this model appropriately to be integrated with both the existing F35 IAB and the aircraft ICP.

The completed model must:

• Fulfill Block 3 and C2D2 APG-81 RADAR system capability moving forward
• Match LM delivered RADAR model capability as built into F35 IAB
• Execute in hard real time on COTS hardware and ICP HWIL TR2 and TR3 aircraft interfaces through aircraft-like' hardware
• Execute in hard real time on COTS hardware and interface with an externalized' F35 in-a-box wrapper interface
• Define/validate RADAR/EW ICD changes required to enable a pulse level EW model
• Synchronize with F35 IAB and ICP lab system configurations

Responses shall be sent by email to thomas.kracinovich@navy.mil and martha.johnson@navy.mil.

Responses shall include technical information describing a proposed solution including information regarding the required access to data and the rights to use it. The response should also include a price ROM and a lead time ROM.

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes. It does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the Navy is not at this time seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the interested party's expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will be synopsized on beta.SAM Website. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement.