Energy monitoring projects fail in two familiar ways: dashboards nobody acts on, and consultant systems disconnected from the machines. Building on the PLC/OT layer you already own avoids both.
The architecture
Meters integrate per the patterns this blog keeps returning to: Modbus meter parks through an edge concentrator, machine-level energy from the drives themselves (modern drives meter their own consumption — free granularity nobody uses), and critical feeders on proper meters with the register maps documented as contracts. The data lands where machine data already lives — historian or Zsense-class platform — because energy divorced from production context is just a bill with extra steps: kWh per tonne slit, per pressing cycle, per shift is where decisions hide.
From numbers to actions
The reports that change behavior are small: a weekly per-machine league table with baselines (the drive retrofit posts’ before/after habit, institutionalized), idle-consumption flags (the machine drawing 30 % of full power while “off” is the classic first win), and demand-peak context for load-management decisions — staggering big starters and managing peak windows is often worth more than efficiency itself under demand tariffs. For plants heading to ISO 50001, this same layer becomes the measurement backbone — the standard wants exactly the baselines and significant-energy-user tracking the OT data already provides.
Start small and honest: ten measuring points chosen by bill impact, three reports someone owns, review after a quarter — then scale what got acted on.
FAQ
Meters on everything? No — meter the significant users and calculate the rest; the drive-reported energy covers machine granularity cheaply.
Who should own the weekly report? Whoever can change schedules and setpoints — energy reports owned by accounting describe the past; owned by operations, they change it.
Zone Otomasyon builds energy monitoring into retrofits and Zsense deployments — measurement first, dashboards second, decisions always. Energy projects.