Tiza Group

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

EirGrid Compliance Testing and Model Validation

How EirGrid Grid Code tests and model validation work: notice periods, EON, ION and FON, model types, and how to compare site test data with the model.

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

Written test requestat least 15 Business DaysReconfirm the test time3 Business Days beforeGrid Code Testdispatch and measurementsCompare model withtest measurementsFinal OperationalNotification (FON)validRevised model, 90Business DaysinvalidresendProcess flowdates of the worked example (illustrative)36 MW set-point test, five pointsmean error 0.40 MW = 1.1 % of 36 MWlargest error 0.8 MW = 2.2 % at 100 ms22 Jun 2027: test notice due (15 Business Days)8 Jul 2027: reconfirm the test time13 Jul 2027 (Tuesday): ride-through test16 Jul 2027 (Friday): tests end23 Nov 2027: revised model due (90 Business Days)MWms1002003004005000102030-0.8measuredsimulatedProofRequestTestCompareModelFON© tizagrp.comWritten test requestat least 15 Business DaysReconfirm the test time3 Business Days beforeGrid Code Testdispatch and measurementsCompare model withtest measurementsFinal OperationalNotification (FON)validRevised model, 90Business DaysinvalidresendProcess flowdates of the worked example (illustrative)36 MW set-point test, five pointsmean error 0.40 MW = 1.1 % of 36 MWlargest error 0.8 MW = 2.2 % at 100 ms22 Jun 2027: test notice due (15 Business Days)8 Jul 2027: reconfirm the test time13 Jul 2027 (Tuesday): ride-through test16 Jul 2027 (Friday): tests end23 Nov 2027: revised model due (90 Business Days)MWms1002003004005000102030-0.8measuredsimulatedProofRequestTestCompareModelFON© tizagrp.com
Flow chart of the EirGrid compliance process: written test request with at least 15 Business Days of notice, reconfirmation 3 Business Days before, the Grid Code Test with dispatch and measurements, comparison of the model with the test measurements, a revised model within 90 Business Days if it does not match, and the Final Operational Notification; with the dates of the worked example (22 June, 8 July, 13 July, 16 July and 23 November 2027) and the measured against simulated active power at five points after fault clearing, with a mean absolute error of 0.40 MW. Location in the system and operating principle. Illustrative: real values come from the nameplate and the manufacturer's manual.
Short answer

Under the EirGrid Grid Code (Version 18) a generator proves compliance through Grid Code Tests during commissioning and through validated dynamic models. Tests that need dispatch require at least 15 Business Days notice, models must be validated against test measurements, and a revised model is due within 90 Business Days of the end of the tests if the first one does not match. The result of the process is the final operational notification.

Short answer: EirGrid compliance testing and model validation

EirGrid compliance testing and model validation are the two proofs a generator gives before it is allowed to operate under the EirGrid Grid Code (Version 18, issued 27 October 2026). Compliance is shown by Grid Code Tests during commissioning, under clause CC.15, and by dynamic models that match the measured behaviour of the plant, under appendix PC.A8. A plant that completes the process receives a Final Operational Notification (FON). A plant that cannot meet a requirement applies for a derogation under GC.9.

The overview of the document is in the EirGrid Grid Code guide. The requirements being tested are in the wind and solar requirements guide, the ride-through guide and the frequency response guide. The regional context is in the Ireland and New Zealand guide.

The testing process in CC.15

The user and EirGrid meet to discuss commissioning, including commissioning tests and Grid Code Tests, in line with the connection agreement. The main rules are:

  • Purpose. Grid Code Tests confirm that the plant meets all requirements that must be met before the Operational Date. EirGrid notifies the tests it requires under the connection agreement. Passing a test does not reduce the user’s own responsibility to comply at all times.
  • Notice. The user tells EirGrid as soon as possible if commissioning needs dispatch for test purposes. It gives not less than 15 Business Days of notice of the test time and reconfirms it not less than 3 Business Days before.
  • Request. Each test that needs dispatch is requested in writing, with the details of the test, the dispatches and duration, preferred times and the milestones for any sections that can be completed separately.
  • Verification. Before the Operational Date the user verifies the technical data given under the Planning Code, with the results of the relevant tests. The verified values are entered in the registered data.
  • Notifications. The generator completes the Energisation (EON), Interim (ION) and Final (FON) Operational Notifications in sequence. An ION lasts no longer than 24 months. If a requirement cannot be met, a Limited Operational Notification (LON), valid up to 12 months, covers the gap while the issue is resolved.

EirGrid also publishes testing pages for power park modules and for system services, and an information note on the operational notification procedure. Use the current versions from the EirGrid site, since their contents are updated separately from the Grid Code.

The models in PC.A8

