41 U.S.C. 421 and 48 CFR chapter 1.
(a) Pursuant to FAR 27.304-1(e), the contracting officer shall insert the clause at 252.227-7039, Patents—Reporting of Subject Inventions, in solicitations and contracts containing the clause at FAR 52.227-11, Patent Rights—Retention by the Contractor (Short Form).
Interim and final invention reports and notification of all subcontracts for experimental, developmental, or research work (FAR 27.304-1(e)(2)(ii)) may be submitted on DD Form 882, Report of Inventions and Subcontracts.
The contracting officer shall insert the clause at 252.227-7034, Patents-Subcontracts, in solicitations and contracts containing the clause at FAR 52.227-11, Patent Rights—Retention by the Contractor (Short Form).
DoD activities shall use the guidance in subparts 227.71 and 227.72 instead of the guidance in FAR subpart 27.4.
This subpart prescribes policy with respect to foreign license and technical assistance agreements.
In furtherance of the Military Assistance Program or for other national defense purposes, the Government may undertake to develop or encourage the development of foreign additional sources of supply. The development of such sources may be accomplished by an agreement, often called a foreign licensing agreement or technical assistance agreement, wherein a domestic concern, referred to in this subpart as a “primary source,” agrees to furnish to a foreign concern or government, herein referred to as a “second source;” foreign patent rights; technical assistance in the form of data, know-how, trained personnel of the primary source, instruction and guidance of the personnel of the second source, jigs, dies, fixtures, or other manufacturing aids, or such other assistance, information, rights, or licenses as are needed to enable the second source to produce particular supplies or perform particular services. Agreements calling for one or more of the foregoing may be entered into between the primary source and the Government, a foreign government, or a foreign concern. The consideration for providing such foreign license and technical assistance may be in the form of a lump sum payment, payments for each item manufactured by the second source, an agreement to exchange data and patent rights on improvements made to the article or service, capital stock transactions, or any combination of these. The primary source's bases for computing such consideration may include actual costs; charges for the use of patents, data, or know-how reflecting the primary source's investment in developing and engineering and production techniques; and the primary source's “price” for setting up a second source. Such agreements often refer to the compensation to be paid as a royalty or license fee whether or not patent rights are involved.
It is Government policy not to pay in connection with its contracts, and not to allow to be paid in connection with contracts made with funds derived through the Military Assistance Program or otherwise through the United States Government, charges for use of patents in which it holds a royalty-free license or charges for data which it has a right to use and disclose to others, or which is in the public domain, or which the Government has acquired without restriction upon its use and disclosure to others. This policy shall be applied by the Departments in negotiating contract prices for foreign license technical assistance contracts (227.675) or supply contracts with second sources (227.674); and in commenting on such agreements when they are referred to the Department of Defense by the Department of State pursuant to section 414 of the Mutual Security Act of 1954 as amended (22 U.S.C. 1934) and the International Traffic in Arms Regulations (see 227.675).
(a) Contracts between the Government and a primary source to provide technical assistance or patent rights to a second source for the manufacture of supplies or performance of services shall, to the extent practicable, specify the rights in patents and data and any other rights to be supplied to the second source. Each contract shall provide, in connection with any separate agreement between the primary source and the second source for patent rights or technical assistance relating to the articles or services involved in the contract, that—
(1) The primary source and his subcontractors shall not make, on account of any purchases by the Government or by others with funds derived through the Military Assistance Program or otherwise through the Government, any charge to the second source for royalties or amortization for patents or inventions in which the Government
(2) The separate agreement between the primary and second source shall include a statement referring to the contract between the Government and the primary source, and shall conform to the requirements of the International Traffic in Arms Regulations (see 227.675-1).
(b) The following factors, among others, shall be considered in negotiating the price to be paid the primary source under contracts within (a) of this section:
(1) The actual cost of providing data, personnel, manufacturing aids, samples, spare parts, and the like;
(2) The extent to which the Government has contributed to the development of the supplies or services, and to the methods of manufacture or performance, through past contracts for research and development or for manufacture of the supplies or performance of the services; and
(3) The Government's patent rights and rights in data relating to the supplies or services and to the methods of manufacture or of performance.
In negotiating contract prices with a second source, including the redetermination of contract prices, or in determining the allowability of costs under a cost-reimbursement contract with a second source, the contracting officer:
(a) Shall obtain from the second source a detailed statement (see FAR 27.204-1(a)(2)) of royalties, license fees, and other compensation paid or to be paid to a primary source (or any of his subcontractors) for patent rights, rights in data, and other technical assistance provided to the second source, including identification and description of such patents, data, and technical assistance; and
(b) Shall not accept or allow charges which in effect are—
(1) For royalties or amortization for patents or inventions in which the Government holds a royalty-free license; or
(2) For data which the Government has a right to possess, use, and disclose to others; or
(3) For any technical assistance provided to the second source for which the Government has paid under a contract between the Government and a primary source.
Pursuant to section 414 of the Mutual Security Act of 1954, as amended (22 U.S.C. 1934), the Department of State controls the exportation of data relating to articles designated in the United States Munitions List as arms, ammunition, or munitions of war. (The Munitions List and pertinent procedures are set forth in the International Traffic in Arms Regulations, 22 CFR,
(a) In reviewing foreign license and technical assistance agreements between primary and second sources, the Department concerned shall, insofar as its interests are involved, indicate whether the agreement meets the requirements of §§ 124.07-124.10 of the International Traffic in Arms Regulations or in what respects it is deficient. Paragraphs (b) through (g) of this subsection provide general guidance.
(b) When it is reasonably anticipated that the Government will purchase from the second source the supplies or services involved in the agreement, or that Military Assistance Program
(1) If the agreement specifies a reduction in charges thereunder, with respect to purchases by or for the Government or by others with funds derived through the Military Assistance Program or otherwise through the Government, in recognition of the Government's rights in patents and data, the Department concerned shall evaluate the amount of the reduction to determine whether it is fair and reasonable in the circumstances, before indicating its approval.
(2) If the agreement does not specify any reduction in charges or otherwise fails to give recognition to the Government's rights in the patents or data involved, approval shall be conditioned upon amendment of the agreement to reflect a reduction, evaluated by the Department concerned as acceptable to the Government, in any charge thereunder with respect to purchases made by or for the Government or by others with funds derived through the Military Assistance Program or otherwise through the Government, in accordance with § 124.10 of the International Traffic in Arms Regulations.
(3) If the agreement provides that no charge is to be made to the second source for data or patent rights to the extent of the Government's rights, the Department concerned shall evaluate the acceptability of the provision before indicating its approval.
(4) If time or circumstances do not permit the evaluation called for in (b) (1), (2), or (3) of this subsection, the guidance in (c) of this subsection shall be followed.
(c) When it is not reasonably anticipated that the Government will purchase from the second source the supplies or services involved in the agreement nor that Military Assistance Program funds will be provided for the purchase of the supplies or services, then the following guidance applies.
(1) If the agreement provides for charges to the second source for data or patent rights, it may suffice to fulfill the requirements of § 124.10 insofar as the Department of Defense is concerned if:
(i) The agreement requires the second source to advise the primary source when he has knowledge of any purchase made or to be made from him by or for the Government or by others with funds derived through the Military Assistance Program or otherwise through the Government;
(ii) The primary source separately agrees with the Government that upon such advice to him from the second source or from the Government or otherwise as to any such a purchase or prospective purchase, he will negotiate with the Department concerned an appropriate reduction in his charges to the second source in recognition of any Government rights in patents or data; and
(iii) The agreement between the primary and second sources further provides that in the event of any such purchase and resulting reduction in charges, the second source shall pass on this reduction to the Government by giving the Government a corresponding reduction in the purchase price of the article or service.
(2) If the agreement provides that no charge is to be made to the second source for data or patent rights to the extent to which the Government has rights, the Department concerned shall:
(i) Evaluate the acceptability of the provision before indicating its approval; or
(ii) Explicitly condition its approval on the right to evaluate the acceptability of the provision at a later time.
(d) When there is a technical assistance agreement between the primary source and the Government related to the agreement between the primary and second sources that is under review, the latter agreement shall reflect the arrangements contemplated with respect thereto by the Government's technical assistance agreement with the primary source.
(e) Every agreement shall provide that any license rights transferred under the agreement are subject to existing rights of the Government.
(f) In connection with every agreement referred to in (b) of this section, a request shall be made to the primary source—
(1) To identify the patents, data, and other technical assistance to be provided to the second source by the primary source or any of his subcontractors,
(2) To identify any such patents and data in which, to the knowledge of the primary source, the Government may have rights, and
(3) To segregate the charges made to the second source for each such category or item of patents, data, and other technical assistance.
(g) The Department concerned shall make it clear that its approval of any agreement does not necessarily recognize the propriety of the charges or the amounts thereof, or constitute approval of any of the business arrangements in the agreement, unless the Department expressly intends by its approval to commit itself to the fairness and reasonableness of a particular charge or charges. In any event, a disclaimer should be made to charges or business terms not affecting any purchase made by or for the Government or by others with funds derived through the Military Assistance Program or otherwise through the Government.
(a) Patent interchange agreements between the United States and foreign governments provide for the use of patent rights, compensation, free licenses, and the establishment of committees to review and make recommendations on these matters. The agreements also may exempt the United States from royalty and other payments. The contracting officer shall ensure that royalty payments are consistent with patent interchange agreements.
(b) Assistance with patent rights and royalty payments in the United States European Command (USEUCOM) area of responsibility is available from HQ USEUCOM, ATTN: ECLA, Unit 30400, Box 1000, APO AE 09128; Telephone: DSN 430-8001/7263, Commercial 49-0711-680-8001/7263; Telefax: 49-0711-680-5732.
This subpart prescribes policy, procedures, and instructions for use of clauses with respect to processing licenses, assignments, and infringement claims.
Whenever a claim of infringement of privately owned rights in patented inventions or copyrighted works is asserted against any Department or Agency of the Department of Defense, all necessary steps shall be taken to investigate, and to settle administratively, deny, or otherwise dispose of such claim prior to suit against the United States. This subpart 227.70 does not apply to licenses or assignments acquired by the Department of Defense under the Patent Rights clauses.
Statutes pertaining to administrative claims of infringement in the Department of Defense include the following: the Foreign Assistance Act of 1961, 22 U.S.C. 2356 (formerly the Mutual Security Acts of 1951 and 1954); the Invention Secrecy Act, 35 U.S.C. 181-188; 10 U.S.C. 2386; 28 U.S.C. 1498; and 35 U.S.C. 286.
The procedures set forth herein will be followed, where applicable, in copyright infringement claims.
(a) A patent infringement claim for compensation, asserted against the United States under any of the applicable statutes cited in 227.7002, must be actually communicated to and received by a Department, agency, organization,
(1) An allegation of infringement;
(2) A request for compensation, either expressed or implied;
(3) A citation of the patent or patents alleged to be infringed;
(4) A sufficient designation of the alleged infringing item or process to permit identification, giving the military or commercial designation, if known, to the claimant;
(5) A designation of at least one claim of each patent alleged to be infringed; or
(6) As an alternative to (a) (4) and (5) of this section, a declaration that the claimant has made a bona fide attempt to determine the item or process which is alleged to infringe, but was unable to do so, giving reasons, and stating a reasonable basis for his belief that his patent or patents are being infringed.
(b) In addition to the information listed in (a) of this section, the following material and information is generally necessary in the course of processing a claim of patent infringement. Claimants are encouraged to furnish this information at the time of filing a claim to permit the most expeditious processing and settlement of the claim.
(1) A copy of the asserted patent(s) and identification of all claims of the patent alleged to be infringed.
(2) Identification of all procurements known to claimant which involve the alleged infringing item or process, including the identity of the vendor or contractor and the Government procuring activity.
(3) A detailed identification of the accused article or process, particularly where the article or process relates to a component or subcomponent of the item procured, an element by element comparison of the representative claims with the accused article or process. If available, this identification should include documentation and drawings to illustrate the accused article or process in suitable detail to enable verification of the infringement comparison.
(4) Names and addresses of all past and present licenses under the patent(s), and copies of all license agreements and releases involving the patent(s).
(5) A brief description of all litigation in which the patent(s) has been or is now involved, and the present status thereof.
(6) A list of all persons to whom notices of infringement have been sent, including all departments and agencies of the Government, and a statement of the ultimate disposition of each.
(7) A description of Government employment or military service, if any, by the inventor and/or patent owner.
(8) A list of all Government contracts under which the inventor, patent owner, or anyone in privity with him performed work relating to the patented subject matter.
(9) Evidence of title to the patent(s) alleged to be infringed or other right to make the claim.
(10) A copy of the Patent Office file of each patent if available to claimant.
(11) Pertinent prior art known to claimant, not contained in the Patent Office file, particularly publications and foreign art.
(c) Any Department receiving an allegation of patent infringement which meets the requirements of this paragraph shall acknowledge the same and supply the other Departments which may have an interest therein with a copy of such communication and the acknowledgement thereof.
(1) For the Department of the Army—Chief, Patents, Copyrights, and Trademarks Division, U.S. Army Legal Services Agency;
(2) For the Department of the Navy—The Patent Counsel for Navy, Office of Naval Research;
(3) For the Department of the Air Force—Chief, Patents Division, Office of The Judge Advocate General;
(4) For the Defense Logistics Agency—The Office of Counsel; for the National Security Agency, the General Counsel;
(5) For the Defense Information Systems Agency—the Counsel;
(6) For the Defense Special Weapons Agency—The General Counsel; and
(7) For the Defense Mapping Agency—The Counsel.
(d) If a communication alleging patent infringement is received which does not meet the requirements set forth in paragraph (c) of this section, the sender shall be advised in writing—
(1) That his claim for infringement has not been satisfactorily presented, and
(2) Of the elements considered necessary to establish a claim.
(e) A communication making a proffer of a license in which no infringement is alleged shall not be considered as a claim for infringement.
(a) A communication by a patent owner to a Department of Defense contractor alleging that the contractor has committed acts of infringement in performance of a Government contract shall not be considered a claim within the meaning of 227.7004 until it meets the requirements specified therein.
(b) Any Department receiving an allegation of patent infringement which meets the requirements of 227.7004 shall acknowledge the same and supply the other Departments (see 227.7004(c)) which may have an interest therein with a copy of such communication and the acknowledgement thereof.
(c) If a communication covering an infringement claim or notice which does not meet the requirements of 227.7004(a) is received from a contractor, the patent owner shall be advised in writing as covered by the instructions of 227.7004(d).
An investigation and administrative determination (denial or settlement) of each claim shall be made in accordance with instructions and procedures established by each Department, subject to the following:
(a) When the procurement responsibility for the alleged infringing item or process is assigned to a single Department or only one Department is the purchaser of the alleged infringing item or process, and the funds of that Department only are to be charged in the settlement of the claim, that Department shall have the sole responsibility for the investigation and administrative determination of the claim and for the execution of any agreement in settlement of the claim. Where, however, funds of another Department are to be charged, in whole or in part, the approval of such Department shall be obtained as required by 208.7002. Any agreement in settlement of the claim, approved pursuant to 208.7002 shall be executed by each of the Departments concerned.
(b) When two or more Departments are the respective purchasers of alleged infringing items or processes and the funds of those Departments are to be charged in the settlement of the claim, the investigation and administrative determination shall be the responsibility of the Department having the predominant financial interest in the claim or of the Department or Departments as jointly agreed upon by the Departments concerned. The Department responsible for negotiation shall, throughout the negotiation, coordinate with the other Departments concerned and keep them advised of the status of the negotiation. Any agreement in the settlement of the claim shall be executed by each Department concerned.
When a claim is denied, the Department responsible for the administrative determination of the claim shall so notify the claimant or his authorized representative and provide the claimant a reasonable rationale of the basis for denying the claim. Disclosure of information or the rationale referred to above shall be subject to applicable statutes, regulations, and directives pertaining to security, access to official records, and the rights of others.
Settlement of claims involving payment for past infringement shall not be
This section contains clauses for use in patent release and settlement agreements, license agreements, and assignments, executed by the Government, under which the Government acquires rights. Minor modifications of language (e.g., pluralization of “Secretary” or “Contracting Officer”) in multi-departmental agreements may be made if necessary.
(a) Covenant Against Contingent Fees. Insert the clause at FAR 52.203-5.
(b) Gratuities. Insert the clause at FAR 52.203-3.
(c) Assignment of Claims. Insert the clause at FAR 52.232-23.
(d) Disputes. Pursuant to FAR 33.014, insert the clause at FAR 52.233-1.
(e) Non-Estoppel. Insert the clause at 252.227-7000.
(a)
(b)
(c)
The following clauses are examples for use in patent release and settlement agreements, and license agreements not providing for payment by the Government of a running royalty.
(a) License Grant. Insert the clause at 252.227-7004.
(b) License Term. Insert one of the clauses at 252.227-7005 Alternate I or Alternate II, as appropriate.
The clauses set forth below are examples which may be used in patent release and settlement agreements, and license agreements, when it is desired to cover the subject matter thereof and the contract provides for payment of a running royalty.
(a)
(b)
(c)
(d)
(2) Where more than one Department or Government Agency is licensed and there is a ceiling on the royalties payable in any reporting period, the licensing Departments or Agencies shall coordinate with respect to the pro rata share of royalties to be paid by each.
(e)
(a) The clause at 252.227-7011 is an example which may be used in contracts of assignment of patent rights to the Government.
(b) To facilitate proof of contracts of assignments, the acknowledgement of the contractor should be executed before a notary public or other officer authorized to administer oaths (35 U.S.C. 261).
Even though no infringement has occurred or been alleged, it is the policy of the Department of Defense to procure rights under patents, patent applications, and copyrights whenever it is in the Government's interest to do so and the desired rights can be obtained at a fair price. The required and suggested clauses at 252.227-7004 and 252.227-7010 shall be required and suggested clauses, respectively, for license agreements and assignments made under this paragraph. The instructions at 227.7009-3 and 227.7010 concerning the applicability and use of those clauses shall be followed insofar as they are pertinent.
The format at 252.227-7012 appropriately modified where necessary, may be used for contracts of release, license, or assignment.
Executive Order No. 9424 of 18 February 1944 requires all executive Departments and agencies of the Government to forward through appropriate channels to the Commissioner of Patents and Trademarks, for recording, all Government interests in patents or applications for patents.
This subpart—
(a) Prescribes policies and procedures for the acquisition of technical data and the rights to use, modify, reproduce, release, perform, display, or disclose technical data. It implements requirements in the following laws and Executive Order:
(1) 10 U.S.C. 2302(4).
(2) 10 U.S.C. 2305 (subsection (d)(4)).
(3) 10 U.S.C. 2320.
(4) 10 U.S.C. 2321.
(5) 10 U.S.C. 2325.
(6) Pub. L. 103-355.
(7) Executive Order 12591 (Subsection 1(b)(6)).
(b) Does not apply to computer software or technical data that is computer software documentation (see subpart 227.72).
(a) As used in this subpart, unless otherwise specifically indicated, the terms “offeror” and “contractor” include an offeror's or contractor's subcontractors, suppliers, or potential subcontractors or suppliers at any tier.
(b) Other terms used in this subpart are defined in the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items.
Section 2320(b)(1) of Title 10 U.S.C. establishes a presumption that commercial items are developed at private expense whether or not a contractor
(a) DoD shall acquire only the technical data customarily provided to the public with a commercial item or process, except technical data that—
(1) Are form, fit, or function data;
(2) Are required for repair or maintenance of commercial items or processes, or for the proper installation, operating, or handling of a commercial item, either as a stand alone unit or as a part of a military system, when such data are not customarily provided to commercial users or the data provided to commercial users is not sufficient for military purposes; or
(3) Describe the modifications made at Government expense to a commercial item or process in order to meet the requirements of a Government solicitation.
(b) To encourage offerors and contractors to offer or use commercial products to satisfy military requirements, offerors, and contractors shall not be required, except for the technical data described in paragraph (a) of this subsection, to—
(1) Furnish technical information related to commercial items or processes that is not customarily provided to the public; or
(2) Relinquish to, or otherwise provide, the Government rights to use, modify, reproduce, release, perform, display, or disclose technical data pertaining to commercial items or processes except for a transfer of rights mutually agreed upon.
(a) The clause at 252.227-7015, Technical Data—Commercial Items, provides the Government specific license rights in technical data pertaining to commercial items or processes. DoD may use, modify, reproduce, release, perform, display, or disclose data only within the Government. The data may not be used to manufacture additional quantities of the commercial items and, except for emergency repair or overhaul, may not be released or disclosed to, or used by, third parties without the contractor's written permission. Those restrictions do not apply to the technical data described in 227.7102-1(a).
(b) If additional rights are needed, contracting activities must negotiate with the contractor to determine if there are acceptable terms for transferring such rights. The specific additional rights granted to the Government shall be enumerated in a license agreement made part of the contract.
(a) Except as provided in paragraph (b) of this subsection, use the clause at 252.227-7015, Technical Data—Commercial Items, in all solicitations and contracts when the contractor will be required to deliver technical data pertaining to commercial items, components, or processes. Do not require the contractor to include this clause in its subcontracts.
(b) Use the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, in lieu of the clause at 252.227-7015 if the Government will pay any portion of the development costs. Do not require the contractor to include this clause in its subcontracts for commercial items or commercial components.
(c) Use the clause at 252.227-7037, Validation of Restrictive Markings on Technical Data, in all solicitations and contracts for commercial items that include the clause at 252.227-7015 or the clause at 252.227-7013. Do not require the contractor to include this clause in
(a) DoD policy is to acquire only the technical data, and the rights in that data, necessary to satisfy agency needs.
(b) Solicitations and contracts shall—
(1) Specify the technical data to be delivered under a contract and delivery schedules for the data;
(2) Establish or reference procedures for determining the acceptability of technical data;
(3) Establish separate contract line items, to the extent practicable, for the technical data to be delivered under a contract and require offerors and contractors to price separately each deliverable data item; and
(4) Require offerors to identify, to the extent practicable, technical data to be furnished with restrictions on the Government's rights and require contractors to identify technical data to be delivered with such restrictions prior to delivery.
(c) Offerors shall not be required, either as a condition of being responsive to a solicitation or as a condition for award, to sell or otherwise relinquish to the Government any rights in technical data related to items, components or processes developed at private expense except for the data identified at 227.7103-5(a)(2) and (a)(4) through (9).
(d) Offerors and contractors shall not be prohibited or discouraged from furnishing or offering to furnish items, components, or processes developed at private expense solely because the Government's rights to use, modify, release, reproduce, perform, display, or disclose technical data pertaining to those items may be restricted.
(e) As provided in 10 U.S.C. 2305, solicitations for major systems development contracts shall not require offerors to submit proposals that would permit the Government to acquire competitively items identical to items developed at private expense unless a determination is made at a level above the contracting officer that—
(1) The offeror will not be able to satisfy program schedule or delivery requirements; or
(2) The offeror's proposal to meet mobilization requirements does not satisfy mobilization needs.
(a) Contracting officers shall work closely with data managers and requirements personnel to assure that data requirements included in solicitations are consistent with the policy expressed in 227.7103-1.
(b)(1) Data managers or other requirements personnel are responsible for identifying the Government's minimum needs for technical data. Data needs must be established giving consideration to the contractor's economic interests in data pertaining to items, components, or processes that have been developed at private expense; the Government's costs to acquire, maintain, store, retrieve, and protect the data; reprocurement needs; repair, maintenance and overhaul philosophies; spare and repair part considerations; and whether procurement of the items, components, or processes can be accomplished on a form, fit, or function basis. When it is anticipated that the Government will obtain unlimited or government purpose rights in technical data that will be required for competitive spare or repair parts procurements, such data should be identified as deliverable data items. Reprocurement needs may not be a sufficient reason to acquire detailed manufacturing or process data when items or components can be acquired using performance specifications, form, fit and function data, or when there are a sufficient number of alternate sources which can reasonably be expected to provide such items on a performance specification or form, fit, or function basis.
(2) When reviewing offers received in response to a solicitation or other request for data, data managers must balance the original assessment of the Government's data needs with data prices contained in the offer.
(c) Contracting officers are responsible for ensuring that, wherever practicable, solicitations and contracts—
(1) Identify the type and quantity of the technical data to be delivered under the contract and the format and media in which the data will be delivered;
(2) Establish each deliverable data item as a separate contract line item (this requirement may be satisfied by listing each deliverable data item on an exhibit to the contract);
(3) Identify the prices established for each deliverable data item under a fixed-price type contract;
(4) Include delivery schedules and acceptance criteria for each deliverable data item; and
(5) Specifically identify the place of delivery for each deliverable item of technical data.
(a) 10 U.S.C. 2320 requires, to the maximum extent practicable, an identification prior to delivery of any technical data to be delivered to the Government with restrictions on use.
(b) Use the provision at 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions, in all solicitations that include the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items. The provision requires offerors to identify any technical data for which restrictions, other than copyright, on use, release, or disclosure are asserted and to attach the identification and assertions to the offer.
(c) Subsequent to contract award, the clause at 252.277-7013 permits a contractor, under certain conditions, to make additional assertions of use, release, or disclosure restrictions. The prescription for the use of that clause and its alternate is at 227.7103-6 (a) and (b).
(a)
(1)
(2)
(b)
The standard license rights that a licensor grants to the Government are unlimited rights, government purpose rights, or limited rights. Those rights are defined in the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items. In unusual situations, the standards rights may not satisfy the Government's needs or the Government may be willing to accept lesser rights in data in return for other consideration. In those cases, a special license may be negotiated. However, the licensor is not obligated to provide the Government greater rights and the contracting officer is not required to accept lesser rights than the rights provided in the standard grant of license. The situations under which a particular grant of license applies are enumerated in paragraphs (a) through (d) of this subsection.
(a)
(1) Data pertaining to an item, component, or process which has been or will be developed exclusively with Government funds;
(2) Studies, analyses, test data, or similar data produced in the performance of a contract when the study, analysis, test, or similar work was specified as an element of performance;
(3) Created exclusively with Government funds in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes;
(4) Form, fit, and function data;
(5) Necessary for installation, operation, maintenance, or training purposes (other than detailed manufacturing or process data);
(6) Corrections or changes to technical data furnished to the contractor by the Government;
(7) Publicly available or have been released or disclosed by the contractor or subcontractor without restrictions on further use, release or disclosure other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the software to another party or the sale or transfer of some or all of a business entity or its assets to another party;
(8) Data in which the Government has obtained unlimited rights under another Government contract or as a result of negotiations; or
(9) Data furnished to the Government, under a Government contract or subcontract thereunder, with—
(i) Government purpose license rights or limited rights and the restrictive condition(s) has/have expired; or
(ii) Government purpose rights and the contractor's exclusive right to use such data for commercial purposes has expired.
(b)
(i) That pertain to items, components, or processes developed with mixed funding except when the Government is entitled to unlimited rights as provided in paragraphs (a)(2) and (a)(4) through (9) of this subsection; or
(ii) Created with mixed funding in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes.
(2) The period during which government purpose rights are effective is negotiable. The clause at 252.227-7013 provides a nominal five-year period. Either party may request a different period. Changes to the government purpose rights period may be made at any time prior to delivery of the technical data without consideration from either party. Longer periods should be negotiated when a five-year period does not provide sufficient time to apply the data for commercial purposes or when necessary to recognize subcontractors’ interests in the data.
(3) The government purpose rights period commences upon execution of the contract, subcontract, letter contract (or similar contractual instrument), contract modification, or option exercise that required the development. Upon expiration of the Government rights period, the Government
(4) During the government purpose rights period, the government may not use, or authorize other persons to use, technical data marked with government purpose rights legends for commercial purposes. The Government shall not release or disclose data in which it has government purpose rights to any person, or authorize others to do so, unless—
(i) Prior to release or disclosure, the intended recipient is subject to the use and non-disclosure agreement at 227.7103-7; or
(ii) The intended recipient is a Government contractor receiving access to the data for performance of a Government contract that contains the clause at 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.
(5) When technical data marked with government purpose rights legends will be released or disclosed to a Government contractor performing a contract that does not include the clause at 252-227-7025, the contract may be modified, prior to release or disclosure, to include that clause in lieu of requiring the contractor to complete a use and non-disclosure agreement.
(6) Contracting activities shall establish procedures to assure that technical data marked with government purpose rights legends are released or disclosed, including a release or disclosure through a Government solicitation, only to persons subject to the use and non-disclosure restrictions. Public announcements in the Commerce Business Daily or other publications must provide notice of the use and non-disclosure requirements. Class use and non-disclosure agreements (e.g., agreements covering all solicitations received by the XYZ company within a reasonable period) are authorized and may be obtained at any time prior to release or disclosure of the government purpose rights data. Documents transmitting government purpose rights data to persons under class agreements shall identify the technical data subject to government purpose rights and the class agreement under which such data are provided.
(c)
(i) That pertain to items, components, or processes developed exclusively at private expense except when the Government is entitled to unlimited rights as provided in paragraphs (a)(2) and (a)(4) through (9) of this subsection; or
(ii) Created exclusively at private expense in the performance of a contract that does not require the development, manufacture, construction, or production of items, components, or processes.
(2) Data in which the Government has limited rights may not be used, released, or disclosed outside the Government without the permission of the contractor asserting the restriction except for a use, release or disclosure that is—
(i) Necessary for emergency repair and overhaul; or
(ii) To a foreign government, other than detailed manufacturing or process data, when use, release, or disclosure is in the interest of the United States and is required for evaluation or informational purposes.
(3) The person asserting limited rights must be notified of the Government's intent to release, disclose, or authorize others to use such data prior to release or disclosure of the data except notification of an intended release, disclosure, or use for emergency repair or overhaul which shall be made as soon as practicable.
(4) When the person asserting limited rights permits the Government to release, disclose, or have others use the data subject to restrictions on further use, release, or disclosure, or for a release under paragraph (c)(2)(i) or (ii) of this subsection, the intended recipient must complete the use and non-disclosure agreement at 227.7103-7 prior to release or disclosure of the limited rights data.
(d)
(2) When the Government needs additional rights in data acquired with government purpose or limited rights, the contracting officer must negotiate with the contractor to determine whether there are acceptable terms for transferring such rights. Generally, such negotiations should be conducted only when there is a need to disclose the data outside the Government or if the additional rights are required for competitive reprocurement and the anticipated savings expected to be obtained through competition are estimated to exceed the acquisition cost of the additional rights. Prior to negotiating for additional rights in limited rights data, consider alternatives such as—
(i) Using performance specifications and form, fit, and function data to acquire or develop functionally equivalent items, components, or processes;
(ii) Obtaining a contractor's contractual commitment to qualify additional sources and maintain adequate competition among the sources; or
(iii) Reverse engineering, or providing items from Government inventories to contractors who request the items to facilitate the development of equivalent items through reverse engineering.
(a) Use the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, in solicitations and contracts when the successful offeror(s) will be required to deliver technical data to the Government. Do not use the clause when the only deliverable items are computer software or computer software documentation (see 227.72), commercial items (see 227.7102-3), existing works (see 227.7105), special works (see 227.7106), or when contracting under the Small Business Innovation Research Program (see 227.7104). Except as provided in 227.7107-2, do not use the clause in architect-engineer and construction contracts.
(b) Use the clause at 252.227-7013 with its Alternate I in research contracts when the contracting officer determines, in consultation with counsel, that public dissemination by the contractor would be—
(1) In the interest of the government; and
(2) Facilitated by the Government relinquishing its right to publish the work for sale, or to have others publish the work for sale on behalf of the Government.
(c) Use the clause at 252.227-7025, Limitations on the Use or Disclosure of Government Furnished Information Marked with Restrictive Legends, in solicitations and contracts when it is anticipated that the Government will provide the contractor, for performance of its contract, technical data marked with another contractor's restrictive legend(s).
(d) Use the provision at 252.227-7028, Technical Data or Computer Software Previously Delivered to the Government, in solicitations when the resulting contract will require the contractor to deliver technical data. The provision requires offerors to identify any technical data specified in the solicitations as deliverable data items that are the same or substantially the same as data items the offeror has delivered or is obligated to deliver, either as a contractor or subcontractor, under any other federal agency contract.
(e) Use the following clauses in solicitations and contracts that include the clause at 252.227-7013:
(1) 252.227-7016, Rights in Bid or Proposal Information;
(2) 252.227-7030, Technical Data—Withholding of Payment;
(3) 252.227-7036, Declaration of Technical Data Conformity; and
(4) 252.227-7037, Validation of Restrictive Markings on Technical Data (paragraph (e) of the clause contains information that must be included in a challenge).
(a) Except as provided in paragraph (b) of this subsection, technical data or computer software delivered to the Government with restrictions on use, modification, reproduction, release, performance, display, or disclosure may not be provided to third parties unless the intended recipient completes and signs the use and non-disclosure agreement at paragraph (c) of this subsection prior to release, or disclosure of the data.
(1) The specific conditions under which an intended recipient will be authorized to use, modify, reproduce, release, perform, display, or disclose technical data subject to limited rights or computer software subject to restricted rights must be stipulated in an attachment to the use and non-disclosure agreement.
(2) For an intended release, disclosure, or authorized use of technical data or computer software subject to special license rights, modify paragraph (1)(d) of the use and non-disclosure agreement to enter the conditions, consistent with the license requirements, governing the recipient's obligations regarding use, modification, reproduction, release, performance, display or disclosure of the data or software.
(b) The requirement for use and non-disclosure agreements does not apply to Government contractors which require access to a third party's data or software for the performance of a Government contract that contains the clause at 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.
(c) The prescribed use and non-disclosure agreement is:
The undersigned,
(1) The Recipient shall—
(a) Use, modify, reproduce, release, perform, display, or disclose Data marked with government purpose rights or SBIR data rights legends only for government purposes and shall not do so for any commercial purpose. The Recipient shall not release, perform, display, or disclose these Data, without the express written permission of the contractor whose name appears in the restrictive legend (the “Contractor”), to any person other than its subcontractors or suppliers, or prospective subcontractors or suppliers, who require these Data to submit offers for, or perform, contracts with the Recipient. The Recipient shall require its subcontractors or suppliers, or prospective subcontractors or suppliers, to sign a use and non-disclosure agreement prior to disclosing or releasing these Data to such persons. Such agreement must be consistent with the terms of this agreement.
(b) Use, modify, reproduce, release, perform, display, or disclose technical data marked with limited rights legends only as specified in the attachment to this Agreement. Release, performance, display, or disclosure to other persons is not authorized unless specified in the attachment to this Agreement or expressly permitted in writing by the Contractor. The Recipient shall promptly notify the Contractor of the execution of this Agreement and identify the Contractor's Data that has been or will be provided to the Recipient, the date and place the Data were or will be received, and the name and address of the Government office that has provided or will provide the Data.
(c) Use computer software marked with restricted rights legends only in performance of Contract Number
(d) Use, modify, reproduce, release, perform, display, or disclose Data marked with special license rights legends (To be completed by the contracting officer. See 227.7103-7(a)(2). Omit if none of the Data requested is marked with special license rights legends).
(2) The Recipient agrees to adopt or establish operating procedures and physical security measures designed to protect these Data from inadvertent release or disclosure to unauthorized third parties.
(3) The Recipient agrees to accept these Data “as is” without any Government representation as to suitability for intended use or warranty whatsoever. This disclaimer does not affect any obligation the Government may have regarding Data specified in a contract for the performance of that contract.
(4) The Recipient may enter into any agreement directly with the Contractor with respect to the use, modification, reproduction, release, performance, display, or disclosure of these Data.
(5) The Recipient agrees to indemnify and hold harmless the Government, its agents, and employees from every claim or liability, including attorneys fees, court costs, and expenses arising out of, or in any way related to, the misuse or unauthorized modification, reproduction, release, performance, display, or disclosure of Data received from the Government with restrictive legends by the Recipient or any person to whom the Recipient has released or disclosed the Data.
(6) The Recipient is executing this Agreement for the benefit of the Contractor. The Contractor is a third party beneficiary of this Agreement who, in addition to any other rights it may have, is intended to have the rights of direct action against the Recipient or any other person to whom the Recipient has released or disclosed the Data, to seek damages from any breach of this Agreement or to otherwise enforce this Agreement.
(7) The Recipient agrees to destroy these Data, and all copies of the Data in its possession, no later than 30 days after the date shown in paragraph (8) of this Agreement, to have all persons to whom it released the Data do so by that date, and to notify the Contractor that the Data have been destroyed.
(8) This Agreement shall be effective for the period commencing with the Recipient's execution of this Agreement and ending upon
(a)
(b)
(a)
(2) The clause at 252.227-7013 does not permit a contractor to incorporate a third party's copyrighted data into a deliverable data item unless the contractor has obtained an appropriate license for the Government and, when applicable, others acting on the Government's behalf, or has obtained the contracting officer's written approval to do so. Grant approval to use third party copyrighted data in which the Government will not receive a copyright license only when the Government's requirements cannot be satisfied without the third party material or when the use of the third party material will result in cost savings to the Government which outweigh the lack of a copyright license.
(b)
(a)
(2) The procedures for correcting minor informalities shall not be used to obtain information regarding asserted restrictions or an offeror's suggested asserted rights category. Questions regarding the justification for an asserted restriction or asserted rights category must be pursued in accordance with the procedures at 227.7103-13.
(3) The restrictions asserted by a successful offeror shall be attached to its contract unless, in accordance with the procedures at 227.7103-13, the parties have agreed that an asserted restriction is not justified. The contract attachment shall provide the same information regarding identification of the technical data, the asserted rights category, the basis for the assertion, and the name of the person asserting the restrictions as required by paragraph (d) of the solicitation provision at 252.227-7017. Subsequent to contract award, the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, permits the contractor to make
(4) Neither the pre- or post-award assertions made by the contractor, nor the fact that certain assertions are identified in the attachment to the contract, determine the respective rights of the parties. As provided at 227.7103-13, the Government has the right to review, verify, challenge and validate restrictive markings.
(5) Information provided by offerors in response to the solicitation provision may be used in the source selection process to evaluate the impact on evaluation factors that may be created by restrictions on the Government's ability to use or disclose technical data. However, offerors shall not be prohibited from offering products for which the offeror is entitled to provide the Government limited rights in the technical data pertaining to such products and offerors shall not be required, either as a condition of being responsive to a solicitation or as a condition for award, to sell or otherwise relinquish any greater rights in technical data when the offeror is entitled to provide the technical data with limited rights.
(b)
(1) Requires a contractor that desires to restrict the Government's rights in technical data to place restrictive markings on the data, provides instructions for the placement of the restrictive markings, and authorizes the use of certain restrictive markings; and
(2) Requires a contractor to deliver, furnish, or otherwise provide to the Government any technical data in which the Government has previously obtained rights with the Government's pre-existing rights in that data unless the parties have agreed otherwise or restrictions on the Government's rights to use, modify, reproduce, release, perform, display, or disclose the data have expired. When restrictions are still applicable, the contractor is permitted to mark the data with the appropriate restrictive legend for which the data qualified.
(c)
(2) A contractor may request permission to have appropriate legends placed on unmarked technical data at its expense. The request must be received by the contracting officer within six months following the furnishing or delivery of such data, or any extension of that time approved by the contracting officer. The person making the request must:
(i) Identify the technical data that should have been marked;
(ii) Demonstrate that the omission of the marking was inadvertent, the proposed marking is justified and conforms with the requirements for the marking of technical data contained in the clause at 252.227-7013; and
(iii) Acknowledge, in writing, that the Government has no liability with respect to any disclosure, reproduction, or use of the technical data made prior to the addition of the marking or resulting from the omission of the marking.
(3) Contracting officers should grant permission to mark only if the technical data were not distributed outside the Government or were distributed outside the Government with restrictions on further use or disclosure.
(a) The clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, requires a contractor, and its subcontractors or suppliers that will deliver technical data with other than unlimited rights, to establish and follow written procedures to assure that restrictive markings are used only when authorized and to maintain
(b) The clause at 252.227-7037, Validation of Restrictive Markings on Technical Data requires contractors and their subcontractors at any tier to maintain records sufficient to justify the validity of restrictive markings on technical data delivered or to be delivered under a Government contract.
(a)
(2) The correction of nonconforming markings on technical data is not subject to 252.227-7037, Validation of Restrictive Markings on Technical Data. To the extent practicable, the contracting officer should return technical data bearing nonconforming markings to the person who has placed the nonconforming markings on such data to provide that person an opportunity to correct or strike the nonconforming marking at that person's expense. If that person fails to correct the nonconformity and return the corrected data within 60 days following the person's receipt of the data, the contracting officer may correct or strike the nonconformity at that person's expense. When it is impracticable to return technical data for correction, contracting officers may unilaterally correct any nonconforming markings at Government expense. Prior to correction, the data may be used in accordance with the proper restrictive marking.
(b)
(2) Contracting officers have the right to review and challenge the validity of unjustified markings. However, at any time during performance of a contract and notwithstanding existence of a challenge, the contracting officer and the person who has asserted a restrictive marking may agree that the restrictive marking is not justified. Upon such agreement, the contracting officer may, at his or her election, either—
(i) Strike or correct the unjustified marking at that person's expense; or
(ii) Return the technical data to the person asserting the restriction for correction at that person's expense. If the data are returned and that person fails to correct or strike the unjustified restriction and return the corrected data to the contracting officer within 60 days following receipt of the data, the unjustified marking shall be corrected or stricken at that person's expense.
(a)
(b)
(c)
(1)
(i) Are publicly available without restrictions;
(ii) Have been provided to the United States without restriction; or
(iii) Have been otherwise made available without restriction other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the technical data to another party or the sale or transfer of some or all of a business entity or its assets to another party.
(2)
(ii) If the person asserting the restriction fails to respond to the contracting officer's request for information or additional supporting documentation, or if the information submitted or any other available information pertaining to the validity of a restrictive marking does not justify the asserted restriction, a challenge should be considered.
(3)
(i) A subcontractor's or supplier's business interests in its technical data would be compromised if the data were disclosed to a higher tier contractor;
(ii) There is reason to believe that the contractor will not respond in a timely manner to a challenge and an untimely response would jeopardize a subcontractor's or suppliers right to assert restrictions; or
(iii) Requested to do so by a subcontractor or supplier.
(4)
(5)
(6)
(i) A contracting officer's final decision that an assertion is not justified must be issued a soon as practicable following the failure of the person asserting the restriction to respond to the contracting officer's challenge within 60 days, or any extension to
(ii) A contracting officer who, following a challenge and response by the person asserting the restriction, determines that an asserted restriction is justified, shall issue a final decision sustaining the validity of the asserted restriction. If the asserted restriction was made subsequent to submission of the contractor's offer, add the asserted restriction to the contract attachment.
(iii) A contracting officer who determine that the validity of an asserted restriction has not been justified shall issue a contracting officer's final decision within the time frames prescribed in 252.227-7037. As provided in paragraph (g) of that clause, the Government is obligated to continue to respect the asserted restrictions through final disposition of any appeal unless the agency head notifies the person asserting the restriction that urgent or compelling circumstances do not permit the Government to continue to respect the asserted restriction.
(7)
(8)
(a)
(1) Requires contractors to furnish written assurance, at the time technical data are delivered or are made available to the Government, that the technical data are complete, accurate, and satisfy the requirements of the contract concerning such data;
(2) Provides for the establishment of remedies applicable to technical data found to be incomplete, inadequate, or not to satisfy the requirements of the contract concerning such data; and
(3) Authorizes agency heads to withhold payments (or exercise such other remedies an agency head considers appropriate) during any period if the contractor does not meet the requirements of the contract pertaining to the delivery of technical data.
(b)
(2) The clause at 252.227-7030, Technical Data—Withholding of Payment, provides for withholding up to 10 percent of the contract price pending correction or replacement of the nonconforming technical data or negotiation of an equitable reduction in contract price. The amount subject to withholding may be expressed as a fixed dollar amount or as a percentage of the contract price. In either case, the amount shall be determined giving consideration to the relative value and importance of the data. For example—
(i) When the sole purpose of a contract is to produce the data, the relative value of that data may be considerably higher than the value of data produced under a contract where the production of the data is a secondary objective; or
(ii) When the Government will maintain or repair items, repair and maintenance data may have a considerably higher relative value than data that merely describe the item or provide performance characteristics.
(3) Do not accept technical data that do not conform to the contractual requirements in all respects. Except for nonconforming restrictive markings (see paragraph (b)(4) of this subsection), correction or replacement of
(i) The provisions of a contract clause providing for inspection and acceptance of deliverables and remedies for nonconforming deliverables; or
(ii) The procedures at FAR 46.407(c) through (g), if the contract does not contain an inspection clause providing remedies for nonconforming deliverables.
(4) Follow the procedures at 227.7103-12(a)(2) if nonconforming markings are the sole reason technical data fail to conform to contractual requirements. The clause at 252.227-7030 may be used to withhold an amount for payment, consistent with the terms of the clause, pending correction of the nonconforming markings.
(c)
(2) As prescribed in 246.710, use the clause at 252.246-7001, Warranty of Data, and its alternates, or a substantially similar clause when the Government needs a specific warranty of technical data.
(a) 10 U.S.C. 2320 provides subcontractors at all tiers the same protection for their rights in data as is provided to prime contractors. The clauses at 252.227-7013, Rights in Technical Data—Noncommercial Items, and 252.227-7037, Validation of Restrictive Markings on Technical Data, implement the statutory requirements.
(b) 10 U.S.C. 2321 permits a subcontractor to transact directly with the Government matters relating to the validation of its asserted restrictions on the Government's rights to use or disclose technical data. The clause at 252.227-7037 obtains a contractor's agreement that the direct transaction of validation or challenge matters with subcontractors at any tier does not establish or imply privity of contract. When a subcontractor or supplier exercise its right to transact validation matters directly with the Government, contracting officers shall deal directly with such persons, as provided at 227.7103-13(c)(3).
(c) Require prime contractors whose contracts include the following clauses to include those clauses, without modification except for appropriate identification of the parties, in contracts with subcontractors or suppliers, at all tiers, who will be furnishing technical data for non-commercial items in response to a Government requirement:
(1) 252.227-7013, Rights in Technical Data—Noncommercial Items;
(2) 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends;
(3) 252.227-7028, Technical Data or Computer Software Previously Delivered to the Government; and
(4) 252.227-7037, Validation of Restrictive Markings on Technical Data.
(d) Do not require contractors to have their subcontractors or suppliers at any tier relinquish rights in technical data to the contractor, a higher tier subcontractor, or to the Government, as a condition for award of any contract, subcontract, purchase order, or similar instrument except for the rights obtained by the Government under the Rights in Technical Data—Noncommercial Items clause contained in the contractor's contract with the Government.
Technical data may be released or disclosed to foreign governments, foreign contractors, or international organizations only if release or disclosure is otherwise permitted both by Federal export controls and other national security laws or regulations. Subject to such laws and regulations, the Department of Defense—
(a) May release or disclose technical data in which it has obtained unlimited rights to such foreign entities or authorize the use of such data by those entities; and
(b) Shall not release or disclose technical data for which restrictions on use, release, or disclosure have been asserted to foreign entities, or authorize the use of technical data by those entities, unless the intended recipient is subject to the same provisions as included in the use and non-disclosure agreement at 227.7103-7 and the requirements of the clause at 252.227-7103, Rights in Technical Data—Noncommercial Items, governing use, modification, reproduction, release, performance, display, or disclosure of such data have been satisfied.
(a) The clause at 252.227-7032, Rights in Technical Data and Computer Software (Foreign), may be used in contracts with foreign contractors to be performed overseas, except Canadian purchases (see paragraph (c) of this subsection), in lieu of the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, when the Government requires the unrestricted right to use, modify, reproduce, perform, display, release or disclose all technical data to be delivered under the contract. Do not use the clause in contracts for existing or special works.
(b) When the Government does not require unlimited rights, the clause at 252.227-7032 may be modified to accommodate the needs of a specific overseas procurement situation. The Government should obtain rights in the technical data that are not less than the rights the Government would have obtained under the data rights clause(s) prescribed in this part for a comparable procurement performed within the United States or its possessions.
(c) Contracts for Canadian purchases shall include the appropriate data rights clause prescribed in this part for a comparable procurement performed within the United States or its possessions.
(a) Use the clause at 252.227-7018, Rights in Noncommercial Technical Data and Computer Software—Small Business Innovation Research (SBIR) Program, when technical data or computer software will be generated during performance of contracts under the SBIR program.
(b) Under the clause at 252.227-7018, the Government obtains a royalty-free license to use technical data marked with an SBIR data rights legend only for government purposes during the period commencing with contract award and ending five years after completion of the project under which the data were generated. Upon expiration of the five-year restrictive license, the Government has unlimited rights in the SBIR data. During the license period, the Government may not release or disclose SBIR data to any person other than its support services contractors except—
(1) For evaluational purposes;
(2) As expressly permitted by the contractor; or
(3) A use, release, or disclosure that is necessary for emergency repair or overhaul of items operated by the Government.
(c) Do not make any release or disclosure permitted by paragraph (b) of this section unless, prior to release or disclosure, the intended recipient is subject to the use and nondisclosure agreement at 227.7103-7.
(d) Use the clause at 252.227-7018 with its Alternate I in research contracts when the contracting officer determines, in consultation with counsel, that public dissemination by the contractor would be—
(1) In the interest of the Government; and
(2) Facilitated by the Government relinquishing its right to publish the work for sale, or to have others publish the work for sale on behalf of the Government.
(e) Use the following provision and clauses in SBIR solicitations and contracts that include the clause at 252.227-7018:
(1) 252.227-7016, Rights in Bid or Proposal Information;
(2) 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions;
(3) 252.227-7019, Validation of Asserted Restrictions—Computer Software;
(4) 252.227-7030, Technical Data—Withholding of Payment;
(5) 252.227-7036, Declaration of Technical Data Conformity; and
(6) 252.227-7037, Validation of Restrictive Markings on Technical Data (paragraph (e) of the clause contains information that must be included in a challenge).
(f) Use the following clauses and provision in SBIR solicitations and contracts in accordance with the guidance at 227.7103-6 (c) and (d):
(1) 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends; and
(2) 252.227-7028, Technical Data or Computer Software Previously Delivered to the Government.
(a) Existing works include motion pictures, television recordings, video recordings, and other audiovisual works in any medium; sound recordings in any medium; musical, dramatic, and literary works; pantomimes and choreographic works; pictorial, graphic, and sculptural works; and works of a similar nature. Usually, these or similar works were not first created, developed, generated, originated, prepared, or produced under a Government contract. Therefore, the Government must obtain a license in the work if it intends to reproduce the work, distribute copies of the work, prepare derivative works, or perform or display the work publicly. When the Government is not responsible for the content of an existing work, it should require the copyright owner to indemnify the Government for liabilities that may arise out of the content, performance, use, or disclosure of such data.
(b) Follow the procedures at 227.7106 for works which will be first created, developed, generated, originated, prepared, or produced under a Government contract and the Government needs to control distribution of the work or has a specific need to obtain indemnity for liabilities that may arise out of the creation, content, performance, use, or disclosure of the work or from libelous or other unlawful material contained in the work. Follow the procedures at 227.7103 when the Government does not need to control distribution of such works or obtain such indemnities.
(a) Use the clause at 252.227-7021, Rights in Data—Existing Works, in lieu of the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, in solicitations and contracts exclusively for existing works when—
(1) The existing works will be acquired without modification; and
(2) The Government requires the right to reproduce, prepare derivative works, or publicly perform or display the existing works; or
(3) The Government has a specific need to obtain indemnity for liabilities that may arise out of the content, performance, use, or disclosure of such data.
(b) The clause at 252.227-7021 provides the Government, and others acting on its behalf, a paid-up, non-exclusive, irrevocable, world-wide license to reproduce, prepare derivative works and publicly perform or display the works called for by a contract and to authorize others to do so for government purposes.
(c) A contract clause is not required to acquire existing works such as books, magazines and periodicals, in any storage or retrieval medium, when the Government will not reproduce the
Use the clause at 252.227-7020, Rights in Special Works, in solicitations and contracts for modified existing works in lieu of the clause at 252.227-7021, Rights in Data—Existing Works.
(a) Use the clause at 252.227-7020, Rights in Special Works, in solicitations and contracts where the Government has a specific need to control the distribution of works first produced, created, or generated in the performance of a contract and required to be delivered under that contract, including controlling distribution by obtaining an assignment of copyright, or a specific need to obtain indemnity for liabilities that may arise out of the creation, delivery, use, modification, reproduction, release, performance, display, or disclosure of such works. Use the clause—
(1) In lieu of the clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, when the Government must own or control copyright in all works first produced, created, or generated and required to be delivered under a contract; or
(2) In addition to the clause at 252.227-7013 when the Government must own or control copyright in a portion of a work first produced, created, or generated and required to be delivered under a contract. The specific portion in which the Government must own or control copyright must be identified in a special contract requirement.
(b) Although the Government obtains an assignment of copyright and unlimited rights in a special work under the clause at 252.227-7020, the contractor retains use and disclosure rights in that work. If the Government needs to restrict a contractor's rights to use or disclose a special work, it must also negotiate a special license which specifically restricts the contractor's use or disclosure rights.
(c) The clause at 252.227-7020 does not permit a contractor to incorporate into a special work any works copyrighted by others unless the contractor obtains the contracting officer's permission to do so and obtains for the Government a non-exclusive, paid up, world-wide license to make and distribute copies of that work, to prepare derivative works, to perform or display publicly any portion of the work, and to permit others to do so for government purposes. Grant permission only when the Government's requirements cannot be satisfied unless the third party work is included in the deliverable work.
(d) Examples of works which may be procured under the Rights in Special Works clause include, but are not limited, to audiovisual works, computer data bases, computer software documentation, scripts, soundtracks, musical compositions, and adaptations; histories of departments, agencies, services or units thereof; surveys of Government establishments; instructional works or guidance to Government officers and employees on the discharge of their official duties; reports, books, studies, surveys or similar documents; collections of data containing information pertaining to individuals that, if disclosed, would violate the right of privacy or publicity of the individuals to whom the information relates; or investigative reports.
This section sets forth policies and procedures, pertaining to data, copyrights, and restricted designs unique to the acquisition of construction and architect-engineer services.
(a) Except as provided in paragraph (b) of this subsection and in 227.7107-2, use the clause at 252.227-7022, Government Rights (Unlimited), in solicitations and contracts for architect-engineer services and for construction involving architect-engineer services.
(b) When the purpose of a contract for architect-engineer services, or for construction involving architect-engineer services, is to obtain a unique architectural design of a building, a monument, or construction of similar nature, which for artistic, aesthetic or other special reasons the Government
(c) The Government shall obtain unlimited rights in shop drawings for construction. In solicitations and contracts calling for delivery of shop drawings, include the clause at 252.227-7033, Rights in Shop Drawings.
Use the provisions and clauses required by 227-7103-6 and 227.7203-6 when the acquisition is limited to—
(a) Construction supplies or materials;
(b) Experimental, developmental, or research work, or test and evaluation studies of structures, equipment, processes, or materials for use in construction; or
(c) Both.
The clause at 252.227-7024, Notice and Approval of Restricted Designs, may be included in architect-engineer contracts to permit the Government to make informed decisions concerning noncompetitive aspects of the design.
(a) Contractor data repositories may be established when permitted by agency procedures. The contractual instrument establishing the data repository must require, as a minimum, the data repository management contractor to—
(1) Establish and maintain adequate procedures for protecting technical data delivered to or stored at the repository from unauthorized release or disclosure;
(2) Establish and maintain adequate procedures for controlling the release or disclosure of technical data from the repository to third parties consistent with the Government's rights in such data;
(3) When required by the contracting officer, deliver data to the Government on paper or in other specified media;
(4) Be responsible for maintaining the currency of data delivered directly by Government contractors or subcontractors to the repository;
(5) Obtain use and non-disclosure agreements (see 227.7103-7) from all persons to whom government purpose rights data is released or disclosed; and
(6) Indemnify the Government from any liability to data owners or licensors resulting from, or as a consequence of, a release or disclosure of technical data made by the data repository contractor or its officers, employees, agents, or representatives.
(b) If the contractor is or will be the data repository manager, the contractor's data management and distribution responsibilities must be identified in the contract or the contract must reference the agreement between the Government and the contractor that establishes those responsibilities.
(c) If the contractor is not and will not be the data repository manager, do not require a contractor or subcontractor to deliver technical data marked with limited rights legends to a data repository managed by another contractor unless the contractor or subcontractor who has asserted limited rights agrees to release the data to the repository or has authorized, in writing, the Government to do so.
(d) Repository procedures may provide for the acceptance, delivery, and subsequent distribution of technical data in storage media other than paper, including direct electronic exchange of data between two computers. The procedures must provide for the identification of any portions of the data provided with restrictive legends, when appropriate. The acceptance criteria must be consistent with the authorized delivery format.
This subpart—
(a) Prescribes policies and procedures for the acquisition of computer software and computer software documentation, and the rights to use, modify, reproduce, release, perform, display, or disclose such software or documentation. It implements requirements in the following laws and Executive Order:
(1) 10 U.S.C. 2302(4).
(2) 10 U.S.C. 2305 (subsection (d)(4)).
(3) 10 U.S.C. 2320.
(4) 10 U.S.C. 2321.
(5) 10 U.S.C. 2325.
(6) Executive Order 12591 (subsection 1(b)(6)).
(b) Does not apply to computer software or computer software documentation acquired under GSA schedule contracts.
(a) As used in this subpart, unless otherwise specifically indicated, the terms “offeror” and “contractor” include an offeror's or contractor's subcontractors, suppliers, or potential subcontractors or suppliers at any tier.
(b) Other terms used in this subpart are defined in the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation.
(a) Commercial computer software or commercial computer software documentation shall be acquired under the licenses customarily provided to the public unless such licenses are inconsistent with Federal procurement law or do not otherwise satisfy user needs.
(b) Commercial computer software and commercial computer software documentation shall be obtained competitively, to the maximum extent practicable, using firm-fixed-price contracts or firm-fixed-priced orders under available pricing schedules.
(c) Offerors and contractors shall not be required to—
(1) Furnish technical information related to commercial computer software or commercial computer software documentation that is not customarily provided to the public except for information documenting the specific modifications made at Government expense to such software or documentation to meet the requirements of a Government solicitation; or
(2) Relinquish to, or otherwise provide, the Government rights to use, modify, reproduce, release, perform, display, or disclose commercial computer software or commercial computer software documentation except for a transfer of rights mutually agreed upon.
(a) The Government shall have only the rights specified in the license under which the commercial computer software or commercial computer software documentation was obtained.
(b) If the Government has a need for rights not conveyed under the license customarily provided to the public, the Government must negotiate with the contractor to determine if there are acceptable terms for transferring such rights. The specific rights granted to the Government shall be enumerated in the contract license agreement or an addendum thereto.
A specific contract clause governing the Government's rights in commercial computer software or commercial computer software documentation is not prescribed. As required by 227.7202-3, the Government's rights to use, modify, reproduce, release, perform, display, or disclose computer software or computer software documentation shall be identified in a license agreement.
(a) DoD policy is to acquire only the computer software and computer software documentation, and the rights in such software or documentation, necessary to satisfy agency needs.
(b) Solicitations and contracts shall—
(1) Specify the computer software or computer software documentation to be delivered under a contract and the delivery schedules for the software or documentation;
(2) Establish or reference procedures for determining the acceptability of computer software or computer software documentation;
(3) Establish separate contract line items, to the extent practicable, for the computer software or computer software documentation to be delivered under a contract and require offerors and contractors to price separately each deliverable data item; and
(4) Require offerors to identify, to the extent practicable, computer software or computer software documentation to be furnished with restrictions on the Government's rights and require contractors to identify computer software or computer software documentation to be delivered with such restrictions prior to delivery.
(c) Offerors shall not be required, either as a condition of being responsive to a solicitation or as a condition for award, to sell or otherwise relinquish to the Government any rights in computer software developed exclusively at private expense except for the software identified at 227.7203-5(a) (3) through (6).
(d) Offerors and contractors shall not be prohibited or discouraged from furnishing or offering to furnish computer software developed exclusively at private expense solely because the Government's rights to use, modify, release, reproduce, perform, display, or disclose the software may be restricted.
(a) Contracting officers shall work closely with data managers and requirements personnel to assure that computer software and computer software documentation requirements included in solicitations are consistent with the policy expressed in 227.7203-1.
(b)(1) Data managers or other requirements personnel are responsible for identifying the Government's minimum needs. In addition to desired software performance, compatibility, or other technical considerations, needs determinations should consider such factors as multiple site or shared use requirements, whether the Government's software maintenance philosophy will require the right to modify or have third parties modify the software, and any special computer software documentation requirements.
(2) When reviewing offers received in response to a solicitation or other request for computer software or computer software documentation, data managers must balance the original assessment of the Government's needs with prices offered.
(c) Contracting officers are responsible for ensuring that, wherever practicable, solicitations and contracts—
(1) Identify the types of computer software and the quantity of computer programs and computer software documentation to be delivered, any requirements for multiple users at one site or multiple site licenses, and the format and media in which the software or documentation will be delivered;
(2) Establish each type of computer software or computer software documentation to be delivered as a separate contract line item (this requirement may be satisfied by an exhibit to the contract);
(3) Identify the prices established for each separately priced deliverable item of computer software or computer software documentation under a fixed-price type contract;
(4) Include delivery schedules and acceptance criteria for each deliverable item; and
(5) Specifically identify the place of delivery for each deliverable item.
(a) Use the provision at 252.227-7017, Identification and Assertion of Use, Release, or Disclosure Restrictions, in all solicitation that include the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation. The provision requires offerors to identify any computer software or computer software documentation for
(b) Subsequent to contract award, the clause at 252.227-7014 permits a contractor, under certain conditions, to make additional assertions of restrictions. The prescriptions for the use of that clause and its alternates are at 227.7203-6(a).
(a)
(b)
The standard license rights in computer software that a licensor grants to the Government are unlimited rights, government purpose rights, or restricted rights. The standard license in computer software documentation conveys unlimited rights. Those rights are defined in the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation. In unusual situations, the standard rights may not satisfy the Government's needs or the Government may be willing to accept lesser rights in return for other consideration. In those cases, a special license may be negotiated. However, the licensor is not obligated to provide the Government greater rights and the contracting officer is not required to accept lesser rights than the rights provided in the standard grant of license. The situations under which a particular grant of license applies are enumerated in paragraphs (a) through (d) of this subsection.
(a)
(1) Computer software developed exclusively with Government funds;
(2) Computer software documentation required to be delivered under a Government contract;
(3) Corrections or changes to computer software or computer software documentation furnished to the contractor by the Government;
(4) Computer software or computer software documentation that is otherwise publicly available or has been released or disclosed by the contractor or subcontractor without restrictions on further use, release or disclosure other than a release or disclosure resulting from the sale, transfer, or other assignment of interest in the software to another party or the sale or transfer of some or all of a business entity or it assets to another party;
(5) Computer software or computer software documentation obtained with unlimited rights under another Government contract or as a result of negotiations; or
(6) Computer software or computer software documentation furnished to
(i) Restricted rights in computer software, limited rights in technical data, or government purpose license rights and the restrictive conditions have expired; or
(ii) Government purpose rights and the contractor's exclusive right to use such software or documentation for commercial purposes has expired.
(b)
(2) The period during which government purpose rights are effective is negotiable. The clause at 252.227-7014 provides a nominal five-year period. Either party may request a different period. Changes to the government purpose rights period may be made at any time prior to delivery of the software without consideration from either party. Longer periods should be negotiated when a five-year period does not provide sufficient time to commercialize the software or, for software developed by subcontractors, when necessary to recognize the subcontractors’ interests in the software.
(3) The government purpose rights period commences upon execution of the contract, subcontract, letter contract (or similar contractual instrument), contract modification, or option exercise that required development of the computer software. Upon expiration of the government purpose rights period, the Government has unlimited rights in the software including the right to authorize others to use data for commercial purposes.
(4) During the government purpose rights period, the Government may not use, or authorize other persons to use, computer software marked with government purpose rights legends for commercial purposes. The Government shall not release or disclose, or authorize others to release or disclose, computer software in which it has government purpose rights to any person unless—
(i) Prior to release or disclosure, the intended recipient is subject to the use and non-disclosure agreement at 227.7103-7; or
(ii) The intended recipient is a Government contractor receiving access to the software for performance of a Government contract that contains the clause at 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends.
(5) When computer software marked with government purpose rights legends will be released or disclosed to a Government contractor performing a contract that does not include the clause at 252.227-7025, the contract may be modified, prior to release or disclosure, to include such clause in lieu of requiring the contractor to complete a use and non-disclosure agreement.
(6) Contracting activities shall establish procedures to assure that computer software or computer software documentation marked with government purpose rights legends are released or disclosed, including a release or disclosure through a Government solicitation, only to persons subject to the use and non-disclosure restrictions. Public announcements in the Commerce Business Daily or other publications must provide notice of the use and non-disclosure requirements. Class use and non-disclosure agreements (e.g., agreements covering all solicitations received by the XYZ company within a reasonable period) are authorized and may be obtained at any time prior to release or disclosure of the government purpose rights software or documentation. Documents transmitting government purpose rights software or documentation to persons under class agreements shall identify the specific software or documentation subject to government purpose rights and the class agreement under which such software or documentation are provided.
(c)
(2) Contractors are not required to provide the Government additional rights in computer software delivered
(d)
(e)
(a)(1) Use the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, in solicitations and contracts when the successful offeror(s) will be required to deliver computer software or computer software documentation. Do not use the clause when the only deliverable items are technical data (other than computer software documentation), commercial computer software or commercial computer software documentation, commercial items (see 227.7102-3), special works (see 227.7205), or contracts under the Small Business Innovative Research Program (see 227.7104), Except as provided in 227.7107-2, do not use the clause in architect-engineer and construction contracts..
(2) Use the clause at 252.227-7014 with its Alternate I in research contracts when the contracting officer determines, in consultation with counsel, that public dissemination by the contractor would be—
(i) In the interest of the Government; and
(ii) Facilitated by the Government relinquishing its right to publish the work for sale, or to have others publish the work for sale on behalf of the Government.
(b) Use the clause at 252.227-7016, Rights in Bid or Proposal Information, in solicitations and contracts that include the clause at 252.227-7014.
(c) Use the clause at 252.227-7019, Validation of Asserted Restrictions—Computer Software, in solicitations and contracts that include the clause at 252.227-7014. The clause provides procedures for the validation of asserted restrictions on the Government's rights to use, release, or disclose computer software.
(d) Use the provision at 252.227-7025, Limitations on the Use or Disclosure of Government-Furnished Information Marked with Restrictive Legends, in solicitations and contracts when it is anticipated that the Government will provide the contractor, for performance of its contract, computer software or computer software documentation marked with another contractor's restrictive legend(s).
(e) Use the provision at 252.227-7028, Technical Data or Computer Software Previously Delivered to the Government, in solicitations when the resulting contract will require the contractor to deliver computer software or computer software documentation. The provision requires offerors to identify any software or documentation specified in the solicitation as deliverable items that are the same or substantially the same as software or documentation which the offeror has delivered or is obligated to deliver, either as a contractor or subcontractor, under any other federal agency contract.
(f) Use the clause at 252.227-7037, Validation of Restrictive Markings on Technical Data, in solicitations and contracts that include the clause at 252.227-7014 when the contractor will be required to deliver noncommercial computer software documentation (technical data). The clause implements statutory requirements under 10 U.S.C. 2321. Paragraph (e) of the clause contains information that must be included in a formal challenge.
(a)
(b)
(a)
(2) The clause at 252.227-7013, Rights in Technical Data—Noncommercial Items, does not permit a contractor to incorporate a third party's copyrighted software into a deliverable software item unless the contractor has obtained an appropriate license for the Government and, when applicable, others acting on the Government's behalf, or has obtained the contracting officer's written approval to do so. Grant approval to use third party copyrighted software in which the Government will not receive a copyright license only when the Government's requirements cannot be satisfied without the third party material or when the use of the third party material will result in cost savings to the Government which outweigh the lack of a copyright license.
(b)
(a)
(2) The procedures for correcting minor informalities shall not be used to obtain information regarding asserted restrictions or an offeror's suggested asserted rights category. Questions regarding the justification for an asserted restriction or asserted rights category must be pursued in accordance with the procedures at 227.7203-13.
(3) The restrictions asserted by a successful offeror shall be attached to its contract unless, in accordance with the procedures at 227.7203-13, the parties have agreed that an asserted restriction is not justified. The contract attachment shall provide the same information regarding identification of the computer software or computer software documentation, the asserted rights category, the basis for the assertion, and the name of the person asserting the restrictions as required by paragraph (d) of the solicitation provision at 252.227-7017. Subsequent to contract award, the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, permits a contractor to make additional assertions under certain conditions. The additional assertions must be made in accordance with the procedures and in the format prescribed by that clause.
(4) Neither the pre- or post-award assertions made by the contractor nor the fact that certain assertions are identified in the attachment to the contract, determine the respective rights of the parties. As provided at 227.7203-13, the Government has the right to review, verify, challenge and validate restrictive markings.
(5) Information provided by offerors in response to the solicitation provision at 252.227-7017 may be used in the source selection process to evaluate the impact on evaluation factors that may be created by restrictions on the Government's ability to use or disclose computer software or computer software documentation.
(b)
(1) Requires a contractor who desires to restrict the Government's rights in computer software or computer software documentation to place restrictive markings on the software or documentation, provides instructions for the placement of the restrictive markings, and authorizes the use of certain restrictive markings. When it is anticipated that the software will or may be used in combat or situations which simulate combat conditions, do not permit contractors to insert instructions into computer programs that interfere with or delay operation of the software to display a restrictive rights legend or other license notice; and
(2) Requires a contractor to deliver, furnish, or otherwise provide to the Government any computer software or computer software documentation in which the Government has previously obtained rights with the Government's pre-existing rights in that software or documentation unless the parties have agreed otherwise or restrictions on the Government's rights to use, modify, produce, release, or disclose the software or documentation have expired. When restrictions are still applicable, the contractor is permitted to mark the software or documentation with the appropriate restrictive legend.
(c)
(2) A contractor may request permission to have appropriate legends placed on unmarked computer software or computer software documentation at its expense. The request must be received by the contracting officer within six months following the furnishing or delivery of such software or documentation, or any extension of that time approved by the contracting officer. The person making the request must—
(i) Identify the software or documentation that should have been marked;
(ii) Demonstrate that the omission of the marking was inadvertent, the proposed marking is justified and conforms with the requirements for the marking of computer software or computer software documentation contained in the clause at 252.227-7014; and
(iii) Acknowledge, in writing, that the Government has no liability with respect to any disclosure, reproduction, or use of the software or documentation made prior to the addition of the marking or resulting from the omission of the marking.
(3) Contracting officers should grant permission to mark only if the software or documentation were not distributed outside the Government or were distributed outside the Government with restrictions on further use or disclosure.
(a) The clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, requires a contractor, and its subcontractors or suppliers that will deliver computer software or computer software documentation with other than unlimited rights, to establish and follow written procedures to assure that restrictive markings are used only when authorized and to maintain records to justify the validity of restrictive markings.
(b) The clause at 252.227-7019, Validation of Asserted Restrictions—Computer Software, requires contractors and their subcontractors or suppliers at any tier to maintain records sufficient to justify the validity of markings that assert restrictions on the use, modification, reproduction, release, performance, display, or disclosure of computer software.
(a)
(2) The correction of nonconforming markings on computer software is not subject to 252.227-7019, Validation of Asserted Restrictions—Computer Software, and the correction of nonconforming markings on computer software documentation (technical data) is not subject to 252.227-7037, Validation of Restrictive Markings on Technical Data. To the extent practicable, the contracting officer should return computer software or computer software documentation bearing nonconforming markings to the person who has placed the nonconforming markings on the software or documentation to provide that person an opportunity to correct or strike the nonconforming markings at that person's expense. If that person fails to correct the nonconformity and return the corrected software or documentation within 60 days following the person's receipt of the software or documentation, the contracting officer may correct or strike the nonconformity at the person's expense. When it is impracticable to return computer software or computer software documentation for correction, contracting officers may unilaterally correct any nonconforming markings at Government expense. Prior to correction, the software or documentation may be used in accordance with the proper restrictive marking.
(b)
(2) Contracting officers have the right to review and challenge the validity of unjustified markings. However, at any time during performance of a contract and notwithstanding existence of a challenge, the contracting officer and the person who has asserted a restrictive marking may agree that the restrictive marking is not justified. Upon such agreement, the contracting officer may, at his or her election, either——
(i) Strike or correct the unjustified marking at that person's expense; or
(ii) Return the computer software or computer software documentation to the person asserting the restriction for correction at that person's expense. If the software or documentation are returned and that person fails to correct or strike the unjustified restriction and return the corrected software or documentation to the contracting officer within 60 days following receipt of the software or documentation, the unjustified marking shall be corrected or stricken at that person's expense.
(a)
(b)
(c)
(1) A subcontractor's or supplier's business interests in its technical data would be compromised if the data were disclosed to a higher tier contractor.
(2) There is reason to believe that the contractor will not respond in a timely manner to a challenge and an untimely response would jeopardize a subcontractor's or supplier's right to assert restrictions; or
(3) Requested to do so by a subcontractor or supplier.
(d)
(2)
(3)
(ii) Contracting officers must have reasonable grounds to challenge the current validity of an asserted restriction. Before challenging an asserted restriction, carefully consider all available information pertaining to the asserted restrictions. Resolution of questions regarding the validity of asserted restrictions using the process described at 227.7203-12(b)(2) is strongly encouraged. After consideration of the situations described in paragraph (c) of this subsection, contracting officers may request the person asserting a restriction to furnish a written explanation of the facts and supporting documentation for the assertion in sufficient detail to enable the contracting officer to determine the validity of the assertion. Additional supporting documentation may be requested when the explanation provided by that person does not, in the contracting officer's opinion, establish the validity of the assertion.
(iii) Assertions may be challenged whether or not supporting documentation was requested. Challenges must be in writing and issued to the person asserting the restriction.
(4)
(e)
(2) Only a contracting officer's final decision, or actions of an agency Board of Contract Appeals or a court of competent jurisdiction, that sustain the validity of an asserted restriction constitute validation of the restriction.
(f)
(a)
(b)
(i) The provisions of a contract clause providing for inspection and acceptance of deliverables and remedies for nonconforming deliverables; or
(ii) The procedures at FAR 46.407(c) through (g), if the contract does not contain an inspection clause providing remedies for nonconforming deliverables.
(2)
(ii)
(a) Subcontractors and suppliers at all tiers should be provided the same protection for their rights in computer software or computer software documentation as are provided to prime contractors.
(b) The clauses at 252.227-7019, Validation of Asserted Restrictions—Computer Software, and 252.227-7037, Validation of Restrictive Markings on
(c) Require prime contractors whose contracts include the following clauses to include those clauses, without modification except for appropriate identification of the parties, in contracts with subcontractors or suppliers who will be furnishing computer software in response to a Government requirement (see 227.7103-15(c) for clauses required when subcontractors or suppliers will be furnishing computer software documentation (technical data)):
(1) 252.227.7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation;
(2) 252.227.7019, Validation of Asserted Restrictions—Computer Software;
(3) 252.227.7025, Limitations on the Use or Disclosure of Government Furnished Information Marked with Restrictive Legends; and
(4) 252.227.7028, Technical Data or Computer Software Previously Delivered to the Government.
(d) Do not require contractors to have their subcontractors or suppliers at any tier relinquish rights in technical data to the contractor, a higher tier subcontractor, or to the Government, as a condition for award of any contract, subcontract, purchase order, or similar instrument except for the rights obtained by the Government under the provisions of the Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation clause contained in the contractor's contract with the Government.
Computer software or computer software documentation may be released or disclosed to foreign governments, foreign contractors, or international organizations only if release or disclosure is otherwise permitted both by Federal export controls and other national security laws or regulations. Subject to such laws and regulations, the Department of Defense—
(a) May release or disclose computer software or computer software documentation in which it has obtained unlimited rights to such foreign entities or authorize the use of such data by those entities; and
(b) Shall not release or disclose computer software or computer software documentation for which restrictions on use, release, or disclosure have been asserted to such foreign entities or authorize the use of such data by those entities, unless the intended recipient is subject to the same provisions as included in the use and non-disclosure agreement at 227.7103-7 and the requirements of the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, governing use, modification, reproduction, release, performance, display, or disclosure of such data have been satisfied.
(a) The clause at 252.227-7032, Rights in Technical Data and Computer Software (Foreign), may be used in contracts with foreign contractors to be performed overseas, except Canadian purchases (see paragraph (c) of this subsection) in lieu of the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government requires the unrestricted right to use, modify, reproduce, release, perform, display, or
(b) When the Government does not require unlimited rights, the clause at 252.227-7032 may be modified to accommodate the needs of a specific overseas procurement situation. The Government should obtain rights to the computer software or computer software documentation that are not less than the rights the Government would have obtained under the software rights clause(s) prescribed in this part for a comparable procurement performed within the United States or its possessions.
(c) Contracts for Canadian purchases shall include the appropriate software rights clause prescribed in this part for a comparable procurement performed within the United States or its possessions.
When contracting under the Small Business Innovative Research Program, follow the procedures at 227-7104.
(a) Use the clause at 252.227-7020, Rights in Special Works, in solicitations and contracts where the Government has a specific need to control the distribution of computer software or computer software documentation first produced, created, or generated in the performance of a contract and required to be delivered under that contract, including controlling distribution by obtaining an assignment of copyright, or a specific need to obtain indemnity for liabilities that may arise out of the creation, delivery, use, modification, reproduction, release, performance, display, or disclosure of such software or documentation. Use the clause—
(1) In lieu of the clause at 252.227-7014, Rights in Noncommercial Computer Software and Noncommercial Computer Software Documentation, when the Government must own or control copyright in all computer software or computer software documentation first produced, created, or generated and required to be delivered under a contract; or
(2) In addition to the clause at 252.227-7014 when the Government must own or control copyright in some of the computer software or computer software documentation first produced, created, or generated and required to be delivered under a contract. The specific software or documentation in which the Government must own or control copyright must be identified in a special contract requirement.
(b) Although the Government obtains an assignment of copyright and unlimited rights in the computer software or computer software documentation delivered as a special work under the clause at 252.227-7020, the contractor retains use and disclosure rights in that software or documentation. If the Government needs to restrict a contractor's rights to use or disclose a special work, it must also negotiate a special license which specifically restricts the contractor's use or disclosure rights.
(c) The clause at 252.227-7020 does not permit a contractor to incorporate into a special work any work copyrighted by others unless the contractor obtains the contracting officer's permission to do so and obtains for the Government a non-exclusive, paid up, world-wide license to make and distribute copies of that work, to prepare derivative works, to perform or display any portion of that work, and to permit others to do so for government purposes. Grant permission only when the Government's requirements cannot be satisfied unless the third party work is included in the deliverable work.
(d) Examples of other works which may be procured under the clause at 252.227-7020 include, but are not limited to, audiovisual works, scripts, soundtracks, musical compositions, and adaptations; histories of departments, agencies, services or units thereof; surveys of Government establishments; instructional works or guidance to Government officers and employees on the discharge of their official duties; reports, books, studies, surveys or similar documents; collections of data containing information pertaining to individuals that, if disclosed, would violate the right of privacy or publicity of the
Follow 227.7107 when contracting for architect-engineer services.
Follow 227.7108 when it is in the Government's interests to have a data repository include computer software or to have a separate computer software repository. Contractual instruments establishing the repository requirements must appropriately reflect the repository manager's software responsibilities.
41 U.S.C. 421 and 48 CFR chapter 1.
For Defense Environmental Restoration Program construction contracts entered into pursuant to 10 U.S.C. 2701 and executed between December 5, 1991, and December 31, 1999—
(1) Any rights of action under the performance bond shall only accrue to, and be for the exclusive use of, the obligee named in the bond.
(2) In the event of default, the surety's liability on the performance bond is limited to the cost of completion of the contract work, less the balance of unexpended funds. Under no circumstances shall the liability exceed the penal sum of the bond.
(3) The surety shall not be liable for indemnification or compensation of the obligee for loss or liability arising from personal injury or property damage, even if the injury or damage was caused by a breach of the bonded contract.
(4) Once it has taken action to meet its obligations under the bond, the surety is entitled to any indemnification and identical standard of liability to which the contractor was entitled under the contract or applicable laws and regulations.
(a) The requirement for performance and payment bonds is waived for cost-reimbursement contracts. However, for cost type contracts with fixed-price construction subcontracts over $25,000, require the prime contractor to obtain from each of its construction subcontractors—
(i) A payment bond in favor of the prime contractor sufficient to pay labor and material costs; and
(ii) A performance bond in an equal amount if available at no additional cost.
Fidelity and forgery bonds generally are not required but may be used when—
(1) Necessary for the protection of the Government or the contractor; or
(2) The investigative and claims services of a surety company are desired.
(a) Withholding may be appropriate in other than construction contracts (see 232.970-1(b)).
When a requirement for a performance bond or other security is included in a solicitation for dismantling, demolition, or removal of improvements (see FAR 37.300), use the provision at 252.228-7004, Bonds or Other Security. Set a period of time (normally ten days) for return of executed bonds.
The DoD has established the National Defense Projects Rating Plan, also known as the Special Casualty Insurance Rating Plan, as a risk-pooling arrangement to minimize the cost to the Government of purchasing the liability insurance listed in FAR 28.307-2. Use the plan in accordance with the following guidelines when it provides the necessary coverage more advantageously than commercially available coverage.
(1) The plan—
(i) Is implemented by attaching an endorsement to standard insurance policy forms for workers’ compensation, employer's liability, comprehensive general, and automobile liability. The endorsement states that the instant policy is subject to the National Defense Projects Rating Plan.
(ii) Applies to eligible Defense projects of one or more departments/agencies. For purposes of this section, a Defense project is any eligible contract or group of contracts with the same contractor.
(A) A Defense project is eligible when—
(
(
(B) A contract is eligible when it is—
(
(
(
(2) Under construction contracts, include construction subcontractors in the prime contractor's plan only when subcontractor operations are at the project site, and the subcontract provides that the prime contractor will furnish insurance.
(3) Use the agreement in Table 28-1, Insurance Rating Plan Agreement, when the Government assumes contractor premium payments upon contract termination or completion.
(4) The Federal Tort Claims Act provides protection for Government employees while driving Government-owned vehicles in the performance of their assigned duties. Include the endorsement in Table 28-2, Automobile Insurance Policy Endorsement, in automobile liability insurance policies provided under the National Defense Projects Rating Plan.
It is agreed that 100 percent *
* In the event the Government has less than a 100 percent interest in premium funds or dividends, modify the assignment to reflect the percentage of interest and extent of the Government's assumption of additional premium obligation.
The United States of America hereby assumes and agrees to fulfill all present and future obligations of the prime contractor with respect to the payment of 100 percent of the premiums under said policies.
This agreement, upon acceptance by the prime contractor, the United States of America, and the Company shall be effective from
United States of America
It is agreed that insurance provided by the policy with respect to the ownership, maintenance, or use of automobiles, including loading and unloading thereof, does not apply to the following as insureds: The United States of America, any of its agencies, or any of its officers or employees.
(d) Submit requests for waiver through department/agency channels. Include the following—
(i) Name and address of contractor;
(ii) Contract number;
(iii) Date of award;
(iv) Place of performance;
(v) Name of insurance company providing Defense Base Act coverage;
(vi) Nationality of employees to whom waiver is to apply; and
(vii) Reason for waiver.
The Defense Department Group Term Insurance Plan is available for contractor use under cost-reimbursement type contracts when approved as provided in department or agency regulations. A contractor is eligible if—
(a) The number of covered employees is 500 or more; and
(b) The contractor has all cost-reimbursement contracts; or
(c) At least 90 percent of the payroll for contractor operations to be covered by the Plan is under cost-reimbursement contracts.
Use the clause at FAR 52.228-7, Insurance—Liability to Third Persons, in solicitations and contracts, other than those for construction and those for architect-engineer services, when a cost-reimbursement contract is contemplated, unless the head of the contracting activity waives the requirement for use of the clause.
(a) Use the clause at 252.228-7000, Reimbursement for War-Hazard Losses, when—
(1) The clause at FAR 52.228-4, Worker's Compensation and War-Hazard Insurance Overseas, is used; and
(2) The head of the contracting activity decides not to allow the contractor to buy insurance for war-hazard losses.
(b)(1) Use the clause at 252.228-7001, Ground and Flight Risk, in negotiated fixed-price contracts for aircraft production, modification, maintenance, repair, or overhaul, unless—
(i) The aircraft is being acquired for a foreign military sale and the foreign government has not agreed to assume the risk; or
(ii) The cost of insurance for damage, loss, or destruction of aircraft does not exceed $500, and the contracting officer agrees to recognize the insurance costs.
(2) If appropriate, revise the clause at 252.228-7001, Ground and Flight Risk, as follows—
(i) Include a modified definition of “aircraft” if the contract covers other than conventional types of winged aircraft, i.e., helicopters, vertical take-off aircraft, lighter-than-air airships or other nonconventional aircraft. The modified definition should describe a stage of manufacture comparable to the standard definition.
(ii) Modify “in the open” to include “hush houses,” test hangars and comparable structures, and other designated areas.
(iii) Expressly define the “contractor's premises” where the aircraft will
(iv) Revise paragraph (d)(iii) of the clause to provide Government assumption of risk for transportation by conveyance on streets or highways when transportation is—
(A) Limited to the vicinity of contractor premises; and
(B) Incidental to work performed under the contract.
(c)(1) Use the clause at 252.228-7002, Aircraft Flight Risk, in cost reimbursement contracts—
(i) For the development, production, modification, maintenance, repair, or overhaul of aircraft; or
(ii) Otherwise involving the furnishing of aircraft to the contractor by the Government.
(iii) With the definition of “aircraft” modified, if appropriate, to include helicopters, vertical take-off aircraft, lighter-than-air airships or other nonconventional aircraft.
(2) Use the clause at 252.228-7002, Aircraft Flight Risk, appropriately modified, in fixed price contracts when—
(i) The clause at 252.228-7001, Ground and Flight Risk, is not used; and
(ii) Contract performance involves the flight of Government furnished aircraft.
(d) The clause at 252.228-7003, Capture and Detention, may be used when contractor employees are subject to capture and detention and may not be covered by the War Hazards Compensation Act (42 U.S.C. 1701
(e) The clause at 252.228-7005, Accident Reporting and Investigation Involving Aircraft, Missiles, and Space Launch Vehicles, may be used in solicitations and contracts which involve the manufacture, modification, overhaul, or repair of these items.
(f) Use the clause at 252.228-7006, Compliance with Spanish Laws and Insurance, in solicitations and contracts for services or construction to be performed in Spain by other than a Spanish contractor or subcontractor.
41 U.S.C. 421 and 48 CFR chapter 1.
(a) Within DoD, the agency-designated legal counsels are the defense agency General Counsels, the General Counsels of the Navy and Air Force, and for the Army, the Chief, Contract Law Division, Office of the Judge Advocate General.
(c) The contracting officer may direct the contractor to litigate the applicability of a particular tax if—
(i) The contract is either a cost reimbursement type or a fixed price type with a tax escalation clause; and
(ii) The direction is coordinated with the agency-designated legal counsel through the DoD Tax Policy and Advisory Group.
(d)(i) Tax relief agreements between the United States and foreign governments in Europe that exempt the United States from payment of specific
(ii) Tax relief also may be available in countries that have not signed tax relief agreements. The potential for such relief should be explored in accordance with paragraph (d)(iii) of this section.
(iii) Review DoDD 5100.64, Department of Defense Foreign Tax Relief Program, before contracting with a foreign source. Refer questions on implementation of the program to the Commanding Officers in Table 29-1, Designated Commanding Officers, which have been designated under subsection E.7 of DoDD 5100.64 to serve as—
(A) Single point of contact for U.S. contracting offices for investigation and resolution of specific foreign tax relief matters; and
(B) Liaison with responsible diplomatic mission and local foreign tax authorities.
(iv) Refer foreign tax relief questions which have not been resolved by the designated Commanding Officer to the agency-designated legal counsel.
(v) When an acquisition is for a contract to be performed in a country or area listed in Table 29-1, Designated Commanding Officers—
(A) Obtain from the designated Commanding Officer detailed information concerning the taxes and duties from which the Government of the United States is exempt, and
(B) Provide the information to prospective offerors.
(C) Do not provide prospective offerors any other information about foreign taxes or duties.
(D) Issue tax exemption certificates, as appropriate, to assist the contractor in obtaining relief from foreign taxes and duties which were excluded from the contract price.
(E) Seek advice and assistance from the designated Commanding Officer and, if necessary, the agency-designated legal counsel if the contractor notifies the contracting officer that it has been assessed a tax or duty by a foreign government which could increase the contract price.
(vi) Also see subpart 229.70 for special procedures for obtaining tax relief and duty-free import privileges when conducting U.S. Government acquisitions in certain foreign countries.
Use the clause at 252.229-7000, Invoices Exclusive of Taxes or Duties, in solicitations and contracts when a fixed-price contract will be awarded to a foreign concern.
(a) Use the clause at 252.229-7001, Tax Relief, in solicitations and contracts when a contract will be awarded to a foreign concern in a foreign country. When contract performance will be in Germany, use the clause with its Alternate I.
(b) Use the clause at 252.229-7002, Customs Exemptions (Germany), in solicitations and contracts requiring the import of U.S. manufactured products into Germany.
(c) Use the clause at 252.229-7003, Tax Exemptions (Italy), in solicitations and contracts when contract performance will be in Italy.
(d) Use the clause at 252.229-7004, Status of Contractor as a Direct Contractor (Spain), in solicitations and contracts requiring the import into Spain of supplies for construction, development, maintenance, or operation of Spanish-American installations and facilities.
(e) Use the clause at 252.229-7005, Tax Exemptions (Spain), in solicitations and contracts when contract performance will be in Spain.
(f) Use the clause at 252.229-7006, Value Added Tax Exclusion (United Kingdom), in solicitations and contracts when contract performance will be in the United Kingdom.
(g) Use the clause at 252.229-7007, Verification of United States Receipt of Goods, in solicitations and contracts when contract performance will be in the United Kingdom.
(h) Use the clause at 252.229-7008, Relief from Import Duty (United Kingdom), in solicitations issued and contracts awarded in the United Kingdom.
(i) Use the clause at 252.229-7009, Relief from Customs Duty and Value Added Tax on Fuel (Passenger Vehicles) (United Kingdom), in solicitations issued and contracts awarded in the United Kingdom for fuels (gasoline or diesel) and lubricants used in passenger vehicles (excluding taxis).
(j) Use the clause at 252.229-7010, Relief from Customs Duty on Fuel (United Kingdom), in solicitations issued and contracts awarded in the United Kingdom that require the use of fuels (gasoline or diesel) and lubricants in taxis or vehicles other than passenger vehicles.
This subpart prescribes procedures to be used by contracting officers to obtain tax relief and duty-free import privileges when conducting U.S. Government acquisitions in certain foreign countries.
(a) The Joint United States Military Group (JUSMG), Spain Policy Directive 400.4, or subsequent directive, applies to U.S. contracting offices acquiring supplies or services in Spain when the introduction of material or equipment into Spain is required for contract performance.
(b) Upon award of a contract with a Direct Contractor, as defined in the clause at 252.229-7004, the contracting officer will notify JUSMG-MAAG Madrid, Spain, and HQ 16AF/LGTT and forward three copies of the contract to JUSMG-MAAG, Spain.
(c) If copies of the contract are not available and duty-free import of equipment or materials is urgent, the contracting officer will send JUSMG-MAAG three copies of the Letter of Intent or a similar document indicating the pending award. In these cases, authorization for duty-free import will be issued by the Government of Spain. Upon formal award, the contracting officer will forward three copies of the completed contract to JUSMG-MAAG, Spain.
(d) The contracting officer will notify JUSMG-MAAG, Spain, and HQ 16AF/LGTT of ports-of-entry and identify the customs agents who will clear property on their behalf. Additional
This section contains procedures to be followed in securing relief from the British value added tax and import duties.
(a) U.S. Government purchases qualifying for tax relief are equipment, materials, facilities, and services for the common defense effort and for foreign aid programs.
(b) To facilitate the resolution of issues concerning specific waivers of import duty or tax exemption for U.S. Government purchases (see 229.7002-3), contracting offices shall provide the name and activity address of personnel who have been granted warranted contracting authority to Her Majesty's (HM) Customs and Excise at the following address: HM Customs and Excise, International Customs Division G, Branch 4, Adelaide House, London Bridge, London EC4R 9DB.
No import duty shall be paid by the United States and contract prices shall be exclusive of duty, except when the administrative cost compared to the low dollar value of a contract makes it impracticable to obtain relief from contract import duty. In this instance, the contracting officer shall document the contract file with a statement that—
(a) The administrative burden of securing tax relief under the contract was out of proportion to the tax relief involved;
(b) It is impracticable to secure tax relief;
(c) Tax relief is therefore not being secured; and
(d) The acquisition does not involve the expenditure of any funds to establish a permanent military installation.
In the event a value added tax or import duty problem cannot be resolved at the contracting officer's level, refer the issue to HQ Third Air Force, Staff Judge Advocate, Unit 4840, Box 45, APO AE 09459. Direct contact with HM Customs and Excise in London is prohibited.
(a)
(b)
(1) To HM Customs and Excise—
(i) Contract number;
(ii) Name and address of contractor;
(iii) Type of work (e.g., laundry, transportation);
(iv) Area of work; and
(v) Period of performance.
(2) To the regional office of HM Custom and Excise to which the contractor applied for relief from the duty on road fuel—copy of the contract.
(c)
41 U.S.C. 421 and 48 CFR chapter 1.
(a) The contracting officer will estimate the facilities capital cost of money and capital employed using—
(1) An analysis of the appropriate Forms CASB-CMF and cost of money factors; and
(2) DD Form 1861, Contract Facilities Capital Cost of Money.
The DD Form 1861 provides a means of linking the Form CASB-CMF and DD Form 1547, Record of Weighted Guidelines Application. It—
(a) Enables the contracting officer to differentiate profit objectives for various types of assets (land, buildings, equipment). The procedure is similar to applying overhead rates to appropriate overhead allocation bases to determine contract overhead costs.
(b) Is designed to record and compute the contract facilities capital cost of money and capital employed which is carried forward to DD Form 1547.
Complete a DD Form 1861 only after evaluating the contractor's cost proposal, establishing cost of money factors, and establishing a prenegotiation objective on cost. Complete the form as follows:
(a) List overhead pools and direct-charging service centers (if used) in the same structure as they appear on the contractor's cost proposal and Form CASB-CMF. The structure and allocation base units-of-measure must be compatible on all three displays.
(b) Extract appropriate contract overhead allocation base data, by year, from the evaluated cost breakdown or prenegotiation cost objective and list against each overhead pool and direct-charging service center.
(c) Multiply each allocation base by its corresponding cost of money factor to get the facilities capital cost of money estimated to be incurred each year. The sum of these products represents the estimated contract facilities capital cost of money for the year's effort.
(d) Total contract facilities cost of money is the sum of the yearly amounts.
(e) Since the facilities capital cost of money factors reflect the applicable cost of money rate in Column 1 of Form CASB-CMF, divide the contract cost of money by that same rate to determine the contract facilities capital employed.
To establish cost and price objectives, apply the facilities capital cost of money and capital employed, as determined under 230.7000, as follows:
(a)
(2)
(b)
(a) The contractor may include contract facilities capital cost of money in cost reimbursement and progress payment invoices. To determine the amount that qualifies as cost incurred, multiply the incurred portions of the overhead pool allocation bases by the latest available cost of money factors. These cost of money calculations are interim estimates subject to adjustment.
(b) As actual cost of money factors under CAS 414 and FAR 31.205-10 are finalized, use the new factors to calculate contract facilities cost of money for the next accounting period.
(a) Contract facilities capital cost of money for final cost determination or repricing is based on each year's final cost of money factors determined under CAS 414 and supported by separate Forms CASB-CMF.
(b) Separately compute contract facilities cost of money in a manner similar to yearly final overhead rates. Also like overhead costs, include in the final settlement an adjustment from interim to final contract cost of money. Do not, however, adjust estimated or target cost.
(a) Forms CASB-CMF are normally initiated by the contractor under the same circumstances as Forward Pricing Rate Agreements (see FAR 15.809) and evaluated as complementary documents and procedures.
(b) Separate forms are required for each prospective cost accounting period of contract performance.
(c) The contractor may submit annually or with individual contract price proposals, as agreed with the administrative contracting officer (ACO).
(d) The contractor must submit a final form under CAS 414 as soon as possible after the end of each accounting period, together with a proposal for actual overhead costs and rates.
(a) The contracting officer may ask the ACO to complete the forms as part of field pricing support.
(b) When the Weighted Guidelines Method is used, completion of the DD Form 1861 requires information not included on the Form CASB-CMF, i.e., distribution percentages of land, building, and equipment for the business unit performing the contract. Choose the most practical method for obtaining this information, for example—
(1) Contract administration offices could obtain the information through the process used to establish factors for facilities capital cost of money or could establish advance agreements on distribution percentages for inclusion in field pricing reports;
(2) The corporate ACO could obtain distribution percentages; or
(3) The contracting officer could request the information through a solicitation provision.
(a)
(b)
(c)
(1) The interest rate determined by the Secretary of the Treasury under Public Law 92-41 (85 Stat. 97); or
(2) The time-weighted average of the interest rate for each cost accounting period during which the asset is being constructed, fabricated, or developed.
(d)
(a) The interest rate in 230.7100(c)(1) is established semi-annually and is published in the
(b) To calculate the time-weighted average interest rate—
(1) Multiply the various rates in effect during the months of construction by the number of months each rate was in effect; and
(2) Divide the sum of the products by the total number of months in which the rates were experienced.
(a) The calculation of the representative investment requires consideration of the rate or expenditure pattern of the costs to construct, fabricate, or develop a capital asset.
(b) If a majority of the costs were incurred toward the beginning, middle, or end of the cost accounting period, the contractor shall either—
(1) Determine a representative investment amount for the cost accounting period by calculating the average of the month-end balances for that cost accounting period; or
(2) Treat month-end balances as individual representative investment amounts.
(c) If the costs were incurred in a fairly uniform expenditure pattern throughout the construction, fabrication, or development period, the contractor may—
(1) Determine a representative investment amount for the cost accounting period by averaging the beginning and ending balances of the construction, fabrication, or development cost account for the cost accounting period; or
(2) Treat month-end balances as individual representative investment amounts.
(a) Determine the imputed cost of money for an asset under construction, fabrication, or development by applying a cost of money rate (see 230.7101-1) to the representative investment amount (see 230.7101-2).
(1) When a representative investment amount is determined for a cost accounting period in accordance with 230.7101-2(b)(1) or 230.7101-2(c)(1), the cost of money will be the time-weighted average rate.
(2) When a monthly representative investment amount is used in accordance with 230.7101-2(b)(2) or 230.7101-2(c)(2), the cost of money will be the interest rate in effect each month. (Under this method, the cost of money is determined monthly and the total for the cost accounting period is the sum of the monthly amounts.)
(b) The imputed cost of money will be capitalized only once in any cost accounting period, either at the end of the period or at the end of the construction, fabrication, or development period, whichever comes first.
(c) When the construction of an asset takes more than one cost accounting period, the cost of money capitalized for the first cost accounting period will be included in determining the representative investment amount for any future cost accounting periods.
An offset to the profit objectives as set forth in FAR Subpart 15.9 is not required for CAS 417 cost of money.
41 U.S.C. 421 and 48 CFR chapter 1.
Use the clause at 252.231-7000, Supplemental Cost Principles, in all solicitations and contracts which are subject to the principles and procedures described in FAR subpart 31.1, 31.2, 31.6, or 31.7.
(f)(1) In accordance with Section 8122 of Pub. L. 104-61, and similar sections in subsequent Defense appropriations acts, costs for bonuses or other payments in excess of the normal salary paid by the contractor to an employee, that are part of restructuring costs associated with a business combination, are unallowable under DoD contracts funded by fiscal year 1996 or subsequent appropriations. This limitation does not apply to severance payments or early retirement incentive payments. (See 231.205-70(b) for the definitions of “business combination” and “restructuring costs.”)
The contractor also must comply with subpart 230.70 and maintain records to demonstrate compliance.
(c)(1)(i)(C)(
(
(
(
(
(
(
(
(
(
(
(
(
(
(2) Departments/agencies shall not supplement this regulation in any way that limits IR&D/B&P cost allowability. See 225.7303-2 for allowability exceptions for foreign military sales contracts.
(i) In addition to the limitations in FAR 31.205-18(c)(2)(i), for major contractors—
(
(
(
(
(
(
(
(
(
(
(
(
(ii) The cognizant contract administration office shall furnish contractors with guidance on financial information needed to support IR&D/B&P costs and on technical information needed from major contractors to support the potential interest to DoD determination (see also 242.771-3(a)).
(iii) The total maximum allowable amount limitation may be waived at a level above the contracting officer. A waiver may be appropriate for contractors whose significant growth in sales or IR&D/B&P spending justify higher levels of reimbursement.
(a) Preparing any material, report, list, or analysis on the actual or projected economic or employment impact in a particular State or congressional district of an acquisition program for which all research, development, testing, and evaluation has not been completed (10 U.S.C. 2249).
(a)
(b)
(1)
(2)
(3)
(4)
(5)
(c)
(i) Such costs are allowable in accordance with FAR part 31 and DFARS part 231;
(ii) An audit of projected restructuring costs and restructuring savings is performed;
(iii) The cognizant administrative contracting officer (ACO) reviews the audit report and the projected costs and projected savings, and negotiates an advance agreement in accordance with paragraph (d)(8) of this subsection; and
(iv) For business combinations that occur—
(A) Prior to October 1, 1996, the Under Secretary of Defense (Acquisition & Technology) or the Principal Deputy certifies that projections of future restructuring savings resulting for DoD from the business combination are based on audited cost data and should result in overall reduced costs for DoD.
(B) October 1, 1996, through November 18, 1997, the Under Secretary of Defense (Acquisition & Technology) or the Principal Deputy—
(C) After November 18, 1997, the Under Secretary of Defense (Acquisition & Technology) or the Principal Deputy determines in writing that the audited projected savings for DoD resulting from restructuring will exceed either—
(2) The audit, review, certification, and determination required by paragraph (c)(1) of this subsection shall not
(d)
(1) Promptly execute a novation agreement, if one is required, in accordance with FAR subpart 42.12 and DFARS subpart 242.12 and include the provision at DFARS 242.1204(e).
(2) Direct the contractor to segregate restructuring costs and to suspend these amounts from any billings, final contract price settlements, and overhead settlements until the certification, or determination, or both, as applicable, in paragraph (c)(1)(iv) of this subsection is obtain.
(3) Require the contractor to submit an overall plan of restructuring activities and an adequately supported proposal for planned restructuring projects. The proposal must include a breakout by year by cost element, showing the present value of projected restructuring costs and projected restructuring savings.
(4) Notify major buying activities of contractor restructuring actions and inform them about any potential monetary impacts on major weapons programs, when known.
(5) Upon receipt of the contractor's proposal, as soon as practicable, adjust forward pricing rates to reflect the impact of projected restructuring savings. If restructuring costs are included in forward pricing rates prior to execution of an advance agreement in accordance with paragraph (d)(8) of this subsection, the contracting officer shall include a repricing clause in each fixed-price action that is priced based on the rates. The repricing clause must provide for a downward price adjustment to remove restructuring costs if the certification, or determination, or both, as applicable, required by paragraph (c)(1)(iv) of this subsection is not obtained.
(6) Upon receipt of the contractor's proposal, immediately request an audit review of the contractor's proposal.
(7) Upon receipt of the audit report, determine if restructuring savings will exceed restructuring costs on a present value basis. However, for business combinations that occur on or after October 1, 1996, the audited projected savings for DoD must exceed the costs allowed by a factor of at least two to one on a present value basis, unless the determination in paragraph (c)(1)(iv)(B)
(8) Negotiate an advance agreement with the contractor setting forth, at a minimum, a cumulative cost ceiling for restructuring projects and, when necessary, a cost amortization schedule. The costs may not exceed the amount of projected restructuring savings on a present value basis. The advance agreement shall not be executed until the certification, or determination, or both, as applicable, required by paragraph (c)(1)(iv) of this subsection is obtained.
(9) Submit to the Director of Defense Procurement, Office of the Under Secretary of Defense (Acquisition & Technology), ATTN: OUSD (A&T) DP/CPF, a recommendation for certification, or determination, or both, as applicable. Include the information described in paragraph (e) of this subsection.
(10) Consult with the Director of Defense Procurement, Office of the Under Secretary of Defense (Acquisition & Technology), when paragraph (c)(1) (iv)(B)
(e)
(2) The contractor's restructuring proposal.
(3) The proposed advance agreement.
(4) The audit report.
(5) Any other pertinent information.
(6) The cognizant ACO's recommendation for certification, or determination, or both, as applicable. This recommendation must clearly indicate one of the following, consistent with paragraph (c)(1)(iv) of this subsection:
(i) Contractor projections of future cost savings resulting for DoD from the
(ii) The audited projected savings for DoD will exceed the costs allowed by a factor of at least two to one.
(iii) The business combination will result in the preservation of a critical capability that might otherwise be lost to DoD, and the audited projected savings will exceed the costs allowed.
(1) Pursuant to section 841 of the National Defense Authorization Act for Fiscal Year 1994 (Pub. L. 103-160), no limitation may be placed on the reimbursement of otherwise allowable indirect costs incurred by an institution of higher education under a DoD contract awarded on or after November 30, 1993, unless that same limitation is applied uniformly to all other organizations performing similar work under DoD contracts. The 26 percent limitation imposed on administrative indirect costs by OMB Circular No. A-21 shall not be applied to DoD contracts awarded on or after November 30, 1993, to institutions of higher education because the same limitation is not applied to other organizations performing similar work.
(2) The cognizant administrative contracting officer may waive the prohibition in 231.303(1) if the governing body of the institution of higher education requests the waiver to simplify the institution's overall management of DoD cost reimbursements under DoD contracts.
(3) Under 10 U.S.C. 2249, the costs cited in 231.205-22(a) are unallowable.
Under 10 U.S.C. 2249, the costs cited in 231.205-22(a) are unallowable.
Under 10 U.S.C. 2249, the costs cited in 231.205-22(a) are unallowable.
41 U.S.C. 421 and 48 CFR chapter 1.
Departments and agencies in accordance with department/agency procedures, shall prepare and submit to the Under Secretary of Defense (Acquisition and Technology), through the Director of Defense Procurement, annual reports (Report Control Symbol DD-ACQ(A) 1891) containing the information required by FAR 32.006-5.
(a) The Director of Defense Procurement, Office of the Under Secretary of Defense (Acquisition and Technology) (OUSD(A&T)DP) is responsible for ensuring uniform administration of DoD contract financing, including DoD contract financing policies and important related procedures. Agency discretion under FAR Part 32 is at the DoD level and is not delegated to the departments and agencies. Proposals by the departments and agencies, to exercise agency discretion, shall be submitted to OUSD(A&T)DP through the DoD Contract Finance Committee (see 232.071).
(b) Departments and agencies are responsible for their day-to-day contract financing operations. Refer specific cases involving financing policy or important procedural issues to
(c) The Under or Assistant Secretary, or other designated official, responsible for the comptroller function within the department or agency is the focal point for financing matters at the department/agency headquarters. Departments and agencies may establish contract financing offices at operational levels.
(1) Department/agency contract financing offices are—
(i) Army: Office of the Assistant Secretary of the Army (Financial Management);
(ii) Navy: Office of the Assistant Secretary of the Navy (Financial Management and Comptroller), Office of Financial Operations;
(iii) Air Force: Air Force Contract Financing Office (SAF/FMPB);
(iv) Defense agencies: Office of the agency comptroller.
(2) Contract financing offices should participate in—
(i) Developing regulations for contract financing;
(ii) Developing contract provisions for contract financing; and
(iii) Resolving specific cases that involve unusual contract financing requirements.
(a) The Contract Finance Committee consists of—
(1) A representative of OUSD(A&T)DP, serving as the Chair;
(2) A representative of the Comptroller of the Department of Defense;
(3) A representative of the Defense Finance and Accounting Service;
(4) A representative of the Civilian Agency Acquisition Council (for matters pertaining to the FAR);
(5) A representative of the National Aeronautics and Space Administration (for matters pertaining to the FAR);
(6) An advisory consultant from the Defense Contract Audit Agency; and
(7) Two representatives of each military department and the Defense Logistics Agency (one representing contracting and one representing the contract finance office).
(b) The Committee—
(1) Advises and assists OUSD(A&T)DP in ensuring proper and uniform application of policies, procedures, and forms;
(2) Is responsible for formulating, revising, and promulgating uniform contract financing regulations;
(3) May recommend to the Secretary of Defense through OUSD(A&T)DP further policy directives on financing; and
(4) Meets at the request of the Chair or a member.
Use the policies and procedures in this section in determining the financial capability of current or prospective contractors.
The contracting officer shall perform a financial review when the contracting officer does not otherwise have sufficient information to make a positive determination of financial responsibility. In addition, the contracting officer shall consider performing a financial review—
(a) Prior to award of a contract, when—
(1) The contractor is on a list requiring preaward clearance or other special clearance before award;
(2) The contractor is listed on the Consolidated List of Contractors Indebted to the Government (Hold-Up List), or is otherwise known to be indebted to the Government;
(3) The contractor may receive Government assets such as contract financing payments or Government property;
(4) The contractor is experiencing performance difficulties on other work; or
(5) The contractor is a new company or a new supplier of the item.
(b) At periodic intervals after award of a contract, when—
(1) Any of the conditions in paragraphs (a)(2) through (a)(5) of this subsection are applicable; or
(2) There is any other reason to question the contractor's ability to finance performance and completion of the contract.
(a) The contracting officer shall obtain the type and depth of financial and other information that is required to establish a contractor's financial capability or disclose a contractor's financial condition. While the contracting officer should not request information that is not necessary for protection for the Government's interests, the contracting officer must insist upon obtaining the information that is necessary. The unwillingness or inability of a contractor to present reasonably requested information in a timely manner, especially information that a prudent business person would be expected to have and to use in the professional management of a business, may be a material fact in the determination of the contractor's responsibility and prospects for contract completion.
(b) The contracting officer shall obtain the following information to the extent required to protect the Government's interest. In addition, if the contracting officer concludes that information not listed in paragraphs (b)(1) through (b)(10) of this subsection is required to comply with 232.072-1, that information should be requested. The information must be for the person(s) who are legally liable for contract performance. If the contractor is not a corporation, the contracting officer shall obtain the required information for each individual/joint venturer/partner:
(1) Balance sheet and income statement—
(i) For the current fiscal year (interim);
(ii) For the most recent fiscal year and, preferably, for the 2 preceding fiscal years. These should be certified by an independent public accountant or by an appropriate officer of the firm; and
(iii) Forecasted for each fiscal year for the remainder of the period of contract performance.
(2) Summary history of the contractor and its principal managers, disclosing any previous insolvencies—corporate or personal, and describing its products or services.
(3) Statement of all affiliations disclosing—
(i) Material financial interests of the contractor;
(ii) Material financial interests in the contractor;
(iii) Material affiliations of owners, officers, directors, major stockholders; and
(iv) The major stockholders if the contractor is not a widely-traded, publicly-held corporation.
(4) Statement of all forms of compensation to each officer, manager, partner, joint venturer, or proprietor, as appropriate—
(i) Planned for the current year;
(ii) Paid during the past 2 years; and
(iii) Deferred to future periods.
(5) Business base and forecast that—
(i) Shows, by significant markets, existing contracts and outstanding offers, including those under negotiation; and
(ii) Is reconcilable to indirect cost rate projections.
(6) Cash forecast for the duration of the contract (see 232.072-3).
(7) Financing arrangement information that discloses—
(i) Availability of cash to finance contract performance;
(ii) Contractor's exposure to financial crisis from creditor's demands;
(iii) Degree to which credit security provisions could conflict with Government title terms under contract financing;
(iv) Clearly stated confirmations of credit with no unacceptable qualifications;
(v) Unambiguous written agreement by a creditor if credit arrangements include deferred trade payments or creditor subordinations/repayment suspensions.
(8) Statement of all state, local, and Federal tax accounts, including special mandatory contributions, e.g., environmental superfund.
(9) Description and explanation of the financial effect of issues such as—
(i) Leases, deferred purchase arrangements, or patent or royalty arrangements;
(ii) Insurance, when relevant to the contract;
(iii) Contemplated capital expenditures, changes in equity, or contractor debt load;
(iv) Pending claims either by or against the contractor;
(v) Contingent liabilities such as guarantees, litigation, environmental, or product liabilities;
(vi) Validity of accounts receivable and actual value of inventory, as assets; and
(vii) Status and aging of accounts payable.
(10) Significant ratios such as—
(i) Inventory to annual sales;
(ii) Inventory to current assets;
(iii) Liquid assets to current assets;
(iv) Liquid assets to current liabilities;
(v) Current assets to current liabilities; and
(vi) Net worth to net debt.
(a) A contractor must be able to sustain a sufficient cash flow to perform the contract. When there is doubt regarding the sufficiency of a contractor's cash flow, the contracting officer should require the contractor to submit a cash flow forecast covering the duration of the contract.
(b) A contractor's inability of refusal to prepare and provide cash flow forecasts or to reconcile actual cash flow with previous forecasts is a strong indicator of serious managerial deficiencies or potential contract cost or performance problems.
(c) Single or one-time cash flow forecasts are of limited forecasting power. As such, they should be limited to preaward survey situations. Reliability of cash flow forecasts can be established only by comparing a series of previous actual cash flows with the corresponding forecasts and examining the causes of any differences.
(d) Cash flow forecasts must—
(1) Show the origin and use of all material amounts of cash within the entire business unit responsible for contract performance, period by period, for the length of the contract (or until the risk of a cash crisis ends); and
(2) Provide an audit trail to the data and assumptions used to prepare it.
(e) Cash flow forecasts can be no more reliable than the assumptions on which they are based. Most important of these assumptions are—
(1) Estimated amounts and timing of purchases and payments for materials, parts, components, subassemblies, and services;
(2) Estimated amounts and timing of payments of purchase or production of capital assets, test facilities, and tooling;
(3) Amounts and timing of fixed cash charges such as debt installments, interest, rentals, taxes, and indirect costs;
(4) Estimated amounts and timing of payments for projected labor, both direct and indirect;
(5) Reasonableness of projected manufacturing and production schedules;
(6) Estimated amounts and timing of billings to customers (including progress payments), and customer payments;
(7) Estimated amounts and timing of cash receipts from lenders or other credit sources, and liquidation of loans; and
(8) Estimated amount and timing of cash receipt from other sources.
(f) The contracting officer should review the assumptions underlying the cash flow forecasts. In determining whether the assumptions are reasonable and realistic, the contracting officer should consult with—
(1) The contractor;
(2) Government personnel in the areas of finance, engineering, production, cost, and price analysis; or
(3) Prospective supply, subcontract, and loan or credit sources.
(e)(2) Progress payments based on percentage or stage of completion are authorized only for contracts for construction (as defined in FAR 36.102),
(a) The contracting officer may establish provisional delivery payments to pay contractors for the costs of supplies and services delivered to and accepted by the Government under the following contract actions if undefinitized:
(1) Letter contracts contemplating a fixed-price contract.
(2) Orders under basic ordering agreements.
(3) Spares provisioning documents annexed to contracts.
(4) Unpriced equitable adjustments on fixed-price contracts.
(5) Orders under indefinite-delivery contracts.
(b) Provisional delivery payments shall be—
(1) Used sparingly;
(2) Priced conservatively; and
(3) Reduced by liquidating previous progress payments in accordance with the Progress Payments clause.
(c) Provisional delivery payments shall not—
(1) Include profit;
(2) Exceed funds obligated for the undefinitized contract action; or
(3) Influence the definitized contract price.
See 232.070 for offices to be consulted regarding financial matters with DoD.
(a)(2) When determining whether an offeror's financial condition is adequate security, see 232.072-2 and 232.072-3 for guidance. It should be noted that an offeror's financial condition may be sufficient to make the contractor responsible for award purposes, but may not be adequate security for commercial contract financing.
(d)
(f)
(i)
(ii)
(g)
(b)(2) If the contract contains foreign military sales requirements, each approval shall specify the amount of contract financing to be charged to each country's account.
(a) The use of guaranteed loans as a contract financing mechanism requires the availability of certain congressional authority. The DoD has not requested such authority in recent years, and none is now available.
(a)(9) The requirements of FAR subpart 32.4 do not apply to advertisements in high school and college publications for military recruitment efforts under 10 U.S.C. 503 when the contract cost does not exceed $500.
To ensure uniform application of this subpart (see FAR 32.402(e)(1)), the departmental/agency contract financing office shall prepare the documents required by FAR 32.409-1 (e) and (f).
(b) If an advance payment procedure is used without a special bank account, replace paragraph (a)(4) of the Findings, Determination, and Authorization for Advance Payments at FAR 32.410 with:
(4) The proposed advance payment clause contains appropriate provisions as security for advance payments. These provisions include a requirement that the outstanding advance payments will be liquidated from cost reimbursements as they become due the contractor. This security is considered adequate to protect the interest of the Government.
(a) Use the clause at 252.232-7000, Advance Payment Pool, in any contract that will be subject to the terms of an advance payment pool agreement with a nonprofit organization or educational institution. Normally, use the clause in all cost reimbursement type contracts with the organization or institution.
(b) Use the clause at 252.232-7001, Disposition of Payments, in contracts when payments under the contract are to be made by a disbursing office not designated in the advance payment pool agreement.
(c) Use the clause at 252.232-7005, Reimbursement of Subcontractor Advance Payments-DoD Pilot Mentor-Protege Program, when advance payments will be provided by the contractor to a subcontractor pursuant to an approved mentor-protege agreement (See subpart 219.71).
(a) An advance payment pool agreement—
(1) Is a means of financing the performance of more than one contract held by a single contractor;
(2) Is especially convenient for the financing of cost-type contracts with nonprofit educational or research institutions for experimental or research and development work when several contracts require financing by advance payments. When appropriate, pooled advance payments may also be used to finance other types of contracts held by a single contractor; and
(3) May be established—
(i) Without regard to the number of appropriations involved;
(ii) To finance contracts for one or more department(s) or contracting activity(ies); or
(iii) In addition to any other advance payment pool agreement at a single contractor location when it is more convenient or otherwise preferable to have more than one agreement.
In DoD, customary progress payments may be either uniform or flexible (FAR 32.501-1(a)). See also 232.501-1 and 232.502-1-71.
(a)(i) The customary uniform progress payment rate for DoD contracts is 75 percent for large businesses, 90 percent for small businesses, and 95 percent for small disadvantaged businesses.
(ii) The progress payment rates applicable to foreign military sale requirements are the same rates applicable to DoD requirements.
(iii) For customary flexible progress payments, determine the appropriate rate using the appropriate CASH computer program (see 232.502-1-71).
(a) Unusual progress payment arrangements require the advance approval of the USD(A&T)DP. Contracting officers shall submit all unusual progress payment requests to the department or agency contract financing office for approval, coordination with the Contract Finance Committee (232.171), and submission to the USD(A&T)DP.
(b) The contracting officer may approve progress payments when the contract price exceeds the funds obligated under the contract; provided, the contract contains an appropriate Limitation of Funds clause. However, the contracting officer shall limit such payments to the lesser of—
(i) The applicable rate (i.e., the lower of the progress payment rate, the liquidation rate, or the loss-ratio adjusted rate); or
(ii) 100 percent of the funds obligated.
(b)(1) If the contractor is a small disadvantaged business, progress payments may be provided when the contract will involve $50,000 or more.
(a) Foreign military sale (FMS) progress payments apply to DoD acquisitions on behalf of foreign governments or international organizations (Section 22 of the Arms Export Control Act).
(b) FMS progress payments do not apply to acquisitions—
(1) For replenishing U.S. Government inventories or stocks; and
(2) Made under DoD cooperative logistic support arrangements.
(a)
(2) Progress payment amounts that are determined by using customary uniform rates are insensitive to the other factors influencing contractor investment in work in process inventory. Consequently, contractor investments in work in process inventory vary among contractors and contracts.
(3) Flexible progress payment rates are designed to tailor the progress payment rate to more closely match the contractor's cash needs for financing contract performance. The flexible rate is expressed as a percentage which is applied to costs to determine the amount payable as a progress payment, in the same manner as customary uniform rates are applied.
(4) For flexible progress payments, cash needs are measured and projected based on the investment required for the work in process inventory over the life of the contract. Total investment is measured by a weighted average of total costs paid by the contractor. The contractor's investment is the weighted average of the amount not paid by the Government.
(5) DoD, as a matter of policy, requires contractors to retain a minimum investment level in work in process inventory over the life of the contract (see Table 32-1, Customary Uniform Progress Payment Rates). This minimum investment level is based on the customary uniform progress payment rate and its related investment percentage. Accordingly, the DoD will make progress payments at a rate (expressed as a whole number) that is the highest rate which yields a corresponding investment by the contractor in work in process inventory of not less than the minimum investment percentage.
(6) The customary flexible progress payment rate will be determined by using the DoD Cash Flow Computer Model. The rate computed shall not—
(i) Exceed 100 percent; or
(ii) Be less than the customary uniform progress payment rate that would have been applied to the contract in the absence of customary flexible progress payments.
(7) Table 32-1, Customary Uniform Progress Payment Rates, shows the customary uniform progress payment rates for other than small or small disadvantaged businesses (see also 232.501-1), minimum contractor investment (except for contracts funded with FY87 appropriations), and the applicable DoD Cash Flow Computer Model. For contracts or line items that are funded with FY87 appropriations, a contractor must retain at least a 25 percent investment in work in process inventory over the life of the contract or over the contract performance period applicable to the contract line item.
(b)
(i) The contractor requests flexible progress payments;
(ii) The contractor agrees to the requirements of this section;
(iii) The contract contains the clause at FAR 52.232-16, Progress Payments. However, small business contractors may get flexible progress payments if they agree to use the clause at FAR 52.232-16 without its Alternate I; and
(iv) The criteria in paragraphs (b)(2) and (3) of this subsection are met.
(2) Do not use flexible progress payments for—
(i) Sealed bid contracts;
(ii) Undefinitized contract actions; or
(iii) Contracts awarded and performed entirely outside of the United States, its possessions or territories.
(3) Contractors who submit cost or pricing data, as defined in FAR 15.401, for negotiated fixed-price contracts in excess of $1 million may request flexible progress payments.
(4) Subcontractors who request flexible progress payments, meet the criteria in paragraph (b)(3) of this subsection, and agree to the requirements of this subsection are to receive flexible progress payments. The prime contractor determines the flexible progress payment rate without regard to the rate in the prime contract. In determining the appropriate customary flexible rate, the prime contractor will use the DoD Cash Flow Computer Model and review the cash flow data provided by the subcontractor.
(5) Prior to contract award, the contracting officer shall determine the customary flexible progress payment
(i) The model takes into account key cash flow factors including contract cost profile, delivery schedules, subcontractor progress payments, liquidation rates, and payment/reimbursement cycles. For contracts funded with FY87 appropriations, use the CASH-IV model.
(ii) From time to time the Department of Defense may change the uniform progress payment rate and/or the minimum contractor investment rate, which may have an effect upon the variables within the DoD Cash Flow Computer Program. In order to avoid frequent revision and redistribution of the computer program, the program is designed to permit use of either a particular model (CASH-II, CASH-V, etc.) or a program option to input the equivalent uniform progress payment rate and minimum contractor investment rate (90%/5%, 80%/20%, etc.), as shown in the table at (a)(7). Either method will result in the same flexible progress payment rate calculation. When the Cash Flow Computer Program does not contain the model needed for a particular situation, the contracting officer shall use the program option.
(6) If the contractor requests flexible progress payments after contract award or definitization, the contracting officer may, if warranted, grant their use. However, the contractor must provide adequate new consideration (see FAR 32.501-4).
(c)
(i) Actual and projected incurred cost, broken down by element of cost and by month, for the duration of the contract;
(ii) Float times for each element of cost;
(iii) Dates and lag times of actual and projected progress payment and delivery payment receipts; and
(iv) Associated contract price and profit percentage.
(2) Contracting officers shall verify the cash flow data using the procedures normally used to verify contractor cost and pricing data, and establish the customary flexible progress payment rate during the negotiation of the contract price.
(3) If any customary flexible progress payment rate is later determined to be overstated because factual data submitted in support of the rate computation was not current, accurate, or complete at the time the rate was established, the flexible progress payment clause at 252.232-7003 provides for—
(i) Reduction of the flexible progress payment rate; and
(ii) Contractor payment of interest.
(4) The contracting officer will assess the interest charge on the amount of the overpayment resulting from facts that were not current, accurate, or complete, whether or not the overpayment has been liquidated. Calculate the interest from the date of the overpayment to the date of liquidation of the overpayment. In determining the amount of interest, the contracting officer may determine an average overpayment amount and duration as the basis for the interest computation. Interest rates change periodically; therefore, calculate average amounts and durations separately for each interest period that has a different interest rate.
(5) Administrative contracting officers are encouraged to establish advance agreements at contractor locations for payment float and lag times which are common to several contracts. Float and lag times may vary significantly from one contract to another due to variances in efficiency at different payment offices or due to differing procedures for high dollar versus low dollar value contracts. It may, therefore, be appropriate to establish advance agreements on several different float and lag profiles to suit different contract situations.
(d)
(i) Apply the new customary flexible progress payment rate to the next contractor progress payment request; and
(ii) Adjust the unliquidated progress payment balance.
(2) Either the Government or the contractor may request a rate review at any time to determine if the computed investment percentage in work in process inventory is outside of the investment tolerance in paragraph (d)(1) of this subsection. For contracts funded with FY87 appropriations, the investment range is 23 to 27 percent with a target of 25 percent.
(3) The administrative contracting officer shall assess changes in the following factors during each periodic review required by FAR 32.503-5 and shall review the customary flexible progress payment rate whenever there has been—
(i) A significant change in the float or lag factors;
(ii) A significant change in the delivery schedule; or
(iii) Substantial work added to or deleted from the contract.
(e)
(f)
(a) Use the clause at 252.232-7002, Progress Payments for Foreign Military Sales Acquisitions, in any contract that provides for progress payments and contains foreign military sale requirements.
(b) Use the clauses at 252.232-7003, Flexible Progress Payments, and 252.232-7004, DoD Progress Payment Rates, in contracts using a customary flexible progress payment rate.
(c) Use the clause at 252.232-7004, DoD Progress Payment Rates, in addition to the clauses prescribed at FAR 32.502-4.
(b)
(g)
(i) Except as provided in paragraph (g)(ii) of this subsection, the contracting officer shall prepare a supplementary analysis of the contractor's request for progress payments and calculate the loss ratio adjustment using the procedures in FAR 32.503-6(g).
(ii) The contracting officer may request the contractor to prepare the supplementary analysis as an attachment to the progress payment request when the contracting officer determines that the contractor's methods of estimating the “Costs to Complete” are reliable, accurate, and not susceptible to improper influences.
(iii) To maintain an audit trail and permit verification of calculations, do not make the loss ratio adjustments by altering or replacing data on the contractor's original request for progress payment (SF 1443, Contractor's Request for Progress Payment, or computer generated equivalent).
(d) An administrative contracting officer (ACO) determination that the contractor's material management and accounting system conforms to the standard at 252.242-7004(f)(7) constitutes the contracting officer approval requirement of FAR 32.503-15(d).
(i) The contractor retains records of the transfer activity that took place in the prior month;
(ii) The contractor prepares, at least monthly, a summary of the transfer activity that took place in the prior month; and
(iii) The summary report includes as a minimum, the total number and dollar value of transfers.
(b) Disbursing officers are those officials designated to make payments under a contract or to receive payments of amounts due under a contract. At installations where integrated accounting is in effect, the finance and accounting officer is a disbursing officer. The disbursing officer is responsible for determining the amount and collecting contract debts whenever overpayments or erroneous payments have been made. The disbursing officer also has primary responsibility when the amounts due and dates for payment are contained in the contract, and a copy of the contract has been furnished to the disbursing officer with notice to collect as amounts become due.
(c)(9)(vii) Upon transfer of a case to the contract financing office, the contracting officer shall close the debt record by reference to the date of transfer.
(a)(i) For contract debts resulting from other than a termination for default, the office which first determines an amount due, whether it be the contract administration office, the contracting office, the disbursing office, or the selling office/agency, shall—
(A) Make a demand for payment; and
(B) Provide a copy of the demand to the payment office cited in the contract.
(ii) For contract debts resulting from a termination for default, the contracting officer shall make the demand and direct the debtor to make such payment to the designated office.
(b)(3) The contracting office shall forward deferment requests to the contract financing office of the contracting department or agency for a decision on granting the deferment.
Only the department/agency contract financing offices (232.108(1)) are authorized to compromise debts covered by this subpart.
(a) The DoD Contract Finance Committee, with the approval of the USD(A&T)DP, may exempt the contracts in FAR 32.617(a) (2) through (5) and other contracts, in exceptional circumstances, from the administrative interest charges required by this subpart.
(a)(7) Other exceptions—
(A) Contracts for instructions of military or ROTC personnel at civilian schools, colleges, and universities;
(B) Basic agreements with telephone companies for communications services and facilities, and purchases under such agreements; and
(C) Transportation contracts with common carriers for common carrier services.
Disbursing officers will transfer responsibility for debt collection to departmental/agency contract financing offices in accordance with comptroller regulations. Notwithstanding the transfer of the debt collection responsibility, contracting officers shall continue to provide assistance as requested by the debt collection office.
(a) For those debts covered by this subpart, the department or agency
(1) Have been transferred to a contract financing office;
(2) Are on the way to a contract financing office at the inception of bankruptcy or insolvency proceedings;
(3) Are pending and not forwarded to a contract financing office at the inception of bankruptcy or insolvency proceedings; and
(4) Are the result of bankruptcy or insolvency proceedings.
(b) The contract financing office or other office designated within a department or agency will furnish proof of claims to the Department of Justice.
(c) The office of origin of a debt will provide, as soon as possible, information on a bankruptcy, insolvency, reorganization, or rearrangement to the office designated within a department/agency to receive this information.
(d) The information and proof of claim requirements in paragraphs (b) and (c) of this section do not apply to debts of less than $600.
Fixed-price contracts shall be fully funded except as permitted by 232.703-1.
(1) A fixed-price contract may be incrementally funded only if—
(i) The contract is funded with research and development appropriations;
(ii) Congress has otherwise incrementally appropriated program funds; or
(iii) The head of the contracting activity approves the use of incremental funding for either base services contracts or hazardous/toxic waste remediation contracts.
(2) Incrementally funded fixed-price contracts shall be fully funded as soon as practicable after full funding is available.
Annual military construction appropriations acts restrict the use of funds appropriated by the acts for payments under cost-plus-fixed-fee contracts (see 216.306(c)).
(a) Upon receipt of the contractor's notice under paragraph (c) of the clause at 252.232-7007, Limitation of Government's Obligation, the contracting officer shall promptly provide written notice to the contractor that the Government is—
(1) Allotting additional funds for continued performance and increasing the Government's limitation of obligation in a specified amount;
(2) Terminating the contract; or
(3) Considering whether to allot additional funds; and
(i) The contractor is entitled by the contract terms to stop work when the Government's limitation of obligation is reached; and
(ii) Any costs expended beyond the Government's limitation of obligation are at the contractor's risk.
(b) Upon learning that the contract will receive no further funds, the contracting officer shall promptly give the contractor written notice of the Government's decision and terminate for the convenience of the Government.
(c) The contracting officer shall ensure that, in accordance with paragraph (b) of the clause at 252.232-7007, Limitation of Government's Obligation, sufficient funds are allotted to the contract to cover the total amount payable to the contractor in the event of termination for the convenience of the Government.
Use the clause at 252.232-7007, Limitation of Government's Obligation, in solicitations and resultant incrementally funded fixed-price contracts. The contracting officer may revise the contractor's notification period, in paragraph (c) of the clause, from “ninety” to “thirty” or “sixty” days, as appropriate.
(b) Only contracts for personal services may prohibit the assignment of claims.
(d) Pursuant to Section 3737(e) of the Revised Statutes (41 U.S.C. 15), and in accordance with Presidential delegation dated October 3, 1995, Secretary of Defense delegation dated February 5, 1996, and Under Secretary of Defense for Acquisition and Technology delegation dated February 23, 1996, the Director of Defense Procurement determined on May 10, 1996, that a need exists for DoD to agree not to reduce or set off any money due or to become due under the contract when the proceeds under the contract have been assigned in accordance with the Assignment of Claims provision of the contract. This determination was published in the
(b) The assignee shall forward—
(i) To the administrative contracting officer (ACO), a true copy of the instrument of assignment and an original and three copies of the notice of assignment. The ACO shall acknowledge receipt by signing and dating all copies of the notice of assignment and shall—
(A) File the true copy of the instrument of assignment and the original of the notice in the contract file;
(B) Forward two copies of the notice to the disbursing officer of the payment office cited in the contract;
(C) Return a copy of the notice to the assignee; and
(D) Advise the contracting officer of the assignment.
(ii) To the surety or sureties, if any, a true copy of the instrument of assignment and an original and three copies of the notice of assignment. The surety shall return three acknowledged copies of the notice to the assignee, who shall forward two copies to the disbursing officer designated in the contract.
(iii) To the disbursing officer of the payment office cited in the contract, a true copy of the instrument of assignment and an original and one copy of the notice of assignment. The disbursing officer shall acknowledge and return to the assignee the copy of the notice and shall file the true copy of the instrument and original notice.
(a)(1) Use the clause at 252.232-7008, Assignment of Claims (Overseas), instead of the clause at FAR 52.232-23, Assignment of Claims, in solicitations and contracts when contract performance will be in a foreign country.
(2) Use Alternate I with the clause at FAR 52.232-23, Assignment of Claims, unless otherwise authorized under 232.803(d).
DoD policy is to assist small disadvantaged business concerns by paying them as quickly as possible after invoices are received and before normal payment due dates established in the contract (see 232.905(2)).
(1) In most cases, Government acceptance or approval can occur within
(2) Designated payment offices are encouraged to pay small disadvantaged business (SDB) concerns as quickly as possible after invoices are received and before normal payment due dates established in the contract. The restrictions of FAR 32.903 prohibiting early payment do not apply to invoice payments made to SDBs. Contractors shall not, however, be entitled to interest penalties if invoice payments are not made before the normal payment due dates established in the contract.
(f)(6) DoD Manual 4000.25-5-M, Military Standard Contract Administration Procedures (MILSCAP), authorizes electronic signature of receiving reports.
(a)(i) DoD policy is to make contract financing payments as quickly as possible. Generally, the contracting officer shall insert the standard due dates of 7 days for progress payments and 14 days for interim payments on cost type contracts in subparagraphs (b)(2) of the Prompt Payment clauses at FAR 52.232-25, 52.232-26, and 52.232-27.
(ii) The contracting officer should coordinate payment terms with offices that will be involved in the payment process to ensure that terms specified can be met. Where justified, the contracting officer may insert a due date greater than but not less than the standard. In determining payment terms, consider—
(A) Geographical separation;
(B) Workload;
(C) Contractor ability to submit a proper request; and
(D) Other factors that could affect timing of payment.
(d) The contracting officer shall use the following standard prompt payment terms for performance-based payments: The contractor entitlement date, if any, specified in the contract, or 14 days after receipt by the designated billing office of a proper request for payment, whichever is later.
(c)
(b)(2) If the contract contains foreign military sales requirements, each approval shall specify the amount of contract financing to be charged to each country's account.
(a) If the payment office is not capable of making payment by electronic funds transfer (EFT), the payment office is relieved of the requirement to pay by EFT is DoD complies with 31 CFR 208.3, which requires written notice and submittal of an implication plan to the Department of the Treasury, Financial Management Service.
If the solicitation or contract includes the clause at 252.204-7004, Required Central Contractor Registration, and payment under the contract will be made by electronic funds transfer, use the clause at 252.232-7009, Payment by Electronic Funds Transfer (CCR), instead of the clause at FAR 52.232-33, Mandatory Information for Electronic Funds Transfer Payment, or the clause at FAR 52.232-34, Optional Information for Electronic Funds Transfer Payment.
41 U.S.C. 421 and 48 CFR chapter 1.
When it would be helpful in reviewing the current claim, the contracting officer should get information on claims previously filed by the contractor with other contracting officers.
See 10 U.S.C. 2410(b) for limitations on Congressionally directed payment of a claim under the Contract Disputes Act of 1978, a request for equitable adjustment to contract terms, or a request for relied under Pub. L. 85-804.
DFARS 243.105(a) limits contracting officer authority.
Use Alternate I of the clause at FAR 52.233-1, Disputes, when—
(1) The acquisition is for—
(i) Aircraft
(ii) Spacecraft and launch vehicles
(iii) Naval vessels
(iv) Missile systems
(v) Tracked combat vehicles
(vi) Related electronic systems;
(2) The contracting officer determines that continued performance is—
(i) Vital to the national security, or
(ii) Vital to the public health and welfare; or
(3) The head of the contracting activity determines that continued performance is necessary pending resolution of any claim that might arise under or be related to the contract.
Use the clause at 252.233-7001, Choice of Law (Overseas), in solicitations and contracts when contract performance will be outside of the United States, it possessions, and Puerto Rico, unless otherwise provided for in a government-to-government agreement.