Redundancy vs. Resource Efficiency

Design active-active and shared protection pools to satisfy availability obligations without carrying permanently idle capacity as your only resilience strategy.

CyberTRIZ analysis · Telecommunications contradiction NC025 · one of 8,235 worked contradictions published by CyberTRIZ.AI

Regulations

EU_NIS2 ISO_22313 SEC_REG_SCI IEC_62443 ISO_22317

Business Context

Telecommunications networks require redundancy to maintain service when equipment, links, sites, power systems, software functions, or entire facilities fail. Conventional resilience architectures frequently dedicate duplicate resources to standby roles, improving availability but reducing utilization because substantial capacity remains inactive during normal operation. Eliminating those resources improves efficiency but increases exposure to failures and maintenance events.

Telecommunications TRIZ Resolution

Redundancy should be designed as productive shared capacity rather than permanently idle duplication wherever the architecture permits. Active-active configurations, shared protection pools, dynamic rerouting, distributed workloads, and elastic capacity can allow resources to carry useful traffic during normal conditions while remaining available for recovery. Different services can also share resilience resources when their simultaneous failure requirements are sufficiently independent.

Applicable TRIZ Principles

Principle 5 – Merging allows resilience resources to protect multiple systems or services instead of maintaining separate standby capacity.

Principle 6 – Universality enables infrastructure to perform productive functions during normal operation and protection functions during failures.

Principle 15 – Dynamics reallocates capacity rapidly when faults or maintenance events occur.

Expected Outcome

Maintained or improved network resilience

Higher utilization of redundant assets

Reduced dedicated standby capacity

Better capital efficiency

Decision Indicators

Early indicators include:

Large amounts of protection capacity remain permanently idle.

Each service maintains independent backup resources.

Redundancy investment grows faster than active network capacity.

Asset-utilization initiatives repeatedly threaten resilience targets.

Failover resources cannot support productive workloads during normal operation.

TRIZ principles applied

P5 MergingP6 UniversalityP15 Dynamics

Controls that address this (22)

EU_NIS2-CTRL-001 - Daily safeguarding reconciliationoperational · critical priority · Daily reconciliation between safeguarded customer balances, core ledger balances and safeguarded bank accounts. Variances above EUR 100 must EU_NIS2-CTRL-002 - Critical ICT incident reportingoperational · critical priority · All major ICT incidents impacting payment services, customer data or availability must be classified within 4 hours and reported under DORA EU_NIS2-CTRL-003 - GDPR breach notification workflowoperational · critical priority · Personal data breaches must be assessed within 12 hours and reported to the Belgian DPA within 72 hours where risk to data subjects exists.