Definition
EMS (Energy Management System) enables energy consumption monitoring, sub-metering, energy efficiency analysis, and energy-saving optimization. Meter collection devices collect electricity and water meter data through protocols such as Modbus and DL/T 645, and report it to the EMS platform. Suitable for buildings, factories, campuses, and other AMR and energy cost management scenarios.
System Functions
The core functions of EMS include: real-time monitoring of energy consumption in each circuit (electricity, water, gas, heat); sub-metering (lighting, air conditioning, power, equipment, etc.); historical data storage and trend analysis; energy consumption reports, year-on-year and month-on-month comparisons, cost accounting; energy efficiency benchmarks, abnormal alerts, target management; linkage with BMS building systems and DMP equipment management; demand-side management, peak-valley optimization, load forecasting. Data collection can come from AMR metering systems, DCS, SCADA, intelligent meters, etc.
Data Acquisition
Meter readers and concentrators collect data from electricity meters, water meters, gas meters, and heat meters via Modbus, DL/T 645, M-Bus and other protocols; industrial gateways collect energy data from DCS and PLC; intelligent distribution cabinets and power monitoring devices connect via Modbus and OPC UA. Data is uploaded to the EMS platform via 4G, NB-IoT, fiber, etc., supporting edge computing, local storage, and resumable transmission during network outages.
Application Value
EMS helps enterprises understand detailed energy consumption, identify high-energy-consuming areas, and support energy-saving renovations and efficiency optimization. Sub-metering can detect leaks and abnormal electricity usage. Linking with BMS allows for on-demand control of air conditioning and lighting. It is suitable for commercial buildings, industrial parks, data centers, public buildings, manufacturing industries, and more.
Sub-meter circuits and the metering boundary
The smallest object in energy management is a metering point, not the name of a building. A metering point has to state the medium, the circuit, the ratio, the unit, and the extent that point represents. A difference between the incoming total meter and the sub-meters is allowed when it comes from unmetered outlets, losses, and meter error. Only a difference that suddenly grows needs to be chased. If the split follows the organization chart rather than the actual distribution, and one bus feeds both production and air conditioning, no algorithm can separate the two uses. Cumulative meters for water, gas, and heat, like electricity meters, have to use a difference of readings that carry time. Do not subtract the arrival times of two reads.
The condition is that meters are already installed on the circuits. Communication only brings the readings back. A circuit with no meter cannot be replaced by an estimate for long. An estimate has to be marked on its own, and it cannot be added to measured readings and still be called measured. Clocks have to share the billing day boundary, or the daily freeze is off by one interval and the monthly report is a little wrong every day. When the system is linked to building control, the energy system may send a target or read consumption. It should not seize and write the chiller's protection parameters. Keep a gap as a gap. Recalculate that interval only after the catch-up read succeeds.
Ratio, clock, and missing readings
Writing a missing reading as zero does the most damage. If the hour when communication stopped is stored as zero consumption, daily usage falls, and the next difference after recovery turns the jump in the cumulative value into a spike. The right record is that this interval has no reading. Compute the cumulative difference only between two valid freezes, and say that the interval grew. A wrong ratio has two directions. The meter has already applied the transformer ratio and the platform multiplies again, or neither side multiplies. A communication check will not find this. Compare primary current with the meter display.
Tariff periods have to use either the clock inside the meter or the platform clock, and only one of them. If the two sources disagree, peak and off-peak energy for the same day do not match, while the total energy does. After a retrofit the circuit archive is often left unchanged, an old lighting meter now feeds power, and the report still scores it as lighting. Separate a negative value from a reset to zero. Replacing a meter resets the cumulative register. That is not energy flowing backwards. Export and a grid-tied photovoltaic system need their own direction flag. Alarm thresholds should follow that circuit's baseline, not one constant for the whole plant, and the baseline should at least separate production days from shutdown days. A manual edit needs a reason, or the next reconciliation cannot tell which point was changed.
How a cumulative difference is computed
Usage is the difference of two valid cumulative values, not a missing point filled with zero. Leave an interval blank while communication is down. After recovery, subtract the two valid freezes on either side and note that the interval grew. Recording the outage as zero, and the jump at recovery as a spike, puts a false valley and a false peak on the same curve. Mark a cumulative reset caused by a meter change on its own. Do not treat it as energy flowing backwards.
Store direction separately. Grid import and export are not the same cumulative as forward consumption. Folding them into one net value makes the split meaningless. A tariff recognizes only one clock. Using both the meter's periods and the platform's periods makes total energy match and peak and off-peak disagree. Update the archive the day a circuit is rebuilt. Retire the old name. Do not change what it means. Separate alarm thresholds for production days and shutdown days. One constant for the whole plant either false-alarms all day or misses the shutdown. Keep the original value of a manual edit, or the next reconciliation cannot tell which point was touched.
Track the difference between the sum of the sub-meters and the total meter by day. If the difference suddenly grows, look first for a new circuit that never entered the split, then for a ratio that was changed, and only then at the meter itself. If the difference is stable and can be explained by unmetered load, do not edit readings to force a balance. If steam or heat is billed on cumulative heat, also check that supply and return temperatures are valid. When temperature is invalid, the heat increment should not enter the daily total. Keep manual estimates in their own column. They do not join the measured total, and the report should say they are estimates. The billing day boundary follows the agreed clock. A catch-up that crosses the boundary is split by freeze time. After a circuit is retired, set the archive state to retired and keep the last valid reading. Deleting the point leaves history hanging.