Docstoc

Sample Resume of Census Agent

Document Sample
Sample Resume of Census Agent Powered By Docstoc
					Field Data Collection Automation Program (FDCA)                8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




                                                  Cover Page

                                    U.S. Census Bureau
                                     Decennial Management Division


                 DRAFT REQUEST FOR PROPOSAL
                                            No. 52-SOBC-5-XXXX


                         FIELD DATA COLLECTION
                         AUTOMATION PROGRAM




                                     Appendix A-2 Page 1 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)                            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




SECTION C – DESCRIPTION/SPECIFICATION ..............................................................4
  C.1    BACKGROUND ...................................................................................................4
  C.2    THE FIELD DATA COLLECTION OPERATIONS............................................5
  C.3    ORGANIZATION OF OPERATIONS .................................................................9
  C.4    FDCA SCOPE......................................................................................................11
  C.5    REQUIREMENTS ...............................................................................................12
  C.5.1    FDCA MOBILE OPERATIONS .....................................................................12
    C.5.1.1 General Requirements ..................................................................................13
    C.5.1.2 Assignment Management Requirements......................................................15
    C.5.1.3 Address List Requirements ..........................................................................16
    C.5.1.4 Mapping and GPS Requirements .................................................................17
    C.5.1.5 Data Collection Questionnaire Requirements ..............................................20
    C.5.1.6 Time/Attendance and Expense (T/A & E) Requirements ............................22
    C.5.1.7 Special Requirements for Supervisor MCEs................................................23
    C.5.1.8 Transmission Requirements .........................................................................24
    C.5.1.9 Mobile Operations Performance Requirements ...........................................25
  C.5.2    FDCA OFFICE OPERATIONS ......................................................................26
    C.5.2.1 RCC, PRAO and LCO Infrastructure Requirements ...................................26
    C.5.2.2 Operational Control (OC) Function Requirements ......................................33
    C.5.2.3 Other Management Information Systems ....................................................44
    C.5.2.4 Evaluations and Experiments [FOR INFORMATION ONLY] ..................44
    C.5.2.5 Other Office Requirements ..........................................................................46
    C.5.2.6 Office Operations Performance Requirements ............................................47
  C.5.3    FDCA TELECOMMUNICATIONS ...............................................................47
    C.5.3.1 General Requirements ..................................................................................47
    C.5.3.2 Voice Requirements .....................................................................................47
    C.5.3.3 Data Requirements .......................................................................................49
    C.5.3.4 Telecommunications Performance Requirements........................................49
  C.5.4    FDCA SUPPORT ............................................................................................49
    C.5.4.1 General Requirements ..................................................................................50
    C.5.4.2 Help Desk and Maintenance ........................................................................51
    C.5.4.3 Network and Systems Operations ................................................................52
    C.5.4.4 Training Support ..........................................................................................53
    C.5.4.5 Support Performance Requirements ............................................................53
  C.5.5    FDCA SECURITY ..........................................................................................54
    C.5.5.1 Certification & Accreditation (C&A) of Information Technology Systems54
    C.5.5.2 Federal Information Processing Standards (FIPS) Requirements ................56
    C.5.5.3 FDCA Support Facilities ..............................................................................56
    C.5.5.4 Personnel Security........................................................................................58
    C.5.5.5 Information Technology Security for OCE, MCE and support facilities ....61
  C.5.6    FDCA MANAGEMENT .................................................................................63
    C.5.6.1 General Requirements ..................................................................................63
    C.5.6.2 CMMI and ISO Requirements .....................................................................64
    C.5.6.3 Communication with the Government .........................................................65

                                          Appendix A-2 Page 2 of 75
                                      PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)                             8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



     C.5.6.4     Work Breakdown Structure and Project Schedule .......................................65
     C.5.6.5     Systems Development Life-Cycle (SDLC) ..................................................67
     C.5.6.6     Earned Value (EV) .......................................................................................69
     C.5.6.7     Financial Reporting ......................................................................................70
     C.5.6.8     Government’s FDCA Project Management Office (FDCA PMO) ..............70
     C.5.6.9     Contract Startup and Kick-off Meetings ......................................................70
     C.5.6.10      Monthly Status Reports ............................................................................71
     C.5.6.11      Subcontracting and Subcontract Participation Plan .................................71
     C.5.6.12      Self-Assessment Report for Award Fee Determination ...........................72
     C.5.6.13      Program Management Reviews (PMRs) ..................................................72
     C.5.6.14      Meetings ...................................................................................................73
     C.5.6.15      Inventory Management ............................................................................74
     C.5.6.16      Section 508 of the Rehabilitation Act of 1975, as amended ....................74
     C.5.6.17      Health, Safety, and Security .....................................................................75
     C.5.6.18      Closeout Requirements ............................................................................75




                                        Appendix A-2 Page 3 of 75
                                    PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



ATTACHMENT 1


      SECTION C – DESCRIPTION/SPECIFICATIONS/WORK STATEMENT

                     Section C – Performance-Based Statement of Work
                        Department of Commerce, Bureau of Census
                         Field Data Collection Automation Contract

SECTION C – DESCRIPTION/SPECIFICATION

C.1     BACKGROUND

The official U.S. Census is described in Article I, Section 2 of the Constitution of the
United States. It calls for enumeration of the people every ten years. This enumeration is
called a decennial census. There are currently two main aspects of a decennial census,
collection of respondent data from paper form mailings, the Internet, and telephone, and
then collection of respondent data by enumerators sent into the field. The latter is called
field data collection and the automation support for these activities, which reflect the scope
of the FDCA contract.

The process begins in 2007, when the Census Bureau will conduct initial activities for a
dress rehearsal of nearly all operations planned for the 2010 Census, including the field
data collection operations. This represents the final operational test of the entire
complement of methodological, procedural, and automation prior to the field data
collection for the decennial census in 2010.

For the 2010 Census, significant preparatory operations begin in early 2009, with the
opening, staffing, and automation and telecommunications build-out for 12 temporary
Regional Census Centers (RCC), the Puerto Rico Area Office (PRAO), and 450+
temporary Local Census Offices (LCO), which will eventually support 27,000+ office
staff, who will monitor, manage, and control approximately 500,000 mobile field staff.
From this framework of RCCs, the PRAO, LCOs, and mobile field staff, the field data
collection process begins with an operation called Address Canvassing. The Census
Bureau conducts Address Canvassing to ensure a complete address list for conducting data
collection operations. The FDCA contract provides both the office and field automation
support required for Address Canvassing. The Census Bureau conducts approximately 18
distinct field operations for the collection of response data (see section J for a full list of
intended operations, their schedules, and operational activities). These operations
constitute the bulk of the enumeration effort for a decennial census. The Census Bureau
has designed these operations to collect data from people who did not respond to the initial
mailings, or to enumerate special populations or people residing in special situations, such
as the military, college dormitories, shelters, etc. The Non-Response Follow-Up (NRFU)
operation reflects an operation in this category, which also will utilize significant
automation support from FDCA. Following the data field collection operations, the

                                     Appendix A-2 Page 4 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



Census Bureau conducts a final set of evaluation operations. These operations are
generally used to determine the accuracy and completeness of the response data and the
effectiveness of field collection operations. Census Coverage Measurement (CCM) is a
vital operation within this category designed to measure the coverage error of the
enumeration of persons and living quarters in a decennial census. FDCA will provide the
automation support required to conduct the type of complex interview required for the
CCM operation.

Within less than 1 ½ years of the start of operations, the Census Bureau must complete all
data collection necessary to update the census address list and enumerate the resident
population of the 50 states, District of Columbia, and Puerto Rico regardless of where they
live. As required by law, the Census Bureau must deliver the state level population counts
and the calculations for reapportioning the United States House of Representatives to the
President by December 31, 2010. By April 1, 2011, the Census Bureau must deliver more
detailed counts to the states for the purpose of redistricting as specified by Public Law 94-
171.

C.2      THE FIELD DATA COLLECTION OPERATIONS

Overview

      1. Non-Field Operations (e.g., questionnaire mailings to households, internet, phone,
         data capture of completed forms at the Data Centers and the National Processing
         Center, etc.)
      2. Field Operations (the scope of FDCA)
                Dress Rehearsal (all field operations)
                Census Operations
                  Preparatory Operations (establish RCCs, PRAO, LCOs, voice/data
                    telecommunications infrastructure, office and management information
                    systems, recruit and train enumerators, etc.)
                  Address Canvassing
                  NRFU
                  NRFU Reinterview
                  16+ Others
                Evaluations and Experiments
                  Coverage Measurement – Person Interview
                  Multiple others to be determined

For the full list of operations, their order and dates of execution, including those which will
remain paper-based with FDCA providing automation to support the production of control
documents, monitoring of status and costs, and general management, see Section J.




                                     Appendix A-2 Page 5 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



The Dress Rehearsal

Prior to conducting the Census and Coverage Measurement operations, in 2008 the Census
Bureau will conduct a dress rehearsal of nearly all operations planned for the 2010 Census.
This will be the final operational test of the entire complement of methodological,
procedural, and automation prior to the onset of production operations. Although the dress
rehearsal requires the full functionality of that needed for the 2010 Census as defined
within this SOW, the scale at which this functionality is required is significantly smaller
for dress rehearsal. Specifically, the dress rehearsal will be conducted in three LCOs and
the regional management will reside within the current BOC Regional Office
infrastructure.

The dress rehearsal begins approximately 2 years in advance of the production census
operations, with the FDCA contractor providing critical automation support to the RCCs,
LCOs, and field staff. The LCOs open in early 2007 with the first operation, Address
Canvassing, starting in April of 2007. The Operations Milestone Schedule and Scale
document available in Section J – Census and Coverage Measurement Operations will
further clarify the timing for both dress rehearsal and 2010 Census production operations.

The outcome of the dress rehearsal will include lessons learned and validation from all
major areas: methodological, procedural and automation. Positive validation of aspects
within methodological, procedural and automation areas supports the approach for the
2010 Census. Lessons learned may evolve into changes that may impact automation
design: new or changes to methods used may require creation of a new operation; new or
changes to procedures may require the creation of a new module within an existing
operation; automation lessons learned may range from code module revisions to
architecture changes. Therefore the FDCA contractor must provide for flexibility and
adaptability to ensure the successful transitioning from dress rehearsal to production
operations.

Address Canvassing

Address Canvassing (AC) involves field verification and correction of addresses for all
living quarters and street features contained in a decennial census extract of the
MAF/TIGER (Master Address File/Topologically Integrated Geographic Encoding and
Referencing.) The MAF and TIGER databases reflect master repositories of addresses and
geographic features maintained by the Census Bureau. Address canvassing requires the
enumerators (typically referred to as “listers” for this operation) to compare the addresses
for the residential structures found in their assignment area to the address and map
information provided from the MAF and TIGER File. The field enumerators will verify
existing living quarters, add new living quarters that missing from the address list, and
delete from the address list living quarters that do not exist on the ground. They will also
capture latitude and longitude coordinates for every structure containing one or more living
quarters. The goal of this operation is to ensure the accuracy and completeness of the


                                     Appendix A-2 Page 6 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



Census Bureau address file and spatial database used to deliver questionnaires and conduct
subsequent data collection operations.

Enumerators will knock on every door to attempt to contact respondents to verify address
information as well as inquire about any additional living quarters. They will compare the
information provided by the respondents to their address list and map, including making
the required changes. They will add any addresses for any residential structures they
locate within their assigned area, but for which the structure’s address is missing from the
address list. They will delete any addresses included on their address list for which they
cannot locate a residential structure within their assignment area. They will make changes
to existing addresses, such as changing an apartment number, if necessary. The
enumerators will make the appropriate corresponding changes to the maps. This will
include adding new street features that are not on the maps, deleting street features that are
not on the ground, and correcting street feature identifiers, including street name, street
type, directional prefixes or suffixes, etc. The enumerators will collect a map coordinate
for every structure that contains a living quarter. In addition, they will classify each living
quarter as a “housing units” or “other living quarters.” “Other living quarters” reflect
living quarters that differ from your typical house, apartment, or mobile home. Other
living quarters include such places as college dormitories, prisons, skilled nursing
facilities, and the like. The Census Bureau will use all map and address updates from
Address Canvassing to update the MAF/TIGER for later Census Bureau operations.

Non-Response Follow-Up (NRFU)

The Census Bureau conducts the Non-Response Follow-Up operation to obtain completed
questionnaires for housing units from which we did not receive a completed questionnaire
through the mail, Internet, or by telephone.

For NRFU, each enumerator requires a list of housing unit addresses to visit, a map for
their assigned area, and the census questions necessary to collect data from household
respondents. The enumerator completes a questionnaire for each housing unit based on the
residents and occupancy status as of Census Day (April 1). The enumerator may capture
or verify GPS coordinates for the structure. The supervisory staff reviews the completed
questionnaires, with the return of any unacceptable questionnaires to the original
enumerator or, if necessary for assignment to another enumerator for
completion/resolution.

The NRFU universe will fluctuate (up and down) during the operation, reflecting mail
returns received after the start of the operation, new housing units discovered, and
additional cases assigned based on data capture results. The enumerator assignments must
reflect these daily fluctuations, making automation support of this operation with an MCE
a critically anticipated improvement.

The NRFU operation requires special procedures for specific areas or under specific
conditions to accomplish the enumeration. These special procedures include:

                                     Appendix A-2 Page 7 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



       Blitz enumeration. In blitz enumeration, a crew of enumerators conducts NRFU on
        a compressed time schedule in specific areas with outstanding workloads. The
        objective involves establishing a large census presence (particularly in hard-to-
        enumerate apartment buildings) to complete large case loads in one massive sweep.
       Local facilitators. By engaging community activists, religious leaders, and other
        recognized local figures, the CLs facilitate the completion of NRFU.
       Paired enumeration. When safety reasons dictate, enumerators work together in
        pairs to conduct NRFU.

Census Coverage Measurement

The Census Bureau conducts an evaluation program to measure coverage error of the
enumeration of persons and living quarters in 2010 Census. This evaluation, referred to as
Census Coverage Measurement (CCM) consists of an independent enumeration of
approximately one percent of the living quarters and persons associated with those living
quarters within the 50 states, the District of Columbia, and Puerto Rico. A key feature of
the CCM involves its “independence” from the rest of census data collection. This
independence dictates certain requirements in managing the CCM, including the automated
systems supporting that management. For example, the Census Bureau plans to have the
RCCs will manage CCM field operations. This configuration will require special
arrangements to ensure the independence of the CCM interviews.

For the 2010 CCM effort, census headquarters will select a sample of geographic areas
composed of one or more contiguous census blocks. Field staffs visit and identify all
living quarters in those geographic areas (known as Independent Listing). Headquarters
compares the address information collected during independent list to corresponding
addresses collected during the census (by computer matching augmented by clerical
review). Specially trained enumerators follow up on the identified discrepancies to obtain
more information to resolve them (known as Living Quarters Follow-up), which may be
done in two phases. Then, CCM enumerators contact the list of sample coverage
measurement addresses and independently enumerate the persons associated with these
addresses (the Person Interview). The Person Interview involves two phases; 1) attempt at
telephone interview for cases having a phone number; and 3) a later personal visit for any
interviews not collected during the telephone phase. Headquarters compares the
enumeration of independently enumerated persons to the information collected during
Census operations. Some discrepancies are identified for yet another visit (the Person
Follow-up) by CCM enumerators to obtain additional information. All of this information
is used to ascertain if the people interviewed in the Person Interview were found in the
census at their right (Census Day) address and if the people enumerated in the census were
enumerated correctly or erroneously.

The functionality associated with both phases of the Person Interview may seem similar to
that requested for NRFU, such as an automated questionnaire, GPS coordinate collection,
automated capture of payroll data, and electronic maps. The Person Interview

                                     Appendix A-2 Page 8 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



questionnaire will be substantially different and more complex than the one used for
NRFU. The Person Interview questionnaire will collect much more than just persons
living at the address and their characteristics. It will also collect information about persons
who may have stayed or at one time lived at that address. The questionnaire must also
collect information on other places the person could have lived or stayed including
alternate addresses. A detailed set of questions are asked for many complex living
situations such as child custody, college students, persons with multiple residences. This is
done in order to determine the correct location to count the person and also to provide the
necessary data to determine if the person was double counted elsewhere. Given the
number of complex situations, the Person Interview instrument is lengthy, with very
complicated skip patterns. An important functionality for the Person Interview involves
providing the enumerator with the capability to incorporate extensive notes into the
computing device to describe more thoroughly complex living situations not adequately
covered by the specific questions during any point in the interview. Given the time it will
take to conduct an interview for some situations, the ability of the Person Interview
instrument to quickly move from one question to the next with virtually no waiting will
prove critical to our success at collecting all of the required information.

C.3     ORGANIZATION OF OPERATIONS

The Census Bureau will establish, and the FDCA contractor will support, temporary office
structures to manage the full range of address update and data collection activities for the
2010 Census. These temporary offices include Regional Census Centers (RCCs), the
Puerto Rico Area Office, and the Local Census Offices (LCOs). The Census Bureau
maintains a hierarchical organizational structure of offices that is geographically
organized, with LCOs reporting to RCCs, which subsequently report to Census Bureau’s
permanent headquarters. The enumerators and other field staff report to the LCOs. Each
RCC will have responsibility for providing management oversight for 35 – 50 LCOs. Each
LCO will have a peak office staff of around 60 people, with a peak field staff of 1,000+.
The FDCA contractor has responsibility for providing the telecommunications and
Information Technology (IT) infrastructure, along with systems, applications, and
peripheral IT hardware necessary for both the RCCs and LCOs to carry out their full range
of management, operational material production, and administrative responsibilities.

As detailed in the graphic below, census enumerators perform the address update and data
collection work. Enumerators, who represent the largest number of positions on the
census, work for short periods of time, ranging from a few weeks to a few months.
Enumerators work out of their homes, with assignments generally located close to their
residence. Crew Leaders (CLs), who also work out of their homes, supervise a group of 12
to 16 enumerators. They generally meet with each enumerator on a daily basis to carry out
their supervisory responsibilities. Field Operations Supervisors (FOS) typically supervise
8 - 12 CLs. This supervisory chain of command has full responsibility for all management
functions, including technical guidance, quality assurance, monitoring of productivity,
administrative activities such as review and approval of payroll, hiring and training of new
staff, termination of staff for poor performance, etc.

                                     Appendix A-2 Page 9 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)                               8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



                                   5-Tier Organizational Structure for
                              Census and Coverage Measurement Operations


National Level                                                     HQ                        Data


                                                                                  Data Centers + the National
 District Level
                                                                                      Processing Center


Regional Level
                                                                12 RCCs                             Data
                                           Field Office Staff




                    Coverage
  Local Level      Measurement
                    Operation                              450+ LCOs
                   bypasses the
                      LCOs        Field Office Staff




  Field Level

                                             FOS                Crew Leader      Enumerator / Lister


A detailed overview of this organization structure can be found in Appendix A of the
FDCA Scope Document.

The Field Data Collection Automation (FDCA) Contract

In the past, field data collection was predominantly handled through paper address lists,
maps, and questionnaires. Although this approach has been developed and used
successfully for all previous Decennial Censuses, the labor cost of handling the paper and
converting information from forms to database entries is high.

For the 2010 Decennial Census, the Census Bureau plans to use automation provided by
the FDCA contract to directly capture information collected during personal interviews and
eliminate the need for paper maps and address lists for the two largest field data collection
operations, Address Canvassing and Non-Response Follow-Up, and the Census Coverage
Measurement Person Interview process. The Census Bureau believes that the cost of
implementing this technology will most importantly be to the Late Mail Return (LMR)
process – significantly reducing unnecessary interviews of housing units whose short form
was received after the date at which the Census Bureau begins the Non-Response Follow-
Up (NRFU) operation. This will reduce workload and complexity of the field operation,
thereby increasing efficiency and reducing operational risk. Other savings and efficiencies
are anticipated related to space requirements for the temporary RCC and LCO facilities,

                                      Appendix A-2 Page 10 of 75
                                  PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



