VBK Modernization RFI.pdf

PDF 186 KB Posted

Attached to
Request for Information (RFI) Vehicle Base Kit (VBK) Modernization
Solicitation number
Not on record
Issued by

About this file

This is a Request for Information (RFI) issued by the U.S. Army Product Manager Vehicle Protection Systems (PdM VPS) for the Vehicle Base-Kit (VBK) Modernization effort. The RFI was issued November 19, 2026, with responses due by December 4, 2026. The Government seeks market research on industry capabilities to develop a 3U VPX next-generation Modular Active Controller (MAC) and Safety Control and Interface Panel (SCIP). Key technical areas of interest include GPGPU integration into ruggedized 3U VPX computing environments, SOSA-aligned architecture conformance, FPGA-based discrete I/O and video processing, Time-Sensitive Networking (TSN) implementation per IEEE 802.1DP with evaluation of 1G versus 10G bandwidth options, system integration and platform maturation methodologies, safety architecture design, and cybersecurity resilience. Specific technical questions address GPGPU module availability and thermal/power challenges, FPGA family recommendations (Microchip PolarFire, AMD Zynq MPSoC, Intel/Altera), TSN endpoint solutions with particular focus on Layer-2 hardware conformance and NVIDIA ConnectX Class NIC performance, ruggedization standards qualification (MIL-STD-810, MIL-STD-461, VITA 47), and software verification tools for safety-critical applications.

The anticipated contract vehicle is a Rapid Prototyping OTA with options for Low-Rate Initial Production (LRIP) and follow-on production, with a Period of Performance of three years for the RP OTA and five years for production. Estimated contract value and vehicle selection are to be determined following market research completion. Anticipated contract volumes range from 300 units (low) to 900 units (high). The anticipated RFP release and proposal due date are March 2027, with contract award anticipated March 2027. PdM VPS encourages responses from all interested parties including large businesses, small businesses, small disadvantaged businesses, service-disabled veteran-owned small businesses, women-owned small businesses, HUBZone firms, and 8(a) certified firms, though small business set-aside determination is pending completion of market research. Respondents should submit responses electronically to Jerad Kays (jerad.w.kays.civ@army.mil) with detailed technical responses addressing each question, optional pricing information for TSN solutions, and industry feedback on alternative technical approaches and emerging technologies. This RFI is for market research purposes only and does not constitute a binding solicitation or commitment to award a contract.

View the file

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

UNCLASSIFIED

Distribution Statement A: Approved for public release. OPSEC-2026-512

DEPARTMENT OF THE ARMY

Portfolio Acquisition Executive Maneuver Ground

Program Manager Advanced Targeting, Layered Survivability, and Stryker (ATLSS)

Product Manager Vehicle Protection Systems (PdM VPS)

REQUEST FOR INFORMATION (RFI)

SUBJECT: Vehicle Base-Kit (VBK) Modernization

RFI Number [TBD] Issue Date November 19th, 2026 Response Deadline December 4th,2026

NOTICE: This is a Request for Information (RFI) only. This RFI is issued solely for market research and information planning purposes in accordance with Federal Acquisition Regulation (FAR)

10.001. This document does not constitute a solicitation for proposals, a promise to issue a solicitation in the future, or a commitment by the Government to contract for any supplies or services. The Government will not pay for any information or administrative costs incurred in response to this RFI. Responses to this RFI will not be returned. The Government is under no obligation to acknowledge receipt of information received or provide feedback to respondents.

SECTION 1 — GENERAL INFORMATION

1.1 Purpose

The Portfolio Acquisition Executive Ground Maneuver, Program Manager Advanced Targeting, Layered Survivability, and Stryker (ATLSS), and Product Manager Vehicle Protection Systems (PdM VPS) are issuing this Request for Information (RFI) to conduct market research in support of the Vehicle Base-Kit (VBK) Modernization effort, specifically the development of a 3U VPX next generation Modular Active Controller (MAC) and its associated Safety Control and Interface Panel

(SCIP).

The purpose of this RFI is to:

• Identify industry capabilities relevant to the VBK Modernization effort

• Gather technical information on current and emerging technologies applicable to the VBK platform, including SOSA-aligned 3U VPX computing, TSN-based backplanes, FPGA-based I/O processing, and a GPGPU-based compute system

