Enron Mail

From:mark.walker@enron.com
To:hollis.kimbrough@enron.com, marion.horna@enron.com, kurt.anderson@enron.com,dave.schulgen@enron.com
Subject:Detailed Guidance On 1.5 Availability Computation. Do not send
Cc:
Bcc:
Date:Wed, 3 Apr 2002 02:39:00 -0800 (PST)

Cc: jeff.duff@enron.com, mark.fisher@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bcc: jeff.duff@enron.com, mark.fisher@enron.com
X-From: Mark V Walker
X-To: Hollis Kimbrough, Marion Horna, Kurt Anderson, Dave Schulgen
X-cc: Jeff Duff, Mark Fisher
X-bcc:
X-Folder: \mark fischer 7-12-02\Notes Folders\All documents
X-Origin: FISCHER-M
X-FileName: mark fischer 7-12-02 LNotes.nsf

Executive Summary
Marion Horna and Kurt Anderson requested an explanation of how the EW 1.5
Availability was computed. In addition, Barry Riffe and Jeff Duff have
expressed concerns that there is confusion between the EW 750 owners, I.E.,
and EWC on how to categorize (OOH, UAH, or other) the direction curtailment &
windshear curtailment for availability computations. The attached memo is
the result of a throrough review of the Exhibits in the 1.5 contracts that
define availability and the UAH & OOH clauses which are similar between 1.5
and 750 project contracts. This memo doesn't include a thorough review of
the Technical Specs or Germainisher Lloyd design recommendations for 1.5
projects. This draft memo proposes that:

1) EWC should not be penalized for direction curtailment and windshear
curtailment losses to availability IF that curtailment is in accordance with
the Tech Spec of Germanischer Lloyd recommendations or requirements.
Neither the UAH term or the OOH term in the contract apply.
The corrections applied to correct for windshear in previous EW 750 reports
were made to compensate for the limitations of controller counters.

2) Only those Offline Hrs ordered by the organizations specifically
mentioned in the OOH clause in the contract should be included in the OOH
term in
the contract. For example, if the owner is not specifically mentioned in
the OOH clause then their orders for offline turbine should not be included in
OOH.

The availability resulting from this computation will not penalize
availability for all reasons that the turbine didn't produce power in good
winds. There will be events that prevent turbine production but do not lower
availability, ie. high winds, direction curtailment.