Blog

2026.11.10

Product-Level Electricity Cost Allocation for Manufacturers

Product-Level Electricity Cost Allocation for Manufacturers

A factory considering a product-level electricity cost allocation system needs more than a chart of total kWh. It needs a defensible answer to which meter interval belongs to which production order, batch, lot, and good quantity; how shared utilities, idle time, and rework are treated; and how the resulting cost reconciles with the electricity bill and ERP ledger. This guide turns those decisions into a data contract, allocation policy, RFP, and FAT/SAT acceptance plan for manufacturers in Thailand.

The core design: connect energy, production, and accounting ledgers

kWh is a physical quantity. Electricity cost is a monetary amount finalized under a contract, tariff, accounting period, and company policy. A correct meter reading does not automatically produce a correct product cost. Preserve interval readings first; join them to the production order and lot timeline; allocate consumption under an approved rule; then reconcile the amount with ERP cost centers and accounting documents. Keep versions of raw readings, allocation rules, tariff inputs, calculations, and approvals. A revised good quantity or late meter reading must produce an explainable new calculation rather than silently replacing the old one.

General energy monitoring answers how much a site, building, or asset consumes and whether consumption is unusual. Product costing asks how much an identified batch absorbed, why the cost changed, and who approved a correction. ISO 50006:2023 addresses energy performance indicators and baselines; it does not prescribe a plant’s product accounting policy. The two purposes can share metering data, but they require different decisions and evidence.

Choose the cost object and denominator before buying software

“By product” may mean a monthly SKU average, a production order, a lot, an operation, or an individual machine run. Each requires different meter coverage and MES detail. A monthly product-family estimate may use line kWh and machine hours. An actual lot-level figure needs reliable start, pause, changeover, finish, and quantity records on the same time axis as the meter. State the decision the calculation will support: for example, review weekly lot electricity cost and good-unit kWh for one product family to investigate operations with a material variance. Sampling more data than that decision needs can increase integration and maintenance cost without improving the decision.

Define kWh, THB, good units, rejects, rework, and held units separately. If the energy intensity denominator is good output, a zero-good-output lot is an exception, not a divide-by-zero result. A metric based on input quantity may also be useful, but it needs another name. Mark provisional in-period costs and final monthly costs as different states. Otherwise a report may display an estimate as if the bill had already been posted.

For the wider cost-model boundary, see standard costing implementation and variance analysis. For meter connectivity, see factory power-meter data collection. The missing bridge between them is the subject here: assigning actual interval kWh to production and reconciling the money.

Build a meter-to-MES mapping that survives equipment changes

Start with the single-line diagram, distribution boards, meters, assets, lines, and product families. A meter called “Line A” may include a dryer, compressor, inspection machine, conveyor, and lighting. Record the meter ID, CT ratio and configuration, cumulative or interval reading type, unit, time zone, missing-data flag, retry behavior, calibration, and replacement history. Make meter-to-asset and asset-to-line relationships effective-dated. A wiring change today must not silently rewrite last month’s cost.

MES needs order ID, item and revision, operation ID, equipment ID, lot ID, start, stop, resume and completion events, and good, reject, and rework quantities. Machine state may arrive from a PLC while order selection comes from a terminal. Their clocks may differ. The interface contract must define event time, receipt time, time synchronization status, time zone, delayed arrival, and who resolves an unassigned interval. It is a business decision about ownership of electricity, not merely a CSV field mapping.

Product-Level Electricity Cost Allocation for Manufacturers - figure 1

Avoid adding upstream and downstream meter readings into one total: that double counts the same electricity. Use the incoming meter for total reconciliation and submeter readings for allocation, then hold the difference in a named pool for unmetered load, loss, or unresolved mismatch. Estimated readings need an explicit quality flag, method, cap, and approval. If the source provides cumulative counters, calculate differences and detect reset or rollover. A negative difference should be investigated before it becomes a negative cost.

Calculate batch or lot kWh from interval overlap

