Request for Information for Common High Altitude Anti-Submarine Warfare Weapon Capability (C-HAAWC)

Purpose: This is a Request for Information (RFI) as defined in FAR 15.201(e). The Department of the Navy, Naval Sea Systems Command (NAVSEA) Program Executive Office (PEO) Undersea Warfare Systems (UWS), Undersea Weapons Program Office (PMS404) is seeking industry feedback on the capability, technical risk, and program timeline to meet the Government's need for the development of an Air Launch Accessory (ALA) for use in employing the MK 54 family of lightweight torpedoes (MK 54 MOD 0, MK 54 MOD 1, and MK 54 MOD 2) from a P-8A Poseidon Maritime Patrol and Reconnaissance Aircraft. The Navy is interested in the full potential of industry responses, to include small business participation. The small business size standard for NAICS 334511 is 1,250 employees. Development Contract Concept and Background: The Navy is in the process of developing the MK 54 MOD 2 lightweight torpedo. Due to changes in the mass properties, length, and outer mold lines from the MK 54 MOD 0/1, the current HAAWC ALA, MK 14 MOD 0 Torpedo Wing Assembly, is not compatible with the MK 54 MOD 2 design. There is also an update to the electrical and logical interfaces between the launch platform and the MK 54 to incorporate the enhanced Digital Fire Control Interface (eDFCI). It is the Navy's desire to award a contract in the 2024 calendar year for design and development of an Air Launch Accessory (ALA) that will be compatible with the complete family of MK 54 Torpedoes (MOD 0, MOD 1, and MOD 2). The combination of any variant of the MK 54 Torpedo and the new common ALA will comprise the Common High Altitude ASW Weapon Capability (C'HAAWC) weapon system. C'HAAWC Design Objectives and Technical References: The Navy has performed requirements traceability analysis within the Dynamic Object Oriented Requirements System (DOORS) to ensure the traceability of the existing MK 14 MOD 0 Torpedo Wing Assembly design requirements from the HAAWC Capability Production Document (CPD) to the Performance Specification for the High Altitude ASW Weapon Capability (NAVSEA specification number 7609779) and the Performance Specification for the High Altitude ASW Weapon Capability Air Launch Accessory (NAVSEA specification number 7609780). Given the requirements flowed to the HAAWC ALA spec, 7609780, the Navy would like an assessment of a proposed C'HAAWC to (a) meet the original HAAWC specifications; (b) address the commonality issues of the MK 54 Torpedo family, which includes the MK 54 MOD 2; and (c) propose any updates to the specifications. Additional contractor requirements would be described within a contract Statement of Work. The primary C'HAAWC objective is to expand on the foundational HAAWC concept, which provided increased standoff range and weapon release envelope for P-8A launch. The ALA will be used exclusively with the MK 54 family of torpedoes and it is desired that the ALA be common to all MK 54 configurations. The Navy desires the capability to carry and release five (5) C-HAAWC weapons from the P-8A weapons bay, commensurate with the existing capability for HAAWC. Due to the increase in weight of the MK 54 MOD 2 torpedo, the design of the C'HAAWC must consider the 1000-lb store weight limitation for each All-Up Round (AUR) system loaded in the P-8A Poseidon weapons bay. The ALA interfaces with the P-8A and the MK 54 lightweight torpedo are described in the MK 54 MOD 0/1 Configuration Drawing (NAVSEA drawing number 7083425), the MK 54 MOD 2 Mechanical Interface Control Drawing (8819019), the MK 54 Torpedo Electrical Interface Control Document (8594949), and the MK 54 Torpedo Interface Requirements Specification / Interface Design Description (8594950). The ALA must have a MIL-STD-1760 electrical interface to allow data transfer from the P-8A Poseidon Station Control Unit. The ALA must interface with the torpedo in accordance with the eDFCI. The Navy's intent is to field the C'HAAWC with the capability for the ALA to receive in-flight mid-course targeting updates and torpedo presets after release from the P-8A aircraft, thus requiring a data link. The ALA and AUR shall interface with the CMBRE+ and the upcoming Standardized Tester of Reprogrammable Munitions (STORM) for conducting a Built-In Test (BIT) and reprogramming ALA software. It is the Navy's desire that any proposed C-HAAWC program be synchronized with the MK 54 MOD 2 program such that, 1) as a threshold, sufficient C-HAAWC testing, certification, and/or qualification is completed to allow the use of the C-HAAWC during MK 54 MOD 2 OT launches from a P-8A Poseidon; and, 2) as an objective, the C-HAAWC Program conducts OT and attains IOC concurrent with the MK 54 MOD 2. Data Library: The Navy will provide, upon request, an electronic library (e.g., CDs) for respondent accessibility to Controlled Unclassified Information (CUI) HAAWC technical documentation and hard-copy classified HAAWC technical documentation for those responders that are cleared to receive SECRET level of classified data. The Navy does not warrant the content and performance of the design data contained therein. Documentation may include: Performance Specification for the High Altitude ASW Weapon Capability Air Launch Accessory (NAVSEA Specification number 7609780) (including a classified annex) The torpedo and HAAWC Security Classification Guides The current MK 54 MOD 0/1 Configuration Drawing (NAVSEA drawing number 7083425) The development MK 54 MOD 2 Mechanical Interface Control Drawing (8819019) MK 54 Torpedo Electrical Interface Control Document (8594949) MK 54 Torpedo Interface Requirements Specification / Interface Design Description (8594950) MK 54 MOD 2 Acquisition Schedule Overview of current fixed wing ALA operations and the current Torpedo fixed wing ALA Technical Data Package P-8A Bomb Rack Unit (BRU) and Pylon specifications Solid models of the P-8A weapons bay and MK 54 family of Torpedoes (MK 54 MOD 0, MOD 1, and MOD 2). Responding to this Notice: The C-HAAWC RFI attachments contain controlled unclassified information (CUI) and controlled classified information. Interested parties are required to have Defense Security Service (DSS) issued SECRET facility clearance, SECRET personnel clearances and SECRET safeguarding capability to gain access to this NATO classified information. Level of Facility Security Clearance (FCL) required: SECRET Level of safeguarding for classified information/material required at contract facility: SECRET The contractor shall be required to implement components of the OPSEC process to protect and safeguard critical information per requirements. Offerors interested in obtaining access to the controlled documents are instructed to request access through sam.gov. Offerors must also fill out and return the Terms of Use (TOU) agreement (Attachment A) and DD254 and send via electronic mail to: TO: Mr. Brian Lofgren - brian.a.lofgren.civ@us.navy.mil SUBJECT LINE: Your Company Name - C-HAAWC RFI Once the TOU is approved the requests to access the controlled documents in sam.gov will be approved. The Contracting Officer will only grant access to the controlled documents to the individuals named on the TOU. Upon approval of a DD254, the government will mail a CD containing the classified documents to the address listed on the approved DD254. Information is desired in the following areas: Technical challenges to developing a universal C'HAAWC that can function with any of the MK 54 family of torpedoes; Technical feasibility of a C'HAAWC design with an AUR weight of no more than 1000 lbs, given the MOD 2's mass properties; Feasibility of aligning to the MK 54 MOD 2 IOC; Highest technical risk areas and mitigation strategies for the same; Recommended changes to the Performance Specification for the High Altitude ASW Weapon Capability Air Launch Accessory to reduce performance and program timeline risk (be specific of the effect of the recommend changes); Any additional technical risks or challenges, whose resolution or mitigation a responder deems critical to the success of a C-HAAWC program; Modeling and Simulation (M&S) capabilities, including any certifications and or accreditations for weapon system performance verification Data Right assertions to any technical data, including hardware and software, that the responder anticipates to be included as a part of its design, Background and history of any testing performed with the responders design, Demonstrated capability either through flight testing and or M&S, and Company Information (excluded from page limitation): Company Name Company Address DUNS Number CAGE Code Website address Technical Point of Contact (Name, Email Address, and Telephone Number) Business Size Status (e.g., large, small, HUBZone, SDB, SDVOSB, VOSB, WOSB) Level of Facility Clearance Submission Instructions: Responses to this RFI shall be UNCLASSIFIED and shall not exceed 50 pages in length, excluding the cover page containing company information. Responses shall be submitted in electronic format (Microsoft Word 2016 or later, or searchable Adobe Acrobat Portable Document Format (PDF) 8.0 or later, compatible formats). Each submission shall be electronic (virus-scanned) and sent via email to the Point of Contact (POC) listed below. Please submit your email with the subject line, - RFI C-HAAWC: [Company Name]. Telephonic and oral responses are not acceptable. All responses must be received on or before the - Response Date specified. Proprietary information, if any, must be clearly marked. To aid the Navy in its review and evaluation, please segregate proprietary information to the maximum extent practicable. Inquiries on RFI Content: The Navy will accept questions from industry regarding content of this RFI. E-mail questions should be sent to PCO/Contract Specialist (brian.a.lofgren.civ@navy.mil). In order to ensure adequate response time, the desired deadline for Navy receipt of questions on RFI content is 2 June 2023 at 4:30 PM EST. NO CLASSIFIED MATERIAL SHALL BE SUBMITTED UNDER ANY CIRCUMSTANCE. DISCLAIMER AND IMPORTANT NOTES This RFI is issued for informational and planning purposes only and is not to be construed as a commitment by the Government to issue a solicitation or award a contract. In accordance with FAR 15.201(e), responses to this notice are not offers and cannot be accepted by the Government to form a binding contract. As such, the Government will not reimburse any costs associated with responding to this notice. Any organization responding to this notice should ensure that its response is complete and sufficiently detailed to allow the Government to determine the organization's qualifications to perform the work. Respondents should properly mark their responses with the appropriate restrictive markings. Information that is proprietary or competition sensitive may be protected from disclosure under the public records law only if properly labeled as such. The Government may not respond to any specific questions or comments submitted in response to this sources sought notice or information provided as a result of this sources sought. Any information submitted by respondents as a result of this sources sought notice is strictly voluntary. Respondents will not be notified of the results of this notice. The information obtained from submitted responses may be used in the development of an acquisition strategy and future solicitation. Response to this notice is not a request to be added to a bidders list or to receive a copy of a solicitation. If a solicitation is issued, it will be announced later via sam.gov and all interested parties must respond to that solicitation announcement separately from to the response to this RFI.