AN/SPY-6(V) Production RFI/Sources Sought

Active

Contract Opportunity

Update 1/14/2024: The RFI has been updated to provide new information on the Government's intended contracting path forward and ask updated questions based on narrowing down the acquisition strategy. TDP updates are also anticipated to be added to the Bidder's Library in the near future and primary POCs have been updated. There are edits throughout this RFI so please read in it's entirety.

UPDATE 4/1/2024: The Unclassified Bidder's Library with draft TDP is now available to industry. For those interested in access, please submit the signed Terms of Use Agreement, DD 2345, and a capabilities statment, if those have not already been provided as well as a request for Bidder's Library access via e-mail to Brittany Burton, (brittany.m.burton4.civ@us.navy.mil), and Tom Kostyo (thomas.f.kostyo.civ@us.navy.mil), with a copy to the Contracting Officer, Ms. Holly Danner (holly.r.danner.civ@us.navy.mil).

SECTION 1: SYNOPSIS

The Naval Sea System Command (NAVSEA) is hereby issuing a Sources Sought Request for Information (RFI) on behalf of the Program Executive Office Integrated Warfare Systems Above Water Sensors directorate (PEO IWS 2.0). NAVSEA is issuing this announcement as part of a market survey for the AN/SPY-6 radar variants. This includes the Air and Missile Defense Radar (AMDR) (AN/SPY-6(V)1) for DDG-51 FLT III, the AMDR Backfit radar for DDG-51 FLT IIA (AN/SPY-6(V)4), the Enterprise Air Surveillance Radar (EASR) Rotator (AN/SPY-6(V)2), and the EASR Fixed Face (AN/SPY-6(V)3). For convenience, the term “SPY-6” is used in this RFI to refer to all noted radar variants.

The SPY-6 variant radars are built upon common hardware line replaceable units (LRUs) using modular, open system principles. It is PEO IWS 2.0’s intent to competitively award a multi-award Indefinite Delivery Indefinite Quantity (IDIQ) contract to procure and supportAN/SPY-6(V) radars as early as FY27, but NLT FY28. The basis for production of SPY-6 hardware is contained in the Technical Data Package (TDP), which is currently available in DRAFT form as Government Furnished Information (GFI). Multi Award Contract (MAC) IDIQ scope will include “Build-to-Print" production where applicable for all variants of SPY-6, and may include technology refresh, obsolescence resolution, and additional development support. The term “Build-to-Print" in this context means producing to the exact specifications, drawings, and design contained within the TDP, with modifications allowed only for the purposes of addressing obsolescence, non-compliances with the system specifications (A-Specifications), and reducing life-cycle cost of all SPY-6 radars to be fielded.

The Government intends to compete requirements for breakouts of LRUs or subsystems via multiple delivery or task order within the IDIQ. Feedback is desired from industry on this strategy, the potential LRUs to be competed separately, and individual interest in each of the potential breakouts. Final Contract types have not yet been determined but may be fixed-price incentive, firm-fixed price, or some combination thereof, with the potential for other incentives to be determined. Currently the Government is interested in scheduling 1:1 discussions with industry companies that are interested in participation at the full subsystem level. Future opportunities will be available for interested subcontractor participation.

SECTION 2: GENERAL INFORMATION

Pursuant to FAR 52.215-3 this is a Request for Information (RFI) notice only. This RFI is for planning purposes and is issued solely for conducting market research in accordance with FAR Part 10. The Government is NOT seeking or accepting unsolicited proposals. This notice shall not be construed as a contract, a promise to contract, or a commitment of any kind by the Government. Specific responses will not disqualify or have an impact on participation and evaluation on future solicitations. Not responding to this RFI does not preclude participation in any future solicitation. If a solicitation is issued in the future, it will be announced via the System for Award Management (SAM.gov) website and interested parties must comply with that announcement. It is the responsibility of interested parties to monitor SAM for additional information pertaining to this requirement.

Any small businesses that believe they can accomplish this entire requirement should indicate their small business status (see FAR Part 19) in their response.

PEO IWS 2.0 representatives may or may not choose to meet with RFI respondents. Such discussions would only be intended to get further clarification of potential capability to meet the requirements.

Questions regarding this announcement shall be submitted in writing via e-mail to the Contract Specialist and Contracting Officer’s email addresses (listed in Section 5 below). Verbal questions will not be accepted. Questions shall not contain classified information.

SECTION 3: REQUIREMENTS OVERVIEW

A brief overview of the SPY-6 variant mission requirements and array configuration is provided as follows:

