Other Transaction Authorities (OTAs)

An OT runs on a small, dedicated cross-functional team. The set of seats is roughly the same as a complex FAR procurement, but several of the seats expect different muscles.

• Agreements Officer (AO) – warranted to enter into, administer, and terminate the OT. Owns the agreement language, the negotiation, and the determination paperwork. Not necessarily a CO.
• Program manager and end user – own the requirement and the success criteria. The end user is going to live with whatever the prototype produces, so their voice matters in framing the problem and judging success.
• Legal counsel – OT-fluent counsel, ideally someone who has done this before. The dispute, IP, and termination provisions are negotiated, not pulled from a clause matrix.
• Comptroller / financial manager – calls color of money, signs off on payable milestone structure, and validates any cost-share arrangement.
• IP cadre or IP-fluent counsel – the OSD IP Cadre exists for exactly this kind of work. The IP strategy is one of the highest-leverage decisions on a prototype OT.
• Small business representative – particularly if Gate 2 (all small or nontraditional defense contractors) is in play.
• DCAA / DCMA – optional, at the Agreements Officer's discretion. DCAA can support price evaluations and accounting-system reviews when the deal is expenditure-based or includes resource sharing. DCMA can support administrative oversight if delegated.

The composition shifts depending on the deal. A simple prototype with a single small nontraditional defense contractor and fixed milestone payments needs less audit and accounting muscle than a $200M consortium prototype with cost-share, indirect rates, and complex teaming.

The first decision is which OT statute applies. The two statutes look similar from a distance, but the eligibility tests, the cost-share defaults, and the follow-on options are genuinely different.

If the answer is "honestly, this looks like a routine commercial buy with no innovation angle," that is the answer. Walk it back to a Part 12 commercial buy, a CSO if the problem is open-ended, or a regular sources-sought-into-RFP path. OTs are not a faster-FAR shortcut and treating them like one tends to produce slow OTs.

OT market intelligence has the same goal as FAR market research (figure out who is out there and what they can do) but the channels are different. The sources you want to reach largely do not read SAM.gov.

• Innovation organizations as channels. DIU, AFWERX, SOFWERX, and the service labs maintain communities of nontraditional defense contractors, run pitch days, and operate problem-statement intake processes. Going through them is often faster than building outreach from scratch.
• Consortia. If a topical consortium already exists for your problem area (cyber, hypersonics, medical, training, naval, space, software), the membership list is a ready-made bidder pool. ACC‑NJ hosts several DoD-wide consortia.
• Commercial channels. LinkedIn, industry conferences, hackathons, and innovation challenges (challenge.gov, AFWERX challenges) reach commercial firms in ways a SAM.gov posting will not.
• SBIR / STTR pipelines. Companies that have completed Phase II SBIR work are pre-qualified small nontraditional defense contractors and frequently the right pool to draw from for prototype OTs.

Document what you did. The market-intelligence record supports both the eligibility gate determination (you can show nontraditional defense contractor participation was real) and any later defense of the competition.

The OT statutes do not require a specification, a Statement of Work, or any particular requirement format. They require the Agreements Officer to describe the problem clearly enough that industry can propose solutions against it.

The historical example most often cited is DARPA's Global Hawk solicitation in 1994: a two-page description asking for a high-altitude UAV that could reach 60,000 feet, stay aloft 24 hours, and come in at $10M flyaway price. No spec. Industry got to propose how. The result became Global Hawk.

Before award, the Agreements Officer has to independently validate and document that the prototype OT meets one of the four eligibility gates from Section 4 of the Concepts tab. The documentation is in the file. It does not have to be a formal D&F, but it has to exist and be defensible.

• Nontraditional defense contractor participation (Gate 1): identify the nontraditional defense contractor by name, describe the work share, and document why the participation is "significant." Attach the nontraditional defense contractor's representation.
• All small or nontraditional defense contractors (Gate 2): list every significant participant and their status. The list is the documentation.
• One-third cost share (Gate 3): document the total project cost, the federal share, the non-federal share, and the form (cash, in-kind, IR&D). Do not count costs incurred before the agreement was effective unless the Agreements Officer has specifically determined those costs were incurred in anticipation of the agreement.
• Exceptional circumstances (Gate 4): SPE-level determination, in writing, citing the statutory factors. Plan additional time for routing.

OT solicitations are not required to look like an RFP. They can be oral. They can be a five-page Broad Agency Announcement. They can be an Area of Interest under an existing CSO. They can be a topic call inside a consortium. The Agreements Officer picks the format that fits the problem and the bidder pool.

Whichever method, the solicitation should at minimum describe the problem, state the instructions, identify the success criteria (or the evaluation factors), and list any known terms the agency intends to apply. Performers should know what "winning" looks like before they invest in a proposal.

