Todd,
	Just another update on where we stand with the interval meter data. How is everything going in your world? I am getting a lot of projects thrown at me right now, so let me know if there is any deliverables that I owe you. I just want to make sure I am not letting anything slip through the cracks. Hope all is going well, I will try to stop by before I leave out of  Houston this week(Currently spending a lot of time in 3 Allen center).


			Ps   I thought you said our stock price would not go below $40. Did Ken and Jeff forget to check in with you before the big decision. J


						Chris
						503-807-8959

 -----Original Message-----
From: 	Rutledge, John  
Sent:	Friday, August 17, 2001 6:38 PM
To:	Stokley, Chris; Frazier, Michael
Cc:	Alvarez, Charles; Taylor, Todd; Chmil, Shawn
Subject:	Re: FW: CES2423 Project Proposal

Chris, Michael--

I've been looking at some of the MV-90 files from CSC. Here's what I have found:

There are 1200 to 1400 meters reported each day. We will need to keep an eye on this number to see what kind of growth to expect.
Almost all meters report in 15 minute intervals. Interestingly enough, one meter (UCSF CUP 3), started reporting 5 minute intervals on 6 August, and has done so ever since.
The current prototype application I am using to read this data into a temporary database reads about 1meter per second, so I am averaging around 20 minutes per file. While I think I can improve the speed of this process, it does not take into account the need to map this data to the correlating account data, so any gains may be lost there.
Although some of the datafiles are complete (4 readings per hour X 24 hours X every meter) others are missing quite a lot of data. ("9 missing readings for meter KZ+029402367...87 missing readings for meter KZ+029402370...15 missing readings for meter KZ+029402392...") I will work with CSC next week to figure out what is causing this extreme variance in the dependability of the data from day to day.

Next week I will be looking into MDMA to match up these meter ids with accounts. I will let you know what I find.

--John


--John







From:	Chris Stokley/ENRON@enronXgate <mailto:Stokley/ENRON@enronXgate> on 08/15/2001 06:47 PM
To:	John Rutledge/HOU/EES@EES <mailto:Rutledge/HOU/EES@EES>
cc:	 
Subject:	FW: CES2423 Project Proposal

John,
	I have not heard back from you on the items listed below, where do you stand on these questions


							Chris

 -----Original Message-----
From: 	Stokley, Chris  
Sent:	Tuesday, August 14, 2001 6:27 AM
To:	Rutledge, John
Subject:	RE: CES2423 Project Proposal

John,

	Could you tell me who I would speak to in order to find out the priorities that are pushing this process back to 11:00am? Also, how much time does it take you to get this file into the database once you receive the file from CSC? This is making the assumption that the database is configured and ready to go. What are you currently seeing in the way of missing data coming in from these files on a daily basis.


								Chris
								503-807-8959

 -----Original Message-----
From: 	Rutledge, John  
Sent:	Wednesday, August 08, 2001 11:18 AM
To:	Winter, Maurice; Stokley, Chris; Frazier, Michael
Cc:	Alvarez, Charles
Subject:	CES2423 Project Proposal

Have attached the project proposal as returned by CSC. I am also summarizing a discussion I had with Geoff Goodfellow of CSC:

Since CSC is using a third-party, packaged application to produce this file, they are limited in their ability to deliver exactly what we want (in the context of the 51 hour, $4,883.62 estimate).

We requested that missing data (e.g., phone line down) be backfilled in a later day's file, but this is not possible because the process to produce this file only queries on meter data for a specific date, not all data received on a specific date. For example, if they ran it today, for 7 August, we would receive all meter data for that date, but they would have actually received more than that on the 7th, perhaps data dated 6 Aug for meters that failed to dial in on that day. Getting this data will require further development (read: mo' money).

Also, the file is 26MB, of which more that 25% is blank spaces on the end of each line. Again, since this is an external application, I have been told that it is not possible to eliminate this extra space. (Not a killer, since we won't actually be putting it in the database, but it just adds to processing/network overhead.)

I have also been told that file delivery will occur between 11 a.m. and 12 p.m. daily. This is because of current priorities, but even at the earliest, we won't be able to get it before 7:30 a.m. (Data is collected from 12 a.m. to 6 a.m., the report run takes 1 hour 30 minutes, a file is produced at 7:30.)

--John





---------------------- Forwarded by John Rutledge/HOU/EES on 08/08/2001 10:57 AM ---------------------------


jthoma56@csc.com <mailto:jthoma56@csc.com> on 08/07/2001 04:11:43 PM
To:	rgresch@enron.com <mailto:rgresch@enron.com>
cc:	jjackson@enron.com <mailto:jjackson@enron.com>, john.rutledge@enron.com <mailto:john.rutledge@enron.com>, kenny.ha@enron.com <mailto:kenny.ha@enron.com> 
Subject:	CES2423 Project Proposal


Bob -
Attached is the Project Proposal and Purchase Order document for the MV-90
Data Download (CES2423) Work Request.  Please review the documents at your
earliest convenience.  If the offer is acceptable to EESO, please forward
your acceptance to my attention via electronic mail attached to this
submission.
If you have any questions or require additional information, please contact
me at 614-737-1345.

Best Regards -
Jim
(See attached file: CES2423.MV90 Project Proposa 080701.doc)
 - CES2423.MV90 Project Proposa 080701.doc << File: CES2423.MV90 Project Proposa 080701.doc >>