Combining kWh per Unit: Divide the Totals Before Ranking Production Batches
Two production batches show different energy use per unit, and the weekly report averages the two displayed ratios. If the batches contain very different quantities, that average can misrepresent total energy divided by total output. Preserve both underlying quantities before choosing the aggregation.

Original conceptual illustration; not a live software screen, specific product or customer installation.
Key takeaways
Overall intensity needs matched energy and production totals.
An equal average of batch ratios answers a different question.
Zero production and missing coverage need explicit treatment.
1. Define what the combined figure means
For an overall specific-energy requirement, define the energy boundary, output definition and common reporting window. Decide whether output means accepted units, total units or another agreed measure. Mixing those definitions changes the question even when every calculation is correct.
Use the ProSight Software platform overview to begin a reporting discussion, then provide the required calculation and acceptance evidence. This article defines a reporting method; it does not claim a particular package includes a configurable ratio calculation or production-system connector.
2. Keep numerator and denominator together
Retain energy and production quantity for each included batch, with units, boundaries and quality. Combine only compatible records. Electricity for an entire site divided by output from one machine is not automatically that machine’s energy intensity.
For positive production quantities, dividing summed energy by summed output is equivalent to weighting each batch intensity by its production quantity. NIST’s weighted-mean reference describes the general sum-of-weighted-values relationship. Here the weights follow the explicitly chosen production denominator.
This is a different question from time-weighting irregular power samples. First establish trustworthy interval energy and production records. An aggregation formula cannot reconstruct missing observations or correct a meter boundary that includes unrelated equipment.
3. Compare two hypothetical batches
Suppose batch A uses 100 kWh to produce 10 accepted units, giving 10 kWh per unit. Batch B uses 900 kWh for 300 accepted units, giving 3 kWh per unit. The equal average of those two displayed intensities is 6.5 kWh per unit.
The combined production intensity is instead (100 + 900) / (10 + 300) = 1,000 / 310, approximately 3.226 kWh per unit. Multiplying that result by 310 reproduces the combined 1,000 kWh, subject to rounding.
Both arithmetic results can be computed, but they answer different questions. The 6.5 result describes an equally weighted average of two batch-level ratios. It must not be labelled as total energy per total unit. These are invented acceptance values, not a customer result or promised saving.

Original explanatory infographic. Values and test cases are hypothetical; equipment selection and implementation require project-specific verification.
Diagnostic comparison
Hypothetical record | Energy / output |
Batch A | 100 kWh / 10 units |
Batch B | 900 kWh / 300 units |
Combined | 1,000 / 310 = 3.226 kWh/unit |
4. Treat incomplete and zero-output periods honestly
An interval with energy use and zero production has no finite per-unit intensity under ordinary division. Do not silently replace the denominator with one or report zero intensity. Decide how standby energy belongs in the chosen production accounting boundary.
If energy is missing for a batch, excluding only that numerator while retaining its production can understate intensity. Apply a paired inclusion policy and report excluded quantities or intervals. Any estimate needs a visible method and approval appropriate to the decision.
Keep products with incompatible denominators separate unless an agreed conversion makes them comparable. A count of small items and a count of large assemblies may require a different normalisation. Do not create a universal efficiency ranking from quantities that represent different work.
Define energy, production and time boundaries.
Preserve each batch’s paired quantities and quality.
Sum compatible included energy and output separately.
Divide totals and disclose exclusions and zero-output rules.
5. Verify the report against an independent calculation
Build a small fixture containing unequal batches, zero output, missing energy and a boundary-crossing record. Calculate expected totals independently. Check filters, groupings and exports as well as the headline figure so that a dashboard change cannot alter the denominator unnoticed.
Round at presentation, while retaining enough precision for reconciliation. Record the measurement sources, inclusion rule, output definition and reporting window beside the result. A useful comparison also explains whether production mix or accounting boundaries changed.
For a ProSight Software project enquiry, bring matched sample records, the intended commercial decision and the proposed equipment boundaries. Confirm supported ingestion, calculations and reporting scope for the actual deployment. Request a demonstrable acceptance case before relying on the combined intensity.
Recommended equipment / related solutions
Start with the ProSight Software platform overview to discuss the supported software scope and the reporting evidence your team needs.
Where the requirement needs engineered integration or a tailored reporting workflow, review ProSight Custom project scope. Confirm deliverables and the exact supported deployment before selecting an implementation.
Related practical guide: Irregular Sensor Samples: When a Simple Average Answers the Wrong Question
Frequently asked question
Can I weight by batch duration instead?
Only if that answers the specified question. Overall energy per produced unit uses production quantity as the denominator; duration is a different weighting basis.
Technical references
Need help with your application?
Send the equipment models, current documentation and a sanitised test example. Discuss this integration and equipment requirement with ProSense; confirm the actual functions, interfaces and acceptance scope before purchase or deployment.

.png)
Comments