Request for Information Offensive Anti-Surface Warfare (OASuW) Analysis of Alternatives (AoA) Update

Request for Information Offensive Anti-Surface Warfare (OASuW) Analysis of Alternatives (AoA) Update 1. SUMMARY: This announcement constitutes a Request for Information (RFI) of key capabilities, technical readiness levels, cost, schedule and risks associated analyzing the trade space for the Offensive Anti Surface Warfare (OASuW) AoA update. This update expands the Next Generation Land Attack Weapon AoA to include Naval TACAIR with the objective to inform DoN next generation strike weapon roadmaps. The goal of this RFI is to provide industry an opportunity to inform the government of relevant information regarding maturity, manufacturability, sustainment, and affordability of existing and emerging technologies that may support future air launched Surface Warfare (SuW) and land strike capabilities in the 2030 timeframe. The study will examine the performance and cost trade space for this mission in the 2030 timeframe. 1.1 KEY DATES: 1. Notification to attend Industry Day 30 April 2019 2. Industry Day Registration 10 May 2019 3. Industry Day 20 May 2019 4. Responses Due 28 June 2019 1.2 ATTACHMENTS: 1) Cost Data Template to assist the Government team to quickly summarize the various concept(s) information. 2) Detailed List of Information to assist the Government in modeling the concept(s). 2. BACKGROUND: The OASuW Update effort will examine potential solutions to be employed from aircraft against maritime and land targets in a range of environments. The trade space will be assessed with respect to concept capabilities; mission effectiveness; technical and operational risk; development and total ownership cost; and overall system value. Responses to this RFI should provide the Navy with distinct alternatives as well as emerging and existing technologies that could be applied to the OASuW solution set. While the analysis is focused on the OASuW mission area, candidate concepts will be assessed against maritime and fixed, relocatable, moving and hardened land targets. The target set will be discussed at the Industry Day presentation. It is the intent of this AoA Update to analyze individual and combinations (Family of Systems (FOS) and System of Systems (SOS)) of existing weapons, modifications to existing weapons, ongoing demonstration efforts, new weapon designs, and enabling capabilities to determine the most cost-effective manner in which to achieve multiple levels of operational capabilities at acceptable level of operational risk. Furthermore, elements from various submissions may be utilized in government-led concept engineering trade studies to identify additional potential approaches. 3. RESPONSE CONTENT AND INFORMATION REQUESTED: Naval Air Systems Command (NAVAIR) is requesting concepts, systems, subsystems, and technologies that might be part of a material solution (or multiple solutions). The primary interest areas are associated with the air vehicle itself. This includes airframe, propulsion, guidance, navigation, control, communication, payload, and warhead. Also consideration to the following as applicable; interoperability, autonomy in denied environment, weapon to weapon communications and collaboration in RF denied environment, logistics/product support (all elements), CVN Handling, CVN compatible container, self-targeting capability, WSESRB compliance Subsystems associated with encasement devices are also of interest, as well as those associated with mission planning, C2 and launch (integration, launch and guidance control, launcher equipment). Respondents should provide information on system and/or subsystems that include proposed weapon system Concepts of Employment (CONEMP), maintenance and logistics concepts and schedule and cost risks. Estimates of system and subsystem technology readiness levels (TRLs), integration readiness levels (IRLs), manufacturing readiness levels (MRLs), and, if available, initial technology maturation (TMS) strategies. A description of how the weapon system and/or subsystem fit into the overarching infrastructure may also be addressed. The NGLAW system may be launched from the F-35 (interior and exterior carriage), F/A-18, Next Generation Fighter, and P-8 Aircraft. RFI submissions for both system and subsystems should address: 1) A concept overview with description, diagrams, and interfaces; 2) Key technology characterizations and inputs to enable Life cycle cost estimates and schedule associated with RDT&E, Procurement, and Sustainment; 3) Key performance characteristics to enable effectiveness modeling and assessment. 4) TRL, IRL, and MRL assessments. 5) Specifically, how the solution is leveraging previous and existing DoD investments (with budget PE and name), IR&D, and commercial projects Lists of desired information for both weapon system performance and cost analysis are included in this RFI. For complete weapon system concepts, the RFI responses should include, but not be limited to: 1) A concept overview with description, diagrams, and interfaces to include maximum standoff range, flight profile, terminal maneuvers, lethality, signatures, an illustration of concept geometry, location of major subsystems, and mass properties. 2) A discussion of the implications of maritime employment should be provided, as well as key parameters of interest to aircraft attributes (e.g., compatibility, interoperability, safety, etc.). The response should provide sufficient fidelity to establish the technical credibility of the design, as well as define the ground rules, assumptions and methodologies utilized for performance and mass properties estimates. 3) To the extent possible, provide key assumptions and rationale for use in developing life cycle costs/schedule associated with RDT&E, Procurement, and Sustainment 4) A description of the CONEMP for systems in the operational context. The CONEMP should discuss how mission tasks will be allocated across Joint Force assets to mitigate capability gaps. It should also include enabling capabilities and kill-chain support requirements such as targeting, command and control, and communications. 5) A description of growth potential. This includes the ability to be incrementally upgraded due to evolving threat environments that may affect one or more of the OASuW capability requirements and/or the future availability of "game changing technologies" (e.g., energetics). 6) Capability for alternative mission attributes, such as EA/EW, ISR&T, SIGINT and decoy. Cost data: The effort will consider cost data, including estimating relationships, methodologies and cost drivers in order to understand the optimal solution set to meet the capability requirements. Data sources and points of contact for relevant past or ongoing efforts, as well as potential capabilities, to include system and subsystem relationships for use in estimating cost and schedule should also be provided in the RFI response. Responses for each weapon system concept should include a completed RFI Cost Data Template. The template provides cost related areas of interest and formats. Ideas and inputs regarding affordability initiatives and cost reduction techniques can be provided and will be assessed in the study. 4. INDUSTRY DAY: In support of this effort, a classified Industry Day is scheduled for 20 May 2019 at the Johns Hopkins University Applied Physics Laboratory. The study team will present information related to the study and field questions from respondents. The Government team intends to conduct breakout sessions with individual respondents during Industry Day, upon request. Unclassified questions can be submitted to Mr. Brian Kelly (contact@example.gov) prior to the Industry Day; classified questions up to SECRET can be submitted to Mr. Brian Kelly (contact@example.gov). The deadline for Industry Day registration is 10 May 2019. Additional details about Industry Day (building number, classified visit requests, etc.) will be provided. Interested respondents are advised that the Government CSS described in the Data Protection section below will be in attendance. 5. DATA PROTECTION AND SECURITY: Sensitive and/or proprietary information received from Industry and other respondents as a result of this RFI, and all future exchanges of information, will be properly protected from any unauthorized disclosures; however, it is incumbent upon the respondent to appropriately mark all submissions. In order to complete its review, NAVAIR 4.0M must be able to share the information within the Government and any responses marked in a manner that will not permit such internal Government review may be returned without being considered. Interested responders are advised that the employees of University Affiliated Research Centers (UARC) under contract with the Government will serve as technical reviewers of information provided in response to the RFI. Employees of these organizations that participate in or with the study team are required to sign and submit Non-Disclosure Agreements that will be held on file with the Government. Organizations under contract with the Government for the OASuW Update effort are: - Johns Hopkins University Applied Physics Laboratory (JHU/APL) Beyond the above organizations, the Government will not release any material marked Proprietary information, to any firm, agency, or individual outside the Government or OASuW Update study team. Any objections to release of information to any of the support contractors must be clearly and prominently delineated in the cover letter to any submission (LOI and the full response). Further, any markings affixed to submissions must clearly allow for disclosure to the support contractors to which the respondent has no objection. If interested respondents want additional protection of their information through a Proprietary Information Agreement (PIA) between themselves and the list of organizations above, they must indicate their desire in the LOI. Upon receiving the LOI, and notification of PIA intent, a list of POC for the organizations involved will be provided. Interim and final results of the AoA Update will be provided to the office of the Chief of Naval Operations (OPNAV); Secretary of the Navy (SECNAV); and Office of the Secretary of Defense (OSD) Staffs and Congress which may include non-government personnel on contract with each office. Any proprietary information used to develop the final results will be properly protected from unauthorized disclosures. 6. INSTRUCTIONS, RESPONSE FORMAT, AND SUBMITTAL: 6.1 Notification to attend Industry Day: Companies interested in attending industry day or responding to this RFI must submit an unclassified notification to Mrs. Jennifer Doane, (contact@example.gov) , Ph# +1 (555) 000-0000, no later than 10 May 2019 with the following data in order to register and verify credentials (DO NOT submit classified information): (1) An UNCLASSIFIED description of your company's submission (2) CAGE code and Classified Mailing Address (3) POC cleared to receive classified material from Industry Day (4) POC for technical and contractual purposes (5) Description of company's ability to manage and secure classified information (6) Intent (yes or no) to establish PIA with Non-Government members of AoA team 6.2 Response Format: Companies are to adhere to the National Industrial Security Program Operating Manual (NISPOM) procedures for the transmittal of classified responses. RFI submissions (up to SECRET) shall be provided a hard copy and CD ROM with electronic media that is Microsoft Office 2010 compatible. While not required, if tracking numbers are available, please provide the numbers to the POC to ensure appropriate delivery. Unclassified Submittals shall be sent to: NAVAIRSYSCOM MISSION ENGINEERING AND ANALYSIS DEPARTMENT ATTN: Brian Kelly AIR 4.13 BLDG 2187, UNIT 1180 48110 SHAW ROAD PATUXENT RIVER MD 20670-1906 Classified Submittals shall be sent to: Outer address: COMMANDER ATTN: Code 4.13 Technical Security Manager NAVAIRSYSCOM 48110 SHAW ROAD STE 1180 PATUXENT RIVER MD 20670-1906 Inner address: COMMANDER ATTN: CODE 4 13 BRIAN KELLY NAVAIRSYSCOM 48110 SHAW ROAD STE 1180 PATUXENT RIVER MD 20670-1906 In the event that companies interested in responding to the RFI believe their response would require additional information, please contact the following POC for additional instructions. Point of Contact: Matthew Ketchum NGLAW Security Manager +1 (555) 000-0000 contact@example.gov As Stated above, this is NOT a request for proposal. THIS IS NOT TO BE CONSTRUED AS A COMMITMENT BY THE GOVERNMENT, NOR WILL THE GOVERNMENT PAY FOR ANY INFORMATION SOLICITED OR PROVIDED. DISCLAIMER: THE GOVERNMENT DOES NOT INTEND TO AWARD A CONTRACT ON THE BASIS OF THIS RFI OR TO OTHERWISE PAY FOR THE INFORMATION SOLICITED. This RFI does not constitute a solicitation for proposals or the authority to enter into negotiations to award a contract. No funds have been authorized, appropriated, or received for this contemplated effort. This RFI is for planning purposes only and shall not be considered as a request for proposal or as an obligation on the part of the Government to acquire any products or services. No entitlement to payment of direct or indirect costs or charges by the Government will arise as a result of contractor submission of responses to this RFI or the Government's use of such information. The Government reserves the right to reject, in whole or in part, any contractor's input resulting from this RFI. Responses to this RFI will not be returned. Whatever information is provided in response to this RFI may be used to assess tradeoffs and alternatives. The information provided may be utilized by the Navy in developing its acquisition strategy and in its Statement of Objective and Performance Specifications. The government may also combine information from multiple submissions in response to this RFI in order to construct its own concepts. Any information provided to the government will be safeguarded in accordance with original classification markings.