• Understand the state of the market with respect to SOSA-aligned computing, FPGA-based I/O processing, Time-Sensitive Networking (TSN) solutions, and semi-active VPX backplane designs

• Inform the Government's acquisition strategy, requirements development, and procurement planning

• Identify potential sources capable of supporting the VBK Modernization effort

PdM VPS encourages responses from all interested parties, including large businesses, small businesses, small disadvantaged businesses, service-disabled veteran-owned small businesses (SDVOSBs), women-owned small businesses (WOSBs), HUBZone small businesses, and 8(a) certified firms.

1.2 Issuing Organization

Portfolio Acquisition Executive Portfolio Acquisition Executive Ground Maneuver Program Manager Program Manager Advanced Targeting, Layered Survivability, and

Stryker (ATLSS) Product Manager Product Manager Vehicle Protection Systems (PdM VPS) Contracting Officer TBD Primary Point of Contact Jerad Kays, APM POC Email jerad.w.kays.civ@army.mil POC Organization PdM VPS

1.3 Disclaimer and Important Notices

a. This RFI is issued for market research purposes only pursuant to FAR 10.001. It is not a solicitation and shall not be construed as one. b. The Government will not award a contract based on responses to this RFI. c. The Government will not reimburse respondents for any costs associated with preparing or submitting responses to this RFI. d. Responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. e. Information received in response to this RFI may be used by the Government to shape future acquisition documents, including a subsequent Request for Proposal (RFP). f. The Government reserves the right to cancel this RFI at any time without obligation or liability to any respondent. g. Submission of a response to this RFI does not guarantee receipt of a future solicitation or participation in any subsequent procurement. h. All information provided by the Government in this RFI is preliminary and subject to change.

SECTION 2 — TECHNICAL AREAS OF INTEREST

PdM VPS requests industry input on the following technical areas. Respondents are encouraged to address as much as possible, to the extent relevant to their organizational capabilities and experience.

2.1 Computing and Processing — GPGPU Integration

PdM VPS is transitioning the VBK primary compute element to a GPGPU module on a SOSA-aligned 3U VPX HPC card.

a. Does your organization have experience integrating any GPGPU modules into a ruggedized, embedded 3U VPX computing environments?

