What EPMS does (and doesn’t do)
EPMS is the data acquisition and visualization layer for electrical infrastructure. It collects real-time and historical data from meters, breakers, transformers, generators, UPS, and ATS, then makes the data available through dashboards, reports, and alarms.
What EPMS provides when done well:
- Real-time visibility into electrical system state across the facility
- Energy consumption data for sustainability reporting, cost allocation, and demand response
- Power quality monitoring for sensitive loads
- Alarming on abnormal conditions (overloading, voltage events, equipment trips)
- Historical data for trending and predictive maintenance
- Sequence-of-events recording for fault analysis
What EPMS doesn’t do: replace protective relaying, replace the BMS, or generate operational value if no one looks at the dashboards.
EPMS platforms
Common EPMS platforms in the commercial and industrial market:
- Schneider Electric Power Monitoring Expert (PME) — Long market history, broad device support, on-premise or cloud deployment.
- Eaton Power Xpert Insight / PXM — Strong integration with Eaton equipment, networked across platforms.
- ABB Ability eDrives / Cylon — Less common in US commercial; more common in industrial/utility applications.
- Generic SCADA-based EPMS — Wonderware, GE iFIX, Ignition, and other industrial software platforms configured for electrical applications. Common in industrial customer environments.
- Cloud-native platforms — Schneider EcoStruxure, Eaton xPert Connect, and various startup offerings. Growing rapidly but maturity varies.
What to monitor and where
Common EPMS monitoring points by hierarchy:
Service entrance level
- Utility revenue meter data (kWh, kW peak demand)
- Main breaker status and trip data
- Utility power quality (voltage, frequency, harmonics)
Major distribution level
- Each major feeder breaker status, current, power factor
- Transformer temperature, loading, tap position
- MV switchgear protection relay status and trip data
Submetering level
- Major load groups (HVAC, lighting, process, kitchen) for energy allocation
- Tenant submetering in colocation or mixed-use buildings
- Critical load monitoring (refrigeration plants, IT loads, etc.)
Backup power systems
- Generator status, run hours, fuel level, alarms
- ATS position and transfer history
- UPS status, battery health, load percentage
Where EPMS deployments go wrong
- Over-monitoring. Specifying meters on every panel and every motor creates massive data volume that operations teams can’t use. Better to monitor strategic points well.
- No data consumer. The EPMS is installed but no one looks at the dashboards. Without operations engagement during design, the system becomes "installed and forgotten."
- Network architecture errors. Modbus TCP traffic on the same network as BACnet/IP traffic, network segmentation issues, IT/OT boundaries not properly defined. Reliability problems and security exposure.
- Sensor placement errors. CTs installed on wrong conductors, voltage taps from wrong phases, polarity errors. Discovered during commissioning if you’re lucky, much later if not.
- Time synchronization missing. Sequence-of-events analysis requires all devices time-synchronized to within a few milliseconds. NTP setup on the EPMS network is often overlooked.
- Cybersecurity afterthought. EPMS connects to corporate networks and cloud services. Vulnerability management, patching, and access control need to be designed in, not retrofitted.
How to design an EPMS that actually gets used
1. Define the operational use cases first
What questions will operations actually ask the EPMS? Energy cost allocation? Demand response participation? Critical load monitoring? Equipment health trending? Different use cases drive different monitoring points and different platform selection.
2. Engage operations during design
The people who will use the system after handover should review the design before construction. Their input on dashboard layout, alarm thresholds, and reporting requirements shapes whether the system gets used.
3. Plan for operational support
EPMS requires ongoing software updates, configuration management, and platform support. Plan for who provides this support and how the service contract is structured. Many EPMS deployments fail operationally because no one owns the platform after handover.
4. Build in cybersecurity from start
Network segmentation, firewall rules, account management, vulnerability scanning. These need to be defined during design, not bolted on after deployment.
5. Specify training requirements explicitly
System training for facility engineering staff. Documentation including specific use case walkthroughs, not just "here’s the manual." Refresher training annually for the first few years.