Prepared Direct Testimony of Robert McCullough on Behalf of the ...

Page 46 <strong>of</strong> 76SE.4TAC-400ancillary services, because I wanted to match only those transactions that were eligible to receivepayment in the event that a given line was congested.I then searched the data for transactions that matched imports on the LADWP system withexports on the IS0 system, by date, hour, scheduling coordinator, and tie-point. Such a matchwould meet the definition <strong>of</strong> a half Death Star (as described below). I also searched for theopposite case, i.e., for transactions that matched exports on the LADWP system with importsh m the IS0 system, by date, hour, scheduling coordinator, and tie-point. Such matches wouldalso meet the definition <strong>of</strong> a half Death Star. Combining the results <strong>of</strong> these two searches by date,hour, and scheduling coordinator yields matches that meet the definition <strong>of</strong> a full Death Star.Occassionally, as in the case with Enron, I included more than one scheduling coordinator at atime to see if they were acting together. It is clear from this analysis (as further described below)that Enron and Portland General Electric were working together on transactions that match thedefinition <strong>of</strong> a Death Star.When I could not find accurate matches, I dropped information from the dataset, so there areundoubtedly more. To avoid double counting, I generally looked only at the hour-ahead market,although it is quite possible to have a Death Star in both the day-ahead and hour-ahead marketsfor the same date, time, and tie-point.What is the source <strong>of</strong> the LADWP scheduling records you used for this purpose?I used files39 called "All Schedules and Prices for 2000.csv" and "All Schedules and Prices for1-1-2001 to 9-6-2001 .csv9' provided by LADWP to the California Senate Select Committee toj9LADWP Transaction Data, First Quarter 1997 thrwgh September 6,2001, Exhibit SEATAC-424.