{"resourceId":"nvidia-dsx-flex-exchange-overview-2026","versions":[{"version":"external-9f522938491b1278b32fa6ff6c4eb4c3f9488cc66de6cc6356fe4f9bc6abbb57","resource":{"id":"nvidia-dsx-flex-exchange-overview-2026","title":"DSX Flex Exchange: loadtarget commands, breach alerts, and best-effort shedding semantics","organization":"NVIDIA","sector":"AI factory grid-flexibility control plane","geography":"Global (DSX Flex schema/docs)","publishedAt":"undated DSX Exchange docs (live Sep 22, 2026 retrieval)","publicationDate":null,"eventDate":"2026-09-22","sourceName":"NVIDIA DSX Exchange Documentation","sourceLabel":"Vendor interface specification","sourceUrl":"https://docs.nvidia.com/dsx-exchange/schema/dsx-flex/overview","evidenceClass":"standards-guidance","outcomeClass":"emerging","topics":["infrastructure","operating-model","data-security"],"finding":"DSX Flex Exchange docs define a CloudEvents-over-MQTT control plane for real-time power management. Key event types include grid.loadtarget.set.v1 (ISV fire-and-forget load target), grid.powerstate.status.v1, grid.powerbreach.alert.v1, and grid.powerbreach.enforcement.v1. Companion schemas describe load constraints in W/kW/MW with optional UTC intervals, and a strategy.best_effort flag where the Flex Agent sheds non-disruptively via DPM-enabled jobs and may leave the feed non-compliant if the target cannot be met. Shed hints are described as non-binding; enforcement outcomes include applied/failed/skipped.","sledRelevance":"Clarifies that DSX Flex is a signaling/enforcement API with best-effort modes—not a guarantee of utility-grade compliance—so SLED sites must map schema semantics to interconnect contract terms.","evidence":"MQTT CloudEvents binding; event types loadtarget.set / powerstate.status / powerbreach.alert / powerbreach.enforcement; load targets in watt|kilowatt|megawatt; interval start/end UTC; strategy.best_effort non-disruptive DPM shed with possible non-compliance; shed hints non-binding; enforcement codes applied|failed|skipped.","architectureImplications":"Integrators must implement signed event handling, correlation IDs, and explicit policy when best_effort cannot meet targets—including escalation to infra enforcement.","governanceImplications":"Contract language should state whether best_effort non-compliance is acceptable or whether hard enforcement/breaker backstops apply.","securityPrivacyImplications":"JWS-signed payloads and trace context are specified; operational security depends on MQTT authz and key management not fully detailed on the overview page.","caveats":"Interface spec without measured field compliance rates; schemas page complements overview; not a utility tariff.","streamIds":["nvidia"],"roles":{"sales":"Use the Flex Exchange overview to demystify DSX Flex for utility and facilities buyers: it is a loadtarget and breach event API with best-effort shedding, not automatic interconnect approval. Sell integration and contract-mapping work that decides what happens when best_effort fails, including escalation to infra enforcement or utility backstops.","engineering":"Fit for sites implementing Emerald or ISV agents against DSX Flex. Architecture is MQTT CloudEvents among ISV, Flex Agent, and Infra Agent roles with correlation IDs. Prerequisites: broker security, signed payloads, and DPM-enabled job classes. Proof of value: inject loadtarget.set and observe the status, breach, and enforcement chain end to end.","delivery":"Work is control-plane integration plus failure-mode runbooks owned by facilities OT and platform power-agent owners. Acceptance: event round-trip proven, best_effort non-compliance path documented, and enforcement codes monitored. Risks include treating best_effort as firm capacity and weak MQTT authorization or key custody."},"roleDetails":{"sales":{"customerProblem":"Buyers hear Flex marketing without knowing command/enforcement semantics.","stakeholders":["facilities OT","utility liaison","security","AI platform"],"discoveryQuestions":["Is best_effort acceptable under your interconnect?","Who runs the Infra Agent?","What is the breach escalation path?"],"valueHypothesis":"Clear event semantics reduce false promises about firm curtailment.","potentialEngagement":"Schema-to-contract mapping workshop for one feed.","unsupportedClaims":["Best_effort equals firm MW","MQTT API replaces utility breaker","Guaranteed compliance"]},"engineering":{"fit":"Sites wiring ISV/Flex/Infra agents to DSX Flex.","architectureIntegration":"CloudEvents on MQTT with loadtarget and breach flows.","prerequisites":["MQTT security","JWS keys","DPM-enabled jobs","correlation-id logging"],"constraints":["best_effort may end non-compliant","shed hints non-binding"],"security":"Harden broker authz and payload signing keys.","proofOfValue":["loadtarget round-trip","breach alert observed","enforcement code captured"]},"delivery":{"work":"Implement agents; test failure modes; document escalation.","dependencies":["NVIDIA schemas","ISV/Emerald","OT network"],"ownership":"Facilities OT with platform power-agent owner.","skillsAdoption":"Ops need event literacy and curtailment drills.","governanceCheckpoints":["Contract vs best_effort aligned","Key custody defined","Monitoring on enforcement codes"],"acceptanceCriteria":["Event chain works","Non-compliance path documented","Alerts pageable"],"risks":["Silent non-compliance","Unsigned events","No infra backstop"]}},"retrievedAt":"2026-09-23T03:13:00Z","enrichedAt":"2026-09-23T03:21:35Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"None claimed.","procurementImplications":"Buy Flex integration as a control-plane project with security scope, not a checkbox license.","operatingModelImplications":"Operate to event SLOs (ack/enforcement latency) alongside IT SLOs.","sourceVerification":{"openedUrl":"https://docs.nvidia.com/dsx-exchange/schema/dsx-flex/overview","referenceExcerpt":"grid.loadtarget.set.v1 — ISV sets load target (fire-and-forget command)","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}