Systems and records
Energy interconnection workflow data as long-horizon document tasks
By SourceX Editorial · Reviewed by Noah Loul ·
9 sections
Short answer
Represent each interconnection application as a dated sequence of states, from request through studies and agreement to operation or withdrawal, where every change is triggered by a document and judged under the tariff version, deadlines and asset facts in force that day. The model's task is to name the permissible next step on a stated date, with evidence, while engineering content stays screened out.
Agent run
Energy interconnection
Key takeaways
- Model each application as dated states triggered by documents, judged under the rules in force on that date.
- Store the governing procedure version and every accepted asset version; later facts must never leak into earlier labels.
- Check readiness thresholds on the deadline date, not the date someone reviewed the file.
- Screen every file for CEII, landowner data and confidentiality before it is referenced in a case.
- Let models propose administrative next steps and deadlines; keep engineering decisions with engineers.
How do you represent an interconnection application as a long-horizon document task?
Represent each application as a dated sequence of states, from request through studies and agreement to operation or withdrawal, where every state change is triggered by a specific document and judged under the tariff version, deadlines and asset facts in force on that date. The task given to a model is then precise: given the file as it stood on a stated date, name the permissible next step, what is due and by when, and the evidence that supports it.
That framing turns a sprawling project folder into something checkable. A request form, a deficiency notice, a study report, a restudy, a deposit receipt, a site control document and an agreement each become an event with a date, a source and a consequence. The decision at each point can be compared with what the transmission provider or utility actually did next.
The framing also exposes why these files are hard for AI. The relevant facts are spread across many documents, the rules change partway through, and the right next step depends on dates that are easy to misread. Those are exactly the properties that make long-horizon document tasks useful for training and evaluation.
Why does an interconnection file change under the applicant for years?
Interconnection files change because the process itself is long, staged and revised while projects wait. Berkeley Lab's Queued Up 2026 edition reports that the median project built in 2025 took over five years from interconnection request to commercial operation in the regions with available data, and it tracks requests as active, operational or withdrawn among other statuses.
The rules moved during that time as well. FERC's explainer on Order No. 2023 describes the shift from serial first-come, first-served studies to cluster studies, a 150-day cluster study followed by a facilities study before an agreement, a requirement to show 90 percent site control at request and 100 percent when the facilities study agreement is executed, commercial readiness deposits, and withdrawal penalties when a withdrawal materially affects other requests. A later FERC order on an ISO New England compliance filing accepted a 270-day cluster study timeline, a reminder that each transmission provider's own tariff sets the operative dates.
Smaller projects follow a different track. FERC Order No. 2006 set Small Generator Interconnection Procedures for generators no larger than 20 MW, with a Study Process, a Fast Track Process for certified facilities no larger than 2 MW, and a 10 kW Inverter Process. Distribution-level interconnections are typically governed by state rules and utility tariffs, with IEEE 1547-2018 as the technical standard for interconnecting distributed energy resources.
Which dated facts decide what an applicant may do next?
Four kinds of dated fact decide the next step: the tariff or procedure version that governs the request, the deadlines and deposits attached to the current study phase, the project's asset facts as last accepted by the transmission provider, and the safety and confidentiality boundary around engineering information. A record that lacks any of them cannot support a label.
Tariff version is the one most often lost. A request submitted before a transmission provider's Order No. 2023 compliance filing took effect may sit under transition rules; FERC's ISO New England order notes customers had to meet new readiness requirements within 60 days of the compliance filing's effective date. The schema stores the governing procedure by name, version and effective date, not as a single label for the provider.
Asset facts are the second trap. Capacity, technology, point of interconnection and expected in-service date are often revised, and each revision may trigger a material modification review or restudy. Keep every accepted version with its acceptance date so a model sees the facts that applied when a decision was made, not the latest ones.
The safety boundary is fixed, not dated. Protection settings, switching steps and commissioning procedures belong to engineers and are outside the task.
The rights screened application state and decision schema
The schema below has one row per entity, with the fields a utility, transmission provider or developer would need to reconstruct a decision and the validator check that makes the record trustworthy. Each document reference points to a file that has passed the rights and confidentiality screen described later; nothing in the schema stores the engineering content itself.
| Entity | Key fields | Purpose | Validator check |
|---|---|---|---|
| Application | application_id, applicant_token, request_date, process_track, queue_or_cluster_id | Anchors the case and its track (large, small, fast track, distribution) | process_track is one of the tracks defined in the governing procedure |
| Governing procedure | procedure_name, version, effective_from, transition_rule_ref | States which rules apply on each date | Every state event falls inside a version's effective dates |
| Asset version | version_no, capacity_mw, technology, poi_ref, expected_cod, accepted_on | Keeps each accepted change to the project | Versions are ordered; no state event uses a version accepted after it |
| Readiness evidence | site_control_pct, evidence_date, deposit_type, deposit_posted_on, security_form | Shows whether readiness thresholds were met on time | Thresholds compared on the deadline date, not the review date |
| Study | study_type, cluster_id, start_date, due_date, issued_date, revision_of | Records each study and restudy with its own dates | A restudy references the study it revises |
| Deficiency or notice | notice_type, issued_on, cure_deadline, cured_on | Captures the clocks that can end an application | cured_on is not later than cure_deadline unless the outcome is withdrawal |
| Agreement | agreement_type, tendered_on, executed_on, milestone_list_ref | Marks the move from study to construction obligations | executed_on follows the facilities study or a recorded waiver |
| State event | event_id, from_state, to_state, event_date, trigger_doc_ref, actor_role | The trajectory a model is evaluated on | Every transition is in the allowed-transition table |
| Decision label | as_of_date, permissible_next_steps, due_items, label_author, second_review | The answer key for each as-of point | Two reviewers agree or the disagreement is recorded |
| Rights screen | doc_ref, ceii_status, personal_data_status, confidentiality_terms, cleared_by | Proves each referenced file may be used | No referenced file has an uncleared status |
Which transitions are allowed from each application state?
Write the allowed transitions down before labelling any case. The states below follow the broad shape of large-generator procedures after Order No. 2023; a team should replace them with the states in its own transmission provider's or utility's procedure and keep the version in the governing procedure entity.
Grading follows from the table. For each as-of date, a model's answer is correct when every next step it proposes is permissible from the recorded state, it names each due item with the right deadline, and it cites the document that triggered the current state. An answer that proposes a step the table blocks, or that misses a cure deadline already running, fails regardless of how well it reads. Score withdrawals separately: they are frequent and terminal, and a model that predicts them well has learned something different from one that sequences studies correctly.
| State | Entered when | Permissible next states | Blocked by |
|---|---|---|---|
| Request submitted | Request form, deposit and site control evidence received | Validated, deficient, withdrawn | Missing readiness evidence at the stated threshold |
| Deficient | Deficiency notice issued with a cure period | Validated, withdrawn | Cure deadline passes without cure |
| In cluster study | Cluster window closes and study starts | Restudy, facilities study, withdrawn | Readiness deposit not posted for the phase |
| Restudy | A withdrawal or change requires re-evaluation | Facilities study, withdrawn | Asset change exceeds what the procedure allows without a new request |
| Facilities study | Facilities study agreement executed with full site control | Agreement tendered, withdrawn | Site control below the required share at execution |
| Agreement executed | Interconnection agreement signed | Construction milestones, suspended, terminated | Milestone or security obligations missed |
| Operational or withdrawn | Commercial operation declared, or withdrawal recorded | None; terminal | Not applicable |
What valid and invalid example records demonstrate the structure?
Both records below are illustrative and describe no real project or utility. They show what the validator should accept and what it should reject.
- Valid record, as of the day after a cluster window closes: a battery storage request under the provider's post-compliance procedure, asset version 1 accepted at request, site control evidence dated before the request at the required share, deposit posted on the request date, state in cluster study, permissible next steps listed as await study results or withdraw, due item listed as the next readiness deposit with its date. Every referenced file shows a cleared rights screen.
- Invalid record, rejected for three reasons: the decision label uses asset version 2, accepted 4 months after the as-of date; the readiness check compares site control on the date the reviewer looked rather than on the deadline; and the study entity attaches a one-line diagram whose CEII status is unscreened.
- What the invalid record would teach if it slipped through: that later facts were known earlier, that readiness can be judged after the fact, and that engineering drawings are ordinary attachments. Each is a lesson a model should never learn.
- Fix: re-label using asset version 1, recompute readiness on the deadline date, and replace the diagram reference with a text description cleared by the security lead, or drop the study attachment.
What must be screened out before an interconnection file can be shared?
Screen every file for three things before it enters a case: critical infrastructure information, personal and landowner data, and contractual confidentiality. Interconnection folders mix all three with ordinary correspondence, so the screen runs on files, not on whole folders.
FERC's CEII program covers specific engineering, vulnerability or detailed design information about proposed or existing critical infrastructure, and excludes simply giving the general location of the infrastructure. Study models, one-line diagrams and protection details can fall inside it; FERC also notes narrative descriptions are generally public unless they carry specific engineering detail. The security or CIP lead should decide, case by case, with the default being exclusion.
Not everything is sensitive. Many transmission providers publish queue lists, and the open-source gridstatus library standardizes their columns into fields such as queue ID, project name, interconnecting entity, county, state, interconnection location, transmission owner, generation type, capacity, queue date, status, proposed completion date and withdrawal date, with statuses grouped as active, withdrawn or completed. Public fields like these make a sound spine for each case; the private files around them need the screen.
Ownership is a separate question from sensitivity. A developer's own applications, a utility's notices and a consultant's studies may each carry different rights, and land agreements carry personal data about landowners. Counsel confirms who may license each class of file.
Where should a model's role in interconnection work stop?
A model trained on these cases should propose administrative next steps, deadlines and missing evidence, and stop there. It should not produce or alter protection settings, switching or clearance steps, study assumptions or anything an engineer must stamp.
Stop or narrow the case set when any of the following appears:
- The governing procedure version for a date cannot be established from the file.
- A study or restudy result is cited but the report itself is withheld, so the label cannot be checked.
- Engineering content would be needed to explain the decision, such as a network upgrade justified by a power flow result.
- The applicant's commercial terms or financial security details are bound by confidentiality clauses that have not been cleared.
- The case involves a dispute, complaint or regulatory proceeding still open.
- Technical compliance with IEEE 1547 or a utility's interconnection requirements is the actual question; that remains engineering work.
Where SourceX fits for an interconnection archive
Developers, independent power producers, utilities and consultancies that keep years of interconnection correspondence hold the long, dated, document-heavy histories this schema describes. Whether a given archive can be licensed turns on the rights and confidentiality screen above and on review by counsel and the security lead.
Project developers, consultants and utilities holding interconnection files can license selected records to AI teams through SourceX, which covers sourcing, rights review, contracting, preparation, delivery and payment. Eligibility is checked through a short assessment with no data upload, the company approves scope and signs before delivering anything, and multi-terabyte sets can stay in the company's own storage or travel on encrypted drives.
Frequently asked questions
What is energy interconnection workflow data?
It is the dated record of an interconnection request as it moves through validation, studies, agreements and construction to operation or withdrawal, with the documents, deadlines and decisions at each step. Structured well, it supports AI tasks that ask what the next permissible step is on a given date.
Why are interconnection applications long-horizon tasks?
They run for years, involve many documents and parties, and change rules partway through. Berkeley Lab reports the median project built in 2025 took over five years from request to commercial operation where data was available, so a single decision depends on facts scattered across a long timeline.
Can public queue data be used for AI training?
Published queue lists are a useful spine, with fields such as queue ID, status, capacity and dates. They do not contain the documents and decisions that make a task checkable, and each publisher's terms of use should still be checked.
Is an interconnection study report CEII?
Parts may be. FERC's CEII program covers specific engineering, vulnerability or detailed design information about critical infrastructure, and study models and diagrams can qualify. The security or CIP lead should screen each file, and general location alone does not qualify.
Does Order No. 2023 apply to small or distribution projects?
Order No. 2023 reformed large generator interconnection procedures. Generators no larger than 20 MW follow small generator procedures from Order No. 2006 and later revisions, and distribution interconnections are usually governed by state rules and utility tariffs.
Sources
- FERC's Order No. 2023 explainer describes cluster studies, a 150-day cluster study followed by a facilities study, 90 percent and 100 percent site control thresholds, commercial readiness deposits and withdrawal penalties. Source
- A FERC order on ISO New England's Order No. 2023 compliance filing accepted a 270-day cluster study timeline and notes readiness requirements apply within 60 days of the compliance filing's effective date. Source
- FERC Order No. 2006 set small generator interconnection procedures for generators no larger than 20 MW, with Study, Fast Track (up to 2 MW) and 10 kW Inverter processes. Source
- Berkeley Lab's Queued Up 2026 edition reports a median of over five years from interconnection request to commercial operation for projects built in 2025, in regions with data. Source
- The gridstatus library standardizes interconnection queue columns, including queue ID, status, capacity, queue date and withdrawal date, with statuses active, withdrawn and completed. Source
- FERC's CEII program covers specific engineering, vulnerability or detailed design information about critical infrastructure, not simply its general location. Source
- IEEE 1547-2018 is the IEEE standard for interconnection and interoperability of distributed energy resources with associated electric power systems interfaces. Source
See if your company qualifies
A short company assessment. No data uploads are needed.