Earth-Observation Ground-Data Mission Architect — Civil Space

The mandate

The constellation programme has mature spacecraft and instrument designs, but its ground-data components were procured around separate acquisition, calibration, processing and distribution boundaries. Mission rehearsals can create products, yet teams cannot consistently reconstruct packet loss, auxiliary data, algorithm version and quality flags behind an image delivered to a civil user. Operational acceptance needs a complete evidence architecture.

The deliverable is an Earth-Observation Ground Data Mission Architecture spanning downlink, ingest, raw preservation, calibration, product generation, catalogue and authorised distribution. It will define identities, provenance, quality, latency, reprocessing, continuity and user notice. A reference mission thread and acceptance package must work through primary and contingency ground paths without changing spacecraft-command scope.

Milestone one at week four supplies mission journeys, interface gaps and acceptance risks. Week nine closes milestone two with architecture, contracts and evidence requirements. At week sixteen, milestone three delivers end-to-end rehearsals including loss and reprocessing. The accepted design, supplier obligations, operational playbook and transition backlog form milestone four at week twenty-two.

Acceptance requires mission assurance to trace six unseen products back to acquisition windows, packets, auxiliary sources, calibration and algorithm releases; operators must recover a missed primary pass through contingency procedures; and users must receive correct quality or reprocessing notice. The mission director signs only after an internal team reproduces the evidence chain without consultant assistance.

The client will provide mission requirements, interface documents, pass plans, packet samples, calibration records, algorithms, quality rules, supplier contracts and user commitments. Ground-station and processing teams will support rehearsals inside controlled facilities. Client assurance retains formal qualification authority, while the mission director resolves boundary and supplier decisions within three business days.

Why this is external work

Each supplier can demonstrate its contractual component, but nobody independent owns the evidential journey from instrument acquisition to user product. Programme staff are concentrated on spacecraft readiness and lack capacity to arbitrate interfaces before acceptance. External architecture provides cross-supplier mission evidence without intruding into protected command systems or favouring a downstream platform.

What you will own

• Trace observation request, acquisition, downlink, packet, auxiliary input, calibration, processing, catalogue and distribution evidence end to end.
• Define persistent identities and provenance for passes, instrument modes, raw segments, calibration assets, algorithms and released products.
• Specify quality, completeness, latency, reprocessing and user-notice contracts across every ground-system and supplier boundary.
• Design continuity for missed pass, corrupt segment, unavailable calibration, ground-station loss and delayed distribution.
• Run end-to-end mission threads across primary and contingency paths with injected evidence and timing defects.
• Reconcile acceptance requirements, supplier commitments, operational staffing and lifecycle cost into a sequenced mission decision.
• Transfer qualification scripts, reprocessing governance and evidence review to mission assurance and ground operations.

Candidate qualifications

• Architected mission-critical ground-data systems for Earth observation, scientific missions, weather satellites or comparable civil remote sensing programmes.
• Governed acquisition-to-product provenance across packet handling, calibration, algorithms, quality flags and reprocessing.
• Led end-to-end ground rehearsals involving multiple stations and suppliers under mission timing constraints.
• Designed user notification when products changed after calibration or processing correction.
• Worked within controlled civil-space facilities while keeping data architecture separate from spacecraft-command authority.
• Delivered acceptance evidence internal mission teams could reproduce without continuing supplier or consultancy interpretation.

Non-negotiables

• The named architect must lead Tokyo mission reviews and attend rehearsals at designated ground facilities.
• No commercial attachment may exist with ground-station, processing, archive or distribution suppliers under evaluation.
• Spacecraft command, mission safety and formal acceptance remain with authorised client personnel.
• Controlled mission and partner data cannot leave approved facilities or be used for external benchmarking.

1. 49 words maximum. Describe an Earth-observation product whose quality changed because acquisition or calibration context was missing.
2. 49 words maximum. How would you preserve user trust when a released product requires later reprocessing?
3. 49 words maximum. Which client inputs are indispensable before rehearsing a contingency ground-data path?