DRS Replacement. ISO Interface Specification. Date Created: 11/9/2015. Document Version: 1.0. Owner: CAISO/ITPD

Transcription

1 ISO Interface Specification DRS Replacement Date Created: 11/9/2015 Owner: CAISO/ITPD Doc ID: GNFDMDEHU6BB Page 1 of 32

2 Location of Replacement.pdf Revision History Date Version Description Author 11/9/2015 Initial Version CAISO 2

3 Table of Contents 1. INTRODUCTION PURPOSE CONTACT INFORMATION RELATED DOCUMENTS RELEASE NOTES API TRANSITION SUPPORT BUSINESS SCENARIO SERVICE LEVEL AGREEMENT SUBMITMETERDATA USE MODEL OPERATION DETAILS WSDL (SUBMITDRMETERDATA_V1.WSDL)...10 submitmeterdata_v1.wsdl Used for normal SOAP messaging...10 submitmeterdata_docattach_v1.wsdl Used when.net is the source of processing MESSAGE TYPE Element Table Schema (MeterData_v1.xsd) Example XML File (SubmitMeterData_v1.xml) MESSAGE TYPE Element Table Schema Example XML File (StandardOutput.xml) RETRIEVEMETERDATA USE MODEL OPERATION DETAILS WSDL (RETRIEVEMETERDATA_V1.WSDL)...16 retrievemeterdata_v1.wsdl Used for normal SOAP messaging...16 retrievemeterdata_docattach_v1.wsdl Used when.net is the source of processing MESSAGE TYPE Element Table Schema (RequestMeterData_v1.xsd) Example XML File (RequestMeterData_v1.xml) RETRIEVEBATCHVALIDATIONSTATUS USE MODEL OPERATION DETAILS WSDL (RETRIEVEBATCHVALIDATIONSTATUS_V1.WSDL)...21 retrievebatchvalidationstatus_v1.wsdl Used for normal SOAP messaging...21 retrievebatchvalidationstatus_docattach_v1.wsdl Used when.net is the source of processing MESSAGE TYPE Element Table Schema (BatchValidationStatus_v1.xsd)

