Automated Load Forecast System (ALFS) Interface Specification. Fall 2017 Release

Size: px

Start display at page:

Download "Automated Load Forecast System (ALFS) Interface Specification. Fall 2017 Release"

Iris Hill
6 years ago
Views:

1 Automated Load Forecast System (ALFS) Interface Specification Fall 2017 Release Version: 1.1 March 27, 2017

2 Revision History Date Version Description 03/01/ Initial document release related to the Load Forecast Interfaces. ExternalEntityLoadForecast 3/27/ Add technical specification for Submit VER Forecast ExternalEnergyForecast ISO Public Page 2 of 14

3 TABLE OF CONTENTS 1 Introduction Purpose Related Documents Document Release Notes Version 1.0.x Submit External Entity Load Forecast Operation Details External Entity Load Forecast Element Table Fault Return Fault Return Element Table Schema (StandardOutput.xsd) Appendix Data Type ISO Public Page 3 of 14

4 1 Introduction 1.1 Purpose This document describes submit and response XSDs related to the Area Load Forecast System (ALFS) Interface. 1.2 Related Documents For more information on current or past project initiative releases, please refer to the release planning page at ISO Public Page 4 of 14

5 2 Document Release Notes 2.1 Version 1.0.x This document release version affects the following system data interface specifications: # Service Schema Version # Major Minor 1 new submitexternalentityloadforecast_v1 ExternalEntityLoadForecast_v1.xsd 1 v Existing Submit5MinFSPVERForecast_v1 ExternalEnergyForecast_v1.xsd 1 V ISO Public Page 5 of 14

6 3 Submit External Entity Load Forecast 3.1 Operation Details The service has one operation with three message types. All input and output messages are in XML format. Refer to Section for time data logic on data horizon window. Operation Message Types Message WSDL XSD submitexternale ntityloadforecas t_v1 Input SubmitExternalEntityLoad Forecast submitexternalent ityloadforecast_v 1.wsdl ExternalEntityLoadForecas t_v1.xsd Output Standard reply output SubmitStandardOutput.xsd Fault faultreturntype StandardOutput.xsd 3.2 External Entity Load Forecast Element Table Element Data Description Type Req d Message Header (optional) TimeDate Application level relevant time and date for when this instance of the message was produced. Source Source system which provides data for this service. string Version Minor Version Identifier; Date reflecting the release this latest version update was related to. string Message Payload forecasttype Load forecast type: 1. The Anode Type representing the entity s load forecast zone String For Entity forecast the value should be: LFZ AggregateNode. mrid Aggregate Node representing the Entity load forecast zone (32 characters) String ISO Public Page 6 of 14

7 Element Data Description Type Req d CurveData. AreaLoadCurve. starttime The start time representing the beginning time of the segment break point of the load curve; expected at a 5 min, 15 min, or hourly break point, with length of the load forecast being at a 5 min, 15 min, or hourly granularity. Note: the submit user is expected to provide the data at the correct break point interval, the system will not break the data down. For example, if a user is intending to submit 5 minute load forecast and has a flat load for 30 minutes, we would expect 6 different break points with the same MW value. CurveData. AreaLoadCurve. endtime The end time representing the end time of the segment break point of the load curve; expected at a 5 min, 15 min, or hourly break point, with length of the load forecast being at a 5 min, 15 min, or hourly granularity. Note: the submit user is expected to provide the data at the correct break point interval, the system will not break the data down. For example, if a user is intending to submit 5 minute load forecast and has a flat load for 30 minutes, we would expect 6 different break points with the same MW value. CurveData. AreaLoadCurve. timepoints. Value1 The Mega Watt value of the submitted forecasted load for the interval represented by the start and end time Float CurveData. AreaLoadCurve. Value1Multiplier M Value representing Mega for the Mega Watt; the load forecast value is assumed to be in Megawatt, regardless of submitted multiplier. Enumeration No CurveData. AreaLoadCurve. Value1Unit W Value representing Watt for the Mega Watt; the load forecast value is assumed to be in Megawatt, regardless of submitted unit. Enumeration No Data Logic The system will limit the submitted forecast to 40 minutes before the binding hour up to a 96 hour time horizon; data submitted less than the 40 minute horizon will not be stored or used in forecast calculations, data submitted after the 360 hour time horizon will not be stored or used in forecast calculations. Ex: ISO Public Page 7 of 14

8 Current time 04/01/ :14:30 User can submit forecast from 04/01/ :00:00 till 04/06/ :00:00. 4 Submit 5 Min VER Forecast 4.1 Operation Details The service has one operation with three message types. All input and output messages are in XML format. Operation Message Types Message WSDL XSD Submit5MinFSP VERForecast_v1 Input Submit5MinFSPVERFore cast submit5minfspv ERForecast_v1.w sdl ExternalEnergyForecast_v1. xsd Output Standard reply output SubmitStandardOutput.xsd Fault faultreturntype StandardOutput.xsd 4.2 External Energy Forecast Element Table Element Data Description Type Req d Message Header (optional) TimeDate Application level relevant time and date for when this instance of the message was produced. Source Source system which provides data for this service. string Version Minor Version Identifier; Date reflecting the release this latest version update was related to. string Message Payload forecasthorizonperiod: start The Start time representing the start of the time frame of the VER forecast dataset forecasthorizonperiod: end The End time representing the end of the time frame of the VER forecast dataset ISO Public Page 8 of 14

