SOFARS PART 5607
ACQUISITION PLANNING
SUBPART 5607.1 - ACQUISITION PLANS
5607.104 General Procedures.
(Updated January 2014)
(a) 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. Acquisition planning or strategies, or a combination of the two may be required. The following are examples of planning and strategy documentation. Templates can be found in the DCG. Briefings and plans shall be developed based on the complexity and dollar value of the acquisition.
(1) Acquisition Planning Sheet (APS) – Smaller dollar acquisition planning. Provides areas for tracking planned, revised and actual dates for selected events ranging from submittal of Procurement Request package to contract award.
(2) Written Acquisition Plan (AP) – Planning is required per FAR 7.101 for all acquisitions. FAR 7.1 and DFARS 207.1 address policies related to acquisition planning and development of written Acquisition Plans. The document, Appendix E Acq Plan Template, is mandatory for the written AP for all acquisitions exceeding the thresholds contained within DFARS 207.103.
(3) 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 execution approaches are integrated into the SAMP. The Appendix F document, 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.
(4) Acquisition Strategy Brief (ASB) – Acquisitions dealing with large dollar actions and increased risk may call for a briefing highlighting the relevant facts surrounding the acquisition. An Acquisition Strategy Brief may also be requested for task/delivery orders that must be negotiated and are large dollar actions with increased risk. The brief then will be presented to the PEO/Dir or Deputy PEO/Dir, the DOP/Deputy DOP and the HCD/FCO Chief. Describes the technical, business, management, program contracting approach, and other considerations that will control and guide the program contracting process. DoDI 5000.02 requires an acquisition strategy at certain milestones of the program.
(5) 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.
(6) Other – Procurement Desktop Defense (PD2) Milestone Plan, Project management software (other available items that can be used similarly to APS usage).
(d) For all actions exceeding $8M, unless the contract or order is entirely reserved or set-a-side for Small Business under FAR 19, contracting officers shall coordinate their acquisition plans/strategy with their field office Small Business Representatives. 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 acquisition plans/strategy that meet the above criteria with the command’s Director of Small Business Programs.
(f) See the DCG for guidance on “Alpha” Acquisition Contracting.
5607.105 Contents of Written Acquisition Plans.
Removed January 2014)
SUBPART 5607.5 - Inherently Governmental Functions
5607.503 Policies.
(Revised April 2008)
(e) Contracting Officers shall insure that each contracting requirement for services is accompanied by a written determination from the requiring activity that none of the functions contained in the requirement are inherently governmental as defined in FAR 7.503. A formal Determination and Finding (D&F) is required. Disagreements over the determination shall be resolved by the Contracting Officer and reviewed at one level above the Contracting Officer. Should the Contracting Officer and Chief of the Contracting Office fail to agree on the conclusion, forward the package to SORDAC-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.
(Added June 2009)
(h) See 5609.901 for Guidance on Contractors in the Federal Workplace.
HQ, United States Special Operations Command
Special Operations Research, Development, and Acquisition Center (SORDAC-K)
SOFARS 5607
February 2007