Aemo Connection Agreement

After receiving a complete connection request and approving the performance standards, the Connection Network Service Provider (NSP) establishes a connection offer. The liaison NSP informs AEMO that a monitoring agreement has been signed and provides the information required under clause 5.3.7 (g) of the national electricity rules. In Victoria, AEMO has additional tasks. The transmission network is a declared shared network (DSN) and AEMO has been delegated to certain functions performed in other parts of the NEM by the NSP connecting when processing connections to the Victorian transport network. These pages focus on generating system connections, as this is the most common type of connection. In the following pages you will find more information about the general connection process in the transmission and distribution networks in the NEM and a more detailed description of the connection process on the Victorian transmission network. After receiving a complete connection request, AEMO creates a connection offer. If a declared common network (DSN) extension is required, the contracts required for the connection can be quite complex. Use of System Agreement (UoSA) documents AEMO`s connection offer, which is usually accompanied by a number of other contracts in an executable form and which meet, among other things, the formal requirements for connection and network agreements. Their number, form and execution time vary depending on: for any request regarding connections, please contact connections@aemo.com.au.

Network connections provide information on the establishment or modification of connections to transmission and distribution networks in the national electricity market (NEM). A person who wishes to connect an institution to the Connection Applicant (NEM) must contact the Network Service Provider (NSP). The binding NSP manages the connection process and is the primary point of contact for the connection requestor. NSP: The link NSP prepares a connection offer. Link competitor: Executes contracts with link NSP. AEMO: AEMO is not involved at this stage of the process. For projects requiring an extension of the NSD and consisting of countervailable and non-countervailable work (e.g.B. Interface and other small non-separable jobs), there are two other ways to develop the necessary extension: AEMO: executes the necessary contracts with the historical DTSO, the connection requestor and the selected DTSO (if questionable). AEMO determines whether the increase is countervailable or countervailable.

Across the NEM, AEMO`s role as a market and system operator is to assess and negotiate performance standards that may have an impact on the security of the energy system. AEMO also participates in the evaluation of simulation models of power plants and associated control systems, as well as commissioning and commissioning. Figure 1: Contracts for a project that does not require an increase For an unquestionable DSN extension, the established DTSO will create, own and exploit the increase. The structure of the contract is shown in Figure 3. . The contractual structure of a countervailable project is independent of the person choosing the party that builds, owns and operates the expansion. The structure of the contract is shown in Figure 2. In the case of projects that do not require an extension of the DSN, AEMO typically executes two contracts (see Figure 1): Figure 3: Contracts for a non-objectionable project requiring an extension – the historical DTSO builds, owns and operates the extension (rents and easements necessary if assets are to be located on land that is not owned by the DTSO). . . .