High Service Availability vs Planned Maintenance
Rotate maintenance across redundant constellation elements under NIS2 continuity obligations to preserve service availability while eliminating deferred-maintenance risk.
CyberTRIZ analysis · Space contradiction LMO026 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Space-based services may require continuous or near-continuous availability, particularly for communications, navigation, monitoring, or critical infrastructure applications. Software maintenance, calibration, orbital adjustments, diagnostics, and other planned activities can temporarily reduce service capacity. Avoiding these activities protects immediate availability but can increase long-term operational risk.
Space TRIZ Resolution
Maintenance should be distributed across redundant mission resources so service capacity remains available while individual elements are temporarily removed from normal operation. Constellations can rotate maintenance periods, and software or configuration updates can be staged progressively rather than deployed simultaneously.
Applicable TRIZ Principles
Principle 1 – Segmentation performs maintenance on individual mission elements rather than the complete service architecture.
Principle 19 – Periodic Action schedules maintenance during lower-demand periods.
Principle 20 – Continuity of Useful Action maintains service through unaffected spacecraft or infrastructure.
Expected Outcome
Higher service continuity
Regular maintenance capability
Lower lifecycle operational risk
Reduced maintenance-related disruption
Decision Indicators
Early indicators include:
Necessary maintenance is repeatedly postponed to preserve availability.
Routine updates cause complete service interruptions.
Multiple spacecraft undergo maintenance simultaneously without necessity.
Constellation redundancy is not used to support maintenance.
Equipment degradation accumulates because downtime is considered unacceptable.