A shared data model for equipment from multiple vendors
Align equipment identities, measurement names, units, and status definitions so dashboards, alerts, and reports can use the same data while preserving source fields and conversion rules.
Meters, inverters, and sensors may all send a field called power. Its unit, measurement location, and sign convention can differ across devices. Putting these values on the same chart can suggest they are directly comparable. Equipment integration needs shared field definitions so those comparisons have a clear basis.
Start with a mapping table. Keep each vendor’s source field and document the platform name, unit, and conversion. The same table can guide new connections and later maintenance.
Connect systems through stable equipment identities
A device may have different names in meter software, a gateway, and a maintenance register. Assign a stable platform identity and map the source identifiers to it. Display names can change while historical records continue to reference the same equipment record.
Record the location and scope of each measurement. Adding a main meter to its submeters can count the same energy twice. Input and output measurements also describe different flows. When replacing equipment, preserve the old identity, replacement time, and relationship to the new device.
Align what each field measures
This illustrative mapping table can be adapted to the equipment documentation.
| Item | Definition to record | Use affected |
|---|---|---|
| Measurement target | Equipment, circuit, phase, and location | Filtering and comparisons |
| Value meaning | Instantaneous, interval average, or cumulative | Trends and period totals |
| Unit and scale | Source unit, target unit, and conversion | Charts and report calculations |
| Direction | Import, export, or the vendor’s sign convention | Energy flows and aggregation |
| Time and quality | Time source, update behavior, and validity | Alerts and missing-data handling |
Keep power and energy consumption in separate fields. kW measures power; kWh measures energy over time. The EIA explanation of electricity measurement describes this distinction. Period consumption calculated from cumulative meter readings also needs rules for resets, replacements, and missing intervals.
Separate equipment status from data quality
A device can be running while its platform data is stale. Equipment status describes the device; data quality describes the information currently available. Show the update time and communication condition alongside the last reported operating state.
Vendor status codes can have different levels of detail. Map them to shared display states while preserving the original code and document version. Mark unmapped codes as unidentified so maintenance staff can complete the mapping.
Preserve source values and conversion rules
When converting W to kW, renaming fields, or grouping events, record the source field, rule, and applicable version. Report values can then be traced to their inputs and compared after a rule change.
Manual corrections should include a reason, time, and responsible person. Keep the source record and corrected result, and state which outputs use the correction. This makes changes to historical figures explainable.
Test one equipment group and one management use
Choose devices with different formats and connect them using the same mapping table. Verify one trend chart or period report against device displays and source records. Include valid zero readings, unknown states, and missing data.
For the connection interfaces, see the Modbus, MQTT, and API integration guide. Shared definitions provide the next layer of consistency for alerts and reports.
lvsota’s equipment and data integration service connects equipment from multiple vendors and existing systems. Bring an equipment list, point documentation, and a proposed management view to discuss your integration needs.
Explore Equipment and data integration