Distributed Computing vs Network Dependence

Ensure critical processing functions remain locally executable and document network-failure fallback modes to meet NIS2 continuity and incident-response obligations.

CyberTRIZ analysis · Space contradiction TSI027 · one of 8,235 worked contradictions published by CyberTRIZ.AI

Regulations

EU_NIS2 ISO_27001 EU_AI_ACT IEC_61508

Business Context

Distributed computing across spacecraft, ground infrastructure, relay systems, and cloud resources can provide greater aggregate processing capability without placing all hardware onboard one vehicle. However, distributing computation creates dependence on communications availability, latency, synchronization, and network integrity. A centralized onboard architecture reduces network dependence but requires greater local resources.

Space TRIZ Resolution

Critical functions should remain executable locally while distributed resources provide additional performance when connectivity is available. Workloads can migrate according to network condition, urgency, and resource availability. Intermediate results and essential data can also be cached locally to maintain continuity during temporary disconnection.

Applicable TRIZ Principles

Principle 1 – Segmentation separates connectivity-dependent workloads from critical local functions.

Principle 15 – Dynamics relocates processing according to network and resource conditions.

Principle 24 – Intermediary uses external computing resources when they provide operational advantage.

Expected Outcome

Greater aggregate computing capability

Reduced onboard hardware demand

Maintained operation during network interruptions

More flexible workload allocation

Decision Indicators

Early indicators include:

Loss of connectivity disables critical processing functions.

Spacecraft carry excessive computing resources solely for occasional workloads.

Processing location remains fixed despite changing network conditions.

Temporary communication outages cause unnecessary mission interruption.

Distributed resources cannot be used because workload migration is unsupported.

TRIZ principles applied

P1 SegmentationP15 DynamicsP24 Intermediary

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.