VoltMage Edge EMS
Collects sub-second telemetry, manages the local operations queue and coordinates on-site dispatch.
Product detailEnergy management system for BESS
A battery EMS that connects optimization to reliable site execution.
VoltMage Edge EMS provides the local operating bridge between cloud intelligence, site telemetry and the PCS/BMS control envelope.
REAL DEPLOYMENT Local telemetry, command validation and edge execution form part of the 30 MWh Kostinbrod deployment.The operating problem
A dispatch instruction is only useful if the site can accept, validate and prove it.
Cloud optimization and market schedules operate on different time horizons from plant controls. A BESS EMS has to translate between them, preserve equipment authority, manage intermittent connectivity and give operators evidence of what was requested and delivered.
- Collect and normalize battery, PCS, meter, alarm and site telemetry with reliable timestamps.
- Prevent an economic instruction from overriding the BMS, PCS or electrical protection envelope.
- Translate approved schedules or setpoints into the interface expected by the plant.
- Handle command priority, local queueing, acknowledgement and connectivity recovery.
- Maintain a traceable record from requested action to measured response.
How VoltMage solves it
Local control with cloud context and plant authority intact.
VoltMage Edge EMS is installed at the site and connects the plant to VoltMage Cloud. Integration is designed around the equipment and interface map of each asset; the website does not assume a protocol or command path before that technical assessment.
VoltMage Signals
Interprets operating events, alarms, deviations and changing asset context.
Product detailVoltMage Aptitude
Applies asset policy and validates proposed actions before the local dispatch path.
Product detailVoltMage Data Platform
Organizes time-series telemetry, asset relationships, quality flags and downstream access.
Product detailHow it works
From input to verified operating outcome.
Each stage keeps its own responsibility and evidence. That makes it possible to test the commercial logic before expanding control authority.
-
01
Map the plant
Document meters, PCS, BMS, protection, gateways, command ownership and network boundaries.
-
02
Connect read-only
Ingest telemetry first and validate timestamps, units, quality and equipment behavior.
-
03
Define the envelope
Encode local limits, command precedence, failure modes and operator approval rules.
-
04
Shadow commands
Generate intended actions without controlling the plant and compare them with actual operation.
-
05
Validate locally
Check current readiness and reject instructions outside the permitted envelope.
-
06
Execute selectively
Release agreed commands through the site-specific interface.
-
07
Verify response
Measure acknowledgement and delivered power against the requested setpoint.
-
08
Escalate exceptions
Preserve logs and operator visibility when a command is delayed, constrained or rejected.
Commercial outcomes
What a connected operating layer changes.
- A clear boundary between economic optimization and embedded equipment protection.
- Lower operational ambiguity between cloud schedules and physical delivery.
- Local continuity for queued actions and telemetry during connectivity interruptions.
- A staged path from monitoring to selected control and guarded autonomy.
- Comparable execution evidence across sites and equipment vendors.
- Faster diagnosis of missing, delayed or constrained asset response.
Technical capabilities
Designed for real asset constraints.
- Sub-second plant telemetry collection where the site interface supports it
- Local operations queue and on-site dispatch
- EMS/BMS/PCS and meter integration mapping
- SOC, active/reactive power, ramp and grid-limit checks
- Requested-versus-delivered setpoint tracking
- Cloud orchestration, local event handling and connectivity recovery workflows
Integration scope: interfaces, protocols, control authority and market access are confirmed for each asset. VoltMage does not claim universal compatibility or market eligibility without technical and commercial review.
Built for the operating team
One system, different decisions.
Asset owners
Create a governed and measurable control path without weakening embedded safeguards.
EPCs and integrators
Define boundaries between plant equipment, gateway, EMS and cloud optimization.
Operations teams
Observe commands, acknowledgements, telemetry quality and exceptions in one chain.
Portfolio operators
Standardize operating evidence while preserving site-specific implementation.
FAQ
Questions buyers and technical teams ask.
FAQ content is visible on the page. FAQ structured data is intentionally omitted because current Google eligibility is restricted and this is a commercial software site.
What is the difference between a BMS, PCS and EMS?
The BMS protects and manages battery cells and packs. The PCS converts power and enforces converter limits. The EMS coordinates plant-level operation, schedules and setpoints across those systems. The exact boundary varies by project.
Does VoltMage replace the BMS?
No. VoltMage is positioned above the embedded BMS and electrical protection. Those systems keep authority over the battery safety envelope.
Can VoltMage work with an existing EMS?
Yes. VoltMage can operate with an existing EMS when its interfaces and responsibilities are suitable. The integration design defines which system owns scheduling, validation, command translation and local execution.
Which communication protocols are supported?
Protocol support is confirmed against the actual PCS, BMS, meters, gateway and existing EMS during technical discovery. VoltMage does not publish a universal compatibility claim before reviewing the site interface documentation.
What happens if cloud connectivity is lost?
The edge design includes a local operations queue and site-specific fallback behavior. The exact action—hold, complete, reject or revert—must be defined in the approved plant operating policy.
Can the EMS control reactive power?
Reactive-power monitoring and control can be part of a site integration when the equipment, grid requirements and authority model support it. It is validated project by project.
Technical guides