Defense contractors invest substantial capital developing the technology embedded in weapons systems, aircraft, vehicles, communications equipment, and other military capabilities. The Government purchases those systems, but it does not necessarily acquire unlimited rights to the technical data and software needed to maintain, modify, or reproduce them.
Congress is now reconsidering that balance.
As negotiations continue over the fiscal year 2027 National Defense Authorization Act, lawmakers are examining proposals that could expand the Defense Department's access to technical data, software, and repair information.
In a November 3 interview with Federal News Network, Professional Services Council CEO Jim Carroll described ongoing discussions about how to give military personnel access to necessary repair information while protecting the intellectual property of companies that developed the technology.
The issue is more consequential than routine equipment maintenance.
Control over technical data can determine who performs maintenance, who manufactures replacement parts, and who competes for future sustainment contracts.
Under existing Defense Federal Acquisition Regulation Supplement provisions, Government license rights generally depend on the nature of the technology, its funding history, and the applicable contractual provisions.
Technology developed exclusively at Government expense may carry broad Government rights. Privately developed technology can receive more restrictive protections. Mixed-funded development may result in Government Purpose Rights or specially negotiated licenses.
Those distinctions are central to the defense industrial base.
Section 861 of the House-passed FY2027 NDAA, H.R. 8800, would alter the framework by generally establishing Government Purpose Rights as the default for covered technical data and software delivered under future DoD contracts unless a contractor demonstrates the need for more restrictive rights.
Other legislative proposals address access to materials needed for maintenance, repair, and overhaul.
These proposals are not yet enacted law. Their final language, scope, and implementation remain uncertain.
The competing considerations are substantial.
DoD needs reliable access to maintenance information to preserve readiness, repair damaged equipment, and avoid unnecessary dependence on a single supplier throughout a system's service life.
Contractors, however, may have invested significant private capital in developing the technology. Broad rights allowing disclosure to third parties could diminish the commercial value of that investment and potentially enable competing manufacturers to reproduce proprietary designs.
The answer may depend on distinguishing several categories of information.
Technical instructions necessary to maintain or repair an existing system are not necessarily equivalent to detailed manufacturing data enabling a competitor to reproduce the entire product.
Similarly, permitting an authorized repair activity to modify software for maintenance purposes is different from granting unrestricted commercial reproduction rights.
For contractors, the central lesson is that intellectual-property planning should begin before contract award.
Companies should document the funding history of their technology, identify pre-existing intellectual property, maintain accurate restrictive-rights assertions, and determine which licenses are necessary for Government sustainment.
Prime contractors should also understand the rights held by subcontractors and commercial technology providers. A prime cannot necessarily grant the Government rights to information it does not own or control.
The emerging policy debate demonstrates that intellectual property is no longer simply a legal issue addressed after technology development.
It is becoming a central component of defense acquisition strategy, pricing, competition, and long-term sustainment.
Contractors developing proprietary technology for military applications should monitor the final FY2027 NDAA carefully and review how future solicitations allocate technical-data and software rights.
Recommended FedContractPros Product: FedClause360
FedClause360 helps contractors evaluate technical-data rights, software licensing, intellectual-property provisions, and related contractual obligations before agreeing to Government access or disclosure requirements.
Disclaimer:
This article is provided for general informational and educational purposes only and does not constitute legal, intellectual-property, procurement, or government-contracting advice. The FY2027 NDAA provisions discussed are legislative proposals, not enacted requirements. The Government's technical-data and software rights depend on the applicable law, contract terms, funding history, commercial status, license agreements, and specific circumstances.