ISO Interface Specification Customer Interface For Resource Adequacy(CIRA) Document Version: 2.1
Date Created: 8/16/2015
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 1 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
Location of Document
Revision History Date
Version
Description
Author
8/16/2015 4/1/2016 4/1/2016
1.0 2.0 2.1
Document creation Updated to add new service Fixed Namespaces in Example files for RequestResourceCapacityData_v1 and ResourceAdequacyCapacityDataresults _v1 XSDs
Sunil Nallagangu Arul Jayaraman Sunil Nallagangu
Versioning should be as follows: 1. Draft – When a document is still in its developing stages and is not ready for review and sign off. 2. V 0.n – When changes are made before the document is ready for initial review. 3. V 1.0 – When a document is ready for review and sign off. It remains as v 1.0 after sign off if no changes are made. 4. V 1.n – When changes are made after the initial review. “n” represents the number of iterations of changes until the official signoff. 5. V 2.0 – When additional changes are requested after initial sign off and Change Request is approved. The Change Request that initiated the revision must be referenced in the Revision History Description. 6. V2.n – When changes are made after the second sign off where the changes do not affect downstream/related documents or system code (i.e.: grammar changes, etc.)
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 2 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
Table of Contents CUSTOMER INTERFACE FOR RESOURCE ADEQUACY(CIRA) ....................................................................... 1 DOCUMENT VERSION: 2 ............................................................................................................................................. 1 DATE CREATED: 8/16/2015 .......................................................................................................................................... 1 LOCATION OF DOCUMENT ....................................................................................................................................... 2 REVISION HISTORY ...................................................................................................................................................... 2 TABLE OF CONTENTS ................................................................................................................................................. 3 1.
INTRODUCTION................................................................................................................................................... 6 1.1 1.2 1.3 1.4 1.5 1.6 1.7
2.
PURPOSE .............................................................................................................................................................. 6 CONTACT INFORMATION ....................................................................................................................................... 6 RELATED DOCUMENTS ......................................................................................................................................... 6 RELEASE NOTES ................................................................................................................................................... 7 API TRANSITION SUPPORT .................................................................................................................................... 7 RPC & DOC STYLE ATTACHMENTS ...................................................................................................................... 7 DATE TIME DATA TYPE ELEMENTS ...................................................................................................................... 8
SOAP HEADER ELEMENTS ............................................................................................................................... 8 2.1 IDENTITY OF MESSAGE PRODUCER ....................................................................................................................... 8 2.1.1 Identity ........................................................................................................................................................ 9 2.1.2 Timestamp ................................................................................................................................................... 9 2.1.3 Message Freshness ..................................................................................................................................... 9
3.
STANDARD XSDS ................................................................................................................................................. 9 3.1 STANDARD ATTACHMENT INFORMATION ............................................................................................................. 9 3.1.1 Element Table ...........................................................................................................................................10 3.1.2 Schema (StandardAttachmentInfor.xsd) ....................................................................................................10 3.1.3 Example XML File (StandardAttachmentInfor.xml) ..................................................................................10 3.2 FAULT RETURN ....................................................................................................................................................11 3.2.1 Element Table ............................................................................................................................................11 3.2.2 Schema (StandardOutput.xsd) ...................................................................................................................12 3.2.3 Example XML File (StandardOutput.xml) .................................................................................................12
4.
SUBMIT CSP OFFERS BUSINESS SCENARIO ..............................................................................................14 4.1 OVERVIEW ...........................................................................................................................................................14 4.2 SERVICE LEVEL AGREEMENT...............................................................................................................................14 4.3 USE MODEL .........................................................................................................................................................14 4.3.1 Submit CSP Offers .....................................................................................................................................14 4.4 OPERATIONAL DETAILS .......................................................................................................................................15 4.4.1 Submit CSP Offers .....................................................................................................................................15 4.5 WSDL .................................................................................................................................................................16 4.5.1 submitCSPOffers_v1.wsdl .........................................................................................................................16 4.5.2 submitCSPOffers_v1_DocAttach.wsdl ......................................................................................................16 4.6 SUBMIT CSP OFFERS REQUEST............................................................................................................................16 4.6.1 Element Table ............................................................................................................................................16 4.6.2 Schema (CSPOfferSet_v1.xsd) ...................................................................................................................17
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 3 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
4.6.3 Example XML File (submitCSPOffersRequest_v1xml) ..............................................................................17 4.6.4 Example XML File (updateCSPOffersRequest_v1.xml) ............................................................................19 4.7 SUBMIT CSP OFFERS RESPONSE ..........................................................................................................................20 4.7.1 Element Table ............................................................................................................................................20 4.7.2 Schema (SubmitStandardOutput_v1.xsd) ..................................................................................................21 4.7.3 Example XML File (submitCSPOffersResponse_v1.xml) ..........................................................................21 4.8 FAULT RETURN ....................................................................................................................................................22 5.
RETRIEVE CSP OFFERS BUSINESS SCENARIO .........................................................................................23 5.1 OVERVIEW ...........................................................................................................................................................23 5.2 SERVICE LEVEL AGREEMENT...............................................................................................................................23 5.3 USE MODEL .........................................................................................................................................................23 5.3.1 Retrieve CSP Offers ...................................................................................................................................23 5.4 OPERATIONAL DETAILS .......................................................................................................................................24 5.4.1 Retrieve CSP Offers ...................................................................................................................................24 5.5 WSDL .................................................................................................................................................................25 5.5.1 retrieveCSPOffers_v1.wsdl ........................................................................................................................25 5.5.2 retrieveCSPOffers_v1_DocAttach.wsdl .....................................................................................................25 5.6 RETRIEVE CSP OFFERS REQUEST ........................................................................................................................25 5.6.1 Element Table ............................................................................................................................................25 5.6.2 Schema (RequestCSPOfferSet_v1.xsd) ......................................................................................................26 5.6.3 Example XML File (retrieveCSPOffersRequest_v1.xml) ...........................................................................26 5.7 RETRIEVE CSP OFFERS RESPONSE.......................................................................................................................27 5.7.1 Element Table ............................................................................................................................................27 5.7.2 Schema (CSPOfferSet_v1.xsd) ...................................................................................................................28 5.7.3 Example XML File (retrieveCSPOffersResults_v1.xml) ............................................................................28 5.8 FAULT RETURN ....................................................................................................................................................30
6.
WITHDRAW CSP OFFERS ................................................................................................................................31 6.1 OVERVIEW ...........................................................................................................................................................31 6.2 SERVICE LEVEL AGREEMENT...............................................................................................................................31 6.3 USE MODEL .........................................................................................................................................................31 6.3.1 Withdraw CSP Offer ..................................................................................................................................31 ..................32 6.4 OPERATIONAL DETAILS .......................................................................................................................................32 6.4.1 Withdraw CSP Offers ................................................................................................................................32 6.5 WSDL .................................................................................................................................................................33 6.5.1 withdrawCSPOffers_v1.wsdl .....................................................................................................................33 6.5.2 withdrawCSPOffers_v1-DocAttach.wsdl ...................................................................................................33 6.6 WITHDRAW CSP OFFERS REQUEST .....................................................................................................................33 6.6.1 Element Table ............................................................................................................................................33 6.6.2 Schema (RequestCSPOfferSet_v1.xsd) ......................................................................................................34 6.6.3 Example XML File (withdrawCSPOffersRequest_v1.xml) ........................................................................34 6.7 WITHDRAW CSP OFFERS RESPONSE ....................................................................................................................34 6.7.1 Element Table ............................................................................................................................................35 6.7.2 Schema (SubmitStandardOutput_v1.xsd) ..................................................................................................35 6.7.3 Example XML File (withdrawCSPOffersResponse_v1.xml) ......................................................................35 6.8 FAULT RETURN ....................................................................................................................................................36
7.
RETRIEVE RESOURCE ADEQUACY CAPACITY DATA ...........................................................................37 7.1
OVERVIEW ...........................................................................................................................................................37
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 4 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.2 SERVICE LEVEL AGREEMENT...............................................................................................................................37 7.3 USE MODEL .........................................................................................................................................................37 7.3.1 Retrieve Resource Adequacy Capacity Data .............................................................................................38 7.4 OPERATIONAL DETAILS .......................................................................................................................................39 7.4.1 Retrieve Resource Adequacy Capacity Data .............................................................................................39 7.5 WSDL .................................................................................................................................................................39 7.5.1 retrieveResourceAdequacyCapacityData_v1.wsdl ....................................................................................39 7.5.2 retrieveResourceAdequacyCapacityData_v1_DocAttach.wsdl .................................................................39 7.6 RETRIEVE RESOURCE ADEQUACY CAPACITY DATA REQUEST.............................................................................39 7.6.1 Element Table ............................................................................................................................................39 7.6.2 Schema (RequestResourceAdequacyCapacityData_v1.xsd) ......................................................................40 7.6.3 Example XML File (requestResourceAdequacyCapacityData_v1.xml) ....................................................40 7.7 RETRIEVE RESOURCE ADEQUACY CAPACITY RESPONSE .....................................................................................41 7.7.1 Element Table ............................................................................................................................................41 7.7.2 Schema (ResourceAdequacyCapacityDataResults_v1.xsd) .......................................................................41 7.7.3 Example XML File (ResourceAdequacyCapacityDataResults_v1.xml) .....................................................42 7.8 FAULT RETURN ....................................................................................................................................................43 8.
ERROR CODES ....................................................................................................................................................44
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 5 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
1. Introduction 1.1 Purpose This document describes the Market Participant interface to CAISO’s Customer Interface for Resource Adequacy(CIRA) web 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 Customer Interface for Resource Adequacy(CIRA) web services, please send email to
[email protected]
1.3 Related Documents CAISO’s ISO MARKET program has produced a set of documents describing its web services architecture and associated interfaces to the Bidding, Market Results, Trades, CSP Offer and Sandbox services. CASIO’s ISO MARKET Web Services Architecture & Integration Specification is the top-level document in this set; 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.
CAISO’s Web Services Architecture & Integration Specification
B2B Security Specification
(CAISO ISS)
Interface Specification for Bidding Services
Client Public/Private Key Instructions (CAISO ISS)
Interface Specification for Inter-SC Trade Services
Interface Specification Customer Interface for Resource Adequacy(CIRA) services. Figure 1 – ISO MARKET Web Services Interface Specification Document Set
Owner: Nallagangu, Sunil
Interface Specification for Market Result Services
Sandbox Services & Test Client Guide
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 6 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
The ISO MARKET Web Services Interface Specification Document Set is available online at the locations indicated below. Doc. No.
Document Name ISO MARKET B2B Security Specification
Location https://mpp.caiso.com/Information%20Security/I SO%20B2B%20Security%20Specification.pdf
1 (you must have access to the Market Participant Portal) 2
Client Public/Private Key Instructions
ClientPublic_PrivateKeyGuidelines.pdf
3
ISO MARKET Interface Specification for Bidding Services
http://www.caiso.com/2350/2350840c5ff70.html
ISO MARKET Interface Specification for Inter-SC Trade Services
http://www.caiso.com/2350/2350a39e27ea0.html
4
ISO MARKET Interface Specification for Market Results Services
http://www.caiso.com/2359/2359b9866b2c0.html
5
6
ISO MARKET Sandbox Services and Test Client Guide
http://www.caiso.com/17bf/17bf9e393f990.html
7
ISO Interface Specification for Competitive Solicitation Process(CSP)
http://www.caiso.com/informed/Pages/Relea sePlanning/Default.aspx
ISO Acceptable Use Guidelines
http://www.caiso.com/Documents/ISO_Servi cesAcceptableUseGuidelinesApr9_2013.pdf
8
1.4 Release Notes This document release 2.0 will be the second release for the Competitive Solicitation Process(CSP), to be released in the 2016.
1.5 API Transition Support Initial Implementation.
1.6 RPC & Doc style Attachments All services support both rpc/literal and document/literal with an attachment (doc-attach). Doc style attachments are supported by WSDLs that have suffix _DocAttach in their name, this Doc style attachment is mainly intended for .Net clients. Example: 1. submitCSPOffers_v1.wsdl supports rpc style . 2. submitCSPOffers_v1_DocAttach.wsdl supports Doc style attachments. Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 7 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
Attachments will be zipped(gzip style of compression) and then Base64 encoded.
1.7 Date Time Data Type Elements The dateTime data type is used to specify a date and a time. 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 + (plus) or - (minus) to specify an offset from the UTC time
Note: All components are required. Sample Timezones supported by CIRA API UTC 2002-05-30T00:00:00Z
Timezone with Offset 2002-05-30T00:00:00+07:00
2. SOAP Header Elements This section specifies how the identity of the message producer and the message signature is specified in the SOAP message header section.
2.1 Identity of Message Producer Identify of the message producer is specified in CAISO custom element encapsulated in . The following fragment illustrates the use of this element
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 8 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
LNP Tester40 3433lfff23 2014-04-22T16:30:45.0 PDT
2.1.1 Identity Identity of the message producer is specified by the element, which allows any string that does not contain line feeds, carriage returns, tabs, leading or trailing spaces, or multiple spaces.
2.1.2 Timestamp The Security Timestamp is encapsulated via the element in the and indicates when the token was created . 2.1.3 Message Freshness This specification uses a Nonce as a measure to thwart replay attacks. The Nonce is a unique, randomly generated number. The nonce is encapsulated via the element in the
3. Standard XSDs 3.1 Standard Attachment Information The attachment information schema, StandardAttachmentInfor.xsd, is used to provide general information for a SOAP attachment. The root element in the schema is standardAttachmentInfor, which can contain one or more attachment elements.
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 9 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
3.1.1 Element Table
Element
Data Description
Type
Req’d
id
Globally unique identifier.
string
No
name
Attachment filename.
string
No
description
Description of attachment.
string
No
version
Version ID of attachment file
string
No
sequenceNumber
Sequence number if there are multiple attachments.
string
No
type
Attachments file type, zip
string
No
size
Size of attachment file.
string
No
source
Source of attachment file.
string
No
tool
Tool used to generate attachment.
string
No
creationTime
Time attachment file was created.
dateTime
No
compressFlag
Indicates whether or not attachment has been compressed (YES or NO).
string
No
compressMethod
Compress method used (if attachment file compressed).
string
No
AttributeList.Sequence
Attribute list sequence number.
string
No
AttributeList.Name
Name of an attribute
string
No
AttributeList.Value
Value of an attribute
string
No
3.1.2 Schema (StandardAttachmentInfor.xsd) Each service bundle will contain the same StandardAttachmentInfor.xsd 3.1.3 Example XML File (StandardAttachmentInfor.xml) Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 10 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
123456789 Out1 CSP_ATTACHEMENT 1.1 12 ZIP 180 GWED GZIP 2006-06-17T09:30:47.0Z yes ZIP 2 GWED 1
3.2 Fault Return Any error in consuming the service will result in the fault return of the standardOutput. This section is applicable to all services. 3.2.1 Element Table Element
Data Description
Type/ Length
Format/ Length
Req’d
OutputDataType.EventLog id
Event log identifier.
string
No
name
Event log name.
string
No
description
Event log description.
string
No
type
Event log type.
string
No
creationTime
Event log creation time.
date
No
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 11 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
Data Description
Date Created: Type/ Length
8/16/2015 Format/ Length
Req’d
collectionType
Event log collection type.
string
No
collectionQuantity
Event log collection quantity.
string
No
Event.result
Event result.
string
No
Event.id
Event identifier.
string
No
Event.name
Event name.
string
No
Event.description
Event description.
string
No
Event.creationTime
Event creation time.
dateTime
No
Event.severity
Event severity.
string
No
Event.priority
Event priority.
string
No
Event.sequence Number
Event sequence number.
string
No
Event.eventType
Event type.
string
No
Service.id
Service identifier.
string
No
Service.name
Service name.
string
No
Service.description
Service description.
string
No
Service.comments
Service comments.
string
No
3.2.2 Schema (StandardOutput.xsd) Each service bundle will have the same StandardOutput.xsd file. 3.2.3 Example XML File (StandardOutput.xml) Event-123 Event Name The Event Description Error Event 2014-01-03T11:00:00Z Submit CSP Offer 1 Invalid Value Found in Field XX 1234 Error Event 1234 An invalid data value was presented Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 12 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
2014-01-03T11:00:00Z High High 1 Initiated by CSP API 1234567 submitCSPOffers_v1 Having problems - Invalid data has been presented Some one needs to fix the data and resubmit
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 13 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
4. Submit CSP Offers Business Scenario 4.1 Overview Scheduling coordinators can submit new CSP Offers or update existing CSP Offers for affiliated resources. Note : This service will be supported in the future release.
4.2 Service Level Agreement Service availability
Service level goal is 99.9%.
Expected size of payload (average and maximum)
TBD
Expected frequency (average and maximum)
Annual CSP Offers once a year. Monthly CSP Offers once a month. Intramonthly CSP Offers once a day. 4 hrs
Longest time the service can be unavailable before business is impacted Business impact if is unavailable Expected response time for the service
CIRA UI provides mechanism to submit/update CSP Offers 5 to 30 secs.
Expected time to exchange
5 to 30 secs.
4.3 Use Model The sequence diagram below describes the service level interactions between the Scheduling Coordinator systems and the CSP. Channel level security and authentication are abstracted from this diagram (They will be covered in another document; B2B Security Specifications). 4.3.1 Submit CSP Offers
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 14 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
4.4 Operational Details 4.4.1 Submit CSP Offers The service has one operation with three message types. Operation
Message Types
Owner: Nallagangu, Sunil
Message
WSDL
XSD
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 15 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification submitCSPOffers
Input Output Fault
submitCSPOffers Request submitCSPOffers Response faultReturnType
Date Created:
submitCSPOffers_v1.wsdl/ submitCSPOffers_v1_DocA ttach.wsdl
8/16/2015
CSPOfferSet_v1.xsd SubmitStandardOutput.xsd StandardOutput.xsd
4.5 WSDL 4.5.1 submitCSPOffers_v1.wsdl 4.5.2 submitCSPOffers_v1_DocAttach.wsdl Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx
4.6 Submit CSP Offers Request 4.6.1 Element Table Element
Data Description
Type/ Length
Req’d
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) CompetitiveSolicitationProcessOfferSet (Required) mRID
Master resource identifier of CSP Offer Set that is generated by CSP. This attribute is not applicable when submitting New CSP Offers
string
No
resourceAdequacy PeriodType
Resource Adequacy Period Type is defined as the timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumeration
Yes
CompetitiveSolicitationProcessOfferSet.offerPeriod (Required) start
Start date of Offering Period in GMT . For ANNUAL offering type it’s first day of the year, for MONTHLY/INTRAMONTHLY it’s first day of the month
dateTime
Yes
end
End Date of Offering Period in GMT . For ANNUAL offering type it’s last day of the year, for MONTHLY/INTRAMONTHLY it’s last day of the month
dateTime
Yes
CompetitiveSolicitationProcessOfferSet.SchedulingCoordinator (Optional) Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 16 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
mrid
Date Created:
Data Description
Master resource identifier of Scheduling Coordinator
8/16/2015 Type/ Length
string
Req’d
Yes
CompetitiveSolicitationProcessOfferSet. CompetitiveSolicitationProcessOffer (Required) mrid
Master resource identifier of CSP Offer that is generated by CSP. This attribute is not applicable when submitting new CSP Offers
string
No
startTime
First date of the month in GMT
dateTime
Yes
endTime
Last day of the month in GMT
dateTime
Yes
versionID
This element is not applicable for this service
integer
No
status
This element is not applicable for this service
string
No
comments
This element is not applicable for this service
string
No
RegisteredGenerat or/RegisteredInterT ie
Master resource identifier of Resource(RegisteredGenerator or RegisteredInterTie ) for which offer is being made.
string
Yes
genericCapacity.val ue
Generic MW value represents the generic RA capacity that the given resource is submitting for the CSP offer. A non-zero positive value should be provided for generic MW when flexible MW is not offered.
float
No
flexibleCapacity.val ue
Flexible MW value represents the flexible RA capacity that the given resource is submitting for the CSP offer. . A non-zero positive value should be provided for flexible MW when generic MW is not offered.
float
No
flexibleCategory
If offer has flexible mw then flxible category( 1, 2 or3) must be provided
integer
No
price
CSP Offer price $/kw
float
Yes
4.6.2 Schema (CSPOfferSet_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 4.6.3 Example XML File (submitCSPOffersRequest_v1xml) 2001-12-17T09:30:47Z SC1 v20160301 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 17 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
MONTHLY 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 1 10.00 20.00 6.14 RESOURCE_ID_1 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 1 20.00 40.00 3.14 RESOURCE_ID_2 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 1 30.00 60.00 8.14 RESOURCE_ID_3 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 18 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
2015-10-01T07:59:59Z 2015-09-01T08:00:00Z SC1
4.6.4 Example XML File (updateCSPOffersRequest_v1.xml) 2001-12-17T09:30:47Z SC1 v20160301 1234 MONTHLY 100 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 2 5.00 10.00 3.14 RESOURCE_ID_1 101 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 1 10.00 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 19 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
60.00 7.14 RESOURCE_ID_2 2015-10-01T07:59:59Z 2015-09-01T08:00:00Z
4.7 Submit CSP Offers Response 4.7.1 Element Table Element
Data Description
Type / Length
Req’d
outputDataType (required) EventLog.Event (required) result
Success or failure message. If Success, all bids (offers) received by CSP will be returned as part of BID element
string
Yes
id
A unique identifier
string
Yes
description
Appropriate details related to the result of the event
string
no
creationTime
The creation time in GMT format
dateTime
No
integer
Yes
string
Yes
EventLog.Service (required) id name
The service Id (created by the Caiso web services framework.) The name of the service as used by the Web Service. submitCSPOffers_v1
EventLog.BID (optional) –
BID_ID
Unique Identifier of the CSP Offer
string
No
START_TIME
First day of Offering Month for which CSP Offer is received
dateTime
Yes
END_TIME
Last day of Offering Month for which CSP Offer is received
dateTime
Yes
RESOURCE_ID
Master Resource Identifier of the resource for which Offer is received
string
Yes
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 20 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015 Req’d
Element
Data Description
Type / Length
resourceAdequacyPe riodType
The timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumerati on
Yes
MARKET_TYPE
Not applicable for this service
string
No
RESULTS
Status of the CSP Offer. RECEIVED
string
Yes
String
No
EventLog.BATCH (optional) BATCH_ID
Unique identifier generated by caiso to represent submission of a request to create or update CSP Offers
4.7.2 Schema (SubmitStandardOutput_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 4.7.3 Example XML File (submitCSPOffersResponse_v1.xml) Success 7ca407d3-1476-4cc6-91ab-8de4c1ae2e6b Successfully Received 2014-11-13T19:32:45.879+00:00 99b8d07d-0d06-4f08-8af3-a5d4ad961271 submitCSPOffers_v1 100 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z RESOURCE_ID_1 MONTHLY RECEIVED 101 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z RESOURCE_ID_2 MONTHLY RECEIVED Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 21 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
102 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z RESOURCE_ID_3 MONTHLY RECEIVED
4.8 Fault Return For Fault return see section Fault Return
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 22 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
5. Retrieve CSP Offers Business Scenario 5.1 Overview Scheduling Coordinators can retrieve CSP Offers created/updated for the affiliated resources. Note : This service will be supported in the future release.
5.2 Service Level Agreement Service availability
Service level goal is 99.9%.
Expected size of payload (average and maximum)
TBD
Expected frequency (average and maximum)
Annual CSP Offers once a year. Monthly CSP Offers once a month. Intramonthly CSP Offers once a day. 4 hrs
Longest time the service can be unavailable before business is impacted Business impact if is unavailable Expected response time for the service
CIRA UI provides mechanism to submit/update CSP Offers 5 to 30 secs.
Expected time to exchange
5 to 30 secs.
5.3 Use Model The sequence diagram below describes the service level interactions between the Scheduling Coordinator systems and the CSP. Channel level security and authentication are abstracted from this diagram (They will be covered in another document; B2B Security Specifications). 5.3.1 Retrieve CSP Offers
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 23 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
5.4 Operational Details Each service has one operation with three message types. 5.4.1 Retrieve CSP Offers
Operation
Message
Owner: Nallagangu, Sunil
Message
WSDL
XSD Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 24 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
Types retrieveCSPOffers
Input Output Fault
retrieveCSPOffers Request retrieveCSPOffers Response faultReturnType
retrieveCSPOffers_v1.wsdl / retrieveCSPOffers_v1_Doc Attach.wsdl
RequestCSPOfferSet_v1.xsd CSPOfferSet_v1.xsd StandardOutput.xsd
5.5 WSDL 5.5.1 retrieveCSPOffers_v1.wsdl 5.5.2 retrieveCSPOffers_v1_DocAttach.wsdl Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx
5.6 Retrieve CSP Offers Request 5.6.1 Element Table Element
Data Description
Type/ Length
Req’d
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) CompetitiveSolicitationProcessOfferSet (Required) mRID
Master resource identifier of CSP Offer Set that is generated by CSP.
string
No
includeHistory
A Boolean flag to indicate if history of CSP Offers need to be retrieved. If set to true, result set includes all versions of the CSP offers with versionID fied populated.
boolean
No
resourceAdequacy PeriodType
Resource Adequacy Period Type is defined as the timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumeration
No
dateTime
No
CompetitiveSolicitationProcessOfferSet.offerPeriod start
Start date of Offering Period in GMT . For ANNUAL offering type it’s first day of the year, for MONTHLY/INTRAMONTHLY it’s first day of the month
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 25 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
end
Date Created:
Data Description
End Date of Offering Period in GMT . For ANNUAL offering type it’s last day of the year, for MONTHLY/INTRAMONTHLY it’s last day of the month
8/16/2015 Type/ Length
Req’d
dateTime
No
string
Yes
CompetitiveSolicitationProcessOfferSet.SchedulingCoordinator (Optional) mrid
Master resource identifier of Scheduling Coordinator
CompetitiveSolicitationProcessOfferSet. CompetitiveSolicitationProcessOffer (Optional) mrid
Master resource identifier of CSP Offer that is generated by CSP. This attribute is not applicable when submitting new CSP Offers
string
No
startTime
First date of the month in GMT
dateTime
No
endTime
Last day of the month in GMT
dateTime
No
comments
This element is not applicable for this service
string
No
RegisteredGenerat or/RegisteredInterT ie
Master resource identifier of Resource(RegisteredGenerator or RegisteredInterTie ) for which offer is being made.
string
No
5.6.2 Schema (RequestCSPOfferSet_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 5.6.3 Example XML File (retrieveCSPOffersRequest_v1.xml) 2001-12-17T09:30:47Z Source System v20160301 MONTHLY 2015-10-01T07:59:59Z 2015-09-01T08:00:00Z SC1 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 26 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
5.7 Retrieve CSP Offers Response 5.7.1 Element Table Element
Data Description
Type/ Length
Req’d
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) CompetitiveSolicitationProcessOfferSet (Required) mRID
Master resource identifier of CSP Offer Set that is generated by CSP. This attribute is not applicable when submitting New CSP Offers
string
No
resourceAdequacy PeriodType
Resource Adequacy Period Type is defined as the timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumeration
Yes
CompetitiveSolicitationProcessOfferSet.offerPeriod (Required) start
Start date of Offering Period in GMT . For ANNUAL offering type it’s first day of the year, for MONTHLY/INTRAMONTHLY it’s first day of the month
dateTime
Yes
end
End Date of Offering Period in GMT . For ANNUAL offering type it’s last day of the year, for MONTHLY/INTRAMONTHLY it’s last day of the month
dateTime
Yes
string
Yes
CompetitiveSolicitationProcessOfferSet.SchedulingCoordinator (Optional) mrid
Master resource identifier of Scheduling Coordinator
CompetitiveSolicitationProcessOfferSet. CompetitiveSolicitationProcessOffer (Required) mrid
Master resource identifier of CSP Offer that is generated by CSP. This attribute is not applicable when submitting new CSP Offers
string
No
startTime
First date of the month in GMT
dateTime
Yes
endTime
Last day of the month in GMT
dateTime
Yes
versionID
Version of the CSP offer. This element is populated when the request sets includeHistory flag to boolean
integer
No
status
Status of the CSP Offer. Possible statuses include: RECEIVED,PENDING,CANCELLED,ACCEPTED,VALID,INVALID
string
No
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 27 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
comments
Date Created:
Data Description
Comments are populated in following cases :
8/16/2015 Type/ Length
Req’d
string
No
1. Comments specified by client when Withdrawing/cancelling the CSP Offer. 2. Comments set by system during CSP offer processing. RegisteredGenerat or/RegisteredInterT ie
Master resource identifier of Resource(RegisteredGenerator or RegisteredInterTie ) for which offer is being made.
string
Yes
genericCapacity.val ue
Generic MW value represents the generic RA capacity that the given resource is submitting for the CSP offer. A non-zero positive value should be provided for generic MW when flexible MW is not offered.
float
No
flexibleCapacity.val ue
Flexible MW value represents the flexible RA capacity that the given resource is submitting for the CSP offer. . A non-zero positive value should be provided for flexible MW when generic MW is not offered.
float
No
flexibleCategory
If offer has flexible mw then flxible category( 1, 2 or3) must be provided
integer
No
price
CSP Offer price $/kw
float
Yes
5.7.2 Schema (CSPOfferSet_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 5.7.3 Example XML File (retrieveCSPOffersResults_v1.xml) 2001-12-17T09:30:47Z CIRA v20160301 1234 MONTHLY 100 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z 0 ACCEPTED Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 28 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
1 10.00 20.00 6.14 RESOURCE_ID_1 101 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z RESOURCE_ID_2 is not valid. 1 PENDING 2 20.00 40.00 3.14 RESOURCE_ID_2 102 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z Reason for cancellation .... 1 CANCELLED 2 30.00 60.00 8.14 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 29 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
RESOURCE_ID_3 2015-10-01T07:59:59Z 2015-09-01T08:00:00Z SC1
5.8 Fault Return For Fault return see section Fault Return
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 30 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
6. Withdraw CSP Offers 6.1 Overview Scheduling Coordinators can withdraw a previously submitted CSP Offer before Offer adjustment period closes. Note : This service will be supported in the future release.
6.2 Service Level Agreement Service availability
Service level goal is 99.9%.
Expected size of payload (average and maximum)
TBD
Expected frequency (average and maximum)
Annual CSP Offers once a year. Monthly CSP Offers once a month. Intramonthly CSP Offers once a day. 4 hrs
Longest time the service can be unavailable before business is impacted Business impact if is unavailable Expected response time for the service
CIRA UI provides mechanism to submit/update CSP Offers 5 to 30 secs.
Expected time to exchange
5 to 30 secs.
6.3 Use Model The sequence diagram below describes the service level interactions between the Scheduling Coordinator systems and the CSP. Channel level security and authentication are abstracted from this diagram (They will be covered in another document; B2B Security Specifications).
6.3.1 Withdraw CSP Offer
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 31 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
6.4 Operational Details Each service has one operation with three message types. 6.4.1 Withdraw CSP Offers
Operation withdrawCSPOffers
Messag e Types Input Output Fault
Owner: Nallagangu, Sunil
Message
WSDL
withdrawCSPOffersReq uest withdrawCSPOffersResp onse faultReturnType
withdrawCSPOffer s_v1.wsdl
XSD RequestCSPOfferSet_v1 SubmitStandardOutput_v1.xsd StandardOutput.xsd Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 32 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
6.5 WSDL 6.5.1 withdrawCSPOffers_v1.wsdl 6.5.2 withdrawCSPOffers_v1-DocAttach.wsdl Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx
6.6 Withdraw CSP Offers Request 6.6.1 Element Table Element
Data Description
Type/ Length
Req’d
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) CompetitiveSolicitationProcessOfferSet (Required) mRID
Master resource identifier of CSP Offer Set that is generated by CSP.
string
No
includeHistory
This element is not applicable for this service
boolean
No
resourceAdequacy PeriodType
Resource Adequacy Period Type is defined as the timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumeration
No
CompetitiveSolicitationProcessOfferSet.offerPeriod start
Start date of Offering Period in GMT . For ANNUAL offering type it’s first day of the year, for MONTHLY/INTRAMONTHLY it’s first day of the month
dateTime
No
end
End Date of Offering Period in GMT . For ANNUAL offering type it’s last day of the year, for MONTHLY/INTRAMONTHLY it’s last day of the month
dateTime
No
string
Yes
CompetitiveSolicitationProcessOfferSet.SchedulingCoordinator (Optional) mrid
Master resource identifier of Scheduling Coordinator
CompetitiveSolicitationProcessOfferSet. CompetitiveSolicitationProcessOffer (Optional) mrid
Master resource identifier of CSP Offer that is generated by CSP. This attribute is not applicable when submitting new CSP Offers
string
No
startTime
First date of the month in GMT
dateTime
No
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 33 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
Date Created:
Data Description
8/16/2015 Type/ Length
Req’d
endTime
Last day of the month in GMT
dateTime
No
comments
Reason for withdrawing CSP Offer. This is mandatory element for this service
string
No
RegisteredGenerat or/RegisteredInterT ie
Master resource identifier of Resource(RegisteredGenerator or RegisteredInterTie ) for which offer is being made.
string
No
6.6.2 Schema (RequestCSPOfferSet_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 6.6.3 Example XML File (withdrawCSPOffersRequest_v1.xml) 2001-12-17T09:30:47Z String v20160301 1234 102 Reason for cancellation ...
6.7 Withdraw CSP Offers Response Element
Data Description
Type / Length
Req’d
outputDataType (required) EventLog.Event (required) result
Success or failure message. If Success, all bids (offers) received by CSP will be returned as part of BID element
Owner: Nallagangu, Sunil
string
Yes
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 34 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
Date Created:
Data Description
Type / Length
8/16/2015 Req’d
id
A unique identifier
string
Yes
description
Appropriate details related to the result of the event
string
no
creationTime
The creation time in GMT format
dateTime
No
integer
Yes
string
Yes
EventLog.Service (required) id name
The service Id (created by the Caiso web services framework.) The name of the service as used by the Web Service. submitCSPOffers_v1
EventLog.BID (optional) –
BID_ID
Unique Identifier of the CSP Offer that is withdrawn
string
No
START_TIME
First day of Offering Month for which CSP Offer is withdrawn
dateTime
Yes
END_TIME
Last day of Offering Month for which CSP Offer is withdrawn
dateTime
Yes
RESOURCE_ID
Master Resource Identifier of the resource for which Offer is withdrawn
string
Yes
resourceAdequacyPe riodType
The timeframe of Offering Period ANNUAL,MONTHLY, or INTRAMONTHLY
Enumerati on
Yes
MARKET_TYPE
Not applicable for this service
string
Yes
RESULTS
Status of the CSP Offer. CANCELLED
string
Yes
String
No
EventLog.BATCH (optional) BATCH_ID
Not applicable for this service
6.7.1 Element Table 6.7.2 Schema (SubmitStandardOutput_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 6.7.3 Example XML File (withdrawCSPOffersResponse_v1.xml) Success 7ca407d3-1476-4cc6-91ab-8de4c1ae2e6b Successfully Received 2014-11-13T19:32:45.879+00:00 Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 35 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
99b8d07d-0d06-4f08-8af3-a5d4ad961271 withdrawCSPOffers_v1 102 2015-09-01T08:00:00Z 2015-10-01T07:59:59Z RESOURCE_ID_3 MONTHLY CANCELLED
6.8 Fault Return For Fault return see section Fault Return
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 36 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7. Retrieve Resource Adequacy Capacity Data 7.1 Overview Scheduling Coordinators can retrieve their Resource Adequacy Capacity Data using this service. Note : This service will be supported in the upcoming 2016 release.
7.2 Service Level Agreement Service availability
Service level goal is 99.9%.
Expected size of payload (average and maximum)
TBD
Expected frequency (average and maximum)
Every day once and user can retrieve Resource Adequacy capacity data whenever they need it. 4 hrs
Longest time the service can be unavailable before business is impacted Business impact if is unavailable Expected response time for the service
CIRA UI provides mechanism to view this data. 5 to 30 secs.
Expected time to exchange
5 to 30 secs.
7.3 Use Model The sequence diagram below describes the service level interactions between the Scheduling Coordinator systems and the CIRA system. Channel level security and authentication are abstracted from this diagram (They will be covered in another document; B2B Security Specifications).
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 37 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.3.1 Retrieve Resource Adequacy Capacity Data
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 38 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.4 Operational Details Each service has one operation with three message types. 7.4.1 Retrieve Resource Adequacy Capacity Data
Operation retrieveResourceAde quacyCapacityData
Message Types Input
Output
Fault
Message
WSDL
XSD
retrieveResourceA dequacyCapacityD ataRequest retrieveResourceA dequacyCapacityD ataResponse faultReturnType
retrieveResourceAdequacyCa pacityData_v1.wsdl / retrieveResourceAdequacyCa pacityData_v1_DocAttach.w sdl
RequestResourceAdequacyCa pacityDataet_v1.xsd ResourceAdequacyCapacityDat aet_v1.xsd StandardOutput.xsd
7.5 WSDL 7.5.1 retrieveResourceAdequacyCapacityData_v1.wsdl 7.5.2 retrieveResourceAdequacyCapacityData_v1_DocAttach.wsdl Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx
7.6 Retrieve Resource Adequacy Capacity Data Request 7.6.1 Element Table Element
Data Description
Type/ Length
Req’d
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) ResourceAdequacy(required) Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 39 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification Element
Date Created:
Data Description
8/16/2015 Type/ Length
Req’d
MarketIntervalTime(required) intervalStartTime
Market Interval Start Time
dateTime
Yes
dateTime
Yes
string
Yes
string
Yes
in GMT intervalEndTime
Market Interval End Time in GMT
ResourceAdequacy.SchedulingCoordinator mrid
Master resource identifier of scheduling coordinator
ResourceAdequacy. RegisteredGenerator/RegisteredInterTie mrid
Master resource identifier of RegisteredGenerator/RegisteredInterTie
7.6.2 Schema (RequestResourceAdequacyCapacityData_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx 7.6.3 Example XML File (requestResourceAdequacyCapacityData_v1.xml) 2001-12-17T09:30:47Z Source System v20160301 2001-12-17T07:00:00Z 2001-12-17T08:00:00Z TEST_RESOURCE_1 SC_TEST
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 40 of 44
Template Version:
1.4
Document Version:
2.1
Technology
cczxxz
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.7 Retrieve Resource Adequacy Capacity Response 7.7.1 Element Table Element
Data Description
Req’d
Type/ Length
MessageHeader (optional)
TimeDate
Application level relevant time and date for when this instance of the message was produced, in GMT Time format
datetime
Yes
Source
Source system which provides data for this service
String
Yes
Version
Date reflecting the release this latest version update was related to.
String
Yes
MessagePayload (required) ResourceAdequacy(required) intervalStartTime
Market Interval Start Time in GMT
dateTime
Yes
intervalEndTime
Market Interval End Time in GMT
dateTime
Yes
lastUpdated
Last updated time of the record
dateTime
Yes
boolean
Yes
ResourceAdequacy.MustOfferObligation (optional) MOOFlag
The Must Offer Obligation (MOO) Flag. Possible values are true or false
ResourceAdequacy. RACapacity (required) capacityMW
Resource Adequacy MW value
float
Yes
resourceAdequacy Type
RA Type. Possible values are FLEX or GENERIC
String
No
integer
Yes
ResourceAdequacy.RAFlexCategory(optional) flexibleCategory
Flex category of the resource
ResourceAdequacy.RegisteredGenerator/RegisteredInterTie mrid
Master resource identifier of RegisteredGenerator/RegisteredInterTie
string
No
string
Yes
ResourceAdequacy.RegisteredGenerator.configuration (optional) mrid
Master resource identifier of RegisteredGenerator/RegisteredInterTie
7.7.2 Schema (ResourceAdequacyCapacityDataResults_v1.xsd) Location: http://www.caiso.com/informed/Pages/ReleasePlanning/Default.aspx Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 41 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.7.3 Example XML File (ResourceAdequacyCapacityDataResults_v1.xml) -01 20016-01-17T00:00:00Z String v20160301 20016-01-17T09:00:00Z 20016-01-17T08:00:00Z 20016-01-17T00:00:00Z true 3.14 FLEX 0 TEST_RESOURCE_1 20016-01-17T09:00:00Z 20016-01-17T08:00:00Z 20016-01-17T00:00:00Z true 5.12 FLEX 0 TEST_RESOURCE_2
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 42 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
7.8 Fault Return For Fault return see section Fault Return
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 43 of 44
cczxxz
Template Version:
1.4
Document Version:
2.1
Technology
Customer Interface For Resource Adequacy ISO Interface Specification
Date Created:
8/16/2015
8. Error Codes
Owner: Nallagangu, Sunil
Program Office
Copyright 2012 California ISO Doc ID: GNFDMDEHU6BB-46-46
Page 44 of 44