1 / 9

Avoiding CSA Bypass Issue in MVO Submissions for Power Units

Avoid complications in power unit management by ensuring CSA notifications are correctly followed in MVO submissions. Failure to do so can lead to inactive ESIID causing power outages, potential permit charges, and miscommunication among CRs. Stay proactive and prevent bypassing CSA flags to guarantee smooth operations. Review and compare data from various periods to identify trends and discrepancies. Take necessary steps to address overlooked CSA notifications and establish a clear protocol for MVO submissions to prevent future issues.

twila
Télécharger la présentation

Avoiding CSA Bypass Issue in MVO Submissions for Power Units

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Issue 2007-I075 Non-CSA CR sends MVO with bypass CSA Flag

  2. Issue • Non-CSA CR submits a MVO with the bypass CSA Flag, resulting in CSA CR never knowing the ESIID is not active. CSA premise management company is left with a Unit with no power and may incur charges for permits in the hundreds of Dollars.

  3. Data for Comparison1/29/08 – 1/31/08 and 2/26/08 – 02/28/08

  4. Data for Comparison1/29/08 – 1/31/08 and 2/26/08 – 02/28/08

  5. Data for 02/13/08 – 03/23/08

  6. Data for 02/13/08 – 03/23/08

  7. MVOs with flag from another CR Remaining CRs contains 3 CRs who sent 4 1 CR who sent 2 7 CRs who sent 1

  8. Discussion • It was noticed that in some instances Delete CSA notifications may have been overlooked • For example: • CR A was the current Rep of Record • CR A was the current CSA. • CR B submitted the 814_18 add CSA which was accepted and ERCOT sent the current CSA the 814_18 Delete CSA notification • A week or so after the new CSA was established, the current CR submitted a MVO with the bypass CSA flag bypassing the CSA (from CR B)

  9. Next steps • Where do we go from here?

More Related