costs associated with data capture of paper forms, and quality and accuracy of data
collected.

While the scope of the FDCA contract is to support all field data collection operations, the
requirements will focus on the direct automation of four operations (Address Canvassing,
NRFU, NRFU Reinterview, and Census Coverage Measurement Person Interview), in
addition to requirements for management information systems support for all paper-based
operations, office networks and systems, and a voice and data telecommunications network
to support all operations. The FDCA contractor will design, develop, test, deploy,
implement, maintain, secure, support, and then de-install and, as appropriate dispose of the
systems, telecommunications, and IT infrastructure required for the management, control,
and conduct of all field data collection and evaluation operations for Census 2010, and the
dress rehearsal of those operations in 2008.

The requirements for field data collection under FDCA have been categorized into six
major areas: Mobile Computing Environment, Office Computing Environment,
Telecommunications, Security, Support, and Management. Ultimately the success of the
FDCA contract and contractor will be measured by their ability to implement these
requirements in a way which supports and enhances the U.S. Census Bureau’s ability to
meet legal deadlines, improve operations, maintain and improve coverage for all
population groups and geographic levels, contain costs, and mitigate risks for the 2010
Census.

C.4       FDCA SCOPE

The scope of the FDCA Program will consist of resources, processes, services, and support
for decennial census field data collection activities as defined below:

         Mobile Operations:
             ▬ Automate the conduct and management of the census and
               evaluation/experimentation operations (e.g., Address Canvassing (AC),
               Non-Response Follow-Up (NRFU), Census Coverage Measurement -
               Person Interview (CCM-PI), etc., and the dress rehearsal of those
               operations).
             ▬ Automate the conduct and management of administrative functions (e.g.,
               collection, submission, and review of time, mileage, expenses, etc.)
             ▬ Automate the conduct and management of supervisory functions (e.g.,
               review and approval of work and payroll, reassignment of work, etc.).
             ▬ Provide the systems, applications, and infrastructure necessary to interface
               mobile field staff systems with Census Bureau and other external systems.

         Office Operations:



                                     Appendix A-2 Page 11 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



              ▬ Provide automation; office equipment; voice, data, and telecommunications
                hardware, software, infrastructure, and supplies.
              ▬ Automate management and administration functions.
              ▬ Provide hardware, software, and telecommunications for interface to
                internal and external systems.

         Telecommunications:
              ▬ Provide LAN, WAN, Internet, point-to-point, etc. Voice/Data/Video
                telecommunications capability.

         Support:
              ▬ Provide IT and telecommunications support across the 50 United States, the
                District of Columbia, and Puerto Rico.
              ▬ Provide IT and telecommunications deployment, update, problem
                resolution, and replacement operation across the 50 United States, the
                District of Columbia, and Puerto Rico.
              ▬ Provide training, training materials, and training products.
              ▬ Provide multiple language support and language data translation.

         Security:
              ▬ Secure all IT and telecommunications according to Federal, Census Bureau,
                state, and local requirements (e.g., U.S. Code Title 13, FIPS 140-2, Public
                Law, Presidential Directive, Homeland Security, NIST, etc.).

         Management:
              ▬ Provide program management services (e.g., cost, risk, systems
                development life-cycle, IT security, accountability, inventory, version,
                configuration, change control, CMM, CMMI, ISO 9000, etc.).

C.5       REQUIREMENTS

      C.5.1   FDCA MOBILE OPERATIONS

      FDCA Field Staff are defined as the Field Operations Supervisors, Crew Leaders, and
      Enumerators. The operations component of the project covers the provision of
      infrastructure, automation, telecommunications, technical procedures, specified
      training and training materials, and support necessary for all field staff who will
      conduct visits to living quarters throughout the United States and Puerto Rico to collect
      respondent data. The estimated staffing levels and workloads for each operation can be
      found in Section J - Workload Performance. Field staff typically work within the local


                                     Appendix A-2 Page 12 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    areas where they live, with most employed for only a few weeks to a few months,
    depending on the specific census operation.

    Providing an intuitive and reliable Mobile Computing Environment (equipment,
    applications, and transmission infrastructure) for field staff to collect and transmit data
    daily represents a critical function. The Address Canvassing Operation involves
    determining the existence and updating the addresses for living quarters during a two-
    month period in the Spring 2009. Non-response Follow-up involves contacting
    occupants of housing units during a three-month period in the Spring/Summer 2010.
    Census Coverage Measurement Person Interview involves the re-enumeration of a
    statistical subset of households following the NRFU operation. The Mobile
    Computing Environment provides the automation equipment, instruments, and
    infrastructure necessary to collect address, map, and response data, as well as
    accomplishing administrative functions such as providing hours worked, mileage, and
    other expenses, and text messaging.

     C.5.1.1     General Requirements

    The General Requirements cover needs common to the entire spectrum of operations
    for this section.

        C.5.1.1.1.   The FDCA contractor shall provide a Mobile Computing
        Environment (MCE) to provide automation support for census field staff to conduct
        their assigned work.

        C.5.1.1.2.   The MCE shall automate the conduct of work functions (i.e., address
        list and map updating, data collection, etc.) and administrative functions (i.e., time
        and attendance, and expense reporting) for field staff conducting the Address
        Canvassing, Non-Response Follow-Up, Non-Response Follow-Up Reinterview,
        and Census Coverage Measurement Personal Interview operations. See the
        Operations Milestone Schedule and Scale document in Section J – Census and
        Census Coverage Measurement Operations for the estimated timing and scale of
        operation needs.

        C.5.1.1.3.    The MCE shall be able to
        store/retrieve/use/input/edit/add/delete/verify each data element (or globally for the
        entire record) of the address lists, maps, and data collection questionnaire files as
        defined by their draft data element specifications in Section J – Data Collection and
        Map Specifications.

        C.5.1.1.4.    The MCE shall generate and assign a unique identification number
        when adding a living quarter within any application on the MCE, which allows this
        type of add (e.g., new address to the address lists, new map spot for a new housing
        unit, etc.). The numbering convention to be used will be specified by the
        Government after contract award.

                                     Appendix A-2 Page 13 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.1.5.    The contractor’s design for their MCE solution shall be based upon
        Section C requirements and the workload and performance specifications outlined
        in Section J – Workload Performance. ***

        C.5.1.1.6.    The FCDA contractor’s solution shall ensure that no data originating
        from the MCE is deleted without positive acknowledgement of data receipt and
        validation (i.e., data are not corrupted, in proper format, of proper type, process-
        able, etc.).

        C.5.1.1.7.    The MCE shall be able to fully operate all its designed functionality
        within all 50 states, the District of Columbia, and Puerto Rico, including urban,
        rural and remote locations.

        C.5.1.1.8.    The MCE shall be able to operate its designed functionality and be
        fully operable by the field staff at the housing unit doorstep/entrance (indoors and
        outdoors), in a stationary running automobile and while walking or standing.

        C.5.1.1.9.    The MCE shall be able to fully operate all its designed functionality
        and be fully usable by the field staff in common weather conditions (e.g., while
        being exposed to rain/sleet/snow, dust, sunshine, day, dusk, night, and in the
        extreme heat or cold conditional as may be found within the 50 United States, the
        District of Columbia, and Puerto Rico during the date when the census operations
        are scheduled to be conducted).

        C.5.1.1.10.  The MCE shall be able to fully operate all its designed functionality
        and be fully operable by the field staff while wearing gloves as appropriate for the
        outdoor weather conditions, which may occur in the 50 United States, the District
        of Columbia, and Puerto Rico during the dates and times when the Census
        Operations are scheduled to be conducted.

        C.5.1.1.11.The MCE and any and all of its required hardware and software
        components shall optimize the field staff productivity.

        C.5.1.1.12.  The MCE and any and all of its required hardware and software
        components shall be designed and implemented in such a way as to prevent or
        minimize: the loss of components, component connectivity problems, loss or
        corruption of data, breakage, and problems with reliability and operability which
        would cause MCE down-time. ***

        C.5.1.1.13.    As practical, the MCE shall be designed to deter the possibility of
        theft (i.e., have limited or no general functionality that would be desirable by the
        general public, have a appearance that would NOT invite theft, etc.).

        C.5.1.1.14.  The MCE and any and all of its required components shall be capable
        of operating 24 hours a day in all 7 time zones covering the US and Puerto Rico for


                                     Appendix A-2 Page 14 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        10 continuous hours (including any standby mode) while actively conducting work
        in the field and away from external power sources. ***

        C.5.1.1.15.    The MCE shall have all aspects of its use, operation, and management
        incorporate intuitiveness and simplicity-of-use so enumerators of varying ages (18
        – 80+) with no familiarity of automation or census activities, can become fully
        productive in the MCE’s use with minimal training. Note – the Government will
        finalize training duration and content after contract award. ***

        C.5.1.1.16.   The design and packaging of the FDCA contractor’s MCE solution,
        and any and all of its required components, shall minimize negative effects from
        power interruption at all times (i.e., the interview is not interrupted, data are not
        lost, transmissions are not prevented, etc.).

        C.5.1.1.17.   The FDCA contractor’s MCE solution shall allow its operation by
        multiple field workers, with the ability to identify each field worker and what tasks
        they have specifically performed within the MCE.

        C.5.1.1.18.  The FDCA contractor’s MCE solution shall use Universal Time for its
        entire designed recording, logging, stamping of dates and times. ***

        C.5.1.1.19.    The MCE shall be designed and implemented such that the Title 13
        data are irretrievable and the device will be unusable by unauthorized personnel.

        C.5.1.1.20.   The FDCA contractor’s MCE solution shall provide the capability,
        from the assignment management and data collection functionality, to add and view
        notes related to a specific case.

        C.5.1.1.21.  The FDCA contractor’s MCE solution shall provide the capability to
        append to previously entered notes, but not edit or delete.

    C.5.1.2      Assignment Management Requirements

    The Assignment Management component of the MCE enables the field workers to
    receive new assignments, review/organize/track progress on single and multiple
    assignments, complete their assigned work and send completed work for review and
    further processing. This component tracks certain status information to assist the field
    worker in their daily activities. For example, this component tracks the date/time they
    pick up an assignment, when they start working on the assignment, when they
    complete work, the outcome of their work, and when they send it for further
    processing. The field worker can sort their assigned work on such things as tracking
    criteria as just described and assignment location information.

    Additional functionality that the Assignment Management component must
    accommodate is the ability to disable partial or whole assignments for an enumerator
    whose work has been reassigned to another field staff member. The reassignment of

                                     Appendix A-2 Page 15 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    work may result from the: 1) resignation or termination of an enumerator; 2) need to
    rework cases due to quality issues, including falsification of data; 3) movement of
    cases to other staff who have completed their caseload or provide special skills (such as
    specific language capabilities, ability to deal with difficult respondents, etc). This
    functionality requires the termination of access to cases by the original enumerator, and
    provision of all required information (address, status flags, notes, etc.) to the
    enumerator being reassigned these cases. Assignment Management also requires
    tracking of reassigned cases, including specific enumerator names, dates, etc.

    Access termination to specific cases during NRFU is also a result of “Late Mail Return
    (LMR)” process. These reflect cases for which the Census Bureau has received a
    completed questionnaire in the mail, or for which respondents have provided their
    census data through the Internet or by telephone. This functionality will reduce
    respondent burden by updating enumerator assignments thereby minimizing the
    incidence of visiting households for which the Census Bureau has already received
    their census data.

        C.5.1.2.1. The FDCA contractor’s MCE solution shall provide the capability for
        the field staff to distinguish between and manage (e.g. review, organize, track,
        assign, reassign, disable, etc.), the work associated with single and multiple
        assignments.

        C.5.1.2.3. The FDCA contractor shall provide a daily process, and an
        implementation of that process, which will disable access to cases and/or
        assignments on the MCE of all affected field staff, based on any “Late Mail
        Returns” (specifically for NRFU) received from respondents or reassignments of
        their cases and/or assignments by supervisory or LCO staff. ***

    C.5.1.3      Address List Requirements

    To conduct the 2010 Census, the Census Bureau requires the most complete and
    accurate address list possible. The functional requirements identified under the
    Address List component reflect the Census Bureau’s objectives for updating the
    address list and associated census maps as part of this operation. Specifically, these
    requirements reflect the enumerators’ need to access the address list for their assigned
    area for purposes of updating it, including addition of addresses identified as missing
    from the list, updating or correcting house number and/or street name, or other related
    information for the addresses shown on the list, and the identification of addresses that
    no longer exist or are used for non-residential purposes.

        C.5.1.3.1. The FDCA contractor’s MCE solution shall provide a capability for the
        field staff to access each address contained in their assignment for purposes of
        determining the accuracy of the address and geographic information.




                                     Appendix A-2 Page 16 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)             8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.3.2. The FDCA contractor’s MCE solution shall provide the capability for
        field staff to add to, or mark for delete, addresses from the work assignment.

        C.5.1.3.3. The FDCA contractor’s MCE solution shall provide the capability for
        the field staff to add/edit/delete/verify address and geographic information for
        individual data elements, or a range of data elements from the address list for a
        work assignment and to input/edit status codes related to an address from the
        address list. See Section J – Data Collection and Map Specifications for status
        codes and address list fields.

        C.5.1.3.4. The FDCA contractor’s MCE solution shall provide a capability to
        search for a specific address contained on the list, displaying its correct location on
        the appropriate section of the census map at the appropriate scale, with the
        requested item displayed in the center of the map.

        C.5.1.3.5. When an enumerator chooses to delete an address from their address
        list, the FDCA contractor’s MCE solution shall not actually delete the entry from
        the list but shall only flag the address as deleted and prompt for the specific reason
        for the delete by the field worker.

        C.5.1.3.6. When an address being reviewed has a duplicate or alternate address,
        which also points to the same physical structure and geographic location, the
        FDCA contractor’s MCE solution shall provide the capability for the user to
        designate one address as “primary” and any additional address as “duplicate.”

        C.5.1.3.7. The FDCA contractor’s MCE solution shall provide the capability for
        the field staff to search/sort/filter the address list for view/input/edit/delete based on
        any field or combination of fields within the address list record definition. This
        search/sort/filter capability shall provide the flexibility to view and take action on
        the results of the request using multiple methodologies to enhance user friendliness
        (e.g., results display containing only the addresses meeting the specified criteria,
        results display containing all addresses with those addresses meeting the criteria
        being flagged, etc.).

        C.5.1.3.8. The FDCA contractor’s MCE solution shall provide the capability to
        undo an entry in an address field, to cancel an entire address action before saving,
        and to restore the address record to its original condition as it was prior to making
        changes.

    C.5.1.4      Mapping and GPS Requirements

    The Mapping and GPS components of the FDCA contractor’s MCE solution must be
    tightly integrated with the Address List function. The purpose of automating the
    Mapping with GPS component is three fold: 1) to assist the field worker in navigating
    to the correct location, incorporating “You are here.” functionality; 2) to place each
    individual living quarters at its correct geographic location, (i.e., census block.); and 3)

                                     Appendix A-2 Page 17 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    provide the ability to update the census maps, including the addition, update,
    correction, or deletion of streets, street names, and other related information. In
    addition to the objective to enumerate the entire resident population, the 2010 Census
    must also provide accurate tabulations of data for a wide range of political, statistical,
    and administrative areas. The Census Bureau’s ability to meet the requirements for
    providing these types of tabulations starts with the accurate assignment of each living
    quarters to its appropriate census block. The primary goals of the GPS capability
    include: 1) collecting the most accurate coordinate possible for determining the
    geographic location of each address; and 2) providing the capability for the enumerator
    to indicate the location of the address where the GPS coordinates are not accurate
    enough or not available.

    Enumerators conducting the Address Canvassing Operation will add new street
    features to the census map, including the collection of required GPS coordinates.
    Where not possible, the enumerator may use a manual process to indicate the location,
    direction, and name information associated with a new street. The manual process for
    adding a new street must facilitate the ability to ensure the geographic assignment
    accuracy of all addresses located along the new feature.

        C.5.1.4.1.   The FDCA contractor’s MCE solution shall provide the capability to
        update the census maps, including the addition, update, correction, or deletion of:
        map spots, streets (add and delete only), and their related attributes.

        C.5.1.4.2.    Through a single step user operation, the FDCA contractor’s MCE
        solution shall allow the collection and input of longitude and latitude coordinates
        for an existing or new structure (i.e., map spotting), using coordinates gathered by
        manual means (note - this functionality shall not require the field staff to input the
        longitude and latitude numbers manually) and by GPS means when a signal is
        available.

        C.5.1.4.3.    The GPS within the FDCA contractor’s MCE solution shall be
        capable of a three (3) meter or better positional accuracy when it acquires a Wide
        Area Augmentation System (WAAS) signal. Note –coordinates shall be collected
        regardless of accuracy or signal availability.

        C.5.1.4.4.    When GPS coordinates are received by the FDCA contractor’s MCE
        solution, the device shall automatically record the coordinates if they were
        determined via a GPS WAAS or GPS non-WAAS signal.

        C.5.1.4.5.    Where no GPS signal is received, the device shall record the longitude
        and latitude coordinates as a manual entry.

        C.5.1.4.6.      The FDCA contractor’s MCE solution shall flag collected GPS
        coordinates that place a unit in a different census block than the block in which the
        unit is listed.


                                     Appendix A-2 Page 18 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.4.7.    When a new map spot is input on the FDCA contractor’s MCE
        solution, the system shall automatically generate and assign a new Map Spot
        Number for that structure being spotted which has not previously been used by
        Census Bureau for that Census Block or CCM cluster as appropriate (note – the
        Census Bureau requires all map spots be numbered uniquely within each Census
        Block or CCM cluster. See Section J – Universe for map spot number
        specifications).

        C.5.1.4.8.    When the FDCA contractor’s MCE solution collects a new set of
        coordinates for a structure with an existing map spot defined, then the FDCA
        contractor’s MCE solution shall display the newly collected/spotted map spot, and
        also retain the coordinates of the pre-existing map spot.

        C.5.1.4.9.   The FDCA contractor’s MCE solution shall place new map spots
        input by the user where they indicate on the map regardless of the GPS coordinate
        collected.

        C.5.1.4.10.  The FDCA contractor’s MCE solution software shall restrict the field
        staff from entering map spots outside of the census block for which they are
        conducting address update or data collection activities.

        C.5.1.4.11.  The MCE shall store Census map (spatial) data files containing all
        blocks of the field worker’s assignment plus an extended as appropriate for the
        assignment area to be determined.

        C.5.1.4.12.  The contractor’s MCE solution shall graphically and/or textually
        display the data elements from the census map data file as appropriate to the
        function being performed (e.g., navigation, map spotting, etc.).

        C.5.1.4.13.  When graphically displaying a map, the MCE shall have a “You Are
        Here” indicator on the map, which is based on the MCE’s determination of its
        location.

        C.5.1.4.14. The FDCA contractor’s MCE solution shall provide rescaling (e.g.,
        zoom in and zoom out) capability for displaying of maps.

        C.5.1.4.15.  The FDCA contractor’s MCE solution shall provide a scroll or pan or
        similar capability in any direction desired for displaying of maps.

        C.5.1.4.16. The FDCA contractor’s MCE solution shall provide a capability to
        zoom in based on the field staff selecting a specific region of the map currently
        displayed.

        C.5.1.4.17.   The FDCA contractor’s MCE solution shall provide the capability to
        view the list of addresses associated with an individual map spot, street within their
        assignment area, or census block they select while viewing a map.

                                     Appendix A-2 Page 19 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.4.18.   The FDCA contractor’s MCE solution shall provide the capability to
        view the map for a selected address, census block, or census tract selected from a
        display of the address list.

        C.5.1.4.19.  The FDCA contractor’s MCE solution shall automatically delete
        received assignment maps only after successful transmission.

    C.5.1.5      Data Collection Questionnaire Requirements

    The Data Collection Questionnaire component enables the field workers to gather
    respondent information required by the Census. There are three unique instances
    requiring an automated questionnaire under the scope of this contract: 1) automating
    the data collection of response data for census operations; 2) automating the data
    collection of response data for reinterview operations; and 3) automating the data
    collection of response data for Census Coverage Measurement operations.

    The Census Bureau mails paper questionnaires to the majority of the approximately
    130 million households, with most of the remainder delivered by census enumerators.
    Non-Response Follow-Up (NRFU) involves having enumerators contact those
    households who did not respond to the mail out to obtain a completed census
    questionnaire. Other Census operations, such as Update Enumerate, will continue to
    utilize paper questionnaires, unless the Government, in conjunction with the FDCA
    contractor, determines to accept any cost and schedule changes associated with
    automating such data collection operations.

    The interview data collected from respondents, such as collected during NRFU will
    flow through quality control operations. This process, known as reinterview, involves
    having a separate enumerator staff conduct independent interviews at a sample of
    households for purposes of comparing the results with the responses obtained by the
    enumerator. The Census Bureau conducts reinterview for purposes of identifying any
    systematic quality issues, along with any corrective action necessary. In cases where
    the reinterview process determines that an enumerator has falsified data for one or
    more households, the corrective action will involve termination of the original
    enumerator and rework of all appropriate cases.

    The Data Collection Questionnaire component must also accommodate the conduct of
    a separate independent survey, called Census Coverage Measurement, to measure the
    overall quality of the census results. During this survey, field staff will conduct a
    telephone or personal interview with pre-specified households to collect the census
    information for all persons who resided there on Census Day. This is an extensive
    interview, which requires collection of alternative addresses where the person may
    have been enumerated for many complex living situations. As such the questionnaire
    is lengthy and has complicated skip patterns and also relies on the ability for
    enumerators to include extensive notes at any point in the interview. We call this
    activity, which occurs in the Fall 2010, the “Person Interview” component of the

                                     Appendix A-2 Page 20 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    Census Coverage Measurement Operation. The questionnaire required for this
    interview involves an extended series of questions in addition to the basic census items
    designed to ensure a complete and accurate list of all people who should be considered
    living at each unit. Subsequent activities involve matching the results of the Person
    Interview to the census data collected through regular census operations, including
    mail returns, Internet or telephone responses, and other personal visit enumeration
    operations, such as NRFU.

        C.5.1.5.1.   The FDCA contractor’s MCE solution shall automate the census
        questionnaires for conducting NRFU + NRFU Reinterview.

        C.5.1.5.2.    The FDCA contractor’s MCE solution shall automate the census
        questionnaires for conducting the Census Coverage Measurement Personal
        Interview Operation and the Census Coverage Measurement reinterview quality
        assurance activity.

        C.5.1.5.3.   The FDCA contractor’s MCE solution shall implement data collection
        questionnaire specifications in a manner that facilitates interviewing respondents at
        each assigned housing unit or new housing unit identified in their assignment. Final
        questionnaire specifications to be provided by the Government after contract
        award. See Section J – Data Collection and Map Specifications for examples of
        questionnaires.

        C.5.1.5.4.   The Data Collection Questionnaires shall provide the capability to
        input/review/edit/update/delete any and all data fields requiring input by the
        enumerator.

        C.5.1.5.5.    The MCE shall provide a capability, with prompting to ensure the
        user understands the consequence of this action, to blank out any or all fields within
        a case that have not already been transmitted should the enumerator determine the
        data they have entered are incorrect.

        C.5.1.5.6.   MCE data collection questionnaire shall provide the capability to exit
        a case before completion, saving all data collected to that point for later access.

        C.5.1.5.7.   MCE data collection questionnaires shall provide the capability to
        resume an incomplete case and upon user action, to re-open a given case, the
        FDCA contractor’s MCE solution shall position the user at the point in the data
        collection questionnaire where he/she left off.

        C.5.1.5.8.    The FDCA contractor’s MCE solution shall pre-populate the data
        collection questionnaire for cases designated for reinterview with specified census
        data for all members of the household included in the original response.

        C.5.1.5.9.     The FDCA contractor’s MCE solution shall provide the capability for
        the field staff to conduct a replacement interview (i.e., interview the same

                                     Appendix A-2 Page 21 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        household for a case previously completed and checked-out as completed from the
        LCO).

        C.5.1.5.10.   If multiple data collection files are created on a single case, the FDCA
        contractor’s MCE solution shall uniquely identify each of those files while still
        retaining their identification, which associates them to the same case.

        C.5.1.5.11.  All data collection questionnaires and the supporting help screens on
        the FDCA contractor’s MCE solution shall be required in both Spanish and
        English. Note - Different versions of Spanish may be used stateside and in Puerto
        Rico; additional languages may be requested after contract award.

        C.5.1.5.12.   The FDCA contractor’s MCE solution shall provide the capability to
        toggle between the English and Spanish versions of data collection questionnaires
        at any point in the process while retaining any data previously entered.

        C.5.1.5.13. The entire MCE solution shall be required in Spanish for operations
        conducted in Puerto Rico (including the operating system).

        C.5.1.5.14.The FDCA contractor shall only use translations provided by the
        Census Bureau for all non-English language requirements.

    C.5.1.6      Time/Attendance and Expense (T/A & E) Requirements

    The T/A & E component enables the field workers to submit their hours worked, miles
    driven, and other related expenses in an electronic format. The primary goals for
    automating this component include: 1) providing referential integrity checks to
    minimize errors and effectively link hours claimed with the actual work completed; and
    2) using automation to simplify and expedite the submission of all required
    information, thereby reducing the amount of training required and delays in payment.
    The near real-time linkage of completed work to cost will provide the type of timely
    and accurate reporting that will facilitate the effective management of staff and
    resources.

    Section J – Time/Attendance & Expenses contains a mock up of the “Daily Pay and
    Work Record”, a paper version of the T/A &E form, report examples and a layout of
    the data to be delivered to DAPPS, as defined for the 2006 test for the MCE. These
    document are provided for information purposes to help clarify the functionality
    required for the FDCA contractor’s MCE solution as specified below. The
    Government and FDCA contractor will work together to finalize the detailed
    requirements associated with this component.

        C.5.1.6.1. The FDCA contractor’s MCE solution shall provide a time and expense
        capture capability (e.g., automated form, etc.) with the ability to add, store, edit and
        delete data elements as shown in Section J – Time/Attendance & Expenses


                                     Appendix A-2 Page 22 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.6.2. The FDCA contractor’s MCE solution shall stamp all time and expense
        files with an identifier that uniquely identifies the specific MCE and field staff
        person, using information that uniquely identifies the person and the device.

        C.5.1.6.3. The FDCA contractor’s MCE solution shall stamp each time and
        expense file with a date/time identifier that complies with audit report GAO-03-
        352G, dated January 2003 (See www.GAO.gov).

        C.5.1.6.4. The FDCA contractor’s MCE solution shall provide the type of quality
        control and referential integrity checks on the fields within the time and expense
        forms as described in Section J – Time/Attendance & Expenses.

        C.5.1.6.5. The FDCA contractor’s MCE solution shall provide a mechanism,
        which shall create a referential link between the Time and Expense data the field
        staff submits and the specific Assignment(s) and Case(s) for which they were
        incurred.

        C.5.1.6.6. The FDCA contractor’s MCE solution shall delete from the MCE the
        Time and Expense data or files once both of the following two conditions have
        been met: 1) the data were successfully transmitted; and 2) Time and Expense data,
        which are older than 14 days from the current date.

    C.5.1.7      Special Requirements for Supervisor MCEs

    The FDCA contractor’s MCE solutions provided to supervisors (i.e., Field Operations
    Supervisors and Crew Leaders) must contain all of the functionality of their
    subordinate field staff, since they may temporarily or permanently take over a field
    staff’s assignment during Address Canvassing or Data Collection (NRFU or Census
    Coverage Measurement.) In addition to these enumerator MCE functions, the
    supervisor must manage the work of their crew of enumerators (see Section C.3
    Organization of Operations for crew information). In the event that an enumerator
    resigns, falls behind, or is terminated, the field supervisor requires the ability to
    reassign part or all of their work to another enumerator or to themselves. As part of
    their management of their staff, field supervisors must certify the payroll of each their
    staff, including reviewing the associated completed work. Therefore, the field
    supervisors’ MCE must contain additional functionality to support these management
    processes:

        C.5.1.7.1. The FDCA contractor’s MCE solution shall provide the additional
        capability for Field Operations Supervisors and Crew Leaders to retrieve, access,
        store, manage, and delete when no longer needed, FOS/CL/Enumerator
        management reports (see Section J – MCE Reporting) generated by Office
        Computing Environment (OCE).

        C.5.1.7.2. For Address Canvassing and Non-Response Follow-up, the FDCA
        contractor’s MCE solution shall provide the capability for Field Operations

                                     Appendix A-2 Page 23 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        Supervisors and Crew Leaders to assign, reassign case(s) or assignment(s) to one or
        more subordinate enumerators, and to change that assignment as needed within
        their respective area of responsibility over the course of the field data collection
        operation.

        C.5.1.7.3. The FDCA contractor’s MCE solution shall provide the capability for
        Field Operations Supervisors and Crew Leaders to review blocks or cases with
        specific status codes (see Section J – Data Collection and Map Specifications), and
        if necessary reassign selected blocks or cases. The government will supply the
        specific codes after contract award.

        C.5.1.7.4. The FDCA contractor’s MCE solution shall incorporate the capability
        for Field Operations Supervisors and Crew Leaders to access time and expense data
        transmitted by their assigned field staff for purposes of reviewing and
        certifying/approving or rejecting with further explanation/correction, including the
        retransmission of the original data along with appropriate action flags and
        instructions back to the OCE.

        C.5.1.7.5. The FDCA contractor’s MCE solution shall provide the capability for
        Field Operations Supervisors and Crew Leaders to send text messages to their
        assigned field staff (i.e., Crew Leader to Enumerator for the Crew Leaders, Field
        Office Supervisor to the Crew Leader for the Field Office Supervisors, any LCO
        staff to any Field Staff) using either the LCO’s OCE or their MCE.

    C.5.1.8      Transmission Requirements

    The primary purpose of the Transmission component of the MCE is to send and
    receive data as necessary for field staff to complete their assigned work, including
    administrative functions. Although simply described in an individual mode, the
    requirements below become highly complex when considering the number of staff
    transmitting at peak, the volume of data being transmitted, the geographic (U.S and
    Puerto Rico) operability requirements of the transmission network, and the frequency
    and speed requirements relation to the supervisory functions, such as quality reviews,
    reassignment of work, certification of payrolls, etc. The success of the use of MCEs
    for the 2010 Census will rely in large part on the ability to ensure effective, efficient,
    accurate, secure, and frequent transmissions, with a minimum requirement for daily
    transmissions from every field staff.

    The transmission process is heavily monitored by RCC and LCO staffs to ensure field
    workers are transmitting daily. This expectation is required to meet the strict deadlines
    associated with the Census and to proactively pinpoint potential problem areas.

        C.5.1.8.1. The FDCA contractor’s MCE solution shall be capable of transmitting
        (i.e., receiving and sending) all required data for single or multiple assignments.



                                     Appendix A-2 Page 24 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.1.8.2. The FDCA contractor’s MCE solution shall be capable of transmitting
        (i.e., receiving, sending, logging and acknowledging success/failure), any and all
        assignment and payroll data (e.g., address lists, maps, GPS data, payroll forms and
        data, expense forms and data, messages from supervisors, etc.), including additions
        and updates, necessary for the field staff to conduct, report on, and complete their
        work in the field.

        C.5.1.8.3. The FDCA contractor’s MCE solution shall be capable of receiving,
        processing, and validating acknowledgement receipts.

        C.5.1.8.4. The FDCA contractor’s MCE solution shall generate a status report on
        all transmissions attempted by the MCE to date, and shall append to that report for
        viewing by the MCE user.

        C.5.1.8.5. The FDCA contractor’s MCE solution shall send field staff’s gathered
        case data automatically based on the status indicator for that case. Details to be
        determined/provided post contract award.

        C.5.1.8.6. The FDCA contractor’s MCE solution shall remind the field staff to
        complete their T&A data daily if the MCE determines that their T&A data are not
        completed and the MCE is in a state of sending assignment data to the respective
        destination system.

        C.5.1.8.7. The FDCA contractor’s MCE solution shall have the capability for the
        field staff to send their completed Assignment and Time/Expense data on demand.

        C.5.1.8.8. The FDCA contractor’s MCE solution shall acknowledge to the sending
        system when it has successfully received all data being transmitted, i.e. that is valid
        and process-able by the MCE.

        C.5.1.8.9. If, in the process of transmitting (i.e., sending or receiving), the FDCA
        contractor’s MCE solution is unsuccessful, the MCE shall automatically retry until
        it has successfully accomplished the transmission.

        C.5.1.8.10. The MCE Transmission Log shall note what was transmitted, the date,
        time, user, destination, content/data type, and the outcome status.

        C.5.1.8.11. The MCE Transmission Log shall be a permanent log on the MCE to
        which information can be appended, but not deleted without appropriate
        authorization.

    C.5.1.9      Mobile Operations Performance Requirements

        C.5.1.9.1. The FDCA contractor shall provide a Mean Time to Repair (MTTR)
        (e.g. time from problem report to restore unit to exact function just prior to the
        failure) of 24 hours for all components used to provide the MCE solution.

                                     Appendix A-2 Page 25 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



C.5.2   FDCA OFFICE OPERATIONS

The FDCA Office Operations includes providing an Office Computing Environment
(OCE) of hardware, software, telecommunications, technical procedures, and training
materials and applications to enable a temporary staff to carry out census operations
within:
    Regional Census Centers (RCC) and the Puerto Rico Area Office (PRAO) will
        provide overall management and oversight of the Local Census Offices (LCOs).
        The Government will provide the RCC and PRAO facilities, furnishings, HVAC,
        electrical, supplies, and staffing for government operations.
    Local Census Offices are located throughout the United States and Puerto Rico.
        The LCOs oversee and support the census data collection process during Census
        Field Operations. The Government will provide the LCO facility, furnishings,
        HVAC, electrical, supplies, and staffing.

The automation provided, in addition to enabling the typical office automation needs, will
include specialized systems that seamlessly interface with the mobile computing
environment of the enumerator to monitor, send, and receive data as necessary for field
staff to complete their assigned work including administrative functions. Additional
specialized systems include automated control and tracking systems (e.g., a management
information system to automate operations control (OC) functions) for the management,
monitoring, and control of both electronic (Address Canvassing, Non-Response Follow-
Up, Census Coverage Measurement Person Interview) and paper-based (e.g., Group
Quarter Validation, Update Leave, etc.) census operations.

    C.5.2.1       RCC, PRAO and LCO Infrastructure Requirements

    The RCC, PRAO and LCO Infrastructure requires the coordination of the Government,
    GSA, the FDCA contractor and any other government contracts involved in the space
    build out. Space build out refers to the physical readiness, including electrical,
    heating/cooling, and any telecommunication requirements for the space. The space
    build out, under GSA contract, will require power and telecommunication requirements
    from the FDCA contractor related to the FDCA deliverables and GFE.

    The system design for the RCCs/PRAO and LCOs must accommodate a wide range of
    applications (developed under FDCA, developed by other contracts, developed by the
    Census Bureau) as required under this SOW (see Section J – Interfaces). Note – the
    interfaces specified in Section J is not a comprehensive list and other interfaces may be
    required post award.

        C.5.2.1.1     The Role of the Government

              C.5.2.1.1.1.   The Government will provide, specify the standards of, and be
              responsible for the RCC, PRAO and LCO build out (i.e., electrical, walls,
              floors, HVAC, physical security system, furniture, and remaining utility

                                     Appendix A-2 Page 26 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             infrastructure) prior to the FDCA contractor’s installation of contract
             deliverables.

             C.5.2.1.1.2.  The Government will provide the FDCA contractor their
             schedules and status for all RCC, PRAO and LCO space build-outs as they
             become available.

             C.5.2.1.1.3.    The Government will provide RCC/LCO on-site FDCA
             contractors the space and office furniture necessary to accomplish their work if
             it determines / or awarded solution requires- on-site contractor support as
             necessary for contract performance fulfillment.

             C.5.2.1.1.4.     The Government will provide the staff necessary to: open the
             facility; to allow delivery inside government controlled space; to allow for the
             receipt of equipment the FDCA contractor supplies for the OCE of each RCC,
             PRAO and LCO.

             C.5.2.1.1.5.    The Government will review and certify as ready for deployment
             in accordance with the test and acceptance plan (see Section C.5.6.5) the FDCA
             contractor installed OCE for each RCC, PRAO and LCO.

        C.5.2.1.2     General and Environment Requirements

             C.5.2.1.2.1.   The FDCA contractor shall provide an Office Computing
             Environment (OCE) to provide census field staff the automation capability
             necessary to conduct their assigned work related to field data collection at all
             RCCs/PRAO and LCOs.

             C.5.2.1.2.2.      The entire OCE for PRAO shall be in Spanish.

             C.5.2.1.2.3.    The FDCA contractor shall automate the conduct of all
             RCC/PRAO and LCO field data collection related work functions (i.e., word
             processing, spreadsheet, database, printing, monitoring/managing/controlling of
             automated and paper based census and census coverage measurement
             operations, etc.). See Section J – Census and Census Coverage Measurement
             Operations for the estimated timing and scale of operations needs.

             C.5.2.1.2.4.   The FDCA contractor shall as necessary design, develop,
             acquire, configure, integrate, test, install, de-install, support and maintain all
             hardware, software (including integration of GFE COTS and GFE custom
             software – see Section J - Interfaces), and telecommunications delivered to each
             RCC, PRAO and LCO to create a standard operating environment for the RCC,
             PRAO and the LCO.

             C.5.2.1.2.5.   The integrated OCE & MCE environment that the FDCA
             contractor provides shall be able to operate and provide its full functionality

                                     Appendix A-2 Page 27 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             for: all RCCs which will generally be located within the metropolitan areas of
             the existing regional offices; at all LCOs where ever they operate within the 50
             states, District of Columbia, and Puerto Rico, including rural/urban and remote
             areas; and within the space and environmental constraints of the RCCs/PRAO
             and LCOs as provided by the Government. ***

             C.5.2.1.2.6.    The FDCA contractor shall ensure that the OCE they provide for
             the RCCs/PRAO and LCOs be able to effectively and efficiently operate within
             the constraints of the physical, environmental, and operational conditions of the
             field offices.

             C.5.2.1.2.7.    The FDCA contractor shall design and implement the
             infrastructure of the OCEs to allow for moderate expansion (not to exceed
             20%), adds, moves, and change without the need to significantly alter that
             infrastructure. For example, if more voice and data equipment and printers are
             needed, then the infrastructure should be robust enough to support it without
             having to procure additional routers/hubs/switches/voice-ports/data-ports, etc.

             C.5.2.1.2.8.    Upon closeout of each RCC, PRAO and LCO or upon
             repair/replacement of any equipment during operations, the FDCA contractor
             shall de-install, degauss or otherwise sanitize (to include tracking and reporting
             on items sanitized) all systems and storage that maintained any data to render
             the data completely unrecoverable in whole or in part, and dispose of all
             equipment, systems, and other deliverables provided by the FDCA contractor as
             specified by the Government.

             C.5.2.1.2.9.  The FDCA contractor shall provide to GSA within the
             timeframe required by GSA, the FDCA contractor's electrical, voice, data
             requirements, with wiring/cabling diagram(s) for the RCCs/PRAO and LCOs
             needed to support the intended deliverables and GFE within those locations

             C.5.2.1.2.10.  The OCE at the RCCs/PRAO and LCOs shall each be provided
             with the current predominant removable storage medium of the day (e.g.,
             floppy drives, CD drive, DVD drives, etc.) as appropriate to the needs of the
             FDCA contractor’s solution.

             C.5.2.1.2.11.  The FDCA contractor shall work with the PMO and other key
             organizations, including Field Division and GSA, to establish processes,
             procedures, detailed activities and schedules associated with installing and
             maintaining the automation required at the RCCs/PRAO and LCOs.

             C.5.2.1.2.12.   The FDCA contractor shall establish a process, with supporting
             automation, which captures and maintains a central searchable document
             repository of all government correspondence generated during the life of this
             project. This repository shall be accessible by staff at HQ, RCCs/PRAO, and
             LCOs with access controls.

                                     Appendix A-2 Page 28 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.1.2.13.  The OCE of the RCCs/PRAO and LCOs shall interface as
             required with external systems listed in Section J – Interfaces.

             C.5.2.1.2.14.   The FDCA contractor shall ensure that all applicable municipal
             code requirements are observed for the installation and maintenance of all
             deliverables (e.g., voice communication systems, data communication systems,
             etc.).

             C.5.2.1.2.15.   The FDCA contractor shall take into account and address the
             various installation scenarios and terms that may be encountered in the facilities
             the Census Bureau leases space with. The Government FDCA Contractor
             Officer may direct the FDCA contractor to use specified contractors.

             C.5.2.1.2.16.   The FDCA contractor shall be required to employ labor sources
             which are certified by the current established certification authorities (e.g.,
             Institute of Electrical and Electronics Engineers (IEEE), etc.) to perform any
             cabling installations which may be required for build-out, installation, testing,
             and maintenance of deliverables (e.g., voice, data, etc.).

             C.5.2.1.2.17. The FDCA contractor shall design, develop, provide, update,
             and maintain a Space Leasing and Property Management Tracking System
             (SLPMTS) providing read/write use capabilities for Census Bureau users and
             FDCA contractors for the duration of the Space Leasing and Property
             Management process. Users of the system will include, Census Bureau staff,
             FDCA contractors, and other personnel, as appropriate.

             C.5.2.1.2.18.  The SLPMTS shall be developed, maintained, and modified by
             the FDCA contractor(s) as needed, per Census specifications, during the
             duration of the Space Leasing and Property Management process.

             C.5.2.1.2.19.   The FDCA contractor shall provide the near-real time capability
             for Census HQ to monitor the operations of each RCC, PRAO and LCO (i.e.,
             their functions, systems, and data through direct access, monitoring reports, or a
             combination of both).

             C.5.2.1.2.20. The OCE functionality related to the Census Coverage
             Measurement Operation shall only be accessible to and operated from the
             RCC/PRAO, with appropriate design, implementation and access controls to
             ensure independence from regular census operations.

             C.5.2.1.2.21.   The OCE of the RCCs/PRAO and LCOs shall provide the
             capability to generate and send electronic textual messages to any and all field
             staff's MCE.




                                     Appendix A-2 Page 29 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)             8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.2.1.3     Contingency Requirements

             C.5.2.1.3.1.    The OCE functionality provided for LCO operations shall be
             replicated at the RCCs, PRAO and another LCO (in addition to the work
             already performed at that LCO), as a contingency in the event that an LCO
             cannot function.

             C.5.2.1.3.2.    The OCE functionality provided at the RCC/PRAO, shall be
             replicated at Census HQ, another RCC, or alternate site as a contingency in the
             event that the RCC/PRAO cannot function.

        C.5.2.1.4     Office Systems Networking Requirements

             C.5.2.1.4.1.    The OCE shall provide access control for its functions and data
             for a variety of user-type classifications.

             C.5.2.1.4.2.      The OCE shall provide printing capability for all OCE users.

             C.5.2.1.4.3.    The FDCA contractor shall provide a mechanism which ensures
             the efficient and expeditious transfer of the Census Bureau’s multi-terabyte
             cartographic and other data files required to begin the Census and Census
             Coverage Measurement operations at the RCCs/PRAO and LCOs. See Section
             J – Workload Performance for this sizing and workload data.

             C.5.2.1.4.4.   The OCE provided for the RCCs/PRAO and LCOs shall provide
             Internet connectivity and access.

        C.5.2.1.5     Printing Requirements

             C.5.2.1.5.1.   The FDCA contractor shall provide and integrate in the RCCs,
             PRAO and LCOs the printers necessary to handle the volume and schedule of
             print operations as defined in Section J – Office Computing Environment.

             C.5.2.1.5.2.    The FDCA contractor shall provide for the RCC/PRAO
             infrastructure, printing equipment, and software necessary to produce the wide
             variety of small and large scale maps necessary to carry out geographic
             programs and field operations, such as those to update political, statistical, and
             administrative boundaries used to tabulate the census results. Examples of
             printer requirements from Census 2000 may be found in Section J – Office
             Computing Environment.

             C.5.2.1.5.3.    Those printers needed to support large operations with large
             printing jobs provided by the FDCA contractor for the RCC, PRAO and LCO
             environments shall be designed such that they will not require paper added
             more frequently than once an hour during heavy printing operations at these
             locations. See section J – Workload Performance.


                                     Appendix A-2 Page 30 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.1.5.4.    The FDCA contractor shall provide for the ability to resume
             printing at the particular point where a job was interrupted.

             C.5.2.1.5.5.     All printing capabilities of the OCE must include the
             functionality of printing specific information based on selected geographic or
             other criteria (e.g., specify to print an individual questionnaire label, print all
             questionnaire labels for an assignment area, or print all questionnaire labels for
             an LCO, etc.). The FDCA contractor shall work jointly with the Government
             after contract award and prior to their development of a detailed OCE design to
             develop and deliver the full needs related to this requirement.

             C.5.2.1.5.6.  The FDCA contractor shall enable the RCCs and the PRAO
             OCE the capability of printing e-size (36 inches X 42 inches) color maps from
             data and/or map files located remotely at Census HQ or NPC.

             C.5.2.1.5.7.      The FDCA contractor shall enable the RCCs, PRAO and LCOs'
             OCE with the capability to print graphic (e.g. maps, etc.) and text (e.g. address
             lists, reports, etc.) in black and white on 8.5 inch by 11 inch paper, and 8.5 inch
             by 14 inch paper, and 11 inch by 17 inch paper. See Section J – Office
             Computing Environment for printing load requirements.

             C.5.2.1.5.8.    The FDCA contractor shall enable the LCOs' OCE with the
             capability to print self-adhesive address labels in black and white in a variety of
             standard label sizes.

             C.5.2.1.5.9.   The FDCA contractor shall provide installation, maintenance,
             and preventative maintenance of the equipment.

        C.5.2.1.6     FDCA Operations Management Reporting Requirements

        A large part of the productivity in the field is dependent upon the RCC, PRAO and
        LCO management’s ability to track all aspects of work in the field. This is
        accommodated through the “Management Reporting” capability that tracks
        completed and outstanding work within all operations, including asset tracking,
        field worker transmissions, box shipments of paper materials, etc. Access to data
        are restricted to the “jurisdiction” of the organization unit requiring access. With an
        effort as large as the census, the RCCs, PRAO and LCOs use exception reports as a
        critical tool in their management approach to ensure completion of work on time
        and within budget. Managers will still require cumulative reports reflecting
        completed work, but they accomplish much of their day-to-day tracking by
        reviewing exception reports that show information in total and by staff
        organization, such as: 1) amount of incomplete work; 2) missing transmissions; 3)
        performance issues, including production and quality; and 4) work yet shipped or
        received. Headquarters management relies heavily on the cumulative daily cost
        and progress reports to understand the status of the entire program.


                                     Appendix A-2 Page 31 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.1.6.1.   The FDCA contractor shall provide the HQ, RCC, PRAO and
             LCO an OCE with a management reporting capability on the FDCA operations
             by HQ, RCC/PRAO, LCO, Field Office Supervisor District (FOSD), Crew
             Leader District (CLD), and Enumerator. (See Section J – OCE Reporting for
             an example reports list).

             C.5.2.1.6.2.   The HQ, RCC, PRAO and LCO OCE's management reporting
             capability shall produce each report in near real-time and shall not require
             batch processing to accomplish any reporting.

             C.5.2.1.6.3.   The HQ, RCC, PRAO and LCO OCE's management reporting
             shall provide an ad-hoc reporting capability.

             C.5.2.1.6.4.   The HQ, RCC, PRAO and LCO OCE's management reporting
             shall provide daily reports on the previous day's operation.

                        The FDCA contractor shall provide the capability for HQ,
             C.5.2.1.6.5.
             RCCs, PRAO and LCOs to archive any and all reports generated.

             C.5.2.1.6.6.    The HQ, RCC, PRAO and LCO OCE's management reporting
             shall be capable of generating, displaying, and printing reports which contain
             textual, graphic, and cartographic elements.

             C.5.2.1.6.7.   The HQ, RCC, PRAO and LCO OCE's management reporting
             shall support reports which contain sorts, filters, subtotals, and totals.

             C.5.2.1.6.8.    The HQ, RCC, PRAO and LCO OCE's management reporting
             shall provide daily, weekly, monthly, and cumulative summary reports on the
             program goals and the progress of those goals against established benchmarks
             with comparisons between offices (i.e., HQ, RCC, PRAO and LCO scorecards
             utilizing percentages) for all MCE and paper-based operations.

             C.5.2.1.6.9.   The HQ, RCC, PRAO and LCO OCE's management reporting
             shall support the report types such as those highlighted in Section J – OCE
             Reporting under Management Reporting Types.

                         The OCE of the RCCs, PRAO and LCOs shall interface with the
             C.5.2.1.6.10.
             Census HQ Cost and Progress (C&P) System to provide operational status and
             cost data.

             C.5.2.1.6.11.   The OCE of the RCCs, PRAO and LCOs shall interface with the
             Census "Staffing Authorization" application to obtain data values from the
             Staffing Authorization which shall be combined with cost and progress data in
             reports that shall be provided to the LCOs, RCCs, PRAO and FLD HQ for
             control and tracking of census operations.


                                     Appendix A-2 Page 32 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    C.5.2.2       Operational Control (OC) Function Requirements

    Automation of the Operations Control (OC) function provides an automated control
    and information capability to manage census and census coverage measurement field
    operations. This function is a critical link in the management process as it provides
    monitoring, tracking, management, control, and reporting on both the progress of each
    field data collection operation in its entirety, as well as on the progress of work units
    within each of these operations.

    The census and census coverage measurement operations are conducted throughout
    urban, rural and remote areas of the United States and Puerto Rico and utilize both
    paper and electronic methods for collecting information about people who reside in
    both regular housing units and other types of living quarters. The technical design of
    the system automating the OC function must therefore accommodate widely varying
    data aggregations (e.g., the extreme differences in population density from urban to
    rural America will mean that a census block aggregation of address data may contain
    thousands of housing unit locations in urban settings, and only a handful in rural
    setting). The technical design of the system automating the OC function must also be
    able to accommodate other unique differences such as in Puerto Rico the standard for
    the address information adds a subdivision component in addition to the street name,
    house number, post office name, and ZIP Code.

        C.5.2.2.1     Setup Requirements for the System Automating the OC Function

              C.5.2.2.1.1.   The FDCA contractor’s solution for automating the OC function
              shall be designed such that it can easily and quickly be updated to provide
              added modules/databases supporting newly created census operations.

              C.5.2.2.1.2.   The FDCA contractor’s solution for automating the OC function
              shall provide a capability to control when the LCOs and RCCs/PRAO can
              access the workload/universe in the OCE associated with a particular Census
              Operation.

              C.5.2.2.1.3.     The FDCA contractor’s solution for automating the OC function
              shall interface with specified systems (See Section J - Interfaces for example
              list of interfacing systems) as required to establish the necessary Universe of
              data the OCE needs to effectively monitor and manage Census and Census
              Coverage Measurement Operations under scope of the FDCA contract.

              C.5.2.2.1.4.    The FDCA contractor’s solution for automating the OC function
              for the RCCs, PRAO and LCOs shall interface with the Decennial Response
              Integration System (DRIS) to receive the universe input files required for each
              Census operation. Note - see Section J – Interfaces for a list of external
              interfacing systems.



                                     Appendix A-2 Page 33 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.1.5.   For each Census and Census Coverage Measurement Operation
             under scope of FDCA, the FDCA contractor’s solution for automating the OC
             function shall store all the data necessary, including associated addresses from
             processing the Universe files and status information collected and related,
             necessary for Census staff to use the OCE to monitor and manage that
             operation.

             C.5.2.2.1.6.    The FDCA contractor shall provide an automatic "Case History"
             process, and an implementation of that process, which shall record and
             maintain for each case, all actions (e.g., who, date, time, in or on what system,
             where the case is in the Census production process from inception to final
             disposition on DRIS, and type of action performed) associated with that case
             (e.g., assigned to by and who, reassigned by and to who, who and when each
             attempt made to contact and/or input data from the respondent, who and when
             completed and transmitted, etc.). ***

             C.5.2.2.1.7.   The Case History data shall be accessible from the FDCA
             contractor’s solution for automating both the OC function and the MCE for
             those with the appropriate access privileges for that case.

        C.5.2.2.2     Functionality associated with data to be delivered to the MCE

             C.5.2.2.2.1.    The address lists provided to the MCE shall be sequenced to
             minimize the distance traveled by the enumerator to enumerate all the locations
             in each assignment. The Government may work with the contractor post award
             to refine these rules.

             C.5.2.2.2.2.   Address lists delivered to the MCE shall include sufficient
             neighboring addresses to the enumerator’s assigned addresses to assist them
             with issues such as orientation, address mix-ups, etc.

             C.5.2.2.2.3.   The FDCA contractor shall provide an automated process so that
             the surnames (for addresses of mail returns in update leave areas and in multi-
             units of mail-out/mail-back areas) from DRIS, which are specific to a field
             staff's incomplete assignment(s) are transmitted to their MCE on a daily basis.

             C.5.2.2.2.4.   The FDCA contractor shall provide an automated process to
             make telephone numbers associated with the census coverage measurement
             sample that are supplied on the mail return respondent forms (processed by
             DRIS) available to the census coverage measurement staff in the RCC/PRAO
             for the phone phase of the Census Coverage Measurement – Person Interview
             operation. The FDCA contractor shall work with the DRIS contractor to
             provide, at a minimum, a daily update to the census coverage measurement
             sample address information.



                                     Appendix A-2 Page 34 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.2.5.     The FDCA contractor shall provide an automated process so that
             all the original interview data are provided to the MCE for reinterview
             assignments.

             C.5.2.2.2.6.   The FDCA contractor shall provide an automated process so that
             the telephone number collected during Census operations is provided to the
             MCE for each unit in CM case assignments.

             C.5.2.2.2.7.     The FDCA contractor shall provide a weekly process, and an
             implementation of that process, which shall: generate a weekly summary of the
             Time and Expense data submitted by a field staff's MCE, send that summary to
             the field staff's MCE, and allow them to review/retain/delete that summary
             information on their MCE.

        C.5.2.2.3 Functionality associated with data to be delivered to the System
        supporting the OC Function from the MCE

             C.5.2.2.3.1.   The FDCA contractor shall provide a mechanism, which shall
             alert a Crew Leader on their MCE, that their field staff has transmitted work
             pending their review and approval.

             C.5.2.2.3.2.     The FDCA contractor’s solution for automating the OC function
             shall provide a capability, which automatically reviews assignments transmitted
             by field staff for possible issues requiring Crew Leader review, including
             alerting the Crew Leader on their MCE to review these specific assignments
             before routing the data for any further processing.

             C.5.2.2.3.3.    The FDCA contractor’s solution shall allow RCC, PRAO, LCO,
             FOS, and Crew Leaders to enable/disable the ability of a field staff's MCE to
             transmit its data. **

             C.5.2.2.3.4. The FDCA contractor shall provide the FDCA contractor’s solution
             for automating the OC function for the LCOs with the capability to send
             acknowledgements, assignments (Address Lists, Maps, T&A Forms, Expense
             Forms), case or assignment updates based on Late Mail Returns, alerts, and
             messages, and reports to the MCE of the field staff.

             C.5.2.2.3.5. The FDCA contractor’s solution for automating the OC function
             shall provide the capability to accept a transmitted case regardless of its status
             during certain periods during the operation. Government will provide the
             detailed requirements for this after contract award.

             C.5.2.2.3.6. The FDCA contractor’s solution for automating the OC function
             shall provide the capability to reject a transmitted case during certain times
             during the operation. Government will provide the detailed requirements for
             this after contract award.

                                     Appendix A-2 Page 35 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.2.2.4 Decennial Applicant Personnel Payroll System (DAPPS) Interface
        Requirements

        The Decennial Applicant, Personnel and Payroll System (DAPPS) provides an
        administrative management system for the 2010 Census. DAPPS supports the
        processes necessary to recruit, clear, qualify, appoint, and pay the temporary
        employees hired to conduct the decennial census. This includes tracking the status
        of every applicant, and providing the reporting, information processing, and
        internal and external interfaces necessary to carry out these administrative
        activities. The DAPPS is GFE, but will also provide other systems developed
        under FDCA with necessary information as described by the interface requirements
        with FDCA systems described below.

             C.5.2.2.4.1.   The FDCA contractor shall recommend for government
             approval, procure, deliver, install, configure, integrate, administer, maintain,
             and dispose, the appropriate hardware, OS software, and telecommunication
             required to support the DAPPS system as specified in the Census Bureau
             Requirements for DAPPS Infrastructure for the 2010 Census (see Section J -
             Interfaces).

             C.5.2.2.4.2.    The FDCA contractor’s solution for automating the OCE’s OC
             function provided by the FDCA contractor shall provide a mechanism to
             interface to the Decennial Applicant Personnel Payroll System (DAPPS) which
             shall provide:

                     The ability to determine the specific position type for each employee
                      (i.e., FOS, CL, Enumerator);

                     The ability to review production & expenses data on any field staff (i.e.,
                      determine the hours worked, miles charged, expenses charged, and other
                      information on each employee, regardless of whether they are still
                      employed by Census or not).

             C.5.2.2.4.3.    The FDCA contractor’s solution for automating the OCE
             function provided by the FDCA contractor shall provide a mechanism to
             interface to the Decennial Applicant Personnel Payroll System (DAPPS) which
             shall provide:

                     The ability to verify that a person has been cleared for employment (i.e.,
                      flagged as eligible in the DAPPS database) prior to their being issued
                      equipment, assigned work, and assigned a transmission account;

                     The ability to simultaneously communicate termination of employment
                      to all systems and databases delivered by the FDCA contractor,
                      updating their status and revoking access privileges.


                                     Appendix A-2 Page 36 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.4.4.     The FDCA contractor’s solution for automating the OC function
             shall provide the capability to interface with the Applicant Geocoding System
             to facilitate the assignment of work to field staff near where they live.

        C.5.2.2.5     Universe Requirements

        The Census Bureau maintains at its headquarters a “universe” of data for tracking
        the enumeration and processing status of all addresses included in the decennial
        census. This universe, or a subset of it, is required for the initial set up of all FDCA
        operations. The universe data elements includes tracking specific operations to
        which each address is assigned, as well as attributes or outcomes of operations,
        including occupancy status, population counts, etc. The FDCA contractor will
        work with all stakeholders, including census staff and other contractors to
        determine the best design for providing and maintaining this universe of data for
        the RCCs, PRAO and LCOs.

             C.5.2.2.5.1.    The FDCA contractor’s solution for automating the OC function
             shall provide a mechanism to utilize and maintain the living quarter universe
             (e.g., browse, search, filter, sort, display, request add, request delete, request
             update). See Section J – Universe for the universe data element description).

        C.5.2.2.6 STREET INDEX Database Interface Requirements (used for manual
        geo-coding of applicants)

        The Census Bureau maintains an index of geographic information related to streets
        and addresses throughout the United States, including attributes such as the state,
        county, census tract, census block associated with an address range (e.g., 101 – 301
        Main St.). In Census 2000, these data were made available to the RCC/PRAO and
        LCO staff via a graphical user interface to the Census Bureau’s Geography
        Division’s Street Index data files. For the 2010 census, the RCCs, PRAO and
        LCOs still require the capability to determine the location of where each census
        applicant resides, including the associated census geographic codes. The
        RCCs/PRAO/LCOs use these codes to determine the specific assignments for
        which the applicants should be considered, including the associated pay rates. The
        FDCA contractor will work with all stakeholders, including census staff and other
        contractors, as necessary and appropriate, to design the most effective solution
        possible to provide this capability.

             C.5.2.2.6.1. The FDCA contractor’s solution for automating the OC function
             shall provide a mechanism to browse, search, filter, sort and display the data
             elements from the Street Index database as specified in Section J - Universe.

        C.5.2.2.7     Assignment Preparation Requirements

        The creation of assignments will be performed by NON-FDCA systems. For
        example, for Address Canvassing, the Census Bureau will define geographic areas

                                     Appendix A-2 Page 37 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        (groups of one or more census blocks) for assignment to individual enumerators.
        For other census operations, specific cases within individual blocks, grouping
        adjacent blocks or cases together to reach a specific assignment size will be
        designated. The definition of these assignments is done outside of the systems
        provided by FDCA. These assignment data/files will be delivered for input into the
        FDCA contractor’s solution for automating the OC function. This preparation of
        assignments, for delivery to the field for paper-based operations, consists of a
        significant amount of printing, sorting, and grouping of paper into address register
        binders and map pouches. The workloads related to this printing requirement can
        be found in Section J – Office Computing Environment. Although the creation and
        preparation of electronic assignments does not involve this massive printing effort,
        similar sorting and grouping of information is required in order to make
        assignments to field staff.

             C.5.2.2.7.1.    The FDCA contractor’s solution for automating the OC function
             shall provide the capability to access/retrieve/search/sort/filter/display all
             addresses and related status information by operation.

             C.5.2.2.7.2.    The FDCA contractor’s solution for automating the OC function
             shall provide the capability to add and/or remove cases from assignments that
             have been made, regardless of whether the assignment has been received by the
             field staff's MCE.

             C.5.2.2.7.3.   The FDCA contractor’s solution for automating the OC function
             for the LCO shall have the capability to assemble, package, organize, and
             uniquely identify for the appropriate MCE electronic work assignments
             (including required electronic Address Lists and Maps) for transmission to field
             staff MCEs.

             C.5.2.2.7.4.     The FDCA contractor’s solution for automating the OC function
             shall provide the capability to access, display, and create a label showing the
             assignment and questionnaire control information, as provided on the input
             delivery file, including a barcode representation of a specified component of the
             assignment identification information for each paper-based operation.

             C.5.2.2.7.5.    The FDCA contractor shall provide any and all barcodes for
             paper document control according to the format provided by the Government
             after contract award.

        C.5.2.2.8     Make Assignments Functionality

        The creation of the assignments (geographic areas or lists of cases) is performed
        outside of the FDCA contract. The Make Assignment Functionality involves
        associating these individual operational assignments with the specific field staff
        responsible for performing the work. Initially, this association is done for each
        FOS and the CLs who report to them. Once assigned to the CL level, the work will

                                     Appendix A-2 Page 38 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        be assigned at the enumerator level.

        For Census Coverage Measurement, the Make Assignment Functionality must first
        determine where a field worker worked during the Census operations before
        assigning them work in the CM operations. This functionality ensures the
        independence as described in Section C.2 Census and Census Coverage
        Measurement Operations.

        This functionality, for both Census and CM provides the capability to reassign
        work from one field worker to another and to assign the same work to multiple
        field workers, as required to implement special enumeration procedures.

             C.5.2.2.8.1. The FDCA contractor’s solution for automating the OC function for
             the LCOs shall provide the capability to adjust initial Field Office Supervisor
             District (FOSD) and Crew Leader District (CLD) assignments as required.

             C.5.2.2.8.2.  The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to assign an individual person to a
             FOSD and/or CLD.

             C.5.2.2.8.3.     The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to change/modify work assignments
             for field staff regardless if they are pending delivery or have already been
             transmitted.

             C.5.2.2.8.4.  The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to assign and reassign work to and
             between employees within and across FOS, CL, and LCO Districts with
             appropriate domain controls including work previously conducted, completed
             and checked-out/transmitted from the LCO.

             C.5.2.2.8.5.  The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to assign the same work to multiple
             employees simultaneously (e.g., the "Blitz" enumeration procedures require
             sending multiple enumerators with the same assignment to a specific location to
             collect NRFU interviews near the end of the Operation) with the ability to
             toggle/schedule this capability. ***

             C.5.2.2.8.6.   The FDCA contractor’s solution for automating the OC function
             for the LCOs shall have the capability to access/retrieve/display information
             regarding previous census work history by an employee (e.g., operations they
             worked, geographic area they were assigned, etc.).




                                     Appendix A-2 Page 39 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.2.2.9     Assignment Control & Tracking Functionality

        Assignment control and tracking provides the functionality required to inform
        RCC/PRAO and LCO management about the overall status of address update and
        data collection operations, regardless of whether conducted using mobile
        computing equipment or paper-based. This component provides the capability to
        track assignments for completeness and accuracy by incorporating quality control
        measures and reporting features. LCO and/or RCC/PRAO management must have
        a mechanism to know the status of each assignment for an operation, including a
        process to quickly resolve multiple submissions of the same assignment or case, as
        well as tracking assignments through all stages of each operation, such as: to be
        assigned, assigned, awaiting quality control, passed/failed quality control, assigned
        for rework, approved by crew leader, received in LCO, shipped to processing, etc.
        Each assignment for an operation will be given a unique identification number for
        tracking purposes. The FDCA solution will track the status and stage of operation
        for each assignment, including providing the necessary summary and/or exception
        reports for management purposes as detailed below:

             C.5.2.2.9.1.     The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to accept cases regardless of their
             status (e.g., accept a case which has its date/time-based Final Attempt Override
             triggered).

             C.5.2.2.9.2.  The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to review the status of an employee's
             work assignments, both historical and current.

             C.5.2.2.9.3.   The FDCA contractor’s solution for automating the OC function
             shall provide the capability to track the Census and Census Coverage
             Measurement phases (e.g. telephone, personal visit, non-response conversion)
             of operations by case or geographic area.

             C.5.2.2.9.4.   The FDCA contractor’s solution for automating the OC function
             shall track operational progress within each Census operation and provide
             alerts for when the subsequent operations can begin based on trigger criteria to
             be specified by the Government after contract award.

             C.5.2.2.9.5.    The FDCA contractor’s solution for automating the OC function
             shall provide the capability for LCO staff to effectively monitor, manage, and
             resolve when multiple assignment files transmitted by one or more field staff
             exist for the same assignment or case. ***

             C.5.2.2.9.6.    The FDCA contractor shall provide the solution for automating
             the OC function for the LCOs, and the FOS & Crew Leaders MCE, with the
             capability to review their field staff's transmitted work prior to that work being
             released for further processing.

                                     Appendix A-2 Page 40 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.9.7.    The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to check paper assignments in from
             the field for validation prior to release for further processing.

             C.5.2.2.9.8.   The FDCA contractor’s solution for automating the OC function
             shall provide the capability to reassign and restart cases identified by LCO
             staff.

             C.5.2.2.9.9.   The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to review completed assignments
             submitted by the field staff’s MCE.

             C.5.2.2.9.10. The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to edit the notes field associated with
             a case.

             C.5.2.2.9.11. The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to check work out to DRIS for further
             processing.

             C.5.2.2.9.12.   The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to check paper-based operations work
             (e.g., address registers, maps, questionnaires, etc.) out to field operations for
             work, and back in from field operations upon completion.

             C.5.2.2.9.13. The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to capture and record status
             information on the progress of paper-based operations (e.g., when work is
             checked-in, when work is checked-out, etc.).

             C.5.2.2.9.14.  The FDCA contractor shall work with the Census Bureau and
             the DRIS contractor to develop their LCO check-out solution for paper-based
             operations work so that it accommodates and integrates with the DRIS check-in
             processes at the DCs.

             C.5.2.2.9.15. The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to check-out and check-in paper-
             based operations work utilizing a combination of hands-free (i.e., like used in
             grocery checkouts) barcode scanning and keyboard entry.

             C.5.2.2.9.16.   The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability for the LCO, RCC, PRAO and HQ to
             track the receipt of work at the DCs.




                                     Appendix A-2 Page 41 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.9.17. The FDCA contractor’s solution for automating the OC function
             for the RCCs, PRAO and LCOs shall interface with the DRIS system to send
             completed work from the field staff for further Census processing.

             C.5.2.2.9.18.  The FDCA contractor’s solution for automating the OC function
             shall provide the capability to automatically determine and alert the OC user of
             the need for Closeout and to signal the initiation of the closeout phase to the
             MCE.

        C.5.2.2.10 Reinterview/Quality Control

        The reinterview/quality control component of the field data collection process
        requires independence from the original census and census coverage measurement
        operations in both a logical and physical aspect. The Census Bureau hires a
        separate staff and isolates them in terms of location within the RCC, PRAO and
        LCO to ensure the integrity of the reinterview work. The Census Bureau maintains
        a logical separation of reinterview/quality control data from the original census and
        census coverage measurement data via access controls to the system(s). In Census
        2000, we accomplished this separation by creating the reinterview component for
        each census operation as a separate and distinct operation.

        The Matching Review and Coding System (MaRCS), a Government GFE will
        create the information necessary to determine reinterview assignments. The FDCA
        system must make the data available to the field staff for reinterviews. Once the
        reinterviews are completed, the FDCA system must provide the capability to return
        the data collected for these assignments to the MaRCS for further processing. That
        is, the FDCA control system that manages the reinterview work must provide an
        interface to the MaRCS.

        The assignment, control and tracking functionality required for reinterview
        activities is entirely consistent with that required for regular census operations.
        Therefore, the government requires that the design of the reinterview component
        adhere to the reinterview operational workflow and integrate into or be very similar
        to the census and census coverage measurement control system design while
        maintaining the independence through appropriate means.

             C.5.2.2.10.1. The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to alert LCO staff of cases requiring
             review based on their status code.

             C.5.2.2.10.2.  The FDCA contractor’s solution for automating the OC function
             for the LCOs shall provide the capability to track the monitoring and
             observations of field staff by their supervisors.




                                     Appendix A-2 Page 42 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



             C.5.2.2.10.3. The FDCA contractor’s solution for automating the OC function
             for the RCCs, PRAO and LCOs shall interface with the Census MARCS
             system to enable the reinterview universe identification.

             C.5.2.2.10.4.  The FDCA contractor’s solution for automating the OC function
             for the RCCs, PRAO and LCOs shall interface with the Census MARCS
             system to identify cases for which the OC function will make the original
             interview data available to the field staff's MCE for the reinterview phase of
             operations.

        C.5.2.2.11 Electronic Collection of Respondent Data

        This component refers to the electronic collection of response data from the office
        environment. Reinterview operations generally allow for data collection activities
        to take place over the telephone, prior to conducting personal visits. The Census
        Bureau conducts the phone phase to gather as much information as possible for
        those cases with a valid telephone number, thereby reducing the amount of time
        and cost in comparison to conducting a personal visit. The Census Bureau plans to
        assign all cases that remain incomplete following the phone phase, including those
        that do not have a telephone number to the personal visit phase. The OCE
        developed by the FDCA contractor must support the ability to conduct telephone
        interviews. The government’s expectation is that, if the FDCA contractor chooses
        to use the MCE to satisfy this telephone interview requirement, that the MCE’s
        transmission step will be bypassed and utilize instead the high-speed
        communications infrastructures of the RCCs, PRAO and LCOs.

             C.5.2.2.11.1.      The FDCA contractor’s solution for automating the OC
             function for the RCCs/PRAO and LCOs shall provide the capability for
             conducting interviews and collecting respondent data over the telephone for the
             Census Coverage Measurement – Person Interview operation and for the
             reinterview phase of NRFU from the RCCs/PRAO and LCOs respectively.

             C.5.2.2.11.2.   For respondent data collected over the telephone from the
             RCCs/PRAO and the LCOs, the completed case data shall be sent to its next
             destination in the production process immediately upon interview completion
             using the communications infrastructure of the RCC/PRAO or LCO.

        C.5.2.2.12 Transmission/Shipping Requirements for completed work

        Once the field staff completes the paper and electronic assignments, there are two
        methods for sending in the work: electronic transmission and paper courier. The
        FDCA contractor provides for specific capabilities within each method. The
        transmission capability required by the mobile field worker is described in Section
        C.5.1.8. This section addresses the corresponding functionality required within the
        office to enable and disable field worker transmissions.


                                     Appendix A-2 Page 43 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        For courier shipment of paper documents between the LCOs and field staff, the
        Census Bureau anticipates using Crew Leader assistants and a contracted shipping
        vendor. The Census Bureau requires that the FDCA contractor provide a seamless
        interface for tracking boxes and their contents from origination to destination points
        in conjunction with any contracted shipping vendor.

              C.5.2.2.12.1.       The FDCA contractor’s solution for automating the OC
              function for the LCOs shall provide the capability to track, review the status,
              generate notifications based on user specified criteria regarding the status of
              transmissions.

              C.5.2.2.12.2.  The FDCA contractor’s solution for automating the OC function
              for the LCOs shall provide the capability to enable and/or disable field staff
              transmission capability from the MCE.

              C.5.2.2.12.3.  The FDCA contractor’s solution for automating the OC function
              for the LCOs shall provide the capability to interface with the selected contract
              shipping vendors for LCO, RCC and PRAO staff to electronically track
              shipments from the LCO/RCC/PRAO to the DC/HQ. The government will
              provide the selected shipping vendor post contract award.

              C.5.2.2.12.4. The FDCA contractor’s solution for automating the OC function
              for the LCOs shall provide the capability to electronically track the contents
              (LDS) of each shipped package and the associated contract-shipping vendor
              tracking number.

    C.5.2.3       Other Management Information Systems

        C.5.2.3.1. In addition to the functionality of the FDCA contractor’s solution for
        automating the OC function, the FDCA contractor shall design, create, deliver,
        maintain, and support for the OCE other functionality, either within the OC
        function’s system or other contractor developed management information system,
        as required (e.g., asset tracking, etc.).

    C.5.2.4       Evaluations and Experiments [FOR INFORMATION ONLY]

    Evaluations of the 2010 Census primarily include research that will be done using
    results from completed census operations and processes. Using metrics from census
    operations and processes, and data collected from follow-up surveys, evaluations
    analyze and measure the impact of new initiatives on data quality and the core census
    processes. Evaluation goals are to:
         Eliminate or reduce the impact of apparent sources of error in future data
            collections;
         Assess alternatives in collecting, processing, or presenting data in future data
            collections;


                                     Appendix A-2 Page 44 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



            Determine appropriate caveats or other information about the data that should
             be presented to data users.

    Experiments are national surveys that must occur during a decennial census because
    the census environment provides the best conditions to learn about the value of new or
    different methods or technology. The Census 2000 experiments involved studies on
    topics such as differently designed questionnaires, use of various types of
    administrative records, and alternative response modes.

    The Census Bureau conducts a research and experimental program during each
    decennial census to test new methodologies and/or procedures. This provides the
    Census Bureau with the opportunity to evaluate the validity of these methods and
    procedures in a true census environment. The research and experimental program may
    include or involve components of the FDCA contract. The specific requirements of the
    research and experimental program for the FDCA contract, including data outputs, will
    be determined after contract award. These requirements may involve telephone
    assistance, telephone fulfillment, the telephone inbound and outbound operation,
    Internet self-response, Internet assistance, the telephone agent application, IVR
    assistance, and the Customer Satisfaction Survey.

    An example of an evaluation and experiment program from the Census 2000 Testing,
    Experimentation, and Evaluation Program can be found at the Census Bureau’s
    Internet site located at http://www.census.gov/pred/www/.

        C.5.2.4.1. Based on Government input after contract award, the FDCA contractor
        shall determine, document, and record the exact type of data needed for the 2008
        Dress Rehearsal and 2010 Census evaluations. The Government will provide pre-
        defined samples of census form IDs that will meet the needs of the evaluation
        program.

        C.5.2.4.2. The FDCA contractor shall make all FDCA data available to the
        Government as required for evaluations of the 2008 Dress Rehearsal and the 2010
        Census. The FDCA contractor shall work with the Government after contract
        award to determine the type of data needed to support evaluations and the transfer
        mechanism. This data may involve any operation and process performed or
        supported by the FDCA, including data on:
            Telephone network volumes and disposition, IVR assistance, census form
               and language guide fulfillment, telephone agent assistance, telephone agent
               response capture, outbound telephone enumeration activities, telephone
               agent application, and the Customer Satisfaction Survey
            Internet self-response, and Internet assistance
            A pre-defined sample of response data for all modes
            A pre-defined sample of images of paper census forms



                                     Appendix A-2 Page 45 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



                 Metrics related to paper census form check-in, electronic response receipts,
                  processing (including non-ID), and paper data capture

        C.5.2.4.3. The FDCA contractor shall work with the Government after contract
        award to determine and document the scope of experiment-related requirements as
        it relates to the operations and processes performed or supported by FDCA.

        C.5.2.4.4. The FDCA contractor shall provide all response data for all modes,
        which includes experimental data items not considered part of the “standardized
        and organized” data. The mechanism for delivery of this data shall be determined
        after contract award.

        C.5.2.4.5. The FDCA contractor shall ensure that the applicable operations and
        processes performed or supported by FDCA for the 2010 Census are also provided
        for experimental census forms to be used during the 2010 Census.

    C.5.2.5       Other Office Requirements

    General office automation requirements, outside of the control of field operations,
    encompass the use of faxes, copiers, cell phones, laptops for managers, etc. and
    associated support supplies. This component provides for the capability to integrate
    these components into the office-computing environment.

        C.5.2.5.1.     The FDCA contractor shall procure, deliver, maintain, and support for
        Census HQ, the same E-size printers (hardware) they provide for the RCCs/PRAO
        to satisfy their E-size printing requirements.

        C.5.2.5.2.    The FDCA contractor shall provide within the Census HQ the
        capability to print on-site E-size (36inches by 42 inches) color maps from data
        and/or map files located at Census HQ or NPC.

        C.5.2.5.3.    The FDCA contractor shall provide within the NPC the capability to
        print on-site E-size (36inches by 42 inches) color maps from data and/or map files
        located remotely at Census HQ or NPC.

        C.5.2.5.4.     The FDCA contractor shall procure, deliver, maintain, and support for
        the NPC the same E-size printers (hardware) they provide for the RCCs/PRAO to
        satisfy their E-size printing requirements.

        C.5.2.5.5. The FDCA contractor shall support the hardware and peripherals for
        Geography Programs at the RCC/PRAO (i.e., install, integrate, support, and de-
        install).

        C.5.2.5.6.   The FDCA contractor shall provide one multi media graphics
        workstation for each RCC including the Puerto Rico Area Office.
        (Specifications/capabilities required will be provided post contract award.)

                                     Appendix A-2 Page 46 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    C.5.2.6      Office Operations Performance Requirements

        C.5.2.6.1. The FDCA contractor shall provide a Mean Time Between Failure
        (MTBF) calculation for all components used to provide the OCE solution.

        C.5.2.6.2. The FDCA contractor shall provide a Mean Time to Repair (MTTR) (e.g.
        time from problem report to restore unit to exact function just prior to the failure) of
        24 hours for all components used to provide the OCE solution.

