Infrastructure Capacity vs Deployment Cost
Design infrastructure for incremental, modular capacity expansion with export-controlled technology compartmentalised per increment to limit licensing exposure as deployment scales.
CyberTRIZ analysis · Space contradiction TSI012 · one of 8,235 worked contradictions published by CyberTRIZ.AI
Regulations
Business Context
Orbital communications networks, navigation services, servicing platforms, data relays, depots, and other shared infrastructure become more useful as their capacity increases. Building substantial capacity in advance, however, requires significant launch and deployment investment before demand is certain. Building only minimum initial capacity reduces financial exposure but may create bottlenecks as utilization grows.
Space TRIZ Resolution
Infrastructure should be designed for incremental expansion rather than maximum initial deployment. Modular capacity, standardized interfaces, distributed assets, and scalable software architectures allow resources to be added as demand develops. Initial infrastructure can establish core functionality while preserving defined expansion paths.
Applicable TRIZ Principles
Principle 1 – Segmentation divides infrastructure into independently deployable capacity increments.
Principle 15 – Dynamics expands infrastructure according to actual utilization.
Principle 35 – Parameter Changes adjusts capacity and service configuration as demand evolves.
Expected Outcome
Scalable space infrastructure
Lower initial deployment cost
Reduced underutilized capacity
Better alignment between investment and demand
Decision Indicators
Early indicators include:
Large infrastructure investments depend on uncertain future demand.
Significant deployed capacity remains unused.
Capacity expansion requires redesign of the original architecture.
Initial deployment cost prevents otherwise viable infrastructure projects.
Demand growth cannot be accommodated incrementally.