Dynamic Congestion Manager for Loads (DCMl)

Overview

Dynamic Contingency Manager for Datacenters/Loads (DCML) is Splight’s real-time grid protection solution that safeguards the transmission system by disconnecting critical datacenter loads during thermal contingencies. When a monitored transmission line or transformer experiences a breaker trip or overload condition, DCML immediately triggers a fast disconnection command to selected datacenters—causing them to switch to backup power and relieve stress on the grid.

This approach enables grid operators to operate closer to true physical capacity while still maintaining safety and reliability. DCML is designed for hyperscalers, colocation providers, and infrastructure operators participating in contingency support programs or grid reliability services.

---

Required Inputs

DCML depends on high-quality real-time telemetry to detect contingencies and execute fast, auditable disconnection commands. Input signals are streamed through Splight connectors using supported protocols.

Real-Time Input Attributes

For Each Datacenter (or big load):

Attribute	Description	Required?	Frequency	Protocol
power_draw	Real-time power consumption	Yes	At least every 5 seconds	MQTT, Modbus, DNP3, IEC81850
breaker_status	Internal breaker state (optional)	Optional	On change	MQTT, Modbus, DNP3, IEC81850
grid_connection_status	Whether the datacenter is grid-connected or on backup	Yes	At least every 5 seconds	MQTT, Modbus, DNP3, IEC81850

For Each Transmission Line:

Attribute	Description	Required?	Frequency	Protocol
active_power_start	Active power flow at the start node of the line (in MW)	Yes	At least every 1 second	MQTT, Modbus, DNP3
active_power_end	Active power flow at the end node of the line (in MW)	Yes	At least every 1 second	MQTT, Modbus, DNP3
breaker_status	Line breaker status: open or closed	Yes	On change	MQTT, Modbus, DNP3
current_r_start	Phase R current at the start node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
current_r_end	Phase R current at the end node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
current_s_start	Phase S current at the start node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
current_s_end	Phase S current at the end node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
current_t_start	Phase T current at the start node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
current_t_end	Phase T current at the end node (RMS, in A)	Yes	At least every 1 second	MQTT, Modbus, DNP3
frequency	System frequency measured at either start or end of the line (in Hz)	Yes	At least every 1 second	MQTT, Modbus, DNP3
reactive_power_start	Reactive power flow at the start node of the line (in MVAR)	Yes	At least every 1 second	MQTT, Modbus, DNP3
reactive_power_end	Reactive power flow at the end node of the line (in MVAR)	Yes	At least every 1 second	MQTT, Modbus, DNP3
switch_status_start	Disconnector or switch status at the start node (open/closed)	Yes	On change	MQTT, Modbus, DNP3
switch_status_end	Disconnector or switch status at the end node (open/closed)	Yes	On change	MQTT, Modbus, DNP3
voltage_start	Line-to-neutral voltage at the start node (RMS, in kV)	Yes	At least every 1 second	MQTT, Modbus, DNP3
voltage_end	Line-to-neutral voltage at the end node (RMS, in kV)	Yes	At least every 1 second	MQTT, Modbus, DNP3

Metadata Requirements

For each Generator:

Metadata	Description	Required?	Example
max_capacity	Generator nameplate capacity	Yes	100 MW

For the Grid:

Metadata	Description	Required?	Example
maximum_allowed_diconnection	Provided by the electrical study performed by Splight	Yes	303MW

Note: Telemetry must have timestamps aligned to UTC ±30s. Poor quality input may block control actions and disable contingency response.

---

Features

DCML includes a fixed set of analytics and visualizations designed to give visibility into contingency readiness and actual response behavior.

Metric	Description	Unit
Datacenter Power Draw (Real-Time)	Current load per datacenter	MW
Historical Power Draw	Time-series of datacenter consumption	MW over time
Line Loading	Current and historical loading of monitored lines	% or MW
Total Grid Offload via DCML	Sum of load shed through DCM actions	MW
Disconnection Matrix	Real-time contingency map: which datacenters will disconnect under which failures	Boolean matrix

---

Control Capabilities

DCML issues disconnection commands to participating datacenters when a contingency is detected. These are enforced via connector-based setpoints or breaker interface.

Control Logic Summary

• System continuously monitors breaker line loadings and statuses

• If a contingency is detected, the Disconnection Matrix determines which datacenters must switch to backup

• Command is sent to disconnect from grid immediately

Commands Issued

Command	Trigger	Action
disconnect	Triggered via asset control attribute	Breaks physical tie to grid

Timing and Safety

• Total response time: < 500 ms from event detection to command dispatch

• Each control action is logged with timestamp and associated contingency

• Disconnections are only sent when DCML detects a real contingency event

Deployment Notes

• DCML requires a pre-modeled Equivalent Grid using Splight's SLD tooling, based on prior engineering studies

• Each datacenter and transmission line must be onboarded as an asset with complete metadata and real-time input streams

• Only Splight-controlled connectors can issue control commands (self-hosted nodes must meet latency guarantees)

---

Support

Need help validating inputs, testing control logic, or scaling up? Contact your Implementation Manager or email [email protected].

---

Watch this video walkthrough

Video comming soon

---