Integrated lithium battery energy storage solutions

EMS Interface|Dispatch coordination

Coordinate upper-level dispatch and field devices within clear authority and state boundaries

Customer EMS / station control integration — schedule targets become device commands with states, alarms, metering, permissions and loss-of-comm fallback.

  • Reliable commands ACK · timeout · reject codes
  • True states Quality · time · SOE
  • Clear boundaries Mode · role · clamp
  • Controllable loss Autonomy · safe return

Four interface coordination capabilities

What EMS / station-control integration must prove — not an EMS product feature page Demo data

  • Clear authority definition Who may command, override or freeze
  • Point list & data model map Canonical tags · units · quality
  • Command & state closed loop REQ → ACK → measured feedback
  • Loss autonomy & SIT/SAT evidence Predictable fallback with proof

Layered responsibility table · bidirectional control tree

Who owns each layer — and how commands descend while feedback ascends Demo data

Layered RACI

LayerPrimary dutyProtocolOwner
Operations dispatchSchedule / targetNorthboundOwner ops
Station controlMode / interlockEMS IFSystem
System EMSTranslate / arbitrateICDIntegrator
PCS / BMSExecute / clampField busVendors
MeteringM&V valuesModbusEPC
Aux controlHVAC / fire IFRTUMEP
SurveillanceAlarm / SOEHistorianO&M

Bidirectional control tree

↓

  1. Dispatch target P / Q window
  2. EMS translate Constraints
  3. PCS / BMS Execute

↑

  1. Measured P/Q Feedback
  2. State / alarm SOE
  3. Quality / time PTP
  • Command down
  • Feedback up
  • Authority
  • Safety

Command translation

Upper targets must be translated into device-executable commands

Seven steps from schedule window to confirmed receipt — with SEQ / timeout / idempotency demo Demo data

  1. Dispatch target P window demo
  2. Validate constraints SOP · mode · role
  3. Allocate limits Per PCS share
  4. Issue to PCS Setpoint write
  5. Diagnose response ACK / reject
  6. Settle / verify Measured vs target
  7. Confirm receipt Close SEQ

SEQ-016 · timeout 2 s · idempotent key DEMO-EMS-7 · last ACK PASS

Unified point list & data model · protocol coverage overview

Machine-readable dictionary with coverage and type / quality / time legends Demo data · 89% coverage

Unified point list (excerpt)

IDCanonicalCustomer tagType / unitR/WPeriodQualityTime
P001PCS.P_setSITE.PCS01.Pfloat kWWOn chgGOODPTP
P014BMS.SOCSITE.BESS.SOCfloat %R1 sGOODPTP
A003PCS.FaultSITE.PCS01.FLTboolREventGOODSOE
M010Meter.kWh_impSITE.MTR.IMPfloat kWhR15 mGOODNTP
C002EMS.ModeSITE.MODEenumWOn chgGOODPTP

Protocol coverage

89% Mapped vs required (demo)
  • Read 612
  • Write 98
  • Event 132
  • Analog 54%
  • Digital 28%
  • Enum / cmd 18%
  • Type = engineering unit locked
  • Quality = GOOD / BAD / OLD
  • Time = PTP preferred · NTP fallback

Operating mode authority matrix · command handshake mechanism

Who may operate in each mode — and the seven-step handshake with reject codes Demo data

Mode & authority matrix

ModeEMS cmdLocal autoManualEmergency
REMOTEFullInhibitInhibitOverride
LOCAL AUTOLimitedFullInhibitOverride
MANUALInhibitInhibitFullOverride
EMERGENCYInhibitInhibitInhibitFull

Command handshake — seven steps

  1. REQ Command request
  2. AUTH Role / mode gate
  3. VALID Range / SOP
  4. EXEC Device write
  5. ACK Device ACK
  6. MEASURE Feedback sample
  7. CLOSE Measured ACK
  • Idempotent command keys
  • Timeout → safe reject
  • Reject codes logged to EMS
  • Evidence retained for SIT/SAT

Power schedule & limit arbitration

Day plan curves · strictest-wins rules · live KPI example Demo data

Day plan (multi-series · HTML spark)

Schedule · clamp · measured overlay

Constraints & arbitration (strictest wins)

  • Min(EMS target, BMS SOP, PCS map, thermal floor)
  • Mode gate before write
  • Rate limit per ICD
  • Reject if quality BAD / OLD
  • Issue to PCS only after VALID

Live example KPI

  • Target P 1.10 MW
  • Issued P 1.05 MW
  • Measured P 1.04 MW
  • Clamp reason SOP demo

Loss-of-comm autonomy

Predictable autonomy and controlled return when the EMS link is lost

Safe, predictable behavior — avoid power cliffs and restart thrash Demo data

  1. Heartbeat lost Detect
  2. Data stale Quality OLD
  3. Time sync lost PTP / NTP
  4. Command anomaly Reject flood
  5. Gateway fault Path fail
  6. Local policy Hold / isolate
  7. Alarm record SOE
  8. Align Resync
  9. Return to run Gated

Goal: safety · predictability · no abrupt power drop · no frequent restart

States · time quality · roles · metering validation

Four equal cards that deepen the coordination surface Demo data

State / alarm / event model

  • Severity taxonomy
  • Cause + action hint
  • Flood suppression
  • Historian export

Time sync & data quality

  • PTP preferred
  • NTP fallback
  • Quality bits
  • SOE skew ≤ 100 ms demo

Roles & security permissions

  • Operator · engineer
  • Command gates
  • Session log
  • VLAN / TLS northbound

Metering & M&V checks

  • Import / export kWh
  • Demand window
  • Cross-check PCS
  • Evidence pack

Every command confirmed · every state traceable

Close the EMS interface with a proven command loop and an evidence chain for SIT / SAT — not a public download wall. Demo data · ICD-EMS-2608-121-C

  • Authority frozen before wiring
  • Ambiguous maps rejected
  • Reject codes retained
  • Fallback timed & logged
  • SAT gated on evidence

SIT / SAT test stages (evidence chain)

  • Point-to-point Tag map QA
  • Command loop REQ→ACK
  • Schedule arbitration Clamp cases
  • Loss-of-comm Fallback drill
  • Time / quality PTP / SOE
  • Role gates Permission matrix

Issued artifacts

  • ICD release
  • Point list CSV
  • Alarm dictionary
  • SIT script pack
  • SAT checklist