####### PART IV \-- REPRESENTATIONS AND INSTRUCTIONS

####### SECTION L - INSTRUCTIONS, CONDITIONS AND NOTICES TO OFFERORS OR RESPONDENTS

**L.1 FAR 52.252-1 SOLICITATION PROVISIONS INCORPORATED BY REFERENCE
(FEB 1998)**

This solicitation incorporates one or more solicitation provisions by
reference, with the same force and effect as if they were given in full
text. Upon request, the Contracting Officer will make their full text
available. The Offerors are cautioned that the listed provisions may
include blocks that must be completed by the Offerors and submitted with
their quotation or offer. In lieu of submitting the full text of these
provisions, the Offerors may identify the provision by paragraph
identifier and provide the appropriate information with its quotation or
offer. Also, the full text of a solicitation provision may be accessed
electronically at this address: [www.acqnet.gov]{.underline}

FEDERAL ACQUISITION REGULATION (48 CFR CHAPTER I) CLAUSES

[NUMBER]{.underline} [TITLE]{.underline} [DATE]{.underline}

52.204-6 Data Universal Numbering System (DUNS) Number OCT 2003

52.214-34 Submission of Offers in the English Language FEB 2000

52.214-35 Submission of Offers in U.S. Currency FEB 2000

16. Facilities Capital Cost of Money OCT 1997

52.215-1 INSTRUCTIONS TO OFFERORS -- COMPETITIVE ACQUISITION --

WITH ALTERNATIVE I OCT 1997

24. Pre-award On-Site Equal Opportunity Compliance

Review FEB 1999

46. Evaluation of Compensation for Professional

Employees FEB 1993

52.237-10 Identification of Uncompensated Overtime OCT 1997

**L.2 FAR 52.252-5 AUTHORIZED DEVIATIONS IN PROVISIONS (APR 1984)**

(a) The use in this solicitation or contract of any Federal Acquisition
    Regulation (48 CFR Chapter 1) provision with an authorized deviation
    is indicated by the addition of "(DEVIATION)" after the date of the
    provision.

(b) The use in this solicitation or contract of any Commerce Acquisition
    Regulation provision with an authorized deviation is indicated by
    the addition of "(DEVIATION)" after the name of the regulation.

**L.3 CAR 1352.252-71 REGULATORY NOTICE (MAR 2000)**

Offerors are advised that certain provisions and clauses identified with
a Commerce Acquisition Regulation (CAR) notation for identification
purposes have not yet been binding for this acquisition and will be
contained in the CAR at Part 13 of Title 48 of the Code of Federal
Regulations.

**L.4 CAR 1352.215-73 INQUIRIES (MAR 2000)**

Offerors must submit all questions concerning this solicitation in
writing via the website at <dir.fdca.pmo@census.gov>. Questions must be
received no later than June 27, 2005. All responses to the questions
will be made in writing and included in an amendment to the
solicitation.

L.5 CAR 1352.233-71 SERVICE OF PROTESTS (MAR 2000)

An agency protest may be filed with either (1) the Contracting Officer
or (2) at a level above the Contracting Officer, with the agency Protest
Decision Authority. See 64 Fed. Reg. 16,651 (April 6, 1999) - (Internet
site:
[http://oamweb.osec.doc.gov/conops/reflib/alp1296.htm)]{.underline} for
the procedures for filing agency protests at the level above the
Contracting Officer (with the Protest Decision Authority).

Agency protests filed with the Contracting Officer **shall** be sent to
the following address:

Contracting Officer\
U.S. Census Bureau\
Acquisition Division\
Room G-314, FB 3, Stop 1700\
Washington, DC 20233

If a protest is filed with either the Protest Decision Authority or with
the General Accounting Office (GAO), a complete copy of the protest
(including all attachments) **shall** be served upon the Contracting
Officer and Contract Law Division of the Office of the General Counsel
within one day of filing with the Protest Decision Authority or with
GAO. Service upon the Contract Law Division **shall** be made as
follows:

> U.S. Department of Commerce
>
> Office of the General Counsel
>
> Contract Law Division -- Room 5893
>
> Herbert C. Hoover Building
>
> 14^th^ Street and Constitution Avenue, NW
>
> Washington, DC 20230
>
> Attn: Mark Langstein, Esquire

L.6 TYPE OF CONTRACT

The Government anticipates a contract structure with multiple incentives
applied to various elements such as Cost Plus Award Fee (CPAF), Cost
Plus Incentive Fee (CPIF), and Firm Fixed Price (FFP). The cost
reimbursement line items will be "completion" and not "term". Offerors
**shall** propose the contract type for each contract line item and the
incentive arrangements for each incentive line item, for Government
evaluation. The purpose of the "hybrid type" contract is to motivate the
Contractor to strive for outstanding performance and results in all
areas of the contract.

**L.7 COMPETITIVE RANGE**

The Census Bureau intends to evaluate proposals and award a contract
after conducting discussions with Offerors whose proposals are
determined to be within the competitive range. Offerors considered
within the competitive range are those Offerors that the Contracting
Officer considers the most highly rated proposals, or if the Contracting
Officer determines that the number of proposals that would otherwise be
in the competitive range exceed the number at which an efficient
competition can be conducted, the Contracting officer will limit the
number of proposals in the competitive range to **three** Offerors.

**L.8 EVALUATION SUPPORT**

Offerors are advised that the Government may utilize outside Contractors
and/or Consultants to assist in the evaluation of proposals. These
outside Contractors will have access to any and all information
contained in the Offerors' proposals, and will be subject to appropriate
conflict of interest standards and confidentiality restrictions.

L.9 SUBMISSION OF OFFERS

> Offerors **shall** submit to the address below, their proposal
> materials by 3:00 p.m. Eastern Time in accordance with the dates
> specified in Section L.14. Offers received at this destination after
> the time and date specified for receipt **shall** be considered
> non-compliant.

\(a\) MARKINGS: It is important that the offer is sealed and the outer
envelope or wrapping of the offer is addressed as follows:

Mailing Address: U.S. Census Bureau

Attn: Michael L. Palensky

Room G-314, FB 3, Stop 1700

Washington, DC 20233

Solicitation No.: YA1323-05-RP-0009

> (NOTE: Failure to mark the outer cover could cause the offer to be
> misdirected and received too late at the required destination.)

\(b\) Offers **shall** be mailed or hand-carried to the office cited
above and also cited in SF 33, block 7.

\(c\) If sent via FedEx, UPS or similar delivery services, offers must
be delivered to the physical address below by the time and date
specified in L.9 above.

Physical address: U.S. Census Bureau

> Attn: Michael L. Palensky
>
> 4700 Silver Hill Road

Room G-314, FB 3, Stop 1700

Suitland, MD 20746

**L.10 AMENDMENTS TO PROPOSAL**

Any changes to a proposal made by an Offeror after its initial
submission **shall** be submitted following the same instructions in
this section for the appropriate volume to the following address:

Mailing Address: U.S. Census Bureau

Attn: Michael L. Palensky

Room G-314, FB 3, Stop 1700

Washington, DC 20233

Physical address: U.S. Census Bureau

> Attn: Michael L. Palensky
>
> 4700 Silver Hill Road

Room G-314, FB 3, Stop 1700

Suitland, MD 20746

Changes **shall** be described in summary format and the
changes/replacement pages **shall** be clearly identifiable. Changes
from the original page **shall** be indicated on the outside margin by
vertical lines adjacent to the change. The Offeror **shall** include the
date of the amendment at the bottom of the changed pages.

L.11 ACCEPTANCE OF PROPOSALS

Regarding acceptance of proposals:

> \(a\) The Government reserves the right to consider as acceptable only
> those proposals submitted according to all technical requirements
> stated or referenced in this solicitation that demonstrate an
> understanding of the problems involved and the scope of the project.

\(b\) Alternate proposals will not be evaluated.

L.12 RESERVED

L.13 PRIME CONTRACTOR RESPONSIBILITIES

The selected Offeror **shall** be held responsible as the Prime Systems
Integrator Contractor for the procurement of all services required under
this contract. The selected Offeror **shall** also be held responsible
by the Government for performance of all Contractor obligations under
any contract and subcontract(s) resulting from their proposal. The
Government will render all payments due for services performed solely to
the Prime System Integrator Contractor.

**L.14** **ANTICIPATED AWARD DATE AND MILESTONE SCHEDULE**

The anticipated contract award date is on or about March 31, 2006, but
may be earlier or later than this date. The anticipated effective date
of the contract will be the award date of the contract. The Government
is not obligated to award the contract on this date.

Milestones for submission of proposals and evaluation are as follows:

Questions Related to the RFP Due: *June 27, 2005*

> Advance Proposal Materials Due: *July 8, 2005*

-   ~~Similar Experience Matrix Template Attachment L.1~~

```{=html}
<!-- -->
```
-   Organizational Performance Questionnaire Attachment L.2

-   Individual's Performance Questionnaire Attachment L.3

> [Full Proposals Due]{.underline}: *July 18, 2005*
>
> **Exception**: Oral Presentation Charts, Cost Proposals [and Letters
> of Commitment]{.underline} Due: *August 15, 2005*
>
> Competitive Range Determination: *September 2, 2005*
>
> Initial Oral Presentations/Discussions: *September 5- 23, 2005*
>
> Prototype Development/Technical Exchange: *September 26, 2005 --
> December 2, 2005*
>
> Government Delivers Data Files for Offeror's Prototype: *October 3,
> 2005*
>
> Prototype Field Demonstration and Test Plan Due: *November 1, 2005*
>
> Logistics and Telecommunication Analyses Due: *November 14, 2005*
>
> Government Approves Prototype Field Demonstration and Test Plan:
> *November 18, 2005*
>
> Prototype Test Demonstration by Offeror: *December 5--9, 2005*
>
> Prototype Oral Presentation and Discussions: *December 12 --16, 2005*
>
> Request for Final Revisions: *December 19, 2005*
>
> Final Proposal Revisions Due*: January 20, 2006*
>
> Contract Award: March 31*, 2006*

**L.15 NORTH AMERICAN INDUSTRY CLASSIFICATION SYSTEM (NAICS) CODE FOR
SUBCONTRACTORS**

> \(a\) [In accordance with]{.underline} ~~As stated in~~ FAR provision
> 52.219-1, ~~Section K, at paragraph K.9~~ entitled "SMALL BUSINESS
> PROGRAM REPRESENTATION," the NAICS code for this solicitation is
> 541512, "Computer Systems Design Services" that has an associated size
> standard of \$21,000,000.
>
> \(b\) Subcontracted work need not be classified as NAICS Code 541512.
> It should be classified under the NAICS Code that is appropriate for
> the work. The size standard for that NAICS Code can be used to
> determine if subcontracting goals are met.
>
> **L.16 WRITTEN PROPOSAL, ORAL PRESENTATION/DISCUSSIONS, AND PROTOTYPE
> DEVELOPMENT INSTRUCTIONS**
>
> \(a\) Offerors **shall** submit a four-volume written proposal in
> accordance with Section L.9. A prototype of the Mobile Computing
> Environment (MCE) **shall** be produced and field tested during the
> technical exchange and submitted in accordance with the schedule at
> L.14. Design requirements for the MCE are in Section J.
>
> \(b\) In addition to the written proposal, Offerors **shall** also
> make Oral Presentations to the Government. In the event there is a
> discrepancy between the written proposal and the oral presentation,
> the written proposal takes precedence. Oral Presentations **shall** be
> conducted in accordance with the instructions in Section L.16.1.7.

(c) If an Offeror fails to submit both a written proposal and conduct an
    oral presentation as scheduled, the Government will consider the
    entire offer to be non-responsive.

(d) Offerors **shall** submit only the information required by this
    section. Marketing literature, marketing or product videos,
    catalogs, manuals, product literature, or other extraneous
    information, either electronic or hard copy, provided with the
    proposal will not be reviewed or utilized in the evaluation.

(e) Any questions related to the RFP **shall** be submitted via email
    directly to the Census Bureau at <dir.fdca.pmo@census.gov> by *June
    27, 2005.*

L.16.1 Written Proposal Organization

The following table summarizes the written proposal organization
requirements.

+----------+-------+-------+--------------------+--------------------+
| Proposal | Date  | C     | Sections           | Maximum Pages and  |
|          | Due   | opies |                    | Special            |
| Volume   |       |       |                    | Instructions       |
+==========+=======+=======+====================+====================+
| **Volume | ~~    | Six   | **Similar          | Template provided; |
| I:**     | 7/8/2 | (6)   | Experience**       | up to ten (10)     |
|          | 005~~ | CD-   |                    | projects may be    |
| Similar  |       | ROMs; | **Section 1**      | cited, with the    |
| Ex       | [7/   | one   |                    | Project            |
| perience | 18/20 | (1)   | Similar Experience | Description/       |
|          | 05]{. | ori   | Project References | Approach portion   |
| and      | under | ginal | (Attach. L.1)      | not to exceed one  |
|          | line} | and   |                    | (1) page.          |
| Past     |       | fi    | **Past             | References         |
| Per      | [7    | fteen | Performance**      | **shall** **not**  |
| formance | /8/20 | (15)  |                    | exceed four (4)    |
|          | 05]{. | hard  | 12. **Section 2**  | pages for each     |
|          | under | c     |                    | project.           |
|          | line} | opies | Past Performance   |                    |
|          |       |       | (Attach. L.2)      | The Offerors       |
|          |       |       |                    | **shall** mail the |
|          |       |       |                    | attached           |
|          |       |       |                    | questionnaires     |
|          |       |       |                    | directly to the    |
|          |       |       |                    | references.        |
|          |       |       |                    |                    |
|          |       |       |                    | In the proposal,   |
|          |       |       |                    | provide the list   |
|          |       |       |                    | of references with |
|          |       |       |                    | complete contact   |
|          |       |       |                    | information. **No  |
|          |       |       |                    | page limitation.** |
+----------+-------+-------+--------------------+--------------------+
| **Volume | 7/18  | Six   | > **Technical      | **100 pages**      |
| II:**    | /2005 | (6)   | > Approach -       |                    |
|          |       | CD-   | > Section 1**      | [No                |
| Te       | [1    | ROMs; |                    | limit              |
| chnical, | 1/14/ | one   | Mobile Operations  | ation]{.underline} |
|          | 05]{. | (1)   |                    |                    |
| **Manag  | under | Orig  | 3.  Office         | [No                |
| ement,** | line} | inal, |     Operations     | limit              |
|          |       | and   |                    | ation]{.underline} |
| **and    | [1    | fi    | 4.                 |                    |
| Key      | 1/14/ | fteen | Telecommunications |                    |
| P        | 05]{. | (15)  |                    |                    |
| ersonnel | under | hard  | 5.  Support        |                    |
| Appr     | line} | c     |                    |                    |
| oaches** |       | opies | 6.  Security       |                    |
|          |       |       |                    |                    |
|          |       |       | 7.  Logistics      |                    |
|          |       |       |     Analysis       |                    |
|          |       |       |                    |                    |
|          |       |       | 8.  Telecom        |                    |
|          |       |       |     Analysis       |                    |
+----------+-------+-------+--------------------+--------------------+
|          | 7/18  |       | > **Program        | 30 pages           |
|          | /2005 |       | > Management**     |                    |
|          |       |       | >                  | Exception:         |
|          | 7/18  |       | > **Section 2**    |                    |
|          | /2005 |       | >                  | D and E are not    |
|          |       |       | > A. FDCA Mgmt.    | included in the    |
|          | 7/18  |       | > Approach         | 30-page limit.     |
|          | /2005 |       | >                  |                    |
|          |       |       | > B. Org.          |                    |
|          | 7/18  |       | > Structure        |                    |
|          | /2005 |       | >                  |                    |
|          |       |       | > C. Org.          |                    |
|          | 8/15  |       | > Resources        |                    |
|          | /2005 |       | >                  |                    |
|          |       |       | > D. CWBS & Proj.  |                    |
|          |       |       | > Sch.             |                    |
|          |       |       | >                  |                    |
|          |       |       | > E. Subcontract   |                    |
|          |       |       | > and Subcontract  |                    |
|          |       |       | > Participation    |                    |
|          |       |       | > Plan             |                    |
+----------+-------+-------+--------------------+--------------------+
|          | 7/8   |       | **Key Personnel**  | []{.mark}          |
|          | /2005 |       |                    |                    |
|          |       |       | Section 3 --       | []{.mark}          |
|          | ~~    |       |                    |                    |
|          | 7/8/2 |       | A. Individual's    | []{.mark}          |
|          | 005~~ |       | Performance        |                    |
|          |       |       | Questionnaire      | A. Template        |
|          | 7/18  |       |                    | provided no page   |
|          | /2005 |       | (Attach. L.3)      | limit              |
|          |       |       |                    |                    |
|          | ~~    |       | B. Resume          | []{.mark}          |
|          | 7/8/2 |       | Summaries          |                    |
|          | 005~~ |       |                    | []{.mark}          |
|          |       |       | []{.mark}          |                    |
|          | 8/15  |       |                    | B. 3 pages per     |
|          | /2005 |       | C. Letters of      | Summary            |
|          |       |       | Commitment         |                    |
|          |       |       |                    | []{.mark}          |
|          |       |       | []{.mark}          |                    |
|          |       |       |                    | C. Scanned images  |
|          |       |       |                    | acceptable. One    |
|          |       |       |                    | (1) required from  |
|          |       |       |                    | each key person    |
|          |       |       |                    | and one (1) page   |
|          |       |       |                    | limit per letter.  |
|          |       |       |                    |                    |
|          |       |       |                    | []{.mark}          |
|          |       |       |                    |                    |
|          |       |       |                    | []{.mark}          |
+----------+-------+-------+--------------------+--------------------+
| **Volume | 8/15  | Six   | **Oral             | No page limitation |
| III:**   | /2005 | (6)   | Presentations**    | -- Must be able to |
|          |       | CD-   |                    | cover all slides   |
| **Oral   |       | ROMs; | **Section 1**      | during oral        |
| Present  |       | one   |                    | presentation time  |
| ations** |       | (1)   | Oral Presentation  | allotted           |
|          |       | Orig  | Format             |                    |
|          |       | inal, |                    |                    |
|          |       | and   | > Key Personnel    |                    |
|          |       | fi    | >                  |                    |
|          |       | fteen | > Similar          |                    |
|          |       | (15)  | > Experience       |                    |
|          |       | hard  | >                  |                    |
|          |       | c     | > Program          |                    |
|          |       | opies | > Management       |                    |
|          |       |       | >                  |                    |
|          |       |       | > Technical        |                    |
|          |       |       | > Approach         |                    |
+----------+-------+-------+--------------------+--------------------+
| **Volume | 8/15  | Six   | **Cost Proposal**  | No page limitation |
| IV:**    | /2005 | (6)   |                    |                    |
|          |       | CD-   |                    |                    |
| **Cost   |       | ROMs; |                    |                    |
| Pr       |       | one   |                    |                    |
| oposal** |       | (1)   |                    |                    |
|          |       | orig  |                    |                    |
|          |       | inal, |                    |                    |
|          |       | and   |                    |                    |
|          |       | seven |                    |                    |
|          |       | (7)   |                    |                    |
|          |       | hard  |                    |                    |
|          |       | c     |                    |                    |
|          |       | opies |                    |                    |
+----------+-------+-------+--------------------+--------------------+

L.16.1.1 Submission of Written Proposal Material

Offerors **shall** submit written proposals on CD-ROMs and in hard copy.
CDs **shall** be marked clearly. The same file naming conventions
(defined below) **shall** be used.

> \(a\) Volumes I, II, and III may be placed together on one (1) set of
> CD-ROMs, while Volume IV **shall** be on a separate set of CD-ROMs.
> CDs must be readable on an IBM PC-compatible system running Windows XP
> 2003 or higher.
>
> \(b\) Each CD-ROM **shall** be clearly labeled, and each label
> **shall** state the following:
>
> \(1\) Offerors' name
>
> \(2\) Solicitation number
>
> \(3\) Date of the submission
>
> \(4\) Proposal volume (name, number) contained on the CD-ROM
>
> \(c\) If more than one CD-ROM is required for a volume, each CD-ROM
> **shall** be labeled as Disk \"x\" of \"y\" (e.g., Disk 1 of 2).
>
> \(d\) If there are any discrepancies between the electronic version
> and the hard copy version submitted in response to this RFP, the hard
> copy version **shall** take precedence.

L.16.1.2 Table of Electronic Submission Requirements and File Naming
Conventions

> Electronic files **shall** be named in accordance with the following
> conventions.

+-------------+--------------------------+-----------------------------+
| Vol         | Format                   | File Naming Convention      |
| ume/Section |                          |                             |
+=============+==========================+=============================+
| **Volume    |                          |                             |
| I**         |                          |                             |
+-------------+--------------------------+-----------------------------+
| Section 1   | Both Microsoft Word      | **FDCA2010 Vol I Sec        |
|             | (.doc) and Adobe Acrobat | 1\_\[Offerors               |
| Similar     | Portable Document        | name\]\_\[date\].pdf**      |
| Experience  | Formats (.pdf), current  |                             |
|             | versions                 | **name\]\_\[date\].doc**    |
|             |                          |                             |
|             |                          | Abbreviations are           |
|             |                          | acceptable for Offerors     |
|             |                          | name, e.g., Census Bureau  |
|             |                          | BOC                         |
+-------------+--------------------------+-----------------------------+
| Section 2   | Both Microsoft Word      | **FDCA2010 Vol I Sec        |
|             | (.doc) and Adobe Acrobat | 2\_\[Offerors               |
| Past        | Portable Document        | name\]\_\[date\].pdf**      |
| Performance | Formats (.pdf), current  |                             |
|             | versions                 | **name\]\_\[date\].doc**    |
+-------------+--------------------------+-----------------------------+
| **Volume    |                          |                             |
| II**        |                          |                             |
+-------------+--------------------------+-----------------------------+
| ####        | Both Microsoft Word      | **FDCA2010 Vol II Sec       |
|   Section 1 | (.doc) and Adobe Acrobat | 1\_\[Offerors               |
|             | Portable Document        | name\]\_\[date\].pdf**      |
| Technical   | Formats (.pdf), current  |                             |
| Approach    | versions                 | **name\]\_\[date\].doc**    |
|             |                          |                             |
|             |                          | Abbreviations are           |
|             |                          | acceptable for Offerors     |
|             |                          | name, e.g., Census Bureau  |
|             |                          | BOC                         |
+-------------+--------------------------+-----------------------------+
| **Section   | Both Microsoft Word      | **FDCA2010 Vol II Sec       |
| 2**         | (.doc) and Adobe Acrobat | 2\_\[Offerors               |
|             | Portable Document        | name\]\_\[date\].pdf**      |
| Program     | Formats (.pdf), current  |                             |
| Mgnt        | versions                 | **name\]\_\[date\].doc**    |
|             |                          |                             |
|             | Microsoft Excel (current | **name\]\_\[date\].xls**    |
|             | version) formats; all    |                             |
|             | spreadsheets must be     | []{.mark}                   |
|             | contained in the same    |                             |
|             | workbook.                | **name\]\_\[date\].mpp**    |
|             |                          |                             |
|             | Microsoft Project(.mpp)  |                             |
|             | current version.         |                             |
+-------------+--------------------------+-----------------------------+
| **Section   | Both Microsoft Word      | **FDCA2010 Vol II Sec       |
| 3**         | (.doc) and Adobe Acrobat | 3\_\[Offerors               |
|             | Portable Document        | name\]\_\[date\].pdf**      |
| Key         | Formats (.pdf), current  |                             |
| Personnel   | versions                 | **name\]\_\[date\].doc**    |
+-------------+--------------------------+-----------------------------+
| **Volume    |                          |                             |
| III**       |                          |                             |
+-------------+--------------------------+-----------------------------+
| **Section   | ~~Both~~ Microsoft Word  | **FDCA2010 Vol III Sec      |
| 1**         | (.doc), ~~and~~ Adobe    | 1\_\[Offerors               |
|             | Acrobat Portable         | name\]\_\[date\].pdf**      |
| Oral        | Document Formats (.pdf), |                             |
| p           | current versions,        | **name\]\_\[date\].doc**    |
| resentation |                          |                             |
|             | PowerPoint (.ppt)        | **name\]\_\[date\].ppt**    |
| Format      | current versions, or any |                             |
|             | other format not listed  |                             |
|             | on this chart with prior |                             |
|             | FDCA PMO approval.       |                             |
+-------------+--------------------------+-----------------------------+
| **Volume    |                          |                             |
| IV**        |                          |                             |
+-------------+--------------------------+-----------------------------+
| **Cost      | Adobe Acrobat Portable   | **FDCA2010 Vol IV Sec 1 or  |
| Proposal**  | Document (.pdf), current | 2\_\[Offerors               |
|             | version and              | name\]\_\[date\].pdf**      |
|             |                          |                             |
|             | Microsoft Excel (current | **FDCA2010 Vol IV Sec 1 or  |
|             | version) formats; all    | 2\_\[Offerors               |
|             | spreadsheets must be     | name\]\_\[date\].xls**      |
|             | contained in the same    |                             |
|             | workbook.                | **\[Offeror                 |
|             |                          | name\]\_\[date\].doc**      |
|             | Microsoft Word (.doc)    |                             |
+-------------+--------------------------+-----------------------------+

