In the same quarter, a CFO receives three energy management software proposals. Each vendor shows a flawless dashboard full of real-time charts, promises "up to 30% savings," and asks for a six-figure annual license plus hardware. All three demos look good. None explains what concrete decision the software will enable or how the investment is recovered. The CFO, rightly, postpones the decision.
The problem isn't the software: it's the lack of a framework to evaluate it. A well-chosen energy management system (EMS) is one of the best visibility investments a plant can make. A poorly chosen one is an expensive dashboard nobody looks at three months in. This article gives the criteria a CFO —not an engineer— should use to filter the proposals.
The software is not the first step
Before evaluating any tool, a warning is in order: software doesn't fix bad data, it just shows it faster. If the plant doesn't first have a reliable database of consumption and billing —what we call Utility Data Management (UDM)— the most expensive EMS will only produce pretty dashboards on rotten foundations.
The correct order is: first reliable data and a baseline (audit), then the software that exploits them. See the full framework in the pillar Industrial energy management.
What problem an EMS should solve (and which it shouldn't)
An EMS doesn't exist to show charts. It exists to enable decisions that save money: detecting a demand peak before it triggers the month's charge, alerting to a power factor that's dropping, comparing the unit cost between plants, validating that the bill matches actual consumption.
If a software function doesn't end in a decision or an actionable alert, it's decoration. That's the first filter.
The 6 criteria to evaluate energy management software
| # | Criterion | Question the vendor must answer |
|---|---|---|
| 1 | Integration with the bill | Does it read my CFE/supplier bill and reconcile it with measured consumption? |
| 2 | Useful granularity | Does it measure at intervals that allow managing demand (15 min), not just the monthly total? |
| 3 | Actionable alerts | Does it warn before the cost occurs, or only report after? |
| 4 | The right KPIs | Does it calculate the indicators that matter or just chart kWh? |
| 5 | Total cost of ownership | What does license + hardware + implementation + support cost over 3 years? |
| 6 | Data independence | Is the data mine and exportable, or am I captive to the vendor? |
Criterion 1 · Integration with the CFE bill
The most immediate value of an EMS is reconciling what you measure with what you're charged. Software that doesn't read your bill or cross-check it against your real consumption leaves you blind to the most common problem: billing errors. See CFE billing validation: 7 common errors.
Criterion 2 · Granularity that allows managing, not just observing
Maximum demand is charged on the highest 15-minute peak of the month. Software that only shows you monthly consumption doesn't let you manage that peak. Granularity must be enough to act, not to fill charts.
Criterion 3 · Actionable alerts vs vanity dashboards
The difference between a useful EMS and a decorative one: the useful one warns you before —"you're going to exceed your contracted demand in 20 minutes"—; the decorative one shows you after what you already paid. Ask about the alerts, not the charts.
Criterion 4 · That it calculates the right KPIs
Charting kilowatts is easy. Calculating energy intensity per unit produced, load factor, or real unit cost requires crossing energy with production and with the bill. Those are the KPIs that move decisions. See Essential energy KPIs.
Criterion 5 · Total cost of ownership over 3 years
The annual license is the tip of the iceberg. The real cost includes meters and hardware, installation, integration with your systems, training, and support. Ask for the TCO over three years, not the list price of the first year.
Criterion 6 · Your data is yours
If switching vendors means losing your history, you're captive. Demand exportability and data ownership from the contract onward.
Build vs buy vs managed service
There are three paths, and the right one depends on size and the internal team:
- Buy and implement it yourself (buy): makes sense if you have an energy engineering team to maintain the system and act on the alerts.
- Build custom (build): rarely justified; you reinvent something that already exists.
- Managed service: the software plus a team that operates the cycle (measure, analyze, decide, report) for you, as part of an energy management service. It's what usually pays off most for plants without a dedicated energy area, because software alone doesn't save: savings come from whoever acts on what the software shows.
The most common budget mistake
Approving the software license but not the time of the person who will operate it. An EMS without someone to act on its alerts is pure expense. Before signing, define who owns the number and how much time they'll dedicate. If there's no one, the managed service is the answer. And for the full investment —license, hardware, and operation— to pass the financial filter, it's worth building it as a business case with payback for the CFO.
Next step
Choosing energy management software is a financial decision, not a technical one, and it should start from which decisions you want to enable and what return justifies the spend. At Enerlogix we evaluate your case without vendor bias within the 360 Management Plan, and if it makes sense, we operate the full cycle as a service so the savings actually happen.
Before signing any license, request a free evaluation of the 360 Management Plan. We help you define what you need —and what you don't— and how to justify it before your leadership, a topic we cover in executive energy reports for leadership.
Frequently asked questions
The annual software typically ranges from 60,000 to 400,000 MXN depending on scope, plus the hardware. But the relevant number for a CFO is not the list price of the first year, but the total cost of ownership over 3 years, which includes license, meters, installation, integration, training, and support, compared against the projected savings with your own data.
No. The software gives visibility; savings come from acting on that visibility. It's wise to distrust 30% guarantees without a business case built on your data. If a function doesn't end in a decision or an actionable alert, it's decoration. Software doesn't fix bad data, it just shows it faster.
It depends on the granularity you already have. Many plants need additional meters to manage demand at 15-minute intervals, because maximum demand is charged on the highest 15-minute peak of the month. Software that only shows monthly consumption doesn't allow managing that peak, only observing it.
Between 4 and 12 weeks, depending on the number of measurement points and the integration with your systems. Capturing the historical series for a baseline can start earlier, with your own bills. It's best to first have a reliable database of consumption and billing before exploiting any tool.
Yes. Even on CFE basic supply, managing maximum demand, power factor, and bill validation generates enough savings to justify the investment. The most common budget mistake is approving the license but not the time of the person who will operate it: without someone to act on the alerts, it's pure expense.
