Amendment 0001.pdf

Amendment 0001

The purpose of this amendment is to:

1. Extend the response date of the solicitation from 05/05/2026 at 12:00 PM EST. to 05/08/2026 at 12:00

PM EST.

2. Publicly provide responses to inquiries posed by interested parties.

Question 1: SOW Task 3.1 — LiDAR Sensor Hardware

Task 3.1 calls for the contractor to integrate additional sensors, such as LiDAR, into the NIST V2X testbed.

Will the LiDAR sensor hardware be Government-Furnished Property, or will the contractor procure the unit? If contractor-procured, please confirm whether CLIN 0002 may include this hardware as an Other Direct Cost, or whether a separate funding action is anticipated to cover hardware acquisition.

Response 1: The hardware will be Government-Furnished Property

Question 2: SOW Task 4 — OmniAir Plugfest Scheduling

The SOW identifies one (1) anticipated domestic trip to an OmniAir Consortium plugfest. Should the contractor budget for a specific known event date and location, or should travel be priced to a generic GSA per diem assumption pending event scheduling?

Response 2: The location of the next plugfest (in October/November) isn’t known – but it will be within the continental U.S. and could be estimated as 5-day domestic travel.

Question 3: Place of Performance — Off-laboratory Work

The SOW identifies NIST-Gaithersburg as the place of performance. May the Key Personnel resource perform off-laboratory deliverable work (literature survey, framework drafting, technical-report writing) remotely, subject to NIST research-staff direction, or is 100% on-site presence required throughout the period of performance?

Response 3: Hybrid work is possible, but the lab work requires on-site presence and will constitute a significant portion of the work.

Question 4: Sample V2X Testbed Data Sets

To support Task 1.3 validation activities, will NIST share — prior to award or at award — sample V2X testbed data sets sufficient for the contractor to validate the Task 1 software tool against? If so, in what formats?

Response 4: See https://doi.org/10.18434/mds2-3541

Question 5: Data Rights Regime for Deliverable Source Code https://doi.org/10.18434/mds2-3541

Per FAR 52.227-14 (Rights in Data — General) and successor clauses under the FAR Overhaul, please clarify the data-rights regime that will apply to deliverable source code (Deliverables #1 and #4). Will NIST seek Unlimited Rights, Government-Purpose Rights, or Limited Rights, and how will pre-existing contractor IP (e.g., open-source libraries the contractor maintains, or contractor-proprietary platform components) be treated?

Response 5: NIST will seek unlimited rights for new software developed as part of the contract. While the new software is not expected to require use of proprietary libraries, use of pre-existing contractor IP would need to be consistent with the terms defined in their licenses and would remain the intellectual property of the contractor.

Question 6: HSPD-12 Badging Timeline

For HSPD-12 badging at the Low-Risk position-sensitivity level, what processing time is NIST currently experiencing, so the contractor can plan the schedule from award to first on-site work date accurately?

Response 6: If the qualified personnel is a US Citizen, 1 week. Otherwise, 4 weeks.

Question 7: Volume III Terms and Conditions — Tailoring

The RFQ requires the contractor to either accept all terms or list exceptions. Are there clauses where NIST would consider tailoring (for example, regarding data rights to preserve pre-existing contractor platform IP, or limitation-of-liability language), or is the solicitation strictly take-it-as-written?

Response 6: No.