Request for Information (RFI) W911SR-26-RFI-VIPER_Final.pdf

REQUEST FOR INFORMATION (RFI)

VEHICLE INTEGRATED POINT ENHANCED RADIAC (VIPER)

W911SR-26-RFI-VIPER

1.0 DISCLAIMER

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes – it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. Solicitations are not available at this time. Requests for a solicitation will not receive a response. This notice does not constitute a commitment by the United States Government to contract for any supply or service whatsoever.

All information submitted in response to this RFI is voluntary; the United States Government will not pay for information requested nor will it compensate any respondent for any cost incurred in developing information provided to the United States Government. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. If a solicitation is released, it will be synopsized on SAM.gov. It is the responsibility of the potential offerors to monitor this site for additional information pertaining to this requirement.

The information provided in this RFI is subject to change and is not binding on the Government.

All submissions become the property of the Government and will not be returned. Proprietary, confidential, privileged commercial or financial information submitted in the RFI response should be marked accordingly to ensure appropriate handling and disposition by the Government. No classified information shall be submitted in the RFI response.

2.0 INTRODUCTION & PURPOSE

Ionization radiation occurs naturally and is increasingly used in civilian applications. The possibility of a nuclear battlefield increases the possibility of Service Members receiving total doses of radiation above public health guidelines. Managing total dose is a part of the commander’s responsibility for force protection. As part of the risk management process, applying radiation safety mitigation measures should act in concert with other risk mitigation measures to minimize the overall risk. The highest risk of significant casualties will usually occur from the conventional weapons threat.

Manned platforms currently lack the capability to communicate crew exposure data to a Common Operational Picture (COP). Fielding a networked crew monitor to general purpose mounted forces would enable the Army to identify and penetrate areas on the battlefield with the least amount of radiological contamination. Commanders will use this information to enable platforms and their crews to maintain freedom of maneuver and exploit, as safely as possible, areas the enemy has purposefully contaminated. The joint force could then use compiled crew exposure data to shape re-compete operations and inform potential avoidance maneuvers for follow-up surge and re-supply forces.

Joint Project Manager CBRN Sensing under the Joint Product Manager Integrated Early Warning is conducting a market survey to identify potential industry sources capable of providing Vehicle Integrated Platform Enhanced RADIAC (VIPER) development, testing and platform integration support.

VIPER provides rapid and accurate monitoring of platform crew exposure to radiological and nuclear hazards replacing the legacy AN/VDR-2 and AN/UDR-13 systems developed in the 1970s and 1980s. It modernizes the platform mounted monitoring capabilities used across the U.S. Army’s currently fielded manned ground and aviation platforms.

This is a standalone capability designed to integrate into various Army ground-based and aviation platforms. VIPER provides network capable, integrated gamma dose rate, total dose and prompt dose detection and monitoring both inside and outside of platforms.

The VIPER system is envisioned to provide integrated gamma dose rate, residual dose, prompt dose detection and monitoring within military vehicles, and approximate environmental radiation levels outside the platform. As such, it supports dismounted crew operations by approximating radiation levels in the environment outside the platform. This information is provided to commanders via dedicated data port(s) with networking capabilities enabling it to send crew exposure data to the host platform for immediate personnel protection actions, and dissemination to Army mission command software systems.

The system will calculate outside dose using attenuation factors based on materials used in platform construction. The consolidated readings from vehicles outfitted with VIPER can develop the COP on the location and intensity of radiation across the battlefield allowing commanders to make informed decisions.

Ideally any proposed solution would incorporate designs based on mature proven technologies, such as products considered Government Non-Developmental or Commercial-Off-The-Shelf solutions (COTS). However, since the VIPER Radiac must operate in a complex environment, it’s acknowledged that development efforts will likely be required, at minimum to meet military environmental standard specifications, such as listed in MIL STD 810H and/or MIL STD 461G and/or MIL STD 464.

Any final design needs to be sufficiently robust to survive continuous use and operation on a wide range of platforms and be sufficiently hardened to survive possible nuclear events. Some being platforms which create significant vibration levels and others which create significant Electromagnetic Interference (EMI) fields within which the designed system must continue to operate.

Following review of the RFI responses, the Government will make determinations regarding next steps with the VIPER program.

Potential NAICS Code: 334519 Other Measuring and Controlling Device Manufacturing PSC Code: 6665 Hazard-Detecting Instruments and Apparatus

