Energy consumption is in your monitoring system. Energy performance indicator calculations are in Excel. The explanation for why cooling consumption spiked in March is in an email from a maintenance colleague. When audit preparation begins, you have to piece together what happened and how the company responded.
Most energy managers know the situation. The system works somehow, the numbers eventually add up, but everything is compiled manually, and only one person really understands it. Before an audit, the search begins: what actually happened during the year, and did anyone respond?
Jiřina Švambergová has experienced this from both sides. She first implemented ISO 50001 at a manufacturing company, where she used FLOWBOX but still completed half of her analyses in Excel. Today, she is designing a FLOWBOX module that incorporates exactly what she was missing back then.
“When a deviation is reported to the shop floor supervisor, they know what is happening at that moment. Ask them about it a month later, and they can no longer give you an answer. And if you send them a spreadsheet of monthly data, that will not tell them much either.”
Nobody is doing their job badly. The data is simply spread across five different places, each managed by someone else.
Why Act Now?
An amendment to the Czech Energy Management Act, introduced by Act No. 87/2025 Coll., has been in force since January 2026. It removed the employee headcount and turnover criteria, leaving just one: the organization’s average annual energy consumption over the previous three years. This includes heat, fuels, all sites and, within a holding structure, affiliated companies.
Organizations exceeding 23,611 MWh must have an ISO 50001 energy management system implemented and certified by 31 December 2027. Failure to comply can result in a fine of up to CZK 5 million.
Certification follows a three-year cycle with surveillance audits and an internal audit at least once a year. Companies that already hold a certificate therefore focus on maintaining the system rather than implementing it: adding data for the past year, finding out why consumption spiked in May and what was done about it, and demonstrating improvement.
A surveillance audit checks whether the system operated throughout the year, rather than simply whether documentation exists.
Six Steps Required by the Standard
The steps follow a defined sequence, with each building on the previous one. What differs is how much work each step involves in Excel compared with FLOWBOX.
| Step | In Excel and Emails | In FLOWBOX |
|---|---|---|
| Energy data collection | Manually transcribing invoices and meter readings, month after month | Data from connected meters, invoices and manual readings in one overview |
| Identifying SEUs | Adding up and reorganizing operational consumption by technology | Pareto analysis by energy type and process, with a documented methodology |
| Selecting EnPIs | Downloading degree-day data and repeating the analysis for every variable | Correlation analysis with R² within the system, with suggested indicators by sector |
| Baselines and deviations | Monthly spreadsheets, with deviations discovered only during evaluation | A baseline derived from a regression equation, thresholds and monitoring according to data availability |
| Corrective actions | Emails, phone calls and Teams messages, with no central record of how an issue was addressed | When a threshold is exceeded, the system prompts users to record the cause and an action |
| Audit documentation | Compiling information from multiple files shortly before the audit | Time-stamped exports, with supporting records created continuously |
Start with the Data You Already Have
The standard does not require you to digitalize all metering before implementation. It requires you to identify significant energy uses, so you know where it makes sense to start.
However, coverage must be sufficient. If you can account for only half of a plant’s consumption and know nothing about the other half, your selection of significant energy uses will not stand up to scrutiny. The Pareto principle applies: a small number of items account for most consumption, while a long list of smaller items does not need to be monitored individually.
FLOWBOX therefore combines the sources your company already has: live data from connected meters, invoices and manual readings. For machines without dedicated metering, an initial model-based estimate using rated power and operating hours is sufficient. Once sub-meters are connected, the indicators are recalculated using actual data, without having to redefine the SEUs.
Annual consumption by energy type forms the basis of a Pareto analysis. It might show, for example, that furnaces, compressors and washing equipment account for 83% of electricity consumption, while heating and drying account for 81% of natural gas consumption. This provides the justification for SEU selection that an auditor expects: supported by a documented method rather than a desk-based guess.
The same data can be viewed in two ways, and they provide different information. A breakdown by electrical distribution boards and pipe branches shows where energy flows. A breakdown by processes and technologies shows what consumes it. The second perspective reveals where it makes sense to look for savings.
A glass-melting furnace may account for 70% of a plant’s consumption, but its energy use may be directly proportional to production volume, with limited scope for adjustment. The compressor room at the same plant may look much less significant on the chart while offering greater savings potential.
FLOWBOX therefore builds its Pareto analysis around processes rather than consumption points. During setup, it checks that the sum of assigned consumption does not exceed 100% of the relevant energy type. It is a basic check, but this is precisely where spreadsheet errors occur—and where auditors find them.
The same analysis also shows where installing meters first will deliver the most value, instead of adding them across the facility without clear priorities.
Energy Performance Indicators That Mean Something
The number of kilowatt-hours consumed does not, on its own, tell you whether a company is managing energy more effectively. Was it a cold winter, or was energy being wasted? Without normalization, you cannot answer that question, and auditors check this when reviewing EnPIs.
FLOWBOX therefore offers a selection of relevant variables according to the type of operation and calculates correlation analyses: gas consumption against degree days, for example, or electricity consumption against production volume.
The R² value indicates whether a variable is suitable. The threshold is 0.65. Below that, the system marks the variable as unsuitable; above it, as suitable. Outliers can be excluded, but a justification is mandatory, because this is exactly what an auditor will ask about.
The resulting regression equation becomes the energy baseline against which performance is measured throughout the year.
FLOWBOX provides suggested indicators and variables for individual sectors, so energy managers do not have to start from scratch. The final choice remains theirs. The system provides supporting evidence; it cannot replace operational knowledge.
Targets follow from these indicators, and this is where a recurring mistake appears: setting a target as a fixed percentage reduction every year. After three or four years, there may be little room left for further reductions, putting the organization at odds with the continual improvement requirement in Clause 10.2. Alongside a consumption target, it therefore makes sense to set targets that demonstrate improvement in ways other than repeatedly reducing the same figure.
Every Deviation Has a Follow-Up
When a deviation from the baseline exceeds a defined threshold, the system prompts users to record the cause and a corrective action. In advanced mode, the value cannot even be saved without them. Every change retains a timestamp and the identity of its author.
Timing matters. If a deviation is reported during the week it occurs, the shop floor supervisor still knows what happened. A month later, they may no longer be able to explain it. And if records are completed retrospectively before an audit, the opportunity to respond when the issue arose has already passed. All that remains is a deterioration in performance without an explanation.
Response speed depends on the input data. Connected, continuous metering enables daily and weekly views; manually entered monthly values provide a monthly view. FLOWBOX works in both cases, at the corresponding level of detail.
Alongside deviation monitoring, FLOWBOX also calculates consumption forecasts. This shows both what has happened and where the indicator is heading under current operating conditions.
What the Data Commonly Reveals
Once significant energy uses are monitored more frequently than monthly, the same findings tend to appear across different operations.
- Consumption outside operating hours. A plant running one or two shifts does not manufacture at weekends, but energy demand fails to fall as much as expected.
- Idle operation. Equipment remains switched on between shifts, or an empty production hall continues to be cooled.
- Compressed air leaks. These are most visible when production has stopped but the compressor continues to cycle. See where else manufacturing plants typically find savings.
- Simultaneous heating and cooling. Common in office buildings during spring and autumn: instead of turning down the heating, someone opens a window.
- Fifteen-minute demand peaks. Exceeding contracted capacity only becomes apparent retrospectively on the monthly bill, unless it is prevented through peak shaving.
- Real-time anomalies. A deviation lasting several hours may disappear within daily or monthly totals.
The last two points show why monitoring frequency matters. Monthly evaluation will miss most of these findings, even if the formal monitoring and measurement requirement is met.
Make Energy Management Less Dependent on One Person
Energy management often depends on one person who understands the spreadsheet structure, the origin of the data and the meaning of individual calculations. This makes providing cover difficult. The standard explicitly addresses this in Clauses 7.3 and 7.4, which require awareness and communication across the organization.
FLOWBOX provides role-based views. The energy manager configures the system and has access to the full picture. The production manager monitors indicators and action plans across processes. Department managers see only their own areas. Senior management receives a summary to support decision-making. For people working directly with machines, a dedicated awareness dashboard shows a single figure, a target and the trend for their production hall.
Shared records also preserve operational knowledge. Results can be traced back to the associated actions and change history, making the information useful to people who were not involved in the original decision.
Audit Evidence Is Created During Everyday Work
Indicator monitoring, action records and change history together form the evidence an auditor requires. FLOWBOX uses them to compile an export containing Pareto charts supporting SEU selection, a meter register, a data collection plan, correlation analyses, EnPIs and deviations, corrective actions, and a management review report in accordance with Clause 9.3.
The auditor receives traceable data with timestamps and clear responsibility, rather than a patchwork of Excel files.
This changes the starting point for an internal audit. Instead of collecting supporting documents, the auditor begins by checking them. They open the selection of significant energy uses and see the figures behind it. They open an indicator and see the supporting correlation analysis, including excluded values and the reasons for excluding them. They open a deviation and see who responded and when.
These three questions form the core of reviewing Clauses 6.3, 6.4 and 9.1. The answers are either recorded in the system or unavailable.
The difference goes beyond saving time before an audit. When a company identifies a problem during the monitoring period, it has time to address it and evaluate the impact of its actions. When data is completed retrospectively, that opportunity has already passed for the period concerned.
Where Software Ends and Organizational Responsibility Begins
This boundary should be made clear from the outset. FLOWBOX replaces manual work, but it is not a consultancy for implementing ISO standards. The certificate itself is issued by an independent accredited certification body. Deploying the software alone does not guarantee certification or a predetermined level of energy savings.
| What FLOWBOX Supports | What Remains the Organization’s Responsibility |
|---|---|
| Energy review, SEUs, baselines and EnPIs (Clause 6) | Energy policy and management commitment (Clause 5) |
| Monitoring, evaluation and audit evidence (Clause 9) | Identifying interested parties and risks (Clauses 4 and 6.1) |
| Visualization and evidence of improvement (Clause 10) | Competence, resources and responses to nonconformities |
| Dashboards supporting awareness and communication (Clauses 7.3 and 7.4) | The content of action plans and the selection of improvement opportunities |
This division of responsibilities is precisely why most companies do not need a consultant. The organizational side of the standard is very similar in process terms to ISO 9001, ISO 14001 or ISO 45001. If you already use these standards, much of the existing structure can simply be extended to include energy data.
FLOWBOX guides you methodically through the analytical part, which is often the most demanding, step by step and using the terminology auditors expect.
What If You Already Have a Certificate?
The questions are different, but they lead to the same place. How many days does preparing for a surveillance audit take, and how much of that time is spent searching for information? Could someone else take over the system if the energy manager left? And for every deviation recorded last year, do you know why it occurred and what was done about it—or will you have to reconstruct the story from emails?
Where the answers are uncomfortable, the issue is not a flaw in implementation. The system is simply spread across tools that were never designed to remember why things happened.
About the Solution
The FLOWBOX ISO 50001 module is part of the FLOWBOX energy platform, which collects data and monitors and controls energy consumption and generation in industrial facilities and buildings. It supports individual plants and multi-site installations, including certification across multiple locations within one organization.
See how GRAMEX achieved ISO 50001 certification with FLOWBOX, or find answers to common questions in our ISO 50001 FAQ.