The basic method intersects a metered interval with an order’s active interval. Suppose a machine records 30 kWh from 12:00 to 12:15. Order A runs for the first ten minutes and B for the last five. A time-proportional allocation gives 20 kWh to A and 10 kWh to B. This is an assumption that load was roughly uniform within the interval. Heating, startup, cleaning, or changeover may violate it. Choose shorter readings, machine-state weights, or an additional meter where the error matters; record the assumption and test its sensitivity.

When two orders share an asset simultaneously, time alone is insufficient. Processing volume, actual occupancy, observed cycles, recipe, or another approved driver can divide the interval. Quantity proportion is an allocation assumption, not a direct measurement. Compare plausible drivers and show their effect on monthly cost. If a closed order’s good quantity changes, the per-unit intensity changes too. Retain the original result, calculate a new version, and preserve the difference.

An idle machine may still draw power. Allocating all idle kWh to the nearest product can make the product seem inefficient because of unrelated downtime. Moving all idle kWh into overhead can hide long changeovers caused by that product. Classify planned standby, changeover, breakdown, quality hold, off-shift standby, and cleaning, then assign an owner and approved driver. Unexplained time should remain visible in an exception pool rather than be forced into products at month-end.

Treat shared utilities, standby, and rework explicitly

Compressed air, HVAC, extraction, chilled water, and lighting serve more than one order. A residual split equally across all products is hard to defend. Define each shared utility’s benefiting lines and periods; where available, use run time, flow, operating assets, or another observable driver. If there is no signal, apply a time-limited provisional rate and plan a meter or observation study. Record the rule version, effective date, basis, and approver. A retrospective change should link to its adjustment entry.

Standby is not zero simply because there is no current order. A furnace may maintain heat; refrigeration or exhaust may be needed for safety or quality. Distinguish planned order standby, maintenance necessity, and demand-driven idle time. Management cost for quotations, accounting cost for inventory valuation, and an improvement-loss indicator may use different treatments. Do not put all three into an unlabeled column. The accounting team owns the policy; the system must reproduce it.

Rework is a common source of double counting. Decide whether the first run and rework kWh both stay with the original lot or whether rework has a separate order and variance. Electricity consumed by scrap does not disappear, even when scrap is removed from the good-unit denominator. Define where that cost appears. Preserve parent-child relationships after lot split or merge so previously allocated kWh and THB remain traceable.

Product-Level Electricity Cost Allocation for Manufacturers - figure 2

Tariffs, bills, and ERP valuation need separate decisions

Depending on the contract and period, an electricity bill may contain components beyond simple energy volume. Do not assume a universal tariff or tax rate. Import period, invoice ID, cost component, currency, cost center, journal, adjustments, and tax treatment from ERP or accounting. Decide which components belong in product cost and which remain separate. If time-of-use rates apply, match interval timestamps to the effective tariff version. A provisional rate can support daily analysis; after the bill arrives, calculate and approve the difference. Retain what users saw before finalization.

A useful provisional display may be “measured production kWh × provisional energy rate.” Monthly reconciliation then tests whether product allocations plus shared, unallocated, and adjustment amounts equal the ERP amount in scope. This is a calculation pattern, not a prescribed accounting policy. Demand-related charges may need a driver other than interval kWh. Late invoices, retrospective correction, multiple currencies, and a mid-month contract change should be explicit test cases.

ERP cost-center allocation can handle part of the monetary process while meter-to-lot attribution still happens elsewhere. SAP’s public help documents allocation and valuation concepts, but actual capability depends on product version, configuration, accounts, and the plant’s workflow. Test what the existing ERP can perform before adding a new costing engine. Choose the detail sent from MES or the allocation service to ERP, and retain a path from accounting result back to the source meter interval.

Reconcile physical volume, assigned volume, and money

