Skip to content

PTP Obligation Bid (PTP)

PTP Obligation Bid (PTP)

The following diagram describes the structure of a PTP Obligation bid:

PTPOblication Structure

The CapacitySchedule structure is identical to the structure described in the SelfArrangedAS and CapacityTrade sections of the document. The following diagram describes the structure for maximum prices. If more than one MaximumPrice block is provided, start and end times must not overlap.

MaximumPrice Sub-Structure

On submission, the following table describes the items used for a PTPObligation:

Element Req? Datatype Description Values
startTime K dateTime Start time for bid Valid start hour boundary for trade date
endTime K dateTime End time for bid Valid end hour boundary for trade date
externalId N string External ID QSE supplied
source K string Source settlement point Valid settlement point name
sink K string Sink settlement point Valid settlement point name
bidId1 K string

MP assigned bid 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.

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.
MaximumPrice/startTime Y dateTime Start time for maximum price Valid hour boundary
MaximumPrice/endTime Y dateTime End time for maximum price Valid hour boundary
MaximumPrice/price Y float Maximum price Any value
CapacitySchedule/startTime N dateTime not used not used
CapacitySchedule/endTime N dateTime not used not used

CapacitySchedule/

TmPoint/time

 Y dateTime Absolute time for beginning of interval Valid time between schedule start and end times

CapacitySchedule/

TmPoint/ending

 N dateTime Absolute time for end of interval Valid time between schedule start and end times

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)

The following is an XML example for a PTPObligation:

<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>
    <PTPObligation>
        <startTime>2008-01-01T00:00:00-05:00</startTime>
        <endTime>2008-01-02T00:00:00-05:00</endTime>
        <marketType>DAM</marketType>
        <source>JNSNCNTY8101</source>
        <sink>JUDKINS_8</sink>
        <bidId>926606</bidId>
        <CapacitySchedule>
            <TmPoint>
                <time>2008-01-01T00:00:00-05:00</time>
                <ending>2008-01-02T00:00:00-05:00</ending>
                <value1>327</value1>
            </TmPoint>
        </CapacitySchedule>
        <MaximumPrice>
            <startTime>2008-01-01T00:00:00-05:00</startTime>
            <endTime>2008-01-02T00:00:00-05:00</endTime>
            <price>15.00</price>
        </MaximumPrice>
    </PTPObligation>
</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:PTPObligation>
        <ns1:mRID>AEN.20080614.PTP.926606.AEN.JNSNCNTY8101.JUDKINS_8</ns1:mRID>
        <ns1:externalId/>
        <ns1:status>ACCEPTED</ns1:status>
        <ns1:error>
            <ns1:severity>INFORMATIVE</ns1:severity>
            <ns1:text>Successfully processed the ERCOT PTP BID.</ns1:text>
        </ns1:error>
    </ns1:PTPObligation>
</ns1:BidSet>