How to Build Consistent Multi Site Energy Monitoring Reports

A monthly electricity bill can tell you what a site used. It rarely tells you whether that use was reasonable.

Across several facilities, the problem gets bigger. One site may look efficient because it is smaller. Another may look wasteful because it runs extra shifts, has refrigeration, charges vehicles, or carries a larger base load. A low total cost can hide high energy intensity. A high total cost can simply reflect longer operating hours.

Consistent reporting fixes the comparison problem. It gives each site the same rules, the same time periods, the same asset language, and the same treatment of missing data. Only then can managers compare facilities with confidence and assign follow-up work to the right people.

Good multi-site reporting starts with field measurements that can be understood later.

Start with the reporting question

Before choosing meters, dashboards, or charts, decide what the report must answer.

A useful report does not try to show every possible electrical value. It focuses on a small set of measures that match the way the business actually runs. For several facilities, that short list is usually better than a crowded dashboard that no one trusts.

Common measures include:

Measure	What it can reveal	What must be defined
Daily energy use	Changes in total consumption from one day to the next	Reporting cutoff, site boundary, included loads
Out-of-hours load	Equipment running when the site should be quiet	Operating hours, weekends, public holidays
Maximum demand	Peaks that may affect capacity or demand charges	Interval length, demand window, reset rules
Energy per production unit	Efficiency relative to output	Production unit, counting method, time alignment
Energy per square metre	Broad site comparison for similar buildings	Floor area, occupancy, excluded zones

The key is to define each measure once, then use the same definition everywhere.

If “out-of-hours” means 6 pm to 6 am at one site and 8 pm to 5 am at another, the comparison will be weak. If one production site reports energy per tonne and another reports energy per pallet, the result may still be useful locally, but it should not sit in the same comparison chart without context.

A good multi site energy monitoring program starts with these definitions. The data has to serve the question, not the other way around.

Set the same measurement boundary at every site

A measurement boundary explains what is inside the number and what is outside it. Without that boundary, the same chart can compare very different things.

For example, a “whole site” reading might include:

• Main production equipment

• Lighting and general power

• Heating, ventilation and air conditioning

• Refrigeration

• Compressed air

• Electric vehicle charging

• Tenant or landlord loads

• Pumps, workshops, or external yards

  
  

Those loads may not be present at every site. Some may also be metered separately. The report should make this clear rather than pretending each facility is identical.

Decide what is included

For each figure in the report, document the inclusion rule in plain language.

For example:

• Whole-site energy includes all electricity downstream of the main incoming supply.

• Production energy excludes office lighting, amenities, and EV charging.

• Refrigeration energy includes freezer plant and cool room evaporators, but excludes general warehouse lighting.

• Out-of-hours load excludes scheduled cleaning shifts where they are part of normal operation.

  
  

These definitions do not need to be complex. They need to be consistent and easy to check.

Keep landlord and tenant services visible

Shared buildings can make reporting difficult. One facility may pay for a landlord-supplied chiller through rent. Another may have the chiller on its own meter. One site may include external lighting on the main switchboard, while another may not.

If these differences cannot be removed from the data, keep them visible in the comments or report notes. A fair comparison may need categories such as “tenant-controlled energy” and “whole tenancy energy” rather than one broad number for all sites.

Treat special loads as separate where possible

Some loads can distort site comparisons. EV charging, refrigeration, air compressors, process heating, and wastewater treatment can all shift the result.

Separating these loads helps the report show what changed. A site with rising usage may not be running less efficiently. It may simply have added vehicle charging or new equipment. Sub-metering does not need to cover every minor circuit, but it should cover the loads that can change the story.

Build a repeatable data structure

Consistent field data is the base of consistent reporting. If the data structure changes from site to site, the report will need manual interpretation every month.

A reading labelled `Meter 4` may make sense to the installer on the day. Six months later, it tells a remote reviewer almost nothing. A better label connects the reading to the site, switchboard, circuit, asset, and purpose.

For example:

