Take your energy data back from the meter vendor
Every industrial plant in India runs on electricity, and every plant has energy meters. Modbus, mostly. Sometimes with a nameplate from Schneider, Selec, Elmeasure, or a private-label OEM.
Ask the plant manager where the data goes. In more plants than we’d like to admit, the honest answer is the same shape:
Meter reads its own readings. Pushes them to the meter supplier’s server. The supplier hands back a Power BI or a portal login. Monthly bill to see your own numbers.
Same meter. Modbus port on the local bus. Edge Node reads it, buffers it, keeps it on infrastructure you own. Your dashboards, your SQL, your export.
The plant produces the electricity data. The plant owns the meters. But the plant is renting access to its own numbers.
How did this pattern take hold?
Meter suppliers figured out something obvious: a meter is a commodity, but a dashboard is a subscription. Selling the meter is a one-time margin. Selling the meter with a cloud service attached is a recurring one.
So the meter ships with two ways to speak. Modbus for the shop floor. A cloud phone-home for the vendor. Most plants never realise the Modbus port is right there — the vendor never mentions it, the SI team doesn’t use it, and the vendor cloud is the path of least resistance to get something on a screen.
By the time the CFO notices the monthly bill, the plant’s data has been living on the vendor’s disks for two years.
The Modbus port was there the whole time
Every serious industrial energy meter exposes Modbus TCP or Modbus RTU on a local port. It’s not a hidden feature. It’s in the datasheet. It’s wired to your OT network already, because commissioning needs it.
That local port is the same one the vendor’s cloud gateway uses on the plant side to read the meter and forward the data upward. There’s no proprietary protocol involved. It’s Modbus, and Modbus is a public standard from 1979.
If your meter vendor tells you Modbus won’t give you the same fidelity as their cloud, ask them which registers their cloud reads. It’s the same registers. The vendor cloud is a Modbus reader with a UI on top.
What EdgeBits ships today for this
The path we set up for a plant that wants to take its energy data back looks like this:
An Edge Node on the plant floor. Small Linux box — Raspberry Pi 4 to industrial PC, whichever fits your enclosure. Debian or Rocky Linux. Reads the meter over Modbus TCP or Modbus RTU using our production connector. Same port the vendor cloud uses, just pointed at your box instead of theirs.
A local buffer on TimescaleDB. Every reading — kWh, kVA, kVAr, power factor, voltage, current, harmonics if you want them — lands in a hypertable on your box. Retention is your call. Ninety days at raw resolution and three years at hourly rollups is a common starting point.
Your dashboards. Edge Analytics is a full data-plane if you want per-line, per-shift, per-plant energy dashboards, BEE / PAT reports, and benchmarking out of the box. It runs on your server, or in your VPC. If you already run Grafana or Power BI, the REST egress feeds those from the same TimescaleDB.
Nothing leaves the plant unless you decide. If your compliance team wants an air-gapped setup, that’s a config flag. If your finance team wants monthly data to land in SAP, that’s another egress.
The rupee math
Illustrative example. One plant, twelve meters across two sites, current hosted-dashboard bill you can find on your own vendor invoice.
The numbers scale linearly with meters. Ten sites, sixty meters, and the delta gets into serious operating-cost territory. And that’s ignoring the fact that your data is now portable — you can add a second analysis tool without paying the vendor a second time.
Pilot in a week: one line, one meter, on your infrastructure. If the readings match the vendor cloud (they will), the extension across all your meters is a config file. Book a scoping call on the contact page.
What OEE has to do with this (nothing, and that’s the point)
Energy is often the entry point, not the finish line. Buyers who take their meter data back usually add a second use case within six months: shift energy per tonne, per work order, per cost centre. Sometimes an OEE dashboard follows. Sometimes it doesn’t — the buyer just wants clean energy visibility and reliable BEE / PAT reports, and that’s a valid stopping point.
Either way, the data is yours. Every downstream use case is one more consumer of a database that already belongs to you.
Own your energy data
30-minute scoping call. We’ll tell you plainly whether your meters can be read via Modbus (they can), what the plant-floor Edge Node looks like, and what the annual delta versus your vendor cloud actually is on your invoice.
Book a call