AFFARS Part 5307

Previous PageTable Of ContentsAFFARSNext Page



PART 5307-ACQUISITION PLANNING

TABLE OF CONTENTS

SUBPART 5307.1-ACQUISITION PLANS 7-1

SUBPART 5307.3-CONTRACTOR VERSUS GOVERNMENT PERFORMANCE 7-5

This page is blank.

PART 5307-ACQUISITION PLANNING

SUBPART 5307.1-ACQUISITION PLANS

(i) All system modifications when the estimated total acquisition cost of the modification is $10 million or more;

(iii) Acquisitions that plan to use the Federal Supply Schedule (FSS) program. Use the estimated value of the entire planned requirement, including any portion using the FSS program, to determine applicability and approval level.
(h)(i) Submit the acquisition plan or Single Acquisition Management Plan to the address stated in DFARS 207-103(h)(i) and a copy of the transmittal memorandum to SAF/AQCK.

SAMPs must be prepared for all ACAT I and II programs as defined by Section 4.8 of DODI 5000.2 , Operation of the Defense Acquisition System. SAMPs are optional for all other programs and acquisitions. SAMPS for ACAT I and II programs must be approved by the Principal Deputy Assistant Secretary of the Air Force (Acquisition and Management)(PDASAF(A&M)). The acquisition strategy for ACAT ID programs requires additional approval by USD(AT&L), the acquisition strategy for ACAT IAM programs requires additional approval by ASD(C31), and the SAMP for ACAT IAC programs requires additional approval by AFAF(A). Signature by the approving official on the SAMP document constitutes approval. For all SAMPS requiring SAF/AQ or higher approval, coordination is required from SAF/AQC as the Air Force Competition Advocate General. SAMPS's prepared for ACAT III programs must be approved by the PEO or DAC, unless the program exceeds the PEO/DAC acquisition plan approval threshold (see 5307.104-90(b)). In this case, the SAMP must be approved by PDASAF (A&M). Whenever a SAMP is prepared, it must meet the requirements of an acquisition plan as described in the FAR, and the SAMP approval process as stated in the Air Force SAMP Guide, must be followed in lieu of the acquisition plan approval process described herein. Delegation procedures are also outlined in the Air Force SAMP Guide.

(c) In acquisitions where sole source approvals will be obtained, Air Force acquisition planning must provide appropriate opportunities for the following:
(1) involving Defense Contract Management Agency and Defense Contract Audit Agency early in the acquisition process,
(2) obtaining appropriate contractor input for use in the development of the acquisition strategy and of the abbreviated RFP or letter of solicitation,
(3) establishing a Government/Contractor team (including executors and reviewers), committed on a real-time basis to streamlining the acquisition process and maintaining open communications;
(4) teaming of the Government and Contractor in development of the proposal and model contract, leading to agreement on contractor effort and costs associated with the task(s); and
(5) teaming of the Government and contractor during post-award contract performance to improve communications and develop efficient contract administration methods.

(a) General. MAJCOMs, FOAs, and DRUs must prescribe procedures for processing APs and must 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)). The approval requirements below reflect normal expectations. Requests for case-by-case delegations PDASAF(A&M) must be compelling.
(b) Approval requirements.

Threshold

PEO Program

DAC Program

Other Contracting***

Review/Coordinate

$5M to <$50M

SM*

SM*

center commander

