Professional Check
Five connection tests, one capacity-envelope calculation and a hard check on public register claims.
- Five focused lessons
- 10 scored questions
- Answer rationales after submission
Read a GB BESS connection as a set of rights, works, milestones and operating limits. Then test whether the project can energise and dispatch as claimed.
This course focuses on the evidence between a register row and an operable grid connection under the reformed GB process.
Five connection tests, one capacity-envelope calculation and a hard check on public register claims.
From connection architecture and Gate status through works, milestones, operational limits, constraints and a complete readiness case.
Scores and progress remain on this device. No account or sign-up is required.
Read the agreement, works, land and milestones together before treating a connection date as deliverable.
Identify transmission or distribution, voltage, connection point, import and export rights and the party responsible for each asset.
A BESS can be directly connected, embedded or co-located. The network boundary determines the agreement, works, charges, metering and operating relationship.
Record maximum import and export capacity separately. The lower direction can constrain cycling and service recovery.
A single MW headline can conceal asymmetric rights and shared-capacity limits.
Gate 2 indicates that a project meets readiness and strategic-alignment requirements for a confirmed connection position under the reformed process.
Gate 1 is a non-firm early-stage position. Gate 2 can provide a confirmed date, point and queue position, subject to the agreement and delivery chain.
Register fields can be blank or under correction while offers are issued and countersigned. Preserve the register date.
Gate 2 strengthens contractual status. It does not prove that land, planning, finance, equipment and network works are complete.
A target date depends on customer works, network works, outages, consents, milestones and agreement conditions.
Build a critical path with responsible party and evidence for each dependency. Check whether the date is contractual, indicative, backstop or conditional.
Long-lead transformers, switchgear, protection studies and network reinforcement can control energisation.
Repeating a date from a register without its conditions creates false schedule certainty.
A right to connect does not guarantee that network capacity is unconstrained in every hour.
Operational limits can include non-firm arrangements, active network management, intertripping, outage restrictions and export caps. Constraint risk affects revenue, charging and service delivery.
Quantify curtailment or unavailability using contract terms and relevant network evidence rather than a regional average alone.
A firm name in a presentation can be inconsistent with operational clauses in the actual agreement.
Use the connection agreement and network correspondence for rights, then use registers as dated public summaries.
Registers are valuable for market-wide comparison, while they can contain duplicated stages, technology aggregation or transitional fields. Join them with planning, land and company evidence.
Label the project contracted, Gate 1, Gate 2, under construction, energised or operational only when the relevant evidence supports that stage.
A register row proves a recorded contract status at a date. It does not prove physical progress.
Answer every question before submitting. Correct answers and rationales appear only after the complete attempt.
Map contractual status, physical works, operational rights and constraint exposure to the evidence available at the technical cut-off.
Trace the BESS from batteries and PCS through transformer, switchgear, connection point and network ownership boundary.
Map import and export meters, auxiliary supplies, shared assets and co-located generation. Identify which entity holds the connection agreement and which entity owns each interface asset.
Carry voltage, capacity and fault-level requirements into equipment specifications and schedule.
A project can own a site and equipment while another entity controls the critical connection right.
The agreement allocates works, costs, securities, milestones, liabilities and termination rights.
Extract connection point, capacities, date, network reinforcements, user works, charges, securities and conditions precedent. Record variation and cancellation rights.
Test whether budget and schedule include every customer obligation and interface assumption.
A low quoted connection charge can exclude substantial customer works and land rights.
The reformed process prioritises projects that are ready and strategically aligned.
For Gate 2, inspect the readiness evidence, land position and strategic criterion used. Confirm countersignature and any protection category. For Gate 1, avoid assigning a confirmed connection date.
Track the current offer-issuance timetable and data-correction notices at the extraction date.
A blank Gate field can reflect timing or data correction. Treating blank as Gate 2 is unsupported.
Connection delivery is a multi-party project with technical, property, consenting and outage dependencies.
Link design approvals, procurement, civil works, protection, communications, commissioning and energisation. Add network outage windows and dependencies on upstream reinforcement.
Use evidence-backed dates and schedule contingency. Reconcile changes through the agreement variation process.
A single delayed upstream asset can invalidate a detailed customer construction schedule.
BESS economics depend on both directions, shared capacity and continuous or short-term ratings.
Model gross and net limits at the relevant meter. Include auxiliary load, transformer losses and co-located generation. Test the recharge time implied by the import right.
Caister needs 180 MWh of grid import before losses. A 60 MW import right requires at least three hours, with actual time longer after losses and tapering.
Using export MW as the charging limit can overstate cycling frequency and service recovery.
Operational access can be conditional even when the connection is energised.
Identify active network management, intertrip, export limitation, outage, restoration and dispatch instructions. Establish compensation rights and notification standards.
Model historical constraint evidence only when it matches the same node, regime and future network configuration.
A historical low-curtailment period before new connections is weak evidence for the future queue.
Constraint exposure changes available hours, energy recovery, service performance and imbalance risk.
Build scenarios for planned outages, forced unavailability and active curtailment. Separate lost gross revenue, avoided charging cost and possible compensation.
Test correlations with high-price periods and network stress. A simple annual percentage can miss concentrated value loss.
Five percent curtailed hours can remove more than five percent of value when they occur in the most valuable periods.
Public connection registers are dated summaries with known transitional limitations.
Preserve source file, change date and row identifiers. Resolve duplicates across stages, phases and technology types. Reconcile project names with planning and company records.
Use the register to state recorded status. Use separate evidence for construction, energisation and operation.
Removing apparent duplicates without a documented rule can erase legitimate project phases.
The case turns a 100 MW headline into a conditional operating envelope.
Caister has a countersigned Gate 2 offer for 100 MW export and 60 MW import with a target date in 2028. Customer works include a 132 kV transformer and protection scheme. Upstream reinforcement and a planned outage remain network dependencies.
The 180 MWh AC delivery target requires more than 180 MWh charge energy. At 90 percent round-trip efficiency and 60 MW import, simplified recharge time is 3.33 hours. The project is contracted with a conditional delivery path, and the operating model must use asymmetric limits.
Calling Caister a ready-to-build 100 MW two-hour project omits the import constraint and unresolved network dependencies.
Answer every question before submitting. Correct answers and rationales appear only after the complete attempt.