Market MCPCs
Market MCPCs
The purpose of this interface is to provide a query for MCPCs, for either the DAM or SASM market. Specific SASM ID is needed for SASM market type.
The request message would use the following message fields:
Message Element Value Header/Verb get Header/Noun MCPCs Header/Source Market participant ID Header/UserID ID of user Request/MarketType DAM or SASM Request/TradingDate Trading date Request/Option Optional: SASM ID (required for SASM) Format: YYYYMMDDHHMMSS
The purpose of this interface is to provide a query for MCPCs for the DAM market.
The request message would use the following message fields
Message Element Value Header/Verb get Header/Noun MCPCs Header/Source Market participant ID Header/UserID ID of user Request/MarketType DAM or RTM Request/TradingDate Trading date Request/StartTime Start time of interest for RTM MarketType Request/EndTime End time of interest for RTM MarketType
The corresponding response messages would use the following message fields:
Message Element | Value |
---|---|
Header/Verb | reply |
Header/Noun | MCPCs |
Header/Source | ERCOT |
Reply/ReplyCode | Reply code, success=OK, error=ERROR or FATAL |
Reply/Error | Error message, if error encountered |
Payload/ | MCPCs |
The following diagram describes the structure of MCPCs:
Within each MCPCSchedule, an asType is specified and the values of ‘value1’ convey individual MCPC values.
The following is an XML example:
<ns1:MCPCs xmlns:ns0="http://www.ercot.com/schema/2007-05/nodal/eip/il"
xmlns:ns1="http://www.ercot.com/schema/2007-06/nodal/ews">
<ns1:MCPCSchedule>
<ns1:time>2023-04-07T00:00:00-05:00</ns1:time>
<ns1:ending>2023-04-07T01:00:00-05:00</ns1:ending>
<ns1:value1>0.0</ns1:value1>
<ns1:asType>ECRS</ns1:asType>
<ns1:marketType>DAM</ns1:marketType>
</ns1:MCPCSchedule>
<ns1:MCPCSchedule>
<ns1:time>2023-04-07T00:00:00-05:00</ns1:time>
<ns1:ending>2023-04-07T01:00:00-05:00</ns1:ending>
<ns1:value1>0.01</ns1:value1>
<ns1:asType>Non-Spin</ns1:asType>
<ns1:marketType>DAM</ns1:marketType>
</ns1:MCPCSchedule>
<ns1:MCPCSchedule>
<ns1:time>2023-04-07T00:00:00-05:00</ns1:time>
<ns1:ending>2023-04-07T01:00:00-05:00</ns1:ending>
<ns1:value1>3.69</ns1:value1>
<ns1:asType>Reg-Down</ns1:asType>
<ns1:marketType>DAM</ns1:marketType>
</ns1:MCPCSchedule>
<ns1:MCPCSchedule>
<ns1:time>2023-04-07T00:00:00-05:00</ns1:time>
<ns1:ending>2023-04-07T01:00:00-05:00</ns1:ending>
<ns1:value1>4.0</ns1:value1>
<ns1:asType>Reg-Up</ns1:asType>
<ns1:marketType>DAM</ns1:marketType>
</ns1:MCPCSchedule>
<ns1:MCPCSchedule>
<ns1:time>2023-04-07T00:00:00-05:00</ns1:time>
<ns1:ending>2023-04-07T01:00:00-05:00</ns1:ending>
<ns1:value1>12.0</ns1:value1>
<ns1:asType>RRS</ns1:asType>
<ns1:marketType>DAM</ns1:marketType>
</ns1:MCPCSchedule>
</ns1:MCPCs>
New example for RTC+B Implementation
<ns1:MCPCs xmlns:ns0="http://www.ercot.com/schema/2007-05/nodal/eip/il" xmlns:ns1="http://www.ercot.com/schema/2007-06/nodal/ews"> <ns1:MCPCSchedule> <ns1:time>2023-04-07T00:00:00-05:00</ns1:time> <ns1:value1>0.0</ns1:value1> <ns1:asType>ECRS</ns1:asType> <ns1:marketType>RTM</ns1:marketType> </ns1:MCPCSchedule> <ns1:MCPCSchedule> <ns1:time>2023-04-07T00:00:00-05:00</ns1:time> <ns1:value1>0.01</ns1:value1> <ns1:asType>Non-Spin</ns1:asType> <ns1:marketType>RTM</ns1:marketType> </ns1:MCPCSchedule> <ns1:MCPCSchedule> <ns1:time>2023-04-07T00:00:00-05:00</ns1:time> <ns1:value1>3.69</ns1:value1> <ns1:asType>Reg-Down</ns1:asType> <ns1:marketType>RTM</ns1:marketType> </ns1:MCPCSchedule> <ns1:MCPCSchedule> <ns1:time>2023-04-07T00:00:00-05:00</ns1:time> <ns1:value1>4.0</ns1:value1> <ns1:asType>Reg-Up</ns1:asType> <ns1:marketType>RTM</ns1:marketType> </ns1:MCPCSchedule> <ns1:MCPCSchedule> <ns1:time>2023-04-07T00:00:00-05:00</ns1:time> <ns1:value1>12.0</ns1:value1> <ns1:asType>RRS</ns1:asType> <ns1:marketType>RTM</ns1:marketType> </ns1:MCPCSchedule> </ns1:MCPCs>