Active

Contract Opportunity

Procurement Technical Assistance Centers (PTACs) are an official government contracting resource for small businesses. Find your local PTAC (opens in new window) for free government expertise related to contract opportunities.

I. Description:

The Army Contracting Command - Redstone, Redstone Arsenal, Alabama 35898, on behalf of the Strategic and Operational Rockets and Missiles (STORM) Project Management Office (PMO), Program Executive Office Missiles and Space, hereby issues the following Sources Sought/Request for Information (RFI) to ascertain the level of interest of potential vendors desiring to contract for the development and production of a new Multiple Launch Rocket System (MLRS) Family of Munitions (MFOM) Joint Reduced Range Rocket (JR3). The Government is interested in a JR3 that is a representative model or prototype system in an All-Up Round configuration, which can be tested in a relevant environment in preparation for rapid development or fielding, qualification, and production. This solution must be suitable for integration on currently fielded M270 MLRS or M142 High Mobility Artillery Rocket System (HIMARS) variants launchers. The solution must be capable of achieving production level maturity by Fiscal Year (FY) 2028.

The JR3 will be a surface-to-surface, live fire, qualification rocket. It will provide MLRS and HIMARS batteries the opportunity to conduct live fire training at varied ranges, in varied environmental conditions, and during any time of day or night. The JR3's essential role will be live fire crew qualification to allow crews to perform their Platoon, Battery, and Battalion level Mission Essential task Lists (METL) qualification tables (TC 3-09.8).

Requirement Statement: The primary driver is cost followed by the ability to incorporate the following requirements:

II. JR3 System Requirements

The STORM PMO will use the submitted White Papers to assess the ability of industry to develop a munition with the following desired characteristics.

Requirement Statements

1. JR3 should have operation, storage, and handling requirements similar to the current MFOM.

2. JR3 should achieve a munition reliability of 0.95 or better. The JR3 munition reliability is defined as a successful launch, flight, and warhead event for any selected rocket.

3. JR3 should be capable of meeting all system requirements throughout a minimum shelf life of 10 years.

4. JR3 should have a minimum impact range of 7.5 to 8 kilometers. Maximum impact range should be no greater than 15 kilometers. Minimum and maximum ranges should be based on standard atmosphere with sea level launcher and target altitudes.

5. JR3 should operate with current (US/Partner Nations) fire support infrastructure and be capable of integrating with the current M142/M270 SW suite.

6. JR3 should fly a normal trajectory (free flight and/or trajectory corrected) over friendly troops with a near precision impact no less than 25-30 meters of targeted point and 2 km fire support safety distance from impact. Worst case range safety fan shall remain within the currently fielded Reduced-Range Practice Rocket (RRPR) range safety fan.

7. JR3 should be contained in a Launch Pod envelope that meets or exceed performance specification and electrical/mechanical interface control definitions (maintain critical form, fit and function interfaces and performance) with MFOM munitions, launchers and logistical/material handling equipment. The physical dimensions of the launch pod (i.e. height, width, length, weight), as well as the mechanical and electrical interfaces, must be compatible with the current M270 series, M142 launchers and existing logistical assets. The launch pod shall be usable with the current family of launchers to avoid the cost of modifying or developing new launchers and to avoid costly changes to current logistical/material handling equipment. Detailed technical information shall be submitted if a proposed launcher modification for a feasible JR3 solution is required.

8. Loading/Unloading of the pod from the launcher and re-supply vehicle shall mimic tactical operations to include connection and loading/unloading.

9. JR3 shall be contained in a Launch Pod envelop that assumes the same current launcher volume and interface restrictions as the current MLRS/GMLRS launch pods. The launch pod shall house a minimum of six (6) and a maximum of forty-eight (48) (in multiples of 3) JR3 rockets and have the same center of gravity range within those of the current MLRS Family of Munitions (MFOM).

10. JR3 should be able to use current and future Advanced Field Artillery Tactical Data System (AFATDS) and launcher software to enable the user to execute fires from all domains.

11. JR3 warhead should be designed with Modular Open Systems Architecture (MOSA) interface between the motor and the warhead, which would allow for future growth and effects to be added without the need to design a new All Up Round. The ability to see a flash/bang/smoke as an initial or follow on increment/update is desirable.

