The ISO 50001 energy data collection plan: what clause 6.6 requires and how much metering you need

What does ISO 50001 require of the energy data collection plan?

Clause 6.6, titled planning for collection of energy data, turns the energy review into something that can be measured month after month. It feeds the energy review, the indicators and the baseline: without a defined flow of data, an EnPI is a one-off calculation.

The clause has four working parts.

• Key characteristics. Identify the features of your operations that determine energy performance, and measure, monitor and analyse them at planned intervals.
• The plan itself. Specify the data needed to monitor those characteristics, and state how and at what frequency they are collected and retained. The plan must fit the organisation's size, complexity, resources and measuring equipment.
• Review. Look at the plan again at defined intervals and update it when something changes, such as a new SEU, a new meter or a revised action plan.
• Data quality. Measuring equipment used for the plan must give data that are accurate and repeatable.

Detail on the energy data collection plan was one of the changes the 2018 edition made to the 2011 text, so a list of meters on its own no longer answers the clause. ISO/TC 301 is also developing ISO 50012, a separate guidance document on the energy data collection plan, currently at draft stage; ISO 50001 itself is unchanged.

The five categories of data the plan must cover

The standard lists what the plan has to include. Read it as a checklist against your SEU list from the energy review guide: every SEU should appear under at least the first three headings.

For each line the plan then answers the same practical questions: which instrument or record provides it, how often it is read or logged, who is responsible, where it is stored and for how long.

Metering: how much measurement is enough?

Proportionality is written into the clause. A single-site office with one electricity supply and a gas boiler can run a sound plan from the fiscal meters, monthly invoices, the building management system and weather data. A processing group with steam, compressed air and refrigeration as SEUs needs finer measurement, at the level where decisions are taken.

Start with what you already have

Before adding hardware, list every existing source: fiscal meters, invoices, supplier interval data, building management and SCADA historians, equipment controllers and production records. The gap is often in retention and analysis, not hardware.

Close the gaps that matter

Add measurement where an SEU has no reliable data, where two SEUs share a meter and cannot be separated, or where an action plan needs verification. Portable loggers used for a defined campaign are often enough to characterise an SEU or verify a project; permanent sub-metering is justified where the SEU is large, variable or central to an indicator. Estimation, for example from run hours and rated power, can be acceptable for smaller uses if the method is written down and applied consistently.

Accuracy and repeatability

The standard requires data that are accurate and repeatable, not for a particular accuracy class. In practice that means knowing which instruments feed the plan, keeping their calibration or verification status current where the manufacturer or your own method requires it, checking sub-meter totals against the fiscal meter, and correcting for known faults.

A worked example: one SEU in the plan

Take an illustrative food plant whose energy review identified the compressed-air system as an SEU. Consumption depends on production volume and on leakage; the operating criterion is the discharge pressure set point; an action plan is replacing one fixed-speed compressor with a variable-speed unit. The plan's entries for that SEU might read as follows.

The retention periods are the plant's own choice, not a figure from the standard. The same pattern repeats for every other SEU and for whole-site consumption by energy type.

From collected data to monitoring, deviations and review

Collecting data is only the first half. Clause 9.1 requires you to monitor, at a minimum, the effectiveness of action plans, the EnPIs, the operation of the SEUs and actual against expected consumption, and to investigate and respond to significant deviations in energy performance.

A workable rhythm is a monthly indicator report that compares each EnPI with its baseline, a written threshold for what counts as a significant deviation, and a short investigation record whenever the threshold is crossed. How the indicators are normalised against relevant variables is covered in the EnPIs, energy baselines and normalisation guide.

The plan also loops back: new data feed the next energy review update, and management review should see whether the data were complete and reliable.

What auditors find wrong with data collection plans

The certification body's auditors trace data from source to decision, so gaps in the plan show up quickly.

• A meter list, not a plan. The document names meters but not frequency, responsibility or retention, so nobody can show the data were actually collected.
• No relevant variables. Consumption is recorded but production, weather or occupancy is not, so indicators cannot be normalised and improvement cannot be separated from changes in activity.
• Operating criteria that are never recorded. Set points exist in a procedure, but no log shows they were checked, leaving clause 8.1 control unproven.
• Action plans with no verification data. A project is reported as a saving with no before-and-after measurement defined in advance.
• Data nobody checks. Sub-meters drift, loggers fail or totals never reconcile with the fiscal meter, and the error surfaces only when an auditor adds up the figures.

How these points are raised as findings and how audit days are sized are explained in the ISO 50001 certification process guide.

ISO 50001 energy data collection plan: questions buyers ask