7.105  Contents of written acquisition plans.

9. Amend section 7.105 by--

a. Removing from the first sentence of the introductory text the words "see paragraph (b)(19)" and adding the words "see paragraph (b)(21)" in their place;

b. Redesignating paragraphs (b)(3) through (b)(21) as paragraphs (b)(4) through (b)(22), respectively;

c. Adding a new paragraph (b)(3);

d. Removing from newly redesignated paragraph (b)(5)(i) the words "contract type selection (see part 16);";

e. Removing from newly redesignated paragraph (b)(5)(ii)(A) the words "see 7.103(t)" and adding the words "see 7.103(v)" in its place; and

f. Adding paragraph (b)(5)(iv).

The added text reads as follows:

7.105  Contents of written acquisition plans.

* * * * *

(b) * * *

(3) Contract type selection. Discuss the rationale for the selection of contract type. For other than firm-fixed-price contracts, see 16.103(d) for additional documentation guidance. Acquisition personnel shall document the acquisition plan with findings that detail the particular facts and circumstances, (e.g., complexity of the requirements, uncertain duration of the work, contractor's technical capability and financial responsibility, or adequacy of the contractor's accounting system), and associated reasoning essential to support the contract type selection. The contracting officer shall ensure that requirements and technical personnel provide the necessary documentation to support the contract type selection.

* * * * *

(5) * * *

(iv) For each contract (and order) contemplated, discuss the strategy to transition to firm-fixed-price contracts to the maximum extent practicable. During the requirements development stage, consider structuring the contract requirements, e.g., contract line items (CLINS), in a manner that will permit some, if not all, of the requirements to be awarded on a firm-fixed-price basis, either in the current contract, future option years, or follow-on contracts. This will facilitate an easier transition to a firm-fixed-price contact because a cost history will be developed for a recurring definitive requirement.

* * * * *