NVIDIA DSX Flex Architecture
The public DSX™ Flex event model establishes how grid-facing power requirements enter an AI factory, how participating systems report operating state and exceptions, and which decisions remain local. These boundaries help NCPs plan the factory-side response and give integrators the context needed before implementation-specific configuration and validation.
What the Flex Schema Standardizes
The DSX Flex schema provides the shared event model that independently implemented systems use to exchange power intent and reported outcomes through DSX Exchange. It standardizes participant roles and publisher responsibilities, versioned event types, topic and payload structures, lifecycle states, correlation fields, and message-security requirements.
The schema does not prescribe how targets are validated, how local schedules are implemented, where telemetry originates, which workload or site controls respond, or how advisory infrastructure actions are evaluated. Those decisions remain with each participating solution and the deployment’s operating policy.
Read the Generated Reference and Source Together
The operation, message, and schema pages are generated from the same AsyncAPI definition. Start with an operation page to identify the MQTT topic, publishing and subscribing roles, and message type. Then follow the message to its payload schema for required fields, allowed values, and referenced objects.
Some nested objects and arrays appear as references instead of being fully
expanded in the generated page. If the page does not show an object’s complete
structure, open the
Raw AsyncAPI Spec.
A $ref entry points to another named definition in the same specification;
follow its path into components.schemas. For an array, items either defines
each entry directly or points to its definition with another $ref. The
versioned AsyncAPI source
contains the same contract.
How Flex Participants Relate
The DSX Flex schema assigns event responsibilities to three logical participant roles:
source attribute and corresponding Flex
topic paths. See the
source format
in the authoritative schema.The factory-side roles connect power management and infrastructure orchestration to Flex. A power-management implementation participates as the DSX Flex Agent, receiving load targets and publishing operating-state reports. The Infrastructure Management Agent role is intended to connect your infrastructure orchestration to Flex. DSX software does not currently provide an implementation of this role or publish the schema’s breach-alert and enforcement events.
How Flex Uses DSX Exchange
The Grid ISV, DSX Flex Agent, and Infrastructure Management Agent use the same Flex power-management event contract. Exchange carries their events between authorized publishers and subscribers. Flex defines the event meaning; Exchange provides the transport for the target, state, and exception paths.
This figure follows a Grid ISV’s power requirement through Exchange to an illustrative GPU-power response managed by DSX MaxLPS DPS (Dynamic Power Software). It includes operating-state and exception reports returned to the Grid ISV. The sequences below trace the target/status and breach/enforcement interactions among the participating roles.
In this GPU-power example, workloads keep their existing scheduler while DPS adjusts power limits. Facility measurements can inform the response through their own Exchange integrations. The Flex overview provides the wider workload, facility, and site-energy context; those systems are not shown as additional control targets here. For the GPU control model, see DPS documentation.
Each participant connects to NVIDIA DSX Exchange as an MQTT client. Publishers
send events to topics, the Exchange broker routes them, and authorized
subscribers receive them. Each event is a structured CloudEvent encoded as
JSON. The topic identifies the operation and publisher, the CloudEvent metadata
identifies the event and its source, and the signed data field contains the
event-specific payload.
data field with
JWS,
which the receiving participant verifies for payload integrity and authenticity.
Connection authorization does not replace payload verification.Flex exchanges are asynchronous. A load target communicates intent rather than producing a synchronous operating result. The DSX Flex Agent reports changing state through a continuing stream of full power-state snapshots, published when state changes and at periodic reporting points. Subscribers may therefore receive status updates that do not correspond to a target they published. Correlation identifiers can relate events within an interaction, but they do not make the status stream a command response.
Exchange transports these events; participating systems maintain the state and make the decisions described by them. For the Flex integration described here, the Grid ISV connects through the configured gateway to an Exchange broker in the Common Services Cluster (CSC). Exchange handles routing between this shared-services boundary and factory-side systems.
How Load Targets Become Reported Power State
A Load Target Set specifies one or more requested power constraints and when they apply. A target can cover selected feeds or all feeds. When the DSX Flex Agent receives a target, it updates its schedule and reports the update in a later Power State Status event. Factory-side power management uses local control logic to determine how the managed loads respond.
Flex scopes targets and reported state by feed. A feed_tag is a
deployment-defined identifier for a managed power scope. It can correspond to
an electrical feed, a data hall, or another site-defined boundary, but the
schema does not prescribe that mapping. The NCP and participating systems must
use a consistent mapping; when feed_tags is omitted or empty, the target
applies to all feeds.
A Power State Status event is a full snapshot of the reported state for all feeds. It includes active and scheduled targets, calculated load, transition state, and target compliance. When no target is active, status reports operation against the feed’s default constraint.
Mapping Grid Commitments to Flex Exchanges
A grid-facing integration may need to support different kinds of power-response commitments. A request to reduce demand carries expectations about advance notice, how long each response must last, and expected use over the year. The following EPRI Flex MOSAIC classes illustrate these differences.
Scroll to compare all three dimensions →
| Response class | How much notice?Notification window | How long per activation?Activation duration | How much use over the year?Annual utilization |
|---|---|---|---|
| ACritical peaking | ≥1 hour | ≤5 hours | ≤1% |
| BPeaking | ≤10% | ||
| CFast | ≥5 minutes | ||
| DProlonged | Instantaneous | ≤96 hours | |
| EFully grid responsive | Unbounded | Unbounded |
Two grid requests can call for the same power limit over the same interval while carrying different expectations for use over the year. The Grid ISV accounts for the applicable program rules and commitments when determining which targets to publish and how to relate the reported response to that commitment.
Flex provides common target, operating-state, and exception exchanges that the ISV can use within that integration. Program-specific decisions and records remain outside the schema. The following example follows one scheduled activation, from target publication through the factory’s reported restoration.
Example: Observe a Scheduled Load Reduction
In this example, a Grid ISV publishes a scheduled load reduction. The DSX Flex Agent reports when it has updated the schedule, when the transition begins, the current state during operation, and when the transition ends. Each arrow represents an event publication routed through Exchange. The event names match the feed example below, from schedule registration through restoration.
Scroll horizontally to inspect the complete ladder.
After receiving the target, the agent publishes target_set to report that it
updated the schedule; this value does not mean that the requested operating
state was achieved. start_ramp_down and end_ramp_down mark publications at
the beginning and end of the reported transition. The in_flight field
indicates whether the agent is actively moving between power levels, while a
periodic event reports current state without asserting a new transition.
These fields do not prescribe the internal control method.
Because every Power State Status event is a full snapshot, subscribers evaluate the active and scheduled targets, calculated load, transition state, and compliance together.
This example uses illustrative values and timings for DPS-reported snapshots
on feed main-a: a calculated load initially near 860 kW and a 500 kW target
scheduled for 14:00–15:00 UTC. The curve connects the snapshots’
calculated_load values, which can differ from measured power during
transitions. Select a snapshot to compare its reported state with the target.
- Calculated load
- 860 kW
- Flex target
- 500 kW · scheduled
- Transition
- Not in progress
- Target compliance
- No active target
target_set: The agent has registered the 500 kW target for 14:00–15:00 UTC. The load has not moved. This snapshot confirms the schedule, not achievement of the target.
Target Compliance Is Not Grid-Program Compliance
Power State Status reflects the state known to factory-side power management
for the loads it manages. A compliant value means that the calculated load is
within the active Flex target; it is not a complete utility or grid-program
compliance record. External metering, site operations, reconciliation, and
program reporting remain outside the Flex event model.
How the Schema Represents Breach and Enforcement
The published schema defines an exception lifecycle for a factory that cannot maintain an active target. It defines the meaning of the events without requiring every deployment to implement breach detection or infrastructure enforcement.
A Power Breach Alert reports the power exception. One breach can progress
through active, optional escalated, and resolved states under the same
breach identifier. The event identifies the affected target and feed, reports
the power condition, and can include ordered shed hints.
Shed hints are advisory. An Infrastructure Management Agent uses its own
topology and operating criteria to decide how to respond. A Power Breach
Enforcement event separately reports whether infrastructure actions were
applied or reverted and whether the overall outcome was success,
partial, or error.
Example: Report and Respond to a Breach
During an active target interval, factory-side power management reports that it cannot maintain the target. This example follows the breach reports and infrastructure response. Each arrow represents an event publication routed through Exchange. Select a stage to explore the reports; the full sequence remains visible.
Scroll horizontally to inspect the complete ladder.
The Flex Agent reports the power condition through alerts. The Infrastructure Management Agent separately reports its actions and their outcomes. Select a stage to follow what each report establishes.
Breach state and enforcement outcome answer different questions: the Power Breach Alert reports whether the power condition is active, escalated, or resolved, while Power Breach Enforcement reports what the Infrastructure Management Agent did in response. An enforcement outcome alone does not establish that the breach was resolved.
Next Steps
- Plan the factory-side response. NCPs and AI factory operators can review the NVIDIA DSX MaxLPS overview and DPS documentation.
- Integrate grid services. Grid services integrators looking to connect
their solution to DSX Flex can follow the
Grid Services Integration Guide to implement
the
isvrole, from connection setup and signed load-target commands through status interpretation and basic integration checks. - Review the Flex schema. Grid-facing integrators can use the DSX Flex schema to identify the Grid ISV operations, topics, messages, payload fields, delivery requirements, and security fields.