3.0 GENERAL TECHNICAL CAPABILITIES & SURVIVABILITY (PUBLIC

RELEASE)

Encouragement of Alternative Technologies: The Government's primary objective with this RFI is to identify alternative, robust sensor technologies that move beyond the limitations of traditional Geiger-Müller (GM) tubes.

Legacy GM-tube technology is historically vulnerable to extreme physical environments and struggles with response times and saturation during high-intensity events. The Government is highly interested in innovative, non-GM tube designs (e.g., ruggedized solid-state sensors, scintillators, or other advanced semiconductor technologies) capable of operating across a diverse range of complex military platforms, including wheeled, tactical ground vehicles and aviation assets.

To accommodate public posting, the parameters below represent the broad general characteristics and capabilities required of the VIPER system.

Note: To facilitate responses from vendors who may not be authorized to access CUI Technical Specification Summary (see Section 6.0 below for access requirements) or who offer alternative commercial capabilities, the following represents the high-level, unclassified baseline characteristics of the desired system. Exact numerical thresholds and objective criteria are housed within the CUI Technical Specification Summary; see Section 3.2 for access instructions.

3.1 High-Level General System Characteristics (Public)

• Alternative Detection Technology: Solutions that utilize robust detection hardware beyond traditional GM tubes, offering improved physical survivability and faster response times.

• Broad Dynamic Range & Sensitivity.

• Platform Survivability (Mechanical & Environmental).

• EMI & Cybersecurity Hardening.

• Vehicle Data Integration & Networking.

• Size, Weight, and Power (SWaP) Optimization.

• Maintainability & Calibration Concepts.

3.2 Access to Detailed Technical Specification Summary (CUI Attachment)

The highly specific parameters of the design envisioned and desired capabilities such as exact dose rate ranges, shock/vibration profiles, power draw thresholds, and mean-time-to-repair metrics are contained in the restricted Technical Specification Summary attachment.

The Technical Specification Summary attachment contains Controlled Unclassified Information (CUI). Please see Section 6.0 below for instructions and security prerequisites required to request access to this document.

Vendors may choose to submit a response based on the general public information in this RFI if they do not meet the restrictive requirements of the CUI Technical Specification Summary, but they must clearly state so in their submission.

4.0 REQUESTED INFORMATION OF INTEREST

Note for Vendors without CUI Access: If your organization does not possess the requisite cybersecurity certifications (e.g., CMMC Level 2) to access the CUI Technical Specification Summary attachment, you are still highly encouraged to submit a response and pricing data.

For Items 3, 4, and 5 below, please base your answers and gap analysis on your system's ability to meet the qualitative, general operational characteristics outlined in the public Section 3.1.

If your organization has the potential capability to provide the required products/services, please provide the following information:

1. Administrative Profile: Organization name, address, primary points of contact (POCs) and their email address, web site address, telephone number, Cage Code and the Unique Entity ID (Created in SAM.gov).

2. Business Profile: Company ownership (public, private, joint venture) and NAICS code (334519) with associated business classification.

3. System Capabilities and Shortfalls:

• Directly address each capability detailed in the previous paragraphs. Clearly state whether your organization/company possesses a currently available system or technology that meets each requirement.

• Provide detailed gap analysis. For each capability, identify if your current system:

• Fully Meets the requirement, or

• Partially Meets the requirement (explain limitations and provide current

TRL/MRL), or

• Does Not Meet the requirement.

4. Proposed System Design and Technology:

• Explain how your company would expect to “build” the system.

• Describe your proposed system design to address ALL stated requirements, including those not met by existing solutions. Include:

• Key system components and their functions.

• Proposed technologies and their maturity levels.

• Rationale for technology selections.

• Provide a tentative system design (if possible).

5. Maintenance and Calibration Support Concept:

• Detail your proposed Maintenance and Calibration Support Concept for the proposed

VIPER technical solution. Address:

• Planned maintenance intervals and procedures.

• Calibration requirements and procedures, with both user and depot level calibration.

• Logistics and support infrastructure.

• Training and documentation for maintenance personnel.

6. Human-Centered Design (HCD):

• Describe your approach to incorporating Human-Centered Design (HCD) principles throughout the development, testing, and fielding process.

• Explain how you will gather and integrate continuous user feedback as the system is developed, tested and fielded.

• Detail specific HCD methods and activities you will employ.

7. Relevant Experience and Test Data:

• Disclose any previous experience developing similar systems like VIPER.

