Inactive

1. Notice. This Request for Information (RFI) is issued for informational purposes and market research only; it does not constitute a solicitation. The Government will not reimburse any company or ind... 1. Notice. This Request for Information (RFI) 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 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, 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 United States (US) Army Program Executive Office (PEO) Aviation, Assured Airspace Access Systems Product Management Office (PdM A3S), in partnership with the US Navy Program Executive Office Tactical (PEO(T)) Air Traffic Management and Combat Identification Office (PMA-213) are conducting market research to identify possible sources in the commercial marketplace capable of providing a replacement for the AN/APX-123A(V) transponder installed on manned and unmanned systems, as well as surface and subsurface platforms. 3. Instructions to potential respondents. 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. Proposed devices will be referred to as “products”. Responders must respond to at least one of the following sections: Section 5, Section 6 or Section 7. Responders may respond to more than one, or any combination, of Sections 5, 6 and/or 7. Whether responding to one, or multiple sections, response(s) must be clear as to which section(s) the response addresses. All Reponses shall include Respondent Data, as identified in Section 3.1. Each Section 5/6/7 response shall include the information requested in Section 4 and shall follow the directions set by Section 8. 3.1 Respondent DataCompany Information Company Name Address Point of Contact (include phone number and email address) CAGE Code and Data Universal Numbering System (DUNS) number Web Page URL Company’s country of ownership. If the company is foreign owned, provide evidence of valid Special Security Agreement (SSA) with Department of State. North American Industry Classification System (NAICS) code relevant to your company’s response (i.e., large business, small business, certified 8(a) concern, veteran-owned, HUBZone, woman-owned, etc.). 4. General Civilian/Military Mode 5 capable Transponder Product Requirements. 4.1.0 Detail how the product meets the requirements of MIL-PRF-CXP3, Rev 1. A copy of this specification may be provided upon request. 4.1.1 Detail the size, weight, and power characteristics, plus unit cost(s) (SWaP-C) of the products to include base, mount, appliques, crypto, adapters, etc. 4.1.2 The Technology Readiness Level (TRL) of the product must be at least 7. Describe how the product has been demonstrated to TRL 7 or higher 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.3 The Manufacturing Readiness Level (MRL) of the product must be at least 7. Describe how the product has been demonstrated to MRL 7 or higher and describe plans to achieve MRL 8 or higher. If not currently MRL 7, clearly describe the approach and estimated timeline to achieve MRL 7. 4.1.4 Discuss what country and city where the proposed transponder would be manufactured. Response should also indicate where any major sub-assemblies are manufactured if different locations are utilized. 4.1.5 If the product is currently being manufactured, detail what platform(s) for US, North Atlantic Treaty Organization (NATO), or other partner nations have the product installed and what certification(s) have been obtained. 4.1.6 Describe the manufacturing management system in place and how manufacturing risk is handled to promote the suitable maturity, manufacture, adjustments, fielding, and sustainment during the anticipated fielded lifetime of the product. Explain your International Organization for Standardization (ISO) certification (or equivalent) level. 4.1.7 Describe how suppliers are managed, including supplier capability, tracking, reporting, and the in-house/supplier detection of fraudulent or counterfeit electronic components. Explain their ISO (or equivalent) certification level. 4.1.8 Describe the life-expectancy of the product and any foreseen obsolescence. Identify any parts or vendors foreign to the United States of America. Provide the Bill of Materials (BOM) and supplier list, including country and city. 4.1.9 Illustrate and describe the product’s cryptographic device (either internal or external). 4.1.10 Describe how cryptographic material / keys are loaded, if the product is cold-loadable, and if the cryptographic device is simple key loader (SKL) compatible, Profile B compatible, capable of accepting Black Key, and if the cryptographic device utilizes a Department of Defense (DoD) 9-pin standard fill cable. If a non-standard fill cable is required, provide cost data and specify whether the cable is proprietary. 4.1.11 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 and AIMS 04-900A. 4.1.12 Describe the National Security Agency (NSA) certification status of the product and how the product meets the minimum-security standards per NSA Operational Security Doctrine, DOC-016-15, Rev Dec 2018, if embedded Crypto is used. 4.1.13 Discuss how the product is compatible with emerging requirements such as Crypto Modernization 2 (CM2). AIMS 17-1000 Rev 1, and RTCA DO-181F and 260C. 4.1.14 Discuss how the keys are held under power off conditions. If the product uses a battery, describe type, size, replacement time, assembly configuration, rechargeable vs. non-rechargeable, replacement frequency, and access procedures to replace. Detail what solutions might be available to mitigate the need for batteries in loading and holding keys. Discuss compliance to “power loss” exemptions for Crypto Key Retention, such as crash protection. 4.1.16 Include the estimated cost range for the proposed transponder, assuming an initial estimated quantity of 1, 101, and 501, in 2023 dollars. 4.1.17 Describe how Modular Open Systems Approach (MOSA) standards have been incorporated into the design of the product. 4.1.18 Describe whether the product can perform all ADS-B capability in accordance with AIMS 17-1000 Rev 1, DO-260B, (and TSO-C166b). What about ADS-B In? (1090MHz In; UAT 978MHz weather and FIS-B traffic data) 4.2 Environmental Requirements 4.2.1 Describe the product’s compliance with MIL-STD-810 and MIL-STD-167 Environmental Requirements and with MIL-STD-461 and MIL-STD-464 Electromagnetic Environmental Effects (E3). Provide any test plans and test reports specifically pertaining to MIL-STD-810H, MIL-STD-464C, MIL-STD-167A, and MIL-STD-461G testing of the product, or for the latest version of the standard for which the equipment has been qualified. 4.2.2 Describe and illustrate the product’s heat signature (thermal characteristics)/dissipation and any cooling requirements and/or peripherals. 4.3 Identification, Friend or Foe (IFF) Requirement. Describe the product’s compliance with the IFF requirements of AIMS 17-1000 Rev 1, Federal Aviation Administration (FAA) Technical Standard Orders (TSOs) C112e and C166b, and Radio Technical Commission for Aeronautics (RTCA) DOs 178B, 181E, 254, and 260B. 4.4 Airworthiness Requirement. Describe how any non-developmental items/commercial off-the-shelf or developmental products will be ready to achieve Aviation Airworthiness Approval per Army Regulation (AR) 70-62, Airworthiness Qualification of Aircraft Systems. 4.5 Electrical Requirements. 4.5.1 Describe the product’s compatibility with the electrical requirements of MIL-STD-704A-F. 4.5.2 Describe the product’s compatibility with low voltage power requirements of MIL-STD-1399, Section 300. 4.6 Human Systems Integration 4.6.1 Characterize Human Systems Integration (HSI) performed on any proposed existing or developmental products across the HSI domains of manpower, personnel, training, human factors engineering, soldier survivability, systems safety, and health hazards with attention to maintainability and supportability. 4.6.2 Describe the product’s Human System Interface compliance to MIL-STD-1472H. 4.7 Interfaces and Transponder Support 4.7.1 Describe how the equipment is operated, controlled, and status using each and any of the available interfaces. 4.7.2 List all product interfaces (e.g., Ethernet, ARINC 429, MIL-STD-1553, etc.) to include antennae ports, including any limitations of each interface for achieving full product functionality. 4.7.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. 4.7.4 Describe the Time-of-Day and the GPS interfaces with the product including functionality and limitations and methods for inputting TOD. 4.7.5 Describe whether the product is M-Code compatible and/or upgradeable. 4.8 Logistics Requirements 4.8.1 For fielded systems provide product Reliability, Availability and Maintainability (RAM) data to include Mean Time Before Failure (MTBF) and Mean Time to Repair (MTTR) as calculated as: MTTR = Total Downtime / Number of Failures; MTBF = Total Up Time / Number of Failures. Indicate whether the substantiating data is actual or predicted. For systems not yet fielded, provide predicted reliability as determined per MIL-HDBK-217F. 4.8.2 Describe the Built-In-Test (BIT) or Prognostic Health Management (PHM) capability and limitations. 4.8.3 Describe how the operational software/firmware is loaded in the product, what equipment is required, what software coding language(s) are used, what software development processes are used, and what entity develops and updates the software. 4.8.4 Describe the capability to perform all levels of maintenance (organizational, intermediate, and depot). If depot level maintenance currently exists for the product, detail the capabilities (inspection, testing, and repair) and the location (city, country). 4.8.5 Describe efforts that have been performed to support Failure Mode, Effects & Criticality Analysis (FMECA), Level of Repair Analysis (LORA), and Maintenance Task Analysis (MTA). 4.8.6 Describe how obsolescence, manufacturing sources, material shortages, or hardware and software monitoring for Diminishing Manufacturing Sources and Material Shortages (DMSMS) are tracked by the respondent and flowed down to suppliers. 4.8.7 Discuss what type of predictive maintenance functionality combined with Artificial Intelligence (AI), if any, including visual or audio notifications or data capture/software capabilities are provided within the transponder for use by the operator, maintainer, and trainer. 4.8.8 Discuss what data is available to support operations, maintenance, installation and training for the product. Detail any possible data rights restrictions that may be imposed. 4.8.9 Describe any support equipment, special handling (including hazardous materials), computer resources, facilities and infrastructure needed to support the product. 4.9 Cybersecurity Requirements 4.9.1 Describe the product’s cybersecurity compliance with DoDI 8500.01 and other Cybersecurity Policies as defined in the following chart: https://dodiac.dtic.mil/dod-cybersecurity-policy-chart/ 4.9.2 Describe any vulnerability scanning and/or software assurance completed or planned. Describe Risk Management Framework (RMF) compliance. Describe if any Authority to Operate (ATO) has been obtained for the system. 4.9.3 Describe if any Cyber Survivability Risk Assessment (CSRA), Cyber Risk Assessment (CRA), or Cyber Table Top (CTT) events have been completed for your system and to what Phase. Note that discussion of the event results may be classified and should only be disclosed in accordance with associated Security Classification Guides (SCG) or handled and marked appropriately. 4.9.4 Describe if any other Cyber related testing that has been done to assess system maturity and vulnerabilities. Note that discussion of the test results may be classified and should only be disclosed in accordance with associated Security Classification Guides (SCG) or handled and marked appropriately. 4.9.5 Discuss the timeline and process to be used for emergency software services for the product. 4.10 System Safety. Describe compliance to MIL-STD-882E and identification, classification, and mitigation of system related hazards. 5. MOSA Card-Based Transponder. A card-based transponder that is an Open VPX profile circuit card mounted into the CMOSS Mounted Form Factor (CMFF) chassis. 6. Form-Fit-Function Replacement Transponder for U.S. Navy Platforms. A “drop-in replacement” transponder which can be a Line Replaceable Unit (LRU) that will serve as a suitable substitute for the current AN/APX-123A(V) Common Digital Transponder (CXP) and can mount in the existing CXP tray without any updates to the platform interface or platform software. This Form-Fit-Function CXP replacement must go beyond solely an obsolescence-only redesign for the AN/APX 123A and include modernized functionality, significantly improved SWaP, and other improvements. Designate ability for drop-into shipboard environments as well without any updates (e.g., Mode C –1000 Feet, MIL-STD-167A, MIL-STD-1399 Sect 300, etc.). 7. Small Form-Factor Transponder (e.g. micro-transponder). Include options for new capabilities (M5L2-B, ADS-B In, UAT Weather, etc.). 8. Responses, Communications and Additional Considerations. 8.1 Responses shall not exceed 100 pages (excluding any cover page). Include technical and descriptive text, functional block diagrams, and illustrations to provide sufficient detail. The submitted documentation becomes the property of the United States Government and will not be returned. 8.2 All information submitted will be adequately safeguarded from unauthorized disclosure in accordance with FAR Part 15.207. Summary papers that fail to comply with the instructions herein or present ideas not pertinent to the subject may not be reviewed. Information submitted in response to this RFI is submitted at no cost to the Government and will not be returned. Note: If the interested party is a foreign concern or if a US interested party has a team member or partner who is a foreign entity, adherence to all International Traffic and Arms Regulations (ITAR) is required. 8.3 It is requested that no classified data be provided. If a respondent believes a complete response would require submission of classified information, notify the Government POC immediately so that proper actions by the Government and vendor can be coordinated. 8.4 To aid the Government and permit assistance from Government contractor support service personnel, it is preferred that submissions do not contain any information marked proprietary. 8.5 Do not submit marketing material. 9. Jason Baggett, Assistant Product Manager, 256-313-4227, jason.a.baggett2.civ@army.mil