Resilience vs. Resource Utilization

Implement elastic, shared capacity pools with dynamic reallocation so resilience obligations are met without permanently reserving idle infrastructure.

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

Regulations

EU_NIS2 ISO_22313 IEC_62443 ISO_22317 NIST_RMF

Business Context

Resilient networks require sufficient spare resources to absorb equipment failures, traffic rerouting, maintenance, and exceptional demand. Maintaining this reserve improves continuity but reduces average utilization. Operating infrastructure near maximum utilization improves apparent efficiency but leaves little capacity to absorb abnormal conditions.

Telecommunications TRIZ Resolution

Resilience capacity should be shared, elastic, and condition-dependent wherever possible. Resources can support normal traffic while preserving predefined mechanisms for reallocating workloads during failures. Capacity pools, dynamic routing, scalable computing, traffic prioritization, and temporary service degradation can protect critical functions without requiring every resource to maintain permanent unused headroom.

Applicable TRIZ Principles

Principle 6 – Universality allows capacity to serve normal and resilience functions.

Principle 15 – Dynamics changes resource allocation according to network state.

Principle 16 – Partial or Excessive Action preserves essential service during exceptional conditions without requiring every service to retain full capacity.

Expected Outcome

Improved network resilience

Higher average resource utilization

Reduced dedicated reserve capacity

Better use of infrastructure during normal operation

Decision Indicators

Early indicators include:

Large resilience margins remain unused during normal conditions.

High utilization targets leave insufficient failure capacity.

Individual services maintain separate recovery reserves.

Resource-efficiency initiatives reduce restoration options.

Capacity cannot be redistributed effectively after failures.

TRIZ principles applied

P6 UniversalityP15 DynamicsP16 Partial or excessive actions

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.