Compliance is easier to manage when every technical obligation has a clear evidence path. For projects using GFM controls, BESS or HVDC, a technology label alone does not demonstrate performance. The assessment needs to describe the proposed configuration, the applicable requirements and the conditions covered by the evidence.
Establish the applicable requirements
Identify the relevant grid code, connection agreement and operator-specific requirements. Create a register that maps each obligation to its acceptance criteria, assessment method and evidence owner. Resolve interpretation questions before running a large study programme.
Separate network impact from plant performance
Grid impact studies examine how a connection affects the surrounding network. Compliance assessments demonstrate whether the plant meets its own performance obligations. The two inform each other, but one does not replace the other.
Keep models and settings traceable
Record the controller versions, parameters and network assumptions used in each assessment. When the design or settings change, identify which results require review. A controlled evidence register helps prevent reports based on different plant configurations from being combined without qualification.
Close the evidence gaps
Link study reports, model checks and relevant test evidence to the requirements register. Document deviations, mitigation measures and unresolved actions. Agree the next verification step with the relevant parties rather than treating a completed simulation report as the end of the connection process.
Questions for your project team
- Can each requirement be traced to current evidence?
- Do the study models represent the proposed control settings?
- Who owns the remaining actions and acceptance decisions?
Further reading
AEMO: system strength impact assessment guidelines ↗
The AEMO material is an Australian example of connection impact assessment. Requirements elsewhere follow the applicable local framework.
