[Code of Federal Regulations]
[Title 48, Volume 1]
[Revised as of October 1, 2003]
From the U.S. Government Printing Office via GPO Access
[CITE: 48CFR4.602]

[Page 68-69]
 
            TITLE 48--FEDERAL ACQUISITION REGULATIONS SYSTEM
 
                CHAPTER 1--FEDERAL ACQUISITION REGULATION
 
PART 4_ADMINISTRATIVE MATTERS--Table of Contents
 
                     Subpart 4.6_Contract Reporting
 
Sec.  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 report data to the Federal Procurement Data 
Center (FPDC), which collects, processes, and disseminates official 
statistical data

[[Page 69]]

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) Data for other policy and management control purposes.
    (b) The FPDS Reporting Manual provides a complete list of reporting 
and nonreporting agencies and organizations. This manual (available at 
no charge from the General Services Administration, Federal Procurement 
Data Center, 7th & D Streets SW., room 5652, Washington, DC 20407, 
telephone (202) 401-1529, FAX (202) 401-1546) provides the necessary 
instruction to the data collection point in each agency as to what data 
are required and how often to provide the data.
    (c) Data collection points in each agency report data on SF 279, 
Federal Procurement Data System (FPDS) Individual Contract Action 
Report, and SF 281, Federal Procurement Data System (FPDS) Summary 
Contract Action Report ($25,000 or Less), or computer-generated 
equivalent. Although the SF 279 and SF 281 are not mandatory for use by 
the agencies, they do provide the mandatory format for submitting data 
to the FPDS.
    (d) The contracting officer must report 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 the provision 
prescribed at 4.603(a). If the successful offeror does not provide its 
number, the contracting officer must contact the offeror and obtain 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.

[48 FR 42113, Sept. 19. 1983. Redesignated at 50 FR 52429, Dec. 23, 
1985, and amended at 54 FR 29280, July 11, 1989; 53 FR 43388, Oct. 26, 
1988; 55 FR 52788, Dec. 21, 1990; 56 FR 41744, Aug. 22, 1991; 57 FR 
60572, Dec. 21, 1992; 60 FR 48259, Sept. 18, 1995; 61 FR 67412, Dec. 20, 
1996; 62 FR 40236, July 25, 1997; 65 FR 60544, Oct. 11, 2000; 68 FR 
56680, Oct. 1, 2003]