Guide to Information Systems v2 03 Apr 2014

8/10/2019 Guide to Information Systems v2 03 Apr 2014

http://slidepdf.com/reader/full/guide-to-information-systems-v2-03-apr-2014 1/101

GUIDE TO INFORMATION SYSTEMSMONDAY, 14 APRIL 2014

Version: 2.03

Reference: IT Systems © 2014 Australian Energy Market Operator Ltd (AEMO). All rights reserved.



Guide to Information Systems

Important Notice

AEMO has prepared this Guide to Information Systems (Guide) to provide guidance on the use of the Energy Market

Systems under the National Gas or Electricity Rules (Rules), as at the date of publication.

No reliance or warranty

This Guide does not constitute legal or business advice, and should not be relied on as a substitute for obtaining 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 the accuracy, reliability, completeness,

currency or suitability for particular purposes of that information.

Limitation of liability

To the maximum extent permitted by law, AEMO and its advisers, consultants and other contributors to this Guide (or

their respective associated companies, businesses, partners, directors, officers or employees) are not liable (whether

by reason of negligence or otherwise) for any errors, omissions, defects or misrepresentations in this document, or for

any loss or damage suffered by persons who use or rely on the information in it.

Copyright

Copyright 2014 Australian Energy Market Operator Limited. The material in this publication may be used in accordance

with the copyright permissions on AEMO’s website.

Trademark notices

Microsoft 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 obsolete

The release of this document changes the Flat File Specification v1.06 and earlier versions of Guide to Information

Systems.

Distribution

Available to the public.

Prepared by

PMO Documentation Team

Last update: 14/04/2014 12:36 PM

Notes

v2.00 updated for May Release 2014 and add new Gas Supply Hub (GSH).v2.01 updated to include MarketNet costs for intermittent generation and confidential data for public researchers.

Further information

For further information, please visit www.aemo.com.au or contact:

AEMO Information and Support Hub

Phone: 1300 AEMO 00 (1300 236 600) and follow the prompts.

Email: [email protected]

© 2014 AEMO i

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

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


http://www.aemo.com.au/About-AEMO/Legal-Notices/Copyright-Permissions

http://www.aemo.com.au/About-AEMO/Legal-Notices/Copyright-Permissions




Contents

1 Introduction 11.1 Purpose 1

1.2 Audience 1

1.3 How to use this guide 2

1.4 What's in this guide 2

2 What AEMO Provides 3

2.1 About AEMO's IT systems 3

2.2 IT interfaces 4

2.3 Communications 5

2.4 AEMO IT Systems Overview 6

2.5 Data network connection (MarketNet) 8

2.5.1 Data network connection decisions 8

2.5.2 Data network connection options 8

2.5.3 Registered participant entitlements 9

2.5.4 Unregistered organisations access requests 11

2.5.5 Additional connection and bandwidth 11

2.5.6 Making changes to your MarketNet connection 12

2.5.7 MarketNet access control 12

2.6 User Rights Management (URM) 12

2.7 Understanding the set participant function 13

2.8 Software 13

2.9 Security 15

2.9.1 About security 15

2.9.2 Participant's security responsibilities 16

2.9.3 Excluding IP addresses in Microsoft Internet Explorer 17

2.10 Passwords 19

2.10.1 Changing your participant user password 19

2.10.2 Changing your Participant ID password 20

2.11 Data sharing 29

2.11.1 About data sharing 30

2.11.2 Data sharing example 31

2.11.3 Data sharing set-up 31

2.11.4 Data sharing removal 32

© 2014 AEMO ii






6.6 BB operation 57

6.7 BB user access 57


6.8.1 Registered user access 58

6.8.2 Registered user access types 59

7 Gas Supply Hub 60

7.1 About the GSH 60

7.2 GSH IT interfaces 61

7.3 GSH IT systems 61

7.4 GSH participant categories 62

7.5 GSH systems user access 62

8 National Electricity Market 64

8.1 About the NEM 64

8.2 NEM IT interfaces 65

8.3 NEM IT systems 66

8.4 NEM retail functionality 67

8.5 NEM wholesale functionality 68

8.6 NEM participant categories 71

8.6.1 Retail participant categories 71

8.6.2 Wholesale participant categories 71

8.7 NEM systems user access 73

8.8 NEM Dispatch Engine (NEMDE) 73

8.8.1 Market solver files 73

8.9 Other NEM IT systems 73

9 Retail Gas Market 74

9.1 About the FRC Hub 74

9.2 Retail Gas Market IT interfaces 75

9.3 Retail Gas Market IT systems 75

9.4 Retail Gas Market participant categories 75

9.5 Retail Gas Market user access 76

10 Short Term Trading Market 78

10.1 About STTM 78

10.2 STTM IT interfaces 79

10.3 STTM IT systems 7910.4 STTM participant categories 80

© 2014 AEMO iv




10.5 STTM user access 80

11 Needing Help 82

11.1 AEMO's Information and Support Hub 8211.1.1 Contacting the Information and Support Hub 82

11.1.2 Information to provide AEMO 82

11.2 Feedback 83

12 References 84

12.1 Rules, law, and government bodies 84

12.2 AEMO's website 84

13 Index 87

© 2014 AEMO v




Figures

Figure 1: AEMO IT systems overview 7

Figure 2: understanding MarketNet 8

Figure 3: data sharing in the energy market systems web portal 31

Figure 4: setting up IT systems timeline 46

Figure 5: DWGM IT systems overview 50

Figure 6: DWGM user access request 53

Figure 7: BB overview diagram 54

Figure 8: BB home page 58

Figure 9: GSH IT systems overview 60

Figure 10: NEM IT systems overview 65

Figure 11: Retail Gas Market IT systems overview 74

Figure 12: Retail Gas Market user access request 77

Figure 13: STTM IT systems overview 78

Figure 14: STTM user access request 81

Tables

Table 1: AEMO's IT interf aces 4

Table 2: MarketNet data network connection options 9

Table 3: participant bandwidth entitlements 10

Table 4: annual prepayment options 11

Table 5: additional connection and bandwidth options 11

Table 6: user rights management for energy markets 13

Table 7: software packages provided by AEMO 14

Table 8: participant's security responsibilities 16

© 2014 AEMO vi




Table 9: energy market systems web portal production and pre-production URLs 41

Table 10: AEMO URLs 42

Table 11: file-based interface addresses 43

Table 12: Additional specific mapping addresses 44

Table 13: checklist for setting up IT systems 47

Table 14: DWGM IT interfaces 50

Table 15: DWGM IT systems 50

Table 16: DWGM functionalities used by each registrable capacity 51

Table 17: BB interfaces 55

Table 18: BB functionality 55

Table 19: BB mandatory and eligible registrable capacities 56

Table 20: GSH IT interfaces 61

Table 21: GSH IT systems 61

Table 22: GSH functionalities used by each registrable capacity 62

Table 23: NEM interfaces 66

Table 24: NEM IT systems 66

Table 25: MSATS functionality 67

Table 26: EMMS functionality 68

Table 27: MSATS functionalities used by each participant categor y 71

Table 28: EMMS functionalities used by each participant category 72

Table 29: Retail Gas Market interfaces 75

Table 30: Retail Gas Market system functionalities 75

Table 31: Retail Gas Market functionalities used by each registrable capacity 76

Table 32: Table 23: STTM interfaces 79

Table 33: STTM system f unctionalities 79

Table 34: STTM functionalities used by each registrable capacity 80

© 2 01 4 AE MO vii




Glossary

These abbreviations, symbols, and special terms assist the reader’s understanding of the

terms used in this document. For definitions of these terms, the reader should always referto the applicable market Rules.

A

AEMC Australian Energy Market Commission

AEMO Australian Energy Market Operator

AES Advanced Encryption Standard

AEST Australian Eastern Standard Time

B

BBBulletin Board

C

CSV Comma-separated values; a file format for exchanging data.

D

Data Interchange A set of cooperating applications used to replicate data between AEMO's energy market systems and a participant's

DBMS conforming to the MMS Data Model.

DBMSDatabase management system

DWGMDeclared Wholesale Gas Market (Victoria)

E

EMMS Wholesale Electricity Market Management System; software, hardware, network and related processes.

Energy market systems web portalSingle web portal interface to access AEMO's IT systems.

© 2014 AEMO viii




F

FCASfrequency control ancillary services

FTPFile transfer protocol

I

Implementation dateUsually one business day before the effective registration date of a registration change. Upon special request,

AEMO may agree to implementation two business days before the effective registration date, given sufficient notice

time to comply with the Rules and Change Management Procedures.

Interactive entity Web-based entity for user rights access

IPWANInternet protocol wide area network

L

LANLocal area network

M

MarketNet AEMO’s private network available to participants having a participant ID.

MMS Data ModelThe definition of the interface to participants of data published by AEMO. A database conforming to the MMS Data

Model can contain a local copy of all current participant-specific data recorded in the main database. The MMS

Data Model includes database tables, indexes and primary keys.

MSATSRetail Market Settlement and Transfer Solution

MW Megawatt

N

NEMNational Electricity Market

NER National Electricity Rules

NGERACNational Gas Emergency Response Advisory Committee

NGR

National Gas Rules

© 2014 AEMO ix




NMI[electricity] National Metering Identifier

P

PA Participant Administrator; manages participant organisations user access and security.

Participant IDRegistered participant identifier

PASA Projected Assessment of System Adequacy

POPPoint of presence (in network)

Pre-productionTest and training environment, typically showing much less activity, if any.

ProductionLive environment, actively reflecting the currently available data.

R

Registrable capacitiesRegistered participant categories, such as customer, generator, network service provider, trader, reallocator, special

participants, market participant, and intending participants.

RulesThe National Electricity or Gas Rules.

S

SCADA Supervisory Control and Data Acquisition

SRA Settlements Residue Auction

STTM

Gas short term trading market

U

URMUser ri ght management

V

VPN Virtual Private Network

© 2014 AEMO x





Chapter 1 Introduction

1 Introduction

1.1 Purpose

This guide provides an overview of AEMO’s market systems used by participants. It is

relevant to IT decision making during the registration process and provides an understanding

of the IT systems requiring set up. Because each participant has its own scope of business

and operation, this document only outlines the facilities available. Please seek advice for

your organisation’s specific business needs.

The setting up of IT systems and the processing of registration have steps taking many

weeks, and are interdependent. IT systems setup at your end is a complex process andrequires careful planning by an experienced IT team.

Time frames for your IT team to set up your IT systems vary according to the market you

are registering in, your organisations individual requirements, and the experience of your IT

team. Time frames are provided as a guide only. Organisations are encouraged to progress

setting up their IT systems in parallel with the registration process. For more details about

registration, see Registration.

This document is written in plain language for ease of reading. Where there is a discrepancy

between the Rules, and information or a term in this document, the Rules take precedence.

1.2 Audience

This document is relevant to:

l Interested parties considering registration with AEMO.

l New registrants applying for registration with AEMO.

l Existing participants requiring IT system assistance while registering in another energy market.

l Project managers creating an AEMO registration project plan.

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

l Participants requiring an understanding of the web applications AEMO provides, and

whether they are suitable for use by their organisation.

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

© 2014 AEMO 1

http://www.aemo.com.au/About-AEMO/Energy-Market-Registration/Registering-in-Energy-Markets








monitors the process cycle times of its information systems to ensure performance standards

are met.

AEMO has a six-monthly release program meaning participants can expect new releases

twice per year, around April–May and October–November. AEMO has pre-productionenvironments as well as production environments, each separately maintained. New features

are added to pre-production ahead of production, and are announced in change notices and

technical specifications sent to participants by email. The pre-production environments are

intended for participant testing and training purposes, so the data reflects those activities.

All participants are obliged to ensure their systems are updated for each new release.

For details about AEMO’s Change Management process, see IT Change Management.

2.2 IT interfaces

AEMO has numerous systems with multiple interfaces to provide for the needs of all

participants. Access to some systems does depend on a participant’s registration category.

Table 1 below is a generic guide to the interfaces AEMO provides. For more details about

each market’s IT systems, see the relevant market section in this guide.

