1 Introduction
1.1 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 are:
- Procurers: AEMO or Transmission Network Service Providers (TNSPs) procuring contracts from the system security service provider Energy Rules Terms.
- Providers: are parties entering into system security contracts with Procurers. Initially, AEMO anticipates providers to be Market Generators See Relevant Rules or Procedures (Scheduled and Semi-Scheduled) and Integrated Resource Providers with Battery Energy Storage Systems A small distributed battery storage for residential and commercial consumers (BESS Battery Energy Storage System).
1.2 Objective
The EMMS Energy Market Management System (formerly MMS); software, hardware, network and related processes. - Technical Specification - December 2025 (Release) describes the projects planned by AEMO from a participant perspective and includes any system related changes for participants.
1.3 Status
Version | Status |
|---|---|
0.01 |
Presents the EMMS - Technical Specification - December 2025 evolving design. Please send feedback to Contact Us. In the Details of your enquiry section, mention the EAS Knowledge Management team as the Resolver group. |
1.4 Release dates
Scheduled for implementation in:
- Pre-production AEMO’s test system available to participants: Tuesday 2025
- Production AEMO’s live system: Tuesday 2 December 2025
1.5 Projects and enhancements
Changes and enhancements for this Release include:
No. | Functionality | Change | Affected interface | Reference |
|---|---|---|---|---|
1 | Registration | Minor updates to identify security service providers and associated units |
|
|
2 | Settlements | Updates to Settlement Reports |
|
|
3 | Electricity Data Model 5.6 | New/updated data model tables to support enablement instructions, ISF schedules and ISF reporting. Settlements/Billing changes for NSCAS and NMAS security services procured by AEMO |
|
|
4 | Markets Portal | New ISF interface called the Security Service Management (SSM) |
|
|
5 | Reports | Adds new reports |
|
|
1.6 Rule and procedure changes
Title | Project | Version/status | Effective |
|---|---|---|---|
Procedures For Issue of Directions And Clause 4.8.9 Instructions | ISF | Final | 4 July 2024 |
ISF | Final | 1 December 2024 | |
Network Support and Control Ancillary Services (NSCAS) Description and Quantity Procedure | ISF | Final | 1 December 2024 |
ISF | Final | 8 November 2024 | |
ISF | Final | 17 October 2024 | |
Provisional Security Enablement Procedures (Provisional Procedures) | ISF | Final | 30 June 2024 |
1.7 Related technical specifications
Title | Description |
|---|---|
EMMS – Technical Specification – Data Model 5.6 – 2025 | Provides the detailed Data model table changes. |
1.8 Related documents
These guides and resources are updated according to this technical specification and published for the pre-production Release Date.
Title | Description | Status |
|---|---|---|
Markets Portal Help |
| Not started |
Data Interchange Online Help | Update documentation related to Data Model 5.6 | Not started |
1.9 Approval to change
No approval or agreement to change required from participant change controllers. Agreement was sought in the NEM Reform Wholesale Consultative Forum.
1.10 Market systems user group meetings
The Market Systems User Group (MSUG Market Systems User Group) is an industry user group established to discuss NEM 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.
1.11 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 Page 1.
1.12 Changes in this version
No changes, this is the initial version.