> ### Subpart 4.6- Contract Reporting

> ## 4.600 Scope of subpart.

> This subpart prescribes uniform reporting requirements for the Federal Procurement Data System (FPDS).

> ## 4.601 Record requirements.

> (a) Each executive agency shall establish and maintain for a period of 5 years a computer file, by fiscal year, containing unclassified records of all procurements exceeding $25,000. This file shall be accessible to the public using FPDS-NG.
> (b) With respect to each procurement carried out using competitive procedures, agencies shall be able to access from the computer file, as a minimum, the following information:
> (1) The date of contract award.
> (2) Information identifying the source to whom the contract was awarded.
> (3) The property or services obtained by the Government under the procurement.
> (4) The total cost of the procurement.
> (5) Those procurements which result in the submission of a single bid or proposal so that they can be separately categorized and designated noncompetitive procurements using competitive procedures.
> (c) In addition to paragraph (b) of this section with respect to each procurement carried out using procedures other than competitive procedures, agencies shall be able to access-
> (1) The reason under Subpart 6.3 for the use of such procedures; and
> (2) The identity of the organization or activity which conducted the procurement.
> (d) In addition to the information described in paragraphs (b) and (c) of this section, for procurements in excess of $25,000, agencies shall be able to access information on the following:
> (1) Awards to small disadvantaged businesses using either set-asides or full and open competition.
> (2) Awards to business concerns owned and controlled by women.
> (3) The number of offers received in response to a solicitation.
> (4) Task or delivery order contracts.
> (5) Contracts for the acquisition of commercial items.
> (6) Contracts or task orders treated as commercial items pursuant to 12.102(g).
> (e) In addition to the information described in paragraphs (b), (c), and (d) of this section, agencies must be able to access information from the computer file to identify bundled contracts with a total contract value, including all options, exceeding $5,000,000.
> (f) Agencies must transmit this information to the Federal Procurement Data System in accordance with its procedures.

> ## 4.602 Federal Procurement Data System.

> (a) The FPDS provides a comprehensive mechanism for assembling, organizing, and presenting contract placement data for the Federal Government. Federal agencies will now report data directly to the Federal Procurement Data System-Next Generation (FPDS-NG), which collects, processes, and disseminates official statistical data on Federal contracting. The data provide-
> (1) A basis for recurring and special reports to the President, the Congress, the General Accounting Office, Federal executive agencies, and the general public;
> (2) A means of measuring and assessing the impact of Federal contracting on the Nation's economy and the extent to which small, veteran-owned small, service-disabled veteran-owned small, HUBZone small, small disadvantaged, and women-owned small business concerns are sharing in Federal contracts; and
> (3) Information for other policy and management control purposes, and for public access.
> (b) The FPDS website, https://www.fpds.gov, provides instructions for submitting data. It also provides a complete list of departments, agencies, and other entities that submit data to the FPDS, as well as technical and end-user guidance, and a computer-based tutorial.
> (c)(1) Data collection points in each agency shall submit FPDS-required data on contract actions directly to FPDS-NG. Agencies must report all transactions over $2,500 and modifications to those transactions regardless of dollar value.
> (2) Agencies participating under the Small Business Competitiveness Demonstration Program (see Subpart 19.10) shall report as an individual contract action all awards, regardless of dollar value, in the designated industry groups.
> (3) Agencies may choose to report transactions at or below $2,500, including those made using the Governmentwide commercial purchase card, except as provided in paragraph (c)(2) of this section.
> (4) Until September 30, 2004, agencies shall report contract actions between $2,500 and $25,000 either in individual or summary form. After September 30, 2004, agencies shall submit only individual contract action reports.
> (d) The contracting officer must identify and report (if it is not pre-populated by the Central Contractor Registration (CCR) database), a Contractor Identification Number for each successful offeror. A Data Universal Numbering System (DUNS) number, which is a nine-digit number assigned by Dun and Bradstreet Information Services to an establishment, is the Contractor Identification Number for Federal contractors. The DUNS number reported must identify the successful offeror's name and address exactly as stated in the offer and resultant contract. The contracting officer must ask the offeror to provide its DUNS number by using either the provision prescribed in paragraph (a) of 4.603 or the FAR clause prescribed at 4.1104. If the successful offeror does not provide its number, the contracting officer must contact the offeror and assist them in obtaining the DUNS number.
> (e) Unique Procurement Instrument Identifier (PIID).
> (1) The FPDS requires that each reporting agency assign a unique identifier for every contract, purchase order, BOA, Basic Agreement, and BPA reported to FPDS. Such identifiers shall comply with the contract numbering guidelines established by the Joint Financial Management Improvement Project. The PIID shall consist of alpha characters in the first positions to indicate the agency, followed by alphanumeric characters identifying bureau, offices, or other administrative subdivisions. The last portion of the PIID shall be numbered sequentially. The PIID may include other elements, as appropriate, such as fiscal year. Delivery orders, task orders, and call numbers must be unique in combination with the basic reference contract vehicle identifier. When the basic reference contract is available for multi-agency use (GWAC, Federal Supply Schedule contract, etc.), an ordering agency shall use the same agency identification prefix for its delivery orders, task orders, and call numbers as it uses for its contractual instruments.
> (2) Agencies are required to have in place, no later than October 1, 2003, a process that will ensure that each PIID reported to FPDS is unique, Governmentwide, and will remain so for at least 20 years from the date of contract award. To eliminate the possibility of duplication between agencies, agencies must submit their proposed identifier to the Federal Procurement Data Center, which will maintain a registry of the identifiers on the FPDC website and validate their use in all transactions.

> ## 4.603 Solicitation provisions.

> (a) Insert the provision at 52.204-6, Data Universal Numbering System (DUNS) Number, in solicitations that-
> (1) Are expected to result in a requirement for the generation of an individual contract action report (see 4.602(c)); and
> (2) Do not contain the clause at 52.204-7, Central Contractor Registration.
> (b) Insert the provision at 52.204-5, Women-Owned Business (Other Than Small Business), in solicitations that-
> (1) Are not set aside for small business concerns;
> (2) Exceed the simplified acquisition threshold; and
> (3) Are for contracts that will be performed in the United States or its outlying areas.