Message-ID: <17377993.1075840448308.JavaMail.evans@thyme>
Date: Tue, 18 Jun 2002 00:38:00 -0700 (PDT)
From: kevin.cousineau@enron.com
To: mark.fisher@enron.com
Subject: Re: Questions/Observations about VisuPro
Cc: ronald.brzezinski@enron.com, joe.chapman@enron.com, 
	alaadin.suliman@enron.com, hollis.kimbrough@enron.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Bcc: ronald.brzezinski@enron.com, joe.chapman@enron.com, 
	alaadin.suliman@enron.com, hollis.kimbrough@enron.com
X-From: Kevin Cousineau
X-To: Mark Fisher
X-cc: Ronald Brzezinski, Joe Chapman, Alaadin Suliman, Hollis Kimbrough
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

Mark: 

First, the new version of VisuPro (Version IV) will use standard local time, 
not daylight time. This means that during the year it will be off by one hour 
for 1/2 of the year. 

Second, the plant pc cannot have more then one version and copy of VisuPro 
running at one time. If it does then strange things happen. I will ask our 
SCADA people to make sure that Joe does not run more then one copy of VisuPro 
on any plant pc. 

Regards 

KLC 




Mark Fisher
06/17/2002 09:18 AM
To: Ronald Brzezinski/EWC/Enron@ENRON
cc: Kevin Cousineau/EWC/Enron@ENRON, Joe Chapman/EWC/Enron@ENRON, Alaadin 
Suliman/EWC/Enron@Enron, Hollis Kimbrough/EWC/Enron@ENRON 

Subject: Questions/Observations about VisuPro

Ron,

While I was at Mill Run/Somerset last week a few things came up about 
visupro. 

First a question about the new version. As I understand it, the new version 
is going to use "local time". Is this local STANDARD time or local time 
(taking Daylight Savings time into account)? The owner's representative 
indicated a preference for local standard time.

Now for a couple of things Joe Thorpe at the site mentioned. He has observed 
that if two copies of visupro are running at the plant, then 10-minute data 
does not get written. Second if visupro (at the plant) has the errdev file 
open, then new data does not get written to the file. Are you aware of these 
observations? If not you might want to contact Joe Thorpe and see if he has 
additional examples, and do some kind of testing. These are probably issues 
with the way that Paradox locks files.

Mark Fisher