The OT statutes do not prescribe an evaluation method. The Agreements Officer designs one to fit the project. Common patterns include peer review by subject-matter experts (frequent in CSO-style and DIU work), a structured panel evaluation against named criteria, or an iterative process where the agency asks follow-up questions or runs interactive sessions with bidders.

What evaluations should not look like is a Part 15 source selection in disguise. Adjectival ratings, formal tradeoff narratives, and the full apparatus of FAR Subpart 15.3 are not required and inviting them creates an inconsistency between the OT framing and the actual process. A protester arguing that the agency really ran a Part 15 procurement and should have followed Part 15 rules has more to work with when the evaluation record looks like a Part 15 record.

The Truth in Negotiations Act and the certified cost or pricing data regime do not apply to OTs. That is one of the deliberate design choices that makes OTs accessible to nontraditional defense contractors: commercial firms that do not capture cost data the way traditional defense contractors do, and would walk away rather than build a CAS-compliant accounting system to bid.

Price reasonableness still has to be established. The Agreements Officer has to be able to defend "this price is fair and reasonable for what we are getting." The order of preference looks roughly like:

1. Competitive proposals from the OT solicitation itself (the cleanest evidence).
2. Commercial pricing for similar offerings in the marketplace.
3. Parametric data, market data, or independent government estimates.
4. Cost information from the performer, only as a last resort and asked for narrowly. Demanding cost data from a nontraditional defense contractor tends to scare them off and undermines the reason you chose an OT in the first place.

Document the analysis in the file. The standard is "fair and reasonable," not "lowest possible." On a prototype effort against a novel problem, the fair-and-reasonable analysis often ends up resting heavily on the competition itself.

IP is the area of an OT where the Agreements Officer has the most flexibility and the most potential to either set the program up for success or quietly hand the government a dead end. Get the IP strategy in writing before solicitation.

• Outcome focus. What does the end user need to do with the technology over its life cycle? Operate it? Maintain it? Recompete future development? Each of those drives a different rights package.
• License rights vs ownership. The default in most OTs is that the performer keeps title to its inventions and the government takes a license. The license scope, exclusivity, and transferability are negotiated.
• Background vs developed IP. Background IP (what the performer brings to the table) generally stays with the performer. Developed IP (created during the project, especially with government funding) is the live negotiation.
• Computer software and technical data. Government Purpose Rights, Limited Rights, Restricted Rights and the various asserted-rights regimes are still useful frameworks even though DFARS clauses do not apply automatically. The OSD IP Cadre exists to help structure the rights package.

The single biggest IP failure mode: getting an excellent prototype with no rights to recompete the production phase or to maintain the system after the prime walks. That is a totally avoidable outcome and it is avoided by negotiating the IP package with the production phase already in mind.

OT financial management runs on payable milestones. Each milestone is an objectively verifiable event tied to a payment amount. When the milestone is met, the performer invoices and gets paid.

Well-structured milestones do two jobs at once. They give the performer predictable cash flow (especially important for small nontraditional defense contractors that cannot float a year of effort), and they give the government a checkpoint to evaluate progress before more money goes out the door. Failure to hit a milestone is a management decision point, not an automatic termination.

• Milestones can be sequential, conditional, or contingent. "Pay X on completion of integration test, pay Y on completion of field demo, pay Z on government acceptance of the operational prototype" is a common structure.
• Milestones can be priced options. Phase 2 only triggers if Phase 1 succeeds. The agreement can include the priced Phase 2 milestone but the government is not obligated to fund it.
• Withholds tied to deliverables. If a report or deliverable accompanies a milestone, the government can withhold a portion until the deliverable is accepted.

Resource sharing is when the performer (or other non-federal party) puts skin in the game alongside the government's funding. It is required as the eligibility basis when neither Gate 1 nor Gate 2 applies (the one-third minimum from Gate 3). It is also a tool the Agreements Officer can use voluntarily when it would genuinely incentivize the performer.

• Cash or in-kind. Labor, materials, equipment, IP rights, facilities all count.
• IR&D dollars can count as resource share. Profit or fee cannot.
• Costs incurred before agreement effective date generally do not count, with a narrow exception for costs incurred in anticipation of the agreement and approved in writing by the Agreements Officer.
• The share does not have to come from the prime alone. Subs and third-party financiers can contribute. The team has to have authority to commit the resources.

If the agreement requires resource sharing, it should also address what happens if the performer cannot deliver its share: an adjustment to government funding, a rebalancing, or a remedy. Think through the failure mode at award.

A consortium is a commercial arrangement among performers, often coordinated by a Consortium Management Organization (CMO). The government is generally not a party to the consortium itself. The government awards the OT to the consortium (or to individual members under an umbrella) and the consortium handles internal governance.

Consortia are useful when the topic area has a deep bench of repeat performers and the government wants standing access to that pool without rebuilding outreach from scratch each time. They can also be inefficient when the project is narrow enough that a direct award to a single performer would have been simpler.

Reporting note: when the OT is a consortium award with multiple sub-awards, the standard pattern is to set up an Indefinite Delivery Vehicle (IDV) record in FPDS for the umbrella agreement and report individual project awards to consortium members as orders against that IDV.

None of the FAR machinery for changes, disputes, or termination flows through to OTs. Whatever the agreement says is what governs. That puts a lot of weight on the original drafting.

• Modifications. The agreement should address how mods are made, who has to consent, and whether the government has any unilateral change rights (typically narrow: Agreements Officer name changes, accounting line edits, things that do not affect the performer's payment).
• Disputes. No Contract Disputes Act. The agreement should set out an escalation path and a final resolution mechanism: alternative dispute resolution, mediation, named jurisdiction, or some combination. Get this right at award.
• Termination. The agreement should say when and how each party can terminate, what notice is required, and how amounts due are calculated. Common pattern: government may terminate for insufficient funding; performer may terminate if commercial viability disappears or the government fails to perform.
• Remedies. When termination happens, what does the government get back? Recoupment of investment, IP deliverables, technical data, and license rights are all on the table.

• Research OTs get reported in the Financial Assistance Award Data Collection (FAADC) system, since they are treated as financial assistance for reporting purposes.
• Prototype and Production OTs get reported in FPDS using the OT module (or via a contract writing system that propagates to FPDS).
• PIID conventions: the 9th position of the award number is "3" for Research OTs and "9" for Prototype and Production OTs.
• SAM registration is required for the prime awardee. For consortium awards, both the consortium lead and any consortium members receiving a direct award have to be registered or at minimum have a UEI.
• Distribution is via the Global Exchange (GEX) and the Electronic Document Access (EDA) system, just like FAR-based contracts.
• Invoicing uses Wide Area Workflow (WAWF) within PIEE.
• Government Furnished Property uses the PIEE GFP Module.
• Comptroller General access clause is required by statute for Prototype or Follow-on Production OTs above $5M.

A follow-on Production OT (or a sole-source FAR-based production contract under §4022(f) authority) requires two things in writing: that competitive procedures were used in the original prototype, and that the prototype was successfully completed. The Agreements Officer documents both.

"Successful completion" means the performer met the key technical goals of the project, satisfied any success metrics the agreement built in, or accomplished a particularly favorable or unexpected result that justifies transition to production. The cleanest path is to build the success metrics into the agreement itself at award, share them with the performer up front, and judge against them at the end.

For consortium prototypes, the determination addresses the participants who successfully completed individual prototype subprojects. The consortium-level award is not required to have produced a single "winner."

Two paths after a successful prototype:

• Production OT under §4022(f). Same flexibilities as the prototype. Negotiated terms, milestone payments, OT-style IP regime continues. No second competition required.
• FAR-based production contract. Sole source to the prototype performer on the strength of the prior competition and the successful prototype determination. The contract itself is a normal FAR contract with the full clause set.

Either path is authorized. The choice usually turns on what the production phase actually looks like. A production phase that needs ongoing FAR-style oversight, a FAR-style accounting posture, and traditional clauses on pricing, audits, and Buy American often makes more sense as a FAR contract. A production phase that continues to involve commercial-style operations and an ongoing IP negotiation often makes more sense as a Production OT.

The follow-on award does not have to be made by the same organization that awarded the prototype. Multiple DoD organizations can award their own follow-on production efforts based on a single successful prototype.

The local CO works through the standard triage. Is there a commercial product that already does this? Maybe. Worth a market research pass. If a clearly-better commercial product exists and matches the requirement, this becomes a Part 12 commercial buy and the conversation ends.

The market research comes back mixed. There are several scheduling platforms in the market, but none of them handle the unit's specific data feeds without integration work. The closest match needs custom development to talk to the unit's authoritative crew-qualification system. That development is the open question, and the answer will determine which acquisition path makes sense.

Three paths look reasonable on paper:

The customer wants commercial software with custom integration, fast, and is open to working with a startup. The unit's program office reaches out to AFWERX and pitches the problem. AFWERX agrees to take it on as a problem statement and route it through their established prototype OT pathway, which uses ACC‑NJ as the awarding contracting command. The local CO's role shifts from "you are buying this" to "you are the customer's CO and your shop will support the integration on the back end."

The Agreements Officer at AFWERX, working with the unit's program manager and the local CO's requirements team, drafts a problem statement. It is short. Three pages. No spec.

The solicitation goes out through AFWERX channels: posted to SAM.gov, pushed through the AFWERX network, syndicated through the relevant consortium membership. Twenty-three solution briefs come in over a 30-day window.

The evaluation panel includes the program manager, the unit's lead scheduler, an AFWERX technical evaluator, and an IT security representative. They review the briefs against the named criteria (technical merit, team capability, business viability, fit to the problem). Six performers are invited to Phase 2.

Pitch day is virtual. Each performer gets 20 minutes plus Q&A. Three are selected to submit full proposals. The down-select narrows further from there.

The selected performer is a small commercial software company with prior SBIR Phase II completion, three commercial customers in adjacent markets, and no prior experience as a defense prime. They are a nontraditional defense contractor. The eligibility gate is straightforward: Gate 2 (all significant participants are small or nontraditional defense contractors).

The agreement is a Prototype OT under 10 USC §4022. The award value is $4.2M over 12 months. Payment is structured as five payable milestones tied to integration, deployment, operational evaluation events, and final acceptance.

IP terms: government takes Government Purpose Rights to all deliverables created under the agreement. Performer retains background IP. Three named open-source components are flagged in the agreement with their license terms. The OSD IP Cadre reviewed the rights package before solicitation.

The agreement names mediation followed by district court for disputes (no Contract Disputes Act applies). It includes the Comptroller General access clause as a best practice (the clause is statutorily required for Prototype or Production OTs above $5M; this one comes in below that line, but the agreement carries it anyway in case the follow-on production phase pushes total payments past the threshold). It specifies WAWF for invoicing and EDA for distribution.

The 12-month period of performance unfolds. Most of it goes well. M1 hits on schedule. M2 is two weeks late because security accreditation takes longer than projected, but the delay is documented, no modification is needed, and the milestone payment is held until the trigger is met.

At M3, the prototype goes live at the customer site for the 90-day operational evaluation. The unit's two officers are now spending 30 minutes on Thursday instead of two days. The defect log shows real bugs but no blockers. The iteration cycle between M3 and M4 closes most of the major issues.

At M5, the success metrics are reviewed. The agreement defined success as: scheduling time reduced by at least 75% (achieved: 88%), all three data sources reliably integrated (achieved), no operational outages attributable to the prototype during the evaluation window (achieved). The Agreements Officer writes the Successful Prototype Determination, signs it, and files it.

The customer wants to scale the prototype to two more units in the same wing and to add a small set of capabilities the original prototype did not include (mobile access, additional reporting). The total estimated value of the production phase is $9M over three years.

Two paths from here.

The customer's leadership wants the production phase managed locally, including normal CPARS reporting and a more conventional contractor-CO relationship for the field-deployed units. The decision is to take Path 2: the local contracting shop will award a sole-source FAR-based production contract to the same performer.

The local CO who is going to award the FAR-based production contract receives a documentation package from ACC‑NJ. They review carefully because the entire defensibility of the sole source rests on what is in it.

• The original prototype solicitation and the published problem statement.
• The market intelligence record showing how performers were reached.
• The evaluation record from Phases 1 through 3 (solution briefs scored, pitch day notes, full proposal evaluation).
• The award documentation showing 23 solution briefs received and 3 finalists, plus the eligibility gate determination (Gate 2).
• The Prototype OT itself with its milestones, IP package, and success criteria.
• The Successful Prototype Determination, signed by the Agreements Officer.
• The IP rights package the government received under the prototype, which carries forward to the production phase.

The local CO writes a sole-source justification citing 10 USC §4022(f) as the statutory basis, attaches the prototype documentation by reference, and proceeds with award. The production contract uses FAR Part 12 commercial procedures since the deliverable is commercial software with services, the clauses come from the standard 52.212 set, and CPARS reporting begins at the first task order.

OTs come with their own vocabulary. Most of it sounds like FAR vocabulary but means different things. The terminology is one of the easiest places to get tripped up in conversation.

The header on a prototype OT solicitation does several things in a small footprint: identifies the authority, names the type of award, sets expectations on competition, and alerts performers to the FOIA exemption.

The Agreements Officer has to document which eligibility gate is being relied on and why. This sample uses Gate 2 (all significant participants are small or nontraditional defense contractors), which is the simplest one to document.

This is the document that unlocks the follow-on production pathway. Without it, no sole-source production. With it, either a Production OT or a FAR-based production contract is on the table.

A few wording patterns slip into draft OT documents and quietly undercut the agreement. These are not illegal. Most of them are FAR-borrowed muscle memory from an Agreements Officer or program manager who learned to write FAR documents first.