1. 1 Agenda 9:30-9:40Welcome Mike Palensky, Chief, Acquisition Division 9:40-9:50Safety at the Suitland Federal Center George Barnett, Human Resources Division 9:50-10:05Keynote Address Preston Jay Waite, Associate Director for Decennial Census 10:05-10:30Acquisition Strategy and Timeline Mike Palensky, Chief, Acquisition Division 10:30-11:30FDCA Scope and High-Level Requirements Q&As Ed Wagner, FDCA Project Manager 11:30-12:30LUNCH 12:00-3:30Demonstration in Gannett/Hollerith Conference Rooms 12:30-2:00 Breakout Sessions: Session I: Auditorium, Session II: Kallek and Session III: Taeuber Rooms 2:00-2:30BREAK 2:30-3:30Q&As and Wrap Up Mike Palensky, Chief, Acquisition Division

2. 2Agenda 9:30-9:40Welcome Mike Palensky, Chief, Acquisition Division 9:40-9:50Safety at the Suitland Federal Center George Barnett, Human Resources Division 9:50-10:05Keynote Address Preston Jay Waite, Associate Director for Decennial Census 10:05-10:30Acquisition Strategy and Timeline Mike Palensky, Chief, Acquisition Division 10:30-11:30FDCA Scope and High-Level Requirements Q&As Ed Wagner, FDCA Project Manager 11:30-12:30LUNCH 12:00-3:30Demonstration in Gannett/Hollerith Conference Rooms 12:30-2:00 Breakout Sessions: Session I: Auditorium, Session II: Kallek and Session III: Taeuber Rooms 2:00-2:30BREAK 2:30-3:30Q&As and Wrap Up Mike Palensky, Chief, Acquisition Division

3. 3 Agenda 9:30-9:40Welcome Mike Palensky, Chief, Acquisition Division 9:40-9:50Safety at the Suitland Federal Center George Barnett, Human Resources Division 9:50-10:05Keynote Address Preston Jay Waite, Associate Director for Decennial Census 10:05-10:30Acquisition Strategy and Timeline Mike Palensky, Chief, Acquisition Division 10:30-11:30FDCA Scope and High-Level Requirements Q&As Ed Wagner, FDCA Project Manager 11:30-12:30LUNCH 12:00-3:30Demonstration in Gannett/Hollerith Conference Rooms 12:30-2:00 Breakout Sessions: Session I: Auditorium, Session II: Kallek and Session III: Taeuber Rooms 2:00-2:30BREAK 2:30-3:30Q&As and Wrap Up Mike Palensky, Chief, Acquisition Division

4. 4 Field Data Collection: Vision 2010 Census Preston Jay Waite Associate Director for Decennial Census February 28, 2005

5. 5 Census 2000 a Great Success But There is Still Room for Improvement We did phenomenal work in the field, but: It was very expensive We were drowning in paper, and We conducted unnecessary field interviews for late mail return households Our systems worked, but they were developed at high risk and without an established enterprise architecture

6. 6 Lessons Learned from Census 2000 If we want to save money in Census 2010, we must do so in the field If we want to save money in the field, we must reduce workload, paper and people If we want quality improvement, we must reduce operational risk in our IT systems and simplify enumerator work assignments If we want to achieve our 2010 Census goals, operational testing of design infrastructure must continue in the decade

7. 7 The 2010 Census Reengineering Plan Goals of the 2010 Census Reduce Risks Contain costs Improve accuracy Provide more relevant data

8. 8 Field Data Collection Vision for 2010 More efficient and accurate field data collection methods without sacrificing data quality Use mobile computing solutions with GPS technology for: Determining accurate locations of housing units Address and map updating activities Nonresponse followup and other field data collection operations Reduce paper data capture Reduce NRFU workload by updating enumerator work assignments daily based on late mail returns

9. 9 Field Data Collection Potential Benefits Increased quality of data – GPS and embedded quality assurance Reduction in costs for field data capture Reduction in NRFU interviews – by providing daily updates on late mail returns Reduced real estate costs – less space required for our 450 + temporary offices

10. 10 What has happened with FDCA since the August 27, 2004 Industry Day? Conducted market research Analyzed preliminary 2004 Census Test evaluation results Selected the field data collection operations/functions that will be automated using mobile computing solutions for 2010 Revised the scope of the FDCA Program Defined the acquisition strategy Established the Project Management Office

11. 11 Conclusion FDCA is a critical effort to the success of the 2010 Census 2010 Census cannot succeed if FDCA fails FDCA cannot succeed without private sector partnership This is where you come in

