Part 507—Acquisition Planning
Subpart 507.1—Acquisition Plans
“Planner” means the person residing in the requirements office who initiates, coordinates and prepares written acquisition plans. The person may be in an individual program office or have responsibility for a number of such offices.
“Planning team” means a team of individuals formed to prepare individual elements of an acquisition plan. The team should be comprised of technical and professional representatives from the requirements customer, contracting, budget, counsel, small business technical advisors (SBTA), and other offices as warranted.
“Requirements office” means the internal GSA office that establishes and funds the agency need. If an organization outside of GSA establishes and funds the need, then the requirements office will be the GSA office that is managing the acquisition for that outside organization.
507.103 Agency-head responsibilities.
The HCA must ensure that the planning team adheres to the requirements of FAR Part 7, Acquisition Planning.
507.104 General procedures.
(a) The planner shall:
(1) Comply with the requirements of FAR Subpart 7.1, and coordinate with other members of the planning team as appropriate.
(2) Write the acquisition plan using all planning team members especially for complex or highly sensitive acquisitions.
(3) Review the acquisition history of the supplies and services.
(4) Review the description of the supplies, including (when necessary for adequate description) a picture, drawing, diagram, or other graphic representation.
(6) Coordinate with local representatives of the Office of the Chief Information Officer (CIO) if the action involves IT services or supplies for use by GSA to ensure compliance with the requirements of GSA Order CIO 2135.1, GSA Information Technology (IT) Capital Planning and Investment Control (not required for establishing a Federal Supply Schedule program).
(7) Obtain concurrence of the contracting officer, and approvals as required in paragraph 507.105(c)(1).
(8) Coordinate with the Office of General Counsel on an as needed basis, but definitely for plans over $20 million.
(9) Ensure that an interagency agreement is in place in all agency specific clauses, terms and conditions are incorporated in the acquisition, when conducting purchases on behalf of other agencies.
(10) Follow sustainability policies and procedures specified in Part 523 throughout the procurement.
(b) The contracting officer shall:
(1) Ensure that acquisition planning and market research are performed for all acquisitions.
(2) Ensure that the contract file contains a copy of the approved acquisition plan.
(c) Applicability. With the following exceptions, all acquisitions, including orders and BPAs, require written acquisition plans.
(1) When awarding a single IDIQ contract or a BPA for a specific requirement and agency, an acquisition plan will be developed for the base contract. The resulting orders should be covered by and reference the same acquisition plan.
(2) Oral plans.
(d) The planner is encouraged to use the Acquisition Planning Wizard (APW) (found at http://apw.gsa.gov), or any successor system, for all acquisitions exceeding the SAT. Not later than 7 calendar days after the acquisition plan is approved, if not completed in APW, an electronic copy shall be sent to email@example.com.
507.105 Contents of acquisition plans.
(1) The APW contains the format prescribed in FAR 7.105 and shall be used in the preparation of acquisition plans. Where a particular element described in FAR 7.105 does not apply, the acquisition plan should read “not applicable.” The dollar value, complexity (e.g., commercial versus non-commercial item) and method of acquisition (e.g., full and open competition versus task/delivery order) of the supplies and services to be acquired will affect the scope and breadth of the acquisition plan.
(3) For leasehold interests in real property, a modified version of the contents of acquisition plans for leases is provided in the APW.
(4) The requirement for a written plan may be waived by the appropriate level of an approving official listed in GSAM 507.105(c). When the requirement for a written plan is waived, an oral plan is still required. The planner must obtain approval for the oral plan from the approving official.
(b) Oral plans. Oral plans are only authorized by approval of the HCA and may be used in unusual and compelling situations. The planner shall document a summary of the oral plan, and shall also include: the name and signature of the approving official; the date the oral plan was approved; and the reason for waiving a written plan. The summary shall be included in the official contract file. In addition, the summary should be a part of, or attached to, any justification for other than full and open competition as required by FAR 6.302, or in the basis for using an exception to the fair opportunity process required by FAR 16.505(b)(2). The summary may be prepared after award if preparation before award would unreasonably delay the award, such as in the case of circumstances warranting the use of a letter contract.
(c) Approval thresholds.
(1) The following are the dollar value thresholds and the level of the approving official for approving acquisition plans or waiving written plans. For purposes of leasing, the Simplified Leasing Acquisition Threshold (SLAT) is defined in Part 570. The HCA may authorize higher level approving officials for the thresholds set out below.
Below the SAT
( SLAT for leases)
SAT (SLAT for leases) to,
and including, $6 million
One Level above the Contracting Officer
Over $6 million to,
and including, $20 million
Over $20 million
Note: Thresholds shall include all options.
(2) If the acquisition meets one of the following criteria and is greater than the SAT, the planner must obtain HCA approval of the plan:
(i) Complex, critical to agency strategic objectives and mission, highly visible or politically sensitive.
(ii) An acquisition with which GSA has little or no experience that may result in a need for greater oversight or risk management.
(iii) Actions using significantly changed methods (e.g., methods of procurement such as lease versus purchase, or methods of performance such as contractor versus Government personnel).
(iv) New construction or repair, lease prospectus and alteration prospectus budget line items.
(v) Any acquisition that involves–
(i) Must be coordinated with the applicable category manager, and obtain approval by the HCA and Senior Procurement Executive; and
(ii) All of the following information must be included in the rationale for adding transactional data reporting elements:
(A) List of the data element(s) to be collected.
(B) Describe how the information will be used.
(C) Describe the method of submission (e.g. which information technology system will be used, what format(s) are acceptable).
(D) Address any potential duplication (i.e. does the contractor submit this data in any other method already?).
(E) Describe efforts to minimize burden on small business.
(F) Describe consequence to Federal program if the element(s) are not collected.
(G) Describe alternatives to obtaining the information other than collecting it from the contractor through this clause.
(H) Identify whether or not this data will be made publicly available and the rationale for this decision, and how the information will be published, if applicable.
(I) Estimated annual burden to the public in terms of hours. The estimate should indicate the number of contractors expected to report the data, frequency of reporting, annual hour burden, and an explanation of how the burden was estimated.
(J) Estimated annual cost to the public in terms of dollars. The estimate should be broken out by initial setup costs and the cost to maintain the reporting requirement.
(K) Estimated total annual cost to the government.
(iii) The approval requirements in this subparagraph do not apply to additional data elements added to a task/delivery order or blanket purchase agreement. However, coordination with the applicable category manager is required.
507.107 Additional requirements for acquisitions involving consolidation, bundling or substantial bundling.
(a) Applicability. The contracting officer must determine if the requirement is considered consolidation, bundling or substantial bundling per the definitions in FAR 2.101(b) and 7.107-4. Additional guidance on the definitions is available on the GSA Acquisition Portal (http://insite.gsa.gov/consolidationbundling).
(b) Thresholds for Written Determination. Notwithstanding exceptions per FAR 7.107-1(b), a written determination is required for–
(1) Consolidation requirements above $2 million; and
(2) Bundling requirements at any dollar value.
(c) Approvals for Written Determination.
(1) The contracting officer shall obtain approvals as required by the Service prior to the Associate Administrator, Office of Small Business Utilization (AA OSBU) and the Senior Procurement Executive (SPE).
(2) The contracting officer shall coordinate with the GSA Office of Small Business Utilization (OSBU) for AA OSBU’s approval prior to the SPE’s approval.
(3) Review and approval guidance can be found on the GSA Acquisition Portal (http://insite.gsa.gov/consolidationbundling).
(d) Contents of Written Determination for Consolidation.
(1) The contracting officer must provide the following information, which includes the requirements at FAR 7.107-2:
(i) Brief description of the acquisition history.
(ii) Description of the market research conducted.
(iii) Identification of any alternative contracting approaches that involve a lesser degree of consolidation of contract requirements.
(iv) Identification of the contracting approach selected.
(v) Identification of any negative impacts to small business concerns.
(vi) Description of steps taken to include small business concerns in the acquisition strategy.
(vii) Explanation of the substantial benefits.
(viii) Statement that the consolidation and/or bundling is necessary and justified.
(2) Additional consolidation and bundling guidance is available on the GSA Acquisition Portal (http://insite.gsa.gov/consolidationbundling).
(e) Additional Contents of Written Determination for Bundling.
(1) The contracting officer must provide the information required by paragraph (e)(2) of this subsection in addition to paragraph (d) of this subsection when the requirement is considered bundling (see FAR 2.101). The additional information listed in this paragraph includes the requirements at FAR 7.107-3.
(2) The contracting officer must use market research to determine prices the Government could have been or could be charged by a small business for the work previously performed by other than small business(es) (see FAR 7.107-3(g)).
(f) Additional Contents of Written Determination for Substantial Bundling.
(1) The contracting officer must provide the following information in addition to paragraphs (d) and (e) of this subsection when the requirement is considered substantial bundling (see FAR 7.107-4).
(2) The contracting officer must provide the following information, which includes the requirements at FAR 7.107-4(b):
(i) Explain the rationale for not selecting each alternative contracting approach with a lesser degree of consolidation.
(ii) Identify the specific impediments to participation by small business concerns as contractors, including any relevant socioeconomic subcategories.
(iii) Explain any actions designed to maximize small business participation through teaming.
(iv) Explain any actions designed to maximize small business participation through subcontracting, including suppliers.
(g) Substantial Benefits Reporting.
(1) The contracting officer must monitor and measure actual savings throughout the acquisition life cycle, and report realized substantial benefits to the SPE.
(2) Realized substantial benefits shall be reported:
(i) Within 14 calendar days after award of the contract.
(ii) Within 30 calendar days after completion of the contract.
(iii) During contract performance as requested by the SPE on a case by case basis.
(3) Reporting guidance is available on the GSA Acquisition Portal (http://insite.gsa.gov/consolidationbundling).
(a) Notification to public of rationale for consolidated, bundled or substantially bundled requirement.
(1) A summary notification of a determination that a consolidated, bundled or substantially bundled requirement is necessary and justified will be published by the SPE on the GSA public website at http://www.gsa.gov/consolidationbundling. The notice will be posted within 7 days of the SPE approved determination.
(2) Any solicitation related to the consolidation, bundled or substantially bundled requirement can only be published after the summary notice from subparagraph (a)(1) of this section has been published for at least 7 days.
(3) The contracting officer is encouraged to provide the summary notification from subparagraph (a)(1) of this section to the Governmentwide Point of Entry (GPE) before issuance of the solicitation.
(4) The contracting officer shall publish the SPE approved determination with the publication of the solicitation, redacted as necessary.
(5) For bundled or substantially bundled requirements, in addition to the requirements of this subsection, the contracting officer must verify compliance with the notification requirements of FAR 7.107-5(b).
(b) Notification to SBA of follow-on consolidated or bundled requirements.
(1) The contracting officer shall coordinate with the designated SBTA (see 519.4 to provide follow-on notification to the SBA PCR in accordance with FAR 7.107-5(c). The designated SBTA will provide notification to the AA OSBU.
(2) The SBTA will submit the notification to SBA PCR within 5 business days of receiving the notification from the contracting officer or request an extension from the contracting officer.
Subpart 507.5—Inherently Governmental Functions
(a) Concurrent with the transmittal of each statement of work or any modification to a statement of work for a service contract, the requirements office must provide the contracting officer a written determination that none of the functions to be performed are inherently governmental as defined in FAR 7.5. The determination must include a statement that the requirement is not for functions similar to those listed under FAR 7.503(c).
(b) The requirements office must also review the examples of functions listed under paragraph (d) of FAR 7.503. While these functions are not inherently governmental, they may restrict the discretionary authority, decision-making responsibility, or accountability of Government officials using the contractor services or work products. If the services to be acquired may cause such restrictions, the acquisition plan must discuss the associated vulnerabilities, and address management controls to mitigate them.
(1) These measures may include requiring special controls and safeguards to prevent improper personal services relationships, contractor personnel access to privileged or sensitive information, and/or confusion regarding the mistaking of contractor employees for Federal employees.
(3) The HCA resolves any disagreement regarding the requirements official’s determination, following the guidelines in FAR 7.5. The HCA may delegate this authority to a level not lower than the contracting director.
Subpart 507.70—Additional Requirements for Purchases in Support of National Security Systems involving Weapons Systems
507.7000 Scope of subpart.
This subpart prescribes acquisition policies and procedures for use in acquiring information technology supplies, services and systems in support of a weapon system as part of a national security system, as defined by FAR 39.002.
(a) Although GSA’s mission does not include the direct acquisition of weapon systems on behalf of the Department of Defense (DoD), GSA contracting activities may procure information technology supplies, services and systems in support of a weapon system, which is part of a national security system (e.g., components, services to install and maintain weapon systems, ancillary items and services) when responding to a bona-fide requirement received from a requiring agency or program office.
(b) Contracting Officers shall ensure that all requiring agency regulations and the policies and directives of The Committee on National Security Systems at www.cnss.gov are incorporated during the acquisition planning stage and are met before acquiring information technology supplies, services and systems in support of a weapon system as part of a national security system.
(c) Employees responsible for or procuring information technology supplies, services and systems in support of a weapon system shall possess the appropriate security clearance associated with the level of security classification related to the acquisition. They include, but are not limited to contracting officers, contract specialists, project/program managers, and contracting officer representatives.