Grid compliance, performance and reliability testing
Proving the plant behaves as the network requires, meets its guaranteed output and efficiency, and runs reliably before takeover.
Last updated 2026-09-07
What is Grid compliance, performance and reliability testing?
The last phase of a power project is proving three separate things. First, that the plant behaves as the electricity network requires it to - responding as expected, staying connected when the network is disturbed and providing what the network operator has been told it will provide. Second, that it produces the output and achieves the efficiency the contract guarantees. Third, that it can run continuously and reliably rather than merely achieving a good number once. Each is tested formally, each has agreed acceptance criteria, and together they are what allows the plant to be taken over.
Compliance testing is run with the network operator, whose requirements the plant must meet before it is allowed to operate commercially. The tests are defined by the network operator, witnessed by them or reported to them, and the plant cannot be released to full commercial operation until they are satisfied. Programming them is genuinely difficult, because they need the network to be in a suitable state and the network operator to be available, and neither is under the project's control. Slots are booked well in advance and missing one can cost weeks.
Performance testing is a contractual event. Output and efficiency are measured under agreed conditions, with agreed instrumentation, agreed corrections back to reference conditions and agreed calculation methods, all settled long beforehand because there is real money attached to the result. Reliability testing then requires the plant to run for an agreed continuous period within agreed limits, demonstrating that it holds together in service. Only when all three are complete and accepted does the plant pass to the operator, with any outstanding items carried on an agreed list into the defects period.
How does Grid compliance, performance and reliability testing work, step by step?
- 1
Step 1: Agree the test regime long before testing starts
The test programme, the conditions, the instrumentation, the measurement methods, the corrections and the acceptance criteria are all agreed between the operator, the plant supplier and the contractor well in advance, and the network operator's requirements are established alongside them. Agreeing this early is essential, because a dispute about method after a test has been run is expensive and hard to resolve. The agreed regime is documented and becomes the reference for everything that follows.
- 2
Step 2: Book the network operator's involvement early
Compliance testing needs the network operator to be available and the network to be in a suitable state, and their programme does not flex to suit the project. Test slots are requested well in advance, the required submissions are made on their timescale, and the project programme is built around the dates that come back. Most delays at this stage are caused by underestimating this lead time. Contingency is built in because a missed slot may not recur quickly.
- 3
Step 3: Install and prove the test instrumentation
Performance testing is only as good as the measurement, so the test instrumentation is installed, calibrated and proved in advance, with calibration certificates traceable and accepted by all parties. Locations, installation details and uncertainties are agreed as part of the test regime. Where permanent plant instrumentation is to be used, its calibration is confirmed and accepted. Nothing about the measurement arrangement is settled on the day of the test.
- 4
Step 4: Carry out network compliance testing
The plant is demonstrated to behave as the network operator requires: responding to network conditions, adjusting output as instructed, riding through disturbances and providing the capabilities that were declared. Tests are executed by the commissioning team and the operator to the network operator's defined programme, with results recorded and submitted as required. All of it is done under the operator's permit and safety regime. Settings and acceptance values belong to the network operator and are applied by the operator alone.
- 5
Step 5: Run the performance test under agreed conditions
The performance test is run when the plant is stable and the ambient and operating conditions fall within the agreed window. Readings are taken over the agreed duration with all parties present, then corrected back to reference conditions and evaluated against the guarantees using the agreed method. The result is documented and issued. Because the outcome carries commercial consequences, the discipline around who observes, who records and who calculates is set out beforehand and followed exactly.
- 6
Step 6: Complete the reliability run
The plant then runs continuously for an agreed period within agreed operating limits, demonstrating that it holds together in normal service. Interruptions are assessed against pre-agreed rules about what counts as a failure and what restarts the clock. This is often the most frustrating part of a project, because a small auxiliary fault can end a run that was nearly complete. Teams prepare by making sure the small systems are as sound as the large ones before the run starts.
- 7
Step 7: Resolve shortfalls and retest where necessary
Where a test does not meet its criteria the cause is investigated jointly, the remedy is agreed and the test is repeated under the same regime. Retesting has to be planned in, particularly where the network operator's involvement is needed again. The contract usually sets out what happens where a guarantee is not met after reasonable attempts, and those provisions are applied rather than negotiated informally on site.
- 8
Step 8: Complete takeover and pass the plant to the operator
When compliance, performance and reliability are all accepted the plant is taken over. The outstanding item list is agreed and carried into the defects period with dates against it, the operating and maintenance documentation and the as-built records are handed over, spares are transferred and training is completed and recorded. From takeover the operator runs the plant and all access is under their control. Remaining work is executed under their permit system and, in many cases, waits for a planned outage.
What are the benefits of Grid compliance, performance and reliability testing?
- Demonstrates objectively that the plant meets what was promised to the network and to the owner
- Formal acceptance criteria agreed in advance remove most of the scope for later dispute
- The reliability run exposes weaknesses in small auxiliary systems before the operator has to live with them
- Provides a measured performance baseline the operator can compare against for the life of the plant
- Completes the training and documentation transfer that the operating team needs
- Gives a clear, dated point at which responsibility passes from the project to the operator
What are the limitations of Grid compliance, performance and reliability testing?
- Depends on the network operator's availability and programme, which the project cannot control
- Test slots missed for weather, fuel or network reasons can be difficult to rebook quickly
- Performance results carry commercial consequences, so disputes over method are costly
- A single small auxiliary failure can end a nearly complete reliability run
- Retesting can require the whole co-ordination effort to be repeated
- Outstanding work after takeover is slow, permit controlled and may have to wait for an outage
What is Grid compliance, performance and reliability testing best suited for?
What plant does Grid compliance, performance and reliability testing need?
- Calibrated test instrumentation with traceable certificates, installed and proved in advance
- Data acquisition and recording equipment able to log all agreed test parameters
- Portable measurement equipment for ambient and reference condition monitoring
- Communications links to the control room and to the network operator during testing
- Permit-to-work, isolation and tagging systems administered by the operator throughout
- Documentation, records and training facilities for the takeover handover process
How is Grid compliance, performance and reliability testing quality-checked?
- Test regime, instrumentation, corrections and acceptance criteria agreed and documented before testing
- Network operator's requirements established and test slots secured well in advance of readiness
- All test instrumentation calibrated with traceable certificates accepted by every party
- Compliance, performance and reliability results recorded, evaluated and formally issued
- Outstanding item list agreed with dates and carried into the defects period at takeover
- Operating and maintenance documentation, as-built records, spares and training completed and recorded