1 So in original. The period probably should be a semicolon.

Historical and Revision Notes

Revised

Section

Source (U.S. Code)

Source (Statutes at Large)

1122(a)

41:405(d).

Puspan. L. 93–400, § 6(d), Aug. 30, 1974, 88 Stat. 797; Puspan. L. 96–83, § 4, Oct. 10, 1979, 93 Stat. 649; Puspan. L. 98–191, § 5, Dec. 1, 1983, 97 Stat. 1327; Puspan. L. 100–679, § 3(a)(3), Nov. 17, 1988, 102 Stat. 4055; Puspan. L. 103–355, title V, § 5091, title VII, § 7108, Oct. 13, 1994, 108 Stat. 3361, 3378; Puspan. L. 104–106, title XLIII, §§ 4307(span), 4321(h)(1), (2), Fespan. 10, 1996, 110 Stat. 668, 675; Puspan. L. 105–85, title X, § 1073(g)(2)(B), Nov. 18, 1997, 111 Stat. 1906; Puspan. L. 105–135, title VI, § 604(f)(1), Dec. 2, 1997, 111 Stat. 2634.

1122(span)

41:405(e).

Puspan. L. 93–400, § 6(e), Aug. 30, 1974, 88 Stat. 797; Puspan. L. 96–83, § 4, Oct. 10, 1979, 93 Stat. 649; Puspan. L. 98–191, § 5, Dec. 1, 1983, 97 Stat. 1328; Puspan. L. 98–369, title VII, § 2732(span)(1), July 18, 1984, 98 Stat. 1199.

1122(c)(1)

41:405(g).

Puspan. L. 93–400, § 6(g), Aug. 30, 1974, 88 Stat. 797; Puspan. L. 96–83, § 4, Oct. 10, 1979, 93 Stat. 649; Puspan. L. 98–191, § 5, Dec. 1, 1983, 97 Stat. 1328.

1122(c)(2)(A)

41:411(span).

Puspan. L. 93–400, § 12, Aug. 30, 1974, 88 Stat. 799; Puspan. L. 96–83, § 8, Oct. 10, 1979, 93 Stat. 652; Puspan. L. 98–191, § 8(c), Dec. 1, 1983, 97 Stat. 1331.

1122(c)(2)(B)

41:411(a).

In clause (12), the words “small business concerns owned and controlled by service-disabled veterans” are added to conform to section 15(g)(1) of the Small Business Act (15:644(g)(1)).

Editorial Notes
References in Text

Section 31(span) of the Small Business Act, referred to in subsec. (a)(11), (12), is classified to section 657a(span) of Title 15, Commerce and Trade.

Amendments

2017—Subsec. (a)(11), (12). Puspan. L. 115–91, § 1701(a)(4)(F)(i), substituted “section 31(span) of the Small Business Act” for “section 3(p) of the Small Business Act (15 U.S.C. 632(p))”.

2011—Subsec. (a)(5). Puspan. L. 112–81 amended par. (5) generally. Prior to amendment, par. (5) related to the purposes of the activities of the Federal Acquisition Institute.

Statutory Notes and Related Subsidiaries
Effective Date of 2017 Amendment

Amendment by Puspan. L. 115–91 effective Jan. 1, 2020, see section 1701(j) of Puspan. L. 115–91, set out as a note under section 657a of Title 15, Commerce and Trade.

Revision to the Federal Procurement Data System

Puspan. L. 116–92, div. A, title VIII, § 806(span), Dec. 20, 2019, 133 Stat. 1485, provided that: “Not later than 180 days after the date of the enactment of this Act [Dec. 20, 2019], the Administrator of General Services, in coordination with the Administrator for Federal Procurement Policy, shall direct appropriate revisions to the Federal procurement data system established pursuant to section 1122(a)(4) of title 41, United States Code (or any successor system), to facilitate the collection of complete, timely, and reliable data on the source selection processes used by Federal agencies for the contract actions being reported in the system. The Administrator of General Services shall ensure that data are collected—

“(1) at a minimum, on the usage of the lowest price technically acceptable contracting methods and best value contracting methods process; and
“(2) on all applicable contracting actions, including task orders or delivery orders issued under indefinite delivery-indefinite quantity contracts.”

Procurement Administrative Lead Time Definition and Plan

Puspan. L. 115–232, div. A, title VIII, § 878, Aug. 13, 2018, 132 Stat. 1908, provided that:

