From: "Saved by Windows Internet Explorer 7" Subject: FR Doc E8-8447 Date: Sun, 27 Apr 2008 08:49:57 -0500 MIME-Version: 1.0 Content-Type: text/html; charset="Windows-1252" Content-Transfer-Encoding: quoted-printable Content-Location: X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6000.16545 FR Doc E8-8447
[Federal Register: April 22, 2008 (Volume 73, Number =
[Rules and Regulations]              =20
[Page 21773-21779]
From the Federal Register Online via GPO Access []
[DOCID:fr22ap08-14]                        =20





48 CFR Parts 1, 2, 4, 12, and 52

[FAC 2005-25; FAR Case 2004-038; Item I; Docket 2008-0001, Sequence 6]
RIN 9000-AK94

Federal Acquisition Regulation; FAR Case 2004-038, Federal=20
Procurement Data System Reporting

AGENCIES: Department of Defense (DoD), General Services Administration=20
(GSA), and National Aeronautics and Space Administration (NASA).

ACTION: Interim rule with request for comments.


SUMMARY: The Civilian Agency Acquisition Council and the Defense=20
Acquisition Regulations Council (Councils) have agreed on an interim=20
rule amending the Federal Acquisition Regulation (FAR) to revise the=20
process for reporting contract actions to the Federal Procurement Data=20
System (FPDS).

DATES: Effective Date: April 22, 2008.
    Comment Date: Interested parties should submit written comments to=20
the FAR Secretariat on or before June 23, 2008 to be considered in the=20
formulation of a final rule.

ADDRESSES: Submit comments identified by FAC 2005-25, FAR case 2004-
038, by any of the following methods: ht=
comments via the Federal eRulemaking portal by inputting ``FAR Case=20
2004-038'' under the heading ``Comment or Submission''. Select the link=20
``Send a Comment or Submission'' that corresponds with FAR Case 2004-
038. Follow the instructions provided to complete the ``Public Comment=20
and Submission Form''. Please include your name, company name (if any),=20
and ``FAR Case 2004-038'' on your attached document.
     Fax: 202-501-4067.
     Mail: General Services Administration, Regulatory=20
Secretariat (VPR), 1800 F Street, NW, Room 4035, ATTN: Diedra Wingate,=20
Washington, DC 20405.
    Instructions: Please submit comments only and cite FAC 2005-25, FAR=20
case 2004-038, in all correspondence related to this case. All comments=20
received will be posted without change to http://fr=
including any personal and/or business confidential information=20

FOR FURTHER INFORMATION CONTACT: Mr. Ernest Woodson, Procurement=20
Analyst, at (202) 501-3775 for clarification of content. Please cite=20
FAC 2005-25, FAR case 2004-038. For information pertaining to status or=20
publication schedules, contact the FAR Secretariat at (202) 501-4755.


A. Background

    As of October 2003, all agencies were to begin reporting FAR-based=20
contract actions to the modified system. During Fiscal Year 2004,=20
members of the interagency Change Control Board, as well as=20
departmental teams working on the migration of data from the old to new=20
system, recognized both the opportunity to standardize reporting=20
processes and the need to revise the FAR to provide current and clear=20
reporting requirements.
    In this interim rule, the Government is establishing its commitment=20
for Federal Procurement Data System (FPDS) data to serve as the single=20
authoritative source of all procurement data for a host of applications=20
and reports, such as the Central Contractor Registration (CCR), the=20
Electronic Subcontracting Reporting System (eSRS), the Small Business=20
Goaling Report (SBGR), and Resource Conservation and Recovery Act=20
(RCRA) data.
    The enhanced FPDS was put into production on October 1, 2003 by=20
implementing newer technology to report contract actions. The old=20
system had 48 data elements; the new system has 145+ elements,=20
including who funds the contract. The new system has the ability to=20
receive data and provide data to other applications used in the=20
procurement community, allowing the Government to give ``credit'' to=20
the agency that funds the contract action. The system is also an=20
enabler ensuring that metrics are consistent when comparing one=20
department, service, or organization to another.
    Small agencies that do not have the staff or resources necessary to=20
purchase the automated contract writing application necessary for=20
reporting contract actions as required by this interim rule are=20
encouraged to partner with a large agency and become a subscriber on=20
their system. For information about frequently asked questions, see=20
    The rule amends the FAR by:
    1. Revising FAR 1.106 to change the FAR segment 4.602 to 4.605, and=20
4.603 to 4.607.

[[Page 21774]]

    2. Revising FAR 2.101 to add a definition for ``Chief Acquisition=20
Officer'' and revising the definition for ``Data Universal Numbering=20
System number '' to include that it is the identification number for=20
Federal contractors.
    3. Renaming FAR 4.601 ``Definitions'' and revising the section to=20
add definitions for ``assisted acquisition,'' ``contract action,''=20
``contract action report (CAR),'' ``definitive contract,'' ``direct=20
acquisition,'' ``entitlement program,'' ``generic DUNS number,''=20
``indefinite-delivery vehicle (IDV),'' ``requesting agency,'' and=20
``servicing agency'' as they pertain to FPDS.
    4. Renaming FAR section 4.602 ``General'' and revising to describe=20
the general characteristics of FPDS and identify data that will and=20
will not be maintained in FPDS.
    5. Renaming FAR section 4.603 ``Policy'' and revising the section=20
to: describe the use of FPDS to maintain publicly available information=20
about contract actions; require agencies to report actions subject to=20
the FAR and using appropriated funds; require agencies performing=20
assisted or direct acquisitions to report such actions; encourage=20
agencies exempt from the FAR or using non-appropriated funds to report=20
such actions; and require agencies awarding contracts using a mix of=20
appropriated and non-appropriated funds to only report the full=20
appropriated portion of the action.
    6. Adding a new FAR section 4.604, Responsibilities. The new=20
section: describes the responsibility of the Senior Procurement=20
Executive (SPE) and head of the contracting activity for developing and=20
monitoring a process to ensure timely and accurate reporting of=20
contractual actions to FPDS describes the responsibility of the=20
contracting officer for the submission and accuracy of the contract=20
action report; describes how and when the contract action report is to=20
be submitted to FPDS when a contract writing system is or is not=20
integrated with FPDS or when the contract action is awarded pursuant to=20
FAR 6.302-2 or in accordance with the authorities listed at FAR Subpart=20
18.2; and indicates the date that the Chief Acquisition Officer of each=20
agency reporting to FPDS must submit an annual certification of the=20
agency's reported actions.
    7. Adding a new FAR section 4.605, Procedures. The new section=20
describes: the Procurement Instrument Identifier; and the Data=20
Universal Numbering System (DUNS).
    8. Adding a new FAR section 4.606, Reporting Data. The new section=20
will describe: the mandatory actions agencies must report to FPDS; the=20
use of FPDS ``Express Reporting;'' the reporting requirements for=20
agencies participating in the Small Business Competitiveness=20
Demonstration Program; and the responsibility of the GSA Purchase Card=20
Management to provide purchase card data to FPDS; how agencies may=20
report other actions not specified in the subpart; and actions not to=20
be reported to FPDS, including imprest funds transactions below the=20
micro-purchase threshold, orders from GSA Stock and Global Supply=20
Programs, orders against certain indefinite-delivery vehicles,=20
purchases made using Javits-Wagner-O'Day service stores, and purchases=20
made using non-appropriated fund activity cards, chaplain cards,=20
individual Government personnel training orders, and Defense Printing.
    9. Renumbering the existing FAR 4.603 as 4.607.

B. The Councils have developed the following list of questions and=20
answers to facilitate the public's understanding of the changes=20
proposed in FAR Case 2004-038 for reporting contract actions under the=20
Federal Acquisition Regulation (FAR), Subpart 4.6.

    Question 1: What is the Federal Procurement Data System (FPDS)?
    FPDS is a comprehensive mechanism for assembling, organizing, and=20
presenting contract procurement data for the Federal Government. The=20
system collects, processes, and disseminates official statistical data=20
on Federal contracting. The data is used to generate reports for the=20
three branches of Government and the general public.
    Question 2: Why are we changing the way the Federal Government=20
collects procurement data?
    The way the Federal Government collects procurement data is being=20
enhanced to satisfy the Government's compelling need to manage and=20
understand how and where your tax dollars are spent. Collecting data=20
about Government procurements provides a broad picture of the overall=20
Federal acquisition process. The ability to look at all contracts=20
across many agencies, in greater detail, is a key component in=20
establishing transparency, trust in our Government, and credibility in=20
the professionals who use and perform these contracts. With an enhanced=20
view of Federal spending we can conduct analyses to structure strategic=20
procurements and save money, improve Governmentwide management, and=20
establish interoperability with other Governmentwide data systems.
    Question 3: What impact will the enhancements have on errors in=20
    Government procurement executives realize that contracts are=20
written for extended periods of time and that modifications are=20
routinely made to these contracts, even if just to exercise an option.=20
As a result of inputting data regarding these contracts into FPDS, some=20
errors will end up in FPDS. Additionally, as long as there are data=20
elements in a contract writing system that are released to FPDS without=20
validation, errors will continue. Regardless of the reason it happens,=20
if we continue to allow the data to be input in FPDS without=20
validation, the professionalism and credibility of the acquisition=20
community is called into question. The FPDS enhancements provide the=20
capability to correct any information that is incorrect or outdated.
    Question 4: What level of effort is expected of contracting=20
personnel in eliminating errors in procurement reported to FPDS?
    We anticipate minimal effort is required of the contracting officer=20
or contracting specialist to ensure that the data reported to FPDS is=20
current, accurate, and complete. It is incumbent on contracting=20
officers and agencies to assure the accuracy of all information=20
submitted. It is also certain that if care is taken to record the data=20
correctly the first time, it will reduce the burden to make=20
corrections. To draw attention to the criticality of this information,=20
the Office of Federal Procurement Policy (OFPP) will require each=20
agency, beginning in December 2007, to certify annually that all data=20
is accurate and complete. See
    Question 5: Why is it important for procurement data to be accurate=20
and timely?
    (a) Timely and accurate procurement data ensures that the recurring=20
and special reports to the President, Congress, the Government=20
Accountability Office, and the general public on the expenditure of=20
taxpayer dollars are reliable, useful, realistic, and serve as a=20
rational basis for assessing--
     The effect of Federal contracting on our Nation's economy=20
and the extent to which small, veteran-owned small, service-disabled=20
veteran-owned small, HUBZone small, small disadvantaged, women-owned=20
small business concerns, and nonprofit agencies operating under the=20
Javits-Wagner-O'Day Act are sharing in Federal contracts; and
     Measuring the impact of other Federal procurement policies=20
and management initiatives.

[[Page 21775]]

    (b) In addition to the above, a list of purposes for which this=20
business information is used, includes but is not limited to the=20
     Decisions on organization structure.
     Decisions related to staffing.
     Decisions related to training.
     Assessments on the extent to which awards are made to=20
businesses in the various socio-economic categories.
     Assessments of the impact of competition on the=20
acquisition process.
    (c) FPDS also provides the following--
     An authoritative source of information;
     Discipline in the reporting process;
     Confidence in Government acquisition practices, and=20
reports; and
     Standardized means for collecting contract data.
    Question 6: Does FPDS contain non-procurement data? If so, do we=20
use these contracts in our statistics?
    It is true several agencies have used FPDS to account for other=20
types of awards that were not FAR based contracts. Once these actions=20
are identified, the Government subtracts the dollars and actions from=20
the total of FAR based actions prior to calculating totals or=20
establishing goals.
    Question 7: Why should FPDS collect non-FAR based actions?
    Many agencies are already collecting other business data that is=20
non-FAR based. In the future, FPDS will be able to accurately discern=20
what is FAR based and non-FAR based actions. Agencies that desire=20
internal business information and have a bona fide need for this=20
information can request a modification to FPDS. In these cases, the=20
business data may or may not be accessible to the public.
    Question 8: What additional responsibilities will contracting=20
officers have as a result of the FPDS enhancements?
    Contracting officers will have the following additional=20
    a. The submission and accuracy of the individual contract action=20
report (CAR), and validating the CAR prior to transmittal of the data.
    b. The review of their own CAR information as well as all FPDS=20
information created by subordinates within their organization.
    (1) Whenever a contract writing system is integrated with FPDS,=20
confirming the CAR for accuracy prior to release of the contract award.
    (2) Ensuring that the CAR is submitted within 3 business days after=20
contract award whenever an automated contract writing system is not=20
    (3) Ensuring that the CAR is submitted to FPDS within 30 days after=20
contract award for any actions done following FAR 6.302-2 or FAR=20
Subpart 18.2.
    (4) Including a code to identify the source of funds being used to=20
procure needed supplies or services. Emphasis is not just on the=20
contracting office awarding the contract, but also on reporting=20
accurate funding information to include the funding office code of the=20
customer agency for whom the contract, delivery order, or task order is=20
issued, and submitting the correct information to FPDS.
    Question 9: Why should the contracting officer be responsible for=20
data reported to FPDS?
    The contracting officer is ultimately responsible for the=20
solicitation and award of a contract action and by virtue of that=20
responsibility, the contracting officer is also responsible for all=20
actions through close-out of the contract. The CAR is a part of the=20
contract file documentation and as such, its accurate and timely=20
completion rests with the contracting officer.
    Question 10: How will contract specialists or other acquisition=20
staff be affected by the enhancement to FPDS?
    The enhancements will provide for data collection to be more=20
automated. Where data collection is not automated, contracting officers=20
will be required to approve or validate fewer elements. Overall, the=20
enhancements will facilitate better accuracy.
    Question 11: Why is there an emphasis on Indefinite Delivery=20
Vehicles (IDV) in FPDS?
    IDV's provide agencies with a simplified process for obtaining=20
commonly used commercial supplies and services at prices associated=20
with volume buying. They are emphasized because of their increased use=20
in every agency and in interagency contracting.
    Question 12: What needs are satisfied by making procurement data=20
publicly accessible in FPDS?
    Making procurement data publicly accessible provides the public--
    a. Important information about acquisitions awarded by the Federal=20
    b. The ability to fully understand how tax dollars are spent;
    c. An understanding where and how competition is conducted; and
    d. Information on where and with whom business opportunities exist.
    Additionally, collecting data about Government procurements=20
provides a broad picture of the overall Federal acquisition process.=20
Having the ability to look at Federal contracts across many agencies,=20
in greater detail, is a key ingredient to establishing trust in our=20
Government and credibility in the professionals who award and=20
administer these contracts. With a transparent view of Federal=20
spending, analyses may be conducted to structure procurements=20
strategically and save taxpayer dollars; improve Governmentwide=20
management; ensure appropriate small business participation; and=20
establish interoperation with other Governmentwide data systems. This=20
information will enable service-wide, department-wide, or=20
Governmentwide strategic sourcing.
    Question 13: Which agencies must report to FPDS and why?
    Executive departments and agencies are responsible for collecting=20
and reporting procurement data to FPDS as required by Federal=20
Acquisition Regulations (FAR).
    In addition, the recent passage of The Federal Funding=20
Accountability and Transparency Act of 2006 has established that all=20
officials who make Federal awards of any type have a duty to report=20
their activities to the public. Therefore, reporting procurement data=20
applies to the entire United States Government.
    As previously stated, all levels of the Government use the reported=20
    Question 14: What is the FPDS Express Reporting Application?
    FPDS's Express Reporting Application allows users to report a=20
single record for a single vendor for multiple contract actions.
    Question 15: Will agencies be able to see their data just like the=20
public can see it?
    Yes. FPDS will provide the official Federal reports as well as=20
several workload reports designed specifically for first-line=20
supervisors and contract managers.
    The use of Federal reports will alleviate the need for individual=20
agencies to collect, verify, and distribute statistics for a host of=20
requirements such as the Small Business Goaling Report (SBGR), the=20
Performance-Based Acquisition (PBA) report, and the Resource=20
Conservation and Recovery Act (RCRA) Report just to name a few.
    Question 16: Does FPDS contain contract data from non-FAR agencies?
    Some agencies which are not subject to the FAR may be required by=20
other authority, statute, or at the Office of Management and Budget's=20
direction to report non-FAR based contract action data into FPDS. For=20
example, the Federal Funding Accountability and Transparency Act of=20
2006 requires a searchable website that provides public access to=20
information about Federal expenditures.
    This is not a significant regulatory action and, therefore, was not=20
subject to

[[Page 21776]]

review under Section 6(b) of Executive Order 12866, Regulatory Planning=20
and Review, dated September 30, 1993. This rule is not a major rule=20
under 5 U.S.C. 804.

C. Regulatory Flexibility Act

    The interim rule is not expected to have a significant economic=20
impact on a substantial number of small entities within the meaning of=20
the Regulatory Flexibility Act, 5 U.S.C. 601, et seq., because contract=20
reporting is not accomplished by the vendor community, only by=20
Government contracting entities. Therefore, an Initial Regulatory=20
Flexibility Analysis has not been performed. The Councils will consider=20
comments from small entities concerning the affected FAR Parts 1, 2, 4,=20
12, and 52 in accordance with 5 U.S.C. 610. Interested parties must=20
submit such comments separately and should cite 5 U.S.C 601, et seq.=20
(FAC 2005-25, FAR case 2004-038), in correspondence.

D. Paperwork Reduction Act

    The Paperwork Reduction Act does not apply because the changes to=20
the FAR do not impose information collection requirements that require=20
the approval of the Office of Management and Budget under 44 U.S.C.=20
3501, et seq.

E. Determination to Issue an Interim Rule

    A determination has been made under the authority of the Secretary=20
of Defense (DoD), the Administrator of General Services (GSA), and the=20
Administrator of the National Aeronautics and Space Administration=20
(NASA) that urgent and compelling reasons exist to promulgate this=20
interim rule without prior opportunity for public comment. This action=20
is necessary because the applicable procedures in the rule are=20
necessary to inform Federal agencies and the public when and how=20
Federal procurement data must be reported. The action is not expected=20
to have any impact on the vendor community. However, pursuant to Pub.=20
L. 98-577 and FAR 1.501, the Councils will consider public comments=20
received in response to this interim rule in the formation of the final=20

List of Subjects in 48 CFR Parts 1, 2, 4, 12, and 52

    Government procurement.

    Dated: April 4, 2008.
Al Matera,
Director, Office of Acquisition Policy.

Therefore, DoD, GSA, and NASA amend 48 CFR parts 1, 2, 4, 12, and 52 as=20
set forth below:
1. The authority citation for 48 CFR parts 1, 2, 4, 12, and 52=20
continues to read as follows:

    Authority: 40 U.S.C. 121(c); 10 U.S.C. chapter 137; and 42=20
U.S.C. 2473(c).


1.106  [Amended]

2. Amend section 1.106 in the table following the introductory=20
paragraph by removing FAR segments ``4.602'' and ``4.603'' and adding=20
``4.605'' and ``4.607'' in their place, respectively.


3. Amend section 2.101 in paragraph (b)(2) by adding, in alphabetical=20
order, the definition ``Chief Acquisition Officer''; and revising the=20
definition ``Data Universal Numbering System (DUNS) number'' to read as=20

2.101  Definitions.

* * * * *
    (b) * * *
    (2) * * *
* * * * *
    Chief Acquisition Officer means an executive level acquisition=20
official responsible for agency performance of acquisition activities=20
and acquisition programs created pursuant to the Services Acquisition=20
Reform Act of 2003, Section 1421 of Public Law 108-136.
* * * * *
    Data Universal Numbering System (DUNS) number means the 9-digit=20
number assigned by Dun and Bradstreet, Inc. (D&B), to identify =
business entities, which is used as the identification number for=20
Federal contractors.
* * * * *


4. Revise Subpart 4.6 to read as follows:

Subpart 4.6--Contract Reporting

4.600 Scope of subpart.
4.601 Definitions.
4.602 General.
4.603 Policy.
4.604 Responsibilities.
4.605 Procedures.
4.606 Reporting Data.
4.607 Solicitation Provisions.

4.600  Scope of subpart.

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

4.601  Definitions.

    As used in this subpart--
    Assisted acquisition means a contract, delivery or task order=20
awarded by a servicing agency on behalf of a requesting agency. The=20
agency providing the assistance may also administer the contract=20
    Contract action means any oral or written action that results in=20
the purchase, rent, or lease of supplies or equipment, services, or=20
construction using appropriated dollars over the micro-purchase=20
threshold, or modifications to these actions regardless of dollar=20
value. Contract action does not include grants, cooperative agreements,=20
other transactions, real property leases, requisitions from Federal=20
stock, training authorizations, or other non-FAR based transactions.
    Contract action report (CAR) means contract action data required to=20
be entered into the Federal Procurement Data System (FPDS).
    Definitive contract means any contract that must be reported to=20
FPDS other than an indefinite delivery vehicle. This definition is only=20
for FPDS, and is not intended to apply to Part 16.
    Direct acquisition means an order awarded directly by the=20
requesting agency against the servicing agency's contract. In a direct=20
acquisition, the servicing agency awards and administers the contract=20
but does not participate in the placement of an order.
    Entitlement program means a Federal program that guarantees a=20
certain level of benefits to persons or other entities who meet=20
requirements set by law, such as Social Security, farm price supports,=20
or unemployment benefits.
    Generic DUNS number means a DUNS number assigned to a category of=20
vendors not specific to any individual or entity.
    Indefinite delivery vehicle (IDV) means an indefinite delivery=20
contract that has one or more of the following clauses:
    (1) 52.216-18, Ordering.
    (2) 52.216-19, Order Limitations.
    (3) 52.216-20, Definite Quantity.
    (4) 52.216-21, Requirements.
    (5) 52.216-22, Indefinite Quantity.
    (6) Any other clause allowing ordering.
    Requesting agency means the agency that has the requirement for an=20
interagency acquisition.
    Servicing agency means the agency that will conduct an assisted=20
acquisition on behalf of the requesting agency.

[[Page 21777]]

4.602  General.

    (a) The FPDS provides a comprehensive web-based tool for agencies=20
to report contract actions. The resulting data provides--
    (1) A basis for recurring and special reports to the President, the=20
Congress, the Government Accountability Office, Federal executive=20
agencies, and the general public;
    (2) A means of measuring and assessing the effect of Federal=20
contracting on the Nation's economy and the extent to which small,=20
veteran-owned small, service-disabled veteran-owned small, HUBZone=20
small, small disadvantaged, women-owned small business concerns, and=20
nonprofit agencies operating under the Javits-Wagner-O'Day Act, are=20
sharing in Federal contracts; and
    (3) A means of measuring and assessing the effect of other policy=20
and management initiatives (e.g., performance based acquisitions and=20
    (b) FPDS does not provide reports for certain acquisition=20
information used in the award of a contract action (e.g.,=20
subcontracting data, funding data, or accounting data).
    (c) The FPDS Web site, http://frwebgat=
log&to=3D, provides instructions=20
for submitting data. It also provides--
    (1) A complete list of departments, agencies, and other entities=20
that submit data to the FPDS;
    (2) Technical and end-user guidance;
    (3) A computer-based tutorial; and
    (4) Information concerning reports not generated in FPDS.

4.603  Policy.

    (a) In accordance with the Federal Funding Accountability and=20
Transparency Act of 2006 (Pub. L. No. 109-282), all Federal award data=20
must be publicly accessible.
    (b) Except as provided in 4.606(a)(2), executive agencies shall use=20
FPDS to maintain publicly available information about all contract=20
actions exceeding the micro-purchase threshold, and any modifications=20
to those actions that change previously reported contract action report=20
data, regardless of dollar value.
    (c) Agencies awarding assisted acquisitions or direct acquisitions=20
must report these actions and identify the Funding Agency Code from the=20
applicable agency codes maintained by the National Institute of=20
Standards and Technology (NIST) using NIST Special Publication 800-87,=20
``Codes for the Identification of Federal and Federally Assisted=20
Organizations,'' at
    (d) Agencies exempt from the FAR are encouraged to report contract=20
actions in FPDS.
    (e) Agencies awarding contract actions with a mix of appropriated=20
and nonappropriated funding shall only report the full appropriated=20
portion of the contract action in FPDS.

4.604  Responsibilities.

    (a) The Senior Procurement Executive in coordination with the head=20
of the contracting activity is responsible for developing and=20
monitoring a process to ensure timely and accurate reporting of=20
contractual actions to FPDS.
    (b)(1) The responsibility for the submission and accuracy of the=20
individual contract action report (CAR) resides with the contracting=20
officer who awarded the contract action.
    (2) When a contract writing system is integrated with FPDS, the CAR=20
must be confirmed for accuracy prior to release of the contract award.
    (3) When a contract writing system is not integrated with FPDS, the=20
CAR must be submitted to FPDS within three business days after contract=20
    (4) For any action awarded in accordance with FAR 6.302-2 or=20
pursuant to any of the authorities listed at FAR Subpart 18.2, the CAR=20
must be submitted to FPDS within 30 days after contract award.
    (5) When the contracting office receives written notification that=20
a contractor has changed its size status in accordance with the clause=20
at 52.219-28, Post-Award Small Business Program Rerepresentation, the=20
contracting officer must submit a modification contract action report=20
to ensure that the updated size status is entered in FPDS-NG.
    (c) The chief acquisition officer of each agency required to report=20
its contract actions must submit to the General Services Administration=20
(GSA), in accordance with FPDS guidance, by January 5, an annual=20
certification of whether, and to what degree, agency CAR data for the=20
preceding fiscal year is complete and accurate.

4.605  Procedures.

    (a) Procurement Instrument Identifier (PIID). Agencies must have in=20
place a process that ensures that each PIID reported to FPDS is unique,=20
Governmentwide, and will remain so for at least 20 years from the date=20
of contract award. Agencies must submit their proposed identifier=20
format to the FPDS Program Management Office, which maintains a=20
registry of the agency unique identifiers on the FPDS website, and must=20
validate their use in all transactions. The PIID shall consist of alpha=20
characters in the first positions to indicate the agency, followed by=20
alphanumeric characters identifying bureaus, offices, or other=20
administrative subdivisions. Other pertinent PIID instructions can be=20
found at http://frwebgat=
    (b) Data Universal Numbering System (DUNS). The contracting officer=20
must identify and report a DUNS number (Contractor Identification=20
Number) for the successful offeror on a contract action. The DUNS=20
number reported must identify the successful offeror's name and address=20
as stated in the offer and resultant contract, and as registered in the=20
Central Contractor Registration (CCR) database in accordance with the=20
clause at 52.204-7, Central Contractor Registration. The contracting=20
officer must ask the offeror to provide its DUNS number by using either=20
the provision at 52.204-6, Data Universal Numbering System (DUNS)=20
Number, the clause at 52.204-7, Central Contractor Registration, or the=20
provision at 52.212-1, Instructions to Offerors--Commercial Items.
    (1) Notwithstanding the inclusion of the provision at 52.204-6 in=20
the associated solicitation or except as provided in paragraph (b)(2)=20
of this section, the contracting officer shall use one of the generic=20
DUNS numbers identified in CCR to report corresponding contract actions=20
if the contract action is--
    (i) With contractors located outside the United States and its=20
outlying areas as defined in 2.101 who do not have a DUNS number, and=20
the contracting officer determines it is impractical to obtain a DUNS=20
    (ii) With students who do not have DUNS numbers;
    (iii) With dependents of veterans, Foreign Service Officers, and=20
military members assigned overseas who do not have DUNS numbers; or
    (iv) For classified or national security.
    (2) In accordance with agency procedures, authorized generic DUNS=20
numbers found at http://frwebgat=
log&to=3D may be used to report contract=20
actions when--
    (i) Specific public identification of the contracted party could=20
endanger the mission, contractor, or recipients of the acquired goods=20
or services; or
    (ii) The agency determines it is impractical to obtain a DUNS=20

4.606  Reporting Data.

    (a) Actions required to be reported to FPDS. (1) As a minimum,=20
agencies must report the following contract actions over the micro-
purchase threshold, regardless of solicitation process used, and=20
agencies must report any modification to these contract actions

[[Page 21778]]

that change previously reported contract action data, regardless of=20
dollar value:
    (i) Definitive contracts, including purchase orders and imprest=20
fund buys over the micro-purchase threshold awarded by a contracting=20
    (ii) Indefinite delivery vehicle (identified as an ``IDV'' in=20
FPDS). Examples of IDVs include the following:
    (A) Task and Delivery Order Contracts (see Subpart 16.5),=20
    (1) Government-wide acquisition contracts.
    (2) Multi-agency contracts.
    (B) GSA Federal supply schedules.
    (C) Blanket Purchase Agreements (see 13.303).
    (D) Basic Ordering Agreements (see 16.703).
    (E) Any other agreement or contract against which individual orders=20
or purchases may be placed.
    (iii) All calls and orders awarded under the indefinite delivery=20
vehicles identified in paragraph (a)(1)(ii) of this section.
    (2) Agencies participating in the Small Business Competitiveness=20
Demonstration Program (see Subpart 19.10) shall report as a contract=20
action each award in the designated industry groups, regardless of=20
dollar value.
    (3) The GSA Office of Charge Card Management will provide the=20
Government purchase card data, at a minimum annually, and GSA will=20
incorporate that data into FPDS for reports.
    (4) Agencies may use the FPDS Express Reporting capability for=20
consolidated multiple action reports for a vendor when it would be=20
overly burdensome to report each action individually. When used,=20
Express Reporting should be done at least monthly.
    (b) Reporting Other Actions. Agencies may submit actions other than=20
those listed at paragraph (a)(1) of this section, and must contact the=20
FPDS Program Office at integrated.acquisition@gsa=
.gov if they desire to=20
submit any of the following types of activity:
    (1) Transactions at or below the micro-purchase threshold, except=20
as provided in paragraph (a)(2) of this section.
    (2) Any non-appropriated fund (NAF) or NAF portion of a contract=20
action using a mix of appropriated and nonappropriated funding.
    (3) Lease and supplemental lease agreements for real property.
    (4) Resale activity (i.e., commissary or exchange activity).
    (5) Revenue generating arrangements (i.e., concessions).
    (6) Training expenditures not issued as orders or contracts.
    (7) Grants and entitlement actions.
    (8) Interagency agreements, also known as interservice level=20
agreements, memoranda of understanding, or memoranda of agreement.
    (9) Letters of obligation used in the A-76 process.
    (c) Actions not reported. The following types of contract actions=20
are not to be reported to FPDS:
    (1) Imprest fund transactions below the micro-purchase threshold,=20
including those made via the Government purchase card (unless specific=20
agency procedures prescribe reporting these actions).
    (2) Orders from GSA stock and the GSA Global Supply Program.
    (3) Purchases made at GSA or JWOD service stores, as these items=20
stocked for resale have already been reported by GSA.
    (4) Purchases made using non-appropriated fund activity cards,=20
chaplain fund cards, individual Government personnel training orders,=20
and Defense Printing orders.
    (d) Agencies not subject to the FAR may be required by other=20
authority (e.g., statute or OMB) to report certain information to FPDS.

4.607  Solicitation Provisions.

    (a) Insert the provision at 52.204-6, Data Universal Numbering=20
System (DUNS) Number, in solicitations that--
    (1) Are expected to result in a requirement for the generation of a=20
CAR (see 4.606(a)(1)); and
    (2) Do not contain the clause at 52.204-7, Central Contractor=20
    (b) Insert the provision at 52.204-5, Women-Owned Business (Other=20
Than Small Business), in all 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=20
or its outlying areas.

4.805  [Amended]

5. Amend section 4.805 in paragraph (b)(9) by removing ``4.601'' and=20
adding ``4.603'' in its place.


12.301  [Amended]

6. Amend section 12.301 in paragraph (b)(2) by removing the words=20
``that are expected to exceed the threshold at 4.601(a)''.


52.204-5  [Amended]

7. Amend section 52.204-5 by removing from the introductory text=20
``4.603(b)'' and adding ``4.607(b)'' in its place.
8. Amend section 52.204-6 by--
a. Removing from the introductory text ``4.603(a)'' and adding=20
``4.607(a)'' in its place;
b. Revising the date of the provision;
c. Removing from paragraph (a) the word ``parent'';
d. Revising paragraph (b)(1)(i); and
e. Adding a sentence to the end of paragraph (b)(1)(ii).
    The revised and added text reads as follows:

52.204-6  Data Universal Numbering System (DUNS) Number.

* * * * *
* * * * *
    (b) * * *
    (1) * * *
    (i) Via the Internet at http:/=
og=3Dlinklog&to=3D or if the=20
offeror does not have internet access, it may call Dun and=20
Bradstreet at 1-866-705-5711 if located within the United States; or
    (ii) * * * The offeror should indicate that it is an offeror for=20
a U.S. Government contract when contacting the local Dun and=20
Bradstreet office.
* * * * *
    (End of provision)
9. Amend section 52.204-7 by--
a. Revising the date of the clause;
b. In paragraph (a), in the definition ``Data Universal Numbering=20
System +4 (DUNS+4) number'', by removing the word ``parent'';
c. Revising paragraph (c)(1)(i); and
d. Adding a sentence to the end of paragraph (c)(1)(ii).
    The revised and added text reads as follows:

52.204-7  Central Contractor Registration.

* * * * *
* * * * *
    (c) * * *
    (1) * * *
    (i) Via the Internet at http:/=
og=3Dlinklog&to=3D or if the=20
offeror does not have internet access, it may call Dun and=20
Bradstreet at 1-866-705-5711 if located within the United States; or
    (ii) * * * The offeror should indicate that it is an offeror for=20
a U.S. Government contract when contacting the local Dun and=20
Bradstreet office.
* * * * *
    (End of clause)
10. Amend section 52.212-1 by--

[[Page 21779]]

a. Revising the date of the provision; and
b. In paragraph (j), by removing the word ``parent''; removing ``http://frwebgate.=
g&to=3D'' and adding ``http:/=
og=3Dlinklog&to=3D'' in its=20
place; and adding a sentence to the end of the paragraph to read as=20

52.212-1  Instructions to Offerors--Commercial Items.

* * * * *
* * * * *
    (j) * * * The offeror should indicate that it is an offeror for=20
a Government contract when contacting the local Dun and Bradstreet=20
* * * * *
    (End of provision)
[FR Doc. E8-8447 Filed 4-21-08; 8:45 am]