Previous PageNext Page





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.

(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.

(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. DCG
(Removed January 2014)

SUBPART 5607.5 - Inherently Governmental Functions

5607.503 Policies.
(Revised January 2018)
(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 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-KM 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)
February 2007

Previous PageTop Of PageNext Page