Grid compliance testing
Proving to the network operator that the site responds the way the network requires - before it is allowed to trade.
Last updated 2026-09-06
What is Grid compliance testing?
Grid compliance testing is where the site demonstrates to the network operator that it behaves as the connection requires. It is not a check that the plant works; that was functional commissioning. It is a demonstration, to a third party, on their terms, that the site responds correctly to the conditions and instructions the network will present to it. Until it is complete and accepted, the site generally cannot trade, whatever else has been achieved. It is the last major external dependency in the project and, like the connection compound, it runs on somebody else's programme.
What is tested, how, in what sequence, and what constitutes acceptance are all defined by the network operator and set out in the project's connection arrangements. None of that is described here and none of it should be assumed from another project. What is general is the shape of the exercise: tests are planned and submitted in advance, they are carried out with the network operator involved or witnessing, they are evidenced with recorded data, and the results are submitted and formally accepted. It is a documentary exercise as much as a technical one, and projects usually lose more time to submissions and reviews than to the testing itself.
The practical lesson from projects that have done this is to prepare for it far earlier than feels necessary. The site's control system has to be capable of doing what the tests will ask of it, which is a design requirement rather than something to discover during testing. The people, the instrumentation and the data recording have to be arranged in advance. Slots with the network operator have to be booked and are not easily moved. And a failed test is not simply repeated: it is investigated, corrected, resubmitted and rescheduled, which on a busy operator's programme can cost far more time than the test would have taken. Getting it right first time is worth a great deal of preparation.
How does Grid compliance testing work, step by step?
- 1
Step 1: Establish the requirements at design stage
What the network operator will require the site to demonstrate is established when the plant and control system are being designed, not when testing approaches. The control system has to be specified from the outset to be capable of the behaviour that will be tested and of recording it. Discovering a capability gap during compliance testing is one of the more expensive positions a battery project can find itself in.
- 2
Step 2: Plan the tests and submit the plan
A test plan is prepared setting out what will be demonstrated, how, in what order, and what data will be recorded, and it is submitted to the network operator for acceptance in advance. The review takes time and may generate comments that change the plan. That review period is allowed for in the programme rather than absorbed by it.
- 3
Step 3: Book the window with the network operator
Testing requires the network operator's involvement and their availability, and windows are booked well in advance. They are difficult to move and difficult to recover if missed. The date is treated as a fixed project milestone and everything else is arranged around it, in the same way as the connection date itself.
- 4
Step 4: Prepare the site, the people and the instrumentation
Before the window opens the plant is available and stable, the instrumentation and data recording are in place and proved, and the people who will conduct and witness the tests are identified and present. Data recording in particular is checked beforehand, because a test that is performed correctly but not properly recorded has to be performed again.
- 5
Step 5: Carry out the tests as planned
Tests are conducted in accordance with the accepted plan, with the network operator involved or witnessing as their requirements specify. Deviations from the plan are agreed rather than improvised. The specific procedures, settings and acceptance criteria belong to the network operator's requirements for the project and are followed as issued.
- 6
Step 6: Record and review the results as they are produced
Results are recorded and reviewed during the testing period rather than afterwards, so that a problem is identified while the window is still open and the people are still on site. A result reviewed a week later is a result that will be dealt with in a new window, on a new date, with everyone remobilised.
- 7
Step 7: Submit the results and obtain acceptance
The evidence is compiled and submitted to the network operator, who reviews it and formally accepts it or comes back with comments. This review period is a real duration in the programme. Projects consistently underestimate it and consistently assume that testing complete means compliance accepted, which it is not.
- 8
Step 8: Deal with failures through the formal route
A failed test is investigated with the designer and the equipment supplier, corrected, and then replanned, resubmitted and rescheduled. There is no shortcut and no informal repeat. Because the cost of failure is measured in weeks of programme rather than hours of testing, the preparation that avoids it is almost always worth more than it costs.
What are the benefits of Grid compliance testing?
- Formally establishes that the site may operate on the network
- Provides independent evidence that the plant behaves as the connection requires
- Exposes control system shortcomings before the asset is relied upon commercially
- Produces a recorded baseline of site behaviour for the operator
- Gives the network operator confidence in the asset from the start
- Completes the last major external dependency in the project
What are the limitations of Grid compliance testing?
- Runs entirely on the network operator's programme and availability
- Test windows are booked well ahead and are hard to move or recover
- Submission and review periods are real durations that are routinely underestimated
- A failed test costs weeks, not hours, because it must be replanned and rescheduled
- Requires control system capability that must be designed in from the outset
- Until acceptance is granted, the asset generally cannot trade
What is Grid compliance testing best suited for?
What plant does Grid compliance testing need?
- Instrumentation and data recording equipment proved before the test window
- Control system monitoring and diagnostic equipment
- Communications arrangements between the site and the network operator
- Site plant available and stable for the duration of the window
- Document management arrangements for compiling and submitting evidence
- Competent people identified and present for the whole window
How is Grid compliance testing quality-checked?
- Control system capability confirmed against the requirements at design stage
- Test plan submitted to and accepted by the network operator before testing
- Test window booked and treated as a fixed project milestone
- Data recording proved before the window opens, not during it
- Results reviewed while the window is still open and the team is still on site
- Formal acceptance obtained and recorded before the asset is considered compliant