`VIC_BENDIGO_MSBA_COMPRESSOR_01_kWh`

That kind of label is longer, but it is clear. It shows the state, site, board, asset, metering point, and unit. The exact naming style can vary, but the logic should stay the same across all facilities.

Record the details that affect the number

Good reports need more than interval data. They also need the supporting details that explain how the reading was created.

Keep a register for each metering point with:

• Site name and site code

• Physical location of the meter

• Electrical circuit or board served

• Asset or load description

• Meter make and model

• Communications method

• Current transformer ratio

• Voltage reference where relevant

• Units recorded by the meter

• Scaling applied in software

• Commissioning date

• Notes on exclusions or known limitations

  
  

This register prevents many common reporting errors. A current transformer ratio entered incorrectly can make a site look far better or worse than it really is. A unit mismatch between watt-hours and kilowatt-hours can do the same. If scaling happens inside both the meter and the reporting platform, the error can be harder to spot.

Use existing meters where they are suitable

A new reporting project does not always need a full replacement of the field layer. Existing meters may be reusable if they provide the right readings, accuracy, interval data, and communications interface.

Acrel meters can form part of the measurement layer where new or replacement meters are needed. The right choice depends on the circuit, data required, installation conditions, and the communication path back to the reporting system.

ProSense can assess the field requirements, including meters, gateways, communications and the reporting platform. That assessment should also look at whether existing meters can stay in place, and what extra data is needed to make the reports comparable.

Meter configuration, scaling and circuit records help stop reporting errors.

Standardise time and interval rules

Time handling can quietly undermine energy reports across facilities. This is especially true for organisations with sites in different Australian states.

A site in Queensland does not observe daylight saving time. Sites in Victoria, New South Wales, South Australia, Tasmania and the ACT do. Western Australia and the Northern Territory do not. If the reporting system does not handle this correctly, daily totals and operating-hour comparisons can shift.

Set clear rules for:

• Local time versus a single national time reference

• Daylight saving changes

• Reporting cutoff time

• Week start day

• Public holiday treatment

• Interval length

• How late-arriving data is handled

  
  

For most operational reports, local time is easier for site teams to understand. A 6 am start should mean 6 am at that site. For national analytics, a platform may still need to store time in a consistent internal format and display it locally.

The reporting cutoff also matters. If one site reports midnight to midnight and another reports 7 am to 7 am, daily figures will not align with the same operating cycle. A production facility that runs overnight may need a different reporting day from a retail or storage site, but the rule should be stated and applied consistently.

Make data quality part of the report

A report should not hide the condition of the data. Missing intervals, communications outages, flatlined sensors and estimated values should be visible.

If a meter fails for three days, the site should not appear to have achieved a sudden energy reduction. If intervals are estimated, the report should say so. If a gateway loses connection, the report should separate “no data received” from “no energy used”.

Good data quality notes can include:

• Percentage of expected intervals received

• Number of missing intervals

• Longest communications outage

• Number of estimated intervals

• Meter status or last received timestamp

• Any manual corrections applied

  
  

This does not need to clutter the main page. A simple data quality line beside each site can save hours of confusion.

For example, a monthly report might show:

Site	Energy use	Data quality	Comment
Site A	82,400 kWh	100% complete	Normal operation
Site B	59,100 kWh	94% complete	Communications outage for two nights
Site C	41,800 kWh	100% complete	Lower production volume
Site D	18,200 kWh	61% complete	Meter fault, result not comparable

That last line matters. Without it, Site D might look like the best performer. In reality, it should be excluded from comparison until the metering issue is fixed.

Compare sites using operating measures

Total energy is useful, but it is rarely enough. Site comparisons become stronger when energy is paired with operating measures.

Useful operating measures can include:

• Production volume

• Operating hours

• Occupancy

• Floor area

• Refrigerated volume

• Number of shifts

• Weather exposure

• Major asset run hours

  
  

