PPA_RFI__Vehicle_Dimension_and_VIN_Decoding_API_Integration_QandA.pdf
PDF 154 KB Posted
- Solicitation number
- Not on record
About this file
This is a Questions and Answers document supporting a Request for Information (RFI) issued by the Department of War Personal Property Activity (PPA) regarding vehicle-dimensions and VIN-decoding API integration. The RFI deadline for submitting clarifying questions was 3 September 2026 at 4:00 p.m. Central Time. The PPA is conducting market research to identify potential solutions that enable customers to prepopulate vehicle-dimension and weight data using a 17-character VIN or vehicle-selection inputs such as year, make, model, and trim, thereby streamlining the process and reducing manual data entry.
Key requirements and clarifications include: comprehensive data coverage for vehicle model years 1981 to present with data accuracy evaluation criteria to be finalized based on RFI responses; client-side caching of vehicle data with cache management approaches and retention parameters still under development; incremental data updates rather than full data transmission; flexible acquisition approaches for data subscription and system integration that may be separate or combined; API handling of unresolved or ambiguous trim information through fallback responses, confidence indicators, or user-selection workflows; and non-sensitive reference data with firewall configuration for API traffic between systems. The PPA has not yet determined separate versus single acquisition of data subscription and system integration and welcomes industry recommendations on viable acquisition, licensing, implementation, and sustainment approaches.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| PPA__Vehicle_Dimension_and_VIN_Decoding_API_Integration_RFI.pdf |
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
PERSONAL PROPERTY ACTIVITY
1 SOLDIER WAY
SCOTT AIR FORCE BASE, ILLINOIS 62225-5357
SUBJECT: Department of War (DoW) Personal Property Activity (PPA) Vehicle Dimensions and VIN-Decoding API Integration Questions and Answers
I. INTRODUCTION AND OVERVIEW
The PPA provides this questions and answers document in support of the request for information (RFI) regarding potential vehicle-dimensions and VIN-decoding API integration.
The RFI invited industry and stakeholders to submit clarifying questions to the PPA by 3 September 2026, at 4:00 p.m. Central Time. This document provides the questions received and the PPA’s responses.
The responses reflect the PPA’s current understanding as of the posting date. The responses are subject to change as requirements evolve and as the PPA receives and considers additional feedback from industry and stakeholders. This questions and answers document is provided for clarification and does not amend or supersede the RFI.
II. QUESTIONS AND ANSWERS
1. Where are the performance thresholds measured?
The PPA is assessing how to evaluate data accuracy across vehicle model years. The RFI requires comprehensive coverage for applicable vehicles from model year 1981 to the present.
The PPA will consider information provided in RFI responses as it finalizes additional data-accuracy criteria.
2. May cached dimension records survive the annual data refresh?
The PPA anticipates client-side caching of vehicle data, consistent with the RFI. The duration and retention parameters have not yet been established. The current plan is to provide updates based on incremental changes rather than full data transmission. The PPA welcomes industry feedback on cache-management approaches, including the handling of updated, corrected, or removed records.
3. Is the data subscription a separate acquisition from the integration?
The PPA has not determined whether the data subscription and system integration would be acquired separately or as part of a single solution. As this is a market-research effort, the PPA welcomes industry recommendations on viable acquisition, licensing, implementation, and sustainment approaches.
4. What is captured at vehicle turn-in today?
The vehicle dimensions are not currently captured at vehicle turn-in. Instead, dimensions are entered earlier in the process using vehicle information.
5. What should the API return when trim cannot be resolved from the VIN alone?
The PPA has not selected an approach for instances in which a VIN does not resolve to a specific vehicle trim. The PPA welcomes industry recommendations on practical approaches for handling unresolved or ambiguous trim information, including fallback responses, confidence indicators, and user-selection or confirmation workflows.
6. What are the hosting and authorization expectations for the data source?
No unique hosting or authorization requirements are currently anticipated because the data is expected to be non-sensitive reference data. The receiving system is protected by a firewall boundary that may require configuration to permit API traffic between systems.
The PPA will assess any additional cybersecurity, connectivity, compliance, and technical requirements based on the final data flows and technical implementation.
7. What is the intent of this RFI?
The intent of this RFI is to identify potential solutions that enable customers to prepopulate vehicle-dimension and weight data using a 17-character VIN or vehicle-selection inputs, such as year, make, model, and trim. Currently, customers must manually enter this information or locate it through external online sources. The desired solution would streamline the process, reduce manual data entry, and improve the customer experience.
File details come from the government source that posted it. Updated .