eXtended Range Counter-sUAS Missile (XRC)

Active

Contract Opportunity

REQUEST FOR INFORMATION OR PLANNING PURPOSES

The government will not pay for any costs related to the RFI response.

Your response will be treated as information only. It shall not be used as a proposal.

This RFI is issued for the purpose of acquiring information on research, development, and testing of interceptor technologies for application in United States (U.S.) Army missile systems.

Pursuant to FAR 15.2 this notice is being issued as a Request for Information (RFI). Any questions concerning this posting should be sent to the Contracts Point of Contact (POC) Charity Andrews, US Army Contracting Command-Redstone, CCAM-MZA-B, Redstone Arsenal, AL, charity.d.andrews.civ@army.mil.

The U.S. Army Combat Capabilities Development Command (DEVCOM) Aviation and Missile Center (AVMC) is currently conducting market research only. No award is intended as a result of this synopsis nor does the government intend to pay for information received. Responses to this notice are not an offer and cannot be accepted by the government to form a binding contract. RFI Responses will only be accepted from U.S. companies and organizations. Foreign participation is not authorized for these responses.

SYNOPSIS.

The AvMC Missile Science & Technology (S&T) Capability Area Lead (CAL) for Air and Missile Defense (AMD) is conducting research to identify potential interested sources with the capability to develop a new Stinger Vehicle Universal Launcher (SVUL) compatible missile (and/or contributing component) technologies with greater range than the current Stinger for the Counter-Small Unmanned Aircraft System (C-sUAS) mission in support of the eXtended Range Counter-sUAS (XRC) S&T program.

This request is to inform planning of the XRC S&T program to mature missile concepts for potential transition in the mid to far term. As a result, respondents should consider describing concepts and/or component technologies at any development stage that could be matured to a system/subsystem model or prototype demonstration in that timeframe.

XRC STRATEGY.

The XRC program objectives are to investigate, design, and develop C-sUAS kinetic missile interceptor capabilities and/or component technologies that increase range, reduce reaction time, increase lethality, improve reliability, and reduce reload time for fixed site and mobile C-sUAS configurations. Objectively, the missile concept would maintain lethality against traditional MSHORAD targets. This project will provide maneuver forces a quick-response, high speed, long-range kinetic interceptor capability against Group 3 sUAS that operate at higher altitudes with greater standoff ranges for Multi-Domain Operations (MDO). XRC seeks to establish technical viability of an extended range interceptor compliant with the SVUL and Forward Area Air Defense Command and Control (FAAD C2). XRC may be integrated with Army air defense & C-UAS systems to support fixed, semi-fixed, mobile, mounted, and dismounted (objective) C-sUAS operations.

Starting in FY25 the government intends to collaboratively develop component and all-up-round (AUR) technologies with industry while maintaining internal AvMC research teams for verification and collaboration throughout the XRC program. The government anticipates this technology development will culminate in AUR prototype demonstration before FY30.

XRC GOALS.

The XRC programmatic goals are as follows:

1. Missile concepts must be capable of defeating Group 2-3 sUAS, assuming ground system support is provided to the XRC missile. A missile includes all the components necessary to execute the engagement of a threat given receipt of track from an external C2 system (before and after launch), the authority to engage, and launch support.


2. Missile concepts should have versatile employment options (fixed/semi-fixed, mounted, dismounted (objective)) and should prioritize integration with the SVUL and Forward Area Air Defense Command and Control (FAAD C2). Concepts should consider integration with existing Army AMD launchers/platforms.

1. Missile concepts should increase range, reduce reaction time, increase lethality, improve reliability, and reduce reload time against Group 2 & 3 sUAS that operate at higher altitudes with greater standoff ranges for MDO.


2. Candidate missile concepts must be capable of conducting a ~5 year development program to achieve prototype demonstration, including a flight representative simulation with integrated tactical flight software, hardware-in-the-loop testing, and flight testing.

1. Candidate solutions must be capable and suitable for maneuver force operations in all battlefield environments. Solutions must be on path to meet insensitive munitions compliance requirements, and support such considerations as safety, human factors, transportability, mobility, cybersecurity, training, and Army Integrated Logistics Support (ILS).


2. The system must be capable of supporting high reliability, operational availability, and materiel availability in an operational combat environment.

SCHEDULE.

The schedule below is intended to best inform government and industry of the state of the art technology for extended range missiles in small form factor. The RFI release is to allow respondents time to gather their applicable knowledge and prepare for a government run Industry Day. Industry Day is intended to generate significant programmatic and technical discussions between the government and industry. There will be in person and virtual options. The government intends to have open discussion with respondents throughout the RFI period so that we have captured status of industry as it pertains to the technical realism of the XRC program.

