AN/APX-123A(V) Transponder 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 t