L.16.1.3 Written Proposal Formatting Instructions

Offerors **shall** confine their submission to the established page
limitations described in this section. Cover letters, title pages, table
of contents, list of figures, acronym lists, and compliance matrices are
excluded from the page limitations. All pages in excess of the maximum
number of pages stated will not be evaluated.

Each proposal volume **shall** be bound in a separate three-ring binder
of minimum size to contain the material. A binder cover page **shall**
be affixed to the outer cover of each volume that clearly identifies
each volume with a volume number and name, copy number (i.e., copy 2 of
6), solicitation number, date of submission, and Offerors' name. This
information also **shall** appear on the spine of the binder. Tab
indexing **shall** be used to identify all sections within a particular
proposal volume. There **shall** be no writing or graphics on the tab
index page other than that required for identifying the particular
section.

The Offerors' written proposal **shall** be prepared on standard 8.5x11
inch pages. The proposal pages **shall** be numbered, printed on one
side only, and bound along the left margin. Each page **shall** have a
one-inch margin at the top and the bottom and on each side. Page
numbers, notations of proprietary material, and any other identifying
information printed on each page may be included in the margin.

Text **shall** be in Times New Roman, 11 point font; however, text
included in figures or graphics in the written proposal may be reduced
to 9 point font (Arial or Arial Narrow may also be used for figures or
graphics). Table text must maintain 11 point font. Should Offerors
require fold-out pages for graphics, one fold-out page **shall** not
exceed 17x11 inches. Fold-outs will be counted as two (2) pages,
regardless of size, and subsequent page numbering must be adjusted
appropriately.

NOTE: For spreadsheet text in the Cost Volume (Volume IV), any font and
size is permitted.

L.16.1.4 Written Proposal Content

The evaluation of the written proposals will be based on the information
presented. Therefore, organization, clarity, accuracy of information,
relevance, and completeness are of prime importance. The written
proposals **shall** be provided in four (4) volumes, as follows:

Volume I -- Similar Experience/Past Performance

Section 1 - Similar Experience

(See ATTACHMENT L.1 Similar Experience Matrix Template)

Section 2 -- Past Performance

(See ATTACHMENT L.2, Organization's Performance Questionnaire.)

Volume II -- Technical/Management/Key Personnel Approaches

Section 1 --Technical Approach including Prototype Development

Section 2 -- Program Management

Section 3 -- Key Personnel

Volume III -- Oral Presentations

Section 1 -- Oral Presentation Format

Section 2 -- Oral Presentation Facilities

Volume IV -- Cost

Section 1- General Information

Section 2 Proposal Submission Instructions

**L.16.1.5 Volume I - Similar Experience and Past Performance**

Volume I **shall** present evidence of the Offeror and its teaming
partners' similar experiences. For FDCA evaluation purposes, Similar
Experience will reflect "whether" contractors have performed work
similar in scope and magnitude to the FDCA requirements, and Past
Performance will describe "how well" contractors performed relevant
work.

The Offerors **shall** include the following sections in Volume I of
their written proposals.

L.16.1.5.1 Volume I, Section 1: Similar Experience Project References

Volume I **shall** present evidence of the Offerors' Similar Experience
as Prime Systems Integrators (to include teaming partners and
subcontractor(s)) on ten (10) contracts performed in the past five (5)
years. Contracts (commercial, Federal, state, local government and
foreign governments) of similar work and complexity related to the FDCA
effort are preferred. The Offerors' documentation of relevant experience
**shall** include a description of the specific project that also
addresses each project's characteristics, such as the level of
complexity, scale, geographic distribution, automation/technology
infusion/expansion, and operational schedule for lifecycle phases. The
Offerors **shall** prioritize Similar Experience submissions in order of
their relevancy to the FDCA, i.e., one (1) being the most relevant to
ten (10) being the least relevant in the opinion of the Offerors.
Attachment L.1 provides the Similar Experience Matrix Template.

This template must be used for all Similar Experience projects, and the
format may not be modified except to expand boxes to accommodate
additional text. The Project Description/Approach portion may not exceed
one (1) page; other portions may be expanded at the Offerors'
discretion, so long as the total pages for each project reference do not
exceed four pages. No additional items beyond the following content may
be added to the template.

(a) **Matrix Content**

```{=html}
<!-- -->
```
(1) **Contract Title/Project Name and Contract Number:** Indicate the
    name of the project as well as the title of the contract, if this
    differs from the project name. Also provide the contract or order
    number.

(2) **Performed By:** Enter the name of the company performing the work.
    If several companies on the Offerors' team are participating,
    provide all of the company names.

(3) **Major Subcontractor(s):** Enter the major Subcontractor(s)
    assigned to the contract/order, or enter "Not applicable."

(4) **Agency/Company:** Agency or company for which the work is being
    performed. If applicable, also supply the name of the division,
    group, or other organization within the agency/company. If the work
    has been contracted by one agency but performed for another, list
    both and clarify their roles.

(5) **Contracting Officer (CO):** Provide the name, mail address,
    telephone number, FAX number, and e-mail address for the contract's
    official contracting officer. The Administrative Contracting Officer
    (ACO) may be substituted for the CO. The Government reserves the
    right to contact this reference, so Offerors must ensure the current
    validity of this information.

(6) **Contracting Officer's Technical Representative (COTR):** Provide
    the name, mail address, telephone number, FAX number, and e-mail
    address for the COTR. The Government reserves the right to contact
    this reference, so Offerors must ensure the current validity of this
    information.

(7) **Other Technical Point of Contact (POC):** Provide the name, mail
    address, telephone number, FAX number, and e-mail address for an
    additional technical POC from the customer organization who is
    knowledgeable of the Offerors' performance on this project. The
    Government reserves the right to contact this reference, so Offerors
    must ensure the current validity of this information. If the
    referenced contract is with a non-government organization, provide
    contracting points of contact here.

(8) **Period of Performance:** Indicate, by month and year, the start
    and completion (or "ongoing") dates for the project, contract, or
    order. State original completion date, and if applicable, revised
    completion date.

(9) **Contract Type and Total Value:** Enter the contract's (or order's)
    type (Cost Plus, Incentive, Award Fee, IDIQ, FFP, T&M, etc.). Enter
    the original total dollar value of the contract and the current
    dollar value, if different. If contract type was different for
    project phases, list all applicable contract types.

