1 / 7

Issue 2007-I075

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

pascha
Download Presentation

Issue 2007-I075

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 Comparison

  4. Data for Comparison

  5. Market Requirement Upon receipt of an 814_24 containing the REF~2W, ERCOT shall validate that the CR submitting the 814_24 is also the CR with an active CSA relationship.  • If the CSA CR is different than the CR submitting the 814_24 MVO, ERCOT will ignore the REF~2W segment and will process as a MVO to CSA. • ERCOT will validate CSA CR based upon DUNS • Validation of DUNS on exact DUNS or (Option A) • Validation of DUNS based upon umbrella DUNS (Option B) ERCOT will not validate on the 814_24 Move Out (MVO) that includes a REF~1P~B44

  6. ERCOT Analysis • Option A (Validation of DUNS on exact DUNS ) • Initial Estimate of 180 hours for Development and Testing • With the number of hours from the high level estimate, it was determined once the PRR or SCR would go through for approval, it would be worked in a project, and can not be worked as a SIR. • Option B (Validation of DUNS based upon umbrella DUNS) • Initial Estimate of 640 hours for Development and Testing • In addition, in order to allow for one log-in to access information across multiple DUNS, the parent / child relationship was not implemented in the current architecture and would require significant architecture changes (across multiple systems). • With the number of hours from the high level estimate, it was determined once the PRR or SCR would go through for approval, it would be worked in a project, and can not be worked as a SIR.

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

More Related