## 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 MWData Use: To populate COP and ICCP, and support settlements | Hourly | Data Type: MW Value meeting the following validations LRL or - 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 and 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. 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):** ```xml ``` data can be omitted (leaving the existing value in the APX system unchanged) by omitting the “X” and “Y” attributes from the element in order to skip specific intervals. **ParameterCurve Example (Interval 2 is omitted):** ```xml ```