• Do you possess, or have access to Government test data on any prototyping or production effort that you have undertaken, like VIPER? If applicable, please provide access to any available Government test data from previous prototyping or production efforts. Include:

• Test reports (including independent third-party, government, and internal tests) with:

Test date, location, and system configuration/version.

Test plans, data, and results.

Test facility qualifications (certifications, accreditations).

8. Licensing, Data Rights, and Intellectual Property:

• Describe all Intellectual Property (IP), licensing, and Data Rights associated with the system and software, keeping in mind the Government’s intent to secure Unlimited Rights for Government-funded developments and sufficient license rights to maintain and support the system throughout its lifecycle.

9. Other Relevant Information:

• Include any additional information you deem beneficial to this RFI and relevant to the development and deployment of the VIPER Radiac system.

10. Existing capability to manufacture VIPER systems. If this manufacturing capability has been funded in the past by the federal government, including Small Business Innovations Research (SBIR) or Small Business Technology Transfer (STTR) programs, please indicate year awarded, Federal Agencies participating, phase, and project title.

11. Sales Information. Specifically, is this solution (or one very similar to this specification) routinely sold to commercial customers and/or other government entities. Name of contract vehicle participation as a prime or subcontractor if any.

12. Please state the estimated Department of Defense Hardware/Software Technology

Readiness Level (TRL) of candidate technology (Refer to DoD Technology Readiness Assessment Guidebook, ed. June 2023).

13. Alternative Technology Trade-Off Analysis (If Applicable): If your proposed system deviates from traditional GM-tube parameters or the high-level baseline characteristics in Section 3.1, please describe:

• The operational and physical benefits of your alternative approach (e.g., extreme vibration tolerance, zero maintenance, or solid-state reliability).

• The specific engineering trade-offs (e.g., dynamic range vs. power consumption) and how they still meet the mission goal of crew protection.

5.0 SUBMISSION, PAGE LIMITATION AND DUE DATES

General RFI Submissions:

The Government is requesting that responses to this RFI do not exceed ten (10) total pages. Your response to this RFI, including any capabilities statement, shall be electronically submitted to Contract Specialist, Kevin Rohe (kevin.t.rohe.civ@army.mil) and Contracting Officer, Gentian Mulla (gentian.mulla.civ@army.mil) in Portable Document Format (PDF), via email no later than 12:00 p.m. Eastern Standard Time on October 5, 2026 and reference “W911SR-26-RFI- VIPER” in the subject line of the email and on all enclosed documents. Information and materials submitted in response to this request will become property of the Government and https://www.google.com/url?q=mailto%3Akevin.t.rohe.civ%40army.mil https://www.google.com/url?q=mailto%3Agentian.mulla.civ%40army.mil

WILL NOT be returned. DO NOT SUBMIT CLASSIFIED MATERIAL. No phone calls will be accepted.

Questions:

All questions must be submitted no later than 12:00 p.m. Eastern Standard Time on September 25, 2026. Questions shall NOT contain proprietary or classified information. An unattributed list of questions and answers will be posted at the same location of this RFI.

6.0 REQUESTING ACCESS TO THE CUI TECHNICAL SPECIFICATION SUMMARY

To receive the current Controlled Unclassified Information (CUI) Technical Specification Summary document referenced in this RFI, interested parties must submit a formal request via email to the primary Points of Contact (POCs) listed in Section 5.0.

Interested parties MUST provide the following verified evidence of security compliance with their access request:

• Joint Certification Program (JCP) Certification: Provide a copy of an approved, active DD Form 2345 (Joint Certification Program).

• NIST SP 800-171 Assessment (SPRS): Provide evidence of a current assessment (completed within the last 3 years) uploaded to the Supplier Performance Risk System (SPRS) in accordance with DFARS 252.240-7997 (NIST SP 800-171 DoD Assessment Requirements - DEVIATION 2026-O0025).

• CMMC Level 2 (Self-Assessment): Provide evidence of a completed Cybersecurity Maturity Model Certification (CMMC) Level 2 (Self) assessment aligned with NIST SP 800-171 Rev 2 and reflected in SPRS for each contractor information system that will process CUI.

• Safeguarding Confirmation: Provide a signed statement on company letterhead confirming full compliance with the safeguarding and cyber incident reporting requirements of DFARS 252.204-7012.

Failure to provide all the above information will prevent the Government from providing access to the CUI Technical Specification Summary.