EVENT LOG FOR SITE BO2 Most recent activity to be listed first. First line of each entry lists date, time & who is reporting. Subsequent lines of each entry aligned under Time column. Do not use tabs, only spaces. Date Time Who What -------- ----- -------- ----------------------------------------------- 12/18/2002 17:13 Darren The site was turned off on 12-16-02 but after talking with Scott Livingston I decided to leave the computers on the data collection platform running and sending files to "test" data. This site is also due to water up on 1-9-03. We will be on site to lift our tags from the power and re-tune the entire system. 12/18/2002 12:35 Don_Warf -------- Original Message -------- Subject: ladder outages and such Date: Wed, 18 Dec 2002 11:55:58 -0800 From: "Mackey, Tammy M NWP" To: "'Chase Darren'" , "'Livingston Scott'" , "'Warf Don'" Washington Shore and Cascade Island will be coming back in service on 09 January unless contractors request an extension. Bradford Island will be coming out of service on 21 January. Tammy 12/16/2002 17:19 Dave Disabled site checking in etc/sites while facility is dewatered. 12/16/2002 11:56 Darren The last file BO202350.B was sent in at 11:45 on 12-16-02. The computers were turned off and will be restarted when the facility is ready for the ladder to be watered up. Also it was brought to my attention that on Friday 12-13-02 This site was brought down to oriface flow, Tammy Mackey is the one that relayed that to me. The dates for water up are still up in the air Tammy will e-mail us the schedule when it is finalized. 12/16/2002 09:15 darren@p 0E:TestTagFailure: This site has been powered down due to the dewatering of the ladder. All transceivers will be tuned when the ladder is watered back up. . 12/16/2002 09:12 Darren This site was powered down at 08:45 this morning (12-16-02). The transceivers were tagged out at the power distribution panels with the approval of COE Biologist Tammy Mackey. The last file is BO202350.B 12/11/2002 10:01 darren@p 0E:TestTagFailure: After viewing the exciter report it appears that the transceiver has drifted out of tune. This will be addressed next week. . 12/09/2002 08:52 darren@p 0E:TestTagFailure: After viewing the exciter report it appears that the "phase" has shifted by 4% this is a sign of de-tuning. PTOC personnel will re-tune the sysytem on the next site visit. . 12/06/2002 08:36 darren@p 0E:TestTagFailure: We will investigate this on the next site visit. . 12/05/2002 09:04 darren@p 0E:TestTagFailure: Some of the failures appear to be caused by the fact that the timer tag is firing while the status report is being sent to the computer but we do not see "test aborted due to system activity". I will check the timer tag when I am on site. . 12/04/2002 15:27 darren@p 03:Overrun: Will investigate this condition on next site visit. The exciter report does not show any indication that the transceiver is de- tuning. There is no elevated noise. . 12/03/2002 16:05 darren@p 03:Overrun: Alarm acknowledged. Site was visited today will report findings tomorrow. . 12/02/2002 10:19 darren@p 03:Overrun: The "overrun" condition is possibly due the de-tuning of the transceiver. It has changed by 2% but the noise levels appear to be acceptable. this will be checked on next site visit. The exciter voltage may have to be altered and then retuned. . 11/27/2002 08:48 darren@p 05:ExcessiveNoise,06:ExcessiveNoise,07:ExcessiveNoise,08:ExcessiveNoise,0A :ExcessiveNoise,0D:ExcessiveNoise,0F:ExcessiveNoise,10:ExcessiveNoise: Alarms were caused by PTOC personnel while performing maintenance on all transceivers. . 11/27/2002 08:08 darren@p 03:Overrun: This condition is being investigated by PTOC personnel. This unit will be addressed on next site visit. . 11/25/2002 11:50 Darren_C On Friday 11-22-02, Scott and I traveled to Bonneville to check and retune all transceivers. We also megged out all coils and tried to get rough estimates on cable lengths. We did address a few issues that were in need of attention: Coil 03 at BO2 was not firing it's timer tag, The connector to the VTT was loose and not making good connection, this has happened in the past and is due to the wires and the pins that are used for the timer tag. At BO1 we looked at coils 0A,17 that were alerting us to overrun conditions on a quite frequent basis, coil 0A was out of tune and once it was retuned and the power supply adjusted the overrun condition went away,coil 17 was also retuned. 11/25/2002 09:22 darren@p 03:TestTagFailure,04:BadExcFreq,04:BadOscFreq,04:LowExcCurrent,06:LowExcCu rrent: Alarms were generated by PTOC personnel while performing tuning and maintenace on transceivers. . 11/22/2002 07:40 darren@p 03:TestTagFailure: Alarm will be addressed by PTOC personnel Today. . 11/20/2002 09:06 darren@p 03:TestTagFailure: This alarm will be addressed Friday when the site is visited. The Exciter report does show a slight increase in noise "signal". We will try to retune this unit and monitor for future failures. . 11/19/2002 13:58 darren@p 03:TestTagFailure: This alarm is going to be addressed on the next site visit. . 11/18/2002 08:16 darren@p 03:TestTagFailure,08:Overrun: Test tag failure has been noted. The transceiver for this coil has been checked and seems to be tuned and is optimized for performance. The overrun is being looked at by PTOC personnel in the lab. . 11/12/2002 08:43 darren@p 03:TestTagFailure,08:Overrun: The test tag failure is a known failure and will be addressed on the next site visit. The transceiver is performing given the status dumps. The overrun condition is being investigated by PTOC personnel. . 11/08/2002 09:14 darren@p 03:TestTagFailure: Test tag was checked and found to be bad. It will be addressed on next site visit. . 11/07/2002 08:27 darren@p 03:TestTagFailure: I tested this timer tag yesterday by checking the hit rate. The unit appears to be in tune and the noise is down. This may require a site visit, the VTT bd may need to be replaced. . 11/06/2002 10:44 darren@p 03:TestTagFailure,09:TestTagFailure: PCA'd into site and fired the test tag and then checked the hit rate. Both parameters were satisfactory. Will monitor for future failures. . 10/24/2002 08:43 darren@p 03:TestTagFailure: ~03-7 10/22/02 11:02:18 ALARM Test tag hit rate :100. This is what the hit rate was after testing. 10/23/2002 13:30 scottl@p 03:HighTemp,03:TestTagFailure,05:HighTemp,08:HighTemp,0A:Overrun: The trailer that was used for a sun shield was removed from the site on 10/22. High temp alarms are to be expected until perminate shades can be installed. 10/19/2002 08:34 darren@p 03:TestTagFailure: No explanation for failure. The diagnostics look fine but the timer tag is not always firing. Will check on next site visit. 10/18/2002 08:57 dlwarf@p 01:HighTemp,03:HighTemp,03:TestTagFailure,04:HighTemp,05:HighTemp,06:HighT emp,07:HighTemp,08:HighTemp,09:TestTagFailure: High temp alarms acknowledged. 10/16/2002 08:48 dlwarf@p 03:TestTagFailure: Timer tag on 03 will be checked on the next visit. 10/14/2002 08:07 dlwarf@p 03:HighTemp,03:TestTagFailure,04:HighTemp,05:HighTemp,06:HighTemp,07:HighT emp,08:HighTemp: High temp alarms noted. 10/12/2002 09:34 dlwarf@p 03:TestTagFailure: Acknowledged. 10/11/2002 08:36 Scott_Li PCA'd to PC1 and fired the the testtag for Coil 03 and failed. When at the site on 10/7, the potentiomenter on the VTT PCB was turned completely counter-clockwize meaning that the TT was virtually off.. Adjusted pot and checked hit rate and all was well ... Will look into this again on the site visit. 10/11/2002 08:28 scottl@p 02:TestTagFailure,03:TestTagFailure,0B:Overrun: These alarms were generated by PTOC Maint. Testtag failure was corrected. 10/09/2002 11:32 Scott_Li This entry is for maintenance done on Monday Oct.7th. PTOC personnel retuned and calibrated ( set equalization )on all adult transceivers. Also readjusted VTT pcb on coil 10 , bo1 and coil 03 , b02. Timertags for these coils were not being detected. Hit rate after adjustments was at 100 percent. No other problems to report. 10/02/2002 08:43 dlwarf@p 02:TestTagFailure,03:TestTagFailure,0B:Overrun: All coils will be tuned during a site visit on 10/4 or 10/7. 09/29/2002 10:13 dlwarf@p 01:HighTemp,02:HighTemp,03:HighTemp,03:TestTagFailure,04:HighTemp,05:HighT emp,06:HighTemp,07:HighTemp,08:HighTemp: Acknowledged. 09/28/2002 10:05 dlwarf@p 01:HighTemp,02:HighTemp,02:TestTagFailure,03:HighTemp,04:HighTemp,05:HighT emp,06:HighTemp,07:HighTemp,08:HighTemp: Acknowledged. 09/24/2002 08:45 dlwarf@p 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp: Acknowledged. 09/23/2002 08:11 dlwarf@p 02:TestTagFailure,03:HighTemp,05:HighTemp,07:HighTemp,08:HighTemp: Acknowledged. 09/21/2002 12:51 dlwarf@p 03:HighTemp,05:HighTemp,0B:LowExcCurrent: Acknowledged. 09/19/2002 08:25 darren@p 02:TestTagFailure,0B:LowExcCurrent: I PCA'd into site and readjusted the current alarm threshold on coil 0B to 3400mA so the alarm would cease. We will check into why the current has diminished to this level. The test tag failure is unknown. 09/15/2002 12:34 dlwarf@p 02:TestTagFailure: Acknowledged. 09/14/2002 07:56 dlwarf@p 01:HighTemp,02:HighTemp,02:TestTagFailure,03:HighTemp,04:HighTemp,05:HighT emp,06:HighTemp,07:HighTemp,08:HighTemp,0B:LowExcCurrent: Acknowledged. 09/12/2002 08:34 scottl@p 01:HighTemp,02:HighTemp,02:TestTagFailure,03:HighTemp,03:TestTagFailure,04 :HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,08:HighTemp,0B:LowExcCurrent : Some of these errors were generated by PTOC during GMC, Others are due to high temp in the enclosures. 09/10/2002 10:07 Scott Megger measurements were taken yesterday on all coils. Data from these tests will be entered into the master document and posted to the PSMFC FTP server. Retuned all transceivers that required adjustments. 09/09/2002 08:55 darren@p 03:TestTagFailure,09:TestTagFailure: Alarms acknowledged. 09/06/2002 11:10 darren@p 02:TestTagFailure,03:TestTagFailure: Alarms acknowledged. 09/01/2002 08:30 dlwarf@p 02:TestTagFailure: Acknowledged. 08/29/2002 14:29 Don_Warf All transceivers were set to "Unique Off" at 13:15 PST today. 08/29/2002 08:06 darren@p 01:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07:HighTemp,08 :HighTemp: Alarms acknowledged. 08/27/2002 09:15 dlwarf@p 02:TestTagFailure,09:TestTagFailure: Acknowledged. 08/21/2002 08:58 darren@p 02:TestTagFailure: Alarm has been acknowledged. 08/17/2002 08:53 darren@p 03:HighTemp: Alarm acknowledged. 08/14/2002 08:58 scottl@p 01:HighTemp,02:HighTemp,03:HighTemp,03:TestTagFailure,04:HighTemp,05:HighT emp,06:HighTemp,07:HighTemp,08:HighTemp,0A:HighTemp,0B:HighTemp,0C:HighTem p,0D:HighTemp,0E:HighTemp,0F:HighTemp,10:HighTemp: Temp alarms are due to the high ambient temperature. Sill working on a fix, like sun shades. 08/13/2002 08:59 scottl@p 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,0F:HighTemp: Until sunshades adaquate sun shades are installed at this location. These temp alarms will continue to persist. 08/13/2002 08:27 darren@p 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,0F:HighTemp: These alarms are on the enclosures not covered by the trailer. High Temp conditions are being addressed by PTOC personnel and Destron-Fearing. 07/23/2002 08:08 scottl@p 01:HighTemp,02:HighTemp,03:HighTemp,04:HighTemp,05:HighTemp,06:HighTemp,07 :HighTemp,08:HighTemp,08:LowExcCurrent,08:Overrun: Temperature problems are being addressed. 07/17/2002 09:12 Scott_Li General maintenance check found that several transceivers were slightly out of tune. Checked all instruments and retuned what was nessesary. No major problems t report 07/15/2002 14:13 darren@p 03:TestTagFailure: No apparent reason for failure. We will monitor for further alarms. 07/13/2002 16:13 dlwarf@p 01:HighTemp,02:HighTemp,03:HighTemp,03:TestTagFailure,04:HighTemp,05:HighT emp,06:HighTemp,07:HighTemp,08:HighTemp,0F:HighTemp: High temp alarms to be addressed next week. 07/02/2002 10:58 scottl@p 08:Overrun: Will monitor for excessive errors 07/02/2002 10:56 scottl@p 05:Overrun: Will monitor for excessive errors 06/28/2002 11:27 Darren_C On Tuesday I met with COE personnel to get the phone lines for BO1, and BO2 installed to the Fiber to Copper converters in the AFF. The lines were tied into the AFF but I could not establish any Dial tone to either pittag room. I verified that dial tone was present at the converters. I called and talked to Roger at EC Electric to find out what was done when dial tone was verified after their work was performed. He explained that there is still one piece of the system that is not right for communications to either pittag room. He said he has passed this information onto the proper people to make a decision on what to do to rectify this situation. Brandt was e-mailed and replied that the vendor IFS has been contacted about replacing the equipment and should know something in a couple of weeks. 06/26/2002 11:48 scottl@p 06:LowExcCurrent: The current alarm threshold for this xcvr is set to 3800mA. The xcvr is tuned to 3900mA. Will PCA to site and change the alarm threshold to 3500. the xcvr does not appear to be detuning, all electrical parms are acceptable 06/26/2002 10:52 Scott_Li While looking into coil efficiencies for 0D and 0F, noticed that the coil ID mapping for Comm 17 and 18 in minimon was incorrect. Comm 17 was configured with ID 0F , changed to 10, Comm 18 was configured with ID 10, changed 0F. This error does not cause misrepresentation in the data set , only causes confusion when sending remote commands to the xcvrs. 06/19/2002 10:39 Darren_C On Monday and Tuesday (6-17,6-18-02) I was on site to perform test and tuning on all transceivers and coils. All coils had a Megohm test performed and the transceivers were noted as to whether or not the analog boards had been modified, they were subsequently tuned. We have placed the trailer at Cascade Island for some shading on the enclosures for Transceivers 09-10 we will monitor this for the overtemp alarms we were seeing on Saturday. The Sunshields will be looked at next week to try and determine what can be done to make them useful in protecting the enclosures from the direct sun. 06/19/2002 09:55 scottl@p 06:LowExcCurrent: Error was generated by PTOC personel 06/18/2002 15:35 Scott_Li Looking into the cause of the low efficiencies for Weir 50 , coils 05, 06, coil 06 was in Standby Mode from day 02114 to 02127, the below indicates the exact time that the reader was returned Read-Mode. ~06-12 05/07/02 10:57:32 ALARM MESSAGE: Reader is in scan mode. This should explain why Weir 50 has such low YTD efficiencies. 06/18/2002 08:19 scottl@p 03:TestTagFailure: No appearent reason for the testag failure, could be due to PTOC personel doing maintenence. 06/18/2002 08:07 scottl@p 06:LowExcCurrent: 06:LowExcCurrent: This alarm was caused by PTOC maint. personel. 06/17/2002 15:47 Scott_Li Looking at the ADE report, Unique Pittag detections at Weir 50 by day, indicates that most of the fish transiting through this weir between day 02114 and 02127 were in fact missed . The number of fish that were missed during this time span accounts for most of the 40 percent deficiency on the YTD detection totals for this weir. As of 02127, the weir 50 efficiencies are at levels that compare to the rest of the weirs in the ladder. Will look into this further for an explanation and enter that info into the event log. 06/17/2002 15:12 Don_Warf Turned unique off on coils 05 and 06 to monitor performance. 06/17/2002 14:33 Scott_Li The transceiver status report interval was changed to report every 60 minutes on all transceivers at ~1420 , 6/17/02 06/14/2002 13:34 Scott Coil 05 and 06 detection efficiency was noticed to be approx. 40 % lower than the rest of the antennas in the ladder. Looking at the exciter reports , it becomes very obvious that the exciter phase is shifting by as much as 3 % with a elevated change in temperature therefore resulting in an increase in noise levels. An example follows. Phase Exciter Voltage Signal Temp 1% *=======|=========== 16.0V *------------------- 9% ==*=====|=========== 36C 4% ========|==========* 16.0V *------------------- 17% ========|==========* 59C Although the above is interesting, without looking at the detection efficiencies during the heat of a day when the temperatures are the highest, we cannot attribute the above as the cause of low efficiencies. A site visit is planned for next week and will investigate more then. 06/14/2002 08:55 scottl@p 03:TestTagFailure: No appearent reason for the testtag failure. 06/14/2002 08:52 Scott_Li Looking into a testag failure , immediately noticed all these temperature alarms, The below is just a small sample. ~0B-9 06/13/02 18:00:01 ALARM PROBLEM: high temperature ~06-12 06/13/02 18:08:25 ALARM PROBLEM: high temperature ~0C-10 06/13/02 18:15:31 ALARM PROBLEM: high temperature ~05-11 06/13/02 18:16:36 ALARM PROBLEM: high temperature ~0C-10 06/13/02 18:17:04 ALARM PROBLEM: high temperature ~03-7 06/13/02 18:32:21 ALARM PROBLEM: high temperature ~06-12 06/13/02 19:07:15 ALARM Temperature: 55C Maybe we need some sun shades that provide shade? 06/05/2002 08:42 darren@p 09:TestTagFailure: There is no obvious reason for the failure. The tag did continue to fire. Will check into this on the next site visit. 05/31/2002 15:14 Carter_S Turned on Check_Submit flag. 05/29/2002 08:33 Darren_C A General Maintenance Check was performed on each site. No Problems were found. I changed the Status Report send times to 360 min. or once per file. I will do BWL and B2A remotely. 05/23/2002 16:59 Carter_S Date: Thu, 23 May 2002 12:02:24 -0700 From: Darren Chase To: "sandy.downing" CC: Carter Stein , Don Warf , scott livingston Subject: Reader Unique settings Sandy, I have turned all of the transceiver unique settings to "off" on the coils that you had requested. They are as follows: Bradford "A" branch: 01,01,03,04,09,0A,0F, and 10 Branch "B": 11,12,13,14,17,18,1F, and 20 Cascade Island: 01,02,0B,0C,0D,0E,0F, and 10 McNary Or.:03,04,07,08,0B,0C,0D, and 0E McNary Wa: 05,06,07,08,0D,0E,0F, and 10 If these are not correct please let me know. D.Chase 05/22/2002 08:31 Anthony Tuned all transceivers at site. When checking why coil 04 was not responding I found the following: Coil 04 transceiver s/n 2303 had no AC power to the outlet in the enclosure. I disconnected the AC cable from transceiver and checked all fuses(=good). Found that breaker had tripped in the AC distribution panel. Switched breaker back on and reconnected AC cable to the transceiver. Transceiver shows 118VAC at the input to U1 (AC to DC converter) and 0VDC at the output. Coil 04 transceiver s/n 2303 was replaced by transceiver s/n 2393. The analog board s/n 143U01873 was transferred to transceiver s/n 2393. Transceiver was flashed, equalization/current calibrated, and checked for communications to the pit tag room(=good). I will return transceiver s/n 2303 to the Kennewick shop on 05/24/02. 05/22/2002 08:28 darren@p 04:LowExcCurrent,04:TestTagFailure: Alarms were generatedwhile transceiver SN 2303 on coil 04 was being replaced. 05/20/2002 09:37 darren@p 03:TestTagFailure: Will check this out on next site visit. 05/19/2002 14:06 Don_Warf Reader 04 has not been heard from since Friday. PCAed in to try a reset. Was not able to communicate with the reader. Will investigate on Tuesday's general maint. check. 05/16/2002 08:30 darren@p 03:TestTagFailure: Failure will be looked at on the next site visit. 05/13/2002 10:39 Darren_C After speaking with Anthony Carson and viewing the "raw" file BO202129.B it was noted that there appears to have been a power outage at 10:22 on 5-9-02. There may be some concern that there was more of a brown out condition rather than just loss of power. This is being derived by the "noise" and "low exc current" alarms just prior to the test tags firing and then the status dumps. Since we have already lost one (1) transceiver (06) this could be a concern. We will follow up with the corp staff at Bonneville to determine the power outage and what caused this to happen. Unfortunately when we lost the transceiver we did not have a Data Collection Platform to report what was going on. We will need to watch this site for further outages. 05/12/2002 08:30 darren@p 01:LowExcCurrent,03:TestTagFailure,06:BadExcFreq,06:BadOscFreq,06:LowExcCu rrent,06:TestTagFailure,09:TestTagFailure: All failures will be looked at on the next site visit. 05/06/2002 11:12 Scott_Li Turned the reader unique setting to off on coils 10.0d, at 8:40 pst per Carters suggestion. 05/06/2002 11:06 Scott_Li Set the file submission frequency to upload 4 times per day. 05/03/2002 09:53 Scott_Li Changed the number of files generated per day to 4 on both primary and backup computers at 0850pst. 05/02/2002 08:37 Darren There has been a failure of a transceiver on coil 06. I found this Tuesday morning. I was unable to replace the transceiver because I did not have one on hand at the time. It will be replaced early next week. I was unable to find out exactly what caused the failure. These units are running on then "warm" side. I have spoke with Dan Johnson with Destron-Faering about the cause of this but still do not have an answer. This will continue to be examined. 05/01/2002 12:42 Scott_Li This entry is for work done at the facility on April 25,02. All transceivers were turned on and start collecting data at ~ 1200 hr. 4/25/02. This time also reflects the approximate time that the data collection platforms began receiving data from all 16 transceivers. 05/01/2002 09:18 Darren_C I PCA'd into site because I noticed that it had not sent files since yesterday. I noticed that the auto upload time was at 0 and the file that was being created was BO202120.F which did not coincide with the correct Julian Date. I stopped and started Minimon and the file changed to BO202121.A. The file size indicates that the .F file contains all of yesterday from that point on. This is almost the same problem that we have seen on a few Dial-up sites where PTTP locks up the screen but the program is still collecting Data. 04/30/2002 10:24 D.Chase As of 10:25 on 4-30-02 this site will begin to send files automatically. I uploaded 25 files to the server (02117.D-02120.D) at Carter's request. All went well. 04/29/2002 08:29 darren@p 06:BadExcFreq,06:BadOscFreq,06:LowExcCurrent,06:TestTagFailure: Transceiver 06 will be inspected today 4-29-02. Coil 0C needs to be looked at as well. I will be on site to check on I.P. connections and visit all facilities. 04/16/2002 11:51 Dave I added BO1, BO2, MC1, and MC2 to the 2002 log menu in the Interrogation Site Event Logs web page, accessible by the public at "www.pittag.org/Ptoc_OM/event_log/index.html". 04/15/2002 08:47 Dave Per Darren, 4/12/02: All transceiver tuning was finished. Destron-Fearing made all the necessary changes to the enclosures as well as a board modification on the analog board. All cable termination's have been completed and the transceivers were tuned by Destron-Fearing and PSMFC. 04/09/2002 11:50 Carter_S Dean B. said that BO2 coil #01 LED was not displaying, but power was on and it was collecting data. The ribbon cable may be loose. 04/05/2002 13:17 Don_Warf Re-tuned all temporary transceivers. Tuning notes on each unit will be posted soon. All transceivers are being fed from a GFI 110 volt outlet. This can trip- out at any time and needs to be checked as often as possible. 03/28/2002 08:47 Darren_C The site has temporary data collection on weirs 52 and 51. The transceivers were tuned and buffers cleared at 15:30 on 3-27-02. 03/26/2002 16:25 Carter_S Virtual timer tags set up for all coils. 03/14/2002 09:50 Carter_S From: "Ebberts, Blaine D NWP" To: "'carters@psmfc.org'" , "'Fodrea Kimberly - KEWI-4'" Cc: "Clugston David A NWP" Subject: FW: DACW57-02-C-0003/BONNEVILLE PIT TAG PRODUCTION CONTRACT Date: Thu, 14 Mar 2002 08:41:45 -0800 From: Nomie, Naameh A NWP Sent: Wednesday, March 13, 2002 5:03 PM To: Bannister, Brandt D NWP; Thomas, Jon B NWP; Dasso, Joseph M NWP Cc: Ebberts, Blaine D NWP; Tyrrell, Michael E NWP; Wegner, Brian C NWP; McDowell, Jeffrey R NWP Subject: DACW57-02-C-0003/BONNEVILLE PIT TAG PRODUCTION CONTRACT To All: The Contractor advised the Govt. in writing that he will not be able to complete the work out side the in-water work by April 8, 2002. He projects to complete all work by 22 April 2002 instead. He site the following reasons for being behind schedule: 1. Delay in delivery of PIT TAG Buildings. The Manufacturer needed 6-8 weeks after approval of submittals which was approved on February 6, 2002.. 2. Delay in GFM (Transformer FTQ3) which was supposed to be delivered on February 1, 2002 but, has not been delivered as of this date. The requested time extension is at no costs to the Govt. Please let me know if the requested time extension is ok. I need to hear from you by COB Monday March 18, 2002. Thanks. Naameh 03/13/2002 10:02 Don_Warf Cascade ladder was watered up for the season on March 8th at 16:00. 03/07/2002 15:34 Carter_S Set up coil configuration in ptagis3 database. 03/07/02 15:23 carters Initial log creation for BO2 ####End of Event Log for BO2###