Table 1: AEMO's IT interfaces

Interface Function

Data network connection Any access to AEMO’s market systems requires a data network connection to

MarketNet—this is the first step in implementing your access to AEMO’s market

systems, see "Data network connection (MarketNet)" on page 8.

AEMO’s website (HTTP) Suitable as a source of any publicly available market data at no cost. The p ublic

data published on AEMO’s website is the same as distributed through the file

interfaces, although file interfaces also contain each participant’s private data.

The data is in CSV format in many files and some graphical summaries are also

provided, see Electricity Data and Gas Market Data.

Web portal

(web browser HTTPS)

Participants can interact with AEMO’s systems using a web browser over a

secure communications channel (MarketNet). The browser interfaces allow

direct data entry and are designed for secure, interactive use, suitable for light

demand for data transfer. Examples of functionality are:

n User administration for participant users.

n Placing bids.

n Retrieving reports.

n Retrieving settlement information.

n Monitoring prudential exposure.

Using a web browser interface can cut participant’s cost and client side footprint

by:

n Reducing the requirement for participants to maintain an ITinfrastructure at their site.

© 2014 AEMO 4

http://www.aemo.com.au/Gas/Market-Data



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


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





Chapter 2 What AEMO Provides

Interface Function

n Allowing participant business user access 24 hours a day, 7 days per

week for 365 days per y ear—wherever a connection to MarketNet is

available.n Being fully maintained and supported by AEMO.

n Being available to all participants at no additional cost.

n Providing a secure web interface.

n Allowing the use of multiple participant IDs.

n Being easy to learn with user interface guides available for each web

application—requiring less staff t raining.

n Providing a consist ent look and feel across each web interface.

File upload to web portal

(web browser HTTPS)

Many of AEMO’s systems allow the upload of files directly to the web browser

interface.

File server (FTP) System to system interaction using batch processing, suitable for:

n Participant systems using database technology.

n Submission or receipt of high volumes of data.

n Management of security and data distribution.

The file interface is required for:

n Receiving dispatch data.

n Participants needing an on-going data feed of 5-minute public data (such

as, traders).

Web services (HTTPS) Web services and software for both retail and wholesale systems are available for

some IT system functionalities. The web services functionality differs for each

market, for more details, read the web services details in this guide for yourspecific market.

Pre-production &

production environments

All participants have access to pre-production and production environments.

AEMO implements pre-production environments for testing and training

purposes, prior to AEMO approving your registration. AEMO implements new

functionality in pre-production ahead of the production environments, and

announces the changes in regular emails.

2.3 Communications

The AEMO's Information and Support Hub sends email, including:

l MarketNet password expiry reminder: An automated password expiry reminder is 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 Change notices: Sent immediately when a change notice is issued to advise of any

changes in AEMO's IT systems. This is directed by default to

AEMOHelpDeskComms@your_domain.com.au.

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

© 2014 AEMO 5






Figure 1: AEMO IT systems overview

© 2014 AEMO 7




2.5 Data network connection (MarketNet)

This section discusses AEMO’s private data network connection, MarketNet. Any access to

AEMO’s market systems requires a data network connection to MarketNet—this is the firststep in implementing your access to AEMO’s market systems. Participants provide details of

requirements for network connectivity to MarketNet in the “IT Systems” section of the

registration application.

Figure 2: understanding MarketNet

For provision and maintenance of MarketNet, participants must provide details for a suitably

qualified IT Technical Network Contact in their registration application.

2.5.1 Data network connection decisions

Participants need to decide on the physical connection and preferred management approach

for their connection to MarketNet. Considerations for each participant include:

l Availability of connection into MarketNet.

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

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

l Disaster recovery plans for participant connections, equipment, and site(s)—as

determined by your business needs. AEMO recommends geographic or technology

diversification, or both.

Organisations registering as intending participants are not required to connect to AEMO’ssystems, but may wish to do so by paying an annual prepayment, see "Data network

connection (MarketNet)" above.

2.5.2 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 security reasons,

the connection is dropped if there is no activity for 30 minutes.

The table below explains the choices required for your registration application.

© 2014 AEMO 8




Table 2: MarketNet data network connection options

Connection Type Details

Dedicated Link 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

participant router, via the telecommunication provider’s Bearer, to AEMO’s

IPWAN. The participant, with AEMO’s assistance, is responsible for

arranging t he subscription link with their chosen telecommunication

provider—including the access costs.

Please contact AEMO’s Information and Support Hub to find out if AEMO

supports your preferred technology for a dedicated link.

VPN LAN to

LAN

Permanent VPN LAN to LAN is quick to set up. VPN connections are set up directly

between the participant and AEMO.

The connection is from the participant firewall, using the internet, to AEMO’s

VPN 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 establish

connections with AEMO servers securely using the internet. This connection

type provides a similar service to dedicated links. An IPsec-compliant VPN

device is required at the participant site to enable this type of connection.

VPN variable Variable Internet Variable VPN connection from a workstation, using the internet, to

VPN Concentrator. Internet Workstation VPN requires installation of a Cisco

VPN client software package. For security reasons, the connection drops if

there is no activity for 30 minutes.

The workstation connection operates like a dial-up MarketNet connection. It

allows individual workstations in a participant organisation to establish

connections with AEMO servers.

The AEMO preferred method to enable this type of connection is to install

Cisco VPN client software, available for Windows and Unix-like systems.

AEMO supp lies this software, pre-configured for your use, in conjunction

with at least one RSA SecurID t oken.

2.5.3 Registered participant entitlements

Because it is a resource shared by all participants, the Bandwidth Pricing Model is the

method employed by AEMO to fairly manage the usage of MarketNet. Participant

entitlements are based on registration status, and participant fees paid in any combination of

the electricity or gas markets.

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

© 2014 AEMO 9

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 permanent connections, and two

variable VPN connections (two tokens).

AEMO understands that some participants have legacy arrangements that do not fit these

entitlements, therefore considers variations on a case-by-case basis.

Costs associated with the implementation of data communications between the participant

organisation and AEMO are the responsibility of the participant organisation. Participants

are responsible for arranging and maintaining their equipment and software, and any

telecommunications infrastructure needed to connect to AEMO’s points of presence (POPs).

Bandwidth entitlements

Each company ABN registered with AEMO is allocated bandwidth according to their total

fees paid per year.

The following table provides an indication of the bandwidth entitlements available for

participants.

Table 3: 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 new

organisations commencing participation in the market.

For example, an organisation with a registered ABN in:

l The National Electricity Market, paying total fees of $400,000 per year, is entitled to 2 x

256k permanent and 2 x 256k variable connections.

l Any gas market combination of, the Declared Wholesale Gas Market, a Retail Gas

Market, and the Short Term Trading Market, paying total fees of $800,000 per 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 total fees of $1,

100,000 per year is entitled to 2 x 1024k permanent and 2 x 256k variable connections.

Participants can apply for additional connections or bandwidth in excess of the entitlements,

see " Unregistered organisations access requests" on the facing page.

© 2014 AEMO 10




2.5.4 Unregistered organisations access requests

AEMO’s Information and Support Hub handles requests for network connections and public

data access from unregistered organisations, or third parties providing services to registered

participants. Third parties who require a MarketNet connection must pay for their network connection and arrange access credentials with the participants they represent.

AEMO considers requests on a case-by-case basis, and, if applicable, provides an 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 4 below. Please

provide relevant organisation details, and outline your reason for requiring access in an

email.

Table 4: annual prepayment options

Option Bandwidth (kbps) Fee per year + GST

Up to 2 permanent connections (plus up to 2 variable VPN

connections)

256 $17,000

1024 $51,000

1 VPN variable connection 256 $5,000 ($300 for each

subsequent connection –

includes 1 token)

1 VPN variable connection for public researchers to access

confidential intermittent generation data only (e.g. wind

and solar).

128

(for up to 100 GB per

year)

$1,000 (includes 1 token)

AEMO’s website has public data available at no cost, see Electricity Data and Gas Market

Data.

2.5.5 Additional connection and bandwidth

To provide the connection points with increased capacit y, AEMO charges additional service

fees on a cost recovery basis.

Table 5: 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)

© 2014 AEMO 11









mailto:[email protected]








2.5.6 Making changes to your MarketNet connection

To make changes to your MarketNet connection, send the completed MarketNet Connection

Request Form MarketNet Connection Request Form by email to AEMO’s Information and

Support Hub.

After receiving your request, AEMO’s technical network officer contacts your technical

network contact to finalise specific details of the connection (such as IP addressing details).

Your request must comply with the " Registered participant entitlements" on page 9.

2.5.7 MarketNet access control

The participant ID interface to the MarketNet access control is a web-based application. For

more details, see "Changing your Participant ID password" on page 20.

For information regarding acceptable passwords, see "Security" on page 15.

2.6 User Rights Management (URM)

The user rights management system (URM) is a web application in the energy market

systems web portal. This system controls access by participant users to most applications. Allparticipant ID user credentials access rights are managed by your company's participant

administrator (PA) with the sole exception being the master access set up by AEMO during

registration. The PA is responsible for the management of their participant user’s access to

AEMO’s systems.

The primary IT security contact (as nominated on the participant ID’s registration form) is

the initial PA who can set up another user with the same access rights (that is, another PA),

unlock accounts, create new temporary passwords, and make participant users who have left

the organisation inactive.

Under AEMO’s security policy Electricity Market Management Systems Access Policy andProcedure, the passwords expire regularly. AEMO’s pre-production and production systems

are independently controlled, so you can have different credentials for each, even though they

may initially be the same.

User interaction with AEMO’s systems requires secure (HTTPS) access to AEMO’s private

network, MarketNet with a login and appropriate access rights, see "Data network

connection (MarketNet)" on page 8.

Table 6 on the facing page describes the user rights management process for the electricity

and gas markets.

© 2014 AEMO 12

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


http://www.aemo.com.au/About-the-Industry/Information-Systems#systems





















Table 6: user rights management for energy markets

Market Requirement

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

AEMO’s syst ems.

Gas Each participant user must complete a Gas Systems User Access Request and attach it to the

registration application. The form allows for access to multiple markets and multiple companies

for each participant user. For information about completing a request, see the relevant gas

market section in this document.

For more details about participant administration and user rights access, see Guide to User

Rights Management.

2.7 Understanding the set participant function

A company having multiple ABNs may have several participant IDs. The set participant

function in AEMO's web portals allows participant users to have a single user ID to perform

work for multiple participant IDs without logging out and logging back in again.

AEMO has made the use of single user ID logins available on the understanding that each

participant is responsible for the management of the accesses granted to each user. Security is every user’s concern and each participant administrator has a role in establishing and

maintaining effective control of access to sensitive information.

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

2.8 Software

AEMO provides sample software packages to assist with data validation and replicating data between AEMO's systems and participants' systems. Use of the software is subject to

understanding the following:

l The software is an example of the functionality only, and may not be of production

quality or fully tested.

l Participants must independently develop or acquire software to meet their needs, if the

software is insufficient for their use.

l Participants use the software or associated materials at their own risk. AEMO does not

assure that the software or associated materials are complete, free from errors, reliable,

© 2014 AEMO 13

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












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








and fit for particular purposes. Nor does AEMO assure that the software is free from

viruses and other programs that may affect other software or systems.

l Participants intending to use the software are responsible for independently verifying and

checking the accuracy, completeness, reliability, or suitability of the software orassociated materials.

l Software versions are updated for each new release. Participants using AEMO’s software

are responsible for ensuring they are using the current version. Change notices and

technical specifications advise participants of software changes for each release.

Table 7 below describes the sample software packages provided by AEMO.

Table 7: software packages provided by AEMO

Software Description Market

B2B Validation Module A validation application participants can embed in their B2B

systems allowing validation of an .XML file before it is deployed

to the MSATS B2B Hub.

Retail (MSATS)

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 to the MMS Data Model.

AEMO provides the Data Interchange applications to particip ants

to assist with the replication of data to their DBMS. Successfully

implementing and managing Data Interchange requires an

experienced IT team, planning, networking, database

