Disclose Transmission Congestion and Curtailment History for GPU Offtake

Consider an illustrative diligence call: a site owner describes an unused interconnect as “available power.” The buyer asks whether summer transmission constraints ever reduced service. The owner shares a dashboard showing high electricity prices—but no utility correspondence explaining whether those events affected physical delivery. The conversation stalls because price exposure and curtailment have been treated as the same thing.

For Supermicro HGX B300-class deployments, that distinction belongs in the initial disclosure, not a footnote after commercial terms. Your job is to document known constraints and evidence gaps, not certify transmission deliverability.

1. Define the path and historical window

Start with the serving utility, point of delivery, and relevant transmission path or constrained interface identified in utility or interconnection documents. Include the applicable pricing node or zone if known. Do not infer the site’s electrical exposure merely because a congested line is nearby.

State the exact historical period reviewed, the sources available, and any missing intervals. Then summarize relevant congestion events:

• Event dates, duration, and seasonal concentration.
• The identified path, interface, or limiting facility.
• Whether the event involved a planned outage, unplanned outage, operating restriction, or another documented condition.
• Whether records show an effect on this site’s service—or only a broader regional constraint.

“No events found in the supplied records” is narrower and more defensible than “no congestion.” If the site has not operated at the proposed load, say so.

2. Separate LMP exposure from physical curtailment

In markets using locational marginal pricing, transmission congestion can affect the congestion component of LMP without interrupting service at the property. Whether that becomes a buyer’s cost exposure depends on the supply contract, tariff, and settlement arrangement.

Physical curtailment is different: the site may be instructed or contractually required to reduce consumption. Disclose applicable interruptible-service provisions, demand-response obligations, emergency procedures, and documented utility-directed reductions.

Economic redispatch also needs careful labeling. Generator redispatch or a regional congestion-management action does not, by itself, establish that site load was curtailed. Identify whose output or consumption changed and whether the action was voluntary, contractual, or mandatory.

Where applicable, report event counts, total hours, duration ranges, notice received, and documented load reductions over the stated period. Separate actual events from notices that never resulted in a reduction. Mark unavailable records as unknown, not zero.

3. Connect known constraints to sustained GPU load

A Supermicro HGX B300-class load discussion should specify the proposed operating profile, not just nameplate interconnect capacity. Distinguish IT demand from total facility demand, including cooling and electrical overhead. Identify assumptions about sustained operation, ramping, seasonal conditions, and maintenance.

Disclose known constraints that could limit sustained MW delivery, including:

• Seasonal transmission ratings or recurring constrained operating windows.
• Contingency-related restrictions identified in applicable studies.
• Temporary service limits pending documented network upgrades.
• Service terms allowing interruption or reduced delivery.
• Planned transmission work that may affect the serving path.

Attribute each constraint to its source and state whether its current applicability is confirmed. Historical congestion is relevant evidence, but neither a clean history nor an unused interconnect guarantees future delivery.

For commercial context, see Pacific Intelligent Technologies, Inc.’s bridge-capacity information and capacity information. Keep those discussions separate from utility confirmation of site-specific service conditions.

4. Build a dated evidence annex

Make the disclosure auditable without requiring buyers to reconstruct every event. Use an annex index with document title, issuer, publication date, covered period, relevant page, and the claim it supports.

Include, where available:

• Utility letters: service restrictions, interruption terms, and explanations of path constraints.
• ISO/RTO dashboards or screenshots: capture date, event date, node or interface, filters, units, and source URL.
• Interconnection study excerpts: limiting facilities, contingencies, operating assumptions, and upgrade dependencies.
• Outage and constraint logs: separate transmission events from site equipment failures; identify documented service effects.
• NERC, ISO/RTO, or utility notices relied upon: explain their geographic and operational relevance rather than presenting a regional warning as proof of site curtailment.

Preserve context around excerpts. A screenshot of a price spike does not prove physical curtailment; a study produced under different load assumptions may not answer today’s question. Flag superseded documents and unresolved requests.

5. Send a bounded disclosure, not a promise

Lead with a one-page summary: records reviewed, relevant events, observed service impacts, known current restrictions, and open questions. Attach the annex and assign an owner to each follow-up.

Ask counsel and a utility consultant to review proposed disclosure language, particularly interruption rights, contractual exposure, and statements about future service. Pacific Intelligent Technologies, Inc. is not acting as the site’s transmission operator, and this disclosure should not suggest otherwise.

Ready to organize your site-owner evidence package? Schedule a 30-minute disclosure discussion. Bring the utility correspondence, relevant study excerpts, and event log—not an unsupported “firm power” claim.

FAQ

Is this the same as interconnection queue status?

No. Queue disclosure addresses process position, studies, and unresolved milestones. This disclosure addresses historical constraints and their relevance to service. Keep the interconnection queue-status disclosure separate.

Can SAIDI and SAIFI replace the event log?

No. Those reliability indices do not establish which transmission constraints affected the site or distinguish pricing events from load reductions. Cross-reference the utility outage and SAIDI/SAIFI disclosure.

Are congestion costs demand charges?

Not inherently. Congestion-related energy exposure and tariff demand charges are different mechanisms. Explain applicable contracts here and link to the demand-charge pass-through disclosure for that separate issue.

Where should an owner start?

Use the site-owner GPU offtake brief to organize the broader package. For company context, visit Pacific Intelligent Technologies, Inc..