AFFARS PGI 5307 Acquisition Planning 

Table of Contents

Click any column header below to sort by that column.

 AF PGI 5307 Acquisition Planning

AF PGI 5307.104-92 Acquisition Strategy Panels (ASP) and Acquisition Plan (AP) Approval Authority or Streamlined Acquisition Strategy Summary (SASS)

(b)(3) Acquisitions less than $10M that should consider use of an AP rather than a SASS:

(i) Acquisitions where there is limited experience with the specified requirement and there is a moderate to high risk of not completing the acquisition successfully;

(ii) Acquisitions where incentives (e.g. award fee, incentive fee) are to be included;

(iii) Acquisitions where there is a history of protests or performance problems; and,

(iv) Acquisitions being conducted in accordance with FAR 15.3 and DoD Source Selection

Procedures unless the Source Selection Authority (SSA) is the contracting officer.

 (b)(4) The acquisition strategy approving authority may utilize the ASP briefing charts and associated note pages, minutes, and changed charts to satisfy a required written AP if the content complies with requirements set forth in DFARS PGI 207.105

AF PGI 5307.105 Contents of Written Acquisition Plans

See the Acquisition Plan or SASS template.

 AFICC PGI 5307 Acquisition Planning

AFICC PGI 5307.104 General Procedures

(a) In order to develop a sound acquisition strategy acquisition teams should engage with the AFICC/KA Acquisition Center of Excellence (ACE) and others as appropriate, including Contracting, Financial Management, Staff Judge Advocate and other technical experts (e.g., AFPEO/CM).

(b) In order to maximize mission effectiveness through reductions in rate, process and demand management, Contracting Officers are encouraged to identify and consider the use of existing contracts and agreements, to include those within the Department of Defense and Federal Agencies, during the market research phase and prior to awarding a new contract.  At a minimum, Contracting Officers should consider exploring the AFICC Launch Pad and GSA Acquisition Gateway (Solution Finder) and also utilize available resources such as the AFICC Strategic Sourcing Toolbox.

AFICC PGI 5307.104-92 Acquisition Strategy Panels (ASP) and Acquisition Plan (AP) Approval Authority

(a)(1) For large dollar or complex requirements it is recommended that the ASP convenes at least 18 months prior to the planned start of the contract or within a reasonable period of time that is commensurate with the complexity and value of the acquisition. An example of a typical timeline for large dollar and/or complex acquisitions is provided below.

• 24 months or > - requirements identified and approved

• 24 months - market research initiated

• 18 months - ASP convened

• 16 months - Acquisition Plan Approved

• 14 months - Source Selection Plan Approved (if required)

• 12 months - Business Clearance obtained/solicitation release

• 3-4 months - Contract Awarded

• 1-2 months - Phase-in Starts

• 0 months - Contract Start

 AFMC PGI 5307 Acquisition Planning

AFMC PGI 5307.104 General Procedures

(a) In order to develop a sound acquisition strategy, AFMC acquisition personnel are encouraged to engage the local Acquisition Center of Excellence (ACE) and others as appropriate, including Contracting, Financial Management, Staff Judge Advocate, Small Business and other technical experts.

 (b) AFMC/CA is the Early Strategy & Issues Session (ESIS) authority for AFPEO/CM acquisitions > $100M to <$1B unless further delegated by AFMC/CA. See the AFPEO/CM ESIS template. To schedule an ESIS for programs where AFMC/CA is the approval authority, send an email notification to AFMC/PK Workflow with the following information: name of program, program office POC, estimated dollar value, projected need date for the ESIS, status of RAD, projected ASP date, RFP release date, and contract award date.

AFMC PGI 5307.104-92 Acquisition Strategy Panels (ASP) and Acquisition Plan (AP) Approval Authority or Streamlined Acquisition Strategy Summary (SASS) Approval Authority

(a)(3)

(i) AFMC/CA is the ASP Chair for AFPEO/CM programs ≥ $100M to < $1B, unless further delegated by AFMC/CA. To schedule an ASP for programs where AFMC/CA is the approval authority, send an e-mail notification to AFMC/PK Workflow with the following information: name of program, program office POC, date of ESIS, status of RAD, projected RFP release date and contract award date.

(b)(1)

(i) AFMC/CA is the AP approval authority for AFPEO/CM programs ≥ $100M to < $1B, unless further delegated by AFMC/CA.

(b)(2) The following actions do not require an AP or SASS:

(f) The Small Business Innovation Research (SBIR) program, including the Small Business Technology Transfer (STTR) program (e.g., DoD-wide program planning/solicitation)

(g) Acquisitions in accordance with FAR Subpart 13.5. Simplified Procedures for Certain Commercial Items.

For Air Force Research Laboratory:

