Energy, FCAS, And MNSP Bid Format And Validation
Format and Validation for Energy,FCAS, and MNSP Bids and Offers4.01 FinalJanuary 2020Describes the interface to submit file-basedenergy, FCAS, and MNSP dispatch bids andoffers
Format and Validation for Energy, FCAS, and MNSP Bids and OffersImportant NoticePURPOSEThis Format and Validation for Energy, FCAS, and MNSP Bids and Offers (Guide), prepared by the AustralianEnergy Market Operator (AEMO), provides guidance for the Settlements Residue Auction under the NER or AuctionRules(Rules).NO RELIANCE OR WARRANTYThis document does not constitute legal or business advice, and should not be relied on as a substitute for obtainingdetailed advice about the National Gas or Electricity Law, the Rules or any other applicable laws, procedures orpolicies. While AEMO has made every effort to ensure the quality of the information in this Guide, neither AEMO, norany of its employees, agents and consultants make any representation or warranty as to the accuracy, reliability,completeness, currency or suitability for particular purposes of that information.LIMITATION OF LIABILITYTo the maximum extent permitted by law, AEMO and its advisers, consultants and other contributors to this Guide (ortheir respective associated companies, businesses, partners, directors, officers or employees) are not liable(whether by reason of negligence or otherwise) for any errors, omissions, defects or misrepresentations in thisdocument, or for any loss or damage suffered by persons who use or rely on the information in it.TRADEMARK NOTICESMicrosoft is a trademark of Microsoft Corporation in the United States and/or other countries.Oracle and Java are registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries.DISTRIBUTIONAvailable to the public.DOCUMENT IDENTIFICATIONBusiness custodian: Manager, Market Monitoring and ChangeIT custodian: Team Lead, NEM Scheduling and Operations Forecasting SystemsPrepared by: Technology, Technical WritersVERSION HISTORYVersion 4.01Changes for the 5MS - Dispatch project with explanation of the JSON Bid/Offer File. Changes toproperties in the JSON schema. Updated validation messages.Last update: Monday, 20 January 2020 3:14 PMDOCUMENTS MADE OBSOLETEThe release of this document changes any previous versions of Format and Validation for Energy, FCAS, and MNSPBids and Offers and Participant Input Interface Energy – MNSP-FCAS Bid File Submission.FEEDBACKYour feedback is important and helps us improve our services and products. To suggest improvements, pleasecontact AEMO's support hub. 2020 Australian Energy Market Operator Limited.The material in this publication may be used in accordance with the copyright permissions on AEMO’s website.
ContentsIntroduction1Purpose1Audience1What's in this guide2How to use this guide3Chapter 1 Need to Know4Dispatch offers and bids explanation4Related rules and procedures5Assumed knowledge5Format and Validation for Energy, FCAS, and MNSP Bids and Offers user rights access6Chapter 2 About the Dispatch Bid/Offer Submission7What the Dispatch Bid/Offer Submission is for7Who can use the Dispatch Bid/Offer Submission7How to use the Dispatch Bid/Offer Submission8Chapter 3 Dispatch Bid/Offer Submission Explained9Dispatch Bid/Offer Submission design9JSON syntax10Bid/offer format10Bid/Offer Cut-off time10Service types10Bid/offer processing order10Submission level information11Valid or invalid bid/offer submission12Chapter 4 Energy Bids/Offers13About energy bids/offers13Energy bid element14Energy bid/offer details17Chapter 5 FCAS Offers21About FCAS offers21FCAS service types21FCAS offer element22FCAS offer details23 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and OffersIII
FCAS offer detailsChapter 6 MNSP Offers2326About MNSP offers26MNSP offer element27MNSP offer details29Chapter 6 Rebid Explanation32About rebid explanations32Rebid explanation element32Rebid explanation details33Chapter 7 Submitting a Dispatch Bid/Offer by FTP35FTP submission prerequisites35FTP participant file server addresses36FTP submission rules36FTP processing order for multiple files36FTP Bid/offer filename36Submitting an FTP bid/offer37FTP Throttling limit39Receiving FTP bid/offer acknowledgements39Chapter 8 Dispatch Bid/Offer Submission ResponseResponse details4040Chapter 9 Schema Validation Messages44Needing Help50Frequently asked questions50AEMO's support hub50Feedback51Rules terms52GlossaryCommon terms5353References58Appendix 1 JSON Dispatch Bid/Offer Submission Schema59Appendix 2 Electricity Data Model72Energy bid/offer tables72FCAS offer tables72MNSP offer tables73Index 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers74IV
IntroductionPurposeAudienceWhat's in this guideHow to use this guide1123PurposeThis Guide describes:1. The JSON Dispatch Bid/Offer Submission and validations used by participantsto submit and maintain Energy, Frequency Controlled Ancillary Services(FCAS), and Market Network Service Provider (MNSP) bids in the NEM.2. How to submit your JSON Dispatch Bid/Offer Submission by FTP.AudienceThe primary audience is:llDevelopers of systems handling Energy, FCAS, and MNSP Bids/Offers.Market Participants submitting and maintaining Energy, FCAS, and MNSPBids/Offers.The secondary audience is business users requiring an understanding of theDispatch Bid/Offer Submission. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers1
What's in this guideWhat's in this guideThis guide explains the JSON schema for submitting Bids/Offers andhow to submit Bids/Offers over FTP.For help submitting web-based Bids/Offers, see Guide to Energy andFCAS Bids.For help submitting Bid/Offer APIs, see Guide to Dispatch Bid/OfferAPIs.For help submitting Network Control Ancillary Services (NCAS) reoffers or system restart ancillary services (SRAS) re-offers, see ASRe-Offer Bid Format and Validation.Chapter 1 Need to Know on page 4 explains how the terms Dispatch Bids andOffers are used throughout this guide, the skills required to complete andsubmit bids, lists the related Rules and procedures, and provides the entityrequired for Participant User access.Chapter 2 About the Dispatch Bid/Offer Submission on page 7 explains what theDispatch Bid/Offer Submission is for, who can use it, how to use it, thesubmission rules.Chapter 3 Dispatch Bid/Offer Submission Explained on page 9 explains thedesign, format, processing order, submission level information, valid, andinvalid Dispatch Bid/Offer Submissions.Chapter 4 Energy Bids/Offers on page 13 explains the Energy bids element of theDispatch Bid/Offer Submission.Chapter 5 FCAS Offers on page 21 explains the Frequency Control AncillaryService (FCAS) bids element of the Dispatch Bid/Offer Submission.Chapter 6 MNSP Offers on page 26 explains the Market Network Service Provider(MNSP) bids element of the Dispatch Bid/Offer Submission.Rebid Explanation on page 32 explains the Rebids explanation element of theDispatch Bid/Offer Submission.Chapter 7 Submitting a Dispatch Bid/Offer by FTP on page 35 explains theDispatch Bid/Offer Submission over FTP.Chapter 8 Dispatch Bid/Offer Submission Response on page 40 explains theresponse received after submission. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers2
How to use this guideChapter 9 Schema Validation Messages on page 44 explains the validationmessages received in a response.Needing Help on page 50 provides a list of frequently asked questions aboutDispatch Bid/Offer Submissions and how to contact AEMO's Support Hub.Rules terms on page 52 provides a list of National Electricity Rules (NER) termsused throughout this guide.Glossary on page 53 provides the definition of the capitalised terms usedthroughout this guide.References on page 58 provides a list of references used throughout this guide.Appendix 1 JSON Dispatch Bid/Offer Submission Schema on page 59 providesand example of an entire JSON schema Dispatch Bid/Offer Submission.Appendix 2 Electricity Data Model on page 72 explains the Dispatch Bid/OfferSubmission related Electricity Data Model tables.How to use this guidelllllFor an explanation of the terms Offer and Bid used throughout this Guide, readDispatch offers and bids explanation on page 4.This guide is written in plain language for easy reading.Where there is a discrepancy between the Rules and information or a term inthis document, the Rules take precedence.Where there is a discrepancy between the relevant Procedures and informationor a term in this document, the Procedures take precedence.The references listed throughout this document are primary resources and takeprecedence over this document.lText in this format indicates a resource on AEMO’s website.lText in this format indicates a direct link to a section in this guide.lText in this format is an action to complete in the Markets Portal interface.lllGlossary and Rules terms are capitalised and have the meanings listed againstthem in the Rules terms on page 52 and Glossary on page 53.The numbers on the example screenshots throughout this guide refer to thenumbered explanations in the topic.References to time are Australian Eastern Standard time (AEST) unlessotherwise specified. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers3
Chapter 1 Need to KnowDispatch offers and bids explanationRelated rules and proceduresAssumed knowledgeFormat and Validation for Energy, FCAS, and MNSP Bids and Offers user rightsaccess4556Dispatch offers and bids explanationThis chapter provides and explanation of the terms Offer and Bid and how they areused throughout this Guide.Bid explanationIn this Guide the term Dispatch Bid (Bid) relates to the Dispatch of a Scheduled Loadand has the meaning given to it in the National Electricity Rules (NER).The term Bid relates to the following Dispatch Bids:1. Energy (Scheduled Loads)Offer explanationIn this Guide the term Dispatch Offer (Offer) means a Generation Dispatch Offer, aNetwork (MNSP) Dispatch Offer, or a Market Ancillary Service (FCAS) Offer. Theseterms have the meaning given to them in the National Electricity Rules (NER).The term Offer relates to the following Dispatch Offers:1. Energy (Generation Dispatch Offer)2. Frequency Control Ancillary Service (FCAS)3. Market Network Service Provider (MNSP - Network Dispatch Offer) 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers4
Related rules and proceduresRelated rules and proceduresItemLocationDispatch inflexibilitiesAEMC website NER clause 3.8.19(b)(2)Introduction toMarket RulesAEMC website NER Chapter 3Market Floor PriceAEMC website NER 3.9.6.MNSP Convexity RuleAEMC website NER Clause 3.8.6A (e).Operating Procedure:Mandatory RestrictionOffersAEMO website Security and Reliability Power System OperatingProceduresProvision of ramp ratesAEMC website NER clauses 3.8.3A(f) and (g)RebiddingAEMC website NER clause 3.8.22(c)(3)Rebidding andTechnical te-settlement-2019Assumed knowledgeThis guide assumes you have knowledge of:lJSON basicslREST API standardslWeb-based technologieslThe operating system you are usinglConnecting to AEMO's Electricity IT systems 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers5
Format and Validation for Energy, FCAS, and MNSP Bids and Offers user rights accessFormat and Validation for Energy, FCAS, and MNSP Bidsand Offers user rights accessParticipant Administrators (PAs) authorise Participant User access in MSATS. Theinitial PA is set up by the AEMO system administrator as part of the registrationprocess.Participant Users submitting Dispatch Bid/OfferSubmission via FTP require access to AEMO'sprivate network, MarketNet. For help, see Guide toElectricity Information Systems.Participant Users submitting Dispatch Bid/OfferSubmission via APIs and web require credentialsprovided by their company's ParticipantAdministrator.For more detailsabout participantadministration anduser rights access,see Guide to UserRights Management.The entity required to access Dispatch Bid/OfferSubmission is:EMMS – Offers and Submissions – Energy FCAS MNSP Bids. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers6
Chapter 2 About theDispatch Bid/OfferSubmissionThis chapter explains what the Dispatch Bid/Offer Submission is for, who can use it,and how to submit it.What the Dispatch Bid/Offer Submission is forWho can use the Dispatch Bid/Offer SubmissionHow to use the Dispatch Bid/Offer Submission778What the Dispatch Bid/Offer Submission is forEffective Dispatch Bid/Offer Submissions are used in the Dispatch process.Use the JSON Dispatch Bid/Offer Submission format to submit and maintain Energy,Frequency Controlled Ancillary Services (FCAS), and Market Network ServiceProvider (MNSP) Bid/Offers to your chosen interface.Who can use the Dispatch Bid/Offer SubmissionAuthorised Market Participants can use Dispatch Bid/Offer Submission inaccordance with the National Electricity Rules (NER).Access to submit Dispatch Bid/Offer Submissions requires credentials provided byyour company's Participant Administrator. For help, see Format and Validation forEnergy, FCAS, and MNSP Bids and Offers user rights access on page 6. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers7
How to use the Dispatch Bid/Offer SubmissionHow to use the Dispatch Bid/Offer SubmissionThe 5-minute JSON Dispatch Bid/Offer Submission format is availablefrom 1 April 2021. The current 30-minute csv format is not supportedfrom 1 July 2021. Participants choosing to use FTP as their primaryprotocol must convert to the JSON Dispatch Bid/Offer Submission by1 July 2021.Interfaces for submitting bids/offersBefore attempting any changes or operations on production systems, AEMOencourages participants to use the pre-production environment to test proceduresand to train Participant Users.You can submit a Dispatch Bid/Offer Submission using the following interfaces:1. API to AEMO's e-Hub for all Offer Types. You can access APIs over the internetand MarketNet. See Guide to AEMO's e-Hub APIs.2. FTP to your participant folders on the Participant File Server for all Bid/OfferTypes.To automate submission of the Dispatch Bid/Offer Submission, participants canset up Data Interchange. For help, see Concise Guide to Data Interchange.3. For Energy and FCAS Bid/Offer Types only:a. Manual entry to the Markets Portal. For help, see Guide to Web-basedEnergy and FCAS bids.b. File upload to the Markets Portal. For help, see this guide for the JSONschema layout and for help uploading the Dispatch Bid/Offer Submission,see Guide to Web-based Energy and FCAS bids. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers8
Chapter 3 DispatchBid/Offer SubmissionExplainedDispatch Bid/Offer Submission designJSON syntaxBid/offer formatBid/Offer Cut-off timeService typesBid/offer processing orderSubmission level informationValid or invalid bid/offer submission910101010101112Dispatch Bid/Offer Submission designThe Dispatch Bid/Offer Submission is a JSONformat, supporting:1. Multiple Trading Days and DUIDs.2. A mix of DUIDs bidding or offering with andwithout a Mandatory Restriction Offer.For details of theJSON schema, seeAppendix 1 JSONDispatch Bid/OfferSubmission Schemaon page 59.3. Separate formats for different Service Types soyou don't need to include unrequired fields.4. Provision of all Service Types in the sameDispatch Bid/Offer Submission.5. JSON schema validation based on ServiceType.6. Modern technologies natively supporting JSON. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and OffersFor more detailsabout MandatoryRestrictions, seeOperatingProcedure:MandatoryRestriction Offers.9
JSON syntaxJSON syntaxlData is in name and value pairs.The name in double quotes is followed by a colon and then a value.lData is separated by commas.lCurly braces hold objects.lSquare brackets hold arrays.Bid/offer formatParticipants can submit 5-minute Dispatch Bids in aJSON format (compressed or uncompressed) for FTP,API, and web upload.For an example,see Submissionlevel information onthe next page.For more detailsabout the JSONschema, seehttps://jsonschema.org/Bid/Offer Cut-off timellA Daily Bid/Offer is one submitted before theBid/Offer Cut-off Time.A Rebid is a Bid/Offer submitted after theBid/Offer Cut-off Time.The Bid/Offer Cut-offTime is 12:30 pm theday before theTrading Day.Service types1. Energy2. Frequency Controlled Ancillary Services (FCAS)3. Market Network Service Provider (MNSP)Bid/offer processing orderDispatch Bid/Offer Submissions are processed by AEMO in the order they arereceived. You must ensure the correct submission order so your latest DispatchBid/Offer Submission is the Effective Dispatch Bid/Offer Submission acknowledgedby AEMO’s systems. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers10
Submission level informationFor a Dispatch Bid/Offer Submission to become Effective you mustreceive an Acknowledgement from AEMO's systems. For an example,see Dispatch Bid/Offer Submission Response on page 40.Submission level informationYou supply the Bid/Offer Service Type information in the relevant element:energyBids, fcasBids, mnspBids.To support multiple bids for different Service Types, every Dispatch Bid/OfferSubmission can supply the following submission level information.The Participant ID is not required in the submission. AEMOdetermines it in the identity management layer, validating authorisationto submit for the respective DUIDs.Submission level fields explainedRule legend:M: Mandatory – You must provide the field if providing the parent field.O: Optional – You may provide the field, if not provided a default is assumed. To indicate no value, you mustremove the entire attribute.C: Conditional – The field is normally optional but may be mandatory under certain conditions. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers11
Valid or invalid bid/offer mpstringOParticipant provided timestamp for thesubmission. Expected in the format:format:date-timeyyyy-mm-ddThh:MM:ss[ 10:00]e.g. 2021-04-23T20:20:39, 2021-0423T20:20:39 10:00referenceIdstring(100)MA participant provided reference.Must be unique for each submissioncommentstring(100)OParticipant provided comment or description forthis submissionauthorisedByString(20)OPerson authorising this submission. Used forparticipant’s reference, not validatedenergyBidsarrayCCollection of one or more Energy bidsfcasBidsarrayCCollection of one or more FCAS bids.mnspBidsarrayCCollection of one or more MNSP bids.Valid or invalid bid/offer submissionValid bid/offerFor FTP submissions, if the entire Dispatch Bid/OfferSubmission is valid, an acknowledgement returns.The acknowledgement is a compressed file calledACK.zip containing an ACK.json file.For examples, seeResponse Examples.The data from valid and subsequent communications is processed andcommunicated in NEM reports, complying with the Electricity Data Model. For details,see Appendix 2 Electricity Data Model on page 72.Invalid bid/offerFor FTP submissions, if any of the Dispatch Bid/Offer Submission contains invaliddata, the whole Bid/Offer is rejected and an acknowledgement returns. Theacknowledgement is a compressed file called CPT.zip (for corrupt) containing aCPT.json file indicating all detected errors. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers12
Chapter 4 EnergyBids/OffersThis chapter explains the Energy bids elements of the Dispatch Bid/OfferSubmission. For details about the whole schema, see Appendix 1 JSON DispatchBid/Offer Submission Schema on page 59.About energy bids/offersEnergy bid elementEnergy bid/offer details131417About energy bids/offersAn Energy Bid/Offer contains at least one Energy Service Type, in the energyBidselement.The Dispatch Bid/Offer Submission in Energy bid/offer details on page 17 is valid,even though it has no mention of Mandatory Restriction (MR) items because it is notcompulsory for participants to bid for Mandatory Restriction Offers. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers13
Energy bid elementEnergy bid element 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers14
Energy bid element 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers15
Energy bid element 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers16
Energy bid/offer detailsEnergy bid/offer detailsProvide this data in the energyBid element of the Dispatch Bid/Offer Submission. Foran explanation of the fields, see energyBid element details below.Table 1 energyBid element detailsRule legend:M: Mandatory – You must provide the field if providing the parent field.O: Optional – You may provide the field, if not provided a default is assumed. To indicate no value, you mustremove the entire attribute.C: Conditional – The field is normally optional but may be mandatory under certain ergyBidobjectMMandatory for energy bids onlyproperties: tradingDate, duid, prices, fastStartProfile,dailyEnergyConstraint, rebidExplanation,mrPriceScalingFactor, energyPeriodsRequired: tradingDate, duid, prices, energyPeriodstradingDatestringMString in date formatMust be a valid date.The effective date for this bid. Expected in theformat:yyyy-mm-dd or yyyy-mm-dd 00:00:00e.g.2021-04-232021-04-23 00:00:00duidstring(10)MDispatchable Unit identifier recorded in AEMO'ssystemsMust be upper casemaxLength: 10pricesarrayMAn array of 10 prices - Items:priceminItems: 10maxItems: 10e.g. [0.00, 0.00, 20.00, ]items:pricenumberMBand pricesmultipleOf: 0.01e.g. 0.01, etc.fastStartProfileobjectOFast-Start Inflexibility ProfileProperties: minimumLoad, t1, t2, t3, t4Required: minimumLoad, t1, t2, t3, t4 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers17
Energy bid/offer detailsElementTypeRuleDescription/validationOnly valid for fast-start units. If not provided, theunit is treated as slow start, and all values in the datamodel will default to null.mrPriceScalingFactornumberOMandatory restrictions offer price scaling factor.multipleOf: 0.0001minimum: 0Not valid for scheduled loads.dailyEnergyConstraintintegerORepresents the maximum energy available from aconstrained Plant in the Trading DayOnly relevant to the Energy Service TypeCannot be negativeExpressed in MWh/dayminimum: 0maximum: 999999mrPriceScalingFactornumberOMandatory restrictions offer price scaling factor.multipleOf: 0.0001minimum: 0Not valid for scheduled loads.energyPeriodsarrayMAn array of 288 period objects: periodID, maxAvail,rampUpRate, rampDownRate, bandAvail, pasaAvail,mrCapacity, fixedLoadItems:EnergyBidRequired: periodId, bandAvail, maxAvail, pasaAvail,rampUpRate, ies: tradingDate, duid, prices, fastStartProfile,dailyEnergyConstraint, rebidExplanation,mrPriceScalingFactor, energyPeriodsRequired: tradingDate, duid, prices, energyPeriodsperiodIdintegerMThe 5-minute trading interval, starting from theinterval starting at 0400 (and ending at 0405)Must be between 1 and 288maxAvailintegerMMaximum availability loading for a period, in wholemegawattsminimum: 0 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers18
Energy bid/offer RateintegerMRate of change up - The maximum rate of increasefor the unit in MW/minminimum: 0rampDownRateintegerMRate of change down - The maximum rate ofdecrease for the unit in MW/minminimum: 0bandAvailarrayMAn availability for each of the 10 price bands must beprovided - items:availMin Items: 10Max Items: 10e.g. [0, 0, 100, 200, 0, 0, ]items:availintegerMThe availability (or required level) of energy for eachprice band, in whole megawattsminimum: 0pasaAvailintegerMThe unit’s capability including any capabilitypotentially available in 24 hoursminimum: 0mrCapacityintegerORequired if offering under Mandatory Restrictions.minimum: 0Must be the same for each 5-minute period in a 30minute Trading Interval.Must have a Price Scaling Factor and all 288 periods.Not valid for a Scheduled LoadDUID must be a Generating UnitThe initial MR Bid for a Mandatory Restriction Perioddeclared in the relevant Region for a particularTrading Day must be made before the MR Bid Cut-offTime for that MR Period, otherwise the MR Bid isrejected.An MR Bid for a Trading Day only applies for thatday.MR Capacity RebidsThe initial MR Bid must be valid.After the MR Bid Cut-Off Time, the factor must bethe same as the last valid MR Bid.fixedLoadintegerOFixed unit output, in MW. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers19
Energy bid/offer detailsElementTypeRuleDescription/validationMust be 1 MW or greater.A rebid reason must be provided if this field ispopulated. See Rebid Explanation on page 32minimumLoadnumberMMinimum MW loadminimum: 0t1numberMTime to synchronise, in minutesminimum: 0maximum: 30t2numberMTime to reach minimum load, in minutesminimum: 0maximum: 30t3numberMTime at minimum load, in minutesminimum: 0maximum: 59t4numberMTime to shut down, in minutesminimum: 0maximum: 59commentsstringOParticipant's free form fieldmaxLength: 500rebidExplanationobjectCRequired for rebids, fixed load, and low ramp ratesProperties: reason, eventTime, awareTime,decisionTime, categoryRequired: reasonSee Rebid Explanation on page 32 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers20
Chapter 5 FCAS OffersThis chapter explains the Frequency Control Ancillary Service (FCAS) bids elementof the Dispatch Bid/Offer Submission. For details about the whole schema, seeAppendix 1 JSON Dispatch Bid/Offer Submission Schema on page 59.About FCAS offersFCAS service typesFCAS offer elementFCAS offer detailsFCAS offer details2121222323About FCAS offersAn FCAS Offer contains at least one FCAS Service Type, in the fcasBids element.FCAS service typesFCAS service types are: RAISE6SEC, RAISE60SEC, RAISE5MIN, RAISEREG,LOWER6SEC, LOWER60SEC, LOWER5MIN and LOWERREG). 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers21
FCAS offer elementFCAS offer element 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers22
FCAS offer detailsFCAS offer detailsProvide this data in the fcasBids element of the Dispatch Bid/Offer Submission. Foran explanation of the fields, see fcasBid element details below.FCAS offer detailsTable 2 fcasBid element detailsRule legend:M: Mandatory – You must provide the field if providing the parent field. 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers23
FCAS offer detailsO: Optional – You may provide the field, if not provided a default is assumed. To indicate no value, you mustremove the entire attribute.C: Conditional – The field is normally optional but may be mandatory under certain andatory for FCAS bidsProperties: tradingDate, duid, prices, service,rebidExplanation, fcasPeriodsRequired: tradingDate, duid, prices, service, tringMString in date format.Must be a valid date.The Trading Day the Offer is for. Expected in the format:yyyy-mm-dd or yyyy-mm-dd 00:00:00e.g.2021-04-232021-04-23 00:00:00duidstring(10)MDispatchable Unit identifier recorded in AEMO's systemsMust be upper casemaxLength: 10pricesarrayMAn array of 10 prices - Items:priceminItems: 10maxItems: 10e.g. [0.00, 0.00, 20.00, ]items:pricenumberMBand pricesmultipleOf: 0.01e.g. 0.01, etcservicefcasPeriodsstring(10)MarrayMThe FCAS service type, one of:RAISE6SEC, RAISE60SEC, RAISE5MIN, RAISEREG,LOWER6SEC, LOWER60SEC, LOWER5MINAn array of 288 period objects: periodID, maxAvail,bandAvail, enablementMin, lowBreakPoint,highBreakPoint, enablementMaxItems:fcasPeriods 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers24
FCAS offer jectMfcasPeriodsProperties: periodId, maxAvail, bandAvail,enablementMin, lowBreakPoint, highBreakPoint,enablementMaxRequired: periodId, bandAvail, maxAvail, enablementMin,lowBreakPoint, highBreakPoint, enablementMaxperiodIdintegerMThe 5-minute trading interval, starting from the intervalstarting at 0400Must be between 1 and 288maxAvailintegerMMaximum availability loading for a period, in wholemegawattsminimum: 0bandAvailarrayMAn availability for each of the 10 price bands must beprovided: items/availe.g. [0, 0, 100, 200, 0, 0, ]Min Items: 10Max Items: 10items:availintegerMThe availability (or required level) of energy for each priceband, in whole megawattsminimum: 0enablementMinintegerMMinimum MW output this service can supplyminimum: 0enablementMaxintegerMFCAS low break point, in megawattsminimum: 0lowBreakPointintegerMFCAS high break point, in megawattsminimum: 0highBreakPointintegerMMaximum MW output that this unit can provide The fullservice availability (as per MaxAvail)minimum: 0rebidExplanationobjectCRequired for rebids, fixed load, and low ramp ratesproperties: reason, eventTime, awareTime, decisionTime,categoryRequired: reasonSee Rebid Explanation on page 32 2020 AEMO Format and Validation for Energy, FCAS, and MNSP Bids and Offers25
Chapter 6 MNSP OffersThis chapter explains the Market Network Service Provider (MNSP) bids element ofthe Dispatch Bid/Offer Submission. For details about the whole schema, seeAppendix 1 JSON Dispatch Bid/Offer Submission Schema on page 59.About MNSP offersMNSP offer elementMNSP offer details262729About MNSP offersAn MNSP Offer contains at least one M
FormatandValidationforEnergy, FCAS,andMNSPBidsandOffers 4.01Final January2020 Describestheinterfacetosubmitfile-based energy,FCAS,andMNSPdispatchbidsand
Aug 27, 2019 · SUBMISSION OF BID: a. Bids must be sealed in an envelope, and the outside of the envelope should be marked with the following information: 1. Marked with the words “Sealed Bid”. 2. Name of the firm submitting the Bid. 3. Title of the Bid. 4. Bid Number. 5. Bid Due Date. 6. Contact e-mail and telephone number. b. The bid must be submitted as .
3.3 A bid that contains any escalation clause is considered invalid. 3.4 Bidders shall include a Bid Bond or other approved bid security with the bid form submitted to the Owner when the bid form indicates such bid security is required. The bond value shall be 5% of the bid amount. The form of bond is shown in section 00 43 13.
to Bid form (SBD1) and requisite bid forms attached as (Part 4) with its bid. Bidders must take careful note of the special conditions. 2.2 All bids submitted in reply to this invitation to bid should incorporate all the forms, parts, certificates and other documentation forming part of this invitation to bid, duly completed and
pre-bid meeting will be held at the following place and time: All Vendors submitting a written bid must attend the mandatory pre-bid meeting. Failure to attend the mandatory pre-bid meeting shall result in disqualification of the Vendor's bid. No person attending the pre-bid meeting may represent more than one (1) Vendor.
accordance with this Offer Letter Bid Centres The centres specified in paragraph 14 of this Offer Letter for the submission of Bid Forms Bid Closing Date Monday, February 02, 2015, being the last date of the Bid Period Bid Form Bid form as enclosed with this Offer Letter and specifically marked as 'Bid-Cum-
Bid/Proposal Title: Bid/Proposal Number: Indicate what part of the bid this form package is being submitted for: 1. Base Bid/Proposal Only: 2. Base Bid/Proposal with Alternates*: (List Alternate #s ) 3. Only Bid/Proposal Items*: (List Item #s ) *If you are only bidding on certain items or alternates on a bid/proposal, indicate the alternates
Bid security in the form of a bid bond, payable to the Town of Manchester, is required in the sum of 5 percent (5%) of the total bid. Bid security shall be subject to the conditions set forth in the Standard Instructions to Bidders. No bidder may withdraw their bid for a period of sixty (60) days after the date of bid opening.
In recent years technologies like Artificial Intelligence (AI) is been proved immensely valuable to SCM. As the name suggests AI defined as the ability of a computer to independently solve problems that they have not been explicitly programmed to address. The field of AI came to existence in 1956, in a workshop organized by John McCarthy (McCarthy Et al., 2006). In successive years the .
