Introduction
Audience
AEMO Australian Energy Market Operator provides this information as a service targeting business analysts and IT staff in Registered Participant See Relevant Rules or Procedures companies.
The primary audience is Scheduled Generators See Relevant Rules or Procedures and MNSPs submitting MT PASA Medium Term Projected Assessment of System Adequacy. A 24-month supply demand forecast, published weekly, with daily resolution. Offers.
Objective
The EMMS Energy Market Management System (formerly MMS); software, hardware, network and related processes. - Technical Specification - October 2023 (Release) describes the projects planned by AEMO from a participant perspective and includes any system related changes for participants.
Status
|
Version |
Status |
|---|---|
|
2.0 |
This technical specification is final. For updated information, see MT PASA Offers. |
|
1.03 |
There are no changes or updates to the content from v1.02. This is only to fix the version numbering. |
|
1.02 |
We expect the design is complete. There may be minor changes according to pre-production feedback and testing. |
|
1.01 |
The design is 99% complete. There may be minor changes according to feedback and testing |
|
1.00 |
More detailed information with the design about 90% complete. We still expect changes to the final design while review and testing are in progress Integrated resource providers (IRP) are included in this technical specification although the new Participant Category is not effective until a later date |
|
0.02 |
Presents the EMMS - Technical Specification - October 2023 evolving design Please send feedback to techwriters@aemo.com.au |
Release dates
MTPASA scheduled for implementation in:
-
Pre-production AEMO’s test system available to participants: Monday 28 August 2023
-
Production AEMO’s live system: Wednesday 4 October 2023
Projects and enhancements
Changes and enhancements for this Release include:
|
Project |
Change |
Affected interfaces |
|---|---|---|
|
Changes for Scheduled Generators when submitting MT PASA Offers Refers to the MT PASA process only |
|
Rule and procedure changes
|
Project |
Title |
Version/status/rule |
Effective/final |
|---|---|---|---|
|
MT PASA |
NEM Reliability Forecasting Guidelines and Methodology Consultation |
Final |
30 April 2023 |
|
9 October 2023 |
|||
|
11.151 11.151.1 11.151.2 11.151.3 |
|||
|
v1.7 |
1 November 2021 |
Related technical specifications
|
Title |
Description |
|---|---|
|
Explains the changes to the MMS Data Model v5.2 |
Related documents
These guides and resources are updated according to this technical specification and published for the pre-production Release Date.
|
Title |
Description |
Publish date |
|---|---|---|
|
Help creating and submitting the csv payload to the MT PASA Offers file interface |
Draft published Send feedback to: techwriters@aemo.com.au |
|
|
Help using the Markets Portal > MT PASA Offer interface to submit csv payloads |
Draft published Send feedback to: techwriters@aemo.com.au |
|
|
Help using the MT PASA Offers API interface |
Draft published Send feedback to: techwriters@aemo.com.au |
Approval to change
No approval or agreement to change required from participant change controllers. AEMO sought agreement in the NEM Reliability Forecasting Guidelines and Methodology Consultation.
Market systems user group meetings
The Market Systems User Group (MSUG Market Systems User Group) is an industry user group established to discuss wholesale and retail IT systems releases. Its purpose is to facilitate the continuing improvement of AEMO's IT systems by seeking feedback and collaboration from participants.
MSUG meetings are open to all interested parties, with invitations sent to all included on the distribution list. If you have a technical question for a project and want to attend the MSUG ask your company’s support team to include your email address in their AEMO Help Desk Bulletin (CRM) distribution list.
Version numbers
Incremental version numbers such as 1.01, 2.01 and so on mean there is a minor change to the technical specification.
Major version numbers such as 1.00, 2.00 means there are substantial changes to the technical specification. Participants must carefully review these changes, detailed in Introduction.
Changes in this version
|
V2.0 |
V1.03 |
|---|---|
|
Version number updated to reflect final publication. There are no content changes. |
Version number increased from V1.02 to V1.03. There are no content changes. |