C.5.3   FDCA TELECOMMUNICATIONS

Telecommunications, both voice and data, are vital to an effective census. In this
requirement area the FDCA contractor will provide, manage, operate, and maintain
telecommunications functionality as required (i.e., LAN, WAN, ISP, Leased Line, Land
Line, Wireless etc. for both voice and data) for the FDCA program to operate seamlessly
as a single integrated system interfacing the:
     Field staff’s mobile computing environments
     FDCA Field Offices (RCCs, Puerto Rico Area Office, and LCOs)
     Other centers/systems (see Section J - Interfaces for a matrix of all interfacing
        systems):
         The National Processing Center (NPC), which is primarily responsible for
            assembly and distribution of kits that contain materials needed to perform field
            work, and also the captures of map updates
         The DRIS Data Centers (DC) that optically scan mailed-in census
            questionnaires and consolidate data collected in the field
         Headquarters Data Processing (HQDP), which contains the computing
            resources necessary to analyze census data and run enterprise applications.
         Other external systems (see Section J - Interfaces)

    C.5.3.1      General Requirements

    The General Requirements cover needs common to the entire spectrum operations for
    this section.

        C.5.3.1.1.     The FDCA contractor shall provide and be responsible for all voice
        and data telecommunications (e.g., LAN cabling, T1 acquisition and interface and
        installation, long distance service, etc.) and voice and data telecommunication
        devices (e.g., telephones, modems, routers, PBXs, etc.) required by the RCC,
        PRAO, LCO, and the field staff’s MCE for their operations.

        C.5.3.1.2.      The FDCA contractor shall fully integrate all voice and data
        deliverables.

    C.5.3.2      Voice Requirements



                                     Appendix A-2 Page 47 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.3.2.1.  The voice communications capability the FDCA contractor provides
        for the RCCs/PRAO and LCOs shall be capable of sending and receiving calls.

        C.5.3.2.2.   The voice communications capability the FDCA contractor provides
        for the RCCs/PRAO and LCOs shall provide: auto-attendant, special messages
        handling, hands free operation, call waiting, queuing of calls, group transfers,
        mailboxes, and other special features for specified users as required.

        C.5.3.2.3.   The voice communications capability the FDCA contractor designs
        and implements for the RCCs/PRAO and LCOs shall provide sufficient high-
        quality speakerphones for each RCC/LCO to support their conference call needs.

        C.5.3.2.4. The voice communications capability the FDCA contractor designs and
        implements for the RCCs/PRAO and LCOs shall include sufficient telephone
        instruments and lines to support the peak staffing and call volume levels of each
        office. See Section J – Workload Performance.

        C.5.3.2.5. The voice communications capability the FDCA contractor designs
        and implements for the RCCs/PRAO and LCOs shall provide local, long distance,
        and 800 number toll-free services.

        C.5.3.2.6.   The voice communications capability the FDCA contractor designs
        and implements for the FDCA contract shall comply with requirements of Section
        508 of the Federal Rehabilitation Act as specifically required for each RCC, PRAO
        and LCO throughout their operational life.

        C.5.3.2.7.  After contract award the FDCA contractor shall work with the
        government to develop and implement requirements for nation-wide toll free 800
        numbers, IVR, and call routing based on the incoming call's location capabilities.

        C.5.3.2.8.   After contract award the FDCA contractor shall work with the
        government to develop and implement requirements for the capability to modify
        IVR and 800 number (without IVR support) routing rules for call termination (e.g.,
        recruiting 800 line will terminate in the RCCs until the LCOs open, etc.).

        C.5.3.2.9.   After contract award the FDCA contractor shall work with the
        government to develop and implement requirements for English and Spanish
        languages in the IVR systems.

        C.5.3.2.10.    After contract award the FDCA contractor shall work with the
        government to develop and implement requirements for special needs capabilities
        for any toll free numbers and IVR systems to accommodate the anticipated special
        needs traffic (i.e., voice communications devices to accommodate deaf and hard of
        hearing individuals).



                                     Appendix A-2 Page 48 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    C.5.3.3      Data Requirements

        C.5.3.3.1.   The FDCA contractor shall provide an integrated wide area data
        communications capability (e.g., WAN, etc.) between Census HQ, NPC, DRIS
        DCs, ROs, RCCs, PRAO, LCOs, MCEs, and the Internet as required to meet the
        operational needs of those offices and environments to support FDCA while
        meeting Census Bureau network interfacing requirements.

        C.5.3.3.2.    The FDCA contractor shall provide an integrated local area data
        communications capability (e.g., LAN, etc.) within each RCC, PRAO and LCO as
        required to support the operational needs of those offices.

        C.5.3.3.3.   All voice and data communications capabilities provided by the
        FDCA contractor shall provide a backup capability in the event that the primary
        capability becomes non-operational for any period of time.

        C.5.3.3.4.    All voice and data capabilities provided by the FDCA contractor shall
        be capable of performing, with no degradation in service, the peak operational
        loads of the voice or data communications function they support.

        C.5.3.3.5.   The FDCA contractor shall install, establish, configure, administer,
        monitor, and maintain email services for the RCC, PRAO and LCO staff, and
        messaging for the field staff using MCEs. The email services provided shall
        integrate with Census email system address books.

    C.5.3.4      Telecommunications Performance Requirements

        C.5.3.4.1.   The FDCA contractor shall monitor the data and voice network, and
        its components, as required to ensure operational effectiveness for all users and
        maintaining a 99% availability of network capability and resources.

        C.5.3.4.2.   The FDCA contractor shall provide an OCE for each RCC, PRAO
        and LCO which enables rapid data communication and shared system services &
        resources between computing devices within each RCC/PRAO and LCO, and
        between computing devices at differing RCCs/PRAO and LCOs (e.g., a LAN,
        WAN, or similar capable technology).

        C.5.3.4.3.   The FDCA contractor shall provide a Mean Time to Repair (MTTR)
        of 4 hours or less for all components used to provide the Telecommunications
        solution.

        C.5.3.4.4.     The FDCA contractor’s telecommunication solution shall have the
        ability to utilize a backup telecommunications capability in 1 hour or less.

