SIBR Interface Specification for Bidding Services

Transcription

1 SIBR Interface Specification for Bidding Services (Business Rules v 8.x(Fall 2014) or later) Version: 11.5 Oct 8, 2014

2 Revision History Date Version By Description 11/5/ WT 10/8/ WT Minor edits and added reference examples for Wheeling differences between v2 and v3 services. 7/2/ WT Updates for sample xml and correction to data elements regarding Transaction based bids. Added BSAP endpoints for BaseSchedule. 6/3/ WT Updates to the CB artifacts and Base Schedule artifacts. 5/8/ WT Update based on newest design schema changes. Updated section 1.3 with these changes. (Base Schedule, Base Schedule Results) 3/31/ WT Update based on newest design schema changes. Updated section 1.3 with these changes. (Base Schedule, Bid Results) WT 2/27/ Initial Draft for Fall 2014 Web Service changes. EIM and Scheduling Point submission changes. See section 1.3 2/20/ WT Added sample Request xml for Energy Forecast per method and for bid retrieval per method. 1/23/ WT Added Enumeration values for the Bid Option. Seperated the submitrawbid BidResults and CleanBidSet for both v1 and v2 versions for clarity. Moved table for Energy Product with Self- Page 2 of 305

3 Schedule to come after the SubmitRawBid Element tables. Added Appendices for xml examples for submitting Bids / EnergyForecast. 12/17/ WT/ Updated to return the Ramp Rate attribute and elements to the xsds for RawBid, CurrentBid and CleanBid. 11/22/ WT/ Removed Draft language, and updated order for attributes and elements (alphabetical). 10/28/ WT/ Update Clean Bid, Bid Results, and Raw Bid for new elements to show the. Dispatch Options for FERC 764, Capacity Limit at plant level and introduced new Energy Forecasting submission and requests. Removed deprecated services for CleanBid,BidResults, and RawBid. Also removed Ramp Rate bid components. 1/17/ WT/ Update Section and for content related to the Opportunity Cost in the Regulation Component. (y2axisdata) 1/14/ WT/ Update Section 1.3 for content related to the Opportunity Cost in the Regulation Component. 12/11/ WT/ Update Clean Bid, Bid Results, and Raw Bid for new element to show the Opportunity Cost. Removed deprecated services for CleanBid,BidResults, and RawBid. 12/08/ WT/ Update Clean Bid, Bid Results, and Raw Bid for new element to show the Charge Limit Component. Removed deprecated services for CleanBid,BidResults, and RawBid. 7/1/ WT/ Update Clean Bid and Bid Results for new element to show the Open Tie Status. Removed deprecated services for CleanBid and BidResults. 2/1/ WT/ Update to bidcreditstatus pg /11/ WT/ Update to bidstatus and bidcreditstatus pg /25/ WT/ DRAFT version for the CB related web services. 3/1/ WT/ DRAFT version for the MSG related web services. 2/19/ WT/ Updated to include all supported versions of the web services Page 3 of 305