b. What GPGPU 3U VPX HPC module or carrier solutions does your organization offer/use or have in development that are SOSA-aligned and compatible with a 3U VPX (1.0" pitch) backplane?

c. What are the known technical challenges of transitioning from older GPGPU modules to modern GPGPUs in a vehicle-mounted embedded environment (thermal, power, PCIe Gen4/Gen5, backplane Ethernet, GPUDirect RDMA, hypervisor bring-up)? How have you addressed them?

d. What is the current availability, TRL, and production readiness of GPGPU-based solutions for defense/ruggedized applications? Identify supply-chain risks and lead times.

e. What ruggedization standards (MIL-STD-810, MIL-STD-461, VITA 47) have your GPGPU-based solutions been tested/qualified against, over a -40 °C to +85 °C range?

2.2 SOSA Architecture Alignment

a. What SOSA-aligned/conformant products (processor modules, FPGA/IO cards, backplanes, power supplies, chassis) do you offer relevant to the COMPUTE

SYSTEM?

b. Do you have SOSA conformance testing/certification experience? Which SOSA Technical Standard version(s)?

c. Lessons learned and challenges designing/integrating SOSA-aligned systems, and mitigations.

d. Assessment of current SOSA ecosystem maturity and multi-vendor conformant product availability.

e. Experience with SOSA-aligned integration in ground-vehicle applications and relevant past performance.

2.3 FPGA-Based Discrete I/O, Video Processing, and Front-Plate Connectors Current 3U computed designs utilize FPGA’s for discrete-I/O and video routing/processing, and hosts all external front-plate connectors.

a. What FPGA-based I/O/video modules do you offer/use for a 3U VPX, SOSA-aligned form factor?

b. Which FPGA families (Microchip PolarFire / PolarFire SoC, AMD Zynq MPSoC, Intel/Altera) do you recommend for discrete-I/O and video (3G-SDI/HDMI/DP/RS- 170A) in ruggedized vehicle applications, and why?

c. Your approach to FPGA firmware development, version control, and configuration management for embedded defense systems.

d. Test/verification methodologies for FPGA-based I/O and video systems in military environments.

e. Connector count and selection: Provide recommendations to accommodate the full I/O set.

Example of IO sets: 26 Ethernet ports [12×10G, 12×1G, 2×1G], 4× 3G-SDI in, HD-SDI/DP/HDMI/RS-170A out, 6× RS-422, 4× RS-485, 2× CAN, 1× MIL-STD- 1553, 22 discrete signals, 14 Release Enables, GPS/5G RF, and power on a single 3U VPX front plate.

Comment on high-bandwidth connectors (e.g., Amphenol Centaur-class) vs.

MIL-DTL-38999 for the 10 GbE channels, and on cost/manufacturability trade-offs of reducing high-speed connector count.

2.4 Time-Sensitive Networking (TSN) — IEEE 802.1DP

PdM VPS intends to implement TSN aligned with IEEE 802.1DP. A key open decision is 1G vs. 10G TSN. Industry has reported that ConnectX-class NICs on Orin-class processor cards did not achieve production Layer-2 TSN conformance; GPGPU-based TSN solutions are of specific interest. What experiences do you have specifically with TSN and NVIDIA ConnectX Class NIC’s?

2.4.1 General TSN Capabilities

a. What TSN-capable switches, endpoint NICs, and 3U VPX networking modules do you offer, and are they Layer-2 hardware TSN or software-based?

b. Experience with IEEE 802.1DP (802.1AS timing sync, 802.1Qbv TAS, 802.1Qci PSFP) specifically; application domain and lessons learned.

c. Ruggedization qualifications (MIL-STD-810, MIL-STD-461, VITA).

d. Can you provide a true Layer-2 hardware TSN endpoint compatible with an GPGPU processor cards in a 3U VPX chassis? If not, what is your recommended path (dedicated FPGA VPX TSN endpoint, IO/backplane-hosted switch, or software TSN)?

2.4.2 1G TSN vs. 10G TSN Trade-Space

a. Performance differences between 1G and 10G TSN in a VPX embedded VPS environment.

b. SWaP-C differences (3U VPX, ruggedized).

c. ROM pricing for both 1G and 10G switch and endpoint solutions.

d. Availability and supply-chain risk for IEEE 802.1DP-conformant ruggedized 1G vs.

10G solutions.

e. TRL of 1G vs. 10G for defense ground-vehicle applications.

f. Your recommended bandwidth option and rationale, considering the ≥50 Gbps aggregate-to-processor requirement.

2.4.3 TSN Integration Considerations

a. Key challenges integrating TSN in a 3U VPX chassis alongside a GPGPU card, backplane, and data ingest IO.

b. TSN configuration/management tools.

c. Multi-vendor TSN interoperability considerations.

2.5 System Integration and Platform Maturation

a. Methodology for maturing prototype embedded systems to production-ready status in a defense environment.

b. Systems-engineering processes/tools for heterogeneous integration in a 3U VPX chassis.

c. Test & evaluation methodologies for ruggedized vehicle-mounted systems, including

ENV (shock, vibration, sand/dust, altitude/thermal), EMI (MIL-STD-461), and functional FQT.

d. Configuration management / baseline control for embedded hardware and firmware.

e. Foreseen risks/challenges in this effort and recommended mitigations (e.g., GPGPU

TSN Layer-2 availability, active-cooling ENV/EMI qualification, AUPC of high-speed connectors and fans).

f. Experience transitioning systems from prototype to program of record within Army/DoD acquisition.

2.6 Safety Architecture and SCIP Integration

a. Thoughts, comments, or concerns on switching from a Discrete/Hardware centered safety architecture, to a software-based safety architecture (except for E-STOP).

b. What is your experience with Software Verification Tools for safety critical applications? E.g. Rapita.

c. What is your experience with architecture separating safety critical code from standard code? What advice/suggestions do you recommend if this path is chosen going forward?

d. What is your experience with Industry Safety Standards such as DO178C-A or ISO 26262-ASIL D. What advice/suggestions do you recommend if this path is chosen going forward?

e. What is your experience with developing safety qualified verification tools. What advice/suggestions do you recommend if this path is chosen going forward?

f. Experience designing safety-significant controllers using lock-step, safety-pedigree microcontrollers (e.g., Infineon AURIX-class) with external watchdog and opto-isolated inhibit drivers.

g. Experience designing for safety using TSN in military applications?

h. Approach to a Power-Inhibit architecture (24 discretes, ~12 mA per channel, gang-able), loopback confirmation, and guarded 2-action E-STOP.

i. Experience developing safety software to AOP-52, including lock-step fault handling and fault-tree analysis.

j. Experience with MIL-DTL-38999 connector designs carrying mixed CAN + discrete safety interfaces.

2.7 Cybersecurity and Resilience

Respondents are encouraged to include relevant cybersecurity capabilities, certifications, or approaches, NSA-approved Network Attached Storage (NAS) for periods processing, and dual-layer (HW/SW) encryption.

SECTION 3 — ACQUISITION INFORMATION

3.1 Anticipated Contract Type

• Rapid Prototyping OTA o With option to LRIP o Potential Follow-on Production Contract

3.2 Estimated Contract Value

TBD - To be determined upon completion of requirements development and market research.

3.3 Anticipated Contract Volume

Unit Volume:

• Low: 300

• Medium: 550

• High: 900

3.4 Period of Performance

RP OTA: 3 years

Follow-on Production: 5 Years

3.5 Contract Vehicle

TBD — PdM VPS is evaluating appropriate contract vehicles, including open market, existing GWACs, and other applicable mechanisms.

3.6 Small Business Considerations

TBD — Small business set-aside determinations will be made in accordance with applicable regulations following completion of market research. Respondents are encouraged to identify their business size and socioeconomic status.

3.7 Anticipated Acquisition Timeline

RFI Release 19, November

RFI Response Deadline 04, December

Industry Day (If Applicable) TBD

Request for Proposal (RFP) Release TBD

Proposal Due Date March 2027

Anticipated Contract Award March 2027

SECTION 4 — RFI RESPONSE INSTRUCTIONS

4.1 Response Format Requirements (Suggestion)

File Format Adobe PDF (.pdf) or Microsoft Word (.docx)

Font Arial or Times New Roman, minimum 12-point

Maximum Page Limit 20 Pages

Classification UNCLASSIFIED only

Language English

4.2 Response Content

PART A — COMPANY INFORMATION (Required)

1. Company legal name and DBA name, if applicable

2. Company mailing address and primary place of performance

3. Business size designation

1. Small Business?

2. Non-Traditional?

4. Primary POC name, title, phone, and email

PART B — CAPABILITY STATEMENT (Optional, 1 page + Appendix limit)

1. Corporate Overview

2. Relevant Experience — embedded computing, GPGPU integration, SOSA-aligned systems, 3U VPX / semi-active backplane design, FPGA integration, TSN networking, safety-significant controllers, and/or defense system integration

3. Past Performance (contract number if available, customer/agency, PoP, value, description and relevance)

4. Certifications and Qualifications (including SOSA conformance)

5. Teaming arrangements, if applicable

PART C — TECHNICAL RESPONSE Provide detailed responses to the technical areas of interest in Section 3, organized by subsection, directly addressing each question. Include datasheets/specifications as attachments; identify limitations and lessons learned.

PART D — TSN PRICING INFORMATION (Optional but Strongly Encouraged)

1. ROM pricing for 1G TSN switch and endpoint solutions (ruggedized 3U VPX)

2. ROM pricing for 10G TSN switch and endpoint solutions (ruggedized 3U VPX)

3. Applicable NRE costs for TSN integration

4. Licensing/sustainment costs

5. Lead-time estimates

6. Optional ROM pricing for GPGPU-based 3U VPX HPC cards, FPGA-based backplane, FPGA-based IO with high-speed connectors, VPX power supply (500 W/380 ms hold-up), and an active cooling thermal kit.

Note: Pricing is for planning purposes only and does not constitute a binding offer.

PART E — INDUSTRY FEEDBACK (Optional but Encouraged)

1. Feedback on the Government's modernization approach

2. Risks/challenges not addressed (e.g., GPGPU TSN Layer-2 availability, active-cooling ENV/EMI qualification, connector/fan AUPC)

3. Alternative technical approaches or architectures

1. Include architectures for dual redundant design

4. Emerging technologies relevant to VBK modernization

5. Recommended NAICS codes

6. Recommended contract types/vehicles

7. Any other beneficial information

4.3 Submission Instructions

Submission Method Electronic (Email)

Submit Responses To Jerad Kays, PdM VPS

Email Address jerad.w.kays.civ@army.mil

Email Subject Line VBK Modernization RFI Response - [Company Name]

Response Deadline TBD — Responses received after the deadline may not be considered

Acknowledgment The Government will not confirm receipt of RFI responses

4.4 Proprietary and Business-Sensitive Information

The Government appreciates the time and effort taken to respond to this RFI. The Government acknowledges its obligations under 18 U.S.C. 1905 to protect information qualifying as PROPRIETARY. Pursuant to this statute, the Government is willing to accept any trade secret, or confidential restrictions placed on qualifying data forwarded in response to the RFI and to protect it from unauthorized disclosure subject to the following:

• Clearly and conspicuously mark qualifying data as trade secret or confidential with the restrictive legend (all caps) "PROPRIETARY" with any explanatory text, so that the Government is clearly notified of what data needs to be appropriately protected.

• In marking such data, please take care to mark only those portions of the data or materials that are truly trade secret or confidential (over breadth in marking inappropriate data as PROPRIETARY may diminish or eliminate the usefulness of your response). Use circling, underscoring, highlighting or any other appropriate means to indicate those portions of a single page which are to be protected.

• The Government is not obligated to protect unmarked data. Additionally, marked data that is already in the public domain or in the possession of the U.S. Government or third parties, or is afterward placed into the public domain by the owner or another party through no fault of the U.S. Government will not be protected once in the public domain. Data already in the possession of the Government will be protected in accordance with the Government’s rights in the data.

Business Confidential data transmitted electronically, whether by physical media or not, whether by the respondent or by the Government, shall contain any restrictive legend, with any explanatory text, on both the cover of the transmittal e-mail and at the beginning of the file itself. Where appropriate for portions only of an electronic file, use the restrictive legends “PROPRIETARY DATA BEGINS:” and “PROPRIETARY DATA ENDS.”

SECTION 5 — INDUSTRY DAY (TBD)

PdM VPS is considering an Industry Day to provide additional context on the VBK Modernization effort, present the current state of the platform, and engage industry. If scheduled, it may include Government program briefings, one-on-one sessions, and Q&A.

SECTION 6 — ADDITIONAL INFORMATION

6.1 Classification

This RFI and all associated activities are UNCLASSIFIED. All responses shall be unclassified.

6.2 Data Rights

The Government shall have unlimited rights to use, reproduce, modify, and distribute all information submitted, except for information clearly marked proprietary. In any reproductions of technical data or any portions thereof subject to asserted restrictions, the Government shall also reproduce the asserted restriction legend and any explanatory text. Data submitted in response to this RFI will not be returned.

Respondents shall provide a release statement indicating that the proprietary information may be distributed to Army personnel involved with reviewing this RWP, including government support contractors.

6.3 Section 508 Compliance

Electronic documents should, to the extent practicable, comply with Section 508 (29 U.S.C. § 794d).

6.4 Foreign Ownership, Control, or Influence (FOCI)

(TBD) - Respondents with known FOCI concerns are encouraged to identify them.

6.5 Export Control

(TBD) - ITAR/EAR considerations will be addressed in a subsequent solicitation. Respondents are encouraged to identify export-control considerations relevant to the technologies described, including CDS/encryption components.

END OF REQUEST FOR INFORMATION

1.1 Purpose
1.2 Issuing Organization
1.3 Disclaimer and Important Notices
2
2.1 Computing and Processing — GPGPU Integration
2.2 SOSA Architecture Alignment
2.3 FPGA-Based Discrete I/O, Video Processing, and Front-Plate Connectors
2.4 Time-Sensitive Networking (TSN) — IEEE 802.1DP
2.4.1 General TSN Capabilities
2.4.2 1G TSN vs. 10G TSN Trade-Space
2.4.3 TSN Integration Considerations
2.5 System Integration and Platform Maturation
2.6 Safety Architecture and SCIP Integration
2.7 Cybersecurity and Resilience
3
3.1 Anticipated Contract Type
3.2 Estimated Contract Value
3.3 Anticipated Contract Volume
3.4 Period of Performance
3.5 Contract Vehicle
3.6 Small Business Considerations
3.7 Anticipated Acquisition Timeline
4
4.1 Response Format Requirements (Suggestion)
4.2 Response Content
4.3 Submission Instructions
4.4 Proprietary and Business-Sensitive Information
6
6.1 Classification
6.2 Data Rights
6.3 Section 508 Compliance
6.4 Foreign Ownership, Control, or Influence (FOCI)
6.5 Export Control

File details come from the government source that posted it. Updated .