Part 5607 - ACQUISITION PLANNING

Subpart 5607.1 - ACQUISITION PLANS

5607.102 Policy.

5607.104 General Procedures.

5607.105 Contents of Written Acquisition Plans.

Subpart 5607.5 - Inherently Governmental Functions

5607.503 Policies.

Subpart 5607.1 - ACQUISITION PLANS

5607.102 Policy.

(Added August 2016)

See 5637.102(k) for additional policy regarding the acquisition of services in accordance with DoD

Instruction 5000.74.

5607.104 General Procedures.

(Revised June 2017)

(a) In accordance with FAR 7.102(a) , acquisition planning is required for all acquisitions.

Acquisition planning is paramount and should begin as soon as the requirement is identified,

preferably well in advance of the fiscal year in which contract award or order placement is

necessary. In addition to the DFARS thresholds for a written acquisition plan, an acquisition plan is

required for the following actions. The detail to which the plan is developed will be determined by

the complexity of the acquisition and the dollar threshold.

(1) Services acquisitions not managed or reviewed as part of PEO Program of Record with an

estimated total value of SAT or more (DoDI 5000.74).

(2) Acquisitions using other than full and open competition require advocate for competition

coordination ( FAR 7.104(c) ).

(3) Acquisitions over $10M not completely set-aside for small business therefore, requiring small

business coordination. If the primary contracting officer is also the Small Business Representative

then the contracting officer shall coordinate their acquisition plans/strategy with the command’s

Director of Small Business Programs. For Headquarters buying divisions, coordinate the plan with

the command’s Director of Small Business Programs.
(b) The following are examples of planning and strategy documentation. FAR 7.1 and DFARS 207.1

address policies related to acquisition planning and the development of written acquisition plans.

Templates can be found in the DCG. Approvals shall be in accordance with 5601-1 .

(1) Streamlined Acquisition Planning – For acquisitions that do not require a formal written

acquisition plan in accordance with DFARS 207.103 , a simplified acquisition plan is required to

document pre-award decisions and risk assessment information. Alternate contract documentation

such as memorandum for record, business clearance memorandum, or other documentation may be

used in lieu of a standalone acquisition plan. At a minimum, documentation should address the

following as applicable: market research considerations (competition, SB, commercial alternatives,

pre-existing contract vehicles), and the appropriate contract type.

(2) Written Acquisition Plan (AP) – FAR 7.1 and DFARS 207.1 address policies related to acquisition

planning and development of written Acquisition Plans. When the acquisition meets the DFARS

207.103 threshold for a written acquisition plan, the template in the DCG is mandatory and includes

the required content.

(3) Acquisition Strategies for Services (IAW DoDI 5000.74) – When a written acquisition plan is

required for services, the plan should address the tenets in DFARS 237.102-76; a separate strategy

is not required. For service acquisitions below DFARS thresholds, the acquisition planning

documents should be commensurate with the complexity of the acquisition and address the tenets,

as applicable.

(4) Single Acquisition Management Plan (SAMP) – Describes a program's overall program strategy

per the USSOCOM D 70-1. The acquisition strategy, Systems Engineering Plan (SEP), program

issues, and contract execution approaches are integrated into the SAMP. The Single Acquisition

Management Plan Template may be used in lieu of a separate AP as long as all of the elements

required by the FAR and DFARS are contained in the SAMP. Some programs will also require a

separate AP or SEP. These documents should be referenced in the SAMP with final conclusions,

recommendations, or summaries incorporated where appropriate.

(5) Simplified Acquisition Strategy Brief (SASB) – May be used in combination with a written AP

and/or SAMP however, this simplified version does not in its self-constitute a written plan IAW D

FARS 207.103 . Acquisitions dealing with large dollar actions and increased risk may call for a

briefing in addition to an AP/SAMP highlighting the relevant facts surrounding the acquisition and/or

those key strategic elements only within the written AP/SAMP.

(6) Combined Written Acquisition Plan and Strategy Brief – A formal acquisition strategy brief may,

with approval of the SSA and/or the MDA, constitute the written AP in accordance with DFARS

207.103 as long as it meets all requirements defined in FAR 7.105, DFARS 207.105 , and DoDI

5000.02, Enclosures 2 and 4.

(c) An acquisition plan is not required for individual orders when the contract-level acquisition plan

adequately covers all anticipated orders and the order is issued IAW the terms of the basic contract.

(d) Designated Planner: IAW DFARS 207.103 , the program manager, or other official responsible for

the program, has overall responsibility for acquisition planning. For smaller dollar and less complex

acquisitions, the person responsible for developing the acquisition plan and milestones will be the

Contracting Officer. With larger, systems-level acquisitions there will be a team of planners

including a representative from all the affected functional areas, including the Contracting Officer

and a Program Manager (or RAO) who are responsible for decisions regarding the acquisition plan.
5607.105 Contents of Written Acquisition Plans.

(Removed January 2014)

Subpart 5607.5 - Inherently Governmental Functions

5607.503 Policies.

(Revised June 2023)

(e) The requiring activity shall provide to the Contracting Officer a written determination that none

of the functions contained in the requirement are inherently governmental. The determination shall

be prepared in accordance with FAR 7.503 and DFARS 207.503. Disagreements over the

determination shall be resolved by the Contracting Officer and reviewed at one level above the

Contracting Officer. Should the Contracting Office and Requiring Activity fail to agree on the

conclusion, forward the package to SOF AT&L-KZ for a final determination.

(Moved January 2014 from 5637.590-90(a))

(g) In accordance with DPAP memo Reporting Inherently Government Functions Indicators to the

Federal Procurement Data System dated 25 Feb 2013, contracting officers shall ensure that

requiring organizations provide the function indicator with their requirements packages so it may be

appropriately reported on new awards dated March 1, 2013 forward and modifications to those

awards. The function indicators are Closely Associated Functions, Critical Functions, and Other

Functions. Definitions for each function indicator, applicability, and the format for reporting to

FPDS-NG can be found within the DPAP memo stated above. DCG

(Added June 2009)

(h) See 5609.901 for Guidance on Contractors in the Federal Workplace.

HQ, United States Special Operations Command

Special Operations Forces Acquisition, Technology, and Logistics (SOF AT&L-K)

SOFARS 5607

February 2007