1. AN/SPY-6(V)1 is designed to meet mission performance and size, weight, and power – cooling (SWAP-C) requirements of the DDG-51 FLT III ships with AEGIS Baseline 10 (BL 10) combat system. The AN/SPY-6(V)1 will provide volume search, tracking, Ballistic Missile Defense (BMD) discrimination, and missile communications in a wide diversity of environments and conditions. This variant includes 37 Radar Modular Assemblies (RMAs) per array, each which contain independent transmit and receive LRUs and provide SPY +16 minimum sensitivity. There are 4 arrays per shipset.


2. AN/SPY-6(V)2 is designed to meet Air Defense and Air Traffic Control mission performance and SWAP-C requirements of the CVN (Nimitz) class carriers, Landing Helicopter Assault (LHA) hulls, and Landing Platform/Dock (LPD) hulls. This variant includes a single array on a rotating platform, with 9 RMAs.


3. AN/SPY-6(V)3 is designed to meet Air Defense and Air Traffic Control mission performance and size, weight, and power – cooling (SWAP-C) requirements of CVN (Ford) class carriers and will additionally provide engagement support for Future Frigate (FFG(X)) hulls. This variant includes 9 RMAs per array with 3 arrays per shipset.


4. AN/SPY-6(V)4 is designed to meet mission performance and SWAP-C requirements of the DDG-51 FLT IIA ships with a variant of AEGIS Baseline 10 (BL 10) combat system, to be defined. The AN/SPY-6(V)4 will provide volume search, tracking, BMD discrimination, and missile communications in a wide diversity of environments and conditions. This variant includes 24 RMAs per array with 4 arrays per shipset.

The notional shipset procurement schedule (including potential FY27-30 FMS) for the above SPY-6 variants is:

SPY-6 Variant FY27 FY27 FY28 FY29 FY30 FY31 FY32 FY33 FY34 FY35

AN/SPY-6(V)1 2-6 2-4 2-4 2-4 2 2 2 2 2 2

AN/SPY-6(V)2 0-2 1-6 0-5 0-1 2 0 0 1 0 0

AN/SPY-6(V)3 1-3 2-3 1-4 1 2 1 1 0 0 1

AN/SPY-6(V)4 2 2-5 2-3 2-3 2 2 2 2 2 2

Unit Totals 5-13 7-18 5-16 6-9 8 5 5 5 4 5

Quantity Note: The Government is considering capturing potential FMS quantities in FY27-FY30 options on this future contract action, which drives the upper-range uncertainty. Multiple countries have expressed interest in procuring SPY-6 variants, but no formal FMS cases are in progress. There is potential for FMS quantities beyond FY30. USN quantities drive the lower end of the range and are stable through FY29, with increased potential for changes beyond.

For context, the FY16-25 SPY-6 contract procurement schedules are as follows:

SPY-6 Variant FY16 FY17 FY18 FY19 FY20 FY21 FY22 FY23 FY24 FY25 Totals

AN/SPY-6(V)1 1 2 1 3 2 0 3 2 2 2 18

AN/SPY-6(V)2 0 0 0 0 4 0 2 2 2 0 10

AN/SPY-6(V)3 0 0 0 0 2 0 2 1 2 1 8

AN/SPY-6(V)4 0 0 0 0 0 0 0 1 1 2 4

Unit Totals 1 2 1 3 8 0 7 6 7 5 40

The Government is interested in procuring SPY-6 radar LRUs from Offerors that have the following attributes:

1. Have past experience developing and manufacturing complex radar systems or subsystems, including S-Band Radio Frequency (RF) electronics, digital communications networks, x86 processing nodes, high-voltage power distribution and conditioning systems, high-capacity cooling units, and array structures.


2. Have demonstrated the ability to produce hardware units according to detailed technical data package materials provided to them.


3. Experience teaming with industry partners for subsystem development


4. Experience cooperating with other prime industry partners integrating complex systems.


5. Experience maintaining fielded Navy hardware systems.

The Government contemplates acquisition via the following separate delivery/task orders within the IDIQ for production:

1. Digital Receiver/Exciter (DREX) LRUs


2. Transmit/Receive Integrated Microwave Module (TRIMM) LRUs


3. Prime Power Equipment (PPE) subsystems


4. Production Integrator, including remainder of radar subsystem procurements


5. Level-of-Effort Labor Hours/ODCs for Engineering Support Tasking as necessary via Technical Instruction

SECTION 4: SUBMISSION OF RESPONSES

The Government is not requiring written responses, although written responses will be accepted. The Government seeks to have a one-on-one discussion with each interested company that would participate as a prime contractor for one or more delivery orders to further discuss this RFI and receive industry responses. The Government also intends to schedule one or more virtual industry days in the future which would allow for participation of interested subcontractors as well as interested prime contractors.