9 Element Data Description Type Req d RegisterdGenerator: mrid The Resource MRID of the VER resource. Notes: only resource registered as VER resources are processed by the system, non VER resources will not cause an error in the submit process, but will be ignored in the data processing. String RegisterdGenerator: EnergyForecast: forecasttype The forecast type being submitted identifying the resource as a VER energy producer versus a VER energy consumer Notes: for VER resource submit, the interface only allows EPF for VER resource producers Enumeration RegisterdGenerator: EnergyForecast: EnergyForecastInterval: energyforecast: units MW Value representing the units of measurement of the data being submitted String RegisterdGenerator: EnergyForecast: EnergyForecastInterval: energyforecast: value MW value representing the VER resource generation output during the interval period Float RegisterdGenerator: EnergyForecast: EnergyForecastInterval: intervalperiod: start The start interval breakpoint for the VER output Notes: the start interval should be represented at the 5 minute break point. RegisterdGenerator: EnergyForecast: EnergyForecastInterval: intervalperiod: end The end interval breakpoint for the VER output Notes: the end interval should be represented at the 5 minute break point. ISO Public Page 9 of 14

10 Element Data Description Type Req d SchedulingCoordinator: mrid The SC representing the VER resource String Time Submit The VER forecast submit expects that the participants submit a rolling 5 hour window, for the entire VER portfolio. The information should be submitted at a 5 minute breakpoint granularity, with the MW output at each 5 minute break point. Forecast submitted will be processed and used as part of the next Market run to determine VER output capabilities. Processing time takes approximately 3 Minutes for submitted data to be used by the next market interval, the process used to evaluate the submitted forecast runs every 5 minutes, at a 4:15 minute offset. For example: VER data submitted after 10:59:15 and before 11:04:15, will be processed and sent to the market by 11:07:15, to be used for the 11:07:30 RTD run process, to determine the dispatch of 11:15:00. Note: the participant should account for processing time of data submit to data population. 5 Fault Return 5.1 Fault Return The fault return message is the same for all ALFS services. Element Table Element Data Description Type Req d 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 collectiontype Event log collection type. string No collectionquantity Event log collection quantity. string No ISO Public Page 10 of 14

11 Element Data Description Type Req d 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. 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 ISO Public Page 11 of 14

12 Schema (StandardOutput.xsd) <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns:m=" xmlns:xs=" targetnamespace=" 13/StandardOutput.xsd" elementformdefault="qualified"> <xs:element name="outputdatatype" type="m:outputdatatype"/> <xs:complextype name="outputdatatype"> <xs:sequence> <xs:element name="eventlog" type="m:eventlog" maxoccurs="unbounded"/> </xs:sequence> </xs:complextype> <xs:complextype name="eventlog"> <xs:sequence> <xs:element name="id" type="xs:string" minoccurs="0"/> <xs:element name="name" type="xs:string" minoccurs="0"/> <xs:element name="description" type="xs:string" minoccurs="0"/> <xs:element name="type" type="xs:string" minoccurs="0"/> <xs:element name="creationtime" type="xs:" minoccurs="0"/> <xs:element name="collectiontype" type="xs:string" minoccurs="0"/> <xs:element name="collectionquantity" type="xs:string" minoccurs="0"/> <xs:element name="event" type="m:event" maxoccurs="unbounded"/> <xs:element name="service" type="m:service" minoccurs="0" maxoccurs="unbounded"/> </xs:sequence> </xs:complextype> <xs:complextype name="event"> <xs:sequence> <xs:element name="result" type="xs:string"/> <xs:element name="id" type="xs:string" minoccurs="0"/> <xs:element name="name" type="xs:string" minoccurs="0"/> <xs:element name="description" type="xs:string" minoccurs="0"/> <xs:element name="creationtime" type="xs:" minoccurs="0"/> <xs:element name="severity" type="xs:string" minoccurs="0"/> <xs:element name="priority" type="xs:string" minoccurs="0"/> <xs:element name="sequencenumber" type="xs:string" minoccurs="0"/> <xs:element name="eventtype" type="xs:string" minoccurs="0"/> </xs:sequence> </xs:complextype> <xs:complextype name="service"> <xs:sequence> <xs:element name="id" type="xs:string"/> <xs:element name="name" type="xs:string"/> <xs:element name="description" type="xs:string"/> <xs:element name="comments" type="xs:string"/> </xs:sequence> </xs:complextype> </xs:schema> ISO Public Page 12 of 14

13 6 Appendix A Data Type The data type is used to specify a date and a time. Any valid XML datetime format with timezone can be used for the request, but the response will always follow one format. TimeZone information in the request and response is mandatory and it can either be specified as offset hours from UTC or use the Z timezone identifier. The is specified in the following form YYYY-MM-DDThh:mm:ss[(+ -)hh:mm:ss] where: 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 OR YYYY-MM-DDThh:mm:ssZ The Z at the end indicates that the timezone is in GMT/UTC format Note: All components are required. Request Examples of format: T00:00:00-07:00 offset of 7 hours based on Pacific Daylight Time T00:00:00-08:00 offset of 8 hours based on Pacific Standard Time T08:00:00-00:00 Timestamp in GMT/UTC T07:00:00Z Timestamp in GMT/UTC Response Example of format: T08:00:00-00:00 Timestamp in GMT/UTC T07:00:00-00:00 Timestamp in GMT/UTC ISO Public Page 13 of 14

14 Note: There will be a standard output error response returned if the request refers to a datetime format other than the defined acceptable formats described above. ISO Public Page 14 of 14

Automated Load Forecast System (ALFS) For RC Interface Specification

Automated Load Forecast System (ALFS) For RC Interface Specification Version: 1.0 October 22, 2018 Revision History Date Version Description 10/23/2018 1.0 Initial document release related to the Load