48 C.F.R. §§ 52.204-16

Current through October 31, 2024
Section 52.204-16 - Commercial and Government Entity Code Reporting

As prescribed in 4.1804(a), use the following provision:

Commercial and Government Entity Code Reporting (AUG 2020)

(a)Definition. As used in this provision-

Commercial and Government Entity (CAGE) code means-

(1) An identifier assigned to entities located in the United States or its outlying areas by the Defense Logistics Agency (DLA) Commercial and Government Entity (CAGE) Branch to identify a commercial or government entity by unique location; or
(2) An identifier assigned by a member of the North Atlantic Treaty Organization (NATO) or by the NATO Support and Procurement Agency (NSPA) to entities located outside the United States and its outlying areas that the DLA Commercial and Government Entity (CAGE) Branch records and maintains in the CAGE master file. This type of code is known as a NATO CAGE (NCAGE) code.
(b) The Offeror shall provide its CAGE code with its offer with its name and location address or otherwise include it prominently in its proposal. The CAGE code must be for that name and location address. Insert the word "CAGE" before the number. The CAGE code is required prior to award.
(c) CAGE codes may be obtained via-
(1) Registration in the System for Award Management (SAM) at www.sam.gov. If the Offeror is located in the United States or its outlying areas and does not already have a CAGE code assigned, the DLA Commercial and Government Entity (CAGE) Branch will assign a CAGE code as a part of the SAM registration process. SAM registrants located outside the United States and its outlying areas shall obtain a NCAGE code prior to registration in SAM (see paragraph (c)(3) of this provision).
(2) The DLA Commercial and Government Entity (CAGE) Branch. If registration in SAM is not required for the subject procurement, and the Offeror does not otherwise register in SAM, an Offeror located in the United States or its outlying areas may request that a CAGE code be assigned by submitting a request at https://cage.dla.mil.
(3) The appropriate country codification bureau. Entities located outside the United States and its outlying areas may obtain an NCAGE code by contacting the Codification Bureau in the foreign entity's country if that country is a member of NATO or a sponsored nation. NCAGE codes may be obtained from the NSPA at https://eportal.nspa.nato.int/AC135Public/scage/CageList.aspx if the foreign entity's country is not a member of NATO or a sponsored nation. Points of contact for codification bureaus, as well as additional information on obtaining NCAGE codes, are available at http://www.nato.int/structur/AC/135/main/links/contacts.htm.
(d) Additional guidance for establishing and maintaining CAGE codes is available at https://cage.dla.mil.
(e) When a CAGE code is required for the immediate owner and/or the highest-level owner by Federal Acquisition Regulation (FAR) 52.204-17 or 52.212-3(p), the Offeror shall obtain the respective CAGE code from that entity to supply the CAGE code to the Government.
(f) Do not delay submission of the offer pending receipt of a CAGE code.
(g) If the solicitation includes FAR clause 52.204-2, Security Requirements, a subcontractor requiring access to classified information under a contract shall be identified with a CAGE code on the DD Form 254. The Contractor shall require a subcontractor requiring access to classified information to provide its CAGE code with its name and location address or otherwise include it prominently in the proposal. Each location of subcontractor performance listed on the DD Form 254 is required to reflect a corresponding unique CAGE code for each listed location unless the work is being performed at a Government facility, in which case the agency location code shall be used. The CAGE code must be for that name and location address. Insert the word "CAGE" before the number. The CAGE code is required prior to award.

(End of provision)

48 C.F.R. §§52.204-16

79 FR 31191 , May 30, 2014, as amended at 80 FR 38312 , July 2, 2015; 81 FR 45867 , July 14, 2016; 85 FR 40063 , July 2, 2020
81 FR 45867 , 7/14/2016; 85 FR 40063 , 8/3/2020