Source: http://farsite.hill.af.mil/reghtml/changes/dac/DCN19990809.htm
Timestamp: 2017-10-17 05:55:58
Document Index: 303716565

Matched Legal Cases: ['art 217', 'art 3', 'arts 204', 'art 204', 'art 204', 'arts 204', 'arts 204', 'ART 204', 'ART 204', 'ART 213', 'art 204', 'art 204', 'art 204', 'art 4', 'art 42', 'art 42', 'art 42', 'ART 213']

DCN19990809
DFARS CHANGE NOTICE 19990809
[DFARS Case 97-D308]
SUMMARY: The Director of Defense Procurement has issued a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to update guidance pertaining to multiyear contracting. The rule contains statutory requirements related to the award of multiyear
contracts for supplies, services, and weapon systems.
EFFECTIVE DATE: August 9, 1999.
Regulations Council, PDUSD (A&T) DP (DAR), IMD 3D139, 3062 Defense Pentagon, Washington, DC 20301-3062. Telephone (703) 602-4245; telefax (703) 602-0350. Please cite DFARS Case 97-D308.
This final rule amends DFARS Subpart 217.1 to update guidance pertaining to the award of multiyear contracts. The rule adds requirements to reflect the provisions of 10 U.S.C. 2306(g)(2)(B), 10 U.S.C. 2306b(i)(3), and Section 8008(b) of Public Law 105-56; updates
other statutory references throughout the subpart; and makes editorial revisions for clarity. In addition, the rule adds a definition of ``Congressional defense committees'' at DFARS 202.101
This final rule does not constitute a significant revision within the meaning of FAR 1.501 and Public Law 98-577 and publication for public comment is not required. However, comments from small entities concerning the affected DFARS subparts will be considered in accordance with 5 U.S.C. 610. Such comments should cite DFARS Case 97-D308.
Government procurement. Michele P. Peterson, Executive Director, Defense Acquisition Regulations Council.
DFARS Case 97-D308
["Congressional defense committees" means-
(4) The Subcommittee on Defense of the Committee on Appropriations of the House of Representatives.]
217.170 All multiyear contracts [General].
(a) Before a multiyear contract is awarded, the cost of that contract shall be compared [Before awarding a multiyear contract, the head of the agency must compare the cost of that contract] against [to] the cost of an annual procurement approach, using a present value analysis. The multiyear contract shall not be awarded [Do not award the multiyear contract] unless the analysis shows that it [the multiyear contract will] results in the lowest [lower] cost (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense Appropriations Acts [10 U.S.C. 2306b(l)(5)]).
(b) The head of the agency shall [must] provide written notice to the Committees on Appropriations and National Security in the House of Representatives and in the Senate [congressional defense committees] at least 10 days before termination of any multiyear contract (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense appropriations acts [10 U.S.C. 2306b(l)(4)]).
(c) The Secretary of Defense may instruct the head of the agency proposing a multiyear contract to include in that contract negotiated priced options for varying the quantities of end items to be procured over the life of the contract (10 U.S.C. 2306b(j)).
(d) Every multiyear contract must comply with FAR 17.104(c), unless an exception is approved through the budget process in coordination with the cognizant comptroller.
[(e)(1) DoD must receive authorization from, or provide notification to, Congress before entering into a multiyear contract for certain procurements, including those expected to-
(i) Exceed $500 million for any particular system or system component (see 217.173(b)(4));
(iii) Employ an unfunded contingent liability in excess of $20 million (see 217.172(c)); or
(iv) Involve a contract for advance procurement leading to a multiyear contract that employs economic order quantity procurement in excess of $20 million in any one year (see 217.174(a)(2)).
(2) A DoD component must submit a request for authority to enter into such multiyear contracts as part of the component's budget submission for the fiscal year in which the multiyear contract will be initiated. DoD will include the request, for each candidate it supports, as part of the President's Budget for that year and in the Appendix to that budget as part of proposed legislative language for the appropriations bill for that year (Section 8008(b) of Pub. L. 105-56).
(3) If the advisability of using a multiyear contract becomes apparent too late to satisfy the requirements in paragraph (e)(2) of this section, the request for authority to enter into a multiyear contract must be-
(ii) Made by the Secretary of Defense, in writing, to the congressional defense committees (Section 8008(b) of Pub. L. 105-56).]
(a) 10 U.S.C. 2306(g).
(1) DoD [The head of the agency] may enter into multiyear acquisitions [contracts] for the following [types of] services (and items of supply relating to such services), even though funds are limited by statute to obligation only during the fiscal year for which they were appropriated:
(iii) Specialized training requiring high quality instructor skills (e.g., training for pilots and other aircrew members or foreign language training).
(2) [The head of the agency may use t]This authority may be used as long as the contract does not extend beyond 5 years [only if the term of the contract does not exceed 5 years. However, the head of the agency may extend the term of the contract by exercising an option that does not-
(i) Exceed 3 years; or
(ii) Include charges for plant, equipment, or other nonrecurring costs already amortized].
[(3) Before entering into a multiyear contract for services, the head of the agency must make a written determination that-
(i) There will be a continuing need for the services and incidental supplies consistent with current plans for the proposed contract period;
(ii) Furnishing the services and incidental supplies will require-
(iii) Using a multiyear contract will be in the best interest of the United States by encouraging effective competition and promoting economical business operations (e.g., economic lot purchases and more efficient production rates).]
(2) [The head of the agency may use t]This authority may be used as long as [only if the term of] the contract does not extend beyond [exceed] 4 years.
(c) Award of a multiyear contract for services requires a written determination by the head of the agency (10 U.S.C. 2306(g)(1)) that-
(1) There will be a continuing need for the services and incidental supplies;
(2) Furnishing the services and incidental supplies will require-
(3) Using a multiyear contract will be in the best interest of the United States by encouraging effective competition and promoting economical business operations (e.g., economic lot purchases and more efficient production rates).
(b) [The head of the agency may enter into a] A multiyear contract for supplies may be used if, in addition to the conditions listed in FAR 17.105-1(b), the use of such a contract will promote the national security of the United States.
(c) The head of the agency shall [must] provide written notice to the Committees on Appropriations and National Security in the House of Representatives and in the Senate [congressional defense committees] at least 30 days before the contracting officer awards a multiyear contract including an unfunded contingent liability in excess of $20 million (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense appropriations acts [10 U.S.C. 2306b(l)(1)(A)]).
(d) Agencies shall [must] establish reporting procedures to meet the requirements of paragraph (c) of this section. [The head of the agency must] S[s]ubmit copies of the notifications to the Director of Defense Procurement, Office of the Under Secretary of Defense (Acquisition and Technology) (OUSD(A&T)DP), and to the Deputy Under Secretary of Defense (Comptroller) (Program/Budget) (OUSD(C)(P/B)).
(a) As authorized by 10 U.S.C. 2306b(a[h]) and subject to the conditions in paragraph (b) of this section, the head of the agency may enter into a multiyear contract for-
(b) The following conditions must be satisfied before a multiyear contract may be awarded [The head of the agency must ensure that the following conditions are satisfied before awarding a multiyear contract] under the authority described in paragraph (a) of this section:
(2) The Secretary of Defense certifies to Congress that the current 5-year defense program fully funds the support costs associated with the multiyear program (10 U.S.C. 2306b(i)(1)(A)). [The head of the agency must submit] I[i]nformation supporting this certification shall be submitted to USD(C)(P/B) for transmission to Congress through the Secretary of Defense.
(3) The proposed multiyear contract provides for production at not less than minimum economic rates, given the existing tooling and facilities (10 U.S.C. 2306b(i)(1)(B)). [The head of the agency must submit to USD(C)(P/B)] I[i]nformation supporting the agency's determination that this requirement has been met shall be submitted to USD(C)(P/B), with the information supporting the certification required by paragraph (b)(2) of this section.
(4) If the value of the [a] multiyear contract [for a particular system or component] exceeds $500,000,000 [million], the applicable Defense appropriations act specifically provides that a multiyear contract may be used to procure the particular system or system component (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense appropriations acts) [use of a multiyear contract is specifically authorized by-
(ii) A law other than an appropriations act
(10 U.S.C. 2306b(i)(3)).]
(5) All other requirements of law are met and there are no other statutory restrictions on using a multiyear contract for the specific system or component (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense appropriations acts) [(10 U.S.C. 2306b(i)(2))]. One such restriction may be the achievement of specified cost savings. If the agency finds, after negotiations with the contractor(s), that the specified savings cannot be achieved, the head of the agency shall [must] assess the savings that, nevertheless, could be achieved by using a multiyear contract. If the savings are substantial, the head of the agency may request relief from the law's specific savings requirement. The request shall [must]-
(iv) Be submitted to OUSD(A&T)DP for transmission to Congress via the Secretary of Defense and the President (10 U.S.C. 2306b(i)(2)).
(a) The head of the agency shall [must] provide written notice to the Committees on Appropriations and National Security in the House of Representatives and in the Senate [congressional defense committees] at least 30 days before awarding-
(1) A multiyear contract providing for economic order quantity purchases [procurement] in excess of $20 million in any [one] year; or
(2) A contract for advance procurement leading to a multiyear contract that employs economic order quantity procurement in excess of $20 million in any [one] year (Section 9021 of Pub. L. 101-165 and similar sections in subsequent Defense appropriations acts [10 U.S.C. 2306b(l)(1)(A)]).
(b) Before initiating an advance procurement, the contracting officer shall [must] verify that it is consistent with DoD policy (e.g., Part 3 of DoD 5000.2-R, Mandatory Procedures for Major Defense Acquisition Programs (MDAPs) and Major Automated Information System (MAIS) Acquisition Programs, and the full funding policy in Volume 2A, Chapter 1, of DoD 7000.14-R, Financial Management Regulation).
48 CFR Parts 204, 212, 213, 252, and 253
[DFARS Case 98-D027]
Defense Federal Acquisition Regulation Supplement; TaxpayerIdentification Numbers and Commercial and Government Entity Codes
SUMMARY: The Director of Defense Procurement has issued a final rule amending the Defense Federal Acquisition Regulation Supplement (DFARS) to add procedures for reporting payment information to the Internal Revenue Service (IRS); to revise the procedures for obtaining Taxpayer
Identification Numbers (TINs) and Commercial and Government Entity (CAGE) codes when contractors are required to register in the Central Contractor Registration (CCR) database; and to make editorial changes.
Ms. Sandra G. Haberlin, Defense Acquisition Regulations Council, PDUSD (A&T) DP (DAR), IMD 3D139, 3062 Defense Pentagon, Washington, DC 20301-3062. Telephone (703) 602-0289; telefax (703) 602-0350. Please cite DFARS Case 98-D027.
1. Reporting payment information to the IRS. This rule supplements the final FAR rule published as Item I of Federal Acquisition Circular 97-12 on June 17, 1999 (64 FR 32741).
a. The FAR rule renumbered and retitled FAR 4.903, Payment information, as FAR 4.904, Reporting payment information to the IRS; and deleted the list, previously located at FAR 4.903(b), of the types of payments that are exempt from reporting payment information to the IRS on Form 1099. The list was considered unnecessary for including in the FAR, because the payment office is responsible for submitting Form 1099 reports to the IRS.
b. This rule adds a new section at DFARS 204.904, Reporting payment information to the IRS. The new section contains a list that is similar to the one previously found in the FAR, but the list has been updated to comply with the Taxpayer Relief Act of 1997 (Pub. L. 105-32). Section 1022 of the Act amended 26 U.S.C. 6041A to add payments under certain classified contracts to the list of exceptions, and to remove payments for services provided by corporations from the list. DFARS
204.904 also adds a requirement for the contracting officer to provide a statement to the payment office if the contractor is providing services subject to Form 1099 reporting to the IRS. The statement is not required if the contracting officer concludes that one of the exceptions listed at DFARS 204.904(1) applies. This procedure is added to the DFARS to facilitate issuance of Form 1099 reports by the payment office.
2. Procedures for obtaining TINs and CAGE code numbers when CCR applies. The FAR rule also modified the process for obtaining TINs, by permitting agencies to prescribe their own procedures for obtaining TINs from contractors and for providing the TINs to the payment office.
DoD uses the CCR database for these purposes. This DFARS rule clarifies that the contracting officer must not use the solicitation provisions at FAR 52.204-3, Taxpayer Identification, and DFARS 252.204-7001, Commercial and Government Entity (CAGE) Code Reporting; or paragraph
(b) of the provision at FAR 52.212-3, Offeror Representations and Certifications--Commercial Items, when the contractor is required to register in the CCR database, since the information that these provisions request is duplicative of the information that the contractor must provide during the CCR process.
3. Editorial changes. This DFARS rule makes a number of editorial changes, including updating CAGE code information in Subpart 204.72, Contractor Identification, and clarifying certain requirements in Subpart 204.73, Central Contractor Registration.
4. Proposed rule. A proposed DFARS rule was published in the Federal Register on January 15, 1999 (64 FR 2617). Three sources submitted comments on the proposed rule. All comments were considered in the development of the final rule.
5. This rule was not subject to Office of Management and Budget review under Executive Order 12866, dated September 30, 1993.
DoD certifies that this final rule will not have a significant economic impact on a substantial number of small entities within the meaning of the Regulatory Flexibility Act, 5 U.S.C. 601, et seq., because the FAR and DFARS already contain requirements for offerors and contractors to provide TINs and CAGE codes and to register in the CCR database. This rule simply clarifies that, if a prospective contractor is required to register in the CCR database, it does not have to
provide a TIN or a CAGE code to the contracting officer.
The Paperwork Reduction Act (44 U.S.C. 3501, et seq.) applies because the rule contains information collection requirements. The final rule decreases the collection requirements currently approved under Office of Management and Budget Control Number 0704-0225, since the rule limits use of the solicitation provision at 252.204-7001, Commercial and Government Entity (CAGE) Code Reporting, to contractors that are not required to register in the CCR database. Therefore, the final rule reduces the number of respondents by 89,545, and the number of burden hours by 22,386.
List of Subjects in 48 CFR Parts 204, 212, 213, 252, and 253
Therefore, 48 CFR parts 204, 212, 213, 252, and 253 are amended as follows:
Taxpayer Identification Numbers and Commercial
and Government Entity Codes
Additions to the DFARS are indicated in [bold and brackets]. Deletions are indicated by strikethroughs.
[204.203 Taxpayer identification information.]
204.602-70 Solicitation provision.
[204.603 Solicitation provisions.]
SUBPART 204.9-INFORMATION REPORTING TO THE INTERNAL REVENUE SERVICE [TAXPAYER IDENTIFICATION NUMBER INFORMATION]
[204.904 Reporting payment information to the IRS.
204.905 Solicitation provision.]
SUBPART 204.72-CONTRACTOR IDENTIFICATION
204.7202-3 Contractor identification numbers [TINs].
[SUBPART 213.1-PROCEDURES]
213.106-3 Award and documentation.]
[204.203 Taxpayer identification information.
(2) For a DoD basic ordering agreement or indefinite-delivery contract that requires the contractor to register in the Central Contractor Registration (CCR) database (see Subpart 204.73)--
(ii) If the contractor is not registered, the contracting officer must follow the procedures at 204.7303(b).]
When the Commercial and Government Entity codes for the prospective offerors are not available to the contracting office, use the provision at 252.204-7001, Commercial and Government Entity (CAGE) Code Reporting.
[204.603 Solicitation provisions.
(1) Use the provision at 252.204-7001, Commercial and Government Entity (CAGE) Code Reporting, in solicitations when-
(i) The solicitation does not include the clause at 252.204-7004, Required Central Contractor Registration; and
(ii) The CAGE codes for the potential offerors are not available to the contracting office.
(2) Use the provision at FAR 52.204-6, Data Universal Numbering System (DUNS) Number, in solicitations that-
(i) Have an estimated value exceeding $25,000; or
(ii) Have an estimated value of $25,000 or less and include the clause at 252.204-7004, Required Central Contractor Registration.]
(b) DoD uses the DD Form 350, Individual Contract[ing] Action Report, (see 204.670) to meet these reporting requirements.
(1) 26 U.S.C. 6041 and 6041A and 26 CFR 1.6041 require Government payors to report to the IRS, on IRS Form 1099, payments of an annual cumulative value of $600 or more provided to a contractor, except payments for-
(i) Supplies, unless the supplies are incidental to the furnishing of services;
(ii) Telegram, telephone, freight, storage, or similar charges;
(iii) Income that the payor must report on IRS Form W-2 (e.g., payments to employees or payments under contracts for personal services);
(iv) Any contract with a Federal agency;
(v) Any contract with a State, the District of Columbia, or a possession of the United States; or a political subdivision, agency, or instrumentality of any of the foregoing;
(vi) Any contract with an organization exempted from taxation by 26 U.S.C. 501(a). Such organizations may include charitable, social welfare, labor, agricultural, veterans', and political organizations; business leagues; social clubs; fraternal societies; and employees' associations. Contracting officers may obtain additional information to assist in determining an organization's tax-exempt status via the Internet at http://www.irs.ustreas.gov/prod/bus_info/eo/eo-types.html;
(vii) Any contract with a foreign government or a political subdivision of a foreign government;
(viii) Any contract with an international organization listed in 22 U.S.C. 288;
(ix) Any classified contract excepted by 26 U.S.C. 6050M. As used in this section only, a contract is classified if-
(A) DoD designates the existence of the contract or the contract subject matter as classified (i.e., the contract requires a specific degree of protection against unauthorized disclosure for reasons of national security); or
(B) The head of the agency determines that filing IRS Form 1099 would interfere with the effective conduct of a confidential law enforcement or foreign intelligence activity; or
(x) Such other services as the IRS may specify in regulations.
(2) Unless an exception in paragraph (1) of this section applies, the contracting officer must provide, as the last page of the copy of the contract sent to the payment office-
(i) A statement that the contractor is providing services subject to Form 1099 payment information reporting to the IRS, as required by 26 U.S.C. 6041 and 6041A; and
(ii) The contractor's Taxpayer Identification Number and type of organization, if the contract does not include the clause at 252.204-7004, Required Central Contractor Registration.
204.905 Solicitation provision.
Do not use the provision at FAR 52.204-3, Taxpayer Identification, in solicitations that include the clause at 252.204-7004, Required Central Contractor Registration.]
This subpart prescribes uniform policies and procedures for identification of commercial and Government entities when it is necessary to:[--]
(a) Exchange data with another contracting activity, including contract administration activities and contract payment activities, or to comply with the reporting requirements of Subpart 204.6; or
(b) Identify contractors for the purposes of developing computerized acquisition systems or solicitation mailing lists.
204.7201 Definitions.
(a) "Commercial and Government e[E]ntity (CAGE) code" means-
(1) A code assigned by the Defense Logistics [Information] Services Center (DL[I]SC) to identify a commercial or Government entity; or
(2) A code assigned by a member of the North Atlantic Treaty Organization (NATO) and maintained by the Defense Logistics Services Center. [that DLIS records and maintains in the CAGE master file. This type of code is known as an "NCAGE code."]
(b) "Contractor identification code" means any code required by [that] the contracting office for the purpose of [uses to] identifying the [an] offeror. [The three types of contractor identification codes are] CAGE codes[,] and Data Universal Numbering System (DUNS) numbers[, and Taxpayer Identification Numbers (TINs).] are two examples of contractor identification codes.
204.7202 General.
Various coding systems are in use to identify commercial and government entities. Codes are requested by contracting and contract administration offices for various reasons. This guidance is designed to improve the accuracy of the initial code assignment and to help ensure that the data are maintained accurately and are up-to-date.
(a) [DLIS assigns or] CAGE codes are [records] assigned [and] or maintain[s CAGE codes]ed by the Defense Logistics Services Center (DLSC) to identify commercial and Government activities[entities]. Their use is prescribed by 253.204-70(b)(5)(ii)(C) and DoD 4000.25-5-M, Military Standard Contract Administration Procedures (MILSCAP)[; Volume 7 of DoD 4100.39-M, Federal Logistics Information System (FLIS) Procedures Manual; and 253.204-70(b)(5)(ii)(C) prescribe use of CAGE codes].
(b) CAGE codes have also been known in the past as federal supply codes for manufacturers (FSCM) and federal supply codes for nonmanufacturers (FSCNM).
[(1) If a prospective contractor must register in the Central Contractor Registration (CCR) database (see Subpart 204.73) and does not have a CAGE code, DLIS will assign a CAGE code when the prospective contractor submits its request for registration in the CCR database.
(c) [(2) If registration in the CCR database is not required,] If the [prospective contractor's] CAGE code is not already available in the contracting office, and the apparent [prospective contractor] awardee does not respond to the provision at 252.204-7001, Commercial and Government Entity (CAGE) Code Reporting, use the following procedures[:] in the order listed--
[(i) To identify the prospective contractor's CAGE code, use--
(A)](1) Use [T]the bimonthly H-[series]8 microfiche or CD ROM publication [that contains the H-4/H-8 CAGE master file] issued by DL[I]SC. (Their address is: DLSC-RP [Customer Service], Federal Center, 74 N. Washington [Avenue, North], Battle Creek, MI 49017-3084. Their telephone numbers are [is: toll-free 1-888-352-9333]: DSN 932-4725, FTS 552-4725, or commercial (616) 961-4725.);
(2) [(B)] Use [T]the on-line access to the CAGE file through the Defense Logistics Information System;
(3) [(C)] Use [T]the on-line access to the Defense Logistics Agency [(DLA)] CAGE file through the DLA Network or dial-up capability; or
[(D) The Internet to access the CAGE Lookup Server at http://www.dlis.dla.mil/cageserve.htm.]
(4) [(ii) If no CAGE code is identified through use of the procedures in paragraph (b)(2)(i) of this subsection, a]Ask DL[I]SC to assign a CAGE code. Submit a DD Form 2051, Request for Assignment of a [Commercial and Government Entity (]CAGE[)] Code, (or electronic equivalent) to the address in paragraph (c)(1) [(b)(2)(i)(A)] of this subsection, ATTN: DL[I]SC-SBB. The contracting [office] activity completes Section A of the DD Form 2051, Request for Assignment of a Commercial and Government Entity (CAGE) Code, and the contractor completes Section B. The contracting [office] activity must verify Section B before [submitting] the form is submitted.
(d)[(c)] Direct questions on obtaining computer tapes, electronic updates, or code assignments to DL[I]SC (DL[I]SC-SBB) at DSN 932-4358[81], FTS 552-4358, or commercial (616)[ ]961-4358[81].
204.7202-3 Taxpayer identification numbers [TINs].
The taxpayer identification number is prescribed [Requirements for use of TINs are] in FAR Subpart 4.9.
204.7203 Responsibilities of contracting officers.
(a) The contracting officer shall [A]assist the offeror[s] in obtaining the required contractor [CAGE] code(s).
(b) [Do not deny a potential]Prospective offerors may not be denied a solicitation [package] or bid set because the offeror does not have a contractor [identification] code.
(c) The contracting officer or designee shall not request a new code assignment until the appropriate microfiche, hardcopy or computer files have been screened in an effort to identify a current code for the entity. If the contracting officer does not have access to the files or listings, then initiate action to obtain the files or listings and any equipment necessary to use those files and/or listings (see 204.7202-1 and -2).
(d) If a CAGE code is being requested, it is the responsibility of the contracting activity to request the assignment of the CAGE code by completing section A of the DD Form 2051, Request for Assignment of a Commercial and Government Entity (CAGE) Code (see 253.303-2051). The prospective contractor will complete section B of the form. The completed form or electronic equivalent will be submitted by the contracting activity to DLSC-SBB for processing and code assignment after the contracting activity has verified the data submitted by the contractor.
[(c)] CAGE codes may be requested [Consider requesting a CAGE code] at the time the [a potential] offeror is sent a solicitation package or added to the mailing list to ensure that a code is assigned in sufficient time to process the DD Form 350, Individual Contracting Action Report, without delay.
(a) Changes, except name changes, may be submitted in writing- [DLIS will accept written requests for changes to CAGE files, other than name changes, from the following entities:]
(1) By t[T]he entity identified by the code, using company letterhead, through the contract administration office;[. The entity must use company letterhead to forward the request.]
(2) By t[T]he contracting office; or[.]
(3) By t[T]he contract administration office (see also [see] FAR Subpart 42.12, Novation and Change-of-Name Agreements).
[(b)](4) Using the [Submit requests for changes to CAGE files on] DD Form 2051, facsimile or electronic equivalent,
to:[--]
Defense Logistics [Information] Services Center
DL[I]SC-SBB
74 N. Washington [Avenue, North]
Telephone Numbers: DSN 932-4358[81], FTS 552-4358
commercial (616) 961-4358[[81.]
Facsimile: (616) 961-4528, 4388[, 4485.]
Internet: http/www.dlsc.dla.mil/form2051.htm
(b)[(c)] The change-of-name agreement shall be submitted to DLSC-SBB by the contracting officer responsible for execution of the agreement (see FAR Subpart 42.12. [The contracting officer responsible for execution of a change-of-name agreement (see FAR Subpart 42.12) must submit the agreement to DLIS-SBB.] In the event [If] there are no current contracts in force, each contracting and contract administration office receiving notification of changes from the commercial entity shall [must] forward a copy of the change notice annotated with the CAGE code to DL[I]SC-SBB unless the change notice indicates that DL[I]SC-SBB has already [has] been notified.
(c)[(d)] Additional guidance for maintaining CAGE codes is [in] set forth at Volume 7 of DoD 4100.39-M, Defense Integrated Data System (DIDS) [Federal Logistics Information System (FLIS) Procedures] Manual.
After May 31, 1998, p[P]rospective contractors must be registered in the CCR database, prior to award of a contract, basic agreement, basic ordering agreement, or blanket purchase agreement, unless the award results from a solicitation issued on or before May 31, 1998. This policy applies to all types of awards except the following: [except for-]
(a) Purchases made [paid for] with a Governmentwide
commercial purchase card.[;]
(b) Awards made to foreign vendors for work performed
outside the United States.[;]
(c) Classified contracts or purchases (see FAR 4.401) [when
registration in the CCR database, or use of CCR data, could
security].[;]
(d) Contracts awarded by deployed contracting officers in
the course of military operations, including, but not limited to,
contingency operations as defined in 10 U.S.C. 101(a)(13) [or
2302(7)], or contracts awarded by contracting officers in the
conduct of emergency operations, such as responses to natural
disasters or national or civil emergencies. [; and]
(a)(1) Except as provided in 204.7302, the contracting officer shall [must] require each offeror to provide a DUNS [number (see 204.603(2))] or, if applicable, a DUNS+4 number, with its verbal or written offer, regardless of the dollar amount of the offer.
(2) Prior to making an award of any [Before awarding a] contract, basic agreement, basic ordering agreement, or blanket purchase agreement after May 31, 1998, unless the award results from a solicitation issued on or before May 31, 1998, the contracting officer shall [must] verify that the prospective awardee [contractor] is registered in the CCR database (but see paragraph (b) of this section). The contracting officer may verify registration using the DUNS number or, if applicable, the DUNS+4 number, by calling toll[-]free: 1-800-841-4431, commercial: 1-[(]616[)]-961-5757, or Defense Switched Network (DSN): 932-5757; via the Internet at http://ccr.edi.disa.mil/ccr/cgi-bin/status.pl; or as otherwise provided by agency procedures.
(3) Verification of registration is not required [The contracting officer need not verify registration before placing an] for orders or calls placed under contracts, basic agreements, basic ordering agreements, or blanket purchase agreements [a DoD contract or agreement].
[(4) The contracting officer must verify registration before placing an order or call under a non-DoD contract or agreement. If the contractor is not registered, the contracting officer must follow the procedures in paragraph (b) of this section.]
(4)[(5)] After May 31, 1998, a[A]s part of the annual review of basic agreements, basic ordering agreements, and blanket purchase agreements, contracting officers shall [must] modify these agreements to incorporate the clause at 252.204-7004, Required Central Contractor Registration.
(b) If the contracting officer determines that a prospective awardee [contractor] is not registered in the CCR database [and an exception to the registration requirements for the award does not apply (see 204.7302)], the contracting officer shall [must]--
(c) Agencies shall [must] protect against improper disclosure of contractor CCR information.
(d) The contracting officer shall [must], on contractual documents transmitted to the payment office, provide either the Commercial and Government Entity code or the DUNS number in accordance with agency procedures.
Except as provided in 204.7302, use the clause at 252.204-7004, Required Central Contractor Registration, in [solicitations and contracts.]-
(c) Basic agreements, basic ordering agreements, and blanket purchase agreements issued after May 31, 1998, unless they resulted from solicitations issued on or before May 31, 19998.
[(b)(2) Paragraph (b) of the provision at FAR 52.212-3 does not apply when the solicitation includes the clause at 252.204-7004, Required Central Contractor Registration.]
[SUBPART 213.1-PROCEDURES
213.106-3 Award and documentation.
(e) The procedures at FAR 13.106-3(e) do not apply when the contract includes the clause at 252.204-7004, Required Central Contractor Registration.]
As prescribed in 204.602-70[3(1)], use the following provision:
(DEC 1991) [(AUG 1999)]
(a) The O[o]fferor is requested to enter its CAGE code on its offer in the block with its name and address. The CAGE code entered must be for that name and address. Enter ["]CAGE["] before the number.
(b) If the O[o]fferor does not have a CAGE code, it may ask the Contracting Officer to request one from the Defense Logistics [Information] Services Center (DL[I]SC). The Contracting Officer will-
(2) Complete section A and forward the form to DL[I]SC; and
(F) BLOCK B5F, TIN. * * *
(3) An agency or instrumentality of [the] a Federal, State, or local g[G]overnment.