Resilience vs Architectural Simplicity
Design multifunction components for graceful degradation so resilience requirements are met without compounding verification burden under functional safety standards.
CyberTRIZ analysis · Space contradiction RMA015 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Resilient spacecraft can continue providing useful mission capability despite failures, environmental disturbances, infrastructure interruptions, or degraded equipment. Creating this resilience often introduces redundant paths, alternative modes, additional software, backup communications, and reconfiguration capability. These additions can make the architecture increasingly complex and difficult to verify.
Space TRIZ Resolution
Resilience should come from flexible use of existing resources rather than unlimited addition of backup systems. Multifunction components, graceful degradation, functional redistribution, standardized recovery modes, and external mission resources can provide alternative paths without duplicating complete architectures.
Applicable TRIZ Principles
Principle 6 – Universality enables existing resources to perform alternative functions during failures.
Principle 15 – Dynamics reconfigures the architecture according to available capability.
Principle 24 – Intermediary uses other spacecraft, ground infrastructure, or external services when internal resources become unavailable.
Expected Outcome
Higher mission resilience
Lower architectural complexity
Reduced hardware duplication
More manageable recovery configurations
Decision Indicators
Early indicators include:
Every resilience requirement creates another dedicated backup system.
Recovery modes become too numerous to verify effectively.
Backup architecture approaches the complexity of primary systems.
Existing spacecraft resources are not considered for degraded operations.
Resilience improvements substantially increase integration effort.