A power monitoring system (PMS) reads the power meters on a plant's electrical distribution and records energy, demand, power factor and power quality events, so engineers can see where the electricity goes and what happened when the supply misbehaved. It is made of meters on the incomers, feeders, MCCs and utility equipment, a network to read them, data servers, and a SCADA with a historian that turns the readings into alarms and energy reports. How a PMS relates to an FMCS, a BMS and an MES is covered in What is FMCS; this article follows Rockwell Automation's PowerMonitor documents and AVEVA's documentation along the path from meter to report.
1. What a power meter records
Rockwell's PowerMonitor 5000 (Bulletin 1426) manual lists what the meter measures: voltage line to line and line to neutral, current, frequency, voltage and current unbalance, real, reactive and apparent power, true and displacement power factor, energy in kWh, kVARh and kVAh, kW, kVAR and kVA demand, projected demand, demand power factor and crest factor (
The PowerMonitor 1000 (Bulletin 1408) manual explains the main quantities (
- Energy is kept as forward, reverse and net totals. When the kWh total rolls over to zero, the GWh total goes up by one.
- Demand is the average power over a demand period, 15 minutes by default. Setting more than one period gives a sliding-window demand. The end of each interval comes from the internal timer, status input 2 (an external end-of-interval contact), a controller command or an Ethernet demand broadcast.
- Projected demand is a linear projection to the end of the current interval; demand power factor is kW demand divided by kVA demand.
- True power factor is reported per phase and in total, lagging as negative and leading as positive.
Power quality is where the PowerMonitor 5000 models differ. The M6 adds harmonics up to the 63rd order, waveform capture and power quality event classification; the M8 adds flicker, sub-cycle transient capture, harmonics up to the 127th order and interharmonics (p. 18). Sag and swell detection is listed for all models, EN 50160 weekly and yearly logs for the M8 only (p. 21).
| Measurement | Where it is measured | What it is used for |
|---|---|---|
| Energy – kWh, kVARh, kVAh | main feeds, feeders, process lines, machines | consumption reporting, cost allocation by actual use, shadow billing |
| Demand – kW, kVA, projected | utility feed, plant areas | demand analysis, load profiling, keeping demand under a peak limit |
| Power factor | utility feed, feeders | power factor correction to cut utility penalties |
| Voltage, current, unbalance | feeders, MCCs, distribution panels | a central view of the distribution for trending, alarms and load shedding |
| Harmonics, sags, swells | utility feed, where power enters | power quality monitoring to protect equipment and reduce downtime |
| Status inputs – WAGES | PowerMonitor 5000 inputs | water, air, gas, electricity and steam data |
The table follows Rockwell's PowerMonitor Products Application Guide (
2. Where the meters sit
The application guide starts with "metering the envelope": energy monitoring on the plant main feeds, which shows total consumption, lets the utility bill be checked with a shadow bill and points to the largest users. Submeters then go on process lines and utility equipment such as compressors and boilers, and their energy is correlated with production indicators (p. 5). For each level it names a meter (p. 15):
- Utility feed: a PowerMonitor 5000, to catch power quality problems where power enters the plant.
- Feeders, MCCs, control panels: a PowerMonitor 1000, most often for submetering at cell or site level. Its manual states that it is not a circuit protective device (
1408-UM002E-EN-P p. 7). - Machines: a PowerMonitor 500, which also covers motors on across-the-line starters that give no energy data.
The current PowerMonitor 1000 models are BC3 (basic consumption), TS3 (adds voltage, current, frequency and unbalance) and EM3 (adds demand and the load factor log); TR1, TR2, EM1 and EM2 are discontinued (
3. What the meter keeps by itself
The PowerMonitor 5000 keeps energy, data, min/max, load factor, time-of-use, event, setpoint and alarm logs on every model, plus power quality, waveform, trigger and snapshot logs on the M6 and M8. It has setpoints, three relay outputs, one KYZ pulse output and four status inputs (
4. Communication: from the meter to the SCADA
The PowerMonitor 5000 has a native EtherNet/IP port with a web page, and optionally DeviceNet or ControlNet (
Through a Logix controller. Add-on Profiles in Studio 5000 Logix Designer bring meter data into the controller as tags: 16 parameters chosen by number on the PowerMonitor 1000, full configuration and monitoring on the PowerMonitor 5000 (
Directly over Modbus TCP. AVEVA's MBTCP Communication Driver (Communication Drivers 2026) has a generic ModbusPLC connection for Modbus controllers that are not on its supported list but follow the Modbus specification. Its settings show what must match the meter's register map: port 502 by default, a reply timeout of 3 seconds by default, one-based addressing unless zero-based is selected, byte swapping, register order for
Time. Events from different meters only line up if their clocks agree. The PowerMonitor 1000 sets its clock by SNTP (
5. From history to energy reports
Energy totals are counters, so a report needs the increase over each hour or shift. AVEVA's counter retrieval mode returns that increase for each cycle, including rollovers, using a rollover value set for each tag in the Historian, and it works with floating-point counters (Operations Management Interface 2026). How a historian stores data: what is a process historian.
Rockwell's guide lists what the data is used for: consumption reporting to catch leaks and waste, demand analysis, submetering, cost allocation by actual use rather than floor area, distribution monitoring, power quality, load profiling and shadow billing (
Two Rockwell energy software products appear in these sources. The 2018 guide describes FactoryTalk EnergyMetrix as a central energy database used through a web browser, with consumption, demand, billing and cost allocation reports and a power quality report of the sags and swells PowerMonitor units detect (pp. 26–29). FactoryTalk Energy Manager is a cloud software-as-a-service application on FactoryTalk DataMosaix, with dashboards for energy consumption, intensity, costs and emissions, energy baselines and measurement and verification. Meter alarms need priorities like any plant alarm: see
What we check first
This is TDL's practice, not a Rockwell Automation or AVEVA requirement.
- We list every meter from the single-line diagram: the incomer, feeder or MCC it sits on, its model, CT and PT ratios and port.
- We check that each model gives the values the report needs; on a PowerMonitor 1000, demand needs the EM3.
- We choose the path per meter: EtherNet/IP into a controller through the Add-on Profile, or Modbus into the SCADA driver, with gateway and unit IDs for serial meters.
- For Modbus, we set addressing base, byte swap and register order from the register map, then compare one known value with the meter's web page before building the rest.
- We confirm the demand period and its synchronisation source, and one time source for meters and servers.
- We set a rollover value for every energy tag and check one report period by hand against the meter's energy log.
- We keep the meters on the control network, in their own zone: see IEC 62443.
How TDL approaches it
At Samsung Electronics HCMC CE Complex (SEHC), TDL maintains and upgrades the FMCS and the power monitoring system under a yearly maintenance contract: 17 servers, 14 workstations and 37 PLCs on ControlLogix and AVEVA System Platform, with Modbus TCP and EtherNet/IP. The scope includes preventive maintenance with backups and restore tests, ControlLogix firmware migration and redundancy reconfiguration, extension of the AVEVA System Platform SCADA, Modbus TCP to EtherNet/IP communication, and FAT and site commissioning (project page). TDL is a System Integrator in the Rockwell Automation PartnerNetwork and a System Integrator member of the AVEVA Partner Ecosystem. Services: facility monitoring (FMCS) and SCADA and historian.
Frequently asked questions
What is the difference between a PMS and an FMCS?
A PMS watches the electrical network: energy, demand, power factor and power quality from meters on incomers, feeders and machines. The FMCS article explains how the two relate; at SEHC, TDL maintains the FMCS and the PMS together on ControlLogix and AVEVA System Platform.
Where should power meters be installed in a factory?
Rockwell's application guide starts with the plant main feeds, then submeters on feeders, process lines and utility equipment such as compressors and boilers. It puts a PowerMonitor 5000 at the utility feed, a PowerMonitor 1000 on feeders and MCCs and a PowerMonitor 500 at machine level.
How is electrical demand calculated?
Demand is the average power over a demand period. On a PowerMonitor 1000 the period is 15 minutes by default, more than one period gives a sliding window, and the end of each interval can come from the internal timer, status input 2, a controller command or an Ethernet broadcast.
Can a PowerMonitor be read over Modbus?
The PowerMonitor 1000 supports Modbus RTU on its
How is a meter's energy total turned into consumption per shift?
The energy total is a counter that rolls over, so a report needs the increase per period, not the raw value. AVEVA's counter retrieval mode returns that increase for each cycle, including rollovers, using a rollover value set for each tag in the Historian.
Sources
- Rockwell Automation,
1426-UM001L-EN-P , PowerMonitor 5000 Unit User Manual, 11/2022 — p. 17–21 - Rockwell Automation,
1408-UM002E-EN-P , PowerMonitor 1000 Unit User Manual, 04/2023 — p. 7–12, 60–65 - Rockwell Automation,
1400-AT001A-EN-P , PowerMonitor Products Application Guide, 09/2018 — p. 5–10, 15, 18–30 - Rockwell Automation, 1426 PowerMonitor 5000, product page
- Rockwell Automation, FactoryTalk Energy Manager, product page, and FactoryTalk Energy Manager User Guide, Introduction
- AVEVA, Get started with the MBTCP Communication Driver, ModbusPLC connection, ModbusBridge connection and ModbusPLCRS connection, Communication Drivers 2026 documentation
- AVEVA, Counter retrieval, Operations Management Interface 2026 documentation
Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.