ML051460219

Preliminary Information on ERDS Delay

ML051460219
Person / Time
Site:	Millstone
Issue date:	04/19/2005
From:	Felicia Hinson Plant Support Branch 1
To:	Florek D, Mcnamara N, Schneider M Division Reactor Projects I
References
FOIA/PA-2005-0207
Download: ML051460219 (14)

Text

5 Max Schneider:Preliminary Information on ERDS Delay Pane 1 

l Max Schneider;- Prelimin ary pnforrnatno E _ elay Page i 'I From:

To:

Date:

Subject:

Felicia Hinson Florek, Donald; McNamara, Nancy; Schneider, Max 4/19/05 10:40AM Preliminary Information on ERDS Delay All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC ERDS contractor). Region I initially logged in to ERDS at 10:14:43 AM. Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia CC:

Kardaras, Tom; Lorson, Raymond; LSaul~scientech.com; McGinty, Tim

)
5

Max S-c-h-n-eider - Re: Preliminary Information on EROS Delay Page1 From:

Nancy McNamara To:

Donald Florek; Felicia Hinson; Max Schneider Date:

4/19/05 10:42AM

Subject:

Re: Preliminary Information on ERDS Delay Did they not see this during the test that was conducted the week before?

CC:

LSaulscientech.com; Raymond Lorson; Tim McGinty; Tom Kardaras

iMax Schneider - Re Prelimiray !nforr ation on ERDS Delay (PLEASE BE ADVISED)

Page 1i 3

.eme at w

Act I

From:

Tom Kardaras To:

SMS2@nrc.gov Date:

4/19/05 10:56AM

Subject:

Re: Preliminary Information on ERDS Delay (PLEASE BE ADVISED)

I will be out of the office between Thursday, April 14, 2005 and Tuesday, April 19, 2005. If further assistance is required, please contact Tim McGinty at 301 415-5710 or TJM1 @nrc.gov

>>> SMS2 04/19/05 10:56 >>>

Note: The Unit 2 ERDS failed testing last week. The CR said that Unit 2 ERDS does not work while the Unit is shutdown. This doesn't make any sense (it may not be what they intended to communicate on the CR) since ERDS would nearly always be needed when a plant is shutdown, post event. This is one of the areas for evaluation the residents are recommending to the SIT (i.e., potential precursor that would have led them to investigate ERDS the week prior).

Thanks, Max.

>>> Felicia Hinson 04/19/05 10:40AM >>>

All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC ERDS contractor). Region I initially logged in to ERDS at 10:14:43 AM. Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia

Schneider - Re: Prelinary nfpormation on ERDS Delay Page 1 From:

Nancy McNamara To:

Max Schneider Date:

4/19/05 11:16AM

Subject:

Re: Preliminary Information on ERDS Delay Im hoping Felicia asks HQs. But if you have information regarding last week's test, please provide it to everyone on the email.

I Max Schneider - RE: Prelimin

-- ----- __ _.qry Information on ERDS P la Paae 1.1 I Max Shneider-RE-rlmn-nomtono RSDlyPo From:

"Lynne Saul" <Isaul scientech.com>

To:

"'Max Schneider"' <SMS2@nrc.gov>, "'Donald Florek'" <DJF1 @nrc.gov>, "'Felicia Hinson'" <FML@nrc.gov>, "'Scott Barber'" <GSB.kplpo.KPDO @ nrc.gov>, "'Nancy McNamara"'

<NTM©nrc.gov>

Date:

4/19/05 11:45AM

Subject:

RE: Preliminary Information on ERDS Delay I would like to clarify about the problem Unit 2 ERDS had last week. A value of --1.#INDOOE was being sent for two data points. The NRC ERDS reported that it was receiving unknown values for two points because it could not convert that string to a number. This caused Unit 2 to fail it's ERDS test.

Lynne Saul SCIENTECH Program Manager 200 S. Woodruff Idaho Falls, ID 83401 Phone: 208-524-9371 Fax: 208-524-9282

---

Original Message----

From: Max Schneider [1]

Sent: Tuesday, April 19, 2005 8:56 AM To: Donald Florek; Felicia Hinson; Scott Barber; Nancy McNamara Cc: Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras; LSaultscientech.com

