Final missions: build a complete and resilient Mars architecture
The previous fifteen modules teach calculations, architecture reading and the limits of overly simple reasoning. Module 16 introduces almost no new concept. Instead, it forces them to connect. A propulsion equation meets a mass budget; a water-consumption estimate meets an emergency reserve; a communications outage meets local authority; and an attractive architecture has to show that it remains operable when reality stops following the nominal scenario.
A final study does not need to imitate a NASA or SpaceX programme. It must be labelled as a Delta-Sierra educational architecture: dated assumptions, reproducible calculations, visible margins and a clear boundary between capabilities demonstrated today and engineering extrapolation.
1. The mission brief: start from functions, not from a favourite vehicle
Each team receives a campaign objective: pre-deploy cargo, transport a crew, land essential elements, remain on the surface long enough to cross a return window, then leave an infrastructure that is more robust than it was on arrival. The first task is to translate this objective into functions: power, air, water, food, thermal control, communications, mobility, maintenance, medical care, refuge, storage, local production and return.
2. Build the architecture as functional chains
A useful architecture reads from input to output: source, conversion, storage, distribution, use, measurement, maintenance and degraded mode. Water is not just a tank. It needs a source, extraction, purification, storage, distribution, recovery, quality analysis and a response if contamination removes one loop from service.
For every life-critical function, the final sheet should identify the nominal path, backup path, endurance of the backup, fault-detection method, any shared resource capable of defeating both paths, and the expected human or automatic action. This table becomes the backbone of the design review.
3. Close the budgets before discussing appearance
An architecture that does not close its budgets is not yet an architecture. At minimum it should track mass, energy, peak power, water, oxygen, food, habitable volume, data storage, communications capacity, spare parts and crew time. Values may be educational assumptions, but their origin and sensitivity must be explicit.
If a resource is used at average rate q for a duration t, the base requirement is q × t. A mission adds losses, variability, refuge days and delay scenarios. The goal is not to find a magical “exact” number; it is to identify which assumption drives the design and how the architecture changes when that assumption moves.
4. Final mission A — cargo must make human arrival less risky
Cargo leaves first. It carries the elements whose absence would make crew arrival unacceptable: initial power, communications, unloading capability, habitat or refuge, reserves, critical spares and possibly local-resource equipment. The study must state what is tested before crew departure, which telemetry demonstrates readiness and which threshold would force the human launch to be delayed.
Then inject a failure: a cargo flight misses its window, a solar array is damaged or a handling rover is immobilised. The team must show whether the site can continue preparing for arrival with reduced capability or whether the campaign has to be reconfigured.
5. Final mission B — human transit is a moving habitat
The crew vehicle must be assessed as a temporary habitat: air, water, thermal control, food, sleep, exercise, hygiene, medical capability, radiation shelter, maintenance and access to equipment. Propulsion alone is not the architecture. A shorter trip may move mass into propulsion; a slower trajectory may increase consumables and exposure. The correct answer is the one that makes the whole system more robust for the chosen scenario.
6. Final mission C — arrival, EDL and site activation
The scenario must connect landing dispersion with surface operations. Two vehicles several kilometres apart may both count as successful landings while making the campaign much harder. The design therefore defines localisation, mobility, towing, energy reserves and the time needed to bring life-critical functions online.
The capstone must also state what happens if the crew arrives while part of the site is still off-nominal. Is there an independent refuge? How long can it operate? Which tasks can be deferred? Which operations remain prohibited until verification is complete?
7. Final mission D — turn an initial base into a durable system
A base that survives one hundred days is not automatically a settlement. The long campaign should show how maintenance, inventory, local production and training progressively reduce dependencies. A locally made part is useful only if material, geometry and quality are controlled. An extracted resource is useful only if it is purified, stored and distributed.
Sustainability therefore appears in loops: recycle more, repair more part families, manufacture selected consumables, increase refuge capacity, document procedures and transfer competence to the next team.
8. Long campaign: 500 sols without a perfect scenario
The operations plan should be long enough for ageing to matter. Filters clog, seals age, batteries lose capacity, dust accumulates, spares are consumed and people fatigue. The schedule must reserve time for inspection, exercise, care, training and lessons learned.
Do not fill every hour. An architecture optimised to full utilisation often assumes nothing unexpected will happen. Time margin is a resilience resource just like spare parts.
9. Injected failures: the mission is not validated until it has been disturbed
- Logistics delay: the next cargo arrives months later.
- Power: a dust event strongly reduces solar production.
- ECLSS: one oxygen-production train is unavailable for several days.
- Communications: Earth is temporarily unavailable or too slow for immediate decisions.
- Mobility: a pressurised rover is immobilised far from the site.
- Medical: one crewmember can no longer perform a primary role.
For each failure, the final dossier explains detection, decision authority, loads shed, available endurance, recovery criteria and the effect on the rest of the campaign. If the answer is “send a replacement from Earth,” it must include launch-window timing and the real delay before the part can become available.
10. Decision gates: know when to say “we do not launch”
A strong dossier is not trying to prove that the mission must fly. It makes visible the condition that requires delay or abort. The ability to say “no” is a mark of engineering maturity.
11. Final quantitative exercise — connect margin to a decision
For the exercise only, suppose a critical reserve is consumed at 18 units per day, the campaign must survive 45 days without outside support, and the team requires a 25% margin. The planning need is:
If measured stock after a failure falls to 860 units, the question is not “can we survive today?” but “what decision do we make now so that a limit is not crossed weeks later?” The team may reduce consumption, start secondary production, cancel an activity or advance return. The capstone must justify the choice with numbers, not intuition.
12. Review package: what the team must deliver
- a mission-and-assumptions page;
- a functional architecture and interface map;
- main budgets with units, margins and sources;
- a cargo–crew–surface–return timeline;
- degraded modes and emergency stocks;
- at least six injected failures;
- a decision-and-authority matrix;
- launch, continue, retreat and abort criteria;
- a register of demonstrated, extrapolated and prospective elements;
- a conclusion naming the three largest residual risks.
13. Evaluate the architecture without rewarding spectacle
The final assessment should reward coherence, traceability and the ability to acknowledge limits. A less spectacular architecture with explicit budgets, backups and decisions is stronger than an impressive concept built on hidden assumptions. The most important criteria are closure of life-critical functions, common-cause control, repairability, margin discipline and the boundary between fact and prospect.
14. The last skill: hand the system to the next team
A durable human mission does not end at return. It leaves data, procedures, qualified parts, known errors and a base that is easier for the next crew to understand. The final documentation therefore explains not only what was built, but what changed during the campaign and why.
At this point the student does not “know Mars” in an encyclopaedic sense. They can do something more useful: state an assumption, quantify it, connect it to other systems, search for what can break it, and explain a decision in a form that another person can verify.