Tiza Group

Home / Guides / Codes and grid connection: US, UK, CA, AU

Grid Code Compliance: ECC and Operational Notification

How a generator proves ECC compliance in GB: the ECP steps, the EON, ION and FON notifications, evidence and model validation, with a worked check example.

By Shadai García, CEO and protection engineer at Tiza Group.

Data, models, energisation planEON: energise the plant networkCommissioning tests, updated modelsION: synchronise, with restrictionsOpen items closed andtests match models?Noclose itemsand retestYesFON: operate without restrictionsNESO and DNO:one evidence fileProcess flowmodel 12.0 Mvar, test 11.2 Mvar: 0.8 Mvar0.8 / 40 = 0.02 pu: below 0.05, passessecond case: test 9.8, error 2.2 Mvar2.2 / 40 = 0.055 pu: above 0.05, failscorrect the model before the FONtest 11.2 Mvar: 0.8 / 40 = 0.020 putest 9.8 Mvar: 2.2 / 40 = 0.055 pu00.020.05assumed tolerance 0.05 puerror in per unit on the 40 MVA module baseillustrative; the tolerance is an assumptionEvidenceDataModelsSimulationsTestsNotification© tizagrp.comData, models, energisation planEON: energise the plant networkCommissioning tests, updated modelsION: synchronise, with restrictionsOpen items closed andtests match models?Noclose itemsand retestYesFON: operate without restrictionsNESO and DNO:one evidence fileProcess flowmodel 12.0 Mvar, test 11.2 Mvar: 0.8 Mvar0.8 / 40 = 0.02 pu: below 0.05, passessecond case: test 9.8, error 2.2 Mvar2.2 / 40 = 0.055 pu: above 0.05, failscorrect the model before the FONtest 11.2 Mvar: 0.8 / 40 = 0.020 putest 9.8 Mvar: 2.2 / 40 = 0.055 pu00.020.05assumed tolerance 0.05 puerror in per unit on the 40 MVA module baseillustrative; the tolerance is an assumptionEvidenceDataModelsSimulationsTestsNotification© tizagrp.com
Grid Code compliance process as a flow chart: data, models and energisation plan, EON, commissioning tests and updated models, ION, the decision on whether open items are closed and tests match the models, with a retest loop, and FON, and a worked check of a 40 MW module where a 0.8 Mvar reactive step error is 0.020 per unit and passes an assumed 0.05 tolerance while 2.2 Mvar is 0.055 and fails. Location in the system and operating principle. Illustrative: real values come from the nameplate and the manufacturer's manual.
Short answer

In GB a plant does not simply connect: it earns permission in steps. The European Compliance Processes (ECP) of the Grid Code lead to an Energisation Operational Notification (EON), an Interim Operational Notification (ION) and a Final Operational Notification (FON). Each step needs evidence: data, validated models, simulations and tests.

Short answer: how a plant proves ECC compliance

A plant that meets the European Connection Conditions (ECC) proves it through the European Compliance Processes (ECP) of the GB Grid Code. The process gives three notifications in order: the Energisation Operational Notification (EON), the Interim Operational Notification (ION) and the Final Operational Notification (FON). Each one is a formal letter that opens the next stage, and each rests on evidence the developer supplies. The base rules are in the Grid Code overview. The current text is Grid Code Issue 6, Revision 46, dated 8 October 2026.

The three notifications

NotificationWhat it permitsWhat the developer shows
EONEnergising the plant’s own network from the gridData, design documents and, where required, simulation models and the energisation plan
IONSynchronising and operating, under any restrictions the notice listsUpdated models, completed commissioning tests and the plan to close open items
FONOperating without those restrictionsEvidence that every item from the ION is closed and the tests match the models

Within the ECP, the EON has its own section, the plant-type processes follow, and the FON closes the sequence. The ION may carry a schedule of unresolved issues, and the FON is issued once they are resolved. The code also has a Limited Operational Notification (LON), used when a plant with a FON or ION loses compliance.

What counts as evidence

