EVENT LOG FOR SITE PRA

        Most recent activity to be listed first.
        First line of each entry lists date, time and who is reporting.
        Subsequent lines of each entry aligned under Time column.
        Do not use tabs, only spaces.

Date       Time  Who      What
---------- ----- -------- -----------------------------------------------
12/22/2005 12:28 bturley@
            Site visit on 12/21/05. We updated the windows security patches on
    the data and utility computers. We also updated the antivirus and firewall
    software on PC1 data computer. Therefore, there are some small (3-4
    minute) gaps in data files PRA05355.B1 through PRA05355.J1. These occurred
    when we had to restart the computer. PC2 remained on during this time and
    no fish were detected while PC1 was down.
12/22/2005 12:08 bturley@
    08:Overrun:         Overrun caused by de-watered ladder.
12/06/05 12:00 mail_bot
    Right ladder was de-watered on 12/5/05. It is scheduled to be watered up 
    again on 1/16/06. The left ladder will stay watered up all winter.
11/08/2005 08:09 bturley@
    08:TestTagFailure:         Test tag failed for no apparent reason. Noise
    report one second later indicated noise at 1%. So, that is not an issue.
11/04/2005 09:03 bturley@
    08:TestTagFailure:         Test tag failed for no apparent reason
10/25/2005 08:14 bturley@
    08:TestTagFailure:         Test tag failed for unknown reason
10/25/2005 08:12 bturley@
    06:BadExcFreq,06:BadOscFreq,06:LowExcCurrent:         The following alarms
    occurred during routine reader maintenance on coil 06 by Biomark
    personnel:

    Bad Exciter Frequency
    Bad Oscillator Frequency
    Low Exciter Current
09/30/2005 07:17 bturley@
    08:TestTagFailure:         Coil 08's flaky test tag has failed again
09/20/2005 08:15 bturley@
    08:TestTagFailure:         Test tag failure. Not sure what caused test tag
    to fail.
09/12/2005 15:45 bturley@
    08:TestTagFailure:         Test tag failure. Not sure why it happened.
09/09/2005 07:12 bturley@
    08:TestTagFailure:         Test tag failure on 08. No indication as to why
    the test tag failed
09/01/2005 13:27 bturley@
    08:TestTagFailure:         test tag fired at the same time as the reader
    diagnostics. This may have caused the test tag to fail???
08/23/2005 14:03 bturley@
    08:TestTagFailure:         Not sure what is causing this test tag failure.
08/23/2005 14:01 bturley@
    02:LowExcCurrent:         Not sure what is causing this low exciter
    current alarm. We will address this on the next site visit. The coil has
    been reading tags well.
08/03/2005 14:50 bturley@
    08:TestTagFailure:     The test tag tried to fire at the same time the
    transceiver sent a noise report. That may have been the cause of the test
    tag failure.
07/27/2005 13:35 bturley@
    08:TestTagFailure:        Reader sent a status report at the same time as
    timer tag tried to go off. This may have caused the test tag failure
07/25/2005 06:53 bturley@
    08:TestTagFailure:         Test tag tried to fire during a status report.
    This may have caused the failure
06/28/2005 10:23 bturley@
    03:LowExcCurrent,04:LowExcCurrent,08:LowExcCurrent:         Low Exciter
    Current Alarms were caused by Biomark personnel during routine
    maintenance.

    All transceivers were tuned, the firewall and anti-virus programs were
    updated for the computers.

    A new firewall and antivirus subscription was purchased for the utility
    computer.
06/20/2005 07:17 bturley@
    08:TestTagFailure:         Reader sent a noise report at the same time as
    the test tag tried to fire. Don't know if this caused the failure or not.
06/17/2005 08:11 bturley@
    08:TestTagFailure:         The transceiver sent a noise report at the same
    time as the test tag fired. I'm not sure, but this may be the reason for
    the test tag failure.
05/19/2005 12:45 acarson@
    08:TestTagFailure:         Reader sent a DRS at the same time the test tag
    fired. I don't know if this is why the test tag failed, but it has worked
    properly since.
05/19/2005 12:32 acarson@
    08:TestTagFailure:         Test tag failed because of system activity
04/19/2005 10:00 acarson@
    08:TestTagFailure: 08:TestTagFailure:         Not sure why the test tag
    failed. The reader did send a noise report at the same time, but I don't
    know if that caused the test tag failure. It hasn't failed since.
04/19/2005 09:59 acarson@
    08:TestTagFailure:         Not sure why the test tag failed. The reader
    did send a noise report at the same time, but I don't know if that caused
    the test tag failure. It hasn't failed since.
03/19/2005 12:21 acarson@
    The water outages for PRA 2004/05 maintenance periods are:

    Left Ladder -
    Out of service 11/24/04 @ 1015
    In service 02-03-05 @ 1420

    Right Ladder -
    Out of service 02-04-05 @ 0945
    In service 02-28-05 @ 1135

03/03/2005 15:12 acarson@
    07:LowExcCurrent,08:LowExcCurrent: Tuned all coils, erased all buffers,
    and update firewall/antivirus software for both PC1 And PC2.
02/04/2005 17:03 acarson@
    01:ExcessiveNoise,02:ExcessiveNoise,03:ExcessiveNoise,04:ExcessiveNoise,05
    :ExcessiveNoise,06:ExcessiveNoise: The left ladder was fully flooded on
    2/3/05 and the Right ladder will be dewatered by 2/4/05.  On 2/4/05 coils
    05-08 were enabled and coils 01-04 were placed in stdby.  All noise
    thresholds were set to 99% until next site visit.
         ####End of Event Log for PRA###