Search This Blog

Showing posts with label Restrictive Rights in Software. Show all posts
Showing posts with label Restrictive Rights in Software. Show all posts

Monday, August 3, 2026

Protecting Intellectual Property And Proprietary Data In Federal Government Contracting






Contractual relationships established directly with the US government or subcontracts and purchase orders under government contracts with other companies must contain provisions for the protection of intellectual property and proprietary data. This article will address the major processes by which that protection is achieved.

RIGHTS IN TECHNICAL DATA AND SOFTWARE

The Defense Federal Acquisition Regulation (DFAR) contains the most widely used provisions by a federal agency that allow a contractor, subcontractor or supplier under government contracts to assert ownership or protective rights for specific technical data and software. Keep in mind that the more a company has invested in a technology, a product or a system the higher the level of protection available under the DFAR. If the government has or will invest in the technical data and software then the level of protection that can be asserted diminishes and the government begins to assume ownership and attendant control of the related intellectual property.

It is important during the solicitation and proposal stage to assert rights in technical data and software so the business relationship is clearly understood by all parties and appropriate protective markings, licensing and related measures can be covered in the contractual documentation. The following information in the DFAR should be studied to ascertain how to appropriately assert rights during proposals to the government and to prime contactors:

SUBPART 227.71—TECHNICAL DATA AND ASSOCIATED RIGHTS

SUBPART 227.72—COMPUTER SOFTWARE, COMPUTER SOFTWARE DOCUMENTATION, AND ASSOCIATED RIGHTS

The government does not sign agreements to protect specific data, abiding instead by the DFAR-specified assertions regarding ownership and use of technical data and computer software as they are negotiated in contracts. The government will comply with specific marking and identification of proprietary data. Details on these markings are provided at the conclusion of this article.

NON-DISCLOSURE AGREEMENTS BETWEEN COMPANIES

When two companies begin an exchange of information that may lead to a mutually exclusive business arrangement under a government contract, a Non-Disclosure Agreement (NDA) is generally signed to protect proprietary data.

The first page of such an agreement is on the left in the illustration below. The entire document may be obtained free of charge by downloading it at the "Box Net" cubicle in the right margin of this site.

TEAMING AGREEMENTS BETWEEN COMPANIES

When two companies agree to form a mutually exclusive agreement to prepare a proposal as a team to a government agency a teaming agreement is generally executed. The first page of such an agreement is on the right in the illustration below . The entire document may be obtained free of charge by downloading it at the "Box Net" cubicle in the right margin of this site.

A teaming agreement remains in force until it is replaced by a subcontract from the lead company to the following company upon award of the prime contract. In the case of a joint venture, the prime contract award results in two contracts from the joint venture contract level to the respective participating company levels.


PLEASE CLICK ON ILLUSTRATION OR DOWNLOAD TO ENLARGE

PROTECTING RATE INFORMATION BETWEEN COMPANIES

It is generally recognized by all industries participating in federal government contracting that internal overhead and G&A rates and the data that support them are proprietary data. The reason for the proprietary nature of rate data between companies is that in government work firms are teaming with each other exclusively on one project and competing against each other on additional contracts or projects at the same time.

Assuming everyone pays a generally similar labor rate on the market to retain employees and that fringe costs about the same for everyone, then overhead and G&A are what wins and loses jobs and specific, company internal overhead rates are very closely held.

Companies do not disclose the details of their rates to other companies and they do not expect to see another company's proprietary rate information. So companies view each other’s rate information on a fully loaded basis, meaning the total of the base cost, any proprietary indirect cost and an agreed upon profit percent.

If a prime contractor requests that subcontractor proprietary rate information be supplied with a proposal the detail should be double wrapped and the package stamped, 'Government Eyes Only'. The prime will then hand the package off to DCAA without opening it and receive only the fully loaded result of the burdened rate pricing.

DCAA or federal agency pricing analysts perform detail audits of subcontractor rate information but prime contractors are not provided the result. An audit statement by the government that the subcontractor detail rate support is acceptable or not acceptable is all that is provided to the prime contractor.

Government auditors do not make value judgments or negotiate; they review the logic and support for rates, check the math and provide a report to the government contracting officer who will conduct the negotiations, if any.

PROTECTIVE MARKINGS FOR PROPRIETARY DATA SUBMITTED TO THE GOVERNMENT AND TO A PRIME CONTRACTOR