BOCO/****

> $50M to < $500M

PEO

DAC

center commander

SCCO

> $500M

PDASAF(A&M)

PDASAF(A&M)

PDASAF(A&M)

SAF/AQC

A-76 > 300FTEs

PDASAF (A&M)

PDASAF (A&M)

PDASAF (A&M)

SAF/AQC

Threshold

PEO Program

DAC Program

Other Contracting

Review/Coordinate****

$5M to < $15/30M**

SM*

SM*

center commander

BOCO/****

>$15/30M** to < $120M and non-MAIS

PEO

DAC

center commander

SCCO

> $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 5302.101 for MAIS definition.
(3) For all commands except AFMC, review and approval levels for Other Contracting APs that do not require SPE approval must be in accordance with Command procedures. For PEO Programs assigned outside AFMC, the PEO is the AP approval authority.
(c) APs requiring Final Acquisition Action Approval (FAAA) by the SPE.
(1) SAF/AQCK furnishes SPE AP approval to the contracting activity by memorandum entitled, " (FAAA)," outlining any restrictions (exceptions) which have been imposed. SAF/AQCK prepares and processes FAAAs. SAF/AQCK must monitor clearance of the exceptions noted in the FAAA. When an AP and justification and approval (J&A) require SPE approval, the J&A documentation should be submitted concurrently with the AP. Anticipate 45 days for staffing and issuance of the FAAA after receipt by SAF/AQCK.
(2) When AP approval by the SPE is required, the following procedures apply: (i) APs requiring SPE approval must be signed by the contracting officer, chief of the contracting office, and program manager (for A-76 cost comparisons affecting 300 or more full-time equivalents (FTEs), the Competitive Sourcing Management Steering Group (CSMSG) Chairperson). Additionally, for AFMC PEO actions, APs requiring SPE approval must be signed by the Buying Office Contracting Official (BOCO) and for AFMC DAC actions, by the Senior Center Contracting Official. The responsible PEO or DAC must also sign the AP prior to submitting it to SAF/AQCK for SPE approval. For Other Contracting, signature must be in accordance with command procedures prior to submitting to SAF/AQCK for SPE approval.
(ii) For AFMC PEO Programs, the PEO must forward the AP to SAF/AQCK prior to solicitation release. SAF/AQCK must begin internal review of the AP upon receipt from the PEO and will release the document for SAF/AQ staffing. Within five work days of receiving the AP from the PEO, SAF/AQCK must send the PEO and program office written authorization to release the solicitation on the 15th calendar day after SAF/AQCK received the plan. The contracting officer may release the solicitation on or after the specified date, unless directed otherwise by the SPE. SAF/AQCK must verbally communicate SPE direction to stop release of the solicitation, followed up by written cancellation or amendment of the authorization to the PEO. In this case, the contracting officer must not release the solicitation until the FAAA is signed or a revised date is specified in the amendment. After the solicitation is issued, negotiations must not commence (see 5306.003) nor must sealed bids be received until the FAAA is signed by the SPE.
(iii) For AFMC DAC Programs, procedures for processing the AP after signature by the DAC are the same as forPEO programs, except authorization and SPE directions will be sent to the Senior Center Contracting Official.
(iv) For PEO Programs assigned outside AFMC, the AP must be submitted after signature to the MAJCOM Chief of Contracting who has been delegated the responsibility for initial reviews as a service to the ASAF(A). The AP must be forwarded by the PEO to SAF/AQCK within 30 calendar days or when problems have been resolved, whichever occurs earlier. The MAJCOM's transmittal letter will address any unresolved issues and include a recommendation regarding solicitation release. Within five work days of receiving the AP from the PEO, SAF/AQCK will send the PEO contracting activity a written authorization to release the solicitation immediately, unless major issues precluding solicitation release have been identified and the SPE has directed that the solicitation not be released. SAF/AQCK must verbally communicate SPE direction to stop release of the solicitation, followed up by written cancellation or amendment of the authorization. In this case, the contracting officer must not release the solicitation until the FAAA is signed or a revised release date is specified in the amendment. After the solicitation is issued, negotiations must not commence (see 5306.003) and sealed bids must not be received until the FAAA is signed by the SPE.
(v) For acquisitions citing the authority in FAR 6.302-2 (unusual and compelling urgency), the contracting officer must not release the solicitation until approval is received, except when approval will unreasonably delay the acquisition. When justified in accordance with FAR 6.302-2 (c)(1), the solicitation may be released and the acquisition cycle continued (including contract award) prior to the signing of the FAAA. The contracting activity must request the FAAA as early as possible.
(vi) For full and open competition acquisitions that support quick reaction capability, the contracting officer may release the solicitation and continue the acquisition cycle up to, but not including contract award, prior to the signing of the FAAA. The contracting activity must request the FAAA as early as possible.
(d) Changes. If a change occurs to the program that significantly affects the AP (e.g., scope, dollar value, contract type), the contracting officer must 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 must be identified by a vertical bar in the right margin. [See 5343.102 for approval requirements for contract changes for Air Force Acquisition Programs which result in a contract performance extension by 50 percent or more of the original contract period of performance.]

5307.104-91 Acquisition Strategy Panels (ASPs)
(a) General. An ASP must be held for all acquisitions that require a written acquisition plan in accordance with DFARS 207.103(d(i)) and 5307.103(d)(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 must prescribe procedures for conducting ASPs. In general, each ASP should:
(1) Take place as early as possible in the acquisition planning process to develop a systematic and disciplined approach to achieve an efficient/effective acquisition; and
(2) Address user requirements, final acquisition objectives, and the alternative methods to attain those objectives. The ASP must address all relevant requirements of the written acquisition plan (see FAR 7.105) and any other considerations needed to fully assess the planned acquisition approach.
(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)). SAF/AQ is the ASP chairperson for any A-76 cost comparisons that affect 300 or more full-time equivalents (FTEs); however, SAF/AQ may delegate this authority on individual cost comparisons. ASPs for other acquisitions in AFMC must 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:
(1) Legal, engineering, comptroller, and contracting communities and the user organization(s) must be invited to participate;
(2) For acquisitions for ACAT programs, the ASP members will be from the applicable standing ASP created from the test, legal, operations, engineering, contracting/competition advocate, comptroller, logistics/sustainment, and program management areas and a representative of the Defense Contract Management Agency ; and
(3) Additional members should be invited as appropriate for the specific acquisition. The ASP chairperson should consider representatives from other disciplines, such as test and evaluation, logistics, manufacturing, quality assurance, competition advocate, base environmental, safety, and bio-environmental and medical (occupational health).
(e) The ASP chairperson must 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 must 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.

(1) Statement of need.
(A) Applicability of a Decision Coordinating Paper (DCP), Defense Acquisition Board (DAB), and/or Internal Service Reviews. Use the acquisition plan and/or SAMP to document the acquisition strategy in support of the Acquisition Strategy Panel (ASP), the Overarching Integrated Product Team and Working Level Integrated Product Team and the DAB process.
(b) Plan of action.
(4) Contracting considerations. APs must include major component contract actions and all other contract which have a significant effect on the total acquisition.
(17) Security considerations. APs which contain information which should not be released outside the Government must be marked "FOR OFFICIAL USE ONLY" and handled accordingly.
(18) Other considerations. If any contract(s) under the AP will authorize decentralized ordering (i.e., ordering by a contracting office at any other location), describe the oversight procedures for tracking orders, enforcement of contract terms and conditions, and prevention/identification of abuses, such as issuance of out-of-scope orders.

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