Aegis Station Logistics Program

Fleet CommanderGround Control for the Lunar Tanker Fleet

The ground-side coordinator that dispatches sorties, deconflicts pads, holds emergency reserves, and maximises water throughput to station — one console commanding the entire 84-tanker constellation.

84
Tankers / 1 Console
11 + 11
Pads / Berths
1 Hz
Fleet Telemetry
// 01 Ground Segment Overview
Safety Boundary
Mission-Critical
Not safety-critical. If the coordinator goes down, every vehicle holds its current mode safely under its own autonomous flight software.

Each tanker flies its own safety-critical flight software — autonomous flight, fault detection, and safing all live on the vehicle. The Fleet Commander is the ground-side brain: it never flies a ship, it orchestrates the fleet.

It talks to all 84 vehicles over the same CCSDS-over-UDP link an individual operator console uses — every tanker is an independent command and telemetry endpoint. The coordinator aggregates per-vehicle telemetry into fleet-wide situational awareness at 1 Hz and issues a small, well-defined command vocabulary back to each ship.

// 02 Ground Control Console

Frames below are screen captures of the coordinator in operation — a live tanker fleet under auto-dispatch, with telemetry refreshing at 1 Hz.

Fleet Commander — fleet overview
FIG. 01 — Fleet Overview: water throughput, the schedule as flown on the fleet clock (launches in the last 24 hours, time after the slot, hours a pad and a berth are held), mode breakdown, pad & berth occupancy — here fourteen hours into the first fleet day, the cadence still filling FC-CONSOLE-001
Fleet Commander — single-vehicle telemetry
FIG. 02 — Vehicle Detail: GNC, propulsion, power, thermal zones & recovery commands FC-CONSOLE-002
Fleet Commander — pad and berth deconfliction
FIG. 03 — Pad & Berth Status: 11 surface pads, 11 station berths, FIFO berthing queue — here on the schedule, each pad showing its stage, the swap arm's step, the fill's step and the minutes to its liftoff FC-CONSOLE-003
Fleet Commander — vehicle grid
FIG. 04 — Vehicle Grid: per-ship mode, charge, reserve and comms health — offline ships flagged in red FC-CONSOLE-004
Fleet Commander — coordinator settings
FIG. 05 — Coordinator Settings: fleet size, auto-dispatch, standby reserve, loading-site mode FC-CONSOLE-005
// 03 Fleet–to–Vehicle Contract

Command Vocabulary — ADR-0014

DISPATCHASSIGN SORTIE
RELEASEFREE PAD / BERTH
SWAP_COMPLETECARTRIDGE SWAPPED
RESUMEEXIT SAFE / STANDBY
SET_MODEFLIGHT GATES
TLM SUBSCRIBESTATE TRACKING

Transport & Telemetry

LinkCCSDS / UDP
Endpoints1 PER VEHICLE
Fleet TLM Rate1 Hz
State ModelTLM-GATED
Console LinkWEBSOCKET
DeploymentGROUND SEGMENT
Clean Separation — FSW ADR-0006 / 0014
The interface is the only coupling between ground and flight. Vehicle FSW is one image flown in 84 copies on each ship's flight processor; the coordinator is a single ground instance managing all 84. Different deployment target, different scaling model, different safety boundary — joined by one deterministic command/telemetry contract.
// 04 What It Coordinates
01 — DISPATCH

Sortie Scheduling

Launch slots stand every 17.6 minutes, 82 a day. A tanker is given the earliest slot its servicing can make and lifts off at it; between pads that finish together the choice is scored on state of charge, idle time, position and wear.

02 — DECONFLICT

Pad & Berth Management

Each surface pad has a line: a returning tanker joins the shortest and waits on the apron. The head of a line is called onto its pad one servicing time before the launch slot it has been given, so a pad is held for servicing and nothing else. On the pad the swap arm and the propellant fill work together, 2.6 hours from the call to liftoff; a berth's arm swaps the cartridge in 1.3. Eleven station berths sit behind a FIFO berthing queue.

03 — RESERVE

Standby Allocation

Holds one to two highest-charge vehicles in emergency reserve per the fleet spec — excluded from routine water duty, ready for emergency tasking.

04 — REROUTE

Surface-to-Surface Routing

Suborbital hops between LUNET nodes to reposition the fleet where the next demand is, without a return to station between legs. The duty type exists in the coordinator; routing logic is not yet built.

05 — RESPOND

Anomaly Response

When a vehicle goes SAFE or ABORT, its pending sortie is reassigned and its pad freed — the fleet heals around the loss without operator intervention. A vehicle past its mode's flight-time limit is called stuck and flagged.

06 — OPTIMISE

Throughput & Awareness

Aggregates 84 telemetry streams into fleet-wide situational awareness, paces each ship's simulator through its coasts, keeps one fleet clock for the pads, the berths and the launch slots, and reports the schedule as flown: launches in the last day, time after the slot, hours a pad and a berth were held.

// 05 The Fleet, as Run in Simulation

