Message-ID: <10194334.1075855743810.JavaMail.evans@thyme> Date: Tue, 12 Sep 2000 09:12:00 -0700 (PDT) From: randall.gay@enron.com To: carrie.slagle@enron.com, susan.harrison@enron.com, robert.superty@enron.com, george.smith@enron.com Subject: Contract Exchange Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-From: Randall L Gay X-To: Carrie Slagle, Susan Harrison, Robert Superty, George Smith X-cc: X-bcc: X-Folder: \Randall_Gay_Dec2000\Notes Folders\Sent X-Origin: Gay-R X-FileName: rgay.nsf I think we are on the right track from our meeting yesterday. I talked to Patti today and she is confirming the way we want to do things from a users perspective. My thought is that we get a good, general, working model as to how the information will flow, then take it back to our groups and go over different scenarios within each region, such as Opal Plant, Socal, etc. We can see how the information will flow and see what we need to tinker with. I also have a few questions we need to think about at some point, and I did not want to forget them. 1. When we make a change to an existing upstream/downstream contract, how will we notify the counterparties that a change has occurred. 2. Should we lock out our customer's at some time so they can't make changes at a late time? We could do the rest over the phone. 3. On EDI pipes, we could conceivably make changes up to 11:45 am, but it would affect customers whose noms are due at 11:30. I thought these were just questions we might want to think about. I'm sure there are a lot of others. Thanks.