This is the content of an email: The counterparties that CPR uses in correlation to the SITARA portfolios set up, should not be set up as books, they should be set up like the example below. All the PB counterparties need to be set up like the example below. The PB should not be set up as books. Any questions or comments, please call me. Russ

Subject: Counterparty set up for Sitara

This is the content of an email: Thanks for the T-Shirt and the magic wand. People have already been at my desk trying to steal my magic wand, it's definitely a crowd pleaser. That was sweet of you to think of me!

Subject: Thank You!

This is the content of an email: As per our discussion, I have done the following to fix the issues with Questar data: - dumped data from 02/04/2001 -> present, for all cycles - fixed the transform component to pull the proper column for utilized capacity and also to assign the correct effective date for each value - re-transformed and re-loaded ALL cycle 5 data (from the *htm files we have) Now, in loading the 86 or so days back into the DB, approx. 3603 PRIMARY KEY violations were logged...this means that they are duplicating point data within the same day, same cycle, etc. If this data could be examined more closely in the reports that are subsequently generated, we can make sure that things are truly copacetic from our side (a "surface" scan of the *.htm files shows that they are indeed duplicating points, usually with different names...the utilized capacity associated with these points is the same though, so this doesn't appear to be a big issue, except for the fact that we will continue to have primary key violations being logged). As always, any questions, just ask. Thanks,

Subject: Questar

This is the content of an email: In a recent CommodityLogic staff meeting, I took stock of the number of people and projects that I have provided from Energy Operations to that team. From conversations that you and I have had, I get the impression that perhaps others have led you to believe that my commitment to CommodityLogic has been limited. The truth is that I hand picked key members of the team and transferred projects that we were already undertaking in Energy Operations to round out the suite of products to be offered through CommodityLogic. I just thought that it might be helpful for you to have the facts so that you are fully informed whenever you are involved in conversations around CommodityLogic. Staffing Contributions CommodityLogic Project Manager (NomLogic): Carrie Slagle, Manager CommodityLogic Project Maanger (Integration): Susan Harrison, Manager CommodityLogic Project Manager (ContactLogic) Mary Solmonson, Senior Director CommodityLogic Team Member (NomLogic): Molly Sumrow, Specialist User Requirement and Testing Staff: Energy Operations Gas Schedulers, Power Confirmation Team and Financial Settlements Projects Transferred to CommodityLogic NomLogic (previously known as Contract Exchange in Energy Operations) ContactLogic (global databases in Energy Operations) Two of the Project Managers on the team, Carrie Slagle and Susan Harrison, were transferred from Energy Operations to CommodityLogic. Both had worked in managerial roles in our natural gas business, reporting to Brent Price. Both had been significantly challenged in the first half of 2000 by roles where they were charged with managing large teams of people. But knowing both Carrie and Susan well, I viewed them as valuable members of the operations team who know a lot about the business. Both have proven in the past to be good project leaders. Therefore, identifying them as project managers for CommodityLogic made a lot of sense -- providing gas operations
Subject: Contributions to CommodityLogic