12. JR3 software should emulate all current and future MFOM. Should be capable of being fired over the cab and sides of the launcher. Should be cleared to fire over all personnel and man-made structures within all launcher exclusion areas.

13. JR3 launch pods should be reusable and/or reloadable.

*Note: the order of characteristics does not indicate or define priority or perceived value.

Reference Technical Documentation:

• 13214701 (POD-TO-M270A1 Launcher Interface)

• MIS-48656 (Missile Command Specification Interface Control Document Electrical Interface Definition for the Multiple Launch Rocket System Fire Control System) Rev E

• MIS-49157 (Missile Command Specification Interface Control Document for the Rocket Pod, 298MM, M31 Rocket) Rev H

• MIS-49257 (Missile Command Specification Interface Control Document for the Rocket Pod, 298MM, M30E1 Rocket) Rev B

• MIS-38667 (Missile Command Specification Interface Control Document Electrical Interface Definition for the Multiple Launch Rocket System Armored Vehicle Mounted Rocket Launcher M270-202 Subsystems) Rev B

• 13027605 (Cage Interface Control Drawing) Rev G)

• MIS-52612 (Missile Command Specification Interface Requirements Specification for the Guided Missile and Launching Assembly with Ground Support Equipment ATACMS 2000 with Unitary) Rev C

• 11508910/02 (Interface Control Document, Multiple Launch Rocket System Fire Control System) Rev D

• MIS-35437 System Specification for the Reduced Range Practice Rocket M28A2 for the Multiple Launch Rocket System (MLRS) Rev D

• MIS-PRF-49150 (Performance Specification for the Guided Multiple Launch Rocket System Unitary Rocket) Rev D

• MIS-PRF-56821 (Performance Specification for the Guided Multiple Launch Rocket System Alternative Warhead Rocket) Rev B

• MIS-PRF-52607 (System Performance Specification Guided Missile and Launching Assembly, Surface Attack; M57 for ATACMS 2000 with Unitary) Rev G

The above documents can be requested by sending an email to Lindsay Jennings @ Lindsay.d.jennings.civ@army.mil and Mónica E. Clemons @ monica.e.clemons.civ@army.mil with the company name, address, CAGE Code, security clearance level, and documents requested no later than 30 October 2023. Reference Technical Documentation will only be provided to companies cleared to handle and store documentation classified to the SECRET level. The Government reserves the right to refuse release of this information to companies that fail to demonstrate adequate clearance level.

III. Technical Information Paper (TIP) Description

Based on the above scope of effort and technical characteristics, the Army Contract Command- Redstone is requesting the following information:

1. A detailed system description to include the munition and its weight, size, required power, sensors, and warhead type.


2. An assessment of system performance against each Requirement. Identify Requirements that are met, exceeded, or not met. Provide an approach to meet the Requirements not currently met, if applicable, to the training rocket.


3. Weapon mechanical, electrical, and communications interfaces, whether these interfaces support MOSA, all supported communication networks, and compatibility with current MLRS Launch Systems.


4. Environmental survivability (MIL-STD-810H) in worldwide conditions (Army Regulation 70-38).


5. A ROM unit cost for production at 1000 - 5000 munitions per year.


6. Logistics requirements to include, but not limited to (supply, maintenance, transportation, shelf life, training).


7. Software and hardware integration impacts to the existing fleet of Army platforms.


8. Human factors required for weapons/ordnance handling and employment.


9. An assessment of the Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL) of the product including key subsystems such as guidance and sensor mechanisms employed; propulsion, datalink, safe, arm, and fire device; etc. Substantiate TRL claims with descriptions of test and evaluation events associated with weapon design. Substantiate MRL assessment according to the criteria in the DoD MRL Deskbook 2018.


10. Description of the Intellectual Property and proposed Government Rights of this system.


11. Modeling and Simulation data to support the munition’s claimed capabilities.


12. Indicate readiness and willingness to participate in a U.S Government sponsored capability demonstration No Earlier Than (NET) 4QFY25 and No Later Than (NLT) 3QFY26.


13. System performance data to the extent available and relevant test data demonstrating the performance. Video evidence can be submitted and must not exceed 10 GB cumulatively.

