ML20148P013
| ML20148P013 | |
| Person / Time | |
|---|---|
| Site: | Millstone  |
| Issue date: | 06/23/1997 |
| From: | Neri A, Querio R, Raheja R SARGENT & LUNDY, INC. |
| To: | |
| Shared Package | |
| ML20148N977 | List: |
| References | |
| PI-MP3-11, NUDOCS 9707010099 | |
| Download: ML20148P013 (17) | |
Text
. . - . _ -
e
(.
- !"" INSTRUCTION PI-MP3-11 PROJECT
[ .
INSTRUCTION .- REV.3 l
l Client: Northeast Utilities l
Station: Millstone Unit 3 l
l
Title:
DISCREPANCY REPORT SUBMITTAL AND CLOSURE l
[ Safety-Related Non-Safety-Reilated Reviewed By: Approved By:
System Lead Programmatic 08M Lead Accident QA Engineer Intemal Review Verification Team Lead Mitigation Committee Manager Lead Chairman y m _., s 1 / Date: d*A S-$
l b $ $*' WS W/ Waw N& '
lN/U.oMb& %K10 ' '
Description
(/ (/ f.XJ Rev.3 Revised PI to require posting of DR interaction between S&L and NU on NU proposed resolutions on Internet Bulletin Board Also replaced Attachment 6.2 to reflect current DR database screens.
l l
1 l
l l
Page 1 of 10
~
9707010099 970627 PDR ADOCK 05000423 P PDR
3
- A , , ,
PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION [ REV. 3 1.0 PURPOSE f
j This instruction establishes the requirements for the preparation, submittal and closure of Discrepancy Reports for descrepant conditions identified by the Independent Corrective Action Verification Program (ICAVP) Team. This l Instruction addresses the preparation of DRs by the ICAVP team, the review of proposed resolutions developed by Northeast Utilities and the trending of DRs generated by the Verification Team.
2.0 REFERENCE l l
2.1 NRC Confirmatory Order Establishing Independent Correction Action Verification Program - Millstone Nuclear Power Station, Units 1, 2, j and 3 1
2.2 PI-MP3-01, ICAVP Communication Protocol l 2.3 PI-MP342, Review of System Design for Compliance with Design &
Licensing Basis 2.4 PI-MP3-03, Review of Plant Mc-Jifications Prepared After Receipt of Operating License for Technical Adequacy and for Configuration Control.
2.5 PI-MP3-04, Programmatic Reviews 2.6 PI-MP3-05, Physical Plant Configuration Walkdowns 2.7 PI-MP3-06, Operations and Maintenance and Testing Procedures and Training Documentation Reviews 2.8 PI-MP3-07, Review of Accident Mitigation Systems 2.9 PI-MP3-10, Differing Professional Opinions 2.10 PI-MP3-12, Project File Index Page 2 of 10
" 7 ""
PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION - REV.3 s
l l 3.0 DEFINITIONS l 3.1 Accident Mitigation Review Group (ARG)- The subgroup of the ICAVP l Verification Team responsible for review of critical characteristics of accident mitigation systems to ensure those systems can perform their required safety functions.
3.2 Internal Review Committee (IRC) - A committee comprised of senior S&L management personnel responsible for overall technical oversight of the ICAVP.
3.3 Operations & Maintenance and Testing Review Group (ORG) - The stbgroup of the ICAVP Verification Team responsible for the review of the opereting, maintenance and testing procedures, and training materials for the sy items within the scope of the ICAVP.
3.4 System Review Group (SRG)- The subgroup of the ICAVP Verification Team responsible for performing an in-depth review of the design of the systems .n the scope of the ICAVP.
3.5 Configsration Review Group (CRG)-The subgroup of the SRG Vermcation Team responsible for walkdowns to verify the current as :
built conditions are in conformance with the design output documents. )
3.6 Program-lnatic Review Group (PRG)- The subgroup of the ICAVP Verifica'lan Team responsible for review of the processes used to change the facility design or the operation, maintenance and testing of the facility.
The PRG is also responsible for verifying the adequacy of NU's corrective actions.
3.7 Discrepancy Report (DR)-The mechanism for documenting the discrepant conditions identified by the ICAVP and reporting the condition to NU for resolution.
3.8 Discrepancy - A discrepancy is a condition, such as an error, omission or oversight which prevents consistency among the physical ,
configuration, information sources (e.g. documentation and databases), I design basis and/or regulatory requirements.
Page 3 of 10
i
~
INSTRUCTION PI-MP3-11 PROJECT INSTRUCTION ~- 7"" REV. 3 i
4.0 RESPONSIBILITIES
} 4.1 Initiator - Responsible for preparation of DR in accordance with
, the instructions contained in this project instruction.
Responsible for review of proposed NU resolutions in i accordance with the instructions contained in this project instruction.
i 4.2 Verification Group Lead - Responsible for first level review of DRs prepared by Initiator.
- Responsible for review of S&L's
! dispositions to proposed NU resolutions.
- Responsible for resolving comments with the initiator.
) 4.3 Verification Team Manager -
Responsible for reviewing initial DRs and S&L dispositions to proposed NU resolutions.
l.
- Responsible for resolving comments with the Verification Group Lead and the Initiator.
f Responsible for overall control of DR process including maintenance of DR log, trending data and external 4
distributions.
i 4.4 IRC Members / Chairman -
Responsible for reviewing DRs and
'3 dispositions of proposed NU
> resolutions prepared by the Verification Team and for resolving any comments with the Verification
- Team.
i 1
Page 4 of 10 1
. - . ~ . - - . - . - - - - . - . . . . . - - . _ . - - . . . .- -
PROJECT '9 h INSTRUCTION PI-MP3-11 INSTRUCTION .d REV.3 5.0 PROCEDURE The Nuclear Regulatory Commission (NRC) Confirmatory Order (Reference 2.1) requires Northeast Utilities (NU) to implement the ICAVP. References 2.3 through 2.8 provide the instructions for implementing the reviews included in the scope of the ICAVP. Discrepant conditions identified by the Verification Team members during the performance of these reviews will require the initiation of a DR. This project instruction provides the requirements for initiating, processing and closure of DRs. DRs shall not be generated for findings already identified by NU during implementation of their Configuration Management Plan.
Note: DRs shall be generated as soon as practical after the condition has been identified. Those DRs which may be potential operability concems shall be expedited through the review and approval process and NU shall be notified per Subsection 5.5.1 of this instruction.
The DR process involves the following tasks:
- a. DR initiation
- b. DR resolution and closure
- c. DR log and trending data
- d. DR distribution DRs shall be generated in an electronic format using a DR Access Database.
Attachments 6.2 through 6.5 of this project instructions illustrate sample database input screens. Hardcopies of the DRs, a DR Log, DR status reports and DR trend reports can be generated from the database.
The detailed instructions for each of the above task are described in sub-sections 5.2 through 5.5. Attachment 6.1 is a flow chart illustrating the DR process.
5.2 DR Initiation 5.2.1 Members of the ARG, CRG, ORG, PRG and SRG Verification Teams shall initiate a DR for any discrepant condition identified during their respective reviews. The individual initiating the DR shall be referred to as the initiator.
Page 5 of 10 1
.- - . - . . .=- - . - . . - _ - - - ~ . . - . - . - . . - - . - . . - - . . -
b PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION .- REV. 3 l
l Mgig: Before initiating a DR, the Initiator shall ensure the condition has been thoroughly investigated and the total scope of the condition has been identified. Any additional information needed from NU shall be requested per PI-MP3-01.
5.2.2 The Initiator shall prepare the Discrepancy Report by entering the following data into the database's " Discrepancy Screen", Attachment 6.2:
Hgig The fields listed below which are indicated with an asterisk have pulldown menus. Applicable entries in these menus are listed in Attachment 6.6.
Field instruction Review Group
- Enter Applicable Review Group Review Element
- Enter Applicable Review Element Discipline
- Enter Applicable Organization Discrepancy Type
- Enter Applicable Discrepancy Type Potential Operability
- Enter whether the Discrepancy is a issue Potential Operability Issue using the guidance in Attachment 6.7 System / Process Enter by Full Name the system or process being reviewed.
Discrepancy Enter brief title Description Enter detailed description of condition including specific references and basis for potential operability determination, if DR is determined to be potential operability issue.
Page 6 of 10
1 PROJECT INSTRUCTION PI-MP3-11 l lNSTRUCTION .- REV.3 t
Initiator Enter your name; Last name first followed
- by first and middle initials (i.e. Doe, J. A.)
l Date Enter preparation date The database will automatically assign DR Nos., revision level and status.
5.2.3 The VT Lead shall review the initial DR draft.
5.2.3.1 If the VT Lead has comments on the DR or determines that additional information is needed, the VT Lead shall resolve the comments with the Initiator.
5.2.3.2 If the VT Lead does not concur with the DR, the VT Lead shall complete the " Invalid Screen", Attachment 6.3, by entering his name, date and justification for the invalid disposition. The VT Lead shall review the invalid disposition with the Initiator.
5.2.3.3 If the Initiator agrees with the VT Lead's invalid disposition, the Initiator shall indicate his concurrence on the " Invalid Screen",
Attachment 6.3. The initiator shall then file the invalid DR with the applicable element review file.
5.2.3.4 If the VT Lead and Initiator do not reach agreement, the VT Manager shall resolve the issue. If either of the parties has a safety concern related to the DR, the provisions of PI-MP3-10 for Differing Professional Opinions may be invoked.
5.2.3.5 If the VT Lead concurs with the DR, the VT Lead shall enter his name, and date on the Discrepancy Screen, Attachment 6.2.
5.2.4 The VT Manager shall review the DR. The review process shall be consistent with the instructions contained in Subsections 5.2.3.1 through 5.2.3.5 above, except that any comments or invalid dispositions shall be reviewed with both the Initiator and the VT Lead.
Ngtt' The reviews associated with Subsections 5.2.3 and 5.2.4 I can be concurrent in a group session, i
I Page 7 of 10
~
"y "
PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION - REV. 3 5.2.5 The IRC shall review the DR. The review process shall be consistent
. i with the instruction contained in Subsections 5.2.3.1 through 5.2.3.5 above, except that any comments or invalid dispositions shall be reviewed with the Initiator, VT Lead and VT Manager.
5.2.6 The VT Manager shall distribute approved DRs to the NRC, NEAC, NU and the Public in accordance with Subsection 5.5 of this project instruction.
5.3 DR Resolution and Closure 5.3.1 Proposed resolutions submitted by NU shall be reviewed in a manner similar to the DR initiation process described in Subsection 5.2 of this project instruction. The DR proposed resolution shall first be reviewed by the Verification Team and then the IRC. Concurrent review by VT members, Leads, and Manager are permitted.
5.3.2 The initiator shall summarizes the NU resolution on the "NU Resolution Screen", Attachment 6.4. Concurrence by the VT members shall be indicated on the screen, Attachment 6.4. The DR shall be distributed to the NRC, NEAC, NU and the Public per Section 5.5 of this project instruction.
5.3.3 If the Initiator, VT Lead, VT Manager or IRC do not concur with the proposed resolution, the non-concurring party shall document their I lustification for rejecting the resolution on the " Rejection Screen", !
Attachment 6.5 and obtain concurrence from all other members on '
Attachment 6.5. Rejected Dispositions shall be distributed to the NRC, NEAC, and NU in accordance with Subsection 5.5 of this project instruction.
5.3.4 Revised proposed resolutions submitted by NU in response to S&L i comments shall be reprocessed in accordance with Subsection 5.3.1 through 5.3.3. Only one additional resolution cycle per discrepancy is anticipated.
5.3.5 If all groups, (the VT members and the IRC) cannot reach agreement on acceptance of the proposed NU resolutions and anyone has a safety concern, then the provisions of PI-MP3-10 for differing professional opinions DPO may be invoked.
Page 8 of 10
"y
~
l PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION - REV. 3 i
l 5.4 DR Loa and Trendina Data l
5.4.1 DR Log i
- 5.4.1.1 The DR database shall automatically assign DR Nos, status and
- revision. Hardcopy logs can be generated from the database.
l 5.4.2 Trending Data 5.4.2.1 The DR database can be sorted by the entries on Attachment 6.6 to
. generate trend reports. l
! 5.5 DR Distribution
. 5.5.1 Initial issues i
- 5.5.1.1 The VT Manager shall distribute DRs to the NRC, NEAC, NU and the Public per Subsection 3.3 of PI-MP3-01. Distribution to the
! NRC, NEAC, and NU shall be in the form of hardcopies. Distribution to the public shall be via the electronic bulletin board. Posting of the DR's on the electronic bulletin board will be 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> after hard-copies are mailed to NU/NRC/NEAC. Since generation of DR's will l l be by electronic media with database security provisions, signatures j shall not be required.
5.5.1.2 The VT Manager will fax DRs which may pose potential operability i concern to the NU Point Of Contact identified in PI-MP3-01. The date j sent shall be entered on the Discrepancy Screen.
l i
l ,
f 4
i i
i d
i f
4 Page 9 of 10
. l j
s l
- c dIL l PROJECT INSTRUCTION
- ]p*" INSTRUCTION PI-MP3-11 REV.3 1
l 1
j 5.5.2 Proposed Resolutions l 1
i 5.5.2.1 The VT Manager shall distribute accepted (closed) DRs to the NRC, i NEAC, NU and the Public in accordance with Subsection 3.4 of PI-MP3-01. Hardcopies shall be sent to the NRC, NEAC, and NU.
2 i
5.5.2.2 The VT Manager shall distribute S&L comments on proposed l
- resolutions to the NRC, NEAC, and NU, in accordance with 1 4 l Subsection 3.4 of PI-MP341. Posting of DR interaction between NU and the VT on the electronic bulletin board will be 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> after hardcopies are mailed to NU/NRC/NEAC.
l l 6.0 ATTACHMENTS 6.1 Process Flowchart, Processing Findings & Resolutions (1 page).
{
6.2 Sample Discrepancy Screen (1 page).
t 6.3 Sample Invalid Screen (1 page).
4 6.4 Sample Resolution Screen (1 page).
4 6.5 Sample Rejection Sheet (1 page) 6.6 Summary of Available Entries for Pulldown Menus (1 page) 6.7 Criteria for Operability Determination (1 page).
N_qtg: Attachments 6.2 through 6.4 are sample illustrations of the DR Access Database data entry screens. This instruction will be revised if the data fields are revised. Revision to this instruction is not required for format changes to the data entry screens.
Page 10 of 10
(
Initiate Discrepancy PI-MP311. Rev. 2 PROCESSING FINDINGS :
AND RESOLUTIONS VT 1r Review DR vrMgmt i
1r Document Basis for Not m is DR Vaid & DR not Discrepent c Awe? vend W 4 VT Yes v
go, % Review DR info Required IRC is DR Valid & DR not Adequaie? Velid ~~
Yes Submit DR to NRC/
NEAC/NU & Post on ,
Electronic BB VT Mgmt 1r Provide DR Response to VT Management NU Document Neesons for Rejection / Submit to NU/ 1r NRC/NEAC & Post on Review NU Response Electronic BB for Adequacy VT Mamt 1r Review NU Response
& VT Acceptance /
Re;ection
.RC a
r Document Acceptance NU Response & Submit to NRC/
No toDR Yes ----> NEAC/NU & Post on Adequate? Electronic BB VT Mgmt
- PI-MP3-11, Rev. 3 Attachment 6.2 k
l l sus i :v. $
! - file: . Edit JYew n.-Becords Windowmtielp', 44 m. >* M:A Ec 4 r:'i m -q m
- l 9
1 l Exit Discrepancy invstid Resolution Rejection i
,. 9:6. 6 c -
- ^
,, fQ. _u,. . g2,;., yu h. . , ,,4 y,Jpu
- y
,,W, . l ,f p;j gmas(niny j . p. / , y ..Group:
Beview . : ' v. ; ,l,JAccident Mkgation .
, ;~
,v a .y am Qg ""'"'f.M .f:,;-
3,
- RW Ehunent
- ;l.JCorrectrve Action Process
. :: a c - c. --~
~g gybn[*y. . -
..i n Q ; m.,jl&n.@m
.~ , h % Q Mgg
, m]7.ps 4 . g w,n.c C h ]p n.m{.l0$j' TQ l ";; 4'Eh nDiscipline:';] Electrical Desgn 1 ..;;. y : m',
g,- *:: Potent,ial Operataty: leade' 1DaJes i', $_ m@
e w g,qh ,y
'. WM3:
i Disciepancy Type: 7lCalculabon ,.y: w.
" ~ gy, ;g%#QiNf;!!M9 e'
, .. . ..! -*!; > Y y-i
, @.'; .if
{
l
'Spetem/ Process:ilQSS c .. s-a& 2.& Mumr nwwwunn.,x..:a. ns.n,.xu .,
m' gi EC: % . Lie:&c,.St .- -
...M 7 h. :nu;3g1.p]W; y;Q#;fa ~I
. l.
Dis.crepancy: p l . . >, ~ , r]. Sample Discrepancy Report
~
- .? - 4) l .:Descrip
_Wortj Descriphon of Sample Discrepancy Report dj l 1,:,.
- b 4 Gj
- se
}
- n.
, s 1 initiatoc Heen si H.wv H FValid Ilnvalid .IReview . Needed Date:. 6/16/1997 j VT Lead:l R 9.ep R x D - H FValid Finvalid .liiReview Needed? :Date::
) -VT Managec wier Dur' t " . IValid Finvalid FReview Needed , jDate: Q
'l . IRC Chairuiere[ nir'+ Arwe H . (~ Valid T, ..m inv.alid ,l.ii Q-p, Review Needed m- XDa.te:
- 4. .
34any
)
. 7;. , - < ,J .~v
..,g . . .n_?:g._
4 l Is this a Potential Operability lasue? . , ,,c , o _. . 1 1. .L A I aINUMi:.s;la e 1
i l
1 a
a 1
l l 1 I
I I
i
PI MP3-11, Rev. 3 Attachment 6.3
=Q S&v c
= Elle Edit Yiew Becords Window ticip n" .m 4 1
8
- DB-MP3-0001 2 Exit Discrepancy invalid Resolution Rejection l
1 invalid Date- l 6/16/1997 . _
_- l Invalid Sample lustdication for invalid descripancy &
, Justification.
== ;M
+; -
~ p>
n (A
h is]
3 4A% .. .
.. y ... 'g> -
- Ey 'e i . -o ,
EN .he "
,e r, j u
To view Diu repancy Review Checkoffs, return to DISCREPANCY screen.
[4]_4 j Recordl1 lof 1 l >j H1 Justifcation for Invalid Discreparv/ , _o , , .
, j,,x; ; 11FLTR I la .1.2.lNUMI. /;I A i
' PI-MP3-11, Rev. 3 j ,.
Attachmsnt 6.4 i -35 DEE-e
! =
Elle -Edit ,'llew Becords Window tielp c 1
i 4
4 DR MP3-0001 2 j Exit . Discrepancy ,etnva
. ~ lid ' Resolution Rejection-
}
Dil No: lD R-MP3-0001 .a() g g t Date Entered: l 6/16/1997 -
NU Resolute,r Sample Resolution Descnotion e
! lutWdid/%
av .W s..
4 ; / 4., v.m}y;.Me.,, i{
1 g,g .y
. '- ; h..
9
^
g
- . lf E '.:-l '; <
1 .
j- .., )
j 4 ,Y c j '
1 a.
J - . e.:4 lm n i' 4 M Mjha u :f _ g
- . yy y"wm ppp-mp7yc/e c7 ;7m . - - fjd
, - yynnrer
- -s.z ; Do you accept or rep, et NU's re:olution? yymgyg* pars py
' 'I4x?
~ "
I
_ ' initiatos: Hv vr,isi H so,' M RAccept . . . -F Reject
.. .. , 'M FReview Needed . . Datet 6/16/1997 VT Lead:' RM+oRvD - H f~ Accept F Reject RHeview Needed Date:
VT Manager. %ver [iuri L y I Accept I Reject R Review Needed Date:
IRC Chairasan: Snd Ar.s , H I Accept F. . Reject
- R Review Needed.
Date-t '
i M141 Record {1 lol 1 lklHI 2
Descriptionof NortheastUtilitiesResobAionS W \ ~ ^ :.x _ ilFLTflj%!1:e.j; A lNUM l . . a 1 Ataj i
h i
a t
a 4
1 i
v
~
PI-MP3-11, Rev. 3 Attachmont 6.5 1
j =E ESv ? l
= Elle Edit yiew Becords Window Help e i
DR-MP3-0001 2 1 .. .
l l Exit ~Discrepanby in.va. lld . Resolution Rejection l Date:- l 6/16/1997 1
Justification Ios Sample Relecton Just6 cation +
Heioction:-
I
. , e j ; .di .} fj;j up
- 9 ,
t g
( ; ,
l i
i i
- t:
- 't.,A a;
k.
n rs
~, .
kf2j t
I i
5 4 l
, xs.. ..s. .v ., . . n. ~,. ,. ,-
c
, .. ..n 4-n; e.1, ..iTo view Resolution Review Checkoffs, return' to RESOLUTION s,creen!', 'Ca 3 4 l Hj 4 l Record l1 lot 1 l>lHl i Justifcation fotRejection of Resdution lffTUil I i INUMl l 1
i
< 1 1
i i I
i i
i 1
2 i
l t
l
)
i i
i i
1 a
l .
'.. 1 PI-MP3-011, Rev.1 Attachment 6.6 i
SUMMARY
OF AVAILABLE ENTRIES FOR PULLDOWN MENUS l
FIELD ENTRIES Review Group CRG ORG :
PRG SRG ARG l Review Element System Design Modification Design j System Installation 1 Modification Installation Operating Procedures Test Procedure Maintenance Procedure Training Procedure Change Process l Corrective Action Process !
l Discipline' ' Mechanical Design j Electrical Design l I&C Design !
Structural Design l Piping Design l Equipment Qualification l Operations Maintenance Training Other Discrepancy Type Drawing Component Data Calculation Licensing Document Test Requirements Installation Requirements Installation Implementation O&M&T Procedure O&M&T Implementation Corrective Action Procedure Implementation Change Process l
Potential Operability Issue Yes No
._ _ _ _ _ _ _ _ _ _ _ . _ .. _ _ . _ _ _ _ . _ _ _ _ . - _ . _ ~ _ _ _ _ .. _ . _ _ __ _
C ,
[
r.
PIMP 3-11, Rev.1 Attachment 6.7 l- CRITERIA FOR POTENTIAL OPERABILITY ISSUE l
The following criteria shall be used to determine if a DR poses potential operability L issue:
- 1. Any departure from the conditions of the operating license, Technical Specifications.
- 2. Any occurrence or plant condition that requires notification to the NRC or other :
regulatory agency in accordance with the Configuration Management Plan.
i
- 3. Failure to meet the provisions of the Technical Requirements Manual.
- 4. Conditions resulting in a Maintenance Rule Functional Failure (MRFF)
5, Any occurrence that appears to jeopardize radiological protection, or may be a violation of a program, procedure or regulation with radiological implications.
I
. - - - . __ ._. .