C.5.4   FDCA SUPPORT



                                     Appendix A-2 Page 49 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



Support within FDCA will be to provide Help Desk, Hardware/Software
Management/Repair/Replacement/Inventory Tracking, and Training
Designs/Materials/Products as required to effectively manage all work accomplished in
fulfillment of this contract’s requirements, and for the effective performance of operational
deliverables. As in any operation, effective support of an operation is often as critical as
the conducting of the operation itself. Success of support for FDCA will therefore heavily
rely upon the capability to be proactive and preventative, followed by post-problem
responses, which are quick and highly effective. The challenge will be to implement such
a support structure that is high-performing nation-wide in scope for both the urban and
rural/remote settings for the FDCA field staff.

    C.5.4.1      General Requirements

    The General Requirements cover needs common to the entire spectrum operations for
    this section.

        C.5.4.1.1. The FDCA contractor shall provide computer and
        telecommunications (voice and data) support for FDCA (i.e., for the RCCs, the
        PRAO, the LCOs, and the field mobile computing environment).

        C.5.4.1.2.   For all contract deliverables the FDCA contractor shall provide all
        hardware, software, installation, maintenance (including preventative), support,
        training and decommissioning/data sanitization to any location required in the
        United States and Puerto Rico.

        C.5.4.1.3.    The FDCA contractor shall be responsible for the configuration
        management of all computer and telecommunications configuration changes and
        the tracking and reporting of those changes in a central tracking system, which they
        shall establish and maintain.

        C.5.4.1.4.    The FDCA contractor shall be responsible for all aspects of
        packaging, delivery, setup, installation, integration, configuration, test, certification
        of readiness for production use, management, administration, monitoring,
        maintenance, repair, upgrade, life-cycle replacement, de-installation, removal, and
        disposal of deliverables (i.e., both COTS and custom hardware and software) and
        removal of their associated shipping materials.

        C.5.4.1.5.   The FDCA contractor shall be responsible for ensuring the safe
        shipping of the MCE or any component thereof, and that the MCE is adequately
        insured to cover full loss or damage.

        C.5.4.1.6.  The FDCA contractor shall distribute/deliver the MCE, its complete
        replacement, or group of components for replacement, as a single package to an
        agreed upon destination.



                                     Appendix A-2 Page 50 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.4.1.7.   The FDCA contractor shall support all contract deliverables according
        to the Service Level Agreements as jointly developed by the FDCA contractor with
        the government after contract award.

        C.5.4.1.8.   The FDCA contractor shall support dial-up (in and out) services as
        required by the RCCs, PRAO, LCOs, for faxing and remote connectivity.

        C.5.4.1.9.    The FDCA contractor shall provide the process for the OCEs and
        MCEs for all staff to receive version updates (e.g. patches, virus definition files,
        etc.) of any software or data while in the field at any time during the Census
        operation.

        C.5.4.1.10.  The FDCA contractor shall provide comprehensive near real-time
        configuration management and reporting on all hardware and software
        configurations and version releases deployed.

        C.5.4.1.11. The MCE delivered to each field staff, or any component for
        replacement, shall be in a weather and impact secure shipping container (eg.
        DHL/Fedex/UPS drop test).

        C.5.4.1.12.  The MCE shipped to each field staff, or any replacement component
        for an MCE, shall include a document identifying all the contents of the shipping
        container for easy inventorying and to facilitate the easy re-packaging of contents
        should multiple random inventory/testing inspections be conducted.

        C.5.4.1.13. In the event of a software and/or hardware failure of the OCE or MCE
        which renders any or all of its designed functionality inoperable, the OCE or MCE
        shall be fixed and/or replaced and be back in full operation restored to its exact
        state (HW, SW, functionality, with all data) just prior to the failure.

    C.5.4.2      Help Desk and Maintenance

    Minor problems become major problems when encountered at the scale needed to
    conduct a Decennial Census. Even the smallest deviation in an application from its
    described help documentation can lead to an overwhelming number of calls to a
    support desk.

    Therefore, the impact of a hardware or software errors can become very costly in terms
    of productivity in the field. The cost associated with fixing the error is minimal
    compared to the impact on all aspects of field automation support. Therefore, field
    staff will need to receive fast and effective resolutions to problems/questions.

        C.5.4.2.1.   The FDCA contractor shall be responsible for providing a Help Desk
        function providing support for all FDCA deliverables and work.



                                     Appendix A-2 Page 51 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.4.2.2.  The FDCA contractor’s help desk shall accept requests via e-mail,
        telephone and web.

        C.5.1.2.2. The Help Desk shall have design components of its operation, which
        specifically address performance in an environment where callers are new
        temporary employees where a significant percentage cannot differentiate between
        technical/automation problems and procedural problems.

        C.5.4.2.3.   The FDCA contractor shall, in consultation with and as approved by
        the government, develop, publish, disseminate and implement standard operating
        procedures (SOP) for the Help Desk and users of the Help Desk.

        C.5.4.2.4.  The FDCA contractor shall establish and implement, in consultation
        with and as approved by the government, Operations Management and Quality
        Control activities to assess the effectiveness of operations and resolution of
        problems received by the help desk..

        C.5.4.2.5.   The FDCA contractor’s help desk shall document each help desk call,
        including erroneous calls such as those for procedural assistance. The elements for
        what is recorded in each ticket will be worked out in consultation with and as
        approved by the government.

        C.5.4.2.6.   The FDCA contractor’s help desk shall provide operating hours from
        7am – 8pm (local time of RCCs/LCOs) seven days a week. The FDCA
        contractor’s help desk hours of operation may be expanded/curtailed based on
        finalized operational schedule to finalized post contract award.

        C.5.4.2.7.   The FDCA contractor shall provide a problem prioritization scheme
        and help desk metrics reporting.

        C.5.4.2.8.   The FDCA contractor’s Help Desk services shall provide any and all
        help as required for problem resolution on FDCA deliverables.

    C.5.4.3      Network and Systems Operations

    The FDCA network operations encompass all the data and voice operations at the
    RCCs/PRAO/LCOs, and data to/from the MCEs, and the flow of that data to HQ and
    external systems as required. The size of this total network operation will therefore
    require significant capacity and capability (see Section J - Workload Performance for
    sizing and workload assumptions).

        C.5.4.3.1.  The FDCA contractor shall implement a network operation center
        function which shall be capable of 24x7 central monitoring, administering,
        managing, and controlling all network and telecommunications activity and
        equipment at and between the RCCs/PRAO, LCOs, and the deployed MCEs.

                                     Appendix A-2 Page 52 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)            8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.4.3.2.    The FDCA contractor shall design, build, and deploy the capabilities
        for complete near real time network and system monitoring, management, control,
        security, and administration, both centrally and locally at the individual RCC/LCO,
        as appropriate, for the most effective FDCA IT support of census operations.

        C.5.4.3.3.   The FDCA contractor shall establish and support network
        connectivity for contractor provided and government provided resources (hardware
        and software) at the LCOs, PRAO, RCCs, and for the MCEs of the field staff.

    C.5.4.4      Training Support

        C.5.4.4.1.    The FDCA contractor shall create and maintain training tools (to
        include: instructional designs, user manuals, administration manuals, WBT/CBT
        modules, data sets, and other training materials as required to conduct training)
        associated with function, installation, use, operation, maintenance, administration,
        and decommissioning of all deliverables.

        C.5.4.4.2.    The FDCA contractor shall ensure that all training deliverables that
        can be incorporated into an automated training system or are to be utilized by an
        LMS shall be Sharable Courseware Object Reference Model (SCORM)
        conformant and has passed the SCORM Conformance Test Suite (Self Test), which
        indicates that the product conforms to the latest version of SCORM specifications
        as outlined in the SCORM Conformance Requirements.

        C.5.4.4.3.   The FDCA contractor shall support training needs as required, to
        include performing instruction, delivery and management of Learning Management
        Systems, for FDCA-related training support for all FDCA deliverables.

    C.5.4.5      Support Performance Requirements

        C.5.4.5.1. The FDCA contractor shall calculate and report uptime (e.g. FDCA
        Solution is available for use)) and mean time to repair (e.g. time from problem
        report to restore unit to exact function just prior to the failure) metrics for each 30
        calendar day period by RCC, LCO, and FOS.

        C.5.4.5.2. The FDCA contractor shall calculate and report uptime and mean time
        to repair (e.g. time from problem report to restore unit to exact function just prior to
        the failure) metrics separately for problems impacting shared functionality or
        resources by offices or groups of field staff greater than 20.

        C.5.4.5.3. The FDCA contractor shall provide a process to assess customer
        satisfaction by RCC, LCO, and FOS on a monthly boundary.

        C.5.4.5.4. The FDCA contractor shall provide near real time reporting and
        monitoring of performance metrics and a “control panel/dash board” application to
        visually report those metrics from any internet enabled PC.

                                     Appendix A-2 Page 53 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.4.5.5. If the OCE or MCE encounters a hardware and/or software error, the
        device shall log the error, alert the user, and attempt to repair the error with
        minimum staff interaction. The FDCA contractor shall work with the government
        to jointly determine the criteria for “minimum staff interaction” after award.

C.5.5   FDCA SECURITY

The scope of security for FDCA is to design, implement, and manage the securing of all
contract deliverables (e.g., systems, data, operating environments, processes, etc.) within
all phases of the System Development Life Cycle for FDCA Fieldworker Operations,
Office Operations, and Telecommunications as appropriate to handle Title 13 information
and the access/operation of government data and systems as required by the following
mandates:

    1) FIPS 140-2, http://www.itl.nist.gov/fipspubs/
    2) NIST Special Publications 800-18, 800-30, 800-34, 800-37, and 800-63
    3) Department of Commerce IT Security Program Policy located at
       http://www.osec.doc.gov/cio/oipr/itsec/DOC-IT-Security-Program-Policy.htm,
    4) Census Bureau’s IT Security Program Policies (See Section J - Security)

The scope of these security directives may change over the life of this contract due to the
evolution of laws and policies stimulated from previous events and unforeseen future
events. The potential for new laws or changes to laws and policies, although outside the
control the Census Bureau, may affect scope and/or requirements for the FDCA contract.
Therefore, in the event that such a change/modification occurs that affects the FDCA scope
and/or requirements, the Government requires the FDCA contractor to address these
situations in the most cost effective and efficient manner possible.

The requirements defined below shall not eliminate any additional requirements specified
in the mandates above.

    C.5.5.1      Certification & Accreditation (C&A) of Information Technology
    Systems

        The FDCA contractor shall ensure that the FDCA solution is certifiable and fully
        certified prior to any processing of Census data by the Chief of the Information
        Technology Security Office (ITSO) and the Department of Commerce Office of
        Security at the Census Bureau and accredited by the Associate Director for
        Decennial Census, according to NIST Special Publication 800-37. This process is
        documented in Section 3.4 of the Department of Commerce IT Security Program
        Policy located at http://www.osec.doc.gov/cio/oipr/itsec/DOC-IT-Security-
        Program-Policy.htm.

        C.5.5.1.1.      The Government shall guide the C&A process.


                                     Appendix A-2 Page 54 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.5.1.2.   The Government shall review the Security Plan, Contingency Plan,
        NIST Special Publication 800-26 Self-Assessment Questionnaire, and Risk
        Assessment, supporting NIST 800-37 documentation, and Plan of Action and
        Milestones. The Government will also perform onsite IT and physical security
        inspections of contractor facilities supporting the FDCA project.

        C.5.5.1.3.   The FDCA contractor shall repeat a security certification and
        accreditation of the production solution every three (3) years.

        C.5.5.1.4.    The FDCA contractor shall be required to complete a “modified”
        certification and accreditation process for the development, test, and 2008 Dress
        Rehearsal solutions as outlined in Section J - Security.

        C.5.5.1.5.    All sites operated by the FDCA contractor for or on behalf of the
        Government shall be available at all times for inspection by security personnel
        from the Department of Commerce Office of Security at the Census Bureau, the
        Census Bureau’s ITSO, and the Decennial Data Communications and Security
        Staff to ensure that the sites comply with all applicable physical and IT security
        requirements of the Federal Government, Department of Commerce, and the
        Census Bureau.

        C.5.5.1.6.    The FDCA contractor shall work with the Government to jointly
        determine the inspection schedule based on FDCA schedule requirements and the
        availability of Government staff.

        C.5.5.1.7.   The FDCA contractor shall complete a NIST Special Publication 800-
        26 Self Assessment Questionnaire on an annual basis.

        C.5.5.1.8.  The FDCA contractor shall deliver, maintain, and adhere to all
        documentation required to fulfill security requirements and NIST 800-37 and the
        C&A processes for both production and dress rehearsal solutions.

        C.5.5.1.9.   The FDCA contractor shall provide Security Plans that address all
        processes the FDCA contractor will follow to ensure that FDCA, its components
        and associated facilities meet the security requirements necessary to receive
        accreditation, and complies with NIST Special Publication 800-18.

        C.5.5.1.10.  The FDCA contractor shall provide an Overall Risk Management
        Plan that complies with NIST Special Publication 800-30.

        C.5.5.1.11.  The FDCA contractor shall update/maintain the risk management
        plans as new risks are identified throughout the life cycle, and shall review
        annually.



                                     Appendix A-2 Page 55 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.5.1.12.   The FDCA contractor shall perform a risk assessment of the entire
        program annually to include individual assessments of each FDCA contractor
        facility and review annually.

        C.5.5.1.13.   The FDCA contractor shall provide a Plan of Action and Milestones
        for any issue that arises from the annual risk assessments.

        C.5.5.1.14.  The FDCA contractor shall, either through risk assessment or risk
        mitigation, maintain a “low” level of risk for the solution prior to deployment.

        C.5.5.1.15.   The FDCA contractor shall provide risk assessments on E-
        authentication (NIST Special Publication 800-63), data sensitivity, and file
        transfers as appropriate for the system/facility.

        C.5.5.1.16.   The FDCA contractor shall provide Continuity of Operations Plans
        that also addresses contingency planning and complies with NIST Special
        Publication 800-34.

        C.5.5.1.17.  The FDCA contractor shall provide Supporting documentation that
        supports every Test ID within the Census Bureau’s Security Test and Evaluation
        document. This document is available within Section J - Security.

        C.5.5.1.18.   In the event of any major changes to production systems, including
        changes in scope for the system; the FDCA contractor shall be required to re-
        certify and re-accredit the solution as guided by the Census Bureau’s IT Security
        Office.

    C.5.5.2      Federal Information Processing Standards (FIPS) Requirements

        C.5.5.2.1.   FDCA shall conform to NIST publications (FIPS and Special
        Publications) in the security category.

        C.5.5.2.2.   The FDCA contractor shall document how the FDCA design adheres
        to FIPS requirements. The FIPS requirements for computer security can be found
        at http://www.itl.nist.gov/fipspubs/.

    C.5.5.3      FDCA Support Facilities

    FDCA support facilities are any non-RCC/PRAO and non-LCO facilities that are
    required by the contractor for the total FDCA solution. For example, these may
    include any Network Operation Centers (NOC), Data Centers, development & test
    facilities, etc. The FDCA contractor is responsible for all logical and physical access
    controls to these facilities. The government is responsible for administering physical
    access controls at the RCCs/PRAO and LCOs.


                                     Appendix A-2 Page 56 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.5.3.1    The FDCA contractor shall acquire, build-out, install, maintain and
        provide security for any FDCA support facilities that they require to support the
        FDCA solution.

        C.5.5.3.2     Any FDCA support facility created, as a result of this contract, shall
        require that the FDCA contractor create and administrator logical and physical IT
        access controls.

        C.5.5.3.3    The FDCA contractor, as a part of the solution, shall be responsible
        for any logical access controls to automated systems at the RCCs/PRAO, LCOs,
        and any FDCA support facilities.

        C.5.5.3.4    In any support facility, the FDCA contractor shall comply with all
        security requirements necessary to be qualified as a Title 13 data processing
        facility. Accordingly, the FDCA contractor shall comply with all confidentiality
        and privacy policies described in http://www.census.gov/main/www/policies.html.

        C.5.5.3.5    The FDCA contractor shall house the FDCA systems and equipment
        at secure FDCA support facilities that have been approved by the Department of
        Commerce Office of Security at Census. All systems housed at these facilities
        shall be required to be certified and accredited in accordance with NIST 800-37.

        C.5.5.3.6   The Department of Commerce’s Office of Security, Anti-Terrorism
        Branch shall perform physical security inspections of all FDCA facilities.

        C.5.5.3.7   The FDCA contractor shall restrict access to FDCA support facilities
        where census data are handled to avoid unintentional or accidental disclosure.

        C.5.5.3.8     The FDCA contractor shall ensure that any person requiring access to
        FDCA support facilities where census data are being handled have taken the
        confidentiality oath.

        C.5.5.3.9    The FDCA contractor shall ensure all necessary security measures are
        in place in FDCA support facilities to protect the IT the FDCA contractor delivers
        and/or supports from malicious attacks, including but not limited to protecting staff
        from biochemical or other hazardous materials.

        C.5.5.3.10    The FDCA contractor shall ensure all necessary security measures are
        in place to protect the FDCA Systems from malicious attacks including denial of
        service attacks.

        C.5.5.3.11  The FDCA contractor shall provide for site-specific physical security
        at all FDCA support facilities.



                                     Appendix A-2 Page 57 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.5.3.12    After contract award, the FDCA contractor shall work with the
        Department of Commerce Office of Security at Census to determine requirements
        on a site-by-site basis.

        C.5.5.3.13      The FDCA contractor shall provide FDCA support facility access
        controls.

        C.5.5.3.14    The FDCA contractor shall centrally control and monitor all aspects
        of IT security for each/all RCC/PRAO, LCO, and FDCA support facilities.

        C.5.5.3.15   The FDCA contractor shall provide guard service to implement
        security procedures and monitor security systems twenty-four (24) hours per day,
        seven (7) days per week, at all FDCA support facilities, including any dedicated
        portion of commercial facilities.

        C.5.5.3.16    The FDCA contractor shall monitor fire panels internally at a central
        control panel within each FDCA support facility and have it monitored externally
        by either a separate off-site entity or a direct link into the fire department.

        C.5.5.3.17    Within each FDCA support facility, the FDCA contractor shall
        provide a smoke detection system equipped with audible and visual alarms that are
        integrated into the centrally monitored security system.

    C.5.5.4       Personnel Security

    The Census Bureau hires staff for the RCC, PRAO, LCO and enumerator positions.
    The suitability clearance required for these positions will be handled by the Census
    Bureau.

    Title 13, U.S.C., Section 23(c) permits the Government to use non-Government
    employees to assist in performing the work authorized under this title, but only if such
    temporary staff members are sworn to observe the limitations imposed by Section 9 of
    this title.

        C.5.5.4.1       FDCA Contractor hired management, technical and maintenance
        staff

              C.5.5.4.1.1    All FDCA contract employees shall take the Census Bureau
              Oath of Nondisclosure (BC-1759, “Special Sworn Status”) of the data to
              receive Special Sworn Status (SSS) prior to access to Title 13 information. A
              designated Census Bureau employee or a Notary Public, if the Census Bureau
              designee is unavailable, will administer the oath.

              C.5.5.4.1.2   All FDCA contractors shall be required to renew their Special
              Sworn Status with the Census Bureau on an annual basis.

                                     Appendix A-2 Page 58 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




             C.5.5.4.1.3    All contract employees shall be subject to penalties for unlawful
             disclosure of Title 13 census data.

             C.5.5.4.1.4  All FDCA contractor personnel with access to Title 13
             information shall complete an annual Title 13 Security Awareness Course
             provided by the Census Bureau’s Policy Office.

             C.5.5.4.1.5  All FDCA contractor personnel with access to IT resources shall
             complete an annual IT Security Awareness Course provided by the Census
             Bureau’s IT Security Office.

             C.5.5.4.1.6    The FDCA contractor shall ensure that all
             contractor/subcontractor employees do not work or visit FDCA sites covered by
             the FDCA contract until a favorable pre-employment background investigation
             is received from the Government. Individuals who have had a recent
             background investigation with another Government agency, which meet
             Department of Commerce requirements, and which can be verified by the
             Office of Security, do not require a pre-employment investigation from Census.
             Type of investigation, date, and verification contact must be provided to the
             Office of Security for investigation.

             C.5.5.4.1.7  The FDCA contractor shall submit to the Contracting Officer
             within forty-eight (48) hours of contract award the required investigative
             package (See Section J - Security for the required forms) for all potential
             personnel starting work on FDCA at contract award.

             C.5.5.4.1.8  All other potential personnel, including FDCA contractor(s) or
             subcontractor(s) performing contract work or support work and any project
             supervisors and management officials who visit the sites shall complete the
             required paperwork and pass the Government’s suitability clearance prior to
             starting work on FDCA.

             C.5.5.4.1.9    The FDCA contractor shall submit paperwork for new FDCA
             employees at least two (2) calendar weeks before they commence work under
             this contract. Necessary forms will be furnished by the Government at contract
             award and will be made available to the FDCA contractor as needed during the
             life of this contract.

             C.5.5.4.1.10  Building maintenance staff in any support facility shall be
             required to clear a pre-employment investigation.

        C.5.5.4.2       Foreign Nationals



                                     Appendix A-2 Page 59 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        Contractor personnel who are not U.S. citizens are subject to the same security
        processing as any other Contractor. The suitability clearance requires that non-
        United States citizens reside in the United States for at least two (2) years leading
        up to the date of submission of the appropriate clearance forms.

             C.5.5.4.2.1. The FDCA contractor shall not employ or use any foreign
             nationals on any aspect of the FDCA contract who have been in the United
             States less than two (2) years.

             C.5.5.4.2.2. The FDCA contractor shall only submit suitability clearance
             paperwork for foreign nationals who resided in the United States for the two (2)
             years preceding submittal of the suitability paperwork. The Government
             reserves the right to change the policy related to Foreign Nationals and the
             FDCA contractor shall adhere to such changes.

             C.5.5.4.2.3. Foreign nationals who have resided in the United States for at least
             the previous two (2) years before FDCA employment shall only be granted
             access to Title 13 data after providing all necessary forms including
             Immigration and Naturalization Service (INS) documentation and passing the
             suitability clearance. (See Section J - Security for the required forms).
             However, these foreign nationals shall not be allowed in any Government
             designated restricted areas.

             C.5.5.4.2.4. The FDCA contractor shall ensure that Foreign Nationals:
                     do not access Government designated restricted areas;
                     do not assume administrative or policy-forming responsibilities for any
                      FDCA-related work;
                     do not assume security related positions such as security management or
                      oversight, guards, or security officers in any FDCA-related facilities;
                     do not access classified (national security) information; and
                     do not access restricted areas, such as computer rooms or
                      telecommunication centers, in any FDCA-related facilities.

        C.5.5.4.3       Commerce Acquisition Regulation Compliance

        The following are information technology security clauses required for all contracts
        for services involving information technology in which the contract must have
        physical or electronic access to Department of Commerce information. Reference
        the November 17, 2003 memorandum from the Deputy Director for Acquisition,
        Christine A. Markris, Subj: Information Technology Security Clauses.

             C.5.5.4.3.1  The FDCA contractor shall fully comply with CAR 1352.237-71
             (see Section J - Security for a copy of this regulation).



                                     Appendix A-2 Page 60 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)             8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



              C.5.5.4.3.2  The FDCA contractor shall fully comply with CAR 1352.239-73
              (see Section J - Security for a copy of this regulation).

              C.5.5.4.3.3  The FDCA contractor shall fully comply with CAR 1352.239-74
              (see Section J - Security for a copy of this regulation).

              C.5.5.4.3.4  Failures to Comply – failure of the FDCA contractor to comply
              with the requirements of this section may result in termination of this contract,
              or removal of some contracted employees from DOC facilities. Compliance
              with these requirements shall not be construed as providing a contract
              employee clearance to have access to classified information.

    C.5.5.5       Information Technology Security for OCE, MCE and support facilities

        C.5.5.5.1     The FDCA contractor shall monitor, account for, perform, and ensure
        that all systems/equipment/products delivered which may have contained Title 13
        data during their operational life, are degaussed or otherwise sanitized so that Title
        13 data are unrecoverable in whole or in part. The process used shall be in
        compliance with applicable government regulations and guidance.

        C.5.5.5.2    The FDCA contractor shall use all means available to provide security
        for the government owned source code and data.

        C.5.5.5.3     Government owned source code and data, which becomes available to
        the FDCA contractor under the terms in this Statement of Work, shall be restricted
        to the uses necessary to ensure proper functioning of the systems supported by
        FDCA, and shall not be disclosed or used for any other purpose without the prior
        written permission of the Contracting Officer. These restrictions shall not apply to
        material currently published and presently in the public domain, or material
        obtained by the FDCA contractor about FDCA applications systems independent of
        the government.

        C.5.5.5.4     The FDCA contractor shall be responsible for making regular
        backups, on a schedule approved by the government, of all computer data that
        supports FDCA applications systems within the RCCs, PRAO, LCOs, and on each
        of the Field Staffs’ MCEs.

        C.5.5.5.5    The FDCA contractor shall have the responsibility to ensure
        appropriate security is implemented, i.e. network access, database access, computer
        room and telephone closet access, and general access to the RCCs, PRAO and
        LCOs.

        C.5.5.5.6   The FDCA contractor shall establish and implement back-up and
        recovery procedures for the RCCs, PRAO, LCOs, Field Staff MCEs and all support
        facilities.

                                     Appendix A-2 Page 61 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




        C.5.5.5.7    The FDCA contractor shall administer an effective backup and
        recovery program, consistent with Census Bureau operating procedures, regulations
        and the requirements of this SOW. This will include off-site storage and retrieval
        from such storage facility(ies).

        C.5.5.5.8   The FDCA contractor shall develop an operations manual specifying
        back-up schedules, retention cycles and recovery procedures for each RCC, the
        PRAO and each LCO, support facilities and generally for the Field Staff MCEs.

        C.5.5.5.9   The FDCA contractor shall periodically test the established back-up
        and recovery procedures, and back-up system components in accordance with
        back-up schedules.

        C.5.5.5.10  The FDCA contractor shall maintain the back-up library in
        accordance with retention cycles and, if needed, execute recovery procedures.

        C.5.5.5.11   The FDCA contractor shall develop and implement disaster recovery
        plan(s) and testing for the RCCs, PRAO, LCOs, Field Staff MCEs and all support
        facilities.

        C.5.5.5.12   The FDCA contractor shall establish and implement network
        administration procedures to implement network access controls and user ID and
        password integrity.

        C.5.5.5.13 The FDCA contractor shall establish and implement access controls to
        the MCE to meet all applicable security requirements.

        C.5.5.5.14    The FDCA contractor shall establish and implement automated post
        office administration procedures to ensure the integrity of the email systems for the
        RCCs, PRAO, LCOs and support facilities, the prevention of unauthorized access
        to email files, the retention of email data, including archiving recovery of email
        capability in the event of systemic failure.

        C.5.5.5.15   The FDCA contractor shall establish and implement anti-viral
        measures for the RCCs, PRAO, LCOs, support facilities and Field Staff MCEs to
        ensure virus screening ability, the detection of virus penetration, the eradication of
        any detected virus, and the immediate notification of the LAN Security Officer, the
        Computer Security Officer and the customer support manager of any detected
        virus.

        C.5.5.5.16    The FDCA contractor shall implement a physical intrusion monitoring
        system that is monitored 24/7 by police/fire authorities for all the FDCA contractor
        support facilities.


                                     Appendix A-2 Page 62 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