(10) **Product/Service Provided**: If the performing company did not
     perform all aspects of the project, then state which portion(s) it
     did perform.

(11) **Small Business Participation:** Indicate the small business
     participation goals set for the contract and the extent to which
     the Offerors attained the applicable goals, if the contract
     required subcontracting goals or plans. If goals or plans were not
     required, enter "Not Applicable."

(12) **Awards, Recognitions, and Certifications Received:** List all
     awards (to include award fees, in chronological order),
     recognition, and additional contract work (not including no-cost
     extensions) received on the program. Enter any quality,
     engineering, or process awards, certifications, and ratings
     received for the work on this project.

> \(13\) **Project Description and Approach:** Describe the technical
> and management approach developed and used in the formulation of a
> solution to the project, including tools and methodologies. This
> portion should focus on demonstrations of effectiveness in terms of
> management, technical implementation, and costs.

[]{.mark}

> \(14\) **Relevancy of Similar Experience:**

a\. Describe briefly the reference project, what it accomplished, and
your role.

> b\. Describe in detail the work you managed or performed in this
> project that demonstrates:

-   Experience in executing similar large, geographically dispersed,
    complex operational support systems, utilizing the same or similar
    technologies as FDCA.

-   Implementation of a comprehensive security program, including both
    physical and data security for a complex project that includes: 1) a
    large and dispersed user population that interfaces with the
    public; 2) both office and mobile systems; and 3) a nationwide
    telecommunications network.

-   Implementation of software process lifecycle and hardware design and
    manufacturing methodologies.

-   Implementation of nation-wide deployment and support process
    methodologies.

-   Integration of systems and services with other (external)
    contractors and the Government; Experience in applying lessons
    learned from previous projects.

-   Experience in rapid development and deployment of system
    modifications in an operational environment.

-   Complexity of the project, meaning the technical innovation required
    in applying new technologies, extensive interactions with various
    stakeholders/users and other Contractors.

-   Extensive security requirements, geographic dispersion of system
    components and users, and the management of all related elements of
    the project.

L.16.1.5.2 Volume I, Section 2: Organizational Performance Questionnaire
(Past Performance Questionnaire)

The Offerors **shall** contact past performance references directly and
request that they complete and submit the attached past performance
questionnaires to the Government by July 8, 2005. Offerors **shall**
request that their references email the organization past performance
questionnaire directly to the Census Bureau at
<dir.fdca.pmo@census.gov>. If email is not available, they may mail the
questionnaire to the Government address listed in Section 9 or FAX their
references to 301-457-8465.

The Offerors **shall** submit in a Microsoft Word file by July 8, 2005
their list of respondents from whom the Government is expected to
receive past performance questionnaires. The Government will provide the
Offerors with confirmation of received/non-received past performance
questionnaires by July 12, 2005 so that the Offerors may follow-up with
non-received past performance questionnaires. After July 15, 2005, the
Government will follow-up with references to help facilitate receipt of
non-received past performance questionnaires. Attachment L.2
(**Organization's Performance Questionnaire**) provides the
questionnaire to be sent to the Offerors' references.

L.16.1.6 Volume II, Section 1: Technical Approach

Volume II **shall** address both technical and program management
aspects of the work proposed for FDCA. The Technical Approach is defined
as the tools, methodologies, processes, and plans for accomplishing the
work in the SOW, Section C, using a total system approach.

The Program Management Approach is defined as the Offerors'
capabilities, as well as intentions, in regards to management of the
project: the application of knowledge, skills, tools, resources, and
techniques to project activities to meet project requirements.

The Offerors **shall** include the following sections/subsection(s) in
Volume II of their written proposals.

**L.16.1.6.1 Volume II: Technical Approach to Field Staff Operations**

Offerors **shall** develop a detailed approach, reflecting the steps
(methodology) the Offerors will take to fully design, build, test,
deploy, implement, operate, monitor, maintain, secure, and then dispose
of the systems, infrastructure, staffing, training, supplies,
procedures, and other deliverables as required to support the Field
Operations. Offerors **shall** specifically discuss their approach as it
relates to Address Canvassing, Census Coverage Management, Non Response
Follow-Up, and administrative operations function of the 500,000 field
office supervisors, crew leaders, enumerators, listers, and interfaces
to Census Bureau systems.

L.16.1.6.1.1 Volume II: Mobile Computing Environment Approach

The Offerors **shall** include in their initial proposals, a high-level
system design for a prototype of their Mobile Computing Environment
(MCE) (See Attachment L.4 for Prototype Development Instructions). The
MCE will be further defined during the technical exchange period with
the Government. ~~At the end of this period, Offerors **shall** submit
the actual device for Government field-testing during the evaluation of
their final revisions.~~ The final revision ~~documentation~~
[proposals]{.underline} **shall** include a discussion of how the MCE
**shall** support the field operation by possessing the required
characteristics outlined in Section C 5.1. Specifically, the Offerors
**shall** discuss the final design, packaging, usability, and
maintainability.

**L.16.1.6.1.2 Volume II: Office Operations**

The Offerors **shall** develop a detailed approach, reflecting the steps
(methodology) the Offerors will take to provide and integrate all
automation and telecommunications hardware, software, and systems for
the 12 RCCs plus Puerto Rico Area Office (PRAO), and 455 LCOs. A limited
portion of the Office Computing Environment (OCE) Operational Control
(OC) Functionality **shall** be required in the Prototype (See
Attachment L.4 for Prototype Development Instructions). Offerors'
submissions **shall** cover the detailed requirements for Office
Operations as outlined in Section C 5.2.

L.16.1.6.1.3 Volume II: Telecommunications

The Offerors **shall** describe a detailed approach to fully enable
Local Area Network (LAN), (WAN), Voice, and Data telecommunications for
the RCCs, LCOs, and the Field Staff's Mobile Computing Environment, with
the systems in the RCCs and LCOs capable of receiving the millions of
transmissions and connects per day from the field staff. A limited
portion of the Telecommunications functionality **shall** be required in
the Prototype (See Attachment L.4 for Prototype Development
Instructions). Offerors' responses **shall** cover the detailed
requirements for Telecommunications as outlined in Section C 5.3.

L.16.1.6.1.4 Volume II: Support

The Offerors shall describe in detail their approach to providing Help
Desk, Hardware/Software Management/Repair/Replacement, and Training
Designs/Materials/Products support as required to effectively manage all
the work described in Section C5.4.

L.16.1.6.1.5 Volume II: Security

#### The Offerors shall describe all steps planned to fully secure all telecommunications, automation, and electronic storage for Title 13 data on all deliverables. Offerors' responses shall cover all requirements as outlined in Section C5.5. 

#### L.16.1.6.1.6 Volume II: Logistics Analysis

Offerors **shall** provide a detailed written logistics analysis,
supported by a model and/or simulation, describing and validating the
Offeror's Mobile Computing Environment (MCE) and Office Computing
Environment (OCE) logistics approaches across the entire FDCA project
and lifecycle (i.e., manufacturer to end user, initial deployment to
disposition). This analysis **shall** incorporate a formal risk analysis
methodology (e.g., qualitative, tree-based, etc.) as the Offeror deems
appropriate.

**L.16.1.6.1.7 Volume II: Telecommunication Analysis**

The Offerors **shall** provide a detailed written telecommunications
analysis, supported by a model and/or simulation, describing and
validating the data telecommunications architecture under full loading,
which validates that the architecture will effectively handle the data
and processing loads required for normal and peak operations for the
following components:

-   Communication backbone (e.g., circuits between offices, MCEs, etc.)

-   Communications backbone components (e.g., switch, router, hub, etc.)

-   Any proposed central or distributed server systems for the solution
    (e.g., email solutions, assignment transmission and receipt servers,
    etc.)

-   OCE (e.g., LAN, servers, printers, PCs, etc.)

-   MCE

This analysis **shall** incorporate a formal risk analysis methodology
(e.g., qualitative, tree-based, etc.) as the Offeror deems appropriate.

L.16.1.6.2 Volume II, Section 2: Program Management

**L.16.1.6.2.1** **Volume II: FDCA Management Approach**

The FDCA Management Approach should discuss the Offerors' planned
management processes for the FDCA contract. Offerors **shall** include
discussion of relevant tools and methodologies. Offerors **shall**
demonstrate a thorough understanding of the technologies and
methodologies to be employed, their expected results, and performance
standards. Relevant topics include staffing, contracting and
subcontracting, metrics, quality assurance, security, configuration
management, approach to deliverables, logistics support, earned value
management and cost control, financial reporting, inventory management
and disposition, Section 508, and contract closeout. The Offerors
**shall** provide a written outline of the Program Management Plan with
their initial proposal.

**L.16.1.6.2.2 Volume II: Organizational Structure**

The Offerors **shall** describe their planned Organizational Structure
for the FDCA program. Considerations to address include reporting
structure, team organization, division of responsibilities, and
interaction with the Census Bureau organization.

**L.16.1.6.2.3 Volume II: Organizational Resources**

The Offerors **shall** explain how they will provide the required
resource infrastructure and or backup staffing resources. Relevant
organizational resources would include corporate contracting staff,
billing and accounting staff and systems, human resources/recruiting,
training, and limited use of expert resources. Particularly relevant is
the organization's ability to provide quality staff for peak workload
volumes throughout the contract.

#### L.16.1.6.2.4 Volume II: Contract Work Breakdown Structure (CWBS) and Project Schedule

#### L.16.1.6.2.4.1 Contract Work Breakdown Structure

The Offerors **shall** propose a product/deliverable oriented Contract
Work Breakdown Structure (CWBS) reflecting their plan for breaking the
work into detailed work elements with weighted milestones (described
further in L.16.1.6.2.4.2.). The Offerors **shall** describe the role
their WBS dictionaries will play to support the Scope Management of
FDCA**.** In addition, the Offerors **shall** provide samples from a WBS
dictionary they would propose using on FDCA. The WBS dictionary's
description and samples are the only narrative information permitted.
After Contract Award, the selected vendor **shall** mature the narrative
descriptions in a (CM controlled) WBS Dictionary using inputs from the
Basis of Estimates (reference L.16.1.8.1, volume IV, Cost Proposal,
section "b" *Cost Proposal General Instructions*) and other project
documentation; see Section C 5.6.

**L.16.1.6.2.4.2 Project Schedule:**

[The Offerors **shall** propose a Project Schedule. The Project Schedule
**shall** include WBS identifier groupings for each schedule entry,
weighted milestones, and resources required for preliminary planning of
subsequent phase(s). If Labor Resources are offered within the
Offeror\'s July 18th submission, high-level Labor Resource
categorizations are acceptable for this purpose. Specific details of
Labor Resources shall be provided with the cost proposals due on August
15, 2005.]{.underline}

**L.16.1.6.2.4.2.1 Integrating Schedules**

Integrating Schedules with Milestones and Payments --The project
schedule tools and processes proposed by Contractor(s) **shall** be
capable of supporting/correlating to a methodology similar to a concept
that uses a schedule of values. Performance Based Payments and the
schedule of values concept are methodologies the Census Bureau is
considering in an overall integrated baseline that firmly links
progress, invoices, payments and the measurements of Earned Value.

L.16.1.6.2.5 Volume II: Subcontracting Plan and Subcontract
Participation Plan

The Offerors **shall** submit a subcontracting plan for this
acquisition. The plan must be submitted in accordance with FAR Part 19,
with specific attention paid to FAR 19.704 and FAR 52.219-9.

The Offerors **shall** show each Subcontractor's business size, as well
as the estimated percentage and types of work to be subcontracted.

All prospective Subcontractors contacted by an Offeror in any manner
**shall** be expressly advised in writing that no solicitation **shall**
be construed in any manner to be an obligation on the Offerors' part to
enter into a subcontract with said Subcontractor. Nor **shall** any
contract result in any claim whatsoever against the United States
Government for reimbursement of costs for any efforts expended by said
Subcontractor, regardless of whether or not the Offerors is awarded a
contract.

The Offerors **shall** subcontract a minimum of 20 percent *of the
**total contract price*** to small business concerns[. Offerors may use
2nd and 3rd tier subcontractors to meet the subcontract minimum of 20
percent of total contract price.]{.underline}

The Offerors **shall** note that the current (FY2004) subcontracting
goals (expressed in terms of a percentage of total planned
subcontracting dollars) for the Department of Commerce
[www.osec.doc.gov](http://www.osec.doc.gov/) are as follows (FY2004):

Small businesses (includes all below) 44.8 %

Small disadvantaged businesses 10.35 %

8(a) 6.11%

Women-owned small businesses 7.8%

> Hubzone small businesses 3.0%
>
> Veteran-Owned Small Businesses 4.0%
>
> Service-disabled Veteran-Owned Small Businesses 3.0%

The Offerors **shall** propose goals for the use of small businesses for
each category below, expressed in terms of percentages of total planned
subcontracting dollars for this contract:

Small businesses (includes all below) \_\_\_\_ %

Small disadvantaged businesses \_\_\_\_ %

8(a) \_\_\_\_ %

Women-owned small businesses \_\_\_\_%

> Hubzone small businesses \_\_\_\_%
>
> Veteran-Owned Small Businesses \_\_\_\_%

Service-disabled Veteran-Owned Small Businesses \_\_\_\_%

> ![](media/image1.wmf){width="0.5701388888888889in"
> height="7.847222222222222e-2in"}
>
> Total small business percentage \_\_\_\_\_ %

The Offerors **shall** submit a Subcontract Participation Plan. This
plan **shall** include identification of the functions/performance areas
the Offerors intend to subcontract. It **shall** also include the scope,
the estimated subcontract value, and labor categories/hours to be
subcontracted. The Offerors **shall** include any plans to mentor
emerging and other small businesses. The Offerors **shall** include
plans to mentor small businesses to reach accreditation of SEI CMMI
level 2 or 3, and ISO 9000 (as applicable) on this project.

*[Note: The generation of estimated subcontract value and labor
categories/hours information in the Subcontract Participation Plan may
be left blank in the July 18, 2005 submission and may be submitted as
change pages with the submission of the cost proposal due on August 15,
2005.]{.underline}*

L.16.1.6.3 Volume II, Section 3: Key Personnel

**L.16.1.6.3.1** **Volume II Key Personnel Overview**

Key Personnel are defined as the sum of the skills, experience, and
education of those personnel designated as "key" in the RFP, or by the
Offerors. The Government requires that the following personnel, at a
minimum, be designated as key:

1\) Project (or Program) Manager (PM)

2\) Deputy PM(s)

3\) IT Security Manager

4\) Quality Manager

5)  System Architect

6)  Software Development Manager

7)  Telecommunication Manager

8)  Logistics Manager

9)  Technical Support Manager

10) Financial Manager