4 6.4.3 Example XML File (BatchValidationStatus_v1.xml) RETRIEVEDRCALCULATEDDATA USE MODEL OPERATION DETAILS WSDL (RETRIEVEDRCALCULATEDDATA_V1.WSDL)...27 retrievedrcalculateddata_v1.wsdl Used for normal SOAP messaging...27 retrievedrcalculateddata_docattach_v1.wsdl Used when.net is the source of processing MESSAGE TYPE Element Table Schema (DRCalculatedData_v1.xsd) Example XML File (DRCalculatedData_v1.xml...29 APPENDIX DATETIME DATA TYPE Introduction 1.1 Purpose This document describes the Market Participant interface to CAISO s new DRS Replacement 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 DRS Replacement web services, please send to ServiceDesk@caiso.com 1.3 Related s 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, 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. B2B Security Specification (CAISO ISS) CAISO s Web Services Architecture & Integration Specification Client Public/Private Key Instructions (CAISO ISS) 4

5 Interface Specification for DR Replacement Web Services Figure 1 ISO MARKET Web Services Interface Specification Set The ISO MARKET Web Services Interface Specification Set is available online at the locations indicated below. Doc. No. Name Location 1 2 ISO MARKET B2B Security Specification Client Public/Private Key Instructions rivatekeyguidelines.pdf 1.4 Release Notes Release Notes for ISO Interface Specification for DRS Replacement Web Services Version 1 This document release will be the first release of the interface specification The services being created for DRS Replacement effort are the following: 1. submitmeterdata_v1 submit a create or modify request for meter data 2. submitmeterdata_v1_docattach submit a create or modify request for meter data for.net clients 3. retrievemeterdata_v1 retrieve request for meter data of a resource 4. retrievemeterdata_v1_docattach retrieve request for meter data of a resource for.net clients 5. retrievebatchvalidationstatus_v1 to request the status on a submission of a create or modify 6. retrievebatchvalidationstatus_v1_docattach to request the status on a submission of a create or modify for.net clients 7. retrievedrcalculateddata_v1 retrieve request for baseline and performance data 8. retrievedrcalculateddata_v1_docattach retrieve request for baseline and performance data for.net clients 5

6 1.5 API Transition Support Initial Implementation 6

7 2. Business Scenario Market Participants can retrieve or submit the following data via the DRS Replacement web services: Retrieve Meter data Retrieve DR Calculated (Performance and Baseline) data Submit request for Meter data Submit modification request for Meter data Retrieve status for the creation or modification requests 7

8 3. 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 TBD TBD TBD Expected response time for the service TBD Expected time to exchange Market Participants utilizing the service will not be able to submit or retrieve Meter Data, Baseline or Performance data TBD 8

9 4. SubmitMeterData 4.1 Use Model The diagram below shows the sequence for submitmeterdata : Market Participant prepare request parameters : : DRSReplace DRSReplacement mentapi submitmeterdatarequest submitbatch Generate batch id transform Return batch id submitmeterdataresponse 9

10 4.2 Operation Details The service has submitmeterdata_v1 operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD submitmeterdat a_v1 Input submitmeterda tarequest submitmeterdata_v1. wsdl MeterData_v1.xsd Output Fault submitmeterda taresponse faultreturntyp e submitmeterdata_do cattach_v1.wsdl StandardOutput_v1.xsd StandardOutput_v1.xsd 4.3 WSDL (submitdrmeterdata_v1.wsdl) submitmeterdata_v1.wsdl Used for normal SOAP messaging submitmeterdata_docattach_v1.wsdl Used when.net is the source of processing The WSDL can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications. 4.4 Message Type submitmeterdatarequest Element Table Element Data Description 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 Req d Source Source system which provides data for this service 10

11 Element Data Description Type/ Length Req d Version Date reflecting the release this latest version update was related to. MessagePayload (required) MessagePayload.MeterMeasurementData (one to many occurences) measurementquality Quality of the measurement. Examples are: Actual, Estimated measurementtype Type of the measurement. Examples are: Gen, Load etc. timeintervallength Interval length of the trading time in minutes. Example: 5, 15, 60 unitmultiplier unitsymbol versionid The interval length should be the same for a trade date. For example, if the prior submission for the date happened in 5 minute intervals, the rest of the hours need to be submitted with the same interval length. The unit multiplier of the measured quantity. Valid values are: M for megawatt k for kilowatt The unit of measure of the measured quantity. Valid value is: Wh The version of the submission. Will be populated only in the retrieve response. Cannot be specified for submissions. This will be auto generated by the system. MessagePayload.MeterMeasurementData.DemandResponseRegistration (optional) Float Integer No mrid Master resource identifier of the registration (Registration ID) demandresponseper formancemeasureme nt Method used for the demand response performance measurement. Examples include Physical, Statistical etc. No MessagePayload.MeterMeasurementData.MeasurementValue (one to many occurences) all activity records created for this asset intervalendtime EndDatetime of the interval for which the meter value is being submitted or retrieved datetime metervalue Meter value or Meter Quantity Decimal timestamp Updated time stamp datetime No MessagePayload.MeterMeasurementData.RegisteredGenerator mrid Master resource identifier of the generator resources as specified by master file. MessagePayload.MeterMeasurementData.RegisteredInterTie mrid Master resource identifier of the intertie resource as provided in the master file * * 11

12 Element Data Description Type/ Length Req d MessagePayload.MeterMeasurementData.RegisteredLoad mrid Master resource identifier of the load resource as provided in the master file *Only one of these three elements is required at a given time Schema (MeterData_v1.xsd) * The XSD can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications Example XML File (SubmitMeterData_v1.xml) SubmitMeterData_v1.xml Sample request for a meter data submission <?xml version="" encoding="utf-8"?> <!--Sample XML file generated by XMLSpy v2016 (x64) ( <MeterData xmlns=" xmlns:xsi=" xsi:schemalocation=" MeterData_v1.xsd"> <MessagePayload> <MeterMeasurementData> <measurementquality>actual</measurementquality> <measurementtype>gen</measurementtype> <timeintervallength>5</timeintervallength> <unitmultiplier>k</unitmultiplier> <unitsymbol>wh</unitsymbol> <MeasurementValue> <intervalendtime> t19:05: :00</intervalendtime> <metervalue>0</metervalue> </MeasurementValue> <RegisteredGenerator> <mrid>abc_123</mrid> </RegisteredGenerator> </MeterMeasurementData> </MessagePayload> </MeterData> 12

13 4.5 Message Type submitmeterdataresponse and faultreturntype both conform to the StandardOutput.xsd Element Table Element Data Description Type / Length Req d StandardOutput (required) MessageHeader (optional) TimeDate Application level relevant time and date for when this instance of the message was produced, in GMT Time format datetime Source Source system which provides data for this service Version Date reflecting the release this latest version update was related to. MessagePayload (required) EventLog.Service (required) The service Id (created by the web services framework. id name The name of the service as used by the Web Service. EventLog.Event (required) creationdatetime Time of creation description Description of event id Id of the event result Result of submission EventLog.Batch (optional) integer string datetime integer No No mrid This represents the batch ID for submission of a request creationtime Creation time datetime No Schema StandardOutput_v1.xsd The XSD can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications. 13

14 4.5.3 Example XML File (StandardOutput.xml) Sample response for submitdrmeterdata request <?xml version="" encoding="utf-8" standalone="yes"?> <StandardOuput xmlns=" <EventLog> <Event> <result>success</result> <id>7ca407d cc6-91ab-8de4c1ae2e6b</id> <description>successfully Received </description> <creationtime> t19:32: :00</creationtime> </Event> <Service> <id>99b8d07d-0d06-4f08-8af3-a5d4ad961271</id> <name>submitdrmeterdata_v1</name> </Service> <Batch> <mrid>24</mrid> </Batch> </EventLog> </ StandardOuput> 14

15 5. RetrieveMeterData 5.1 Use Model The diagram below shows the sequence for retrievemeterdata : Market Participant : : DRSReplace DRSReplacement mentapi prepare request parameters retrievemeterdatarequest Submit request Query database transform Return meter data retrievemeterdataresponse 15

16 5.2 Operation Details The service has retrievemeterdata_v1 operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD retrievemeterdat a_v1 Input retrievemeterd atarequest retrievemeterdata_v1.wsdl RequestMeterData_v1.xsd Output Fault retrievemeterd ataresponse faultreturntyp e retrievemeterdata_d ocattach_v1.wsdl MeterData_v1.xsd StandardOutput_v1.xsd The structure of the request for retrieving the meter data information is described below in 5.4. The response structure (MeterData_v1.xsd) and StandardOutput_v1.xsd have been described earlier in this document in sections 4.4 and WSDL (retrievemeterdata_v1.wsdl) retrievemeterdata_v1.wsdl retrievemeterdata_v1.wsdl Used for normal SOAP messaging retrievemeterdata_docattach_v1.wsdl Used when.net is the source of processing The WSDL can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications. 5.4 Message Type retrievemeterdatarequest Element Table Element Data Description Type/ Length Req d MessageHeader (Optional) 16

17 Element Data Description Type/ Length Req d TimeDate Application level relevant time and date for when this instance of the message was produced, in Pacific Prevailing Time format datetime Source Source system which provides data for this service Version Date reflecting the release this latest version update was related to. MessagePayload (required) MessagePayload.MeterDataRequest(one or more occurrences) requesttype Type of request. Allowed values are: METER_DATA DR_CALCULATED_DATA The type METER_DATA returns information related to the meter data while DR_CALCULATED _DATA relates information regarding the baseline and performance calculation MessagePayload.MeterDataRequest.DemandResponseRegistration (optional) mrid Master resource identifier of the registration (Registration ID) MessagePayload.MeterDataRequest.Measurement (optional) measurementtype Type of the measurement. Examples include GEN, LOAD etc. No unitmultiplier The unit multiplier of the measured quantity. Valid values are: No M for megawatt k for kilowatt unitsymbol The unit of measure of the measured quantity. Valid value is: No Wh versionid The version of the submission. Will be populated only in the retrieve response. Cannot be specified for submissions. This will be auto generated by the system. Integer No MessagePayload.LocationRequest.rangePeriod end end date and time of interval in GMT format datetime start start date and time of interval in GMT format datetime MessagePayload.MeterMeasurementData.RegisteredGenerator mrid Master resource identifier of the generator resources as specified by master file. MessagePayload.MeterMeasurementData.RegisteredInterTie mrid Master resource identifier of the intertie resource as provided in the master file * * 17

18 Element Data Description Type/ Length Req d MessagePayload.MeterMeasurementData.RegisteredLoad mrid Master resource identifier of the load resource as provided in the master file *Only one of these three elements is required for a specific request Schema (RequestMeterData_v1.xsd) * The XSD can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications Example XML File (RequestMeterData_v1.xml) Sample request to retrieve meter data based on a time range. <?xml version="" encoding="utf-8"?> <!--Sample XML file generated by XMLSpy v2016 (x64) ( <RequestMeterData xmlns=" xmlns:xsi=" xsi:schemalocation=" RequestMeterData_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <MeterDataRequest> <requesttype>meter_data</requesttype> <DemandResponseRegistration> <mrid>r1234</mrid> </DemandResponseRegistration> <Measurement> <measurementtype></measurementtype> <unitmultiplier>k</unitmultiplier> <unitsymbol>wh</unitsymbol> </Measurement> <rangeperiod> <end> t00:00:00+00:00</end> <start> t01:00:00+00:00</start> </rangeperiod> <RegisteredGenerator> <mrid>abc_123</mrid> </RegisteredGenerator> </MeterDataRequest> </MessagePayload> </RequestMeterData> 18

19 Sample response: <?xml version="" encoding="utf-8"?> <MeterData xmlns=" xmlns:xsi=" xsi:schemalocation=" MeterData_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <MeterMeasurementData> <measurementquality>actual</measurementquality> <measurementtype>gen</measurementtype> <timeintervallength>5</timeintervallength> <unitmultiplier>m</unitmultiplier> <unitsymbol>wh</unitsymbol> <versionid>1</versionid> <DemandResponseRegistration> <mrid>drp1</mrid> <demandresponseperformancemeasurement>physical </demandresponseperformancemeasurement> </DemandResponseRegistration> <MeasurementValue> <intervalendtime> t19:35:00+00:00</intervalendtime> <metervalue>2</metervalue> <timestamp> t19:32: :00</timestamp> </MeasurementValue> <RegisteredGenerator> <mrid>gen123</mrid> </RegisteredGenerator> </MeterMeasurementData> </MessagePayload> </MeterData> 19

20 6. RetrieveBatchValidationStatus 6.1 Use Model The diagram below shows the sequence for retrievebatchvalidationstatus : Market Participant prepare request parameters : : DRSReplacement DRSReplace mentapi retrievebatchvalidationstatusrequest Submit request Query database transform Return batch status retrievebatchvalidationstatusresponse 20

21 6.2 Operation Details The service has retrievebatchvalidationstatus_v1 operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD retrievebatchval idationstatus_v1 Input retrievebatchvali dationstatusreq uest retrievebatchvalidatio nstatus_v1.wsdl BatchValidationStatus_v1.xsd Output Fault retrievebatchvali dationstatusres ponse faultreturntyp e retrievebatchvalidatio nstatus_docattach_v 1.wsdl BatchValidationStatus_v1.xsd StandardOutput_v1.xsd 6.3 WSDL (retrievebatchvalidationstatus_v1.wsdl) retrievebatchvalidationstatus_v1.wsdl Used for normal SOAP messaging retrievebatchvalidationstatus_docattach_v1.wsdl Used when.net is the source of processing The WSDL can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications. 6.4 Message Type retrievebatchvalidationstatusrequest Element Table Element Data Description 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 Req d Source Source system which provides data for this service 21

22 Element Data Description Type/ Length Req d Version Date reflecting the release this latest version update was related to. MessagePayload (required) MessagePayload.BatchStatus (optional) mrid This represents the batch ID of a request that was generated by the system and sent back to the user for submission of a request creationtime Date/time of status creation in GMT format datetime description Description of batch status There are 4 values for status: SUCCESS, FAIL, IN_PROCESS, and NOT_PROCESSED. Once the batch is submitted, the status is set to "NOT_PROCESSED". The processor runs every x seconds to pick up the XML submissions. If you query within the x seconds that the scheduler picks it up, you will see the status as "NOT_PROCESSED". If you query during the time the scheduler is processing the batch, you will get "IN_PROCESS" status. Once the processing is complete, the status will change to "SUCCESS" or "FAIL". MessagePayload.DistributedEnergyResourceContainer (optional) (0 to unbounded occurrences) mrid Master resource identifier of the distributed energy resource container (also referred to in the DRS system as the location) not relevant to this specification, but used for submission of DR locations No name Name of the location not relevant to this specification No MessagePayload.DistributedEnergyResourceContainer.ErrorLog (required) reasons for error in locations mrid Master resource identifier aka location ID No starttime Start time of the error in GMT datetime No endtime End time of the error in GMT datetime No errmessage error message errpriority Priority number for the error message integer logtimestamp Date time when the error was created datetime MessagePayload.DemandResponseRegistration (optional) (0 to unbounded occurrences) 22

23 Element Data Description Type/ Length Req d mrid Master resource identifier of the registration aka Registration ID No name Name of the registration No MessagePayload.DemandResponseRegistration.ErrorLog(required) reasons for error in batch mrid Master resource identifier aka Registration ID No starttime Start time of the error in GMT datetime No endtime End time of the error in GMT datetime No errmessage error message errpriority Priority number for the error message integer logtimestamp Date time when the error was created in GMT datetime MessagePayload.RegisteredResource (optional) (0 to unbounded occurrences) MessagePayload.RegisteredResource.MktOrganisation (required)** MessagePayload.RegisteredResource.MktOrganisation.RegisteredGenerator mrid Master resource identifier of the registered generator as specified in masterfile No name Name of the resource No MessagePayload.RegisteredResource.MktOrganisation.RegisteredInterTie mrid Master resource identifier of the registered intertie resource as specified in masterfile No name Name of the resource No MessagePayload.RegisteredResource.MktOrganisation.RegisteredLoad mrid Master resource identifier of the registered load resource as specified in masterfile No name Name of the resource No MessagePayload.RegisteredResource.ErrorLog(one to many occurrences) reasons for error in batch mrid Master resource identifier of the resource No starttime Start time of the error in GMT datetime No endtime End time of the error in GMT datetime No errmessage error message errpriority Priority number for the error message integer logtimestamp Date time when the error was created in GMT datetime ** Only one of the three elements within the MKTOrganisation (Generator, Load or Intertie) would be populated for a given response 23

24 6.4.2 Schema (BatchValidationStatus_v1.xsd) The XSD can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications Example XML File (BatchValidationStatus_v1.xml) <?xml version="" encoding="utf-8"?> <!--Sample XML file generated by XMLSpy v2014 rel. 2 ( <BatchValidationStatus xmlns=" BatchValidationStatus_v1.xsd" xmlns:xsi=" xsi:schemalocation=" BatchValidationStatus_v1.xsd BatchValidationStatus_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <BatchStatus> <mrid>1</ mrid> </BatchStatus> </MessagePayload> </BatchValidationStatus> Sample successful batch response: <?xml version="" encoding="utf-8"?> <BatchValidationStatus xmlns=" xmlns:xsi=" xsi:schemalocation=" BatchValidationStatus_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <BatchStatus> <mrid>11</mrid> <description>success</description> <creationtime> t19:32: :00</creationtime> </BatchStatus> </MessagePayload> </BatchValidationStatus> Sample response for failed batch: 24

25 <?xml version="" encoding="utf-8"?> <BatchValidationStatus xmlns=" xmlns:xsi=" xsi:schemalocation=" BatchValidationStatus_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <BatchStatus> <mrid>11</mrid> <description>invalid date range specified</description> <creationtime> t19:32: :00</creationtime> </BatchStatus> <RegisteredResource> <ErrorLog> <mrid>11</mrid> <endtime> t19:32: :00</endtime> <errmessage>invalid date range specified in the request</errmessage> <errpriority>0</errpriority> <logtimestamp> t19:32: :00</logtimestamp> <starttime> t19:30: :00</starttime> </ErrorLog> <MktOrganisation> <RegisteredGenerator> <mrid>gen123</mrid> <name>resourcename</name> </RegisteredGenerator> </ MktOrganisation> </RegisteredResource> </MessagePayload> </BatchValidationStatus> 25

26 7. RetrieveDRCalculatedData 7.1 Use Model The diagram below shows the sequence for retrievedrcalculateddata : Market Participant : : DRSReplace DRSReplacement mentapi prepare request parameters retrievedrcalculateddatarequest Submit request Query database transform Return calculated data retrievedrcalculateddataresponse 26

27 7.2 Operation Details The service has retrievedrcalculateddata_v1 operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD retrievedrcalcu lateddata_v1 Input retrievedrcalc ulateddatareq uest retrievedrcalculated Data_v1.wsdl RequestMeterData_v1.xsd Output retrievedrcalc ulateddatares ponse retrievedrcalculated Data_DocAttach_v1. wsdl DRCalculatedData_v1.xsd Fault faultreturntyp e StandardOutput_v1.xsd The structure of the request for retrieving the baseline and performance data information is described in 5.4. The response structure (DRCalculatedData_v1.xsd) is described below and StandardOutput_v1.xsd has been described earlier in this document in sections 4.4 and WSDL (retrievedrcalculateddata_v1.wsdl) retrievedrcalculateddata_v1.wsdl retrievedrcalculateddata_v1.wsdl Used for normal SOAP messaging retrievedrcalculateddata_docattach_v1.wsdl Used when.net is the source of processing The WSDL can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications. 7.4 Message Type retrievedrcalculateddataresponse Element Table 27

28 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 Pacific Prevailing Time format datetime Source Source system which provides data for this service Version Date reflecting the release this latest version update was related to. MessagePayload (required) MessagePayload.DemandResponseRegistration (one or more occurences) mrid Master resource identifier of the registration (Registration ID) Name Name of the registration No baselinemethod The baseline methodology used for the Registration MessagePayload.DemandResponseRegistration.DemandResponseProvider (required) mrid DRP ID of the resource/registration as provided by masterfile MessagePayload.DemandResponseRegistration.RegisteredGenerator (required) mrid Master resource identifier as provided by masterfile (Resource ID) MessagePayload.DemandResponseRegistration.RegisteredGenerator.MktOrganization.LoadServingEntit y (required) mrid LSE identifier as provided by masterfile MessagePayload.DemandResponseRegistration.Measurement (one or more occurences) this element will be repeated for each distinct trade date requested timeintervallength Length of the interval in minutes. This has to be the same for a given trade date. integer MessagePayload.DemandResponseRegistration.Measurement.PerformanceStatus (required) demandresponseper formancestatus Status of the calculation. Example is Baseline and Reduction calculated successfully. This will be the same for multiple intervals within a given trade date. MessagePayload.DemandResponseRegistration.Measurement.MeasurementValue (one to many occurences) one for each intervalendtime adjustmentvalue Adjustment value used for the interval in calculation decimal baselinevalue Final baseline value after adjusting the Raw Baseline Value used for the interval in calculation decimal intervalendtime Interval end time datetime metervalue Meter value used for the interval decimal 28

29 Element Data Description Type/ Length Req d performancevalue Calculated performance value Decimal yes rawbaselinevalue Average of the previous ten baseline values belonging to the same hour of ten eligible days- eligibility rules will be available on caiso public website Decimal yes timestamp Updated time stamp Datetime yes MessagePayload.DemandResponseRegistration.Measurement.MeasurementValue.BaselineDetail.Measu rementvalue (one to many occurences) intervalendtime Interval end time of the day used in calculating/averaging the baseline value datetime baselinevalue baseline value used for the specified trade date interval in calculation of event day baseline decimal Schema (DRCalculatedData_v1.xsd) The XSD can be found at the following location: Please refer to the latest version of the artifacts found under the technical specifications Example XML File (DRCalculatedData_v1.xml Sample request to retrieve performance data based on a time range. <?xml version="" encoding="utf-8"?> <!--Sample XML file generated by XMLSpy v2016 (x64) ( <RequestMeterData xmlns=" xmlns:xsi=" xsi:schemalocation=" RequestMeterData_v1.xsd"> <MessageHeader> <TimeDate> T19:32: :00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <MeterDataRequest> <requesttype>dr_calculated_data</requesttype> <DemandResponseRegistration> <mrid>r1234</mrid> </DemandResponseRegistration> <Measurement> <measurementtype></measurementtype> <unitmultiplier>k</unitmultiplier> <unitsymbol>wh</unitsymbol> </Measurement> <rangeperiod> 29

30 <end> t00:00:00+00:00</end> <start> t01:00:00+00:00</start> </rangeperiod> <RegisteredGenerator> <mrid>gen123</mrid> </RegisteredGenerator> </MeterDataRequest> </MessagePayload> </RequestMeterData> Sample Response <?xml version="" encoding="utf-8"?> <DRCalculatedData xmlns=" xmlns:xsi=" xsi:schemalocation=" DRCalculatedData_v1.xsd"> <MessageHeader> <TimeDate> T01:00:00+00:00</TimeDate> <Source></Source> <Version>v </Version> </MessageHeader> <MessagePayload> <DemandResponseRegistration> <mrid>r1234</mrid> <name>registration name</name> <DemandResponseProvider> <mrid>drp1</mrid> </DemandResponseProvider> <RegisteredGenerator> <mrid>gen123</mrid> <MktOrganisation> <LoadServingEntity> <mrid>lse1</mrid> </LoadServingEntity> </MktOrganisation> </RegisteredGenerator> <DemandUtilityDistributionCompany> <mrid>udc1</mrid> </DemandUtilityDistributionCompany> <baselinemethod>10-in-10</baselinemethod> <Measurement> <timeintervallength>5</timeintervallength> <MeasurementValue> <adjustmentvalue>0</adjustmentvalue> <baselinevalue>10</baselinevalue> <intervalendtime> t01:00:00+00:00</intervalendtime> <metervalue>10</metervalue> 30

31 12T01:00:00+00:00</intervalEndTime> 11T01:00:00+00:00</intervalEndTime> <performancevalue>10</performancevalue> <rawbaselinevalue>10</rawbaselinevalue> <timestamp> t01:00:00+00:00</timestamp> <BaselineDetail> <MeasurementValue> <baselinevalue>10</baselinevalue> <intervalendtime> </MeasurementValue> <MeasurementValue> <baselinevalue>10</baselinevalue> <intervalendtime> </MeasurementValue> </BaselineDetail> </MeasurementValue> <PerformanceStatus> <demandresponseperformancestatus></demandresponseperformancestatus> </PerformanceStatus> </Measurement> </DemandResponseRegistration> </MessagePayload> </DRCalculatedData> 31

32 Appendix datetime Data Type 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[(+ -)hh: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 Sample datetime format variations supported by DRSReplacement API: T09:30:47Z T09:30:47.000Z T08:00: :00 Note that this version does not support more than 3 decimal places for milliseconds Daily offset Daylight-Savings Time Non Daylight- Savings Time start T07: T08: end T07: T08: Short Day T08: T07: Long Day T07: T08: