Skip to content

PTP Obligation with Links to Option (CRR)

The following diagram describes the structure of a PTP Obligation w/ Links to Option:

PTP Obligation with Links to Option (CRR) Structure

The following structure is used for minimum reservation prices. Note than if more than on MinimumReservationPrice is provided, the start and end times must not overlap.

MinimumReservationPrice Structure

The CapacitySchedule structure is identical to the structure described previously in this document. On submission, the following table describes the items used for a CRR. In addition, the PeakLoadForecast must be specified for NOIEs.

Element Req? Datatype Description Values
startTime K dateTime Start time for offer Valid start hour boundary for trade date
endTime K dateTime End time for offer Valid end hour boundary for trade date
externalId N string External ID QSE supplied
crrId K string CRR ID ID of CRR
offerId K string

Offer ID

ERCOT’s preference is for QSEs to submit the same Bid/Offer ID for each hour in the submission, versus submitting a different Bid/Offer ID for every hour.  The market system treats either submission format the exact same way.  The purpose of this is to optimize system performance.

QSE supplied

Value Restrictions:

Only alpha numeric, “_”(underscore) and “-“(dash) are valid characters. First and last character should be alpha numeric.

Min Length: 2chars.

Max Length: 12 chars.
crrAccountHolderId K string CRR account holder ID ID of CRR account holder
Source K string Source settlement point Valid settlement point name
Sink K string Sink settlement point Valid settlement point name
CapacitySchedule/startTime N dateTime not used not used
CapacitySchedule/endTime N dateTime not used not used

CapacitySchedule/

TmPoint/time

 Y dateTime Absolute start time for interval Valid time in the trading date

CapacitySchedule/

TmPoint/ending

 N dateTime Absolute end time for interval Valid time in the trading date

CapacitySchedule/

TmPoint/value1

 Y float Megawatts >= 0

CapacitySchedule /

TmPoint/multiHourBlock

 N Boolean Indicates if offer must be taken as a block for all hours true or false (default=false)

MinimumReservationPrice/

startTime

 Y dateTime Start time for minimum reservation price Valid hour boundary

MinimumReservationPrice/

endTime

 Y dateTime End time for minimum reservation price Valid hour boundary

MinimumReservationPrice/

Price

 N decimal Minimum price in $/MWh Default (if not specified) is $2000
NOIEPeakLoadForecast Y float Peak load forecast Peak load forecast in MW

The following is an XML example for a PTP Obligation w/ Links to Option:

<BidSet xmlns="http://www.ercot.com/schema/2007-06/nodal/ews" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.ercot.com/schema/2007-06/nodal/ews ErcotTransactions.xsd">
    <tradingDate>2008-01-01</tradingDate>
    <CRR>
        <startTime>2008-01-01T00:00:00-05:00</startTime>
        <endTime>2008-01-02T00:00:00-05:00</endTime>
        <marketType>DAM</marketType>
        <crrId>779265</crrId>
        <offerId>868558</offerId>
        <crrAccountHolderId>XCRRAH</crrAccountHolderId>
        <source>TNSCLP3___8W</source>
        <sink>TNSCLP3___8X</sink>
        <CapacitySchedule>
            <TmPoint>
                <time>2008-01-01T00:00:00-05:00</time>
                <ending>2008-01-02T00:00:00-05:00</ending>
                <value1>20</value1>
            </TmPoint>
        </CapacitySchedule>
        <MinimumReservationPrice>
            <startTime>2008-01-01T00:00:00-05:00</startTime>
            <endTime>2008-01-02T00:00:00-05:00</endTime>
            <price>20</price>
        </MinimumReservationPrice>
        <NOIEPeakLoadForecast>20</NOIEPeakLoadForecast>
    </CRR>
</BidSet>

And the corresponding response:

<ns1:BidSet xmlns:ns1="http://www.ercot.com/schema/2007-06/nodal/ews">
    <ns1:tradingDate>2008-06-14</ns1:tradingDate>
    <ns1:CRR>
        <ns1:mRID>AEN.20080614.CRR.779265.868558.8008717662000.TNSCLP3___8W.TNSCLP3___8X</ns1:mRID>
        <ns1:externalId/>
        <ns1:status>ACCEPTED</ns1:status>
        <ns1:error>
            <ns1:severity>INFORMATIVE</ns1:severity>
            <ns1:text>Successfully processed the ERCOT CRR OFFER.</ns1:text>
        </ns1:error>
    </ns1:CRR>
</ns1:BidSet>