Technical Information Paper (TIP) responses to this RFI are not-to-exceed 50 single-sided pages in length on 8.5 x 11 paper and not to be a font size no smaller than Arial 10. Responses on compact disc (CD) must be submitted via postal mail. Test data or reports substantiating the performance, TRL, and MRL should be included as attachments. TIP and attachments are limited to 100 pages and audio/video files can be no more than 30 minutes in total. All information must be readable by Microsoft (MS) Word 2019, MS Excel 2019, or Adobe Acrobat and be provided with proper markings for classified and proprietary information. If your submittal contains classified information, it should be properly labeled, handled, and transmitted in accordance with the National Industrial Security Program Operating Manual (NISPOM).

Responses should include:

1. Company Name, CAGE Code, DUNS Number, Company Address, and Place of Performance Address


2. Point of contact, including name, title, phone, and email address


3. Size of company, average annual revenue for the past three years, and number of employees


4. Whether the business is classified as a Large Business, Small Business (including Alaska Native Corporations (ANCs) and Indian tribes), Veteran Owned Small Business, Service-Disabled Veteran-Owned Small Business, HUBZone Small Business. Small Disadvantaged Business (including ANCs and Indian tribes), or Women-Owned Small Business

All respondents are encouraged to submit any questions regarding this RFI by 1600 Central Standard Time 8 November 2023. Questions regarding this announcement shall be submitted in writing by e-mail to Lindsay Jennings @ Lindsay.d.jennings.civ@army.mil or Mónica E. Clemons @ monica.e.clemons.civ@army.mil.

Verbal questions will NOT be accepted. Answers to questions will be posted to SAM.gov. No extensions to the RFI response or question period will be granted.

RFI responses should be submitted via email to Mónica E. Clemons at monica.e.clemons.civ@army.mil and Kyle Teegarden at kyle.r.teegarden.civ@army.mil NLT 8 December 2023. If the UNCLASSIFIED file(s) is larger than 5MB, please reach out to Kyle Teegarden at kyle.r.teegarden.civ@army.mil at least 24 hours prior to the submission deadline to request a “drop-off” link for the DoD SAFE Site (https://safe.apps.mil).

If any of the RFI response files contain Classified information, reach out to Mónica E. Clemons at monica.e.clemons.civ@army.mil and Kyle Teegarden at kyle.r.teegarden.civ@army.mil a week in advance of the submission to obtain instructions for submission.

IV. RFI Timeline and Industry Day Announcement

This RFI serves as the request for TIPs. The following timeline applies to this RFI.

• JR3 RFI Publication: 24 October 2023


• JR3 Reference Technical Documentation Request: 30 October 2023


• JR3 RFI Questions: 8 November 2023.


• Technical Information Paper Submittal and Receipt: TIPs with attachments and audio/video files must be received NLT 1600 Central Standard Time, 8 December 2023.


• JR3 Industry Capability Demonstration Announcement: To Be Determined


• JR3 Industry Capability Demonstration Industry Day: 12 months prior to demonstration


• JR3 Industry Capability Demonstration: NET 4QFY25 and NLT 3QFY26

V. Disclaimer

This RFI is not a Request for Proposal (RFP) and is not to be construed as a commitment by the Government to issue a solicitation or ultimately award a contract. Responses will not be considered as proposals, nor will any contract award be made because of this synopsis.

All information contained in the RFI is preliminary as well as subject to modification and is not binding on the Government. FAR clause 52.215-3, “Request for Information or Solicitation for Planning Purposes," is incorporated by reference in this RFI. The Government does not intend to pay for information received in response to this RFI. Responders to this invitation are solely responsible for all expenses associated with responding to this RFI. This RFI will be the basis for collecting information on capabilities available. This RFI is issued solely for information and planning purposes. Proprietary information and trade secrets, if any, must be clearly marked on all materials. All information received in this RFI that is marked “Proprietary” will be handled accordingly. Please be advised that all submissions become Government property and will not be returned nor will receipt be confirmed. In accordance with FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. If the interested party is a foreign concern or if a U.S. interested party has a team member or partner who is a foreign entity, they will need to adhere to all International Traffic in Arms Regulations (ITAR) requirements.

Attachments/Links