Responses to this RFI should be submitted by the closing date and time via e-mail to Spencer Bryant, Contract Specialist (spencer.m.bryant2.civ@us.navy.mil), and Tom Kostyo (thomas.f.kostyo.civ@us.navy.mil), with a copy to the Contracting Officer, Holly Danner (holly.r.danner.civ@us.navy.mil)

SECTION 4.1: CONTENT

Written responses are not required, with exception of a capability statement and request for a one-on-one meeting. Companies that submitted a capability statement to the previous RFI are not required to resubmit. Companies that optionally choose to respond to this RFI in writing should provide a response not to exceed thirty (30) pages.

Cover Sheet, Company Profile, Table of Contents, and List of Abbreviations and Acronyms are exempt from the page limit. A detailed proposal is not requested. Responses should indicate sufficient detail for assessment of potential contracting strategies and company interest; submissions should be organized as follows:

• Cover Sheet - RFI number and name, address, company, technical point of contact, with printed name, title, email address, telephone number, and date


• Company Profile - Include the following information:
  
  
  
  • Company Name
  
  
  • Company Address
  
  
  • Commercial and Government Entity (CAGE) Code
  
  
  • Point of Contact
  
  
  • E-mail Address
  
  
  • Website address
  
  
  • Telephone Number
  
  
  • Business Category (i.e., large, small disadvantaged, veteran, woman owned, etc.)
  
  
  • Please advise if you would like to be publicly disclosed as an interested party through this FBO notice in an effort to foster industry teaming possibilities.
  
  
  
  


• Table of Contents, with list of figures and tables with page numbers


• General response information


• List of Abbreviations and Acronyms

Product line brochures, catalog excerpts, etc. may be submitted and referenced within the general capability statement and are exempt from the page limit.

The Government wishes to address the following questions in one-on-one sessions (any questions answered in the previous RFI do not need to be discussed again in one-on-ones unless information has changed):

1. Do you have past experience procuring/producing Build to Print hardware? If so, are there any recommended lessons learned for the Government to incorporate into the contracting strategy?


2. What manufacturing facilities does your organization have and what product lines have been developed in these facilities in the past?


3. Do you see utility in the Government pursuing a multiple award strategy with break-outs of the radar subsystems? Are there additional strategies you would suggest or specific parameters you would suggest to increase your interest in competing?


4. Would you prefer to bid on an entire SPY-6 system or a subset? If subset, which subsystem(s) or LRUs would you be interested in bidding? Do you believe there is utility in breaking out a different subset of components from the Government’s initial set?


5. Would you be willing to compete on a multi-award IDIQ contract?


6. In the event of breaking up the system into separate sources, the Government envisions a “production integrator” to produce any components from the TDP not separately sourced, The “production integrator” would also potentially support the Government in management of subsystem sources, and complete the remaining production scope (e.g. configuration management, planning, array integration and test). What considerations do you have for this role and how it would be contracted? Would this be a role your company is interested bidding for? If this role did not include other subsystem production, would your company be interested in competing? Is there a particular mix of subsystems that, when combined with this role, would make competing for this more enticing to your company?


7. Would your company’s interest change if technology refresh scope were included?


8. Would your company’s interest change if firmware, software, or any other development scope were included?


9. What timeframes does your organization believe are appropriate for proposal preparation, and time from contract award to first production unit delivery? Please specify this timeline for each/any LRUs your company is interested in.


10. What minimum time does your organization require with the TDP prior to submitting a proposal?


11. Do you have suggestions for ways to reduce system cost other than through competition?


12. What upgrades does your organization already have planned for manufacturing facilities? How would preparing for this competition change those plans? How would being awarded a contract change those plans?


13. What flexibility does your organization have in production processes to adjust/adapt to increasing/decreasing number of production units?


14. What near-field range (NFR) facilities does your organization own or have access to?


15. What RF circuit card assembly facilities does your organization own or have access to? How much production capacity is available to support projected demand? If needed what approach would you take for increasing capacity? What manufacturing processes does your organization’s facilities support (e.g. surface mount technology (SMT), wire bond, etc)?


16. What is your organization’s experience with non-hermetic Monolithic Microwave Integrated Circuit (MMIC) processing and assembly?


17. If you are teaming, how would your organization manage subcontractors/teammates to ensure that the performance requirements are flowed down and met?


18. Does your organization have the ability for the Government to procure additional parts on a Provisioned Items Order (PIO) for the use as spares?


