Here is an email: Ugh. We'll keep working this angle if their new attorney shows up on deck, but I think Susan and I have done as much as can be done with Howard H. Do any of you know what the Red Cedar facilities look like? I.e. how many miles of line, any big diameter line, any compression, etc? Howard must have read some old cases and gotten himself spooked that their facilites aren't gathering under the modified primary function test. I'm not sure why he thinks signing a transport contract with us will make their situation any worse, but that seems to be his conclusion. If Steve and Bill can't nudge Red Cedar's management into doing the deal, I'd suggest that you both or one of you ask Tsuri (sp?) to have his new lawyer call me and Susan after Howard leaves, maybe with one of the Kinder Morgan lawyers on the phone also, and we'll try to straighten this out.
What is a potential subject line for this email?
A: Red Cedar
Q: John and Terry, could you check into having a Business Objects report done for all groupings with the following information. Previous Cyclce Nomination Current Nomination Confirmation Schedule Confirmation piece is not critical if that prolongs getting the report. The reason for the report - Gas Control needs to know what changes have taken place and this will prevent the teams from doing a manual report. If we already have access to something similar to this, let me know. I would like to be able run this report during cycle. (I think I am probably asking for the moon), but that would be the best time for Gas Control. Thanks. Lynn
Propose a subject line
A: Kermit to Beaver Grouping
IN: Preschedule had a heck-u-va day on Friday. Due to many problems, some of our tags were not completed until after the 3pm preschedule deadline. Apparently, some of our counterparties automatically deny late tags, though they may be corrections of tags made prior to the deadline. In any case, we have a list of tags that have been submitted as real-time tags and the schedules should be treated such. The tags and paths are as follows: 25869: DELAYED TAG NEEDS SUBMITTED NO LATER THAN AN HOUR BEFORE SCHEDULE FLOWS. 10MW HE23-34 ON 07/01: PSCO(G)WSYS-PSCO(T)WSYS/CRAIG#GF-DESERRET(T)CRAIG/BONANZA#4869,mnf-DESERRET(T)BONANZA/MONA#4869mnf-PAC(T)MONA/REDBUTTE#133871f-NEVP(T)REDBUTTE/MEAD#1022243mnf-PSCO-EPMI-APS(T)MEAD/PV#22937-EMPI-APS(T)MEAD/WW/PV #22936F-EPMI-PACE-CISO(T)PV/MALIN-PACE(T)MAL/PACE SYS-PACE 25872: DELAYED TAG NEEDS SUBMITTED NO LATER THAN AN HOUR BEFORE SCHEDULE FLOWS. 10MW HE7-22 IN 07/01: PSCO(G)WSYS-PSCO(T)WSYS/CRAIG#GF-DESERET(T)CRAIG/BONANZA#4869,mnf-DESERET(T)BONANZA/MONA#4869mnf-PAC(T)MONA/REDBUTTE#133871f-NEVP(T)REDBUTTE/MEAD#1022243mnf-PSCO-EPMI-APS(T)MEAD/WW/PV #22936F-EPMI-SRP-SRP(T)PV/KYRENE#GF-SRP 25873: DELAYED TAG NEEDS SUBMITTED NO LATER THAN AN HOUR BEFORE SCHEDULE FLOWS. 15MW HE7-22 IN 07/01: PSCO(G)WSYS-PSCO(T)WSYS/CRAIG#GF-DESERET(T)CRAIG/BONANZA#4869,mnf-DESERET(T)BONANZA/MONA#4869mnf-PAC(T)MONA/REDBUTTE#133871f-NEVP(T)REDBUTTE/MEAD#1022243mnf-PSCO-EPMI-APS(T)MEAD/WW/PV #22936F-EPMI-PNM-EPE(T)PV/WW-SRP(T)WW/MEAD-NEVP(MEAD) 25823: 25MW HE7-22 ON 07/01: DGT(MONA)-AEP-PSCO-EPMI-PAC(T)MONA/REDBUTTE-NEVP(T)REDBUTTE/MEAD-NEVP 25824: 15MW HE1-6 ON 07/01: DGT(MONA)-AEP-PSCO-EPMI-PAC(T)MONA/REDBUTTE-NEVP(T)REDBUTTE/MEAD-CRC(MEAD) 25825: 10MW HE1-6 ON 07/01: DGT(MONA)-AEP-PSCO-EPMI-PAC(T)MONA/REDBUTTE-NEVP(T)REDBUTTE/MEAD-CRC(MEAD) 25870: DELAYED TAG NEEDS SUBMITTED NO LATER THAN AN HOUR BEFORE SCHEDULE FLOWS. 10MW HE23-34 ON 07/02: PSCO(G)WSYS-PSCO(T)WSYS/CRAIG#GF-DESERRET(T)CRAIG/BONANZA#4869,mnf-DESERRET(T)BONANZA/MONA#4869mnf-PAC(T)MONA/REDBUTTE#133871f-NEVP(T)REDBUTTE/MEAD#1022243mnf-PSCO-EPMI-APS(T)MEAD/PV#22937-EMPI-APS(T)MEAD/WW/PV #22936F-EPMI-PACE-CISO(T)PV/MALIN-PACE(T)MAL/PACE SYS-PACE Thanks, Donald.

Generate a subject line.

OUT: Preschedule paths going real-time for Sunday and Monday, 07/01 and 07/02.
IN: Status report of integration testing from Wednesday, Jan. 23rd - (16 gas/ power types of transactions to test) Overall, there were no infrastructure or major application issues. Unlike the prior testing, we've included many more gas transaction types and testing with all non-essential Netco data removed (aka baseline for Netco go-live). In today's test, we had numerous data setup related issues that resulted in downtime (ie EOL- Dynegy information, TGP address information, bad credit counterparty/ contracts, or database issues with data sync/ replication). These were mainly attributed to the massive cleanup/ removal of data not needed. The remaining issues open are being addressed Wednesday night. Given the deferred 12:00pm to 2:00pm start time and data setup/ sync issues, we were unable to complete downstream processes (mainly Settlements, confirmations, SAP). Continuation of testing into Thursday We are requesting the testers with tasks remaining to complete the script execution Thursday (morning shift and afternoon shifts given UBS offsite meetings). We will try to balance the testing activities given some will be out in the morning, and some in the afternoon. The bridgeline will be active from 9 - 5 for communication/ status. RECAP of where testing left off for Netco and EOL entry.

Generate a subject line.

OUT:
Status report of integration testing from Wednesday, Jan. 23rd ; and Thursday's continuation..