Subject:

Re: Preliminary Information on ERDS Delay Note: The Unit 2 ERDS failed testing last week. The CR said that Unit 2 ERDS does not work while the Unit is shutdown. This doesn't make any sense (it may not be what they intended to communicate on the CR) since ERDS would nearly always be needed when a plant is shutdown, post event. This is one of the areas for evaluation the residents are recommending to the SIT (i.e.,

potential precursor that would have led them to investigate ERDS the week prior).

Thanks, Max.

>>> Felicia Hinson 04/19/05 10:40AM >>>

All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC ERDS contractor). Region I initially logged into ERDS at 10:14:43 AM.

Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia CC:

C'Kevin Mangan'" <KAM1 @nrc.gov>, "'Paul Krohn"' <PGK1 @nrc.gov>, "'Raymond

In I Max Schneider - RE: Preliminary Information on ERDS Delay Page 2 Lorson"' <RKL~nrc.gov>, "'Silas Kennedy" <SRK6nrc.gov>, "Tim McGinty"' <TJM1 @nrc.gov>, "'Tom Kardaras"' <TXK1 @nrc.gov>

Max Schneider - RE: Preliminary Inf ormation on E RDS Delay Paae 1 I I Mp
Sq4pe!der - RE: Prelq!naD
Infqrmation on ERDS Delay, Page 1,l, From:

Raymond Lorson To:

Donald Florek; Felicia Hinson; Max Schneider; Nancy McNamara; Scott Barber Date:

4/19/05 12:00PM

Subject:

RE: Preliminary Information on ERDS Delay Don, Max etc.

I think that the ERDS problems should be looked at within the context of the SIT. One other thing that I am not clear on is that a number of emails discussing this problem have included Lynne Saul from Scientech. Is she a licensee vendor? If so we need to docket all of our back and forth emails with her per MC 0620. The easiest way to do this would be for Scott to put in Adams and refer to the ascension number in the SIT report.

Ray

>>> Max Schneider 04/19/05 11:53AM >>>

Does this character of testing failure remove any connection to the Unit 3 ERDS failure? We only feel that 2 failures within 1 week should be evaluated as part of the SIT review to ensure there were not prior opportunities to correct a condition onsite related to emergency response equipment, we aren't advocating one way or another.

>>Lynne Saul" <Isaul@scientech.com> 04/19/05 11:44AM >>>

I would like to clarify about the problem Unit 2 ERDS had last week. A value of *-1.#INDOOE" was being sent for two data points. The NRC ERDS reported that it was receiving unknown values for two points because it could not convert that string to a number. This caused Unit 2 to fail it's ERDS test.

Lynne Saul SCIENTECH Program Manager 200 S. Woodruff Idaho Falls, ID 83401 Phone: 208-524-9371 Fax: 208-524-9282

-Original Message-----

From: Max Schneider [mailto:SMS2@nrc.aovl Sent: Tuesday, April 19, 2005 8:56 AM To: Donald Florek; Felicia Hinson; Scott Barber; Nancy McNamara Cc: Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras; LSaul~scientech.com

Subject:

Re: Preliminary Information on ERDS Delay Note: The Unit 2 ERDS failed testing last week. The CR said that Unit 2 ERDS does not work while the Unit is shutdown. This doesn't make any sense (it may not be what they intended to communicate on the CR) since ERDS would nearly always be needed when a plant is shutdown, post event. This is one of the areas for evaluation the residents are recommending to the SIT (i.e.,

potential precursor that would have led them to Investigate ERDS the week prior).

Thanks, Max.

>>> Felicia Hinson 04/19/05 10:40AM >>>

All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC

I I.

. 1.

'I I Max Schneider - RE: Preliminary Information on ERDS Delay Paae 2 1 ERDS contractor). Region I initially logged in to ERDS at 10:14:43 AM.

Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia CC:

Kevin Mangan; Paul Krohn; Silas Kennedy; Tim McGinty; Tom Kardaras

W i)C8
6
662'er

-P-r'ei--1`i-m- -I'n--a-r-v-,-I",n-f"o-rm-a"t,-i-o-n"-'o-'n-,-E-R-"D-S-Del-ay-..-