Your proposal data may contain rate information, proprietary data or strategic technical solutions that you would not want to fall into the hands of a competitor. The government does not sign Proprietary Data Agreements (PDA's). Examples of the government's obligation to protect your information are covered under the DFAR rights in technical data and software assertions discussed above and in the following FAR clause that requires protective markings by you on the title page of your document and on each subsequent page.FAR 15.509 Limited use of data:

(a) A proposal may include data that the offeror does not want disclosed for any purpose other than evaluation. If the offeror wishes to restrict the proposal, the title page must be marked with the following legend:

"The data in this proposal shall not be disclosed outside the Government and shall not be duplicated, used, or disclosed in whole or in part for any purpose other than to evaluate the proposal; provided, that if a contract is awarded to this offeror as a result of or in connection with the submission of these data, the Government shall have the right to duplicate, use, or disclose the data to the extent provided in the contract. This restriction does not limit the Government's right to use information contained in the data if it is obtainable from another source without restriction."

(b) The offeror shall also mark each restricted sheet with the following legend:

"Use or disclosure of proposal data is subject to the restriction on the title page of this Proposal."

(c) The coordinating office shall return to the offeror any unsolicited proposal marked with a legend different from that provided in 15.509(a). The return letter will state that the proposal cannot be considered because it is impracticable for the Government to comply with the legend and that the agency will consider the proposal if it is resubmitted with the proper legend.

Monday, June 8, 2026

Practical Intellectual Property Management for Small Business Federal Government Contractors



INTRODUCTION

We have previously discussed Intellectual Property (IP) and Proprietary Data (PD) protection for small business:


The above posts discuss rights in technical data and software assertions, non-disclosure and teaming agreements as well as proprietary data protection involving the government and industry partners.

This article expands those discussions by offering practical operations guidelines involving IP protection for small business government contractors.

DEFINITIONS

The World Intellectual Property Organization defines IP as:

“….creations of the mind: inventions, literary and artistic works, and symbols, names, images, and designs used in commerce.

Industrial property, which includes inventions (patents), trademarks, industrial designs, and geographic indications of source; and Copyright, which includes literary and artistic works such as novels, poems and plays, films, musical works, artistic works such as drawings, paintings, photographs and sculptures, and architectural designs.    Rights related to copyright include those of performing artists in their performances, producers of phonograms in their recordings, and those of broadcasters in their radio and television programs.”


OWNERSHIP ENCOUNTERS AND CONTROLS

Bringing IP into existence requires that the tangible property as a result come under control.  For small business this is usually brought about by a series of encounters with IP.  They are discussed below in the relative order in which a small business encounters them.


Company Founding Personnel

A small business usually encounters IP and PD concerns when it is formed.  The operating agreement between the founders must address these matters from the perspective of who brings property to the venture and who owns it as well as the rights to the property developed thereafter. A typical operating agreement may be downloaded from the Box Net “References” cube in the right margin of this site.  Please examine it as a framework and add those elements that are unique to your enterprise.

Employees and Contractors

The next encounter usually entails employees or contractors who apply for work.  It is wise to inquire as a standard practice, and as part of an employment agreement or contract, whether or not an individual has signed a non-compete or proprietary data agreement with prior employers.  If they have, acquire a copy of the agreement and assess whether or not the employment of these personnel poses a risk of IP violations in terms of another company's property or their claim to ownership of what the candidate may develop on your behalf while in your employ. 

Make it clear in your agreements of hire and contracts that IP and PD that employees may participate in developing are the exclusive property of the company, that they will not own it and that they are expected to protect it, even when they leave your firm.

Industry Partners

Declare in your non-disclosure, teaming, and contract agreements the precise definition of the IP and PD ownership brought to the table and the exact share of ownership in subsequent development items.  Most firms use the efforts of their employees (labor records) as a basis to make these distinctions, but further specificity may be necessary on complex projects. 
 
Government Agencies and Prime Contractors

Ensure your policies and practices utilize assertions to document the ownership of IP and sound job cost accounting records for any IP developed at company expense, either in the past or during the course of a contract. The link below discusses the following major rights assertions in detail:

Unlimited Rights
Government Purpose Rights (GPR)
Limited Rights
Restricted Rights
Small Business Innovation Research (SBIR) Data Rights
Specifically Negotiated License Rights
Prior Government Rights
Commercial License Rights

CONCLUSION

Intellectual property and proprietary data protection should be tailored to your organization, its industry relationships, people and practices.  It must grow as the company grows, adapt to changing conditions and be ever-sensitive to risk.

The best intellectual property protections are well understood, practical, teaming relationships among partners, employees, industry and government.  All sides in such relationships lose if disclosure or violations occur. 

Establish sound operations practices and train to insure these practices meet the objectives discussed herein to protect your organization IP.