NVDTS RFI Questionnaire 2026Nov09.docx

REQUEST FOR INFORMATION (RFI)

Commercial-Off-The-Shelf (COTS) Night Vision Device Test Set (NVDTS)

Section 1: Administrative Notice and Survey Instructions

1.1 Purpose and Scope

The United States Army, Product Director Test, Maintenance, and Diagnostic Equipment (PD TMDE), is conducting market research to determine the commercial availability, technical readiness, and budgetary benchmarks for a Night Vision Device Test Set (NVDTS) conforming to Purchase Description TEMOD-26-01 (Version 1.4).

The intended NVDTS will serve as a multi-spectral, automated electro-optical diagnostic station deployed at field and depot maintenance activities. It evaluates image intensifier () tubes, thermal weapon sights, fused optical assemblies (e.g., ENVG-B), and heads-up digital architectures (e.g., IVAS).

1.2 Document Maturity, Trade Space, and Evolution Notice

IMPORTANT NOTICE REGARDING PURCHASE DESCRIPTION STATUS:

Responding vendors should note that the referenced Purchase Description (TEMOD-26-01, Version 1.4) represents an initial working draft developed specifically to assess commercial-off-the-shelf (COTS) or Non-Developmental Item (NDI) availability, evaluate the technical feasibility and reasonability of the parameters, and define the trade space between threshold requirements and objective enhancements.

The Government explicitly intends to refine, update, and mature this specification prior to issuing any formal solicitation. Updates will incorporate industry responses to this RFI, ongoing dialogue with requirements developers, and technical exchanges with Army night vision device (NVD) subject matter experts (SMEs). Vendors are strongly encouraged to identify requirements that appear overly restrictive, cost-prohibitive, technically mismatched with commercial best practices, or in need of clarification, and to propose viable commercial alternatives within the trade space in Section 9 of this survey.

1.3 Non-Binding Budgetary Estimate Disclaimer

NOTICE TO RESPONDING VENDORS:

This document is issued solely for market research, program planning, and technical assessment purposes in accordance with FAR Part 10. It does not constitute a Request for Proposal (RFP), Invitation for Bid (IFB), or an obligation on the part of the Government to acquire any products or services.

All budgetary estimates, pricing data, Rough Order of Magnitude (ROM) costs, and production lead times provided by the vendor are understood to be strictly non-binding. Responding vendors will not be held to the provided cost figures in any future competitive solicitation. The Government will not reimburse any costs associated with preparing or submitting responses to this survey.

1.4 Vendor Response Classifications

For each technical parameter and functional requirement throughout this questionnaire, vendors are requested to categorize their compliance using the following standardized status definitions:

· COTS - Fully Compliant (COTS): The requirement is fully satisfied by a mature, production-line Commercial-Off-The-Shelf or Non-Developmental Item (NDI) available today.

· COTS - Objective Met (COTS-OBJ): The system currently meets or exceeds the enhanced "Objective" requirement as specified in the Purchase Description.

· Near-Term Roadmap (Roadmap): The capability is fully architected and actively in development, with standard commercial availability expected within three (3) to six (6) months of response date.

· Requires Development (DEV): The requirement is technically feasible but requires non-recurring engineering (NRE), hardware/software modifications, or custom development exceeding six (6) months.

· Not Supported (N/S): The current commercial baseline does not meet this requirement, and there are no immediate plans to develop or integrate this capability.

Section 2: Vendor, Corporate, Regulatory, & Past Performance Overview

2.1 Corporate Information & Regulatory Compliance

Company Name

Commercial and Government Entity (CAGE) Code

Unique Entity Identifier (UEI / DUNS)

Corporate Address

Primary Technical Point of Contact (Name, Title, Email, Phone)

Primary Contracts/Business POC (Name, Title, Email, Phone)

[ ] Small Business [ ] Other (Specify)

Manufacturing Facility Location(s)

[ ] Exceptions Noted Below

Export Control Classification:

• ITAR / USML Category (e.g., Cat XII)

• EAR / ECCN Number (e.g., 6A002, 6A003, EAR99)

2.2 Past Performance & Military Fielding Track Record

Please summarize your organization's track record in supplying electro-optical, night vision, or thermal test benches to the U.S. Armed Forces, allied defense ministries (NATO), or major defense prime contractors:

Section 3: Production Scalability, Lead Times, & Bid Sample Readiness

3.1 Manufacturing Scalability & Delivery Lead Times

3.1.1 Current Manufacturing Maturity:

· Is the proposed test set currently in active series production? If yes, what is your current annual/monthly production rate?

· What is the Technology Readiness Level (TRL) and Manufacturing Readiness Level (MRL) of your core system?

