**SECTION F -- DELIVERIES OR PERFORMANCE**

**F.1 52.252.2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)**

This contract incorporates one or more clauses 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. Also, the
full text of a clause may be accessed electronically at this address:
<http://www.arnet.gov/far/>.

(End of clause)

I. FEDERAL ACQUISITION REGULATION CLAUSES

  --------------------------------------------------------------------------------------------
  [NUMBER]{.underline}   [TITLE]{.underline}                              [DATE]{.underline}
  ---------------------- ------------------------------------------------ --------------------
  52.242-15              Stop work order                                  Aug-89

  52.242-15              Stop work order - Alternate I (Apr 1984)         Aug-89

  52.242-17              Government Delay of Work                         Aug-84
  --------------------------------------------------------------------------------------------

**[\
]{.underline}**

**F.1.1 52.211-8 Time of Delivery (Jun 97)**

(a) The Government requires delivery to be made according to the
    following schedule:

  ---------------- ------------ -------------------------------------------
  Required                      
  Delivery                      
  Schedule                      

  *\[Contracting                
  Officer insert                
  specific                      
  details\]*                    

  Item No.         Quantity     Within Days After Date of Contract

                                

                                

                                
  ---------------- ------------ -------------------------------------------

> The Government will evaluate equally, as regards time of delivery,
> offers that propose delivery of each quantity within the applicable
> delivery period specified above. Offers that propose delivery that
> will not clearly fall within the applicable required delivery period
> specified above, will be considered non responsive and rejected. The
> Government reserves the right to award under either the required
> delivery schedule or the proposed delivery schedule, when an offeror
> offers an earlier delivery schedule than required above. If the
> offeror proposes no other delivery schedule, the required delivery
> schedule above will apply.

  ------------- -------------- ------------------------------------------
  Offeror\'s                   
  Proposed                     
  Delivery                     
  Schedule                     

  Item No.      Quantity       Within Days After Date of Contract

                               

                               

                               
  ------------- -------------- ------------------------------------------

