RFI ECON-24-0027 Question and Answer Document for Vehicle Inventory Survey Data File.pdf
PDF 141 KB Posted
- Solicitation number
- ECON-24-0027
- Issued by
-
Department of Commerce US Census Bureau
About this file
This is a Question and Answer document for RFI ECON-24-0027 regarding the Census Bureau's Vehicle Inventory Survey Data File requirements. The document clarifies that contractors will be responsible for verifying accuracy, cleaning, and preprocessing vehicle data from Motor Vehicle Agencies (MVAs) before delivering a complete, static snapshot dataset covering the entire country.
Key technical requirements include delivering data as a delimited or non-delimited fixed length ASCII text file via Managed File Transfer (MFT), providing comprehensive file documentation (including column layouts, data dictionary, and vintage information), and offering technical support with 48-hour response times. The data will primarily support the Vehicle Inventory and Use Survey (VIUS), though the Census Bureau reserves rights for other research uses. The contractor must develop their own data sources if MVA data is incomplete. The file layout must include specific elements like column names, descriptions, maximum lengths, starting positions, formats, and a data dictionary. Post-delivery support will be required for file structure, content completeness, and data consistency issues.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| RFI ECON-24-0027 Vehicle Inventory Data File.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
Q&A for RFI ECON-24-0027 Vehicle Inventory Survey Data File
1. What specific methodologies will be employed to verify the accuracy and completeness of the dataset from MVAs?
a. Verifying the accuracy and completeness of the datasets from the MVAs would be the responsibility of the vendor. The Census Bureau would expect delivery of a complete and accurate dataset, meeting the scope and parameters provided.
2. How does the Census Bureau plan to address potential privacy concerns related to collecting and storing owner contact information?
a. The Census Bureau has the authority to collect and store information. See https://www.census.gov/about/authority.html
3. What role, if any, will the contractor have in cleaning or preprocessing the data before delivery?
a. Cleaning and preprocessing the data is the responsibility of the contractor. The Census Bureau will want the contractor to define how the contractor will clean and preprocess the data given to the Census Bureau.
b. The contractor will give the Census Bureau a complete and accurate delivery for the entire country.
4. Is the dataset expected to be a static snapshot, or should it include updates over time?
a. The Census Bureau wants a static snapshot for the entire country.
5. Are there any specific guidelines or standards that the final dataset must comply with (e.g., data formatting, security measures)?
a. Data Transfers/ Submission instructions:
i. ERD Data Quality Branch will assist in account creation and request a test file.
ii. Data Extract: the data should be provided as a delimited text file or a non-delimited fixed length text file (ASCII). The Census ingest team will need to know the delimiter.
iii. Delivery Method: The data will be transferred via Managed File Transfer
(MFT).
iv. The Contractor shall provide technical support regarding file structure and delivery, file contents and completeness, and data consistency over time.
The contractor shall work to resolve technical issues Economic Reimbursable Surveys Division (ERD) within 48 business hours of being notified.
v. The Contractor will provide adequate documentation and support of transferred files for the Census Bureau to be able to interpret the data:
vi. File layout:
1. Contains column (variable) name
2. Description of the column
3. Maximum length of the column
4. Starting position (if it's a fixed length file)
5. Formats of the data (example: date formats, implied decimals, etc.)
6. Data Dictionary: a Codebook and/or any other information required so an analyst can understand the data
7. File structure (delimited or fixed length)
8. Total record count
9. Data vintage (what year(s) does the file cover)
6. How does the Census Bureau define "administrative record datasets," and what alternative sources might be used if MVA data is incomplete?
a. Please see,
i. https://www.census.gov/content/dam/Census/about/about-the-bureau/adrm/data-linkage/Data%20Acquisitions%20Frequently%20Asked%20Questions.pdf
ii. https://www.census.gov/newsroom/blogs/random-samplings/2021/04/administrative_recor.html.
iii. https://www.census.gov/topics/research/guidance/restricted-use-microdata/administrative-data.html.
b. The contractor must define and develop their own sources to deliver the data to the Census Bureau.
7. Can the Census Bureau clarify any additional use cases for the data beyond VIUS (e.g., for transportation planning or policy analysis)?
a. At this time, the vehicle data the Census Bureau wants is only for VIUS use, but the Census Bureau will retain the right to use the data for research and other programs.
8. Will there be opportunities for contractors to provide ongoing data support post-delivery?
a. Generally, the Contractor shall provide technical support regarding file structure and delivery, file contents and completeness, and data consistency over time. The contractor shall work to resolve technical issues within 48 business hours of being notified.
b. Also please see the answer to number five above.
https://www.census.gov/newsroom/blogs/random-samplings/2021/04/administrative_recor.html https://www.census.gov/newsroom/blogs/random-samplings/2021/04/administrative_recor.html
File details come from the government source that posted it. Updated .