First reconcile incoming kWh with submeter totals, shared load, and unexplained difference. If downstream totals exceed the upstream reading, investigate double counting, CT settings, period alignment, and counter reset. Second reconcile allocated kWh with the metered scope: every interval should be assigned to an order or an explicit exception pool. Third reconcile product, shared, unallocated, and adjustment THB with the ERP cost center in scope. Set tolerance, reason code, owner, due date, and approver at each stage.

Automatically moving every residual to “other” makes a report balance while hiding the cause. Derive thresholds from meter quality, sampling interval, finalization timing, and financial materiality. Matching totals alone does not close a case. A complete record includes period, input versions, rule version, calculation run, approval time, and ERP document. For interface timeouts and replay, the same transaction-level discipline described in ERP–MES error monitoring and replay applies.

Product-Level Electricity Cost Allocation for Manufacturers - figure 3

Set system ownership and correction rights

The metering platform holds raw readings, quality flags, and configuration history. MES holds orders, lots, operations, quantities, and asset-use facts. ERP holds approved item and cost-center masters, accounting periods, tariff and invoice inputs, journals, and final cost. This is a starting allocation of responsibility; define the authoritative source field by field in the current environment. A separate allocation engine should not become an uncontrolled fourth master ledger.

Carry meter event ID, order ID, lot ID, tariff version, calculation run ID, and ERP document ID as a traceable chain. Apply duplicate readings only once. Corrections should preserve the original event and create a revision or reversal. A late meter interval must not silently overwrite a closed month: show the impact, request recalculation, obtain approval, and send the monetary difference to ERP under its policy. Store UTC event time alongside local factory and accounting dates where systems cross time zones. Whether to extend MES or add a separate module depends on the quality of order changes, ERP import capability, and maintenance of wiring history. The MES implementation Go/No-Go guide provides a broader boundary and acceptance framework.

Worked example: keep the unassigned balance visible

The following numbers illustrate a method, not an actual Thai tariff or plant result. Assume 1,000 kWh at the incoming meter, 720 kWh across production submeters, and 180 kWh explained by shared utilities. The remaining 100 kWh stays in an investigation pool for unmetered load, losses, or period mismatch. Of the 720 production kWh, MES can link 420 to order A and 250 to order B. The remaining 50 kWh has no reliable order association and stays as an exception.

Even if the scoped invoice cost were 4,000 THB, it would be premature to multiply every kWh by 4 THB and call A’s cost final. Determine the components and drivers to allocate. If A has 200 good units and B has 100, their interval-based energy intensities are 2.1 and 2.5 kWh per good unit. Rework of 40 kWh for A or a corrected good count would alter those figures. Label every result with period, quality status, cost-finalization state, and allocation-rule version. The 100 and 50 kWh gaps indicate what to investigate: perhaps a missing HVAC meter, a wiring-map error, or an order-terminal workflow issue.

Put calculable cases in the RFP

Specify lines, meters, product families, order volume, required granularity, input formats, current gaps, manual-correction rights, ERP interface, languages, support hours, and retention. “Show cost by product” lets vendors price incomparable scopes. Provide anonymized normal, simultaneous, idle, rework, missing-reading, month-crossing, and correction cases. Ask each bidder to reproduce the calculation and show the ledger, not only a dashboard.

RequirementPlant inputEvidence requested
MeteringMeter/CT, period, communication, wiringPoint list, missing data and replay behavior
ProductionOrder, lot, operation, quantity, timestamp definitionsInterval join and correction calculation
AllocationShared, idle, and rework policiesFormula, versioning, sensitivity
AccountingCost components, period, cost center, approvalsERP bridge, adjustment, audit trail
OperationRoles, languages, service, backupAccess matrix and recovery exercise

Compare initial and running costs under the same period: meters, gateways, MES changes, ERP integration, terminals, data retention, rule maintenance, and month-end labor. A universal cost estimate is unreliable because existing meter coverage, MES accuracy, and ERP change rights vary. If Thai BOI measures may apply, verify current official conditions, activity, timing, application, and approval for the specific case. The name “electricity cost system” is not proof of eligibility.