Choose measures that explain the main reason the site uses energy. A cold storage facility might need energy per pallet position or per cubic metre of refrigerated space. A manufacturing site might use energy per tonne of product. A distribution facility might compare energy per order, per pallet moved, or per operating hour.

Keep the measure stable. If production teams change how they count output, the energy intensity trend will change even if the plant has not. If occupancy numbers are estimates, say so. If output is recorded daily but energy is reported monthly, check that the date ranges match.

The goal is not to make every site look the same. The goal is to explain why they differ.

Give every exception an owner

A report should lead to action. If it only shows charts, it will soon become background noise.

Each monthly report should identify a short list of exceptions that someone can investigate. These should be specific enough to assign.

Examples include:

• Overnight demand stayed above the normal range for ten consecutive nights.

• Weekend energy use rose after a maintenance shutdown.

• Compressor energy increased while production stayed flat.

• One site had a higher maximum demand than larger facilities.

• A meter stopped reporting after switchboard work.

• Energy per production unit rose after a product mix change.

  
  

Every exception needs an owner, a due date, and a clear next step. The owner may be a site manager, maintenance lead, controls technician, production supervisor, facilities contractor, or metering service provider.

For example, a production building with sustained overnight demand may need an after-hours walk-through, a review of control schedules, or a check for equipment left in manual mode. A site with missing data may need communications testing, gateway replacement, or a meter configuration review.

This is where consistent reporting earns its value. The same rules that make sites comparable also make exceptions easier to trust.

Design the monthly report for decisions

A strong multi-site energy report should be short enough to read and detailed enough to support follow-up. The front page should answer the main questions quickly, while appendices or linked views can hold meter-level detail.

A practical monthly structure might include:

1. Executive summary

   
   

Key changes, exceptions, and follow-up items.

1. Site comparison

   
   

Whole-site energy, operating measure, and energy intensity.

1. Out-of-hours review

   
   

Base load trends, weekend use, and abnormal overnight demand.

1. Major load breakdown

   
   

Refrigeration, compressed air, production, HVAC, EV charging, or other key systems.

1. Demand review

   
   

Peak demand, timing, and likely cause.

1. Data quality

   
   

Missing intervals, estimated values, communications faults, and excluded sites.

1. Actions register

   
   

Owner, status, due date, and notes from the previous month.

This format keeps the report focused. It also creates a feedback loop. If the same exception appears for three months with no owner, the reporting process is not finished.

Check the report before using it to rank sites

Multi-site reports are often used to rank facilities. Ranking can be useful, but only after the data has passed basic checks.

Before publishing comparisons, check:

• Are all sites using the same reporting period?

• Are the measurement boundaries documented?

• Are special loads included or separated consistently?

• Are production or occupancy figures aligned to the energy period?

• Are missing intervals visible?

• Are meter ratios and software scaling confirmed?

• Are daylight saving and local time handled correctly?

• Are closed, partly occupied, or recently changed sites flagged?

• Are major equipment changes noted?

• Are estimates separated from measured values?

  
  

A ranking should never punish a site for a measurement issue or reward a site for a failed meter. If two facilities are not directly comparable, group them differently or add context. A refrigerated warehouse, a light assembly plant, and an office-style support facility should not be judged by the same single number.

Build the system so it can grow

The first version does not need to cover every circuit. It should cover the major loads, use clear definitions, and leave room to expand.

As more sites join the reporting program, the naming rules, meter register, time settings, and data quality checks become more valuable. They stop each new facility from becoming a custom project.

A strong setup includes:

• A standard site and asset naming convention

• A documented measurement boundary for each report metric

• A meter register with configuration details

• A consistent interval and time-zone approach

• A clear rule for estimated and missing values

• A short list of business-relevant measures

• An agreed process for assigning exceptions

  
  

With those pieces in place, the dashboard can be simple. The value comes from trust in the numbers.

Consistent multi-site reporting is built through careful definitions, clean meter data, and clear ownership of exceptions. Once those foundations are in place, energy reports stop being a set of disconnected charts and become a practical tool for comparing facilities, finding waste, and following up with confidence.