-- -. -I...I -- I -I
--

I.....----,--.--..-"-

Paqe 1 1 I Max Schneider-RE: Preliminary Information on EROS Delay Pa From:

Raymond Lorson To:

Donald Florek; Felicia Hinson; Max Schneider; Nancy McNamara; Scott Barber Date:

4/19/05 12:58PM

Subject:

RE: Preliminary Information on ERDS Delay Max:

Thanks for the follow-up. I understand that Lynne is a NRC contractor. Pls disregard the MC 0620?

Ray

>>> Max Schneider 04/19/05 12:43PM >>>

Agree should be looked at by SIT. Assumed she was a NRC contractor.

>>> Raymond Lorson 04/19/05 12:00PM >>>

Don, Max etc.

I think that the ERDS problems should be looked at within the context of the SIT. One other thing that I am not clear on is that a number of emails discussing this problem have included Lynne Saul from Scientech. Is she a licensee vendor? If so we need to docket all of our back and forth emails with her per MC 0620. The easiest way to do this would be for Scott to put in Adams and refer to the ascension number in the SIT report.

Ray

>>> Max Schneider 04/19/05 11:53AM >>>

Does this character of testing failure remove any connection to the Unit 3 ERDS failure? We only feel that 2 failures within 1 week should be evaluated as part of the SIT review to ensure there were not prior opportunities to correct a condition onsite related to emergency response equipment, we aren't advocating one way or another.

>>> "Lynne Saul" <Isaul~scientech.com> 04/19/05 11:44AM >>>

I would like to clarify about the problem Unit 2 ERDS had last week. A value of "-1.#INDOOE" was being sent for two data points. The NRC ERDS reported that it was receiving unknown values for two points because it could not convert that string to a number. This caused Unit 2 to fail it's ERDS test.

Lynne Saul SCIENTECH Program Manager 200 S. Woodruff Idaho Falls, ID 83401 Phone: 208-524-9371 Fax: 208-524-9282

---

Original Message-----

From: Max Schneider [mailto:SMS2@nrc.aovl Sent: Tuesday, April 19, 2005 8:56 AM To: Donald Florek; Felicia Hinson; Scott Barber; Nancy McNamara Cc: Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras; LSaul~scientech.com

Subject:

Re: Preliminary Information on ERDS Delay Note: The Unit 2 ERDS failed testing last week. The CR said that Unit 2 ERDS does not work while the Unit is shutdown. This doesn't make any sense (it may not be what they intended to communicate on the CR) since ERDS would nearly always be needed when a plant is shutdown, post event. This is one

Max Schneider - RE: Preliminary Information on EROS Delay Paie24

[ Mp?5 Pcl
neider - RE: Ep
ljiVMryjnformation on,

Rp
qgelay Paqe 21 of the areas for evaluation the residents are recommending to the SIT (i.e.,

potential precursor that would have led them to Investigate ERDS the week prior).

Thanks, Max.

>>> Felicia Hinson 04/19/05 10:40AM >>>

All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC ERDS contractor). Region I Initially logged In to ERDS at 10:14:43 AM.

Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia CC:

Kevin Mangan; Paul Krohn; Silas Kennedy; Tim McGinty; Tom Kardaras

Max Schneider - RE: Preliminary Information on ERDS Delay Paae 1

1. Max qpl
neid

- RE: Preli irl

-- n ERDS Del- --

r m ono ay er yJrLfqr ati Page 1 1 From:

"Lynne Saul" ;dsaul @scientech.com>

To:

"'Max Schneider"' <SMS2@nrc.gov>, "'Donald Florek"' <DJF1 @nrc.gov>, N'Felicia Hinson'" <FML@nrc.gov>, "'Scott Barber' <GSB@nrc.gov>, "'Nancy McNamara" <NTM@nrc.gov>

Date:

4/19/05 1:04PM

Subject:

RE: Preliminary Information on ERDS Delay

Max, It would seem to me that these two types of failure are very different.

However, I am not advocating that they not be looked at in the SIT review.

Instead I was trying to provide more information about what has been reported to me. Lynne Original Message-----

From: Max Schneider [2]

Sent: Tuesday, April 19, 2005 9:54 AM To: Donald Florek; Felicia Hinson; Scott Barber; Nancy McNamara; Isaul@scientech.com Cc: Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras

Subject:

RE: Preliminary Information on ERDS Delay Does this character of testing failure remove any connection to the Unit 3 ERDS failure? We only feel that 2 failures within 1 week should be evaluated as part of the SIT review to ensure there were not prior opportunities to correct a condition onsite related to emergency response equipment, we aren't advocating one way or another.

>>> NLynne Saul" <Isaul~scientech.com> 04/19/05 11:44AM >>>

I would like to clarify about the problem Unit 2 ERDS had last week. A value of "-1.#IND0OE" was being sent for two data points. The NRC ERDS reported that it was receiving unknown values for two points because it could not convert that string to a number. This caused Unit 2 to fail it's ERDS test.

Lynne Saul SCIENTECH Program Manager 200 S. Woodruff Idaho Falls, ID 83401 Phone: 208-524-9371 Fax: 208-524-9282

---

Original Message-----

From: Max Schneider [3]

Sent: Tuesday, April 19, 2005 8:56 AM To: Donald Florek; Felicia Hinson; Scott Barber; Nancy McNamara Cc: Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras; LSaul~scientech.com

Subject:

Re: Preliminary Information on ERDS Delay Note: The Unit 2 ERDS failed testing last week. The CR said that Unit 2 ERDS does not work while the Unit is shutdown. This doesn't make any sense (it may not be what they intended to communicate on the CR) since ERDS would nearly always be needed when a plant is shutdown, post event. This is one of the areas for evaluation the residents are recommending to the SIT (i.e.,

potential precursor that would have led them to Investigate ERDS the week prior).