Date

Event

9/16/2024

DEADLINE: Company submits intent to respond to RFI, intent to attend Industry Day, and Visitor Access Request (VAR) information

9/18/2024

Industry Day at Redstone Arsenal in Huntsville, AL

9/18-19/2024

In Person Company and Government sessions

10/24/2024

DEADLINE: Company requests “DoD SAFE request drop-off”

For more information visit: https://safe.apps.mil/ (applicable to Unclassified Controlled Information CUI) responses only)

10/31/2024

DEADLINE: Company RFI Responses Due by 11:00 PM CST

RESPONSE INTENT.

Government POC:

John J. Gibbs, john.j.gibbs7.civ@army.mil

DEVCOM Aviation and Missile Center (AvMC),

Attn: FCDD-AMT-M, Redstone Arsenal, AL 35898

Administrative POC:

Victoria Bowie, victoria.k.bowie.ctr@army.mil

Respondents are also encouraged to attend an XRC Industry Day. Industry Day will define capability gaps, key technical metrics, and state-of-the-art interceptor technology based on AvMC internal testing and trade studies. The government intends to have technical discussions with industry at the CUI level but can support discussions up to the SECRET level, if desired.

Industry Day respondents must submit VARs no later than September 16, 2024 to receive an XRC Industry Day invitation and approval to attend the September 18, 2024 event at Redstone Arsenal, Huntsville, AL. A virtual attendance/admittance option is also available, and a VAR submission is required for the virtual Industry Day Meeting option.

Send Visitor Authorization Requests (VARs) via DISS:

SMO Code: W1DFAATDD

Meeting/Justification: XRC Industry Day

Meeting Location: DEVCOM Aviation & Missile Center - 5400 Fowler Road, Redstone Arsenal, AL 35898

Meeting Dates: September 18-19, 2024

Government POC: John J. Gibbs, john.j.gibbs7.civ@army.mil

Administrative POC: Victoria Bowie, victoria.k.bowie.ctr@army.mil

Please email Victoria Bowie by September 16, 2024 to RSVP and confirm VAR has been received.

RESPONSE CONTENT.

COVER PAGE:

Please provide one page with the following information:

1. Company Name


2. Mailing address


3. Classified mailing address (if available)


4. Commercial and Government Entity (CAGE) code


5. Data Universal Numbering System (DUNS) code (if applicable)


6. Valid name, e-mail, and phone number of a designated company point of contact


7. Web page URL

Part A. Business Information: (Suggested 0.5 Pages)

Please provide the following information for your company and for any teaming or joint venture partners:

1. Active Security Clearance Level of the respondent and potential teammates/subcontractors (Facility and Personnel)


2. Size of business pursuant to North American Industry Classification System (NAICS) 541715 – Guided missile and space vehicle parts (except engines) research and development


3. Based on the above NAICS Code, state (Yes/No) whether your company qualifies as a Small Business, Woman Owned Small Business, Small Disadvantaged Business, 8(a) Certified, HUB Zone Certified, Veteran Owned Small Business, Service Disabled Small Business, or Central Company Registration.

Part B. Company Capability: (Suggested 4.5 Pages)

Candidate technical solutions should be supported by company experience with missile system development, and the company’s understanding of surface-to-air-missiles as a C-sUAS solution.

1. Describe briefly the capabilities of your company and the nature of the goods and/or services you provide. Include a description of your staff composition and management structure.


2. Describe your company's past experience (no more than five examples) on previous projects similar to this requirement. Include contract numbers, dollar value, a brief description of the work performed, period of performance, indicate whether your firm acted as the prime or subcontractors and agency or organization supported.


3. Describe your processes, experience, and facilities for developing missile systems or components.


4. If you were to use subcontractor(s) for this effort, what subcontractors would you use to do what percentage of what work? What are their experiences, and do you already have a relationship with the subcontractor(s)? How many are small and/or disadvantaged businesses?


5. Describe your company's approach and capabilities in obtaining and retaining qualified and experienced personnel.


6. Describe your company's approach to quality management and inform the government of your company's compliance to quality standards.

Part C. Technical Submission: (Suggested 5 Pages)

The response will include a description of the candidate XRC Missile concept and/or missile component, and how the solution meets the goals outlined in this RFI. Your submission should also:

1. Outline key performance capabilities of your concept.
   
   
   
   1. Estimate missile key technical metrics (Government defined and estimated key technical metrics will be presented at Industry Day).
   
   
   
   


2. Describe the overall technical approach to meet the threat.
   
   
   
   1. Estimate the missile’s ability to fill capability gaps (quantification of capability gaps will be presented at Industry Day).
   
   
   
   


