1 — The concrete scene
Two boxes work separately but become incompatible together because of voltage, temperature or protocol differences. Integration creates new risks.
The key point is never to isolate this subject from the rest of the spacecraft. A local change often moves mass, power, heat, data, software, testing or risk elsewhere in the system.
2 — Essential words, explained before using them
Before calculating, we define every word that will be used next. The goal is for the symbol to come after the idea, never before it.
- ICD
- Interface Control Document.
- Verification
- Prove compliance with requirements.
- Validation
- Prove fitness for actual need.
- Configuration
- Exact hardware-software-parameter version.
- Budget
- Allocation of a limited resource.
- End-to-end
- Test crossing multiple functions.
3 — See the architecture before calculating
Interfaces
Write mechanical, electrical, thermal, data and software interfaces.
Progression
Unit → assembly → chain → vehicle.
Evidence
Analysis, inspection, test or demonstration by requirement.
Configuration
Evidence belongs to a specific version.
4 — Formulas, only when they answer a question
A formula is useful only if we know which question it answers, what every symbol means, and which units must be used.
How to read it : margin equals capability minus need
Simple absolute margin; real convention must be stated.
How to read it : relative margin in percent
Teaching form, not universal.
5 — What units and margins mean
Keep each budget unit: kg, W, K, N, bit/s, dimensions and protocols do not mix.
6 — Three concrete demonstrations, calculated step by step
Power margin
Capability 1,000 W, need 850 W.
M=150 W
M%=150/850×100
≈17.6%
Thermal interface
Box 120 W, interface 100 W.
Need=120 W
Capability=100 W
M=-20 W
Configuration
Test passed in v3.2, logic changed in v3.3.
Evidence=v3.2
Configuration=v3.3
Determine what needs retest.
7 — Deepening: what the simplified diagram hides
Living ICD
Changes propagate to affected parties.
EMC
A neighbour can emit or suffer interference.
Verification / validation
Meeting a document is not always meeting actual use.
Test as you fly
Make tests and sequences as representative as reasonable.
Anomalies
Understand cause before closing the problem.
8 — Application to an Earth-Mars spacecraft
On an Earth-Mars transit, long duration turns a small weakness into cumulative risk: ageing, drift, consumption, cycles and maintenance become as important as nominal performance.
Communication delay forces the vehicle and possibly the crew to diagnose and reconfigure locally. Design must therefore remain observable, understandable and testable in degraded modes.
9 — Reference dossier: what a real project must still consider
This section deliberately goes beyond the introductory calculation. It connects the concept to interfaces, failures, testing, duration and maintenance so the lesson can serve as a reference chapter rather than a revision card.
Integration means managing boundaries
Two units can work separately and fail when connected. Integration verifies mechanical, electrical, thermal, software, RF, fluid and operational interfaces. Interface Control Documents formalise parameters and ownership, but their value depends on remaining current as the design changes.
Budgets evolve until late in the project
Mass, peak power, data rate and thermal predictions change as detail grows. Systems engineering tracks budgets and margins over time and defines when changes require approval and re-analysis by affected subsystems.
Verification and validation are different
Verification asks whether the system meets its requirements. Validation asks whether those requirements and the resulting system actually satisfy the mission need. Both are necessary; a perfectly compliant system can still solve the wrong problem.
Test as you fly, fly as you test
Testing should represent flight configuration and sequences as closely as practical, while flight should avoid untested modes. A complete Mars mission cannot be reproduced on Earth, so environmental tests, simulations, hardware benches and operational rehearsals are combined with explicit knowledge of what remains extrapolated.
Electromagnetic compatibility is invisible but real
Power converters, motors, radios and digital clocks can disturb other equipment through conducted or radiated noise. Cable routing, shielding, grounding and filters are integration issues, and some problems appear only in the complete configuration.
Anomaly management requires cause, not just replacement
Test anomalies must be recorded, reproduced where possible, analysed and closed with rationale. Replacing a failed part without understanding the cause can hide a systemic problem. Traceability lets similar hardware and interfaces be checked.
Mars integration becomes logistics infrastructure
Adding a module to a settlement requires compatibility with existing power, data, fluids, dimensions, software, safety and maintenance. Local interface standards, test benches, calibration references and configuration management become part of industrial autonomy.
10 — Common traps and bad intuitions
- Qualified components ≠ qualified system.
- Confusing verification and validation.
- Giving margin without definition.
11 — Guided exercises
Question : What question comes before choosing hardware?
Question : Why is a nominal result insufficient?
12 — What to remember
- Explain the topic in simple words before symbols.
- Connect at least four interfaces with other subsystems.
- Redo the three numerical examples without reasoning gaps.
- Identify at least three limits or failure modes absent from the ideal calculation.
13 — NASA sources for further study
Primary institutional sources used to check the lesson structure. Teaching-number examples are identified as such.