Back to Blog
Corporate Solutions

Energy Monitoring Software: Meters, kWh and Intensity

How does energy monitoring software work? Meter readings, counter rollovers, kWh per line and per product, peak periods, abnormal consumption alerts and links to downtime and maintenance records.

Enerji YönetimiÜretim TakibiRaporlamaKurumsal Yazılım

Energy monitoring software reads the electricity, gas, water and compressed air meters in a plant or building at regular intervals and shows consumption by line, machine, shift and product. The short answer: your utility bill tells you the monthly total, while the software tells you where, when and for which production that energy was used. The value is not in the raw meter reading but in putting the difference between two readings next to production data.

Why can energy use not be managed from the bill?

The electricity bill gives one number for the whole site and arrives after the month is over. By then you cannot see which compressor ran idle all night, which line drew more energy for the same product than last month, or which machines were running during the peak tariff. Some companies read sub meters by hand and type them into a spreadsheet, but reading times drift, a replaced or reset meter produces negative consumption, and nobody trusts that row any more. The data exists, yet it is not good enough to make decisions with.

A meter reading is not consumption, it is a running total. Consumption is the difference between two readings, and calculating that difference correctly is the first job of the software.

Features energy monitoring software should have

  • Meter tree: main meter, building, line and machine sub meters defined as a hierarchy, with the sum of sub meters compared against the main meter.
  • Reading sources: automatic reading over Modbus or a similar protocol, pulse output counting, and manual entry from a mobile screen for meters without automation.
  • Meter replacement and resets: the last value of the old meter and the first value of the new one are recorded, so no negative consumption appears.
  • Time periods: consumption split by tariff periods such as day, peak and night.
  • Energy per product: consumption divided by good units produced in the same period, giving kWh per unit or per tonne.
  • Alerts: consumption continuing while a line is stopped, use clearly above the normal level, or a meter that stops sending data.
  • Reports: comparisons by line, shift, product and period, with export and a management summary.

How are consumption and kWh per unit calculated?

Every meter holds a cumulative value. The software sorts readings by time and records the difference between consecutive readings as the consumption for that interval. If the difference is negative there are two possibilities: the counter hit its maximum and wrapped around, or the meter was replaced or reset. The first case can be calculated; the second is not corrected automatically and goes to review. Energy per unit is the consumption in a time window divided by the good units produced in the same window. The example below shows the logic:

type Reading = { meterId: string; at: string; value: number }; // cumulative kWh
type Meter = { id: string; rolloverAt: number }; // e.g. 999999 for a 6 digit counter

// Consumption is the difference between two cumulative readings, never the reading itself.
function consumption(meter: Meter, readings: Reading[]): { from: string; to: string; kwh: number; flag?: string }[] {
  const sorted = [...readings].sort((a, b) => a.at.localeCompare(b.at));
  const result: { from: string; to: string; kwh: number; flag?: string }[] = [];
  for (let i = 1; i < sorted.length; i++) {
    const prev = sorted[i - 1];
    const curr = sorted[i];
    let kwh = curr.value - prev.value;
    let flag: string | undefined;
    if (kwh < 0) {
      // Either the counter rolled over or the meter was replaced or reset.
      const rolled = meter.rolloverAt - prev.value + curr.value;
      if (rolled >= 0 && rolled < meter.rolloverAt * 0.1) {
        kwh = rolled;
        flag = 'rollover';
      } else {
        kwh = 0;
        flag = 'needs-review';
      }
    }
    result.push({ from: prev.at, to: curr.at, kwh: Math.round(kwh * 1000) / 1000, flag });
  }
  return result;
}

// Energy intensity: kWh per good unit produced in the same period.
function intensity(kwh: number, goodUnits: number): number | null {
  return goodUnits > 0 ? kwh / goodUnits : null;
}

Two rules matter here. First, a suspicious difference is never silently set to zero and forgotten; it stays visible in reports with a review flag. Second, energy per unit uses good units only, so the energy spent on scrap is carried by the good product, because that is the real cost. The reading interval should be fixed too: hourly or fifteen minute data is rolled up into daily and monthly totals with the same rule.

How does energy tracking connect to downtime and maintenance?

Energy data on its own answers "how much"; answering "why" requires combining it with production and maintenance records. If consumption continues while a line is stopped, something is running idle or leaking, and to see that you need downtime records on the same timeline, which we covered in our downtime tracking and OEE article. When a motor or compressor slowly draws more energy under the same load, that is often an early sign of a maintenance need and can become a work order in your maintenance and breakdown tracking software. For management, energy, output and cost are combined on one screen, as described in our business intelligence and reporting dashboard article. For companies running an energy management system such as ISO 50001, this measurement layer is also the basis for tracking targets and improvements.

Off the shelf or custom software?

Meter manufacturers and some automation vendors ship their own monitoring tools; if you use a single brand of meter and only want consumption charts, they may be enough. If you have meters from different brands, manually read points, a need for energy per product, or integration with production, maintenance and accounting systems, custom development means fewer compromises. Before starting, list your meters, which of them can be read automatically and which questions you want answered; it is the cheapest way to pin down the scope.

Conclusion

Good energy monitoring software reads meters regularly, calculates consumption correctly from the difference of cumulative values, handles counter resets, shows energy per product and explains abnormal use together with downtime and maintenance records. To build this on top of your existing systems, see our corporate solutions page or describe your needs and request a quote.

Let's Build Your Project

Get a free consultation for your website, mobile app, or corporate software project.

Get a Free QuoteExplore our Corporate Solutions service