EirGrid designs and runs the system on the models that users supply, so PC.A8 is detailed:

  • Model types. A balanced, positive-sequence, root mean square time-domain model, and where specified a three-phase electromagnetic transient model, with harmonic studies where EirGrid asks for them.
  • Content. The RMS model includes every material element that affects the active and reactive power of the plant against voltage and frequency changes at the connection point.
  • Aggregation. Models of individual generating units can be aggregated into fewer models of the same site, and the plant is represented as a single lumped model scalable with output at the connection point. A representation of the collector network and extra reactive compensation can be included.
  • Documentation. Enough information to redevelop the model, such as the structure, functionality and Laplace block diagrams. Source code may be provided, or an unambiguous reference to a standard open-source model or to a model already submitted. Models come in a software format specified by EirGrid.
  • Confidentiality. A third-party manufacturer can submit the model if it agrees to the standard confidentiality agreement for users.

Validation and maintenance

Clause PC.A8.6 requires every model to be validated. EirGrid must be satisfied that the behaviour in simulation is representative of the real equipment. The user performs tests and takes measurements, and compares the model output with Grid Code test measurements. The test list may include steady-state reactive capability, voltage control and reactive power stability, low-voltage ride through, high-voltage ride through, and low and high frequency response. After commissioning the user provides a comparison of the predicted behaviour with the tested performance. If the model is not valid, a revised model, source code and documentation are due within 90 Business Days after the tests conclude.

Clause PC.A8.7 keeps the duty alive after commissioning. The user informs EirGrid of changes that materially affect accuracy, including changes to protection settings, controller settings, governor droop or frequency response, and resubmits the model or its parameters. EirGrid also runs its own ongoing validation.

Worked example: dates and a model comparison

The figures are illustrative. The Glossary defines a Business Day as Monday to Friday, excluding public holidays and holidays observed by the TSO. The dates skip the 2027 public holidays of 2 August and 25 October.

  1. A ride-through test is planned for Tuesday 13 July 2027. Fifteen Business Days before is 22 June 2027, so the notice goes in by then. The three-day reconfirmation falls on 8 July 2027.
  2. The tests end on Friday 16 July 2027. Ninety Business Days later is 23 November 2027, which is the last day for a revised model if the first one does not match.
  3. Comparison after a 36 MW set-point test, with active power measured and simulated at five points after fault clearing:
Time after clearing (ms)Measured (MW)Simulated (MW)Error (MW)
10018.017.2-0.8
20027.527.9+0.4
30031.031.4+0.4
40032.632.9+0.3
50033.033.1+0.1

The mean absolute error is (0.8 + 0.4 + 0.4 + 0.3 + 0.1) ÷ 5 = 0.40 MW, which is 1.1 % of the 36 MW set-point. The largest error is 0.8 MW, or 2.2 % of the set-point, at the first point. The code sets no numeric tolerance here, since the tests and measurements are agreed with EirGrid. Treat these percentages as an internal screening measure and agree the acceptance basis in writing before the test.

How this compares with other regimes

The GB process is in the ECC compliance guide and the G99 commissioning guide. Australia’s equivalent is in the GPS hold-point testing guide and the AEMO model requirements guide. Process names differ between countries, so use the Irish terms in Irish submissions.

Checklist for the engineer

  • Agree the test list and the acceptance basis with EirGrid before the commissioning programme is fixed.
  • Plan the 15 Business Day notice and the 3 Business Day reconfirmation for each dispatch test.
  • Prepare the written request for each test that needs dispatch, with milestones.
  • Build the RMS model, and the electromagnetic transient model where specified, as a single scalable model.
  • Prepare model documentation and the software format EirGrid specifies.
  • Record test measurements in a form that allows direct comparison with the model output.
  • Reserve time and resources for a revised model within 90 Business Days.
  • Keep the test plan and report ready for your chartered engineer to review and sign.

From test plan to a review your engineer can sign

A test programme and a model fail mainly on assumptions that nobody reviewed. Tiza prepares the studies and model packages for generation projects: test plans against the clauses, model structure and documentation, and the comparison of model and test records. Tiza does not stamp, sign or certify. The package is delivered ready for your chartered engineer, registered with Engineers Ireland, to review and sign. Contact us with the plan and the model documents.

Frequently asked questions

How much notice does EirGrid need for a commissioning test?

Clause CC.15.3 asks for reasonable advance notice, being not less than 15 Business Days, of commissioning tests, and the date must be reconfirmed not less than 3 Business Days before the tests. Tests that need dispatch also need a formal written request.

What models must a plant supply?

Appendix PC.A8 requires a balanced positive-sequence root mean square time-domain model and, where specified, a three-phase electromagnetic transient model, with documentation. The models must be validated, and the EirGrid text allows an agreed reference to a standard open-source model.

What happens if the model does not match the test results?

Clause PC.A8.6 requires the user to provide a revised model, source code and documentation that match the observed behaviour as soon as reasonably practicable, and in any case within 90 Business Days after the Grid Code compliance tests conclude.

WhatsApp