FAT/SAT must test exceptions and reconciliation

At FAT, use simulated meter and MES data to test duplicate intervals, counter reset, missing readings, clock drift, A-to-B order switch, simultaneous use, idle state, rework, lot split, quantity correction, month boundary, and tariff version. For each, write inputs, expected kWh and THB, exception state, approver, and expected ERP result before the demo. Check that replay does not double count and that correction passes only the appropriate difference to accounting.

At SAT, run agreed cases with real meters, network, MES, ERP, permissions, and shifts. Any test involving machine stoppage must follow plant production and safety procedures. Verify local-to-accounting-day mapping, communication recovery, late arrival, and escalation when an approver is unavailable. A working dashboard is insufficient: the plant must trace an order to a meter interval and an accounting document, with the unreconciled queue resolved or explicitly owned. Run parallel calculations for an agreed period before promoting results into official cost. A large difference may reflect an old rough allocation, but the cause must be explained.

Roll out one line and one product family first

Start by matching one accounting period of invoice and ERP cost, meter readings, and MES order history. Find missing points, clock offsets, unselected orders, and incompatible cost components on paper. Build a small test set with normal and exception cases, then attach the rule and approval workflow to the RFP. Next, preserve raw data and calculate provisional results in parallel with the existing close. Measure baseline close time, variance cases, unallocated kWh, and cost corrections before calling the pilot a success.

Production checks order-change workload; maintenance owns meter reliability; accounting owns cost and journal bridges; IT/OT owns data latency, access, and recovery. Before extending to another line, demonstrate a full month recalculation and export of its audit evidence. A successful system produces a number that its owner can explain, correct under approval, and trace to ERP.

Keep data quality and change control visible

Zero kWh is an observation; a missing value is not zero. Preserve observed, interpolated, entered, estimated, and invalid states and carry their quality into allocated cost. During a meter replacement, link the old final counter, new initial counter, change time, CT settings, and service record. Stop automatic allocation if the transition creates an implausible difference. Effective-date meter, equipment, operation, and product masters so later renaming does not distort history.

Separate trial and approved versions of tariff and allocation changes. A request should show the period, affected products and lots, amount, start date, and rollback method. A retrospective application is a business decision requiring approval, not an invisible recalculation. Design role-based screens: production sees order and lot intensity; maintenance sees meter health and hierarchy balance; accounting sees cost components, unallocated amounts, and posting state. A missing order selection may go to an exception pool and be corrected with evidence at shift end where plant operations require continuity.

Compare multiple plants only after normalizing scope

Two plants can produce the same SKU with different operations, equipment, meter coverage, and shift patterns. Before comparing kWh per good unit, align the operations included, definition of a good unit, treatment of rework, and inclusion of shared utilities. If one plant includes HVAC and the other excludes it, the ranking does not identify the more efficient plant. Display meter scope and unallocated share next to the intensity value. Break results down by product family, operation, and operating condition when equipment capacity and mix differ. A normalized improvement benchmark and each plant’s actual accounting cost serve different purposes.

Headquarters may request a single indicator, but the plant needs a path from that indicator to raw readings, order events, quantity revisions, and tariff versions. A rising SKU intensity may reflect a changed recipe, longer furnace standby, lower good yield, a different shift, or a faulty meter. Use a common minimum data contract for meter ID, asset, order, lot, unit, time, quality flag, and calculation version across sites, while allowing site-specific shared-utility drivers, tariff periods, and approval roles. Standardize accountability without pretending different plants have identical physical facts.

Design role-based screens, security, and retention

A large dashboard for every role hides the work to be done. Production needs order, lot, and operation kWh, good-unit intensity, change from the prior run, and idle/rework breakdown. Maintenance needs missing readings, CT settings, communication health, and upstream/downstream meter difference. Accounting needs tariff version, cost center, component, unallocated THB, posting state, and pending approval. Each role should be able to drill to the same evidence without seeing fields it does not need. Cost rates, customer product codes, and production schedules can be commercially sensitive even when a raw meter value is not. Apply equivalent access control to CSV exports and APIs, and log view, change, approval, and export actions.

