Energy per product becomes useful only when the energy numerator and production denominator describe the same boundary, time window and operating context. Meter readings, PLC states, recipe data and accepted output must be reconciled before the ratio is used for decisions.
The short answer
Define the product, energy boundary and reporting interval. Identify which meters cover the process and which PLC states distinguish production, idle, cleaning, warm-up, changeover and shutdown. Use accepted good output rather than an unexplained counter, preserve recipe and product mix, align clocks, and set rules for partial batches, rework, scrap, meter resets, gaps and estimates. Validate the calculation on representative periods before comparing lines, shifts or products.
- Numerator and denominator share the same boundary and interval.
- Operating states and product mix remain visible.
- Good output, scrap and rework are defined explicitly.
- Formula and allocation changes create controlled revisions.
Decision guide
| Method | Useful when | Control needed |
|---|---|---|
| Direct metering | One meter covers one product process | Meter boundary and batch time |
| State allocation | Shared equipment has reliable operating states | State logic and idle/changeover rules |
| Recipe allocation | Product mix drives energy materially | Recipe version, batch identity and quantity |
| Model allocation | Shared utilities require explanatory variables | Model validity, uncertainty and review |
A practical workflow
- 01
Define decision, product unit, boundary and interval.
- 02
Map meters, PLC states, recipes, counters and accepted production.
- 03
Synchronize time, units and quality; define exclusions and estimates.
- 04
Calculate and reconcile totals against source systems.
- 05
Approve the method, monitor exceptions and revise through change control.
Evidence and acceptance
Keep meter and asset boundaries, source tags, units and clocks, state definitions, recipe revisions, batch and product identifiers, accepted output and scrap rules, allocation formula, baseline, gap and estimate log, reconciliation totals, validation cases, uncertainty, approval and each reported-period input and result.
Common mistakes
- Dividing site energy by one line’s output.
- Ignoring cleaning, idle and changeover energy.
- Mixing gross count with accepted product.
- Joining recipe and meter intervals by local time without clock checks.
- Changing allocation rules while showing one continuous trend.
Responsibility boundary
Primary sources
Technical claims and product boundaries were checked against these primary sources. Fact-checked
Frequently asked questions
Should scrap be included?
Define the decision first; report good output and scrap explicitly so the denominator cannot hide loss.
How is shared utility energy allocated?
Use a documented, validated driver and retain the unallocated total and uncertainty.
Can PLC cycle counts be the denominator?
Only after reconciling them with accepted output, resets, rejects and manual production.
Does AutoNexit calculate the KPI?
No. It preserves the controlled method and evidence around calculations made in approved systems.