Skip to content

Chapter 5: Satellite Architecture and Systems Engineering

Key Concepts in This Chapter

  • The systems engineering V-model applied to space mission development

  • Spacecraft bus versus payload decomposition and mass/power/data budgets

  • Mission phase definitions from pre-Phase A through Phase F disposal

  • Requirements hierarchy and derivation methodology

  • Reliability analysis using FMEA/FMECA

  • Model-based systems engineering and Technology Readiness Levels

  • Assembly, integration, and testing philosophy and environmental test campaigns

5.1 Introduction to Satellite Systems Engineering

The development of a space system is among the most demanding engineering undertakings in modern technology. Unlike terrestrial products, a satellite once launched cannot be physically serviced, replaced, or repaired under normal circumstances. Every design decision made on the ground will influence mission success for the entire operational lifetime, which for geostationary orbit (GEO) commercial telecommunications satellites now routinely extends to 15 years or more. This irreversibility imposes a discipline on space engineers that pervades every aspect of mission design: a rigorous, structured, and thoroughly documented approach known as systems engineering.

Systems engineering, as applied to space missions, is not merely a set of administrative processes. It is a holistic methodology for managing complexity, ensuring that all subsystems work together coherently, that requirements are traceable from mission objectives down to individual component specifications, and that every design claim is backed by verified analysis or test evidence. The European Cooperation for Space Standardization (ECSS) and NASA both publish detailed standards that codify systems engineering practice for space, with ECSS-E-ST-10 series and NASA Systems Engineering Handbook (SP-2016-6105) being the primary references.

This chapter presents the foundational tools and processes of satellite systems engineering: the V-model lifecycle, spacecraft architecture decomposition, budgeting methods, reliability analysis, model-based systems engineering, and the assembly and test philosophy. These concepts apply whether the spacecraft in question is a 3-unit CubeSat developed by a university team in eighteen months or a multi-tonne commercial GEO satellite representing a billion-dollar investment over seven years.

5.2 The Systems Engineering V-Model

The V-model is the canonical lifecycle model for space mission development. It is so named because when depicted graphically, the development flow descends on the left side through successive levels of decomposition and design, reaches the component level at the bottom vertex, and then ascends on the right side through successive levels of integration and verification. At every level on the right side, the verification activities correspond directly to the design activities at the equivalent level on the left.

The left side of the V encompasses:

  1. Mission Requirements Definition: The top-level statement of what the mission must accomplish, expressed in terms observable by the customer or user. Examples include “The system shall provide global coverage of tropical precipitation at a revisit time of no more than 3 hours.”

  2. System Requirements: Derived from mission requirements, these specify what the spacecraft system as a whole must do to satisfy the mission needs, without yet prescribing how.

  3. Subsystem Requirements: Each functional subsystem (power, attitude control, propulsion, thermal, communication, on-board data handling, structure) receives a set of allocated requirements derived from the system requirements through a process of functional decomposition and requirements allocation.

  4. Equipment/Component Requirements: The lowest level specifications, applicable to individual units, assemblies, or components.

The right side of the V encompasses the verification activities:

  1. Unit Qualification and Acceptance Testing: Individual components and assemblies are tested against their specifications, first at qualification levels to demonstrate design margins, and subsequently at acceptance levels for each flight unit.

  2. Subsystem Verification: Assembled subsystems are tested in relevant environments. For example, the propulsion subsystem may be leak-tested and functionally checked before integration into the spacecraft.

  3. System Qualification and Acceptance Testing: The complete spacecraft is subjected to the environmental test campaign described in Section 5.14.

  4. Mission Verification: During launch campaign, in-orbit commissioning, and early operations, all mission-level requirements are demonstrated.

Figure 5.1. The systems engineering V-model for space mission development. The left branch represents successive decomposition and design; the right branch represents successive integration and verification. Horizontal arrows connect each design level to its corresponding verification activities.

A critical concept within the V-model is that verification methods must be defined at the same time as requirements. ECSS-E-ST-10-02 defines four verification methods: Test (empirical demonstration), Analysis (mathematical or simulation-based, which may include similarity to previously qualified items), Review of Design (use of approved records or evidence), and Inspection (visual or dimensional examination). Each requirement must be assigned at least one verification method, and the choice has significant cost and schedule implications.

5.3 Spacecraft Architecture: Bus and Payload

