Message-ID: <9100681.1075841877941.JavaMail.evans@thyme>
Date: Thu, 11 Jan 2001 04:59:00 -0800 (PST)
From: phillip.platter@enron.com
To: kate.symes@enron.com
Subject: Scheduling Wheelabrator
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-From: Phillip Platter
X-To: Kate Symes
X-cc: 
X-bcc: 
X-Folder: \kate symes 6-27-02\Notes Folders\Scheduling
X-Origin: SYMES-K
X-FileName: kate symes 6-27-02.nsf

fyi
---------------------- Forwarded by Phillip Platter/HOU/ECT on 01/11/2001 
03:05 PM ---------------------------
From: Phillip Platter on 01/11/2001 08:28 AM
To: David Poston/PDX/ECT@ECT
cc: Carla Hoffman/PDX/ECT@ECT 
Subject: Scheduling Wheelabrator

fyi
---------------------- Forwarded by Phillip Platter/HOU/ECT on 01/11/2001 
10:34 AM ---------------------------
From: Kourtney Nelson on 01/10/2001 05:29 PM
To: Jeff Richter/HOU/ECT@ECT, Phillip Platter/HOU/ECT@ECT, Chris 
Mallory/PDX/ECT@ECT, Carla Hoffman/PDX/ECT@ECT, Jeremy Morris/PDX/ECT@ECT
cc: Portland Shift, Volume_Management_Portland 
Subject: Scheduling Wheelabrator

When you are scheduling the two Wheelabrator units, please use the following 
counterparties in CAPS:

MARTEL_2_AMFOR:  Wheelabrat
WSENGY_1_Unit 4:  WheelSHAST

We account for these separately and thus they need to be scheduled as two 
separate entities.  

In Enpower there are two counterparties set up as well:

MARTEL_2_AMFOR:  WHEELABRMA
WSENGY_1_Unit 4:  WHEELABRSH

Thanks and let me know if you have any questions,

Kourtney