In our view, a renewable project should be developed from both ends: the resource that makes generation possible, and the network that makes delivery possible. Leaving the second question until the first is settled can turn an attractive site into a difficult project.
A location is more than a resource map.
Solar irradiation or wind conditions help establish the opportunity. The next conversation must include the receiving substation, the line route, access, land constraints and the intended date of operation. A site can be strong on one measure while creating expensive or time-consuming dependencies elsewhere.
Our starting point is a shared development picture. The land team should understand the proposed electrical route. Engineering should know which assumptions are still open. The commercial case should reflect the same connection and commissioning scenario as the delivery programme.
Separate the different meanings of “ready”.
A proposed connection point, an allocation or approval, a physically completed bay and an energised route describe different states. They should be tracked separately. An approval milestone cannot substitute for evidence that the infrastructure, tests and operational arrangements will be ready when the project needs them.
CTUIL publishes information on bay allocation and margin, connectivity and transmission planning. These are useful inputs to development diligence; their relevance must be checked against the particular project and the current information from the responsible authority. See CTUIL’s renewable energy connectivity information.
Read the dependencies in both directions.
Consider an illustrative project where generation equipment can be installed before the evacuation route is available. Accelerating equipment delivery alone does not resolve the missing route. The decision needs a view of permissions, construction access, network works, testing and the commercial consequences of the revised sequence.
The reverse matters too. A network milestone can influence the order in which generation blocks are developed. A changed route can affect land and civil design. Storage can alter import and export requirements, but should be assessed for its actual operating duty; it is not a substitute for the required network rights or studies.
Make uncertainty visible before commitment.
We favour a concise interface register: the assumption being made, the evidence supporting it, the organisation responsible, the date it is needed and the consequence if it changes. This creates a practical link between a technical question and a decision about scope, sequence or capital.
A useful review compares alternatives while they are still available. What happens if the connection point changes? Which package has the longest dependency? What evidence is needed before the next commitment? Which activity can progress without making an unresolved assumption irreversible?
This is why the capabilities belong together.
Project development, transmission engineering and EPC see different parts of the same outcome. Bringing them into one conversation helps expose a constraint while the project can still respond to it. It also gives partners a clearer account of where responsibilities begin, where they meet and what completion actually means.
For Resus, integration is a way of asking better questions early. The goal is a project whose resource, network connection and delivery plan support the same operating purpose.
This perspective explains our development approach. Project-specific connectivity and compliance requirements should be established with the relevant authorities using current regulations and studies.