C.5.6   FDCA MANAGEMENT

The scope of management for FDCA is to provide program management, project
management, and SDLC management for all work accomplished in fulfillment of this
contract’s requirements.

    C.5.6.1      General Requirements

    The General Requirements cover those needs common to the entire spectrum
    operations for this section.

        C.5.6.1.1.  Program Management under the FDCA contract shall provide the
        FDCA contractor and the Government with the tools necessary to effectively
        manage the work performed.

        C.5.6.1.2.   The FDCA contractor shall manage all FDCA tasks in a manner that
        allows completion of FDCA objectives within the schedule, cost, quality, scope,
        and technical baselines.

        C.5.6.1.3.    The FDCA contractor shall provide for the management,
        administration, and documentation of the FDCA contract, which includes the
        provision of all staff, facilities, systems, equipment, processes, procedures, training,
        and management knowledge areas (Quality Assurance/Quality Control (QA/QC),
        security, recruiting, payroll, etc.) necessary to initiate, execute, monitor, status,
        control, secure, and close-out the functions required by this statement of work.

        C.5.6.1.4.   The FDCA contractor shall develop, maintain, report on monthly, and
        comply to a baseline program management plan (B-PMP) required to successfully
        manage the FDCA program.

        C.5.6.1.5.  The FDCA contractor shall develop acceptance test plans, and assist
        the Government as required in conducting those tests, for all FDCA deliverables
        and work performed by the FDCA contractor.

        C.5.6.1.6.   The FDCA contractor shall deliver a set of documentation on each
        systems deliverable (e.g., any software or hardware product or combination such as
        an LCO’s LAN, the MCE, the system automating the OC function, etc.) which
        comprehensively documents all detailed functional specifications of the system
        (including what specific Census function, operation, or performance need each
        functional specification supports, and to include the high level and low level
        detailed designs of the systems) in sufficient detail to allow development of a
        replacement system/capability for the 2020 Census.




                                     Appendix A-2 Page 63 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.1.7.    The FDCA contractor shall develop, and maintain a Master Document
        List, such as a document tree that shows traceability among the Contractor’s FDCA
        documentation.

        C.5.6.1.8.   The FDCA contractor shall deliver an updated Master Document List
        quarterly (January 15th, April 15th, July 15th, and October 15th of each year).

    C.5.6.2      CMMI and ISO Requirements

        C.5.6.2.1.  The FDCA contractor shall meet the requirements for this project in a
        manner compatible with the Software Engineering Institute’s (SEI) Capability
        Maturity Model Integration (CMMI) Level 3 processes and the International
        Standards Organization’s current ISO 9001 standards throughout the FDCA period
        of performance. Additional information can be found at
        http://www.sei.cmu.edu/cmmi and http://www.iso.org/iso/en/ISOOnline.
        frontpage.

        C.5.6.2.2.   The FDCA contractor shall ensure that all deliverables produced by
        all FDCA subcontractors are produced in a manner consistent with CMMI Level 3
        processes, ISO 9001 standards, and software engineering best practices.

        C.5.6.2.3.  The Government requires that all participants (i.e., the prime and
        subcontractors) shall use a common process in fulfillment of CMMI Level 3 and
        ISO 9001 requirements.

        C.5.6.2.4.   Within the first month of contract award, the FDCA contractor shall
        provide a plan for CMMI Level 3 and ISO 9001 compliance.

        C.5.6.2.5.   Within the first year of contract award, and thereafter annually
        throughout the entire contract period of performance, the FDCA contractor shall
        complete a successful CMMI appraisal to verify attainment of Level 3 process
        maturity on the overall FDCA project.

        C.5.6.2.6.   Within the first year of contract award, and thereafter annually
        throughout the entire contract period of performance, the FDCA contractor shall
        complete a successful ISO 9001 audit on the overall FDCA project.

        C.5.6.2.7.    The FDCA contractor shall provide the Government with all
        documentation resulting from the CMMI appraisal and the ISO 9001 audit as soon
        as available from the SEI certified assessor/appraiser or ISO certified auditor.

        C.5.6.2.8.   The team supporting the FDCA effort shall have been trained in the
        use of Software Engineering Institute (SEI) CMMI Level 3 processes and shall be
        able to execute these at the on-set of the contract.


                                     Appendix A-2 Page 64 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    C.5.6.3      Communication with the Government

        C.5.6.3.1.   The FDCA contractor shall establish and maintain effective
        communication with the Government’s FDCA Project Management Office (PMO).
        Daily verbal communication is essential at all levels of the program.

        C.5.6.3.2.    The FDCA contractor shall structure the effort in a manner that
        ensures that the FDCA contractor’s goals and objectives are synchronized with
        those of the Government’s PMO and reflect the attributes of a partnership through
        an open, customer-oriented effort.

        C.5.6.3.3. The FDCA contractor shall consistently take steps to understand the
        PMO business and technical issues.

        C.5.6.3.4.   The FDCA contractor shall work collaboratively with Government
        subject matter, technical, statistical, geographic, systems, and security staff to
        ensure the detailed FDCA specifications and all other FDCA aspects meet
        Government requirements and lead to the success of the 2010 Census.

        C.5.6.3.5.     The FDCA contractor shall as directed by the CO/COTR, coordinate
        its efforts with the Government and other 2010 Census contractors to ensure
        success of the FDCA and the 2010 Census.

        C.5.6.3.6. The FDCA contractor shall provide insight into issues or problems to be
        addressed along with a recommended solution, including a report listing current
        technical, quality assurance and operational problems during the design
        specification, development, testing, deployment, production, and close-out. Timing
        and content of this report will be jointly agreed upon after contract award.

        C.5.6.3.7. The FDCA contractor shall recommend solutions to maintain cost,
        schedule, quality, and technical baselines.

    C.5.6.4      Work Breakdown Structure and Project Schedule

    The Government requires the use of a product-oriented Contract Work Breakdown
    Structure (CWBS) as the core of a program control and scope management approach.
    A WBS is defined as a product-oriented grouping of project elements that organizes
    and defines the total scope of work for the project. A WBS displays and defines the
    product, or products, to be developed and/or produced. It relates the elements of work
    to be accomplished to each other and to the end product, for example, integrating the
    hardware, software, services, data, and facilities for FDCA. The CWBS will be further
    integrated into a project schedule, which the Government and the FDCA contractor
    will use as a project management interface tool that ties technical, cost, quality, scope,
    and schedule baselines into a performance-based, earned value management system
    (EVMS).

                                     Appendix A-2 Page 65 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




        C.5.6.4.1.    The Contractor shall develop, deliver, maintain, and adhere to detailed
        product-oriented CWBSs for FDCA consistent with MIL-HDBK-881
        (http://www.acq.osd.mil/pm/newpolicy/wbs/ mil_hdbk_881/ mil_hdbk_881.htm) to
        use for its management of the FDCA Contract.

        C.5.6.4.2.      The FDCA contractor shall deliver a draft CWBS with their proposal
        to this RFP.

        C.5.6.4.3.    The FDCA contractor shall ensure that the CWBS will allow for
        Government visibility into the FDCA contractor’s detailed milestones and the
        status of deliverables and products for the FDCA contract. The Government will
        use this information for performance measurement and tracking of the status of
        FDCA activities.

        C.5.6.4.4.   The FDCA contractor shall minimize the use of Level-of-Effort cost
        accounts to the greatest extent practical.

        C.5.6.4.5. The FDCA contractor shall develop, deliver, maintain, and adhere to
        separate CWBSs for each of the six FDCA requirements areas (e.g., Mobile
        Computing, Office Computing, Telecommunications, Security, Support, and
        Management) with the requirements area title as the top level.

        C.5.6.4.6.   The FDCA contractor shall develop, deliver, maintain, and adhere to a
        dictionary for each CWBS.

        C.5.6.4.7.    The FDCA contractor shall provide the Government with updates to
        the dictionaries as changes occur within the CWBSs.

        C.5.6.4.8.   The FDCA contractor shall develop, deliver, and maintain a Master
        Integrated Project Schedule (MIPS) that ties to the CWBSs.

        C.5.6.4.9.  The MIPS shall include a unique CWBS identifier for each schedule
        entry and weighted milestone.

        C.5.6.4.10.The FDCA contractor shall provide schedule updates based on the
        CWBS to the Government in a government specified format.

        C.5.6.4.11.   The MIPS shall contain detail of cost and progress, identifying
        specific dates for project tasks and milestones.

        C.5.6.4.12.  All systems development tasks detailed on the MIPS shall separately
        indicate each SDLC phase through to deployment.



                                     Appendix A-2 Page 66 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.4.13. The MIPS shall be delivered with progress tracked and reported
        monthly during the monthly Program Management Reviews.

        C.5.6.4.14.The FDCA contractor shall develop, deliver, maintain, and adhere to a
        FDCA Life Cycle Cost Estimate (LCCE) that links to the CWBSs and project
        schedule.

        C.5.6.4.15.  The LCCE shall include all projected costs for the program for all
        phases and sub phases.

        C.5.6.4.16.The FDCA contractor shall update the LCCE as needed to support the
        Government’s budget process.

    C.5.6.5      Systems Development Life-Cycle (SDLC)

        C.5.6.5.1.    The FDCA contractor shall within 30 days of contract award, provide
        for Government review and approval a comprehensive Systems Development Plan
        (SDP), which describes their plans for conducting the systems development and
        integration efforts necessary throughout the entire systems development life cycle
        (SDLC) in fulfillment of FDCA deliverables and interfaces.

        C.5.6.5.2.   The scope of the SDP shall include new development, modification,
        reuse, reengineering, integration, maintenance, and all other activities resulting in
        systems or systems products, which will be delivered as part of FDCA.

        C.5.6.5.3.    The FDCA contractor shall have, or be able to establish prior to
        contract start, a configuration management (CM) process that provides thorough,
        efficient, and timely implementation of all software and system changes.

        C.5.6.5.4.  The FDCA contractor’s CM process shall incorporate Government
        approval before such changes are initiated. The CM process shall enable
        immediate rollback to deploy previous version releases.

        C.5.6.5.5.  The FDCA contractor shall maintain all source code and required
        documents as part of their CM process.

        C.5.6.5.6.    Deliverables to the government which incorporate FDCA contractor
        developed coding in any form shall include all source code, documentation,
        libraries required for compilation, and an auto-extracting and auto-installing
        wizard.

        C.5.6.5.7.   The FDCA contractor shall support functional and physical
        configuration audits as required by the Government as part of CM process.




                                     Appendix A-2 Page 67 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.5.8.   The FDCA contractor shall document and track all requirements
        against each delivery using the DOORS system.

        C.5.6.5.9.  The FDCA contractor shall provide systems documentation in
        accordance with ISO 9000 standards.

        C.5.6.5.10. The FDCA contractor shall provide detailed systems design
        documentation with links to the 2010 Census Business and/or Logical Architecture.

        C.5.6.5.11.  The FDCA contractor shall develop, deliver, maintain and adhere to a
        physical architecture, which shall interface with the Census Bureau’s 2010 Census
        Physical Architecture.

        C.5.6.5.12.   The FDCA contractor shall provide various technical documents such
        as interface control documents, users’ manuals, software design documents,
        product configuration control, schedules, quality assurance, and other reporting as
        required by the Government.

        C.5.6.5.13.  The FDCA contractor shall collect, analyze, and report systems
        related metrics in the Monthly Progress Report, which provide the FDCA
        contractor and the Government with the insight necessary to accurately predict and
        effectively manage the: cost, schedule, technical performance, and risk associated
        with each systems deliverable for FDCA.

        C.5.6.5.14. The systems related metrics collected and reported shall be agreed to
        and approved by the Government prior to their implementation for collection and
        reporting.

        C.5.6.5.15.  The Government shall revise the systems related metrics required for
        collection and reporting by the FDCA contractor as required.

        C.5.6.5.16. Development, maintenance, and enhancements of software integrated
        or developed for FDCA, which handles response data are considered critical to the
        2010 Census and shall have a defect rate of zero or near zero (i.e., <0.1 %).

        C.5.6.5.17.  The FDCA contractor shall, as required by the government, provide
        training and/or training materials on systems deliverables to government staff
        responsible for FDCA-related training of staff and users.

        C.5.6.5.18.  The FDCA contractor shall provide the methodology to identify and
        resolve software performance issues which shall include the tools and processes to
        be used to detect and report performance problems during the software’s design,
        development, and maintenance.



                                     Appendix A-2 Page 68 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.5.19.The FDCA contractor shall provide a computing environment at the
        FDCA contractor's facility necessary to accomplish software maintenance,
        enhancements, development and associated testing as required in fulfillment of the
        FDCA requirements.

        C.5.6.5.20.   The FDCA contractor’s computing environment at their facility shall
        include all necessary equipment, COTS software and databases, as appropriate.

        C.5.6.5.21.   The FDCA contractor shall make a corporate commitment to, and
        implement a process to, fully coordinate with all Government agencies and other
        contractors to ensure system technical interfaces, software re-use, and other
        technical issues common to more than one program, planning process, or
        organization are optimized to the advantage of the Government.

    C.5.6.6      Earned Value (EV)

        C.5.6.6.1.   The FDCA contractor shall employ EV methodology on the FDCA
        Contract following ANSI/EIA Standard 748-1998.

        C.5.6.6.2.    The FDCA contractor shall ensure that the EV methodology and
        project management processes and systems used by the subcontractor(s) fully
        integrate in electronic form with the FDCA contractor’s systems.

        C.5.6.6.3.  The FDCA contractor shall generate a monthly and cumulative FDCA
        Cost Performance Report (CPR) appropriate to the CWBS.

        C.5.6.6.4.  The level of CPR reporting shall be jointly determined after contract
        award based on the FDCA contractor’s proposed Contract WBSs, however, the
        FDCA contractor shall deliver the CPR at least at a minimum of the 3rd level.

        C.5.6.6.5.    The FDCA contractor shall deliver the CPR by the 15th of each month
        for the current (previous month) and cumulative period for the specific phase.

        C.5.6.6.6. The FDCA contractor’s CPR shall also reflect all subcontractors’ EV
        methodology metrics for both the current and cumulative periods.

        C.5.6.6.7.   The FDCA contractor CPR shall show current and cumulative
        variances and report on the reasons for these variances.

        C.5.6.6.8.    The current and cumulative variance thresholds shall be negotiated
        after contract award and at minimum meet OBM threshold requirements.

        C.5.6.6.9.  The FDCA contractor shall provide the Government with an Insight
        (the Census Bureau’s EV software tool) file each month, to be delivered with the
        CPR.

                                     Appendix A-2 Page 69 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




        C.5.6.6.10.  Guidelines of Department of Defense (DOD) 5000.22 (Section 6.4)
        shall be used to establish cost reporting requirements for subcontractors on the
        FDCA contract.

    C.5.6.7      Financial Reporting

        C.5.6.7.1. The FDCA contractor shall provide FDCA Financial Reports to support
        the Government’s budget process as required by the government.

        C.5.6.7.2. The FDCA contractor’s reports shall include the previous six (6)
        months and cumulative financial information for all FDCA work. The expected
        format of this report is shown in Section J – Program Management Reporting,
        however, this format may change based on the FDCA contractor’s solution and
        proposed CWBSs. The Government will provide the detailed requirements for this
        report after contract award.

        C.5.6.7.3. The FDCA contractor shall generate a Contract Funds Status Report
        (CFSR), DD Form 1586, to be delivered quarterly (January 15th, April 15th, July
        15th, and October 15th).

    C.5.6.8      Government’s FDCA Project Management Office (FDCA PMO)

        C.5.6.8.1. The Government plans to locate its FDCA PMO staff at the Census’
        Suitland, MD facility. The FDCA contractor shall locate the facilities for its
        management and technical leads within the greater Washington, D.C. Metro area.

        C.5.6.8.2. The FDCA contractor shall locate its user acceptance test facility within
        60 minutes driving time of the Census Headquarters in Suitland, MD. The staff
        leads and the user acceptance test lab are not required to be in the same facility but
        should be in close proximity.

    C.5.6.9      Contract Startup and Kick-off Meetings

    The purpose of the kick-off meetings is to ensure mutual understanding of the contract
    and all obligations and responsibilities of the FDCA contractor and the Government.

        C.5.6.9.1. On a date specified by the Government after contract award, the FDCA
        contractor shall meet with the Government and other key FDCA personnel to
        review the activities required to initiate and manage the contract.

        C.5.6.9.2. The FDCA contractor shall work with the PMO to schedule meetings
        for contract kick-off.



                                     Appendix A-2 Page 70 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



    C.5.6.10     Monthly Status Reports

        C.5.6.10.1. The FDCA contractor shall submit a written Monthly Status Report
                   th
        by the 10 day of each month for the previous month’s activities.

        C.5.6.10.2.     The report shall be concise and at a minimum contain the following
        information:
            ▬ The Contract Number and reporting period;.
            ▬ Task order number and task name (if applicable);
            ▬ A summary of the technical work in the following format;
            ▬ A narrative review of work accomplishments and/or significant events for
               the month;
            ▬ Problems and solutions (to include impacts on quality, schedule and cost
               and proposed solutions);
            ▬ Percent of work completed toward interim or final deliverables and
               estimates of time to complete deliverables;
            ▬ Major activities planned for the next month;
            ▬ Monthly and cumulative contract and task order (if applicable) dollars spent
               to date;
            ▬ Graph depicting task-spending plan (planned vs. actual computed by month
               and cumulatively);
            ▬ Indication of funds remaining by contract, phase and task order (if
               applicable);
            ▬ Program issues and high level risks including, but not limited to the areas of
               program management, facilities, equipment, staffing, and funding.
            ▬ Production information including production staffing and other production
               issues;.
            ▬ Status and progress for 508 Compliance;
            ▬ Maintenance issues, maintenance risks, and mitigation activities and/or
               plans;
            ▬ Security issues, security risks, mitigation activities, and/or plans;.
            ▬ Office deployment status reports during deployment of the RCCs/PRAO
               and LCOs.

        C.5.6.10.3.   The FDCA contractor and Government shall jointly determine the full
        contents of the report, to include measurements and metrics for regular reporting, as
        well as the performance baselines/standards for these measurements, after contract
        award.

    C.5.6.11     Subcontracting and Subcontract Participation Plan

    It is the Census Bureau’s goal to assist the Department of Commerce in meeting or
    exceeding its small business goals.



                                     Appendix A-2 Page 71 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.11.1.  The FDCA contractor shall establish, maintain, and adhere to a
        Subcontracting and Subcontract Participation plan that commits a minimum of
        (Not Yet Established) percent of the total contract price to small businesses,
        minority businesses, women-owned businesses, veteran-owned businesses and
        HUBZone businesses (combined).

        C.5.6.11.2.  The FDCA contractor shall document in the plan the types of FDCA
        functions within the contract scope that will be available to small businesses.

    C.5.6.12     Self-Assessment Report for Award Fee Determination

        C.5.6.12.1.  The FDCA contractor shall deliver a Self-Assessment Report in
        accordance with the Government’s Award Fee Determination process and schedule
        (See Section F.4.15 and Section J - Security).

    C.5.6.13     Program Management Reviews (PMRs)

    As a result of the importance of the FDCA project to the overall success of the 2010
    Census, we are requiring the contractor to conduct Program Management Reviews
    (PMRs) on a monthly basis. These PMRs provide a forum for stakeholders outside of
    the Census Bureau's FDCA Project Management Office (PMO) to obtain information
    about the status and issues associated with this project. We anticipate participants from
    decennial participants within other areas of the Census Bureau, as well as external
    oversight groups. The PMR provides a forum for communicating information that
    summarizes the overall status and issues, but does not replace the requirement for daily
    communication with the FDCA PMO about status, cost, issues, etc. As such, the
    FDCA PMO should not hear about issues, concerns, or problems for the first time at
    the PMR.

        C.5.6.13.1.   The FDCA contractor shall schedule and present PMRs on a monthly
        basis unless a change in frequency is jointly agreed upon.

        C.5.6.13.2.    The PMRs shall be at Census Bureau Headquarters unless an alternate
        site is jointly determined.

        C.5.6.13.3.  The first PMR shall be held within sixty (60) days of the contract
        kickoff meeting.

        C.5.6.13.4.  The PMRs shall address technical, business, and programmatic topics,
        with a focus on status, performance and issues/risks.

        C.5.6.13.5.   At least five (5) working days prior to a PMR, the FDCA contractor
        shall provide a proposed agenda to the Government. The Government may add,
        delete, or change items to the agenda prior to the PMR.


                                     Appendix A-2 Page 72 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)           8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        C.5.6.13.6. The FDCA contractor shall provide the PMR handouts to the
        Government at least two (2) days prior to the PMR, but may make revisions as
        needed to address new information.

        C.5.6.13.7.  The FDCA contractor shall ensure that necessary technical and
        management personnel attend the PMRs and that presentation materials and
        supporting data are prepared to ensure that agenda items are fully covered.

        C.5.6.13.8.  Within three (3) working days after a PMR, the FDCA contractor
        shall provide a list of action items and issues that arose during the PMR. The
        Government will provide comments or revisions to this list within three (3)
        working days of receipt.

        C.5.6.13.9.   The FDCA contractor shall provide, as a deliverable, the final PMR
        handouts and a list of action items and issues within three (3) working days of
        receipt of the Government’s comments or revisions.

    C.5.6.14     Meetings

        C.5.6.14.1.  As needed by the Government or the FDCA contractor, the FDCA
        contractor shall participate in business and Field Data Collection Automation
        meetings with the designated personnel from each organization. Meetings between
        the Government and the FDCA contractor may take place in person or via
        conference calls. Available meeting space at the Government is limited so the
        Government expects meetings to occur at the FDCA contractor’s site or by
        electronic means.

        C.5.6.14.2.   The FDCA contractor shall not initiate meetings with Government
        personnel who work for organizations other than the PMO without prior COTR
        notification.

        C.5.6.14.3.     The FDCA contractor shall take minutes for all meetings.

        C.5.6.14.4.  Within three (3) working days after any meeting, the FDCA contractor
        shall provide meeting minutes to the Government. The Government will provide
        comments or revisions within three (3) working days of receipt of minutes.

        C.5.6.14.5.   The FDCA contractor shall provide the final version of minutes
        within three (3) working days after receipt of the Government=s comments or
        revision.

        C.5.6.14.6.  The FDCA contractor shall ensure that its facilities provide sufficient
        meeting space and that the telecommunications equipment can support staff calling
        into a meeting from multiple locations, including the Census Bureau and all FDCA
        facilities.

                                     Appendix A-2 Page 73 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)         8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc




    C.5.6.15     Inventory Management

        C.5.6.15.1. The FDCA contractor shall establish and maintain an automated
        inventory control mechanism for asset control.

        C.5.6.15.2.  All FDCA-purchased inventory, such as hardware, software,
        equipment, and spare parts, in the FDCA contractor and Government facilities,
        shall be controlled using an electronic means.

        C.5.6.15.3.  The FDCA contractor shall work with the Government to ensure that
        a unique identifier, such as a bar code, is placed on all inventoried items.

        C.5.6.15.4.   The FDCA contractor shall provide an inventory control report in an
        electronic format compatible with the Government’s Property Control System.

        C.5.6.15.5. The FDCA Contractor shall provide the ability to generate a real-time
        inventory control report.

        C.5.6.15.6.  The FDCA contractor shall show all changes to the FDCA-purchased
        inventory for the previous month on the inventory control report.

        C.5.6.15.7. The detailed format requirements of this report shall be jointly
        determined after contract award.

    C.5.6.16     Section 508 of the Rehabilitation Act of 1975, as amended

    For the 2010 Census, the Government plans to comply with requirements of Section
    508 of the Rehabilitation Act of 1975, as amended (Section 508) by ensuring that
    people with disabilities have appropriate response options for completing a census
    form. Specifically, within the appropriate range of options for responding to the 2010
    Census, the Government will designate those options that require special modification
    or adaptation directly intended to facilitate access by persons with disabilities. The
    options selected will provide access for disabled persons within the appropriate
    program, cost, security, and risk mitigation requirements for the 2010 Census.

        C.5.6.16.1.  The FDCA contractor shall develop and implement the appropriate
        modifications and adaptations to meet these requirements. If necessary, the
        Government and the FDCA contractor will work together to obtain waivers for
        those response options not modified or adapted to provide access to disabled
        persons.

        C.5.6.16.2.  The FDCA contractor shall adhere to the applicable requirements and
        standards of Section 508, such as ensuring physical access to facilities,
        opportunities for employment, etc., unless otherwise granted a waiver by the

                                     Appendix A-2 Page 74 of 75
                                 PROCUREMENT SENSITIVE