3.1.2 Order Fulfillment Lead Times:

Please provide estimated delivery lead times (weeks or months from receipt of order) based on the following potential procurement tranches:

· Initial Bid / First Article Test (FAT) Units (1–5 systems): ____________ weeks

· Low-Rate Initial Production (10–25 systems): ____________ weeks

· Full-Rate Production (50–100+ systems): ____________ weeks

3.1.3 Supply Chain Fragility & Long-Lead Components:

Identify any single-source, high-lead-time sub-assemblies (e.g., custom large-aperture off-axis parabolic mirrors, scientific sCMOS focal plane arrays, blackbody thermoelectric controllers).

3.2 Bid Sample & Technical Demonstration Readiness

In accordance with Section 6.1.1 of the Purchase Description, bid samples and technical demonstrations will be required for technical evaluation prior to contract award.

· Does your company currently possess a functional, mature test set that can be made available as a Bid Sample or for a hands-on Government demonstration at Redstone Arsenal, AL?

[ ] Yes, available immediately [ ] Available within 30–60 days ARO [ ] Requires custom assembly (>60 days) [ ] No

· What specific accommodations, facilities, or power connections would be required to execute an on-site demonstration of your system's baseline and thermal test capabilities?

Section 4: Hardware Subsystems, SWaP, & Environmental Compliance

4.1 Optical Stimulus Bench & Mechanical Hardware Compliance

Please indicate compliance with the baseline hardware requirements established in Section 3.0 and Table 3.0 of the Purchase Description:

4.2 Environmental Testing & Ruggedization Matrix

Please indicate the current verification maturity of your test set against the specific environmental profiles mandated in Section 6.9 of the Purchase Description:

Section 5: Measurement Capabilities & Test Program Sets (TPS)

5.1 Electro-Optical & Radiometric Diagnostic Coverage

Please assess your test station's native ability to perform automated, objective algorithmic evaluations without operator bias:

5.2 Unit Under Test (UUT) TPS Availability Matrix

Indicate current software, mechanical adapter, and harness readiness across specific inventory configurations:

TM 11-5855-306-23&P

TM 9-5855-1916-13&P

TM 11-5855-343-23&P

IWS Architecture

Section 6: Test Set Calibration Requirements & Support Equipment Paragraph 5.2.3 and 6.13 mandate that the NVDTS be calibratable via the Army Automated Calibration Equipment (ACE) suite or AN/GSM-440 within a maximum calibration budget of 5 to 9 hours.

6.1 Recommended Calibration Standards Architecture

Provide a detailed list of all external test, measurement, and diagnostic equipment (TMDE) and optical transfer standards that your company deems mandatory or recommended to perform full periodic calibration of the test set:

Optical Collimator & Wavefront Alignment

Differential Blackbody Engine (Temperature & Emissivity)

Low-Light Photometric Light Source (Luminance & Color Temp)

Scientific Camera & Eyepiece Relay Distortion

Programmable DC Power Rails & Current DAQ

6.2 Calibration Execution & Interfacing

· Can your test set execute an automated self-calibration routine interfacing with standard Army laboratory equipment (e.g., AN/GSM-440 / AN/USM-440) via software hooks?

· Does calibration require proprietary variable component replacement, factory return-to-depot, or can it be executed entirely via software calibration coefficients saved to onboard non-volatile memory?

· What is your demonstrated Mean Time To Calibrate (MTTC) for:

Fully Automated Routine: ____________ hours Full Manual Procedure: ____________ hours

Section 7: Software, Cybersecurity, Data Rights, & Obsolescence (DMSMS)

7.1 Operating System Hardening & Cybersecurity Baseline

· What operating system hosts your test executive (e.g., Windows 11 Enterprise LTSC, Red Hat Enterprise Linux)?

· Has this platform been hardened against DISA Security Technical Implementation Guides (STIGs)? List any open STIG finding categories (CAT I, CAT II).

· Does your system currently hold a formal Authority to Operate (ATO) on a DoD network (e.g., eMASS package number, sponsoring service, Impact Level IL4/IL5)?

· Can you furnish a comprehensive Software Bill of Materials (SBOM) compliant with NTIA/DoD mandates identifying all commercial, open-source, and proprietary libraries?

7.2 Database Logging & Mission-Priority Fallback

· Does your software architecture automatically log the mandatory metadata schema (Table 5.4.1), including cryptographic SHA-256 session and media signing?

· Describe how your software manages storage degradation when local partition capacity reaches , , and capacity (e.g., selective pruning of passing raw media while strictly preserving numeric test logs).

