United States: Legending Your Technical Data May Differ For Government And Third Parties: Court Of Appeals Rules On The Boeing Technical Data Rights Case

On Monday, Dec. 21, the U.S. Court of Appeals for the Federal Circuit (Court of Appeals) issued its opinion in The Boeing Company v. the Secretary of the Air Force, 2019-2147, reversing and remanding the Armed Services Board of Contract Appeals (ASBCA) decisions in two cases, ASBCA Nos. 61387, 61388. The Court of Appeals opinion is available here. 

Background of Technical Data Rights

Since 1995, the DFARS has prescribed a series of very specific legends that contractors and subcontractors are to use when marking their technical data – or intellectual property, in government-speak. The applicable regulations, including the prescribed legends, are found in DFARS 252.227-7013(f) through 252.227-7017(f).

Technical data rights and the applicable legend vary by contract, but they are critical to the contractors' ability to restrict or limit the Government's use or right to distribute contractors' technical data. If a contractor fails to properly legend its technical data, the Government may – and likely will – treat that technical data as having been provided with unlimited rights. This means that the Government can do anything it wants to – including sharing the technical data with a contractor's competitors.

For example, the Government Purpose Rights legend would be marked as follows:

(End of Legend)

This legend and its brethren inform the Government about how and when the Government may use or disclose the technical data. For years, the Government has insisted on the precisely applicable legend, as written in the DFARS or corresponding contract clause, for the contractor's technical data to be protected.

The Boeing Second Legend

In 2017, defense-giant Boeing raised an interesting question. In addition to the prescribed legend required by the contract, Boeing had added a non-Government notice, informing third-parties that the technical data was Boeing proprietary and required Boeing's permission to use or disclose:

Boeing's basic premise was that the Government legend told the Government what it could and could not do, but it did not inform third parties, including competitors – who may have obtained access to the data through the Government. Without such notice, Boeing reasoned, how would its competitors and other companies know that the technical data belonged to Boeing, they did not have the right to use the technical data freely and without restriction. So, Boeing added the second legend.

The Government rejected double marking.

Boeing proposed an alternate second legend, and again the Government rejected it. Based on the language in Subsection (f) "only the following legends are authorized under this contract," the Government was of the opinion that the only marking permitted was the specific legend that corresponded with the contractual level of technical data rights.

Boeing disagreed, pointing out that its commercial rights against third parties were not being addressed under the prescribed legend. Eventually, Boeing asked for a Contracting Officer's Final Decision (COFD) and appealed that unfavorable decision to the ASBCA. Boeing argued that Subsection (f) only applied to any second legend that would act to limit the Government's rights, not third parties' rights. Boeing's second legend had no impact on Government rights because it was directed toward other parties. The ASBCA dismissed Boeing's motion for summary judgment, finding that Boeing's second legend contravened Subsection (f).

Court of Appeals Opinion

The Court of Appeals' decision provides contractors with valuable insight for its interpretation of Subsection (f) and the corresponding facts at hand. The court worked through a number of arguments raised by the Government, but continually returned to the "plain meaning" of the language in Subsection (f).

In the end, the Court of Appeals found none of the Government's arguments were availing; that the plain meaning of the language ought to control. The Court of Appeals stated, "[t]he only reasonable interpretation of the provision is consistent with Boeing's argument that Subsection 7013(f) 'authorizes the use of certain restrictive markings' for the purpose of restricting the government's rights." In layman's terms, Subsection (f) addresses only the restriction on Government rights, but it does not address any third party restrictions. Therefore, there was no prohibition – in the plain meaning of words used – against a second legend so long as it did not restrict the Government's rights.

Procedurally, the Court of Appeals is the appellate court for the ASBCA. It is limited in its available actions, and can only review the ASBCA's decision, but cannot resolve factual disputes. Accordingly, the Court of Appeals opinion reverses the ASBCA's dismissal of Boeing's motion for summary judgment and remands the case back to the ASBCA to resolve the remaining factual disputes. Specifically, ASBCA must now take up the unresolved factual dispute regarding whether Boeing's proprietary legend, in fact, restricts the Government's rights. If not, then the second legend will stand.

Takeaway

The Court of Appeals' opinion opens the door for contractors to include legends they consider necessary to restrict third party – not Government – rights to use the technical data. So long as the Government's rights are not restricted by the second legend, it should be okay. This will always be a question of fact – what is specific to the language of the second legend? And, does it adversely impact the Government's rights? Contractors should be careful about placing a second legend only when, where, and as needed.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.