> \(b\) Attention is directed to the Contract Award provision of the
> solicitation that provides that a written award or acceptance of offer
> mailed, or otherwise furnished to the successful offeror, results in a
> binding contract. The Government will mail or otherwise furnish to the
> offeror an award or notice of award not later than the day award is
> dated. Therefore, the offeror should compute the time available for
> performance beginning with the actual date of award, rather than the
> date the written notice of award is received from the Contracting
> Officer through the ordinary mails. However, the Government will
> evaluate an offer that proposes delivery based on the Contractor\'s
> date of receipt of the contract or notice of award by adding (1) five
> calendar days for delivery of the award through the ordinary mails, or
> (2) one working day if the solicitation states that the contract or
> notice of award will be transmitted electronically. (The term
> \"working day\" excludes weekends and U.S. Federal holidays.) If, as
> so computed, the offered delivery date is later than the required
> delivery date, the offer will be considered nonresponsive and
> rejected.
>
> (End of clause)
>
> *Alternate I (Apr 1984)*. If the delivery schedule is expressed in
> terms of specific calendar dates or specific periods and is based on
> an assumed date of award, the contracting officer may substitute the
> following paragraph (b) for paragraph (b) of the basic clause. The
> time may be expressed by substituting \"on or before\"; \"during the
> months \_\_\_\_\_\_\_\_\_\_\"; or \"not sooner than
> \_\_\_\_\_\_\_\_\_\_ or later than \_\_\_\_\_\_\_\_\_\_\_\" as
> headings for the third column of paragraph (a) the basic clause. (b)
> The delivery dates or specified periods above are based on the
> assumption that the Government will make award by \_\_\_\_\_\_\_\_
> \[*Contracting Officer insert date*\]. Each delivery date in the
> delivery schedule above will be extended by the number of calendar
> days after the above date that the contract is in fact awarded.
> Attention is directed to the Contract Award provision of the
> solicitation that provides that a written award or acceptance of offer
> mailed or otherwise furnished to the successful offeror results in a
> binding contract. Therefore, the offeror should compute the time
> available for performance beginning with the actual date of award,
> rather than the date the written notice of award is received from the
> Contracting Officer through the ordinary mails.
>
> *Alternate II (Apr 1984)*. If the delivery schedule is expressed in
> terms of specific calendar dates or specific periods and is based on
> an assumed date the contractor will receive notice of award, the
> contracting officer may substitute the following paragraph (b) for
> paragraph (b) of the basic clause. The time may be expressed by
> substituting \"within days after the date of receipt of a written
> notice of award\" as the heading for the third column of paragraph (a)
> of the basic clause.
>
> \(b\) The delivery dates or specific periods above are based on the
> assumption that the successful offeror will receive notice of award by
> \_\_\_\_\_\_\_\_ \[*Contracting Officer insert date*\]. Each delivery
> date in the delivery schedule above will be extended by the number of
> calendar days after the above date that the Contractor receives notice
> of award; provided, that the Contractor promptly acknowledges receipt
> of notice of award.
>
> *Alternate III (Apr 1984)*. If the delivery schedule is to be based on
> the actual date the contractor receives a written notice of award, the
> contracting officer may delete paragraph (b) of the basic clause. The
> time may be expressed by substituting \"within days after the date of
> receipt of a written notice of award\" as the heading for the third
> column of paragraph (a) of the basic clause.

**F.1.2 52.211-9 Desired and Required Time of Delivery (Jun-97)**

> \(a\) The Government desires delivery to be made according to the
> following schedule:

  ---------------- -------------- ------------------------------------------
  Desired Delivery                
  Schedule                        

  *\[Contracting                  
  Officer insert                  
  specific                        
  details\]*                      

  Item No.         Quantity       Within Days After Date of Contract

                                  

                                  

                                  
  ---------------- -------------- ------------------------------------------

> If the offeror is unable to meet the desired delivery schedule, it
> may, without prejudicing evaluation of its offer, propose a delivery
> schedule below. However, the offeror\'s proposed delivery schedule
> must not extend the delivery period beyond the time for delivery in
> the Government\'s required delivery schedule as follows:

  ---------------- ------------- --------------------------------------------
  Required                       
  Delivery                       
  Schedule                       

  *\[Contracting                 
  Officer insert                 
  specific                       
  details\]*                     

  Item No.         Quantity      Within Days After Date of Contract

                                 

                                 

                                 
  ---------------- ------------- --------------------------------------------

> Offers that propose delivery of a quantity under such terms or
> conditions that delivery will not clearly fall within the applicable
> required delivery period specified above, will be considered non
> responsive and rejected. If the offeror proposes no other delivery
> schedule, the desired delivery schedule above will apply.

  ---------------- ------------- --------------------------------------------
  Offeror\'s                     
  Proposed                       
  Delivery                       
  Schedule                       

  *\[Contracting                 
  Officer insert                 
  specific                       
  details\]*                     

  Item No.         Quantity      Within Days After Date of Contract

                                 

                                 

                                 
  ---------------- ------------- --------------------------------------------

> \(b\) Attention is directed to the Contract Award provision of the
> solicitation that provides that a written award or acceptance of offer
> mailed or otherwise furnished to the successful offeror results in a
> binding contract. The Government will mail or otherwise furnish to the
> offeror an award or notice of award not later than the day the award
> is dated. Therefore, the offeror shall compute the time available for
> performance beginning with the actual date of award, rather than the
> date the written notice of award is received from the Contracting
> Officer through the ordinary mails. However, the Government will
> evaluate an offer that proposes delivery based on the Contractor\'s
> date of receipt of the contract or notice of award by adding (1) five
> calendar days for delivery of the award through the ordinary mails, or
> (2) one working day if the solicitation states that the contract or
> notice of award will be transmitted electronically. (The term
> \"working day\" excludes weekends and U.S. Federal holidays.) If, as
> so computed, the offered delivery date is later than the required
> delivery date, the offer will be considered non responsive and
> rejected.
>
> (End of clause)
>
> *Alternate I (Apr 1984)*. If the delivery schedule is expressed in
> terms of specific calendar dates or specific periods and is based on
> an assumed date of award, the contracting officer may substitute the
> following paragraph (b) for paragraph (b) of the basic clause. The
> time may be expressed by substituting \"on or before\"; \"during the
> months \_\_\_\_\_\_\_\"; or \"not sooner than \_\_\_\_\_\_, or later
> than \_\_\_\_\_\_\" as headings for the third column of paragraph (a)
> of the basic clause.
>
> \(b\) The delivery dates or specific periods above are based on the
> assumption that the Government will make award by \_\_\_\_\_\_\_\_\_
> \[*Contracting Officer insert date*\]. Each delivery date in the
> delivery schedule above will be extended by the number of calendar
> days after the above date that the contract is in fact awarded.
> Attention is directed to the Contract Award provision of the
> solicitation that provides that a written award or acceptance of offer
> mailed or otherwise furnished to the successful offeror results in a
> binding contract. Therefore, the offeror shall compute the time
> available for performance beginning with the actual date of award,
> rather than the date the written notice of award is received from the
> Contracting Officer through the ordinary mails.
>
> *Alternate II (Apr 1984)*. If the delivery schedule is expressed in
> terms of specific calendar dates or specific periods and is based on
> an assumed date the contractor receives notice of award, the
> contracting officer may substitute the following paragraph (b) for
> paragraph (b) of the basic clause. The time may be expressed by
> substituting \"within days after the date of receipt of a written
> notice of award\" as the heading of the third column of paragraph (a)
> of the basic clause.
>
> \(b\) The delivery dates or specific periods above are based on the
> assumption that the successful offeror will receive notice of award by
> \_\_\_\_\_\_\_\_\_\_\_ \[*Contracting Officer insert date*\]. Each
> delivery date in the delivery schedule above will be extended by the
> number of calendar days after the above date that the Contractor
> receives notice of award; provided, that the Contractor promptly
> acknowledges receipt of notice of award.
>
> *Alternate III (Apr 1984*). If the delivery schedule is to be based on
> the actual date the contractor receives a written notice of award, the
> contracting officer may delete paragraph (b) of the basic clause. The
> time may be expressed by substituting \"within days after the date of
> receipt of a written notice of award\" as the heading of the third
> column of paragraph (a) of the basic clause.

# F.2 EFFECTIVE PERIOD OF THE CONTRACT

The period of performance for this contract is divided into three (3)
primary phases, Phase I, Phase II, and Phase III, with Phase I being
separated into two (2) sub phases, Phases IA and IB. References to Phase
I within this document **shall** include both sub phases. The dates for
these phases are defined in Clause H.1, "*Option to Extend Term of the
Contract*."

# F.3 DELIVERABLES 

In performing the services and providing the support described in the
Statement of Work, the Contractor **shall** provide the written
deliverable items as described within this document. Note that this list
does not comprise *all work products* that will result from the DRIS
contract work, to include system reports and data deliverables; this
list is meant to outline written deliverables only.

## F.3.1 Deliverable Quality Standards

> The Government will work with the Contractor to define specific
> quality standards for each deliverable. For the documents themselves,
> the Government expects them to be timely, thorough, and accurate. That
> is, they arrive at the designated Government facility on or before the
> scheduled due date; they completely address the Government's
> requirements; and the documents have no more than a few minor errors.
> As each deliverable is usually the end result of a series of
> activities, prior to starting on the task, it is vital that the
> Contractor and the Government agree on the approach for the
> deliverable, the activities involved to develop it, and the
> outline/organization and any other expectations for the final product.

## F.3.2 Deliverable Reviews and Acceptance

> After the delivery of a document, the Government will have twenty (20)
> business days to review the document and provide the Contractor with a
> list of any required revisions and/or corrections. The Contractor then
> will have five (5) business days to make these corrections and
> redeliver the document to the Government. However, the Contractor is
> encouraged to review drafts of documents with the Government task area
> leads and other stakeholders, reducing the likelihood that the
> document will be found deficient, and therefore reducing rework for
> all parties.

# F.3.3 Delivery Method

> Deliverables **shall** be provided electronically whenever possible.
> Electronic delivery **shall** consist of one (1) CD with the
> deliverable files in both Acrobat.pdf and a current Microsoft Word
> format unless the Government requests a different format (i.e.
> wInsight, etc.). The Contractor **shall** also provide one unbound
> hard copy. Delivery via e-mail may be acceptable, or required, in some
> cases, per direction of the DRIS Program Manager (PM). All
> correspondence forwarding deliverables **shall** be addressed to the
> PM and the CO, and delivered to the point of contact listed in Clause
> F.26 "*Delivery Location*." When possible, delivery **shall** be
> coordinated in advance with the point of contact listed in F.26
> "*Delivery Location*."

## F.3.4 List of Deliverables

> The following chart provides a list and schedule of deliverables due
> during Phases IA and IB. The sections after the chart describe the
> deliverables in detail. Many of the Phase I deliverables are Dress
> Rehearsal specific. Phase II deliverables will be determined during
> Phase I. Please note that the dates reflected in the chart are subject
> to change.

**Phases IA and IB Deliverables Chart**

+------+--------+-----------------------+-----------------+-----------+
| *    | **     | **Deliverable**       | **Initial       | **S       |
| *Sec | Refere |                       | Delivery Date   | ubsequent |
| tion | nces** |                       | (or time after  | Delivery  |
| F**  |        |                       | Contract        | Date(s)** |
|      |        |                       | Award)**        |           |
+======+========+=======================+=================+===========+
|      |        |                       |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F    | C.3.6  | Complete Contract     | 1 week          |           |
| .4.1 |        | Startup and Kick-off  |                 |           |
|      |        | Meeting               |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F    | C.3    | CMMI and ISO 9001     | 1 month         | Redeliver |
| .4.4 |        | Compliance Plan       |                 | if        |
|      |        |                       |                 | revised   |
+------+--------+-----------------------+-----------------+-----------+
| F    | C.3.3  | Cost Performance      | 1 month         | Monthly,  |
| .4.3 |        | Report (CPR), and     |                 | by 15^th^ |
|      |        | wInsight file         |                 | of        |
|      |        |                       |                 | following |
|      |        |                       |                 | month     |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | 1 month         | 10^th^    |
| .4.2 | .mark} |                       |                 | day of    |
|      |        | Monthly Status Report |                 | each      |
|      | C.3.7  |                       |                 | month     |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | TBD             | Monthly,  |
| .4.5 | .mark} |                       |                 | by 15^th^ |
|      |        | Inventory Control     |                 | of        |
|      | C.3.12 | Report                |                 | following |
|      |        |                       |                 | month     |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3.8  | Deliver draft         | 2 months        | Redeliver |
| 4.12 |        | Subcontracting and    |                 | if        |
|      |        | Subcontract           |                 | revised   |
|      |        | Participation Plan    |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | 2 months        | Monthly   |
| .4.8 | .mark} |                       | (agenda due 5   | (agenda   |
|      |        | Program Management    | days prior)     | due 5     |
|      | C.3.10 | Review (PMR) Meeting  |                 | days      |
|      |        | Agenda                |                 | prior)    |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | Within three    | Monthly   |
| .4.8 | .mark} |                       | working days    |           |
|      |        | PMR Meeting Minutes   | after a meeting |           |
|      | C.3.11 | and Action Items      |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | 4 months        | Living    |
| .4.7 | .mark} |                       |                 | document  |
|      |        | Deliver Program       |                 | with      |
|      | C.3    | Management Plan for   |                 | minimum   |
|      |        | DRIS                  |                 | of annual |
|      |        |                       |                 | updates   |
+------+--------+-----------------------+-----------------+-----------+
| F    | []{    | []{.mark}             | TBD             | Redeliver |
| .4.9 | .mark} |                       |                 | if        |
|      |        | Deliver Contract Work |                 | revised   |
|      | C.3.2  | Breakdown Structure   |                 |           |
|      |        | (CWBS) and CWBS       |                 |           |
|      |        | dictionary            |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.6  | C.6.2  | Deliver first draft   | 4 months        | NLT       |
|      |        | Concept of Operations |                 | 8/1/07    |
|      |        | (CONOPs) and Systems  |                 | (final    |
|      |        | Architecture for DRIS |                 | 2008 DR)  |
|      |        | (2008 Dress Rehearsal |                 |           |
|      |        | (DR) specific)        |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.5  | C.10.1 | Deliver draft         | 4 months        | As needed |
|      |        | documents needed for  |                 | for       |
|      |        | security              |                 | security  |
|      |        | accreditation (2008   |                 | accre     |
|      |        | DR specific)          |                 | ditations |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3.4  | DRIS Financial Report | 4/15/06         | Every 6   |
| 4.13 |        |                       |                 | months    |
+------+--------+-----------------------+-----------------+-----------+
| F.7  | C.5    | Deliver initial draft | 8 months        | NLT       |
|      |        | Test Plan for DRIS    |                 | 8/1/07    |
|      |        | (2008 DR specific)    |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.8  | C.11   | Deliver initial draft | 8 months        | NLT       |
|      |        | Quality Assurance     |                 | 8/1/07    |
|      |        | Plan for DRIS (2008   |                 | (final    |
|      |        | DR specific)          |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.9  | C.11   | Deliver draft Quality | 8 months        | NLT       |
|      |        | Control Plan for DRIS |                 | 8/1/07    |
|      |        | (2008 DR specific)    |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.10 | C.7    | Deliver draft         | 1 year          | NLT       |
|      |        | detailed              |                 | 8/1/07    |
|      |        | documentation         |                 | (final    |
|      |        | including System      |                 | for 2008  |
|      |        | Design Specifications |                 | DR)       |
|      |        | for all DRIS systems  |                 |           |
|      |        | and documentation     |                 |           |
|      |        | addressing specific   |                 |           |
|      |        | handling of           |                 |           |
|      |        | Exceptions; QA and    |                 |           |
|      |        | QC; scalability;      |                 |           |
|      |        | interfaces with the   |                 |           |
|      |        | Government's systems; |                 |           |
|      |        | data standardization  |                 |           |
|      |        | and organization; MIS |                 |           |
|      |        | report design;        |                 |           |
|      |        | content, and sources  |                 |           |
|      |        | of the data; user     |                 |           |
|      |        | interface design      |                 |           |
|      |        | documents for         |                 |           |
|      |        | telephone and         |                 |           |
|      |        | Internet; and         |                 |           |
|      |        | security requirements |                 |           |
|      |        | for all components    |                 |           |
|      |        | and functions of DRIS |                 |           |
|      |        | (2008 DR specific).   |                 |           |
|      |        | This includes         |                 |           |
|      |        | updating and          |                 |           |
|      |        | delivering any        |                 |           |
|      |        | documents previously  |                 |           |
|      |        | delivered and showing |                 |           |
|      |        | traceability to       |                 |           |
|      |        | Government            |                 |           |
|      |        | requirements.         |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.11 | C.9.1  | Deliver draft         | 1 year          | NLT       |
|      |        | Acquisition Plan      |                 | 8/1/07    |
|      |        | (2008 DR specific).   |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.12 | C.7    | Deliver Physical      | 1 year          | NLT       |
|      |        | Architecture Plan     |                 | 8/1/07    |
|      |        | (servers,             |                 | (final    |
|      |        | communications        |                 | for 2008  |
|      |        | network, etc.). (2008 |                 | DR)       |
|      |        | DR specific)          |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.13 | C      | Deliver draft         | 1 year          | NLT       |
|      | .4.2.2 | External Interface    |                 | 8/1/07    |
|      |        | Control Document      |                 | (final    |
|      |        | (EICD) (2008 DR       |                 | for 2008  |
|      |        | specific)             |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.14 | C.7    | The contractor        | 1 year          | 18 months |
|      |        | **shall** develop,    |                 | (final    |
|      |        | deliver, maintain,    |                 | for 2008  |
|      |        | and adhere to         |                 | DR)       |
|      |        | detailed site plans   |                 |           |
|      |        | (i.e. construction    |                 |           |
|      |        | drawings) for all     |                 |           |
|      |        | DRIS facilities it    |                 |           |
|      |        | will initiate and     |                 |           |
|      |        | operate. The Site     |                 |           |
|      |        | Plans **shall**       |                 |           |
|      |        | specify use of all    |                 |           |
|      |        | space, outline        |                 |           |
|      |        | adherence to          |                 |           |
|      |        | Government            |                 |           |
|      |        | requirements, and     |                 |           |
|      |        | provide for site      |                 |           |
|      |        | security (2008 DR     |                 |           |
|      |        | specific).            |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.15 | C.8,   | Deliver draft 2008 DR | 1 year          | NLT       |
|      | C.9    | Deployment Plan for   |                 | 8/1/07    |
|      | .2.4.1 | DRIS                  |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F    | C.3    | CMMI and ISO 9001     | 1 year          | During    |
| .4.4 |        | appraisal/audit       |                 | each      |
|      |        | results               |                 | phase     |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3.4  | Contract Funds Status | 1/15/06         | Quarterly |
| 4.13 |        | Report (CFSR)         |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3    | Document Tree         | 1/15/06         | Quarterly |
| 4.14 |        |                       |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3.9, | Deliver               | n/a             | 10/20/06  |
| 4.15 | H.13   | Self-Assessment for   |                 |           |
|      |        | 1^st^ Award Fee       |                 |           |
|      |        | period (which ends    |                 |           |
|      |        | 365 days after        |                 |           |
|      |        | funding)              |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.16 | C.7    | Design walk-through   | 18 months       | 24 months |
|      |        |                       |                 | after     |
|      |        |                       |                 | award     |
+------+--------+-----------------------+-----------------+-----------+
| F.24 | C.4.   | Draft MIS Reports     | Within 18       | NLT       |
|      | 2.12.4 | Guide                 | months          | 8/1/07    |
|      |        |                       |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.25 | C.8    | 2008 DR Systems       | Within 18       | NLT       |
|      |        | Operating Guide and   | months          | 8/1/07    |
|      |        | User Manual           |                 | (final    |
|      |        |                       |                 | for 2008  |
|      |        |                       |                 | DR)       |
+------+--------+-----------------------+-----------------+-----------+
| F.   | C.3.9, | Deliver               | n/a             | 10/20/07  |
| 4.15 | H.13   | Self-Assessment for   |                 |           |
|      |        | Award Fee 2^nd^       |                 |           |
|      |        | Period (which ends    |                 |           |
|      |        | 730 days from         |                 |           |
|      |        | contract funding)     |                 |           |
+------+--------+-----------------------+-----------------+-----------+
|      | C.7    | Deliver final DR      | n/a             | 11/11/07  |
|      |        | versions of all DRIS  |                 |           |
|      |        | documents previously  |                 |           |
|      |        | delivered (only if    |                 |           |
|      |        | updates needed based  |                 |           |
|      |        | on testing results)   |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.17 | C.7,   | Certify Ready-For-Use | n/a             | 12/11/07  |
|      | C.8    | of DRIS at all 2008   |                 |           |
|      |        | DR facilities         |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.   | []{    | []{.mark}             | TBD             | TBD       |
| 4.10 | .mark} |                       |                 |           |
|      |        | Project Schedule      |                 |           |
|      | C.3.2  |                       |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.   | []{    | []{.mark}             | TBD             | TBD       |
| 4.11 | .mark} |                       |                 |           |
|      |        | Life Cycle Cost       |                 |           |
|      | C.3.2  | Estimate (LCCE)       |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.18 | H.14   | Subcontracting Report | 4/1/06          | Semi      |
|      |        | (SF 294)              |                 | -annually |
+------+--------+-----------------------+-----------------+-----------+
| F.19 | H.14   | Summary               | 10/15/06        | Q         |
|      |        | Subcontracting Report |                 | uarterly, |
|      |        | (SF 295)              |                 | within 15 |
|      |        |                       |                 | days      |
|      |        |                       |                 | following |
|      |        |                       |                 | the close |
|      |        |                       |                 | of each   |
|      |        |                       |                 | calendar  |
|      |        |                       |                 | quarter   |
+------+--------+-----------------------+-----------------+-----------+
| F    | C.3.14 | Health, Safety, and   | 2007 (month     | Monthly,  |
| .4.6 |        | Security Report       | TBD)            | by the    |
|      |        |                       |                 | 15^th^ of |
|      |        |                       |                 | following |
|      |        |                       |                 | month     |
+------+--------+-----------------------+-----------------+-----------+
| F.20 | C.7    | Deliver Phase II      | 5/1/08          | TBD       |
|      |        | proposal -- Build-    |                 |           |
|      |        | out/Fit-up            |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.20 | C.7    | Deliver Phase II      | 9/1/08          | TBD       |
|      |        | proposal -- System    |                 |           |
|      |        | Operations            |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.22 | C.8    | Deliver Lessons       | 9/15/08         | 12/31/08  |
|      |        | Learned from Dress    |                 |           |
|      |        | Rehearsal             |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.21 | C.8    | Complete 2008 DR      | NLT 12/31/08    | n/a       |
|      |        | Production Activities |                 |           |
+------+--------+-----------------------+-----------------+-----------+
|      | C.7    | Deliver initial 2010  | 12/31/08        | TBD       |
|      |        | updates of all DRIS   |                 |           |
|      |        | documentation listed  |                 |           |
|      |        | above in this table   |                 |           |
|      |        | based on 2008 DR      |                 |           |
|      |        | lessons learned       |                 |           |
+------+--------+-----------------------+-----------------+-----------+
| F.23 | C      | Standardize and       | TBD             | TBD       |
|      | .4.2.7 | Organize Response     |                 |           |
|      |        | Data                  |                 |           |
+------+--------+-----------------------+-----------------+-----------+

# F.4 PROGRAM MANAGEMENT

## F.4.1 Contract Startup and Kick-off Meeting

> The Contractor **shall** conduct a team kick-off meeting, on a date
> specified by the Government after contract award, with the Government
> and other key DRIS personnel. The purpose of the kick-off meeting is
> to introduce the major project participants; communicate the project
> background, scope, and schedule; ensure a common understanding of the
> contract and all obligations and responsibilities of the Contractor
> and the Government; review the activities required to initiate and
> manage the contract; and inform the team of necessary administrative
> items. The Contractor **shall** work with the DRIS Program Office (PO)
> to schedule the contract kick-off meeting.

## F.4.2 Monthly Status Report

> The Contractor **shall** submit, on a monthly basis throughout the
> life of the DRIS contract, a written Monthly Status Report. The
> Contractor **shall** deliver the report by the tenth (10th) day of
> each month for the previous month's activities. The report **shall**
> be concise and at a minimum include the following information:

a.  The Contract Number and reporting period.

b.  Task order numbers and task name (if applicable).

c.  A summary of the technical work in the following format.

    i.  A narrative review of work accomplishments and/or significant
        events for the month.

    ii. Problems and solutions (to include impacts on quality, schedule
        and cost and proposed solutions).

    iii. Percent of work completed toward interim or final deliverables
         and estimates of time to complete deliverables

    iv. Major activities planned for the next month.

d.  Monthly and cumulative contract and task order (if applicable)
    dollars spent to date.

e.  Graph depicting task-spending plan (planned vs. actual completed by
    month and cumulatively).

f.  Indication of funds remaining by contract, phase, and task order (if
    applicable).

g.  Program issues and high level risks including, but not limited to
    the areas of, program management, facilities, equipment, staffing,
    and funding.

h.  Production information including production staffing and other
    production issues.

i.  Status and progress for 508 Compliance.

j.  Maintenance issues, maintenance risks and mitigation activities
    and/or plans.

k.  Security issues, security risks, mitigation activities and/or plans.

> The Contractor and the Government **shall** jointly determine the full
> contents of the report, to include measurements and metrics for
> regular reporting, as well as the performance baselines/standards for
> these measurements, after contract award.
>
> **F.4.3 Cost Performance Report (CPR)**
>
> The Contractor **shall** generate a monthly and cumulative DRIS Cost
> Performance Report (CPR) for each phase/sub phase following the
> appropriate clauses. The level of reporting **shall** be jointly
> determined after contract award based on the Contractor's proposed
> Contract WBSs, however, the Contractor **shall** deliver the CPR at
> least at a minimum of the 3^rd^ level. The Contractor **shall**
> deliver CPR formats 1, 3, 4 and 5 with one cover sheet. The Contractor
> **shall** deliver the CPR by the 15^th^ of each month for the current
> (previous month) and cumulative period for the specific phase. The
> Contractor's CPR **shall** also reflect all subcontractors' EV
> methodology metrics for both the current and cumulative periods. The
> Contractor **shall** show current and cumulative variances and report
> on the reasons for these variances. The current and cumulative
> variance thresholds will be negotiated after contract award. The
> Contractor **shall** provide the Government with a wInsight (the
> Census Bureau's EV software tool) file each month, to be delivered
> with the CPR. Guidelines of Department of Defense (DOD) 5000.22
> (Section 6.4) **shall** be used to establish cost reporting
> requirements for subcontractors on the DRIS contract.

**F.4.4 CMMI and ISO 9001 Compliance Plan and Appraisal/Audit Results**

> Within the first month of contract award, the Contractor **shall**
> provide a plan for CMMI Level 3 and ISO 9001 compliance. The
> Contractor **shall** meet the requirements for this project in a
> manner compatible with the SEI CMMI Level 3 processes and current ISO
> 9001 standards throughout the DRIS period of performance. The
> Contractor **shall** ensure that all deliverables produced by all DRIS
> subcontractors are produced in a manner consistent with CMMI Level 3
> processes ISO 9001 standards, and software engineering best practices.
>
> In addition, within the first year of contract award, the Contractor
> **shall** complete a successful CMMI appraisal to verify attainment of
> Level 3 process maturity and complete a successful ISO 9001 audit on
> the overall DRIS project. The Contractor **shall** again complete the
> same successful appraisal and audit processes within 6 (six) months
> after the start of Phase II. The Contractor **shall** provide the
> Government with all documentation resulting from the CMMI appraisal
> and the ISO 9001 audit as soon as available from the SEI certified
> assessor/appraiser or ISO certified auditor. (Refer to Section C.3 for
> additional information on the CMMI compliance plan and the
> appraisal/audit results.)

### F.4.5 Inventory Control Report

> The Contractor **shall** provide an inventory control report in an
> electronic format compatible with the Government's Property Control
> System. The Contractor **shall** provide the Inventory Control report
> by the 15^th^ of each month with information current through the end
> of the previous month. The Contractor **shall** show all changes to
> DRIS purchased inventory within the Contractor and Government
> facilities for the previous month. The Government will work with the
> Contractor to develop the requirements during Phase IA/IB. (Refer to
> Section C.3.12 for additional information on Inventory Management).

# F.4.6 Health, Safety, and Security Report

For Contractor provided facilities and staffing, the Contractor
**shall** develop, deliver, adhere to and maintain health, safety, and
security programs. The Contractor **shall** ensure that their DRIS
health, safety and security programs comply with policies and practices
that ensure workplace safety and security in accordance with all
Federal, State, local, and Occupational Safety and Health Administration
(OSHA) regulations. The Contractor **shall** deliver a Health, Safety,
and Security Report by the 15^th^ of the month, for the previous month's
activities, for DRIS Data and Call Centers only. At the Government's
request, the Contractor **shall** make available all safety and security
incident reports for all Contractor-operated DRIS facilities.

### F.4.7 Program Management Plan for DRIS

> The Contractor **shall** develop, deliver, maintain and adhere to the
> DRIS Program Management Plan that includes the management strategy and
> processes for all DRIS efforts. At a minimum, the DRIS Program
> Management Plan **shall**:
>
> a\. Establish the project organization, structure, authority, roles,
> responsibilities, and internal reporting relationships;
>
> b\. Establish the contracted site operations organization, structure,
> authority, roles, responsibilities, and internal reporting
> relationships;
>
> c\. Establish project management procedures and policies;
>
> d\. Define interfaces between the project and the Government;
>
> e\. Define roles relative to other corporate units, and the interfaces
> between the project and other corporate units;
>
> f\. Establish reporting requirements;
>
> g\. Describe the relationship of the project organization and
> management procedures to the Contract Work Breakdown Structure (CWBS);
>
> h\. Establish a Master Milestone Schedule;
>
> i\. Establish performance metrics and baselines, as well as a schedule
> for gathering, monitoring, and reporting these performance parameters;
> and
>
> j\. Describe cost and schedule reporting mechanisms.

### F.4.8 Program Management Review (PMR) Meeting Agendas and Minutes

> The Contractor **shall** schedule and present Program Management
> Reviews on a monthly basis at Census Bureau headquarters unless the
> Government and Contractor jointly agree upon an alternate site and/or
> a change in time. The purpose of the PMR is to communicate status and
> issues to a broad-based audience, including Government managers and
> oversight organizations. The review **shall** address technical,
> business and programmatic topics, with focus on status, performance
> and issues/risks. The first PMR **shall** be held within sixty (60)
> days of the contract kickoff meeting. (Refer to Sections C.3.10 and
> C.3.11 for additional information regarding PMR's agendas and
> meetings).
>
> **F.4.9 Contract Work Breakdown Structure (CWBS)**
>
> The Contractor **shall** develop, deliver, maintain, and adhere to
> detailed product-oriented CWBSs for DRIS consistent with MIL-HDBK-881
> ([http://www.acq.osd.mil/pm/newpolicy/wbs/ mil_hdbk_881/
> mil_hdbk_881.htm](http://www.acq.osd.mil/pm/newpolicy/wbs/mil_hdbk_881/mil_hdbk_881.htm))
> to use for its management of the DRIS Contract. The Contractor
> **shall** ensure that the CWBS will allow for Government visibility
> into the Contractor's detailed milestones and the status of
> deliverables and products for the DRIS contract. The Government will
> use this information for performance measurement and tracking of the
> status of DRIS activities. The Contractor **shall** minimize the use
> of Level-of-Effort cost accounts to the greatest extent practical. The
> Government has developed a level 2 Program WBS for Phase IA, which is
> provided in Section J Attachment 4. The Government will also develop
> Program WBSs for Phases IB, II and III based on the Contractor's
> solution. The Contractor **shall** develop a detailed CWBS for each
> phase based on the Government's Program WBS. The Contractor **shall**
> develop, deliver, maintain, and adhere to separate CWBSs for each
> phase/sub phase of DRIS with the phase or sub phase as the top level.
> Given the current phase structure for Phases IA, IB, II and III, the
> Government expects four separate CWBSs. The Contractor **shall**
> update the CWBS when necessary to reflect changes in tasking, program
> structure, program organization, contractual or sub-contractual
> agreements, or reporting requirements. (Refer to Section C.3.2 for
> additional information.)
>
> The Contractor **shall** develop, deliver, maintain, and adhere to a
> dictionary for each CWBS. The Contractor **shall** provide the
> Government with updates to the dictionaries as changes occur to the
> CWBSs.

### F.4.10 Project Schedule

> The Contractor **shall** develop, deliver, and maintain a project
> schedule that ties to the CWBS, for the purposes of detailing and
> tracking status of work activities. The project schedule **shall**
> include a unique CWBS identifier for each schedule entry and weighted
> milestones. The Contractor **shall** provide schedule updates based on
> the CWBS to the Government in a Primavera (P3e) format. The timing of
> this update will be agreed upon during Phase IA.
>
> **F.4.11 Life Cycle Cost Estimate (LCCE)**
>
> The Contractor **shall** develop, deliver, maintain, and adhere to a
> DRIS Life Cycle Cost Estimate that links to the CWBSs and project
> schedule. The LCCE **shall** include all projected costs for the
> program for all phases and sub phases. The Contractor **shall**
> identify all assumptions and constraints used in developing the
> estimate. The Contractor **shall** perform and document cost analyses
> and provide those analyses to the Government. The Contractor **shall**
> update the LCCE based on new or updated information on the program as
> requested by the Government. After award, the Government will work
> with the Contractor to refine the LCCE. The Contractor **shall**
> update the LCCE as needed to support the Government's budget process.
> The Government will determine the timing of updates during Phase IA.

# 

# F.4.12 Subcontracting and Subcontract Participation Plan 

> The Contractor **shall** establish, maintain, and adhere to a
> Subcontracting and Subcontract Participation plan that commits a
> minimum of thirty percent (30%) of the total contract price by Phase
> and FY to small businesses, minority businesses, women-owned
> businesses, veteran-owned business and HUBZone businesses (combined).
> The Contractor **shall** subcontract a minimum of twenty-five percent
> (25%) of the total contract price to first or second tier
> subcontractors. The remaining fiver percent (5%) can be subcontracted
> to third and fourth tier subcontractors.
>
> The Contractor **shall** submit a Subcontract Participation Plan that
> identifies the types of DRIS functions/performance areas within the
> contract scope that will be available to small businesses.
>
> **F.4.13 Contract Funds Status Report (CFSR) and DRIS Financial
> Report**
>
> The Contractor **shall** generate a Contract Funds Status Report
> (CFSR), DD Form 1586 based on the CWBS. The Contractor **shall**
> deliver the CFSR quarterly (January 15^th^, April 15^th^, July 15^th^
> and October 15^th^).
>
> The Contractor **shall** provide DRIS Financial Reports semiannually,
> by April 15^th^ and October 15^th^ of each year, to support the
> Government's budget process. The Contractor **shall** provide separate
> financial reports for paper, telephone, and the Internet. The
> Contractor's reports **shall** include the previous six months and
> cumulative financial information by phase for all phases. The expected
> format of this report is shown in Section J, Attachment 4, however,
> this format may change based on the Contractor's solution and proposed
> CWBSs. The Government will provide the detailed requirements for this
> report after contract award.

### F.4.14 Document Tree

> The Contractor **shall** develop and maintain a document list, such as
> a document tree, quarterly (January 15^th^, April 15^th^, July 15^th^,
> and October 15^th^ of each year) that shows traceability among the
> Contractor's DRIS documentation. Further, this list will provide a
> description of the linkage between documents, either through reference
> or through subdocument structures. As an example, the Program
> Management Plan will likely incorporate by reference several other sub
> plans, such as the Staffing Plan, and Subcontractor Plan, which will
> each have its own independent revision cycle. The Government would
> like to see these linkages clearly spelled out. The tree will include
> the document name, author, update date, and relationship to other
> documents.

### F.4.15 Self-Assessment Report for Award Fee Determination 

> The Contractor **shall** provide a self-evaluation summarizing the
> previous period's activities. The report **shall** be brief and
> factual and **shall** provide, at a minimum, the following
> information:
>
> a\. Cover Page; Contract Title and Number; Contractor's Name; Date of
> Report and Reporting Period.

b.  [Section I]{.underline} - An introduction of overall progress, plus
    a separate description of each task or other logical segment of work
    on which effort was expended during the reporting period. The
    description **shall** include pertinent data and/or graphs in
    sufficient detail to explain any significant results achieved.

c.  [Section II]{.underline} - A description of current technical or
    substantive performance and any problems, which may prevent
    performance. The section **shall** include a summary of responses to
    negative Individual Event Reports.

> d\. [Section III]{.underline} - A planning schedule of significant
> work, including start-up and completion dates. Updates should be
> provided in subsequent technical progress reports; including an
> explanation of any differences between actual progress and planned
> progress, why the differences have occurred and if behind in progress,
> what corrective steps are planned.
>
> e\. [Section IV]{.underline} - A status of Subcontracting Compliance.
> The Contractor **shall** provide:

1.  The name, address, and business status of all subcontractors;

2.  The monthly expenditures and percent of cumulative expenditures for
    large businesses, small businesses, small disadvantaged businesses,
    women-owned small businesses, veteran-owned small businesses,
    service disabled veteran-owned small businesses and HUBZone small
    businesses;

3.  Any variance with explanation between the Contractor's actual small
    business subcontracting utilization and small business
    subcontracting goals by type and overall; and

4.  An updated Subcontract Participation Plan, if changes are necessary.

# F.5 SECURITY 

The Contractor **shall** deliver, maintain, and adhere to all
documentation needed to fulfill security requirements and accreditation
processes. The Contractor **shall** provide the following for all DRIS
systems or facilities: (Refer to Section C.10.1 for additional
information regarding Security requirements).

-   Security Plans that addresses all processes the Contractor will
    follow to ensure that DRIS, its components and associated facilities
    meet the security requirements necessary to receive accreditation,
    and complies with NIST Special Publication 800-18;

-   Continuity of Operations Plan (COOP) that also address contingency
    planning and complies with NIST Special Publication 800-34;

-   Overall Risk Management Plan and Risk Assessments that complies with
    NIST Special Publication 800-30;

-   Other specialized risk assessments on E-authentication (NIST Special
    Publication 800-63), data sensitivity, and file transfers as
    appropriate for the system/facility; and

-   Supporting documentation that supports every Test ID within the
    Bureau of the Census' Security Test and Evaluation document. This
    document will be available within Section J of this RFP.

The Contractor **shall** provide, maintain, and adhere to documentation
required to support the NIACAP process, including completing a FIPS
800-26 Self Assessment on an annual basis.

The Government in conjunction with the Contractor will develop a
comprehensive risk management plan that conforms to NIST Special
Publication 800-30. This plan **shall** include performing a risk
assessment of the entire program every year to include individual
assessments of each contractor facility. In addition the risk management
plan **shall** also require ongoing updates to the risk assessments as
new risks are identified throughout the life cycle. The agreed upon risk
assessment level must be rated at the "low" level prior to the start of
any operations. The Contractor **shall** provide a Plan of Action and
Milestones for any issues that arise from the annual risk assessments.

Prior to processing any census data, the Contractor's system/site must
be certified by the Chief of the Information Technology Security Office
(ITSO) and the Department of Commerce Office of Security at the Census
Bureau and accredited by the Associate Director for Decennial Census,
according to the modified National Information Assurance Certification
and Accreditation Process (NIACAP). This process is documented in the
Department of Commerce IT Security Program Policy located at
<http://www.osec.doc.gov/cio/oipr/itsec/DOC-IT-Security-Program-Policy.htm>.

The Contractor **shall** comply with all applicable security
requirements stated in the Census Bureau's IT Security Program Policies
(See Section J, Attachment14, Part II). This policy includes provisions
for IT, physical and personnel security.

**F.6 CONCEPT OF OPERATIONS (CONOPS) AND SYSTEM ARCHITECTURE FOR DRIS**

The Contractor **shall** develop, deliver, maintain, and adhere to a
CONOPS that addresses, at a high level, the acquisition of space and
equipment for the development of lab(s); the integration and operation
of the DRIS system; the identification, hiring, training, and management
of an adequate work force; the provision of facilities management
services; the conduct of data capture operations; and the close out and
disposition of facilities, materials, and personnel at the conclusion of
data capture operations.

Also, as part of the CONOPS and System Architecture documentation for
DRIS, the Contractor **shall** develop, deliver, update and adhere to a
maintenance plan that examines how to ensure the operational reliability
and security of DRIS.

# 

# F.7 TEST PLAN FOR DRIS 

The Contractor **shall** develop, deliver, maintain and adhere to a test
plan that delineates the tests needed for all aspects of the DRIS. The
Contractor's Test Plan **shall** comply with CMMI and ISO 9001
guidelines. The Contractor's Test Plan **shall** address both Contractor
required and Government required tests. The Contractor **shall** obtain
Government concurrence on its test plan prior to implementation. The
Contractor **shall** maintain flexibility in its test plans to allow for
a series of revisions through the life of the DRIS contract, for which
the Government and the Contractor will jointly determine the timing.
(Refer to Section C.5 for additional information on the test plan.)

. The Co

# F.8 QUALITY ASSURANCE PLAN FOR DRIS 

The Contractor **shall** develop, deliver, maintain, and adhere to a
Quality Assurance Plan that identifies the quality standards and
processes for evaluating overall project performance on a regular basis
to provide confidence that the project will satisfy relevant quality
standards. The QA Plan **shall** cover all DRIS technical processes, as
well as project management and subcontract management processes. (Refer
to Section C.11 for information on the QA plan.)

**F.9 QUALITY CONTROL PLAN FOR DRIS**

The Contractor **shall** develop, deliver, maintain, and adhere to a
Quality Control Plan that will plan for monitoring project results to
determine their compliance with relevant standards and requirements, and
identify errors and recycle and correct data as well as identify ways of
eliminating causes of unsatisfactory performance. The goal of the QC
Plan is to maintain the quality of the Census data, as well as the
quality of the service provided by the electronic response modes. (Refer
to Section C.11 for additional information on the QC plan.)

# 

# F.10 SYSTEM DESIGN SPECIFICATIONS

The Contractor **shall** develop, deliver, maintain, and adhere to
detailed documentation including System Design specifications for all
DRIS Systems and documentation addressing specific handling of
Exceptions, QA and QC, scalability, interfaces with the Government's
systems, data standardization and organization, MIS report design,
content, and sources of the data, user interface design documents for
telephone and Internet, facility requirements for Government- provided
DR sites, and security requirements for all components and functions of
DRIS (2008 DR specific). The requirements definition and design process
may require updating and delivering any documents previously delivered
and showing traceability to Government requirements. Specifications and
system designs **shall** be compliant with relevant standards.

# F.11 ACQUISITION PLAN

The Contractor **shall** develop, deliver, maintain, and adhere to a
draft Acquisition Plan for acquiring the systems, infrastructure and
facilities (including identifying all 2008 DR and 2010 Census DRIS
sites) needed for the 2008 DR and 2010 DRIS. Such a strategy must take
into account scalability and technology transfer to the Government.

# F.12 PHYSICAL ARCHITECTURE 

The Contractor **shall** develop, deliver, maintain, and follow the DRIS
2010 Census Physical Architecture, which **shall** be integrated with
the overall 2010 Census Physical Architecture. Some of the DRIS Physical
Architecture products include: physical data model, system design,
system performance parameters, etc.

# F.13 EXTERNAL INTERFACE CONTROL DOCUMENT (EICD) 

The Contractor **shall** develop, deliver, maintain, and adhere to a
detailed External Interface Control Document (EICD) that thoroughly
details all interface points and the timing and method of interface
between DRIS components, other Government systems and the Contractors
systems. (Refer to Section C.4.2.2 and Section J, Attachment 6 for
additional information.)

# F.14 SITE PLANS FOR DRIS FACILITIES

The Contractor **shall** develop, deliver, maintain, and adhere to
detailed site plans (i.e. construction drawings) for all DRIS facilities
it will initiate and operate as applicable. The Site Plans **shall**
specify use of all space, outline adherence to Government requirements,
and provide for site security.

# F.15 DEPLOYMENT PLAN FOR DRIS

The Contractor **shall** develop, deliver, maintain, and adhere to a
plan for deployment of system components and personnel to sites. The
plan for deployment at a minimum **shall** include:

> a\. Specific placement of resources, as well as the timing of that
> placement.

b.  Detailed position descriptions and qualification standards, as
    appropriate, for identified job positions.

c.  Recommendations to the Government's NPC facility for operational
    staffing recommendations for the paper capture at the NPC.

d.  A comprehensive training program for all DRIS operations, including
    training materials and operational procedures covering all DRIS
    production, quality assurance, and control operations. HR data
    **shall** be provided on a weekly basis on such processes as
    recruiting, hiring and staffing, as appropriate, by operation to the
    Government.

e.  Delineate the processes (equipment, infrastructure, staffing, and
    facilities) needed to deploy the system components of the DRIS
    system.

f.  The Phase II Deployment Plan developed at the end of Phase IB will
    also address national deployment of the DRIS components and
    full-scale production operations for the 2010 Census.

# F.16 DESIGN WALK-THROUGHS 

The Contractor **shall** walk through existing DRIS functionality under
development. The walk throughs **shall** cover all designs, procedures,
and facilities developed to date for paper capture, Internet assistance
and enumeration, telephone assistance (IVR and telephone agent), and
telephone agent collection operations required for 2008 DR and 2010
Census operations.

**F.17** **CERTIFY READY-FOR-USE OF DRIS AT ALL FACILITIES**

The Contractor **shall** develop, deliver, and maintain a pre-production
version of the 2010 DRIS ready to process the 2008 DR workload where the
Contractor **shall** provide remedies, technical and/or operational, for
problems encountered during the 2008 DR operation. After the 2008 DR,
the Government and the Contractor **shall** jointly determine which
changes need to be made to the pre-production system prior to 2010
Census production operations.

# 

# F.18 SUBCONTRACTING REPORT 

The Contractor **shall** submit a Subcontracting Report for Individual
Contracts to report subcontracting activities under this contract on a
Standard Form 294 in accordance with the General Instructions on the
reverse side of the form. (Refer to Section H.14 for additional
information).

The report **shall** be submitted semi-annually to:

> **[Distribution]{.underline}** **[Addressee]{.underline}**

Original U.S. Department of Commerce

The Office of Small and Disadvantaged Business Utilization

> 14th Street and Constitution Avenue, N.W.
>
> Room H6411

Washington, DC 20230

> Copy Contracting Officer

U.S. Census Bureau

Acquisition Division

4700 Silver Hill Road

Room G-314; FOB #3

Washington, DC 20233-4400

# F.19 SUMMARY SUBCONTRACT REPORT

The Contractor **shall** submit a Summary Subcontract Report on all of
its contracts with the Department of Commerce, which has subcontracting
goals on a Standard Form 295. The report **shall** be submitted
quarterly. The report **shall** be submitted no later than fifteen (15 )
days following the close of each calendar quarter. The report **shall**
be submitted to the addresses listed in Clause F.18 "*Subcontracting
Reports.*" (Refer to Section H.14 for additional information.)

# 

# F.20 PHASE II PROPOSAL(S)

The Contractor **shall** develop and deliver proposals for Phase II
work. The first proposal delivered in May 2008 **shall** address
build-out/fit-up of 2010 Census DRIS sites. The second delivered after
2008 DR will address systems and operations. These proposals will build
upon the lessons learned from Phase I and will provide revisions of the
Contractor's management, technical, and quality assurance approaches,
with a goal of creating a risk-reduction plan for completion of the
system development cycle, compliant with the jointly developed DRIS
specification and design.

# F.21 PRODUCTION ACTIVITIES FOR DRESS REHEARSAL 

The Government will determine the timeframe and workload of the 2008 DR
during Phase IA/IB, but at a minimum, the Contractor **shall** deliver
and maintain support activities for the 2008 DR as follows: (Refer to
Section C.8 for additional information.)

a\. Build-out an existing Government-provided site as a 2008 DR facility
for paper capture at the Census Bureau's National Processing Center
(NPC) in Jeffersonville, IN. Build-out/Fit-up an existing Census Bureau
facility for the Internet capture of 2008 DR respondent data. The
Government will determine this site during Phases IA/IB. The Contractor
**shall** provide remedies, on-site technical support of the paper
capture and Internet 2008 DR components. The Contractor is not
responsible for recruiting personnel and staffing the 2008 DR operations
for paper capture, but **shall** be on-site at NPC to provide
operational training and support.

b.  Acquire and deploy the facilities and staffing needed for telephone
    collection and IVR in the 2008 DR.

# F.22 LESSONS LEARNED FROM DRESS REHEARSAL

The Contractor **shall** document and deliver a Lessons Learned document
from the 2008 DR. This document will provide a project record of the
learning -- both through successes and failures -- gained during
execution of Phase I of the DRIS program. The Lessons Learned document
will be applied to Phase II of the project; therefore, the Contractor
**shall** link each lesson to a Phase II strategy for system and process
improvement.

# F.23 STANDARDIZE AND ORGANIZE RESPONSE DATA 

The Contractor **shall** standardize and organize all DRIS response data
from all DRIS self-response modes and from hand-held computers (HHCs)
used by enumerators into a single predefined format for delivery to the
Government's systems. Based on Government feedback during Phases IA/IB,
the Contractor **shall** finalize and document its solution to develop
the standard transfer format and any edits required during the
standardization and organization process.

# F.24 MIS REPORTS GUIDE 

The Contractor **shall** develop, deliver, and maintain a MIS Reports
User Guide documenting all MIS reports delivered to the Government. The
Contractor is required to design, develop and deliver MIS reports that
will provide daily and cumulative status and quality metrics for all
steps in the DRIS operations for both the 2008 DR and the 2010 Census.
Hence, the guide will be used to aid the Government in reviewing and
interpreting the data in these reports, such as identifying the source
of the data and calculations.

The Contractor **shall** work with the Government during Phases IA/IB to
jointly determine the content of the Users' Guide. (Refer to Section
C.4.2.12 for additional information regarding MIS Reporting.)

# F.25 SYSTEMS OPERATING GUIDE AND USERS' MANUAL

The Contractor **shall** develop, deliver, and maintain a 2008 DRIS
Systems Operating Guide and Users' manual. The Contractor **shall**
include information on operating the components of DRIS, which can be
utilized by Government-provided operators, such as in the NPC.

# F.26 DELIVERY LOCATION

Unless otherwise required by this contract, all correspondence and
deliverables **shall** be delivered to the following person or his
representative:

Mike Palensky

Contracting Officer

U.S. Census Bureau

Acquisition Division

4700 Silver Hill Road

Room G-314; SFC #3

Washington, DC 20233-4400

**\[END SECTION F\]**