1
Architecture Platform Overview
znetsixe edited this page 2026-03-23 11:30:57 +01:00

EVOLV Platform Overview

EVOLV is a layered automation platform:

  • edge for plant-side execution
  • site for local aggregation and operational resilience
  • central for APIs, analytics, advisory intelligence, and governance

Topology

flowchart LR
    subgraph OT["OT / Field"]
        PLC["PLC / IO"]
        DEV["Sensors / Machines"]
    end

    subgraph EDGE["Edge Layer"]
        ENR["Edge Node-RED"]
        EDB["Local InfluxDB"]
        EUI["Local Monitoring / Local Dashboards"]
        EBR["Optional Local Broker"]
    end

    subgraph SITE["Site Layer"]
        SNR["Site Node-RED / CoreSync"]
        SDB["Site InfluxDB"]
        SUI["Site Dashboards / SCADA Support"]
        SBR["Site Broker"]
    end

    subgraph CENTRAL["Central Layer"]
        API["API / Integration Gateway"]
        INTEL["Overview Intelligence / Advisory Logic"]
        CDB["Central InfluxDB"]
        CGR["Central Grafana"]
        CFG["Tagcodering"]
        GIT["Gitea + CI/CD"]
        IAM["IAM"]
    end

    DEV --> PLC
    PLC --> ENR
    ENR --> EDB
    ENR --> EUI
    ENR --> EBR
    ENR <--> SNR
    EDB <--> SDB
    SNR --> SDB
    SNR --> SUI
    SNR --> SBR
    SNR <--> API
    API --> INTEL
    API <--> CFG
    SDB <--> CDB
    CDB --> CGR
    IAM --> API
    GIT --> ENR
    GIT --> SNR

Key Decisions

  • Local InfluxDB is required for operational resilience.
  • Central is the advisory and API-entry layer, not the direct field caller.
  • tagcodering is the intended database-backed configuration authority.
  • EVOLV should be designed as a platform, not only as a collection of Node-RED nodes.

Why This Structure

  • Edge remains useful and safe during central outages.
  • Site absorbs plant-specific complexity and protects field systems.
  • Central provides fleet-level visibility, governance, and integration.