Request for Information (RFI) - Control Head Unit (CHU)

Request for Information (RFI)

Control Head Unit (CHU)

Classification

Original Set Aside: N/A

Product Service Code:  6610 – Flight Instruments

NAICS Codes: 334511 - Search, Detection, Navigation, Guidance, Aeronautical, and Nautical System and Instrument Manufacturing; 541330 – Engineering Services

Place of Performance: Army Contracting Command - Redstone 5678 Hicks Road, Redstone Arsenal, AL 35898, USA

Description

1. Notice

This Sources Sought is issued for informational purposes and market research only, it does not constitute a solicitation. The Government will not reimburse any company or individual for expenses associated with preparing/submitting information in response to this posting. The information provided may be used by the Government in developing its acquisition strategy, statement of work/statement of objectives, and performance specifications. Interested parties are responsible for adequately marking proprietary or competition sensitive information contained within their response.

1. Scope

The United States Government (USG) Capability Program Executive – Aviation (CPE AVN), Project Manager, Aviation Mission Systems and Architecture (PM AMSA) is conducting market research to identify possible sources capable of providing a form-fit replacement for the C-12601 control indicator (CI) and provide future growth to support future radio control software for communications and other applications. The USG is interested in information regarding control head system hardware, real-time operating systems, and software at a high Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL), with environmental qualification that support Air-Worthiness Release (AWR) as specified in Section 3.3(C).

1. 1. Background

The C-12601 CI is the current backup control head for the ARC-231 in Army Aircraft. The C-12601 serves as the backup control for Air Traffic Control (ATC) and other waveforms and is now approaching obsolescence. Nascent Next Generation Command and Control (NGC2) Army requirements are driving inclusion of onboard computational capabilities and available interfaces. Multiple software defined radios require use of an intelligent control head capable of hosting multiple software applications to support Design Assurance Level (DAL) and non-DAL applications.

2.2 Instructions to Potential Respondents

Respondents to this RFI must submit evidence which demonstrates their current ability to manufacture and sustain a control head unit if it has been demonstrated.

Respondents are asked to submit documents in easily readable pdf formats not to exceed 20 pages.

3. Requested Information

3.1 Company Information
 

1. Company Name
2. Address
3. Point of Contact (include phone number and email address)
4. CAGE Code
5. Web Page URL
6. State the country of ownership for the company
7. State whether the company is a non-traditional defense contractor

3.2 Capabilities

1. The USG is particularly interested in the physical characteristics and performance capabilities including:

1. Describe the configuration of your proposed solution. Include:

1. Operational startup time
2. Number and type of connectors (e.g., data/audio I/O, control, discrete, antenna, key fill, Ethernet, MIL-STD-1553, serial, RF). For consideration, respondents must include RS-485/422/232 serial control, full duplex 1553, and Ethernet
3. Chipset and computational resources (RAM, ROM, GPU, etc.)
4. Total weight and dimensions of proposed solution
   1. Display – 4.3 inches (minimum diagonal)
   2. Desired Dimensions
      1.  Width - 5.75 inches
      2. Height - 3.35 inches
      3. Depth - Not to exceed 3.9 inches (DZUS rail to connector opening)  
5. Any mounting hardware required (e.g., shock isolators, cooling plates, DZUS rails)
   1. For consideration, solution must be compatible with DZUS rail mounting
6. Maximum and nominal input power requirements of your proposed solution. Include voltage and current. For consideration, nominal power should not exceed - 14W (0.5 A @ 28VDC)
7. Cooling method(s) used on proposed solution
8. Supply chain considerations (e.g., countries of origin, obsolescence)
9. Operating System (e.g. Linux, VxWorks, Deos, etc.)
10. Describe any non-standard (non-conformant) material used in the proposed solution

1. Provide the Mean Time Between Failure (MTBF) of your proposed solution and describe how the MTBF was determined. Note that the Army considers MIL-HDBK-217F an unacceptable source for reliability estimates.
2. Describe how the system architecture of the proposed solution would operate functionally and physically in DoD Modular Open System Approach (MOSA).
   1. Describe any experience with the Hardware Open Systems Technologies (HOST) Technical Standard and how the standard can be applied to the controller solution
   2. Describe how the solution can be deployed
   3. Describe any past experience with similar Department of Defense (DoD) implementations and lessons learned from past experiences
   4. Describe knowledge and experience in product line engineering (PLE)
3. Describe how the developed solution would achieve Cyber Security Compliance IAW AR 25-2.
4. Describe the rights for the external hardware and software interfaces, external drawings, and technical manuals. If other than Government Purpose Rights (GPR), provide an explanation.
    

1. Compliance with Mandates
    

1. State the DO-178 design assurance level of the controller operating system and board support package and how it was obtained; if not already DAL C, provide a path to DAL C certification.
2. State the DO-254 compliance and how it was obtained
    

1. Human Factors IAW MIL-STD-1472H.  Include:
    

1. Sound levels of components such as cooling fan(s) included with your proposed solution.
2. Human factors characteristics of any displays included with your proposed solution.
   1. Daylight readability
   2. Describe compliance with MIL-STD-3009 for Type 1, Class A, Night Vision Goggles
3. How your proposed solution is designed for maintainability.
4. Prominence of knobs, buttons, and other hardware UI features that enable gloved operations in all required conditions.

3.3 Environmental and Electrical

Describe the controller’s compliance with the following environmental, electrical, and electromagnetic specifications. Describe the specific method(s) and procedure(s) utilized for test. Describe any specific test criteria (e.g. limits, duration, number of cycles). If not compliant, discuss future plans to gain compliance.