The Offerors may designate other personnel working on the FDCA contract,
either from the Prime System Integrator, teaming partner(s), or their
Subcontractor(s), as key personnel. The Offerors' Key Personnel for the
FDCA contract are subject to the Key Personnel provisions of Section
H.5. While personnel are not required to be cleared by the Government at
the time proposals are submitted, the Offerors **shall** ensure that all
key personnel proposed will be able to successfully complete the
Government's clearance process at contract award. Individuals designated
as key personnel **shall** submit a completed Government clearance
package to the Census Bureau at the time of the oral presentations. The
Census Bureau will provide these packages no later than fourteen (14)
days prior to the Oral Presentations. The Offerors **shall** ensure that
all personnel designated as key personnel for the FDCA contract are
introduced in person at the Oral Presentation and that only the key
personnel make the Oral Presentation. The Offerors **shall** provide the
following information about their key personnel:

-   Availability of qualified personnel in the minimum "key" areas
    above;

-   Years of relevant experience and skill sets in relevant fields;

-   Recognition in his/her field;

-   Relevant published papers including a full bibliographical
    reference;

-   Possession of degrees and certifications relevant to the proposed
    work;

-   Ability of the personnel to remain on the program through the
    performance of the 2010 Census;

-   Capability to apply innovations in technology; and

-   Customer satisfaction with the performance of the personnel
    (individual awards, grants, continuing business, etc.).

L.16.1.6.3.2 Volume II Individual Performance Questionnaire (Key
Personnel Past Performance Questionnaire)

The Offerors **shall** contact key personnel past performance references
directly and request that they complete and submit the attached
Individual Performance Questionnaires to the Government by July 8, 2005.
Offerors **shall** request that their references email the organization
past performance questionnaire directly to the Census Bureau at
<dir.fdca.pmo@census.gov>. If email is not available, they may mail the
questionnaire to the Government address listed in Section 9 or FAX their
references to 301-457-8465.

The Offerors **shall** submit in a Microsoft Word file by July 8, 2005
their list of respondents from whom the Government is expected to
receive past performance questionnaires. The Government will provide the
Offerors with confirmation of received/non-received past performance
questionnaires by July 12, 2005 so that the Offerors may follow-up with
the references about the non-received past performance questionnaires.
After July 15, 2005, the Government will follow-up with references to
help facilitate receipt of non-received past performance questionnaires.

Attachment L.3 (**Individual Performance Questionnaire**) provides the
questionnaire to be sent to the Offerors' references.

**L.16.1.6.3.3 Volume II Key Personnel Experience**

For personnel to be designated key, the Offerors must assure, to the
greatest extent possible, availability for the appropriate duration of
the contract. The Offerors must also indicate that the person(s) will be
dedicated full time to the project, or if not, provide an explanation.

L.16.1.6.3.4 Volume II Key Personnel Resume Summaries

The Offerors **shall** provide resume summaries for each person
designated as key, providing only relevant experience information.
Resumes are not to exceed three (3) pages each. However, Offerors are
cautioned that the Government is interested in relevant experience only,
and should utilize only the space required to convey this information.

L.16.1.6.3.5 Volume II Key Personnel Letters of Commitment

The Offerors shall provide letters of commitment that provides evidence
of the corporate intent to commit these Key Personnel in the service of
the FDCA requirement from the date of contract award through the
completion of the applicable work. A letter of commitment shall include
the name of the person whose resume is provided, and an indication of
the percentage of time the employee will be assigned to all phases of
this project. In addition, the letter of commitment shall certify that
the Government shall have full accessibility to Key Personnel on demand,
as required by the Government. A corporate official and each key person
shall sign the commitment letters. Letters should be scanned for
insertion into the proposal document, and are limited to one (1) page
each.

L.16.1.7 Volume III: Oral Presentation Instructions

**L.16.1.7.1 Volume III, Section 1: Oral Presentation Format**

The oral presentation slides for the Technical and Program Management
Approaches **shall** be prepared in accordance with the page limitations
in the table provided in Section L.16.1, "Written Proposal Organization"
and the time and table requirements in L.16.1.1 " Oral Presentation
Content." The goal of the Oral Presentations will be to expand on and
enhance the written information provided, not to repeat the written
proposal verbatim.

Hard copy presentation charts **shall** be provided on standard 8.5x11
inch paper in landscape orientation, one chart per page~~. No chart text
**shall** be smaller than 18- point~~. Charts **shall** be numbered
sequentially.

L.16.1.7.1.1 Volume III: Oral Presentations/Discussions

There will be two periods of Oral Presentations/Discussions, each period
consisting of several sessions. [Following the]{.underline}
[Initial]{.underline} [Competitive Range Determination,]{.underline}
[the]{.underline} [Contracting Officer will schedule Oral
Presentations/Discussions.]{.underline} [Each]{.underline} [Offeror that
remains in the Competitive Range will be]{.underline} [invited to Oral
Presentations and will be]{.underline} [issued discussion questions in
writing from the Contracting Officer.]{.underline} [The discussion
questions will be organized by]{.underline} [the evaluation criteria in
Section M, and will reflect the]{.underline} [Offeror's deficiencies,
significant weaknesses and risks. The]{.underline} [Offeror]{.underline}
**[shall]{.underline}** [prepare responses in writing and have them
available for discussion]{.underline} [following]{.underline} [each oral
presentation session identified in the tables below.]{.underline} [The
discussion period following each session will address the written
discussion]{.underline} [questions]{.underline} [the]{.underline}
[Offeror received as well as any additional negotiations the Contracting
Officer feels]{.underline} [are]{.underline} [necessary.]{.underline}
[Discussions will continue as long as necessary following each
session.]{.underline} [The next session (e.g.]{.underline} ["Similar
Experience") will not start until discussions are completed on
the]{.underline} [preceding session]{.underline} [(e.g., "Key
Personnel").]{.underline} [The Contracting Officer may
schedule]{.underline} [additional]{.underline} [discussions with
each]{.underline} [Offeror that do not coincide with the Oral
Presentations.]{.underline} [All discussion periods]{.underline}
[following the Oral Presentation periods]{.underline} [shall be
recorded]{.underline} [as stated in L.16.1.7.1.8.4.]{.underline}

Each Oral Presentation session **shall** begin with the identification
of the session being presented and the presenter's introduction by name,
position, and company affiliation.

Time allotted to each session, as specified in the tables below, does
not relate in any way to the relative importance of the topic in the
evaluation process. Offerors must reference Section M for this
information. Time allotments are structured merely to account for the
amount of time that the Government expects will be required to
thoroughly present each topic.

[Initial Oral Presentation (September 5 -- 23, 2005):]{.underline}

The Offerors **shall** provide an oral presentation relating to the
subject areas of their proposal to the Government. The Initial Oral
Presentations will be presented prior to the Government's technical
exchange period.

The oral presentation **shall** be sufficiently detailed, specific, and
complete to enable the Government to evaluate the presentation
thoroughly in accordance with Section M, Evaluation Factors for Award.

No new presentation slides or alterations **shall** be submitted at the
time of the Oral Presentation. Offerors **shall** only present the Oral
Presentation slides (8.5X11 inch) provided with the original proposal.
Any oral presentation slides submitted with the written proposal, but
not presented due to lack of time, will not be evaluated.

During the Technical Approach portion of the Oral Presentations, The
Offerors may choose to include within their oral presentation one (1) or
more technical demonstration(s). The demonstration is at the Offerors'
discretion; however, it must be provided within the time allotted for
the Technical Approach portion of the oral presentation.

The Initial Oral Presentation **shall** consist of the following
schedule:

+----------+-----------------------------------+-----------------------+
| **S      | **Session Name**                  | **Maximum Allotted    |
| ession** |                                   | Presentation Time**   |
|          | **Initial Oral                    |                       |
| **Each   | Presentation/Discussions**        |                       |
| O        |                                   |                       |
| fferor** |                                   |                       |
+==========+===================================+=======================+
| **Day    |                                   |                       |
| 1**      |                                   |                       |
+----------+-----------------------------------+-----------------------+
| a.m.     | Key Personnel                     | 1 hour                |
+----------+-----------------------------------+-----------------------+
|          | Discussions on Key Personnel      | Until Completed       |
+----------+-----------------------------------+-----------------------+
| a.m.     | Similar Experience                | 1 Hour                |
+----------+-----------------------------------+-----------------------+
|          | Discussions on Similar Experience | Until Completed       |
+----------+-----------------------------------+-----------------------+
| p.m.     | Program Management Approach       | 3 Hours               |
+----------+-----------------------------------+-----------------------+
|          | Discussions on Program Management | Until Completed       |
+----------+-----------------------------------+-----------------------+
| **Day    |                                   |                       |
| 2**      |                                   |                       |
+----------+-----------------------------------+-----------------------+
| a        | Technical Approach                | 6 Hours               |
| .m./p.m. |                                   |                       |
+----------+-----------------------------------+-----------------------+
|          | Discussions on Technical Approach | Until Completed       |
+----------+-----------------------------------+-----------------------+
| Day 3    |                                   |                       |
+----------+-----------------------------------+-----------------------+
| a.m.     | Impromptu Government              | 3 Hours               |
|          |                                   |                       |
|          | Presented Scenarios               |                       |
+----------+-----------------------------------+-----------------------+
|          | Remaining Discussions             | Until Completed       |
+----------+-----------------------------------+-----------------------+

> [Prototype Oral Presentation and Discussions (December 12 - 16,
> 2005):]{.underline}

Prototype Oral Presentation is the Offerors' final opportunity to
present how the prototype relates to their overall technical solution
and to show changes to the proposed technical solution prior to final
submission to the Government. The time will also be granted for the
Offerors to present their Logistics and Telecommunication Analysis as
described in Section L.16.1.6.1.6 and L.16.1.6.1.7. During the prototype
oral presentation, each Offeror is allowed 1 full day during normal
business hours (9:00 a.m.- 4:00 p.m.).

> Below is a proposed schedule. Vendors will be provided with an updated
> schedule and procedures at a later date.

+----------+-----------------------------------+-----------------------+
| **S      | **Session Name**                  | **Maximum Allotted    |
| ession** |                                   | Presentation Time**   |
|          | **Prototype Oral Presentation and |                       |
|          | Discussions**                     |                       |
+==========+===================================+=======================+
| **Day    | Offeror 1                         | 1 Day                 |
| 1**      |                                   |                       |
+----------+-----------------------------------+-----------------------+
|          | Prototype                         |                       |
+----------+-----------------------------------+-----------------------+
|          | Logistics Analysis                |                       |
+----------+-----------------------------------+-----------------------+
|          | Telecommunication Analysis        |                       |
+----------+-----------------------------------+-----------------------+
|          | Oral Discussions                  |                       |
+----------+-----------------------------------+-----------------------+
| ###      | Offeror 2                         | 1 Day                 |
| #  Day 2 |                                   |                       |
+----------+-----------------------------------+-----------------------+
| ####     | Prototype                         |                       |
+----------+-----------------------------------+-----------------------+
|          | Logistics Analysis                |                       |
+----------+-----------------------------------+-----------------------+
|          | Telecommunication Analysis        |                       |
+----------+-----------------------------------+-----------------------+
|          | Oral Discussions                  |                       |
+----------+-----------------------------------+-----------------------+
| ###      | Offeror 3                         | 1 Day                 |
| #  Day 3 |                                   |                       |
+----------+-----------------------------------+-----------------------+
| ####     | Prototype                         |                       |
+----------+-----------------------------------+-----------------------+
|          | Logistics Analysis                |                       |
+----------+-----------------------------------+-----------------------+
|          | Telecommunication Analysis        |                       |
+----------+-----------------------------------+-----------------------+
|          | Oral Discussions                  |                       |
+----------+-----------------------------------+-----------------------+

**L.16.1.7.1.2 Volume III: Oral Presentation of Key Personnel**

The Offerors **shall** introduce *all* personnel designated as "key" in
their proposal in person at the Oral Presentation, although these
personnel are not required to attend the entire presentation. *Only
personnel designated as "key" for the FDCA contract will be permitted to
make a presentation during any Oral Presentation.*

While the written proposals focus on the skills sets, degrees, years of
experience, and other relevant data for Key Personnel, the orals
presentation by Key Personnel should focus on applicable project
experience. This experience would include what projects similar in size
and scope did the personnel perform, what were their roles, what major
achievements did they accomplish on these projects and why have they
been recommended as key on FDCA? In other words, this portion of the
oral presentations should be *results-focused*.

The amount of time dedicated to the presentation of each "key" person is
at the Offerors' discretion, so long as all key personnel are discussed.

**L.16.1.7.1.3** **Volume III:** **Oral Presentation of** **Similar
Experience**

The Offerors **shall** present five (5) of the most relevant projects
from the projects referenced in the Similar Experience Project Matrices
section of the written proposals that provide evidence of the Offerors'
experience in meeting the FDCA requirements, from design through
implementation.

The Offerors **shall** present projects that specifically focus on the
integration of functions and technologies that are similar to the FDCA
integration requirements. *Offerors **shall** also focus on problem
areas they faced with each technology, and how they overcame them.*

**L.16.1.7.1.5 Volume III: Oral Presentation of Technical Approach**

\(a\) The Technical Approach portion of the oral presentations should
present the rationale for the FDCA design proposed in the written
proposal. The presentation **shall** include, factors you see
potentially changing for the 2010 implementation, how will you adjust to
this change, how the approach meets stated requirements, and how the
approach provides the Government with strong assurances that all
required tasks will be accomplished leading to what the Census Bureau
considers a successful 2010 Census.

(b) The Offerors may provide a technology demonstration as part of this
    portion of the oral presentations. It is solely at the Offerors'
    discretion to determine whether a demonstration will or will not
    occur. However, within three (3) working days following notification
    by the Government of the dates/times for the presentation, the
    Offerors must provide the Government with notice of their intent to
    provide a demonstration(s).

    c.  Offerors will not be provided with additional presentation time
        for demonstrations and any demonstration(s) must occur within
        the allotted Technical Approach oral presentation timeframe. The
        Offerors may demonstrate prototypes or existing systems, and may
        provide the presentation within the room or elsewhere within the
        Offerors' facility (bearing in mind that any time required to
        transport the group to a different location for demonstrations
        will count toward the oral presentation time).

**L.16.1.7.1.6 Volume III: Oral Presentation of** **Program Management
Approach**

The Program Management Approach portion of the Oral Presentation
**shall** discuss the rationale for the organizational structure
proposed in the written proposal. Further, it **shall** address the
major management issues and risks the Offerors expect with FDCA, and how
the management approach as written in the proposal will address these
potential problems.

#### L.16.1.7.1.7 Volume III: Impromptu Government Provided Scenarios

The Government will provide the Offerors with several program management
and technical scenarios on the third day of the oral presentation. The
Offerors **shall** prepare and complete responses to these scenarios
within three (3) hours. These questions will allow the Government to
further assess the Offerors' understanding of the FDCA risks,
operations, challenges and so forth.

L.16.1.7.1.8 Volume III, Section 2: Oral Presentation Facilities

L.16.1.7.1.8.1 Facilities

a)  Offerors **shall** provide the facility at which the oral
    presentations are to be conducted. The facility **shall** be located
    within the continental United States. The facility **shall** be
    large enough to accommodate twenty (20) Government personnel in
    addition to the Offerors' oral presentation teams. Specific
    presentation start/end times will be provided with the agenda when
    the Government selects the Offerors who will present oral
    presentations.

b)  The expectation is that three (3) work days is required to complete
    the initial Oral Presentations for each Offeror, and (1) work day
    each Offeror to complete the Prototype Oral
    Presentations/Discussions.

c)  The Offerors **shall** provide separate rooms of sufficient size for
    the Government's team to recess at any time during the Oral
    Presentations. This requirement is solely for the purpose of
    minimizing disruptions to the surrounding environment.