management, batch file management, and disaster recovery. AEMO supp orts data replication to Oracle and SQL Server

databases. The licensing of the participant ID’s SQL Server or

Oracle data store is the responsibility of the participant. Scripts to

build the MMS Data Model are available for SQL Server and

Oracle database platforms, see MMS Data Model.

Participants use the Data Interchange web applications in the

EMMS web portal to:

n Subscribe to receive files in their participant folder on the

EMMS file server.

n Monitor their Data Interchange, Data Delivery, and Data

Sharing statuses.

For more details, see Data Interchange.

Wholesale

Participant Batcher Provides a simple batch interface to MSATS and B2B by removing

the detail of the file handshaking and leaving participants to deal

with the raw .ZIP files only . It transfers files using FTP from and

to the MSATS hub and does the entire message acknowledgement

and file manipulations as required by the MSATS batch file

interface.

Retail (MSATS)

Web Services An additional option to AEMO’s web portals, and batch or file

interfaces for system-to-system interaction with AEMO’s systems.It provides supported and secure web services to participants’

systems using their secure MarketNet connection.

Retail and

Wholesale

© 2014 AEMO 14

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


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








Software packages and documentation are available from Using Energy Market Information

Systems.

2.9 Security

In this section:

2.9.1 About security 15

2.9.2 Participant's security responsibilities 16

2.9.3 Excluding IP addresses in Microsoft Internet Explorer 17

2.9.1 About security

In accordance with security policy, AEMO routinely expires passwords for access to AEMO

systems. Expiry is normally advised through email (sent to the address set up as part of

registration process). The participant ID’s IT security contacts are A EMO’s primary contact

point for all issues affecting the shared responsibility of security of data and access to

AEMO’s systems.

Requests from a participant ID for changes to any details affecting the data exchange between

AEMO and the participant ID are subject to verification of authenticity with the participantID’s IT security contacts.

The obligations for maintaining security are shared by each participant company (and

participant ID) with AEMO. Each participant company has the primary responsibility for

password management for their participant users.

All data submitted to AEMO, or generated by AEMO is permanently stored in secure

databases. AEMO has implemented electronic, physical, and administrative safeguards that

provide a high level of data security. These safeguards are designed to prevent unauthorised

access to system data and to 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 with authorised

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.

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

© 2014 AEMO 15











System integrity is assured through disaster recovery measures, which include hardware

redundancy, systematic data backup and restoration, and the mirroring and replication of

data on geographically separated data storage and processing systems.

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

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

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

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

2.9 on previous page summarises the security responsibilities of participants.

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

2.9.2 Participant's security responsibilities

Table 8: participant's security responsibilities

Security

management

Ensuring mechanisms are in place to protect their internal networks from unwanted

traffic using their MarketNet connection.

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

systems.

Ensuring traffic from the internet and their internal networks is isolated from their

MarketNet connection.

Ensuring no disruption to the availability of AEMO’s systems by utilising

inappropriate processes such as repeated pinging, port scans and so on.

Ensuring no transmission or storage of inappropriate data.

Contacting AEMO’s Information and Support Hub if they suspect a virus may have

transported via AEMO’s systems.

Reporting to the AEMO Information and Support Hub any known or suspectedsecurity breaches that could allow unauthorised access to their own or other

participant organisations data on AEMO Systems.

Providing AEMO’s Information and Support Hub with contact details of specialist

managers for escalation and resolution of identified breaches to security.

© 2014 AEMO 16

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






Password

management

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 a

combination of numbers, upper case and lower case characters, punctuation and

special characters.

Ensuring no shared IDs.

Keeping passwords confidential.

Considering employee termination procedures in relation to AEMO passwords.

Market data access Respecting data access privileges and not attempting to access data they are not

authorised or entitled to access.

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

2.9.3 Excluding IP addresses in Microsoft Internet Explorer

Steps for excluding IP addresses in Microsoft Internet Explorer.

1. Either right-click the Internet Explorer icon then select Properties or double-

click the icon and select Tools>Internet Options.

© 2014 AEMO 17




2. Click the Connections tab.

3. Click LAN settings.

© 2014 AEMO 18




4. Click Advanced.

5. Add any necessary IP addresses within the Exceptions box. Click OK to commit

the Proxy Settings.

2.10 Passwords

In this section:

2.10.1 Changing your participant user password 19

2.10.2 Changing your Participant ID password 20

2.10.1 Changing your participant user password

The following information is a guide to the participant user passw ord format.

l For the rules and recommendations for setting passwords to access the AEMO private

domain MarketNet, see "Changing your Participant ID password" on page 20.

l For details regarding managing logins to specific systems and functionality, see the

Guide to User Rights Management.

l For help changing your password, see the online assistance in AEMO's web portals.

© 2014 AEMO 19

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












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 30 minutes.

If more than six attempts are made the account is locked. The count is reset once a

participant user successfully logs in.

l To unlock an account, you must call AEMO's Information and Support Hub and provide

your organisation's "secure code". Your company's PA can tell you the secure code if

you do not know it.

l After a password is changed, it cannot be changed again for 24 hours. If it requires

changing during this time, contact AEMO's Information and Support Hub.

l Whenever a participant user account is unlocked or password changed by AEMO's

Information and Support Hub, the participant user must send an email confirming the

request and stating that the request was not a security breach. If the participant user

suspects a security breach then they must report the matter to AEMO's Information

and Support Hub immediately so that action can be taken to secure the account.

Warnings:

l Before changing your password, you must disconnect all mapped drives to the

participant server.

l If you connect to MarketNet using an automatic FTP process, you must ensure that youstop the process (well in advance of each expiry date), change the password, modify the

process to use the new password then restart the process.

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.

© 2014 AEMO 21




l You cannot use a previously used password, or a variation—the system remembers the

last 12 previous passwords. The password rule algorithm checks the new password

against the previous 12 passwords and if it finds a sequence 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

Password advice

Review the password you are currently using, and if it is not strong, change it to an

appropriate combination of numbers, letters, special characters, with a length of at least

eight characters, however 12 is recommended. The strength of passwords is dependent 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 not write it downas this clearly reduces security, but you could use a particular pattern of keys, using the shift

key or holding the ALT key down select a number every second or third character, and

include a special character.

Select a word that is easy for you to remember, then insert numbers and special characters

at regular intervals (say every second or third character). As an example a password may be

Se1pt2em3be4r. (started off as the word September with a capital at the start, a full stop at

the end, and the numbers inserted every two 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, see "Using the Participant File Server

Password Changer application" on page 25.

Prerequisites

To use the web-based password changer:

l You need a PC with access to MarketNet. Participants need to ensure they have access

to the relevant AEMO file server using MarketNet from the computer before testing the

© 2014 AEMO 22




password change facility.

Note: the web-based password changer resides on AEMO’s secure MarketNet private

network.

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

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 the password is

being changed.

Instructions

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

1. On a MarketNet-connected machine, 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 Enter Network

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 the Domain and then click OK .

© 2014 AEMO 23




7. The "MarketNet Password Change Website" displays a form, you must enter all the

information in this form. It should look similar to this:

This is your FTP access user name. It is the same user name you entered in the Enter

Network Password dialog box

8. In the NEMNET Username box, enter your user name and press the TAB key Note:

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 server

before proceeding.

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

Logging off is imperative to set the new password correctly.

To restart other processes (if any), on all computers connecting to the shared folders on the

AEMO file server, modify your automatic FTP processes to use the new password and then

restart the processes.

© 2014 AEMO 24




Using the Participant File Server Password Changer application

This section describes the steps for using the EMMS File Server Password Changer

application. For help using the web-based password changer, see "Using the web-based

password changer" on page 22.

Prerequisites

To use the EMMS File Server Password Changer application:

l You need an installation of Participant Data Replication Batcher with standard

properties configuration file.

l A downloaded copy of the latest version of the application EMMS File Server Password

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’s JRE 6 to

run. The “Oracle JRE 6” download is available from "Java SE Downloads",

http://www.oracle.com/technetwork/java/javase/downloads/index.html.

l Stop all automatic FTP processes connecting to AEMO’s file server for which the

password is being changed.

Instructions

To change your participant ID password using the EMMS File Server Password Changer

application:

1. Double-click the installation file, FileServerPasswordChanger_<version>.jar to start

the installer. This is the .JAR file decompressed insee "What AEMO Provides" above on

page 25.

© 2014 AEMO 25

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 see path

selection.

© 2014 AEMO 26




4. Click Browse to select the location of the pdrBatcher installation for which the

password 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 updating passwords on

pdrBatcher installations using a standard configuration.

Please ensure ALL pdrBatcher processes are stopped before continuing with this step.

Failure to stop all running processes may result in your access to AEMO’s file server in

MarketNet becoming locked out.

6. Confirm the configuration details of the pdrBatcher installation for which the password

needs to be updated and click Next to see the MarketNet password change window.

© 2014 AEMO 27




7. Click the MarketNet password change page link which opens a new web browser

window allowing the password to be changed. The process is the same as described in

see "Using the web-based password changer" on page 22.

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

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 the MarketNet user

account. The password to be entered is the new password.

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

© 2014 AEMO 28




10. The Processing form displays the log of configuring your software installation

according to the selected options and settings.

If an error occurs, click Previous and correct the required settings. When the

processing 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 the change worked

correctly:

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

2. Start the pdrBatcher process and confirm connectivity by viewing the log file to

ensure there are no connection errors.

2.11 Data sharing

In this section:

2.11.1 About data sharing 30

2.11.2 Data sharing example 31

2.11.3 Data sharing set-up 31

2.11.4 Data sharing removal 32

© 2014 AEMO 29




2.11.1 About data sharing

Data sharing is handled using Data Interchange. A data sharing requirement may emerge, for

example, due to a merger with, takeover of, or sale of another participant ID. The

requirement met by implementing data sharing is to use one participant ID’s IT system tomanage access and process the data for two or more participant IDs using one participant

ID’s set of folders in the participant file server.

Sharing data achieves the business outcome of having just one data interchange system to

produce an MMS Data Model database containing the data for two or more participant IDs.

The only other way to achieve the same objective is to have a Data Interchange system for

each participant ID, then have a back-end process to merge each of the single participant ID

databases into a common database.

AEMO’s wholesale energy market systems allows a participant ID to share data with anotherparticipant ID, subject to an authorised request. Implementing data sharing means the full

Data Interchange data set (including private data) for the requesting participant ID is made

available to another participant ID’s sets of folders in the participant file servers, as

nominated in the request. The sharing of data is for both pre-production and production.

A key saving is the bandwidth and download time for the public data, since it is common to

both participant IDs. Having all the data in one database can be both an advantage and a

disadvantage.

It is possible to arrange for one participant ID to receive data for more than one other

participant ID or to arrange for both participant IDs to get the data for both participant 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 ID gets the data for both

participant IDs).

Data sharing is not cascaded. This means if a participant ID shares its data with another

participant ID, and the first participant ID is already receiving data shared from a third

participant ID, the data for the third participant ID is unseen by the second participant ID.

To make the second participant ID receive the third participant ID’s data requires a specificrequest to AEMO by those two participant IDs.

Each participant ID can check its own data sharing status in the energy market systems web

portal, see Figure 3 on the facing page.

© 2014 AEMO 30




Figure 3: data sharing in the energy market systems web porta l

2.11.2 Data sharing example

For example, participant ID 1 wishes to manage both participant ID 1 and participant 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 to both

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 they receive for

their participant ID via EMMS Data Subscription services. A participant ID receiving

data for another participant ID does not impact the other participant ID’s file

subscriptions.

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

2.11.3 Data sharing set-up

Sharing Data Interchange data from another participant ID means you must have a data

interchange implementation configured at your site and the Data Subscription web

application set-up.

© 2014 AEMO 31




To set up data sharing, understand what you wish to achieve and ensure your IT systems can

process data for multiple participant IDs from the one file. Ensure downstream processes,

procedures, and systems can handle the database with data for multiple participant IDs.

To formally request data sharing:

l The formal request must nominate a business contact with the authority to request or

authorise the sharing of private data from one business entity to another, plus

nominate a technical contact to directly implement changes at the participant ID site

needed to put the data sharing into place. The request must specify the earliest date for

implementation in pre-production. Production implementation needs separate

arrangement, made by agreement between all parties.

l If there are two (or more) companies (that is, having different ABNs), each company

must provide a request to AEMO's Information and Support Hub, on their respective

company letterhead, signed at senior management level, detailing their specific

circumstances. Include the following template paragraph authorising the sharing of

private data.

<Company name> < ABN>for <participant ID> <requests|authorises> AEMO to make

available <company name> < ABN>for <participant ID> EMMS full subscription data

set (including private data) to <company name> < ABN><participant ID> via the

EMMS Data Interchange and Data Subscription services. This is to remain in place until

advised in writing. A letter from <Company name> < ABN> for <participant ID>

confirming this is forthcoming.

l Participant companies with the same ABN for all participant IDs involved only need a

single request from the company registered for their participant IDs.

l After confirming full agreement by all affected parties (including technical, as

necessary), on or after the requested implementation date, AEMO processes the sharing

request into pre-production, and advises completion to the requestor.

l Similarly, processing the sharing request into production involves confirming full

agreement by all affected parties (including technical, as necessary).

2.11.4 Data sharing removal

One situation requiring removal of data sharing is for a change in the legal ownership or

control of a participant ID involved in sharing of data. To remove data sharing at any time,

only one involved participant ID needs to ask for its removal.

To formally request withdrawal from a data sharing arrangement, submit the request on a

company letterhead, signed at senior management level, detailing the specific circumstances.

Include the following template paragraph authorising the withdrawal of private data sharing.

© 2014 AEMO 32




<Company name> < ABN>for <participant ID> requests AEMO 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 ID is

removed.

A participant company purchasing an existing registered participant ID can contact the

AEMO's Information and Support Hub to ask if any data sharing arrangement is in place for

that participant ID, and if so, can request the sharing be removed.

2.12 Current baseline data

In the same folder as the participant ID’s file server folders, AEMO updates the

\MarketData\Baseline folder daily with current baseline data conforming to the MMS

Data Model. The baseline data files are in a format suitable for loading any of the relevant

database tables, simply by copying each file into the input folder for the “Participant Data

Replication Loader”, see Data Interchange.

Participant ID users need to use the current baseline data for initial population of a new

instance of a database conforming to the MMS Data Model, and can use the data for

repopulation of relevant tables (after truncation).

Baseline data are the static details in the MMS Data Model, and excludes historical data, see

"Monthly data on DVD" below .

2.13 Monthly data on DVD

Fee-paying participant IDs can subscribe to receive monthly archive data sets by emailing a

request to the AEMO's Information and Support Hub. The email must nominate a person

recognised by AEMO as being authorised to make the purchase (usually the IT security contact) and the delivery address.

The data conforms to the MMS Data Model. The monthly archive data sets are not intended

for the historical recovery of public data for a database receiving a data feed using Data

Interchange.

Each monthly archive data set provides the energy market systems historical public data and

replication software. The monthly archive data set is a source for obtaining historical data

for analysis of runs and includes:

© 2014 AEMO 33






l EMMS Data Interchange software. Documentation and software supporting the data

interchange processes in the energy market systems.

l MMS Data Model historical data – SQL Loader format. Non-confidential historical data

for the MMS Data Model including the Oracle SQL Loader control files.l MMS Data Model historical data – .CSV files. Non-confidential historical data for the

MMS Data Model in .CSV files. Some files are in a format incompatible with pdrLoader

configured for data interchange.

l Other Historical Data – .CSV Files. Non-MMS Data Model non-confidential historical

data in .CSV Files.


2.14 System transfers and deregistration

2.14.1 System transfers

AEMO operates duplicates of systems. Occasionally, AEMO advises (by email) of a planned

changeover from an operational system to an alternative. AEMO performs the changeovers in

a way to minimise market impacts. However, there can be times when particular functions

are interrupted or are temporarily unavailable, as advised by email. participant ID systems

and processes need to cater for such interruptions to AEMO services. Some examples of

effects include:

For MSATS, a changeover can result in no connection to AEMO’s MSATS file server for up to

10 minutes whilst B2B data synchronises. This impacts both the “Participant Batcher” and

B2B. Because applications and web browser sessions can lose connection, they may require a

restart from the participant ID end. Any unacknowledged files require resubmission by the

participant ID, because, in effect, 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 very important to keepchecking for, and moving, participant ID files, either manually or using 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.

2.14.2 Deregistration for IT systems

Deregistration is like a transfer, except there is no transferee see, Guide to Market Systems -

NEM Change of Ownership. Effective on the date of deregistration, effects include:

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

© 2014 AEMO 34


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
















Chapter 3 Interfaces

3 Interfaces

This chapter explains the different IT interfaces available for participants to access AEMO's

systems.

In this chapter:

3.1 Energy market systems web portal 36

3.2 Participant file servers 42

3.3 Web services 44

3.1 Energy market systems web portal

In this section:

3.1.1 About the web portal 36

3.1.2 Why use the web portal 36

3.1.3 Who can use the web portal 37

3.1.4 System requirements 37

3.1.5 Gaining access to the web portal 38

3.1.6 Using the web portal 38

3.1.7 Web-based interf ace URLs 41

3.1.1 About the web portal

The web portal is the initial access point for AEMO’s web-based applications. It provides asecure interf ace for authorised users to interact with AEMO’s web-based applications. The

web portal is suitable for use by small operators in place of setting up Data Interchange, see

"Software" on page 13.

3.1.2 Why use the web portal

The web Portal can cut participant’s cost and client side footprint by:

© 2014 AEMO 36




l Reducing the requirement for participants to maintain an IT infrastructure at their site.

l Allowing participant business user access 24 hours a day, 7 days per week for 365 days

per year—wherever a connection to MarketNet is available.

l Being fully maintained and supported by AEMO.

l Being available to all participants at no additional cost.

l Providing a secure web interface with user access rights managed by participants.

l Allowing the use of multiple participant IDs using the set participant function, see

"User Rights Management (URM)" on page 12.

l Being easy to learn with guides available for each web application—requiring less staff

training.

l Providing a consistent look and feel across each web application.

3.1.3 Who can use the web portal

Prior to obtaining access to the web portal, access to MarketNet must be obtained and

established. It is likely that your organisation already has access to MarketNet, particularly if

it is a registered market participant. However, if your organisation does not have access to

MarketNet, this must be completed first. For information about obtaining access to

MarketNet, see "Data network connection (MarketNet)" on page 8.

An initial participant administrator (PA) is set up by AEMO as part of the participant

registration process. For further information regarding registration and access to AEMO’ssystems, see "Setting up your IT Systems" on page 46.

To log on to an AEMO system requires credentials, available from your company's

participant administrator. For help setting up participant user access, see the Guide to User

Rights Management.

3.1.4 System requirements

The Energy Market Systems are accessed using a web browser and require:

l Microsoft Internet Explorer (IE) version 8. AEMO tests all web applications on IE 8

and cannot guarantee compatibility with later versions. Participants can try

compatibility view with later IE versions (Tools>Compatibility View).

l A monitor capable of 1024 x 768 screen resolution.

l Access to MarketNet.

l A user ID, password, and the website address where the application is located on

AEMO’s network, provided by your company's participant administrator.

l The Energy Market Systems web applications run on both Windows and Unix-like

operating systems.

© 2014 AEMO 37

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









For more details about MarketNet, see "Data network connection (MarketNet)" on page 8.

3.1.5 Gaining access to the web portal

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

1. Check that you have the items listed in "System Requirements".

2. Decide on the required application, for help see the relevant market section in this

guide.

3. Download the relevant guide containing information about the user rights access your

participant administrator (PA) requires to set you up. You can find guides on the Using

Energy Market Information Systems web page.

4. Ask your company's PA to give you user rights access to the application. If you don'tknow who your company's PA is contact AEMO's Information and Support Hub, Phone:

1300 AEMO 00 (1300 236 600) and follow the prompts. Email:

[email protected]

For help setting up user rights access your company's PA can reference the Guide to

User Rights Management.

5. Access the energy market systems web portal, see "Using the web portal" below.

3.1.6 Using the web portal

In this section:

Signing in and out

To sign in to the energy market systems web portal:

1. Using your web browser, access the energy market systems web portal, either:

o Pre-production: https://portal.preprod.nemnet.net.au

o Production: https://portal.prod.nemnet.net.au

Note: the energy market systems web portal provides you with a clear indication of the

environment you are working in by providing a different border colour around the

home page. The production environment has a grey border and the pre-production

environment has a green border.

© 2014 AEMO 38



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
















2. Click Energy Market Systems

3. Sign in using the User ID and Password provided by your company's PA.

4. On the left navigation pane, select the menu item for your relevant web application.

© 2014 AEMO 39




5. For assistance using the web portal, click the menu item you require help with and

then click Help in the top-right corner.

To sign out:

l Click Sign Out in the top-right corner.

Adding and loading favourites

You can add favourites to the menu and have them load automatically each time you sign in.

l Add the required menu to your favourites by clicking the yellow star next to the menu

item in the navigation pane.

l Load your favourites automatically each time you sign in to energy market systems by

© 2014 AEMO 40




clicking the arrow next to the menu item in your favourites folder.

For help using favourites, see the on-line assistance in the energy market systems web

portal. Click the Favourites folder and then click Help in the top right-hand corner.

3.1.7 Web-based interface URLs

To access participant-only addresses, requires:

l Connection to MarketNet, see "Data network connection (MarketNet)" on page 8

l Credentials to access the web application or file share.

The primary access uses AEMO’s web portals, requiring the use of a supported web browser.

Table 9 below lists the energy market systems web portal pre-production and production

URLs.

Table 9: energy market systems web portal production a nd pre-production URLs

Name Web addresses (URL)

Energy market systems web portal pre-production

(single web portal interface)

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

Energy market systems web portal production

(single web portal interface)


Table 10 on the facing page list direct access URLs for various market systems.

© 2014 AEMO 41



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




Table 10: AEMO URLs

Name URL Note

EMMS pre-production https://mms.preprod.nemnet.net.au/mms/ 1

EMMS production https://mms.prod.nemnet.net.au/ 1

MSATS pre-production https://msats.preprod.nemnet.net.au/msats/ 1

MSATS production https://msats.prod.nemnet.net.au/ 1

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

NOS production https://nos.prod.nemnet.net.au/ 1

OPDMS pre-production https://opdms.preprod.nemnet.net.au/opdms/ 1

OPDMS production https://opdms.prod.nemnet.net.au/ 1

Industry QC https://td.preprod.nemnet.net.au/td/ 2

AEMO's Information and Support Hub—Customer

Portal

https://infra.preprod.nemnet.net.au/infra/ 2

Domain account password change http://146.178.211.25 3

Notes

1. For help setting up participant user access, see Guide to User Rights Management.

2. Participants must subscribe for access, contact AEMO's Information and Support Hub.

3. For help, see "Changing your Participant ID password" on page 20.

3.2 Participant file servers

In this section:

3.2.1 About file servers 42

3.2.2 Participant file server folders 43

3.2.3 File-based interface URLs 43

3.2.1 About file servers

AEMO’s MarketNet provides access to folders for batch file transfer between AEMO and

participant IDs. MarketNet is the communications infrastructure that allows sharing across

the network, see "Data network connection (MarketNet)" on page 8.

© 2014 AEMO 42

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


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

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


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






http://146.178.211.25/

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

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

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


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

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

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

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


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




Each energy market system has a file server, and each has production (live data) and pre-

production (test data). Each participant ID has secure read-write access to their own set of

folders, plus read-only access to folders accessible by all participants (that is, commonly-

shared folders). The commonly-shared folders contain public data. The private folders are for

secure transfer of data between the participant ID systems and AEMO (such as bidding and

settlement invoices). For the IP addresses, see "File-based interface URLs" below.

For growth planning purposes, it is useful to know that the largest contributors to bandwidth

usage are normally the wholesale and retail market systems.

For information regarding security, see "Security" on page 15.

3.2.2 Participant file server folders

Each participant ID has secure read and write access to folders for the wholesale and retail

systems, each with production and pre-production versions. These folders are for

communication between participant IDs and AEMO. Each participant ID set of folders has at

least two subfolders, \import and \export, with naming being relative to the participant ID.

Further subfolders are for specific subsystems.

The simplest method for access to participant ID folders is to use an FTP client capable of

using passive FTP to put and get files. This is only practical for small amounts of files and

requires the participant ID user to know the login and password for direct access to the

participant file server.

The recommended method for accessing the secure folders and replicating large amounts of

data between AEMO's systems and a participant's DBMS conforming to the MMS Data Model

is to use a batcher program such as Data Interchange, see "Software" on page 13.

For small operators AEMO recommend using the web portal interface to retrieve and upload

files, see "Energy market systems web portal" on page 36.

3.2.3 File-based interface URLs

The general mappings are outlined in the following table.

Table 11: file-based interface addresses

Energy market systems production ftp://146.178.211.63

Energy market systems pre-production ftp://146.178.211.25

MSATS production ftp://146.178.211.205

MSATS pre-production ftp://146.178.211.225

© 2014 AEMO 43

ftp://146.178.211.225/

ftp://146.178.211.205/

ftp://146.178.211.25/

ftp://146.178.211.63/




Additional specific mappings are in the following table, with <participant ID> being your

company's Participant ID.

Table 12: Additional specific mapping addresses

private participant data <production or pre-production>/<participant ID>

market data <production or pre-production>/MarketData

EMMS data to initially populate RDBMS

conforming to MMS Data Model

<production or pre-production>/MarketData/Baseline

MSATS data <production or pre-production>/<participant ID>

To change the password to access the secured private file collections, use a web browser to

access the domain account password change website at http://146.178.211.25. For more

details, see "Changing your Participant ID password" on page 20.

3.3 Web services

AEMO's Web Services provide supported and secure web services to participants’ systems

using their secure MarketNet connection. The web service is provided by AEMO’s web

services server responding to a HTTPS request. The request is stateless, or self-contained,

having no dependency on an y prior or future request. It contains all data required to both

define the request and authenticate the requestor. The response is a block of data sent to theparticipant’s machine making the request. The response is not required to be readable by a

person.

AEMO’s Web Services use existing messaging standards such as aseXML and CSV,

maintaining maximum flexibility and consistency for participants who are free to specify data

formats or payloads that suit the target system. The market systems standard is the transfer

of aseXML documents between participant gateways and the market systems.

3.3.1 Web services system requirements

l Microsoft Internet Explorer (IE) version 8. AEMO tests all web applications on IE 8

and cannot guarantee compatibility with later versions. Participants can try

compatibility view with later IE versions (Tools>Compatibility View).

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

l A user ID and password, provided by your participant administrator (PA), set up with

access to the required web service.

User accounts and user administration is done in the energy market systems web

portal. PAs select the appropriate entity in the Maintain Rights menu, for help seeGuide to User Rights Management.

© 2014 AEMO 44

http://146.178.211.25/






http://146.178.211.25/




l The Web Services Client Software runs on either the Java TM Platform, Standard

Edition 6 (developer version 1.6.0), or the Microsoft .NET Framework 4®.

To demonstrate the web services function correctly at participant sites and to facilitateintegration into participant systems, AEMO provides web services client software.

Participants can use the approach taken in the web services client software to implement

their own custom web client into their gateway system. To obtain software and guides, see

"Web Services" on Using Energy Market Information Systems.

© 2014 AEMO 45

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










IT access credentials are sent to your IT security contact during the registration process.

4.2 Checklist for setting up your IT systems

Use this checklist to help you plan your IT system setup. It is a generic checklist of activities

required for setting up your IT systems. For more details about each market’s IT systems,

see the relevant market section in this guide.

Table 13: checklist for setting up IT systems

What Who How

1 Decide on

network connection

options

Participant Identify and plan the networking and IT work at your end with your

technical teams. AEMO’s default connection bandwidths for new connections are more than adequate for all circumstances, except the

most unusual, and can be changed later, see "Data network connection

(MarketNet)" on page 8.

Participants arrange the subscription link, hardware, and software with

their chosen telecommunication provider—including the access costs.

2 Familiarise and

plan IT systems

setup

Participant AEMO has numerous systems with multiple interfaces to provide for the

needs of all participants. Careful planning is required to decide what

your specific requirements are for interfacing with AEMO’s systems, for

example:

n

How will you replicate data between your systems and AEMO’s?n Do you have a light demand for data transfer suitable for using

the web portal interfaces?

n Do you have a heavy demand for data transfer requiring an IT

infrastructure at your end?

n Do you have an experienced IT team that can maintain the IT

infrastructure at your end and update it for each six-monthly

release cycle?

To familiarise yourself with AEMO’s systems for your market, read the

relevant market section in this guide.

3 Set up data

network connection

Participant

AEMO

The network connection is set up by the participant’s network specialist

and AEMO network specialists (and any third parties as organised by the participant) for their respective ends. The implementation time from

point of technical network staff contact to implementation depends on

such factors as:

n Connection type (VPN takes about 7 to 10 business days, Telstra

advise a dedicated connection takes at least 20 business days).

n Participant equipment.

n Participant configuration.

n Participant time input.

Note: registered participants with an existing MarketNet connection do

not require another one. They can however, make changes to an existing

MarketNet connection, see " Making changes to your MarketNetconnection" on page 12.

© 2014 AEMO 47



Chapter 4 Setting up your IT Systems

What Who How

4 Test the data

network

connectioncommunicates

to AEMO

Participant Testing the network connection demonstrates a successful link to

MarketNet without requiring access into the domain or systems (such as

a “ping” test).

5 Set up access to

AEMO’s market

systems

AEMO AEMO takes approximately 15 business days to set up your IT sy stems

access concurrently with your registration application, and your data

network connection. AEMO contacts the IT security contact provided in

the registration application, advising the IT access credentials and other

useful information for both pre-production and production (production

is not yet activated).

6 Set up pre-

production IT

systems

Participant You can now set up your required pre-production IT systems at your

end. For more details about AEMO’s market systems, see the section in

this guide for your market.

7 Set up data

exchange to

AEMO

Participant Setting up data exchange to AEMO’s systems is complex and requires

careful planning by an expert IT team.

For more specific details of AEMO’s data exchange systems, see the

relevant market section in this guide.

8 Set up user

access to IT

systems

Participant The IT security contact who becomes the participant administrator

identifies and sets up participant user access to AEMO’s systems, see

"User Rights Management (URM)" on page 12.

9 Test pre-

production ITsystems

Participant Using a test system connected to AEMO’s pre-production is ideal for

training and familiarisation. Ensure you can see the folders for yourparticipant ID in each system. Access any other systems relevant to you.

Perform all the expected operations for your business needs, such as

bidding, uploading files, or reporting.

Ensure your pre-production syst em is separate from your production

system.

10 Set up

production IT

systems

Participant AEMO approves and activates your production environment after a

period in pre-production of at least 5 to 10 business days (and may be

much longer). Set up your live systems (production) to be separate from

your test systems (pre-production). Adjust your production processes

based on your experience with pre-production.

11 Test production

IT systems

Participant You are now “live” and can access and enter data into AEMO’s

production environment.

AEMO’s Information and Support Hub provides more details about AEMO’s systems as part

of the registration process.

© 2014 AEMO 48



Chapter 5 Declared Wholesale Gas Market

5 Declared Wholesale Gas Market

This chapter provides an overview of the participant Gas Market System (GMS) operating in

the Declared Wholesale Gas Market (DWGM). It is relevant to IT decision making during theregistration process and provides an understanding of what is required to interface with

AEMO’s market systems. Figure 5 on next page provides an overview of the IT systems in the

DWGM.

In this chapter:

5.1 About the DWGM 49

5.2 DWGM IT interfaces 50

5.3 DWGM IT systems 50

5.4 DWGM participant categories 51

5.5 DWGM systems user access 52

5.1 About the DWGM

Each day an "imbalance" exists between the gas supplied by a participant, and the gas

consumed by that participant and their customers. The DWGM determines a market price

used by all participants to trade their imbalances. In addition to pro viding a mechanism to

trade imbalances, the DWGM also provides the framework for many other essential

functions, including:

l Gathering information for efficient pipeline operations.

l Maintaining a reliable and secure system for the transportation of gas.

l Management of metering data for operational and market balancing.

l Provision of a market based balancing service that determines price and gas flow

quantities.

l Management of market settlement and prudential risk.

For more details:

l About DWGM, see Declared Wholesale Gas Market Guides, Forms and Templates

l About DWGM registrable capacities, see Registration.

l About DW GM Prudential Dashboard, see Using Energy Market Information Systems.

© 2014 AEMO 49

http://www.aemo.com.au/Gas/Wholesale-Gas-Markets/Victorian-Wholesale-Market/Declared-Wholesale-Gas-Market-Guides-and-Forms










http://aemo.com.au/Electricity/Registration












Figure 5: DWGM IT systems overview

Participants are required to comply with the procedures set out by AEMO, which define the

communication interfaces and infrastructure for electronic communications between AEMO

and participants to support the operation of the gas market, see Declared Wholesale Gas

Market Rules and Procedures.

5.2 DWGM IT interfaces

Participants can use several interfaces to interact with DWGM IT systems—file, web, and

web services.

Table 14 : DWGM IT interfaces

Interface Function

Web portal (HTTPS) The WEX and the MIBB both provide web browser interfaces to access the

processes and functions of the DWGM.


(HTTPS)

The WEX allows direct uploading of files to the web portal interface.

File server (FTP) The MIBB provides an FTP file interface for participant interaction with file

servers. For more details, see "Participant file server folders" on p age 43

Web services (HTTPS) The WEX system allows CSV file uploading using HTTPS.

5.3 DWGM IT systems

The IT system operating in the DWGM is called the Gas Market System (GMS). Table 15

below summarises the systems available to participants in the GMS.

Table 15: DWGM IT systems

IT system Interface Description

Market Web portal The MIBB is the interface through which AEMO communicates with gas

© 2014 AEMO 50

http://www.aemo.com.au/Gas/Wholesale-Gas-Markets/Victorian-Wholesale-Market/Declared-Wholesale-Gas-Market-Rules-and-Procedures











Information

Bulletin Board

(MIBB)

File server market participants. It performs the following functions:

n Providing transaction interfaces with external market

participants.n Reporting market information.

n Publishing system-wide notices to market participants and the

public.

Access to the reports depends on a user’s security privileges, which fall

into three general classes:

n Public: available to everybody, including members of the public.

There is no security control over this information.

n All participants: available to all organisations participating in the

gas market.

n Participant confidential: available only to an individual or a

restricted group of participants.

The generation and publishing of a report can be initiated in three ways:

n Daily at a pre-determined time.

n Triggered by an event.

n Forced to run by the administrator.

AEMO publishes a listing of the market reports on its website, User

Guide to MIBB reports. The published details can include (but are not

limited to) purpose, format, contents, type of access, frequency of

reporting, and specification of the data fields.

Web Exchanger(WEX) Web portalFile upload

Web service

The WEX provides the interface for market participants to submit:n Market bids (injections and controllable withdrawals).

n Demand forecast (uncontrollable withdrawals).

n Injection hedge nominations.

n Agency injection hedge nominations.

n Agency confirmations.

AEMO use the submitted information as input into the MIBB. For more

information, see Web Exchanger User Guide.

5.4 DWGM participant categories

Table 16 below describes the relevant functionalities used in DWGM for each participant

category. For more details about registration, see Registration.

Table 16: DWGM functionalities used by each registrable capacity

Registrable capacity WEX MIBB

Interconnected transmission pipeline service provider

Storage provider

© 2014 AEMO 51

http://www.aemo.com.au/Gas/Operational-Data/Data-Guides-and-Manuals














Registrable capacity WEX MIBB

Producer

Market participant - producer

Market participant – storage provider

Market participant – transmission customer

Market participant - distribution customer

Market participant - retailer

Market participant - trader

5.5 DWGM systems user access

Each participant user must complete a Gas Systems User Access Request and attach it to the

registration application. The form allows for access to multiple markets and multiple

companies for each participant user.

The request is an interactive electronic form that changes according to your selections, it

must be completed using Adobe Reader version 9 or above. Please do not print the request

and complete it manually. For help completing the form, see Figure 6 on the facing page.

© 2014 AEMO 52









Figure 6: DWGM user access request

© 2014 AEMO 53



Chapter 6 Gas Bulletin Board

6 Gas Bulletin Board

This chapter provides an overview of the National Gas Market Bulletin Board (BB).

In this section:

6.1 About the BB 54

6.2 BB IT interfaces 55

6.3 BB website 55

6.4 BB participant categories 55

6.5 BB coverage 56

6.6 BB operation 57



6.1 About the BB

The Bulletin Board’s objective is to facilitate trade in gas over the relevant pipeline system,

by making market information available to registered users, and other interested parties, see

Figure 7 below .

For more details:

l About the BB, see Bulletin Board documents.

l About registrable capacities, see Registration.

Figure 7: BB overview diagram



and participants to support the operation of the gas market, see the Bulletin Board

Procedures.

© 2014 AEMO 54

http://www.gasbb.com.au/








6.2 BB IT interfaces

Participants can use web portal and file interfaces to interact with the BB, see Table 17

below.

Table 17: BB interfaces

Interface Function

Web browser (HTTPS) Use the web browser interface to view and download information from the BB.

File upload to web

browser (HTTPS)

Use the web browser interface to upload files directly to the BB.

File server (FTP) Use the file interface to upload and download information to the BB.

6.3 BB website

Table 18 below summarises the two areas of functionality available to participants in the BB.

Table 18: BB functionality

Functionality Interface Description

A publicly available area Web browser Reports available t o registered users and any interested members of the public.

A registered users’ only

area

Web browser

File upload

File server

Information in this area is for example, the “Emergency Page”,

providing support for the National Gas Emergency Response

Advisory Committee (NGERAC) and jurisdictions, allowing sharing

of emergency information amongst registered participants (once the

emergency page is activated by NGERAC or a jurisdiction). A

participant user must register to access the registered users’ only

area, or upload information.

Each BB participant has exclusive access to their own transaction

log report stating the status of the files provided to the BB

operator.

Participants who are facility operators or shippers on BB pipelines must register to use the

BB.

6.4 BB participant categories

Table 19 on the facing page describes the mandatory and eligible registrable capacities forthe BB. For more details about registration, see Registration.

© 2014 AEMO 55





Table 19: BB mandatory and eligible registrable capacities

Registrable capacity Mandatory Eligible

BB Shipper

BB Storage Provider

BB Pipeline Operator

Production Facility Operator

AER/AEMC/ERA

Authorised Representatives

BB Transmission Pipeline

Distribution Pipeline

Gas-fired Electricity Generator

Gas Network Distributor

Gas Retailer

Large End User

Member of NGERAC

Producer

Regulatory Bodies/Government

Service Provider of a pipeline connected to a BB Facility

Storage Provider

6.5 BB coverage

The pipeline systems and facilities covered by the BB include all pipelines identified as BB

pipelines, and all production and storage facilities connecting directly or indirectly to those

pipelines—other than facilities exempted by the BB operator.

The BB does not cover gas transmission pipelines, and production and storage facilities in

Western Australia and the Northern Territory.

© 2014 AEMO 56






Figure 8: BB home pag e

For help using the BB, see the Bulletin Board User Guide.

6.8 BB user access

6.8.1 Registered user access

Participant users who undertake BB transactions, or require access to the emergency page on

behalf of the organisation must register individually with the BB operator to obtain a

username and password for access to the secured section. Registered users can upload and

download transactions, one at a time, using the BB web-upload facility, or upload multiple

transactions using FTP.






and complete it manually.

© 2014 AEMO 58












6.8.2 Registered user access types

There are two types of access for registered BB users:

1. Secure access only is for daily operations such as transaction uploading. This accesstype can also view the emergency page but cannot write to the emergency page. In the

Gas Systems User Access Request, this access type is the default option automatically

selected for “I will use this account to login to the Bulletin Board using the website

interface to either, upload data or manage my account password.”

l Secure access and emergency page upload enables users to upload information to

the BB and provides access to upload information to the emergency web page. In the Gas

Systems User Access Request, this access type displays when Yes is selected for “I will

use this account to upload information to the Bulletin Board emergency pages”.

The access type depends on whether participant users are required to upload

information, or to view the emergency page.

© 2014 AEMO 59



Chapter 7 Gas Supply Hub

7 Gas Supply Hub

This chapter provides an overview of the IT systems in the Gas Supply Hub (GSH). It is

relevant to IT decision making during the registration process and provides an understandingof what is required to interface with AEMO’s market systems. Figure 9 below provides an

overview of the IT systems in the GSH.

In this chapter:

7.1 About the GSH 60

7.2 GSH IT interfaces 61

7.3 GSH IT systems 61

7.4 GSH participant categories 62

7.5 GSH systems user access 62

7.1 About the GSH

The GSH consists of a trading exchange for the wholesale trading of natural gas. It also

pro vides Settlement, Prudential, Delivery Quantity, and Reporting services to trading

participants.

For more details:

l About GSH, see Gas Supply Hub Guides.

l About GSH registrable capacities, see Registration.

l About software and guides, see Using Energy Market Information Systems.

Figure 9: GSH IT systems overview

© 2014 AEMO 60







http://www.aemo.com.au/Gas/Market-Operations/Gas-Supply-Hub







Participants must comply with the Gas Supply Hub Exchange Agreement that sets out the

terms of participation in the gas supply hub and the terms governing transactions entered

into through the exchange. Applicants for membership in the exchange must sign an

agreement with AEMO, agreeing to be bound by the exchange agreement.

7.2 GSH IT interfaces

Participants can use several interfaces to interact with GSH IT systems—file, web, and web

services, see Figure 9 on previous page.

Table 20: GSH IT interfaces

Interface Function

Web portal (HTTPS) The GSH provides web portal interfaces to access the web applications in the GSH.


(HTTPS)

The GSH allows direct uploading of files to the web portal interface or the

participant file server.

File server (FTP) Each participant ID has secure read and write access to folders for production and

pre-production systems. These folders are for communication between participant

IDs and AEMO. For more details, see "Participant file server folders" on page 43

AEMO provides a set of software applications called Data Interchange to assist

participants with the replication of data to their DBMS. Successfully implementing

and managing Data Interchange requires an experienced IT team, planning,networking, database management, batch file management, and disaster recovery.

Participants use the Data Interchange web applications in the EMMS web portal

to:

n Subscribe to receive files in their participant folder on the EMMS file server.

n Monitor their Data Interchange, Data Delivery, and Data Sharing statuses.


Windows application A locally installed trading application that connects to AEMO over MarketNet.

7.3 GSH IT systems

Table 21 below summarises the applications available to participants in the GSH.

Table 21: GSH IT systems


Trayport Exchange

Trading System (ETS)

Windows

application

The ETS allows trading participants to submit orders to buy or

sell gas at the various t rading locations within the gas supply hub. The ETS matches the orders and forms trades between

© 2014 AEMO 61



http://aemo.com.au/Gas/Market-Operations/Gas-Supply-Hub/Legal







Chapter 7 Gas Supply Hub


participants.

GSH Delivered Quantity Web portalFile upload Used by trading participants to submit new delivered quantity data and confirm existing delivered quantity submissions.

Participants can also provide AEMO with delivered quantity data

by uploading a .CSV file to the particip ant file server.

GSH Prudential

Dashboard

Web portal Provides participants with their latest prudential information. The

dashboard shows exactly the same information that AEMO uses

in its prudential assessments and provides participants with

useful information about their accrued financial position with

AEMO.

GSH Publishing Direct Web portal Provides participants with access to GSH reports and statements

published by AEMO. Participants can subscribe to reports for

automated delivery each time a new report is published.

GSH Reallocations Web portal

File upload

Allows particip ants to create, submit, authorise, and view

reallocation requests in accordance with the GSH Reallocation

Procedure. At each settlement run, reallocation details are copied

from the Reallocations system to the Settlements system. The

Settlements system then includes this data in settlements

calculations and incorporates the results in participants’ weekly

settlement statements.

7.4 GSH participant categories

Table 22 below describes the relevant functionalities used in GSH for each participant


Table 22: GSH functionalities used by each registrable capacity

Registrable

capacity

ETS DI Delivered

Quantity

Prudential

Dashboard

Publishing

Direct

Reallocations

Trading participant

Viewing Participant

Reallocation

Participant

7.5 GSH systems user access

Participant ID administrators set up participant user access in the User Rights Management

system in the web portal.

© 2014 AEMO 62






Rights Management.

© 2014 AEMO 63








Chapter 8 National Electricity Market

8 National Electricity Market

This chapter provides an overview of the participant IT systems operating in the National

Electricity Market (NEM). It is relevant to IT decision making during the registration processand provides an understanding of what is required to interface with AEMO’s market systems.

Figure 10 on next page provides an overview of the IT systems in the NEM.

In this chapter:

8.1 About the NEM 64

8.2 NEM IT interfaces 65

8.3 NEM IT systems 66

8.4 NEM retail functionality 67

8.5 NEM wholesale functionality 68

8.6 NEM participant categories 71

8.7 NEM systems user access 73

8.8 NEM Dispatch Engine (NEMDE) 73

8.9 Other NEM IT systems 73

8.1 About the NEM

The NEM interconnects five regional market jurisdictions (Queensland, New South Wales,

Victoria, South Australia and Tasmania). West Australia and the Northern Territory are not

connected to the NEM. It involves both wholesale and retail markets managed in line with

the National Electricity Law and the National Electricity Rules (Rules).

The NEM IT systems assist in determining the spot price and facilitate financial settlement of the market. The systems are designed to meet the performance and reliability requirements

of the Rules and the expectations of market participants, provide security for sensitive

information, and be cost effective for participants.

All files exchanged with MSATS and B2B conform to the Australian Standard for Energy

XML (aseXML), for more details, see aseXML Standards.

For more details:

l About the NEM, see National Electricity Market (NEM).

l About the retail market, see Retail & Metering.

© 2014 AEMO 64

http://www.aemo.com.au/About-the-Industry/Energy-Markets/National-Electricity-Market



http://www.aemo.com.au/en/Electricity/Retail-and-Metering







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





l About wholesale market, see Market Operations.

l About NEM participant categories, see Registration.

l About software and guides, see Using Energy Market Information Systems.

l About files exchanged with MSATS and B2B using the Australian Standard for Energy

XML (aseXML), see aseXML Standards.



and participants to support the operation of the NEM, see MSATS Procedures and B2B

Procedures.

Figure 10: NEM IT systems overview

8.2 NEM IT interfaces

Participants can use several interfaces to interact with NEM IT systems—file, web, and web

services. Table 23 on the facing page describes the interfaces available in the NEM.

© 2014 AEMO 65

http://www.aemo.com.au/Electricity/Market-Operations

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


http://www.aemo.com.au/Electricity/Policies-and-Procedures/Market-Settlement-and-Transfer-Solutions









http://www.aemo.com.au/en/About-AEMO/Energy-Market-Registration/Registering-in-Energy-Markets








8.4 NEM retail functionality

Table 27 on page 71 summarises the functionality available in MSATS. For details about the

functionality relevant to each participant category in the retail market, see "Retailparticipant categories" on page 71.

Table 25: MSATS functionality


Administration Web portal Used by participant administrators to set up and maintain user right s to

AEMO’s system access.

B2B Web portal

File upload

File server

Supports the creation and management of a defined set of business-to-

business transact ions and acknowledgements. Optionally used to manage

your B2B inbox and outbox.

B2B responder

(pre-production

only)

Web portal

File serv er

Used to specify what transactions you would like to receive as part of

testing the operational interaction between participants’ systems and the

MSATS B2B Hub.

File server

interaction (Data

Load Import)

Web portal

File upload

File server

Carries messages between MSATS and participant systems and allows

access to participant archive folders.

Metering data Web portal

File server

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

data.

MSATS limits Web service Informs participants about the status of their transaction limits. Limits areimposed on participant interaction with MSATS to prevent overload of the

system.

NMI information Web portal

File server

Web service

Search and view NMI information.

Ombudsman

(NMI enquiry

reports)

Web portal Provides ombudsman organisations with access to NMI standing data.

Participants can view and download reports on ombudsman enquiries.

Participants

(information &

contacts)

Web portal Used to view participant information and create and maintain particip ant

contacts.

Profile

preparation

(profile

information)

Web portal Performs Metering Data Management (MDM) functions such as defining

profile methods and areas, defining data sources and creating profiles.

Reports Web portal

File server

Web service

(C4 report

only)

Access to CATS & MDM reports.

© 2014 AEMO 67





Settlement data Web portal

File server

Used by authorised users to view settlement data.

Transactions

(change

requests,

objections,

notifications,

data requests)

Web portal

File server

Facilitates the process of consumer connection point transfers 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 all NEM systems.

8.5 NEM wholesale functionality

Table 26 below summarises the functionality available in EMMS. For details about the

functionality relevant to each participant category in the wholesale market, see "Wholesale

participant categories" on page 71.

Table 26: EMMS functionality


Constraints Web portal Web Service

Used to convert a constraint equation into plain English format.

Credit Support W eb portal The Credit Support web interface provides registered participants with a

numerical and graphical view of their credit support status, and a scenario

builder where particip ants can analyse their bank guarantee structure

without saving the changes to the Credit Support system.

Data Delivery Web portal Use the Data Delivery menu to:

n Access the Data Interchange Status Dashboard. The status

dashboard displays: The status of the Data Interchange components

within the participant organisation. A list of filenames, delivery dates and a file re-request count (where a file has been sent to the

participant's system more than once). Multiple file deliveries can

indicate a problem at the participant's end.

n Make a File Delivery query and re-request files. The file delivery web

interface allows participants to query all the files delivered within a

date range, and request selected files delivered again to the file

server.

n View your organisation's Data Sharing arrangements.

Data

Interchange (DI)

Web portal

File server

Data Interchange is a set of cooperating applications used to replicate,

manage, and monitor data between AEMO and a participant's database

conforming to the MMS Data Model.

AEMO provides the Data Interchange applications to participants to assist

© 2014 AEMO 68





with the replication of data to their DBMS. Successfully implementing and

managing Data Interchange requires an experienced IT team, planning,

networking, database management, batch file management, and disasterrecovery.

AEMO supp orts data replication to Oracle and SQL Server databases. The

licensing of the participant ID’s SQL Server or Oracle data store is the

responsibility of the participant. Scripts to build the MMS Data Model are

available for SQL Server and Oracle database plat forms, see MMS Data

Model.

Participants use the Data Interchange web applications in the EMMS web

portal to:

n Subscribe to receive files in their participant folder on the EMMS file

server.

n Monitor their Data Interchange, Data Delivery, and Data Sharing

statuses.


Data Sharing Web portal

File server

Each participant ID can share their data with other participant IDs, subject

to an authorised request. Implementing data sharing means the full “Data

Interchange” data set (including private data) for the requesting participant

ID is made available to another participant's sets of folders in the EMMS

file server, as nominated in the request. The sharing of data is for both pre-

production and production. A data sharing requirement may emerge, for

example, due to a merger with, takeover of, or sale of another NEM

registered participant. The requirement may be to use one company's ITsystem to manage access, and process the data for two or more participant

IDs using just one participant ID's set of folders in the EMMS file server.

The web portal interface provides the status of any data sharing agreements

you have implemented.

Data

Subscription

Web portal Used to subscribe to files for Data Interchange, and obtain the latest MMS

Data Model. EMMS generates files continually, based on changes and five-

minute dispatch runs, etc. These files are typically CSV files that contain

public data and p articipant’s private data.

AEMO recommends participant use of the “Data Interchange” products,

supplied by AEMO, to automate receiving and storage of the files. AEMOprovides working sample software for FTP access to MarketNet and working

sample software for Data Interchange.

Dispatch

instructions

File server Dispatch Instructions from AEMO.

Dispatch

performance &

history

File server Dispatch performance and history.

Intermittent

Generation

Web portal

File upload

File server

AEMO hosts the intermittent generation interfaces and provides data

access to the market and to individual intermittent generators. The systems

produce various types of forecasts at regular run intervals for each forecast

© 2014 AEMO 69














8.6 NEM participant categories

8.6.1 Retail participant categories

Table 27 below describes the relevant and optional functionalities used in MSATS for each

participant category. For more details about registration, see Registration.

Table 27: MSATS functionalities used by each participant category

Relevant = P | Optional = O

Functionality Generator Customers

classifying

loads

Customer NSP Trader Reallocator

Administration

B2B O O

B2B responder O O

File server interaction

(Data Load Import)

O O

Metering data O O

MSATS limits O O

NMI information O O

Ombudsman O O

Participants O O

Profile preparation O O

Reports O O

Settlement data O O

Transactions O O

User Profile

8.6.2 Wholesale participant categories

Table 28 on the facing page explains the relevant and optional functionalities used in the

EMMS for each participant category.

© 2014 AEMO 71





Table 28: EMMS functionalities used by each participant category

Relevant = P | Optional = O

Functionality Generator Customers

classifying

loads

Customer NSP Trader Reallocator

Constraints

Credit Support

Data Delivery

O O O

Data Interchange (DI)

O O O

Data Sharing

O O

Data Subscription

O O

Dispatch Instructions

Dispatch Performance & History

Intermittent Generation

Market Info

O O

Market Direct

Offers & Submissions

Payment Nomination

Performance Monitor

O O O

Prudential Dashboard

Prudential Forecast

Reallocations

Settlements Direct

Settlement Residue Auctions (SRA)

Notes

l Non-market generators may choose to connect to AEMO systems, but have no need to

do so.

l Intending Participants may choose to connect to AEMO’s systems on special request.

© 2014 AEMO 72




8.7 NEM systems user access

Participant ID administrators set up participant user access in the User Rights Management

system in the web portal.


Rights Management.

8.8 NEM Dispatch Engine (NEMDE)

The NEMDE Queue Service is a separately purchasable product from AEMO. It provides an

application interface enabling participant organisation’s analysts to model alternative

outcomes from AEMO’s dispatch engine, the NEMDE Solver. The service allows participants

to edit and submit a NEMDE input file and receive the corresponding output file.

For more details, see NEMDE Queue Service. Application to purchase is to AEMO's

Information and Support Hub.

8.8.1 Market solver files

For each dispatch cycle (5 minutes), a generated input file is submitted to the linear programsolver (NEMDE), producing two output files. The files for each dispatch 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, retaining history for a month or two.

8.9 Other NEM IT systems

Along with EMMS and MSATS, AEMO has other systems, mainly intended for a limited

range of participants, examples include:

l Operations and Planning Data Management System (OPDMS).

l Network Outage Scheduler (NOS).

For more details, see Network Data.

© 2014 AEMO 73



http://aemo.com.au/Electricity/Data/Network-Data


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










Chapter 9 Retail Gas Market

9 Retail Gas Market

This chapter provides an overview of the FRC Hub operating in the retail gas market. It is

relevant to IT decision making during the registration process and provides an understandingof what is required to interface with AEMO’s market systems. Figure 11 below provides an

overview of the IT systems in the Retail Gas Market.

In this chapter:

9.1 About the FRC Hub 74

9.2 Retail Gas Market IT interfaces 75

9.3 Retail Gas Market IT systems 75

9.4 Retail Gas Market participant categories 75

9.5 Retail Gas Market user access 76

9.1 About the FRC Hub

Successf ull y implementing and managing an FRC Hub set up requires planning and an

experienced IT team. Participants are required to pass a certification process that may take

up to 12 weeks. For a smooth FRC implementation, please plan the work at your end

accordingly.

For more details:

l About the gas retail system, see Gas Retail Markets.

l About certification, see FRC Hub.


Figure 11: Retail Gas Market IT systems overview

© 2014 AEMO 74

http://aemo.com.au/Gas/Registration

http://aemo.com.au/AEMO%20Home/Gas/Resources/Information%20Systems/FRC%20Hub


http://aemo.com.au/Gas/Retail-Gas-Markets








and participants to support the operation of the gas market, see Retail Gas Market

Procedures.

9.2 Retail Gas Market IT interfaces

Retail Gas Market participants use the following interfaces to interact with the FRC Hub.

Table 29: Retail Gas Market interfaces

Interface Function

Web portal (HTTPS) Participants can access the FR C Hu b functionality using a web browser.

Web services (HTTPS) Participants can connect a gateway to the hub using HTTPS.

9.3 Retail Gas Market IT systems

Table 30 below summarises the FRC Hub operating in the Retail Gas Market.

Table 30: Retail Gas Market system functionalities

System Interface Description

FRC Hub Web portal

Web service

Provides the interface for participants to send and receive B2B aseXML

transactions. It handles various transactions, such as account creation,

customer transfer notification, and meter data information.

9.4 Retail Gas Market participant categories

Table 31 on the facing page describes the relevant functionalities used in the retail gasmarket for each participant category. For more details about registration, see Registration.

The ACT and NSW retail gas market does not use the FRC Hub, further details are provided

during the registration process.

© 2014 AEMO 75

http://aemo.com.au/AEMO%20Home/Gas/Policies%20and%20Procedures/Retail%20Gas%20Market%20Procedures











Chapter 9 Retail Gas Market

Table 31: Retail Gas Market functionalities used by each registrable capacity

State Registrable capacity FRC Hub

QLD Distributor

Retailer

User

SA Network Operator (including Mildura)

User

VIC Distributor

Market Participant - retailer

9.5 Retail Gas Market user access

Each participant user in the QLD, VIC, and SA retail gas markets must complete a Gas

Systems User Access Request and attach it to the registration application. The form allows

for access to multiple markets and multiple companies for each participant user.



and complete it manually. For help completing the form, see Figure 12 on next page.

Participant users for the ACT and NSW are not required to complete the Gas Systems User

Access Request .

© 2014 AEMO 76














Chapter 10 Short Term Trading Market

10 Short Term Trading Market

This chapter provides an overview of the participant IT systems operating in the short term

trading market (STTM). It is relevant to IT decision making during the registration processand provides an understanding of what is required to interface with AEMO’s market systems.

10 above provides an overview of the IT systems in the NEM.

In this chapter:

10.1 About STTM 78

10.2 STTM IT interfaces 79

10.3 STTM IT systems 79

10.4 STTM participant categories 80

10.5 STTM user access 80

10.1 About STTM

The Short Term Trading Market (STTM) is a market-based wholesale gas balancing

mechanism established at defined gas hubs. The market uses bids, of fers, and forecasts to

determine schedules for deliveries from the pipeline's transmission users and the hubs. The

market sets daily market prices and settles each hub based on the schedules and deviations

from schedules.

For more details:

l About STTM, see Short Term Trading Market.


Figure 13: STTM IT systems overview

© 2014 AEMO 78

http://aemo.com.au/Gas/Registration

http://aemo.com.au/Gas/Market-Operations/Short-Term-Trading-Market









and participants to support the operation of the gas market, see STTM Rules, STTM

Procedures, and STTM Interface Protocol.

10.2 STTM IT interfaces

Participants can use several interfaces to interact with STTM IT systems—file, web, and web

services.

Table 32: Table 23: STTM interfaces

Interface Function Web portal (HTTPS) Participants can access the processes and functions of the STTM using a

web browser.


(HTTPS)

The SWEX allows direct uploading of files to the browser interface.

File server (FTP) SWEX and MIS both provide FTP file interfaces for participant interaction

with file servers.

Web services (HTTPS) The SWEX system allows CSV file uploading using HTTPS.

10.3 STTM IT systems

Table 33 below summarises the IT systems available to participants in the STTM.

Table 33: STTM system functionalities

System Interface Description

STTM Web

Exchanger

(SWEX)

Web portal The SWEX provides the interface for market participants to submit bid data

and other required market information such as:

n Bids and offers

n Price Taker Bids

n Contingency bids and offers

n Price taker bids

n Registered services and trading rights

n Market schedule variations

SWEX Interface

Engine

(SWEXIE)

File

File upload

Web service

SWEXIE allows the upload of files to the STTM database using FTP,

HTTPS, or CSV file upload via SWEX. IT is a simplified process of

submitting bids, offers, withdrawals, allocations, variations, and

transactions.

MarketInformation

System (MIS)

Web portalFile

The MIS provides STTM reports for both public access and participantaccess. The reports detail STTM trading information and general market

data.

© 2014 AEMO 79

http://aemo.com.au/Gas/Policies-and-Procedures/Short-Term-Trading-Markets/Rules-Procedures-and-Interface-Protocol












Chapter 10 Short Term Trading Market

Details of the form of CSV transactions and MIS reports are described in the STTM Rules,

STTM Procedures, and STTM Interface Protocol.

10.4 STTM participant categories

Table 34 below describes the relevant functionalities used in STTM for each participant


Table 34: STTM functionalities used by each registrable capacity

Registrable capacity SWEX SWEXIE MIS

STTM trading participants (shippers & users)

10.5 STTM user access





must be completed using Adobe Reader version 9 or above. Please do not print the requestand complete it manually. For help completing the form, see Figure 14 on next page.

© 2014 AEMO 80






















11.2 Feedback

To suggest corrections to this document, please contact the AEMO Information and Support

Hub.

© 2014 AEMO 83



Chapter 12 References

12 References

The resources listed in this section contain related information that may assist you. Please

ensure you are reading the latest version.

12.1 Rules, law, and government bodies

l "Australian Energy Market Commission" (AEMC), electricity and gas rules

http://www.aemc.gov.au/index.html.

l "Australian Energy Regulator (AER)", www.aer.gov.au.

12.2 AEMO's website

l AEMO website: www.aemo.com.au

l “aseXML Standards”, help with aseXML, including guidelines, schemas, change process,

sample files and white papers, http://www.aemo.com.au/About-the-

Industry/Information-Systems/aseXML-Standards (Home>About the

Industry>Information Systems>aseXML Standards).

l “B2B”, documentation relating to defining and coordinating the implementation of B2Bprocesses associated with metering and the retail electricity

market.http://www .aemo.com.au/Electricity/Policies-and-Procedures/B2B (Home >

Electricity > Policies & Procedures > B2B).

l "Budget and Fees, http://www.aemo.com.au/Electricity/Registration/Budget-and-Fees

(Home > Electricity > Registration > Budget & Fees).

l “Bulletin Board”, http://www.gasbb.com.au.

l "Data Interchange", the web page containing all software and documentation relating to the

Data Interchange components: http://www.aemo.com.au/A bout-the-Industry/Information-Systems/Data-Interchange (Home > About the Industry >

Information Systems > Data Interchange).

l "Declared Wholesale Gas Market Guides, Forms and Templates",

http://www.aemo.com.au/Gas/W holesale-Gas-Markets/Victorian-Wholesale-

Market/Declared-Wholesale-Gas-Market-Guides-and-Forms (Home > Gas > Resources

> Reports and Documents > Declared Wholesale Gas Market Guides, Forms and

Templates).

l “Electricity Data”, http://www.aemo.com.au/Electricity/Data (Home > Electricity > Data).

© 2014 AEMO 84

http://www.aemc.gov.au/index.html

http://www.aer.gov.au/





http://www.aemo.com.au/Electricity/Registration/Budget-and-Fees




































http://www.aer.gov.au/

http://www.aemc.gov.au/index.html




l Electricity Market Management Systems Access Policy and Procedure,

http://www.aemo.com.au/About-the-Industry/Information-Systems#systems (Home >

About the Industry > Information Systems).

l “FRC Hub"http://aemo.com.au/AEMO%20Hom-

e/Gas/Resources/Information%20Systems/FRC%20Hub (Home > Gas > Resources >

Information Systems > FRC Hub).

l "Gas Market Data", http://aemo.com.au/Gas/Market-Data (Home > Gas > Market Data).

l Gas Supply Hub Exchange Agreement , http://aemo.com.au/Gas/Market-Operations/Gas-

Supply-Hub/Legal (Home > Gas > Market Operations > Gas Supply Hub > Legal).

l Gas Systems User Access Request ,

http://aemo.com.au/~/media/Files/Oth-er/energy%20market%20information%20systems/Gas_Systems_User_Access_

Request_v2.ashx (Home > About the Industry > Information Systems).

l Guide to Market Systems - NEM Change of Ownership,

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

(Home > Electricity > Registration > Application Forms > Generator Application

Forms).

l Guide to User Rights Management, http://www.aemo.com.au/About-the-

Industry/Information-Systems/Using-Energy-Market-Information-Systems (Home >

About the Industry > Information Systems).

l “Information Systems”, IT systems information, related documents, and access forms:

http://www.aemo.com.au/About-the-Industry/Information-Systems (Home > About the

Industry > Information Systems).

l "IT Assistance", information to assist participants with IT related issues:

http://www.aemo.com.au/About-the-Industry/Information-Systems/IT-Assistance

(Home > About the Industry > Information Systems > IT Assistance).

l "Market Operations", http://www.aemo.com.au/Electricity/Market-Operations (Home >

Electricity > Market Operations).

l “MMS Data Model”, http://www.aemo.com.au/About-the-Industry/Information-

Systems/Data-Interchange#MMS Data Model (Home > About the Industry >

Information Systems > Data Interchange).

l “MSATS”, http://www.aemo.com.au/Electricity/Policies-and-Procedures/Market-

Settlement-and-Transfer-Solutions (Home > Electricity > Policies & Procedures >

MSATS).

l "National Electricity Mark et (NEM)", http://www.aemo.com.au/About-the-

Industry/Energy-Markets/National-Electricity-Market (Home > About the Industry >Energy Markets > National Electricity Market (NEM)).

© 2014 AEMO 85



http://aemo.com.au/Gas/Market-Data


http://aemo.com.au/~/media/Files/Other/energy%20market%20information%20systems/Gas_Systems_User_Access_Request_v2.ashx

































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





































Chapter 12 References

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

Systems/NEMDE-Queue-Service (Home > About the Industry > Information Systems >

NEMDE Queue Service).

l "Network Data", http://aemo.com.au/Electricity/Data/Network-Data (Home > Electricity > Data > Network Data).

l “Registration”, information on registering in energy markets:

http://www.aemo.com.au/en/About-AEMO/Energy-Market-Registration/Registering-

in-Energy-Markets (Home > About AEMO > Energy Market Registration > Registering

in Energy Markets).

l “Retail Gas Markets" http://aemo.com.au/Gas/Retail-Gas-Markets (Home > Gas > Retail

Gas Markets).

l "Retail Gas Market Procedures", http://aemo.com.au/AEMO Home/Gas/Policies andProcedures/Retail Gas Market Procedures (Home > Gas > Policies & Procedures >

Retail Gas Market Procedures).

l “Settlements" http://www.aemo.com.au/Electricity/Settlements (Home > Electricity >

Settlements).

l "Short Term Trading Market", http://aemo.com.au/Gas/Market-Operations/Short-Term-

Trading-Market (Home > Gas > Market Operations > Short Term Trading Market).

l "STTM Rules, STTM Procedures, and STTM Interface Protocol",

http://aemo.com.au/Gas/Po licies-and-Procedures/Short-Term-Trading-Markets/Rules-Procedures-and-Interface-Protocol (Home > Gas > Policies & Procedures > Short Term

Trading Market > STTM Rules, STTM Procedures and STTM Interface Protocol).

l "Using Energy Market Information Systems", IT systems documentation and software:

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

Information-Systems(Home > About the Industry > Information Systems > Using

Energy Market Information Systems).

© 2014 AEMO 86






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



























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





























13 Index

A About AEMO's IT systems 3

About data sharing 30

About security 15

About STTM 78

About the BB 54

About the DWGM 49

About the FRC Hub 74

About the GSH 60

About the NEM 64

About the web portal 36

Additional conne ction and bandwidth 11

AEMO's website 84

AEMO IT systems overview 7

AEMO URLs 42

annual pre-payment options 11

B

B2B Validation Module 14

Bandwidth en titlements 10

BB coverage 56

BB functionality 55

BB home page 58

BB interf aces 55

BB IT interfaces 55

BB mandatory and eligible registrable capacities 56

BB operation 57

BB overview diagram 54

BB user access 57-58

BB website 55

C

Changing your Participant ID password 20

Checklist for setting up your IT systems 47

Communications 5

Connection entitlements 10

Current baseline data 33

D

Data Interchange 14

Data ne twork connection (MarketNet) 8

Data network connection decisions 8

Data network connection options 8

Data Sharing 29

Data sharing example 31

Data sharing removal 32

Data sharing set-up 31

Declar ed Wholesale Gas Market 49

Dedicated Link 9

Deregistration for IT systems 34

DWGM functionalities used by each registrable

capacity 51

DWGM IT interfaces 50

DWGM IT systems 50

DWGM IT systems overview 50

DWGM participant categories 51

DWGM systems user access 52

DWGM user access request 53

E

electricity whol esale 68

EMMS 68

EMMS functionalities used by each participantcategory 72

© 2014 AEMO 87




EMMS functionality 68

Energy Market Systems Web Portal 36

energy market systems web portal production and pre-

production URLs 41

Excluding IP addresses in Internet Explorer 17

F

Feedback 83

File-based interface URLs 43

File Servers 42

G

Gaining access to the web portal 38

Gas Bulletin Board 54

Gas Market System (GMS) 50

Glossary viii

GSH Delivered Quantity 62

GSH functionalities used by each registrable

capacity 62

GSH IT interfaces 61

GSH IT systems 61

GSH IT systems overview 60

GSH participant categories 62

GSH Prudential Dashboard 62

GSH Publishing Direct 62

GSH Reallocations 62

GSH systems user access 62

I

Information and Support Hub 82

Interfaces 36

IT interfaces 4

M

Making changes to your MarketNet connection 12

market dat 4

Market data access 17

Market Information Bulletin Board (MIBB) 50

Market Information System (MIS) 79

Market solver files 73

MarketNet 8, 38

MarketNet access control 12

MarketNet data network connection options 9

Monthly data on DVD 33

MSATS functionalities used by each participant

category 71

MSATS functionality 67

multiple participant IDs 13

N

Needing Help 82

NEM i nterfaces 66

NEM IT systems 66

NEM IT systems overview 65

NEM participant categories 71

NEM retail functionality 67

NEM wholesale 68

NEMDE Queue 73

P

Participant's security responsibi lities 16

participant administrator 13

Participant Batcher 14

participant entitlements 9

Participant file server folders 43

Participant File Server Password Changer 25

Password 21-22

Password changers 20

© 2014 AEMO 88




password changes 19

Password management 17

publicly available data at no cost 4

R

References 84

Retail Gas Market 74

Retail Gas Market functionali ties used by each

registrable capacity 76

Retail Gas Market interfaces 75

Retail Gas Market IT interfaces 75

Retail Gas Market IT systems 75

Retail Gas Market IT systems overview 74

Retail Gas Market system functionali ties 75

Retail Gas Market user access request 77

Rules, law, and government bodies 84

S

Security 15

Security management 16

setting up IT systems timeline 46

Short Term Trading Market 78

Signing in and out 38

single user ID lo gins 13

STTM functionalities used by each registrable

SWEX Interface Engine (SWEXIE) 79

System requirements 37

System transfers 34

T

Testing the password change 29

Trayport Exchange Trading System (ETS) 61

U

Understanding set participant 13

Unregistered organisations access requests 11

User Rights Management (URM) 12

user rights management for energy markets 13

Using the web portal 38

V

VPN LAN to LAN 9

VPN variable 9

WWeb-based interface URLs 41

web-based password changer 22

Web Exchanger (WEX) 51

Web services 44

Web Services 14

Web services system requirements 44