A spacecraft is conventionally decomposed into two principal elements: the platform (or bus) and the payload. This distinction reflects the fundamental separation between mission-specific functionality and the supporting infrastructure that enables it to operate in space.

5.3.1 The Spacecraft Bus

The spacecraft bus comprises all subsystems that are not part of the primary mission instrument or communication payload. The bus provides power generation and storage, attitude control and navigation, thermal regulation, mechanical structure and mechanisms, inter-satellite and ground communications (TT&C), on-board data handling and storage, and propulsion. Each of these is a complex engineering subsystem in its own right.

Major commercial bus platforms have been developed by the prime spacecraft manufacturers and are used across multiple satellite programs, amortizing development costs and leveraging flight heritage:

  • Boeing 702: A modular GEO platform family: the 702HP (high power, payload power up to roughly 18 kW), the 702MP (medium power) and the 702SP (small, all-electric). It has been used for Intelsat, SES and other commercial and government satellites.

  • Airbus Eurostar 3000: A widely used European GEO commercial platform, designed for lifetimes of 15 years or more (E3000 up to roughly 16 kW of payload power; the newer Eurostar Neo extends this towards 20 kW and above). Electric propulsion options exist for orbit raising and station keeping.

  • Thales Alenia Space Spacebus 4000: French–Italian GEO platform in the mid-to-high power class, used for Arabsat, SES, and Telenor satellites.

  • Lockheed Martin A2100: Modular GEO bus, the most numerous platform in the Lockheed Martin portfolio, with variants serving military (AEHF, SBIRS) and commercial customers.

  • SSTL-150 and SSTL-300: Surrey Satellite Technology Ltd LEO platforms optimised for Earth observation, in the 150 kg and 300 kg class respectively, with standardised interfaces.

5.3.2 The Payload

The payload is the mission-specific element. For a telecommunications satellite, the payload is the transponder chain: antennas, low-noise amplifiers, filters, frequency converters, high-power amplifiers (typically TWTAs or SSPAs), and the multiplexing network. For an Earth observation satellite, the payload is the imaging instrument: the telescope optics, focal plane arrays, on-board image processing electronics, and associated calibration devices. For a scientific mission, the payload may be a suite of instruments measuring particle fluxes, electromagnetic fields, or atmospheric composition.

The payload requirements drive the spacecraft design in a top-down manner. If the science instrument requires the telescope to point at a target with an accuracy of 0.01 arcseconds, this translates directly into stringent attitude control and micro-vibration requirements on the bus. If the payload data rate is 1 Gbps, this flows down to the data handling and downlink subsystem sizing.

Figure 5.2. Simplified satellite block diagram showing the principal functional interfaces between the bus subsystems and the payload. The OBDH serves as the central data processing node, while the PCDU manages all power flows.

5.4 Mission Phases

The lifecycle of a space mission is divided into phases by both ESA and NASA, with broadly equivalent definitions. The ECSS framework defines seven phases labelled 0 through F:

Pre-Phase A (Phase 0): Mission Analysis and Needs Identification. This is the conceptual exploration phase, typically lasting 3–12 months. The objective is to determine whether a mission concept is technically feasible and scientifically or commercially justified. Trade studies are performed at a high level of abstraction. Mission analysis tools are used to size orbits, coverage patterns, and delta-v requirements. Preliminary budgets are developed with large margins (\(\pm\)50% or more). The deliverable is a Mission Analysis Report and a recommendation to proceed (or not) to Phase A.

Phase A: Feasibility. A more detailed feasibility study lasting 6–18 months. Multiple competing concepts may be studied. The key questions are whether the mission can be achieved within the available resources (cost, schedule, technology). The Mission Concept Review (MCR) or System Requirements Review (SRR) gates this phase. TRL requirements are assessed and technology development plans are initiated for any item below TRL 5.

Phase B: Preliminary Design. The selected concept is developed to a preliminary design level. All subsystem architectures are defined. Preliminary Design Review (PDR) is the exit gate. Mass, power, and delta-v budgets are tightened to \(\pm\)20% margins. Key design decisions are made and documented in a System Design Document (SDD). Long-lead items for procurement are identified.

Phase C: Detailed Design. Full design detail is developed down to the component level. All drawings, interface control documents (ICDs), and manufacturing specifications are produced. Critical Design Review (CDR) is the exit gate. After CDR, no further design changes are permitted without formal change control. Mass and power budgets are at \(\pm\)5–10% confidence.

