Use case · Energy
Energy consumption
wattiot reads power from the line's OPC-UA server, totalises it into kWh and splits it across the orders and shifts that were running.
01The situation
The bill says how much. Not where, and not why.
A line with an extruder, an oven, a packer and a compressor. Power analysers already measure every machine and the SCADA already publishes it on an OPC-UA server, but nobody ties it to what is being made.
At the end of the month one number arrives: the kWh of the whole plant. Which order, shift or product used them is left to an estimate.
What each order used, on the order's own record.
TodayA rough split at month end.
Power peaks, as they happen.
TodaySeen on the bill, weeks later.
What the idle line draws, apart from what it produces.
TodayBuried in the total.
02The schema
From the line to the screen, without touching control.
wattiot replaces nothing that already works: it subscribes to the OPC-UA server the line already publishes and sends every reading, encrypted, to the cloud.
What you already have
- Extruder
- Oven
- Packer
- Compressor
- L2.Extruder.kW
- L2.Oven.kW
- L2.Packer.kW
- L2.Compressor.kW
- L2.Active_WO
What wattiot adds
- OPC-UA subscriptionactive
- Local bufferready
- Encrypted uplinkTLS 1.3
- kW_Tot156.8 kW
- kWh_Tot1,240 kWh
- WO #44720.42 kWh/u
- The lineA power analyser on every machine measures its active power, in kW.
- OPC-UA serverThe SCADA publishes each measurement as a node. wattiot only reads: control is untouched.
- wattiot EdgeSubscribes to the nodes, stores locally if the network drops and forwards encrypted.
- wattiot CoreTotalises energy, ties it to the contexts and shows it live.
03From data to result
From instant kW to kWh per order.
Power is a snapshot; energy is the sum of every snapshot. wattiot integrates power into kWh and cuts that sum by the operational contexts that were active.
- 1Instant power
156.8 kWkW_Tot
Each machine's kW, as it arrives from the OPC-UA server.
- 2Totalised energy× Δt
1,240 kWhTOTALIZE(kW_Tot)
A virtual tag integrates kW over time: accumulated kWh, with no new meter.
- 3By contextby context
Afternoon shift
- WO #447114:00–17:00566 kWh
- Stoppage17:00–18:0062 kWh
- WO #447218:00–22:00612 kWh
Every kWh lands on the order, shift or stoppage that was active.
- 4KPI÷ units
kWh per unitkWh_Tot / units
Target 0.45
Stoppage62 kWh, nothing made
kWh per unit for every order, comparable across orders, shifts and products.
04Spec sheet
What the installation takes.
For the technical lead: where each reading comes from, how it is read and what it becomes.
- Source
- The line SCADA's OPC-UA server
- Protocol
- OPC-UA, node subscription. Read-only
- Signals
- Active power per machine (kW) and the active order
- Totalising
- TOTALIZE virtual tag: kW × Δt, reset every shift
- Operational contexts
- Shift, work order, product and line stopped
- KPIs
- kWh per shift and per order, kWh per unit, peak power
- Alarms
- Power peaks and consumption while the line is stopped
- On site
- One wattiot Edge on the line's network
Does this look like your plant?
We will show you on a scenario like yours: what to connect first, what you will see and which plan fits.