V-22 IUs SOO_Final.pdf

DISCLAIMER - This INITIAL DRAFT Statement of Objectives (SOO) is for INFORMATIONAL PURPOSES ONLY to communicate likely program scope to facilitate a requests for information. It is NOT part of an RFP and no proposals should be submitted until and unless the Government issues a Request for Proposal. The content of any eventual RFP the Government issues may contain more specific Statement of Work requirements or otherwise differ from the below INITIAL DRAFT.

SOO Purpose

The Department of War (DoW) purpose and overarching objective of this SOO, is to acquire an obsolescence solution to the following Weapon Replacement Assemblies: Nacelle Interface Units (NIUs), Wing Interface Units (WIUs), Avionics Bay Interface Units (ABIUs).

SOO Background

The V-22 platform is facing significant obsolescence challenges with the following WRAs: the Nacelle Interface Units (NIUs), Wing Interface Units (WIUs), Avionics Bay Interface Units (ABIUs).

Nacelle Interface Unit (NIU): The left and right NIUs are interchangeable. Both NIUs process and monitor engine spark rate and fuel flow inputs. The NIUs also receive rotor resolver position inputs to be processed and send rotor azimuth control signals to the Vibration Structural Life and Engine Diagnostic (VSLED) system.

Wing Interface Unit (WIU): The WIU, located on top of the midwing forward equipment shelf, provides communication links between the MCs and the drive train, hydraulics, fire detection/warning system, electrical power distribution system, Blade Fold/Wing Stow (BFWS), rotor brake and the flight data recorder.

Avionics Bay Interface Unit (ABIU): The ABIU is located in the left avionics bay. The ABIU interfaces with the MCs via 1553B buses B1 and B2. The ABIU provides powershed relay control for selected avionics equipment. The ABIU also provides digital/discrete control and/or monitoring for systems/components located within the fuselage that are not 1553B data bus compatible.

SOO Period and place of performance

Period of Performance: The Government objective is for a two phased approach including design and development followed by production. Design and Development is anticipated to be a 3-4 year COST REIMBURSABLE (Award Fee or Fixed Fee) type contract to include Non- Recurring Engineering, Verification & Validation, Prototyping, and potentially LRIP beginning in FY29. Production will likely be a ~5 year FIXED PRICE (Incentive Fee) type contract to produce the required avionics A-kit and B-Kit shipsets (including spares) with fielding beginning in FY32.

Place(s) of performance: Contractor facilities (development, manufacturing), Government Systems Integration Lab(s), Government Organizational Level(s) (installation training/support).

SOO Scope

This SOO describes the objectives and expected outcomes for successful development, verification & validation, production, installation, and sustainment of modernized NIUs, WIUs, and ABIUs.

SOO Performance Objectives

Data Rights

The Government's objective is for the contractor to provide data rights which ensure affordable sustainment, including unlimited rights for interfaces. The Government’s objective is to have the option to acquire a complete technical data package (TDP), with unlimited rights, allowing for second source production. The Government’s objective is to have the option to acquire all software source code, libraries, build scripts, documentation, etc., allowing for post-acquisition software sustainment and capability insertion.

Modular Open Systems Architecture (MOSA)

The Government's objective is for the contractor to utilize a Modular Open Systems Architecture (MOSA) approach including the use of Future Airborne Capability Environment (FACE), Hardware Open Systems Technologies (HOST), and Sensor Open Systems Architecture (SOSA) standards. The Government’s objective is for the solution to undergo conformance verification against the FACE, HOST, and SOSA standards.

Model Based Systems Engineering (MBSE)

The Government's objective is for the contractor to utilize Model Based Systems Engineering (MBSE), leveraging a Government Reference Architecture (GRA) (if available), to support design and development. The Government's objective is for the contractor to deliver the model(s) to the Government with unlimited data rights to support sustainment and future modernization efforts.

Software Development

The Government’s objective is for the contractor to design/align software to the Future Aircraft Capability Environment (FACE) open standard. The software shall replicate the function of the existing IUs, while expanding its capability. The contractor shall evaluate the software architecture and determine the applicable Design Assurance Level (DAL) for each IU in accordance with DO-178C and provide rationale. The software developed shall be field loadable at the O-Level and packaged in a way that is able to be loaded on designated Navy/Marine Core and Airforce platform load devices.

Service Life

The Government’s objective is for the contractor to develop and manufacture the new WRAs to have a service life of >=15 years.

Airworthiness

The Government’s objective is for the contractor to ensure the upgraded V-22 WRAs and post-modification aircraft meet DoD Airworthiness Certification Criteria, as specified in MIL-HDBK- 516C.

Verification & Validation (V&V)

The Government’s objective is for the contractor to conduct full scope developmental verification & validation, including functional testing, MOSA conformance testing, environmental testing, shock and vibration testing, MIL-STD-704D testing, and electromagnetic environmental effects (E3) testing to ensure suitability for military flight operations.

Supply Chain Assurance

The Government’s objective is for the contractor to implement a robust supply chain assurance program for both hardware and software, including Supply Chain Risk Management (SCRM), Cyber Supply Chain Risk Management (C-SCRM), and counterfeit parts prevention.

Design & Development

The Government’s objective is for the contractor to design and develop a modern version of the impacted avionics WRAs which will provide legacy functionality, allow capability insertion, eliminate vendor lock, and allow affordable sustainment. The Government’s objective is for the contractor to reverse engineer (as required) functions & interfaces of the legacy avionics to ensure compatibility with the existing V-22 avionics system.

Obsolescence Risk Management

The Government’s objective is for the contractor to minimize obsolescence risk (e.g., technology/design refresh planning, select parts whose forecasted availability (predicted years to EOL) is five years or greater). The Government’s objective is for the vendor to conduct ongoing obsolescence risk management through the design and production phases to pro-actively manage risk throughout fielding of the redesigned WRAs.

System Integration

The Government's objective is for the contractor to act as the systems integrator, integrating the new WRAs with existing V-22 electronics, power, cooling, etc. The new WRAs must be compatible with existing V-22 systems such as the Flight Control Computers (FCCs) and Integrated Avionics Processor (IAP).

The contractor shall partner with the government in testing the IUs in a Systems Integration Lab (SIL) to demonstrate system performance in an aircraft representative environment.

Production

The Government objective is for the contractor to produce approximately ~436 shipsets (A kit and B kit) plus 25% (~109) spares.

Test & System Integration Lab (SIL) Assets

The Government’s objective is to have 6 shipsets available as test assets (3) and SIL assets (3).

Flight Testing

The Government’s objective is for the contractor to support flight testing, including instrumentation and data reduction/analysis.

Aircraft Modification & Installation Support

The Government’s intent is to perform an Organizational Level (O-Level) Install in order to support operational availability. The Government's objective is for the contractor to provide training & technical support in preparation for and during the initial installation year.

Logistics Product Support

The Government’s objective is for the contractor to design for supportability and provide documentation (e.g., Bills of Materials (BOM), Interactive Electronic Technical Manuals (IETMs)) and any peculiar support equipment required for product support. The Government’s objective is to use existing common hand tools, Special Test Equipment and Support Equipment to the maximum extent. The Government’s objective is to have logistics product support until ~2055

Operating Constraints

Classification & Sensitivity

This acquisition is Controlled Unclassified Information (CUI), but will receive and generate sensitive covered defense information (FAR 252.204-7012 Safeguarding Covered Defense Information and Cyber Incident Reporting).

Travel

The Government’s objective is for contractor personnel to travel (as required) to support key meetings during design and development, Government SIL/FLIGHT testing, and installation training/support