RFI - VPS - LWR - 30SEP2025.pdf

Request for Information for Laser Warning Receiver

(LWR)

30 September 2025

Distribution Statement A: Approved for public release; distribution is unlimited.

DESCRIPTION OF INTENT:

THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. No award will be made as a result of this request.

DESCRIPTION:

The Vehicle Protection System (VPS) Laser Warning Receiver (LWR) is an Acquisition Category (ACAT) II program currently in production as a survivability sensor for ground combat vehicles.

The Army is assessing market research to inform a potential production contract for award in FY26. The

Government will utilize a Performance Specification to solicit for prospective vendors. A potential requirement could exceed procurement up to 4,000 kits.

DISCLAIMER:

Reference herein to any specific commercial company, product, process, or service by trade name, trademark, manufacturer, or otherwise, does not constitute or imply its endorsement, recommendation, or favoring by the USG or the Department of the Army (DA). The opinions of the authors expressed herein do not necessarily state or reflect those of the USG or the DA and shall not be used for advertising or product endorsement purposes.

GENERAL INFORMATION:

There is no risk to respondents for participating in this RFI. Participation in this effort is strictly voluntary, resulting in no cost or obligation incurred by the USG. The USG is not bound to this information if any solicitation is issued. However, this is an important opportunity for industry to provide input on this program. This RFI, and all information herein, is for informational planning purposes only and does not constitute a proposal request of any kind. All respondents therefore understand that there is no commitment by the USG.

INSTRUCTIONS FOR RESPONDING TO THIS REQUEST:

The USG will not publish any notifications regarding the results of this RFI, or any information identifying the respondents of this RFI.

Responses are expected to remain solely UNCLASSIFIED for this RFI. Controlled Unclassified Information

(CUI) is not authorized. All respondents shall submit via e-mail to the UNCLASSIFIED e-mail addresses listed at the bottom of this posting. Microsoft Office applications or Adobe Acrobat is preferred.

Respondents wishing to submit proprietary information may request a link to submit the proprietary data through the DoD SAFE (Secure Access File Exchange). Contact Mr. Chester Ho, chester.c.ho.civ@army.mil for a link to transmit files through DoD SAFE.

Responses are due no later than 1700 EST on 30 October 2025.

Responses received after the stated due date are not considered by the USG as part of this RFI.

INSTRUCTIONS FOR COMPLETING THIS RFI:

1. Please respond to every question.

2. Number each response with the appropriate question number.

3. Questions do not have to be repeated in the response.

4. A “No Response” indication can be provided for those questions with a “no” answer.

5. If a response will satisfy another question, state: “See response to question XX.”

6. Include relevant sales media and product manuals. If providing an ACROBAT formatted manual, annotate the manual to indicate which material is applicable to the questions. If preferred, include

Internet Web links to locations where animations/videos may be viewed.

7. If providing sales media and/or manuals containing a restricted distribution statement, issue a release statement indicating that the restricted material may be distributed to Army personnel involved with this

RFI.

8. Spell out any acronyms in their first instance.

9. Clearly mark any proprietary information. If applicable, the front page of the response package should state, “Proprietary Information Contained.”

ADMINISTIVE INFORMATION:

1. Manufacturer

a. Company Name:

b. Mailing Address:

c. CAGE:

d. DUNs Number:

e. Company Web Site:

Business Type (Check or identify in your response all that apply):

8(a) Minority Owned

Disabled Veteran Small Business

Hub Zone Small-Disadvantaged

Large Business Women Owned

2. Personnel Responding to this Questionnaire:

a. Name:

b. Title:

c. Responsibility/Position:

d. Telephone/Fax Numbers:

e. E-mail address:

QUESTIONAIRE: Please provide answers to all the following questions with a “not applicable” being acceptable.

1. Security:

a. Does your company currently have a Facility Security Clearance (FCL) for an Army

Contract.

i. Provide current contract number

ii. Provide current facility clearance level

iii. Identify the names and titles of all Key Management Personnel (KMP)

b. If your company does not have a current FCL, would your company be able to produce proof of an FCL or one in process if one is not already obtained by 1 Oct 2026?