d)  The Offerors **shall** provide written notice to the Contracting
    Officer of the desired locations of the oral presentations
    facilities within three (3) work-days following notification by the
    Government of the dates/times for the presentations. Included in
    this notice **shall** be the names and telephone numbers of the
    Offerors' representative whom the Government should contact upon
    arrival at the facilities, information concerning site access
    procedures (if required), information concerning parking location,
    maps of the facilities (if required), building and room numbers, and
    any other logistical information that the Offerors deem necessary.

L.16.17.1.8.2 Volume III: Oral Presentations/Discussion Authorized
Attendees

> The Offerors' attendees **shall** include all presenters and any other
> personnel designated as key in the proposal. There is no limit on the
> number of presenters within a session, although there will be no
> additional time provided for introductions and/or set-up
> modifications. [The]{.underline} [Offeror shall have an authorized
> representative present during all discussion periods.]{.underline}

L.16.1.7.1.8.3 Volume III: Presentation Equipment

a)  The Offerors may use their choice of presentation equipment during
    the oral presentation (e.g., overhead projector, slide projector, or
    computer-driven projection display).

b)  The Offerors **shall** be responsible for providing the presentation
    equipment, preparing it (setting it up) prior to the start of the
    presentations, and operating it during the presentations.

**L.16.1.7.1.8.4** **Volume III: Recording of Oral
Presentations/Discussions**

a)  The Offerors **shall** provide the Government with two (2) copies of
    a recording of the oral presentations and discussion periods on
    DVD-R format before leaving the presentation site. No modifications
    to the content of the presentation whatsoever will be permitted, to
    include editing for any reason.

b)  The Offerors may keep the original master version of the
    recording(s) for their own educational purposes.

c)  The Government will allow one (1) hour after the conclusion of the
    orals presentation for the Offerors to complete the recording and
    copying process.

d)  The Offerors **shall** be responsible for providing the recording
    equipment, set-up, personnel, media, and all other required
    equipment. The Offerors must determine appropriate parameters for
    lighting, sound, and speaker placement prior to the start of
    presentations, as the orals may not be halted for any reason once
    started.

L.16.1.8 Volume IV COST PROPOSAL

L.16.1.8.1 Volume IV, Section 1: General Information

The Government will presume that the Offerors' proposals represent their
best efforts in responding to the solicitation. Inconsistencies between
promised performance and cost or price, **shall** be explained in the
proposal. Any inconsistency, if unexplained, may raise a fundamental
issue as to the Offerors' understanding of the nature and scope of the
work required and of its financial ability to perform the contract. The
burden of proof will rest with the Offeror.

> The cost proposal is not subject to page limitations; however, the
> Offerors **shall** include only the information that is pertinent to
> cost/pricing matters.
>
> **(a) This section shall contain:**

(1) A statement as to whether the accounting system of the Offerors and
    any proposed Teaming Partners is currently deemed adequate by the
    Defense Contract Audit Agency (DCAA) for determining costs
    applicable to a "cost plus" contract (The Government desires that
    the successful Offerors and Teaming Partners have an approved
    accounting system in place) and a statement as to whether or not the
    accounting system of the Offerors and any proposed Teaming Partners
    is currently deemed adequate by the Defense Contract Audit Agency
    (DCAA) for the accumulation of cost in a cost reimbursement
    contract.

(2) An explanation by the Offerors of their labor and burden estimating
    practices (e.g., how individual rates are established; what makes up
    the overhead and burden; whether average rates per labor category
    are utilized; how standard costs/rates, with variances or another
    generally accepted method, are established; and any deviations from
    standard estimating system practices existing in the proposal).

(3) Anticipated other direct costs.

(4) Corporate financial statements/information, including any takeover
    actions, for the last three (3) years.

(5) The average labor and burden rate increases/decreases of the
    Offerors and critical Subcontractors for each of the last three (3)
    fiscal years (along with supporting rationale for the
    increase/decrease).

(6) **Prime and Subcontractor Agreements.** Offerors who intend to use
    teaming agreements in performance of this contract **shall** provide
    a copy of the agreement. If proposing a joint venture, Offerors
    **shall** provide a copy of the joint venture plan/agreement

(7) **Financial Condition and Capability.** The Offerors **shall**
    discuss their current financial status and plans relative to this
    contract, including information documenting their financial
    condition and financial capability to conduct a project of the type
    and magnitude of this contract. This information **shall** be
    provided at both the corporate level and the lowest level pertinent
    to the Offerors' financial condition. If the Offerors are a
    division, subsidiary, or other business affiliate of a firm for
    which the financial information is submitted, the financial
    relationship between the parent and affiliate **shall** be clearly
    described. Include, at a minimum the following information:

> \(a\) Name and location of the company and all its divisions,
> highlighting the division(s) expected to perform the effort.

a.  Other pertinent information on financial resources available to the
    company.

```{=html}
<!-- -->
```
(8) Approval of Business Systems

> \(i\) The Government desires that the successful Offerors have
> business systems that
>
> are currently approved without conditions.
>
> \(ii\) The Offerors **shall** state whether all of the Offerors'
> systems requiring Government approval, such as purchasing, estimating,
> and property administration, are currently approved without condition.
> If not, the Offerors **shall** explain, for each system that has not
> been approved or has received conditional approval:

-   Why the system is not approved or unconditionally approved.

-   What actions the Offeror has taken to obtain approval.

-   The status of the approval; and,

-   The estimated time frame in which the Offeror expects to receive
    approval.

If the Offeror has developed any specific management procedures or
systems expressly for the FDCA contract, the Offeror **shall** include a
brief discussion in this section of the proposal.

**(b)** **Cost Proposal General Instructions**

\(1\) Cost proposals **shall** be fully supported by data adequate to
establish the reasonableness of the proposed amount. Within the Basis of
Estimates (BOE), Offerors **shall** furnish by the lowest reasonable WBS
element (reference below chart) a cost breakdown with supporting data.

Offerors **shall** cover the following topics in their cost
proposal/BOEs:

      • ~~CHART FOR~~ TRACEABILITY BETWEEN RFP'S AND BOE'S - An overall
RFP-to-BOE Cross-Reference ~~Chart~~ Matrix should be delivered. This
~~chart~~ matrix **shall** map all applicable RFP Section C Numbered
Requirement(s) to the corresponding BOE Numbers they are described in.

-   GROUND RULES AND ASSUMPTIONS - List key technical and programmatic
    conditions, estimating ground rules, and assumptions that underpin
    the estimate as a whole. Identify specific cost elements that have
    been excluded from the cost estimate. The Census Bureau recommends
    that vendors identify whether ground rules also apply evenly to
    non-development areas like Equipment, Operations and Maintenance
    (O&M).

> **Methodology Summary** -

-   Cost Estimation - Summarize the primary methodologies, factor
    libraries, models and data sources used to estimate program or
    alternative costs. Briefly state why they were selected. To
    facilitate the documentation, parameter values and factors that are
    used consistently throughout the estimate (e.g., labor rates,
    overhead factors, contract award fee percentages, quantities, scrap
    rates, etc.) can be presented in a summary table. If a table is
    used, the table **shall** list the values of the parameters and
    factors, and it **shall** explain how values were determined.

-   Risk Adjustment - Describe how the cost estimate was generated.
    Specifically, summarize how the standard cost methodologies were
    adjusted for cost estimating, technical, schedule, and other risks.
    Describe any risk analyses conducted (e.g., Monte Carlo simulation,
    identification of risk mitigation strategies) and how their results
    were used to create the cost estimate. Describe the process used to
    distribute risk dollars among WBS elements and over fiscal years.
    Specify the percentile confidence of the risk-adjusted estimate.

-   Inflation Rates - Describe the source of any inflation rates used to
    adjust from Constant Year cost estimates into Then-Year dollars.

-   Appendices-Any additional background information (e.g., model runs,
    inflation rates) that would help reviewers better understand the
    cost proposal.

Offerors **shall** employ the following guidelines when describing each
BOE:

-   WBS \# and Title -- The BOE \# and WBS \# are synonymous. BOE's are
    written to the lowest level WBS element.

-   WBS Element Description.

```{=html}
<!-- -->
```
-   Requirement(s) Reference -- This states the specific RFP section(s)
    the BOE satisfies.

-   Estimate Costs -- Present the WBS element's estimated total dollars
    and distribution across fiscal years. Be sure to identify the base
    year of calculation. State whether the dollars are in Constant Year
    (CYXX) dollars and/or Then Year Dollars.

-   Methodology -- Describe how the WBS element's costs were estimated.
    Depending on the choice of methodology, the estimator should include
    one or more of the following data:

-   If Labor rates are a part of the methodology, then identify direct
    and indirect labor rates, what costs are included in the rates, and
    how the rates were determined.

-   If Labor hours are a part of the methodology, then describe how
    labor hours were estimated, the number of hours and applicable
    actual hourly rates.

-   If material purchases are a part of the methodology, then list the
    materials and purchased parts, the source of estimated prices and
    any crosschecks performed.

-   If subcontracts are a part of the methodology, then summarize the
    work to be performed, and how the price was determined.

-   If cost factors or cost estimating relationships (CERs) are a part
    of the Methodology, then describe their source and how they were
    applied. Included in cost factors are discount factors (e.g., future
    technology cost drops, quantity discounts).

-   If cost models are a part of the methodology, then describe any
    estimating models used and how they were applied.

-   If analogous systems are a part of the methodology, then identify
    the analogous systems and explain how and why they were used.

-   If estimator judgment is a part of the Methodology, then specify who
    (job title is sufficient) provided the estimate and any
    justification.

-   Time Phasing. Describe the analytic approach used to distribute the
    WBS element's estimated costs across fiscal years.

-   Calculations. Present the inputs and algorithm(s) or equation(s) for
    each WBS element so that reviewers can understand the basis for the
    cost estimate. Describe how WBS element costs were aggregated into
    the summary tables.

-   Cost Estimate Summaries - Include a summary table (sample below) of
    estimated costs by fiscal year in Constant and/or Current Then Year
    dollars.

> SAMPLE

  ---------- ---------- --------- --------- ---------- ---------- ----------
             FYXX       FYXX      FYXX      FYXX       **...**    Total

  WBS 3.0                                                         

  WBS 3.1                                                         

  WBS 3.2                                                         

  Etc.                                                            

  Etc.                                                            

  Etc.                                                            

  Etc.                                                            

  Total                                                           
  ---------- ---------- --------- --------- ---------- ---------- ----------

-   Data Sources. Identify WBS-element-unique sources of cost and
    technical data and parameter values. Describe procedures, if any,
    used to normalize those data.

-   Risk Adjustments. Describe any WBS-element-specific procedures used
    to adjust the WBS element's estimated cost for risk. State the costs
    amounts (if any) for the risk adjustment.

-   If Constant Year Dollars were used, include what (if any) cost
    changes might exist if "Then Year" Dollars were calculated.

[**Level of the WBS**]{.underline} -- Execution Period No. 1 BOE's
**shall** be written at the lowest CWBS level required for detailed
planning.

The chart below provides clarification on the cost proposal's level of
detail.

+----+---+----------+----------------------+--------------------------+
|    | * | **E      | **Execution Period   | **Execution Period No.   |
|    | * | xecution | No. 2**              | 3**                      |
|    | B | Period   |                      |                          |
|    | a | No. 1**  |                      |                          |
|    | s |          |                      |                          |
|    | e |          |                      |                          |
|    | P |          |                      |                          |
|    | e |          |                      |                          |
|    | r |          |                      |                          |
|    | i |          |                      |                          |
|    | o |          |                      |                          |
|    | d |          |                      |                          |
|    | * |          |                      |                          |
|    | * |          |                      |                          |
+----+---+----------+----------------------+--------------------------+
| S  | N | Lowest   | PWBS                 | PWBS                     |
| ug | / | Level    |                      |                          |
| ge | A | required | Level 3              | Level 2                  |
| st |   | for      |                      |                          |
| ed |   | Detailed |                      |                          |
|    |   | Planning |                      |                          |
| Lo |   | (        |                      |                          |
| we |   | starting |                      |                          |
| st |   | at level |                      |                          |
| L  |   | 4 and    |                      |                          |
| ev |   | beyond)  |                      |                          |
| el |   |          |                      |                          |
| B  |   |          |                      |                          |
| OE |   |          |                      |                          |
| 's |   |          |                      |                          |
| w  |   |          |                      |                          |
| ri |   |          |                      |                          |
| tt |   |          |                      |                          |
| en |   |          |                      |                          |
| to |   |          |                      |                          |
+----+---+----------+----------------------+--------------------------+
| W  | N | See      | Contractors may      | Contractors may propose  |
| BS | / | draft    | propose the PWBS.    | the PWBS.                |
| Re | A | PWBS     |                      |                          |
| fe |   | f        | Reference            | Reference MIL-HDBK-881   |
| re |   | ramework | MIL-HDBK-881 and the | and the limitations      |
| nc |   | offered  | limitations          | described below.         |
| es |   | in       | described below.     |                          |
|    |   | Section  |                      | Prior to exercising      |
|    |   | C.5.6.4. | Prior to exercising  | Execution Period No. 3,  |
|    |   |          | Execution Period No. | both the Census Bureau   |
|    |   | R        | 2, both the Census   | and selected vendor will |
|    |   | eference | Bureau and selected  | reexamine the            |
|    |   | MIL-H    | vendor will          | appropriateness of the   |
|    |   | DBK-881. | reexamine the        | WBS submitted in this    |
|    |   |          | appropriateness of   | cost proposal. The       |
|    |   |          | the WBS submitted in | Census Bureau will work  |
|    |   |          | this cost proposal.  | together with the        |
|    |   |          | The Census Bureau    | Contractor to solidify & |
|    |   |          | will work together   | drill-down this period's |
|    |   |          | with the Contractor  | WBS before the final     |
|    |   |          | to solidify &        | Performance Measurement  |
|    |   |          | drill-down this      | Baseline (PMB) is        |
|    |   |          | period's WBS before  | created. For this        |
|    |   |          | the final            | reason, the Vendor's     |
|    |   |          | Performance          | **shall** use a Project  |
|    |   |          | Measurement Baseline | Management Information   |
|    |   |          | (PMB) is created.    | System (PMIS) that is    |
|    |   |          | For this reason, the | flexible in changing WBS |
|    |   |          | Vendor's **shall**   | mapping / tiering        |
|    |   |          | use a Project        | capabilities. This       |
|    |   |          | Management           | flexibility is needed in |
|    |   |          | Information System   | the event that any of    |
|    |   |          | (PMIS) that is       | the final (agreed upon)  |
|    |   |          | flexible in changing | Execution Period No. 3   |
|    |   |          | WBS mapping /        | WBS elements change      |
|    |   |          | tiering              | prior to beginning       |
|    |   |          | capabilities. This   | Execution Period No. 3.  |
|    |   |          | flexibility is       |                          |
|    |   |          | needed in the event  | Vendors are encouraged   |
|    |   |          | that any of the      | to reuse elements from a |
|    |   |          | final (agreed upon)  | prior Execution period's |
|    |   |          | WBS elements change  | WBS where appropriate.   |
|    |   |          | prior to beginning   |                          |
|    |   |          | Execution Period No. |                          |
|    |   |          | 2.                   |                          |
|    |   |          |                      |                          |
|    |   |          | Vendors are          |                          |
|    |   |          | encouraged to reuse  |                          |
|    |   |          | elements from a      |                          |
|    |   |          | prior Execution      |                          |
|    |   |          | period's WBS where   |                          |
|    |   |          | appropriate.         |                          |
+----+---+----------+----------------------+--------------------------+
| L  | N | 1\. WBS  | 1\. WBS **shall**    | 1\. WBS **shall** have a |
| im | / | *        | have a Prime Mission | Prime Mission Product    |
| it | A | *shall** | Product Section as   | Section as defined in    |
| at |   | have a   | defined in MIL-HDBK  | MIL-HDBK 881, Appendix   |
| io |   | Prime    | 881, Appendix B.4.2. | B.4.2.                   |
| ns |   | Mission  |                      |                          |
|    |   | Product  | 2\. Level 1, "2.0:,  | 2\. Level 1, "3.0",      |
|    |   | Section  | **shall** represent  | **shall** represent the  |
|    |   | as       | the Contract Phase;  | Contract Phase;          |
|    |   | defined  | "Execution Period    | "Execution Period No.    |
|    |   | in       | No. 2"               | 3."                      |
|    |   | MIL-HDBK |                      |                          |
|    |   | 881,     | 3\. There **shall**  | 3\. There **shall** be   |
|    |   | Appendix | be nothing higher in | nothing higher in this   |
|    |   | B.4.2.   | this Period's Level  | Period's Level 3.0 WBS   |
|    |   |          | 2.0 WBS element      | element (e.g., Level 0)  |
|    |   | 2\.      | (e.g., Level 0)      |                          |
|    |   | Level 1, |                      |                          |
|    |   | "1.0",   | 4\. A WBS element    |                          |
|    |   | *        | **shall** be         |                          |
|    |   | *shall** | reserved for effort  |                          |
|    |   | r        | involved in fully    |                          |
|    |   | epresent | creating and         |                          |
|    |   | the      | validating the next  |                          |
|    |   | Contract | execution period's   |                          |
|    |   | Phase;   | Performance          |                          |
|    |   | "E       | Baseline.            |                          |
|    |   | xecution |                      |                          |
|    |   | Period   |                      |                          |
|    |   | No. 1."  |                      |                          |
|    |   |          |                      |                          |
|    |   | 3\.      |                      |                          |
|    |   | There    |                      |                          |
|    |   | *        |                      |                          |
|    |   | *shall** |                      |                          |
|    |   | be       |                      |                          |
|    |   | nothing  |                      |                          |
|    |   | higher   |                      |                          |
|    |   | in this  |                      |                          |
|    |   | Period's |                      |                          |
|    |   | Level    |                      |                          |
|    |   | 1.0 WBS  |                      |                          |
|    |   | element  |                      |                          |
|    |   | (e.g.,   |                      |                          |
|    |   | Level 0) |                      |                          |
|    |   |          |                      |                          |
|    |   | 4\. A    |                      |                          |
|    |   | WBS      |                      |                          |
|    |   | element  |                      |                          |
|    |   | *        |                      |                          |
|    |   | *shall** |                      |                          |
|    |   | be       |                      |                          |
|    |   | reserved |                      |                          |
|    |   | for      |                      |                          |
|    |   | effort   |                      |                          |
|    |   | involved |                      |                          |
|    |   | in fully |                      |                          |
|    |   | creating |                      |                          |
|    |   | and      |                      |                          |
|    |   | va       |                      |                          |
|    |   | lidating |                      |                          |
|    |   | the next |                      |                          |
|    |   | e        |                      |                          |
|    |   | xecution |                      |                          |
|    |   | period's |                      |                          |
|    |   | Per      |                      |                          |
|    |   | formance |                      |                          |
|    |   | B        |                      |                          |
|    |   | aseline. |                      |                          |
+----+---+----------+----------------------+--------------------------+

