Fault Tolerance vs Power Consumption
Assign active versus standby redundancy modes according to time-criticality of each function so power budgets remain viable without compromising required fault-tolerance integrity.
CyberTRIZ analysis · Space contradiction RMA003 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Fault-tolerant architectures may keep redundant computers, sensors, communications equipment, or other systems powered simultaneously to provide immediate backup capability. This reduces recovery time but increases continuous electrical demand and thermal generation. For power-constrained spacecraft, maintaining every backup system continuously active can significantly reduce resources available for productive mission functions.
Space TRIZ Resolution
Backup capability does not always need to remain fully powered. Systems can use dormant, low-power, or periodically verified redundant elements that activate when faults are detected. Critical functions requiring uninterrupted availability can retain active redundancy, while less time-sensitive functions use standby configurations.
Applicable TRIZ Principles
Principle 10 – Prior Action prepares backup systems and recovery states before failures occur.
Principle 19 – Periodic Action activates or tests redundant equipment only when necessary.
Principle 23 – Feedback uses health information to activate backup capability when abnormal conditions are detected.
Expected Outcome
Maintained fault tolerance
Lower continuous power consumption
Reduced thermal load
Greater energy availability for mission functions
Decision Indicators
Early indicators include:
Backup systems consume significant power during nominal operations.
Redundant equipment remains continuously active without immediate-response requirements.
Fault-tolerance architecture determines spacecraft power-system size.
Thermal loads increase substantially because of active redundancy.
Standby or low-power redundancy receives limited consideration.