Demo Pack 03

Multi-inverter monitoring retrofit

A representative integration package for bringing existing inverter, meter, and environmental data into a consistent operational dashboard. It demonstrates point mapping, quality handling, alarm structure, validation, and controlled handover.

Representative integration example - not a completed installation. Addresses, protocols, cybersecurity controls, and acceptance criteria require project and OEM validation.

Download PDF Request similar support

Architecture

A traceable path from field equipment to operator information.

The concept separates field acquisition, edge processing, transport, storage, and visualisation so each interface can be reviewed and tested.

Representative data path

Inverters, meter
and weather sensors RS-485 or Ethernet
field segments Edge gateway
and quality logic Approved secure
data transport Historian, alarms
and dashboard

Topology only. Network zones, credentials, encryption, firewall rules, remote access, and data retention must follow the client's approved cybersecurity architecture.

Inputs required

OEM register maps and supported communications interfaces.
Existing network drawing, device inventory, and firmware versions.
Approved device addresses, baud rates, unit IDs, and polling limits.
Metering direction, CT ratios, engineering units, and sign convention.
Dashboard users, alarm ownership, retention, and reporting needs.

Engineering outputs

Communications architecture and device-address schedule.
Normalised point list with scale, units, and quality rules.
Dashboard wireframe, alarm matrix, and event definitions.
Factory and site acceptance test records.
Configuration backup, issue log, and as-built handover index.

Data model

Every displayed value carries context and quality.

Illustrative point schedule

Point ID Engineering value Required validation

P_AC_TOTALTotal active power (kW)Register, type, scale, sign, aggregation

E_TOTALLifetime energy (kWh)Rollover, persistence, replacement handling

GRID_V_LL_AVGAverage line voltage (V)Phase source, range, sampling, missing phase

DEVICE_STATENormalised operating stateOEM state table and unknown-code response

ALARM_ACTIVEActive alarm summaryOEM code, severity, timestamp, acknowledgement

Fresh

Valid

The latest sample passes type, range, timestamp, and source-quality checks.

Timed out

Stale

The last value may remain visible, but it is clearly marked and excluded from control decisions.

Rejected

Invalid

Unsupported, out-of-range, or malformed data is not silently presented as a valid measurement.

Validation

Test evidence from point mapping through operator acceptance.

Factory test

Verify data types, byte order, scaling, and sign convention.
Simulate normal, stale, invalid, and communications-loss states.
Check alarm priority, delay, acknowledgement, and recovery.
Confirm dashboard units, labels, timestamps, and aggregation.

Site acceptance

Compare displayed values with approved local equipment readings.
Verify time synchronisation and event sequence across devices.
Prove network-loss alarms and the agreed recovery behaviour.
Record unresolved deviations with an owner and closeout evidence.

Handover

Configuration that can be supported after commissioning.

The closeout pack includes the approved point list, architecture, configuration backup, test evidence, open issues, and access ownership.

Discuss a monitoring scope