Census 2000 Data Capture

By Bodman, Samuel W.

Book Id: WPLBN0000582548
Format Type: PDF eBook:
File Size: 1.59 MB
Reproduction Date: 2005

Title:	Census 2000 Data Capture
Author:	Bodman, Samuel W.
Volume:
Language:	English
Subject:	Government publications, Census., Census report
Collections:	Government Library Collection, U.S. Census Bureau Collection
Historic Publication Date:
Publisher:	United States Census Bureau Department


Citation APA MLA Chicago W. Bodma, B. S. (n.d.). Census 2000 Data Capture. Retrieved from http://gutenberg.cc/

Description
Statistical Reference Document

Excerpt
Excerpt: This report provides an overall synthesis of issues that were identified in several studies addressing the technical and operational elements of the complex and largescale Census 2000 data capture system. The U.S. Census Bureau outsourced the two major components of the Census 2000 data capture program. Those components were the Data Capture System 2000 (DCS 2000) which was awarded to Lockheed Martin and the Data Capture Services Contract (DCSC) awarded to TRW. Lockheed Martin provided equipment for imaging, recognition, and data keying as well as the processing systems for four Data Capture Centers (DCCs). TRW provided staff and services for data capture, facilities management, office equipment, supplies, and office automation for three of the DCCs. (A fourth DCC was managed by the National Processing Center (NPC), a permanent Census Bureau facility in Jeffersonville, Indiana.) Within the report, a distinction is made between the two components, as appropriate.

Table of Contents
Contents Foreword . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .v 1. Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 2. Scope and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3 3. Data Capture Topics Addressed in this Report . . . . . . . . . . . . . . .5 3.1 Performance of the data capture system . . . . . . . . . . . . . . .5 3.2 The system?s ability to capture questionnaire data . . . . . . . .6 3.3 The impact of data capture requirements on the questionnaire design and other factors . . . . . . . . . . . . . . . .7 3.4 The appropriateness of requirements identified for the data capture system . . . . . . . . . . . . . . . . . . . . . . . ..7 4. Findings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9 4.1 Assessing the performance of the data capture system . . . .9 4.2 Factors affecting the system?s ability to capture questionnaire data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 4.3 Issues relating to the impact of data capture requirements on the questionnaire design and other factors . . . . . . . . . .13 4.4 Examining the appropriateness of requirements identified for the data capture system . . . . . . . . . . . . . . . .13 5. Results of Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 5.1 System performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15 5.2 Capturing respondent data . . . . . . . . . . . . . . . . . . . . . . . .15 5.3 The impact of data capture requirements . . . . . . . . . . . . . .15 5.4 Fluid requirements posed substantial risks . . . . . . . . . . . .16 5.5 Other salient observations about Census 2000 data capture system . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16 6. Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 6.1 Unify the design strategy needed for the data capture system . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 6.2 Define requirements early . . . . . . . . . . . . . . . . . . . . . . . . .19 6.3 Develop quality assurance standards early . . . . . . . . . . . . .19 6.4 Focus on redesigning key data capture problem areas . . . .19 6.5 Limit the number of forms . . . . . . . . . . . . . . . . . . . . . . . .20 6.6 Assess future role of automated data capture technology . .20 6.7 Implement a unified Help Desk . . . . . . . . . . . . . . . . . . . . .20 6.8 Train on the actual working system . . . . . . . . . . . . . . . . . .20 6.9 Expand the time for testing . . . . . . . . . . . . . . . . . . . . . . .20 6.10 Better define Decennial Management Information Systems for future contracts . . . . . . . . . . . . . . . . . . . . . . .21 6.11 Provide more information on the scope of documentation requirements . . . . . . . . . . . . . . . . . . . . . .21 6.12 Minimize the use of keying from paper . . . . . . . . . . . . . . .21 6.13 Produce real-time cost data . . . . . . . . . . . . . . . . . . . . . . . .21 7. Author?s Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . .23 7.1 Implement a more structured approach to defining requirements for the data capture system . . . . . . . . . . . . .23 7.2 Research the potential for expanding the all digital data capture environment . . . . . . . . . . . . . . . . . . . . . . . . .23 8. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27