From overview to anomaly tracing

Bring equipment, energy, and event data into one shared state that teams can monitor and trace.

Explore the system
Illustrative data

Site overview

Updated 18:14
Load 466.3 kW
Generation 43.9 kW
Grid import 448.2 kW
Storage SOC 71.7 %
Energy trend · last hour
Load and grid-import trend Changing the period moves the load and grid-import lines to a new illustrative data state. 520 440 360 280 17:15 18:15
Pending
Main panel contact temperatureHuman confirmation required
Demand nearing thresholdAnalysis in progress

Energy flow

Updated 18:14
Site energy flow Select a source to trace renewable energy, grid power, or storage discharge to the site load. Renewables 43.9 kW Grid 448.2 kW Peak-shaving storage −25.4 kW Bus 466.3 kW Site load 466.3 kW
Renewables → load

Event tracing

Updated 18:14

Inverter telemetry updates restored

Event equipment illustration A simplified 2.5D view of a switchboard, site meter, or inverter based on the selected event. Event trace path A measurement moves from equipment through a rule to an event and its response state. EquipmentRuleEventResponse INV-02 Update interval 42 sec Cleared
EquipmentPV Inverter 02
Event42 sec delay
ResponseCleared

From equipment data to an operational view

Open each card to see how the system connects data, interprets conditions, and turns the result into a traceable interface.

Equipment and data connection Start by reviewing existing equipment, data points, and communication conditions for reliable access.

The connection method depends on the site's equipment and existing systems. Final specifications require a point list, update rates, and data-quality checks.

  1. Equipment points
  2. Modbus · MQTT · API
  3. Data-quality check
Rules and site state Normalize measurements from different sources, then apply thresholds and update conditions to form events.

Rules, event levels, and response states are configured for the site while preserving the original measurement and event context for tracing.

  1. Live measurement
  2. Rule evaluation
  3. Event state
Management view and control boundary Shape overview, alert, and reporting views around operational needs; control requires separate authorization and field validation.

This page demonstrates interface and information architecture. Projects involving equipment control still require permission design, fail-safe behavior, and on-site testing.

  1. Management overview
  2. Anomaly tracing
  3. Scope confirmation

Turn existing equipment data into a usable management view

The final interface, data points, and functions depend on equipment, data quality, management needs, and agreed project scope.

Discuss system requirements