i. Proof provided could include:

1. At least a SECRET final facility clearance level

2. At least an interim SECRET facility clearance

3. An existing facility clearance sponsorship letter and documentation that reasonably demonstrates that the facility clearance is in the final stages of obtaining one.

c. Does your company currently meet National TEMPEST standards and which standard?

i. Does your company have a TEMPEST Control Plan in place?

ii. Who is the Accrediting Official (AO) and Certified TEMPEST Technical Authority

(CTTA)?

2. Small Business Questions (if applicable):

a. What are your company’s core competencies?

b. Provide relevant examples of past project or contracts that demonstrate your ability to meet the Army’s LWR requirements.

c. What is the size of your company, how many employees, annual revenue?

d. Will your company have to hire to support this contract? If yes, where will you go to get personal? How quickly can you obtain personnel? If this will be a big growth step for your company, how will you handle the sudden growth and its impact to managing your company? Do you have a growth plan?

e. Do you have any current or past performance issues with the government (e.g., cure notices, negative past performance evaluations)?

f. Are you registered in the System for Award Management (SAM)?

3. Production Capability:

a. Is your company able to perform First Article Testing (FAT)/ First Article Inspection (FAI) on the kit produced for this contract?

i. Is your company able to deliver the initial set of kits within 12 months of contract award? If not, provide a more accurate delivery timeline.

ii. Is your company able to complete quality acceptance in 6 months? If not provide a more accurate quality acceptance timeline.

iii. Is your company able to provide 12 months production lead time after quality acceptance? If not provide a more accurate production lead time.

4. Technical Capabilities:

a. Provide an UNCLASSIFIED ONLY discussion demonstrating your company’s understating of how to provide the U.S. Army a capability for the below characteristics. Companies should provide analysis or test data when possible.

i. Currently integrated on-platform systems can make LWR sensor locations challenging to meet an installed field of view (FOV). Can the sensors of the Laser

Warning Receiver be located on different planes to provide FOV coverage over

360° in azimuth and at least -20° to + 60° in elevation? The use of multiple sensor heads to achieve FOV requirements is permissible.

ii. Threat Classification: Does the system detect and declare laser threats by classification: Laser Range Finder (LRF), Laser Target Designator (LTD), or Laser

Beam Rider (LBR) when presented with those types of systems?

iii. Data Storage: Does the system contain non-volatile memory to store threat data on a rolling basis from at least the 100 most recent threat events? Can the system store the following data (if available) for each event: threat type, threat pulse repetition interval (PRI), Angle of Arrival (AoA) relative to the platform, threat bearing, vehicle longitude and latitude, vehicle attitude, and GPS time? Is the data able to be extracted via a host platform interface. Can data be retained in memory until erased on command?

iv. Does the system have the ability to detect and declare multiple threats simultaneously?

v. Modular Active Framework (MAF) Compliance:

1. Does your company have experience with MAF Compliance requirements?

a. If not, is there an industry standard that is similar to MAF compliant systems that your company has followed?

b. Describe the industry standard that is similar to MAF compliance, if applicable.

2. Describe what your company has done in relation to MAF compliance, what was the process, certification received?

3. With complete MAF and Technical Capabilities, does your system meet the Size Weight and Power (SWaP) requirements of 11.34 kilograms (25 pounds), 0.03m3 volume, and consume less than 100 watts of power?

a. See Appendix A for the complete chart of MAF Compliance requirements as it pertains to Laser Warning Receiver. For this

RFI, the “subsystem” is the LWR. Mark Yes, No, or Unknown in the System Ability column of the chart.

Please send any Questions, Comments, or Concerns to the e-mail addresses listed at the bottom of this posting.

POINT OF CONTACT INFORMATION:

Mr. Chester Ho, chester.c.ho.civ@army.mil

APPENDIX A

LASER WARNING RECEIVER (LWR) MODULAR ACTIVE FRAMEWORK (MAF) REQUIREMENTS

Requirement Title Requirement Description System Ability

(Yes/No/Unknown)

Allow Only Approved Remote Access

Methods

The Subsystem shall allow only the following approved remote access method, if remote access is required:

Secure Shell (SSH).

Enforce Disabling of Functions, Ports, Protocols, and Services

(PP&S)

The Subsystem shall enforce disabling of functions, ports, protocols, and services within the information system deemed to be unnecessary and/or nonsecure, as defined in the MAPS Active Controller (MAC) Controlled Element

PP&S.

Allow Incoming Communications from

Authorized Sources

The Subsystem shall only allow incoming communications from authorized sources routed to authorized destinations, as defined in the MAC Controlled Element PP&S.

Transition to Fault Mode - Intermittent

Heartbeat Failure

The Subsystem shall, upon not receiving a "Heartbeat" for five (5) of the last ten (10) cycles, transition to Fault Mode.

Output "Registration Request"

The Subsystem shall, upon recognizing a communication channel has been established (T) and receipt of the "MCE Authentication Success" (O) input, output "Registration

Validate and Apply Configuration Data

The Subsystem shall, upon receipt of the "Configuration Data" input, validate and apply the configuration data.

Output "Configuration Result"

The Subsystem shall, upon validating and applying the configuration data, output "Configuration Result"

Output "Threat Report"

- Threat Present

The Subsystem shall, upon detecting a threat, output "Threat Report"

Output "Threat Report"

- Threat No Longer

Present

The Subsystem shall, upon determining that a threat is no longer present, output "Threat Report" indicating the threat is no longer present.

Lock Physical

Maintenance Port(s)

The Subsystem physical maintenance port(s) shall be locked (i.e. inputs disallowed) upon the conclusion of maintenance activities.

Perform Integrated Built in Test (IBIT)

The Subsystem shall, upon receipt of the "IBIT Command" input, perform IBIT

Output "IBIT Report" The Subsystem shall, upon performing IBIT, output "IBIT

Report"

Perform Startup BIT The Subsystem shall, upon powering up, perform startup

BIT.

(Yes/No/Unknown)

Use Gigabit Ethernet

(IEEE 802.3) for Non-deterministic Messages

The Subsystem shall, upon the establishment of a communication channel (T) / secure communication channel (O), use Gigabit Ethernet (IEEE 802.3) for all non-deterministic messages

Use Deterministic

Ethernet (IEEE 802.1

AVB/TSN) for

Deterministic Messages

The Subsystem shall, upon the establishment of a communication channel (T) / secure communication channel (O), use deterministic Ethernet (IEEE 802.1

AVB/TSN) for all deterministic messages.

Output "Heartbeat"

The Subsystem shall, upon outputting the first "Secure

Heartbeat", begin to output "Heartbeat" at the rate cited in the configuration file. (T)

Output "Fault Report" -

Initialization

The Subsystem shall, upon performing startup BIT (T) and outputting the first "Secure Heartbeat", output "Fault

Report" for any faults set/cleared during initialization (one

Fault Report per fault) (T).

Output "Subsystem

Status Report"

The Subsystem shall, upon outputting the first

"Heartbeat", assess subsystem status and begin to output

"Subsystem Status Report" at the rate specified in the configuration file.

Output "Mode Status" -

Standby

The Subsystem shall, upon outputting the first "Subsystem

Status Report, transition to Standby Mode and output

"Mode Status" if no critical faults are detected.

Updateable Software

The Subsystem software, including firmware on reconfigurable logic flashes but excluding safety-critical devices designed to be programmed once, shall be updatable.

Permit Modes, Sub-

Modes, Transitions

The Subsystem shall permit only MAF directed the modes, sub-modes, and transitions.

Output

"Communication

Channel Request"

The Subsystem shall, upon powering up, output

"Communication Channel Request".

Wait for Configuration

Data

The Subsystem shall, upon outputting "Registration

Request", wait for configuration data.

Output "Registration

The Subsystem shall, upon failing to receive the

"Configuration Data" input within the registration time limit, output "Registration Request".

(Yes/No/Unknown)

Provide a One Pulse per

Second Signal

The Subsystem shall provide a single-ended one pulse per second signal at a standard TTL gate signal level (3.3V or

5V) to a pin on the logic-bearing element with the gPTP clock.