4 related to SIBR. (Go-live and SCP) 9/22/ WT/ This is Final, changed from DRAFT state. 9/22/ WT/ Modified Namespace for RawBidSet, BidResults, and CleanBidSet XSD and associated WSDLs (versioning in namespace) 9/14/09 3 WT/ New Namespace for RawBidSet, BidResults, and CleanBidSet XSD and associated WSDLs Added Capacity Limit, and Capacity Limit Ind 10/14/ WT/ New Namespace for RawBidSet, BidResults, and CleanBidSet XSD and associated WSDLs Added Bid Status S and SO 10/1/ WT/ DC New Namespace for RawBidSet, BidResults, and CleanBidSet XSD and associated WSDLs Enumeration added for RMT ReferenceType Removed ETP/TOP SelfSchedule Types Updated Contingency Flag Element Description 9/11/ WT/ DC Updates to the Element tables associated with the RawBidSet. Bid Limit notation added for the SIBR application, not specific to any XSD limit. BidResults.xsd [Added escape character to pattern for BidPriceCurve/CurveScheduleDatas/y1AxisData 9/11/ WT Updated namespace for retrievecurrentbidresults.wsdl and retrievecleanbidset.wsdl 8/19/ WT Update to: (these can only be used with SIBR BR set or higher ( SIBR CR4+ release) submitrawbidset.wsdl RawBidSet.xsd retrievecurrentbidresults.wsdl retrievecurrentbidresults_docattach.wsdl RequestBidResults.xsd BidResults.xsd retrievecleanbidset.wsdl retrievecleanbidsetdocattach.wsdl RequestCleanBidSet.xsd CleanBidSet.xsd Element data and example xml files updated with new versions. Page 4 of 305

5 All xml examples for bid submission and retrieves will be placed into a reference file separate from this specification. It will be enhanced to include more examples and specific products in relation to schedule types. 4/2/ WT Update to Submit Raw Bid Set Element table, Example RawBidSet.xml files, WSDL retrievecleanbidset.wsdl, RequestCleanBidSet.xsd, CleanBidSet,xsd, Example CleanBidSet.xml, Example BidResults.xml 2/29/ WT Added comment to IFM Self-Sched Type in the CleanBidSet.xsd for internal use SIBR -> RTM 1/25/ WT Added Section 1.3 for Release notes for xsd wsdl changes Updated BidResults.xsd, RawBidSet.xsd, CleanBidSet.xsd, 11/20/ WT Updated for IMS Update 2, WSDL and XSD changes. 10/18/ WT This version provided for IMS R3 Update 1 posting. SIBR BR ( ) 9/28/ WT Updated date formats in examples for RTM and GMT offsets that were not correct. 8/29/ WT Updated LOF, LFD/U information in examples 7/20/ WT Added some clarity to bidding ProdType SSType, and RetrieveCleanBid, RetrieveCurrentBidResult Web service 2/23/ WT Updated for Release 5 WSDLs and XSDs (see Appendix Changes to XSD Files ver 1.3) 12/20/ DC Updated for Release 4 WSDLs and XSDs (see Appendix - Changes to XSD Files ver 1.2) 6/30/ PM VM Updated for Release 3 WSDLs and XSDs (see Appendix Changes to XSD Files ver 1.1). 5/31/ PM 1 st released version. Page 5 of 305

6 TABLE OF CONTENTS 1 Introduction Purpose Contact Information Release tes for Bidding Services version Namespace Matrix for Physical Bids Namespace Matrix for Convergence Bids (CB) SIBR End Points Related Documents Submit Raw Bid (includes CB) Business Scenario Service Level Agreement Use Model Operation Details WSDL (submitrawbidset_v3.wsdl) ( this has version used with FNM) WSDL (submitrawbidset_v2.wsdl) ( this has version to be used with Bid/Dispatch Option) WSDL (submitcbrawbidset_v1.wsdl) (CB) WSDL (submitcbrawbidset_v wsdl) (CB) Date Time Data Type Format Standard Attachment Information Element table Schema (StandardAttachmentInfor.xsd) Example XML File (StandardAttachmentInfor.xml) SubmitRawBidSet Element Table (v3 service newest to encorporate the FNM changes. ) Element Table (v2 service, for Bid Option and Capacity Limit) Bidding Product Type with Self Schedule Type Submit CB RawBidSet Element Table (v1 service newest to incorporate the CIM changes for consistency. ) Element Table (v go-live) Schema (CB_RawBidSet_v xsd) (CB) Schema (CB_RawBidSet_v1.xsd) (CB) Page 6 of 305

7 2.14 Raw Bid Set Response Element Table CB Raw Bid Set Response Element Table Schema (SubmitStandardOutput.xsd) Schema (SubmitStandardOutput_v xsd) Fault Return (also the same for CB) Element Table Schema (StandardOutput.xsd) (also the same for CB) Submit Bid Action (includes CB Bid Action) Business Scenario Service Level Agreement Use Model Operation Details WSDL (submitbidaction.wsdl) WSDL (submitcbbidaction.wsdl) Submit Bid Action Element Table Submit CB Bid Action Element Table Schema (BidAction.xsd) Schema (CBBidAction.xsd) BidAction Response CBBidAction Response Fault Return CBFault Return Retrieve Clean Bid Set (includes CB ) Business Scenario Service Level Agreement Use Model Operation Details WSDL (retrievecleanbidset_v1.wsdl) WSDL (retrievecleanbidset_v3.wsdl) WSDL (retrievecbcleanbidset_v wsdl) WSDL (retrievecbcleanbidset_v1.wsdl) Clean Bid Set Request Page 7 of 305

8 Element Table CBClean Bid Set Request Element Table Schema (RequestCleanBidSet.xsd) Schema (RequestCBCleanBidSet.xsd) Clean Bid Set Response Element Table (v3 newest service for EIM FNM) Element Table (v2 service, for Bid Option and Capacity Limit) CB Clean Bid Set Response Element Table (v1, newest for EIM, FNM) Element Table (CB - go-live) Schema (CleanBidSet_v2.xsd) Schema (CleanBidSet_v3.xsd) Schema (CB_CleanBidSet_v xsd) Schema (CB_CleanBidSet_v1.xsd) Fault Return Retrieve Current Bid Results (includes CB) Business Scenario Service Level Agreement Use Model Operation Details WSDL (retrievecurrentbidresults_v2.wsdl) WSDL (retrievecurrentbidresults_v3.wsdl) WSDL (retrievecbcurrentbidresults_v1v1.wsdl) Current Bid Results Request Element Table CB Current Bid Results Request Element Table Schema (RequestBidResults.xsd) Schema (RequestCBBidResults.xsd) Current Bid Results Response Element Table (v3 service newest for FNM) Element Table (v2 service, with Bid Option and Capacity Limit) Current CB Bid Results Response Element Table (v1 newest for consistency with CIM) Element Table (v go-live) Page 8 of 305

9 Schema (BidResult_v2.xsd) Schema (BidResult_v3.xsd) Schema (CB_BidResult_v xsd) Schema (CB_BidResult_v1.xsd) Fault Return Submit External Forecast Business Scenario Service Level Agreement Use Model Operation Details WSDL (submitenergyforecast_v1.wsdl) ( this has version used with FERC Minute Market FMM) Submit Energy Forecast Element Table External Energy Forecast v1 Response Element Table Retrieve External Energy Business Scenario Request Energy Forecast Results Element Table Energy Forecast Results Element Table Submit BaseSchedule Business Scenario Service Level Agreement Use Model Operation Details WSDL (BaseSchedule_v1.wsdl) ( this has version used with FNM / EIM) Submit BaseSchedule Element Table BaseSchedule v1 Response Element Table Retrieve BaseSchedule Business Scenario Request BaseScheduleTestResults Element Table Page 9 of 305

10 8.3 BalancingTestResults Element Table Samples Submit Bid xml Sample v3 DAM Submit Bid xml Sample v2 DAM Submit Bid xml Sample v3 RTM Submit Bid xml Sample v2 RTM Submit Energy Forecast xml Sample Energy Forecast Request xml Sample Base Schedule Request xml Sample Current Bid Retrieval Request xml Sample Base Schedule Test Results Retrieval Request xml Sample Page 10 of 305

11 1 Introduction 1.1 Purpose This document describes the Market Participant interface to CAISO s dal Market Bidding Services. It provides the WSDL, XSD, and XML information required by application programmers to create and send messages and to process response messages. 1.2 Contact Information For any questions regarding this document or technical questions related to integrating applications with CAISO s dal Market web services, please send to wtamblyn@caiso.com 1.3 Release tes for Bidding Services version 11.5 Change from 11.4 to 11.5 Update xml example for Wheeling. Change from 11.3 to 11.4 Update xml examples and data usage for Transaction based bids. Added endpoints for BaseSchedule in BSAP. Change from 11.2 to 11.3 Updated 5 services (3 for CB and 2 for Base Schedule) For BaseSchedule_v1 and BaseScheduleResults_v1 the below was added. InterTieBaseSchedule/BaseSchedulingCoordinator/mrid - add For CB_BidResult_v1, CB_CleanBidSet_v1, and CB_RawBidSet_v1 the below were changed. MessageHeader/IncPayloadFlag - add, optional MessageHeader/lastBroadcasted - add, optional MessageHeader/BroadcastSequenceNum - add, optional VirtualBid/SchedulingPoint/mrid - remove VirtualBid/Flowgate/mrid - add, optional Updated element tables to add the BaseSchedulingCoordinator it is in the xsd but was missed on the Element tables. Change from 11.1 to 11.2 Updates to the BaseSchedule and BaseScheduleResults have been made to the below list on the xsd. Element GeneratingBaseSchedule/startTime added Element GeneratingBaseSchedule/stopTime added Element InterTieBaseSchedule/startTime added Element InterTieBaseSchedule/stopTime added Page 11 of 305

12 Element sequenceidentifier was replaced with purchaseserviceentity. Element PrimaryFlowGate was replaced with PrimaryFlowgate Element AlternateSchedulingPoint was replaced with SecondaryFlowgate. Optional MessageHeader elements were added but will not be used by submission. Change from 10.4 to 11.1 Updated existing Energy Forecast for new RequestEnergyForecastResults.xsd and EnergyForecastResults.xsd, this will allow retrieves to pull back Energy Forecast status and messages on submitted Energy Forecasts. All bid services will be updated to encorporate the new functionality introduced with the Energy Imbalanced Market (EIM) and the Full Network Model (FNM) to define transaction IDs for Import and Exports. There are new web services for BaseSchedule submission and retrieval for EIM. Imports either with RA or ETC/TOR contracts and Exports with ETC/TOR contracts will remain as a registered resource in Master File. SIBR will create the resource transaction ID (the dynamic name) for scheduling points (import and export) for non-registered resources with all necessary attributes. This will streamline both Internal resource and Import/export bid identifier. Removed Registered Flag on RawBid (was in the original document, this is not used in submission of bids under Intertie and also the Wheeling Resource.) Added Intertie Wheeling Resource data in the BidResults that was not there on the original post. update some required fields to no in Baseschedule. te: This single document will be used for both the Physical Bids,Convergence Bids and also the Energy Forecast and Base Self-Schedules. Only two versions of the services will be supported, for SIBR all services will either have a namespace of v1, v2 or v3. The version element within the schema will define which release it is associated with. 1.4 Namespace Matrix for Physical Bids The below services will be supported: (v2 for FERC764, v3 for EIM/FNM) TargetNamespace (wsdl) Xmlns (xsd) /RawBidSet_v2.xsd /submitrawbidset_v2.wsdl /RequestBidResults.xsd /StandardAttachmentInfor.xsd Page 12 of 305

13 /StandardOutput.xsd /BidResult_v2.xsd /retrievecurrentbidresults_v2.wsdl /RequestBidResults.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd /CleanBidSet_v2.xsd /retrievecleanbidset_v2.wsdl /RequestCleanBidSet.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd Supported web services in addition to the new version. TargetNamespace (wsdl) Xmlns (xsd) /RawBidSet_v3.xsd /submitrawbidset_v3.wsdl /RequestBidResults.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd /BidResult_v3.xsd /retrievecurrentbidresults_v3.wsdl /RequestBidResults.xsd /StandardAttachmentInfor.xsd Page 13 of 305

14 /StandardOutput.xsd /CleanBidSet_v3.xsd /retrievecleanbidset_v3.wsdl /RequestCleanBidSet.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd The following Bid web services will no longer be supported (deprecated) when the Fall 2014 version is released. TargetNamespace (version) v1 submitrawbidset deprecated with the introduction of the Opportunity Cost change for Pay For Performance. V1 BidResults deprecated with the introduction of the change for Pay For Performance. V1 CleanBidSet deprecated with the introduction of the change for the Pay For Performance. 1.5 Namespace Matrix for Convergence Bids (CB) To be used in conjunction with the CB elements for Convergence Bids. Since this is only the second version of the services there will be no deprecated services for CB web services. TargetNamespace (wsdl) /submitCBRawBidSet_v wsdl Xmlns (xsd) /CB_RawBidSet_v xsd Page 14 of 305

15 /StandardAttachmentInfor.xsd /SubmitStandardOutput_v xsd /StandardOutput.xsd /CB_BidResult_v xsd //retrieveCBCurrentBidResults_v /RequestCBBidResults.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd /CB_CleanBid_v xsd /retrieveCBCleanBidSet_v wsdl /RequestCBCleanBidSet.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd TargetNamespace (wsdl) Xmlns (xsd) /CB_RawBidSet_v1xsd /submitcbrawbidset_v1.wsdl /StandardAttachmentInfor.xsd /SubmitStandardOutput_v1.xsd /StandardOutput.xsd /CB_BidResult_v1.xsd /retrievecbcurrentbidresults_v //RequestCBBidResults.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd /CB_CleanBid_v1.xsd /retrievecbcleanbidset_v1.wsdl //RequestCBCleanBidSet.xsd /StandardAttachmentInfor.xsd /StandardOutput.xsd Page 15 of 305

16 1.6 SIBR End Points Please refer to the System Access Information for Market Participants document that is posted at the below location: Related Documents CAISO s CAISO s dal Market has produced a set of documents describing its web services architecture and associated interfaces to the Bidding, Market Results, and Sandbox Services. Market Participants and their application programmers should read this document to gain an overall understanding of CASIO s web services architecture prior to reading any of the detailed documents shown below. The CAISO Web Services Interface Specification Document Set is available online at the locations indicated below. Doc.. Document Name Location B2B Security Specification ISO System Access and Security Information SIBR Technical Specifications located in : Scheduling Infrastructure Business Rules (SIBR) Bidding CAISO Interface Specification for Market Results Services must have a valid certificate to retrieve from the Market Participant Portal (MPP). Security/B2B Security Requirements.pdf onaccess/default.aspx Page 16 of 305

17 2 Submit Raw Bid (includes CB) 2.1 Business Scenario Scheduling Coordinators submit bid data, trading and scheduling activity data on behalf of market participants who wish to participate in the CAISO Day Ahead, Real Time, and Convergenge Bidding markets. SIBR also supports the Energy Forecast Submission and Base Self-Schedule submissions. While some Scheduling Coordinators submit their bid data through the SIBR portal manually, most Scheduling Coordinators submit their bid data in batch mode through an automated process. To meet the needs for submission of raw bid data from Scheduling Coordinators, two processes can be followed for manual and batch mode, respectively: 1) Portal Process In this process the submission is made via a CAISO Web Portal. Scheduling Coordinators submit bid data through the portal automatically using a proxy application implemented at the portal. The proxy will send the data to SIBR for submission. Using the SIBR portal, Scheduling Coordinators can upload XML files, submit bids, and submit bids via portfolios, which is a collection of bids created by the user and saved for submittal at a later time. 2) Direct Link Process In this case, a Scheduling Coordinator directly invokes the submitrawbidset service or the submitcbrawbidset service that resides in CAISO domain using a security mechanism. This process involves submitting raw bid xml payloads via the CAISO web service interface, but does not preclude the use of a client application for automating the process of invoking the web service The direct link can only be established if a Scheduling Coordinator application knows the concrete information to invoke the SIBR raw bid submit Web services. Since a Scheduling Coordinator application is usually outside of the CAISO firewall, a certain security mechanism shall be implemented for the process. The Scheduling Coordinator applications shall be also responsible for an XML validation prior to a data submission. Page 17 of 305