Set retention separately for raw high-frequency data, interval aggregates, allocation detail, approvals, and ERP document references. If raw data is archived quickly, retain enough interval and quality evidence to reproduce monthly cost. If everything is stored indefinitely, cost and governance burden rise. Agree online and archive periods, restore time, and deletion approval with accounting and company policy. A backup file alone does not prove that the plant can restore and rerun a closed month’s calculation. Test that restoration path.

During an outage, identify whether the meter, gateway, and MES buffer values and events. After recovery, late or out-of-order events should be evaluated by event time and version, while an already posted ERP amount must not be posted again. If a meter fails, an estimate should not become official cost without showing its amount at risk and approval status. Include outage, recovery, recalculation, and adjustment posting in one SAT scenario. If an order selection is missing, continuing production may be appropriate; place the interval in an exception pool and require a documented correction at shift end.

Align production and accounting before inviting bids

Use the same sample order to ask what each department means by “cost.” Production may want a quick value to change an operating condition. Accounting may need a final number reproducible for inventory valuation and the monthly close. Show both, but label their purpose and finalization time. Agree whether finalization happens when the meter reading arrives, the order closes, the invoice arrives, or the journal is approved. Agree whether a later correction changes historical provisional reports or creates an additional revision.

Assign exceptions to the department that can resolve the underlying fact. Maintenance investigates meter and wiring differences; the shift owner resolves unselected orders using work records; accounting checks components and journals missing from the cost center. Record primary owner, due date, substitute, and escalation. If improvement intensity treats standby as an equipment loss while accounting allocates it to a product family, provide a bridge showing standby kWh, rate, THB, and accounting destination. A difference between these two views can be legitimate when its cause is visible.

Measure benefits carefully. A decline in energy intensity after implementation may also reflect changed volume, mix, temperature, equipment, or operating days. Record comparison periods, conditions, and dates of interventions. The immediate value of the system is an earlier, traceable explanation of which electricity belongs to which product and which exceptions remain unresolved. Only then can the plant assess the effect of an actual operating change.

Frequently asked questions

Can meters alone allocate electricity cost by product?

Meters identify energy by asset and time. Product and lot attribution requires MES order, operation, run-time, and quantity facts. Shared and unmetered loads need an approved driver or explicit exception pool, followed by accounting reconciliation.

Can 15-minute readings estimate lot electricity consumption?

Yes, by intersecting reading and order intervals, subject to an assumption about load within each interval. Heating and startup may require shorter intervals, state weights, or another meter. Retain the estimation method and quality flag.

Which system is authoritative: meter platform, MES, or ERP?

Meter readings normally originate in metering, production facts in MES, and monetary postings in ERP. Confirm source, correction right, approval, and handoff timing for each field in the actual plant.

Should standby and rework electricity go into good units?

There is no universal answer. It depends on cause, order and lot relationships, management purpose, and accounting policy. Keep improvement indicators and accounting cost distinct and version the chosen rule.

What does implementation cost?

Meter additions, MES data quality, ERP interface, localization, retention, and audit requirements determine the price. Issue the same sample cases to bidders and compare implementation and operating costs under equal assumptions.

Conclusion: retain what cannot yet be allocated

An auditable product-level electricity cost system links interval kWh, MES orders and lots, and ERP cost on common keys and time rules. It handles shared loads, standby, rework, missing data, and corrections explicitly, then reconciles physical volume, assigned volume, and money. Define those decisions in the RFP and prove exception handling in FAT/SAT before posting the result as final cost.

TOMAS TECH can help a Thailand factory map its existing meters, MES, and ERP into an allocation rule, RFP, and acceptance test. If you are still deciding what to measure and what to allocate, contact us to review one line and product family.

Sources