19. What would your organization recommend for production lead times to delivery of a system or subsystem(s) to a shipyard or land-based facility for each of the SPY-6 variants and why? Would the delivery date Months After Option Exercise (MAOE) decrease based on a learning curve over time? Would Delivery Date MAOE adjust based on the number of units, potentially similar and different variants, being exercised at the same time?


20. Would your organization recommend procuring equipment in blocks or individually based on the needed Delivery Date? If recommendation is as a block, what is your recommendation for structuring the block so that it can adapt to the appropriate number of units?


21. What support equipment and/or test assets would your organization utilize to support hardware production and quality assessments? If support equipment and/or test assets are required, would existing Contractor assets be available? If not, what would be your approach to obtain the equipment?


22. Are there any cost/pricing considerations you would like to bring to the Government’s attention? Do you have any recommendations on the structure of the requirements or the overall contracting strategy that would reduce the total price? What performance incentive structure and growth would your organization recommend and why?


23. Do the potential FMS quantities affect or change your answers to any of the above questions? Are there specific considerations you would like to raise with relation to the potential FMS units?


24. If you’ve reviewed the GFI TDP, what additional data, if any, would your organization believe is necessary to successfully procure andproduce SPY-6 hardware?

Respondents are solely responsible for properly marking and clearly identifying any proprietary information or trade secrets contained within their responses. The Government will not be liable, or suffer any consequential damages, for any proprietary information not properly marked and clearly identified. Proprietary information received in response to this RFI will be safeguarded and handled in accordance with applicable Government regulations.

SECTION 4.2: CLASSIFICATION

All materials submitted in response to this RFI should be UNCLASSIFIED.

If a potential respondent believes submission of classified material is necessary or will provide a higher quality response, please contact Spencer Bryant, Contract Specialist (spencer.m.bryant2.civ@us.navy.mil), and Tom Kostyo (thomas.f.kostyo.civ@us.navy.mil), with a copy to the Contracting Officer, Holly Danner (holly.r.danner.civ@us.navy.mil).

SECTION 4.3: FORMATTING (If optional written responses are provided)

NAVSEA will accept ONLY electronic unclassified submission of responses.

Respondents to this RFI must adhere to the following details:

• Submissions shall be single spaced, typed or printed in Times New Roman font with type no smaller than 12-point font.


• Pages should be 8 1/2 x 11 inches with a minimum of 1 inch margins around the page. Any text contained within tables, graphs, etc. should be 8-point Times New Roman font or larger.


• Included files should be created/prepared using Microsoft Office 2016 compatible applications. Graphics, photographs, and other data that may not be compatible with Microsoft Office 2016 should be submitted in Adobe Acrobat format.


• Submitted electronic files should be limited to the following extensions:

.docx Microsoft Word

.xlsx Microsoft Excel

.pptx Microsoft PowerPoint

.pdf Adobe Acrobat

.mmpx Microsoft Project

Submitted electronic files should not be compressed.

SECTION 5: REQUESTING GOVERNMENT FURNISHED INFORMATION (GFI)

The Government has established a Bidder’s Library with DRAFT TDP material. The Government anticipates additional RFIs/Industry Days with opportunities to comment on the GFI or amend RFI responses in the future. To obtain access to the Bidder’s Library, interested companies shall provide a current copy of their approved DD Form 2345, Military Critical Technical Data Agreement verifying eligibility and authority to receive export-controlled information. In addition, interested companies must complete the Terms of Use Agreement (Attachment 1 of this RFI). The DD Form 2345 and completed Terms of Use Agreement shall be submitted via email to Spencer Bryant, Contract Specialist (spencer.m.bryant2.civ@us.navy.mil), and Tom Kostyo (thomas.f.kostyo.civ@us.navy.mil), with a copy to the Contracting Officer, Holly Danner (holly.r.danner.civ@us.navy.mil). Upon receipt and approval, the GFI will be provided.

IMPORTANT: For purposes of this RFI, each company must be able to receive classified documents up to the SECRET level. However, the Government intends to include classified attachments at the TOP SECRET/SCI/U.S. only level included as part of any future solicitation. Therefore, prime contractors interested in bidding under any subsequent solicitation must be able to receive classified documents up to the TOP SECRET/SCI level and must be a United States (U.S.) company or an independent U.S. subsidiary. The Navy will consider foreign contractors acting as subcontractors to U.S. prime contractors. The export of defense articles, defense services, and related technical data is subject to the Arms Export Control Act and the International Traffic in Arms Regulations (ITAR) and requires the issuance of an export license by the U.S. Department of State.

Please make the request as soon as practicable as it may take several days for the Government to review and approve access to the documents.

Attachments/Links