Questions and Answers_2.pdf
PDF 142 KB Posted
- Attached to
- Driver's License Data
- Solicitation number
- DEC-24-0041
- Issued by
-
Department of Commerce US Census Bureau
About this file
This document contains questions and answers regarding a potential federal contract opportunity for driver's license and state-issued identification card data. The U.S. Census Bureau is seeking a contractor to provide data fields such as driver's license numbers, names, addresses, dates of birth, and other demographics for 50 states, Washington D.C., Puerto Rico, and U.S. island areas. The contractor would transfer the data to the Census Bureau via managed file transfer on a potential one-year base period and one option year. Key questions addressed include the expected amount of data, whether card images would be included, how the data would be collected and standardized, and responsibilities for obtaining necessary permissions from the states.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| Questions and Answers_3.pdf | ||
| Questions and Answers.pdf | ||
| DEC-24-0041 SSN 1.22.24.pdf | ||
| Attachment 1_requirements.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
Action ID: DEC-24-0041 Driver’s License and State Issued Data
QUESTIONS AND ANSWERS
1. What is the potential amount of data?
ANSWER: The exact amount of data will depend on the vendor. It will include driver’s license and state-issued data for 50 states, District of Columbia, Puerto Rico, and Island Areas.
2. Is the agency open to placing the prospective requirement into the 8(a) program?
ANSWER: Yes
3. Is this an on-premises or SaaS deployment?
ANSWER: The data will be transferred to the U.S. Census Bureau via a Managed File Transfer (MFT).
4. Is there a need to redact any information prior to release?
ANSWER: If the data is used as part of research or production efforts where data or data products are released to the public, it will go through the Census Bureau’s standard disclosure avoidance process to ensure Personal Identifiable Information (PII) is not released.
5. What is the potential duration of the project?
ANSWER: Base year (one year) and the option for one option year
6. What is the potential number of users on a regular basis?
ANSWER: The number of users will depend on the projects’ needs and the data content.
7. Does the agency allow acquisition of Data from parties other than states or government divisions?
ANSWER: Yes
8. In the list of items, there is no mention of the Card image or photo of the card holder.
Does the agency plan to include Card image and/or photo?
ANSWER: No
9. How many concurrent users are expected to access the data?
ANSWER: The number of concurrent users will depend on the project needs and the data content.
10. How are we getting the data?
a. Is the data to be provided by state/local sources or is there a need to collect and/or integrate from them?
b. Will data ever be collected from the public? Or will it always come from state/local agencies?
c. Is the data standardized or will it require standardization?
ANSWER: The data collection process will depend on the vendor and how the vendor chooses to collect the data. Based on research, it appears vendors collect the data from other government agencies and they standardize it prior to providing to customers.
11. Do you intend to store it in image format?
12. Is there a need for visualization of the stored data?
13. Is there a need to export and/or restructure data?
ANSWER: Yes, the data may be restructured by Census analysts and/or integrated to existing data.
14. Will entries be updated with license renewals, name/address changes, etc. or will new entries be created?
ANSWER: Yes. If new entries are created, the Census Bureau needs to be able to link them to the original entries. If not, the existing entry will need to be updated.
15. Will expired entries be removed from the database?
ANSWER: No, but the vendor will need to label these entries as such.
16. Does the database need to integrate with other repositories (e.g. organ donor databases, law enforcement, voter registration) ANSWER: No
17. Considering, the data requested in the requirement is PII and most of it is not public information, and not owned by private entities but by each state bodies, is it correct to assume that the client (Census Bureau) currently already has access to this data from all the states and the requirement is to massage and present the data in required data fields?
ANSWER: No
18. If the underline data does not presently exist, is the customer willing to assist in filing required permissions/forms to get access to the restricted data from all the states. While some states offer APIs / Open Data web services that we can integrate and fetch the required data, it would still require permissions to fetch this restricted data. For example, Maryland and DC offer open data APIs while data from PA is not available.
ANSWER: No, the Census Bureau expects the vendor to have permissions to acquire the data.
19. Would the customer be interested in a white paper on which states offers and restrict what data fields?
ANSWER: A white paper including this information is not part of this acquisition.
File details come from the government source that posted it. Updated .