Agenda l.jpg
This presentation is the property of its rightful owner.
Sponsored Links
1 / 45

Agenda PowerPoint PPT Presentation


  • 101 Views
  • Uploaded on
  • Presentation posted in: General

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

Download Presentation

Agenda

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


Agenda l.jpg

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


Agenda2 l.jpg

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


Agenda3 l.jpg

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


Slide4 l.jpg

Field Data Collection: Vision

2010 Census

Preston Jay Waite

Associate Director for Decennial Census

February 28, 2005


Census 2000 a great success but there is still room for improvement l.jpg

Census 2000 a Great SuccessBut 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


Lessons learned from census 2000 l.jpg

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


The 2010 census reengineering plan l.jpg

The 2010 Census Reengineering Plan

Goals of the 2010 Census

  • Reduce Risks

  • Contain costs

  • Improve accuracy

  • Provide more relevant data


Field data collection vision for 2010 l.jpg

Field Data CollectionVision 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


Field data collection potential benefits l.jpg

Field Data CollectionPotential 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


What has happened with fdca since the august 27 2004 industry day l.jpg

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


Conclusion l.jpg

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


Agenda12 l.jpg

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


Fdca acquisition strategy l.jpg

FDCA ACQUISITION STRATEGY

  • 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


Acquisition milestones l.jpg

ACQUISITION MILESTONES

  • Presolicitation Notice Late April

  • Draft RFPLate April

  • Release RFPJune

  • Technical Interchange/Sept. – Dec. Discussion

  • AwardApril 2006


Small business strategy l.jpg

SMALL BUSINESS STRATEGY

  • Second Conference

  • Goals or Mandatory Percentage will be established on Value Added Work.

  • More to Come


Agenda16 l.jpg

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


Field data collection automation l.jpg

Field Data Collection Automation

Edwin B. Wagner, Jr.

Project Manager

February 28, 2005


Field data collection automation presentation outline l.jpg

Field Data Collection AutomationPresentation Outline

  • Program Overview

  • Functional Requirements

  • Management Requirements

  • Challenges

  • Questions & Answers


Field data collection automation19 l.jpg

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.


Field data collection automation20 l.jpg

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.


Field data collection automation21 l.jpg

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


Field data collection automation functional requirements l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements23 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements24 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements25 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements26 l.jpg

Field Data Collection AutomationFunctional 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)


Field data collection automation functional requirements27 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements28 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements29 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements30 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements31 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements32 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements33 l.jpg

Field Data Collection AutomationFunctional 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


Field data collection automation functional requirements34 l.jpg

Field Data Collection AutomationFunctional Requirements

Local Census Offices

Administrative Activities

General Office Activities (COTS

applications)

Word processing

Document printing

Spreadsheets

E-mail


Field data collection automation functional requirements35 l.jpg

Field Data Collection AutomationFunctional Requirements

Regional Census Centers

Replication of all LCO functions

Additional management reporting

capabilities


Field data collection automation functional requirements36 l.jpg

Field Data Collection AutomationFunctional 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.


Field data collection automation functional requirements37 l.jpg

Field Data Collection AutomationFunctional Requirements

Security Policies & Standards

Department of Commerce IT Program

National Institute of Standards and

Technology

Accreditation of FDCA Systems required prior to production


Field data collection automation management requirements l.jpg

Field Data Collection AutomationManagement Requirements

Program Management

Work Breakdown Structure & Project

Schedule

Earned Value (EV)

Financial Reporting

Monthly Status Reports

Subcontract Participation Plan &

Performance


Field data collection automation management requirements39 l.jpg

Field Data Collection AutomationManagement 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


Field data collection automation management requirements40 l.jpg

Field Data Collection AutomationManagement Requirements

Census Bureau Project Management Office

QA & Surveillance

Integrated Product Teams

Change Control Board

Baseline & Financial Management

Co-location – some but degree unknown


Field data collection automation challenges l.jpg

Field Data Collection AutomationChallenges

Legal Deadlines

No relief

No second chance

High Visibility

Critical customer – Congress

Oversight

Media interest


Field data collection automation challenges42 l.jpg

Field Data Collection AutomationChallenges

Security

Changes in standards

Affordability

Impact on solutions

Murphy’s Law


Field data collection automation challenges43 l.jpg

Field Data Collection AutomationChallenges

Solutions

Nationwide coverage/implementation

Usability

Cost effective

Telecommunications & Support

Effective risk mitigation strategies


Field data collection automation44 l.jpg

Field Data Collection Automation

Questions?


Breakout sessions l.jpg

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


  • Login