ML062510288

From kanterella
Jump to navigation Jump to search
E-mail from Eichenholz to Wingfield, Brief for Transcript Reviews
ML062510288
Person / Time
Site: Salem  PSEG icon.png
Issue date: 04/03/2004
From: Eichenholz H
NRC Region 1
To: Ted Wingfield
NRC Region 1
References
FOIA/PA-2005-0194
Download: ML062510288 (3)


Text

Harold9JŽihf

- Re: Brief For Trncript Reviews Page 11 From:

To:

Date:

Subject:

Harold Eichenholz V/

Theodore Wingfield Sat, Apr 3, 2004 1:08 PM Re: Brief For Transcript Reviews

Ted, Attached please find the completed transcript review given to me last week.

Harold

>>> Theodore Wingfield 04/01/04 09:38AM>>>>>

Attached is the applicable form (any specific info included are merely examples of items to enter)..

When finished just email it back to me.

We prefer a "efficient & quality" review of the transcripts (instead of a "rapid" review).

The reason were asking for help is that the volume of transcripts to review has increased beyond the level where I will be able to review them all by mid-late April.

Brief prior to reviewing a transcript:

1) Review the attached "review considerations" document. This was written by Scott Barber to aid in generating.a focussed look at a transcript. It provides a good overview of what we are looking for.

2). Read the attached example "binningu document. This will help comunicate some of the issues that have been identified,.a flavor of what we are extracting from the transcripts, as well as give you an understanding of Why we issued our January 28th letter to PSEG.

Thanks, Ted Information In this record was deloted in accordance With the.Freedom of I,,f,,._at, Act, exeptions
  • ,urintion FOIA-.ý

'VV

Harold

-Completed"Trh-nnscri p"eviej Page-.

Reviewer Harold Eichenholz notes/comments on theminterview (10-29-03)

The following are my observations/questlons of th terview 10-29-03.

ASSESSMENT QUESTION YES/NO AMPLFICATION (N-IYWHY NOT, ETC.)

Subject will raise concerns and has done so?

Yes Doesn't bother him what people think of him Subject would raise concerns if necessary?

Yes His management tells them - if you have an Issue bring It up Subject raises concerns for others, why?

Yes ind acts for those that either do not want to deal wit concern or bring it up, or don't want to be Identified with concern Subject won't raise concerns-Why?

Yes Most try to fix concerns in-house first so that the NRC would not need to be Involved Do others raise concerns?

Yes But concern Is that people that raise concerns do not feel that they are being heard.

Others don't or hesitate to raise questions?

Yes Some are uncomfortable, but it Is nota pervasive problem Someone has experienced retaliation for raising No concerns?

Bins for Issues:

  1. 1 - PERCEIVED LACK OF FREEDOM TO RAISE SAFETY CONCERNS TO PSEG MANAGEMENT
  1. 2 - PRODUCTION OVER SAFETY ISSUES
  1. 3.- SCHEDULE PRESSURE ISSUES
  1. 4.- LABOR - MANAGEMENT ISSUES
  1. 5 - INDUSTRIAL SAFETY ISSUES OTHER UNSPECIFIED ISSUES/COMMENTS
  1. 1 - PERCEIVED LACK OF FREEDOM TO RAISE SAFETY CONCERNS TO PSEG MANAGEMENT (p. 54 - 59) The safety culture at Salem reflects managers, and to a less-r degree peers, looking down on people that raise Issues. Interviewee believes that OSs take direction from above that they are not comfortable with because they have to, and thinks that his particular OS has hade his job threatened for backing up the NEOs and threfore was taken off shift for several weeks to get "reprogrammed.". This OS has PtelLpn several occaslons that hIs crew gets

'him In trouble all the time..ThInks the problem resides With a couple o: OMSthe currenienerai Manageenew position), and a director that Is no longer on-site. An operations personils.harassed by his"upervisors (I.e.,-they hound him hard) because he raises Issues.

  1. 2 - PRODUCTION OVER SAFETY ISSUES (P. 12 - 17) Discusses the Salem 1 Valve BF19 (feed reg. Valve) equipment problem that occurred In mid Oct. 03 that required a plant shutdown. The valve appeared to be stuck and the Interviewee Indicated that no actions were taken for many hours, Including entering TS 3.0.3 and sending someone to attempt to free up the valve and figure out that the valve was mechanically stuck (said the situation was hokey - It took way longer than it should have In his opinion). The sticking of the valve appears to be a recurrent plant equipment problem Involving the valve getting hung up, with a normal response by plant operators consisting of sending a maintenance person to free up the valve (spraying on lubricant and striking valve components with a mallet). The failure of the valve results In entry Into TS 3.0.3 which would require a plant shutdown.

