How to Reduce Energy Costs in Manufacturing Using ERP Data

Why energy costs slip through the cracks

Most plants pay the electricity bill without knowing which shift, machine or batch used the power. The meter spins, the invoice arrives, and the cost lands in overheads. When overheads rise, the accountant spreads the increase across every product, hiding the real culprits. The result is that no one on the shop floor feels responsible for energy waste, and the bill keeps climbing.

An ERP system that tracks production in real time can change this. By linking energy meters to cost centres, the system assigns every kilowatt-hour to the shift or batch that consumed it. The data is already there; it just needs to be collected and shown in the right report.

Map meters to cost centres

Start by listing every energy meter in the plant. Include sub-meters on high-consumption machines like compressors, chillers and dyeing vessels. Assign each meter to a cost centre in the ERP. Facteno, for example, lets you create cost centres for individual machines, production lines or entire departments. Once the mapping is done, the system can post energy consumption to the correct cost centre as soon as the meter is read.

If the plant has smart meters, connect them to the ERP via a simple API or a daily CSV upload. For older plants, a manual reading at shift change is enough to start. The key is consistency: read the same meter at the same time every shift, and post the reading to the same cost centre.

Record energy use per shift and per batch

At shift end, the ERP should show two numbers: the planned energy for the output achieved, and the actual energy consumed. The planned figure comes from the standard cost card, which lists the expected kilowatt-hours per unit of output. The actual figure comes from the meter reading posted to the cost centre.

For batch processes, record the meter reading at the start and end of each batch. Subtract the start reading from the end reading to get the energy used by that batch. Post this to the batch card in the ERP. Facteno does this automatically if the batch card is linked to the correct cost centre.

Here is an illustration for a dyeing plant:

The standard cost card allows 0.35 kWh per piece. Batch DY-24-058 used 0.40 kWh per piece, a 14% overspend. The shift supervisor can now investigate why the extra energy was used.

Set up alerts for energy drift

Configure the ERP to send an alert when energy per unit of output exceeds a rolling average. Use a 30-day average to smooth out normal variation. The alert should go to the shift supervisor and the production manager, not to the whole plant. Too many alerts and they will be ignored.

Facteno can trigger these alerts from the Business Control Centre, a single screen that shows money, orders, plant status and pending approvals. The alert can include the batch card, the energy reading and the standard cost card for quick reference.

Common causes of energy drift:

• The machine was not cleaned between batches, so the next batch took longer to reach temperature.
• The chiller was set too cold, increasing compressor runtime.
• A steam valve was leaking, so the boiler ran more often than needed.
• The shift changed the recipe without updating the standard cost card.
• The meter was read incorrectly, posting the wrong figure to the cost centre.

Reconcile utility bills against ERP readings

Every month, compare the utility bill against the sum of all meter readings posted to the ERP. The two should match within 1-2%. If they do not, there is either a billing error or a meter that is not being read.

For plants with multiple meters, use the ERP to group readings by supplier and by billing period. Facteno’s Finance & Accounts module can generate a reconciliation report that shows the total energy posted to each cost centre, grouped by supplier. This report can be sent to the utility company to dispute incorrect charges.

If the plant has a time-of-use tariff, the reconciliation must split energy use by time band. The ERP should record the time of each meter reading so the correct rate can be applied. Without this, the plant may be paying peak rates for energy used during off-peak hours.

Link energy costs to product costing

Once energy use is tracked per batch, it can be included in the product cost. The standard cost card should list the expected energy per unit of output. The actual cost card should show the energy used by the batch, pulled from the meter readings posted to the ERP.

Facteno’s Product Costing module builds the cost per piece from actual material, wages, utilities and overheads. If energy use rises, the cost per piece rises, and the profit margin falls. This gives the sales team a reason to care about energy efficiency: lower energy use means lower costs and higher margins.

For plants that sell to export markets, energy costs can be shown in the customer’s currency. Facteno’s multi-currency reporting applies the correct exchange rate to energy costs, so the customer sees the impact in their own currency.

When software is not the answer

An ERP system can track energy use, but it cannot fix a leaking steam valve or a clogged chiller. If the alerts show that energy drift is caused by maintenance issues, the solution is to schedule the repair, not to tweak the software.

Similarly, if the standard cost card is wrong, update it. The ERP can only compare actuals to the standard; it cannot set the standard. If the plant changes a recipe or a machine setting, the standard cost card must be updated to reflect the new expected energy use.

For plants with old equipment, the ERP can still help. Even if the machine cannot be upgraded, the ERP can show which shifts or batches are using more energy than expected. This data can be used to train operators or to justify the cost of a new machine.

What to do next week

Pick one machine that has its own meter. If there is no sub-meter, install a temporary one for a week. Map the meter to a cost centre in the ERP. At the end of each shift, record the meter reading and post it to the cost centre. Run the shift-end report and compare planned versus actual energy per unit of output.

If the numbers match within 5%, the process is working. If they do not, investigate why. Was the meter read incorrectly? Was the standard cost card wrong? Was the machine running when it should have been idle?

Once the process is reliable for one machine, add a second. Keep going until every high-consumption machine is tracked. The goal is not to monitor every watt, but to spot the 10-15% of energy that is wasted and cut it.