AN/APX-123A(V) Replacement

1. NOTICE This Request for Information (RFI) is issued for informational and market research purposes only; it does not constitute a request for proposal or a promise to issue a solicitation in the future. Responses to this RFI will not be returned and will not be considered as proposals, nor will they be evaluated as such. The Government will not reimburse any company or individual for any expenses associated with preparing/submitting information in response to this posting, and any costs incurred are not considered allowable direct charges to other contracts or tasking. The information provided may be used by the Government in developing its acquisition strategy, future solicitations, 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. 2. SCOPE The US Navy Deputy Portfolio Acquisition Executive (DPAE) Carrier Strike, Air Traffic Management and Combat Identification Office (PMA-213) is conducting market research to identify possible sources in the commercial marketplace capable of providing a replacement for the AN/APX-123A(V) transponder with Unlimited Rights, or a minimum of Government Purpose Rights (GPR) for all technical data and computer software to ensure seamless cross-platform integration and organic lifecycle sustainment in support of manned and unmanned aircraft, surface, and subsurface platforms. 3. REQUESTED INFORMATION Interested parties who desire to participate in this RFI are encouraged to submit responses that demonstrate they presently have the experience and devices with the technology maturity to answer this RFI. All responses shall include: Respondent Data, in Section 3.1. Transponder Product Requirements Section 4 Section 5: Form-Fit-Function Replacement Transponder and/or Section 6: Small Form-Factor Transponder Responding Instructions are in Section 7. Interested parties may respond to multiple sections but must state which section they are addressing. 3.1. Respondent Data a. Company Name b. Address c. Point of Contact (include phone number and email address) d. CAGE Code and Data Universal Numbering Systems (DUNS) number e. Web Page URL f. Company s country of ownership g. If the company is foreign owned, provide evidence of valid Special Security Agreement (SSA) with Department of State h. North American Industry Classification System (NAICS) code relevant to your company s response along with the company s business size status (i.e., large business, small business, certified 8(a) concern, veteran-owned, HUBzone, woman-owned, etc.) 4. TRANSPONDER PRODUCT REQUIREMENTS 4.1. TECHNOLOGY PERFORMANCE 4.1.1. The Technology Readiness Level (TRL) of the product must be at least 7. Describe how the product has been demonstrated to TRL 7 and describe plans to achieve TRL 8 or higher. If not currently TRL 7, clearly describe the approach and estimated timeline to achieve TRL 7. 4.1.2. Detail how the product meets the requirements of MIL-PRF-CXP4. A copy of this specification may be provided upon request. 4.1.3. Detail the Size, Weight, and Power characteristics, and unit Cost(s) (SWaP-C) of the products to include base, mount, appliques, crypto, adapters, remote control, etc. 4.1.4. Detail the product s capability to support Selective Identification Feature (SIF) Modes 3/A and C, Mode 5 (Levels 1, 2, and 2-B), and 1090MHz ADS-B Out/In. Responses must address UAT 978MHz weather and FIS-B traffic data in accordance with RTCA DO-282C. All capabilities must comply with AIMS 17-1000 Rev 1.1, RTCA DO-260C (TSO-C166c, TSO-C154d, and TSO-C195c), DO-181F, and RTCA DO-282C. Software and hardware development must meet DO-178C Level C and DO-254 Level C standards, respectively. 4.2. INTERFACE 4.2.1. Modular Open Systems Approach (MOSA) Describe how Modular Open Systems Approach (MOSA) standards have been incorporated into the design of the product and how that allows for integration and operability across platforms. 4.2.1.1. The Government s objective is to obtain sufficient technical data and computer software rights to ensure long-term lifecycle sustainment, organic maintenance, and competitive cross-platform integration of the transponder without reliance on a sole-source vendor. For all delivered technical data and computer software, consistent with DFARS 252.227-7989, respondents shall explicitly identify any technical data, computer software, or Commercial-Off-The-Shelf (COTS) components for which Unlimited or GPR rights cannot be provided. For any restricted item, respondents must detail the specific limitations, alternatives, and the resulting impact on cross-platform integration and lifecycle sustainment. 4.2.2. Cryptographic Device 4.2.2.1. Illustrate and describe the product s external cryptographic applique device(s). 4.2.2.2. Describe if the product is cold-loadable, and if the cryptographic device is simple key loader (SKL) compatible and utilizes a Department of Defense (DoD) 6-pin standard fill cable, Profile A and/or B keys compatible, and capable of accepting Black Key. If a non-standard fill cable is required, provide cost data and specify whether the cable is proprietary. 4.2.2.3. Discuss whether the product can perform all Mode 5 cryptographic-related simultaneous interrogation and reply processing functions as described in DoD Air Traffic Control Radar Beacon System IFF Mark XII Systems (AIMS) 17-1000 Rev 1.1 and AIMS 04-900A. 4.2.2.4. Describe the National Security Agency (NSA) certification status of the product and how the product meets the minimum-security standards per the most recent NSA Security Evaluation Requirement Document (SERD). 4.2.2.5. Discuss how the product is compatible with emerging requirements such as Crypto Modernization 2 (CM-2) and the most current SERD, AIMS 17-1000 Rev 1.1, and Radio Technical Commission for Aeronautics (RTCA) DO-181F Change 1 and DO-260C. 4.2.2.6. Discuss how the keys are held under power off conditions. If the product uses a battery, describe type, size, qualifications/certifications, useful life (active/storage), assembly configuration, rechargeable vs. non-rechargeable, replacement frequency, access procedures to replace, and any support equipment requirements required for replacement. Discuss compliance to power loss exemptions for Crypto Key Retention, such as crash protection. 4.2.3. Global Position System 4.2.3.1. Describe the Time-of-Day and the GPS interfaces with the product including functionality and limitations and methods for inputting TOD. Identify any limitations of TOD input that do not meet the requirements of AIMS 17-1000 Rev 1.1. 4.2.3.2. Describe whether the product is M-Code compatible and/or upgradable. 4.2.4. Control 4.2.4.1. Describe how the equipment is operated, controlled, and status using each and any of the available interfaces. 4.2.4.2. List all product interfaces (e.g. Ethernet, ARINC 429, MIL-STD-1553, etc.) to include antenna ports, including any limitations of each interface for achieving full product functionality. 4.2.4.3. Illustrate any access panel(s), status indicators, and connectors and their locations. Describe the functionality of any access panel(s), status indicators and connectors. For visible light indicators, discuss compliance with human factors and Night Vision Imaging System (NVIS). 4.3. ENVIRONMENTAL 4.3.1. Describe the product s compliance with the latest versions of MIL-STD-810, MIL-STD-167A, and MIL-DTL-901 Environmental Requirements, and with MIL-STD-461 and MIL-STD-464 Electromagnetic Environmental Effects (E3). Provide any test plans and test reports summaries specifically pertaining to MIL-STD-810H, MIL-STD-464C, MIL-STD-167A, MIL-DTL-901, and MIL-STD-461G testing of the product, or for the latest version of the standard for which the equipment has been qualified. Government may ask for complete Test Plan and Test Report with additional Request For Information data call. 4.3.2. Describe and illustrate the product s heat signature (thermal characteristics)/dissipation and any cooling requirements and/or peripherals. 4.4. ELECTRICAL 4.4.1. Describe the product s compatibility with the electrical requirements of MIL-STD-704A-F and identify any areas where the product does not meet these requirements under non-standard input conditions 4.4.2. Describe the product s compatibility with low voltage power requirements of MIL-STD-1399, Section 300. 4.5. HUMAN FACTORS 4.5.1. Characterize Human Systems Integration (HSI) performed on any proposed existing or developmental products across the HSI domains (Manpower, Personnel, Training, Human Factors Engineering, Survivability, Systems Safety, and Health Hazards), with attention to maintainability and supportability. Assess whether the system's complexity would require the creation of a new Navy Enlisted Classification (NEC), or if it can be fully supported by existing baseline training. 4.5.2. Describe…