[Limitations & Assumptions]{.underline}:

-   Cost Proposals are to cover all CLIN Structures as defined in
    section B.

-   Execution Period #1's PWBS (in C.5.6.4.) is intentionally not
    complete. Offerors **shall** fill in or supplement the suggested
    areas for Level 3, as well as drill down and create CWBS (Level 4
    and greater).

-   The final overall costs (e.g. in Parent PWBS elements, BAC, Total
    cost goals) **shall** be based on a "bottoms up" rollup, beginning
    from the lowest level of the WBS element tree. \[Note: This is
    consistent with ANSI/EIA-748-A, Section 2.2.J\]

[WBS Areas of Responsibility]{.underline}: As a general rule, after
Contract Award, the following guidelines will exist in terms of WBS
Responsibility. This does not preclude either the Contractor or Census
Bureau from making WBS suggestions, regardless of the level, for the
improvement of the FDCA Performance Baseline.

-   The Census Bureau **shall** have primary management responsibility
    of the WBS for Levels 1 and 3.

```{=html}
<!-- -->
```
-   The Contractor **shall** have primary management responsibility of
    the CWBS for Levels 4 and beyond. These are typically referred to as
    *Work Packages*, the lowest levels of the WBS for capturing costs.
    Although section C.5.6.4.8 offers guidance on the level of detail,
    the Contractor's Project Manager **shall** decompose the WBS to
    whatever level of detail he or she requires to effectively plan and
    manage this effort.

> \(2\) The Offerors **shall** provide roll-up cost to a summary table
> established in the cost proposal that can be transferred to Section B
> of the contract in accordance with the Offerors proposed solution.
>
> \(3\) While travel, security and bill of materials (BOM) costs
> **shall** be included within the appropriate BOE(s), the Offerors
> **shall** also provide individual schedules for travel, security, and
> bill of materials (BOM) costs. However, the travel, security and BOM
> costs **shall** be rolled up from the BOE to the summary table~~s~~.
> Prices **shall** be rounded to the nearest dollar. All unit prices
> **shall** be fully discounted billable prices reflecting all
> discounts. To be considered for award, the Offerors **shall** enter
> the cost data required to complete the summary table. The Offerors is
> expected to establish a reasonable cost relationship between all
> prices/costs listed in Section B.

\(4\) The Government may use an Independent Government Cost Estimate
(GCE) for determining cost reasonableness, etc. The Offerors' estimated
cost (Summary Table~~s~~) **shall** include all items to be delivered.
The Offerors **shall** propose the cost/pricing structure in Section B,
and the deliverables in accordance with the Offerors' proposed solution.
All data **shall** be proposed as "Not Separately Priced" (NSP), meaning
the price is included in the overall cost.

\(5\) The cost/price proposal **shall** be consistent with and support
the other sections of the proposal. All commitments in the technical
proposal that affect the Offerors' cost proposal **shall** be discussed
and quantified in the cost proposal.

\(6\) The following instructions are to assist the Offerors in
developing and presenting information required in support of the
cost/price proposal offered, and to limit the amount of cost/price
documentation initially submitted. Proper presentation and submission of
the requested documentation will assist evaluation of the proposal for
cost/price realism and reasonableness.

> \(c\) Direct Labor Rates
>
> The Offerors **shall** propose a direct labor rate for each labor
> category required by ~~this~~
>
> the Offeror's solution ~~.solicitation; i.e.,~~ . The direct labor
> shall rate **shall** include the estimate of rates required to attract
> and retain qualified personnel for the base and option years for the
> proposed award. The proposal **shall** include:
>
> The data upon which the judgment or estimate was made (e.g., company
> payroll records, salary survey).
>
> A list of the Offeror's skill categories ~~that correlate to each of
> those required by this solicitation and/or any additional categories
> that the Offerors proposes~~, and a description of the skill
> requirements for each.
>
> ~~A description of how the Offeror's skill categories were correlated
> and matched with those required in the solicitation.~~
>
> The rates or, if applicable, the rate ranges of the skill categories.
>
> **(d) Fringe Benefits**
>
> Provide a listing of the fringe benefits proposed.
>
> State the legal requirement or company policy for each fringe benefit
> proposed and the formula for application. This information must
> contain the basis for fringe benefit calculations, judgments, or
> estimates.
>
> **(e) Overhead and General and Administration (G&A)**
>
> The Offerors **shall** explain the basis for any corporate labor
> overhead and general administrative (G&A) charges anticipated.
> Overhead must be shown separately from G&A. The information **shall**
> be prepared for each of the Offerors' two (2) previously completed
> fiscal years and the current fiscal year. Offerors **shall** provide
> detailed background data identifying the cost elements included in the
> overhead, G&A, or indirect pool, and a statement that such treatment
> is in accordance with the Offerors' established accounting practice
> and represents equitable distribution.

\(f\) Fee/Profit

> The Offerors **shall** discuss the amounts and rationale for any
> proposed fees/profit.

**L.16.1.8.1.1 Volume IV:** **Additional Exhibits**

Offerors are encouraged to create any additional non-marketing exhibits
that will assist the Government in the evaluation of the Offerors' cost
proposals.

**L.16.1.8.1.2 Volume IV:** **Explanation of Pricing**

This section of the Offerors' proposals is designed to provide narrative
discussions/explanations of all the assumptions made in developing the
proposals and/or to explain the rationale for the structure of the cost
proposals. It can be used to provide additional information that may not
be found in the appendixes or to discuss innovative techniques employed
in the development of the cost proposals. As long as the information
contained in the "Explanation of Pricing" is related to the cost
proposals, the Offerors may provide as much narrative discussion as they
feel is sufficient to support their cost proposal.

L.16.1.8.2 Volume IV, Section 2: Proposal Submission Instructions

See Section 16.1

The copies of Volume IV **shall** be physically separate from other
volumes of the proposals. Proposal pages **shall** be numbered. Offerors
**shall** ensure that any spreadsheets and narratives are capable of
being extracted by the Government, and therefore must be submitted into
Microsoft Excel or Adobe Acrobat (.pdf) formats.

**L.16.1.8.3** **Volume IV, Section 3: Conflict of Interest Avoidance
Plan.**

The Offerors **shall** discuss any known potential conflicts with
existing efforts being performed under contracts or subcontracts, and
**shall** address their plans for mitigating any conflicts of interest.
Of critical importance is the Offerors' commitment to the performance of
the work required under this contract. Thus, the Offerors **shall**
provide brief narrative discussions of how a future conflict would be
resolved to ensure there is no interruption of the work.

NOTE: **Offerors are to exclude the following Section C requirement from
their cost estimate**

C.5.2.1.6.10. The OCE of the RCCs, PRAO and LCOs **shall** interface
with the Census **HQ Cost and Progress (C&P) System** to provide
operational status and cost data. The details of this interface will be
provided after contract award.

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. The details of this interface will be provided after
contract award.

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. The details of this interface will be
provided after contract award.

C.5.2.4 Evaluations and Experiments \[FOR INFORMATION ONLY\] -- the
entire section.

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). The list of hardware and
peripherals will be provided after contract award.

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.

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.

**ATTACHMENT L.1**

> **SIMILAR EXPERIENCE MATRIX TEMPLATE**

+-----------------------------------------------------------------------+
| 1)  ***Contract/Title*, *Project Name* (Contract Number *XXXX*)**     |
+-----------------------------------------------------------------------+

+----------------------+-----------------------------------------------+
| 2)  **Performed      |                                               |
|     By:**            |                                               |
+----------------------+-----------------------------------------------+
| 3)  **Major          |                                               |
|                      |                                               |
|  Subcontractor(s):** |                                               |
+----------------------+-----------------------------------------------+
| 4)                   |                                               |
|  **Agency/Company:** |                                               |
+----------------------+-----------------------------------------------+
| 5)  **CO:**          |                                               |
+----------------------+-----------------------------------------------+
| 6)  **COTR:**        |                                               |
+----------------------+-----------------------------------------------+
| 7)  **Other          |                                               |
|     Technical POC:** |                                               |
+----------------------+-----------------------------------------------+
| 8)  **Period of      |                                               |
|     Performance:**   |                                               |
+----------------------+-----------------------------------------------+
| 9)  **Contract Type  |                                               |
|     and Total        |                                               |
|     Value:**         |                                               |
+----------------------+-----------------------------------------------+
| 1                    |                                               |
| 0) **Product/Service |                                               |
|     Provided:**      |                                               |
+----------------------+-----------------------------------------------+

+-----------------------------------------------------------------------+
| 11) **Small Business Participation:**                                 |
+-----------------------------------------------------------------------+
| 12) **Awards, Recognitions, and Certifications Received:**            |
+-----------------------------------------------------------------------+
| 13) **Project Description and Approach:**                             |
+-----------------------------------------------------------------------+
| 14) **Relevancy of Experience:**                                      |
+-----------------------------------------------------------------------+

**ATTACHMENT L.2**

**ORGANIZATION'S PERFORMANCE QUESTIONNAIRE**

+-----------------------------------+----------------------------------+
| ORGANIZATION'S PERFORMANCE        |                                  |
| QUESTIONNAIRE                     |                                  |
+-----------------------------------+----------------------------------+
| Your assistance is requested in   |                                  |
| support of a source selection     |                                  |
+-----------------------------------+----------------------------------+
| Please complete this              |                                  |
| questionnaire and mail or send by |                                  |
| fax (301) 457-8465 to:            |                                  |
+-----------------------------------+----------------------------------+
| Michael L. Palensky, Contracting  |                                  |
| Officer                           |                                  |
|                                   |                                  |
| U.S. Census Bureau Desired        |                                  |
| Response Date: July 8, 2005       |                                  |
|                                   |                                  |
| 4700 Silver Hill Road, Stop 1700  |                                  |
|                                   |                                  |
| Washington, DC 20233              |                                  |
+-----------------------------------+----------------------------------+
| When complete, the information on |                                  |
| this form is **SOURCE SELECTION   |                                  |
| SENSITIVE INFORMATION** (41       |                                  |
| U.S.C. 423) and **shall** be      |                                  |
| protected accordingly.            |                                  |
+-----------------------------------+----------------------------------+
| TO BE COMPLETED BY CONTRACTOR     |                                  |
+-----------------------------------+----------------------------------+
| 1.  CONTRACTOR'S NAME AND ADDRESS | 4\. CONTRACT NO.:                |
+-----------------------------------+----------------------------------+
|                                   | 5\. CONTRACT INITIATION DATE:    |
+-----------------------------------+----------------------------------+
|                                   | 6\. COMPLETION DATE:             |
+-----------------------------------+----------------------------------+
|                                   | 7\. CONTRACT VALUE \$            |
+-----------------------------------+----------------------------------+
| 2.  PROJECT NAME:                 | 8\. TYPE OF CONTRACT:            |
+-----------------------------------+----------------------------------+
| 9\. DESCRIPTION OF PROJECT'S KEY  |                                  |
| CHARACTERISTICS:                  |                                  |
+-----------------------------------+----------------------------------+
| Please add a continuation page if |                                  |
| additional space is necessary.    |                                  |
+-----------------------------------+----------------------------------+
| TO BE COMPLETED BY EVALUATING     |                                  |
| ORGANIZATION REPRESENTATIVE       |                                  |
+-----------------------------------+----------------------------------+
| 10\. EVALUATION                   |                                  |
+-----------------------------------+----------------------------------+
| a.  EVALUATOR'S NAME, POSITION    |                                  |
|     DURING PROJECT EXECUTION      |                                  |
|     (Project Manager/COR/Other)   |                                  |
|     AND ORGANIZATION              |                                  |
+-----------------------------------+----------------------------------+
| b.  EVALUATOR'S PHONE NUMBER      | c\. MONTHS PERFORMANCE MONITORED |
|                                   | BY EVALUATOR:                    |
+-----------------------------------+----------------------------------+
| Please check the response code    |                                  |
| for each topic that best reflects |                                  |
| your experience with this         |                                  |
| contractor:                       |                                  |
|                                   |                                  |
| **EX** = Exceptional **VG** =     |                                  |
| Very Good **S** = Satisfactory    |                                  |
| **MG** = Marginal **US** =        |                                  |
| Unsatisfactory **N/O** = Not      |                                  |
| Observed                          |                                  |
+-----------------------------------+----------------------------------+
| A.  **Quality of Products and     |                                  |
|     Services**- Assess the        |                                  |
|     contractor's conformance to   |                                  |
|     contract requirements.        |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| B.  **Overall Performance**-      |                                  |
|     Assess the contractor's       |                                  |
|     overall performance for the   |                                  |
|     project.                      |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| C.  **Schedule**- Assess the      |                                  |
|     timeliness of the contractor  |                                  |
|     against the schedule of       |                                  |
|     activities (as appropriate).  |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| D.  **Technical Requirements**-   |                                  |
|     Assess the contractor's       |                                  |
|     ability and capacity to       |                                  |
|     fulfill the technical         |                                  |
|     requirements of the contract. |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| E.  **Cost Control**- Assess the  |                                  |
|     contractor's willingness and  |                                  |
|     ability to manage the         |                                  |
|     contract budget and control   |                                  |
|     costs.                        |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| F.  **Subcontracting**- Assess    |                                  |
|     the contractor's success at   |                                  |
|     complying with subcontracting |                                  |
|     goals.                        |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| G.  **Customer Satisfaction**-    |                                  |
|     Assess the contractor's       |                                  |
|     responsiveness to customer    |                                  |
|     concerns and "user            |                                  |
|     friendliness" in ROUTINE      |                                  |
|     matters.                      |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| H.  **Customer Satisfaction**-    |                                  |
|     Assess the contractor's       |                                  |
|     responsiveness to customer    |                                  |
|     concerns and "user            |                                  |
|     friendliness" in UNEXPECTED   |                                  |
|     DIFFICULTIES.                 |                                  |
|                                   |                                  |
| GEX GVG GS GMG GUS GN/O           |                                  |
+-----------------------------------+----------------------------------+
| I.  **Repeat Business**- Assess   |                                  |
|     the likelihood that you would |                                  |
|     want this contractor to       |                                  |
|     perform another contract for  |                                  |
|     you in the near future.       |                                  |
|                                   |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| J.  List Contractor's Weak        |                                  |
|     Points:                       |                                  |
+-----------------------------------+----------------------------------+
| K. List Contractor's Strong       |                                  |
| Points:                           |                                  |
+-----------------------------------+----------------------------------+
| L. List any other projects this   |                                  |
| contractor has completed for you: |                                  |
+-----------------------------------+----------------------------------+
| M. If an award fee contract, what |                                  |
| was the average award fee %       |                                  |
| earned?                           |                                  |
+-----------------------------------+----------------------------------+

