Mission Capability vs Platform Simplicity
Use software-defined, modular architectures governed by ISO 12207 lifecycle processes to expand mission capability without multiplying hardware interfaces and verification burdens.
CyberTRIZ analysis · Space contradiction SDP013 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Adding instruments, operating modes, processing functions, communications options, propulsion capability, and autonomous behaviors can increase the range of missions a spacecraft can perform. However, every additional capability can introduce hardware, software, interfaces, verification activities, operational procedures, and failure modes. The spacecraft becomes more capable but increasingly difficult to develop, validate, and operate.
Space TRIZ Resolution
Mission capability should be expanded through configurable and reusable functions rather than independent systems for every requirement. Common computing, software-defined functions, shared sensors, standardized interfaces, and modular payload architectures can support multiple mission needs without proportional growth in platform complexity.
Applicable TRIZ Principles
Principle 5 – Merging combines related functions within common spacecraft resources.
Principle 6 – Universality enables existing systems to support multiple mission functions.
Principle 15 – Dynamics allows spacecraft behavior to change according to mission phase or operational need.
Expected Outcome
Broader mission capability
Lower architectural complexity
Reduced hardware duplication
Easier spacecraft integration and operations
Decision Indicators
Early indicators include:
Every new capability introduces dedicated hardware.
Interface counts increase rapidly as mission functions expand.
Verification effort grows faster than spacecraft capability.
Operational procedures become increasingly specialized.
Multiple systems perform closely related functions independently.