Guide to Electricity Information Systems · Chapter2 NEMITSystems 4 AbouttheNEM 4 Access 4 ... System Interface Description ... experiencedITteam,planning,networking,database

GUIDE TO ELECTRICITYINFORMATION SYSTEMSPROVIDESGUIDANCEFORREGISTEREDPARTICIPANTSANDINTERESTEDPARTIESABOUTAEMO'SPARTICIPANTELECTRICITYMARKETSYSTEMS.

Version: 3.00Published: Thursday, 26 October 2017

No reliance or warrantyThis document does not constitute legal or business advice, and should not be relied on as a substitute forobtaining detailed advice about the National Gas or Electricity Law, the Rules or any other applicable laws,procedures or policies. While AEMO has made every effort to ensure the quality of the information in this Guide,neither AEMO, nor any of its employees, agents and consultants make any representation or warranty as to theaccuracy, reliability, completeness, currency or suitability for particular purposes of that information.

Limitation of liabilityTo the maximum extent permitted by law, AEMO and its advisers, consultants and other contributors to thisGuide (or their respective associated companies, businesses, partners, directors, officers or employees) are notliable (whether by reason of negligence or otherwise) for any errors, omissions, defects or misrepresentationsin this document, or for any loss or damage suffered by persons who use or rely on the information in it.AEMO has prepared this Guide to Electricity Information Systems (Guide) to provide guidance on the use of theEnergy Market Systems under the National Gas or Electricity Rules (Rules), as at the date of publication.

Trademark noticesMicrosoft is a trademark of Microsoft Corporation in the United States and/or other countries.Oracle and Java are registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.

Documents made obsoleteThe release of this document changes any version of the Guide to Electricity Information Systems.

DistributionAvailable to the public.

Document identificationBusiness custodian: n/aIT custodian: Manager, Market SystemsPrepared by: Technical Writers, Market SystemsLast update: Thursday, 26 October 2017 09:47

Version HistoryVersion 3.00. Updated for the Power of Choice project and the B2B e-Hub.

Further informationFor further information, please visitwww.aemo.com.au or contact:AEMO's Support HubPhone: 1300 AEMO 00 (1300 236 600), Email: [email protected]

FeedbackTo suggest corrections or improvements to this document, please contact the AEMO Information and SupportHub.

© 2017 AEMO ii

IMPORTANT NOTICE

GUIDE TO ELECTRICITY INFORMATION SYSTEMS

http://www.aemo.com.au/

mailto:[email protected]?subject=Information Request?subject=Information Request

Chapter 1 Introduction 1Purpose 1

Audience 1

How to use this guide 2

What’s in this guide 2

Chapter 2 NEM IT Systems 4About the NEM 4

Access 4

Releases 5

Environments 5

NEM IT systems overview 6

NEM IT systems 6

NEM retail functionality 7

NEM wholesale functionality 9

NEM participant categories 13

NEM Dispatch Engine (NEMDE) 16

Market solver files 17

Other NEM IT systems 17

Chapter 3 NEM IT Interfaces 18

Chapter 4 Data network connection (MarketNet) 21Data network connection decisions 22

Data network connection options 22

Registered participant entitlements 23

Unregistered participant access requests 25

Additional connection and bandwidth 26

Making changes to your MarketNet connection 26

Chapter 5 Market Data 27Website data 27

Current data 27

Historical data 28

Data sharing 28

About data sharing 28

Data sharing example 30

Data sharing set-up 31

Data sharing removal 32

© 2017 AEMO iii

CONTENTS


© 2017 AEMO iv

Chapter 6 Software Packages 33MSATS retail system software 33

EMMS wholesale system software 34

Chapter 7 Security 35About security 35

Participant's security responsibilities 36

User Rights Management (URM) 37

Understanding the set participant function 38

Changing your Participant ID password 39

Participant user passwords 49

Participant User password format 50

Chapter 8 Setting up your IT Systems 55About setting up your IT 55

Who does what when? 55

Checklist for setting up your IT systems 56

Chapter 9 Connecting to AEMO's Market Systems 60Participant File Servers 60

Web portals 63

Web Services 65

API gateway 66

Chapter 10 System transfers and deregistration 68System transfers 68

Deregistration for IT systems 68

Needing Help 69AEMO's Support Hub 69

Contacting AEMO's Support Hub 69

Information to provide 69

Communications 70

Feedback 71

Related resources 71

Index 89


CHAPTER 1 INTRODUCTION

Purpose 1Audience 1How to use this guide 2What’s in this guide 2

PurposeThis guide provides guidance for Registered Participants about AEMO'sparticipant electricity market systems. It is relevant to IT decision making duringparticipant onboarding and provides an understanding of the IT systems requiringset up. Because each participant has its own scope of business and operation,this document only outlines the facilities available. Please seek advice for yourcompany’s specific business needs.

For participants registering with AEMO, please read this guide before andwhile completing your registration application to help you understand yourrequirements.

Audience

This document is relevant to:

l Interested parties considering registration with AEMO.

l Interested parties requiring an overview of AEMO's participant IT systems.

l New registrants applying for registration with AEMO.

l New registrants and existing participants setting up interfaces to AEMO's ITsystems.

l Participants requiring an understanding of the applications AEMO provides.

l Implementers and maintainers of interfaces to AEMO’s systems.

© 2017 AEMO 1

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 1 INTRODUCTION

How to use this guidel This document is written in plain language for easy reading. Where there is adiscrepancy between the Rules, and information or a term in this document, theRules take precedence.

l Text in this format indicates there is a resource on AEMO’s website.

l For an explanation of the terms and abbreviations, see Glossary on page 73.

l Glossary terms are capitalised and have the meanings listed against them.

l Italicised terms are defined in the National Electricity or Gas Rules. Any rulesterms not in this format still have the same meaning.

l Actions to complete in the web portal interface are bold and dark grey.

You can find resources mentioned throughout this guide on AEMO'swebsite: www.aemo.com.au.

What’s in this guideChapter 2 NEM IT Systems on page 4 explains what IT systems AEMO offers to

Registered Participants.

Chapter 3 NEM IT Interfaces on page 18 explains the different IT interfacesavailable for Registered Participants to access AEMO's IT systems.

Chapter 4 Data network connection (MarketNet) on page 21 explains AEMO'ssecure data network connection and answers questions such as: networkoptions, participant entitlements, and how to change your existing MarketNetconnection.

Chapter 5 Market Data on page 27 explains how to share wholesale data withanother participant ID and where to obtain market data.

Chapter 6 Software Packages on page 33 explains the software AEMOmakesavailable to participants and where to download it.

Chapter 7 Security on page 35 explains Registered Participants user rightsmanagement (URM) for participants, security, and password requirements.

© 2017 AEMO 2



Chapter 8 Setting up your IT Systems on page 55 describes who does what whenduring registration and the steps required for your IT team to set up your ITsystems to interact with AEMO’s market systems.

Chapter 9 Connecting to AEMO's Market Systems on page 60 explains howRegistered Participants connect to AEMO's IT systems.

Chapter 10 System transfers and deregistration on page 68 describes systemstransfers and explains participant deregistration.

Glossary on page 73 explains the capitalised terms used throughout this guide.

Needing Help on page 69 provides information about AEMO communications, howto request assistance for IT related issues, and a list of references mentionedthroughout this guide.

© 2017 AEMO 3


CHAPTER 2 NEM IT SYSTEMSAEMO has numerous electricity systems with multiple interfaces to provide for theneeds of all participants.

About the NEM 4Access 4Releases 5Environments 5NEM IT systems overview 6NEM IT systems 6NEM retail functionality 7NEM wholesale functionality 9NEM participant categories 13NEM Dispatch Engine (NEMDE) 16Other NEM IT systems 17

About the NEM

The NEM interconnects five regional market jurisdictions (Queensland, NewSouth Wales, Victoria, South Australia and Tasmania). West Australia and theNorthern Territory are not connected to the NEM. It involves both wholesale andretail markets managed in line with the National Electricity Law and the NationalElectricity Rules (Rules).

The NEM IT systems assist in determining the spot price and facilitate financialsettlement of the market. The systems are designed to meet the performance andreliability requirements of the Rules and the expectations of market participants,provide security for sensitive information, and be cost effective for participants.

Access

Access to some systems is dependent on a participant’s registration category.AEMOmakes systems available to participants in accordance with the rules andprocedures of each energy market with access available 24 hours a day, 7 days aweek. Except for notified periods of system maintenance and unplanned outages.AEMO constantly monitors its information systems to ensure performancestandards are met.

© 2017 AEMO 4

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 2 NEM IT SYSTEMS

Releases

AEMO has a six-monthly release program meaning participants can expect newreleases twice each year, around April–May and October–November.

Environments

There are pre-production and production environments, each separatelymaintained. The pre-production environments are intended for participant testingand training purposes. New features are added to pre-production one monthahead of production with changes announced in release schedules and technicalspecifications.

You can find change notices and technical specifications on AEMO'swebsite > electricity or gas > IT Change and Release Management.

So participants know which environment they are working in, the pre-productionenvironments have a green border or menu.

© 2017 AEMO 5




Participants are obliged to ensure their systems are kept in line with AEMO'ssystems.

NEM IT systems overview

This diagram is an overview of the electricity market IT systems AEMO provides forRegistered Participants.

Figure 1 AEMO electricity IT market systems

NEM IT systems

Table 1 summarises the NEM IT systems available to participants. For anexplanation of the interfaces, see NEM IT Interfaces on page 18

© 2017 AEMO 6


Table 1 NEM IT systems

System Interface Description

Market Settlementand TransferSolution (MSATS)

Web portalFile uploadFile serverWeb servicesAPI GatewayFTP Gateway

MSATS is the NEM retail system used for NEM energysettlements, by determining energy flows from generators andretailers—MSATS does not determine the cost of energy. Table2 summarises the functionalities available to participants inMSATS.To support the operation of the NEM, participants are requiredto comply with the procedures set out by AEMO, which definethe communication interfaces and infrastructure for electroniccommunications between AEMO and participants . See List ofNational Electricity Market Procedures, guidelines anddocuments .

B2B e-Hub API GatewayFTP Gateway

An electronic information exchange platform facilitating B2BCommunications used by the retail industry.Participants must obtain accreditation to use the B2B e-Hub.For help, see Guide to B2B e-Hub Self Accreditation.

Electricity MarketManagementSystem (EMMSMarkets Portal)

Web portalFile uploadFile serverWeb service

EMMS is the NEMwholesale system determining the cost ofenergy. EMMS provides such things as ancillary services,dispatch, market information, NEM reports, offers andsubmissions, settlements and prudentials, and trading facilities.Table 3 summarises the functionalities available to participantsin EMMS.

NEM retail functionalityTable 4 summarises the functionality available in MSATS. For details about thefunctionality relevant to each participant category in the retail market, see Retailparticipant categories on page 13.

For more details about each functionality, see MSATS guides, information andassistance for using MSATS. Electricity > Retail and Metering > MarketSettlement and Transfer Solutions.

All files exchanged with MSATS and B2B conform to the Australian Standardfor Energy XML (aseXML), for more details, see aseXML Standards onAEMO's website.

© 2017 AEMO 7


http://www.aemo.com.au/Electricity/Policies-and-Procedures/B2B



http://www.aemo.com.au/About-the-Industry/Information-Systems/aseXML-Standards

Table 2MSATS functionality

Functionality Interface Description

Administration Web portal Used by participant administrators to set up and maintainuser rights to AEMO’s system access.

B2B communications API GatewayFTP GatewayWeb portalFile uploadFile server

Supports the creation and management of a defined set ofbusiness-to-business transactions and acknowledgements.Optionally used to manage your MSATS B2B inbox andoutbox.

B2B responder (pre-production only)

Web portalFile server

Used to specify which transactions you would like to receiveas part of testing the operational interaction betweenparticipants’ systems and the B2B e-Hub.Intending B2B participants use the B2B Responder whenperforming their self-accreditation tests.

File server interaction(Data Load Import)

Web portalFile uploadFile server

Carries messages between MSATS and participant systemsand allows access to participant archive folders.

Metering data Web portalFile server

Used for the receipt, storage and aggregation of metering(data stream) data.

MSATS limits Web service Informs participants about the status of their transactionlimits. Limits are imposed on participant interaction withMSATS to prevent overload of the system.

NMI information Web portalFile serverWeb service

Search and view NMI information.

Ombudsman (NMIenquiry reports)

Web portal Provides ombudsman companies with access to NMI standingdata. Participants can view and download reports onombudsman enquiries.

Participants(information &contacts)

Web portal Used to view participant information and create and maintainparticipant contacts.The EMMSMarkets Portal uses the MSATS contacts to sendnotifications for Demand Side Participation, Settlementstatements, and Market Direct notifications.

Profile preparation(profile information)

Web portal Performs Metering Data Management (MDM) functions suchas defining profile methods and areas, defining data sourcesand creating profiles.

© 2017 AEMO 8



Reports Web portalFile serverWeb service

Access to CATS & MDM reports.

Settlement data Web portalFile server

Used by authorised users to view settlement data.

Transactions (changerequests, objections,notifications, datarequests)


Facilitates the process of consumer connection pointtransfers and the management of standing data.

User profile Web portal Used to change and view user profiles and update passwords.Changing a password in MSATS changes the password for allNEM systems.

NEM wholesale functionalityTable 3 summarises the functionality available in EMMS. For details about thefunctionality relevant to each participant category in the wholesale market, seeWholesale participant categories on page 15.

For more details about each functionality, see Markets Portal Help.

Table 3 EMMS functionality


Constraints Web portalWeb Service

Used to convert a constraint equation into plain English format.

Credit Support Web portal The Credit Support web interface provides registered participantswith a numerical and graphical view of their credit support status,and a scenario builder where participants can analyse their bankguarantee structure without saving the changes to the CreditSupport system.

Data Delivery Web portal Use the Data Delivery menu to:

© 2017 AEMO 9


https://portal.preprod.nemnet.net.au/help


