Overview

What this is

Grid Connection Assurance (gridcon) — Track a generator's grid-connection assurance end to end — connection projects and their requirements, the submissions and technical reviews that satisfy them, dependencies between requirements, evidence, connection risks and the exceptions that block progress. It is built from one component of the Renewable Generation Orchestration reference pack.

The domain, in one paragraph

A ConnectionProject (region, connection point, technology, capacity, target dates) carries ConnectionRequirements across categories (GPS, model, SCADA, metering, protection, registration…), each with an owner/reviewer, due date and materiality. Dependencies order requirements (blocks/requires/informs). Each requirement is satisfied through Submissions (versioned, supersedable) that go through TechnicalReviews (accepted / accepted-with-conditions / rework / rejected), backed by EvidenceItems. ConnectionRisks (likelihood × consequence → rating) and ConnectionExceptions capture what threatens the connection.

The 8 models

Projects & Requirements

ConnectionProject · ConnectionRequirement · Dependency

Submissions & Review

Submission · TechnicalReview · EvidenceItem

Risk & Exceptions

ConnectionRisk · ConnectionException

The demo scenario

The Northgate Solar Farm connection NBSF-CONN (transmission, solar, 180 MW, in assessment). The GPS requirement REQ-GPS is accepted (acceptance letter evidence); it blocks the model-validation requirement REQ-MODEL, which is under review: submission SUB-MODEL-01 was superseded by SUB-MODEL-02, whose technical review TR-MODEL-02 came back accepted-with-conditions (re-fit ride-through). That opens risk RSK-MODEL (likelihood 3 × consequence 4 = 12) and exception EXC-MODEL (rework required).

10 rows across all 8 models.