Dropped Schedules_Mismatch Settlements_0711 ... - ERCOT.com

judgedrunkshipServers

Nov 17, 2013 (3 years and 4 months ago)

60 views

October 13, 2008

COPS

Dropped Schedules

Mismatch Settlement

7/11/2008 and 7/14/2008

ERCOT

2

2

October 13, 2008

Overview
-

IT


MOSTML (Dynamic rating, ercotprp, pucprp) deployed to production on 9/25


Running app 200% faster



Outage Scheduler deployed to production but encountered display issues


Development is working to port Outage Scheduler to a new platform



Listener production postponed due to connectivity issues


Certain queries allocated too much memory due to xml conversion; natural
growth of data


JVM cannot be extended due to resource limitations on current platform


Development is working to port MOS Sender and Listener to new platform



Both applications to be moved off the Solaris platform


MOSTML to RHEL 3


Not all applications (Apache/Tomcat/Siteminder) have been tested on RHEL 5 or
Windows 2003


Outage Scheduler to Linux; ColdFusion MX 7 (currently ColdFusion 5)


3

3

October 13, 2008

Response Time

9/25/2008

4

4

October 13, 2008

Throughput

9/25/2008

5

5

October 13, 2008

Overview
-

Settlements

7
/
11
/
08


PKG
1
Dropped
Schedules
Ran
7
/
11
Initial
with mismatches
due to dropped
schedules
Per Protocol
9
.
5
,
resettled
7
/
11
within
21
days
7
/
14
/
08


PKG
1
Dropped
Schedules
Ran
7
/
14
Initial
with mismatches
due to dropped
schedules
7
/
11
‘URC’
dispute and
7
/
14
‘MSR’
disputes
received by
Settlements
Ran
7
/
14
Final with
incorrect
‘MSR’
resolution
Ran
7
/
11
Final
with Correct
‘URC’ resolution
,
but was
incomplete due to
nature of the real
issue
Received
re
-
dispute
of
7
/
14
WCS
/
QSE
identify the
root issue for
7
/
11
;
QSE re
-
disputed
Per Protocol
9
.
5
,
resettled
7
/
14
within
21
days
6

6

October 13, 2008

Problems / Mitigation Strategies

Problem

Mitigation Strategy

Business Process Problem


identification of the
“Dropped Schedules” disputes


Revised approach in Wholesale Client Services to
ensure that the dispute is clearly communicated to
S&B as a mismatch dispute due to dropped schedules


We ask that QSEs enter these disputes on the MSR
Charge Type

Business Process Problem


inconsistent / inaccurate
resolution of the dispute



Incorporate new validation step on Initial settlement to
identify and raise flags when an entity is mismatched
across the board in an interval (in case QSE has not
yet notified ERCOT of the situation)


A desktop procedure / checklist has been created to
address this specific type of dispute


All Zonal settlement staff has been made aware of the
issues experienced on 7/11 and 7/14 and of the new
desktop procedure


Zonal settlement staff “lessons learned” session


All “Mismatch” disputes will be worked by a higher
level analyst

IT Problems


Solaris platform




SIR 11926