Evidence falls into four groups. The Planning Code sets the data, and the ECP sets how it is checked.

  • Data: registered capacity, technical parameters and control settings, kept in line with the Data Registration Code.
  • Models: a model of the plant for system studies. The code requires models that suit the study they feed, and recent revisions add requirements for electromagnetic transient (EMT) models.
  • Simulations: results that show the plant meets reactive capability, fault ride through and, if offered, grid-forming requirements.
  • Tests: commissioning and compliance tests on site, compared against the models.

The order matters. Models that were accepted before construction are compared with test results after commissioning. When the two disagree, the model is corrected, and the plant owner may need to resubmit.

Embedded plants: two layers

A plant on a distribution network answers to two parties. NESO runs the Grid Code process where the code applies to the plant. The distribution network operator (DNO) applies the ENA documents and its own conditions, and asks for its own commissioning forms. The two layers have different forms and timing, so keep a single evidence file and a clear map from each document to each party. See the DNO connection offer guide for the distribution side.

Worked example: does a simulated response match the test?

An illustrative check with assumed values. The tolerance is an assumption for the example, not a code value. Use the tolerance your compliance process states.

A 40 MW power park module is tested for a reactive power step. The model predicted 12.0 Mvar at the grid entry point, and the test recorded 11.2 Mvar.

  1. Error = 12.0 − 11.2 = 0.8 Mvar.
  2. Express it on the module base of 40 MVA: 0.8 ÷ 40 = 0.02 per unit (2 %).
  3. Assumed tolerance: 0.05 per unit. 0.02 is below 0.05, so the model passes this check.
  4. Check the sign and the settling time as well. A small error with the wrong direction of response would still fail the comparison.

Now a second case: the test shows 9.8 Mvar. Error = 2.2 Mvar, or 0.055 per unit. This exceeds the assumed 0.05 per unit, so the model needs correcting before the FON, and the next test should use the corrected data.

Planning the evidence in time

Compliance evidence is cheapest when it is planned with the design. Three habits help:

  • Fix the base values early. Use one per-unit base and one sign convention across models, test plans and reports, so comparisons are direct.
  • Agree the tests before commissioning. Each test needs a procedure, the measurement points and the pass criteria. Settle them with the system operator while the plant is still being built.
  • Keep model versions under control. Record which model version went with which submission, and which firmware version of the inverters it represents. A firmware update after the tests can invalidate the model.

What commonly delays a notification

  • Open items without owners. An ION schedule with items nobody is assigned to stays open. Give each item an owner and a date.
  • Evidence that does not match the registered data. If the data submitted under the Data Registration Code differs from the model or the test, the reviewer stops and asks. Align them before submission.
  • Late test windows. Compliance tests often need the plant at a given output and the system operator’s agreement on timing. Book them early, because weather and network outages move them.

Checklist for the engineer

  • Record the Grid Code issue and revision with the date.
  • Map each ECC clause that applies to the evidence that proves it.
  • Plan the model, data and simulation packages before construction ends.
  • Agree the test list and the witness arrangements with the system operator early.
  • Keep a register of open items so the ION schedule can be closed one by one.
  • Compare model and test results with the same base values and sign convention.
  • Keep one evidence file for NESO and the DNO, with clear versions.
  • Route each document to your chartered engineer for review before submission.

Pre-energisation checks are in commissioning tests for solar plants. The communications and plant controller side is in communications of a solar plant. The UK series starts at the UK codes overview.

From the compliance steps to a package your chartered engineer can sign off

The notifications go faster when the data, models and test plan are consistent from the start. We prepare the engineering design and the power-system studies behind a Grid Code submission, including the evidence list and the study inputs. The package is ready for your chartered engineer to review and sign off before it goes to the network operator. Tiza does not sign or certify designs in the UK. Contact us with the connection offer and the site data.

Frequently asked questions

What are EON, ION and FON?

They are the three operational notifications that a plant receives in the Grid Code compliance process. The EON allows the plant to be energised, the ION allows it to synchronise and operate under any listed restrictions, and the FON confirms that compliance is complete.

What does the ION list contain?

The ION can carry a schedule of outstanding issues that must be closed before the FON, and it may state operating restrictions until they are. The plant owner works through that list with evidence.

Who decides whether the evidence is enough?

NESO, as the system operator, assesses compliance for plants under the Grid Code. For an embedded plant, the distribution network operator also checks its own conditions. Both rely on the documents and test records the developer submits.

WhatsApp