AEMO Setup Runsheet
Introduction
To establish a direct connection to AEMO for retrieving usage information, the following conditions must be met:
- mTLS transport security must be enabled for direct connectivity to AEMO.
- Valid credentials for MSTAT/MarketNet access must be available.
Since interactions with AEMO are exclusively managed by retailers, Biza requires your support to meet these requirements.
mTLS Connectivity
To access data on your behalf, connectivity must be established through mTLS. Follow the steps below:
-
Contact the AEMO support hub (
support.hub@aemo.com.au) to request a certificate for API access.- This must explicitly state that is in an additional certificate request for a third-party (Biza) certificate.
- You should also confirm who the authorised representatives are for your organisation as they will be required to submit the API registration form.
-
AEMO will provide an API registration form for the provision of the certificate.
-
Biza will provide you with the following information
- IT Network setup (Section C).
- CSR provision.
- Personnel details for technical enquiries.
-
You must provide
- Requester details (Section A).
-
Once completed, the form must be submitted by the requester to the AEMO Support Hub (
support.hub@aemo.com.au) with a subject of ‘ATTN: Lucas’ for the signing of the certificates and provision back to Biza.
Account Provision
Account Specification
Biza requires two (2) accounts for each of your environments, for each FRMP (Financially Responsible Market Participant), with the naming of these accounts follow the below standard:
- Pre-production
- BIZAPREPROD1
- BIZAPREPROD2
- Production:
- BIZAPROD1
- BIZAPROD2
The usernames above can be changed, but the following constraints must be considered.
- They must state the space.
- They must be the same username prefix within an environment and end with a rank of
1or2.
Account Cycling
Accounts will be rotated every 30 days to meet the AEMO’s password rotation requirements. Biza will run a script daily to check if an account is due to rotation.
Sharing Credentials with Biza
To share secure details with Biza that include a credential, we require the content and credentials to be sent by different means. Content can be included in a Service Desk ticket, but the credential must come via email. Or you can provide the content and password via two separate emails.