ZenovaConnect

Three deployments. Your data, your control.

From fully cloud-hosted to entirely inside your domain — pick what fits your team's scale and data sensitivity.

System map: where ZenovaConnect sits in the energy stack

Not another monitoring dashboard. The device-data integration layer between vendor data sources and your higher-level energy applications.

Upstream data sources

  • Vendor clouds FusionSolar / iSolarCloud / SEMS / SolisCloud
  • Field devices Inverter / PCS / Meter / Weather station
  • SmartPVLog / 3rd-party collectors RS-485 / Modbus / IEC-104 / TCP

ZenovaConnect integration layer

  • Vendor adapters Auth / API pull / Rate limit / Retry
  • Edge ingestion MQTT / TCP / IEC-104 mapping
  • Normalization Entities / metrics / units / alarms
  • Delivery Webhook / Kafka / MQTT / Private API

Your applications

  • Monitor dashboards
  • VPP / EMS / Dispatch
  • Asset operations platform / SaaS platform
  • BI / Data lake / AI analytics
  • Enterprise platform / SaaS / Custom systems

ZenovaConnect does not replace your monitor, EMS, VPP, or enterprise system. It brings device data in, normalizes it, and pushes it downstream reliably.

Core architecture: from multi-vendor ingestion to one schema

What you see is one schema and stable channels. Internally, our assets are vendor adapters, field mappings, the protocol registry, data quality rules, and delivery reliability.

Control plane

  • Tenant & project management
  • Credential vault (encryption / rotation / least privilege)
  • Protocol & vendor registry
  • Point-list & field mapping

Data plane

  • Pull scheduler (interval / rate-limit)
  • Connector runtime (auth / retry / circuit-breaker)
  • Raw response cache (audit / replay)
  • Schema normalizer (entities / metrics / alarms / time-series)
  • Data quality layer (missing / stale / unit anomaly)
  • Message routing (per-tenant isolation / topic)

Downstream delivery

  • HTTP Webhook (signed / retried / idempotent)
  • Apache Kafka (topic / partition / consumer group)
  • MQTT 5.0 (topic / ACL / QoS)
  • Private API (on-premise calls)

Ops & governance

  • Observability (logs / metrics / trace)
  • Admin console (protocol status / failure replay)
  • SLA & audit (error rate / latency / data freshness)
VENDOR CLOUDSZenovaConnect CloudYOUR CHANNEL华为FusionSolar阳光iSolarCloud固德威SEMS锦浪SolisCloudvendor API · pullSMA · 古瑞瓦特+ 12 more in pipelineZenovaConnectCLOUD AGGREGATORpull · normalize · pushWebhook / Kafka / MQTTHTTP WebhookRESTApache KafkaSTREAMMQTT 5.0PUB/SUBzero infrastructure on your side · we pull · you receive

You maintain no infrastructure. Device data enters our cloud via vendor APIs, gets normalized, and is pushed to your endpoint in your format. Ideal for energy-SaaS teams that need fast onboarding and elastic scale.