EconDefense
ACQ-32 / Intellectual property and technology transfer

Obtain and enforce technical-data rights for competition, repair and integration

Acquire negotiated data rights, enforce federally funded rights, challenge unsupported restrictions, and use specified private-data exceptions for emergency repair or integration.

Authority / instrument · ACQ-32

Technical data & sustainment

Intellectual property and technology transfer

Statute & instrument
Authority holder

Secretary of Defense; program manager and authorized contracting officer for contractual rights/challenges

What this does not authorize / hard limit

Private-expense data generally protected; statutory exceptions and negotiated rights are not ownership of all contractor IP.

Recorded executor

Warranted contracting officer and program manager

Continue to actor →

Recorded executing role; this record-specific route is not an additional institutional office.

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.

Public evidence describes the institution and instrument; it is not approval of an individual transaction.

At a glance

Possible toolACQ-32 · Licensing & IP
Legal basis10 U.S.C. §3771

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 verification

Express 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 implementation

DFARS 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 documented

DoD 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

  • Classify commercial/noncommercial data/software, development-funding history, asserted restrictions and required uses.

    DoD RFO Part27 class deviation2026-O0036 · Effective February 1, 2026; Attachment 227.70 reserved; 227.71–72official acquisition class deviation · Evidence record

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 record
  • Distinguish 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

Funding and financial terms

  • contract deliverables/license acquisition · contract-specific

    Additional rights/deliverables may require negotiated consideration; funding alone does not erase private-expense protections.

    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 record

Exclusions and limits

  • Actual delivery/access and legal permission are separate; challenges to restrictive assertions follow the required procedures.

    DoD RFO Part27 class deviation2026-O0036 · Effective February 1, 2026; Attachment 227.70 reserved; 227.71–72official acquisition class deviation · Evidence record

Authority relationship source

DoD RFO Part27 class deviation2026-O0036 · Effective February 1, 2026; Attachment 227.70 reserved; 227.71–72official acquisition class deviation · Evidence record

Current DoD data-rights procedures →

published guidance: Contract planning/administration, not a public funding application.

Source access and verification notes
  • 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 record

    Automated direct retrieval did not complete on October 4, 2026. This access check does not establish current legal effect or invalidate independently reviewed indexed evidence; see the cited location and this dossier’s access qualifications.

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 →

Requirements and limits

Eligibility & prerequisites

  • Assess development funding, data category, contract deliverables and actual rights.
  • FY26 §805 requires distinguishing missing contract-required data from additional desired data and negotiating options/licenses/escrow for the latter.

Limits & exclusions

  • Private-expense data generally protected; statutory exceptions and negotiated rights are not ownership of all contractor IP.
  • Data-rights license and actual delivery/access are separate requirements; follow restriction-challenge procedures.

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

Execution

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 pathway

Sustainment/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.