1. Requirements for the Control of Electromagnetic Interference (EMI) Characteristics of subsystems, equipment, all ancillaries for EMI / Radio Frequency Interference (RFI) requirements defined in MIL-STD-461G and MIL-STD-464D, as modified by ADS-37A-PRF, electrostatic discharge, and electrical bonding.

1. Requirements for the Interface Standard for Aircraft Electric Power Characteristics as defined in MIL-STD-704A-E and the performance specification utilized to determine compliance.

1. Requirements for Environmental Characteristics as defined in MIL-STD-810H for the following characteristics.

1. Altitude: Sea level to 50,000 ft pressure altitude (Method 500.6, Procedure I)
2. High Temperature Storage: +85°C (Method 501.7, Procedure I)
3. Low Temperature Storage: -62°C (Method 502.7, Procedure I)
4. Temperature Shock: -62°C to +85°C (Method 503.7, Procedure I-C)
5. Solar Radiation: (Method 505.7, Procedure II)
6. Dripping Rain (Method 506.6, Procedures III)
7. Humidity: (Method 507.6, Procedure II)
8. Fungus: (Method 508.8 for test, Guideline 4 of MIL-HDBK-454 for analysis)
9. Salt Fog: (Method 509.7)
10. Sand and Dust: (Method 510.7, Procedures I and II)
11. Explosive Atmosphere: (Method 511.7, Procedure I)
12. Acceleration: Procedure I ‘up’: 10.5g’s, Procedure II ‘up’: 7 g’s; all other directions 6g’s (Method 513.8, Procedures I and II)
13. Vibration: (Method 514.8, Procedure I, Category 14)
14. AH-64 Gunfire Vibration
15. Shock
    1. Functional: (Method 516.8, Procedure I)
    2. Crash Hazard: (Method 516.8, Procedure V)
    3. Bench Handling: (Method 516.8, Procedure VI)
    4. Transit Drop: (Method 516.8, Procedure IV)
16. Temperature/Altitude/Humidity: -54°C to +71°C, Sea Level to 20,000 ft pressure (Method 520.5, Procedure III)
17. Contamination by Fluids: (Method 504.3)

3.4 Items of Interest

The USG requests that responses also include the following information:

1. Plans for hardware and software improvement
2. Engineering Services capabilities
3. Lessons learned from past performance
4. Sustainment capabilities
5. Topology - how the software and hardware components are integrated
6. Production capabilities (monthly, yearly)
7. Diminishing Manufacturing Sources and Material Shortages (DMSMS) capability
8. Preliminary airworthiness assessment in accordance with the Army Military Airworthiness Certification Criteria (AMACC), Revision A. The AMACC is available from the following website:  https://www.avmc.army.mil/Directorates/SRD/TechDataMgmt/
9. TRL and MRL
10. Government Furnished Equipment (GFE) / Government Furnished Information (GFI) required

3.5 Data Rights, Licensing, Costs

The USG requests that respondents describe data rights associated with software code to include executable code, computer databases, computer software documentation, models (e.g., SysML) source code, code listings, design details, processes, flow charts, and related material that would enable the software to be reproduced, recreated or recompiled. PEO Aviation also requests that respondents include licensing costs, including developmental and production licenses, for all components.

           

3.6 Schedule

The USG requests that respondents provide a program schedule that includes a timeline for delivery of minimum purchase quantity systems will be available for lab and mission system integration and overall system lead times.

3.7 Costs and Budgeting

Due to the budgetary importance of understanding technology related costs, the USG requests respondents provide Rough Order of Magnitude (ROM) estimation by quantity range (e.g. Qty 1-50; Qty 51-100; Qty 101-199; Qty 200+) of production assets for relevant products that provide the capabilities described.

3.8 Partnerships or Potential Partnerships

The USG requests that respondents describe partnerships or potential partnerships relevant to the response.

4. Responses, Communications, and Additional Considerations

1. The Government may contact respondents to obtain additional information or clarification to fully understand a company's response. This may include discussions, site visits, demonstrations, etc. to further the Government's understanding of a proposed solution, as well as a company's understanding of the Government's requirements.
2. Respondents shall clearly mark proprietary data with the appropriate markings. Any proprietary information received in response to this request will be properly protected from any unauthorized disclosure. Any material that is not marked will be considered publicly releasable.
3. When submitting a response, please be aware that the Army workforce is supplemented by contracted support personnel. Any proprietary data submitted may be handled by contract support services personnel who have signed Non-Disclosure Agreements (NDAs).
4. Responses are due electronically by 28 August 2026 and shall be submitted electronically via the Department of Defense (DOD) SAFE Site File Exchange website (https://safe.apps.mil) to the following (use the following distribution email addresses as prompted by the site): sara.a.willbourn.civ@army.mil. No hard copy or fax responses will be accepted. If a late submittal is received, acceptance of such will be at the discretion of the Government.
5. Questions, clarifications, or additional information relating to this action shall be submitted via email to Army Contracting Command-Redstone (ACC-RSA) point of contact:  Alyssa Wilbourn, sara.a.wilbourn.civ@army.mil. Subject line must read Request for Information for CHU - [Company Name]. Example: Request for Information for CHU - ABC Inc.  NO telephone calls will be accepted. Questions shall NOT contain proprietary or classified information. Contractors shall not contact any Government personnel regarding this request for information other than the individuals designated. Contacting any Government personnel other than the individuals designated may result in an organizational conflict of interest (OCI) and may result in a contractor being excluded from the competition and consideration for award.

5. Disclaimer

This notice is not a request for proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any award be made as a result.