EnergizeOSMicrogrid EMS
System Architecture

Intelligence above the gate.
Determinism below it.

System Architecture

Layered architecture

EnergizeOS Microgrid EMS is organized as a strict layered system. Intelligence flows downward as recommendations; only the deterministic EMS core issues commands to equipment.

L5
User Interface
Operators, asset owners, engineers — web HMI, reports, chat copilot
L4
LLM Orchestration Layer
Intent understanding, status explanation, report generation, tool coordination
L3
Energy Domain AI Layer
Dispatch recommendation, revenue optimization, forecasting, degradation & anomaly analytics
Safety Gate · Operator Approval · Audit Log
L2
EMS Core — Deterministic Control
Real-time control, PCS commands, interlocks, protection interfaces, fail-safe behavior
L1
Device & Data Integration Layer
Modbus TCP, DNP3, IEC 61850 — PCS, BMS, relays, meters, breakers, SCADA
L0
Physical Assets
BESS, PCS, transformers, switchgear, protection relays, site loads

Layer responsibilities

LLM Orchestration Layer

The LLM layer is responsible for understanding user intent, explaining system status, generating reports, coordinating analytical tools, recommending strategies, and helping operators understand alarms, revenue gaps, dispatch results, and operational risk. It is a reasoning and communication layer — not a control layer.

Energy Domain AI Layer

Domain-specific optimization and analytics: dispatch recommendation, revenue optimization, load and price forecast usage, battery degradation analysis, anomaly detection, fault explanation, operational risk scoring, and microgrid scenario analysis. Outputs are structured recommendations with confidence and constraints — never direct device commands.

EMS Core (Deterministic)

Real-time control, PCS command execution, BMS coordination, relay and meter interfaces, Modbus/SCADA communication, protection logic interfaces, interlock logic, safe operating limits, manual override, emergency stop, and fail-safe behavior. All control paths are deterministic, testable, and auditable.

Device & Data Integration Layer

Protocol adapters (Modbus TCP, DNP3, IEC 61850), device register maps, time-series ingestion, and the site data model that feeds both control and analytics.

Non-negotiable design rules

  • The LLM is never in a real-time control loop and never writes Modbus commands to equipment.
  • EMS control remains fully deterministic; AI provides intelligence, recommendation, explanation, and optimization.
  • Safety gates are mandatory before execution. Deterministic interlocks and limits always override AI suggestions.
  • Protection devices (relays) act independently of the EMS: trip paths are relay-led, hardwired, and fast.
  • Every recommendation and every command is written to an audit log.
Trip vs. Close — the asymmetry that defines the system. Trip is relay-led, hardwired, fast, and EMS-independent. Operational close is EMS-led, slow, interlocked, logged, and user-authorized. AI may inform the close decision; it can never bypass the permissive chain.