[Code of Federal Regulations] [Title 48, Volume 4] [Revised as of October 1, 2006] From the U.S. Government Printing Office via GPO Access [CITE: 48CFR307.104] [Page 18] TITLE 48--FEDERAL ACQUISITION REGULATIONS SYSTEM CHAPTER 3--HEALTH AND HUMAN SERVICES PART 307_ACQUISITION PLANNING--Table of Contents Subpart 307.1_Acquisition Planning Sec. 307.104 General procedures. (d) Each contracting activity shall prepare an Annual Acquisition Plan (AAP). The AAP is a macro plan, containing a list of anticipated contract actions over the simplified acquisition threshold and their associated funding, as well as the aggregate planned dollars for simplified acquisitions by quarter, developed for each fiscal year. The AAP shall conform to reasonable budget expectations and shall be reviewed at least quarterly and modified as appropriate. The chief of the contracting office (CCO) shall obtain this information from the program planning/budget office of the contracting activity and use the AAP to provide necessary reports and monitor the workload of the contracting office. For contract actions, the plan shall contain, at a minimum: (1) A brief description (descriptive title, perhaps one or two sentences if necessary); (2) Estimated award amount; (3) Requested award date; (4) Name and phone number of contact person (usually the project officer); (5) Other information required for OPDIV needs. (e) Once the AAP is obtained, the contracting officer/contract specialist shall initiate discussions with the assigned project officer for each planned negotiated acquisition over $100,000 except for: (1) Acquisitions made under interagency agreements, and (2) Contract modifications which exercise options, make changes authorized by the Changes clause, or add funds to an incrementally funded contract. (The HCA may prescribe procedures for contract actions not covered by this subpart.) (f) The purpose of the discussions between the contracting and project officers is to develop an individual acquisition planning schedule and to address the things that will need to be covered in the request for contract (RFC), including clearances, acquisition strategy, sources, etc. The project officer must either have a statement of work (SOW) ready at this time or must discuss in more detail the nature of the services/supplies that will be required. (g) Standard lead-times for processing various types of acquisitions and deadlines for submission of acceptable RFCs (that is, RFCs which include all required elements such as clearances, funding documents, and an acceptable SOW) for award in a given fiscal year shall be established by the HCA or designee not lower than the CCO. (h) The outcome of the discussions referenced in paragraph (f) of this section between the project officer and the contracting officer/ contracting specialist will be an agreement concerning the dates of significant transaction-specific acquisition milestones, including the date of submission of the RFC to the contracting officer. This milestone schedule document will be prepared with those dates and will be signed by the project officer and the contracting officer. The milestones cannot be revised except by mutual agreement of these same individuals. If the planning schedule indicates the need to obtain approval of a Justification for Other than Full and Open Competition, the CCO must sign the milestone agreement. This document shall be retained in the contract file. All other considerations that will affect the acquisition (technical, business, management) shall be addressed in the RFC (see 307.71).