FAQs and resources

AEMO considered alternative options and determined that a purpose-built system was required to support the needs of the NEM connection process. The Hub is being designed to provide the security, access controls, information management and traceability needed to manage sensitive project information and support collaboration across NEM connection projects.

Layered security, access controls, traceability and information management are core design principles for the Hub. The system is being developed to support the secure handling of NEM connection project information, with controls to protect sensitive data. It is being developed in alignment with relevant regulatory and legislative obligations, including Australian data storage requirements and applicable obligations under the National Electricity Rules (NER) and the Security of Critical Infrastructure (SOCI) Act.

AEMO is developing the cyber security, access and legal arrangements required to support secure use of the Hub, including user access controls, onboarding requirements and relevant terms for authorised organisations and users. Further details will be shared ahead of launch. For any questions in the meantime please email [email protected].

Yes, for the activities brought into the Hub. The Hub is intended to provide a secure, central source of truth for information managed within the Hub from launch, reducing reliance on spreadsheets, email trails and separate file-sharing tools while improving collaboration, visibility and traceability.

No. Direct engagement will remain an important part of NEM connection projects. The Hub is being designed to support these interactions by providing a shared and reliable source of project information, so discussions can focus more on resolving technical complexities, making informed decisions and progressing project outcomes.

The Hub will support active and future NEM connection and EAF projects from launch. Details on how active projects will transition to the Hub will be shared ahead of implementation. Historical or completed projects will not be migrated. Stakeholders requiring information on historical or completed projects should continue to request it through existing channels.

Yes. For queries where review and alignment are required, AEMO and the relevant NSP will be able to collaborate before queries are published. AEMO and NSPs will also retain the ability to publish queries independently where alignment is not required.

Yes. The Hub will support organisation and project-based access arrangements via a shared responsibility and accountability model, enabling authorised organisations to manage user access. AEMO will provide onboarding information, user guides and support materials ahead of launch.

Consultants will be granted access on a project-by-project basis. Access will be limited to the projects they are authorised to support, helping maintain appropriate control over project information and data.

Yes. Before each stage launches, AEMO will undertake targeted industry testing with selected stakeholders to validate key functionality and support a smooth rollout.

AEMO will provide training materials, user guides, demonstrations and other support resources to help stakeholders prepare for the Hub. Support will be rolled out progressively through implementation.

The design and development of the NEM Connections Hub is being funded by AEMO's Onboarding and Connections function as a capital investment. Consistent with AEMO's broader approach to recovering costs associated with connection activities, the investment will be recovered over the useful life of the Hub through AEMO's connections fees, which are charged to connecting proponents as part of the connection assessment process.

The efficiencies delivered, through reduced administrative effort, improved information management and streamlined collaboration, should provide a net benefit to connecting proponents NSPs, OEMs, and consultants.