WEMS SUBMISSION SPECIFICATION VERSION 5.0

Transcription

1 WEMS SUBMISSION SPECIFICATION VERSION 5.0 Published: November 2015

2 IMPORTANT NOTICE Purpose AEMO has prepared this document to provide information about the Wholesale Electricity Market System (WEMS) submission formats required to participate in the Wholesale Electricity Market, as at the date of publication. Disclaimer This document or the information in it may be subsequently updated or amended. This document does not constitute legal or business advice, and should not be relied on as a substitute for obtaining detailed advice about the Electricity Industry Act 2004, the Wholesale Electricity Market (WEM) Rules, or any other applicable laws, procedures or policies. AEMO has made every effort to ensure the quality of the information in this document but cannot guarantee its accuracy or completeness. Accordingly, to the maximum extent permitted by law, AEMO and its officers, employees and consultants involved in the preparation of this document: make no representation or warranty, express or implied, as to the currency, accuracy, reliability or completeness of the information in this document; and are not liable (whether by reason of negligence or otherwise) for any statements or representations in this document, or any omissions from it, or for any use or reliance on the information in it.

3 CONTENTS 1. INTRODUCTION 5 2. SUBMISSION FORMAT DETAILS XML Format CSV Format XML and CSV Differences 9 3. BILATERAL GENERATION XML Format CSV Format RESOURCE PLANS XML Format CSV Format STEM XML Format CSV Format RESERVE CAPACITY ALLOCATION SUBMISSIONS XML Format CSV Format RESERVE CAPACITY CONFIRM ALLOCATION SUBMISSIONS XML Format CSV Format RESERVE CAPACITY CERTIFICATION DATA SUBMISSIONS XML Format CSV Format BILATERAL TRADE DECLARATIONS (RESERVE CAPACITY) SUBMISSIONS XML Format CSV Format XML Format CSV Format LONG TERM SPA SUBMISSIONS XML Format CSV Format CAPACITY CREDITS AND OBLIGATIONS SUBMISSIONS XML Format CSV Format BALANCING VARIATION SUBMISSIONS XML Format CSV ForFmakemat 59 AEMO - WEMS Submission Specifications v5.0 3

4 13. BALANCING STANDING SUBMISSIONS XML Format CSV Format LOAD FOLLOWING VARIATION SUBMISSION XML Format CSV Format LOAD FOLLOWING STANDING SUBMISSION XML Format CSV Format WEB SERVICES SUBMISSIONS BALANCING AND LFAS Web Services Submissions Upload and Validate Allow Gate Closure Violation / Discard File on Error Validation Upload 77 AEMO - WEMS Submission Specifications v5.0 4

5 1. INTRODUCTION This document describes the file formats used for data exchange between Market Participants and AEMO through the WEMS. File Exchange facilitates the exchange of XML and CSV files for Bilateral Generation, Resource Plans, STEM, Reserve Capacity, Balancing and Load Following with functionality within the systems to allow users to perform submit and cancellation requests for each of these submission types. Bilateral Generation, Resource Plans, STEM and some Reserve Capacity submission types also allow the user to make query requests to view the current state of the submission. Similar features are also available to Balancing and Load Following submission types through the reporting web services and through the Market Participant Interface (MPI). AEMO - WEMS Submission Specifications v5.0 5

6 2. SUBMISSION FORMAT DETAILS 2.1 XML Format XML documents must conform to an XML schema definition file XSD file (e.g. the mint.xsd) which is available separately to this document. The XSD file contains the formal definitions for XML document submission. This document describes the XML format in a less formal, but more descriptive manner. Two XSD schema files provide the formal XML specifications for submissions: For Bilateral Generation, Resource Plans, STEM and Reserve Capacity submissions (excluding Certification and Bilateral Declarations), this is the mint.xsd. For Balancing submissions and Load Following submissions, Reserve Capacity Certification and Bilateral Declarations, this is the wems-1.1.xsd. This document provides example XML files with references to relevant parts of the schemas. Standing submissions and variation submissions cannot be made within the same submission files and therefore separate uploads must be performed for these submissions Common mint.xsd XML Elements The mint.xsd file covers validation of Bilateral Generation, Resource Plans, STEM and Reserve Capacity (excluding Certification and Bilateral Declarations). Other submissions that are covered within this document are validated by separate XML Schema Definition XSD files (described later within this document). Submissions using the mint.xsd must have a root element of <bids_offers> containing a single element of <market_submit>, <market_query> or <market_cancel>. This is shown in the examples below: <?xml version="1.0" encoding="utf-8"?> <bids_offers> <market_submit trading_date=" " application_type="[application TYPE]" participant_name="[participant]"user_name="[user]"> [SUBMISSION CONTENT] </market_submit> </bids_offers> <?xml version="1.0" encoding="utf-8"?> <bids_offers> <market_query trading_date=" " application_type="[application TYPE]" participant_name="[participant]"user_name="[user]"> [SUBMISSION CONTENT] </market_query> </bids_offers> <?xml version="1.0" encoding="utf-8"?> <bids_offers> <market_cancel trading_date=" " application_type="[application TYPE]" participant_name="[participant NAME]"user_name="[USER NAME]"> [SUBMISSION CONTENT] </market_cancel> </bids_offers> AEMO - WEMS Submission Specifications v5.0 6

7 The APPLICATION TYPE referenced in the above example varies depending on whether the submission is for Bilateral Generation, Resource Plans, STEM or Reserve Capacity. The valid values are shown below: SUBMISSION TYPE STEM Bilateral Resource Plan Reserve Capacity APPLICATION TYPE STEM BILATERAL RESOURCE_PLAN RESV_CAP_ALLOCATION RESV_CAP_CONFIRM_ALLOCATION RESV_CAP_OFFER LONG_TERM_SPA CAPACITY_CREDITS The values for this attribute will be covered in the relevant section. Likewise, the submission content varies depending on the type of submission and will be covered in the relevant section. The PARTICIPANT NAME referenced in the above example refers to the submitting market participant and is validated accordingly. The USER NAME referenced in the above example refers to the submitting user for the market participant and is validated accordingly. The top level elements must contain the trading date in the trading_date attribute in YYYY-MM-DD format. For a variation submission, this indicates the trading date on which the variation applies, while for a standing submission, this indicates the date on which the standing submission first applies Standing submissions in mint.xsd When a submission is a standing submission, an XML element detailing the submission details will be placed in an element. The submission content element (i.e. the top-level element in the SUBMISSION CONTENT placeholder in Section 2.1.1) must have the standing_flag attribute set to true. For example, a Bilateral Generation submission may appear as follows: <bilateral version_no="1.0" standing_flag="true"> A child element is required when the submission is a standing submission containing the standing submission details. These are defined in the standing element in the mint.xsd file, an example of which follows below. <standing expiry_date=" " type="all"/> AEMO - WEMS Submission Specifications v5.0 7

8 The details of the standing submission fields are given below: ATTRIBUTE ELEMENT TYPE CONSTRAINTS COMMENTS standing_flag Submission specific element Boolean expiry_date standing (YYYY-MM-DD) Not required, defaults to false if not present if standing element is present and not required if cancelling a submission type standing String Valid values: MON, TUE, WED, THU, FRI, SAT, SUN, ALL Whether the submission is a standing submission (true) or a variation submission (false) Expiry of the standing submission The day on which the standing submission applies. ALL is for every day. If a submission is a standing submission, the standing_flag must be set to the value true and the type and expiry_date columns populated with valid values. If the submission is a variation submission or a variation cancel submission, the standing_flag column must be set to the value false and the type and expiry_date values omitted. To cancel a Standing Submission, the standing_flag must be set to true, type must be specified and expiry_date must be omitted. 2.2 CSV Format All CSV files will consist of a header line, followed by zero or more detail lines. Depending on the type of submission being made, one or more of the files may be omitted. This will be documented in the specific CSV file format sections, where relevant. The header line of each individual CSV file must contain the comma separated list of header field names. All fields that are defined for a CSV file format must be present and no fields may be omitted from the header. All detail lines must contain exactly the same number of fields as specified in the header, i.e. no fields may be omitted in the detail lines, though field values may be omitted if the field is optional. Standing submissions and variation submissions cannot be made in the same set of files, therefore separate files must be made for each type of submission Standing submissions in CSV Standing submissions for CSV files that are the equivalent of XML files defined in mint.xsd (i.e. Bilateral Generation, Resource Plans, STEM and Reserve Capacity submissions) have common fields, as shown below: FIELD NAME TYPE CONSTRAINTS COMMENTS standing_flag Boolean Whether the submission (true) is a standing, or (false) a variation submission standing_day_type String if standing_flag = true standing_expiry_date if standing_flag = true and action = "SUBMIT" Valid values: MON, TUE, WED, THU, FRI, SAT, SUN or ALL The date until which the standing submission is valid. AEMO - WEMS Submission Specifications v5.0 8

9 If a submission is a standing submission, the standing_flag must be set to the value true and the standing_day_type and standing_expiry_date columns populated with valid values. If the submission is a variation submission or a variation cancel submission, the standing_flag column must be set to the value false and the standing_day_type and standing_expiry_date values omitted. To cancel a Standing Submission, the standing_flag must be set to true, standing_day_type must be specified and standing_expiry_date must not be set. 2.3 XML and CSV Differences The major difference between fields in XML and CSV submission is in the date format. XML files require dates to be specified in ISO-8601 format of YYYY-MM-DD. This is the default date format of XML schema definitions (XSD files).csv files are specified in DD/MM/YYYY format as this is a common format used in Microsoft Excel, which can be used to export CSV files. XML functionality within the File Exchange covers the ability to submit, query, or cancel for Bilateral Generation, Resource Plans, STEM and Reserve Capacity (for Balancing and LFAS, no query function is provided as this functionality is covered by another web service and in the MPI). However, CSV functionality within the File Exchange only provides the ability to submit and cancel (for all files). File Exchange can be made using either one XML file per submission, or one-to-many CSV files, depending on the submission type. AEMO - WEMS Submission Specifications v5.0 9

10 3. BILATERAL GENERATION The bilateral generation submission allows participants to submit their bilateral generation levels for the trading day into the WEMS. Participants are also able to query and cancel submissions for an individual trading interval, or a range of trading intervals. 3.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a bilateral submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX bilateral BilateralWaSubmit 1 1 standing StandingSubmit 0 1 trade_period TradePeriod 1 48 trade_detail TradeDetail 1 Unlimited Attribute details are shown for each element that comprises a bilateral submission. The attributes of the standing element are not covered here as this is detailed in Section Bilateral Element version_no String Must be set to 1.0 standing_flag Boolean Attribute not required if a variation submission If true, there must be a standing element contained within the bilateral element See Section Trade Period Element start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. supply_quantity_mwh Number Quantity supplied for bilateral contracts (MWh). Clause of the WEM Rules (c) i wp_load_mwh Number Participants must specify a value of 0. Trade Detail Element participant_name String The name of the other participant in the bilateral contract Clause of the WEM Rules (c) ii demand_quantity_mwh Number The quantity of demand requested of the other participant (MWh). Clause of the WEM Rules (c) iii AEMO - WEMS Submission Specifications v5.0 10

11 Sample (Standing) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit trading_date=" " application_type="bilateral" participant_name="testgen2" user_name="testuser"> <bilateral version_no="1.0" standing_flag="true"> <standing expiry_date=" " type="sun" /> <trade_period start_int="1" start_hr="8" end_int="2" end_hr="7" wp_load_mwh="10.0" supply_quantity_mwh="150.0"> <trade_detail demand_quantity_mwh="-50.0" participant_name="testcons1" /> <trade_detail demand_quantity_mwh="-100.0" participant_name="testcons2" /> </trade_period> </bilateral> </market_submit> </bids_offers> Sample (Standing cancellation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel trading_date=" " application_type="bilateral" participant_name="testgen2" user_name="testuser"> <bilateral version_no="1.0" standing_flag="true"> <standing type="sun"> </standing> </bilateral> </market_cancel> </bids_offers> Sample (Variation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit trading_date=" " application_type="bilateral" participant_name="testgen2" user_name="testuser"> <bilateral version_no="1.0" standing_flag="false"> <trade_period start_int="1" start_hr="8" end_int="2" end_hr="7" wp_load_mwh="10.0" supply_quantity_mwh="150.0"> <trade_detail demand_quantity_mwh="-50.0" participant_name="testcons1" /> <trade_detail demand_quantity_mwh="-100.0" participant_name="testcons2" /> </trade_period> </bilateral> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel trading_date=" " application_type="bilateral" participant_name="testgen2" user_name="testuser"> </market_cancel> </bids_offers> Sample (Query) AEMO - WEMS Submission Specifications v5.0 11

12 <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query trading_date=" " application_type="bilateral" participant_name="testgen2" user_name="testuser"> <bilateral start_hr="8" start_int="1" end_hr="10" end_int="2" standing_flag="false" version_no="1.0" /> </market_query> </bids_offers> 3.2 CSV Format The bilateral generation CSV submission consists of a single file. Field details for the CSV file are shown below for each element that comprises a bilateral generation submission. Note that only submit and cancel actions are permitted and no query action is permitted for the CSV transaction. For bilateral CSV submissions, values for supply_quantity_mwh are derived from the negative demand_quantity_mwh value, hence why the field is not required in CSV submissions. FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the bilateral submission. For standing submissions, the trading date that the standing submission is effective from. action String Either "SUBMIT" for submission, or "CANCEL" for cancel. standing_flag Boolean Whether the submission is a standing (true) or variation (false) submission standing_day_type String if standing_flag = true standing_expiry_date if standing_flag = true and action = "SUBMIT" Valid values: MON, TUE, WED, THU, FRI, SAT, SUN or ALL Clause of the WEM Rules (b) ii The date until which the standing submission is valid. Clause of the WEM Rules (b) ii start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. wp_load_mwh Number Participants must specify a value of 0. participant_name String The name of the other participant in the bilateral contract Clause of the WEM Rules (c) ii demand_quantity_mwh Number The quantity demanded by the other participant Clause of the WEM Rules (c) iii The following table lists the fields that are relevant for each section contained in the CSV file Field Group Submission Trade Period Trade Detail Fields trading_date, action,standing_flag, standing_day_type, standing_expiry_date start_hr, start_int, end_hr, end_int, wp_load_mwh participant_name, demand_quantity_mwh AEMO - WEMS Submission Specifications v5.0 12

13 All lines in the file must be specified and contain the same values for the submission fields as specified in the Submission Field Group in above (i.e. trading_date, action, standing_flag, standing_day_type and standing_expiry_date fields). i.e. A submission must be either a standing or variation, not a combination. All trade details for the same trade period must have the same Trade Period fields, as specified in the submission field group in above (i.e. start_hr, start_int, end_hr, end_int and wp_load_mwh fields). Sample (Standing) trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,wp_load_mwh,participant_name,demand_quantity_mwh 7/05/2011,submit,true,SUN,28/05/2011,8,1,7,2,10,TESTCONS1,-50 7/05/2011,submit,true,SUN,28/05/2011,8,1,7,2,10,TESTCONS2,-100 Sample (Standing cancellation) trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,wp_load_mwh,participant_name,demand_quantity_mwh 7/05/2011,cancel,true,ALL,,,,,,,, Sample (Variation) trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,wp_load_mwh,participant_name,demand_quantity_mwh 7/05/2011,submit,false,,,8,1,7,2,10,TESTCONS1,-50 7/05/2011,submit,false,,,8,1,7,2,10,TESTCONS2,-100 Sample (Variation cancellation) trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,wp_load_mwh,participant_name,demand_quantity_mwh 7/05/2011,cancel,false,,,,,,,,, AEMO - WEMS Submission Specifications v5.0 13

14 4. RESOURCE PLANS The resource plan submission allows participants to submit resource plans containing participant, facility, energy, and synchronisation details. Participants are also able to query and cancel submissions for an individual trading interval, or a range of trading intervals. 4.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that contains a resource plan submission, and the number of times that each element can occur within the context of its parent element. Participants with only Non Scheduled Generators are only required to submit the Resource Plan and Participant Detail elements. ELEMENT MINT.XSD TYPE MIN MAX resource_plan ResourcePlanSubmit 0 1 Standing StandingSubmit 0 1 participant_detail ParticipantDetail 1 48 facility_detail FacilityDetailResPlan 1 Unlimited energy_detail EnergyDetail 1 48 Synchronisation Synchronisation 0 Unlimited Attribute details are shown for each element that comprises a resource plan submission. The attributes of the standing element are not covered here as this is detailed in Section Resource Plan Element version_no String. Must be set to 1.0 standing_flag Boolean Attribute not required if a variation submission If true, there must be a standing element contained within the resource plan element See Section Participant Detail Element start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. shortfall_mwh Number Optional Shortfall between net energy scheduled in resource plan and the net contract position in Megawatt hours (MWh). Defaults to 0 if not provided. Clause of the WEM Rules (e) AEMO - WEMS Submission Specifications v5.0 14

15 total_demand_mwh Number Optional Total energy demand from curtailable load and interruptible load in Megawatt hours (MWh). Defaults to 0 if not provided. Clause of the WEM Rules (d) non_sched_generation Number Optional Sum of expected Non-Scheduled Generation in MWh (loss factor adjusted). Clause of the WEM Rules (a) total_demand_eoi_mw Number Optional End of Interval MW value of total demand. Clause of the WEM Rules (da) Facility Detail Element facility_name String (2 to 32 characters) The name of the facility whose details are supplied. Clause of the WEM Rules (b) i facility_type String Valid values: SCHED_GEN and DISP_LOAD Energy Detail Element start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. energy_mwh Number Total energy generated for the specified interval range in Megawatt hours (MWh). Clause of the WEM Rules (b) iii target_mw Number Sent out output at the end of the specified interval range in Megawatts (MW). Clause of the WEM Rules (b) v ramp_rate Number Ramp rate specified for trading interval in (MW/min). Clause of the WEM Rules (b) iv Synchronisation Element time String (hh:mm) Clause of the WEM Rules (b) ii operation String Valid values: COMMIT, DE-COMMIT Clause of the WEM Rules (b) ii AEMO - WEMS Submission Specifications v5.0 15

16 Sample (Standing) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit trading_date=" " application_type="resource_plan" participant_name="testgen" user_name="testuser"> <resource_plan version_no="1.0" standing_flag="true"> <standing expiry_date=" " type="sun" /> <participant_detail start_hr="8" start_int="1" end_hr="7" end_int="2" shortfall_mwh="45.0" total_demand_mwh="23.0" non_sched_generation="0.0" total_demand_eoi_mw="24.1" /> <facility_detail facility_name="test_facility_4" facility_type="non_sched_gen"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" energy_mwh="0.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_11"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="65.0" energy_mwh="0.0" ramp_rate="2.0" /> <synchronisation time="23:59" operation="commit" /> <synchronisation time="00:00" operation="de-commit" /> <synchronisation time="10:45" operation="commit" /> <synchronisation time="13:30" operation="de-commit" /> </facility_detail> <facility_detail facility_name="test_facility_12" facility_type="sched_gen"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="50.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> <facility_detail facility_type="non_sched_gen" facility_name="test_facility_104"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" energy_mwh="0.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_111"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="10.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_112"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="5.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> </resource_plan> </market_submit> </bids_offers> Sample (Standing cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel trading_date=" " application_type="resource_plan" participant_name="testgen1" user_name="testerg1"> <resource_plan version_no="1.0" standing_flag="true"> <standing type="sun" /> </resource_plan> </market_cancel> </bids_offers> Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit trading_date=" " application_type="resource_plan" participant_name="testgen" user_name="testuser"> <resource_plan version_no="1.0" standing_flag="false"> AEMO - WEMS Submission Specifications v5.0 16

17 <participant_detail start_hr="8" start_int="1" end_hr="7" end_int="2" shortfall_mwh="45.0" total_demand_mwh="23.0" non_sched_generation="0.0" total_demand_eoi_mw="24.3" /> <facility_detail facility_name="test_facility_4" facility_type="non_sched_gen"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" energy_mwh="0.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_11"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="65.0" energy_mwh="0.0" ramp_rate="2.0" /> <synchronisation time="23:59" operation="commit" /> <synchronisation time="00:00" operation="de-commit" /> <synchronisation time="10:45" operation="commit" /> <synchronisation time="13:30" operation="de-commit" /> </facility_detail> <facility_detail facility_name="test_facility_12" facility_type="sched_gen"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="50.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> <facility_detail facility_type="non_sched_gen" facility_name="test_facility_104"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" energy_mwh="0.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_111"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="10.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> <facility_detail facility_type="sched_gen" facility_name="test_facility_112"> <energy_detail start_hr="8" start_int="1" end_hr="7" end_int="2" target_mw="5.0" energy_mwh="0.0" ramp_rate="2.0" /> </facility_detail> </resource_plan> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel trading_date=" " application_type="resource_plan" participant_name="testgen1" user_name="testerg1"> <resource_plan version_no="1.0" standing_flag="false"> </resource_plan> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query trading_date=" " application_type="resource_plan" participant_name="testgen" user_name="testuser"> <resource_plan version_no="1.0" standing_flag="true"> <standing type="sun" /> </resource_plan> </market_query> </bids_offers> AEMO - WEMS Submission Specifications v5.0 17

18 4.2 CSV Format The resource plan CSV submission consists of four files, containing details of the overall resource plan, and includes information on participant details, facility details, energy details, facility synchronisation and Balancing data (for pre-balancing market). Only submit and cancel actions are permitted and no query is permitted for the CSV transaction. Participants with only Non-Schedule Generators are only required to submit the file resources_particpant_details.csv. Field details are as follows: resources_participant_details.csv FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the bilateral submission. For standing submissions, the trading date that the standing submission is effective from. action String Either "SUBMIT" for submission, or "CANCEL" for cancel. standing_flag Boolean Whether the submission is a standing submission (true) or a variation submission (false) standing_day_type String if standing_flag = true standing_expiry_date is standing_flag = true and action = "SUBMIT" Valid values: MON, TUE, WED, THU, FRI, SAT, SUN or ALL The date that the standing submission is valid until start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. total_demand_mwh Number Optional Total energy demand from curtailable load and interruptible load in Megawatt hours (MWh). Clause of the WEM Rules (d) shortfall_mwh Number Optional Shortfall between net energy scheduled in resource plan and the net contract position in Megawatt hours (MWh). Clause of the WEM Rules (e) non_sched_generation Number Optional Sum of expected Non-Scheduled Generation in MWh (loss factor adjusted). Clause of the WEM Rules (a) total_demand_eoi_mw Number Optional End of Interval MW value of total demand. Clause of the WEM Rules (da) resources_facility_details.csv FIELD NAME TYPE CONSTRAINTS COMMENTS facility_name String (2 to 32 characters) The name of the facility to which the facility details apply Clause of the WEM Rules (b) i facility_type String Valid values: SCHED_GEN and DISP_LOAD, start_hr Starting hour, between 0 and 23 AEMO - WEMS Submission Specifications v5.0 18

19 FIELD NAME TYPE CONSTRAINTS COMMENTS start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. energy_mwh Number Total energy generated for the specified interval range in Megawatt hours (MWh). Clause of the WEM Rules (b) iii target_mw Number Optional Sent out output at the end of the specified interval range in Megawatts (MW). ( field for SCHED_GEN and DISP_LOAD) Clause of the WEM Rules (b) v ramp_rate Number Ramp rate specified for trading interval in (MW/min). Clause of the WEM Rules (b) iv resources_synchronisation.csv FIELD NAME TYPE CONSTRAINTS COMMENTS facility_name String (2 to 32 characters) The name of the facility to which the synchronisation applies. Clause of the WEM Rules (b) i operation String Valid values: COMMIT, DE-COMMIT. Clause of the WEM Rules (b) ii time String (hh:mm) The time at which the synchronisation operation occurs. Clause of the WEM Rules (b) ii The following table shows the fields within resource plan sections, and the file that contains those sections. Field Group Files Fields Resource Plan resources_participant_details.csv trading_date, action,standing_flag, standing_day_type, standing_expiry_date Participant Detail resources_participant_details.csv start_hr, start_int, end_hr, end_int, total_demand_mwh, shortfall_mwh. non_sched_generation, total_demand_eoi_mw Facility Detail resources_facility_details.csv resources_synchronisation.csv facility_name, facility_type Energy Detail resources_facility_details.csv start_hr, start_int, end_hr, end_int, energy_mwh, target_mw, ramp_rate Synchronisation resources_synchronisation.csv operation, time All lines in the resources_participant_details.csv file must contain the same values for fields in the Resource Plan section as specified in the fields column in above (i.e. trading_date, action, standing_flag, standing_day_type and standing_expiry_date fields). i.e. A submission must be either a standing or variation, not a combination. All energy details for a facility must contain the same values in the Facility Detail section, as specified in the fields column in above (i.e. facility_name and facility_type fields). All synchronisation details for a facility must contain the same values in the Facility Detail section, as specified in the fields column in above (i.e. the facility_name field). AEMO - WEMS Submission Specifications v5.0 19

20 Sample (Standing) These sample submissions are for illustration purposes only. Sample resources_participant_details.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,total_demand_mwh,shortfall_mwh,non_sched_generation,total_demand_eoi_mw 9/03/2011,submit,true,SUN,15/04/2011,8,1,8,1,23,45,0,25 Sample resources_facility_details.csv facility_name,facility_type,start_hr,start_int,end_hr,end_int,energy_mwh,target_mw,ramp_rate TEST_FACILITY_4,NON_SCHED_GEN,8,1,7,2,0,,3.0 TEST_FACILITY_11,SCHED_GEN,8,1,7,2,0,65,3.0 TEST_FACILITY_12,SCHED_GEN,8,1,7,2,0,50,3.0 TEST_FACILITY_104,NON_SCHED_GEN,8,1,7,2,0,,3.0 TEST_FACILITY_111,SCHED_GEN,8,1,7,2,0,10,3.0 TEST_FACILITY_112,SCHED_GEN,8,1,7,2,0,5,3.0 Sample resources_synchronisation.csv facility_name,operation,time TEST_FACILITY_11,COMMIT,23:59 TEST_FACILITY_11,DE-COMMIT,0:00 TEST_FACILITY_11,COMMIT,10:45 TEST_FACILITY_11,DE-COMMIT,13:30 Sample (Standing cancellation) Only a resources_participant_details.csv file is required as part of a cancel resource plan submission. Sample resources_participant_details.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,total_demand_mwh,shortfall_mwh,non_sched_generation,total_demand_eoi_mw 9/03/2011,cancel,true,SUN,,,,,,,,, Sample (Variation) Sample resources_participant_details.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,total_demand_mwh,shortfall_mwh,non_sched_generation,total_demand_eoi_mw 9/03/2011,submit,false,,,8,1,8,1,23,45,0,24 Sample resources_facility_details.csv facility_name,facility_type,start_hr,start_int,end_hr,end_int,energy_mwh,target_mw,ramp_rate TEST_FACILITY_4,NON_SCHED_GEN,8,1,7,2,0,,3.0 TEST_FACILITY_11,SCHED_GEN,8,1,7,2,0,65,3.0 TEST_FACILITY_12,SCHED_GEN,8,1,7,2,0,50,3.0 TEST_FACILITY_104,NON_SCHED_GEN,8,1,7,2,0,,3.0 TEST_FACILITY_111,SCHED_GEN,8,1,7,2,0,10,3.0 TEST_FACILITY_112,SCHED_GEN,8,1,7,2,0,5,3.0 Sample resources_synchronisation.csv facility_name,operation,time TEST_FACILITY_11,COMMIT,23:59 TEST_FACILITY_11,DE-COMMIT,0:00 TEST_FACILITY_11,COMMIT,10:45 TEST_FACILITY_11,DE-COMMIT,13:30 AEMO - WEMS Submission Specifications v5.0 20

21 Sample (Variation cancellation) Only a resources_participant_details.csv file is required as part of a cancel resource plan submission. Sample resources_participant_details.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,total_demand_mwh,shortfall_mwh,non_sched_generation,total_demand_eoi_mw 9/03/2011,cancel,false,,,,,,,,,, AEMO - WEMS Submission Specifications v5.0 21

22 5. STEM The STEM submission allows participants to submit details on their intent in the Short Term Energy Market. STEM contains details on facilities, ancillary services, supply portfolio curve and demand portfolio curve. Participants are able to query and cancel submissions for an individual trading interval, or a range of trading intervals 5.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a STEM submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX Stem StemSubmit 1 1 Standing StandingSubmit 0 1 stem_detail StemDetail 1 48 ancillary_service AncillaryService 0 1 supply_portfolio_curve PqCurveWa 1 1 Point PqPoint 1 Unlimited demand_portfolio_curve PqCurveWa 1 1 Point PqPoint 1 Unlimited stem_facility_detail StemFacilityDetail 0 Unlimited Declaration DeclarationStem 1 48 Attribute details are shown for each element that comprises a STEM submission. The attributes of the standing element are not covered here as this is detailed in Section STEM Element version_no String. Must be set to 1.0 standing_flag Boolean Attribute not required if a variation submission If true, there must be a standing element contained within the stem element. See Section STEM Detail Element start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. AEMO - WEMS Submission Specifications v5.0 22

23 Ancillary Service Element total_liquid_mwh Number Energy reserved for ancillary services from liquid fuelled plant in Megawatt hours (MWh). Clause of the WEM Rules (c) iii and (d) iii total_non_liquid_mwh Number Energy reserved for ancillary services from nonliquid fuelled plant in Megawatt hours (MWh). Clause of the WEM Rules (c) iii and (d) iii Supply Portfolio Curve Element There are no attributes for this element, it contains a collection of point elements, as described below. Demand Portfolio Curve Element There are no attributes for this element, it contains a collection of point elements, as described in below. Point Element price Number Energy price at the point in the supply or demand curve in $/MWh. Clause of the WEM Rules (c) iv & v and (d) iv & v quantity Number Quantity of energy at the point in the supply or demand curve in Megawatt hours (MWh). Clause of the WEM Rules (c) iv & v and (d) iv & v Stem Facility Detail Element facility_name String (2 to 32 characters) Name of the facility Clause of the WEM Rules (a) facility_type String Valid values: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, NON_DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, or INTMNT_INTRPT_LOAD Clause of the WEM Rules (a) Declaration Element start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. AEMO - WEMS Submission Specifications v5.0 23

24 fuel_in_use String Valid values: LIQUID, NON-LIQUID. Clause of the WEM Rules (c) i and (d) i unavailable_capacity_mwh Number Optional Capacity which is unavailable. Default is 0. Clause of the WEM Rules (c) ii and (d) ii Sample (Standing) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit application_type="stem" trading_date=" " participant_name="testgen1" user_name="testerg1"> <stem standing_flag="true" version_no="1.0"> <standing expiry_date=" " type="all" /> <stem_detail start_hr="8" start_int="1" end_hr="7" end_int="2"> <ancillary_service total_liquid_mwh="0.0" total_non_liquid_mwh="20.0" /> <supply_portfolio_curve> <point price="0.0" quantity="25.392" /> </supply_portfolio_curve> <demand_portfolio_curve> <point price="435.0" quantity="25.392" /> </demand_portfolio_curve> </stem_detail> <stem_facility_detail facility_name="testfac1" facility_type="sched_gen"> <declaration start_hr="8" start_int="1" end_hr="7" end_int="2" fuel_in_use="non-liquid" unavailable_capacity_mwh="0.0" /> </stem_facility_detail> </stem> </market_submit> </bids_offers> Sample (Standing cancellation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers> <market_cancel application_type="stem" trading_date=" " participant_name="testgen1" user_name="testerg1"> <stem standing_flag="true" version_no="1.0"> <standing type="all" /> </stem> </market_cancel> </bids_offers> Sample (Variation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers> <market_submit application_type="stem" trading_date=" " participant_name="testgen" user_name="testuser"> <stem standing_flag="false" version_no="1.0"> <stem_detail start_hr="8" start_int="1" end_hr="7" end_int="2"> <ancillary_service total_liquid_mwh="0.0" total_non_liquid_mwh="20.0" /> <supply_portfolio_curve> <point price="0.0" quantity="25.392" /> </supply_portfolio_curve> <demand_portfolio_curve> <point price="435.0" quantity="25.392" /> </demand_portfolio_curve> </stem_detail> AEMO - WEMS Submission Specifications v5.0 24

25 <stem_facility_detail facility_name="testfac1" facility_type="sched_gen"> <declaration start_hr="8" start_int="1" end_hr="7" end_int="2" fuel_in_use="non-liquid" unavailable_capacity_mwh="0.0" /> </stem_facility_detail> </stem> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers> <market_cancel application_type="stem" trading_date=" " participant_name="testgen1" user_name="testerg1"> <stem standing_flag="false" version_no="1.0"> </stem> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <bids_offers> <market_query application_type="stem" trading_date=" " participant_name="testgen1" user_name="testerg1"> <stem standing_flag="true" version_no="1.0"> <standing type="all" /> </stem> </market_query> </bids_offers> 5.2 CSV Format The STEM CSV format consists of four files that contain details on the STEM submission, including ancillary services, supply portfolio curve, demand portfolio curve and facility declarations. Not all CSV files are required to make up a complete STEM submission. The following table indicates which files are required. Note that only submit and cancel actions are permitted and no query is permitted for the CSV transaction. File stem_facility_detail.csv stem_ancillary_service.csv stem_supply_portfolio_curve.csv stem_demand_portfolio_curve.csv Not Not (unless a cancel submission) stem_facility_detail.csv FIELD NAME TYPE CONSTRAINTS COMMENTS facility_name String (2 to 32 characters) The name of the facility whose details are supplied Clause of the WEM Rules (a) AEMO - WEMS Submission Specifications v5.0 25

26 FIELD NAME TYPE CONSTRAINTS COMMENTS facility_type String Valid values: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, NON_DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, or INTMNT_INTRPT_LOAD Clause of the WEM Rules (a) start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. fuel_in_use String Valid values: LIQUID, NON-LIQUID. Clause of the WEM Rules (c) i and (d) i unavailable_capacity_mwh Number Optional Default is 0. Clause of the WEM Rules (c) ii and (d) ii stem_ancillary_service.csv FIELD NAME TYPE CONSTRAINTS COMMENTS start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. total_liquid_mwh Number Energy reserved for ancillary services from liquid fuelled plant in Megawatt hours (MWh). Clause of the WEM Rules (c) iii and (d) iii total_non_liquid_mwh Number Energy reserved for ancillary services from nonliquid fuelled plant in Megawatt hours (MWh). Clause of the WEM Rules (c) iii and (d) iii stem_supply_portfolio_curve.csv The supply portfolio curve file contains the trading date of the submission, and standing submissions standing details as there will always be at least one supply portfolio curve record. FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the bilateral submission. For standing submissions, the trading date that the standing submission is effective from. action String Either "SUBMIT" for submission, or "CANCEL" for cancel. standing_flag Boolean Whether the submission is a standing submission (true) or a variation submission (false) standing_day_type String if standing_flag = true Valid values: MON, TUE, WED, THU, FRI, SAT, SUN or ALL Clause of the WEM Rules 6.3C.6A AEMO - WEMS Submission Specifications v5.0 26

27 FIELD NAME TYPE CONSTRAINTS COMMENTS standing_expiry_date is standing_flag = true and action = SUBMIT The final date on which the standing submission is valid Clause of the WEM Rules 6.3C.6A start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. price Number Energy price at the point in the supply curve in $/MWh Clause of the WEM Rules (c) iv & v quantity Number Quantity of energy at the point in the supply curve in Megawatt hours (MWh). Clause of the WEM Rules (c) iv & v stem_demand_portfolio_curve.csv FIELD NAME TYPE CONSTRAINTS COMMENTS start_hr Starting hour, between 0 and 23 start_int Starting interval within the start hour. Valid values: 1 and 2. end_hr Ending hour, between 0 and 23 end_int Ending interval within the end hour. Valid values: 1 and 2. price Number Energy price at the point in the demand curve in $/MWh Clause of the WEM Rules (d) iv & v quantity Number Quantity of energy at the point in the demand curve in Megawatt hours (MWh). Clause of the WEM Rules (d) iv & v The following table shows the sections within the STEM submission, the files in which the sections are contained and the fields in each section. Section Files Fields STEM submission stem_supply_portfolio_curve.csv trading_date, action,standing_flag, standing_day_type, standing_expiry_date STEM detail stem_ancillary_service.csv stem_supply_portfolio_curve.csv stem_demand_portfolio_curve.csv start_hr, start_int, end_hr, end_int Ancillary Services stem_ancillary_service.csv total_liquid_mwh, total_non_liquid_mwh Supply Portfolio Curve stem_supply_portfolio_curve.csv price, quantity Demand Portfolio Curve stem_demand_portfolio_curve.csv price, quantity Facility Detail stem_facility_detail.csv facility_name, facility_type Facility Declaration stem_facility_detail.csv start_hr, start_int, end_hr, end_int, fuel_in_use, unavailable_capacity_mwh All lines in the stem_supply_portfolio_curve.csv file must contain the same values for the STEM submission section, as specified above (i.e. trading_date, action, standing_flag, standing_day_type and standing_expiry_date fields). i.e. A submission must be either a standing or variation, not a combination. AEMO - WEMS Submission Specifications v5.0 27

28 The trading_date, action, standing_flag, standing_day_type and standing_expiry_date must have the same values for all rows in the stem_supply_portfolio_curve.csv file. The stem_ancilliary_service.csv, stem_supply_portfolio_curve.csv and stem_demand_portfolio_curve.csv files contain the start and end trading intervals for which the details apply. If these intervals are duplicated in the separate files, a common stem detail will be created that becomes the parent of the ancillary service, supply portfolio or demand portfolio. The start and end hour and interval ranges must have the same values across all CSV submission files. Sample (Standing) These sample submissions are for illustration purposes only. Sample stem_facility_detail.csv facility_name,facility_type,start_hr,start_int,end_hr,end_int,fuel_in_use,unavailable_capacity_ mwh STHRNCRS_EG,SCHED_GEN,8,1,8,1,NON-LIQUID,0 STHRNCRS_EG,SCHED_GEN,8,2,8,2,NON-LIQUID,0 Sample stem_ancillary_service.csv start_hr,start_int,end_hr,end_int,total_liquid_mwh,total_non_liquid_mwh 8,1,7,2,0,25 Sample stem_supply_portfolio_curve.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,price,quantity 9/03/2011,submit,true,ALL,22/11/2011,8,1,7,2,0,4.392 Sample stem_demand_portfolio_curve.csv start_hr,start_int,end_hr,end_int,price,quantity 8,1,7,2,435,4.392 Sample (Standing cancellation) Note: Only a stem_supply_portfolio_curve.csv file is required as part of a STEM cancel submission. Sample stem_supply_portfolio_curve.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,price,quantity 9/03/2011,cancel,true,ALL,,,,,,, Sample (Variation) These sample submissions are for illustration purposes only. Sample stem_facility_detail.csv facility_name,facility_type,start_hr,start_int,end_hr,end_int,fuel_in_use,unavailable_capacity_ mwh STHRNCRS_EG,SCHED_GEN,8,1,8,1,NON-LIQUID,0 STHRNCRS_EG,SCHED_GEN,8,2,8,2,NON-LIQUID,0 Sample stem_ancillary_service.csv start_hr,start_int,end_hr,end_int,total_liquid_mwh,total_non_liquid_mwh 8,1,7,2,0,25 Sample stem_supply_portfolio_curve.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,price,quantity AEMO - WEMS Submission Specifications v5.0 28

29 9/03/2011,submit,false,,,8,1,7,2,0,4.392 Sample stem_demand_portfolio_curve.csv start_hr,start_int,end_hr,end_int,price,quantity 8,1,7,2,435,4.392 Sample (Variation cancellation) Note: Only a stem_supply_portfolio_curve.csv file is required as part of a STEM cancel submission. Sample stem_supply_portfolio_curve.csv trading_date,action,standing_flag,standing_day_type,standing_expiry_date,start_hr,start_int,end _hr,end_int,price,quantity 9/03/2011,cancel,false,,,,,,,, 6. RESERVE CAPACITY ALLOCATION SUBMISSIONS 6.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a reserve capacity allocation submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX Resv_cap_allocation ResvCapAllocationSubmit 1 1 consumer Consumer 0 Unlimited Attribute details are shown for each element that comprises a reserve capacity allocation submission. Trading date should be specified as the first day of the trading month. Resv_cap_allocation Element version_no String. Must be set to 1.0 Consumer Element participant_name String The participant name to which the capacity credits are allocated to. Clause of the WEM Rules (b) capacity_credits Number The number of capacity credits allocated to the participant Clause of the WEM Rules (c) capacity_credit_type String The type of capacity credits allocated Valid values: NORM, LTSPA, STSPA, NCS Clause of the WEM Rules (c) AEMO - WEMS Submission Specifications v5.0 29

30 auction_year Number The Reserve Capacity year Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit mode="normal" participant_name="testcon1" trading_date=" " application_type="resv_cap_allocation" user_name="testuser"> <resv_cap_allocation version_no="1.0"> <consumer participant_name="testcons1" capacity_credits="75" capacity_credit_type="norm" auction_year="2008" /> </resv_cap_allocation> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel application_type="resv_cap_allocation" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_allocation version_no="1.0"> </resv_cap_allocation> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query application_type="resv_cap_allocation" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_allocation version_no="1.0"> </resv_cap_allocation> </market_query> </bids_offers> 6.2 CSV Format The reserve capacity allocation CSV submission consists of a single file. Field details for the CSV file are shown below for each element that comprises a bilateral generation submission. Note that only submit and cancel actions are permitted and no query action is permitted for the CSV transaction. FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the reserve capacity allocation submission. Trading date should be the first day of the trading month action String Either "SUBMIT" for submission, or "CANCEL" for cancel. participant_name String The participant name to which the capacity credits are allocated to. Clause of the WEM Rules (b) AEMO - WEMS Submission Specifications v5.0 30

31 FIELD NAME TYPE CONSTRAINTS COMMENTS capacity_credits Number (except for action "CANCEL" when it must be omitted) capacity_credit_type String (except for action "CANCEL" when it must be omitted) auction_year Number (except for action "CANCEL" when it must be omitted) The number of capacity credits allocated to the participant Clause of the WEM Rules (c) The type of capacity credits allocated Valid values: NORM, LTSPA, STSPA, NCS Clause of the WEM Rules (c) The reserve capacity year The following table lists the fields that are relevant for each section contained in the CSV file Field Group Submission Consumer Fields trading_date, action participant_name, capacity_credits, capacity_credit_type, auction_year All lines in the file must be specified and contain the same values for the submission fields as specified in the Submission Field Group in above (i.e. trading_date and action). Sample (Variation) trading_date,action,participant_name,capacity_credits,capacity_credit_type,auction_year 01/10/2011,submit,testcon1,25.200,norm,2011 Sample (Variation cancellation) trading_date,action,participant_name,capacity_credits,capacity_credit_type,auction_year 01/10/2011,cancel,testcon1,,, AEMO - WEMS Submission Specifications v5.0 31

32 7. RESERVE CAPACITY CONFIRM ALLOCATION SUBMISSIONS 7.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a reserve capacity confirm allocation submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX Resv_cap_confirm_allocation ResvCapAllocConfirmSubmit 1 1 supplier Supplier 0 Unlimited Attribute details are shown for each element that comprises a reserve capacity confirm allocation submission. Resv_cap_confirm_allocation Element version_no String. Must be set to 1.0 Supplier Element participant_name String Optional The participant allocating the capacity credits. capacity_credits_reduction Number Optional The number of capacity credits to be reduced Clause of the WEM Rules Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit mode="normal" participant_name="testcon1" trading_date=" " application_type="resv_cap_confirm_allocation" user_name="testuser"> <resv_cap_confirm_allocation version_no="1.0"> <supplier participant_name="testcons1" capacity_credits_reduction="78"> </supplier> </resv_cap_confirm_allocation> </market_submit> </bids_offers> AEMO - WEMS Submission Specifications v5.0 32

33 Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel application_type="resv_cap_confirm_allocation" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_confirm_allocation version_no="1.0"> </resv_cap_confirm_allocation> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation= xsi:nonamespaceschemalocation="mint.xsd"> <market_query application_type="resv_cap_confirm_allocation" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_confirm_allocation version_no="1.0"> </resv_cap_confirm_allocation> </market_query> </bids_offers> 7.2 CSV Format The reserve capacity allocation CSV submission consists of a single file. Note that only submit and cancel actions are permitted and no query action is permitted for the CSV transaction. FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the reserve capacity confirm allocation submission. Trading date should be the first day of the trading month action String Either "SUBMIT" for submission, or "CANCEL" for cancel. participant_name String (except for action "CANCEL" when it must be omitted) capacity_credits_reduction Number (except for action "CANCEL" when it must be omitted) The participant allocating the capacity credits. The number of capacity credits to be reduced Clause of the WEM Rules The following table lists the fields that are relevant for each section contained in the CSV file Field Group Submission Consumer Fields trading_date, action participant_name, capacity_credits_reduction All lines in the file must be specified and contain the same values for the submission fields as specified in the Submission Field Group in above (i.e. trading_date and action). AEMO - WEMS Submission Specifications v5.0 33

34 Sample (Variation) trading_date,action,participant_name,capacity_credits_reduction 01/10/2011,submit,testcon1,6.000 Sample (Variation cancellation) trading_date,action,participant_name,capacity_credits_reduction 01/10/2011,cancel,testcon1, AEMO - WEMS Submission Specifications v5.0 34

35 8. RESERVE CAPACITY CERTIFICATION DATA SUBMISSIONS 8.1 XML Format The reserve capacity certification data submission allows participants to submit certification details for use in the reserve capacity market. Participants are to submit according to their facility type utilising the XML and CSV structures defined below. The xml format is specified by wems-1.0.xsd. The following table contains the details of the nesting structure of elements that comprise a reserve capacity certification submission, and the number of times that each element can occur within the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX rccertificationsubmission rccertificationsubmission 1 1 resourcesubmission resourcesubmission 1 Unlimited block block 0 3 Attribute details are shown for each element that comprises a reserve capacity certification data allocation submission. resourcesubmission Element facilityname String (2 to 32 characters) capacityyear (YYYY) The name of the facility The Reserve Capacity year certificationmode String Possible values are: NORMAL Normal CRC COND Conditional CRC ECRC Early CRC SMALL_GEN Small Generator CRC action String Either "SUBMIT" for submission or "CANCEL" for cancel. projectapproval projectfinancing projectsiteprep projectconstructionstart equipmentinstallation (YYYY-MM- DD) (YYYY-MM- DD) (YYYY-MM- DD) (YYYY-MM- DD) (YYYY-MM- DD) Optional Optional Optional Optional Optional The date which the project was approved. Clause of the WEM Rules (c) iii.1. The date which the project was financed. Clause of the WEM Rules (c) iii.2. The date which the project s site was prepared. Clause of the WEM Rules (c) iii.3. The date which the project started construction. Clause of the WEM Rules (c) iii.4. The date which the project had its equipment installed. Clause of the WEM Rules (c) iii.5. AEMO - WEMS Submission Specifications v5.0 35

36 commissioningtrials fullcapacityobligation decommission (YYYY-MM- DD) (YYYY-MM- DD) (YYYY-MM- DD) Optional Optional Optional The date which the project underwent commissioning trials. Clause of the WEM Rules (c) iii.6. The date which the project achieved full capacity obligation Clause of the WEM Rules (c) iii.7 The date which the project was decommissioned Clause of the WEM Rules (d) forcedoutagerate Number Optional Forced outage rate Clause of the WEM Rules (e) vi. unforcedoutagerate Number Optional Unforced outage rate Clause of the WEM Rules (e) vi. actualforcedoutagerate Number Optional Actual forced outage rate Clause of the WEM Rules (e) vii actualunforcedoutagerate Number Optional Actual unforced outage rate Clause of the WEM Rules (e) vii. conditionalconfirmation String Optional Whether there is conditional confirmation. Must be true or false Should only be true if Conditional CRC previously approved for the same Capacity Year. Clause of the WEM Rules (h). certificationmethodology String Optional The certification methodology types are: ALTERNATE and NORMAL Clause of the WEM Rules ncscontract Boolean Optional Whether there is an NCS contract. Must be true or false Clause of the WEM Rules (j). maxavailablehoursperyear maxavailablehoursperday (1 to 8784) (1 to 24) Optional Optional Maximum hours available for the year. Clause of the WEM Rules (f) ii. Maximum hours available for each day. Clause of the WEM Rules (f) iii. maxactivationcallsperyear Optional Maximum number of activation calls for the year Clause of the WEM Rules (f) iv. minhournoticeperiod integer Optional Minimum notice period required for dispatch. Clause of the WEM Rules (f) v. mindispatchdeliveryhour mindispatchdeliveryinterval maxdispatchdeliveryhour maxdispatchdeliveryinterval (0 to 23) (1 to 2) (0 to 23) (1 to 2) Optional Optional Optional Optional The minimum delivery hour the load can be dispatched. Clause of the WEM Rules (f) vi. The minimum delivery interval the load can be dispatched. Clause of the WEM Rules (f) vi. The maximum delivery hour the load can be dispatched. Clause of the WEM Rules (f) vi. The maximum delivery interval the load can be dispatched. Clause of the WEM Rules (f) vi. AEMO - WEMS Submission Specifications v5.0 36

37 businessdaysdispatch String Optional true when facility can only be dispatched on business days. false when facility can be dispatched on any days. Clause of the WEM Rules (f) vi. initiallevel Number Optional Level in sent out MW Clause of the WEM Rules B block Element capacityblock String Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 availabilityclass String Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 availablecapacitymw Number Available capacity in MW Clause of the WEM Rules (e) ii. availablecapacitymwhot Number Optional Available capacity in MW when temperature > 41C Clause of the WEM Rules (e) iii. Sample (Variation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <rccertificationsubmission> <resourcesubmission facilityname="facility_test_01" capacityyear="2005" certificationmode="normal" action="submit" projectapproval=" " projectfinancing=" " projectsiteprep=" " projectconstructionstart=" " equipmentinstallation=" " commissioningtrials=" " fullcapacityobligation=" " decommission=" " forcedoutagerate="1" unforcedoutagerate="2" actualforcedoutagerate="2" actualunforcedoutagerate="2" conditionalconfirmation="true" certificationmethodology="normal" ncscontract="true" maxavailablehoursperyear="2" maxavailablehoursperday="2" maxactivationcallsperyear="2" minhournoticeperiod="2" mindispatchdeliveryhour="2" mindispatchdeliveryinterval="2" maxdispatchdeliveryhour="2" maxdispatchdeliveryinterval="2" businessdaysdispatch="true" initiallevel="2"> <block capacityblock="block1" availabilityclass="class1" availablecapacitymw="1" availablecapacitymwhot="1" /> <block capacityblock="block2" availabilityclass="class4" availablecapacitymw="1" availablecapacitymwhot="1" /> </resourcesubmission> </rccertificationsubmission> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8" standalone="yes"?> <rccertificationsubmission> <resourcesubmission facilityname="facility_test_01" capacityyear="2005" certificationmode="normal" action="cancel"> </resourcesubmission> </rccertificationsubmission> AEMO - WEMS Submission Specifications v5.0 37

38 8.2 CSV Format Three Reserve Capacity Certification CSV file formats exist for different facility types: - For Scheduled Generators use: rc_certification_sched_gen.csv - For Non-Scheduled Generators use: rc_certification_non_sched_gen.csv - For DSP and Loads use: rc_certification_dsp_load.csv and rc_certification_block_dsp_load.csv (if applicable) rc_certification_sched_gen.csv FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) The name of the facility or facility upgrade. The facility upgrade name is auto generated in the MPR in the format: ParentFacilityName_UPG_CapacityYear[X] Where: CapacityYear = Year that facility Upgrade can be used in the CRC process. X = Automatically Generated by the system as a counter for years where there are multiple upgrades for a facility. capacity_year (YYYY) The reserve capacity year project_approval_date (except for action "CANCEL" when it must be omitted) The date which the project was approved. Clause of the WEM Rules (c) iii.1. project_financing_date (except for action "CANCEL" when it must be omitted) The date which the project was financed. Clause of the WEM Rules (c) iii.2. project_site_prep_date (except for action "CANCEL" when it must be omitted) The date which the project s site was prepared. Clause of the WEM Rules (c) iii.3. project_construction_start_date (except for action "CANCEL" when it must be omitted) The date which the project started construction. Clause of the WEM Rules (c) iii.4. equipment_installation_date (except for action "CANCEL" when it must be omitted) The date which the project had its equipment installed. Clause of the WEM Rules (c) iii.5. commissioning_trials_date (except for action "CANCEL" when it must be omitted) The date which the project underwent commissioning trials. Clause of the WEM Rules (c) iii.6. full_capacity_obligation_date (except for action "CANCEL" when it must be omitted) The date which the project achieved full capacity obligation Clause of the WEM Rules (c) iii.7 AEMO - WEMS Submission Specifications v5.0 38

39 FIELD NAME TYPE CONSTRAINTS COMMENTS decommission_date Optional forced_outage_rate Number (except for action "CANCEL" when it must be omitted) unforced_outage_rate Number (except for action "CANCEL" when it must be omitted) actual_forced_outage_rate Number (except for action "CANCEL" when it must be omitted) actual_unforced_outage_rate Number (except for action "CANCEL" when it must be omitted) conditional_confirmation Boolean (except for action "CANCEL" when it must be omitted) certification_methodology String (except for action "CANCEL" when it must be omitted) ncs_contract Boolean (except for action "CANCEL" when it must be omitted) The date which the project was decommissioned Clause of the WEM Rules (d) Forced outage rate Clause of the WEM Rules (e) vi. Unforced outage rate Clause of the WEM Rules (e) vi. Actual forced outage rate Clause of the WEM Rules (e) vii Actual unforced outage rate Clause of the WEM Rules (e) vii. Whether there is conditional confirmation. Must be true or false Should only be true if Conditional CRC previously approved for the same Capacity Year. Clause of the WEM Rules (h). The certification methodology types are: ALTERNATE and NORMAL Clause of the WEM Rules Whether there is an NCS contract. Must be true or false Clause of the WEM Rules (j). available_capacity_mw Number Available capacity in MW Clause of the WEM Rules (e) ii. available_capacity_mw_hot Number Available capacity in MW when temperature > 41C Clause of the WEM Rules (e) iii. AEMO - WEMS Submission Specifications v5.0 39

40 rc_certification_non_sched_gen.csv FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) The name of the facility or facility upgrade. The facility upgrade name is auto generated in the MPR in the format: ParentFacilityName_UPG_CapacityYear[X] Where: CapacityYear = Year that facility Upgrade can be used in the CRC process. capacity_year project_approval_date project_financing_date project_site_prep_date project_construction_start_date equipment_installation_date commissioning_trials_date full_capacity_obligation_date decommission_date (YYYY) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) Optional conditional_confirmation Boolean (except for action "CANCEL" when it must be omitted) X = Automatically Generated by the system as a counter for years where there are multiple upgrades for a facility. The reserve capacity year The date which the project was approved. Clause of the WEM Rules (c) iii.1. The date which the project was financed. Clause of the WEM Rules (c) iii.2. The date which the project s site was prepared. Clause of the WEM Rules (c) iii.3. The date which the project started construction. Clause of the WEM Rules (c) iii.4. The date which the project had its equipment installed. Clause of the WEM Rules (c) iii.5. The date which the project underwent commissioning trials. Clause of the WEM Rules (c) iii.6. The date which the project achieved full capacity obligation Clause of the WEM Rules (c) iii.7 The date which the project was decommissioned Clause of the WEM Rules (d) Whether there is conditional confirmation. Must be true or false Should only be true if Conditional CRC previously approved for the same Capacity Year. Clause of the WEM Rules (h). AEMO - WEMS Submission Specifications v5.0 40

41 FIELD NAME TYPE CONSTRAINTS COMMENTS certification_methodology String (except for action "CANCEL" when it must be omitted) ncs_contract Boolean (except for action "CANCEL" when it must be omitted) The certification methodology types are: ALTERNATE and NORMAL Clause of the WEM Rules Whether there is an NCS contract. Must be true or false Clause of the WEM Rules (j). available_capacity_mw Number Available capacity in MW Clause of the WEM Rules (e) ii. initial_required_level Number Level in sent out MW Clause of the WEM Rules B rc_certification_dsp_load.csv FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) The name of the facility or facility upgrade. The facility upgrade name is auto generated in the MPR in the format: ParentFacilityName_UPG_CapacityYear[X] Where: CapacityYear = Year that facility Upgrade can be used in the CRC process. X = Automatically Generated by the system as a counter for years where there are multiple upgrades for a facility. capacity_year Year (YYYY) The reserve capacity year project_approval_date (except for action "CANCEL" when it must be omitted) The date which the project was approved. Clause of the WEM Rules (c) iii.1. project_financing_date (except for action "CANCEL" when it must be omitted) The date which the project was financed. Clause of the WEM Rules (c) iii.2. project_site_prep_date (except for action "CANCEL" when it must be omitted) The date which the project s site was prepared. Clause of the WEM Rules (c) iii.3. project_construction_start_date (except for action "CANCEL" when it must be omitted) The date which the project started construction. Clause of the WEM Rules (c) iii.4. equipment_installation_date (except for action "CANCEL" when it must be omitted) The date which the project had its equipment installed. Clause of the WEM Rules (c) iii.5. commissioning_trials_date (except for action "CANCEL" when it must be omitted) The date which the project underwent commissioning trials. Clause of the WEM Rules (c) iii.6. AEMO - WEMS Submission Specifications v5.0 41

42 FIELD NAME TYPE CONSTRAINTS COMMENTS full_capacity_obligation_date decommission_date (except for action "CANCEL" when it must be omitted) Optional conditional_confirmation Boolean (except for action "CANCEL" when it must be omitted) ncs_contract Boolean (except for action "CANCEL" when it must be omitted) The date which the project achieved full capacity obligation Clause of the WEM Rules (c) iii.7 The date which the project was decommissioned Clause of the WEM Rules (d) Whether there is conditional confirmation. Must be true or false Should only be true if Conditional CRC previously approved for the same Capacity Year. Clause of the WEM Rules (h). Whether there is an NCS contract. Must be true or false Clause of the WEM Rules (j). availability_class String Specifies the capacity class: CLASS1 for Generators. CLASS2, CLASS3 or CLASS4 for Loads. Clause of the WEM Rules available_capacity_mw Number Available capacity in MW Clause of the WEM Rules (e) ii. max_available_hours_per_year max_available_hours_per_day (1 to 8784) (1 to 24) Maximum hours available for the year. Clause of the WEM Rules (f) ii. Maximum hours available for each day. Clause of the WEM Rules (f) iii. max_activation_calls_per_year Maximum number of activation calls for the year Clause of the WEM Rules (f) iv. min_hour_notice_period Minimum notice period required for dispatch. Clause of the WEM Rules (f) v. min_dispatch_delivery_hour min_dispatch_delivery_interval max_dispatch_delivery_hour max_dispatch_delivery_interval (0 to 23) (1 to 2) (0 to 23) (1 to 2) The minimum delivery hour the load can be dispatched. Clause of the WEM Rules (f) vi. The minimum delivery interval the load can be dispatched. Clause of the WEM Rules (f) vi. The maximum delivery hour the load can be dispatched. Clause of the WEM Rules (f) vi. The maximum delivery interval the load can be dispatched. Clause of the WEM Rules (f) vi. business_days_dispatch Boolean true when facility can only be dispatched on business days. false when facility can be dispatched on any days. Clause of the WEM Rules (f) vi. AEMO - WEMS Submission Specifications v5.0 42

43 rc_certification_block_dsp_load.csv FIELD NAME TYPE CONSTRAINTS COMMENTS facility_name capacity_year String (2 to 32 characters) (YYYY) capacity_block String (except for action The name of the facility. This must match a facility name included in rc_certification_dsp_load.csv The reserve capacity year. Specifies the capacity block. Must be BLOCK2 or BLOCK3 available_capacity_mw Number Available capacity in MW The rc_certification_dsp_load.csv file and the rc_certification_block_dsp_load.csv files must contain the same values for capacity_year and facility_name fields for a given facility. Sample (Variation) Sample rc_certification_sched_gen.csv action,facility_name,capacity_year,project_approval_date,project_financing_date,project_site_pr ep_date,project_construction_start_date,equipment_installation_date,commissioning_trials_date,f ull_capacity_obligation_date,decommission_date,forced_outage_rate,unforced_outage_rate,actual_f orced_outage_rate,actual_unforced_outage_rate,conditional_confirmation,certification_methodolog y,ncs_contract,available_capacity_mw,available_capacity_mw_hot SUBMIT,Facility_Gen,2005,11/01/2010,11/01/2010,11/01/2010,11/01/2010,11/01/2010,11/01/2010,11/0 1/2010,11/01/2010,3,3,3,3,FALSE,NORMAL,FALSE,10,9 Sample rc_certification_non_sched_gen.csv action,facility_name,capacity_year,project_approval_date,project_financing_date,project_site_pr ep_date,project_construction_start_date,equipment_installation_date,commissioning_trials_date,f ull_capacity_obligation_date,decommission_date,conditional_confirmation,certification_methodolo gy,ncs_contract,available_capacity_mw,initial_required_level SUBMIT,facility_non_sg,2007,22/03/2012,22/03/2012,22/03/2012,22/03/2012,22/03/2012,22/03/2012,2 2/03/2012,22/03/2012,FALSE,NORMAL,FALSE,4,1 Sample rc_certification_dsp_load.csv action,facility_name,capacity_year,project_approval_date,project_financing_date,project_site_pr ep_date,project_construction_start_date,equipment_installation_date,commissioning_trials_date,f ull_capacity_obligation_date,decommission_date,conditional_confirmation,ncs_contract,availabili ty_class,available_capacity_mw,max_available_hours_per_year,max_available_hours_per_day,max_act ivation_calls_per_year,min_hour_notice_period,min_dispatch_delivery_hour,min_dispatch_delivery_ interval,max_dispatch_delivery_hour,max_dispatch_delivery_interval,business_days_dispatch SUBMIT,dsp_and_load,2006,11/02/2011,11/02/2011,11/02/2011,11/02/2011,11/02/2011,11/02/2011,11/0 2/2011,11/02/2011,FALSE,FALSE,CLASS1,10,2,2,2,2,2,2,2,2,TRUE Sample rc_certification_block_dsp_load.csv facility_name,capacity_year,capacity_block,available_capacity_mw dsp_and_load,2006,2,3 dsp_and_load,2006,3,3 AEMO - WEMS Submission Specifications v5.0 43

44 Sample (Variation cancellation) Note: The rc_certification_block_dsp_load.csv is not required as part of a cancel submission. Sample rc_certification_sched_gen.csv action,facility_name,capacity_year,project_approval_date,project_financing_date,project_site_pr ep_date,project_construction_start_date,equipment_installation_date,commissioning_trials_date,f ull_capacity_obligation_date,decommission_date,forced_outage_rate,unforced_outage_rate,actual_f orced_outage_rate,actual_unforced_outage_rate,conditional_confirmation,certification_methodolog y,ncs_contract,available_capacity_mw,available_capacity_mw_hot CANCEL,Facility_Gen,2014,,,,,,,,,,,,,,,,, Note: Cancel submissions must specify a facility name in the submission. AEMO - WEMS Submission Specifications v5.0 44

45 9. BILATERAL TRADE DECLARATIONS (RESERVE CAPACITY) SUBMISSIONS 9.1 XML Format The xml format is specified by wems-1.0.xsd. The following table contains the details of the nesting structure of elements that comprise a reserve capacity bilateral trade declaration submission, and the number of times that each element can occur within the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX rcbilateraldeclarationsubmission rcbilateraldeclarationsubmission 1 1 resourcesubmission declresourcesubmission 1 Unlimited declaration declaration 0 3 Attribute details are shown for each element that comprises a reserve capacity bilateral trade declaration submission. resourcesubmission Element facilityname String (2 to 32 characters) The name of the facility or facility upgrade applied in certification capacityyear String (YYYY) The Reserve Capacity Year action String Either "SUBMIT" for submission or "CANCEL" for cancel. declaration Element This element must not exist when action=cancel capacityblock String Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 auctionmw Number The amount of capacity to be traded in the auction. Clause of the WEM Rules (a) specialpricemw Number Total amount of Special Price Arrangement MW that is not being traded bilaterally. Clause of the WEM Rules (b) bilateralmw Number Amount of capacity being traded bilaterally. Clause of the WEM Rules (c) unavailablemw Number Amount of capacity unavailable for the year. Clause of the WEM Rules (d) AEMO - WEMS Submission Specifications v5.0 45

46 Sample (Variation) <rcbilateraldeclarationsubmission> <resourcesubmission facilityname="facility_test_01" capacityyear="2015" action="submit"> <declaration auctionmw="11.500" bilateralmw="2.600" capacityblock="block2" specialpricemw="0.000" unavailablemw="2.500" /> </resourcesubmission> </rcbilateraldeclarationsubmission> Sample (Variation cancellation) <rcbilateraldeclarationsubmission> <resourcesubmission facilityname="facility_test_01" capacityyear="2005" action="cancel" </resourcesubmission> </rcbilateraldeclarationsubmission> 9.2 CSV Format FIELD NAME TYPE CONSTRAINTS COMMENTS capacity_year String (YYYY) The Reserve Capacity Year action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) capacity_block String (except for action "CANCEL" when it must be omitted) auction_mw Number (except for action "CANCEL" when it must be omitted) special_price_mw Number (except for action "CANCEL" when it must be omitted) bilateral_mw Number (except for action "CANCEL" when it must be omitted) unavailable_mw Number (except for action "CANCEL" when it must be omitted) Structure is as follows: Field Group Submission Declaration Fields capacity_year, action, facility_name capacity_block, auction_mw, special_price_mw, bilateral_mw, unavailable_mw The name of the facility or facility upgrade applied in certification Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 The amount of capacity to be traded in the auction. Clause of the WEM Rules (a) Total amount of Special Price Arrangement MW that is not being traded bilaterally. Clause of the WEM Rules (b) Amount of capacity being traded bilaterally. Clause of the WEM Rules (c) Amount of capacity unavailable for the year. Clause of the WEM Rules (d) All capacity details for a facility must contain the same values in the submission section, as specified in the fields column above (i.e. trading_date, action, facility_name and facility_type fields). Sample (Variation) AEMO - WEMS Submission Specifications v5.0 46

47 capacity_year,action,facility_name,capacity_block,auction_mw,special_price_mw,bilateral_mw,unav ailable_mw 2011,submit,TESTGEN,BLOCK1,12.500,0,000,72.600,8.500 Sample (Variation cancellation) capacity_year,action,facility_name,capacity_block,auction_mw,special_price_mw,bilateral_mw,unav ailable_mw 2011,cancel,TESTGEN1,,,,,,, Note: Cancel submissions must specify a facility name in the submission. AEMO - WEMS Submission Specifications v5.0 47

48 10. RESERVE CAPACITY AUCTION OFFERS DATA SUBMISSIONS 10.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a reserve capacity auction offers data submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX resv_cap_offer ResvCapOfferSubmit 1 1 offer Offer 0 1 Attribute details are shown for each element that comprises a reserve capacity auction offers data submission. Resv_cap_offer Element facility_name String (2 to 32 characters) The name of the facility Clause of the WEM Rules (a) & (b) facility_type String The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD Clause of the WEM Rules (a) & (b) version_no String. Must be set to 1.0 offer Element capacity_block String Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 Clause of the WEM Rules (b) availability_class String Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 Clause of the WEM Rules (b) price Number Reserve Capacity offer price Clause of the WEM Rules (c) & (d) quantity_mw Number Reserve Capacity in MW Clause of the WEM Rules (c) & (d) AEMO - WEMS Submission Specifications v5.0 48

49 Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit application_type="resv_cap_offer" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_offer facility_name="testgen1" facility_type="sched_gen" version_no="1.0"> <offer capacity_block="block1" availability_class="class1" price="25.87" quantity_mw="28.239"> </offer> </resv_cap_offer> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel application_type="resv_cap_offer" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_offer facility_name="testgen1" version_no="1.0"> </resv_cap_offer> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query application_type="resv_cap_offer" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <resv_cap_offer facility_name="testgen1" version_no="1.0"> </resv_cap_offer> </market_query> </bids_offers> AEMO - WEMS Submission Specifications v5.0 49

50 10.2 CSV Format FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the reserve capacity certification data submission. Trading date should be the first day of the trading month action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) facility_type String (except for action "CANCEL" when it must be omitted) capacity_block String (except for action "CANCEL" when it must be omitted) availability_class String (except for action "CANCEL" when it must be omitted) price Number (except for action "CANCEL" when it must be omitted) quantity_mw Number (except for action "CANCEL" when it must be omitted) The name of the facility Clause of the WEM Rules (a) & (b) The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD Clause of the WEM Rules (a) & (b) Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 Clause of the WEM Rules (b) Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 Clause of the WEM Rules (b) Reserve Capacity offer price Clause of the WEM Rules (c) & (d) Reserve Capacity in MW Clause of the WEM Rules (c) & (d) Structure is as follows Field Group Submission Offer Fields trading_date, action, facility_name, facility_type capacity_block, availability_class, price, quantity_mw All capacity details for a facility must contain the same values in the submission section, as specified in the fields column above (i.e. trading_date, action, facility_name and facility_type fields). Sample (Variation) trading_date,action,facility_name,facility_type,capacity_block,availability_class,price,quantit y_mw 24/12/2011,submit,TESTGEN1,SCHED_GEN,BLOCK1,CLASS1,22.500, Sample (Variation cancellation) trading_date,action,facility_name,facility_type,capacity_block,availability_class,price,quantit y_mw 24/12/2011,cancel,TESTGEN1,,,,, Note: Cancel submissions where a facility name isn t specified in the submission cancels the reserve capacity auction offers data submission for all facilities. AEMO - WEMS Submission Specifications v5.0 50

51 11. LONG TERM SPA SUBMISSIONS 11.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a long term SPA submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX long_term_spa LongTermSpaSubmit 1 Unlimited Attribute details are shown for each element that comprises a long term SPA submission. long_term_spa Element facility_name String (2 to 32 characters) The name of the facility facility_type String The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD auction_year Number The Reserve Capacity year start_date end_date (YYYY-MM-DD) (YYYY-MM-DD) Start date of the Special Price Arrangement Clause of the WEM Rules (b) End date of the Special Price Arrangement Clause of the WEM Rules (b) capacity_block String Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 Clause of the WEM Rules (a) availability_class String Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 Clause of the WEM Rules (a) capacity_credits Number The amount of capacity to be traded in the auction Clause of the WEM Rules (a) version_no String. Must be set to 1.0 AEMO - WEMS Submission Specifications v5.0 51

52 Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit application_type="long_term_spa" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <long_term_spa facility_name="testgen1" facility_type="sched_gen" auction_year="2012" start_date=" " end_date=" " capacity_block="block1" availability_class="class1" capacity_credits="65" version_no="1.0"> </long_term_spa> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd "> <market_cancel application_type="long_term_spa" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <long_term_spa facility_name="testgen2" auction_year="2011" version_no="1.0"> </long_term_spa> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query application_type="long_term_spa" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <long_term_spa facility_name="testgen2" auction_year="2011" version_no="1.0"> </long_term_spa> </market_query> </bids_offers> 11.2 CSV Format FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the reserve capacity certification data submission. Trading date should be the first day of the trading month action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) facility_type String (except for action "CANCEL" when it must be omitted) The name of the facility The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD auction_year Number The Reserve Capacity year AEMO - WEMS Submission Specifications v5.0 52

53 FIELD NAME TYPE CONSTRAINTS COMMENTS start_date end_date (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) capacity_block String (except for action "CANCEL" when it must be omitted) availability_class String (except for action "CANCEL" when it must be omitted) capacity_credits Number (except for action "CANCEL" when it must be omitted) Start date of the Special Price Arrangement Clause of the WEM Rules (b) End date of the Special Price Arrangement Clause of the WEM Rules (b) Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 Clause of the WEM Rules (a) Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 Clause of the WEM Rules (a) The amount of capacity to be traded in the auction Clause of the WEM Rules (a) Structure is as follows: Field Group Submission Offer Fields trading_date, action, facility_name, facility_type auction_year, start_date, end_date, capacity_block, availability_class, capacity credits All details for a facility must contain the same values in the submission section, as specified in the Fields column above (i.e. trading_date, action, facility_name and facility_type fields). Sample (Variation) trading_date,action,facility_name,facility_type,auction_year,start_date,end_date,capacity_block,availability_class,capacity_credits 24/12/2011,submit,TESTGEN1,SCHED_GEN,2012,01/02/2012,25/03/2012,BLOCK1,CLASS1, Sample (Variation cancellation) trading_date,action,facility_name,facility_type,auction_year,start_date,end_date,capacity_block,availability_class,capacity_credits 24/12/2011,cancel,TESTGEN1,2012,,,,,, Note: Cancel submissions where a facility name isn t specified in the submission cancels the long term SPA submission for all facilities. AEMO - WEMS Submission Specifications v5.0 53

54 12. CAPACITY CREDITS AND OBLIGATIONS SUBMISSIONS 12.1 XML Format The xml format is specified by mint.xsd. The following table contains the details of the nesting structure of elements that comprise a capacity credits and obligations submission, and the number of times that each element can occur within the context of its parent element. ELEMENT MINT.XSD TYPE MIN MAX capacity_credits CapacityCreditsSubmit 1 Unlimited Attribute details are shown for each element that comprises a capacity credits and obligations submission. Capacity_credits Element facility_name String (2 to 32 characters) The name of the facility facility_type String The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD start_date (YYYY-MM-DD) Capacity credits start date alt_facility_name String Optional Original facility name which it used when it was first certified capacity_block String Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 availability_class String Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 capacity_credits_total Number Total number of capacity credits Clause of the WEM Rules (a) capacity_credits_imo Number Total number of capacity credits anticipated from the AEMO Clause of the WEM Rules (b) version_no String. Must be set to 1.0 AEMO - WEMS Submission Specifications v5.0 54

55 Sample (Variation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_submit application_type="capacity_credits" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <capacity_credits facility_name="testgen1" facility_type="sched_gen" start_date=" " alt_facility_name="testgen35" capacity_block="block1" availability_class= CLASS1 capacity_credits_total="88.000" capacity_credits_imo="11.500" version_no="1.0"> </capacity_credits> </market_submit> </bids_offers> Sample (Variation cancellation) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_cancel application_type="capacity_credits" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <capacity_credits facility_name="testgen2" version_no="1.0"> </capacity_credits> </market_cancel> </bids_offers> Sample (Query) <?xml version="1.0" encoding="utf-8"?> <bids_offers xmlns:xsi=" xsi:nonamespaceschemalocation="mint.xsd"> <market_query application_type="capacity_credits" trading_date=" " participant_name="testcon1" user_name="testuser" mode="normal"> <capacity_credits facility_name="testgen2" version_no="1.0"> </capacity_credits> </market_query> </bids_offers> 12.2 CSV Format FIELD NAME TYPE CONSTRAINTS COMMENTS trading_date The trading date of the reserve capacity certification data submission. Trading date should be the first day of the trading month action String Either "SUBMIT" for submission, or "CANCEL" for cancel. facility_name String (2 to 32 characters) (can be omitted if cancelling all facilities) facility_type String (except for action "CANCEL" when it must be omitted) start_date (except for action "CANCEL" when it must be omitted) The name of the facility The facility types are: SCHED_GEN, NON_SCHED_GEN, INTMNT_GEN, DISP_LOAD, CURT_LOAD, INTRPT_LOAD, INTMNT_NON_DISP_LOAD, INTMNT_CURT_LOAD, INTMNT_INTRPT_LOAD Capacity credits start date AEMO - WEMS Submission Specifications v5.0 55

56 FIELD NAME TYPE CONSTRAINTS COMMENTS alt_facility_name String Optional Original facility name which it used when it was first certified capacity_block String (except for action "CANCEL" when it must be omitted) availability_class String (except for action "CANCEL" when it must be omitted) capacity_credits_total Number (except for action "CANCEL" when it must be omitted) capacity_credits_imo Number (except for action "CANCEL" when it must be omitted) Specifies the capacity block. Must be BLOCK1, BLOCK2 or BLOCK3 Specifies the capacity class. Must be CLASS1, CLASS2, CLASS3 or CLASS4 Total number of capacity credits Clause of the WEM Rules (a) Total number of capacity credits anticipated from the AEMO Clause of the WEM Rules (b) Structure is as follows: Field Group Submission Offer Fields trading_date, action, facility_name, facility_type start_date, alt_facility_name, capacity_block, availability_class, capacity credits_total, capacity_credits_imo All details for a facility must contain the same values in the submission section, as specified in the fields column above (i.e. trading_date, action, facility_name and facility_type fields). Sample (Variation) trading_date,action,facility_name,facility_type,start_date,alt_facility_name,capacity_block,ava ilability_class,capacity_credits_total,capacity_credits_imo 24/12/2011,submit,TESTGEN1,SCHED_GEN,21/11/2011,,BLOCK1,CLASS1,88.000, Sample (Variation cancellation) trading_date,action,facility_name,facility_type,start_date,alt_facility_name,capacity_block,ava ilability_class,capacity_credits_total,capacity_credits_imo 24/12/2011,cancel,TESTGEN1,,,,,,, Note: Cancel submissions where a facility name isn t specified in the submission cancels the capacity credits and obligations submission for all facilities. AEMO - WEMS Submission Specifications v5.0 56

57 13. BALANCING VARIATION SUBMISSIONS Balancing variation submissions allow participants to provide their available capacity for Balancing and also declare some or all of their capacity as unavailable. Participants are also able to cancel all Balancing variation submissions for an individual trading interval, or a range of trading intervals. Note that the cancel function will not remove any Balancing standing submissions XML Format The xml format is specified by wems-1.0.xsd. The following table contains the details of the nesting structure of elements that comprise a Balancing variation submission, and the number of times that each element can occur within the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX balancingvariationsubmission balancingvariationsubmissiontype 1 Unlimited resourcesubmission variationsupplycurveresourcesubmissiontype 1 Unlimited supplycurve variationsupplycurvetype 1 48 tranche tranchetype 0 35 BalancingVariationSubmissions Element The balancingvariationsubmissions element is the root element of the document and has no attributes. It contains resourcesubmission elements. ResourceSubmission Element resourcename resourcename The name of the Balancing resource (the facility name or Portfolio for Synergy PSC) trading (YYYY-MM-DD) action action The action types are: "SUBMIT" "CANCEL" The trading date on which the submissions apply SupplyCurve Element starthour (0 to 23) The hour within the delivery date that the capacity is effective from. startinterval (1 to 2) The interval within the hour that the capacity is effective from. endhour (0 to 23) The hour within the delivery date that the capacity is effective to. endinterval (1 to 2) The interval within the hour that the capacity is effective to. unavailable megawattquantity Optional The unavailable capacity of the resource for the interval range in Megawatts (MW). Defaults to 0 if the attribute is not present. AEMO - WEMS Submission Specifications v5.0 57

58 Tranche Element The tranche element is not required for a cancellation price balancingpricetype Tranche Price, in $/MWh OR the STRING MIN or MAX. Note that MIN and MAX will use the latest min and max Balancing prices for the submission for the particular fuel type. quantity balancingmegawattquantity Tranche Size in MW OR the STRING RPQTY or MAXCAP_MINUS_RPQTY. Note that RPQTY will use the last valid Resource Plan MW Quantity level and MAXCAP_MINUS_RPQTY will use the sent out maximum capacity of the facility as recorded in registration (irrespective of fuel type) minus RPQTY. (Note if used in conjunction with ancillarypurpose, this is the amount of MW required to be cleared to enable the respective services i.e. LFAS). Values are sent out MW (not loss adjusted). maxramp ramprate The maximum rate at which the resource can change its output level in MW/minute fueltype fueltype Generation fuel type: NON_LIQUID Non-Liquid LIQUID Liquid All other values are invalid. ancillarypurpose ancillarypurpose Optional Notification that the submission must be cleared to allow resource to provide Ancillary Services. For IPPs (other than Synergy SAF): LFAS Load Following For Synergy SAF: OTHER Other Ancillary Services LFAS Load Following For Synergy Portfolio: OTHER Ancillary Services LFAS Load Following Note that all Ancillary Service quantities must be submitted at either the Minimum STEM price cap or the Alternative Maximum STEM price cap. Commissioning Tests: The field is also be used to declare plant undergoing commissioning testing. In such cases, the following shall be entered in this field: COMTEST No trading interval ranges can overlap within a file submission for a given resource. All tranches for an interval for a specific resource must have the same maxramp value. All variation cancel submissions must contain only the ResourceSubmission and SupplyCurve elements (i.e. no Tranche elements) AEMO - WEMS Submission Specifications v5.0 58

59 Sample (Variation) <?xml version="1.0"?> <balancingvariationsubmission> <resourcesubmission resourcename="testgen1" trading=" " action="submit"> <supplycurve starthour="14" startinterval="1" endhour="14" endinterval="1" unavailable="30"> <tranche price="max" quantity="100" maxramp="2" fueltype="non_liquid" ancillarypurpose="lfas" /> <tranche price="max" quantity="100" maxramp="2" fueltype="non_liquid" ancillarypurpose="other" /> </supplycurve> <supplycurve starthour="14" startinterval="2" endhour="14" endinterval="2"> <tranche price="200" quantity="250" maxramp="2" fueltype="non_liquid" /> <tranche price="100" quantity="350" maxramp="2" fueltype="non_liquid" /> </supplycurve> </resourcesubmission> <resourcesubmission resourcename="testgen2" trading=" " action="submit"> <supplycurve starthour="14" startinterval="2" endhour="14" endinterval="2"> <tranche price="200" quantity="250" maxramp="2" fueltype="non_liquid" /> <tranche price="100" quantity="350" maxramp="2" fueltype="non_liquid" /> </supplycurve> </resourcesubmission> </balancingvariationsubmission> Sample (Variation cancellation) <?xml version="1.0"?> <balancingvariationsubmission> <resourcesubmission resourcename="testgen1" trading=" " action="cancel"> <supplycurve starthour="14" startinterval="1" endhour="14" endinterval="1"> </supplycurve> </resourcesubmission> </balancingvariationsubmission> 13.2 CSV Format Balancing variation submissions in CSV format comprise a single CSV file. Note that only submit and cancel actions are permitted. Multiple submissions for the same facility for the same trading interval are allowed in a single CSV file, however a warning is issued to advise of potential errors. Note: When action is "CANCEL", only resource_name and trading date/time fields are required to be populated. FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. resource_name String The name of the Balancing resource (the facility name or Portfolio for Synergy PSC) trading_date start_hour start_interval end_hour (0 to 23) (1 to 2) (0 to 23) The trading date on which the submissions apply. The hour within the trading date that the capacity is effective from. The interval within the hour that the capacity is effective from. The hour within the trading date that the capacity is effective to. AEMO - WEMS Submission Specifications v5.0 59

60 FIELD NAME TYPE CONSTRAINTS COMMENTS end_interval (1 to 2) submission_type String (except for action "CANCEL" when it must be omitted) The interval within the end hour that the capacity is effective to. Submission identifier: BAL Balancing Submission UNAV Unavailable declaration (full or partial outage) All other values are invalid price String Optional Tranche Price, in $/MWh OR the STRING MIN or MAX. Note that MIN and MAX will use the latest min and max Balancing prices for the submission for the particular fuel type. quantity String Optional For Balancing: Tranche Size in MW OR the STRING RPQTY or MAXCAP_MINUS_RPQTY. Note that RPQTY will use the last valid Resource Plan MW Quantity level and MAXCAP_MINUS_RPQTY will use the sent out maximum capacity of the facility as recorded in registration (irrespective of fuel type) minus RPQTY. (Note if used in conjunction with ancillary_purpose, this is the amount of MW required to be cleared to enable the respective services i.e. LFAS) Values are sent out MW (not loss adjusted). For Unavailability: Unavailable amount to be excluded from Balancing in MW Values are sent out MW (not loss adjusted). max_ramp Number Optional The maximum rate at which the resource can change its output level in MW/minute fuel_type String Optional Generation fuel type: NON_LIQUID Non-Liquid LIQUID - Liquid All other values are invalid AEMO - WEMS Submission Specifications v5.0 60

61 FIELD NAME TYPE CONSTRAINTS COMMENTS ancillary_purpose String Optional Notification that the submission must be cleared to allow resource to provide Ancillary Services. For IPPs (other than VSAF): LFAS Load Following For VSAF: OTHER Other Ancillary Services LFAS Load Following For Synergy Portfolio: OTHER Other Ancillary Services LFAS Load Following Note that all Ancillary Service quantities must be submitted at either the Minimum STEM price cap or the Alternative Maximum STEM price cap Commissioning Tests: The field is also be used to declare plant undergoing commissioning testing. In such cases, the following shall be entered in this field: COMTEST All tranches submitted for a trading interval (or intervals) for a specific resource must have the same values in the action, resource_name, start_hour, start_interval, end_hour and end_interval fields. No trading interval ranges can overlap within a file submission for a given resource. All cancel submissions must not provide submission_type, price, quantity, max_ramp, fuel_type and ancillary_purpose values. A cancel submission cancels all Balancing and Unavailability submissions for the date range provided. All tranches for an interval for a specific resource must have the same max_ramp value. AEMO - WEMS Submission Specifications v5.0 61

62 Sample (Variation) action,resource_name,trading_date,start_hour,start_interval,end_hour,end_interval,submission_ty pe,price,quantity,max_ramp,fuel_type,ancillary_purpose SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,10,5,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,20,10,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,40,20,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,50,5,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,9,1,9,2,BAL,39.95,15,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,9,1,9,2,BAL,49,95,25,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,MIN,10,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,50,5,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,100,5,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,MAX,20,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,0,1,7,2,BAL,100,10,5,LIQUID, SUBMIT,resource1,24/03/2011,0,1,7,2,BAL,MAX,30,5,LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,MIN,12,1,NON_LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,100,28,1,NON_LIQUID, SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,-200,25,1,NON_LIQUID,LFAS SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,-100,25,1,NON_LIQUID,LFAS SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,-10,50,1,NON_LIQUID,LFAS SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,10,150,1,NON_LIQUID,LFAS SUBMIT,resource3,25/03/2011,8,1,7,2,UNAV,,100,,,, Sample (Variation cancellation) action,resource_name,trading_date,start_hour,start_interval,end_hour,end_interval,submission_ty pe,price,quantity,max_ramp,fuel_type,ancillary_purpose CANCEL,resource1,24/03/2011,8,1,13,2,,,,,, AEMO - WEMS Submission Specifications v5.0 62

63 14. BALANCING STANDING SUBMISSIONS Standing Balancing submissions allow participants to provide their capacity for Balancing and standing declaration of plant unavailability for use whenever variation submissions are not present. Participants are also able to cancel all Balancing (standing and variation) submissions from the start of a trading day, for all future trading days XML Format The xml format is specified by wems-1.0.xsd. The following table contains the details of the nesting structure of elements that comprise a standing Balancing submission, and the number of times that each element can occur within the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX balancingstandingsubmission balancingstandingsubmission 0 Unlimited resourcesubmission standingresourcesubmission 1 Unlimited supplycurve supplycurve 0 48 tranche tranche 0 35 BalancingStandingSubmissions Element The balancingstandingsubmissions element is the root element of the document and has no attributes. It contains resourcesubmission elements. ResourceSubmission Element resourcename resourcename The name of the Balancing resource (the facility name or Portfolio for Synergy PSC) effectivetrading (YYYY-MM-DD) The trading date from which the standing submission applies action action The action types are: "SUBMIT" "CANCEL" Note that a "CANCEL" action will cancel Balancing standing and variation submissions from an effective Trading Interval. SupplyCurve Element The SupplyCurve element is not required for a cancellation starthour startinterval endhour endinterval (0 to 23) (1 to 2) (0 to 23) (1 to 2) The hour within trading day that the capacity is effective from. The interval within the hour that the capacity is effective from. The hour within the trading day that the capacity is effective to. The interval within the hour that the capacity is effective to. unavailable megawattquantity Optional The unavailable capacity of the resource for the interval range in Megawatts (MW). Defaults to 0 if the attribute is not present. AEMO - WEMS Submission Specifications v5.0 63

64 Tranche Element The tranche element is not required for a cancellation price balancingpricetype Tranche Price, in $/MWh OR the STRING MIN or MAX. Note that MIN and MAX will use the latest min and max Balancing prices for the submission for the particular fuel type. quantity balancingmegawattquantity Tranche Size in MW OR the STRING RPQTY or MAXCAP_MINUS_RPQTY. Note that RPQTY will use the last valid Resource Plan MW Quantity level and MAXCAP_MINUS_RPQTY will use the sent out maximum capacity of the facility as recorded in registration (irrespective of fuel type) minus RPQTY. (Note if used in conjunction with ancillarypurpose, this is the amount of MW required to be cleared to enable the respective services i.e. LFAS). Values are sent out MW (not loss adjusted). maxramp ramprate The maximum rate at which the resource can change its output level in MW/minute fueltype fueltype Generation fuel type: NON_LIQUID Non-Liquid LIQUID - Liquid All other values are invalid ancillarypurpose ancillarypurpose Optional Notification that the submission must be cleared to allow resource to provide Ancillary Services. For IPPs (other than Synergy SAF): LFAS Load Following For Synergy SAF: OTHER Other Ancillary Services LFAS Load Following For Synergy Portfolio: OTHER Other Ancillary Services LFAS Load Following Note that all Ancillary Service quantities must be submitted at either the Minimum STEM price cap or the Alternative Maximum STEM price cap. Commissioning Tests: The field is also be used to declare plant undergoing commissioning testing. In such cases, the following shall be entered in this field: COMTEST All standing cancel submissions must contain only the ResourceSubmission element (i.e. only attributes: resourcename, effectivetrading, action) Each standing submission must contain a complete submission covering each trading interval within a trading day, in order for the submission to be valid. All tranches for an interval for a specific resource must have the same maxramp value. No trading interval ranges can overlap within a file submission for a given resource. AEMO - WEMS Submission Specifications v5.0 64

65 Sample (Standing) <?xml version="1.0"?> <balancingstandingsubmission> <resourcesubmission resourcename="testgen1" effectivetrading=" " action="submit"> <supplycurve starthour="8" startinterval="1" endhour="7" endinterval="2"> <tranche price="max" quantity="100" maxramp="2" fueltype="non_liquid" /> <tranche price="max" quantity="100" maxramp="2" fueltype="non_liquid" ancillarypurpose="lfas" /> </supplycurve> </resourcesubmission> </balancingstandingsubmission> Sample (Standing cancellation) <?xml version="1.0"?> <balancingstandingsubmission> <resourcesubmission resourcename="testgen1" effectivetrading=" " action="cancel"> </resourcesubmission> </balancingstandingsubmission> 14.2 CSV Format Standing Balancing submissions in CSV format comprise a single CSV file. Note that only submit and cancel actions are permitted. Note: When action is "CANCEL", only resource_name and effective_trading_date fields are required to be populated. FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. resource_name String The name of the Balancing resource (the facility name or Portfolio for Synergy PSC) effective_trading_ date start_hour start_interval end_hour end_interval (DD/MM/YY YY) (0 to 23) (1 to 2) (0 to 23) (1 to 2) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) (except for action "CANCEL" when it must be omitted) The trading date from which the standing submission applies The hour within the delivery date that the capacity is effective from. The interval within the hour that the capacity is effective from. The hour within the delivery date that the capacity is effective to. The hour within the delivery date that the capacity is effective to. AEMO - WEMS Submission Specifications v5.0 65

66 FIELD NAME TYPE CONSTRAINTS COMMENTS submission_type String (except for action "CANCEL" when it must be omitted) Submission identifier: BAL Balancing Submission UNAV Unavailable declaration (full or partial outage) All other values are invalid price String Optional Tranche Price, in $/MWh OR the STRING MIN or MAX. Note that MIN and MAX will use the latest min and max Balancing prices for the submission for the particular fuel type. quantity String Optional For Balancing: Tranche Size in MW OR the STRING RPQTY or MAXCAP_MINUS_RPQTY. Note that RPQTY will use the last valid Resource Plan MW Quantity level and MAXCAP_MINUS_RPQTY will use the sent out maximum capacity of the facility as recorded in registration (irrespective of fuel type) minus RPQTY. (Note if used in conjunction with ancillary_purpose, this is the amount of MW required to be cleared to enable the respective services i.e. LFAS) Values are sent out MW (not loss adjusted). For Unavailability: Unavailable amount to be excluded from Balancing in MW. Values are sent out MW (not loss adjusted). max_ramp Number Optional The maximum rate at which the resource can change its output level in MW/minute. fuel_type String Optional Generation fuel type: NON_LIQUID Non-Liquid LIQUID - Liquid All other values are invalid. ancillary_purpose String Optional Notification that the submission must be cleared to allow resource to provide Ancillary Services. For IPPs (other than Synergy SAF): LFAS Load Following For VSAF: OTHER Other Ancillary Service LFAS Load Following For Synergy Portfolio: OTHER Other Ancillary Service LFAS Load Following Note that all Ancillary Service quantities must be submitted at either the Minimum STEM price cap or the Alternative Maximum STEM price cap. Commissioning Tests: The field is also be used to declare plant undergoing commissioning testing. In such cases, the following shall be entered in this field: COMTEST All tranches submitted for a trading interval (or intervals) for a specific resource must have the same values in the action, resource_name, effective_date, start_hour, start_interval, end_hour and end_interval fields. AEMO - WEMS Submission Specifications v5.0 66

67 No trading interval ranges can overlap within a file submission for a given resource. All cancel submissions must not provide start_hour, start_interval, end_hour, end_interval, submission_type, price, quantity, max_ramp, fuel_type and ancillary_purpose. A cancel submission cancels all Balancing and Unavailability standing and variation submissions from the start of the effective_trading_date provided. All tranches for an interval for a specific resource must have the same max_ramp value. Sample (Standing) action,resource_name,effective_trading_date,start_hour,start_interval,end_hour,end_interval,sub mission_type,price,quantity,max_ramp,fuel_type,ancillary_purpose SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,50,20,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,8,1,8,2,BAL,100,20,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,9,1,9,2,BAL,10,15,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,9,1,9,2,BAL,50,25,1,NON_LIQUID,OTHER SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,MIN,10,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,10,1,10,2,BAL,50,30,1,NON_LIQUID, SUBMIT,resource1,24/03/2011,0,1,7,2,BAL,50,5,3,LIQUID, SUBMIT,resource1,24/03/2011,0,1,7,2,BAL,150,35,3,LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,MIN,5,1,NON_LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,-100,5,1,NON_LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,50,10,1,NON_LIQUID, SUBMIT,resource1,25/03/2011,8,1,8,1,BAL,100,20,1,NON_LIQUID, SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,-25,20,2,NON_LIQUID,OTHER SUBMIT,resource2,25/03/2011,8,1,8,1,BAL,50,180,2,NON_LIQUID,OTHER SUBMIT,resource3,25/03/2011,8,1,7,2,UNAV,,100,,,, Sample (Standing cancellation) action,resource_name,effective_trading_date,start_hour,start_interval,end_hour,end_interval,sub mission_type,price,quantity,max_ramp,fuel_type,ancillary_purpose CANCEL,resource1,24/03/2011,,,,,,,,,, AEMO - WEMS Submission Specifications v5.0 67

68 15. LOAD FOLLOWING VARIATION SUBMISSION The Load Following variation submission allows participants to submit prices and quantities for use in the Load Following auction that determines which participants are selected to provide the Load Following service. Participants are also able to cancel all Load Following variation submissions for an individual trading interval, or a range of trading intervals. Note that the cancel function will not remove any Load Following standing submissions. Each submission is full and complete. Any update via a Load Following variation submission for an interval will overwrite any previous Load Following submissions for the same type. For example if an interval previously had both LFAS_UP and LFAS_DN types submitted, then when a new submission is received for only LFAS_UP, the effective submission would comprise of the LFAS_DN of the first submission and the LFAS_UP of the second submission XML Format The xml format is specified by wems-1.0.xsd. The following table contains the elements that comprise the Load Following variation submission together with the minimum and maximum occurrences of each element in the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX loadfollowingvariationsubmission loadfollowingvariationsubmission 1 1 resourcesubmission variationloadfollowingresourcesubmission 1 Unlimited offer loadfollowingoffer 1 Unlimited band loadfollowingband 0 Unlimited LoadFollowingVariationSubmission Element The loadfollowingvariationsubmission element has no attributes. It is the root element that contains resourcesubmission elements. ResourceSubmission Element resourcename resourcename The name of the LFAS resource (the facility name or Portfolio for Synergy PSC) trading (YYYY-MM-DD) action action The action types are: "SUBMIT" "CANCEL" The trading date on which the submission applies AEMO - WEMS Submission Specifications v5.0 68

69 Offer Element type loadfollowingoffertype The type of submission LFAS_UP A Load Following offer up LFAS_DN A Load Following offer down BACKUP_LFAS_UP backup Load Following offer up BACKUP_LFAS_DN backup Load Following offer down CANCEL Cancellation of all Load Following variation submissions for the interval range. starthour startinterval endhour endinterval (0 to 23) (1 to 2) (0 to 23) (1 to 2) The hour within the delivery date that the submission is effective from. The interval within the hour that the submission is effective from. The hour within the delivery date that the submission is effective to. The interval within the hour that the submission is effective to. Band Element (Not for Cancel) price megawattprice The enablement price offered for the band in $/MW. size megawattquantity Optional The amount of Load Following capacity offered for the band in MW. All size values are positive. (Must not be included for BACKUP_LFAS_UP or BACKUP_LFAS_DN) No trading interval ranges can overlap within a file submission for a given resource. All variation cancel submissions must contain only the ResourceSubmission and Offer elements (i.e. no Band elements) Sample (Variation) <loadfollowingvariationsubmission> <resourcesubmission resourcename="test1" trading=" " action="submit"> <offer type="lfas_up" starthour="10" startinterval="1" endhour="10" endinterval="2"> <band size="15" price="350"/> </offer> <offer type="lfas_dn" starthour="10" startinterval="1" endhour="10" endinterval="2"> <band size="25" price="270"/> </offer> </resourcesubmission> </loadfollowingvariationsubmission> Sample (Variation cancellation) <loadfollowingvariationsubmission> <resourcesubmission resourcename="test1" trading=" " action="cancel"> <offer type="cancel" starthour="10" startinterval="1" endhour="10" endinterval="2"> </offer> </resourcesubmission> </loadfollowingvariationsubmission> AEMO - WEMS Submission Specifications v5.0 69

70 15.2 CSV Format Load following variation submissions in CSV format comprise a single CSV file. Note that only submit and cancel actions are permitted. Multiple submissions for the same facility for the same trading interval will be allowed in a single CSV file, however a warning will be issued to advise of potential errors. Note: When the action type is "CANCEL", only resource_name and trading date/time fields are required to be populated. FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. resource_name String The name of the LFAS resource (the facility name or Portfolio for Synergy PSC) trading_date start_hour start_interval end_hour end_interval (0 to 23) (1 to 2) (0 to 23) (1 to 2) type String (except for action "CANCEL" when it must be omitted) The trading date on which the submission applies The hour within the delivery date that the submission is effective from. The interval within the hour that the submission is effective from. The hour within the delivery date that the submission is effective to. The interval within the hour that the submission is effective to. The type of submission LFAS_UP A Load Following offer up LFAS_DN A Load Following offer down BACKUP_LFAS_UP backup Load Following offer up BACKUP_LFAS_DN backup Load Following offer down price Number Optional The enablement price offered for the band in $/MW. size Number Optional The amount of Load Following capacity offered for the band in MW. All size values are positive. Must be omitted for BACKUP submissions. All LFAS bands submitted for a trading interval (or interval range) for a specific resource must contain the same values for action, resource_name, start_hour, start_interval, end_hour, end_interval and type. No trading interval ranges can overlap within a file submission for a given resource. All cancel submissions must not provide type, price and size values. A cancel submission cancels all variation LFAS submissions for the date range provided. All tranches for an interval must have the same ramp rate. Sample (Variation) action,resource_name, trading_date, start_hour, start_interval, end_hour, end_interval, type,price,size SUBMIT,TEST1,18/07/2011,8,1,12,2,LFAS_UP,270,20 SUBMIT,TEST1,18/07/2011,8,1,12,2,LFAS_DN,300,20 AEMO - WEMS Submission Specifications v5.0 70

71 Sample (Variation cancellation) action,resource_name, trading_date, start_hour, start_interval, end_hour, end_interval, type,price,size CANCEL,TEST1,18/07/2011,5,1,13,2,,, AEMO - WEMS Submission Specifications v5.0 71

72 16. LOAD FOLLOWING STANDING SUBMISSION Standing Load Following submissions allow participants to provide price and quantities that will be used in the Load Following auction to determine which participants are selected to provide Load Following. Participants are also able to cancel all Load Following (standing and variation) submissions from an individual trading interval, for all future trading intervals. Standing LFAS submissions are not mandatory, however if present, these will apply when there are no variation LFAS submissions applicable for a trading interval. Any update to a standing Load Following submission for an interval will overwrite any previous standing Load Following submissions for the same type for that trading interval. For example if an interval previously had both LFAS_UP and LFAS_DN types submitted, then when a new submission is received for only LFAS_UP, the effective submission would comprise of the LFAS_DN of the first submission and the LFAS_UP of the second submission XML Format The xml format is specified by wems-1.0.xsd. The following table contains the elements that comprise Load Following standing submissions together with the minimum and maximum occurrences of each element in the context of its parent element. ELEMENT WEMS-1.0.XSD TYPE MIN MAX loadfollowingstandingsubmission loadfollowingstandingsubmission 1 1 resourcesubmission standingloadfollowingresourcesubmission 0 Unlimited offer loadfollowingoffer 0 Unlimited band loadfollowingband 0 Unlimited LoadFollowingStandingSubmission Element The loadfollowingstandingsubmission element has no attributes. It is the root element that contains resourcesubmission elements. ResourceSubmission Element resourcename resourcename The name of the LFAS resource (the facility name or Portfolio for Synergy PSC) effectivetrading (YYYY-MM-DD) The trading date from which the standing Load Following submission applies. action action The action types are: "SUBMIT" "CANCEL" Note that a "CANCEL" action will cancel Load Following standing and variation submissions from the effective Trading. AEMO - WEMS Submission Specifications v5.0 72

73 Offer Element type loadfollowingoffertype The type of submission LFAS_UP A Load Following offer up LFAS_DN A Load Following offer down BACKUP_LFAS_UP backup Load Following offer up BACKUP_LFAS_DN backup Load Following offer down starthour startinterval endhour endinterval (0 to 23) (1 to 2) (0 to 23) (1 to 2) The hour within the delivery date that the submission is effective from. The interval within the hour that the submission is effective from. The hour within the delivery date that the submission is effective to. The interval within the hour that the submission is effective to Band Element This element is not required for a cancellation submission. price Number The enablement price offered for the band in $/MW size Number Optional The amount of Load Following capacity offered for the band in MW. All size values are positive. Must not be included for BACKUP_LFAS_UP and BACKUP_LFAS_DN. All standing cancel submissions must contain only the ResourceSubmission element (i.e. only attributes: resourcename, effectivetrading, action) No trading interval ranges can overlap within a file submission for a given resource. Sample (Standing) <loadfollowingstandingsubmission> <resourcesubmission resourcename="testgen1" effectivetrading=" " action="submit"> <offer type="lfas_up" starthour="10" startinterval="1" endhour="10" endinterval="2"> <band size="15" price="270"/> </offer> <offer type="lfas_dn" starthour="10" startinterval="1" endhour="10" endinterval="2"> <band size="25" price="350"/> </offer> </resourcesubmission> </loadfollowingstandingsubmission> Sample (Standing cancellation) <loadfollowingstandingsubmission> <resourcesubmission resourcename="testgen1" effectivetrading=" " action="cancel"> </resourcesubmission> </loadfollowingstandingsubmission> AEMO - WEMS Submission Specifications v5.0 73

74 16.2 CSV Format Standing Load Following submissions in CSV format comprise a single CSV file. Note that only submit and cancel actions are permitted. Note: When action is "CANCEL", only resource_name and effective_trading_date fields are required to be populated. FIELD NAME TYPE CONSTRAINTS COMMENTS action String Either "SUBMIT" for submission, or "CANCEL" for cancel. resource_name String The name of the generation resource (the facility name or Portfolio for Synergy PSC) effective_trading_date start_hour start_interval end_hour end_interval (0 to 23) (1 to 2) (0 to 23) (1 to 2) (except for action CANCEL when it must be omitted) (except for action CANCEL when it must be omitted) (except for action CANCEL when it must be omitted) (except for action CANCEL when it must be omitted) type String (except for action CANCEL when it must be omitted) The trading date on which the standing submission is effective from. The hour within the trading day that the submission is effective from. The interval within the hour that the submission is effective from. The hour within the trading day that the submission is effective to. The interval within the hour that the submission is effective to. The type of submission LFAS_UP A Load Following offer up LFAS_DN A Load Following offer down BACKUP_LFAS_UP backup Load Following offer up BACKUP_LFAS_DN backup Load Following offer down All other values are invalid price Number Optional The enablement price offered for the band in $/MW size Number Optional The amount of Load Following capacity offered for the band in MW. All size values are positive. Must be omitted for Backup submissions. All LFAS bands submitted for a trading interval (or interval range) for a specific resource must contain the same values for action, resource_name, start_hour, start_interval, end_hour, end_interval and type. No trading interval ranges can overlap within a file submission for a given resource. All cancel submissions must not provide start_hour, start_interval, end_hour, end_interval, type, price and size values. A cancel submission cancels all LFAS standing and variation submissions from the start of the effective_trading_date provided. AEMO - WEMS Submission Specifications v5.0 74

75 Sample (Standing) action,resource_name,effective_trading_date,start_hour,start_interval,end_hour,end_interval,typ e,price,size SUBMIT,TESTGEN1,18/07/2011,8,1,12,2,LFAS_UP,270,20 SUBMIT,TESTGEN1,18/07/2011,8,1,12,2,LFAS_DN,300,20 Sample (Standing cancellation) action,resource_name,effective_trading_date,start_hour,start_interval,end_hour,end_interval,typ e,price,size CANCEL,TESTGEN1,18/09/2011,,,,,,, AEMO - WEMS Submission Specifications v5.0 75

76 17. WEB SERVICES SUBMISSIONS BALANCING AND LFAS 17.1 Web Services Submissions Upload and Validate Web services submissions provide the same options and support the same exchange format as the MPI (File Exchange), so given an XML document for a submission, it can either be submitted manually via the MPI or programmatically via the appropriate web service. For each submission type the web service offers four options: upload<submission> e.g. uploadbalancingvariationsubmission This submits a Balancing variation to WEMS. validate<submission> e.g. validateloadfollowingstandingsubmission performs validation of the submission but does not submit any data. This is useful for testing during system development or fault-finding. upload<submission>documents e.g. uploadloadfollowingstandingsubmissiondocuments allows upload of a set of submissions. validate<submission>documents e.g validatebalancingvariationsubmissiondocuments allows validation of a set of submissions Allow Gate Closure Violation / Discard File on Error The submission message includes two boolean elements which are equivalent to the checkboxes of the same name in the MPI. Both elements are optional and omitting either from the request is equivalent to setting it 'false'. By setting Allow Gate Closure Violation to true, the system will accept the submission even if it is after gate closure. By setting Discard File on Error to true, the system will discard the entire submission if any tranche is in error. The normal behaviour (discardfileonerror=false) is for the system to accept all valid tranches and ignore the invalid ones. The element names and locations for these flags are described in the XSD for each submission and also in the examples in the following sections. Refer to the Balancing and Load Following Submissions - User Guide for more information on these fields. Note: for LFAS requests, the element is named Allow_Gate_Closure_Violation but for Balancing submissions it is named allow_gate_closure_violation. AEMO - WEMS Submission Specifications v5.0 76

77 17.3 Validation To validate a submission, the request should be created as follows. This example shows a BalancingVariationSubmission. <soapenv:envelope xmlns:soapenv=" xmlns:ns=" xmlns:ns1=" <soapenv:header/> <soapenv:body> <ns:validatebalancingvariationsubmission> <ns:submission_name>example Submission 123</ns:submission_name> <ns:submission_documents> <ns1:resourcesubmission resourcename="?" action="?" trading="?"> <ns1:supplycurve unavailable="0" starthour="?" startinterval="?" endhour="?" endinterval="?"> <ns1:tranche price="?" quantity="?" maxramp="?" fueltype="?" ancillarypurpose="?"/> </ns1:supplycurve> </ns1:resourcesubmission> </ns:submission_documents> <ns:allow_gate_closure_violation>false</ns:allow_gate_closure_violation> <ns:discard_file_on_error>true</ns:discard_file_on_error> </ns:validatebalancingvariationsubmission> </soapenv:body> </soapenv:envelope> To validate a set of submissions in a single request, the request should be created as follows: <soapenv:envelope xmlns:soapenv=" xmlns:ns=" <soapenv:header/> <soapenv:body> <ns:validatebalancingstandingsubmissiondocuments> <ns:submission_name>submission ABC</ns:submission_name> <ns:submission_documents> (INSERT ONE OR MORE DOCUMENTS HERE) </ns:submission_documents> <ns:discard_file_on_error>false</ns:discard_file_on_error> </ns:validatebalancingstandingsubmissiondocuments> </soapenv:body> </soapenv:envelope> 17.4 Upload To upload a submission via web services, the request (as defined in and should be of the form: <upload<type>submission> <submission_name>name</submission_name> <submission>... </submission> </discard_file_on_error>boolean</discard_file_on_error> </upload<type>submission> For example: <soapenv:envelope xmlns:soapenv=" xmlns:ns=" xmlns:ns1=" <soapenv:header/> <soapenv:body> <ns:uploadbalancingstandingsubmission> <ns:submission_name>submission 123</ns:submission_name> <ns:submission> <ns1:resourcesubmission resourcename="?" action="?" effectivetrading="?"> <ns1:supplycurve unavailable="0" starthour="?" startinterval="?" endhour="?" endinterval="?"> AEMO - WEMS Submission Specifications v5.0 77

78 <ns1:tranche price="?" quantity="?" maxramp="?" fueltype="?" ancillarypurpose="?"/> </ns1:supplycurve> </ns1:resourcesubmission> </ns:submission> <ns:discard_file_on_error>false</ns:discard_file_on_error> </ns:uploadbalancingstandingsubmission> </soapenv:body> </soapenv:envelope> To update a set of submissions via web services, the request should be of the form: <upload<type>submissiondocuments> <submission_name>name</submission_name> <submission_documents> <submission/> <submission/>... <submission/>... <submission/>... <submission/> </submission_documents> </discard_file_on_error>boolean</discard_file_on_error> </upload<type>submissiondocuments> For example: <soapenv:envelope xmlns:soapenv=" xmlns:ns=" <soapenv:header/> <soapenv:body> <ns:uploadbalancingstandingsubmissiondocuments> <ns:submission_name>submissions 123to137</ns:submission_name> <ns:submission_documents> (insert consecutive documents here) </ns:submission_documents> <ns:discard_file_on_error>false</ns:discard_file_on_error> </ns:uploadbalancingstandingsubmissiondocuments> </soapenv:body> </soapenv:envelope> AEMO - WEMS Submission Specifications v5.0 78