(a)

1. (1) Most D-B projects are bid on a lump-sum basis and the RFP should require a bid breakdown to be submitted in the proposal in the form of a schedule of values (SOV).
2. (2) The RFP should specify any specific subordinate breakdown requirements of the items in the SOV.
3. (3) The SOV should be organized into work items, tasks, or milestones identified in the project schedule provided in the proposal.
4. (4) The SOV configuration can vary depending on the specific project and could consist of only a single item for the entire project, but usually can range up to several hundred items allocated for payment on the project.

(b)

1. (1) The SOV will be used for proposal evaluation during the procurement phase and cost tracking, payment requests, and change order price adjustments in the implementation phase.
2. (2) The SOV should be carefully reviewed by the project evaluation team (PET) and scrutinized to observe and resolve any unbalanced items.
3. (3) The PET should compare the SOV against the project schedule provided with the proposal for conformity.
4. (4) The SOV could become a negotiation effort between the Arkansas Department of Transportation and the selected short-list proposer (design-builder) prior to execution of the DBA.

(c)

1. (1) Where existing features must be modified as part of the project work, the existing conditions may not be known in sufficient detail to assign an accurate cost or price.
2. (2) In such case, the department procurement team (DPT) should consider assigning unit costs, against a preassigned estimated quantity for high-risk items or items unclear to the Arkansas Department of Transportation and the short-list proposers during the time of the proposal preparation to establish a basis for measuring and payment for the actual work.
3. (3) A description of the work and the basis for measurement and payment should be included in the project special provisions included with the RFP.