AFFARS Part 5307

Previous PageTable Of ContentsAFFARSNext Page



PART 5307-ACQUISITION PLANNING

SUBPART 5307.1-ACQUISITION PLANS

SAMPs shall be prepared for all ACAT I and II programs as defined by DODD 5000.1, Defense Acquisition, and DOD 5000.2-R, Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) Acquisition Programs. SAMPs are optional for all other programs and acquisitions. Whenever a SAMP is prepared, it shall meet the requirements of an acquisition plan as described in the FAR. In such cases, the SAMP approval process will be followed in lieu of the acquisition plan approval process described herein. The Air Force SAMP Guide and Acquisition Policy Memo 97A-02 provide information on preparing and processing SAMPs.

(c) In acquisitions where sole source approvals will be obtained, Air Force acquisition planning shall provide appropriate opportunities for the following:

(a) General. MAJCOMs, FOAs, and DRUs shall prescribe procedures for processing APs and shall establish review and approval levels for APs that do not require approval by the SPE, PEO, or DAC. SPE approval authority has been delegated, without power to redelegate, to the Principal Deputy Assistant Secretary of the Air Force (Acquisition and Management) (PDASAF(A&M)).
(b) Approval requirements.

> $120M or MAIS***** PDASAF(A&M) PDASAF(A&M) PDASAF(A&M) SAF/AQC

* Single Manager (SM) includes System Program Director (SPD), Product Group Manager (PGM), and Materiel Group Manager (MGM), and Technology Director.
** $15/$30M means $15M or more in any FY or $30M or more for all program years.
***S&T acquisition less than $500 million may use the simplified S&T combined AP and J&A format.
****For other contracting, the first contracting official in the contract chain subordinate to the SCCO
*****See AFFARS 53.202.101 for MAIS definition.

(c) APs requiring Final Acquisition Action Approval (FAAA) by the SPE.

(d) Changes. If a change occurs to the program which significantly affects the AP (e.g., scope, dollar value, contract type), the contracting officer shall submit a revised AP to the approval authority with a statement summarizing the changes. The revised AP should reflect the current status of the action(s) described. Changes in the AP shall be identified by a vertical bar in the right margin. [ See AFFARS 5343.102 for approval requirements for contract changes for Air Force Acquisition Programs (ACAT programs - see AFFARS Part 2) which result in a contract performance extension by 50 percent or more of the original contract period of performance.]

(a) General. An ASP shall be held for all acquisitions that require a written acquisition plan in accordance with DFARS 207.103 (c) and 5307.103 (c)(i)(C), even if the acquisition plan requirement is satisfied by a Single Acquisition Management Plan (SAMP), except acquisitions for basic and applied research (6.1 and 6.2 funds) and replenishment parts. MAJCOMs, FOAs, and DRUs shall prescribe procedures for conducting ASPs. In general, each ASP should:

(b) Responsibility for convening the ASP. For PEO and DAC Programs, the System Program Director (SPD) has responsibility for convening the ASP. For other acquisitions, the contracting officer is responsible for initiating the ASP, which will be convened in accordance with MAJCOM, FOA, or DRU procedures .
(c) ASP chairpersons. SAF/AQ is the ASP chairperson for ACAT I programs; however, SAF/AQ may delegate this authority to PEOs/DACs. PEOs/DACs are the ASP chairperson for their assigned non-ACAT I programs; however, this authority may be delegated (see 5301.601-92 (d)). ASPs for other acquisitions in AFMC shall be chaired in accordance with procedures in the command supplement. In MAJCOMs other than AFMC, the MAJCOM Director of Contracting will chair the ASP. In other organizations, ASPs will be chaired in accordance with procedures in the organization's supplement. The ASP chairperson may designate another official to chair an ASP and may approve waivers to ASP requirements, in accordance with procedures in MAJCOM, FOA, or DRU Supplements. The rationale and approval for all ASP waivers must be documented in the contract file. When practicable, the AP/SAMP approval authority should be the ASP Chairperson.
(d) ASP membership. The ASP chairperson has responsibility for selecting ASP members, as follows:

(e) The ASP chairperson shall ensure that minutes are prepared and distributed to principal attendees and that written recommendations are provided to the program manager or other individual with responsibility for preparing the acquisition plan or Single Acquisition Management Plan (SAMP). Written acquisition plans or SAMPs should be consistent with ASP discussions and any recommendations. Copies of the ASP minutes, the written recommendations, and disposition of any written recommendations should be included in the contract file.
(f) The person responsible for convening the ASP should consider reconvening the ASP if significant changes in program baseline or acquisition strategy occur.

(a) Acquisition background and objectives. The AP preparer shall ensure that reviewers at all management levels have access to documents referenced in the AP. Accomplish this by providing the document, reproducing and attaching pertinent extracts, or quoting the reference within the body of the plan, whichever is most practical. Documents may be referenced provided they can be made available for immediate use if needed by the reviewing officials.

(b) Plan of action.

SUBPART 5307.3-CONTRACTOR VERSUS GOVERNMENT PERFORMANCE

(b) Negotiation. See 5308.705 (f) for procedures relating to cost comparison studies involving the acquisition of services from workshops for the blind or severely disabled.

(a) For detailed procedures related to contracting officer responsibilities in implementing the right of first refusal, see Air Force Commercial Activities Program Instruction dated July 1998.

This page is blank.

Previous PageTop Of PageTable Of ContentsAFFARSNext Page