The signal will be used to monitor the Maximum Time

Interval Error (MTIE) of the gPTP 1 second rollover bit in laboratory settings.

AOP-52

The Subsystem shall comply with sections 4.1, 4.2, 4.3, and

4.5 through 4.11 of AOP-52 (Edition 1).

MIL-STD-882E The Subsystem shall comply with MIL-STD-882E.

MIL-STD-1472G

The Subsystem shall comply with the MIL-STD-1472G.

Identify the sections in compliance.

Output "IBIT Report" -

IBIT Cancelled

The Subsystem shall, upon receipt of the "IBIT Command" input indicating IBIT is to be cancelled, cancel IBIT and output "IBIT Report" indicating all in-process IBIT has been cancelled.

Output "Fault Report"

The Subsystem shall, upon performing IBIT, output "Fault

Report" for any faults set/cleared during IBIT (one Fault

Report per fault).

Safe Hazardous

Elements Then

Transition to Off Mode

The Subsystem in Active Enabled, Maintenance/Active or

Sense Only Mode shall, upon receipt of the "Zeroize" input indicating Zeroize=Asserted for at least three seconds without interruption, safe any hazardous elements and then transition to Off Mode.

Safe Hazardous

Elements Then

Transition to Fault

Mode

The Subsystem in Active Enabled or Sense Only Modes shall, upon determining that a Critical fault exists, safe any hazardous elements and then transition to Fault Mode.

Store Configurable

Registration Time Limit

The Subsystem shall store a configurable registration time limit (the time after outputting "Registration Request", waits before outputting another "Registration Request") in non-volatile memory. The registration time limit will not be contained in the "Configuration Data" input the MAC receives during registration.

(Yes/No/Unknown)

Output "Subsystem

Status Report"

The Subsystem shall output "Subsystem Status Report" at the rate cited in the configuration file.

Output "Fault Report" -

All OPERATIONAL

Modes Except

Initialization

The Subsystem in all OPERATIONAL Modes except

Initialization shall perform continuous BIT and output a

"Fault Report" if a fault is detected or cleared (one Fault

Report per fault).

Mode

The Subsystem in Initialization, Standby or Training Modes shall, upon determining that a Critical fault exists, transition to Fault Mode.

Output "Heartbeat" The Subsystem shall output "Heartbeat" at the rate specified in the configuration file.

Accept "Heartbeat" The Subsystem shall accept a periodic "Heartbeat"

Output "Mode

Acknowledgment"

The Subsystem shall, upon receipt of the "Mode Transition

Command" input and prior to transitioning to the commanded mode, output "Mode Acknowledgment"

Output "Mode Status" The Subsystem shall, upon completing a transition to a new mode, output "Mode Status"

MIL-STD-1275E The Subsystem shall comply with MIL-STD-1275E.

Transition to Normal

Operation Mode After

Reverse Polarity

The Subsystem shall transition to normal operation mode within 100 ms when reverse polarity applied to +28 VDC input returns to normal operational voltage range.

Mode - Consecutive

Heartbeat Fault

The Subsystem shall, upon not receiving a "Heartbeat" for three consecutive cycles, transition to Fault Mode.

Identify Hazardous

Conditions

The Subsystem shall identify hazardous conditions (caused by subsystem equipment) with signs / labels that comply with ANSI Z535.4-2011.

Identification Markings The Subsystem shall have item identification markings in

English on each of its LRUs.

Log MAF Messages

The Subsystem shall log all sent and received MAF messages in accordance with the MAF Message Logging setting cited in the configuration file.

(Yes/No/Unknown)

Synchronize Clock

The Subsystem shall synchronize its clock with network time using 802.1AS generalized-Precision Time Protocol with a jitter of less than 5 μs.

Fault Table

Implementation

The subsystem shall implement all applicable Standard

Faults AND any faults identified within the Subsystem

MCE Operate

Continuously Without

Failure

The subsystem shall, upon successfully initializing with the

Vehicle Base Kit (VBK), operate continuously without failure for a period of at least 72 hours.

Network Settings

Implementation

The subsystem shall implement the network settings IAW the MAF Network ICD.

