At a glance
Possible toolACQ-32 · Licensing & IP
Authority holder: Secretary of Defense; program manager and authorized contracting officer for contractual rights/challenges
Licensing & IP
Mechanism tags describe the source text; they do not expand the authority.
Availability and verificationExpress statutory pathway; award-specific appropriations, available balances, delegations, implementation and approvals not independently verified.
Program process and intake
Checked 2026-10-04 · process documented. Program evidence is separate from legal authority, available funds and transaction approval.
Current DoD Part 27 deviation directly implements technical-data statutes; program teams still must separately obtain deliverables and sufficient license rights.
Program IP strategy and negotiated technical-data/software rights
- Who this route serves
- Government acquisition/sustainment teams and their contractors
- Administering office / routing lead
- Program manager, contracting officer, IP counsel and DoD IP Cadre support
Direct implementationDFARS 227.7100 expressly implements sections 3771–3775 and 3781–3786; the 2026 deviation supplies the controlling DoD regulatory text where applicable.
What this evidence label means Current regulatory process documentedDoD deviation 2026-O0036 took effect February 1, 2026. The 2025 guidebook supplies planning context; it does not override later law.
Status reference date: 2026-10-04 · research checked 2026-10-04
DoD RFO Part27 class deviation2026-O0036 · Effective February 1, 2026; Attachment 227.70 reserved; 227.71–72official acquisition class deviation · Evidence record Program eligibility
Steps and preparation
Plan lifecycle IP needs early; translate them into priced deliverables and rights, not a generic demand for all contractor IP.
Intellectual Property Guidebook for DoD Acquisition (Access not verified) · IP strategy and acquisition planning; data delivery and license distinctionsofficial acquisition guidebook · published 2025-04-30 · Evidence recordDistinguish undelivered contract-required data from additional desired data; evaluate negotiated license, option or escrow arrangements for the latter.
FY2026 NDAA technical-data provision · Section805statute · published 2025-12-18 · Evidence record
Funding, limits and authority relationship
Current DoD data-rights procedures →
published guidance: Contract planning/administration, not a public funding application.
Source access and verification notes
Research scope and sources checked
Read 2026 deviation statutory scope and current IP planning materials; cross-checked enacted 805. Did not treat unrelated sustainment news or a IP Cadre advisory role as proof of transaction signature authority.
What remains unverified
- No specific restriction challenge, license purchase or current§ 805 implementation directive verified.
A dated source check is not continuing monitoring. Recheck the linked official notice before preparing a submission. Browse program research →
Funding conditions
- Purchase/license additional rights where necessary; funding does not automatically erase private rights.
Read the funding and execution guide
Who contributes what
Need & planning
- Operational requirement owner; Service/component portfolio acquisition executive and program manager
Resources
- Sponsoring Service/component appropriations manager and comptroller
Approval
- Service/component acquisition executive and authorized contracting authority, at applicable threshold
Partners & review
- User command
- Counsel, fiscal, engineering, testing, logistics and security staff as applicable
Office links are editorial matches to the original role text, not verified delegations. Composite labels and unmatched actors are preserved.
Coordination pathwaySustainment/engineering identifies data gap → contracting/IP counsel audits existing rights and deliverables → enforce owed data or negotiate additional rights → authorized maintainers.
Actor and execution-role sources
What this research establishes
Legal basisSources linkedLegal sources and instrument limits are recorded.
RequirementsGates recordedRead the requirements for this instrument; applicability depends on the proposed action.
Public fundingRules recordedPurchase/license additional rights where necessary; funding does not automatically erase private rights. Office budget figures are separate institutional context, not an allocation to this instrument. Assigned rolesRoles recordedPublic sources describe institutional authority. The instrument identifies approval and execution roles; a specific signature remains transaction-dependent. EngagementProcess sourcedCurrent DoD Part 27 deviation directly implements technical-data statutes; program teams still must separately obtain deliverables and sufficient license rights. Program check: 2026-10-04; see each route for intake status. Confidence: High on express authority and cited conditions; execution assignment is illustrative unless statute expressly names it.
Currentness: GovInfo 2024 Code (includes FY2025 NDAA, P.L. 118-159) read in full for cited provision; targeted FY2026 NDAA P.L. 119-60 amendment/repeal sweep. No claim of complete legislative currency through 2026-10-02; remaining 2026 delta needs counsel validation.
Review scope: Original research target October 2, 2026; no record-specific last-review date supplied. Publication is not legal-currentness certification.