1

Architecture Telemetry and Smart Storage

znetsixe edited this page 2026-03-23 11:30:57 +01:00

Table of Contents

• EVOLV Telemetry and Smart Storage
• Multi-Level Telemetry Flow
• Design Intent
• Benefits
• Risks To Manage
• Direction

EVOLV Telemetry and Smart Storage

EVOLV uses InfluxDB on multiple levels:

• local for resilience and digital-twin use
• site for plant diagnostics and continuity
• central for fleet analytics and advisory intelligence

Multi-Level Telemetry Flow

flowchart LR
    RAW["Raw Signal"] --> EVAL["Edge Signal Evaluation"]
    EVAL --> KEEP["Keep critical change points"]
    EVAL --> REDUCE["Reduce reconstructable flat spans"]
    KEEP --> L0["Local InfluxDB"]
    REDUCE --> L0
    L0 --> L1["Site InfluxDB"]
    L1 --> L2["Central InfluxDB"]
    L2 --> DASH["Dashboards / Analytics / Intelligence"]

Design Intent

The target is not only naive event storage with a fixed deadband such as 1%.

The intended model is signal-aware:

• evaluate slope and change behavior
• keep points that carry meaningful process information
• avoid storing large runs of low-information points
• preserve enough context that downstream reconstruction remains auditable

Benefits

• lower storage volume without throwing away useful process behavior
• better local resilience because important state transitions are preserved
• stronger support for digital-twin and analytics use cases
• more useful site and fleet history

Risks To Manage

• reconstruction rules must be explicit
• acceptable reconstruction error must be defined per signal class
• compliance-critical signals may need stricter raw retention
• the authoritative layer for each time horizon must be clear

Direction

Smart storage should be treated as a first-class EVOLV architecture feature, not as an afterthought on top of InfluxDB.