High Data Availability vs Storage Capacity

Apply data-minimisation and retention policies by information category to satisfy GDPR obligations while optimising onboard storage use.

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

Regulations

EU_GDPR EU_NIS2 ISO_27001 ISO_12207

Business Context

Maintaining large quantities of onboard data provides operational flexibility when downlink opportunities are limited and allows spacecraft to preserve observations until transmission becomes possible. Increasing storage capacity, however, adds hardware, power demand, radiation exposure, error-management requirements, and data-management complexity.

Space TRIZ Resolution

Data should be retained according to information value rather than uniformly. Onboard prioritization, compression, duplication rules, progressive deletion, and adaptive retention periods can preserve high-value information while reducing storage consumed by redundant or replaceable data.

Applicable TRIZ Principles

Principle 2 – Taking Out removes redundant or low-value stored information.

Principle 15 – Dynamics changes retention policies according to storage availability and mission priority.

Principle 23 – Feedback adjusts data management using current storage and downlink conditions.

Expected Outcome

Greater useful data availability

Lower storage requirements

Reduced data-management burden

Better protection of high-value information

Decision Indicators

Early indicators include:

Storage capacity regularly approaches operational limits.

All data receives similar retention priority.

Large volumes of replaceable data remain onboard.

Storage growth follows payload data generation directly.

Retention policies remain fixed despite changing downlink availability.

TRIZ principles applied

P2 Taking outP15 DynamicsP23 Feedback

Controls that address this (22)

EU_GDPR-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_GDPR-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_GDPR-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.