What IWRP is
The Information Warfare Research Project is a consortium built on a Navy other transaction agreement. Naval Information Warfare Center Atlantic awarded that agreement on behalf of Naval Information Warfare Systems Command. Advanced Technology International, a nonprofit based in Summerville, South Carolina, manages the membership as consortium manager. NIWC Atlantic and NIWC Pacific issue the work. Member companies compete for individual Prototype Project Agreements placed under one base agreement, and the authority behind all of it is 10 U.S.C. § 4022. The current generation, IWRP 3, runs under other transaction agreement No. N65236-24-9-0003, with a period of performance through September 30, 2034.
Two structural facts shape everything else. Membership is a precondition to bid: only members in good standing may respond to solicitations for project awards, and good standing means dues no more than 60 days past due. Enrollment has to happen before the work appears. Second, the documents are public. The consortium publishes the membership agreement, its amendments, and the base agreements for both IWRP 2 and IWRP 3, so a firm can read the terms it will sign before it spends a dollar. Almost everything below comes from those documents and from the Navy's own announcements.
Three generations, and what IWRP 3 changed
IWRP launched in 2018. NIWC Atlantic awarded the third-generation agreement to Advanced Technology International on June 6, 2024, and two terms changed in ways that matter to anyone planning a bid. The ordering period stretched to ten years, October 1, 2024 through September 30, 2034. And the ceiling went away: the Navy described IWRP 3 as carrying an undefined ceiling, against initial limits of $100 million under IWRP 1 and $500 million under IWRP 2.
| Generation | Ceiling | Ordering period | What it means for a bidder |
|---|---|---|---|
| IWRP 1 | $100 million initial limit | Shorter than the current period | Capacity was a real constraint; remaining ceiling could bind before program demand did |
| IWRP 2 | $500 million initial limit | Shorter than the current period | More headroom, same question about capacity late in the period |
| IWRP 3 | Undefined | Oct 1, 2024 – Sep 30, 2034 | Constraint moves back to appropriated money and program demand; a decade of runway to plan against |
IWRP 3 also widened the scope, adding quantum, optical communications, and electromagnetic spectrum operations to the technology areas.
The number worth carrying is the one NIWC Atlantic published with that award. Since launching in 2018, IWRP had executed 171 prototype awards that led to 24 production awards, all totaling approximately $2 billion. That is roughly one prototype in seven reaching production, across six years and the entire membership. It is a real denominator in a field where most consortium marketing has none.
The technology areas are the scope
The base agreement lists seventeen technology areas and says the list may be changed at any time to better meet the environment or a warfighter need. At any given moment it is the boundary, and work that does not map onto one of these areas does not belong here however good it is.
They are cyber warfare; data science and analytics; assured communications; cloud computing; enterprise resource tools; autonomy; mobility; model based systems engineering; on-demand manufacturing; assured command and control; integrated fires; battlespace awareness; DevSecOps; artificial intelligence and machine learning; electromagnetic spectrum; quantum technologies; and optical communications. Most of that list describes software work, which is why IWRP comes up so often at data and AI firms.
How directly a software deliverable answers each published area
The area names are quoted from the IWRP 3 base agreement. The ordering is our editorial read of how much of each area a pure software or data deliverable can answer on its own, not a measurement of award volume, which the Navy does not publish by area.
The scope test is enforced during performance, not only at award. The Agreements Officer, the consortium manager, and the project representative actively monitor projects for compliance with § 4022 throughout performance, and failure to become compliant can end the project agreement and remove the firm from consideration for future ones. That is a real reason not to push a finished product through a prototype authority.
What membership costs and what it requires
Dues are not the barrier. They are payable each October 1: $750 for a large business, $250 for a small business, and no charge for academic institutions and nonprofits. Size is set by SBA size standards against NAICS 541715. New members pay prorated dues on acceptance, at the full rate for an October-through-March start and half rate for April through September. Against the cost of a single white paper, this is a rounding error.
The paperwork sets the schedule. The consortium says an application with all documentation in hand can be processed in as little as one to two business days, and that it can take several weeks when a certificate has to be obtained or renewed. The membership agreement lists what a member carries.
- Be a U.S. firm or institution organized or existing under the laws of the United States, its territories, or possessions
- Not be barred from contracting with or receiving funds from the U.S. Government
- Show in the application a capability to contribute technically in the listed technology areas
- Maintain an active Military Critical Technical Data Agreement, DD Form 2345, with the U.S./Canada Joint Certification Office
- Hold an active SAM.gov registration and a Unique Entity Identifier
- Provide all cost and technical data any solicitation requires, and abide by the base agreement
The DD Form 2345 usually sets the calendar. It is issued through the U.S./Canada Joint Certification Program on its own timeline rather than the consortium manager's, and the consortium describes recent processing as anywhere from a few days to a few weeks. A firm that wants to be positioned for a solicitation next quarter starts that certification now. Firms operating under foreign ownership, control, or influence supply either a mitigation plan approved by the Defense Counterintelligence and Security Agency or a signed export compliance acknowledgment form. That test asks how the company is organized and controlled, and applies to the entity.
How work reaches members
The government seeks prototype work by issuing Requests for Prototype Projects to the consortium, each describing a problem statement and the basis for evaluation. Commercial solutions openings and prize challenges are also available. The consortium manager publicizes each request to members and to potential new members with relevant capability, to the broadest audience practicable.
Timing is worth planning around. The base agreement describes these requests as mainly ad hoc, with an expected increase in the third quarter of every fiscal year, the April-through-June window. Evaluation covers, at a minimum, the technical approach and the proposed cost or price. The consortium manager performs a detailed cost and price analysis of selected proposals, and the Agreements Officer determines whether the total evaluated price is fair and reasonable. The agreement is blunt about what selection is worth on its own: in no way does selection guarantee award.
From outside the consortium to a signed project agreement
One term inside that process deserves more attention than it gets. The government reserves the right to consider prototype submissions, white papers and proposals alike, for up to 24 months after submission, including submissions carried over from IWRP 2, and may fund one at any point in that window after reconfirming the submission is still valid. A non-selection is therefore not always the end of the file. Keep the concept current and treat the submission as live.
The industry-day calendar is the forecast
Consortium exchange and industry-day events run on a published rhythm: approximately two quarterly events on the East Coast supporting NIWC Atlantic areas of responsibility, one quarterly event on the West Coast supporting NIWC Pacific, and roughly four virtual events a year. They are set up so government participants across the NAVWAR enterprise can attend virtually, and built to handle a minimum distribution level of D. When non-members are invited, the event is also advertised on SAM.gov.
Here is the part most firms miss. For each of those events, the government develops and shares in advance an IWRP 3 Prototype Program Plan giving a draft schedule of upcoming prototype projects, including forecasted spending. That is a pipeline forecast distributed to the membership ahead of the solicitations it describes. The consortium manager also owes an annual review by November 30 covering each project's performance for the prior fiscal year and the aggregate, including the percentage on schedule and within budget. A firm that attends the events and reads that review works from better forward-looking information than most of the market has.
The base agreement is not a blank page
Most writing about other transactions repeats the same line: the FAR does not apply, no clauses come attached, every term is negotiated fresh. That is true of the authority in general and false of what a firm signs when it joins IWRP. The base agreement already fixes the defaults, and a member accepts them at signature rather than negotiating project by project. On software and data rights, those defaults are specific.
Government purpose rights are the floor. The government has a minimum of government purpose rights in technical data, computer software, and software documentation delivered under the agreement, subject to the exceptions below.
Those rights carry a five-year clock. The agreement defines government purpose rights as rights that may evolve into unlimited rights five years after delivery, and the prescribed legend states that expiration date and says plainly that no restrictions apply after it. The default is not that a firm keeps its software. It is a restriction that lapses on a schedule.
Several categories go straight to unlimited rights. Form, fit, and function data. Corrections to government-furnished data. Material already public or released without restriction. Studies, analyses, and test data where that work was specified as an element of performance. Data necessary for operation, maintenance, installation, or training. Required software documentation.
Anything more restricted has to be listed with the offer. A member attaches to any offer a list of everything it intends to deliver with less than government purpose rights, naming the item, the basis, the degree of restriction, its duration, and who asserts it. That list is the control, and it is prepared before award.
Unmarked material carries unlimited rights. A member that learns of an erroneous release has one year to give written notice through the consortium manager and cure it going forward. Markings can also be challenged: 60 days to answer a request for justification, after which an unjustified marking may be struck at the member's expense.
Three more terms belong beside those. A member keeps copyright in original works it develops and grants the government a non-exclusive, royalty-free license for government purposes. A member may not put copyrighted material, open-source software included, into a deliverable without the Agreements Officer's written approval unless it owns the copyright or has secured the license rights the government needs. And prototypes and production items physically delivered are wholly owned by the government and may be issued to other firms as government-furnished equipment on later projects.
| Question | Settled by the base agreement | Set in each project agreement |
|---|---|---|
| Data and software rights | Government purpose rights floor, five-year expiration, unlimited-rights categories, assertion list, marking-challenge procedure | Whether a deliverable carries a different level, per the assertion list attached to the offer |
| Patents | The member retains ownership of subject inventions consistent with 35 U.S.C. § 202 | Nothing; the base articles govern |
| Pricing arrangement | Fixed price and expenditure-based are the two permitted forms | Which one applies, and the payable milestones or cost basis |
| Accounting | GAAP and documented cash control on every project | Whether the project is expenditure-based, which adds cost identification by agreement |
| Regulatory clauses | FAR 52.204-25 and 52.204-27 against the member and all projects | The DFARS cybersecurity and telecommunications clauses, plus any required certification level |
| Disputes | Timing bars, elevation path, 60-day step before other remedies | Nothing; the base procedure governs |
Where the regulation still reaches
An other transaction is an exception to the FAR, not an exemption from everything in it
The IWRP 3 base agreement incorporates FAR 52.204-25, on certain telecommunications and video surveillance services and equipment, and FAR 52.204-27, on a ByteDance covered application, by reference against the member and every prototype project. At the project level it incorporates, as required, FAR 52.204-21 on basic safeguarding of covered contractor information systems, FAR 52.204-23, DFARS 252.204-7012 on safeguarding covered defense information and cyber incident reporting, DFARS 252.204-7018, DFARS 252.204-7020 on NIST SP 800-171 assessment requirements, and DFARS 252.227-7025. The January 2026 conformed agreement adds that solicitations may identify a required cybersecurity certification level per requirement under DFARS 252.204-7021. Read the level in the actual solicitation.
Export control, security requirements, and organizational conflicts of interest each have their own article. Orders placed for project agreements are reported by the government to the Federal Procurement Data System, so these awards land in the public spending record the way a contract does, and any agreement providing for payments above $5 million carries a Comptroller General records-examination clause. A firm treating an other transaction as an unobserved side channel has misread the instrument.
Money, accounting, and cost share
Project agreements are awarded fixed price or expenditure-based, decided per project. Fixed-price agreements pay on completed milestones once the project representative has verified the work against the statement of work. Expenditure-based agreements pay on actual costs and carry a notification duty: the member must tell the Agreements Officer, through the consortium manager, whenever it expects the next 60 days of costs to push the running total past 75 percent of the amount allotted.
The accounting floor sits below a cost-type FAR contract and well above nothing. Every member awarded a project agreement keeps records adequate to account for government funds, runs an accounting system complying with generally accepted accounting principles, and documents all cash receipts and disbursements. An expenditure-based agreement adds cost identification down to the individual agreement, segregation of direct costs, and a method for allocating indirect costs equitably.
FAR Part 31 cost principles are not general here. They attach, with DFARS Part 231 and NMCARS Part 5231, to a member already subject to cost accounting standards on other agreements or contracts. A firm that qualifies as nontraditional under 10 U.S.C. § 3014, a test that turns on the absence of full cost accounting standards coverage, is by construction outside that trigger. The two definitions interlock. Cost share, where it appears, must be verifiable from financial records and cannot be counted against another federal vehicle; costs incurred before a project agreement is executed are the member's own.
Who can direct the work, and who governs the consortium
This is where consortium work quietly goes wrong for firms used to commercial delivery. The Agreements Officer's Representative designated for each project is explicitly not authorized to make commitments or changes affecting price, quality, quantity, delivery, or any other term. Only the Agreements Officer, acting through the consortium manager, can. The agreement directs the member to perform no work in response to any other direction, and to notify the consortium manager immediately when one arrives.
Disputes run on a clock. Formal notification cannot be made earlier than 30 days after the dispute arose, and a dispute more than 180 calendar days old cannot be the basis for relief unless the Agreements Officer waives that in writing. Notice sends the matter to the Chief of the Contracting Office for NIWC Atlantic and a consortium executive; if they do not resolve it within 60 days, either party may pursue alternative dispute resolution or other remedies, and performance continues throughout. The government may terminate any project agreement at any time, with an equitable adjustment negotiated in good faith that may include non-cancelable commitments made before termination.
Governance sits with an Executive Committee of seven. The consortium manager holds one permanent seat; the other six are elected from member organizations for three-year terms, allocated as two from large businesses or nonprofits, three from small businesses, and one from academia. The membership agreement states the limit on that role plainly: Executive Committee members not employed by the consortium manager have no access to member proprietary data, no advance insight into potential government solicitations, and no advance insight into source selection decisions.
The production pathway
The reason firms tolerate all of the above is what sits at the end of it. Under § 4022(f), and on a determination that a competitively awarded project agreement has been successfully completed, a follow-on production contract or transaction may be awarded directly to that member without competitive procedures. The base agreement carries the mechanism forward and adds that follow-ons arising from project agreements awarded through previously documented competitive procurements, such as a commercial solutions opening or a prize challenge, may themselves be issued as other transactions without competition.
Congress wrote the consortium case into the statute deliberately, across three NDAAs. The FY2018 act added the sentence stating that a transaction includes all individual prototype subprojects awarded under it to a consortium of United States industry and academic institutions. The FY2019 act added § 4022(f)(3) and (f)(4), which let the department make the successful-completion determination for an individual prototype or subproject within a consortium, and state that a follow-on award is not contingent on the successful completion of all activities in that consortium. The FY2023 act then amended § 4022(f)(2) so the non-competitive follow-on is available even if explicit notification was not listed in the request for proposal. The older advice to check that the solicitation announced a possible follow-on is now good practice rather than a statutory gate.
One sentence in any project agreement decides whether the pathway is real: the one defining successful completion. Tie it to measurable acceptance criteria, such as a detection rate at a stated false-alarm rate, a latency budget under a stated load, or a completed integration against a named system. Satisfaction language leaves that determination to whoever holds the chair at the end of performance, which is not a plan.
Where IWRP fits, and where it does not
It fits when the work is genuinely a prototype inside a listed area and a Navy or Marine Corps sponsor wants the outcome. The base agreement defines a prototype as a physical or virtual model used to evaluate the technical or manufacturing feasibility or military utility of a technology, process, concept, end item, or system. That is wide enough to cover software, models, pipelines, and integrations, and narrow enough to exclude a mature product sold as-is.
The realistic qualifying condition for most software firms is one of the first two in § 4022(d)(1): at least one nontraditional defense contractor or nonprofit research institution participating to a significant extent, or all significant non-federal participants being small businesses or nontraditional defense contractors. The one-third cost share condition is a financing decision of a different character, and the exceptional-circumstances determination is uncommon. The consortium is built around that first pair, and publishes a membership of 843 organizations, 72 percent of them nontraditional.
Which is also the honest limit. Membership is cheap and the barrier to entry is administrative. Winning is neither. Selection is competitive against a member base in the hundreds, the government keeps the ability to award under limited competition or sole source, and the firms that win have usually built a relationship with the sponsoring program before the request appears. Joining buys the right to compete and the visibility to know what is coming. It does not shorten the distance between a capability and a program office that wants it.
Bottom line
IWRP is one of the better-documented consortium vehicles a software or data firm can join, and the documentation is the reason to take it seriously. The dues are trivial, the certification file is the real schedule item, and the base agreement answers in advance the questions that get negotiated one at a time on a bespoke other transaction. That cuts both directions: it removes negotiation risk, and it removes negotiating room.
So the decision is not really about the instrument. It is whether the firm has a capability that maps onto a listed area, whether it can name a Navy or Marine Corps sponsor who wants that capability, and whether it has done the intellectual property inventory before the assertion list is due rather than after. Get those three right and the vehicle does what it was built to do.
Frequently asked questions
Advanced Technology International manages the consortium under an other transaction agreement awarded by Naval Information Warfare Center Atlantic on behalf of Naval Information Warfare Systems Command. NIWC Atlantic and NIWC Pacific offer funding to members through Requests for Prototype Projects. IWRP 3 runs through September 30, 2034.
Dues are payable each October 1: $750 for a large business, $250 for a small business, and no charge for academic institutions and nonprofits. New members pay prorated dues, full rate for an October-through-March start and half rate for April through September. Only members in good standing may respond to solicitations for project awards.
The DD Form 2345, the Military Critical Technical Data Agreement issued through the U.S./Canada Joint Certification Program. Every member holds an active one, and it is granted on the certifying office's timeline rather than the consortium's. Membership itself can be approved in one to two business days once the file is complete, so the certification, not the application, decides whether a firm is eligible when a solicitation lands.
Only to the extent it asserts them correctly. The base agreement sets government purpose rights as the minimum for delivered technical data, software, and documentation, and defines those rights as evolving into unlimited rights five years after delivery. Anything more restricted must be listed with the offer, and unmarked material carries unlimited rights.
Yes, under 10 U.S.C. 4022(f), where the prototype was competitively awarded and the government determines it was successfully completed. The statute lets that determination be made for an individual subproject inside a consortium, and does not require the whole consortium's work to finish first. What decides any single case is how the project agreement defines successful completion.