Request for Information / Sources Sought Control Head Unit (CHU)

eration, federated replacement for the legacy SINCGARS system. To bypass traditional, multi-year aircraft integration timelines and meet emerging Next Generation Command and Control (NGC2) requirements, PM AMSA is seeking an intelligent, airworthy, modular open-systems-compliant controller capable of hosting multiple software applications, enabling rapid, iterative evolutionary capability updates directly to the warfighter. 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 � Aberdeen Proving Ground 6590 Reconnaissance Street, Building 6010 APG, MD 21005 Description 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.2.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 Control Head Unit (CHU) to control the Air to Ground Communications(A2GC) system. 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). 2.1. Background The A2GC system is the Army�s replacement for the legacy SINCGARS system. Unlike its predecessor, this system will be federated from aircraft systems, thus it will need a CHU of its own. To field critical communications capabilities immediately, we must bypass traditional, slower system integration timelines in favor of rapid, iterative evolutionary updates. Emerging waveforms requirements and nascent Next Generation Command and Control (NGC2) Army requirements are driving inclusion of additional 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 5 pages. 3. Requested Information 3.1 Company Information Company Name Address Point of Contact (include phone number and email address) CAGE Code UEI Web Page URL State the country of ownership for the company State whether the company is a non-traditional defense contractor Please identify your company's size standard per the primary NAICS code of 334511- Search, Detection, Navigation, Guidance, Aeronautical and Nautical System and Instrument Manufacturing. The Small Business Size Standard for this NAICS code is 1,350 employees. For more information on small business, refer to: https://www.sba.gov/document/support--table-size-standards If your company is a small business, indicate whether any of the small business categories below apply: 8(a): Small Disadvantaged Business (DB): Woman-Owned Small Business: Historically Underutilized Business Zone (HUBZone): Veteran-Owned Small Business: Service-Disable Veteran-Owned Small Business: If you identify your company as a SB or any of the SB subcategories as stipulated in section j, is your company intending to submit a proposal as a prime contractor? Is your company capable of performing at least 51% of the work? If so, please explain how your company will perform the work within the parameters of the Ostensible Subcontractor Affiliation rule. Does your company possess the capabilities to provide the entire range of products and services discussed in this RFI? If NO, please provide specific capabilities that you intend to provide? 3.2 Capabilities The USG is particularly interested in the physical characteristics and performance capabilities including: Describe the configuration of your proposed solution. Include: Operational startup time 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 Chipset and computational resources (RAM, ROM, GPU, etc.) Total weight and dimensions of proposed solution Display � 4.3 inches (minimum diagonal) Desired Dimensions Width - 5.75 inches Height - 3.35 inches Depth - Not to exceed 3.9 inches (DZUS rail to connector opening) Any mounting hardware required (e.g., shock isolators, cooling plates, DZUS rails) For consideration, solution must be compatible with DZUS rail mounting 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) Cooling method(s) used on proposed solution Supply chain considerations (e.g., countries of origin, obsolescence) Operating System options (e.g. Linux, VxWorks, Deos, etc.) Describe any non-standard (non-conformant) material used in the proposed solution 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. Describe how the system architecture of the proposed solution would operate functionally and physically in DoD Modular Open System Approach (MOSA). Describe any experience with the Hardware Open Systems Technologies (HOST) Technical Standard and how the standard can be applied to the controller solution Describe how the solution can be deployed Describe any past experience with similar Department of Defense (DoD) implementations and lessons learned from past experiences Describe knowledge and experience in product line engineering (PLE) Describe how the developed solution would achieve Cyber Security Compliance IAW AR 25-2. Describe the data rights, licensing structures, or intellectual property (IP) assertions associated with the proposed solution�s external hardware and software interfaces, external drawings, and technical manuals. Consistent with commercial-first preferences (FAR Part 12), please identify if these items are commercial products/services with standard commercial licenses, or if they are offered with Government Purpose Rights (GPR) or Custom/Limited Rights. Compliance with Mandates 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 c