**ATTACHMENT L.3**

**INDIVIDUAL'S PERFORMANCE QUESTIONNAIRE**

+-----------------------------------+----------------------------------+
| INDIVIDUAL'S PERFORMANCE          |                                  |
| QUESTIONNAIRE                     |                                  |
+-----------------------------------+----------------------------------+
| Your assistance is requested in   |                                  |
| support of a source selection     |                                  |
+-----------------------------------+----------------------------------+
| Please complete this              |                                  |
| questionnaire and mail or send by |                                  |
| fax (301) 457-8465 to:            |                                  |
+-----------------------------------+----------------------------------+
| Michael L. Palensky, Contracting  |                                  |
| Officer                           |                                  |
|                                   |                                  |
| U.S. Census Bureau Desired        |                                  |
| Response Date: July 8, 2005       |                                  |
|                                   |                                  |
| 4700 Silver Hill Road, Stop 1700  |                                  |
|                                   |                                  |
| Washington, DC 20233              |                                  |
+-----------------------------------+----------------------------------+
| When complete, the information on |                                  |
| this form is **SOURCE SELECTION   |                                  |
| SENSITIVE INFORMATION** (41       |                                  |
| U.S.C. 423) and **shall** be      |                                  |
| protected accordingly.            |                                  |
+-----------------------------------+----------------------------------+
| TO BE COMPLETED BY CONTRACTOR     |                                  |
+-----------------------------------+----------------------------------+
| 3.  INDIVIDUAL'S NAME, COMPANY    | 4\. CONTRACT NO.:                |
|     AND ADDRESS                   |                                  |
+-----------------------------------+----------------------------------+
|                                   | 5\. CONTRACT INITIATION DATE:    |
+-----------------------------------+----------------------------------+
|                                   | 6\. COMPLETION DATE:             |
+-----------------------------------+----------------------------------+
|                                   | 7\. CONTRACT VALUE \$            |
+-----------------------------------+----------------------------------+
| 4.  PROJECT NAME:                 | 8\. TYPE OF CONTRACT:            |
+-----------------------------------+----------------------------------+
| 9\. DESCRIPTION OF PROJECT'S KEY  |                                  |
| CHARACTERISTICS:                  |                                  |
+-----------------------------------+----------------------------------+
| Please add a continuation page if |                                  |
| additional space is necessary.    |                                  |
+-----------------------------------+----------------------------------+
| TO BE COMPLETED BY EVALUATING     |                                  |
| ORGANIZATION REPRESENTATIVE       |                                  |
+-----------------------------------+----------------------------------+
| 10\. EVALUATION                   |                                  |
+-----------------------------------+----------------------------------+
| c.  EVALUATOR'S NAME, POSITION    |                                  |
|     DURING PROJECT EXECUTION      |                                  |
|     (Project Manager/COR/Other)   |                                  |
|     AND ORGANIZATION              |                                  |
+-----------------------------------+----------------------------------+
| d.  EVALUATOR'S PHONE NUMBER      | c\. MONTHS PERFORMANCE MONITORED |
|                                   | BY EVALUATOR:                    |
+-----------------------------------+----------------------------------+
| Please check the response code    |                                  |
| for each topic that best reflects |                                  |
| your experience with this         |                                  |
| contractor:                       |                                  |
|                                   |                                  |
| **EX** = Exceptional **VG** =     |                                  |
| Very Good **S** = Satisfactory    |                                  |
| **MG** = Marginal **US** =        |                                  |
| Unsatisfactory **N/O** = Not      |                                  |
| Observed                          |                                  |
+-----------------------------------+----------------------------------+
| > **A. Quality of Products and    |                                  |
| > Services**- Assess the          |                                  |
| > individual's conformance to     |                                  |
| > contract requirements.          |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **B. Overall Performance**-     |                                  |
| > Assess the individual's overall |                                  |
| > performance for the project.    |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **C. Initiative**- Assess the   |                                  |
| > individual's use of initiative  |                                  |
| > to avoid problems and to        |                                  |
| > respond to problems.            |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **D. Technical Requirements**-  |                                  |
| > Assess the individual's ability |                                  |
| > and capacity to fulfill the     |                                  |
| > technical requirements of the   |                                  |
| > contract.                       |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **E. Cost Control**- Assess the |                                  |
| > individual's willingness and    |                                  |
| > ability to manage the contract  |                                  |
| > budget and control costs.       |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **F. Customer Satisfaction**-   |                                  |
| > Assess the Individual's         |                                  |
| > responsiveness to customer      |                                  |
| > concerns and "user              |                                  |
| > friendliness" in ROUTINE        |                                  |
| > matters.                        |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| > **G. Customer Satisfaction**-   |                                  |
| > Assess the Individuals          |                                  |
| > responsiveness to customer      |                                  |
| > concerns and "user              |                                  |
| > friendliness" in UNEXPECTED     |                                  |
| > DIFFICULTIES.                   |                                  |
|                                   |                                  |
| GEX GVG GS GMG GUS GN/O           |                                  |
+-----------------------------------+----------------------------------+
| > **H. Repeat Business**- Assess  |                                  |
| > the likelihood that you would   |                                  |
| > want this individual to perform |                                  |
| > another contract for you in the |                                  |
| > near future.                    |                                  |
| >                                 |                                  |
| > GEX GVG GS GMG GUS GN/O         |                                  |
+-----------------------------------+----------------------------------+
| I. List the individual's Weak     |                                  |
| Points:                           |                                  |
+-----------------------------------+----------------------------------+
| J. List the individual's Strong   |                                  |
| Points:                           |                                  |
+-----------------------------------+----------------------------------+
| K. List any other projects this   |                                  |
| individual has completed for you: |                                  |
+-----------------------------------+----------------------------------+

ATTACHMENT L.4

**PROTOTYPE DEVELOPMENT INSTRUCTIONS**

# 1.0 Overview and Scope

The FDCA Prototype will provide the Government the opportunity to
evaluate each Offeror's proposed solution related to several critical
areas of functionality for the FDCA Project. Specifically, these
critical areas include: 1) the Offeror's solution for the mobile
computing environment (MCE) for the Census Bureau's Address Canvassing
operation; 2) a limited portion of the office computing environment's
(OCE) operational control (OC) functionality; 3) the performance of
bi-directional data communications between the MCE and OCE for typical
assignment files. *Note - at [no]{.underline} time during development or
evaluation of the prototypes **shall** Title 13 data be provided or
used.*

Each prototype **shall** be demonstrated and evaluated in an actual
field test conducted by the Offeror. The Census Bureau will evaluate
each prototype through the Offeror's conduct of a limited and simulated
Address Canvassing operation at a government specified location in the
vicinity of the Census Bureau's Suitland, Maryland Headquarters. For
this, the OCE OC component of the prototype **shall** first receive and
process simulated, non-Title 13 data files for the Address Canvassing
operation. First, the Offeror **shall** demonstrate the prototype's load
and processing of the data in these files (note -- the Census Bureau
will assign the initial Field Office Supervisors/Crew Leaders to their
Assignment Areas within the files provided). After the data load and
processing is complete, the Offeror **shall** demonstrate: 1) the making
of assignments for enumerators from both the OCE's OC function and from
the crew leaders MCE, and 2) transmitting those assignments to the
appropriate enumerators' MCEs. The Offeror **shall** then simulate the
conduct the Address Canvassing operating using the assignment files sent
to their MCE (i.e., address list and corresponding maps). This
simulation **shall** involve updating of the address list and maps based
on information obtained solely through observation of the assigned
areas, without direct contact or collection of information from local
residents. The vendor **shall** exercise the full functionality
associated with the assignment from both the enumerator's and the crew
leader's perspective (i.e., reviewing and managing their progress
through the assignment, reading messages sent to them from their crew
leader, validating and updating the address list, validating and
updating the associated geographic map files, collecting GPS
longitude/latitude coordinates, submitting their completed assignments,
submitting their Time & Attendance (T&A) and expense data, reviewing
crew leader approval/disapproval of their work and T&A, redoing or
resubmitting work as appropriate based on
messages/approvals/disapprovals by their crew leader, and reviewing
status and administrative reports).

As the Offeror progresses through the Address Canvassing assignments,
the Offeror **shall** demonstrate the prototype's OCE's OC functionality
to track and report on assignment progress as is done during actual
Census operations. Once all transmissions are completed between the
prototype's OCE and MCE, and all enumerator assignments have been
completed (including re-conducted as appropriate based on demonstration
of crew leader disapproval of a submitted assignment), the Offeror
**shall** then provide the Census Bureau with all completed output files
to validate results. Note -- the Offeror **shall** be required to supply
these output files from completed assignments in the format specified by
the Census Bureau for efficiency in evaluating the prototype of multiple
Offerors.

# 2.0 Deliverables

The Offerors **shall** deliver:

-   A comprehensive test plan (with test scenarios and cases to assess
    and document all designed functionality, performance metrics, and
    usability) for their proposed field demonstration and test of their
    prototype for Government review, modification, and approval;

-   A field demonstration and test of hardware and software which
    prototypes the required OCE's OC functionality (see Sections C and
    J). This system, or its user interface or client, **shall** be
    available for use by the Government at a location within 60 minutes
    driving time of the Census Bureau Headquarters (HQ) for the
    evaluation. If the Offeror's prototype requires backend components
    (e.g., central databases, communications servers, etc.), these can
    be placed in locations as desired by the Offeror;

-   A field demonstration and test of enumerator assignments on 4 MCEs
    conducted at a location specified by the Government and close to the
    Census Bureau Headquarters (1 for a crew leader, 2 for enumerators,
    1 spare);

-   The documented results of the test plan's execution for the field
    demonstration and test, for the Government's subsequent analysis and
    formal evaluation of the prototype,

```{=html}
<!-- -->
```
-   Oral Presentation ~~and Discussion~~, including written
    documentation [that]{.underline} **shall** review the technical
    details of the Offeror's prototype, how it meets the requirements,
    and how it fits into the overall architecture of their final
    solution; and

-   Any training and/or other support materials the Offeror deems
    necessary.

The government will provide the Offerors with the following during the
first week of prototype technical interchange:

-   The needed data files (i.e., the address canvassing "Universe"
    files; see attachments for draft file formats);

-   The Address Canvassing assignments to be demonstrated during the
    prototype's test (e.g., exact addresses to list and update, collect
    map spots, etc.); and

-   The types of assignment management, address canvassing, mapping, and
    Time and Attendance functions to be exercised during the Offeror's
    field demonstration and test of their prototype (e.g., add a
    specific address, change a specific street name, geocode a specific
    map feature, etc.).

All systems, hardware, and software for the prototype **shall** comply
with Department of Commerce and Census Bureau security requirements,
including those necessary to process Title 13 data (*Note -- Title 13
data will [not]{.underline} be used at any time in the prototype's
development or evaluation*). During the technical exchange period the
Government will provide the rules of engagement permitted between the
Offerors and Government staff during conduct of the prototype's field
demonstration and test.

3.0 Requirements for which the Prototype Shall Comply (see RFP Section J
for these documents)

The prototype shall comply with the specification and requirements
listed below in their entirety unless otherwise noted. *\
*

> [Input File (Universe) Formats]{.underline} in FDCA RFP Section J --
> Universe

1.  Master Address File Data Definition, including Puerto Rico

2.  Geographic Reference Files of Codes Data Definition (GRF-C), 2006
    Census Test

3.  Geographic Reference Files of Codes Data Definition (GRF-N), 2006
    Census Test

4.  Data Definition for Map File Contents

> [Output File (Completed Assignment Data) Formats]{.underline} in FDCA
> RFP Section J -- Universe and Section J - Time/Attendance & Expense

5.  Update File Layouts

6.  Draft Record Layout for Input to DAPPS, 2006 Census Test

> [OCE OC Functionality Reference Documents]{.underline} in RFP Section
> J -- Prototype Only

7.  Address Canvassing Prototype Functionality

> [MCE Functionality Reference Documents]{.underline} in RFP Section J
> -- Data and Map Specifications and Section J - Time/Attendance &
> Expense

8.  Address Listing Instrument Specification for English, 2006 Census
    Test version\
    Only highlighted functions and specifications contained in this
    document.

9.  Map Specifications for the 2006 Census Test\
    Only highlighted functions and specifications contained in this
    document.

10. Daily Pay and Work Record - Report Examples, 2006 Census Test\
    Only highlighted functions and specifications contained in this
    document.

11. Daily Pay and Work Record - Paper Version, 2006 Census Test

12. Daily Pay and Work Record for Per Diem - Paper Version, 2006 Census
    Test

# 4.0 Functional Requirements of the Prototype