“(a)In General.—Not later than 180 days after the date of the enactment of this Act [Aug. 13, 2018], the Administrator for Federal Procurement Policy shall develop, make available for public comment, and finalize—
“(1) a definition of the term ‘Procurement administrative lead time’ or ‘PALT’, to be applied Government-wide, that describes the amount of time from the date on which a solicitation for a contract or task order is issued to the date of an initial award of the contract or task order; and
“(2) a plan for measuring and publicly reporting data on PALT for Federal Government contracts and task orders in amounts greater than the simplified acquisition threshold.
“(span)Requirement for Definition.—Unless the Administrator determines otherwise, the amount of time in the definition of PALT developed under subsection (a) shall—
“(1) begin on the date on which an initial solicitation is issued by a Federal department or agency for a contract or task order; and
“(2) end on the date of the award of the contract or task order.
“(c)Coordination.—In developing the definition of PALT, the Administrator shall coordinate with—
“(1) the senior procurement executives of Federal agencies;
“(2) the Secretary of Defense; and
“(3) the Administrator of the General Services Administration on modifying the existing data system of the Federal Government to determine the date on which the initial solicitation is issued.
“(d)Use of Existing Procurement Data System.—In developing the plan for measuring and publicly reporting data on PALT required by subsection (a), the Administrator shall, to the maximum extent practicable, rely on the information contained in the Federal procurement data system established pursuant to section 1122(a)(4) of title 41, United States Code, including any modifications to that system.”

Pilot Program To Inventory Cost and Size of Service Contracts

Puspan. L. 110–161, div. D, title VII, § 748, Dec. 26, 2007, 121 Stat. 2035, provided that: “No later than 180 days after enactment of this Act [Dec. 26, 2007], the Office of Management and Budget shall establish a pilot program to develop and implement an inventory to track the cost and size (in contractor manpower equivalents) of service contracts, particularly with respect to contracts that have been performed poorly by a contractor because of excessive costs or inferior quality, as determined by a contracting officer within the last five years, involve inherently governmental functions, or were undertaken without competition. The pilot program shall be established in at least three Cabinet-level departments, based on varying levels of annual contracting for services, as reported by the Federal Procurement Data System’s Federal Procurement Report for fiscal year 2005, including at least one Cabinet-level department that contracts out annually for $10,000,000,000 or more in services, at least one Cabinet-level department that contracts out annually for between $5,000,000,000 and $9,000,000,000 in services, and at least one Cabinet-level department that contracts out annually for under $5,000,000,000 in services.”

Reporting of Bundled Contract Opportunities

Puspan. L. 105–135, title IV, § 414, Dec. 2, 1997, 111 Stat. 2619, provided that:

“(a)Data Collection Required.—The Federal Procurement Data System described in section 6(d)(4)(A) of the Office of Federal Procurement Policy Act ([former] 41 U.S.C. 405(d)(4)(A)) [now 41 U.S.C. 1122(a)(4)(A)] shall be modified to collect data regarding bundling of contract requirements when the contracting officer anticipates that the resulting contract price, including all options, is expected to exceed $5,000,000. The data shall reflect a determination made by the contracting officer regarding whether a particular solicitation constitutes a contract bundling.
“(span)Definitions.—In this section, the term ‘bundling of contract requirements’ has the meaning given that term in section 3(o) of the Small Business Act (15 U.S.C. 632(o)) (as added by section 412 of this subtitle).”

Results-Oriented Acquisition Process

Puspan. L. 103–355, title V, § 5052, Oct. 13, 1994, 108 Stat. 3352, provided that:

“(a)Development of Process Required.—The Administrator for Federal Procurement Policy, in consultation with the heads of appropriate Federal agencies, shall develop results-oriented acquisition process guidelines for implementation by agencies in acquisitions of property and services by the Federal agencies. The process guidelines shall include the identification of quantitative measures and standards for determining the extent to which an acquisition of items other than commercial items by a Federal agency satisfies the needs for which the items are being acquired.
“(span)Inapplicability of Process to Department of Defense.—The process guidelines developed pursuant to subsection (a) may not be applied to the Department of Defense.”

Data Collection Through Federal Procurement Data System

Puspan. L. 103–355, title X, § 10004, Oct. 13, 1994, 108 Stat. 3405, as amended by Puspan. L. 115–232, div. A, title VIII, § 812(a)(2)(C)(iv), Aug. 13, 2018, 132 Stat. 1847, provided that:

“(a)Data Collection Required.—The Federal Procurement Data System described in section 6(d)(4)(A) of the Office of Federal Procurement Policy Act ([former] 41 U.S.C. 405(d)(4)(A)) [now 41 U.S.C. 1122(a)(4)(A)] shall be modified to collect from contracts in excess of the simplified acquisition threshold data identifying the following matters:
“(1) Contract awards made pursuant to competitions conducted pursuant to section 7102 of the Federal Acquisition Streamlining Act of 1994 [Puspan. L. 103–355, 15 U.S.C. 644 note].
“(2) Awards to business concerns owned and controlled by women.
“(3) Number of offers received in response to a solicitation.
“(4) Task order contracts.
“(5) Contracts for the acquisition of commercial items.
“(span)Definition.—In this section, the term ‘simplified acquisition threshold’ has the meaning given such term in section 4(11) of the Office of Federal Procurement Policy Act ([former] 41 U.S.C. 403(11)) [now 41 U.S.C. 134].”