l Access the Data Interchange Status Dashboard. The statusdashboard displays: The status of the Data Interchangecomponents within the participant company. A list offilenames, delivery dates and a file re-request count(where a file has been sent to the participant's systemmore than once). Multiple file deliveries can indicate aproblem at the participant's end.

l Make a File Delivery query and re-request files. The filedelivery web interface allows participants to query all thefiles delivered within a date range, and request selectedfiles delivered again to the file server.

l View your company's Data Sharing arrangements.

Data Interchange(DI)


Data Interchange is a set of cooperating applications used toreplicate, manage, and monitor data between AEMO and aparticipant's database conforming to the MMS DataModel.AEMO provides the Data Interchange applications to participants toassist with the replication of data to their DBMS. Successfullyimplementing and managing Data Interchange requires anexperienced IT team, planning, networking, databasemanagement, batch file management, and disaster recovery.AEMO supports data replication to Oracle and SQL Serverdatabases. The licensing of the participant ID’s SQL Server orOracle data store is the responsibility of the participant. Scripts tobuild the MMS DataModel are available for SQL Server and Oracledatabase platforms, see MMS Data Model.Participants use the Data Interchange web applications in theEMMS web portal to:

l Subscribe to receive files in their participant folder on theEMMS file server.

l Monitor their Data Interchange, Data Delivery, and DataSharing statuses.

For more details, see Data Interchange.

Data Sharing Web portalFile server

Each participant ID can share their data with other participant IDs,subject to an authorised request. Implementing data sharingmeans the full “Data Interchange” data set (including private data)for the requesting participant ID is made available to anotherparticipant's sets of folders in the EMMS file server, as nominatedin the request. The sharing of data is for both pre-production andproduction. A data sharing requirement may emerge, for example,due to a merger with, takeover of, or sale of another NEMregistered participant. The requirement may be to use one

© 2017 AEMO 10


http://www.aemo.com.au/About-the-Industry/Information-Systems/Data-Interchange#MMS Data Model

http://www.aemo.com.au/About-the-Industry/Information-Systems/Data-Interchange


company's IT system to manage access, and process the data fortwo or more participant IDs using just one participant ID's set offolders in the EMMS file server.The web portal interface provides the status of any data sharingagreements you have implemented.

Data Subscription Web portal Used to subscribe to files for Data Interchange, and obtain thelatest MMS DataModel. EMMS generates files continually, basedon changes and five-minute dispatch runs, etc. These files aretypically CSV files that contain public data and participant’s privatedata.AEMO recommends participant use of the “Data Interchange”products, supplied by AEMO, to automate receiving and storage ofthe files. AEMO provides working sample software for FTP accessto MarketNet and working sample software for Data Interchange.

Dispatchinstructions

File server Dispatch Instructions from AEMO.

Dispatchperformance &history

File server Dispatch performance and history.

IntermittentGeneration


AEMO hosts the intermittent generation interfaces and providesdata access to the market and to individual intermittentgenerators. The systems produce various types of forecasts atregular run intervals for each forecast type.Participants input their intermittent generation information(Elements Unavailable and Upper MW Limit) before the start ofthe relevant trading date. Availability profiles can be updated asfrequently as the change occurs, but not retrospectively forhistorical intervals.

Market Info Web portalFile server

A summary of the market in each of the regions for definedforecast types such as dispatch and pre-dispatch.

Market Direct Web portal Provides access to reports and statements published by AEMO forintermittent generators. Participants can subscribe to reports forautomated delivery each time a new report is published.

Offers &Submissions


Allows participants to submit and maintain energy, frequencycontrol ancillary service (FCAS), MTPASA, NMAS, DSP offers andGELF Declarations.

© 2017 AEMO 11



PaymentNomination

Web portal Provides participants with their current and historical paymentnomination details for the payment of settlements. Participants cannominate a new payment to take effect in a future settlement,change an existing payment nomination and the billing week ittakes effect, or change between normal and early payments.

PerformanceMonitor

Web portal The performance monitor is a graphical view of the current DataInterchange environment run and managed by AEMO. Participantsnot receiving data, or experiencing data delays can contrast thedata delivery performance of their Data Interchange environmentto the AEMO's Data Interchange performance environment.

PrudentialDashboard

Web portal Provides participants with their latest prudential information. Thedashboard shows exactly the same information that AEMO uses inits prudential assessments and provides participants with usefulinformation about their accrued financial position with AEMO.

PrudentialForecast

Web portal Provides participants with a forecast of their expected prudentialposition for the next NEM business day, enabling participants tomanage their prudential obligations.

PrudentialMargin Offsets

Web portal Allows participants to offset their trading amounts against theirreallocation amounts for the determination of the PrudentialMargin (PM) for Maximum Credit Limit (MCL) reviews. For moredetails, see Prudentials and Payments on AEMO's website.

Reallocations Web portalFile upload

Allows participants to create, submit, authorise, and viewreallocation requests in accordance with the settlementsReallocation Procedures. At each settlement run, reallocationdetails are copied from the Reallocations system to theSettlements system. The Settlements system then includes thisdata in settlements calculations and incorporates the results inparticipants’ weekly settlement statements.

© 2017 AEMO 12



SettlementsDirect

Web portal Provides participants with access to information published byAEMO, including settlement statements. Participants can subscribeto reports for automated delivery each time a new report ispublished.

SettlementResidue Auctions(SRA)


The SRA sells entitlements to settlement residue attributable tointer-regional interconnectors up to three years in advance; withthe units auctioned over twelve quarters. The intention is toimprove the efficiency of the NEM by promoting inter-regionaltrade. The risk of trading between regions is better managed bymaking the settlements residue available to the market place.

VAr Dispatch Used by generator control rooms and network operators (RPOs),to control the reactive power devices. Generator traders may alsobe interested in viewing VAr Dispatch instructions.VAr Dispatch issues instructions to RPOs to achieve stable voltagecontrol of the electricity grid. These instructions typically requestchanges to reactive plant (such as, capacitors, reactors, andgenerating units), to increase or decrease the VAr contribution tothe grid.

NEM participant categoriesThis topic describes the relevant and optional functionalities for each NEMparticipant category.

Non-market generators may choose to connect to AEMO systems, but have noneed to do so.

Intending Participants may choose to connect to AEMO’s systems on specialrequest.

For more details about participant categories, see Electricity or GasParticipant Information on AEMO's website.

Retail participant categories

Table 4 describes the relevant and optional functionalities used in MSATS foreach participant category.

© 2017 AEMO 13



Table 4MSATS functionalities used by each participant category

Relevant =C | Optional = O

Functionality Generator Customerclassifying loadsSmallGenerationAggregator

Customer NetworkServiceProvider

SpecialParticipant

Trader Reallocator

Administration C C C C C C

B2B O O C C

B2B responder O O C C

File server interaction(Data Load Import)

O O C C

Metering data O O C C

MSATS limits O O C C

NMI information O O C C

Ombudsman O O C C

Participants O O C C C C

Profile preparation O O C C

Reports O O C C

Settlement data O O C

Transactions O O C C

User Profile C C C C C C

© 2017 AEMO 14


Wholesale participant categories

Table 5 explains the relevant and optional functionalities used in the EMMS foreach participant category.

Table 5 EMMS functionalities used by each participant category

Relevant =C | Optional = O

Functionality Generator Customer classifyingloads & SmallGeneration Aggregator


Trader Reallocator

Constraints C C

Credit Support C C C C C C

Data Delivery C C O O O

Data Interchange(DI)

C C O O O

Data Sharing C C O O

Data Subscription C C O O

DispatchInstructions

C C

DispatchPerformance &History

C

IntermittentGeneration

C

Market Info C C O O

Market Direct C

Offers &Submissions

C C

PaymentNomination

C C C C C C

© 2017 AEMO 15


Functionality Generator Customer classifyingloads & SmallGeneration Aggregator


Trader Reallocator

PerformanceMonitor

C C O O O

PrudentialDashboard

C C C C C C

PrudentialForecast

C C C C C C

Prudential MarginOffsets

C C C

Reallocations C

SettlementsDirect

C C C C C C

SettlementResidue Auctions(SRA)

C C C

VAr Dispatch C C

NEM Dispatch Engine (NEMDE)The NEMDE Queue Service is a separately purchasable product from AEMO. Itprovides an application interface enabling participant company’s analysts tomodel alternative outcomes from AEMO’s dispatch engine, the NEMDE Solver.The service allows participants to edit and submit a NEMDE input file and receivethe corresponding output file.

For more details, see NEMDE Queue Service. Application to purchase is toAEMO's Support Hub.

© 2017 AEMO 16


http://www.aemo.com.au/About-the-Industry/Information-Systems/NEMDE-Queue-Service

Market solver files

For each dispatch cycle (5 minutes), a generated input file is submitted to thelinear program solver (NEMDE), producing two output files. The files for eachdispatch cycle are:

l Input file

l Output file

l Price Setter file

Each day AEMO publishes the market solver files in the participant ID’s file server\MarketData subfolders.

Other NEM IT systemsAlong with EMMS and MSATS, AEMO has other systems, mainly intended for alimited range of participants, examples include:

l Operations and Planning Data Management System (OPDMS).l NetworkOutage Scheduler (NOS).

© 2017 AEMO 17


CHAPTER 3 NEM IT INTERFACESThis chapter explains the IT interfaces available for Registered Participantsto accessNEM participant IT

This table explains AEMO's IT interfaces, their functions, and their suitability forparticipants.

Table 6 AEMO's IT interfaces

Interface Protocol Function

AEMO’swebsite

HTTP Suitable as a source for publicly available market data at no cost. The public datapublished on AEMO’s website is the same as distributed through the fileinterfaces, although file interfaces also contain each participant’s private data.The data is in CSV format in many files along with some graphical summaries.See Electricity Data on AEMO's website.

APIGateway

API Used to push or pull messages from the B2B e-Hub queue using RESTful APIs.

Datanetworkconnection

HTTPS Most access to AEMO’s market systems requires a secure private data networkconnection to MarketNet. If your company is a Registered Participant, it is likelythat you have access to MarketNet. However, if your company does not have

© 2017 AEMO 18

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 3 NEM IT INTERFACES


(MarketNet) access to MarketNet, you must organise this first.For help, see Guide to Information Systems andMarketNet ConnectionRequest.

File server FTP AEMO systems to participant systems interaction using batch processing,suitable for:

l Participant systems using database technology.l Submission or receipt of high volumes of data.l Management of security and data distribution.

AEMO recommends this method to replicate large amounts of dataSee Participant File Servers on page 60.

File uploadto webportal

HTTPS MSATS and EMMS both allow the upload of files directly to the web portalinterface.

FTPGateway

FTP Uses the MSATS Hokey-Pokey protocol to deliver B2B communications.

© 2017 AEMO 19



Internet HTTPS A choice for communicating with the B2B e-Hub over the API gateway only.

Web portals HTTPS Participants can use a web browser over MarketNet to interact with AEMO’sretail and wholesale systems. The web interfaces allow direct data entry andare designed for secure, interactive use. They are suitable for light demand ofdata transfer. Many web applications allow the upload of files directly to theinterface.Examples of functionality are:

l User administration for participant users.l Placing bids.l Retrieving reports.l Retrieving settlement information.l Monitoring prudential exposure.

AEMO recommends small operators use the web portal interface to retrieveand upload files. See Web portals on page 63.

Webservices

HTTPS AEMO provides web services client software for both retail and wholesalesystems. Participants can use the approach taken in the web services softwareto implement their own custom web client into their gateway system.Web services are suitable for retrieving:

l NMI standing data and NMI details.l Constraint information.l MSATS limits status.l MSATS processing status.

See Web Services on page 65.

© 2017 AEMO 20


CHAPTER 4 DATA NETWORK CONNECTION(MARKETNET)

Data network connection decisions 22Data network connection options 22Registered participant entitlements 23Unregistered participant access requests 25Additional connection and bandwidth 26Making changes to your MarketNet connection 26

This topic discusses AEMO’s private data network connection, MarketNet. Mostaccess to AEMO’s market systems requires a data network connection toMarketNet—this is the first step in implementing your access to AEMO’s marketsystems.

Participants provide details of requirements for network connectivity toMarketNet in the IT Systems section of the registration application.

Figure 2 understandingMarketNet

For provision and maintenance of MarketNet, participants must providedetails for a suitably qualified IT Technical Network Contact in theirregistration application.

© 2017 AEMO 21

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 4 DATA NETWORK CONNECTION (MARKETNET)

Data network connection decisions

Participants must decide on the physical connection and preferred managementapproach for their connection to MarketNet. Considerations for each participantinclude:

l Availability of connection into MarketNet.

l Cost of participant equipment and communications bandwidth (check withsupplier).

l Reliability of end-to-end connection (as determined by your business needs).

l Disaster recovery plans for participant connections, equipment, and site(s)—asdetermined by your business needs. AEMO recommends geographic ortechnology diversification, or both.

Companys registering as intending participants are not required to connectto AEMO’s systems, but may wish to do so by paying an annual prepayment.For help, see annual prepayment options on page 25

Data network connection options

AEMO provides two types of connection options:

l A permanent continuous connection.

l A variable connection, intermittently connected for short durations. For securityreasons, the connection is dropped if there is no activity for 30 minutes.

Table 7 on the next page explains the choices required for your registrationapplication.

© 2017 AEMO 22


Table 7MarketNet data network connection options

Connection Type Details

DedicatedLink

Permanent A dedicated connection takes more time to set up. Telstra advise setting up adedicated connection takes at least 20 business days.A dedicated connection, such as Frame Relay or BDSL, is from the participantrouter, via the telecommunication provider’s Bearer, to AEMO’s IPWAN. Theparticipant, with AEMO’s assistance, is responsible for arranging thesubscription link with their chosen telecommunication provider—includingthe access costs.Please contact AEMO’s Support Hub to find out if AEMO supports yourpreferred technology for a dedicated link.

VPN LANto LAN

Permanent VPN LAN to LAN is quick to set up. VPN connections are set up directlybetween the participant and AEMO.The connection is from the participant firewall, using the internet, to AEMO’sVPN Concentrator. Internet VPN is by use of a firewall, router, or VPN device,which has access to the internet.This connection allows multiple servers at the participant site to establishconnections with AEMO servers securely using the internet. This connectiontype provides a similar service to dedicated links. An IPsec-compliant VPNdevice is required at the participant site to enable this type of connection.

VPNvariable

Variable Internet Variable VPN connection from a workstation, using the internet, toVPN Concentrator. InternetWorkstation VPN requires installation of a CiscoVPN client software package. For security reasons, the connection drops ifthere is no activity for 30 minutes.The workstation connection operates like a dial-up MarketNet connection. Itallows individual workstations in a participant company to establishconnections with AEMO servers.The AEMO preferred method to enable this type of connection is to installCisco VPN client software, available for Windows and Unix-like systems.AEMO supplies this software, pre-configured for your use, in conjunction withat least one RSA SecurID token.

Registered participant entitlements

Because it is a resource shared by all participants, the Bandwidth Pricing Modelis the method employed by AEMO to fairly manage the usage of MarketNet.Participant entitlements are based on registration status, and participant fees paidin any combination of the electricity or gas markets.

For more details about fees, see the Budget and Fees.

© 2017 AEMO 23


http://www.aemo.com.au/About-AEMO/Energy-Market-Registration/Current-Energy-Market-Budget-and-Fees

Connection entitlements

Each company ABN registered with AEMO is entitled to two permanentconnections, and two variable VPN connections (two tokens).

AEMO understands that some participants have legacy arrangements that do notfit these entitlements, therefore considers variations on a case-by-case basis.

Costs associated with the implementation of data communications betweenthe participant company and AEMO are the responsibility of the participantcompany. Participants are responsible for arranging and maintaining theirequipment and software, and any telecommunications infrastructure neededto connect to AEMO’s points of presence (POPs).

Bandwidth entitlements

Each company ABN registered with AEMO is allocated bandwidth according totheir total fees paid per year.

The following table provides an indication of the bandwidth entitlements availablefor participants.

Table 8 participant bandwidth entitlements

Total fees per year Entitlement

$0–$500,000 2 x 256k permanent and 2 x 256k variable connections

$500,001–$1,000,000 2 x 512k permanent and 2 x 256k variable connections

over $1,000,000 2 x 1024k permanent and 2 x 256k variable connections

AEMO initially provides 256 kbps bandwidth. This has proven sufficient for newcompanys commencing participation in the market.

For example, a company with a registered ABN in:

l The National Electricity Market, paying total fees of $400,000 per year, isentitled to 2 x 256k permanent and 2 x 256k variable connections.

© 2017 AEMO 24


l Any gas market combination of, the Declared Wholesale Gas Market, a RetailGas Market, and the Short Term Trading Market, paying total fees of $800,000per year, is entitled to 2 x 512k permanent and 2 x 256k variable connections.

l The National Electricity Market and any Gas Market combination, paying totalfees of $1,100,000 per year is entitled to 2 x 1024k permanent and 2 x 256kvariable connections.

Participants can apply for additional connections or bandwidth in excess ofthe entitlements, see Unregistered participant access requests below.

Unregistered participant access requests

AEMO’s Support Hub handles requests for network connections and public dataaccess from unregistered companys, or third parties providing services toregistered participants. Third parties who require a MarketNet connection mustpay for their network connection and arrange access credentials with theparticipants they represent.

AEMO considers requests on a case-by-case basis, and, if applicable, providesan access application form and a data access agreement to complete and return.

There is an annual prepayment for this service, payable in advance, see Table 9.Please provide relevant company details, and outline your reason for requiringaccess in an email.

Table 9 annual prepayment options

Option Bandwidth(kbps)

Fee per year + GST

Up to 2 permanent connections (plus up to 2 variableVPN connections)

256 $17,000

1024 $51,000

1 VPN variable connection 256 $5,000 ($300 for eachsubsequent connection –includes 1 token)

1 VPN variable connection for public researchers toaccess confidential intermittent generation data only (e.g.wind and solar).

128(for up to100 GB peryear)

$1,000 (includes 1 token)

© 2017 AEMO 25


mailto:[email protected]

AEMO’s website has public data available at no cost, see Market Data.

Additional connection and bandwidth

To provide the connection points with increased capacity, AEMO chargesadditional service fees on a cost recovery basis.

Table 10 additional connection and bandwidth options

Options Bandwidth (kbps) Fee per year + GST

Extra bandwidth on existing connection 256 kbps $17,000

Extra bandwidth on existing connection 1024 kbps $51,000

Additional connection 256 kbps $17,000

Additional connection 1024 kbps $51,000

Additional variable connection VPN 256 kbps $300 for each variableconnection (token)

Making changes to your MarketNet connection

To make changes to your MarketNet connection, send the completed MarketNetConnection Request Form MarketNet Connection Request Form by email toAEMO’s Support Hub.

After receiving your request, AEMO’s technical network officer contacts yourtechnical network contact to finalise specific details of the connection (such as IPaddressing details).

Your request must comply with theRegistered participant entitlements onpage 23.

© 2017 AEMO 26


http://www.aemo.com.au/About-the-industry/Information-Systems


CHAPTER 5 MARKET DATA

Website data 27Current data 27Historical data 28Data sharing 28

Website dataAEMO's website has the same data as distributed through the participant fileserver with the exception of participant’s private data. The data is mostly in CSVformat with some graphical summaries. Data retention depends on the file type,for example, Dispatch files are kept for 2 days. The section for each file typeexplains how long each file remains in the current directory.

See Electricity Data on AEMO's website.

Current dataIn the same folder as the participant ID’s file server folders, AEMO updates the\MarketData\Baseline folder daily with current baseline data conforming to theData Model.

The baseline data files are in a format suitable for loading to relevant databasetables by copying each file into the input folder for the Participant DataReplication Loader.

Use the baseline data for initial population of a new instance of a databaseconforming to the Data Model or for re-population of existing tables.

For help, see Guide to Data Interchange or Guide to Participant DataReplication Loader.

Baseline data excludes historical data, see Historical data on the next page.

© 2017 AEMO 27

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 5 MARKET DATA


http://www.aemo.com.au/About-the-Industry/Information-Systems/Data-Interchange

Historical dataOlder files are moved to the Reports Archive and kept for 13 months. The dataconforms to the Data Model.

The archive data is not intended for the historical recovery of public data for adatabase receiving a data feed using Data Interchange. It is a source forobtaining historical data for analysis of runs and includes:

l Non-confidential historical data for the Data Model in .CSV format. Some filesare in a format incompatible with the pdrLoader configured for data interchange.

l Other Historical Data – .CSV Files. Non-MMS Data Model non-confidentialhistorical data in .CSV Files.

To obtain historical data, see Reports archive

Data sharing

About data sharing 28Data sharing example 30Data sharing set-up 31Data sharing removal 32

About data sharing

Data sharing is handled using Data Interchange. A data sharing requirement mayemerge, for example, due to a merger with, takeover of, or sale of anotherparticipant ID. The requirement met by implementing data sharing is to use oneparticipant ID’s IT system to manage access and process the data for two or moreparticipant IDs using one participant ID’s set of folders in the participant fileserver.

Sharing data achieves the business outcome of having just one Data Interchangesystem to produce a Data Model database containing the data for two or moreparticipant IDs. The only other way to achieve the same objective is to have aData Interchange system for each participant ID, then have a back-end process tomerge each of the single participant ID databases into a common database.

© 2017 AEMO 28


AEMO’s wholesale energy market systems allow a participant ID to share datawith another participant ID, subject to an authorised request. Implementing datasharing means the full Data Interchange data set (including private data) for therequesting participant ID is made available to another participant ID’s set offolders in the participant file servers, as nominated in the request. The sharing ofdata is for both pre-production and production.

A key saving is the bandwidth and download time for the public data, since it iscommon to both participant IDs. Having all the data in one database can be bothan advantage and a disadvantage.

It is possible to arrange for one participant ID to receive data for more than oneother participant ID or to arrange for both participant IDs to get the data for bothparticipant IDs.

Unless specifically and clearly requested otherwise, data sharing is one-way(that is, one participant ID gets just its own data and the other participant IDgets the data for both participant IDs).

Data sharing is not cascaded. This means if a participant ID shares its data withanother participant ID, and the first participant ID is already receiving data sharedfrom a third participant ID, the data for the third participant ID is unseen by thesecond participant ID. To make the second participant ID receive the thirdparticipant ID’s data requires a specific request to AEMO by those two participantIDs.

Each participant ID can check its own data sharing status in the energy marketsystems web portal, see Figure 3.

© 2017 AEMO 29


Figure 3 data sharing in the energy market systems web portal

Data sharing example

For example, participant ID 1 wishes to manage both participant ID 1 andparticipant ID 2 data using participant ID 1’s IT systems and access mechanism.

l After requesting set-up by AEMO, participant ID 2’s data is made available toboth participant ID 1 and participant ID 2 file folder sets.

l AEMO delivers to participant ID 1: PUBLIC-DATA.ZIP and PARTICIPANT1_DATA.ZIP (includes both participant ID 1 and participant ID 2 data).

l AEMO delivers to participant ID 2: PUBLIC-DATA.ZIP and PARTICIPANT2_DATA.ZIP (includes only participant ID 2 data).

l Each participant ID can independently manage which data packages theyreceive for their participant ID via EMMS Data Subscription services. Aparticipant ID receiving data for another participant ID does not impact the otherparticipant ID’s file subscriptions.

l If participant ID 2’s files are not removed by participant ID 2, AEMO purges filesolder than a couple of days.

© 2017 AEMO 30


Data sharing set-up

Sharing Data Interchange data from another participant ID means you must havea data interchange implementation configured at your site and the DataSubscription web application set-up.

To set up data sharing, understand what you wish to achieve and ensure your ITsystems can process data for multiple participant IDs from the one file. Ensuredownstream processes, procedures, and systems can handle the database withdata for multiple participant IDs.

Participant companies with the same ABN for all participant IDs only need asingle request from the company registered for their participant IDs.

After confirming full agreement by all affected parties, on or after the requestedimplementation date, AEMO processes the data sharing request into pre-production, and advises completion to the requestor.

Processing the sharing request into production involves confirming full agreementby all affected parties.

To formally request data sharing:

l The formal request must nominate a business contact with the authority torequest or authorise the sharing of private data from one business entity toanother, plus nominate a technical contact to directly implement changes at theparticipant ID site needed to put the data sharing into place. The request mustspecify the earliest date for implementation in pre-production. Productionimplementation needs separate arrangement, made by agreement between allparties.

l If there are two (or more) companies (that is, having different ABNs), eachcompany must provide a request to AEMO's Support Hub, on their respectivecompany letterhead. It must be signed at senior management level and detailtheir specific circumstances. Below is an example of the authorisation required.

© 2017 AEMO 31


<Company name> < ABN>for <participant ID><requests|authorises> AEMO to make available <companyname> < ABN>for <participant ID> EMMS fullsubscription data set (including private data) to<company name> < ABN><participant ID> via the EMMSData Interchange and Data Subscription services. Thisis to remain in place until advised in writing. Aletter from <Company name> < ABN> for <participant ID>confirming this is forthcoming.

Data sharing removal

One situation requiring removal of data sharing is for a change in the legalownership or control of a participant ID involved in sharing of data. To removedata sharing at any time, only one involved participant ID needs to ask for itsremoval.

To formally request withdrawal from a data sharing arrangement, submit therequest on a company letterhead, signed at senior management level, detailingthe specific circumstances. Include the following template paragraph authorisingthe withdrawal of private data sharing.

<Company name> < ABN>for <participant ID> requestsAEMO to remove sharing of <company name> < ABN>for<participant ID> EMMS full subscription data set(including private data) from <company name> <ABN><participant ID>.

Deregistering a participant ID means all data sharing to or from that participant IDis removed.

A participant company purchasing an existing registered participant ID cancontact AEMO's Support Hub to ask if any data sharing arrangement are in placefor that participant ID, and if so, request the sharing is removed.

© 2017 AEMO 32


CHAPTER 6 SOFTWARE PACKAGESAEMO provides sample software packages to assist with data validation andreplicating data between AEMO's systems and participants' systems. Softwareversions are updated for each new release. Participants using AEMO’s softwareare responsible for ensuring they are using the current version. Change noticesand technical specifications advise participants of software changes for eachrelease. Table 11 describes the sample software packages provided by AEMO.

You can find software packages and documentation on AEMO's website >Electricity > IT systems > NEM

MSATS retail system softwareTable 11 Retail software packages provided by AEMO

B2B Validation Module An application participants can embed in their B2B systemsallowing validation of an .XML file before it is deployed to theMSATS B2B Hub.See Guide to Validation Module Software.

MSATS Participant Batcher A simple batch interface to MSATS and B2B removing the detailof the file handshaking and leaving participants to deal with theraw .ZIP files only. It transfers files using FTP from and to theMSATS hub and does the entire message acknowledgement andfile manipulations as required by the MSATS batch file interface.See Guide to Participant Batcher Software.

Web Services An additional option to AEMO’s web portals, and batch or fileinterfaces for system-to-system interaction with AEMO’ssystems. It provides supported and secure web services toparticipants’ systems using the secure MarketNet connection.See Guide to Web Services.

© 2017 AEMO 33

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 6 SOFTWARE PACKAGES


EMMS wholesale system softwareTable 12Wholesale software packages provided by AEMO

Data Interchange Data Interchange is a set of cooperating applications used to replicate, manage,and monitor data between AEMO and a participant's database conforming tothe Electricity Data Model.See Concise Guide to Data Interchange.

Web Services An additional option to AEMO’s web portals, and batch or file interfaces forsystem-to-system interaction with AEMO’s systems. It provides supported andsecure web services to participants’ systems using the secure MarketNetconnection. See Guide to Web Services.

© 2017 AEMO 34

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 6 SOFTWARE PACKAGES

CHAPTER 7 SECURITY

About security 35Participant's security responsibilities 36User Rights Management (URM) 37Understanding the set participant function 38Changing your Participant ID password 39Participant user passwords 49

About security

In accordance with security policy, AEMO routinely expires passwords for accessto AEMO systems. Expiry is normally advised through email and sent to the ITsecurity contacts set up during registration. The IT security contacts are AEMO’sprimary contact for all issues affecting the shared responsibility of security of dataand access to AEMO’s systems.

Requests from a participant ID for changes to any details affecting the dataexchange between AEMO and the participant ID are subject to verification ofauthenticity with the participant ID’s IT security contacts.

The obligations for maintaining security are shared by each participant company(and participant ID) and AEMO. Each participant company has the primaryresponsibility for password management for their Participant Users.

All data submitted to AEMO or generated by AEMO is permanently stored insecure databases. AEMO has implemented electronic, physical, andadministrative safeguards that provide a high level of data security.

These safeguards are designed to prevent unauthorised access to system data andto maintain the confidentiality of all participant information, they include:

l Passwords to authenticate participant users that must be changed regularly.

l The use of secure communication channels for exchanging secure data withauthorised data users and providers.

l Authentication before access to data is granted to a person or system.

l Controls to prevent system users with access to system application logic(programs) from unauthorised modification of associated application data.

© 2017 AEMO 35

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 7 SECURITY

l An audit system that tracks all changes to system data and records what datawas changed, when it changed, and who made the change.

System integrity is assured through disaster recovery measures, which includehardware redundancy, systematic data backup and restoration, and the mirroringand replication of data on geographically separated data storage and processingsystems.

Participants must ensure that AEMO’s market systems, encompassing bothcomputer systems and data networks are:

l Only used for activities supporting the operation of AEMO energy markets.

l Used in a way that provides confidentiality of information passing through thesystems.

l Used in a way that provides required performance and availability.

Chapter 7 summarises the security responsibilities of participants.

Participants requiring access to AEMO’s systems must read and complywith the Systems Access Policy.

Participant's security responsibilities

Table 13 participant's security responsibilities

Securitymanagement

Ensuring mechanisms are in place to protect their internal networks from unwantedtraffic using their MarketNet connection.

Ensuring mechanisms are in place to prevent the transmission of malware to AEMO’ssystems.

Ensuring traffic from the internet and their internal networks is isolated from theirMarketNet connection.

Ensuring no disruption to the availability of AEMO’s systems by utilising inappropriateprocesses such as repeated pinging, port scans and so on.

Ensuring no transmission or storage of inappropriate data.

Contacting AEMO’s Support Hub if they suspect a virus may have transported via AEMO’ssystems.

© 2017 AEMO 36


http://www.aemo.com.au/About-AEMO/Energy-Market-Registration/Understanding-Energy-Market-Information-Systems#policy

Reporting to the AEMO Information and Support Hub any known or suspected securitybreaches that could allow unauthorised access to their own or other participantcompanys data on AEMO Systems.

Providing AEMO’s Support Hub with contact details of specialist managers for escalationand resolution of identified breaches to security.

Passwordmanagement

Performing all activities using their participant IDs.

Changing passwords at least every 90 days.

Ensuring passwords are of adequate strength.It is recommended that passwords be a minimum of 12 characters long, and include acombination of numbers, upper case and lower case characters, punctuation and specialcharacters.

Ensuring no shared IDs.

Keeping passwords confidential.

Considering employee termination procedures in relation to AEMO passwords.

Market dataaccess

Respecting data access privileges and not attempting to access data they are notauthorised or entitled to access.

Ensuring that testing of interfacing applications is not permitted against AEMO’sproduction environments.

User Rights Management (URM)The user rights management system (URM) is in the MSATS web portal webportal. This system controls access for Participant Users to most applications.

The company's PA is responsible for the management of their participant user’saccess to AEMO’s systems with the exception of the PA right that is set up duringregistration.

The primary IT security contact (as nominated on the participant ID’s registrationform) is the initial PA who can set up another Participant User with the sameaccess rights (that is, another PA), unlock accounts, create new temporarypasswords, and make participant users inactive.

© 2017 AEMO 37


AEMO’s pre-production and production systems are independently controlled, soyou can have different credentials for each, even though they may initially be thesame.

User interaction with AEMO’s systems requires secure (HTTPS) access toAEMO’s private network, MarketNet with a login and appropriate accessrights,see Data network connection (MarketNet) on page 21.

Table 14 below describes the electricity user rights management process.

Table 14 user rights management for energy markets

Market Requirement

Electricity The participant administrator (PA) sets up participant users in AEMO’s user rightsmanagement (URM) system. The PA is responsible for the management of theirparticipant user’s access to AEMO’s systems.

Gas Each participant user must complete a Gas Systems User Access Request and attach itto the registration application. The form allows for access to multiple markets andmultiple companies for each participant user. For information about completing arequest, see the relevant gas market section in this document.

Understanding the set participant functionA company having multiple ABNs may have several participant IDs. The setparticipant function in AEMO's web portals allows participant users to have asingle user ID to perform work for multiple participant IDs without logging out andlogging back in again.

AEMO has made the use of single user ID logins available on the understandingthat each participant is responsible for the management of the accesses grantedto each user. Security is every user’s concern and each participant administratorhas a role in establishing and maintaining effective control of access to sensitiveinformation.

For more details about set participant, see Guide to User RightsManagement.

© 2017 AEMO 38


http://aemo.com.au/About-the-Industry/Information-Systems/Using-Energy-Market-Information-Systems

http://aemo.com.au/About-the-Industry/Information-Systems/Using-Energy-Market-Information-Systems#URM


Changing your Participant ID password

Password changers

To change your Participant ID password on the participant server, use one of thefollowing password changers:

l Web-based password changer, Using the web-based password changer onpage 41.

l Password changer application, Using the Participant File Server PasswordChanger on page 44.

Password rules

The password rules are:

l Change your password every 90 days.

l Participant users are allowed six unsuccessful login attempts in a period of 30minutes. If more than six attempts are made the account is locked. The count isreset once a participant user successfully logs in.

l To unlock an account, you must call AEMO's Support Hub and provide yourcompany's "secure code". Your company's PA can tell you the secure code ifyou do not know it.

l After a password is changed, it cannot be changed again for 24 hours. If itrequires changing during this time, contact AEMO's Support Hub.

l Whenever a participant user account is unlocked or password changed byAEMO's Information and Support Hub, the participant user must send an emailconfirming the request and stating that the request was not a security breach. Ifthe participant user suspects a security breach then they must report the matterto AEMO's Information and Support Hub immediately so that action can betaken to secure the account.

l Before changing your password, you must disconnect all mapped drives to theparticipant server.

l If you connect to MarketNet using an automatic FTP process, you must ensurethat you stop the process (well in advance of each expiry date), change thepassword, modify the process to use the new password then restart theprocess.

© 2017 AEMO 39


Password format

The password format is:

l At least eight characters long, however AEMO recommend 12 characters.

l Must contain characters from at least three of the following four character sets:

Description Examples

English upper case letters A, B, C, ... Z

English lower case letters a, b, c, ... z

Numerals 0, 1, 2, ... 9

Non-alphanumeric ("special characters") such as punctuation symbols - + !

l Do not include a space, a comma, or any of the following special characters < >&.

l Must not contain your user ID or any part of your full name.

l You cannot use a previously used password, or a variation—the systemremembers the last 12 previous passwords. The password rule algorithmchecks the new password against the previous 12 passwords and if it finds asequence of characters previously used, the password is not accepted.Examples of unacceptable passwords are:

Current password (or last 12) New password

Asdf1234 Asdf5678

Boot1234 boot4567

CarlMans12 carlmanS45

© 2017 AEMO 40


Password advice

Review the password you are currently using, and if it is not strong, change it to anappropriate combination of numbers, letters, special characters, with a length of atleast eight characters, however 12 is recommended. The strength of passwords isdependent on:

l The length of the password (the longer the better).

l The types of characters included in the password (better to include punctuation,special characters, characters, and numbers).

l The combination of characters used (it is easy to guess days of the week,names of people, any real word).

The downside of using a complex password is the potential to forget it. Do notwrite it down as this clearly reduces security, but you could use a particularpattern of keys, using the shift key or holding the ALT key down select a numberevery second or third character, and include a special character.

Select a word that is easy for you to remember, then insert numbers and specialcharacters at regular intervals (say every second or third character). As anexample a password may be Se1pt2em3be4r. (started off as the word Septemberwith a capital at the start, a full stop at the end, and the numbers inserted everytwo letters). Do not use this example as your password.

Using the web-based password changer

This section describes the steps for using the web-based password changer only.For help using the Participant File Server Password Changer, Using theParticipant File Server Password Changer on page 44.

Prerequisites

To use the web-based password changer:

l You need a PC with access to MarketNet. Participants need to ensure theyhave access to the relevant AEMO file server using MarketNet from thecomputer before testing the password change facility.

Note: the web-based password changer resides on AEMO’s secure MarketNetprivate network.

l You need Microsoft Internet Explorer with HTTP access to the IP address146.178.211.25 through your firewall.

© 2017 AEMO 41


l Remove any proxy servers and direct dial-out to your internet service provider(ISP).

l Stop all automatic FTP processes connecting to AEMO’s file server for thepassword is being changed.

Instructions

To change your participant ID password using the web-based password changer:

1. On aMarketNet-connectedmachine, open your Microsoft Internet Explorer web browser.2. In the Address field enter 146.178.211.25:

3. On your keyboard, press Enter. When the web browser connects, the EnterNetwork Password dialog box appears.

4. Enter your FTP access User Name and press the Tab key.5. Enter your Password and press the Tab key.6. Enter nemnet for theDomain and then clickOK.

7. The "MarketNet Password Change Website" displays a form, you must enter allthe information in this form. It should look similar to this:

© 2017 AEMO 42


This is your FTP access user name. It is the same user name you enteredin the Enter Network Password dialog box

8. In the NEMNET Username box, enter your user name and press the TAB keyNote: Do NOT enter "nemnet" before the username.

9. In the Old Password box, type your old password and press the TAB key.

10. In the New Password box, type the new password and press the TAB key.

11. In the Confirm New Password box, type in the new password again.

12. Click Go to submit the new password.

Important:Wait three minutes for the change to take effect on the AEMO serverbefore proceeding.

13. Completely log off MarketNet and then log back in using the new password.

You must log off to set the new password correctly.

© 2017 AEMO 43


To restart other processes (if any), on all computers connecting to the sharedfolders on the AEMO file server, modify your automatic FTP processes to use thenew password and then restart the processes.

Using the Participant File Server Password Changer

This section describes the steps for using the EMMS File Server PasswordChanger application. For help using the web-based password changer, Usingthe web-based password changer on page 41.

Prerequisites

To use the EMMS File Server Password Changer application:

l You need an installation of Participant Data Replication Batcher with standardproperties configuration file.

l A downloaded copy of the latest version of the application EMMS File ServerPassword Changer, available on Using Energy Market Systems.

l Decompress the .ZIP file to a working folder to create a .JAR file.

l The EMMS File Server Password Changer application itself requires Oracle’sJRE 6 to run. The “Oracle JRE 6” download is available from "Java SEDownloads",http://www.oracle.com/technetwork/java/javase/downloads/index.html.

l Stop all automatic FTP processes connecting to AEMO’s file server for whichthe password is being changed.

Instructions

To change your participant ID password using the EMMS File Server PasswordChanger application:

1. Double-click the installation file, FileServerPasswordChanger_<version>.jarto start the installer. This is the .JAR file decompressed inPrerequisites aboveon page 44.

© 2017 AEMO 44


http://www.aemo.com.au/About-the-Industry/Information-Systems/Using-Energy-Market-Information-Systems

2. Click Next, to see the Disclaimer.

3. Select I accept the terms of this licence agreement. and click Next to seepath selection.

© 2017 AEMO 45


4. Click Browse to select the location of the pdrBatcher installation for which thepassword needs to be updated.

5. Click Next to see the Instance Summary window.

If fields in the Instance Summary window show blank values, then a non-standard configuration is in place. This software is only suitable for updatingpasswords on pdrBatcher installations using a standard configuration.

© 2017 AEMO 46


Please ensure ALL pdrBatcher processes are stopped before continuing withthis step. Failure to stop all running processes may result in your access toAEMO’s file server in MarketNet becoming locked out.

6. Confirm the configuration details of the pdrBatcher installation for which thepassword needs to be updated and click Next to see the MarketNet passwordchange window.

7. Click the MarketNet password change page link which opens a new webbrowser window allowing the password to be changed. The process is thesame as described in Using the web-based password changer on page 41.

8. Click Next when the password update step has been completed, to see theConfiguration Options window.

© 2017 AEMO 47


9. Enter or update the required configuration details:

o Password Encryption key: the key by which to encrypt the password.o MarketNet account password: the password associated with theMarketNet user account. The password to be entered is the new password.

o Retype password: the repeat password of the field above.

© 2017 AEMO 48


10. The Processing form displays the log of configuring your software installationaccording to the selected options and settings.

If an error occurs, click Previous and correct the required settings. When theprocessing completes, click Next.To close the installer, click Done

Testing the password change

When your password change is complete, use the following steps to test if thechange worked correctly:

1. Check the new password is in the pdrBatcher .properties file.

2. Start the pdrBatcher process and confirm connectivity by viewing the logfile to ensure there are no connection errors.

Participant user passwords

Participant User password format 50

© 2017 AEMO 49


Your user ID and password is the same one for MSATS and EMMS, so changingyour password in one system, changes it in the other. Participants areresponsible for managing their own passwords.

Participant User password formatl Passwords are case sensitive.

l Passwords must be 6–20 characters long.

l Passwords must contain at least one character from at least three of thefollowing four character sets:

Description Examples

English upper case letters A, B, C, ... Z

English lower case letters a, b, c, ... z

Numerals 0, 1, 2, ... 9

Non-alphanumeric ("special characters") such as punctuation symbols - + !

l Do not include a space, a comma, or any of the following special characters < >&.

l Passwords expiry every 40 days (equals one cycle). Passwords cannot bereused in the next 12 cycles. A password can be changed before the 40 daysexpires.

l For security reasons, your user ID or the word “password” cannot be used.

l A user is allowed six attempts to log into the system before being locked out.

l If your password is forgotten or locked out, contact your company's PA. If youdon't know who that is, contact AEMO's Support Hub.

For the rules and recommendations for setting passwords to access theAEMO private domain MarketNet, see Changing your Participant IDpassword on page 39.

© 2017 AEMO 50


Change your MSATS password

This topic describes how to change your password in the MSATS web portal. Forhelp changing your password in the EMMS markets portal, see Change yourEMMS password on the next page

For help with the format, see Participant User password format on theprevious page.

1. On

the main menu, click User Profile and then click Change Password.

2. The User Profile - Change Password screen displays with your user ID pre-filled. All other fields are required.

3. Type your Current Password.

4. Type your new password. For security reasons, it must comply with thepassword guidelines, see Participant User password format on the previouspage.

5. Re-enter your new password and click Save.

© 2017 AEMO 51


6. A successful change displays a confirmation message.

Change your EMMS password

This topic describes how to change your password in the EMMS markets portal.For help changing your password in the MSATS web portal, see Change yourMSATS password on the previous page.

For help with the format, see Participant User password format on page 50.

1. On the Markets Portal menu, hover your mouse over Administration and thenclick Change Password.

© 2017 AEMO 52


2. In the Old password field, type the password you logged in with.3. In the New password field, type your new password.

4. In the Confirm new password field, type your new password again.

5. Click Change Password.

© 2017 AEMO 53


Use your new password next time you log in to the EMMS or MSATS webportals.

© 2017 AEMO 54


CHAPTER 8 SETTING UP YOUR IT SYSTEMSThis chapter describes who does what and when during registration and thesteps required for your IT team to set up your IT systems to interact with AEMO’smarket systems. Participants are encouraged to commence setting up their ITsystems in parallel with participant onboarding.

About setting up your IT 55Who does what when? 55Checklist for setting up your IT systems 56

About setting up your IT

The setting up of IT systems and the processing of registration have steps takingmany weeks, and are interdependent. IT systems setup at your end is a complexprocess and requires careful planning by an experienced IT team.

Time frames for your IT team to set up your IT systems vary according to themarket you are registering in, your organisations individual requirements, and theexperience of your IT team. Time frames are provided as a guide only.Organisations are encouraged to progress setting up their IT systems in parallelwith participant onboarding.

Who does what when?AEMO sets up the facilities applicable to the registration such as: domainaccounts, folders for batch files, and standing data in the systems, in both theproduction and pre-production environments.

Participants are responsible for the setting up of infrastructure at their end,including any network, database, and hardware requirements for both theproduction and pre-production environments.

The time frames provided to set up IT systems vary according to the market youare registering in and are a guide only. They are dependent on your individual ITrequirements and the experience of your IT team—please plan accordingly.

© 2017 AEMO 55

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 8 SETTING UP YOUR IT SYSTEMS

Figure 4 setting up IT systems timeline

IT access credentials are sent to your IT security contact during participantonboarding.

Checklist for setting up your IT systemsUse this checklist to help you plan your IT system setup. It is a generic checklistof activities required for setting up your IT systems. For more details about ITsystem functionalities, see .

© 2017 AEMO 56


Table 15 checklist for setting up IT systems

What Who How

1 Decide onnetworkconnectionoptions

Participant Identify and plan the networking and IT work at your end with yourtechnical teams. AEMO’s default connection bandwidths for newconnections are more than adequate for all circumstances, exceptthe most unusual, and can be changed later, Data networkconnection (MarketNet) on page 21.Participants arrange the subscription link, hardware, and softwarewith their chosen telecommunication provider—including theaccess costs.

2 Familiariseand plan ITsystems setup

Participant AEMO has numerous systems with multiple interfaces to providefor the needs of all participants. Careful planning is required todecide what your specific requirements are for interfacing withAEMO’s systems, for example:

l How will you replicate data between your systems andAEMO’s?

l Do you have a light demand for data transfer suitable forusing the web portal interfaces?

l Do you have a heavy demand for data transfer requiring anIT infrastructure at your end?

l Do you have an experienced IT team that can maintain theIT infrastructure at your end and update it for each six-monthly release cycle?

To familiarise yourself with AEMO’s systems for your market, readthe relevant market section in this guide.

3 Set up datanetworkconnection

ParticipantAEMO

The network connection is set up by the participant’s networkspecialist and AEMO network specialists (and any third parties asorganised by the participant) for their respective ends. Theimplementation time from point of technical network staff contactto implementation depends on such factors as:

l Connection type (VPN takes about 7 to 10 business days,Telstra advise a dedicated connection takes at least 20business days).

l Participant equipment.

l Participant configuration.

l Participant time input.

© 2017 AEMO 57


What Who How

Note: registered participants with an existing MarketNetconnection do not require another one. They can however, makechanges to an existing MarketNet connection, Making changes toyour MarketNet connection on page 26.

4 Test the datanetworkconnectioncommunicatesto AEMO

Participant Testing the network connection demonstrates a successful link toMarketNet without requiring access into the domain or systems(such as a “ping” test).

5 Set up accessto AEMO’smarketsystems

AEMO AEMO takes approximately 15 business days to set up your ITsystems access concurrently with your registration application, andyour data network connection. AEMO contacts the IT securitycontact provided in the registration application, advising the ITaccess credentials and other useful information for both pre-production and production (production is not yet activated).

6 Set up pre-production ITsystems

Participant You can now set up your required pre-production IT systems atyour end. For more details about AEMO’s market systems, see thesection in this guide for your market.

7 Set up dataexchange toAEMO

Participant Setting up data exchange to AEMO’s systems is complex andrequires careful planning by an expert IT team.For more specific details of AEMO’s data exchange systems, see therelevant market section in this guide.

8 Set up useraccess to ITsystems

Participant The IT security contact who becomes the participant administratoridentifies and sets up participant user access to AEMO’s systems,User Rights Management (URM) on page 1.

© 2017 AEMO 58


What Who How

9 Test pre-production ITsystems

Participant Using a test system connected to AEMO’s pre-production is idealfor training and familiarisation. Ensure you can see the folders foryour participant ID in each system. Access any other systemsrelevant to you. Perform all the expected operations for yourbusiness needs, such as bidding, uploading files, or reporting.Ensure your pre-production system is separate from yourproduction system.

10 Set upproduction ITsystems

Participant AEMO approves and activates your production environment after aperiod in pre-production of at least 5 to 10 business days (and maybe much longer). Set up your live systems (production) to beseparate from your test systems (pre-production). Adjust yourproduction processes based on your experience with pre-production.

11 Testproduction ITsystems

Participant You are now “live” and can access and enter data into AEMO’sproduction environment.

AEMO’s Support Hub provides more details about AEMO’s systems as partof participant onboarding.

© 2017 AEMO 59


CHAPTER 9 CONNECTING TO AEMO'S MARKETSYSTEMSThis topic explains how to connect to AEMO's IT interfaces.

Participant File Servers

About file servers

AEMO’s MarketNet provides access to folders for batch file transfer betweenAEMO and participant IDs.

Each energy market system has a file server, and each has production (live data)and pre-production (test data) folders. Each participant ID has secure read-writeaccess to their own set of folders, plus read-only access to commonly-sharedfolders that contain public data.

The private folders are for secure transfer of data between the participant IDsystems and AEMO (such as bidding and settlement invoices). For the IPaddresses, see File-based interface URLs on page 62.

Participants require the file interface for:

l Receiving dispatch data.

l Participants needing an on-going data feed of 5-minute public data, such as,traders.

© 2017 AEMO 60

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 9 CONNECTING TO AEMO'S MARKET SYSTEMS

Participant file server folders (FTP Gateway)

Each participant ID set offolders has at least twosubfolders, \import and\export, with namingrelative to the participantID. Further subfolders arefor specific subsystems.

Simplest access method

The simplest method to access participant ID folders is to use an FTP clientcapable of using passive FTP to put and get files. This is only practical for smallamounts of files and requires the participant ID user to know the login andpassword for direct access to the participant file server.

For small operators AEMO recommends using the web portal interfaces toretrieve and upload files. See Web portals on page 63.

Recommended method for large amounts of data

The recommended method for accessing the secure folders and replicating largeamounts of data between AEMO's systems and a participant's DBMS conformingto the Electricity or Gas Data Models is to use a batcher program such as Data

© 2017 AEMO 61


Interchange (DI). See Figure 5 below

Setting up Data Interchange requires planning and good IT skills, including:networking, database management, batch file management, and disasterrecovery. For more details, see Guide to Data Interchange.

Figure 5 Standard DI setup

File-based interface URLs

Table 16 File-based interface addresses

EMMS (wholesale) Production: ftp://146.178.211.63Pre-production: ftp://146.178.211.25

MSATS (retail) Production: ftp://146.178.211.205Pre-production: ftp://146.178.211.225

© 2017 AEMO 62


Table 17 below describes specific mappings, with <participant ID> being yourcompany's Participant ID.

Table 17 Specific mapping addresses

Private participant data <production or pre-production URL>/<participantID>

Market data <production or pre-production URL>/MarketData

Data to initially populate an RDBMS conforming to theData Model

<production or pre-productionURL>/MarketData/Baseline

MSATS data <production or pre-production URL>/<participantID>

Web portals

Who can use the web portals

A MarketNet connection is required to access the web portals. If your company isa registered participant, you probably already have access. For help, see Datanetwork connection (MarketNet) on page 21

Your company's participant administrator (PA) can advise what access you have.An initial PA is set up by AEMO as part of participant onboarding, if you don'tknow who it is, AEMO's Support Hub can advise you.

Your company's PA also provides your company's participant users with theiraccess rights to AEMO's IT systems. For help, seeUser Rights Management(URM) on page 37.

Web portal requirements

The web portals are accessed using a web browser and require:

l The website address where the application is located on AEMO’s network.SeeWeb-based interface URLs on the next page.

l The web portals supports the current and previous versions of Microsoft InternetExplorer (IE11/Edge) and Google Chrome.

© 2017 AEMO 63


l Access to MarketNet; if your company is a registered participant, you probablyalready have access because it is set up during participant onboarding. Formore details, see Data network connection (MarketNet) on page 21.

l A user ID and password provided by your company's participant administrator(PA) who controls access to AEMO's web portals. For more details see UserRights Management (URM) on page 37.

AEMO's web portals run on Windows and Unix-like operating systems.

Accessing the web portal

Follow these steps to gain access to an AEMO web application:

1. Check that you have the items listed in Web portal requirements on theprevious page.

2. Decide on the required application, for help see Guide to Information Systems.

3. Download the relevant guide containing information about the user rightsaccess your participant administrator (PA) requires to set you up. You can findguides on AEMO's website.

4. Ask your company's PA to give you user rights access to the application. If youdon't know who your company's PA is contact AEMO's Support Hub.For help setting up user rights access your company's PA can reference theGuide to User Rights Management.

5. Access the web portal. For help, see Web-based interface URLs below.

Web-based interface URLs

Table 18 below lists the URLs for electricity market IT systems.

Table 18 AEMOweb-based URLs

Name URL

Web portal menu (links to allparticipant web portals)

https://menu.prod.marketnet.net.au/https://menu.preprod.marketnet.net.au/

EMMSMarkets Portal (wholesale) https://portal.prod.marketnet.net.au/https://portal.preprod.marketnet.net.au/

EMMSMarkets Portal Help https://portal.prod.marketnet.net.au/help/

© 2017 AEMO 64




https://menu.preprod.nemnet.net.au/

https://portal.prod.marketnet.net.au/

https://portal.preprod.nemnet.net.au/

Name URL

https://portal.preprod.marketnet.net.au/help/

MSATS and B2B e-Hub (retail) https://msats.prod.nemnet.net.au/https://msats.preprod.nemnet.net.au/

NOS pre-production https://nos.prod.nemnet.net.au/https://nos.preprod.nemnet.net.au/nos/

Domain account password change http://146.178.211.25For help, see Changing your password on the Participant Server inGuide to Information Systems

Web Services

About web services

AEMO provides supported and secure web services to participants’ systemsusing the secure MarketNet connection. AEMO’s web services use existingmessaging standards such as aseXML and CSV, maintaining maximum flexibilityand consistency for participants who are free to specify data formats or payloadsthat suit the target system. The market system's standard is the transfer ofaseXML and ebXML documents between participant gateways and the marketsystems.

For more information, see Guide to Web Services.

Web services requirements1. The web portals supports the current and previous versions of Microsoft Internet

Explorer (IE11/Edge) and Google Chrome.

2. AEMO’s Web Services are accessed using your MarketNet connection.

3. The Web Services Client Software runs on either the Java TM Platform,Standard Edition 7, or the Microsoft .NET Framework 4®.

© 2017 AEMO 65


https://mms.preprod.nemnet.net.au/mms/

https://msats.prod.nemnet.net.au/

https://msats.preprod.nemnet.net.au/msats/

https://nos.prod.nemnet.net.au/

https://nos.preprod.nemnet.net.au/nos/

http://146.178.211.25/

http://www.aemo.com.au/Electricity/National-Electricity-Market-NEM/IT-systems-and-change

http://www.aemo.com.au/Electricity/National-Electricity-Market-NEM/IT-systems-and-change

4. A user ID and password, provided by your participant administrator (PA), set upwith access to the required web service.User accounts and user administration are done in the MSATS energy marketsystems web portal. PAs select the appropriate entity in the Maintain Rightsmenu.

You can find each web service URI in Guide to Web Services.

For help with user accounts and administration, see Guide to User RightsManagement.

API gateway

About the API Gateway

The API Gateway is a communication option for participants using web servicesor using direct connections from a compatible participant gateway. It is accessibleover the internet or MarketNet.

For more details, see Shared Market Protocol (SMP) Technical Guide and theNational Electricity Rules.

API gateway system requirements

AEMO provisions the SSL certificates and API Key as part of the B2Baccreditation process.

Access to the API gateway requires:

l Your MarketNet connection or secure internet access.

l An SSL authentication using digital certificates.

l An API Key provided by AEMO.

l Your IP address range white listed by AEMO.

© 2017 AEMO 66


http://aemo.com.au/About-the-Industry/Information-Systems/Using-Energy-Market-Information-Systems/User-Rights-Management

http://aemo.com.au/About-the-Industry/Information-Systems/Using-Energy-Market-Information-Systems/User-Rights-Management

l Successful completion of B2B Accreditation. For more details see Guide toB2B e-Hub Self-Accreditation.

For the API Gateway to connect to a participant's API, participants must configure:

l An SSL authentication using digital certificates.

l Provide an API Key to AEMO (optional).

© 2017 AEMO 67


CHAPTER 10 SYSTEM TRANSFERS ANDDEREGISTRATION

System transfers

AEMO operates duplicates of systems. Occasionally, AEMO advises (by email) ofa planned changeover from an operational system to an alternative. AEMOperforms the changeovers in a way to minimise market impacts. However, therecan be times when particular functions are interrupted or are temporarilyunavailable, as advised by email. participant ID systems and processes need tocater for such interruptions to AEMO services. Some examples of effects include:

For MSATS, a changeover can result in no connection to AEMO’s MSATS fileserver for up to 10 minutes whilst B2B data synchronises. This impacts both the“Participant Batcher” and B2B. Because applications and web browser sessionscan lose connection, they may require a restart from the participant ID end. Anyunacknowledged files require resubmission by the participant ID, because, ineffect, they have been lost in transit.

For EMMS, any files in participant ID folders are ignored when changing over,except that settlement files are moved to the fresh system. Therefore, it is veryimportant to keep checking for, and moving, participant ID files, either manually orusing automated processes.

When there is a planned outage of one of AEMO's internet links by the carrier,AEMO advises alternative arrangements for the duration of the outage.

Deregistration for IT systems

Deregistration is like a transfer, except there is no transferee see,Guide toMarket Systems - NEM Change of Ownership. Effective on the date ofderegistration, effects include:

l Data sharing to and from the deregistered participant ID is removed.

l Access to AEMO’s file servers by the deregistered participant ID is revoked.

l Any subsequently produced statements and reports are unavailable, becausethere is no primary delivery point.

© 2017 AEMO 68

GUIDE TO ELECTRICITY INFORMATION SYSTEMSCHAPTER 10 SYSTEM TRANSFERS AND DEREGISTRATION

http://www.aemo.com.au/Electricity/Registration/Application-Forms/Generator

http://www.aemo.com.au/Electricity/Registration/Application-Forms/Generator

NEEDING HELP

AEMO's Support Hub 69Communications 70Feedback 71Related resources 71

AEMO's Support Hub

Contacting AEMO's Support Hub

IT assistance is requested through one of the following methods:

l Phone: 1300 AEMO 00 (1300 236 600)

For non-urgent issues, normal coverage is 8:00 AM to 6:00 PM on weekdays,Australian Eastern Standard Time (AEST).

l Email: [email protected]

AEMO recommends participants call AEMO's Support Hub for all urgent issues,whether or not you have logged a call in the Customer Portal.

Information to provide

Please provide the following information when requesting IT assistance fromAEMO:

l Your name

l Organisation name

l Participant ID

l System or application name

l Environment: production or pre-production

© 2017 AEMO 69

GUIDE TO ELECTRICITY INFORMATION SYSTEMSNEEDING HELP

l Problem description

l Screenshots

For AEMO software-related issues please also provide:

l Version of software

l Properties or log files

l Replication Manager support dump and instance name (if Data Interchangeproblem)

Communications

AEMO's Support Hub send emails, including:

l MarketNet password expiry reminder: An automated password expiry reminderis sent when a MarketNet account password has five or less days to expire.This is directed by default to AEMOexpiry@your_domain.com.au.

l Release schedules: Sent immediately when a change notice is issued toadvise of any changes in AEMO's IT systems. This is directed by default toAEMOHelpDeskComms@your_domain.com.au. You can also find releaseschedules and technical specifications on AEMO's website > IT Change andRelease Management.

l Technical specifications: Detailed information about the changes affectingparticipants' IT systems for each six-monthly release.

l AEMO's Support Hub bulletin: Advises participant of updates, outages, andparticipant user group meetings. It contains a copy of any issued change noticeor technical specification. This is directed by default toAEMOHelpDeskComms@your_domain.com.au.

Your IT staff can set up and maintain appropriate distribution for the generic emailaddresses to suit your business needs. If you need to discontinue or change theemail address of any of the above communications, advise AEMO's SupportHub (note individual email addresses are not accepted).

AEMO systems can also send emails containing reports; some manually initiatedby AEMO staff and some automatically generated by specific applications. Forexample, the energy market systems can notify nominated email addresses ofcertain settlements-related information, managed by the relevant web applicationfrom input by participant ID users.

© 2017 AEMO 70




FeedbackYour feedback is important and helps us improve our services and products. Tosuggest improvements, please contact AEMO's Support Hub.

Related resourcesThe resources listed in this section contain related information that may assistyou.

aseXML Standards, links to guidelines, schemas, change process, sample files,and white papers.

Baseline data, data files in a format suitable for loading to participant's DBMconforming to the data model. The data is in the same folder as the participantID’s file server folders, AEMO updates the \MarketData\Baseline folder dailywith current baseline data.

B2B Validation Module Software and Guide, a validation applicationparticipants can embed in their B2B systems to validate an .XML file before it isdeployed to the B2B e-Hub.

Electricity Data, publicly available market data at no cost. The public datapublished on AEMO’s website is the same as distributed through the participantfile server with the exception of participants' private data. The data is in CSVformat in many files along with some graphical summaries.

Guide to Data Interchange, assists participants to understand AEMO's DataInterchange software components. It describes how to set up a standard DataInterchange environment to replicate data between AEMO's energy marketsystems and participants' local DBMS conforming to the MMS Data Model.

Guide to B2B e-Hub Self-Accreditation, assists intending B2B e-HubParticipants to understand the B2B e-Hub (e-Hub) self-accreditation process.

Guide to MSATS and B2B Terms, defines the terms in the electricity retailmarket.

Guide to User Rights Management, assists Participant Administrators tomanage their participant user's access to AEMO’s systems. It also explains howto set up single user IDs for use with the Set Participant function in AEMO’sweb portals.

© 2017 AEMO 71


Guide to Web Services, explains AEMO's available web services and theparameters required to access them.

Historical data, older files are moved to the Reports Archive and kept for 13months. The data is in CSV format and conforms to the Data Model. To obtainhistorical data, see http://www.nemweb.com.au/Reports/ARCHIVE/.

List of National Electricity Market Procedures, guidelines and documents,provides a list of procedures authorised under the NER.

MarketNet Connection Request, use this form to apply for a new MarketNetconnection, or to make a change to an existing MarketNet connection. The formprovides for all types of changes to existing network connections, includingbandwidth changes, participant IP changes, and adding another connection.

MSATS guides, information and assistance for using MSATS. Electricity > Retailand Metering > Market Settlement and Transfer Solutions.

MSATS Participant Batcher Software and Guide, sample software and guide forusing the MSATS file interface.

Participant Information, information about participant categories and registeringin energy markets: Electricity or Gas> Participant Information.

Shared Market Protocol (SMP) Technical Guide, provides participants with thetechnical specifications for the delivery of B2B transactions using the B2B e-Hub APIs. This detail assists participants developing their own systems toutilise these APIs.

Systems Access Policy, the Rules requires AEMO and Registered Participantsto comply with the Systems Access Policy and Procedure for access to AEMO'ssystems.

© 2017 AEMO 72


http://www.nemweb.com.au/Reports/ARCHIVE/

© 2017 AEMO 73


AAccelerate

A process initiated by AEMO to complete In-pro-gress Change Requests following a ROLREvent, allowing for: • Completion of ChangeRequests otherwise requiring the MDP to submitthe Actual Change Date, where that date is notyet submitted. • Specification of an ActualChange Date (RoLR Effective Transfer Date) tosupersede any existing Proposed Change Dateor Actual Change Date on the Change Request.

Accumulation MeterA device complying with Australian Standards,containing a measurement element(s) and arecord of the accumulated quantity of the elec-tricity flowing through the power conductor. Alsoknow as a basic meter.

ACKA file with a filename extension of .ACK; the filecontains an aseXML message to acknowledgeanother file.

ACMAAustralian Communications and Media Author-ity.

Actual Change DateThe effective date of changes specified in aChange Request. The same date as theFromDate in a C4 Report and the Start Date inMSATS interfaces displaying NMI master data.

Actual End DateA date specifying the end of a period whenupdating existing data in CATS. It is only spe-cified in a Change Request for a RetrospectiveChange correcting a past error.

Actual Meter Read DateThe date an actual meter reading is obtained.

Actual Meter ReadingThe accumulated metering data or interval meter-ing data collected from a meter either manuallyor by remote acquisition (as applicable).

Actual Metering DataAccumulated metering data or interval meteringdata that has passed Validation without Sub-stitution.

ADLAverage Daily Load; the electrical energydelivered through a metering point’s datastreams over an extended period, normalised toa “per day” basis.

AEMCAustralian Energy Market Commission

AEMOAustralian Energy Market Operator

AEMOCommunicationAn email from AEMO to a distribution list ofRegistered Participant contacts broadcastingNEM-related information.

AEMO Security ModelThe entities and rights assigned to participantsto maintain access rights to different parts of thesystem.

AESAdvanced Encryption Standard

AESTAustralian Eastern Standard Time

APIApplication Programming Interface; a set ofclearly defined methods of communicationbetween various software components.

API GatewayUsed to push or pull messages from the B2B e-Hub queue using RESTful APIs.

API ProtocolA B2B e-Hub delivery method.

Asset Management StrategyA strategy for the testing of metering installationssubmitted by an MC and approved by AEMOunder clause S7.6 of the NER.

BB2B

Business-to-business communication

B2B e-HubAn electronic information exchange platform facil-itating B2B Communications.

GLOSSARY

© 2017 AEMO 74

B2MBusiness-to-Market

Backup ROLRAs defined in the AER RoLR Guidelines.

Basic MeterA device complying with Australian Standards,containing a measurement element(s) and arecord of the accumulated quantity of the elec-tricity flowing through the power conductor. Alsoknown as an accumulation meter.

Basic Meter ProfileA party that applies a profile shape to a BasicMeter read to produce calculated interval data.

Batch EntityA right type assigned to a user, allowing the useof the Batch Transaction Handlers.

Batch Entity TableThe table that allows execute access to batchcommands to be assigned to a user right.

Batch Handler TransactionsCommunication between participant ID foldersand AEMO. Each participant ID set of folders hasat least two subfolders, \import and \export, withnaming relative to the participant ID.

BBBulletin Board

BCTBulk Change Tool: A component of MSATS usedby AEMO to make bulk changes to data withoutrequiring the submission of Change Requests.

BidOffer (as in NER)

BMPBasic Meter Profile: The application of profileshape data to accumulated metering data to cre-ate half-hourly interval metering data for a ProfileArea.

BundlingA function in MSATS where AEMO bundlesMSATS Change Request Notifications. Thismeans that instead of sending Change Requestnotifications as individual XML messages con-taining a single transaction, many can bebundled into a single XML message (one mes-sage, with multiple transactions, in a single file).

BusinessAs defined in the NERL.

Business DayAs defined in the Rules. [A day other than aSaturday, or Sunday or a day which is lawfullyobserved as a national public holiday on thesame day in each of the participating jur-isdictions.

Business GroupA group of participant companies (each withtheir own Participant IDs) that are part of a singlecommercial enterprise.

Business HourA period of one hour within a business day.

CC4 Report

An MSATS report that containing current CATSStanding Data for one or more NMIs.

CancelledA status of a Change Request.

Category AA category of MP accredited to install whole cur-rent meters of a manually read metering install-ation only.

Category BA category of MP accredited to provide, install,and maintain a metering installation.

Category CA category of MDP accredited to collect meteringdata from manually read metering installationsonly.

Category DA category of MDP accredited to provide meter-ing data services related to the collection, pro-cessing, storing, and delivery of metering data.

CATSConsumer Administration and Transfer Solutionincludes the Participant Life Cycle, CATS, andNMI Standing Data management.

CATS ParticipantAs defined in the MSATS Procedures: CATS Pro-cedures. Any organisation that has a definedrole in the MSATS system, see role.


© 2017 AEMO 75

CATS ProceduresMSATS Procedures: CATS Procedure Principlesand Obligations

CATS Standing DataThe data held in the following database tables: •CATS_NMI_Data_Stream • CATS_NMI_Data •CATS_Meter_Register • CATS_NMI_Par-ticipants_Relationships • CATS_Register_Iden-tifier NMI Standing Data is a sub-set of the CATSStanding Data.

CATS Standing Data Access RulesThe rules specifying which CATS Standing Datacan be accessed, as specified in section 41.5 ofthe CATS Procedures.

Change Reason CodeA code that identifies a type of Change Request.It defines rules such as what NMI informationcan be updated and which roles will receive aChange Request Notification each time theChange Request Status is updated.

Change RequestA transaction submitted by participants inMSATS whenever they want to create or updatedata held in MSATS.

Change Request NotificationA notification generated by MSATS and providedto one or more participants as a consequence ofa change of status of a Change Request.

Change Request StatusThe nominated status in the Change Requestlife cycle. Can be one of the following statuses:Requested, Pending, Completed, Objected, Can-celled, or Pending Validation.

Change Request Status Notification RulesRules that specify which roles are advised whena Change Request undergoes a change instatus, as described in the CATS Procedures foreach Change Reason Code.

ChecksumSee NMI checksum.

Child NameThe Embedded Network Code populated in theEmbNetChild field in MSATS for a Child NMI toindicate that the NMI is a child for a specifiedembedded network.

Child NMIThe NMI assigned to a child connection point.

CLPControlled Load Profile; a type of load profile cal-culated in accordance with the Metrology Pro-cedure.

CompletedOne of the status points of a Change Request.

ConsumerAn end use customer of energy.

ContactExternal and internal business contacts, similarin functionality to an address book. A contactmay be an internal contact within the participantorganisation, or could be an external contactbelonging to another market participant.

ContestableRelates to transmission services or distributionservices; a service permitted by the laws of therelevant participating jurisdiction to be providedby more than one service provider as a con-testable service or on a competitive basis.

Controlled LoadLoad controlled by the metering installation (e.g.frequency injection relay or time clock) and maybe separately metered from the remaining loadat a metering point. The majority of ControlledLoads are associated with off-peak hot water,pool pumps, and air-conditioning units.

Controlled Unmetered DeviceAn Unmetered Device that has a predictableload and is switched in accordance with anOn/Off Table (e.g. street lighting).

Cooling-off PeriodIn the NEM (except Victoria): as defined in theNERR. In Victoria: As defined in the EnergyRetail Code published by the Essential ServicesCommission of Victoria.

CRChange Request

Create PrivilegeProvides the participant user the access right tocreate records represented by an entity.

CSVComma Separated Values; a file format for datausing commas as delimiters.

CTCurrent transformer


© 2017 AEMO 76

CurrentThe participant can receive files compliant to thecurrent aseXML version.

Current FRMPAs defined in the MSATS Procedures, CATS Pro-cedures. The retailer identified on the currentNMI master record.

Current LNSPAs defined in the MSATS Procedures, CATS Pro-cedures. The LNSP identified on the current NMImaster record.

Current MDPAs defined in the MSATS Procedures, CATS Pro-cedures. The MDP identified on the current NMImaster record.

Current PartyThe entity associated with the meter installationand retail arrangements of a consumer.

Current RetailerSee current FRMP

Current RPAs defined in the MSATS Procedures, CATS Pro-cedures. The RP identified on the current NMImaster record.

Customer Classification CodeA code used in MSATS to determine the clas-sification of an End User. For more information,see the CATS Procedures.

Customer Threshold CodeA code used in MSATS to determine the con-sumption for an End User at a single connectionpoint. for more information, see section theCATS Procedures.

DData Interchange

A set of cooperating applications used to rep-licate data between AEMO's energy market sys-tems and a participant's DBMS conforming to theMMS Data Model.

Data RequestA transaction initiated by MSATS and sent to aparticipant at the Pending Validation status ofthe Change Request life cycle.

Data sharingEach participant ID can share their data withother participant IDs, subject to an authorised

request. Implementing data sharing means thefull Data Interchange data set (including privatedata) for the requesting participant ID is madeavailable to another participant's sets of foldersin the EMMS file server, as nominated in therequest. The sharing of data is for both pre-pro-duction and production. A data sharing require-ment may emerge, for example, due to a mergerwith, takeover of, or sale of another registeredparticipant. The requirement may be to use onecompany's IT system to manage access, and pro-cess the data for two or more participant IDsusing just one participant IDs set of folders in theEMMS file server. The Data Interchange webapplication in the Markets Portal provides thestatus of any data sharing agreements you haveimplemented.

Data StreamA stream of metering data associated with a con-nection point, as represented by a NMI. A NMIcan have multiple data streams (e.g. from one ormore meters, or from one or more channels orregisters that comprise a single meter). Eachdata stream is identified by a unique suffix asso-ciated with the NMI.

Data stream Status CodeA code used in MSATS to indicate whether aData stream is used in settlements. For moredetails, see the CATS Procedures.

Data SubscriptionA web application in the Markets Portal used tosubscribe to Data Interchange files and to obtainthe latest MMS Data Model. These files are typ-ically csv files containing public data and par-ticipant’s private data. AEMO recommendsparticipant use of the Data Interchange suite ofproducts, supplied by AEMO, to automate receiv-ing and storage of the files to their systems.AEMO provides working sample software forFTP access (Participant Batcher) to MarketNetand working sample software for Data Inter-change.

DBMSDatabase management system

Default and Deregistration ProcedureProcedure for Metering Providers, Metering DataProviders, Embedded Network Managers andMetering Coordinators.

Delete PrivilegeProvides the participant user the access right todelete records represented by an entity.


© 2017 AEMO 77

DIData Interchange

DLFDistribution Loss Factor

DLF CodeA code used in MSATS to identify a distributionloss factor.

DPIDDelivery point identifier; an Australia Postassigned identifier that is a numeric descriptorfor a postal delivery point equal to a physicaladdress.

DSDispatch

DUIDGeneration Unit ID

DWGMDeclared Wholesale Gas Market (Victoria)

EEENSP

Exempt Embedded Network Service Provider

Embedded Network CodeA code used in MSATS to identify an embeddednetwork.

EMMSWholesale Electricity Market Management Sys-tem; software, hardware, network and relatedprocesses to implement the wholesale energymarket.

EMMS Markets PortalWeb portal for access to AEMO's wholesaleweb-based applications.

End-use CustomerThe person consuming the electricity at the con-nection point, see B2B Procedures: ServiceOrder Process.

EntityThe individual components or building blocks ofthe MSATS system, representing individualpieces of functionality. Some examples of entit-ies are the menu options available on theMSATS main menu (ombudsman, role assign-ment, create participant, CATS reports and soon).

Estimated ReadingAn estimate of a Meter Reading where an ActualMeter Reading for a period in the past is notavailable.

EstimationThe forward estimation of metering data.

Exemption GuidelineExemption Guideline forSmall Customer Meter-ing Installation.

Exemption ProcedureExemption Procedure for Metering InstallationMalfunctions.

Explicit Informed ConsentIn the NEM, apart from Victoria, as defined in theNERL. In Victoria, as defined in the EnergyRetail Code published by the Essential ServicesCommission of Victoria.

FFailed Retailer

A retailer that is the subject of a RoLR Event.

FCASfrequency control ancillary services

Field Validation RulesAs described in the CATS Procedures, they spe-cify, for each Change Reason Code, the fields inMSATS populated at the creation of a trans-action or at other times in the life cycle of a trans-action.

Final ReadingThe last Actual Meter Reading taken where anEnd User vacates an address, changes retailer,all or any part of a metering installation isremoved, or modified and the modificationaffects the energy data in the metering install-ation.

First-Tier Controlled LoadA Controlled Load that is a first-tier load. For thepurposes of the Metrology Procedure, a first-tierload also includes the electricity purchased at aconnection point directly and in its entirety fromthe Local Retailer even if it is not classified.

First Tier CustomerAn end use customer whose energy retailer isthe local retailer.


© 2017 AEMO 78

First Tier NMIThe electricity associated with a first tier NMI(classified as a first tier load) is purchased at aconnection point directly and in its entirety fromthe local retailer.

FTPFile transfer protocol

FTP GatewayUses the MSATS Hokey-Pokey protocol todeliver B2B communications.

FTP ProtocolA B2B e-Hub and EMMS delivery method.

GGBB

Gas Bulletin Board

GELFGenerator Energy Limitation Framework Para-meters

Good Industry PracticeIn relation to any undertaking and any cir-cumstances, the exercise of that degree of skill,diligence, prudence, and foresight that wouldreasonably and ordinarily be expected from askilled and experienced operator engaged in thesame type of undertaking under the same or sim-ilar circumstances.

GSHGas Supply Hub

HHistorical Data

Metering data provided for a previous readingperiod.

Host RetailerSee local retailer

HTTPSHypertext Transfer Protocol Secure, adds thesecurity capabilities of SSL to standard HTTPcommunications.

HVHigh voltage

HV CTHigh voltage current transformer

IILAC

International Laboratory Accreditation Coop-eration

Implementation dateUsually one business day before the effectiveregistration date of a registration change. Uponspecial request, AEMOmay agree to imple-mentation two business days before the effectiveregistration date, given sufficient notice time tocomply with the Rules and Change Man-agement Procedures.

Initiation RulesAs described in the CATS Procedures, the rulesthat specify who can initiate a Change Requestin MSATS.

Insolvency OfficialAn official appointed in respect of a retailer orany property of the retailer and includes areceiver, receiver and manager, administrator,provisional liquidator, liquidator, trustee in bank-ruptcy or person having a similar or analogousfunction.

Interactive EntityA right type assigned to a participant user toaccess the B2B Web Browser or Web Services.

Interactive Entity TableThe table allowing Create, Read, Update, orDelete privileges for an interactive entity to beassigned to a right. This determines what a par-ticipant user can access in MSATS.

Interactive TransactionsInteraction with the MSATS web-based B2BBrowser.

IntervalPeriod over which interval energy data is recor-ded by the metering installation that correspondsto a TI or submultiples of a TI.

Interval MeterA meter that measures consumption of electricityfor each specified interval (usually half-hourly toalign with wholesale market trading intervals). Itis manually read, or remotely read using a com-munications network.

Inventory TableA table of devices for unmetered loads asso-ciated with each NMI as described in the Met-rology Procedure: Part B.


© 2017 AEMO 79

IPWANInternet protocol wide area network

JJurisdiction

participating jurisdiction (defined in the NER)

Jurisdiction CodeCodes used in MSATS to identify the Jurisdictiona NMI belongs to, as specified in the CATS Pro-cedures.

LLAN

Local area network

LatestThe participant is set up to receive both currentand next projected future version of aseXML-compliant files.

Life SupportA situation where an End User relies on elec-tricity for the operation of life support equipment.A term defined in: • The NEM, apart from Victoria,in the NERR. • Victoria, in the Electricity Dis-tribution Code and Energy Retail Code.

LNSPIn the context of a Network Service Provider’s dis-tribution network: Local Network Service Pro-vider In relation to a child connection point:ENM. For the purposes of the Metrology Pro-cedure: If there is more than one Local NetworkService Provider for a local area, a reference tothe LNSP in respect of a metering installation orconnection point is a reference to the LNSP thatholds a licence in respect of the network towhich that metering installation or connectionpoint is connected. legislation in the relevant par-ticipating jurisdiction. Includes both transmissionand distribution businesses.

Load ProfileA profile of metering data aggregated across aspecified set of connection points.

Load TableA table of Unmetered Device market loads pub-lished by AEMO at http://www.aemo.-com.au/Electricity/National-Electricity-Market-NEM/Retail-and-metering.

Local AreaThe geographical area allocated to a networkservice provider by a Jurisdictional Regulator.

log4jA Java logging facility, enabling logging at runtime without modifying the application binary.

Lot NumberThe lot reference number allocated to a streetaddress prior to street numbering (except in theACT).

LRLocal Retailer

LVA Voltage equal to or less than 1kV.

LV CTLow voltage current transformer

MMAMP

Metering Asset Management Plan. A test plandeveloped and maintained by an MP in accord-ance with the Service Level Procedure.

MarketNetAEMO’s private network available to participantshaving a participant ID

Markets PortalSingle web portal interface to access AEMO'swholesale IT systems

MCMeter Coordinator; The Role Code used inMSATS for an MC is RP.

MCLMaximum Credit Limit

MDFF DataThe data contained in an electronic file formattedaccording to the Meter Data File Format spe-cification.

MDFF SpecificationThe Meter Data File Format Specification forNEM12 & NEM 13.

MDMMeter Data Management system includes theProfile Preparation Service, Basic Meter Pro-filing, and Data Aggregation.

MDM Contributory SuffixA suffix defined in sections 6 and 7 of the NMIProcedure used to identify a stream of meteringdata. It is consistent with the NMISuffix contained


© 2017 AEMO 80

in the 200 record of the MDFF interval meteringdatafile.

MDM Data FileMeter Data Management Data File: The stand-ard file for delivery of metering data to AEMO.

MDM ProceduresThe MSATS Procedure: MDM Procedures.

MDPMetering data provider; The party responsible forthe delivery of metering data to AEMO for meter-ing installations defined in the Rules.

Meter AlarmAny alarm within a metering installationdesigned to detect any unexpected occurrence,such as a loss of supply, VT or phase failure,tamper detection, reverse energy flow, pulseoverflow, cycle redundancy check error and tem-perature or time tolerance.

Meter ChurnAny alteration or replacement of a meteringinstallation.

Meter Data File Format SpecificationMetering data delivered to participants is to con-form to the Meter Data File Format Specification,see Meter Data File Format on AEMO's website.

Meter Data Notification ProcessThe provision of metering data to participants aspart of the MDP's normal production processobligations, see B2B Procedures: Meter DataProcess.

Meter Data ProcessThe overall process for the provision of meteringdata to a participant by an MDP. Requests by theappropriate participant for provision of missingmetering data from an MDP, or the querying ofthe validity of any metering data supplied by anMDP. Has 3 component processes: Meter DataNotification Process, Provide Meter Data Pro-cess, and Meter Data Verification Process, seeB2B Procedures: Meter Data Process.

Meter Data Verification ProcessThe process by which a participant queries themetering data received in a Meter Data Noti-fication from an MDP. The process also allows aparticipant to provide an alternative substitutionthat may be considered by the MDP, see B2BProcedures: Meter Data Process.

Meter ProvisionThe provision, installation, and maintenance ofthe components of a metering installation.

Meter ReadingElectricity consumption data taken from a meter,regardless of how it is obtained.

Meter RegisterThe meter register data stored in MSATS, whichincludes both the metering register and otherdata.

Meter Register Status CodeA code used in MSATS to delineate the status ofa meter. For more detail, see the CATS Pro-cedures.

Meter Serial IDA serial number that uniquely identifies eachmetering installation record associated with aNMI.

Metering Data Delivery CalendarThe Metering Data Delivery Calendar providesthe cut-off dates for MDP data delivery.

Metering Installation Type CodeThe type of meter attached to a NMI asdescribed in the CATS Procedures.

Metrology Procedure: Part APart A National Electricity Market

Metrology Procedure: Part BPart B Metering Data Validation, Substitution,and Estimation Procedure.

MMS Data ModelThe definition of the interface to participants ofdata published by AEMO. A database con-forming to the MMS Data Model can contain alocal copy of all current participant-specific datarecorded in the main database. The MMS DataModel includes database tables, indexes andprimary keys.

MPMetering Provider; In MSATS, it is referred to asan MPB.

MPBA Category C Metering Data Provider. An MDPaccredited only to collect metering data, not pro-cess or transfer it.


© 2017 AEMO 81

MPCMetering Provider Data Collection

MSATSRetail Market Settlement and Transfer Solution

MSATS File Exchange ProtocolThe file exchange protocol used by MSATS, seeMSATS File Exchange Protocol in the B2B Pro-cedures: Technical Delivery Specification.

MSATS NotificationAn MSATS transaction, see MSATS Procedures:CATS Procedures and B2B Procedures: ServiceOrders Process.

MSATS ProceduresAll of the following procedures: CATS Pro-cedures, WIGS Procedures, MDM Procedures,NMI Standing Data Schedule, NMI Procedure,and Part A of the NEM RoLR Processes.

MSGAMarket Small Generator Aggregator

MSUGMarket Systems User Group

MTPASAMedium-term Projected Assessment of SystemAdequacy; 2 years worth of data.

MWMegawatt

NNEL

National Electricity Law

NEMNational Electricity Market

NEM RoLR ProcessesNEM RoLR Processes – Part A: MSATS Pro-cedure: RoLR Procedures – Part B: B2B Pro-cedure: RoLR Process.

NEMDENational Electricity Market Dispatch Engine

NERNational Electricity Rules

NERLNational Electricity Retail Law

NERRNational Energy Retail Rules

Network TariffThe rate the network business charges theretailer for the use of their network.

Network Tariff CodeA nominated code for the Network Tariff chargedby the NSP.

New FRMPThe FRMP identified on a change request priorto the change request being completed.

NewMDPThe MDP identified on a change request prior tothe change request being completed.

New PartiesEntities associated with the meter installationand retail arrangements to which a consumertransfers to.

New RetailerFollowing the completion of a transfer of a NMI,the retailer that is the current FRMP.

New RPThe responsible person (RP) identified on achange request prior to the change requestbeing completed, see MSATS Procedures:CATS Procedures.

NGERACNational Gas Emergency Response AdvisoryCommittee

NGRNational Gas Rules

NMASNon-market Ancillary Service

NMI[electricity] National Metering Identifier

NMI AddressThe address where the connection point the NMIrefers to is located (the site address). During aconsumer transfer, this information is supplied tothe new retailer by the LNSP and acts as acheck for the correct NMI identification.

NMI ChecksumA number, one digit in length, used to validatethat a NMI supplied to CATS is a valid.


© 2017 AEMO 82

NMI Classification CodeA code identifying the type of consumer to whicha NMI belongs, e.g. large or small wholesalegenerators.

NMI Data streamThe term used to represent a NMI suffix requiredby MDM to enable the metering data associatedwith a NMI to be correctly identified.

NMI Discovery Search 1The process of finding a NMI and the NMI Check-sum by searching MSATS using the Site, theDPID or a meter’s serial number. For moredetails, see the CATS Procedures.

NMI Discovery Search 2The process of entering a NMI and NMI Check-sum in MSATS to obtain NMI Standing Data. Formore detail, see the NMI Standing Data AccessRules in the CATS Procedures.

NMI Discovery Search 3The search process that can only be used forone of the purposes detailed in the CATS Pro-cedures.

NMI Master RecordThe NMI master record with an end date set tothe year 9999.

NMI ProcedureMSATS Procedures: National Metering Identifier.

NMI Search RulesThe search available in MSATS enabling a par-ticipant to identify a NMI when the only inform-ation available is the DPID, the meter serialnumber, or the Site address. For more details,see the CATS Procedures.

NMI Standing Data Access RulesThe search available in MSATS enabling a par-ticipant to identify nominated CATS StandingData.

NMI Standing Data ScheduleThe AEMO document called NMI Standing DataSchedule.

NMI StatusA code identifying the status of a NMI, forexample active or inactive.

NMI Status CodeA code used in MSATS to determine if a NMI canbe the subject of a retail transfer. For more detail,

see the CATS Procedures.

Non-Controlled LoadA load that is not a Controlled Load.

NSLPNet System Load Profile, a profile shape cal-culated from interval data for metered inputs(e.g. TNI data) less interval data (metered orderived) outputs, to derive an average loadshape for the remaining energy in the profilearea. Net System Load is the residual of the totalsystem load, (net off and the peel off.). The NetOff consists of all of the Interval Meters. The PeelOff consists of profiles that have been applied toother basic meters, as defined by the jur-isdictional rules.

NSPNetwork Service Provider

NSP2Second Network Service Provider: The Roleassigned to a DNSP for a transmission con-nection point (wholesale NMIs) having two NSProles.

NSRDNext Scheduled Read Date; The next scheduledActual Meter Reading of an Accumulation Meter.

OObjected

A status point of a Change Request.

ObjectionA type of transaction raised in relation to aChange Request.

Objection Clearing PeriodThe number of business days an Objection canremain in MSATS. If the Objection is not with-drawn by the end of the Objection ClearingPeriod, it is Cancelled by MSATS.

Objection CodeA code used in MSATS representing the onlygrounds on where an Objection can be lodged.For a list of Objection Codes, see the CATS Pro-cedures.

Objection Logging PeriodThe number of business days available to a par-ticipant for entering an Objection in MSATS.


© 2017 AEMO 83

Objection RulesThe rules applicable in MSATS that determinehow Objections are used for each ChangeReason Code. For more details, see the CATSProcedures.

Off-MarketAn End Use Customer within an embedded net-work who purchases electricity from the EENSPwho supplies the electricity.

Old retailerAny previous FRMP for a NMI.

On-MarketAn End Use Customer at a child connectionpoint who purchases electricity from a retailer.

On/Off TableA table recording the switching status (On = 1,Off = 0) for each trading interval for unmeteredloads associated with a NMI as described in theMetrology Procedure: Part B.

PPA

participant administrator

PA RightThe right assigned to a Participant ID's PA.

Parent FRMPThe retailer who is the Current FRMP for a par-ent connection point.

Parent NameThe Embedded Network Code populated in theEmbNetParent field in MSATS for a Parent NMIto indicate the NMI is a parent for a specifiedembedded network.

Participant's DBMSContains the data received from AEMO intotables matching the Data Model.

Participant BatcherAn application providing an interface for batchtransactions (files).

Participant file serverThe publishing point from AEMO systems to par-ticipant systems. Each participant is allocated anaccount and access to private and public areas.Participants are responsible for interfacing withthe participant file server.

Participant IDRegistered participant identifier; A company canhave more than one Participant ID.

Participant UserAn end-user, using AEMO's participant energymarket systems to view and retrieve informationon behalf of a participant ID. The participantusers access rights are created and maintainedby the participant ID's Participant Administrator.

Participant user IDThe user ID you used to login to the system.

PASAProjected Assessment of System Adequacy

PCOParticipant current outstandings

PDPre-dispatch

pdrBatcherSoftware responsible for transferring files to andfrom AEMO's participant file server to the par-ticipant's local Data Interchange folders. It canbe installed in any environment supporting Java.

pdrLoaderSoftware responsible for loading files to andfrom participant's local Data Interchange foldersto the participant's DBMS. It can be installed inany environment supporting Java.

PendingA status point of a Change Request.

Pending ValidationA status point of a Change Request.

PMPrudential Margin

POEProbability of exceedence

POPPoint of presence (in network)

PPSProfile Preparation Service: Calculates profileshapes by using algorithms and interval energydata. The calculation of the NSLP or the CLP.


© 2017 AEMO 84

Pre-consent Market FacilitationRefers to the ability of a party, such as a pro-spective retailer, to obtain information about aNMI in which it currently does not have aninterest. While typically, this may be to obtaininformation to facilitate quotation and transfer,the policies governing the use of this func-tionality are determined by jurisdictions and theaccess and data available is limited based onthose policies.

Pre-productionAEMO’s test system available to participants

PrivilegeRefers to the create, read, update, and deleteactions available to an entity. These privilegesset the actual access rights to the entity, forexample the ability to create or edit a participantrecord as opposed to just viewing rights to theparticipant record.

ProductionAEMO’s live system

Profile AreaA geographical area comprising a group of oneor more TNIs where a single NSLP is calculated.If part of an LNSP local area is located within thelocal area of another LNSP, that part of the localarea of the first LNSP is considered to be part ofthe profile area of the second LNSP.

Profile NameA code identifying the name of the algorith-mically derived shape that is used to allocate aData stream’s metering data to TIs.

Profile/ProfilingUse of an algorithm to allocate basic meter read-ings to each 30 minute trading interval duringthe meter reading period.

Proposed Change DateThe proposed date when a Role transfers fromone participant to another.

Prospective ChangeA change to a NMI record that takes effect on adate after the date the Change Request is sub-mitted.

Prospective DaysA situation where the number of days under con-sideration occur after the current date.

Prospective PeriodThe maximum period when a ProspectiveChange can be made.

QQualification Procedure

The Procedure for Metering Providers, MeteringData Providers and Embedded Network Man-agers.

RRead Privilege

The access right to view records represented byan entity.

Read Type CodeTypes of meter readings detailed in the CATSProcedures.

Register Identifier Status CodeA code in MSATS indicating if a Meter Registeris active. For more detail, see the CATS Pro-cedures.

Registrable capacitiesRegistered participant categories, such as cus-tomer, generator, network service provider,trader, reallocator, special participants, marketparticipant, and intending participants.

RegulatorIn the context of a RoLR Event, the AER for theNEM, apart from Victoria, and the Essential Ser-vices Commission of Victoria for Victoria.

RejectedA status point of a Change Request. Meaningthe Change Request failed a validation test inMSATS.

RequestedA status point of a Change Request.

ResidentialAs defined in the NERL.

RetailerThe person responsible in the wholesale marketfor the settlement of electricity supplied to a con-sumer’s NMI, see MSATS Procedures: CATS Pro-cedures.

Retrospective ChangeA change to a NMI record that becomes effectiveon or before the date the Change Request is sub-mitted.


© 2017 AEMO 85

Retrospective DaysA situation where the days under considerationmust either be the date of a Change Request ora date preceding the date of the ChangeRequest.

Retrospective PeriodThe maximum period where a RetrospectiveChange can be made.

RightRights are a collection of entities and their asso-ciated access privileges. A right consists ofinformation about various actions that an ownerof a right can perform on each entity in the sys-tem. PAs can create and edit rights and allocatethem to participant users in their company.

RoCRoLR of Choice: The nomination of a RoLR byan End Use Customer (as classified in s.2 of theNational Energy Retail Law) and agreed by theretailer to be its FRMP in a RoLR Event.

RoleThe role a company has with a connection pointin CATS. A single company can have more thanone role associated with a NMI.

Role CodeA code used in MSATS to identify the asso-ciation a participant has with a NMI. For a list ofRole Codes, see the CATS Procedures.

RoLR Effective Transfer DateThe first day after the declaration of a RoLREvent. The date when the NMIs where the FailedRetailer was the FRMP are transferred to theirRoLR, making the RoLR the FRMP for thoseNMIs.

RoLR EventAn event triggering the transfer of End Use Cus-tomers to a RoLR.

RoLR Event Affected JurisdictionThe Jurisdiction affected by a RoLR Event.

RoLR Event Affected MSATS ParticipantMSATS participants potentially affected by aRoLR Event include: • Those with a current Rolefor any NMI where the Failed Retailer wasassigned to one or more MSATS roles on theRoLR Effective Transfer Date, including: theFailed Retailer (the current FRMP, LR or both),the Current LNSP, the Current MDP, or the Cur-rent MPB. • The RoLR for each RoLR Event

Affected NMI. • If the Failed Retailer is a LR, thereplacement LR. • Those having a Role for aNMI where at the time of the RoLR Event, theFailed Retailer was nominated as the NewFRMP on an incomplete Change Request orMSATS Participants nominated in a new Role onsuch a Change Request.

RoLR Event Affected NMINMIs where the Failed Retailer was assigned toone or more Roles for the RoLR Effective Trans-fer Date NMIs where at the time of the RoLREvent, the Failed Retailer was nominated as theNew FRMP on a Change Request that is at oneof the following status points: Requested, Objec-ted, or Pending Validation.

RoLR Key ContactA contact specified in the NEM Retail OperationsContacts List.

RoLR Post Implementation ReviewA review managed by AEMO to assess how aRoLR Event was managed.

RoLR Transition PeriodThe period of time from when a RoLR Eventoccurs to the time a RoLR Post ImplementationReview is complete.

Routine TestingFor the purposes of the Metrology Procedure,includes the ongoing and regular maintenancetesting, compliance testing and in-service testingof a metering installation initiated by the MC orMP to fulfil their obligations under clause S7.3 ofthe NER.

RPResponsible person

RRPRegion reference price

RSFRegional scaling factor

RulesNational Electricity or Gas Rules (NER or NGR)

SSample Test Plan

A statement of the sample size to be taken, thefrequency of sample testing, and the requiredaccuracy.


© 2017 AEMO 86

SCADASupervisory Control and Data Acquisition

Scheduled Meter ReadingAn Actual Meter Reading on a Meter Readingdate scheduled by the relevant MDP.

Scheduled Reading DateThe date on which a Scheduled Meter Readinghas occurred or might occur.

SchemaSee aseXML Schema.

Second-Tier Controlled LoadA Controlled Load that is a second-tier load.

Second-Tier Non-Controlled LoadA Non-Controlled Load that is a second-tierload.

Second Tier CustomerEnd use customers who have transferred to aretailer other than their local retailer.

Second Tier NMIThe electricity associated with a second tier NMIis purchased from a retailer other than the localretailer.

Service Level Procedure (ENM)The Service Level Procedure: Embedded Net-work Managers.

Service Level Procedure (MDP)The Service Level Procedure: Metering Data Pro-vider Services. Details the requirements for thesystems and processes for the collection, pro-cessing, and delivery of metering data by Meter-ing Data Providers.

Service Level Procedure (MP)The Service Level Procedure: Metering ProviderServices Category B for Metering installationTypes 1, 2, 3, 4, 5 and 6. Details the require-ments for the provision, installation, and main-tenance of metering installations by MeteringProviders.

SGASmall Generation Aggregator

Shared Market ProtocolAn initiative to provide a standard for com-munications to support smart meters. AEMO hasextended AEMO’s e-Hub functionality to support

this initiative in line with the B2B Procedure:Technical Delivery Specifications.

SiteThe physical location of the connection point,see B2B Procedures: Customer and Site Detailsand Service Orders Process.

Special Meter ReadingAn Actual Meter Reading taken on a date otherthan a Scheduled Reading Date.

Special Read DateA date when a Special Meter Reading is tooccur.

SRASettlements Residue Auction

SSLSecure Socket Layer, a protocol for encryptinginformation over the internet.

Start DateThe date the change occurs.

STPASAShort-term Projected Assessment of SystemAdequacy; 7 days worth of data

Structured AddressThe structured address format containing the fol-lowing information: • Flat type and flat number •Floor type and floor number • Building name •Location descriptor • House number and suffix •Lot number • Street name and street type •Suburb • Postcode • State

STTMGas short term trading market

SubstitutionA process undertaken for the replacement ofmissing (null) or erroneous accumulated meter-ing data or interval metering data where meter-ing data has failed Validation.

Super User RightSystem administrator right only assigned toAEMO system administrators.

SupersededThe participant can receive files compliant to theThe participant can receive files compliant to thesuperseded aseXML version, and needs tochange over their receiving system before thenext aseXML version release.


© 2017 AEMO 87

System AdministratorThe AEMO system administrator who maintainsthe PA right.

TT & Cs

Terms and conditions

TITrading Interval

Tier 1 SiteA site where the FRMP is the LR. This could bethe case where: • The End Use Customer hastransferred back to the LR as their retailer(FRMP) after a period with another retailer. • Thesite is not contestable. • The site is contestablebut the End Use Customer has not transferred toanother retailer. See also first-tier controlledload.

Tier 2 SiteA site where the FRMP is not the same as theLR. This could be the case if: • A contestableEnd Use Customer has elected to transfer fromthe LR. • An End Use Customer signed a con-tract with a retailer other than the LR prior to theconnection point being established in theMSATS System and it was created as a Tier 2Site. See also second-tier controlled load.

Time frame RulesAs described in the CATS Procedures, the rulesallocating the number of business days to the fol-lowing categories: • Objection Logging Period. •Objection Clearing Period. • RetrospectivePeriod. • Prospective Period.

TNI CodeTransmission Node Identity: A four characteralpha-numeric code used to identify a virtualtransmission node or transmission network con-nection point.

TNSPTransmission Network Service Provider

Transaction Type CodeAs described in the CATS Procedures, a codeused in MSATS to identify a need to changeCATS Standing Data.

UUncontrolled Unmetered Device

An Unmetered Device operating 24 hours perday and has a variable load over a repeated

operating cycle (e.g. traffic signal, where applic-able).

Unmetered DeviceAny electricity-consuming device installed at ornear a connection point that is unmetered, andthe load consumed at that connection point is amarket load. There are two types of UnmeteredDevices: Controlled Unmetered Devices andUncontrolled Unmetered Devices.

Unmetered Load GuidelineGuidelines for unmetered loads.

Unmetered SupplyThe consumption volume calculated for loadsthat have no meter (e.g. street lighting etc).Unmetered metering data for unmetered supplyis submitted to MSATS as interval data (i.e. as ifit was an interval type of metering installation).

Unstructured AddressAn address with the following format: • A string oftext characters with a maximum length of 80 perline. • A maximum of 3 lines.

Update PrivilegeThe access right to update records representedby an entity.

URMUser Rights Management; see the Guide toURM on AEMO's website

Usage FactorThe method of identifying a given data stream’sconsumption in terms of its contribution to theoverall sum of profile loads for a given daterange.

User Rights AccessThe Right a PA assigns to Participant Users toallow access to different areas of MSATS.

VValidated

Metering data that has passed Validation.

ValidationA process to test the veracity and integrity ofmetering data.

VICAMI MeterA meter installed in Victoria as part of theAdvanced Metering Infrastructure mandate.


© 2017 AEMO 88

VPNVirtual Private Network

VTVoltage transformer

WWeb Services

The transfer of aseXML transactions betweenparticipant gateways and the AEMO's market sys-tems.

Wholesale Connection PointConnection points located at the transmissionnode representing bulk supply feeders to a dis-tribution network, interconnectors, and gen-eration points.

Wholesale settlement dayA period of time constituting a day for the pur-poses of wholesale settlement. It is a 24 hourperiod beginning and ending at midnightEastern Standard Time (EST).

WIGSWholesale, Interconnector, Generator andSample procedures contain the principles thatgovern the transfer of consumer settlements, theregistration of metering installation, and man-agement of standing data for NMIs that are clas-sified as wholesale, interconnector, generator orsample.

WIGS ProceduresMSATS Procedures: Procedure for the Man-agement of Wholesale, Interconnector, Gen-erator and Sample (WIGS) NMIs.

XXML

eXtensible Mark-up Language.

ZZIP

The file compression format used for exchangingdata with AEMO.


© 2017 AEMO 89

GUIDE TO ELECTRICITY INFORMATION SYSTEMSINDEX

AAbout data sharing 28About security 35About the NEM 4Accessing the web portal 64Additional connection and bandwidth 26AEMO web-based URLs 64AEMO’s website 18annual pre-payment options 25API gateway 66API gateway system requirements 66

BB2B Validation Module 33Bandwidth entitlements 24Bandwidth Pricing Model 23

CChanging your Participant ID password 39Changing your password 49, 52Checklist for setting up your IT systems 56Communications 70Connection entitlements 24Current data 27

DData Interchange 34Data network connection 18Data network connection (MarketNet) 21Data network connection decisions 22Data network connection options 22Data Sharing 28Data sharing example 30Data sharing removal 32Data sharing set-up 31Dedicated Link 23Deregistration for IT systems 68

EElectricity or Gas Data Models 61electricity wholesale 9EMMS 9EMMS data to initially populate RDBMS

conforming to MMS Data Model 63EMMS functionalities used by each participant

category 15EMMS functionality 9EMMS wholesale system software 34

FFeedback 71File-based interface addresses 62File-based interface URLs 62File Servers 60

GGlossary 73

HHistorical data 28

IInterfaces 60IT Interfaces 18

MMaking changes to your MarketNet

connection 26Market data 27, 63Market data access 37Market solver files 17MarketNet 18, 21MarketNet data network connection options 23MSATS data 63MSATS functionalities used by each participant

category 14MSATS functionality 8MSATS retail system software 33multiple participant IDs 38

NNEM IT systems 7NEM IT systems functionality 6NEM IT systems overview 6NEM participant categories 13NEM retail functionality 7NEM wholesale 9NEMDE Queue 16

PParticipant's security responsibilities 36participant administrator 38Participant Batcher 33Participant entitlements 23Participant file server folders 61

INDEX

© 2017 AEMO 90

Participant File Server Password Changer 44Participant User password format 50Password 39-41Password changers 39Password management 37Private participant data 63publicly available data at no cost 18

RRecommended method for large amounts of

data 61release schedule 5Retail software packages provided by AEMO 33

SSecurity 35Security management 36Setting up Data Interchange 62setting up IT systems timeline 56Simplest access method 61single user ID logins 38Software Packages 33Standard DI setup 62System transfers 68

Ttechnical specification 5Testing the password change 49

Uunderstanding MarketNet 21Understanding set participant 38Unregistered organisations access requests 25User Rights Management (URM) 37user rights management for energy markets 38

VVPN LAN to LAN 23VPN variable 23

WWeb-based interface URLs 64web-based password changer 41Web portal requirements 63Web portals 20Web Portals 63Web services 20, 65Web Services 33-34Web services system requirements 65Website data 27Who 55Wholesale software packages provided by

AEMO 34

GUIDE TO ELECTRICITY INFORMATION SYSTEMSINDEX