Resource Parameter Data
The Resource Parameter data section is only used for providing the following transaction types and is applicable to both Inbound requests and Outbound responses:
ERCOT (TX) Nodal
- Three Part Offers (also requires applicable Bids/Offers data)
- Current Operating Plan
- Resource Parameters (ramp rates, minimum online time, max daily starts, etc.)
CAISO (MRTU) - future
- Generation resource parameters
- Import parameters (ramp rates, contingency dispatch flag, pre-dispatch flag)
- Export pre-dispatch flag
Resource Parameters Attributes
| Item | Description | MRTU(CAISO) | TX(ERCOT) |
|---|---|---|---|
| IntervalLength | Interval size that will be used in the schedule detail: ‘PT1H’ is 1 hour, ‘PT1D’ is 1 day Default is one hour (XSD Optional) | ISO Required Field: ‘PT1H’ or ‘PT1D’ | ISO Required Field: ‘PT1H’ or ‘PT1D |
| Location | Region specific Location ID (XSD Required) | ISO Required Field Data Type: Valid CAISO defined Resource ID | ISO Required Field Data Type: Valid ERCOT defined Resource ID |
Parameter Attributes
Each parameter record must include at least ‘Name’, and ‘Value.’
| Item | Description | MRTU(CAISO) | TX(ERCOT) |
|---|---|---|---|
| Name | One of the valid parameter ‘Names’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
| FromInterval | From interval is until the next specified interval or until LastIntervalEnd. For example, submitting a single value for FromInterval will assign that value to the whole interval range, If omitted the values will be applied to all intervals of the defined time period. (XSD Optional) | ISO Required Field Data Type: Integer between 1 and 25 when FirstIntervalBegin and LastIntervalEnd range = one day |
ISO Required Field Data Type: Integer between 1 and 25 when FirstIntervalBegin and LastIntervalEnd range = one day |
| Value | One of the valid parameter ‘Values’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
Parameter Curve Attributes
| Item | Description | MRTU(CAISO) | TX(ERCOT) |
|---|---|---|---|
| Name | One of the valid parameter ‘Names’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
| FromInterval | From interval is until the next specified interval or until LastIntervalEnd. For example, submitting a single value for FromInterval will assign that value to the whole interval range, If omitted the values will be applied to all intervals of the defined time period. (XSD Optional) | ISO Required Field Data Type: Integer between 1 and 25 when FirstIntervalBegin and LastIntervalEnd range = one day |
ISO Required Field Data Type: Integer between 1 and 25 when FirstIntervalBegin and LastIntervalEnd range = one day |
| Point/X | One of the valid X-axis parameter ‘Values’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
| Point/Y | One of the valid Y-axis parameter ‘Values’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
| Point/Z | One of the valid Z-axis parameter ‘Values’ as defined by the below matrix (XSD Required) | ISO Required Field See matrix below | ISO Required Field See matrix below |
TX (Nodal) Parameters
| Parameter | Description | Interval | Value |
|---|---|---|---|
| Status | Description: Resource Operating Mode Data Use: To populate COP, integrated with SCADA | Hourly | Data Type: Valid Resource Status Acronym. See table below |
| HEL | High Emergency Limit in MW Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MW Value meeting the following validations LRL<LEL<LSL<HSL<HEL<HRL. |
| HSL | High Sustainable Limit in MW Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MW Value meeting the following validations LRL<LEL<LSL<HSL<HEL<HRL. |
| LEL | Low Emergency Limit in MW Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MW Value meeting the following validations LRL<LEL<LSL<HSL<HEL<HRL. |
| LSL | High Sustainable Limit in MW Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MW Value meeting the following validations LRL<LEL<LSL<HSL<HEL<HRL. |
| maxSOC | Maximum operating state of charge for given hour ending.Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MWH Value |
| minSOC | Minimum operating state of charge for given hour ending. Data Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MWH Value |
| targetBeginSOC | Target state of charge at beginning of given hour ending, alternatively known as Hour Beginning Planned SOC. | Hourly | Data Type: MWH Value |
| roundTripEfficiency* | Round trip efficiency of ESR | Hourly | Data Type: Percent value |
| EOCFip | Energy Offer Curve % of FIP Data Use: To populate TPO, and settlements | Hourly | Data Type: A value between 0 and 1. Up to 2 decimals places |
| EOCFop | Energy Offer Curve % of FOP Data Use: To populate TPO, and settlements | Hourly | Data Type: A value between 0 and 1. Up to 2 decimals places |
| MinEnergyFip | Minimum Energy % of FIP Data Use: To populate TPO, and settlements | Hourly | Data Type: A value between 0 and 1. Up to 2 decimals places |
| MinEnergyFop | Minimum Energy % of FOP Data Use: To populate TPO, and settlements | Hourly | Data Type: A value between 0 and 1. Up to 2 decimals places |
| MinEnergyCost | Minimum Energy Cost ($/MWh) Data Use: To populate TPO, and settlements | Hourly | Data Type: Decimal value XXXX.XX |
| StartupCold | Start-up cost ($) for a “cold” resource Data Use: To populate TPO, and settlements | Hourly | Data Type: No Decimal value XXXXXX |
| StartupHot | Start-up cost ($) for a “hot” resource Data Use: To populate TPO, and settlements | Hourly | Data Type: No Decimal value XXXXXX |
| StartupIntermediate | Start-up cost ($) for a “intermediate” resource Data Use: To populate TPO, and settlements | Hourly | Data Type: No Decimal value XXXXXX |
| NormalRampRateCurve | Normal Ramp Rate Curve for Resource | Daily | X Value: Ramp Rate Up value in MW per minute Y Value: Ramp Rate Down value in MW per minute Z Value: Break Point in MW |
| EmergencyRampRateCurve | Emergency Ramp Rate Curve for Resource | Daily | X Value: Ramp Rate Up value in MW per minute Y Value: Ramp Rate Down value in MW per minute Z Value: Break Point in MW |
| MinimumOnlineTime | Minimum Online Time for Resource | Daily | Data Type: Time in hours |
| MinimumOfflineTime | Minimum Offline Time for Resource | Daily | Data Type: Time in hours |
| MaximumOnlineTime | Maximum Online Time for Resource | Daily | Data Type: Time in hours |
| MaximumDailyStarts | Maximum Daily starts for Resource | Daily | Data Type: Integer |
| MaximumWeeklyStarts | Maximum Weekly Starts for Resource | Daily | Data Type: Integer |
| MaximumWeeklyEnergy | Maximum Weekly Energy deliverable by resource in MW/hrs | Daily | Data Type: Integer |
| HotStartTime | Start Time for “Hot” Resource | Daily | Data Type: Time in hours |
| IntermediateStartTime | Start Time for “Intermediate” Resource | Daily | Data Type: Time in hours |
| ColdStartTime | Start Time for “Cold” Resource | Daily | Data Type: Time in hours |
| HottoIntermediate | Time it takes for Resource to go from “Hot” to “Intermediate” | Daily | Data Type: Time in hours |
| IntermediatetoCold | Time it takes for Resource to go from “Intermediate” to “Cold” | Daily | Data Type: Time in hours |
| Reason | Reason for adjusting Resource Parameters | Daily | Data Type: String |
*roundTripEfficiency is a new DA/RT resource parameter that will become available with the implementation of the RTC+B market change
Generation Resources
| Status Acronym | Status Description |
|---|---|
| ONRUC | On-Line and the hour is a RUC-Committed Interval |
| ONREG | On-Line Resource with Energy Offer Curve providing Regulation Service |
| ON | On-Line Resource with Energy Offer Curve |
| ONDSR | On-Line Dynamically Scheduled Resource |
| ONOS | On-Line Resource with Output Schedule |
| ONOSREG | On-Line Resource with Output Schedule providing Regulation Service |
| ONDSRREG | On-Line Dynamically Scheduled Resource providing Regulation Service |
| ONTEST | On-Line Test with Output Schedule ONEMR On-Line EMR (available for commitment or dispatch only for ERCOT-declared Emergency Conditions; the QSE may appropriately set LSL and HSL to reflect operating limits) |
| ONRR | On-Line as a synchronous condenser (hydro) providing Responsive Reserve but unavailable for dispatch by SCED and available for commitment by RUC OUT Off-Line and unavailable |
| OFFNS | Off-Line but reserved for Non-Spin |
| OFF | Off-Line but available for commitment by DAM and RUC |
| EMR | Available for commitment only for ERCOT-declared Emergency Condition events; the QSE may appropriately set LSL and HSL to reflect operating limits |
| STARTUP | The Resource is On-Line and in a startup sequence and has no Ancillary Service Obligations. This Resource status is only to be used for Real-Time telemetry purposes |
| SHUTDOWN | The Resource is On-Line and in a shutdown sequence, and has no Ancillary Service Obligations. This Resource status is only to be used for Real-Time telemetry purposes |
| OFFQS | Offline – QSGR available for SCED development |
| ONOPTOUT | On-Line hour is a RUC Buy-Back hour |
| FRRSUP | On-Line Resource with FRRS-UP obligation |
| ONECRS | On-Line as a synchronous condenser (hydro) providing ECRS but unavailable for dispatch by SCED and available for commitment by RUC |
| ONHOLD | On-Line but temporarily unavailable for Dispatch by SCED or Ancillary Service awards |
Load Resources
| Status Acronym | Status Description |
|---|---|
| ONRGL | Available for dispatch of Regulation Service |
| ONCLR | Available for dispatch of a Controllable Load Resource by SCED with an RTM Energy Bid |
| ONRL | Available for dispatch of Responsive Reserve Service, excluding Controllable Load Resources |
| OUTL | Not available |
| FRRSDN | On-Line Controllable Load Resource with FRRS-Down obligation |
| FRRSUP | On-Line Controllable Load Resource with FRRS-Up obligation |
| ONFFRRRSL | Available for FFR, excluding Controllable Load Resources |
| ONECL | Available for ECRS and RRS, excluding Controllable Load Resources |
MRTU (CAISO) Parameters
| Parameter | Description | Interval | Value |
|---|---|---|---|
| ContingencyDispatchFlag | Flag to indicate contingency only operating reserves; Use “Y” for imports or exports that should only be dispatched in the event of a contingency event, else use “N” | Daily | Data Type: Y or N |
| MinimumLoadCost | The operating cost in dollars incurred for a generator to maintain operation at its minimum load | Daily | At MRTU go-live, this field is non-editable |
| EnergyLimitMax | Maximum daily energy limit in MWh that applies to use-limited generators | Daily | Data Type: MWh (XXX.XX) |
| EnergyLimitMin | Minimum daily energy limit in MWh that applies to use-limited generators | Daily | Data Type: MWh (XXX.XX) |
| RegulatingRampRate | Ramp rate for generators when providing regulation | Daily | Data Type: MW (XXX.XX) |
| OperationalRampRate | Ramp rate for imports when providing energy | Daily | Data Type: MW (XXX.XX) |
| OpReserveRampRate | Ramp rate for imports and generators when providing spin or non-spin | Daily | Data Type: MW (XXX.XX) |
| MinHourlyBlock | Minimum number of consecutive hours that the ISO must award at the same quantity (imports/exports only) | Daily | Data Type: hours (XX) |
MRTU (CAISO) Parameter Curves
| Parameter | Description | Interval | Value |
|---|---|---|---|
| OperationalRampRate | Ramp rate curve for generators when providing energy | Daily | X Value: Operating Level in MW Y Value: Ramp Rate in MW/minute |
| StartUpCostCurve | The startup cost curve for generators; set of three segments comprised of the cooling time in minutes, and price in dollars | Daily | At MRTU go-live, this field is non-editable |
| StartupTimeCurve | The startup time curve for generators; set of three segments of the cooling time in minutes, and startup time in minutes | Daily | X Value: Cooling Time in minutes Y Value: Startup Time in minutes Note: Values entered must be less than the Master File values |
| DistributionFactors | Applies to aggregated generators and provides the distribution % of each unit associated with the aggregated resource | Hourly | X Value: Unit Name Y Value: % expressed as a decimal value |
Additional Resource Parameter Details
Definition of Resource Parameter Business key
The business key for a resource parameter is defined as the unique combination of:
- Region
- MarketParticipant
- Interval
- Location
- <Parameter > or <ParameterCurve >
- Name
Handling of Duplicates records for same Resource Parameter Business Key in same submission
If an APX Scheduling API file is submitted with duplicate resource parameters for the same business key, all resource parameters that match that business key will be rejected and won’t be saved into the APX MarketSuiteTM.
Replacing Resource Parameter Data To replace a previously submitted resource parameter, simply submit an APX Scheduling API file that contains the same <MarketParticipantData> and <ResourceParameters> business keys. The data in the new file will expire previously submitted data for this same business key.
Cancelling / Omitting Intervals for Resource Parameters
Resource Parameters cannot be cancelled. <Parameter> data can be omitted (leaving the existing value in the APX system unchanged) by omitting the “Value” attribute in order to skip specific intervals.
Parameter Example (Interval 2 is omitted):
<MarketParticipantData Region="MRTU" MarketParticipant="SCID1" MarketStage="DA" FirstIntervalBegin="2021-03-02T08:00:00Z" LastIntervalEnd="2021-03-03T08:00:00Z">
<ResourceParameters Location="GEN_1">
<Parameter FromInterval="1" Name="HSL" Value="220"/>
<Parameter FromInterval="2" Name="HSL"/>
<Parameter FromInterval="3" Name="HSL" Value="225"/>
</ResourceParameters>
</MarketParticipantData><ParameterCurve> data can be omitted (leaving the existing value in the APX system unchanged) by omitting the “X” and “Y” attributes from the <Point> element in order to skip specific intervals.
ParameterCurve Example (Interval 2 is omitted):
<MarketParticipantData Region="MRTU" MarketParticipant="SCID1" MarketStage="DA" FirstIntervalBegin="2021-09-17T05:00:00Z" LastIntervalEnd="2021-09-18T05:00:00Z">
<ResourceParameters IntervalLength="PT1H" Location="GEN_1">
<ParameterCurve FromInterval="1" Name="Distribution Factors">
<Point X="Unit_A" Y=".2"/>
<Point X="Unit_B" Y=".5"/>
<Point X="Unit_C" Y=".3"/>
</ParameterCurve>
<ParameterCurve FromInterval="2" Name="Distribution Factors">
<Point />
</ParameterCurve>
<ParameterCurve FromInterval="3" Name="Distribution Factors">
<Point X="Unit_A" Y=".2"/>
<Point X="Unit_B" Y=".5"/>
<Point X="Unit_C" Y=".3"/>
</ParameterCurve>
</ResourceParameters>
</MarketParticipantData>