Field Data Collection Automation Program (FDCA)          8de5a7fe-5427-43f8-a60f-782a1a417ea2.doc



        appropriate authority. Further information can be obtained at
        http://www.section508.gov/.

        C.5.6.16.3.  In addition to meeting the requirements under Section 508, the FDCA
        contractor shall also ensure that it complies with all applicable laws and regulations
        regarding accessibility and employment opportunities for disabled persons.


    C.5.6.17     Health, Safety, and Security

        C.5.6.17.1.  For FDCA contractor provided facilities and staffing, the FDCA
        contractor shall develop, deliver, adhere to and maintain health, safety, and security
        programs.

        C.5.6.17.2.   The FDCA contractor shall ensure that their FDCA health, safety and
        security programs comply with policies and practices that ensure workplace safety
        and security in accordance with all Federal, State, Local, and Occupational Safety
        and Health Administration (OSHA) regulations.

        C.5.6.17.3.    The FDCA contractor shall deliver a Health, Safety, and Security
        Report by the 15th of the month, for the previous month’s activities, for each FDCA
        office facility (e.g., RCCs, PRAO, LCOs, FDCA NOC, etc.).

        C.5.6.17.4.    At the Government’s request, the FDCA contractor shall make
        available all safety and security incident reports for all contractor-operated FDCA
        facilities.

    C.5.6.18     Closeout Requirements

        C.5.6.18.1.  Within 30 days of completion of the last FDCA operation (i.e.,
        Coverage Follow-up) the FDCA contractor shall compile all data from their
        developed and/or supported FDCA systems into a central repository of data tables
        with corresponding data dictionaries. All other data related to their work
        performed shall be delivered in editable electronic format.




                                     Appendix A-2 Page 75 of 75
                                 PROCUREMENT SENSITIVE

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:36
posted:8/10/2011
language:English
pages:75
Description: Sample Resume of Census Agent document sample