Drive Data as an Energy Meter: A Sceptical Guide for UK Plant Teams
Photo: Internet Archive Book Images, No restrictions, via Wikimedia Commons
Most Bosch drives installed on UK plant already measure more than the maintenance team uses. Motor current, estimated torque, output power, running hours, fault history and sometimes an internal kWh counter are available over the fieldbus, the drive display or an engineering tool. The temptation is to treat those values as a free energy meter. The better approach is to treat them as a useful submetering source with known limits.
What the drive actually knows
The drive does not measure shaft power directly. It estimates torque from current, flux and the motor model, then derives power from torque and speed. That estimate can be very good when the motor data has been commissioned correctly and the drive is operating in its normal range. It becomes less reliable at very light load, during rapid transients, when the motor parameters are wrong, or when the drive is operating in a field-weakening region.
A practical data set usually includes output current, torque or power, DC-bus voltage, running hours, fault and warning history, and a product or cycle counter from the PLC. If the drive has an energy counter, record its resolution and whether it counts only motor output or includes drive losses. Those details matter when the figure is presented as an energy report rather than a trend line.
From parameters to a kWh-per-product figure
Start by defining the boundary. A drive-derived figure normally covers the motor and drive, not the whole line. Auxiliary fans, conveyors, heaters, compressed air and control panels sit outside that boundary unless they are separately metered. For internal reporting, it is acceptable to report motor energy separately and add auxiliaries from other sources, provided the boundary is stated clearly.
Next, choose a sampling interval that matches the process. A one-minute average is adequate for a steady duty; a fast cycling machine may need one-second or event-based sampling. Integrate power over time to obtain kWh, then divide by the product count for the same period. Exclude planned idle time, changeovers and washdown unless those are part of the metric you intend to report. A kWh-per-tonne or kWh-per-1,000 units figure is usually more useful than a raw monthly total because it survives changes in production volume.
Validate the result against a portable power analyser or a clamp meter at the first opportunity. Run the comparison at several load points, not just full load. If the drive figure and the external meter differ by more than the uncertainty you are prepared to defend, investigate the motor parameters, CT polarity, sampling method and whether the drive counter includes regenerative energy.
Where the accuracy limits lie
Drive-derived energy data is excellent for ranking machines, spotting drift and building a picture of where energy is used. It is not revenue-grade metering. The torque estimate depends on a motor model that may have been auto-tuned years ago and never checked. Current sensors drift, DC-bus ripple affects short samples, and a kWh counter may have a resolution too coarse for a short product run.
There is also a boundary problem. A drive may report motor output power, while the electricity bill includes drive losses, cooling fans and standby consumption. At low load, those fixed losses can be a meaningful share of the total. If the site reports carbon from drive data, state whether the figure is motor input, motor output or an estimate of supply-side energy.
Presenting it defensibly
A defensible report needs a method statement, not just a dashboard. Record the drive model, firmware, parameter source, sampling interval, boundary, product counter source and validation date. Note any missing data and how it was treated. Use the current UK Government conversion factors for carbon reporting, and keep the factor version with the report so that later comparisons are not misleading.
For internal carbon and efficiency reporting, drive data is strongest when it is used consistently. Compare the same line, the same product family and the same boundary over time. A 6% reduction in kWh per tonne on a well-instrumented line is a credible improvement signal. A single absolute kWh figure pulled from a drive display and presented as a verified total is much weaker.
What it should never be used for
Do not use drive-derived energy as utility billing data, settlement data or a substitute for fiscal metering. Do not use it for external product carbon footprint claims without a validated measurement plan. Do not use it to size cables, protection or transformers; those decisions need design currents and fault levels, not an averaged drive parameter. And do not present it as regulatory-grade evidence unless the method has been reviewed by whoever owns the site's compliance reporting.
A practical rollout
Pick one Bosch drive and one product line. Map the available parameters and confirm which ones are actual measurements rather than model estimates. Log for at least two weeks, including a full production cycle and a quiet period. Compare the drive-derived kWh with a temporary meter. Then build a simple report: kWh per product, running hours, average load and data completeness. Only after that should the method be extended to other lines.
The sub-meter you already own is real, but it is an instrument with a personality. Use it for trend analysis, efficiency tracking and internal carbon reporting, with the limits written down. Treat it as a free clue rather than a certified answer, and it will earn its place in the maintenance and energy toolkit.
