Edge Computing vs Centralized Control

Architect hybrid edge-central systems so centralised governance retains full visibility and patch authority over all distributed edge nodes.

CyberTRIZ analysis · SmartCity contradiction C13-SC009 · one of 8,235 worked contradictions published by CyberTRIZ.AI

Regulations

EU_NIS2 US_IOT_CYBERSECURITY_IMPROVEMENT_ACT ISO_27001 COBIT2019

Business Context

Edge computing allows IoT devices to process information close to where it is generated, reducing communication delays and enabling faster operational responses. However, distributing computing capability across thousands of devices may reduce centralized visibility, complicate software management, and increase governance challenges. Municipalities must benefit from decentralized intelligence while maintaining centralized operational oversight.

Smart CityTRIZ Resolution

Rather than choosing between centralized and distributed computing, municipalities should adopt hybrid architectures where edge devices perform real-time processing while centralized platforms provide governance, analytics, orchestration, and long-term data management.

Applicable TRIZ Principles

Principle 5 – Merging combines edge and centralized computing into a unified architecture.

Principle 15 – Dynamics allocates processing according to operational requirements.

Principle 24 – Intermediary coordinates distributed devices through centralized management platforms.

Expected Outcome

Faster operational response

Better system governance

Reduced communication latency

Improved scalability

Decision Indicators

Early indicators that computing architecture requires optimization include:

Edge devices become difficult to manage.

Central platforms receive incomplete operational data.

Communication delays increase.

Software updates become inconsistent.

Computing resources remain underutilized.

Monitoring these indicators supports balanced digital architecture.

TRIZ principles applied

P5 MergingP15 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.