Message-ID: <7579091.1075840029415.JavaMail.evans@thyme>
Date: Wed, 8 Aug 2001 17:20:39 -0700 (PDT)
From: jtaffe@ci.tacoma.wa.us
To: isas@wscc.com
Subject: RE: Adjust Function
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-From: jtaffe@ci.tacoma.wa.us
X-To: Interchange Scheduling & Accounting Subcommittee (ISAS) <isas@wscc.com>
X-cc: 
X-bcc: 
X-Folder: \ExMerge - Scholtes, Diana\STF\Current issues
X-Origin: SCHOLTES-D
X-FileName: 

I agree and believe that the new specification will allow PSE's greater
adjustment capabilities.  Until then we will (as a PSE)
cancel/withdraw/replace and as a Control Area (LCA) Adjust at our
discretion.

> ----------
> From: 	Doug Hincks
> Sent: 	Wednesday, August 8, 2001 1:24 PM
> To: 	Interchange Scheduling & Accounting Subcommittee (ISAS)
> Subject: 	RE: Adjust Function
> 
> Paul,
>  
> My understanding is that only the LCA has ADJUST capabilities, and I do
> agree that if a PSE needs the tag changed (has a schedule change) that the
> replacement tag is the way to go.  Our RT operators will only ADJUST a tag
> for curtailments.  I believe new version (1.7) will allow PSE's to do an
> ADJUST.
>  
> Doug
> 
>  ----Original Message-----
> From: Rice, Paul [mailto:Paul.Rice@Pacificorp.com]
> Sent: August 8, 2001 14:00
> To: Interchange Scheduling & Accounting Subcommittee (ISAS)
> Subject: Adjust Function
> 
> 
> 
> 
> 		PacifiCorp Real-Time has recently been requested several
> times by PSE's to use their "Adjust" function for changing schedules.
> This has prompted them to ask for a clarification on the Adjust function
> "rules".  It is Real-Times belief that the Adjust function is for Control
> Area use and only for Reliability/Curtailment issues.  If Merchants/PSE's
> want to change a schedule on an existing tag it should be done through the
> Termination/replaced functions at their control and not ask C/A's to use
> their Adjust function.  I have found documentation that tells who has
> control of the Adjust function and how it can be used but cannot find any
> documentation that specifically prohibits or limits it's use to C/A and/or
> their curtailment issues.  Does anybody have any help here??  The main
> issue is, R/T does not have time to perform adjust functions for other
> entities merely at their request.   We can understand doing it when the
> tag originator has lost control and is unable to terminate a tag but not
> on a routine basis.     
> 
>