Power Down to a Safe

State

The Subsystem shall power down to a safe state.

Check Software

Signature

The Subsystem shall, upon determining software integrity is valid, check software signature.

Output "M_Software

Update Status"

The Subsystem shall, upon determining the software signature is invalid, discard the software update and output "M_Software Update Status" indicating Status=Not

Staged.

The Subsystem shall, upon determining the software signature is valid, stage the software update and output

"M_Software Update Status" indicating whether the software update is or is not staged.

Accept "M_INS Data

Output" Input

The Subsystem shall accept the "M_INS Data Output" input.

The Subsystem shall, upon receipt of the "M_Software

Update Request" input indicating Request=Software

Update Readiness, output "M_Software Update Status" indicating the subsystems’ readiness for a software update.

The Subsystem shall, upon determining software integrity is invalid, discard the software update and output

"M_Software Update Status" indicating Status=Not

Staged.

The Subsystem shall, upon receipt of the "M_Software

Update Request" input indicating Request=Cancelled, (Yes/No/Unknown) cancel the software update and output "M_Software

Update Status" indicating Status=Cancelled".

Output "M_Secure

Connection Request"

The Subsystem shall, upon receipt of the "M_Software

Update Request" input indicating Request=Secure

Connection, output "M_Secure Connection Request"

Data Integrity"

The Subsystem shall, upon completed delivery of the

"M_Software Update" inputs, verify software integrity and output "M_Software Data Integrity"

The Subsystem shall, upon receipt of the "M_Software

Update Request" input indicating Status=Install, install the software and output "M_Software Update Status" indicating whether the subsystem is ready for reboot or experienced an error during software installation.

Accept Software

Updates

The Subsystem shall have the ability to accept software updates without impact to current software.

Read a De-asserted

State

The Subsystem shall read a de-asserted state when the resistance to 28 VDC return is in a high impedance (greater than 1 Mohm) state.

Read an Asserted State

The Subsystem shall read an asserted state when the voltage on the output connector is less than or equal to

4.9 VDC.

Note: The transition to the asserted state may take place at a voltage higher than 4.9 VDC.

Implement Maximum

De-bounce

The Subsystem shall implement a maximum de-bounce of

10 ms.

Implement Minimum

De-bounce

The Subsystem shall implement a minimum de-bounce of

5 ms.

Isolate De-bounce

Circuitry

The Subsystem's de-bounce circuitry shall not introduce capacitive characteristics to the input/output pin.

Limit Output Source

Current

The Subsystem shall limit the output source current to a maximum of 50 mA.

Pull Up Discrete Signals The Subsystem shall pull up all discrete signals to the platform 28 VDC power bus.

(Yes/No/Unknown)

Read an Asserted State

The Subsystem shall read an asserted state when the resistance to the 28VDC platform return is less than 200 ohms.

Accept Discretes at 20-

33 VDC

The Subsystem shall be able to accept discretes over a range of 20-33 VDC.

Limit Leakage Current

The Subsystem shall limit leakage current to the LRU's internal pull-up source to less than 250 uA when connected to 28 VDC RTN through a 100 Kohm resistor.

Transition to Off Mode

The Subsystem shall, upon receipt of the "Zeroize" input indicating Zeroize=Asserted for at least three seconds without interruption, transition to Off Mode.

Indicating Zeroize

Status=Asserted

The Subsystem shall, upon receipt of the "Zeroize" input indicating Zeroize=Asserted, output "Subsystem Status

Report" indicating Zeroize Status=Asserted.

Erase Cryptographic

Keys

The Subsystem shall, upon receipt of the "Zeroize" input indicating Zeroize=Asserted for at least three seconds without interruption, erase all cryptographic keys.

Indicating Crypto Key

Status=Zeroized

The Subsystem shall, upon erasing all cryptographic keys, output "Subsystem Status Report" indicating Crypto Key

Status=Zeroized.

Prevent Installation of

Software Components

The Subsystem shall prevent the installation of all software components without a digitally signed certificate.

Prevent Installation of

Firmware Components

The Subsystem shall prevent the installation of all firmware components without a digitally signed certificate.