(a)(5) In order to provide a consistent approach within AFRL, the following procedures for the use of combined ASP/APs are encouraged:

(i) While the ASP/AP will describe the development program (see DFARS 207.103(d)(i) and FAR 32.7), the approval authority should be based upon the total value of contracts to be issued except under Open BAAs, wherein approval authority is based on the highest dollar value for which contracts can be awarded.

(ii) For R&D actions above the thresholds in DFARS 207.103(d)(i) see the AFRL ASP/AP Template.

(iii) Broad Agency Announcements (BAAs) with calls. This approach allows for publication of a basic BAA solicitation that contains overarching information, but does not request white papers or full proposals. The requests for white papers and/or proposals are transmitted via Calls. The ASP/AP briefing presented to the approval authority should be based upon the total estimated value of awards to be made under the BAA with Calls. The ASP/AP briefing should specifically address any follow-on strategy planning requirements applicable before issuing individual calls and the approval authority for the call strategy. Contracting should coordinate on the proposed approach to follow-on strategy requirements.

(iv) Open BAAs. This approach allows offerors to submit proposals any time during the open period. Because it specifically requests proposal submittal, it should be considered a solicitation. An ASP/AP should be accomplished before the open BAA is issued. The approval authority for the ASP/AP should be based on the highest dollar value for which contracts can be awarded.

(v) Revisions to ASP/APs. In order to ensure consistency, a significant change affecting the acquisition is one that meets any of the following criteria:

(A) The need to issue a new contract that was not anticipated in the approved ASP/AP for a development program or the need to process a Justification and Approval for a modification to a contract.

(1) Change in contract type for an anticipated contract.

(2) The cumulative value of the anticipated basic contract(s) and all modifications is/are expected to exceed the approval threshold of the previous ASP/AP approval authority.

(3) The cumulative value of all modifications is greater than or equal to 100 percent of the value of the anticipated basic contract(s).

(B) AFRLI 61-201 procedures to approve and disapprove work unit baseline changes do not change or modify any contracting procedures related to the need for an updated ASP/AP as described above.

(b)(1) Research and Development (R&D)/Enterprise Contracting ASPs, APs, and SASS:

¹ All delegated Approval Authorities must be within the Requirements chain

² Delegated to CA. Further delegable to lo lower than GO/SES

³ Delegable no lower than O-6/GS-15 or equivalent

⁴ Delegable no lower than O-5/GS-14 or equivalent

Contracted Services ASPs, APs, and SASS subject to AFI 63-138:

¹ All delegated Approval Authorities must be within the Technical Executive Officer (TEO) or requirements chain for non-TEO efforts

²Delegable to GO/SES

³Delegable no lower than O-6/GS-15or equivalent

 ⁴ Delegable no lower than O-5/GS-14or equivalent

AFMC PGI 5307.105 Contents of Written APs

 (a) If the format of the AP Template is substantively tailored (i.e., ASP Charts are used for AP), the associated documentation should address at a minimum, all applicable AP content requirements prescribed by FAR and Supplements.

AFMC PGI 5307.107-2 Consolidation

(c)  Should coordinate all consolidation determinations with the local Small Business office.

 SMC PGI 5307 Acquisition Planning

SMC PGI 5307.104 General Procedures

 (c) For other than full and open competitive acquisitions, all acquisition strategy documents (e.g., Acquisition Plans, and Streamlined Acquisition Strategy Summaries above the SAT) should be coordinated with the Competition Advocate unless one of the exceptions at AFFARS 5307.104-92(b)(2) applies.

SMC PGI 5307.104-92 Acquisition Strategy Panels (ASP) and Acquisition Plan (AP) Approval Authority or Streamlined Acquisition Strategy Summary (SASS)

(a)(1) The Contracting Officer should invite both SMC/PK and the SMC/PKC reviewers to attend acquisition strategy meetings with the decision authority when the clearance approval authority is the SCO, DAS(C), or ADAS(C). COCOs should participate in all other strategy meetings with the decision authority when the clearance approval authority is below the SCO.

 USAFA PGI 5307 Acquisition Planning

USAFA PGI 5307.104-92 Acquisition Strategy Panel (ASP) and Acquisition Plan (AP) Approval Authority

(a)(6) See the USAFA SDO assignments for ASPs for Services in USAFA PGI 5337.503-90. For ASPs for Supplies, the USAFA SCO delegates ASP Authority (Supplies) to the COCO for actions < $10M.

(b)(1) The USAFA SCO delegates Acquisition Plan Approval Authority (Services) to the COCO for actions < $10M.  Contracting Officers should refer to the USAFA/PK authorities and delegations site concerning specific COCO designations, delegations and authorities at https://cs2.eis.af.mil/sites/13093/PP/USAFA_PK/_layouts/15/start.aspx#/SitePages/Home.aspx .