NEM External Identity and Access Management
Background
The NEM External Identity and Access Management, known as NEIDAM, introduces a more secure, consistent and streamlined way for organisations, users and authorised third parties to access AEMO market systems and services.
Industry organisations and their representatives rely on access to AEMO systems to undertake market, operational and compliance activities. These access arrangements currently operate across multiple services and processes. NEIDAM will provide a unified approach for identifying users, authentication access and managing permissions across relevant AEMO market services.
NEIDAM forms a part of AEMO's Market Interface Technology Enhancements or MITE, together with Industry Data Exchange and Portal Consolidation. These initiatives are intended to modernise the foundational technology used by AEMO and industry and support the effective implementation of future energy market reforms.
NEIDAM is intended to provide:
- Simpler and more consistent access management, reducing duplicated processes and administrative effort
- Greater organisation level oversight, giving organisations clearer visibility and control over their users, roles and access
- Improved self service, enabling users and administrators to manage more of their own settings, access and permissions
- Stronger security controls, including improved authentication and clearer access management arrangements
- More secure data sharing arrangements, allowing authorised third parties to access participant information through their own approved access arrangements rather than through shared credentials.
NEIDAM was previously referred to as Identity and Access Management (IDAM). The name was updated to NEIDAM in 2026 to make clear that the initiative relates to external access arrangements for organisations and users operating in the National Electricity Market.
Scope
NEIDAM will introduce a unified identity and access management framework for relevant external organisations and users accessing AEMO market systems and services.
The initiative includes capabilities to support:
- User identification and authentication
- Administration of organisations, users, roles and access
- Identity and access lifecycle management
- Organisation level oversight of users and permissions
- Multi-factor authentication
- Identity federation
- Self-service access management capabilities
- Role based access
- Management of service accounts
- Improved auditing and reporting
- More secure sharing of participant information with authorised third parties.
NEIDAM will introduce the concept of a System Access Organisation, providing an organisation level structure for managing access to AEMO market services. Each System Access Organisation will have one or more Organisation Administrators responsible for overseeing relevant users, administrators, roles and access arrangements.
NEIDAM is expected to affect organisations that access relevant AEMO systems and services, including:
- NEM Registered participants
- Gas participants accessing electricity market systems *
- Authorised Service Providers and other authorised recipients
- NEM Accredited organisations
- Gas Supply Hub participants *
- Relevant non-registered organisations with approved access.
*This refers to gas participants accessing common electricity market systems (e.g. MarketsPortal, API and FTP) functionality used by participant for Gas Supply Hub (GSH), Pipeline Capacity Trading (PCT), Day Ahead Auction (DAA) and Gas Bulletin Board (GBB). Other gas market systems, including the Declared Wholesale Gas Market (DWGM) and Short-Term Trading Market (STTM) and Gas Retail Markets, are not impacted beyond service host on MarketsPortal.
Initial Implementation Update
NEIDAM was developed through the NEM Reform Foundational and Strategic Initiatives or FaSI process.
Beginning in 2023, AEMO worked with industry through the FaSI Focus Group to examine the existing challenges associated with identity and access management, industry data exchange and participant portals. This work brought together initiatives now known as NEIDAM, IDX and Portal Consolidation.
For NEIDAM, the business case supports the transition towards a unified approach to external identity and access management, with improved security, scalability, self-service, auditing, reporting and user experience.
Timeline
| Timing | Element | Summary |
|---|---|---|
| 2023 | FaSI Industry Consultation | AEMO commenced consultation with industry through the FaSI Focus Group to identify industry pain points and develop potential future state solutions for identity and access management, industry data exchange and participant portals. |
| 28 March 2024 | FaSI Business Case endorsed | The business case covering Identity and Access Management, Industry Data Exchange and Portal Consolidation was endorsed through the NEM Reform Executive Forum. |
| 31 July 2026 | Initial technical specification published | AEMO published the initial NEIDAM technical specification to support participant planning and assessment of potential impacts. |
| August 2026 onwards | Procedure Consultation and industry readiness | Consultation commenced on the Procedure for Accessing AEMO Systems, alongside ongoing industry engagement and readiness activities. |
| October 2026 – February 2027 | Organisational Readiness Activities commence | AEMO to progressively engage impacted organisations to confirm System Access Organisation arrangement, Organisation Administrators, Service Accounts and other information required to support NEIDAM activities. |
| March – April 2027 | Market Trial | Participants will have an opportunity to validate NEIDAM capabilities and prepare their organisation for the transition, including administrators and user registration migration pathways and critical integrations. |
| 2 May 2027 | NEIDAM Go Live and Cutover | AEMO will transition the existing user database to the new NEIDAM authentication, authorisation and user lifecycle services. |
| July 2027 – May 2028 | Industry Migration | Organisations will progressively migrate users from existing access arrangements to their selected NEIDAM migration approach. All organisations must complete migration by May 2028. |
Procedure Changes
Certain procedures, guidelines and other documents maintained by AEMO require updating to facilitate implementation of the NEIDAM initiative.
For further details regarding the affected documents, please consult the most recent consultations by reviewing the links below.
Procedure for Accessing AEMO Systems
NEIDAM Participant Toolbox
The NEIDAM Participant Toolbox is the central location for practical information, guidance and resources to help organisations prepare for NEIDAM.
The toolbox provides guidance on:
- Preparing your organisation and completing required activities
- Understanding System Access Organisation and administrator arrangements
- Key dates, Market Trial, Go-live and preparation activities
- Industry migration approaches and preparation
- Specifications, templates, user guides, FAQs and support.
Content will be added progressively as activities are confirmed and new guidance becomes available. Organisations should continue to monitor the toolbox for actions, supporting materials and updates.
Information will be added progressively as activities are confirmed and new guidance becomes available. Organisations should continue to monitor this page for actions, supporting materials and updates.
Implementation Toolbox
The Implementation Toolbox is a central location for useful resources to help participants understand and prepare for the changes associated with the rule implementation.
Draft Industry Readiness Approach
Frequently Asked Questions
-
Prepare your organisation
1. Why is AEMO asking my organisation to provide this information?
Ahead of NEIDAM go-live/cutover, AEMO needs organisation-specific information to establish the appropriate access arrangements for affected organisations. This will also support preparation for the subsequent Industry Migration period.
2. Who within my organisation will AEMO contact?
AEMO will engage the relevant representatives progressively. This will include the chief executive or equivalent representative, a duly authorised person and the initial Organisation Administrator. Depending on your organisation’s arrangements, the same person may perform more than one of these roles.
3. What is a System Access Organisation?
A System Access Organisation is the organisation nominated by a Registered Participant to administer access to relevant AEMO market services on its behalf.
Each Participant ID can only be associated with one System Access Organisation.
4. Can my organisation act as its own System Access Organisation?
Yes. A Registered Participant can act as its own System Access Organisation or nominate another organisation to perform this role for one or more Participant IDs.
Different System Access Organisations can also be nominated across different Participant IDs.
5. What is an Organisation Administrator?
An Organisation Administrator is a new NEIDAM role responsible for organisation-level oversight of users and access.
Each System Access Organisation will need at least one active Organisation Administrator. The initial Organisation Administrator will be nominated as part of the organisation preparation process.What happens to Participants Administrators?
The Participant Administrator role remains and will have some additional functionality.
6. Why does AEMO need information about our Service Accounts?
A Service Account is a non-person account used for system-to-system communication or background automation. URM rights alone cannot be used to identify Service Accounts, as they may cover user, administrative and Service Account functions. Therefore, participants will need to identify the existing production URM User Accounts that have been configured for machine-to-machine data exchange with AEMO. These are the accounts that should be transitioned as Service Accounts.
Identifying existing Service Accounts will help ensure they are appropriately accounted for as part of the transition to NEIDAM and minimise potential impacts to systems and processes that rely on them.
7. Is NEIDAM go-live/cutover the same as Industry Migration?
No. They are two separate stages.
NEIDAM go-live/cutover is planned for 2 May 2027. . Go-Live / Cutover refers to the period AEMO transitions the existing user base from the current legacy solution to the new authentication and authorisation services and manage user lifecycle with the new NEIDAM solution.
Industry Migration is planned to commence from July 2027. During this period, organisations will progressively transition users from existing access arrangements to the new NEIDAM arrangements.
8. What can my organisation do now to prepare?
Your organisation can start considering:
- who should be nominated as your duly authorised person
- how access should be managed for your relevant Participant IDs
- who should be nominated as your initial Organisation Administrator
- which existing accounts in URM are Service Accounts
- which monitored IT mailbox should be provided to AEMO
- your organisation’s initial Industry Migration considerations.
AEMO will contact the relevant representative directly when information is required and provide the applicable instructions for responding.
-
Understand your organisation’s access arranagements
1. What is a System Access Organisation?
A System Access Organisation (SAO) is an organisation that manages access to AEMO market services for its users and associated identities.
Registered Participants may act as their own SAO or nominate another organisation to perform this role for one or more Participant IDs.
Other organisations that access AEMO market services, including service providers, market bodies, regulators and data access organisations, may also be an SAO in their own right.
2. Can my organisation act as its own System Access Organisation?
Yes. Registered Participants, accredited entities and other organisations with authorised access to AEMO market services may act as their own System Access Organisation (SAO).
Where applicable, an organisation may also nominate another organisation to perform the SAO role on its behalf.
3. Can a Registered Participant have more than one System Access Organisation?
Yes. A Registered Participant can nominate different System Access Organisations across different Participant IDs.
However, each individual Participant ID can only be associated with one System Access Organisation.
4. What is the difference between an Organisation Administrator and a Participant Administrator?
An Organisation Administrator (OA) is a new NEIDAM role that provides organisation-level oversight of users and access within the System Access Organisation.
A Participant Administrator (PA) continues to administer users and access at the Participant Identity (PID) level, subject to the permissions provided by the Organisation Administrator.
5. Is the Participant Administrator role being replaced by the Organisation Administrator?
No. The Participant Administrator role will continue under NEIDAM.
The Organisation Administrator is a new role that introduces an additional level of organisation-wide administration and oversight. The two roles will therefore operate at different levels within the identity and access management model.
6. How many Organisation Administrators does a System Access Organisation need?
Each System Access Organisation must maintain at least one active Organisation Administrator.
An Organisation Administrator can also create and manage additional Organisation Administrators, Participant Administrators and users within the organisation.
7. Can an Organisation Administrator or Participant Administrator also have business access?
This will depend on the organisation’s Segregation of Duties setting.
NEIDAM provides settings that allow organisations to determine how administrative and business responsibilities are separated. Under full Segregation of Duties, administrators cannot also hold business-user roles. Other settings allow some or all administrators to also hold business roles.
Where both administrative and business roles are permitted, the two sets of privileges cannot be used simultaneously.
8. How will access work if we use a Service Provider?
Under NEIDAM, an authorised Service Provider will be its own System Access Organisation, Organisation Administrator and users, rather than relying on shared credentials.
Access to a Registered Participant’s confidential information will continue to depend on the relevant authorisation and data-sharing arrangements established by that Registered Participant.
Credential sharing will not be permitted under the NEIDAM arrangements.
10. Do our System Access Organisation arrangements have to be the same for every Participant ID?
No. A Registered Participant can have different System Access Organisations across its Participant IDs. Each individual Participant ID, however, can only be linked to one System Access Organisation.
-
Key dates and preparation activities
1. When is NEIDAM going live?
NEIDAM Go-Live/Cutover is planned for 2 May 2027.
2. Will all users be migrated on 2 May 2027?
At Go-Live/Cutover, active users will continue to authenticate in the same way they do today. Active users are those who have accessed AEMO market services within the last 180 days.
3. What will users experience at go-live?
Users will continue to authenticate in the same way they do today and may notice some updates to the look and feel of the portals.
4. What changes for administrators at go-live?
Administrators will have some new functionality available.
5. When does Industry Migration begin?
Industry Migration is planned to commence from July 2027, following a period of stabilisation and pilots.
6. How long does my organisation have to complete Industry Migration?
Industry Migration is planned to run from July 2027 to May 2028. Organisations will be asked to nominate their preferred migration timing within that window. Add default
7. Where can I find more information about the industry migration approaches?
Detailed guidance on Federation, Bulk Provisioning and Progressive Migration is available through your Industry Migration toolbox page.
-
Industry Migration
1. What is Industry Migration?
Industry Migration is the period following Go-Live/Cutover when organisations move their users from legacy arrangements to the target NEIDAM user arrangements. Organisations choose the migration method and timing within the migration window.
2. When does Industry Migration start?
Industry Migration is planned to commence from July 2027, following Go-Live/Cutover, stabilisation and pilot activities.
3. When does Industry Migration need to be completed?
Industry Migration is planned to conclude by May 2028. All users who have yet to commence migration by February 2028 will be defaulted to Progressive Migration to meet the May 2028 deadline. At the completion of the migration period, legacy user accounts that have not migrated will be disabled.
4. What Industry Migration approaches are available?
Three approaches are identified:
- Federation
- Bulk Provisioning
- Progressive Migration
5. What is Federation?
Federation enables an organisation to manage the provisioning of access and use its own trusted Identity Provider for authentication. Organisations choosing Federation will need to coordinate with AEMO to establish the necessary arrangements.
6. What is Bulk Provisioning?
Bulk Provisioning allows an organisation to provide a set of new identities and roles through a file uploaded by an administrator.
7. What is Progressive Migration?
Progressive Migration provides a self-service migration capability. Once activated, users are redirected to the enrolment workflow when they next log in.
-
Service Providers
1. What is a Service Provider under NEIDAM?
A Service Provider is a third party authorised by a Registered Participant to access information or AEMO market services on its behalf.
Under NEIDAM, Service Providers requiring system access will have their own organisational access arrangements rather than relying on credentials belonging to the Registered Participant they support.
2. Does a Service Provider need its own System Access Organisation?
Yes. Under the planned NEIDAM arrangements, each Service Provider requiring access to AEMO market services will be established as its own System Access Organisation (SAO) and will have its own Organisation Administrator and users.
3. Can a Service Provider use a Registered Participant's credentials?
No. Credential sharing will not be permitted under NEIDAM.
Service Providers will need to use access established for their own organisation, with individual users accessing AEMO market services through the appropriate NEIDAM arrangements.
4. Will a Service Provider automatically be able to access a Registered Participant's information?
No. Establishing a Service Provider under NEIDAM does not automatically provide access to a Registered Participant's confidential information.
The Registered Participant must authorise the appropriate data-sharing arrangement before the Service Provider can access that information on its behalf.
5. Who controls what information a Service Provider can access?
The Registered Participant authorises the data-sharing arrangement that allows the Service Provider to access its confidential information.
A Service Provider will only be able to access the information made available through those authorised arrangements.
6. Who manages users within a Service Provider organisation?
Each Service Provider will have its own Organisation Administrator, who will be responsible for administering users and access within that organisation in accordance with the NEIDAM access model.
7. When will Service Providers be onboarded to NEIDAM?
Service Provider onboarding is planned to occur during Industry Migration and will need to align with the migration of the Registered Participant or Participants the Service Provider supports.
AEMO will provide further information on onboarding activities and timing as Industry Migration approaches.
8. What if a Service Provider works with multiple Registered Participants?
A Service Provider may support multiple Registered Participants. The Service Provider will maintain its own organisational access arrangements, while access to each Registered Participant's confidential information will depend on the relevant data-sharing arrangements authorised by that Registered Participant.
Further guidance will be provided on how these arrangements will be established and managed during migration.
9. What should Registered Participants and Service Providers do now?
Registered Participants should begin considering:
- which third parties currently access AEMO market services or information on their behalf
- what information or services those third parties need to access
- whether existing arrangements rely on shared credentials or participant-managed access
- which Service Providers may therefore need to be established and onboarded under NEIDAM.
Service Providers should also consider which Registered Participants they support and the AEMO market services they currently access on their behalf.
AEMO will provide further guidance on the specific onboarding and migration activities required.
Further information
The primary channel for direct stakeholder email communications and procedure consultations for NEIDAM is the monitored, dedicated mailbox [email protected].
General queries in relation to the NEM Reform Program are welcome to [email protected].