Core Concepts
Edge-EMS Builder divides energy-site configuration into data, strategies, coordination, and operations. Find the relevant capabilities by purpose below.
Data and groups
Section titled “Data and groups”| Concept | Meaning |
|---|---|
| Raw data | Values and communication status acquired by CommBridge; writable points can receive control commands |
| Aggregated data | Lua-calculated values, or stored constants and runtime variables |
| Time-scheduled data | Values effective within specified date ranges or daily time periods |
| Shared data | Values synchronized from other EMS Builder nodes, identified by device code and dataKey |
| Data groups | Organize points by device, area, or purpose, supporting parent/child relationships and ordering |
Point names, aliases, and units are for display; dataKey is for computation and invocation. See Data model.
Trigger schemes and alarms
Section titled “Trigger schemes and alarms”A trigger scheme consists of triggers, conditions, and actions. Conditions can be time-based, periodic, or based on data changes. Actions can write points, generate alarms, or publish MQTT messages, and can include post-processing.
Alarm records preserve each trigger occurrence. Alarm events combine ongoing abnormalities from the same source and track active, recovered, and manually resolved states. Unknown observations are not treated as recovery.
See Trigger schemes and Alarm lifecycle.
Communication and device coordination
Section titled “Communication and device coordination”MQTT connection configuration determines how to connect to the broker. Publish and subscribe configurations determine what to send and how to handle received messages.
Device information describes available nodes. Sharing configurations specify which local points to share and at what interval. A shared target specifies a receiving device and binds configurations. A device can receive downstream data while sending local aggregation results upstream.
See MQTT and Device coordination.
Templates and dynamic expansion
Section titled “Templates and dynamic expansion”UDE defines configuration for similar devices as aggregation, group, and sharing templates, then generates configuration for each device unit instance. Reconciliation updates existing instances after template changes. Dynamic placeholders adapt names, sources, and hierarchy according to rules.
History and operations
Section titled “History and operations”- Historical queries provide details and statistical trends; Export generates data files in the background.
- Periodic archiving continuously retains history, business data, and optional runtime files on a schedule.
- Storage assessment recommends capacity and retention periods; Runtime configuration distinguishes file values, runtime values, and environment overrides.
- Maintenance freeze supports operations requiring writes to pause, such as restoration; Control logs track the write process and final results.