Phase D: Manufacturing, Assembly, Integration and Test (AIT). Hardware is procured and manufactured, assembled at unit level, integrated into subsystems, and integrated into the complete spacecraft. The full environmental test campaign (Section 5.14) is completed. Flight Acceptance Review (FAR) gates delivery to the launch campaign. Launch Readiness Review (LRR) approves the launch.

Phase E: Operations. The mission is launched and operated. This phase includes Launch and Early Orbit Phase (LEOP), in-orbit commissioning, and routine operations. Mission performance is monitored against requirements. Anomaly resolution activities are conducted as needed.

Phase F: Disposal. At end of life, the spacecraft is deorbited (LEO) or moved to a graveyard orbit (GEO) in accordance with inter-agency debris mitigation guidelines. Propellant tanks are vented and batteries are passivated to prevent accidental fragmentation.

5.5 Requirements Hierarchy and Derivation

The requirements hierarchy is the formal structure that connects the mission objectives to the lowest-level component specifications. Each level of the hierarchy must satisfy the level above it, and derivation of lower-level requirements from higher-level ones must be traceable, justified, and documented.

5.5.1 Mission Requirements

Mission requirements are expressed from the perspective of the mission stakeholder (customer, science community, operational agency) and describe what the mission must achieve, not how. They are typically expressed in terms of mission-level observables: coverage, resolution, revisit time, data latency, link availability, capacity, accuracy. A mission requirement for an Earth observation mission might read: “The system shall image any point on the Earth’s surface between latitudes 60N and 60S with a ground sample distance of 1 m or better at least once every 24 hours.”

5.5.2 System Requirements

System requirements are derived from mission requirements by identifying the physical and functional characteristics that the complete spacecraft system must possess to meet those mission needs. The derivation process involves analysis, simulation, and trade studies. The 1 m GSD, 24-hour revisit example above leads directly to orbit selection (sun-synchronous LEO at 500–600 km, driving specific altitude and inclination constraints), instrument aperture sizing (at least 0.5 m primary mirror for 1 m GSD at 500 km), and swath width/agility requirements (number of imaging opportunities per day needed to achieve 24-hour revisit at any point on Earth).

5.5.3 Subsystem Requirements

Subsystem requirements are the allocations from system level to each functional subsystem. Requirements allocation must be self-consistent: the sum of allocations must not exceed what the system-level budgets provide. A power budget allocating 100 W to the payload must leave sufficient margin when summed with all other subsystem allocations. Mechanical interface requirements (envelope, mass, centre of mass location, first-mode frequency) are derived from launch vehicle interface requirements and spacecraft structural analysis.

5.5.4 Component Requirements

Component requirements specify the performance, environmental robustness, reliability, and interface characteristics of individual procurement items. They are the inputs to supplier statements of work. Critical components such as processors, memory devices, power semiconductors, and precision optical elements have radiation tolerance requirements derived from the orbit radiation environment analysis.

5.6 Spacecraft Mass Budget

The mass budget is one of the most fundamental engineering control documents for a spacecraft program. Launch vehicle capability is a fixed constraint; the total wet mass (including propellant) of the spacecraft must not exceed the available launch mass at the specified orbit injection point. Mass budgets must be maintained throughout the program with associated confidence levels and margins.

Typical mass allocations as fractions of dry spacecraft mass are shown in Table 5.1. These ranges reflect the diversity of spacecraft designs, from lightweight remote sensing satellites with modest power needs to high-power telecommunications platforms with large deployable solar arrays.

Table 5.1. Typical ranges of subsystem mass as a percentage of dry mass, with illustrative example masses (kg) for three representative mission classes.
Subsystem Typical Range (%) 500 kg GEO 100 kg LEO EO 3U CubeSat
(kg) (kg) (kg)
Structure 15–25 100 20 0.30
Propulsion (dry) 5–20 60 5 0.05
Power (arrays+PCDU) 15–25 90 18 0.25
Thermal 2–5 20 4 0.05
ADCS 5–10 40 8 0.15
TT&C 2–5 15 3 0.10
OBDH 2–3 10 2 0.10
Harness 3–5 20 4 0.05
Payload 20–40 120 30 0.70
Dry Mass Total – 475 94 1.75
System margin – 25 6 0.25
Propellant – – – –
Total Wet Mass – 500+prop 100+prop 2.00+prop