7.3 Diminishing Manufacturing Sources & Material Shortages (DMSMS) / Obsolescence

· What is the guaranteed commercial production and support lifecycle of your core hardware platform (e.g., minimum 5, 7, or 10 years)?

· How does your company monitor and manage component obsolescence (e.g., commercial image sensors, motorized stage controllers, embedded single-board computers)?

· What is your standard policy regarding End-of-Life (EOL) notifications to Government customers, and how are redesigns managed when commercial components become unavailable?

7.4 Data Rights, Technical Data Packages (TDP), & Intellectual Property Strategy In accordance with DFARS 252.227-7013, DFARS 252.227-7014, and Purchase Description Paragraph 6.17, the Government requires clarity regarding intellectual property assertions, software delivery formats, and rights structures across both COTS elements and newly developed modules.

7.4.1 Government-Funded Development Rights (DFARS 252.227-7014(b)(1)):

If the Government funds 100% of the Non-Recurring Engineering (NRE) or development costs for a new Test Program Set (TPS), Interface Test Adapter (ITA) hardware, diagnostic algorithm, or custom harness:

· Do you agree that the Government will receive Unlimited Rights (unrestricted rights to use, modify, reproduce, perform, display, release, or disclose the software, test routines, and hardware documentation in whole or in part, in any manner and for any purpose whatsoever, and to have or authorize others to do so)?

[ ] Fully Agree without Reservation [ ] Agree to Government Purpose Rights (GPR) Only [ ] Exception Noted Below

If Exception Noted, provide detailed commercial/legal rationale:

7.4.2 Mixed Funding / Baseline Adaptation Rights:

If a proposed TPS or module leverages existing proprietary commercial libraries but requires Government funds to integrate or complete:

· Will your company deliver the developed integration code and resulting TPS configurations with at least Government Purpose Rights (GPR), enabling the Army to maintain, rehost, or compete support of the TPS at organic depots (e.g., Tobyhanna Army Depot) or via third-party service contractors?

[ ] Yes [ ] No [ ] Conditional (Explain)

7.4.3 Deliverables & Uncompiled Source Code:

To avoid operational obsolescence and long-term vendor lock-in, will your company deliver the following items upon completion of contract development:

· Fully documented, uncompiled TPS source files, test scripts, and diagnostic sequencing routines?

[ ] Yes [ ] No

· Open Application Programming Interface (API) specifications and software execution hooks?

[ ] Yes [ ] No

· The complete Test Program Set Development Environment (TPSDE) tools and compiler licenses required for Government engineers to modify or author new TPSs organically?

[ ] Yes [ ] No

· Level 3 Technical Data Packages (TDP) (compliant with MIL-STD-31000) for all mechanical mounting sleds, optical alignment hoods, and passive electrical cabling?

[ ] Yes [ ] No

7.4.4 Data Rights Assertions Matrix:

Please identify any commercial or proprietary software elements that will remain subject to Commercial/Restricted Rights and require recurring license fees:

Section 8: Development Roadmap & Non-Recurring Engineering (NRE) For all hardware, measurement, or software items classified as "Near-Term Roadmap (3–6 Months)" or "Requires Development (DEV)", vendors are requested to complete the breakdown below:

Section 9: Technical Trade Space, Cost Drivers, & Industry Feedback The Government recognizes that certain technical combinations in working draft TEMOD-26-01 (v1.4) may drive substantial Non-Recurring Engineering (NRE), inflate per-unit recurring costs, or increase system weight. Responding vendors are requested to highlight requirements that appear over-constrained and propose commercial alternatives.

Section 10: Rough Order of Magnitude (ROM) Budgetary Cost Structure

REMINDER: All financial figures provided in this section are strictly non-binding, rough-order-of-magnitude estimates utilized exclusively for Government life-cycle budget forecasting.

10.1 Hardware Procurement ROM (Per-Unit Basis)

10.2 Software Licensing, Development, & Data Rights ROM

Average TPS cost: $

10.3 Training & Support Services

Section 11: Submission Instructions & Points of Contact Please submit responses in electronic format (.pdf, .docx, or .xlsx) by [Insert Date: 30–45 Days from Issuance] at 17:00 CST.

Submissions To: Product Director TMDE Test Equipment Modernization Program Point of Contact: [Contracting Officer / Contract Specialist]

IMPORTANT PROPRIETARY MARKINGS NOTICE:

Responding vendors are responsible for clearly identifying and marking all proprietary, business-confidential, and competition-sensitive information on each applicable page or data item. The Government will protect properly marked proprietary submissions from unauthorized disclosure in accordance with FAR 3.104 and 18 U.S.C. § 1905.