ML051460239
| ML051460239 | |
| Person / Time | |
|---|---|
| Site: | Millstone  |
| Issue date: | 04/18/2005 |
| From: | Saul L SCIENTECH |
| To: | Felicia Hinson Office of Nuclear Reactor Regulation |
| References | |
| FOIA/PA-2005-0207 | |
| Download: ML051460239 (5) | |
Text
I Max Scqhneider - Millstone 30 Max Schneid;r lso,,, Page 1 From:
To:
Date:
Subject:
"Lynne Saul" <Isaulsscientech.com>
NFelicia Hinson" <FML~nrc.gov>
4/18/05 1:18PM Millstone 3 Tom/Felicia, I spoke with Tom Bowlen at Millstone this morning (we had a previously scheduled test for Millstone 2 today). I asked him if his ERDS connection had a problem yesterday. He said yes - it apparently did. That one of their people had to go to the Unit 3 computer room and stop and restart the ERDS connection in order to get it to work. After talking with Tom Bowlen, I logged onto the NRC ERDS and took screen shots of the ERDS log from yesterday's event. I copied them into a document and added some commentary about what happened at various times. That document is attached to this email in case you are interested in reviewing it.
Lynne Lynne Saul SCIENTECH Program Manager 200 S. Woodruff Idaho Falls, ID 83401 Phone: 208-524-9371 Fax: 208-524-9282 CC:
"Tom Kardaras (Tkardaras)" <TXK1 @nrc.gov>
- 1 a
'Max Schneider - ERDS Log from Millstone 3 Event.doc
_Page 1
Copy of ERDS Log from Millstone 3 Event, 4/17/05
- 9.
- 9*
9 a*
a.
9 9
9 r
9 a.
9'
- 9.
9
.9 9'
- 9.
.9.
9 a,
- 9.
a a.
9 9
9 a.
9 99 9:
1 9
9, 9:
99 9
9 99 9;
9 9*
9 9
I.
99 9:
2
- 9.
9.
.9 99 I
9 9
9
- 9 9:
- 9.
9 99 9*
9
.9 I
I a
I g
ure1 At 9. '
F F
I----
Figure I At 9:22 AM EDT, ERDS detected activity on line 2 but the data being received was not any pattern recognizable to ERDS. Prior to 9:22 AM the log shows the regular message ERDS outputs once an hour to indicate things are OK.
iMax Schneider - ERDS Log from Millstone 3 Event.doc Paqe 21 NV V
- MUMS R.P
-W-sl-O I
I
- -i -I..
V g l-4 V4-This problem continued until 9:24:40 (see Figure 3). There was something that ERDS thought looked similar to a link request message but it was invalid and had an invalid site ID.
Max Schneider-EROS Log from Millstone 3 Event.doc Page 31 I-
- 111I t :. ;...
I..,-.,
. I,; -,
'.1 -. X-.F -+
._1.
111jW IIN..
A.- i-_F i
-1.b
- L z
19w
- 85et I
D*
Yoo I--
g]
At 9:25:40 AM EDT ERDS detects another invalid link request message. After that there is no more activity on the line until 12:02:48 PM EDT and it is more garbage data. At 12:02:59 PM EDT, ERDS receives a RECONNECT request from Millstone 3 which is denied. You will notice that the activity has shifted from Line 2 to Line 1. This indicates that the plant has dialed into ERDS again. The ERDS plant number is on a rotary and each successive call is routed to the next line in the rotary.
At 10: 14:43, Region I logged in. They couldn't see Millstone 3 because Millstone 3 had not successfully connected at that time. Millstone 3 didn't actually get connected until 12:03:34 PM EDT (see Figure 4).
Max Schn eider - ERDS Log from Millstone 3 Event.doc P
4 pg,!
I I --
You can see that Millstone 3 got on line with ERDS at 12:03:34 PM EDT because the log contains a link accepted message. That indicates that the plant is on line.
When Region I logged in again at 12:16:08 PM EDT, Millstone 3 was on line and they were able to see them.