(p. 28 - 34) MS 42 valve bonnet steam leak on a manual valve which should have required a plant shutdown to dose valve - operators would no o nearvalve beca ek was so bad (p. 20) and couldAi determine where theJeak was coming from. Butin

-"nt to valve without operators anc&ia&Mlkaand without consideration f'"t*nee a eam rscu--de~s-o Id-conditions worsen. The thought proc6ssat wenet Into Page Iof 2

Harol Echnoz -

.mp!e!d I

Reviewer Harold Eichenholz notes/comments on the terview (10-29-03) the decision making to dose the valve In the manner In which It was done was a "megawatt mentality." (Interviewee only has second hand knowledge of issue)

(p 43 - ) Grassing In intake structure event In March 03 - Unit 2 was taken off and Unit 150% power. The interviewee thought that the OS was getting pressure from above him to keep the units on-line because he looked uncomfortable.

  1. 3 - SCHEDULE PRESSURE ISSUES (p. 34 -40) Deferral of 5 or 10 yr. inspection Interval for bolts for at least one outage, possibly two ( Summer 2002 or 2002, but possibly Fall 2003). Halfway through 18-month cycle found lots of boron and degraded bolts. Operability determination required to see If.bolts holding the head on the RHR heat exchanger were good enough to hold while bolts were replaced one at a time. Deferral of Inspection was due to wanting to hold outage schedule to 19 days.

Bolting condition should have found during outage If inspection was conducted. Interviewee unaware If Inspection was a specific NRC ISI or IST requirement or If deferral was NRC approved or not. But, he was aware that the responsible engineer was angry when Inspection was deferred and when the bolt wastage was identified, and that the item was removed from the outage schedule.

  1. 4 - LABOR - MANAGEMENT ISSUES (p. 62 - 69) In last 1.5 years had escalating battle between workers and management - thinks it started when INPO gave them a three ratings. Management will not take accountability for deficient processes like work controls - an absolutely horrendous process that results In 17% wrench time. The Issues with work controls has been an ongoing problem for years and they can't seem to get a handle on it. Also, there Is a concern by workers that there Is mismanagement In not fixing broken stuff out In the primary system that needs to be fixed, but because of outage schedule the work on the primary system Is frozen even with 14 more days required for work on the secondary side.

Management does not give credible answers to the plant workers raising questions on this matter and the answers given just do not make any sense.

(p. 73 - 77 ) NEOs concern about being heard. It's the screaming and yelling, the tit-for-tat stuff that Is all adding up into "white noise". NEOs are concerned about how do you make sure that what really needs to be heard gets heard and continue to believe that their attempts to continue to be heard Is still being treated by management as white noise. Most NEOs feel they are white noise - except for a few that are good at jumping up and down. About a year ago the management and union held fairly regular scheduled meetings and were doing ok for awhile, but In the last 6-months things have gotten really. bad. No sense In doing them because they are not productive - not getting anything done. The current situation Is that NEOs believe there are Issues with the plant and some Issues with the workforce, but basically the workforce doesn't trust the management at all,;In anything - either running the plant or In personnel Issues between the company and union. While this environment may be making some people uncomfortable about raising nuclear safety or personal safety Issues, it Is his opinion that those that tend to raise Issues will continue to do so.

  1. 5 - INDUSTRIAL SAFETY ISSUES (p. 28 - 34) MS 42 valve bonnet leak on a manual valve-efforts to dose valve were done without proper.

consideration for steam rescue should conditions deteriorate as part of valve manipulation. (Interviewee only has second hand knowledge of Issue)

OTHER UNSPECIFIED ISSUES/COMMENTS (p. 19 - 28) Relates to potential Issue about event notifications disappearing. Interviewee has had difficulty in locating them In system (example 201-63-897, MS-42 valve bonnet leak In Sept. 02, found only one notification when he knew that three had been written). Believes that a sensitive CR written against a supervisor for not paying attention to safety processes (heat stress and ALARA) was changed to prevent access unless you had the right level of authorty.

  • Not sure If notifications are disappearing, and believes that If Information on notifications In the system Is being changed It Is not being done through malice.

(p. 46 - 48) Continuously have problems with charging pumps and room coolers due to bio-fouling. Situation causes routine entry Into charging system TS to allow deaning of lube oil coolers and routine challenge to safety-related equipment and room coolers. Lot of people working on Issue and trying to fix problem and It Is a top priority - doesn't think there Is any malice regarding this Issue and believes that the service water system Is one of their hardest challenged systems. ( p. 70 - ) Also, feed pumps and air compressors have fouling of their coolers more frequently than used to.

(p. 51 - 53) Record retention concern raised by Interviewee In June or July of 2003 that Is currently being reviewed by his organization. Concern Involves not keeping Q-based records, and therefore not being able to prove that required activities are being accomplished.

Page 2 of 2