3. Describe Concept of Operations and allocation of time for each phase of the engagement.
   
   
   
   1. Estimate time for each component’s functional operation, including external sensor support.
   
   
   2. Estimate the number of required In-Flight telemetry updates, message size, and ideal communication bandwidth.
   
   
   3. Estimate the required accuracy of a track hand-off from external C2 system.
   
   
   4. Describe the expected soldier training required and/or Company support.
   
   
   
   


4. Describe your recommended development approach.
   
   
   
   1. Include a rough order of magnitude (ROM) cost and schedule estimates for the concept design, development, and test of your candidate solution.
   
   
   
   


5. Describe the maturity of your technologies
   
   
   
   1. Include current and projected (upon completion of a 5 year development ) Technology Readiness Level (TRL), Manufacturing Readiness Level (MRL) and Integration Readiness Level (IRL) with justification
   
   
   2. Identify major components of the proposed missile system concept and where, if anywhere, they have been previously used.
   
   
   
   


6. Identify technical and programmatic risks associated with the missile concept.
   
   
   
   1. Describe the top three risks you foresee in development of the XRC concept. What steps would you likely take to mitigate these risks?
   
   
   2. Concerns with the Government's technical or schedule goals, along with suggestions to change the Government's approach or goals to reduce risk.
   
   
   
   

Respondents with missile components-only technologies should define their component as described above where applicable. In addition, they should describe steps to integrate the component with an all-up-round solution.

REVIEW.

The submissions will be reviewed by U.S. Government (USG) personnel and their support contractors. All information provided will be adequately protected. Any proprietary information must be identified. To be reviewed, the statement "Releasable to USG Agencies and their supporting contractors for Review Only" must accompany any proprietary submission. USG personnel reserve the right to request further clarification or request presentations to enhance understanding of the respondent's submittal. Material from respondent with the exception of identified proprietary information may be incorporated into future program documentation to include future solicitations.

When reviewing, USG personnel and their supporting contractors will consider:

1. How well the concept meets the XRC strategic objective of providing an extended range kinetic effector for C-sUAS in SVUL form factor


2. Technical feasibility and level of innovation of the XRC missile (or component) concept


3. Technical risk


4. Programmatic risk


5. Assessed TRL, MRL and IRL of the candidate concept at effort initiation and conclusion

SUBMISSION INSTRUCTIONS.

1. All responses must be unclassified or CUI. All CUI responses require the respondent to request a “DoD SAFE request a drop-off” from the Administrative POC no later than October 24, 2024.


2. All responses are due no later than 11:00 PM CST, October 31, 2024.


3. Response content should comply with the following:
   
   
   
   1. Submitted electronically in an unprotected version of Microsoft Word
   
   
   2. The file name should contain the responder's company name (i.e., System concept-XYZ Corp).
   
   
   3. Limited to 10 pages (excluding Cover Page)
   
   
   4. Time New Roman, Size 12 Font, Single Spaced, 1 inch margin, with embedded figures (if used) in Microsoft Word.
   
   
   5. Less than 8 MB
   
   
   
   

UNCLASSIFIED SUBMISSION

Unclassified submissions should be submitted via email to the Contracts POC. The subject line should match the submission file name (i.e., System concept-XYZ Corp). The email of the sender should be the same as the valid e-mail of the designated company POC.

CUI SUBMISSION

1. CUI submittals should be coordinated with the Administrative POC via these steps:
   
   
   
   1. Company emails the Administrative POC with intent for CUI response.
   
   
   2. Subject Line: “{file name}Request for DoD SAFE”; {file name} is System concept-XYZ Corp
   
   
   3. Government Sends a “DoD SAFE request a drop-off”
   
   
   4. Government Sends a Passphrase to Company
   
   
   5. The Company fills out DoD SAFE site information using valid email of the designated company POC, and the subject line should match the submission file name (e.g., System concept-XYZ Corp).
   
   
   
   

Marketing material is considered an insufficient response to this RFI. Respondents should indicate which portions of their responses are proprietary and should mark them accordingly. The government will honor appropriate proprietary claims to prevent improper disclosure.

Multiple responses may be submitted from a company for AUR and component capabilities. If a company submits multiple responses, each submission should follow the steps outlined in this section. Each response should be submitted as a stand-alone submission. Each response should have a unique file name. Each response will be reviewed individually and not with a combined consideration of another submission.

Contracts POC

Charity Andrews, US Army Contracting Command-Redstone

Attn: CCAM-MZA-B, Redstone Arsenal, AL 35898

charity.d.andrews.civ@army.mil

Attachments/Links