ESA and ECSS practice (see ECSS-E-ST-10-02 and the ESA margin philosophy documents) requires that system-level mass margin (also called system margin or design maturity margin) be applied on top of all subsystem mass estimates. The margin level depends on the maturity of the design: at system requirements review the margin is typically 20%, reducing to 10% by CDR, and to 5% for the flight model at delivery.

5.7 Power Budget

The power budget establishes that the electrical power generation capacity of the spacecraft exceeds the total power demand at all times during the mission, including the most demanding operational scenarios and end-of-life conditions.

5.7.1 Power Load Analysis

Power loads are compiled from the peak and average power consumption of every electrical unit on the spacecraft. Three operational modes are typically analysed:

  • Sunlight nominal: All subsystems operating in their nominal configuration, solar arrays generating power, batteries on float charge.

  • Eclipse: Solar arrays offline, batteries supplying all loads. Power management may reduce non-essential loads.

  • Peak: Brief periods of high power demand, such as during orbit manoeuvres or high-duty-cycle payload operation.

5.7.2 End-of-Life Power Generation

Solar array power output degrades over the mission lifetime due to radiation damage, UV darkening of the coverglass adhesive, and micro-meteoroid impacts. The beginning-of-life (BOL) and end-of-life (EOL) array power outputs are related by:

\[P_{\mathrm{EOL}} = P_{\mathrm{BOL}} \times \mathrm{RF} \times \cos(\theta)\tag{5.1}\]

where RF is the remaining factor accounting for all degradation mechanisms, and \(\theta\) is the sun angle incidence (off-normal) at worst case. For a typical triple-junction GaAs array in GEO over 15 years, RF is approximately 0.77–0.82.

A design margin of at least 20% on the EOL power generation is typically required by ECSS, meaning the array must generate 120% of the required load at EOL under worst-case sun angle.

5.7.3 Delta-V Budget

The delta-v (\(\Delta v\)) budget quantifies the total propulsive manoeuvre capability the spacecraft must provide. Using the Tsiolkovsky rocket equation, the required propellant mass is:

\[m_{\mathrm{prop}} = m_f \left( e^{\Delta v / (I_{sp} \cdot g_0)} - 1 \right)\tag{5.2}\]

where \(m_f\) is the final (dry + residual propellant) mass, \(I_{sp}\) is the specific impulse of the propulsion system, and \(g_0 = 9.80665\) m/s\(^2\) is the standard gravitational acceleration.

A representative delta-v budget for a GEO telecommunications satellite is:

Table 5.2. Representative delta-v budget for a GEO telecommunications satellite (15-year mission).
Manoeuvre \(\Delta v\) (m/s) Notes
GTO to GEO apogee raise 1500 Apogee kick motor or EP orbit raising
North-south station keeping 750 50 m/s/year \(\times\) 15 years
East-west station keeping 30 2 m/s/year \(\times\) 15 years
Attitude control (angular momentum dump) 30 Thruster desaturation
Orbit maintenance (eccentricity control) 10
End-of-life disposal (to graveyard) 11 300 km above GEO
Subtotal 2331
Contingency (5%) 117
Total 2448

North-south station keeping dominates GEO propellant consumption because of the luni-solar perturbations that cause orbital inclination drift. A GEO spacecraft that does not perform north-south station keeping will accumulate inclination at approximately 0.75/year, causing the sub-satellite point to trace a figure-eight pattern (analemma) that degrades antenna pointing from fixed Earth terminals.

5.8 Data Budget

The data budget ensures that the spacecraft can acquire, store, process, and downlink the volume of data generated by the payload within the constraints of the mission design. For an Earth observation mission, the key parameters are:

\[V_{\mathrm{daily}} = R_{\mathrm{payload}} \times t_{\mathrm{imaging}} \times \eta_{\mathrm{compression}}\tag{5.3}\]

where \(R_{\mathrm{payload}}\) is the raw data rate of the instrument in bits per second, \(t_{\mathrm{imaging}}\) is the daily imaging time, and \(\eta_{\mathrm{compression}}\) is the compression ratio applied by on-board processing. The resulting daily data volume must be downlinked within the available contact time, which depends on the ground station network geometry and link budget. For LEO satellites, typical X-band downlink rates of 300–800 Mbps and 2–4 contact passes per day of 5–10 minutes each provide downlink capacities of 100–300 Gbits per day.