18 2.2 Service Level Agreement The following service level agreement defines the business and technical requirements for service availability and performance. Service availability Service level goal is 99.9%. Expected size of payload (average and maximum) Expected frequency (average and maximum) Longest time the service can be unavailable before business is impacted Business impact if is unavailable Expected response time for the service Expected time to exchange (AVG # of bids) to (500+ maximum bids) times size of one bid. At least once an hour per Schedule Coordinator utilizing the service for RTM, and several times prior to DAM closing 10:00 AM per SC. [to be determined] Schedule Coordinators utilizing the service may not complete submitting all their bids [to be determined] [to be determined] 2.3 Use Model The sequence diagram below describes the service interactions between Scheduling Coordinators and SIBR system in a direct link submission process. The data exchange follows CAISO SOA Submit messaging pattern. In this pattern, the data source system is the Scheduling Coordinator who initiates a data transaction by invoking a submitrawbidset service provided by SIBR. The consumer of the Web service is Scheduling Coordinator or a Web portal. The consumer makes request to SIBR with raw bid data by invoking the submit Web service. The SIBR system is the provider of the Web service. The following steps are involved in the submission process: 1) Scheduling Coordinator has the raw bid data set ready in XML format 2) Scheduling Coordinator validates the data set based on the XML schema 3) Scheduling Coordinator invokes the submitrawbidset Web service or the submitcbrawbidset Web service directly to send a request to SIBR with the raw bid data set 4) SIBR returns an acknowledge message back to Scheduling Coordinator. Page 18 of 305

19 : Scheduling Coordinator : submitrawbitset : SIBR Prepare Raw Bids Raw Bid Data XML Validation submitrawbidsetrequest submitrawbidsetresponse Submit bid 2.4 Operation Details The Physical bid service has one operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD submitrawbidset Input SubmitRawBidSet Request Output SubmitRawBidSet Response submitrawbidset_v3.w sdl submitrawbidset_v2.w sdl RawBidSet_v3.xsd RawBidSet_v2.xsd SubmitStandardOutput. xsd Fault faultreturntype StandardOutput.xsd The Convergence Bid service has one operation with three message types. All input and output messages are in XML format Operation Message Types Message WSDL XSD Page 19 of 305

20 submitcbrawbid Set Input SubmitCBRawBidS et Request submitcbrawbidset_v wsdl submitcbrawbidset_v 1.wsdl CB_RawBidSet_v xsd CB_RawBidSet_v1.xsd (not supported for FALL 2014 release.) Output SubmitCBRawBidS et Response SubmitStandardOutput_ v xsd Fault faultreturntype StandardOutput.xsd Page 20 of 305

21 2.5 WSDL (submitrawbidset_v3.wsdl) ( this has version used with FNM) Please review the Technical Interface Specifications for SIBR Bidding under the appropriate header for related WSDL and XSD references WSDL (submitrawbidset_v2.wsdl) ( this has version to be used with Bid/Dispatch Option) WSDL (submitcbrawbidset_v1.wsdl) (CB) WSDL (submitcbrawbidset_v1.wsdl) (CB) ( this has version this version has changes to align with new CIM schema generation to be consistent with the RawBidSet) (not supported for FALL 2014 release.) 2.8 WSDL (submitcbrawbidset_v wsdl) (CB) This is the current supported version Date Time Data Type Format The datetime data type is used to specify a date and a time on the SIBR web services. The datetime is specified in the following form "YYYY-MM-DDThh:mm:ss" where: YYYY indicates the year MM indicates the month DD indicates the day T indicates the start of the required time section hh indicates the hour mm indicates the minute ss indicates the second te: All components are required. To specify a time zone, you can either enter a datetime in Universal Time Coordinate (UTC) time by adding a "Z" behind the time, for example: Page 21 of 305

22 <startdate> t07:00:00z</startdate> Or <starttime> t07:00: :00</starttime> <stoptime> t07:00: :00</stoptime> <markettype>dam</markettype> or you can specify an offset from the UTC time by adding a positive or negative time behind the time, for example: With 7 hour off-set for PDT <starttime> t00:00: :00</starttime> <stoptime> t00:00: :00</stoptime> <markettype>dam</markettype> <BidSchedule> (same logic applies to the timeintervalstart and End). <timeintervalstart> t07:00: <timeintervalend> t07:00: Or an offset can be applied With 8 hour off-set for PST. <starttime> t00:00: :00</starttime> <stoptime> t00:00: :00</stoptime> <markettype>dam</markettype> Offset of the UTC time is usefull when coordinating Daylight Saving Time (DST) changes Standard Attachment Information The attachment information schema, StandardAttachmentInfor.xsd, is used to provide general information for an SOAP attachment. The root element in the schema is standardattachmentinfor, which can contain one or more attachment elements Element table Element Data Description Type Req d id Globally unique identifier. name Attachment filename. description Description of attachment. version Version ID of attachment file sequencenumber Sequence number if there are multiple attachments. Page 22 of 305

23 Element Data Description Type Req d type Attachment file type, such as zip or jpeg. size Size of attachment file. source Source of attachment file. tool Tool used to generate attachment. creationtime Time attachment file was created. datetime compressflag Indicates whether or not attachment has been compressed (YES or NO). compressmethod Compress method used (if attachment file compressed). AttributeList.Sequence Attribute list sequence number. AttributeList.Name Name of an attribute AttributeList.Value Value of an attribute Schema (StandardAttachmentInfor.xsd) Please review the Technical Interface Specifications for SIBR Bidding under the appropriate header for related WSDL and XSD references. (Convergence Bidding under Current Initiatives) Example XML File (StandardAttachmentInfor.xml) <?xml version="1.0" encoding="utf-8"?> <!-- Sample XML file generated by XMLSpy v2006 U ( --> <standardattachmentinfor xmlns=" 13/StandardAttachmentInfor.xsd" xmlns:xsi=" xsi:schemalocation=" 13/StandardAttachmentInfor.xsd"> <Attachment> <id> (assigned by SIBR)</id> <name>gwed_11</name> <description>bid_attachement</description> <version>1.1</version> <sequencenumber>12</sequencenumber> <type>zip</type> <size>180</size> <source>gwed</source> <tool>gzip</tool> <creationtime> t09:30:47.0z</creationtime> Page 23 of 305

24 <compressflag>yes</compressflag> <compressmethod>zip</compressmethod> <AttributeList> <Sequence>2</Sequence> <Name>GWED</Name> <Value>1</Value> </AttributeList> </Attachment> </standardattachmentinfor> Page 24 of 305

25 2.11 SubmitRawBidSet Element Table (v3 service newest to encorporate the FNM changes. ) Element Data Description Type Req d Message Header (header is optional) TimeDate The datetime, in GMT, when the payload is published. datetime Source The source of published data. Version Defined version for the xsd. Default is defined as: v for v3. IncPayloadFlag (these elements will not be utilized in SIBR) / lastbroadcasted (these elements will not be utilized in SIBR) datetime BroadcastSequenceNum (these elements will not be utilized in SIBR) integer Message Payload GeneratingBid description Description of generating bid. (1-32 characters) mrid Unique identifier for transaction not used in submission, this identifier is returned in the response file for bids submitted through the API. name Unique name for generating bid. (1-32 characters) markettype The market type, DAM or RTM. starttime Start time and date of the trading period for which bid applies. datetime stoptime Stop time and date of the trading period for which bid applies. datetime HourlyParameters.biddableCapa citylimit This is a MW quantity that limits the capacity to be used during optimization. SIBR rules inforce submitted quantity, if none submitted default will be used. HourlyParameters.biddableCapa citylimittype Enumerations are: GEN_CAPACITY_LIMIT (used for Generators and NGR resources under Gen condition) LOAD_CAPACITY_LIMIT (used for NGR resources in Load Condition) Page 25 of 305

26 Element Data Description Type Req d HourlyParameters.resourceBidO ption RTM Only te: Bid Option is for TG (Tie-Gen) in GeneratingBid Resources registered with Hourly flag must use Hourly or Once. If no data is submitted, the default will be used. For Real Time Market only: Valid values are: HOURLY (default for Hourly Pre-dispatch) ONCE 15MIN (default for non-hourly Pre-dispatch) DYNAMIC (default for Dynamic resources) Resources registered as Dynamic must use Dynamic. HourlyParameters.timeIntervalEn d End of the time interval in which bid is valid (yyyymm-dd hh24: mi: ss). datetime HourlyParameters.timeIntervalSt art Start of the time interval in which bid is valid (yyyymm-dd hh24: mi: ss). datetime ProductBid.description Description of Product Bid. (1-32 characters) ProductBid.BidDistributionFactor This element is only applicable to Aggregate resource submitting a GDF. ProductBid.BidDistributionFactor. description Description of Bid Distribution Factor. (1-32 characters) ProductBid.BidDistributionFactor. timeintervalend End of the time interval of the operating hour for which the GDF applies. The start and end time must be aligned with the start and end time specified for the Energy Bid. datetime ProductBid.BidDistributionFactor. timeintervalstart Start of the time interval of the operating hour for which the GDF applies. The start and end time must be aligned with the start and end time specified for the Energy Bid. datetime ProductBid.BidDistributionFactor. PnodeDistributionFactor Required element if Distribution Factor is included in the bid. ProductBid.BidDistributionFactor. PnodeDistributionFactor.factor Used to calculate participation of Pnode in an AggregatePnode. For example, for regulation region this factor is 1 and total sum of all factors for a specific regulation region does not have to be 1. For pricing zone the total sum of all factors has to value must be => 0 and <= 1 float ProductBid.BidDistributionFactor. PnodeDistributionFactor. IndividualPnode.mrid Individual Pnode name (1-32 characters) (these are CNODE names associated with the aggregate resource to determine which set will be used for the aggregate to determine the distribution factor. ProductBid.BidSchedule Energy Bid Component is optional. Page 26 of 305

27 Element Data Description Type Req d ProductBid.BidSchedule. description Description of Bid Schedule. (1-32 characters) ProductBid.BidSchedule. timeintervalend End of the time interval for the operating hour for which the bid is being submitted. datetime ProductBid.BidSchedule. timeintervalstart Start of the time interval for the operating hour for the which the bid is being submitted. datetime ProductBid.BidSchedule. BidPriceCurve Used when submitting an Economic Bid for a resource. ProductBid.BidSchedule. BidPriceCurve.description ProductBid.BidSchedule. BidPriceCurve.mrid Description of Bid Price Curve. (1-32 characters) Unique identifier for price curve ProductBid.BidSchedule. BidPriceCurve.CurveScheduleDa tascurvescheduledatas.xaxisda ta The MW value specified on the price curve. Or MW AS Capacity for AS. float for EN and AS ProductBid.BidSchedule.BidPrice Curve.CurveScheduleDatasCurv escheduledatas. y1axisdata The dollar ($) value specified on the price curve.. A price curve segment consist of both the Mw value and the dollar value. float Pattern value = [-+]?[\d]+\.?\d?\d? ProductBid.BidSchedule.BidPrice Curve.CurveScheduleDatasCurv escheduledatas. y2axisdata The Opportunity Cost associated with Regulation (both RU and RD). float for RU RD ProductBid.BidSelfSched Self Schedule Bid Component is optional. description Description of Bid Self Sched. (1-32 characters) timeintervalend End of the time interval for the operating hour for which the bid is being submitted. datetime timeintervalstart Start of the time interval for the operating hour for which the bid is being submitted. datetime pumpselfschedmw Pumping self schedule quantity. If this value is not null, then the unit is considered to be in pumping mode. Float selfschedmw MW value for the specified Self Schedule Product Types other than Pumping Self Schedule Type (PT, ETC, TOR, LSS, GSS, LSG or LSS. float selfsch edsptresource Generating Resource named in the PT Export that supplies non-ra energy for Export. Page 27 of 305

28 Element Data Description Type Req d wheeli ngtransactionreference A unique identifier of a Wheeling Transaction. A wheeling transaction is a balanced Energy exchange among Supply and Demand Resources (Resources must be registered with an Energy Type of WHL in order to submit a Wheeling Transaction. All Wheeling Transactions must be accompanied by either an Energy Bid or Self- Schedule [PT, LPT, ETC, TOR]) (For v3 service this element is ignored, wheeling in v3 service uses the WheelingResource element. Due to the CIM this is retained beause it is used in the retrieves to be backward compatible to be able to use the v3 retrieve and pull back bids submitted with v2 services or through UI. ContractRight Required for Self Schedule type ETC, TOR, RMT ContractRight.description Description of Contrac tright. (1-32 characters) ContractRight.mrid Contract Reference Name (CRN) (1-32 characters) ProductBid.MarketProduct. description Description of Market Product. (1-32 characters) ProductBid.MarketProduct. marketproducttype Market product type. Valid values are: RC product is for DAM bids only. EN RU RD SR NR RC RMU RMD LFU LFD Energy type Regulaion up Regulaion down spinning reserve n-spinning reserve Residual Unit Commitment - Regulation Mileage Up (v1 only) - Regulation Mileage Down (v1 only) Load Following Up Load Following Down Please refer to section 2.11 for appropriate combination of Product Type and SelfSchedule Type Page 28 of 305

29 Element Data Description Type Req d ProductBid.MarketProduct. selfschedtype Self schedule bid contract type. Valid values are: LSG is for LSG resource only LPT is export only RA is not recognized on submitted bids. (This would be a returned value in a retrieve for an Import that has RA.) PT Price Taker ETC Existing transmission contract TOR Transmission ownership right RMT Regulatory Must Take SP Self Provision (AS only) LOF Lay Off Self Schedule WHL Wheeling Transaction LSG Load Serving Generator (Partial QF initiative) RA Resource Adequacy (not a submitted element) LPT Lower Price Taker (Export only)ifm DA AS for RTM (not a submitted element) GSS Generating Self Schedule (NGR) (future use, currently not recognized) LSS Load Self Schedule (NGR) (future use) ProductBid.UnitSchedule Needed when submitting Pumping Level, Pumping Cost, Pumping Shutdown Cost ProductBid.UnitSchedule. parameterid NERC_TAG and SCHEDULING_POINT are reserved for future use and serve no functional use at this time. These would be for Intertie bids. Parameter ID. Valid values are: PUMPING_LEVEL PUMPING_COST PUMPING_SHUTDOWN_COST NERC_TAG SCHEDULING_POINT ProductBid.UnitSchedule. parametervalue If ProductBid.UnitSchedule = STRING then value = YES. Else value = NO. This should be used if the parameter type is STRING Page 29 of 305

30 Element Data Description Type Req d ProductBid.UnitSchedule. parametertype Indication of the type of parameter being defined (STRING or FLOAT) which should be used in conjunction with the parameterid chosen. PUMPING_LEVEL (FLOAT) PUMPING_COST (FLOAT) PUMPING_SHUTDOWN_COST (FLOAT) ProductBid.UnitSchedule. parametervalue Parameter value to be used with associated parametertype which replaces corresponding default values from input bid data. This hould be used if the parameter type is FLOAT float ProductBid.UnitSchedule. timeintervalend Start of the time interval for the operating hour for which the bid is being submitted. datetime ProductBid.UnitSchedule. timeintervalstart End of the time interval for the operating hour for which the bid is being submitted. datetime SchedulingCoordinator.mrid Scheduling Coordinator Identifier. (1-32 characters) contingencyavailflag DAM bids only Contingent operating reserve availiability. Valid value = YES or NO. * required when submitting Day Ahead Ancillary Service bid* te for MSG, this flag needs to be on all configurations and must be consistent (it is validated at the resource level). Resource is available to participate with capacity only in contingency dispatch. energymaxday DAM bids only Maximum amount of energy per day which can be produced during the trading period in MWh. Float energyminday DAM bids only Minimum amount of energy per day which has to be produced during the trading period in MWh. Float curtailmentenergylimit Maximum energy (MWh) left can be curtailed for the Dispatchable Demand Resource (this element is a place-holder for future use) Float greenhousegasadder Green House Gas adder for EIM participating resources. Float This is a daily value. If provided in DAM bid, RTM bids will use the curve from the DAM Clean Bid where the adder was applied. Page 30 of 305

31 Element Data Description Type Req d lowerchargelimit Lowest stored energy (MWh) that should be maintained in the LESR device Float noloadcost Resource fixed no load cost. Float startupramptime Start Up Ramp Time Float if used with MSG stateofcharge Actual stored Energy (MWh) that should be allowed in the LESR device (this element is a place-holder for future use) Float upperchargelimit Highest stored energy (MWh) that should be allowed in the LESR device Float RampRateCurve Curve for Ramp (based on type of Ramp) RampRateCurve.description Description of the object. RampRateCurve.CurveSchedule Datas. The data point values for a Ramp Curve RampRateCurve.CurveSchedule Datas.xAxisData RampRateCurve.CurveSchedule Datas.y1AxisData Operational Level Float Ramp Rate Float if Ramp data is supplied if Ramp data is supplied RampRateCurve.rampRateType Type of Ramp, Operational, Operating Reserve or for Regulation. Enumerations: (OP, OP_RES, REG.) t currently used: INTERTIE, LD_DROP, LD_PICKUP if Ramp data is supplied RegisteredGenerator.mrid Name of the registered Generating Resource(1-32 characters) RegisteredGenerator.Configurati on Configuration in which a MSG resource (CCGT resource or generating units with multiple operating units) can operate. if used with MSG Page 31 of 305

32 Element Data Description Type Req d RegisteredGenerator.Configurati on.mrid Configuration in which a MSG resource (CCGT resource or generating units with multiple operating units) can operate. if used with MSG StartUpCostCurve StartUpCostCurve.description Description of Start Up Cost Curve. (1-32 characters) StartUpCostCurve.CurveSched Datas.xAxisData The data value of the X-axis variable is represented as Cooling time in minutes. float StartUpCostCurve.CurveSched Datas.y1AxisData The data value of the Y-axis variable, is represented as the Cost ($) value. float StartUpTimeCurve StartUpTimeCurve.description Description of Start Up Time Curve. (1-32 characters) StartUpTimeCurve.CurveSched Datas.xAxisData The data value of the X-axis variable is represented as Cooling time in minutes. float StartUpTimeCurve.CurveSched Datas.y1AxisData The data value of the Y-axis variable is represented as Startup time in minutes float Transition Transition.notificationTime MSG bids only Time in minutes the 'To-Configuration ID' requires before deployment. tification time includes transition ramp time float if used with MSG Transition.transitionCost MSG bids only Cost of moving from 'From-Configuration ID' to 'To- Configuration ID' float if used with MSG Transition.transitionRampTime MSG bids only Time in minutes it takes to ramp from 'From- Configuration ID' to 'To-Configuration ID' float if used with MSG Transition.FromConfiguration MSG bids only Configuration in which a MSG resource (CCGT resource or generating units with multiple operating units) can operate. (currently in) if used with MSG Page 32 of 305

33 Element Data Description Type Req d Transition.ToConfiguration MSG bids only Configuration in which a MSG resource (CCGT resource or generating units with multiple operating units) can operate. (going to) if used with MSG InterTieBid description Description of intertie bid. (1-32 characters) mrid Unique identifier for transaction not used in submission, this identifier is returned in the response file for bids submitted through the API. name Unique name of intertie bid. (1-32 characters) markettype The market type, DAM or RTM. starttime Start time and date for which bid applies. datetime stoptime Stop time and date for which bid is applies. datetime HourlyParameters.resourceBidO ption If no data is submitted, the default will be used. For Real Time Market only: RTM Only Resources registered with Hourly flag must use Hourly or Once. HOURLY (default for Hourly Pre-dispatch) ONCE 15MIN (default for non-hourly Pre-dispatch) DYNAMIC (default for Dynamic resources) Resources registered as Dynamic must use Dynamic. HourlyParameters.timeIntervalEn d End of the time interval in which bid is valid (yyyymm-dd hh24: mi: ss). datetime HourlyParameters.timeIntervalSt art Start of the time interval in which bid is valid (yyyymm-dd hh24: mi: ss). datetime ProductBid.description Description of product bid. (1-32 characters) ProductBid.BidSchedule Energy Bid Component is optional ProductBid.BidSchedule. description Description of Bid Schedule. (1-32 characters) ProductBid.BidSchedule. timeintervalend End of the time interval for the operating hour for which the bid is being submitted. datetime ProductBid.BidSchedule. timeintervalstart Start of the time interval for the operating hour for which the bid is being submitted.. datetime Page 33 of 305

34 Element Data Description Type Req d ProductBid.BidSchedule. BidPriceCurve Used when submitting an Economic Bid for a resource. ProductBid.BidSchedule. BidPriceCurve.description ProductBid.BidSchedule. BidPriceCurve. CurveScheduleDatas.xAxisData Description of Bid Price Curve. (1-32 characters) The MW value specified on the price curve. float ProductBid.BidSchedule.BidPrice Curve.CurveScheduleDatas. y1axisdata The dollar ($) value specified on the price curve. A price curve segment consist of both the Mw value and the dollar value. float Pattern value = [-+]?[\d]+\.?\d?\d? ProductBid.BidSelfSched Self Schedule Bid Component is optional description Description of bid self schedule (1-32 characters) timeintervalend End of the time interval for the operating hour for which the bid is being submitted. datetime timeintervalstart Start of the time interval for the operating hour for which the bid is being submitted. datetime selfschedmw Self Schedule MW for the referenced commodity. float wheeli ngtransactionreference A unique identifier of a Wheeling Transaction. A wheeling transaction is a balanced Energy exchange among Supply and Demand Resources (Resources must be registered with an Energy Type of WHL in order to submit a Wheeling Transaction.) All Wheeling Transactions must be accompanied by either an Energy Bid or Self- Schedule [PT, LPT, ETC, TOR]) (For v3 service this element is ignored, wheeling in v3 service uses the WheelingResource element. Due to the CIM this is retained beause it is used in the retrieves to be backward compatible to be able to use the v3 retrieve and pull back bids submitted with v2 services or through UI. ProductBid/BidSelfSched/selfSch edsptresource Valid Generating Resource specified in the PT Export Self Sched as the Support Resource ContractRight Required for Self Schedule type ETC, TOR, RMT Page 34 of 305

35 Element Data Description Type Req d ContractRight.description Description of contract right. (1-32 characters) ContractRight.mrid Contract Reference Name (CRN) (1-32 characters) ProductBid.MarketProduct. description Description of market product. (1-32 characters) ProductBid.MarketProduct. marketproducttype Market product type. Valid values are: EN is currently the only support Product type for Intertie bids. EN Energy type System Resources that are registered as TG are considered as a Generating Bid.) RC is not a biddable type for Interties. RU Regulaion up RD Regulaion down SR spinning reserve NR - n-spinning reserve RC Residual Unit Commitment Please refer to section 2.11 for appropriate combination of Product Type and SelfSchedule Type Page 35 of 305

36 Element Data Description Type Req d ProductBid.MarketProduct. selfschedtype Self schedule bid contract type. Valid values are: te: LPT is export only PT Price Taker LPT Lower Price Taker (Export only) ETC Existing transmission contract SP is not supported currently for Interties. RA is not recognized on submitted bids. (This would be a returned value in a retrieve for an Import that has RA.) TOR Transmission ownership right LOF Lay Off Self Schedule WHL Wheeling Transaction (For v3 service this element is ignored, wheeling in v3 service uses the WheelingResource element. IFM is a returned value in Real-Time Clean bids for any Day-Ahead Award. Due to the CIM this is retained beause it is used in the retrieves to be backward compatible to be able to use the v3 retrieve and pull back bids submitted with v2 services or through UI. RA Resource Adequacy (not a submitted element) IFM DA AS for RTM (not a submitted element) SP Self Provision (AS only) RMT Regulatory Must Take LSG Load Serving Generator (Partial QF initiative) GSS Generating Self Schedule (NGR) (future use, currently not recognized) LSS Load Self Schedule (NGR) (future use) ProductBid.UnitSchedule Needed when submitting Pumping Level, Pumping Cost, Pumping Shutdown Cost ProductBid.UnitSchedule. parameterid NERC_TAG and SCHEDULING_POINT are reserved for future use and serve no functional use at this time. For Interties, currently no UnitSchedule is needed as part of the bid. The IDs below are support in the xsd for possible future use. NERC TAG SCHEDULING POINT PUMPING_LEVEL PUMPING_COST PUMPING_SHUTDOWN_COST Page 36 of 305

37 Element Data Description Type Req d ProductBid.UnitSchedule. parametervalue If ProductBid.UnitSchedule = STRING then value = YES. Else value = NO. This should be used if the parameter type is STRING ProductBid.UnitSchedule. parametertype Indication of the type of parameter being defined (STRING or FLOAT) which should be used in conjunction with the parameterid chosen. PUMPING_LEVEL (FLOAT) PUMPING_COST (FLOAT) PUMPING_SHUTDOWN_COST (FLOAT) NERC TAG (STRING) SCHEDULING POINT (STRING) Parameter Type ProductBid.UnitSchedule. parametervalue Parameter value to be used with associated parametertype which replaces corresponding default values from input bid data. This hould be used if the parameter type is FLOAT float ProductBid.UnitSchedule. timeintervalend Start of the time interval for the operating hour for which the bid is being submitted. datetime ProductBid.UnitSchedule. timeintervalstart End of the time interval for the operating hour for which the bid is being submitted. datetime SchedulingCoordinator.mrid Scheduling Coordinator Identifier. (1-32 characters) contingencyavailflag DAM bids only te: This is not supported currently for Intertie bids. Contingent operating reserve availiability. Valid value = YES or NO. Resource is availiable to participate with capacity only in contingency dispatch. This is an optional element, but required when submitting Day Ahead Ancillary Service bid. MinHourlyBlock The Registered upper bound of MHB for an Inter- Tie Resource (1 to 24 can be used, 1 being the most flexible ) (if not specified a value of 1 is set) integer RampRateCurve This is not supported currently for Intertie bids. Curve for Ramp (based on type of Ramp) reserved for future use and serves no functional use at this time. RampRateCurve.description Description of the object. Page 37 of 305