2.5 Request For Proposal.
2.5.1 Preparing a Preliminary Contract WBS. The DoD
program manager should select the individual WBS elements from the Program WBS
that apply to the contract to include in the request for proposal (RFP) as
described in 2.3.
This is the first time for open dialogue between the Government and potential
contractors. Innovative ideas or promising alternative solutions should
be considered for inclusion in the RFP. The RFP will include a Contract WBS
and the initial WBS dictionary. The RFP should instruct potential
contractors to extend the selected Contract WBS elements to define the
complete contract scope, consistent with the contractor’s proposed approach
for executing the program.
2.5.2 RFP Solicitation Requirements. Again, CLINs,
configuration items, contract work statement tasks, contract specifications,
and contractor responses should relate to the WBS to enhance its effectiveness
in fully describing acquisition objectives. It is important to coordinate the
development of the Program WBS and the CSDR plan with the development of the
SOW to ensure consistency in document structure. When aggregated with the
Program WBS, the extended Contract WBS will form a complete Program WBS to
provide a logical work flow throughout the acquisition cycle.
2.5.3 Extended Contract WBS. Contractors are expected to
extend the Contract WBS to the appropriate lower level that satisfies critical
visibility requirements and does not overburden the management control
system. A preliminary Contract WBS should be included in the RFP, and
the contractor should submit a complete Contract WBS with their
proposal. The proposal should be generally based on the WBS in the RFP,
although contractors should be encouraged to suggest changes needed to meet an
essential RFP requirement or to enhance the effectiveness of the Contract WBS
in satisfying program objectives.