5.9 Failure Modes, Effects, and Criticality Analysis

Failure Modes, Effects, and Criticality Analysis (FMEA/FMECA) is the systematic methodology for identifying how individual component failures propagate through the spacecraft system, and for assessing the severity (criticality) of the resulting mission impact. It is a required activity for space missions under both ECSS and NASA standards.

5.9.1 FMEA Methodology

For each identifiable failure mode of each component or unit, the FMEA documents:

  1. Failure mode: The specific way in which the item fails (e.g., open circuit, short circuit, mechanical seizure, sensor drift).

  2. Failure cause: The physical mechanism that leads to the failure mode (e.g., electromigration, fatigue crack, radiation single event latch-up).

  3. Local effect: What happens at the failing component level.

  4. Next higher level effect: The consequence at the subsystem level.

  5. End effect: The consequence at the mission/spacecraft level.

  6. Detection method: How the failure can be detected by telemetry or built-in test.

  7. Compensating provisions: Redundancy, workarounds, or operational mitigations.

  8. Criticality category: Typically Category I (catastrophic/loss of mission), Category II (critical/major mission degradation), Category III (marginal), Category IV (minor).

5.9.2 Single Point Failures

A single point failure (SPF) is a failure mode that, if it occurs, directly causes a Category I or II outcome without any redundancy providing relief. The goal of reliability design is to eliminate or contain SPFs. For space missions, ECSS requires that all Category I SPFs be identified, and that either design redundancy eliminates them or the program formally accepts the risk with appropriate justification.

Criticality number (CN) in FMECA is computed as:

\[\mathrm{CN}_{ij} = \beta_{ij} \times \alpha_j \times \lambda_p \times t\tag{5.4}\]

where \(\beta_{ij}\) is the conditional probability that the failure mode causes the end effect, \(\alpha_j\) is the failure mode ratio (fraction of item failure rate attributable to this mode), \(\lambda_p\) is the part failure rate (per hour), and \(t\) is the mission duration in hours.

5.10 Design Margin Policy

Design margins are the quantified safety buffers between the design capability and the predicted extreme conditions the spacecraft will experience. ECSS practice applies them at all levels of the design hierarchy. Key margin policies include:

  • Structure: Factors of safety (FoS) on yield and ultimate strength for metallic structures, whose values depend on the standard and the verification approach (typically of the order of 1.1–1.25 on yield and 1.25–1.5 on ultimate; see ECSS-E-ST-32-10C or the applicable launcher requirements). Composite structures typically carry higher factors due to greater statistical variability.

  • Power: Beginning-of-life solar array power shall exceed the maximum load by at least 20%. EOL array power shall meet load requirements with 5% margin.

  • Link budget: Telecommunications links shall include a minimum margin of 3 dB above the required carrier-to-noise ratio.

  • Thermal: Component temperatures shall remain within qualification limits with a margin of at least 5–10C.

  • Data storage: On-board mass memory shall provide at least 20% more capacity than the maximum expected data volume.

  • Delta-v: Propellant budget shall include a system margin of 5–10% on top of all identified manoeuvre requirements.

5.11 Spacecraft Operating Modes

Modern spacecraft are designed with a hierarchy of operating modes that provide graceful degradation in the event of anomalies. The mode hierarchy is typically managed by the On-Board Software (OBSW) and defined in the spacecraft’s Functional Requirements Document:

Launch and Early Orbit Phase (LEOP) Mode: The spacecraft is in this mode from separation from the launcher to completion of solar array deployment and initial attitude acquisition. The spacecraft is in a power-constrained, body-stabilised or spinning configuration. Only essential systems are active.

Safe Mode: An autonomous on-board protection mode triggered by critical anomalies such as under-voltage, thermal over-limit, or loss of ground contact for an extended period. In safe mode, the spacecraft enters a Sun-pointing or minimum-power attitude, sheds non-essential loads, and waits for ground intervention. Safe mode software is held in non-volatile protected memory and is itself protected against software corruption.

Survival Mode: The most power-constrained mode, triggered by extremely low battery state of charge. Only the on-board computer, receiver, and essential heaters remain powered. This mode ensures the spacecraft survives worst-case eclipse or contingency situations.

