kWh per machine, per shift and per part — read from the meters, not the bill.
Energy meters on the LT panel and in each machine panel, and the compressor, chiller and other utilities, are read through the same MOS gateway that reads the machines. Consumption is tied to the machine state and the part count, so the plant knows the cost of a running hour, an idle hour and a single part — by line, shift and product — and sees air leaks and peak loads as they happen.
One number a month; no idea which machine burns energy idle or what a part costs in power.
“Meters on the LT panel and in machine panels are read through the same gateway as the machines and tied to state and count — so the plant knows the cost of a running hour, an idle hour and a single part.”
Drawn, not promised: the top row is energy known as one bill a month. The bottom row is the meters read through the same gateway, so the cost is known per machine, per shift and per part.
Hover or tap a stage to see what is captured there.
Not a standalone tool — a product on the MOS platform, sharing one login, one set of people and roles, and one database with every other module. The lit layers are the ones this product uses; the signal path shows how data moves through them.
The honest map, drawn as one thread. Filled nodes are in the product today; outlined nodes are other MOS modules on the same platform; dotted nodes are roadmap and never represented as available until built. Hover a node.
Each card ends with the thing itself as it appears in MOS — not a description of it.
Step through it or let it play. Each step: who does it, on what, what is captured, and the check that guards it.
Meters with a Modbus port are read as they are; a standard meter is added where a panel has none.
The LT panel, machine panels and utilities are read on the same gateway as the machines.
Every reading is stored against the machine state and the part count at that moment.
kWh per running hour, per idle hour and per part, by line, shift and product.
Peak loads, standby waste and air leak hours raise alerts.
The shift report carries energy next to output; monthly by line and product.
| Your ERP / Tally typically gives | Energy & Utilities adds |
|---|---|
| One bill a month | kWh by machine, line, shift and product |
| Energy as an overhead | kWh per part, from meter and count together |
| Idle machines burning quietly | Idle-hour energy shown per machine |
| Air leaks found on a walk | Leak hours from the compressor load |
Energy meters over Modbus RTU / TCP; existing meters read if they have a port
Compressor and chiller controllers
The same MOS gateway that reads the machines
MOS Edge in the plant
What it connects to, where it runs and what it gives you — the short version your IT and your plant head both want.
Meter reading, tie to state and count, kWh per part, peak/standby/leak alerts, energy in reports.
MOS OEE supplies state and count.
Meters without a Modbus port need a standard meter added.
Automatic load shedding — not represented as available.
Capabilities depend on the plant's process and what is connected at site. Nothing on this page is represented as available until it is built and running.
Which machine burns energy while idle
Compressor load and leak hours
Energy per part, by product and month
Energy cost allocated by line and product
Energy meters on the LT panel and in machine panels; existing meters are read if they have a Modbus port.
The same MOS gateway that reads the machines.
The MOS plant server — screens open in any browser on the network.
LT panel and one line's machine meters on screen.
Idle-hour energy and kWh per part per product start reporting.
Every line and product with its energy cost, next to output.
Only where there is none. Meters with a Modbus port are read as they are; where a panel has no meter, a standard meter is added.
Yes, through their controllers or a meter on their feed — load, pressure and run hours come the same way.
Yes. One gateway on the plant network reads machines and meters; energy per part needs both.
Every machine, live — and the real reason it stopped.
See the module →Every unit scanned at every station. Nothing skips a stage.
See the module →Every part judged by camera in under a second, defect circled.
See the module →Tell us about your plant and what you want to see. We visit, connect one machine or station, and you watch your own data in MOS before anything is quoted.