I M-ax Schneider - RE: Prelimrinarv Informnation on ERDS Delay l

Page 2 I Max S.cn r.r Inomto o:

RD,.el Paae2_

Thanks, Max.

>>> Felicia Hinson 04/19/05 10:40AM >>>

All -

I have attached the copy of ERDS log that was developed by Lynn Saul (NRC ERDS contractor). Region I initially logged In to ERDS at 10:14:43 AM.

Millstone 3 did not actually get connected until 12:03:34 PM EDT.

Lynn worked with Tom Bowlen (Millstone) to determine the cause of the delay with the initial ERDS connection during the Millstone event. It appears that the problem can be attributed to an issue with the utility's ERDS software which will need to be corrected.

Felicia CC:

"'Kevin Mangan"' <KAMI @nrc.gov>, "'Paul Krohn"' <PGK1 @nrc.gov>, "'Raymond Lorson'" <RKL~nrc.gov>, "'Silas Kennedy' <SRK~nrc.gov>, "Tim McGinty" <TJM1 @nrc.gov>, "Tom Kardaras"' <TXK1 @nrc.gov>

I I Max Schneider - Fwd: Millstone issues Page 1 11 From:

To:

Date:

Subject:

Neil Sheehan Max Schneider; Paul Krohn 4/19/05 1:27PM Fwd: Millstone issues Paul/Max, Are we going to be looking at these things?

Neil

Max Schneider - RE: Preliminary Information on ERDS Delay A_

Page 1 From:

Nancy McNamara To:

Donald Florek; Felicia Hinson; Lynne Saul; Max Schneider; Scott Barber Date:

4/19/05 2:19PM

Subject:

RE: Preliminary Information on ERDS Delay I agree we need to look at it. However, everyone needs to keep in mind that the ERDS program is owned by the NRC and most licensee's are using NRC equipment or software, so if there are problems, many times its due to our software or equipment. Now, if the licensee replaced any of that with their own, we are in different space. Again, we need to followup. Also, we should review why the EOF kept telling us it was working when it wasn't. What was the communication disconnect between the CR and EOF. Also, they disconnected the ERDS when they exited the Alert. We needed that connection to continue to follow changing plant conditions in support of cooldown. This may be a good lesson learned to ensure the licensee keeps it up or at least notifies us they turned it off.

CC:

Kevin Mangan; Paul Krohn; Raymond Lorson; Silas Kennedy; Tim McGinty; Tom Kardaras