Nominal Operational Mode: The spacecraft is in its designed operational configuration, with payload active, all subsystems in their intended states, and ground operations following routine procedures.

Manoeuvre Mode: During orbit correction or station-keeping manoeuvres, the spacecraft transitions to a dedicated attitude and power mode that accommodates thruster operations. Star trackers may be excluded from use during thruster burns due to plume contamination risk.

5.12 Model-Based Systems Engineering

Model-Based Systems Engineering (MBSE) represents the transition from document-centric to model-centric development. Rather than maintaining consistency across dozens of separate Word documents and Excel spreadsheets, MBSE uses a formal system model as the authoritative source of truth for requirements, architecture, interfaces, and verification status.

The primary modelling language for MBSE in space applications is SysML (Systems Modelling Language), which provides standardised diagram types:

  • Block Definition Diagrams (BDD): Define the hierarchical decomposition of the system into subsystems, assemblies, and components.

  • Internal Block Diagrams (IBD): Show the internal structure of a block and its interconnections, including power, data, and mechanical interfaces.

  • Requirements Diagrams: Capture requirements as model elements with formal derivation and verification links.

  • Activity Diagrams: Describe functional behaviours and operational scenarios.

  • Parametric Diagrams: Encode quantitative constraints and enable model-based trade studies through parameter binding.

Tools commonly used in space MBSE practice include Cameo Systems Modeler (formerly MagicDraw) for SysML modelling, IBM DOORS (Dynamic Object-Oriented Requirements System) for requirements management, STK (Systems Tool Kit) for orbital analysis, and MATLAB/Simulink for simulation-based verification.

The key advantage of MBSE is consistency maintenance: a change to a requirement automatically propagates to all linked design elements and verification items, eliminating the common problem of “requirements drift” where documents become inconsistent over time.

5.13 Technology Readiness Levels

Technology Readiness Level (TRL) is a standardised scale, originally developed by NASA, for assessing the maturity of a technology or engineering development. The ESA adaptation used in European space programs assigns TRL values from 1 (lowest, basic principles observed) to 9 (highest, actual system qualified through successful mission operations):

Table 5.3. Technology Readiness Level (TRL) definitions as applied in space mission development.
TRL Definition
1 Basic principles observed and reported
2 Technology concept and/or application formulated
3 Analytical and experimental critical function or characteristic proof of concept
4 Component and/or breadboard validation in laboratory environment
5 Component and/or breadboard validation in relevant environment
6 Model or prototype demonstration in relevant environment (ground or space)
7 System prototype demonstration in space environment
8 Actual system completed and flight qualified through test and demonstration
9 Actual system proven through successful mission operations

Space mission programs typically require that all technologies used in flight equipment achieve TRL 6 by the time of Preliminary Design Review (PDR), with the remaining maturation to TRL 7–8 completed before flight acceptance. Technology development programs (TDPs) are initiated early in the mission lifecycle to mature critical technologies from lower TRL levels. The use of below-TRL technologies is a major risk driver and cost/schedule risk for space programs.

5.14 Assembly, Integration, and Testing

The AIT phase (Phase D) is where the spacecraft hardware comes together and is subjected to a rigorous campaign of functional and environmental testing to demonstrate fitness for flight. AIT philosophy distinguishes between:

  • Qualification testing: Demonstrates that the design withstands conditions exceeding the mission environment by defined margins (qualification levels). Performed on qualification models (QM) or on the first of a series (proto-flight model, PFM) to a qualification test level.

  • Acceptance testing: Demonstrates that each individual flight unit is free of workmanship defects. Performed at acceptance levels, which are lower than qualification levels (typically the maximum predicted flight levels) and use a shorter test duration.

5.14.1 Cleanroom Requirements

Spacecraft integration is performed in a cleanroom environment to protect sensitive optical surfaces, connectors, and mechanical interfaces from particulate contamination. The cleanliness level is specified according to ISO 14644-1:

  • ISO Class 7 (formerly Class 10,000): Maximum \(352,000\) particles/m\(^3\) of \(\geq 0.5~\mu\)m. Suitable for spacecraft integration, antenna assembly, and general AIT activities.

  • ISO Class 6 or better: Required for focal plane array installation, laser optics assembly, and contamination-critical mirror surfaces.

