TriSeadon Fleet Line

Access by Need

I need fleet-level logicHow three classes combine into one force outcome. I need the standard operating formationThe preferred TriSeadon Task Group and how it scales by mission. I need mission coverageASW, AAW, ASuW, QRF, C2, and UxV tasks. I need common-core standardsUniversal interfaces, material standards, and upgrade control. I need the actual build scheduleOpen the year-by-year dates, lanes, refits, and deliveries board.

3 Classes = 1 Fleet Effect

TriSeadon fields FFG, DDG, and CAG as one coordinated fleet family rather than patching mission coverage together ship by ship. The classes are engineered together but enter hull production in the locked sequence of FFG first, CAG second, and DDG third. Specialization determines what each class does best; common standards, networks, logistics, and upgrade paths ensure the three classes fight and sustain as one fleet.

Fleet acquisition rule: begin with mature technology, current workers, and active shipyards, then expand national capacity while construction proceeds. The hulls carry protected service-life margins and common upgrade interfaces so future sensors, weapons, unmanned systems, computing, and power equipment can be installed across the fleet without creating three new ship programs or structurally redesigning every class.

The designations in plain language: FFG means Guided-Missile Frigate, an escort optimized for anti-submarine warfare. DDG means Guided-Missile Destroyer, a larger multi-mission combatant centered on air and missile defense. CAG means Guided-Missile Heavy Cruiser, using CA for the heavy-cruiser lineage and G for guided-missile capability; it serves as the flagship, heavy surface-strike combatant, major-gun platform, aviation-support node, QRF platform, and full medical-center capability.

FFG Contribution

Escort, convoy protection, distributed sea control, and persistent ASW screening.

DDG Contribution

Air and missile defense backbone, high-end combat system integration, and theater defense depth.

CAG Contribution

Command, strike coordination, and quick-reaction force orchestration with broader battlespace control.

Open Fleet Baseline Detail | Open Program Timeline | Open Year-by-Year Build and Refit Schedule

TriSeadon Task Group

The TriSeadon Task Group (TTG) is the preferred surface-centric operating model and the formation for which the three classes are designed to produce their strongest combined effect. It is a planning baseline, not an unbreakable deployment rule.

1 CAG

Flagship command, heavy surface and shore fires, aviation, QRF, medical depth, and task-group coordination.

2 DDGs

Distributed air and missile defense, radar and fire-control coverage, escort, and independent action capacity.

3 FFGs

Distributed ASW screen, sea-lane control, acoustic search geometry, and persistent undersea prosecution.

1 Supporting SSN

Undersea reconnaissance, screening, strike, and submarine prosecution; a second SSN may reinforce a high-threat mission.

Flexible by design: commanders may add, remove, substitute, or detach ships according to threat, geography, readiness, and mission. DDGs can operate independently or lead smaller distributed groups. FFGs may detach for escort, port visits, chokepoint patrol, or ASW search while remaining connected to the wider sensor and command network. The SSN is assigned in support and may operate well beyond the visual formation under appropriate submarine command relationships.

Wider-force integration: one TTG can reinforce a carrier, LHA, LHD, LPD, convoy, or independent theater mission. Two TTGs may combine as a TriSeadon Battle Force (TBF) for a larger carrier-support, amphibious-support, sea-control, or wartime operation.

Doctrine: preserve the combined ASW, AAW, ASuW, aviation, QRF, medical, sensor, and magazine advantages of the baseline whenever practical, without forcing commanders to preserve a fixed formation when a different mix better serves the mission.

Mission Envelope

Core Warfare Areas: ASW, AAW, ASuW across one shared command architecture. Air Detachments: CAG air assault and QRF support, DDG SAR-first aviation, and FFG persistent ASW aviation integrated at task-group level. UxV Operations: MQ-19 Aerosonde, MQ-27 ScanEagle, RQ-21 Blackjack-compatible and future VTOL UAVs; USVs; and a common SeaFox, very-small UUV, and small UUV/Seaglider-family package extend ASW, mine defense, surveillance, targeting, communications relay, route reconnaissance, counter-drone, QRF-overwatch, and recovery coverage. QRF Tasks: reinforce, exfil, medivac, extract, attack, VIP transport, and crisis negotiation support. C2 Integration: command-and-control alignment with current USN fleets, CVN groups, SSN/SSBN support patterns, and allied navies.

Common Core and Universal Standards

Shared interfaces, combat-system logic, and maintenance doctrine.
Common physical layout rule: wiring runs, cooling hookups, exhaust routing standards, bolt patterns, plugs, access logic, and core service layouts are standardized across all three classes wherever the common architecture applies.
Common ship-service rule: water makers, HVAC/A/C plants, pumps, valves, and selected tank/service packages are standardized as far as practical around the same removable fleet-support logic used for the larger machinery baseline.
Common acoustic warfighting rule: every skid, sled, packaged plant, machinery room, and engine room is insulated, padded, vibration-isolated, and sound-damped to USN marine-grade quiet-running standards across all three classes.
Common material and SKU strategy to reduce supply complexity.
Planned modernization cycles to prevent capability drift.
Baseline design control to avoid unplanned variant explosion.

Logistics Line | Fuel and Baseline Utility Stack | Program Timeline

Tri-Power and Duty Cycle

Tri-power concept: TriSeadon uses three power sources across the fleet architecture: diesel generation for routine cruise, station-keeping, and hotel loads, gas turbines for sprint and combat surges, and PRIME battery capacity for transient loads, short electric-only quiet-mode operations, ride-through reserve, and resilience.

Why it matters: the fleet is designed so combatants do not live on turbines during ordinary operations. Diesels and batteries carry the low- and medium-speed burden, while turbines are preserved for the moments when speed and peak power really matter.

FFG application: quiet-running ASW posture benefits from diesel-dominant operation and low-speed battery support.
DDG application: the ship keeps sprint and combat margin available without paying Burke-style turbine-hour penalties during routine steaming.
CAG application: the larger hull uses the same tri-power logic at greater scale, supporting command load, aviation support demand, and heavier combat-system draw without making turbines the default answer to everything.
Operational effect: lower routine fuel burn, fewer turbine hours, longer overhaul intervals, and more predictable maintenance cycles across the fleet.
Combat effect: power is treated as a warfighting resource, so electrical demand from sensors, EW, aviation support, unmanned systems, and future weapons is built into fleet architecture instead of bolted on later.

Open Fleet Baseline Detail | Open Logistics Line

Next Drill-Downs

Ship and Builder Line for platform-level detail.

Class Technical Profiles for technical comparison.

Industrial Base Line for yard roles, build locations, and site logic.