12. 12 Agenda 9:30-9:40Welcome Mike Palensky, Chief, Acquisition Division 9:40-9:50Safety at the Suitland Federal Center George Barnett, Human Resources Division 9:50-10:05Keynote Address Preston Jay Waite, Associate Director for Decennial Census 10:05-10:30Acquisition Strategy and Timeline Mike Palensky, Chief, Acquisition Division 10:30-11:30FDCA Scope and High-Level Requirements Q&As Ed Wagner, FDCA Project Manager 11:30-12:30LUNCH 12:00-3:30Demonstration in Gannett/Hollerith Conference Rooms 12:30-2:00 Breakout Sessions: Session I: Auditorium, Session II: Kallek and Session III: Taeuber Rooms 2:00-2:30BREAK 2:30-3:30Q&As and Wrap Up Mike Palensky, Chief, Acquisition Division

13. 13 Advisory Multi-Step Process Presolicitation Notice Voluntary Down select on Prime Past Performance, Experience and Some Technical Write Up RFP Phase Two Tracks Paper Technical Interchange / Prototype Development FDCA ACQUISITION STRATEGY

14. 14 ACQUISITION MILESTONES Presolicitation Notice Late April Draft RFPLate April Release RFPJune Technical Interchange/Sept. – Dec. Discussion AwardApril 2006

15. 15 Second Conference Goals or Mandatory Percentage will be established on Value Added Work. More to Come SMALL BUSINESS STRATEGY

16. 16 Agenda 9:30-9:40Welcome Mike Palensky, Chief, Acquisition Division 9:40-9:50Safety at the Suitland Federal Center George Barnett, Human Resources Division 9:50-10:05Keynote Address Preston Jay Waite, Associate Director for Decennial Census 10:05-10:30Acquisition Strategy and Timeline Mike Palensky, Chief, Acquisition Division 10:30-11:30FDCA Scope and High-Level Requirements Q&As Ed Wagner, FDCA Project Manager 11:30-12:30LUNCH 12:00-3:30Demonstration in Gannett/Hollerith Conference Rooms 12:30-2:00 Breakout Sessions: Session I: Auditorium, Session II: Kallek and Session III: Taeuber Rooms 2:00-2:30BREAK 2:30-3:30Q&As and Wrap Up Mike Palensky, Chief, Acquisition Division

17. 17 Field Data Collection Automation Edwin B. Wagner, Jr. Project Manager February 28, 2005

18. 18 Field Data Collection Automation Presentation Outline Program Overview Functional Requirements Management Requirements Challenges Questions & Answers

19. 19 Field Data Collection Automation Provide an integrated solution for the automation applications, hardware, infrastructure and support services as required by our field staff to successfully conduct the operations necessary for the 2010 Census.

20. 20 Field Data Collection Automation  Applications Mobile Computing Equipment Control System/Management Reports Interfaces COTS  Hardware Mobile Computing Equipment LCO/RCC -- PCs, Servers, Printers, Peripherals, etc.

21. 21 Field Data Collection Automation  IT/Telecommunications Infrastructure Voice IT Data  Services Distribution, installation, de-installation, disposition Technical support/Help desk Network monitoring/maintenance Disaster mitigation & recovery

22. 22 Field Data Collection Automation Functional Requirements  Supervisory Structure Enumerators – work out of their homes Crew Leaders (CLs) – supervise 12 – 16 enumerators Field Operations Supervisors (FOS) – supervise 8 – 12 CLs Local Census Offices – manage peak field staff of up to 1,000+ Regional Census Centers (RCCs) – manage 35 – 50 LCOs

23. 23 Field Data Collection Automation Functional Requirements Operations Using Mobile Computing Equipment (MCE)  Address Canvassing  Spring 2009  ~100,000 field staff  Non-Response Follow-Up  Late April – July 2010  ~500,000 field staff  Coverage Measurement  May 2010 – October 2010  ~8,000 field staff

24. 24 Field Data Collection Automation Functional Requirements Applications for Enumerators on Operations Using MCE  Display of/access to assigned address list  Display maps for navigation to/within assigned area  Collect updated address information  Collect updated map information  Collect latitude & longitude (using GPS)  Residential structures  New streets

25. 25 Field Data Collection Automation Functional Requirements Applications for Enumerators on Operations Using MCE Receipt of assignment updates Collection of census questionnaire data Completion of payroll Transmission of collected & payroll data Security for all applications and functions Training on use of equipment & applications

