The Peak RC Reliability Messaging Tool forwards Merchant Alert email from webSmartOASIS to the Market and Reliability email group Merchant without access to webSmartOASIS bulletin board: Determines that a Merchant Alert is necessary. Contacts the host BA. Merchant requests the BA to issue, on the Merchant’s behalf, a Merchant Alert via the Peak RC Reliability Messaging Tool the Market Reliability email group. Merchant provides BA with the information listed below. Contact information. POR/POD. This information would not be required for outages of primary communication or e-Tagging systems. Date and start/stop time. Optional comments, if any, but do not include either price or quantity when initiating an Alert for the purpose of procuring energy to avoid or remedy an energy or capacity emergency. Note: In this circumstance, the final decision on issuing the Merchant Alert rests solely with the BA. A merchant receiving the Merchant Alert who has excess resource capability, and is willing to provide assistance, directly contacts the requesting merchant to negotiate terms. All information exchanged via this process is stored and retained for at least one year. Merchant Alert Testing To help ensure proper functionality of the Merchant Alert process, tests will be conducted on a regular basis. Under normal conditions, these will be performed no less than four times per year (quarterly) and no more than twelve times per year (monthly). The “Comment” field of the Alert will clearly state that a test is being conducted. The frequency of these tests as well as who will conduct each test will be determined by the WECC Market Interface Committee or by other means as required to maintain continued operations. The timing of these tests will be coordinated with the Reliability Coordinators.
The Peak RC Reliability Messaging Tool forwards Merchant Alert email from webSmartOASIS to the Market and Reliability email group Merchant without access to webSmartOASIS bulletin board: Determines that a Merchant Alert is necessary. Contacts the host BA. Merchant requests the BA to issue, on the Merchant’s behalf, a Merchant Alert via the Peak RC Reliability Messaging Tool the Market Reliability email group. Merchant provides BA with the information listed below. Contact information. POR/POD. This information would not be required for outages of primary communication or e-Tagging systems. Date and start/stop time. Optional comments, if any, but do not include either price or quantity when initiating an Alert for the purpose of procuring energy to avoid or remedy an energy or capacity emergency. Note: In this circumstance, the final decision on issuing the Merchant Alert rests solely with the BA. A merchant receiving the Merchant Alert who has excess resource capability, and is willing to provide assistance, directly contacts the requesting merchant to negotiate terms. All information exchanged via this process is stored and retained for at least one year. Merchant Alert Testing To help ensure proper functionality of the Merchant Alert process, tests will be conducted on a regular basis. Under normal conditions, these will be performed no less than four times per year (quarterly) and no more than twelve times per year (monthly). The “Comment” field of the Alert will clearly state that a test is being conducted. The frequency of these tests as well as who will conduct each test will be determined by the WECC Market Interface Committee or by other means as required to maintain continued operations. The timing of these tests will be coordinated with the Reliability Coordinators.
07%20-%202017-07-20%20MIC%20Merchant%20Alert%20Protocol%20Guideline_LB.docx