Who it's for · OperatorsRegister · Operations
Operators
Satellite, air and maritime operators — the organisations that fly and run the assets
Coverage you can prove. Before the passes.
fly · task · sustain
Operators: on hardware you own, with evidence a board can audit.
- What does it cost us to depend on someone else's stack?
- Which risks does this retire, and which does it create?
- Can we prove, not assert, that it works?
Operators: programmes your teams can run, and prove they ran.
- Who on my team does what, and what do they need to know?
- Does this cover the whole programme or one phase of it?
- What does the audit trail look like on a bad day?
Built for the work Operators actually do.
- What will I model, and how deep does it go?
- Does it integrate with what I already run?
- Can I try it before anyone signs anything?
Read this as — every reader sees every section; this only changes what leads.
- Organisation types
- 3
- harmonised types rolled up here
- Roles employed
- 17
- distinct, from the estate's role catalogue
- Essential classes
- 14
- of the shared ontology
- Briefs on Academy
- 4
- 1 of 3 types covered
products
What each product does for you
One line per product, per kind of operators — the same lines Data Domain holds for every organisation type.
- Satellite OperatorRun constellation programs with requirements tied to service levels.
- Air OperatorManage fleet and UAS programs with compliance traceability.
- Maritime OperatorRun fleet programs with maintenance and compliance traced.
- Satellite OperatorPlan coverage, avoid collisions, protect fleet uptime.
- Air OperatorPlan SATCOM and surveillance coverage along your routes.
- Maritime OperatorCheck satellite coverage and tracking across shipping lanes.
- Satellite OperatorCertify operators on station-keeping and contingency response.
- Air OperatorTrain crews and operators on mission and safety systems.
- Maritime OperatorTrain crews on navigation, comms, and domain awareness.
- Satellite OperatorTrusted catalog of orbits, ground stations, and assets.
- Air OperatorOne reference for airframes, routes, and airspace.
- Maritime OperatorAuthoritative reference for vessels, ports, and lanes.
- Satellite OperatorSpot constellation rivals and open market gaps.
- Air OperatorTrack route competition and emerging UAS players.
- Maritime OperatorWatch lane competition and fleet movements.
briefs
The briefs behind this page
Each brief covers the challenge, what the platform does about it, and the training modules involved. They live on Academy, public, no sign-in — this page links rather than copies, so a corrected sentence is corrected once.
Satellite Operator
Train operators on real spacecraft scenarios, not slideware.
Spacecraft operators need pattern recognition. They need to have seen enough anomalies, eclipse cycles, attitude drifts, and ground-segment failures to react correctly when something rare happens at 3am. Classroom slides cannot build that. Real fleet time is too expensive to use as a training environment.
Scenario · Resolve an unexpected attitude drift and recover the safe-mode satellite
GEO Satellite Operator
Train your GEO control room today. Build the bench for LEO and MEO tomorrow.
GEO operators run a stable, cash-generating business on assets designed for 15+ years on-orbit. But the commercial model is shifting — LEO broadband constellations, MEO PNT and data-relay layers, and hybrid GEO+LEO service offerings are now the direction of travel. The operators who win the next decade will be the ones whose control rooms can absorb new orbit regimes without hiring a second control room. That means cross-training today, not after the first LEO contract is signed.
Scenario · Plan and execute a routine N/S station-keeping burn inside the longitude box at GEO
LEO Satellite Operator
Run hundreds of passes a day without running your operators into the ground.
LEO constellations invert the operational model every control-room was built for. Instead of one geosynchronous slot kept perfectly still, you run hundreds of platforms through hundreds of short ground passes every day. Conjunction rates are high, ground-station scheduling is the bottleneck, inter-satellite links change topology every minute, and automation does most of the flying. Training that evolved around GEO station-keeping misses the operational tempo LEO demands.
Scenario · Plan a 24-hour pass schedule across a 30-station ground network serving a 120-satellite fleet
CubeSat Operator
Fly a 6U demonstrator like it matters — because it does.
CubeSats are no longer classroom curiosities — they are the first flight asset for most new space programmes, the fastest path to qualifying a payload, and the training ground where tomorrow's mission leaders learn what on-orbit operations actually feels like. But the talent bench is thin: many teams have one senior operator who has flown a mission and a half-dozen students who have never commanded a satellite. The mission cadence does not wait for that gap to close on its own.
Scenario · Walk a new operator from launch-vehicle separation through LEOP to commissioning on a 6U Earth-observation demonstrator
- Satellite Operator: brief available
- Air Operator: no brief yet
- Maritime Operator: no brief yet
No brief yet for Air Operator and Maritime Operator — the products above cover them; the training brief does not exist in the corpus today.
roles
Who works here
17 roles Data Domain expects across these organisations, from the estate's role catalogue — the people a rollout has to carry.
Table: Seniority
| Seniority | Roles |
|---|---|
| Executive | 0 |
| Senior | 2 |
| Mid-Level | 12 |
| Junior | 2 |
| Entry | 1 |
Table: Track
| Track | Roles |
|---|---|
| Civilian | 12 |
| Commissioned Officer | 2 |
| Warrant Officer | 1 |
| NCO | 1 |
| Operator | 1 |
All 17 roles
- Project ManagerSenior
- Supply Chain ManagerSenior
- Air Operations OfficerMid-Level
- Aviation Warrant Officer (153A)Mid-Level
- Comms / RF / TT&C EngineerMid-Level
- Flight ControllerMid-Level
- Flight DynamicistMid-Level
- GNC EngineerMid-Level
- Ground Station EngineerMid-Level
- Mission AnalystMid-Level
- Naval Warfare OfficerMid-Level
- Payload EngineerMid-Level
- Space Debris / Orbital Safety EngineerMid-Level
- Systems EngineerMid-Level
- Logistics NCO / Supply SergeantJunior
- Spacecraft OperatorJunior
- UAV Operator (15W)Entry
essentials
What you will model
The ontology classes Data Domain marks essential for operators — 14 of the estate's shared classes. This is the vocabulary every product speaks.
Table: essential classes by organisation type
| Class | Satellite Operator | Air Operator | Maritime Operator |
|---|---|---|---|
| KPI | ✓ | ✓ | ✓ |
| Maintenance | ✓ | ✓ | ✓ |
| Materiel | ✓ | ✓ | ✓ |
| Mission | ✓ | ✓ | ✓ |
| Schedule | ✓ | ✓ | ✓ |
| Standard | ✓ | ✓ | ✓ |
| Verification | ✓ | ✓ | ✓ |
| Procedure | — | ✓ | ✓ |
| Regulation | — | ✓ | ✓ |
| CONOPS | ✓ | — | — |
| Configuration | ✓ | — | — |
| Readiness | — | ✓ | — |
| Supply Chain | — | — | ✓ |
| Validation | ✓ | — | — |
frame
How this kind of organisation buys
Not a claim about us — a description of you, from the same positioning the whole estate uses, so every product speaks to the same buyer in the same terms.
Who
Operators, integrators, primes, engineering firms.
What moves the decision
Autonomy and margin. Vendor lock-in, IP ownership, switching cost, audit defensibility.
Questions this page didn't answer
Send them and we will answer directly, including the ones with awkward answers.
Get in touch