The coordinator exists and runs the fleet closed-loop in simulation, as of November 2026: 84 copies of the tanker's flight software, each flying its own water sortie on liquid oxygen and liquid hydrogen, under one ground process. The ships fly themselves. The coordinator decides who flies, when a ship may lift, which berth it takes and when it is released, and which pad it comes home to — the gates that stand on a shared resource or a ground operation — and sends each one when the ship's telemetry says it is ready. Everything between the gates is the vehicle's own. The fleet is the one the fill campaign is sized at: 82 tankers flying and a reserve of two, with eleven pads and eleven berths.

The first run at this size, on 9 November, had no schedule: a turnaround was half a minute of telemetry-gated steps and every ready ship was dispatched at once. All 82 went up within three seconds, arrived at the station within four seconds of each other and queued 78 deep for eleven berths. It showed that one process could manage 84 stacks through 164 sorties with no anomaly and no telemetry packet dropped, and nothing about the fill, which is stated against a launch every 18 minutes and a pad held for at most 3.2 hours.

The run of 10 November is on that schedule. The coordinator keeps one fleet clock, running at the same twenty times real time as the coasts. Launch slots stand on it every 17.6 minutes. Every tanker on the ground waits in a pad's line on the apron and is called onto the pad one servicing time before its slot. The pad's equipment then takes its time: safe and vent checks, the swap arm pulling the empty cartridge and seating a full one while the couplings chill, transfer 45 t of propellant and purge, then inspection and liftoff at the slot. Those steps and their times are the water logistics dossier's, 2.6 hours in all; a berth's arm takes 1.3. Each step ends only when its time has passed and the ship's telemetry shows what the step was for.

Over 2.14 fleet days the fleet made 167 liftoffs in 167 consecutive slots, 82 of them in the last 24 hours, each on average 16 seconds after its slot and never more than 40. A pad was held 2.58 hours and a berth 1.34, against the 3.2 that eleven of each allow. On the second day nine of the eleven pads and five of the eleven berths were the most in use at once, the berth queue never held more than one ship, and each tanker lifted off 23.9 hours after its last: one flight a day. No anomaly, no safing, no step overrun.

On the host, the 84 stacks are 168 processes and 2,100 message queues, and the run held a fifth of a sixteen-core machine with the coordinator's one-second broadcast holding its second. The two pictures below are the two runs played back from their tapes: the surge of 9 November, and the schedule on its second day.

The fleet coordinator's playback at tick 999 of the 9 November run of 84, which had no launch cadence: the sortie drawn as a loop with the station's eleven berths across the top and the eleven pads along the bottom, 84 vehicle cards around the edge, 77 of them reading BERTH and five at berths, the 77 in three rows of dots in the berth FIFO under the station, the reserve pair sitting above pads 2 and 3
Without a cadence, 9 November, tick 999: all 82 ships in service entered BERTHING within four ticks. Five are at berths and 77 wait in the FIFO under the station; the reserve pair sit above pads 2 and 3. Every element drawn is a field of the coordinator's 1 Hz broadcast. FC-SIM-001
The fleet coordinator's playback at tick 6024 of the 10 November run, on the schedule: nine of the eleven pads along the bottom captioned service, safe or inspect with four or five tankers stacked on the apron above each, pads 4 and 5 free with five waiting; five ships at berths across the top; a few dots on each leg of the loop; the centre text reading fleet day 2 09:15, 82 launches in 24 h of 82, 0.3 min after the slot, pad held 2.6 h, berth held 1.3 h, 9 on pads, 43 on the apron
On the schedule, 10 November, fleet day 2 at 09:15: 82 launches in the last 24 hours. Nine pads are servicing, with the tankers waiting on each apron stacked above; five ships are at berths and none is queued. The ships in flight are about four times too many: burns are flown in real time under a clock running at twenty. FC-SIM-002

What the coordinator does not do is stated as plainly. It holds no position for anything: a pad is a name, there is no map, and the loop in the picture is the sortie, not geometry. Each simulated ship has its own ground and no station, so the eleven pads and eleven berths are the coordinator's bookkeeping until the vehicles share one simulated world, which is the open architecture decision the tanker page names. The schedule run has its own limits. Every step took exactly its tabled time, so the run shows that the cadence closes at 2.6 hours on eleven pads and does not show what a slow transfer, a stalled swap or a pad out of service does to it. The split of the swap's 50 minutes into steps and all of the berth's times are the model's own; the dossier gives a berth only its ceiling. A tanker lands into a pad's line and reaches the pad in no time, where the dossier has an apron and nothing that moves a tanker to it. Nothing waits for a pad to come under the orbit. And the burns are flown in real time under a clock at twenty, so about 26 ships were in flight at once where a sortie in proportion would have about seven; pad hours, berth hours and launches per day do not depend on that. No fault has yet been put to the fleet in a run; the abort path and the operator's own acts are the next runs. Surface-to-surface routing is a duty type without routing logic. The fleet has run against simulated vehicles only.

← Back to Aegis Station