RTD Indicative MCPC

Info

New interface with RTC+B Implementation

This section describes interfaces used to retrieve RTD Indicative MCPC. The request message would use the following message fields:

Message Element Value
Header/Verb get
Header/Noun RTDIndicativeMCPC
Header/Source Market participant ID
Header/UserID ID of user
Request/StartTime Start time of interest
Request/EndTime End time of interest

The corresponding response messages would use the following message fields:

Message Element Value
Header/Verb reply
Header/Noun RTDIndicativeMCPC
Header/Source ERCOT
Reply/ReplyCode Reply code, success=OK, error=ERROR or FATAL
Reply/Error Error message, if error encountered
Payload/ RTDMCPCS

The structure of RTDMCPCs is described by the following diagram:

RTDMCPCs Structure

RTDMCPC Structure

The following elements are used to report RTD MCPCs:

  • RTD Timestamp
  • Repeated Hour Flag
  • Interval ID
  • Interval Ending
  • Interval Ending Repeated Hour Flag
  • REGUP
  • REGDN
  • RRS
  • ECRS
  • NSPIN

The following is an XML example:

<ns1:RTDMCPCS xmlns:ns1="http://www.ercot.com/schema/2007-06/nodal/ews">
               <ns1:RTDMCPC>
                  <ns1:RTDTimestamp>10/08/2025 14:00:04</ns1:RTDTimestamp>
                  <ns1:RepeatedHourFlag>N</ns1:RepeatedHourFlag>
                  <ns1:IntervalID>1</ns1:IntervalID>
                  <ns1:IntervalEnding>10/08/2025 14:05</ns1:IntervalEnding>
                  <ns1:IntervalEndingRepeatedHourFlag>N</ns1:IntervalEndingRepeatedHourFlag>
                  <ns1:REGUP>0.0</ns1:REGUP>
                  <ns1:REGDN>0.0</ns1:REGDN>
                  <ns1:RRS>0.0</ns1:RRS>
                  <ns1:ECRS>0.0</ns1:ECRS>
                  <ns1:NSPIN>0.0</ns1:NSPIN>
               </ns1:RTDMCPC>
               <ns1:RTDMCPC>
                  <ns1:RTDTimestamp>10/08/2025 14:00:04</ns1:RTDTimestamp>
                  <ns1:RepeatedHourFlag>N</ns1:RepeatedHourFlag>
                  <ns1:IntervalID>2</ns1:IntervalID>
                  <ns1:IntervalEnding>10/08/2025 14:10</ns1:IntervalEnding>
                  <ns1:IntervalEndingRepeatedHourFlag>N</ns1:IntervalEndingRepeatedHourFlag>
                  <ns1:REGUP>0.0</ns1:REGUP>
                  <ns1:REGDN>0.0</ns1:REGDN>
                  <ns1:RRS>0.0</ns1:RRS>
                  <ns1:ECRS>0.0</ns1:ECRS>
                  <ns1:NSPIN>0.0</ns1:NSPIN>
               </ns1:RTDMCPC>
                …
               <ns1:RTDMCPC>
                  <ns1:RTDTimestamp>10/08/2025 14:00:04</ns1:RTDTimestamp>
                  <ns1:RepeatedHourFlag>N</ns1:RepeatedHourFlag>
                  <ns1:IntervalID>10</ns1:IntervalID>
                  <ns1:IntervalEnding>10/08/2025 14:50</ns1:IntervalEnding>
                  <ns1:IntervalEndingRepeatedHourFlag>N</ns1:IntervalEndingRepeatedHourFlag>
                  <ns1:REGUP>0.0</ns1:REGUP>
                  <ns1:REGDN>0.0</ns1:REGDN>
                  <ns1:RRS>0.0</ns1:RRS>
                  <ns1:ECRS>0.0</ns1:ECRS>
                  <ns1:NSPIN>0.0</ns1:NSPIN>
               </ns1:RTDMCPC>
               <ns1:RTDMCPC>
                  <ns1:RTDTimestamp>10/08/2025 14:00:04</ns1:RTDTimestamp>
                  <ns1:RepeatedHourFlag>N</ns1:RepeatedHourFlag>
                  <ns1:IntervalID>11</ns1:IntervalID>
                  <ns1:IntervalEnding>10/08/2025 14:55</ns1:IntervalEnding>
                  <ns1:IntervalEndingRepeatedHourFlag>N</ns1:IntervalEndingRepeatedHourFlag>
                  <ns1:REGUP>0.0</ns1:REGUP>
                  <ns1:REGDN>0.0</ns1:REGDN>
                  <ns1:RRS>0.0</ns1:RRS>
                  <ns1:ECRS>0.0</ns1:ECRS>
                  <ns1:NSPIN>0.0</ns1:NSPIN>
               </ns1:RTDMCPC>
            </ns1:RTDMCPCS>