Redundancy vs. Efficiency

Configure redundant resources in load-sharing roles during normal operation so they contribute productive work while retaining full failover capacity on demand.

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

Regulations

EU_NIS2 ISO_22313 IEC_62443 ISO_20000

Business Context

Redundancy protects telecommunications services against component and path failures, but conventional redundant architectures often maintain duplicate resources that contribute little during normal operation. Eliminating these resources improves utilization and reduces cost but leaves the network more exposed when equipment fails or maintenance removes active capacity.

Telecommunications TRIZ Resolution

Redundant resources should contribute to normal network operation while retaining sufficient capacity to assume additional workloads during failures. Load-sharing architectures, common protection pools, dynamic routing, and distributed processing allow redundancy to become productive. Different systems can also share protection resources when their failure conditions are sufficiently independent.

Applicable TRIZ Principles

Principle 5 – Merging combines protection requirements across compatible services.

Principle 6 – Universality gives redundant resources useful normal-state and recovery-state functions.

Principle 15 – Dynamics changes resource assignments when failures occur.

Expected Outcome

Maintained redundancy

Higher normal-state resource utilization

Lower infrastructure cost

Improved resilience efficiency

Decision Indicators

Early indicators include:

Backup assets remain unused except during testing or failures.

Separate systems maintain independent protection capacity.

Efficiency programs repeatedly propose removing essential redundancy.

Redundant infrastructure produces high lifecycle cost.

Resources cannot change roles between normal and failure conditions.

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.