Grid code compliance & model validation studies

A compliance study is the evidence an operator needs to accept a connection: ride-through, current injection, voltage and frequency response and stability, all backed by validated models.

Compliance matrixIllustrative
Every clause, checked in every governing scenario.

When you need it.

  1. A new or modified connection has to prove compliance to the operator.
  2. A connection offer or modification application needs supporting studies.
  3. Compliance has to be shown again after equipment or settings change.
  4. The operator wants evidence of model quality alongside performance results.

How we run it.

  1. 01

    Clauses

    Pin down exactly which clauses and code versions apply.

  2. 02

    Plan

    Plan the studies: ride-through, current, voltage, frequency, stability.

  3. 03

    Model

    Build and validate the models, then run every required case.

  4. 04

    Collate

    Pass or fail for each clause, with the governing scenarios.

  5. 05

    Submit

    Put the pack together in the format the operator expects.

What we use and what we test.

Tools

  • PSCAD / EMTDCEMT clauses
  • PowerFactory · PSS®ERMS clauses
  • AutomationRepeatable runs

Scenarios we run

  • Fault, voltage and frequency envelopes set by the code
  • Minimum and maximum grid strength, and credible outages
  • Dispatch from minimum stable to full output
  • Any model-quality criteria the operator sets

What you get.

  • ReportCompliance report, clause by clause
  • ModelValidated models and a model quality statement
  • EvidenceCases, settings and assumptions for the operator's review
  • PackA document set ready to submit

How we check it

The pack follows the code itself, so a reviewer can trace each requirement to its evidence. Assumptions, tool versions and model sources are recorded. Submission steps differ by operator and project.

Questions engineers ask.

Which grid code do you work to?
We work to the connecting operator's code and version. For GB connections that is the relevant national framework. We confirm the exact clauses in scope at the start of every study.
Do you guarantee the operator will accept the connection?
No one can promise an acceptance outcome. We prepare rigorous, well-documented evidence aligned to the code so the submission can be reviewed cleanly; acceptance rests with the operator.
Can you combine EMT and RMS evidence?
Yes. Different clauses are best demonstrated in different domains; a complete package typically uses RMS for breadth and EMT for the fast-dynamic requirements.