EnergizeOSMicrogrid EMS
Use Case

C&I microgrid,
SDG&E territory.

Reference Deployment

C&I microgrid — Southern California

The first EnergizeOS Microgrid EMS deployment supports a behind-the-meter BESS program at a Fortune 500 manufacturing facility in the SDG&E service territory, delivered with an EPC engineering partner and a BESS integrator, under CA Rule 21 and IEEE 1547-2018 interconnection requirements.

This page is the public-facing description. Commercial terms, protection settings, single-line diagrams, and project-specific procedures are maintained in the internal project workspace and are not published here.

Scope covered by the EMS

AreaEMS role
BESS integrationPCS dispatch, BMS status supervision, rack-level health visibility, SOC and power limit enforcement.
Site load supportPeak shaving and demand management against the facility load profile and tariff structure.
Utility / grid interactionInterconnection-compliant operation under CA Rule 21 / IEEE 1547-2018; coordinated behavior at the point of common coupling.
Export-limited operationZero-export / export-limited control enforced deterministically from revenue-grade meter feedback.
Relay & meter integrationSEL-700G-class protection relay status and permissive interfaces; SEL-735-class revenue metering with CT/PT validation.
PCS / BMS / EMS coordinationDeterministic command path EMS → PCS, with BMS permissives in the interlock chain before any close or dispatch.
Remote monitoringSecure remote visibility of states, alarms, events, and energy flows for owner, EPC, and integrator.
Commissioning supportFAT/SAT-aligned test procedures, trip-lockout verification, interlock chain validation, witness-test support.
Operator reportingDaily and monthly performance, savings, and availability reports generated from audited operational data.
Alarm explanationPlain-language alarm context: what fired, why, criticality, and recommended response.
Dispatch planningDay-ahead plans built from tariff, load forecast, and SOC constraints — reviewed through safety gates before execution.

What this deployment taught the product

  • Interconnection success depends on an auditable evidence chain — every protection setting, test result, and approval must be traceable. The EMS data model treats evidence as a first-class object.
  • Close authority must be singular and interlocked: one permissive chain, one authorized close path, full logging.
  • Multi-party programs (owner, EPC, integrator, utility) need shared, explainable operational truth — which is exactly what the AI layer provides on top of deterministic records.