SOLICITATION NOTICE
D -- RESPONDENT VALIDATION
- Notice Date
- 11/24/2014
- Notice Type
- Presolicitation
- NAICS
- 541512
— Computer Systems Design Services
- Contracting Office
- Department of Commerce, U. S. Census Bureau, Acquisition Division, 1201 East 10th Street, Jeffersonville, Indiana, 47130
- ZIP Code
- 47130
- Solicitation Number
- RFI_RM15-007
- Archive Date
- 1/17/2015
- Point of Contact
- Nicholas Apperson,
- E-Mail Address
-
nicholas.apperson@census.gov
(nicholas.apperson@census.gov)
- Small Business Set-Aside
- N/A
- Description
- REQUEST FOR INFORMATION ON RESPONDENT VALIDATION 1.0 Description 1.1 The US Census Bureau, in support of research and testing for the 2020 Census, is seeking information on methodologies to validate respondents are who they say they are when responding to online questionnaires. 1.2 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. This RFI is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the US Census Bureau is not, at this time, seeking proposals and will not accept unsolicited proposals. Responders are advised that the U.S. Government will not pay for any information or administrative costs incurred in response to this RFI; all costs associated with responding to this RFI will be solely at the respondent's expense. Not responding to this RFI does not preclude participation in any future RFP, if any is issued. 2.0 Background 2.1 During the 2010 Census enumeration, the majority of people were enumerated via paper questionnaires delivered to their living quarters: most by mail, but a smaller proportion was hand-delivered by United States Census Bureau field staff. These questionnaires contained a census identification number (Census ID) that linked the questionnaire to the address of the living quarters. However, there were other opportunities for individuals to respond to the 2010 Census. For example, there were coverage improvement programs like the "Be Counted" operation, which permitted respondents to pick up a blank census form at thousands of locations across the country, complete it, and then mail it in. Or, a respondent could call the toll-free Telephone Questionnaire Assistance line and complete an interview with Census staff instead of returning a census form. There were other programs that offered similar opportunities, but a common element shared by them all is that the response lacked a pre-assigned Census ID; hence, the term "Non-ID." "Non-ID Processing" is the comparison of the addresses associated with these cases to determine whether they match existing Census Bureau address records in the MAF/TIGER database (MTdb) and/or assign the appropriate census geographic codes. 2.1.1 The business goal of this effort is to determine which respondent validation methodology could be incorporated into the Non-ID Processing workflow such that there is minimal impact on respondent burden. In this sense, the Census Bureau is interested in knowing if the person responding without an identification code is the person at the address provided to the Census Bureau. The Census Bureau is not seeking information on respondent authentication at this time. The 2020 Census will offer more response options than it did in 2010, including using the internet as the primary response option, with the majority of the population responding through this mode (Source: Strategic Plan for the 2020 Census). The Census Bureau continues to test mailing materials with Census identification codes to respondents who then use the Census identification codes to log onto the internet self response questionnaire. The Census Bureau has also tested mailing materials without Census identification codes to respondents. Those respondents accessed the Internet and provided their information. During the 2020 Census research and testing phase, the Non-ID Processing team is working to reengineer the program level business processes. Systems are being built which enable ingest, processing and output of standardized data in real-time. The working assumption is that real-time engagement with the respondent will increase the Census Bureau's ability to match and geocode address data and subsequently remove these cases from expensive field follow-on operations. 2.2 The 2010 Census Non-ID Processing Assessment Report (http://www.census.gov/2010census/pdf/2010_Census_Non-ID_Processing_Assessment.pdf) contains valuable information about the program.. At a high level, the Use Cases for 2020 Census Real-Time Non-ID that will require respondent validation can be characterized as follows: 2.2.1 The respondent does not have a Census ID. 2.2.2 The respondent will be accessing the survey via Centurion over the Internet. 2.2.3 The respondent will be using a browser on either their mobile device, a computer at their place of residence, or a computer outside their place of residence. 2.2.4 The respondent may or may not have a standardized address for their place of residence. 2.3 Please respond by answering the following questions. 2.3.1 What process do you recommend the Census Bureau use to validate that a respondent is who they say they are and lives at the reported address? 2.3.2 What is the completeness, coverage and quality of data you recommend the Census Bureau use to validate that a respondent is who they say they are and lives at the reported address? 2.3.3 What data sources are available which can be used to validate a respondent is who they say they are and lives at the reported address? 2.3.4 2.3.5 Do you recommend adding a real-time respondent validation process, a post data collection respondent validation process, or both? If recommending a real-time respondent validation process, what steps can be taken to minimize respondent burden? 3.0 Responses 3.1 Responses, in Adobe Acrobat format, are due no later than, 1/2/2015 and should be submitted via e-mail only to nicholas.apperson@census.gov. Please limit responses to no more than 10 pages. Please be advised that all submissions / responses become Government property and will not be returned. 3.2 Proprietary information should be kept to the minimum and MUST BE CLEARLY MARKED. To aid the Government, please segregate proprietary information. 3.3 Please provide information on respondent validation to address the US Census Bureau's questions. Also, please include additional information that would be of value to the government--please mark as "additional information." 3.4 When submitting a response, the following must be provided on company letterhead or pricing document: Full company name: ________________ Business Address: ___________________ Business size: ______________________ Point of Contact for negotiations to include Phone Number and E-mail: ___________________________________________ DUNS Number: _________________________ 4.0 Questions Regarding this Announcement 4.1 Questions regarding this announcement MUST be submitted in writing by e-mail to nicholas.apperson@census.gov. Please e-mail questions regarding this RFI NLT, 12/19/2014. 5.0 Summary 5.1 THIS IS A REQUEST FOR INFORMATION (RFI) ONLY. The US Census Bureau is seeking information on the applicability and viability of using cloud computing for research and testing efforts for the 2020 Census. This RFI is issued solely for information and planning purposes - it does not constitute a Request for Proposal (RFP) or a promise to issue an RFP in the future. This request for information does not commit the Government to contract for any supply or service whatsoever. Further, the US Census Bureau is not, at this time, seeking proposals and will not accept unsolicited proposals.
- Web Link
-
FBO.gov Permalink
(https://www.fbo.gov/spg/DOC/CB/JeffersonvilleIN/RFI_RM15-007/listing.html)
- Record
- SN03580606-W 20141126/141124234417-07ecf52b2ed3869392979b4dd6af4b93 (fbodaily.com)
- Source
-
FedBizOpps Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |