BB NAMEPLATE RATING DATA SUBMISSION TRANSACTION AND VALIDATION INFORMATION

Transcription

1 BB NAMEPLATE RATING DATA SUBMISSION TRANSACTION AND VALIDATION INFORMATION Version: 1.01 Published: 10 May 2018

2 IMPORTANT NOTICE Purpose These BB Nameplate Rating Data Submissionare made by AEMO under section 227 of the National Gas Law to specify the manner and form for providing information to AEMO for the Bulletin Board under Part 18 of the National Gas Rules (Rules), as at the date of publication, and have effect only for the purposes set out in the Rules. The Rules, the National Gas Law and the document named the BB Procedures prevail over these BB Daily Production and Flow Specification to the extent of any inconsistency. How to use this document The references listed throughout this document are primary resources and take precedence over this document. This document is written in plain language for easy reading. Where there is a discrepancy between the Rules and information or a term in this document, the Rules take precedence. Glossary Terms are capitalised and have the meanings listed against them in the Glossary. Italicised terms are defined in the Rules. Any rules terms not in this format still have the same meaning. Document Identification Business custodian: Manager, Gas Market Monitoring IT custodian: Manager, Market Systems Prepared by: Technical Writer Last update: Thursday, 10 May :43 AM Version History 1.00 First version 1.01 Added validation rule for free text fields; updated JSON format example Further Information For further information, please visit AEMO s website or contact: AEMO Information and Support Hub Phone: 1300 AEMO 00 ( ) and follow the prompts. supporthub@aemo.com.au Feedback Your feedback is important and helps us improve our services and products. To suggest improvements, please contact AEMO's Information and Support Hub. The material in this publication may be used in accordance with the copyright permissions on AEMO s website. Australian Energy Market Operator Ltd ABN info@aemo.com.au NEW SOUTH WALES QUEENSLAND SOUTH AUSTRALIA VICTORIA AUSTRALIAN CAPITAL TERRITORY TASMANIA WESTERN AUSTRALIA 1

3 CONTENTS 1. OVERVIEW 3 2. DESCRIPTION 3 3. DATA FIELDS 4 4. DATA SUBMISSION EXAMPLES 5 5. VALIDATION RULES 7 6. GLOSSARY Abbreviations Terms 8

4 1. OVERVIEW This document specifies the CSV and JSON file format, validation rules, and timing of submissions used by BB reporting entities to submit Nameplate Rating data to AEMO s Natural Gas Services Bulletin Board. 2. DESCRIPTION Transaction name Purpose Submission frequency Submission cut-off time Rollover Required by Notes NAMEPLATE_RATING Provide the nameplate rating of each facility or information about any planned permanent capacity reduction or expansion due to modification of the facility. Annually 31 March or whenever the standing capacity changes. No rollover. BB pipelines, BB production facilities, and BB storage facilities. BB pipelines are required to submit capacities for each direction in which natural gas can be transported on the pipeline. A Capacity Quantity must be submitted with a Capacity Description and the Delivery and Receipt Locations. Note that for complex pipeline facilities that involve more than two directions of flow, more than two capacities may be required.

5 DATA FIELDS: ABBREVIATIONS 3. DATA FIELDS Data element Date field name Description Mandatory Data type Example / Allowed values Facility Id FacilityId A unique AEMO defined Facility identifier. Yes int Capacity Type CapacityType Capacity type can be either: Storage: Holding capacity in storage, or Yes varchar( 10) STORAG E; MDQ MDQ: Daily maximum firm capacity (name plate) under the expected operating conditions adjusted for any facility that is mothballed, decommissioned or down-rated and / or cannot be recalled within one week, planned maintenance excepted. Reflects any long terms changes (greater than 12 months). Capacity Quantity CapacityQuantit y Standing capacity quantity in TJ to three decimal places. Three decimal places is not required if the value has trailing zeros after the decimal place. Yes numeric( 18,3) (if the value is ) Flow Direction FlowDirection Gas flow direction. Values can be either: RECEIPT A flow of gas into the BB facility, or DELIVERY A flow of gas out of the BB facility. Conditional: This field is mandatory for BB storage facilities with a MDQ Capacity Type value. Otherwise leave this field blank. varchar( 10) RECEIPT; DELIVER Y Capacity Description CapacityDescrip tion Free text to describe the meaning of the capacity number provided, including relevant assumptions made in the calculation of the capacity number and any other relevant information. Conditional: This information is mandatory for BB pipelines. Otherwise leave this field blank. varchar( 800) Receipt Location ReceiptLocation The Connection Point Id that best represents the receipt location. The Receipt Location in conjunction with the Delivery Location indicates the capacity direction and location. Conditional: This information is mandatory for BB pipelines. Otherwise leave this field blank. int Delivery Location DeliveryLocation The Connection Point Id that best represents the delivery location. This location in conjunction with the Receipt Location indicates the capacity direction and location. Conditional This information is mandatory for BB pipelines. Otherwise leave this field blank. int

6 DATA SUBMISSION EXAMPLES: ABBREVIATIONS Data element Date field name Description Mandatory Data type Example / Allowed values Effective Date EffectiveDate Gas day date that corresponding record takes effect. Any time component supplied will be ignored. Yes datetime Description Description Free text facility use is restricted to a description for reasons or comments directly related to the quantity or the change in quantity provided in relation to a BB facility (such as daily production data, nameplate rating, LCA flag, etc.), and the times, dates, or duration for which those quantities or changes in quantities are expected to apply. Yes varchar( 255) 4. DATA SUBMISSION EXAMPLES Example 1 The following scenario shows a nameplate data submission for BB pipelines due to changes in standing capacities. A CSV file format example is provided for FTP transfer or BB website upload, and JSON file format for HTTP web services. The JSON format example only illustrates information relating to the transaction data, and does not include header file information. Submission date is A nameplate submission for a BB pipelines ( and ) CSV file format FacilityId,CapacityType,CapacityQuantity,FlowDirection,CapacityDescription,Receipt Location,DeliveryLocation,EffectiveDate,Description ,MDQ,223.01,,This transmission capacity is the amount of gas that the Culcairn Delivery Location is able to withdraw from this pipeline facility., , , ,increase in nameplate pipeline capacity due to completion of VNIE Phase B ,MDQ,220.96,,This transmission capacity is the amount of gas that the Longford Receipt Location and VicHub Receipt Location and TasHub Receipt Location and the Lang Lang Receipt Location are able to inject into this pipeline facility. This capacity is limited by the maximum operating pressure of this pipeline facility and the maximum injection pressure of the Longford Gas Plant, , , ,increased pipeline capacity due to new the commissioning of a new compressor facility JSON format example "ItemList": [ "FacilityId": , "CapacityType": "MDQ", "CapacityQuantity": ,

7 DATA SUBMISSION EXAMPLES: ABBREVIATIONS "FlowDirection": null, "Capacity Description": "This transmission capacity is the amount of gas that the Culcairn Delivery Location is able to withdraw from this pipeline facility", "ReceiptLocation": " ", "DeliveryLocation": " ", "EffectiveDate": " T00:00:00+10:00", "Description": "increase in nameplate pipeline capacity due to completion of VNIE Phase B" "FacilityId": , "CapacityType":"MDQ", "CapacityQuantity": , "FlowDirection":null, "Capacity Description": "This transmission capacity is the amount of gas that the Longford Receipt Location and VicHub Receipt Location and TasHub Receipt Location and the Lang Lang Receipt Location are able to inject into this pipeline facility. This capacity is limited by the maximum operating pressure of this pipeline facility and the maximum injection pressure of the Longford Gas Plant", "ReceiptLocation": , "DeliveryLocation": , "EffectiveDate": " T00:00:00+10:00", "Description": "Increased pipeline capacity due to new the commissioning of a new compressor facility" ] Example 2 The following scenario shows a nameplate data submission for Silver Springs, a storage facility. The facility has STORAGE Capacity Type value, therefore Flow Direction, Capacity Description, Receipt Location, and Delivery Location information are not required. A CSV file format example is provided for FTP transfer or BB website upload, and JSON file format for HTTP web services. The JSON file example only illustrates information relating to the transaction data, and does not include header file information.

8 VALIDATION RULES: ABBREVIATIONS CSV file format FacilityId,CapacityType,CapacityQuantity,FlowDirection,CapacityDescription,Receipt Location,DeliveryLocation,EffectiveDate,Description ,STORAGE,330.60,,,,, ,New storage tank added to facility JSON file example "CompanyId": 100, "ItemList": [ "FacilityId": , "CapacityType":"STORAGE", "CapacityQuantity": , "FlowDirection": null, "Capacity Description": null, "ReceiptLocation": null, "DeliveryLocation": null, "EffectiveDate": " T00:00:00+10:00", "Description": "New storage tank added to facility" ] 5. VALIDATION RULES Effective Date must conform to the date format yyyy-mm-dd. Submissions must only contain Facility Ids operated by the Company Id. Submissions must only contain FacilityIds operated by the reporting identity. Negative values are not accepted for the receipt or delivery Capacity Quantity. Pipelines are required to submit capacities for each direction in which natural gas can be transported on the pipeline. Pipeline Capacity Quantity must be submitted with a Capacity Description and the Delivery and Receipt Points.

9 GLOSSARY: ABBREVIATIONS Storage facilities are required to report capacity for receipts into, and deliveries from, the BB storage facility as well as the quantity of natural gas that can be held in storage. For CSV file submissions, Description and Capacity Description with commas must be enclosed in double quotes, or exclude any commas. 6. GLOSSARY 6.1 Abbreviations Abbreviation Abbreviation explanation AEMO API BB CSV FTP HTTPS JSON NGERAC MDQ REST URL Australian Energy Market Operator. Application Programming Interface. The Natural Gas Services Bulletin Board. Comma Separated Values. Stores tabular data (numbers and text) in plain-text form. Plain text means the content is a sequence of characters, with no data that has to be interpreted instead, as binary numbers. File Transfer Protocol a protocol that allows users to copy files between any systems they can reach on the network. Hypertext Transfer Protocol over SSL. JavaScript Object Notation. National Gas Emergency Response Advisory Committee Maximum Daily Quantity. Representational State Transfer. Uniform Resource Locator. 6.2 Terms Term Authorised User Connection Point BB Procedures Rules TJ Definition A person authorised by a BB reporting entity to submit information to the Bulletin Board for that BB reporting entity. A Receipt Location or Delivery Location. The BB Procedures made under Part 18 of the National Gas Rules, which comprise of the document named the BB Procedures and these Gas Bulletin Board Data Submission Procedures. The National Gas Rules. 1 Terajoule, 1,000 Gigajoules, 1,000,000 Joules. A Joule is a unit of energy.