Electrostatic Discharge (ESD) protection is equally critical. All personnel working with spacecraft electronics must wear grounded wrist straps or ESD-safe footwear, and all work surfaces, tools, and storage containers must be ESD-safe. Single-event latch-up susceptible devices and sensitive CMOS components are particularly vulnerable to ESD damage, which may cause latent failures not detectable until the component is in orbit.

5.14.2 Mass Properties Measurement

Before and after integration, the spacecraft mass properties (total mass, centre of mass location, and moments of inertia tensor) are measured using precision weighing, CG measurement, and bifilar/trifilar suspension pendulum methods. Mass properties data are inputs to launch vehicle separation analysis and to the spacecraft’s attitude control system design. Typical measurement accuracy requirements are:

  • Mass: \(\pm 0.1\%\)

  • Centre of mass: \(\pm 1\) mm per axis

  • Moments of inertia: \(\pm 2\%\)

5.14.3 Environmental Test Campaign

The environmental test campaign demonstrates that the spacecraft survives the launch environment and functions correctly in the space thermal/vacuum environment:

Sinusoidal Vibration: Simulates the quasi-static and low-frequency dynamic loads during launch. The spacecraft is swept from 5 to 100 Hz at a specified acceleration level (typically 0.5–1.0 g for low-frequency sweep) in each of the three orthogonal axes. Notching at structural resonances is applied based on interface force limits agreed with the launch vehicle authority.

Random Vibration: Simulates the broadband excitation from launch acoustic and aerodynamic loads, particularly during transonic and maximum dynamic pressure phases. Specified as a Power Spectral Density (PSD) in g\(^2\)/Hz over the 20–2000 Hz range. Qualification levels are typically about 3 dB above the maximum predicted flight levels, with acceptance tests at the predicted levels, depending on the launcher and applicable standard.

Acoustic Testing: Large spacecraft for which acoustic excitation dominates over direct mechanical excitation are tested in an acoustic chamber (reverberant facility). Sound pressure levels of 130–145 dB at qualification level are typical for medium to large spacecraft.

Shock Testing: Simulates the pyrotechnic shock generated by stage separation, fairing jettison, appendage deployment, and spacecraft separation events. Shock Response Spectra (SRS) of 1000–3000 g at high frequencies (\(> 1\) kHz) are typical. Shock levels attenuate rapidly with distance from the pyrotechnic device, so sensitive components are mounted away from shock sources.

Thermal Vacuum (TV) Testing: The spacecraft is placed in a large vacuum chamber (pressure \(\leq 10^{-5}\) mbar) and thermally cycled between hot and cold operational limits (typically \(-30\degree{}\)C to \(+70\degree{}\)C for non-extreme cases) while fully functional. TV testing reveals workmanship defects such as cold solder joints, connector fretting, and adhesive outgassing that are not detectable in ambient conditions. Thermal balance testing during the same campaign validates the thermal mathematical model.

Electromagnetic Compatibility (EMC): Conducted and radiated emissions from the spacecraft are measured and compared against limits. Conducted and radiated susceptibility to external fields is tested. EMC testing ensures the spacecraft does not interfere with its own subsystems or with the launch vehicle avionics, and verifies immunity to radio frequency interference (RFI) in the operational environment.

5.15 Summary

This chapter has presented the foundational framework of satellite systems engineering. The V-model provides the lifecycle structure within which requirements flow down from mission objectives to component specifications, and verification evidence flows back up to close requirements at each level. The bus/payload decomposition, combined with rigorous mass, power, delta-v, and data budgets, gives the systems engineer the tools to allocate resources across subsystems in a controlled manner. FMEA/FMECA provides a structured method for identifying and managing reliability risks, while design margin policies quantify the safety buffers against uncertainty. The MBSE paradigm, implementing requirements in DOORS and architecture in SysML tools such as Cameo, is progressively replacing document-centric practices in major space programs. TRL management ensures that technology maturity risks are identified and mitigated before they threaten mission schedule and cost. Finally, the AIT phase closes the V-model loop by subjecting the integrated spacecraft to a comprehensive environmental test campaign that gives confidence that the spacecraft will survive launch and perform correctly throughout its operational life.

The subsystems that populate the spacecraft bus—power, attitude control, propulsion, thermal, communications, and data handling—are addressed in depth in the following chapters, building on the architectural foundation established here.