# 504.606 Reporting Data.

1. (a) Reporting requirements. Detailed specification of FPDS data reporting requirements is contained in the FPDS-NG FAQs document (available at https://www.fpds.gov/wiki/index2.php/FPDS-NG_FAQ). Reporting offices are encouraged to use automated information systems for FPDS data reporting, provided that the systems contain all required FPDS data elements via the machine-to-machine process and the automated acquisition system has received the proper certification from the FPDS system manager.

2. (b) The GSA FPDS Sustainability Coding Guidelines at http://insite.gsa.gov/sustainableacquisition must be followed when selecting codes for the following sustainability data elements:

   1. (1) Recovered Materials/Sustainability.

   2. (2) Use of EPA Designated Products.

3. (c) FPDS reporting for acquisitions supporting customer agencies.

   1. (1) GSA-funded acquisitions. There are instances where GSA conducts an acquisition in support of a customer agency but also provides the predominance of funding for the contract award. In these instances, GSA’s Activity Address Codes (AACs) must be used for the contracting agency codes (e.g. Contracting Office ID) and funding agency codes (e.g. Funding Office ID) in FPDS. Examples of GSA funded acquisitions may include those made in support of—

      1. (i) Requisitions. These transactions are transfers of property conducted in accordance with the Federal Property Management Regulation (FPMR) (41 CFR 101-26). Examples of programs that facilitate requisitions from customer agencies include GSA stock supply programs and GSA motor vehicle purchasing. Customer agencies submit requisitions (sometimes referred to as “orders”) to GSA for items under these programs in accordance with the FPMR. GSA then acquires these items from suppliers through contracts or orders in accordance with the FAR and GSAM.

      2. (ii) Shared Services. Under this model, common administrative services-those activities that are common across all agencies-are conducted by an agency (e.g. shared service provider) with expertise in a particular area to reduce duplication and redundancy. In turn, the customer agency reimburses the shared service provider for its costs. Often, shared service providers must conduct acquisitions in order to provide services to other agencies. Accordingly, only the contract/order awarded by the shared service provider to a contractor is reported in FPDS.

   2. (2) Customer-funded acquisitions. There are instances where GSA conducts an acquisition in support of a customer agency but the customer agency provides the predominance of funding for the contract action. In these instances, GSA’s AACs must be used for the contracting agency codes (e.g. Contracting Office ID) but the customer agency's AACs must be used for funding agency codes (e.g. Funding Office ID) in FPDS. Examples of customer-funded acquisitions may include—

      1. (i) Reimbursable Work Authorizations (RWAs). An RWA is an interagency agreement between GSA and a tenant (e.g. federal agency or non-federal source when authorized by statute) whereby GSA recovers its costs for altering, renovating, repairing, or providing services in GSA-managed space over and above the basic operations financed through rent paid by the tenant.

      2. (ii) Assisted acquisitions (see definition at FAR 2.101). GSA regularly acts as the servicing agency in this type of interagency acquisition, where it performs acquisition activities on a customer (requesting) agency's behalf, such as awarding and administering a contract, while the requesting agency provides the required funding.

4. (d) Inherently Governmental Functions. If the procurement is for services, enter the appropriate indicator in the Inherently Governmental Functions field:

   1. (1) “Closely Associated” means functions that are closely associated with inherently governmental functions; those contractor duties that could expand to become inherently governmental functions without sufficient management controls or oversight on the part of the Government. Office of Federal Procurement Policy (OFPP) Policy Letter 11–01, Performance of Inherently Governmental and Critical Functions, provides examples of work that is inherently governmental and therefore must be performed by Federal employees and work that is closely associated with inherently governmental functions that may be performed by either Federal employees or contractors.

   2. (2) “Critical Functions” means functions that are necessary to the agency being able to effectively perform and maintain control of its mission and operations. Typically, critical functions are recurring and long-term in duration.

   3. (3) “Other Functions” means neither “Closely Associated Functions” nor “Critical Functions.”

   4. (4) For services that include performing both “Closely Associated” and “Critical Functions,” select “Closely Associated, Critical Functions.”