+----+------------+---------------------------------------------------+
| ** | **Respon   | ## Function                                       |
| St | sibility** |                                                   |
| ep |            |                                                   |
| ** |            |                                                   |
+----+------------+---------------------------------------------------+
| 1  | Census HQ  | Provide Universe Files                            |
|    |            |                                                   |
|    | See        | > Address File (from non-Title13 source -- not    |
|    | [Section   | > the actual MAF extract used by Census since     |
|    | J]{.       | > this is Title 13)                               |
|    | underline} | >                                                 |
|    | for        | > Simulated GRFC (from non-Title13 source)        |
|    | (Universe) | >                                                 |
|    | Formats    | > Simulated GRFN (from non-Title13 source)        |
|    | for        | >                                                 |
|    | spec       | > Simulated TIGER Extract (from non-Title13       |
|    | ifications | > source)                                         |
|    |            | >                                                 |
|    |            | > Simulated DAPPS Employee Table (from            |
|    |            | > non-Title13 source)                             |
+----+------------+---------------------------------------------------+
| 2  | Offeror 's | Process and Associate Universe Files              |
|    | OCE        |                                                   |
|    |            | -   Offeror **shall** associate the data in all   |
|    | See        |     files in accordance with their design using   |
|    | [Section C |     the common fields within those files to       |
|    | &          |     determine relational linking. This process    |
|    | J]{.       |     **shall** include generating the map files    |
|    | underline} |     and corresponding address list files          |
|    | for a list |     associated with the assignments to be sent to |
|    | of         |     the MCE.                                      |
|    | functions, |                                                   |
|    | fields and | Make Crew Leader/Enumerator Assignments           |
|    | reporting  |                                                   |
|    | needed     | -   *This step is assigning of the work to the    |
|    | pertaining |     enumerator by the crew leader. The Offeror    |
|    | to this    |     **shall** comply with the OCE OC              |
|    | section.   |     Functionality Reference Documents detail of   |
|    |            |     functions, fields and reporting needed for    |
|    |            |     this process.*                                |
|    |            |                                                   |
|    |            | ## This function shall only                       |
|    |            | allow assignments of valid employees based on a s |
|    |            | imulated check and interface to the DAPPS system  |
|    |            |                                                   |
|    |            | Send Assignments to MCEs                          |
|    |            |                                                   |
|    |            | -   At completion of Make Assignment process      |
|    |            |     (either via the office or crew leader         |
|    |            |     functionality) the Offeror 's solution        |
|    |            |     **shall** transmit the assignment to the      |
|    |            |     enumerators' MCEs                             |
|    |            |                                                   |
|    |            | Assignment/Block-Level History Files Created and  |
|    |            | Maintained                                        |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, a comprehensive approach    |
|    |            |     for the OCE to track, report, and maintain    |
|    |            |     status on the progress of all assignments,    |
|    |            |     systems interactions, and uses of the MCE.*   |
+----+------------+---------------------------------------------------+
| 3  | Offeror 's | Crew Leader MCE receives information about work   |
|    | MCE        | to be assigned.                                   |
|    |            |                                                   |
|    | See        | Crew Leader Make Enumerator Assignments           |
|    | [Section C |                                                   |
|    | &          | -   *This functionality **shall** enable the crew |
|    | J]{.       |     leader to assign work to enumerators via the  |
|    | underline} |     MCE.*                                         |
|    | for a list |                                                   |
|    | of         | Enumerator MCE Receives Assignments               |
|    | functions, |                                                   |
|    | fields and | Enumerator Conducts Address Canvassing            |
|    | reporting  |                                                   |
|    | needed     | -   *See MCE Functionality Reference Documents    |
|    | pertaining |     for a full list of functions, fields, and     |
|    | to this    |     reporting that **shall** be required for      |
|    | section.   |     Assignment Management*                        |
|    |            |                                                   |
|    |            | -   *See MCE Functionality Reference Documents    |
|    |            |     for a full list of functions, fields, and     |
|    |            |     reporting needed for Mapping that **shall**   |
|    |            |     be required (note - exclude updating/moving   |
|    |            |     existing street features from required        |
|    |            |     functionality)*                               |
|    |            |                                                   |
|    |            | -   *See MCE Functionality Reference Documents    |
|    |            |     for a full list of functions, fields, and     |
|    |            |     reporting that **shall** be required for      |
|    |            |     Address List*                                 |
|    |            |                                                   |
|    |            | -   *See MCE Functionality Reference Documents    |
|    |            |     for a full list of functions, fields, and     |
|    |            |     reporting that **shall** be required for T&A* |
|    |            |                                                   |
|    |            | MCE Sends Completed Work                          |
|    |            |                                                   |
|    |            | When all addresses for a Census Block are         |
|    |            | completed, user **shall** validates completion    |
|    |            | and MCE **shall** send data to OCE                |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for the |
|    |            |     enumerator to validate when they have fully   |
|    |            |     completed each case and their entire          |
|    |            |     assignment. Note, the Universe files contain  |
|    |            |     field(s)which record this validation.*        |
|    |            |                                                   |
|    |            | At end of day MCE prompts user to complete T&A    |
|    |            | for the day if not already done, then releases    |
|    |            | the T&A data for supervisor review.               |
|    |            |                                                   |
|    |            | -   *Offeror **shall** also prototype the linking |
|    |            |     of work completed that day to the T&A         |
|    |            |     information submitted.*                       |
+----+------------+---------------------------------------------------+
| 4  | Offeror 's | OCE near real-time monitoring of field staff      |
|    | OCE        | activity **shall** report:\                       |
|    |            | Assignments/ Blocks/Addresses Not Sent\           |
|    | See        | Assignments /Blocks/ Addresses Sent\              |
|    | [Section C | Assignments /Blocks/ Addresses Acknowledges\      |
|    | &          | Assignments //Blocks/ Addresses Completed\        |
|    | J]{.       | T&As Completed/Approved/Disapproved               |
|    | underline} |                                                   |
|    | for a list | Assignment/Block-Level History Files **shall** be |
|    | of         | Updated                                           |
|    | functions, |                                                   |
|    | fields and | Compile/Send Enumerator Daily Assignment Status   |
|    | reporting  | Report                                            |
|    | needed     |                                                   |
|    | pertaining | -   *Offeror **shall** propose, and the prototype |
|    | to this    |     will demonstrate, their best approach for     |
|    | section.   |     complete assignment status information to be  |
|    |            |     relayed to the enumerator*                    |
|    |            |                                                   |
|    |            | Compile/Send Crew leader MCE Daily Enumerator     |
|    |            | Status                                            |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for     |
|    |            |     assignment status information on enumerators  |
|    |            |     to be relayed to the assigned crew leader*    |
|    |            |                                                   |
|    |            | Compile/Send Crew leader MCE Daily Enumerator T&A |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for T&A |
|    |            |     information on enumerators to be relayed to   |
|    |            |     the assigned crew leader*                     |
+----+------------+---------------------------------------------------+
| 5  | Offeror 's | Crew leader Review Daily Enumerator Status & T&A  |
|    | MCE        |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    | See        |     will demonstrate, their best approach for     |
|    | [Section C |     this function.*                               |
|    | &          |                                                   |
|    | J]{.       | Crew leader Approve Enumerator Status & T&A       |
|    | underline} |                                                   |
|    | for a list | -   *Offeror **shall** propose, and the prototype |
|    | of         |     will demonstrate, their best approach for     |
|    | functions, |     this function*.                               |
|    | fields and |                                                   |
|    | reporting  | Crew leader Disapprove Enumerator Status & T&A    |
|    | needed     |                                                   |
|    | pertaining | -   *Offeror **shall** propose, and the prototype |
|    | to this    |     will demonstrate, their best approach for     |
|    | section.   |     this function.*                               |
|    |            |                                                   |
|    |            | Crew leader **shall** Message a Enumerator(s)     |
+----+------------+---------------------------------------------------+
| 6  | Offeror 's | OCE OC functionality acts on Crew leader Approval |
|    | OCE        | of Enumerator Status and T&A                      |
|    |            |                                                   |
|    | See        | -   *Offeror **shall** propose, and the prototype |
|    | [Section C |     will demonstrate, their best approach for     |
|    | &          |     this function.*                               |
|    | J]{.       |                                                   |
|    | underline} | OCE OC acts on Crew leader Disapproval of         |
|    | for a list | Enumerator Status and T&A                         |
|    | of         |                                                   |
|    | functions, | -   *Offeror **shall** propose, and the prototype |
|    | fields and |     will demonstrate, their best approach for     |
|    | reporting  |     this function.*                               |
|    | needed     |                                                   |
|    | pertaining | OCE sends Crew leader Messaging to Enumerator     |
|    | to this    |                                                   |
|    | section.   | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for     |
|    |            |     this function.*                               |
|    |            |                                                   |
|    |            | Assignment/Block-Level History Files Updated      |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for     |
|    |            |     this function.*                               |
+----+------------+---------------------------------------------------+
| 8  | Offeror 's | Enumerator **shall** review messages from Crew    |
|    | MCE        | leader                                            |
|    |            |                                                   |
|    | See        | Enumerator **shall** review updated status report |
|    | [Section C | on their Assignments and T&A                      |
|    | &          |                                                   |
|    | J]{.       | Enumerator **shall** fix their T&A that was       |
|    | underline} | disapproved and resends                           |
|    | for a list |                                                   |
|    | of         |                                                   |
|    | functions, |                                                   |
|    | fields and |                                                   |
|    | reporting  |                                                   |
|    | needed     |                                                   |
|    | pertaining |                                                   |
|    | to this    |                                                   |
|    | section.   |                                                   |
+----+------------+---------------------------------------------------+
| 9  | Offeror 's | OCE near real-time monitoring of field staff      |
|    | OCE        | activity **shall** include:\                      |
|    |            | T&As Completed/Approved/Disapproved               |
|    | See        |                                                   |
|    | [Section C | Assignment/Block-Level History Files **shall** be |
|    | &          | Updated                                           |
|    | J]{.       |                                                   |
|    | underline} | Compile/Send Enumerator Daily Assignment Status   |
|    | for a list | Rpt                                               |
|    | of         |                                                   |
|    | functions, | -   *Offeror **shall** propose, and the prototype |
|    | fields and |     will demonstrate, their best approach for     |
|    | reporting  |     this function. See MCE Functionality          |
|    | needed     |     Reference Documents for details on how the    |
|    | pertaining |     Census Bureau will accomplish this internally |
|    | to this    |     for their 2006 test.*                         |
|    | section.   |                                                   |
|    |            | Compile/Send Crew leader MCE Daily Enumerator     |
|    |            | Status                                            |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for     |
|    |            |     this function. See MCE Functionality          |
|    |            |     Reference Documents for details on how the    |
|    |            |     Census Bureau will accomplish this internally |
|    |            |     for their 2006 test.*                         |
|    |            |                                                   |
|    |            | Compile/Send Crew leader MCE Daily Enumerator T&A |
|    |            |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    |            |     will demonstrate, their best approach for     |
|    |            |     this function. See MCE Functionality          |
|    |            |     Reference Documents for details on how the    |
|    |            |     Census Bureau will accomplish this internally |
|    |            |     for their 2006 test.*                         |
+----+------------+---------------------------------------------------+
| 10 | Offeror 's | Crew leader Review Daily Enumerator Status & T&A  |
|    | MCE        |                                                   |
|    |            | -   *Offeror **shall** propose, and the prototype |
|    | See        |     will demonstrate, their best approach for     |
|    | [Section C |     this function.*                               |
|    | &          |                                                   |
|    | J]{.       | Crew leader Approve Enumerator Status & T&A       |
|    | underline} |                                                   |
|    | for a list | -   *Offeror **shall** propose, and the prototype |
|    | of         |     will demonstrate, their best approach for     |
|    | functions, |     this function.*                               |
|    | fields and |                                                   |
|    | reporting  |                                                   |
|    | needed     |                                                   |
|    | pertaining |                                                   |
|    | to this    |                                                   |
|    | section.   |                                                   |
+----+------------+---------------------------------------------------+
| 11 | Offeror    | **Shall** Package on a CD and deliver, or         |
|    |            | electronically send, all completed assignment     |
|    | See        | files from the prototype test to the Census       |
|    | [Section   | Bureau for processing                             |
|    | J]{.       |                                                   |
|    | underline} |                                                   |
|    | for output |                                                   |
|    | file       |                                                   |
|    | formats    |                                                   |
+----+------------+---------------------------------------------------+
| 12 | Census HQ  | Verify completed Block data are usable by HQ      |
+----+------------+---------------------------------------------------+

5.0 Prototype Test and Evaluation Strategy

[Overview]{.underline}

The pre-award evaluation of the prototype for Address Canvassing shall
culminate in each Offeror conducting of a field demonstration and test
of their prototype for the Government. Since the prototype's design from
each Offeror may differ widely in approach, each Offeror shall have
responsibility for developing a comprehensive test plan for their
prototype to validate their prototype's ability to a) meet the
functional requirements specified in the table included in this
document, b) gather and document performance metrics related to those
functional requirements and general operation of the prototype's
components, and c) gather and document data related to usability of
their prototype. (Note -- the Government will provide the test subjects
the Offeror is to use for their usability test. The offer may provide
them up to 4 hours of training, as deemed appropriate, prior to their
conducting of the usability test.). The government will review, modify
as necessary to ensure test plan consistency and completeness of all
Offerors, and approve the test plan. The government will observe the
field demonstration and test conducted by each Offeror and subsequently
analyze and evaluate the results based on the data gathered and
documented by the Offeror according to each test plan.

[Prototype Process and Schedule]{.underline}

Each Offeror shall submit at the beginning of the technical exchange
period, the specific topics related to the Address Canvassing prototype
that they would like to discuss with the government and a proposed start
date for initiating these discussions. The government will develop a
detailed schedule for meeting with Offerors to carry out this technical
exchange based on this information and the timing and resource
requirements for other ongoing pre-award evaluation activities. The
information provided by Offerors shall include the following:

-   Requested date for initiating technical exchange discussions

-   Technical, operational, or other topics organized by individual
    sessions required;

-   High-level functional design of their prototype for government
    review and validation as meeting all functional needs;

-   A comprehensive field demonstration and test plan by 11/1/2005,
    including test scenarios, test cases, and test results gathering
    methods and instruments;

-   Dates of any intended intermediate prototype submissions for cursory
    evaluation by the Government should the Offeror desire feedback on
    their prototype's strengths/weaknesses prior to the field
    demonstration and test; and

-   Provide suggested dates by 11/1/2005 for the conduct of the
    Prototype Test Demonstration during the scheduled test period (see
    Section L.14).

The comprehensive field demonstration and test plan submitted by each
Offeror shall segment their proposed test into the following areas:

1.  Validation of Functionality

-   Receipt of Universe files from the government

-   Universe file processing and OC functionality

-   Telecommunication functionality (i.e., transmissions to and from the
    MCE, assessment of the performance of the full telecommunications
    architecture under production load, etc.)

-   MCE functionality

-   Delivery of output files to the government for validation

2.  Performance Metric Gathering

> Performance metrics gathered shall include, but not be limited to the
> following:

-   Measure Universe files processing time

-   Measure network transmissions (indicate date-time to second for
    each)

    -   Time start & complete send of assignment from OCE

    -   Time start & complete receipt of assignment for MCE

    -   Time start & complete send of completed block for MCE

    -   Time start & complete receipt of completed block for OCE

-   Measure MCE boot-up time

-   Measure time to perform each function (e.g., logon authentication,
    display map, display address list, update address list, etc.)

3.  Usability Metric Gathering

4.  Security Controls\
    Note that each Offeror shall include validation of security controls
    within each sub-category of area 1 above

[Assessment Plan]{.underline}

After completion of the field demonstration and test, the strengths,
weaknesses, and risks of each Offerors' prototype will be evaluated
based on the test plan results and the government's observation of the
test plan's execution, according to the same evaluation criteria to be
used by the Government for final written proposals to the RFP (See
Section M of the FDCA RFP).

6.0 Activity Schedule

See Section L.14.

**\[END SECTION L\]**

#