Do the Day-Ahead and Real-Time market clearing algorithms clear Ancillary Services (ASM) products differently based on a unit's ramp rate curve, if enabled?
The Ramp Rate for Day-Ahead is RR*60 minutes. For Real-Time, the Ramp Rate is RR*5 minutes.
Company X is only submitting Day-Ahead and Real-Time offers for 2 days in advance (OD+2 and OD+3) but there are offers in the MISO portal that go all the way out to OD+6. Where are these offers coming from and is MISO able to use them to commit our units? An example would be we only submitted offers for 4/27-4/29, but I see offers all the way out to 5/4 in the portal.
There are a couple different solutions for this question.
A. Company X submits real-time offers for 5/4, 5/5-5/6.MISO can then copy forward the offer from 5/6 for 5/7-5/9. MISO can then commit our unit for 5/9 on 5/4 for reliability using the copied forward offer from 5/.6 (Yes, MISO would only commit a unit this far ahead if it has a long lead, for example its startup time + notification time is 90 hours. In this scenario, if MISO needs this unit on 5/9 00:00 AM EST because of its economic offers, MISO would send out a notification call on 5/4 or 5/5.
B. Company X is financially bound to that offer (It depends. Take the same example, if it turns out this unit cannot participate on 5/9 00:00 AM and Company X comes because more than 90 hours ahead to turn it off, it is not financially binding. If Company X comes back 85 hours ahead saying this unit cannot be on for 5/9 00:00, there would be charges). MISO would only commit a unit this far ahead if it is a long lead, for example its startup time + notification time is 90 hours.
On the Day-Ahead Product Binding Constraints report, how are the shadow prices (if they are) are reflected in the Locational Marginal Pricing (LMPs). If a constraint is reported as binding in this file, is that price spread reflected in the Marginal Congestion Component of the LMPs?
A binging constraint will impact the Marginal Clearing Price (MCP). So Regional Dispatch Transfer (RDT) shadow prices would be reflected in LMPs
What is the process for uploading XML for Demand Bids?
Please refer to the link below: https://www.misoenergy.org/markets-and-operations/#nt=%2Fmarketsandopstype%3ATechnical%20Infrastructure%2Ftechnicalinfrastructureype%3ADART&t=10&p=0&s=&sd=
If you scroll down all the way to the bottom, the MUI 2.0 documentations are all available there. If you haven't already, I would suggest going through the MUI User Guide:
https://cdn.misoenergy.org/MUI%202.0%20API%20User%20Guide629008.pdf
How do I submit virtual bids and offers through an API?
The MUI API will provide guidance on that. https://cdn.misoenergy.org/MUI%202.0%20API%20User%20Guide629008.pdf
Where can I locate a list of daily day-ahead binding constraints?
https://www.misoenergy.org/markets-and-operations/real-time--market-data/market-reports/#nt=%2FMarketReportType%3ADay-Ahead%2FMarketReportName%3ADay-Ahead%20Binding%20Constraints%20(xls)&t=10&p=0&s=MarketReportPublished&sd=desc
The Ramp Rate for Day-Ahead is RR*60 minutes. For Real-Time, the Ramp Rate is RR*5 minutes.
Company X is only submitting Day-Ahead and Real-Time offers for 2 days in advance (OD+2 and OD+3) but there are offers in the MISO portal that go all the way out to OD+6. Where are these offers coming from and is MISO able to use them to commit our units? An example would be we only submitted offers for 4/27-4/29, but I see offers all the way out to 5/4 in the portal.
There are a couple different solutions for this question.
A. Company X submits real-time offers for 5/4, 5/5-5/6.MISO can then copy forward the offer from 5/6 for 5/7-5/9. MISO can then commit our unit for 5/9 on 5/4 for reliability using the copied forward offer from 5/.6 (Yes, MISO would only commit a unit this far ahead if it has a long lead, for example its startup time + notification time is 90 hours. In this scenario, if MISO needs this unit on 5/9 00:00 AM EST because of its economic offers, MISO would send out a notification call on 5/4 or 5/5.
B. Company X is financially bound to that offer (It depends. Take the same example, if it turns out this unit cannot participate on 5/9 00:00 AM and Company X comes because more than 90 hours ahead to turn it off, it is not financially binding. If Company X comes back 85 hours ahead saying this unit cannot be on for 5/9 00:00, there would be charges). MISO would only commit a unit this far ahead if it is a long lead, for example its startup time + notification time is 90 hours.
On the Day-Ahead Product Binding Constraints report, how are the shadow prices (if they are) are reflected in the Locational Marginal Pricing (LMPs). If a constraint is reported as binding in this file, is that price spread reflected in the Marginal Congestion Component of the LMPs?
A binging constraint will impact the Marginal Clearing Price (MCP). So Regional Dispatch Transfer (RDT) shadow prices would be reflected in LMPs
What is the process for uploading XML for Demand Bids?
Please refer to the link below: https://www.misoenergy.org/markets-and-operations/#nt=%2Fmarketsandopstype%3ATechnical%20Infrastructure%2Ftechnicalinfrastructureype%3ADART&t=10&p=0&s=&sd=
If you scroll down all the way to the bottom, the MUI 2.0 documentations are all available there. If you haven't already, I would suggest going through the MUI User Guide:
https://cdn.misoenergy.org/MUI%202.0%20API%20User%20Guide629008.pdf
How do I submit virtual bids and offers through an API?
The MUI API will provide guidance on that. https://cdn.misoenergy.org/MUI%202.0%20API%20User%20Guide629008.pdf
Where can I locate a list of daily day-ahead binding constraints?
https://www.misoenergy.org/markets-and-operations/real-time--market-data/market-reports/#nt=%2FMarketReportType%3ADay-Ahead%2FMarketReportName%3ADay-Ahead%20Binding%20Constraints%20(xls)&t=10&p=0&s=MarketReportPublished&sd=desc