Parallel Transition Compact
TriSeadon Adds a New Path Without Stopping Today's Fleet Work
TriSeadon is not a stop-work order for the naval industrial base. Cancellation is not part of the TriSeadon charter. The program has no authority or mission to cancel an authorized contract, ship, job, yard mission, or existing program. Current work continues under its existing statutory, contractual, technical-data, security, safety, and appropriations framework while TriSeadon ship design, testing, yards, suppliers, training, and qualification systems mature.
Arleigh Burke construction continues during the TriSeadon ramp. Carriers, submarines, amphibious ships, auxiliaries, special-mission ships, aircraft, helicopters, unmanned systems, weapons, sustainment, overhaul, conversion, inactivation, and decommissioning programs continue according to their own authorized plans. TriSeadon initially addresses the future FFG, DDG, and CAG surface-combatant requirement and the industrial capacity needed to build and sustain it.
The transition occurs through future Navy requirements, solicitations, appropriations, and awards. As TriSeadon ships prove ready and the Navy shifts future surface-combatant demand toward them, existing builders and suppliers may compete for new TriSeadon work, convert or add production lines, qualify modules and components, or continue their existing portfolios. No company must choose the complete program on day one.
Protected Current Mission Rule
This rule protects schedule continuity and the workforce already supporting the fleet. TriSeadon expansion must use new capacity, underused areas, separately authorized modernization, and deliberately sequenced workload transitions rather than silently counting an occupied dock, shop, supplier, or workforce twice.
Replacement does not equal cancellation. After TriSeadon has delivered and operationally replaced a requirement, the Navy and Congress may independently decide whether to reduce, complete, continue, or end the superseded program. That later decision is not made by the TriSeadon Program Office and is not a condition of TriSeadon implementation.
Voluntary Entry and Later Opt-In
| Participation path | What the company may do | Applicable rule |
|---|---|---|
| Continue current work | Perform existing contracts and compete for non-TriSeadon work under the applicable program rules. | No TriSeadon data-rights condition is imposed retroactively on unrelated work. |
| Enter at startup | Bid on ship design, yard operation, modules, components, logistics, software, testing, training, or sustainment. | New TriSeadon development accepts government ownership or equivalent controlling rights in foreground IP; procurement of existing products follows the legacy gate. |
| Enter later | Qualify after the first solicitation cycle, add a second source, lease GOCO or campus capacity, or compete for later blocks and refits. | The same technical, security, cyber, safety, quality, and performance gates apply to every entrant. |
| Offer a legacy product | Propose an existing engine, weapon, sensor, launcher, software product, or support system. | Use the legacy transition gate: validate and exercise existing government rights case by case, buy or license only when that is better value than replacement, bridge with the current product, or compete a replacement. |
| Decline TriSeadon | Remain outside TriSeadon and continue other lawful government and commercial work. | The firm receives no automatic claim on TriSeadon awards, incentives, facilities, or protected production share. |
Participation is voluntary; the contract bargain is not optional after entry. A firm accepting TriSeadon funding, infrastructure, qualification support, or an award must deliver the rights, data, interfaces, test evidence, configuration records, and transition support specified for that TriSeadon scope. Legitimate pre-existing background IP remains protected unless separately negotiated and paid for.
Legacy Technology: Use, Audit, License, or Replace
TriSeadon does not hold a ship or fleet requirement open while an IP dispute is resolved. Current weapons, sensors, aircraft, machinery, and software continue to be purchased and operated while the government follows one of three paths.
- Exercise existing government rights: where the original contract already gives the government sufficient ownership or license rights, use those rights case by case for production, repair, modernization, or second sourcing.
- Buy a better-value license: purchase rights, licenses, or royalties only when their independently evaluated lifecycle cost, schedule, security, and readiness value is better than a replacement competition.
- Compete a replacement: if the owner will not offer acceptable terms, issue a new performance RFP whose resulting foreground IP is government owned or equivalently controlled. Continue the legacy buy until the successor is tested, accepted, supported, and stocked.
This rule applies across the program. ASROC is a representative example: keep the current weapon available, audit the rights, negotiate only if the agreement beats the replacement business case, and otherwise develop a government-controlled successor without creating a capability gap.
Open the New Foreground IP Rule | Open the Legacy Transition Gate
How Surface-Combatant Demand Transitions
- Preserve execution: continue funded ships and sustainment while freezing the TriSeadon decision baseline and establishing independent design authority.
- Prepare the family together: coordinate all three class designs, interfaces, technologies, modules, and test programs while major-yard and state-campus work proceeds on concurrent but phased tracks.
- Prove the product: authorize class production only after design, cost, schedule, safety, integration, and industrial-readiness evidence passes defined gates.
- Sequence class production: build FFG first, CAG second, and DDG third. Common technology proven on earlier classes becomes available to later classes without reopening awarded ships.
- Shift future starts: move future surface-combatant demand into TriSeadon through normal force-structure, authorization, appropriation, and contracting decisions only as each class becomes credible.
- Convert capacity deliberately: allow existing surface-combatant lines, suppliers, tooling, and workers to transition through competed follow-on awards, retraining, new modules, added lanes, or negotiated facility changes.
TriSeadon is therefore a controlled succession path, not an overnight replacement. During overlap, a contractor may support legacy surface combatants, bid on TriSeadon work, and continue unrelated Navy programs at the same time.
TriSeadon Creates Work Before It Replaces Demand
During ramp-up, TriSeadon adds engineering, test, integration, infrastructure, training, module, component, and qualification demand. It can also create renewed or expanded demand for systems and industrial capabilities that have declined or paused, subject to Navy selection and certification.
- AGS-family gun and affordable ammunition development or a competed functional successor.
- Railgun research, pulsed-power, projectile, barrel-life, and naval integration work.
- Small-UAS scout systems and a Fire Scout-compatible future path if the Navy chooses to reinvest.
- AH-1Z Viper, UH-1Y Venom, and MH-60R/S aircraft procurement, sustainment, spares, training, and ship-integration demand.
- New production for Odyssey, AEGIR, PRIME, ATLAS, ONE-Consul, LCB, IWM, IMM, ISO, Cerberus, SCUTUM, Trinion, and their common support systems.
These are additional opportunities, not automatic awards. Each fielded system still requires an approved requirement, funding, competition or lawful acquisition path, integration evidence, and operational acceptance.
Expected Stakeholder Reception
This is an acquisition assessment, not a guarantee of how any named company, union, command, or elected official will respond.
| Stakeholder | Likely attraction | Likely concern | Program answer |
|---|---|---|---|
| Major shipbuilders | Long-run hull demand, funded infrastructure, workforce support, refits, and additional production lanes. | Loss of protected workload, uncertain transition timing, price pressure, or responsibility for shared designs. | Protect authorized work, publish the transition schedule, pay for qualified data deliverables, and compete future scope by measurable performance. |
| Weapons, sensor, and software primes | Larger fleet quantities, recurring upgrades, spares, test work, and access to three common classes. | Broad data demands, background-IP exposure, cybersecurity risk, and reduced sole-source sustainment leverage. | Separate background IP from funded deliverables, price rights explicitly, protect sensitive data, and use negotiated licenses or clean-sheet alternatives where necessary. |
| Smaller and nontraditional suppliers | Lower infrastructure barriers, controlled interfaces, GOCO and campus access, second-source awards, and repeatable demand. | Qualification expense, compliance burden, cash flow, and dominance by incumbents. | Fund first articles and qualification, provide common test facilities, maintain transparent entry gates, and prevent proprietary interfaces from closing the market. |
| Navy, NAVSEA, and DLA | More capacity, supply resilience, configuration control, repair options, and alternate sources. | Large government workload for design authority, data validation, cyber protection, testing, source qualification, and inventory control. | Fund the government workforce and digital production library as real program elements rather than unfunded administrative tasks. |
| Congress, states, labor, and communities | Fleet readiness, domestic production, jobs, training, cleanup, local investment, and wider geographic participation. | District workload shifts, startup cost, environmental liability, execution risk, and fear that existing jobs will be displaced. | Use phased state compacts, protect current missions, publish capacity and cleanup milestones, and release funding only as readiness gates are met. |
Most resistance should be expected as negotiation, lobbying, requests for exceptions, pricing disputes, and schedule protection rather than a complete industry boycott. The federal government remains the dominant customer for major U.S. naval construction, and TriSeadon offers substantial new work. The program becomes more acceptable when it is predictable, pays for legitimate rights and transition costs, protects existing authorized missions, and lets companies enter after startup.
Transition Guardrails
- No current contract is cancelled, modified, or deprived of funding by this policy alone.
- No current yard mission is displaced without a separately authorized workload and capacity decision.
- No privately funded background IP is confiscated; needed rights are verified, negotiated, licensed, or replaced.
- No classified, export-controlled, nuclear, safety-critical, or cyber-sensitive package is released outside its authorized boundary.
- No planned lane, supplier, or campus is counted as available until it passes readiness and acceptance gates.
- No incumbent receives permanent entitlement to future TriSeadon work merely because it performs current work.
- No new entrant receives lower safety, quality, cybersecurity, or technical standards in the name of competition.
- No capability or stakeholder-directed design change enters a ship, module, or system after its production award. Improvements move to the next hull, lot, flight, or scheduled 60-month refit.
Evidence and Program Links
Official acquisition reviews support both sides of this balance: government access to necessary technical data and modular interfaces can reduce vendor lock and improve competition, while overly broad or poorly planned demands can increase prices, reduce bidder interest, and create security or implementation risk. TriSeadon therefore acquires the necessary rights deliberately, protects legitimate background IP, and phases supplier transition instead of assuming ownership.