Preventive Maintenance vs. Service Continuity

Replace calendar-based maintenance with condition-aware, rolling procedures so NIS2 continuity requirements are met without forcing customer-impacting outages.

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

Regulations

EU_NIS2 ISO_22313 IEC_62443 ISO_20000 ISO_27001

Business Context

Preventive maintenance reduces the probability of equipment degradation and future failures, but maintenance itself can require equipment shutdown, traffic migration, site access, software interruption, or reduced redundancy. Postponing maintenance protects immediate service continuity while increasing the probability of later unplanned failure.

Telecommunications TRIZ Resolution

Maintenance should move from rigid calendar-based interruption toward condition-aware and service-aware execution. Equipment health data can identify which interventions are genuinely required, while traffic migration, modular replacement, online maintenance, rolling procedures, and temporary capacity redistribution can allow work to occur without removing the complete service.

Applicable TRIZ Principles

Principle 1 – Segmentation allows individual components to be maintained without disabling the complete system.

Principle 10 – Prior Action prepares traffic migration, replacement components, and maintenance resources before intervention.

Principle 23 – Feedback uses equipment condition and performance data to determine when maintenance is necessary.

Expected Outcome

Improved equipment reliability

Fewer service interruptions

More targeted maintenance

Reduced unplanned failures

Decision Indicators

Early indicators include:

Maintenance windows repeatedly require customer-impacting outages.

Necessary maintenance is postponed to protect availability KPIs.

Healthy equipment receives the same maintenance frequency as deteriorating assets.

Deferred maintenance contributes to avoidable failures.

Maintenance planning lacks reliable condition information.

TRIZ principles applied

P1 SegmentationP10 Preliminary actionP23 Feedback

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.