26. 26 Field Data Collection Automation Functional Requirements Applications for Supervisory Staff on Operations Using MCE Replicate functionality for enumerators Approval of enumerators’ payroll and completed work Initiate reassignment of cases Supervisory reports Communication (text messaging)

27. 27 Field Data Collection Automation Functional Requirements  Paper-Based Operations Update/Enumerate Remote Alaska Enumeration Transient Night (T-Night) Coverage Follow-up Special Place/Group Quarters Advance Visit Group Quarters Enumeration Service-Based Enumeration Military Advance Visit Military Group Quarters Enumeration

28. 28 Field Data Collection Automation Functional Requirements Applications for Enumerators on Paper-Based Operations Provide hard-copy listing of assigned addresses Provide hard-copy maps for assignment area Printing of addresses/bar codes for questionnaires

29. 29 Field Data Collection Automation Functional Requirements Applications for Supervisory Staff on Paper- Based Operations Provide hard-copy assignment list Provide hard-copy maps for assignment areas Provide hard-copy supervisory reports

30. 30 Field Data Collection Automation Functional Requirements  Local Census Offices Control systems Inventory of addresses of all living quarters within assigned area Operational data Status information Assignment information Occupancy status/population count Operational identifiers

31. 31 Field Data Collection Automation Functional Requirements  Local Census Offices Control systems (Continued) Management report generation Operational status Productivity, quality, & cost reports Varied reporting levels Delineation/organization of enumerator assignments Ability to access/generate lists/files by operation

32. 32 Field Data Collection Automation Functional Requirements  Local Census Offices Applications for Operations Using MCE Transmission of enumerator assignments & updates Receipt of caseload status, address, census questionnaire, & map data Receipt of payroll & other administrative data Training on use of applications

33. 33 Field Data Collection Automation Functional Requirements  Local Census Offices Applications for Paper-Based Operations Printing of enumerator, CL, & FOS maps Printing of enumerator assignment listings Check-in/recording receipt of completed address listings, maps & census questionnaires Generation of management reports

34. 34 Field Data Collection Automation Functional Requirements  Local Census Offices Administrative Activities General Office Activities (COTS applications) Word processing Document printing Spreadsheets E-mail

35. 35 Field Data Collection Automation Functional Requirements  Regional Census Centers Replication of all LCO functions Additional management reporting capabilities

36. 36 Field Data Collection Automation Functional Requirements  Telecommunications/IT Infrastructure Voice & IT Data Installation Monitoring/problem resolution De-installation Federal Telecommunication Services Government retains option for use Contingent upon services, costs, etc.

37. 37 Field Data Collection Automation Functional Requirements  Security Policies & Standards Department of Commerce IT Program National Institute of Standards and Technology  Accreditation of FDCA Systems required prior to production

38. 38 Field Data Collection Automation Management Requirements  Program Management Work Breakdown Structure & Project Schedule Earned Value (EV) Financial Reporting Monthly Status Reports Subcontract Participation Plan & Performance

39. 39 Field Data Collection Automation Management Requirements  Program Management (Continued) Program Management Reviews (PMRs) Inventory Management Section 508 of the Rehabilitation Act of 1975, as amended Health, Safety, and Security Project -- CMMI level 3 within 1 year

40. 40 Field Data Collection Automation Management Requirements  Census Bureau Project Management Office QA & Surveillance Integrated Product Teams Change Control Board Baseline & Financial Management Co-location – some but degree unknown

41. 41 Field Data Collection Automation Challenges  Legal Deadlines No relief No second chance  High Visibility Critical customer – Congress Oversight Media interest

42. 42 Field Data Collection Automation Challenges  Security Changes in standards Affordability Impact on solutions  Murphy’s Law

43. 43 Field Data Collection Automation Challenges  Solutions Nationwide coverage/implementation Usability Cost effective Telecommunications & Support Effective risk mitigation strategies

44. 44 Field Data Collection Automation  Questions?

45. 45 Breakout Sessions Track 1 – Field Data Collection Environment Session Moderator – Tim Olson 12:30-2:00 p.m. – Hansen Auditorium Track 2 – Infrastructure, Integration, and Implementation Session Moderator – Jack Marshall 12:30-2:00 p.m. – Kallek Conference Room Track 3 – Data Collection Software Applications Session Moderator – Leah Arnold 12:30-2:00 p.m. – Taueber Conference Room Demonstration Room 12:00 – 3:30 p.m. – Gannett/Hollerith Conference Rooms