A direct follow-on production-award path — this is the legal basis underlying the DACC II Production OTA in Tier 1. It's also the repeatable model: a Tradewinds-vetted, awardable solution → a direct prototype OT → a successfully completed prototype → a sole-source production follow-on.

A contracting office with a warranted agreements officer issues the follow-on production OT, citing §4022(f) — the Tradewinds-based competitive award of the prototype plus its successful completion.

CICA (full-and-open competition) does not apply because the competition requirement was met through Tradewinds. The office must still have a warranted agreements officer to award the OT.

Production and scaling of any capability SBCC first delivered under a Tradewinds-enabled, competed OT prototype.

Pair it with the DACC II Production OTA — it's the legal "why" behind that direct production award, and it's the template for converting Tradewinds-vetted prototypes into production. Lead with the chain: awardable status on Tradewinds got us the prototype direct, we completed it, and §4022(f) now lets the government go straight to production sole-source.

Only reaches follow-on production tied to a competed (here, Tradewinds-enabled), successfully completed prototype (FA68002590001) — not a general-purpose new-work authority. Requires an office with a warranted agreements officer. The "successfully completed" prong must actually be met and documented. If the customer wants a fresh prototype rather than production, this path doesn't apply.

A direct, non-competitive follow-on production award (OT or FAR contract) for the DE&A capability we first delivered under the competed, successfully completed DACC II prototype (FA68002590001) — competitively enabled through our Tradewinds awardable status and then completed. Scope = production, scaling, and sustainment of that prototyped DE&A capability: the data engineering and analytics solutions, decision-support tooling, agile DevSecOps development and deployment, AI/ML-enabled analytics within native DoD data platforms (Envision, Advana, the "Big Six"), data-literacy training, and sustainment of fielded DE&A use cases across AFGSC and other DoD customers.

It only reaches DE&A production work that follows from the qualifying DACC II prototype — data engineering, analytics, decision-support, and the modernization/sustainment of those analytics solutions. Capabilities outside that DE&A line (e.g., unrelated mission services with no tie to the prototyped data-engineering-and-analytics capability) are not covered, and only an office with a warranted agreements officer can use the authority. It is not a general-purpose new-work authority, and it does not cover brand-new prototyping — that's a separate OT prototype action.

Is the need the production, scaling, or sustainment of the DE&A capability we prototyped under DACC II — data engineering, analytics platforms/dashboards, AI/ML decision support, or sustainment of those analytics solutions — and did we competitively earn and complete that prototype (via Tradewinds awardable status)? → this §4022(f) authority is the legal basis (and it's what underpins the DACC II Production OTA). If the need falls outside that DE&A line, or the office lacks a warranted agreements officer, this authority doesn't apply.