Data center system impact study: the SIS clock that binds

A queue row says someone asked for megawatts. A system impact study says what that request does to the grid — and on what clock. For data-center interconnection, Watt Brief reads an RTO, ISO, or transmission provider SIS (or cluster study result) the same way it reads any other public-record delta: identity first, then the modeled outcome and the restudy or decision deadline that binds. A campus deck that claims “feasibility” is not a row. A posted study with a document ID is.

Four fields before you change the site plan

Open the interconnection portal or study posting. Pull these before you change a site-selection plan or a restudy deposit:

• Document ID — the queue position, study case number, or tracking ID the operator printed. That is the identity key with source and event class. We do not invent one because a slide said “SIS complete.”
• Study report — the public SIS results PDF, cluster study appendix, or staff memo that attaches modeled load, contingencies, and upgrade flags. The report is where the clock lives.
• Constrained MW — not IT nameplate. The useful numbers are studied MW, thermal or voltage constraints, required network upgrades, and whether the result is unrestricted, conditional, or withdrawal-forcing. If the packet bounds MW, we keep the bound. If it only says “hyperscale load,” we do not invent a fake campus MW.
• Clock dates — study start, results posted, customer decision due, restudy kickoff, or withdrawal. An open study without a results date is not the same row as a published SIS with a decision clock.

Why the SIS binds before campus PR

Campus marketing moves when the developer wants a headline. A system impact study moves when the operator posts modeled impacts — or when a decision/restudy clock forces an answer. For colo and hyperscale site-selection BD, utility large-load teams, and infra PE, the binding fact is not that someone announced interconnection progress. It is that a named document ID entered or left the SIS phase with a dated status.

A restudy trigger is not soft feedback. It is a public clock: accept upgrades, restudy, withdraw, or miss the window. Watt Brief treats a new SIS result or restudy notice on a known document ID as a delta. A restated “still in study” headline on the same ID is not.

What counts as an SIS delta

• New SIS or cluster study assignment with a document ID and studied MW.
• Results PDF posted with constraints, upgrades, or unrestricted findings.
• Customer decision deadline issued or missed.
• Restudy kicked off or completed on the same identity.
• MW, POI, or configuration amendment that revises the study table.
• Withdrawal or termination after SIS results.

None of that is a trade-magazine feature. It is a pointer to the study PDF and queue record you can open. If the same document ID later gets a restudy or a revised constraint table, that is a new delta on the same identity — not a duplicate with a restated lede.

What we skip

We skip generic “interconnection on track” press kits that do not attach a study ID or results PDF. We skip restated headlines about the same document ID. We skip empty mornings. We skip inventing a queue position because a broker shared a screenshot without a public ID.

An SIS row is not proof the campus will energize. Results recondition. Customers withdraw. Later facilities studies and interconnection agreements still bind. It is also not a substitute for the facilities study, the IA or LGIA, ERCOT Batch Zero verification, a TSR, a water or air permit, a county CUP, or a PUC large-load tariff case — those are separate identities when the sources are separate.

Open the study URL. Match the document ID. If the data-center load is not on that SIS packet, the row is not for you yet.