ML20203F686
| ML20203F686 | |
| Person / Time | |
|---|---|
| Site: | Millstone  |
| Issue date: | 01/28/1998 |
| From: | Neri A SARGENT & LUNDY, INC. |
| To: | |
| Shared Package | |
| ML20203F653 | List: |
| References | |
| PI-MP3-11, NUDOCS 9803020024 | |
| Download: ML20203F686 (20) | |
Text
. _ - _ _ _ _ _ _ _ .
4 PROJECT INSTRUCTION *[*" -
INSTRUCTION PI-MP3-11 REV.5 l l
Client: tiortheast Utilities Station: Millstone Unit 3
Title:
DISCREPANCY REPORT SUBMITTAL AND CLOSURE S Snfety-Related Non Safety Related Reviewed By: Approved By:
System Lead Programmatic O&M Lead Accident QA Engineer Intemal Review Verification Team Lead Mitigation Committee Manager Lead Chairman
' Date' l*2.S* W
!hb b N'/') kE " M?'MdI ~
Description ro V a) o1 Rev.5 Revised PI to: l
. Add Additional DR Status Blocks on Resolution Screen
.- Eliminate IRC Review of Level 4 DR Resolutions Page 1 of 11 l 9803020024 980225 PDR ADOCK 05000423 PDR
~
PROJECT ""
INSTRUCTION PI-MP3-11 INSTRUCTION - REV, 5 l 1.0 PURPOSE This instruction establishes the requirements for the preparation, suhittal I
and cloeure of Discrepancy Reports for descrepant conditions identified by
( the Independent Corrective Action Verification Program (ICAVP) Team. This I
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 2.1 NRC Confirmatory Order Establishing independent Correction Action Verification Program - Millstone Nuclear Power Station, Units 1,2, and 3 2.2 PI-MP3 01, ICAVP Communication Protocol 2.3 PI-MP3 02, Review of System Design for Compliance with Design &
Licensing Basis 2.4 Pl-MP3-03, Reviev. of Plant Modifications 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 Rcviews 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 11 l
PROJECT
-INSTRUCTION
- "y s INSTRUCTION PI-MP3-11 REV.5 l 3.0 DEFINITIQHR ;
3.1 Accident Mitigation Review Group (ARG)- The subgroup of the ICAVP 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' subgroup of the ICAVP Verification Team responsible for the review of the operating, maintenance and testing procedures, and training materials for the systems 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 in the scope of the ICAVP.
l 3.5 Configuration Review Group (CRG)- The subgroup of the SRG Mication Team responsible for walkdowns to verify the current as built conditions are in conformance with the design output documents, t
3.6 Programmatic Review Group (PRG)- The subgroup of the ICAVP Verification 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),
design basis and/or regulatory requirements.
Page 3 of 11 j l
o
-PROJECT INSTRUCTION PI-MP3 INSTRUCTION. .- REV.5..
l~
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-h accordance with the instructions contained in this project instruction.
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.
Responsible for resolving comments
-with the Verification Group Lead and the Initiator.
Responsible for overall control of DR process including maintenance of DR log, trending data and extemal distributions.
4.4 IRC Members / Chairman -
Responsible for reviewing all DRs
- initiated by the Verification Team, for reviewing dispositions of proposed NU resolutions to Level 1,2 and 3 DRs, and for resolving any comments ,
- with the Verification Team.
Page 4 of 11 l
i PROJECT INSTRUCTION PI-MP3 INSTRUCTION REV.5 l 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 swpe 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 concerns 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 cub-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 Tean,s 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 11 l
PROJECT-- INSTRUCTION PI-MP3 '
-lNSTRUCTION REV,S l Ngig: 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:
N213: The fields listed below which are indicated with an asterisk have pulldown menus. Applicable entries in these menus are listed in Attachment 6.6.
~
L SgLd 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.
Discrepanc, 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.
NRC Significance Enter applicable NRC significance level Level from Attachment 6.8.
Page 6 of 11 l
~
PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION REV.5 l Initiator Enter your name; Last name first followed by first and middle initials (i.e. Doe, J. A.) .
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.
l 5.2.3.2 If the VT Lead does not concur with the DR, the VT Lead shall L 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. l 5.2.3.4 If the VT Leed 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 Opi_nions 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 shwil 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.
N_g.lg The reviews associated with Subsections 5.2.3 and 5.2.4 can be concurrent in a group session.
Page 7 of 11 l
~
PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION - REV 5 l 5.2.5 The IRC shall review the DR The review process shall be consisten{
with the instruction contained in Subsections 5.2.3.1 through 5.2.3.5 3 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 instrucuon.
5.3 DR Resolution and Closure 5.3.1 Proposed resolutions submitted by NU shal' be reviewed in a manner similar to the DR initiation process described in Subsection 5.2 of this project instruction except that NU resolutions to Level 4 DRs are not I required to be reviewed by the IRC. Level 1,2, and 3 DR resolutions
] must be reviewed by the IRC. The DR proposed resolution shall first be reviewed by the Verification Team and then the IRC (where applicable). Concurrent review by VT members, Leads, and Manager are permitted. The proposed NU DR resolution shall be posted on the internet in accordance with section 5.5.
5.3.2 The initiator shall electronically transfer the proposed NU resolution on the "NU Resolution Screen", Attachment 6.4. Concurrence by the VT members shall be indicated on the screen, Attachment 6.4. After review of the proposed NU resolution the initiator shall indicate the nature of the DR status by highlighting "yes" or "no" to the following questions:
. Previously identified by NU?
(NU has documented where the discrepancy was previously identified).
. Non-Discrepant Condition?
(NU has provided additional information which establishes the acceptability of the condition)
. Resolution Pending?
(NU has proposed to comphte corrective actions prior to restart to resolve the discrepancy - for significance level 3 or above. S&L finds the planned corrective action acceptable, but needs to review the completed actions).
Page 8 of 11 l
J PROJECTL INSTRUCTION PI-MP3 INSTRUCTION .. REV.5 l;
-e' Resolution Unresolved?
(After NU's second response, all or part of the response is determined not to be acceptable)
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?
]
E proposed resolution, the non-concurring party shall document their justification for not accepting the resolution on the "S&L Comment -
Screen", Attachment 6.5 and obtain' concurrence on the " Resolution -
Screen" from other members in accordance with Subsection 5.3.1, j Resolutions not accepted 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-comments shall be reprocessed in accordance with Subsection 5.3.1 4 through 5.3.3. Only one additional resolution cycle per discrepancy is
. anticipated.
- i. .
., 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 concem, then the provisions of PI-MP3-10 for differing
- professional opinions DPO may be invoked.
5.4 DR Loa and Trendina Data 5.4.1 : DR Log 5.4.1.1 The DR database shall automatically assign DR Nosc status and
- revision. ' Hardcopy logs'can be generated from the database.
5A.2 Trending Data 5.4.2.1 The DR database can be sorted by the entries on Attachment 6.6 to i generate trend reports.
I 5.5 DR Distribution 5.5.1 Initial Issues
[ -
Page 9 of 11 l l
. =. _- - _ _ _ - . _ _ -.-_ -
PROJECT
- "~ INSTRUCTION PI-MP3-11 INSTRUCTION REV. 5 l l
- 5.51.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 and NEAC shall be in the form of hardcopies. Distribution to NU shall be in the form of electronic mall and hardcopy. Distribution to tha public shall be via the electronic bulletin board. Posting of the DR's on the electronic bulletin board will be approximately 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 be by electronic media with database security provisions, signatures shall not be required.
5.5.1.2 The VT Manager will fax DRs which may pose potential operability concern to the NU Poir.1 Of Contact identified in PI-MP3-01. The date sent shall be entered on the Discrepancy Screen.
5.5.2 Proposed Resolutions 5.5.2.1 The VT Manager shall distribute DR resolutions to the NRC, NEAC, l NU and the Public in accordance with Subsection 3.4 of PI-MP3-01.
Hardcopies shall be sent to the NRC, NEAC, and NU. NU shall also be sent electronic copies.
5.5.2.2 The VI' Manager shall post DR resolutions submitted by NU on the electronic bulletin board upon receipt and entry into the database.
5.5.2.3 The VT Manager shall distribute S&L comments on the proposed resolutions to the NRC, NEAC, and NU, in accordance with Subsection 3.4 of PI-MP3-01. DR interaction between NU and the VT shall be posted on the electronic bulletin board.
6.0 ATTACHMENTS 6.1 Process Flowchart, Processing Findings & Resolutions (1 page).
6.2 Sample Discrepancy Screen (1 page).
6.3 Sample Invalid Screen (1 page).
6.4 Sample Resolution Screen (1 page).
6 6.5 Sample Comment Sheet (1 page)
Page 10 of 11 l
" " ' INSTRUCTION PI-MP3-11 PROJECT-INSTRUCTION REV.5 l 6.6 Summary of Available Entries for Pulldown Menus (2 pages) l 6.7 Criteria for Operability Determination (1 page).
I 6.8 Criteria for Categorizing the Relative Significance of Discrepancies identified by the ICAVP.
Nqta: Att9chments 6.2 through 6.4 are sample illustrations of the DR Access Database data entry screens. This instruction will be revbed if the data fields are revised. Revision to this instruction is not required for format changes to the data entry screens.
- l. .
Page 11 of 11 l
}
PROCESSING FINDINGS l iname o,.croponer i coneu, rim.u. w. s AND RESOLUTIONS --
- R** art fDR) * ,ng,g Attachment s.1 g
d .
I tuso,, Revow DR m asemeea VT Memt I
w
_ _ o DR voi,e A DR not m vena l t es Review DR I reo Reemus IRC l
l s OR Valid N m DR not Adeousse? '
Veiid v
Documord km for Yes Not Decramard
_ d W s,aima OR a NRC/NEAC/NU & Post ,
en ri.eien,uc an VT Manager
, Provies OR Rooponse l to S&L D NU j
- Revow N Roopons , ,
i for Aeoguecy & poet oni Electronec BB VT/VT Mgmt l-lWdment Reasono for l e
, inoceouste/Submn to I. Review NV Response t
, NU/NRC/NEAC & Post l 4 VT Acceptance / t i
nn rincirneue RA '
Commerits' i L..
d{95 .3 IRG l *For Level 1. 3. Cnd 3 NU opg engy, No - Response to DR ooguete Yet Document Acceptance '
& Submt to NRC/NEAC/NV &
Post on Electrone BB '
L N "'" _.
- hu sieno l pep n
PI MP311, REV. 5 Attachment 6.2
!L Elle Edit Ylew Becords Window fielp FWin (nnnsrajiisirey; #ikssiiuMf InnaiM itLGRussE 1
o*n$4 ns*WtL ? gps . hQ"QQS ~ 3.z b::.sg '
' T
- f. _ .m ^^^
1:'t 1 x g
J%efn. ' - -3
- =
MWWT@nhp =*w+wS****mm -
- i..
,:es.:
6:6 xy%yNw e g.
3 :
^fp.
u, vies .s:xem, hg%<sConectrv,e y s,pa o,, ~a, .
_ Ad,m Processmm y mua w.u g<sw
,'t .
A M**
R
. pm.u ,L ~g $m E
. sm: . . . !
.j
,. e m . ,.w ElectricalDesgn ;fatential@m gl ti MD' == = ""'"""~ *'~"" *3 ). -- g is l
L fiGpasal4)$ a)g@yy%n
, hmopency .4$$M n. - **n=n"w Cah a m _ Jye $g%
r>> sew $s&s:issuris79 Rw; kj e"~w'""'"'w'*w"%
- N asa n 3
- . h L VissEsWFfsEstaenssisi .
II : k bW % i u==== =
- sygg~g 'M'?g] Sample.=mwmsuuemamu; -
Doaopancy Report mum =umuuaumawwmu Descrphan of Sample Omaopancy Repd i
o
%". QT g
'- \\\A =
tw H F_vilidp9m.s_ .o ne wand a %mPm_evie.ww_medsifEN ,
1/1s/1998 3 3 ..v. S n qpe M_ilneee ie.
-a m .. ___ t -
f hhf k N:Y .g.'..)+, :.k.N:YLN Y$.k'hk YEhhh f.
%i wi Jani4KnannmansriWaq d.dke
, .y
%1r&vi'tud.e.6
- 7 mmc tMeimiGR k 1, L.,wi H[MiidWs!dinisiMWJAndikedwiMSI
- s sammeg. 9:.s3 m m pan m n% w w w*m n - - ~ -
xy 'a'. Wyt ..
! wdlwmyNN$:phpMQtMis$k'$tMBdQ'"MMihdk6'litM"'
Is: Midsv o' 'w:W;ns:;i:!s:s _ :
-,i $:L :.0 itDb %;pifag'( % c- ,.u.,
's qp# ,3. vslas w: es esismi sM.s s
> s
PI MP311, REV. 5 4
Attachmont 6.3
% Elle EdM Ylew Becords %%dow licip D- :e .. .
DR MP3 0643 4
..,,:. . . - . , < . _ , . . , . . < . . . -- c .: :....s .__..e b +
't 4i . EMNd@eT M45 if 1/is/&mdyr@matmRNy#M1M;;;pMMegTN%m Mrsip .
! .seest mwy n a- w *de # *
- h*t *: M *^ M ' "' r " " 4 ? M
' ' "t, '
M R
" p'f h%d%a:
.E
- [ As.pv s.n,* %=on #w ruu mmwey l !k,,
t p .s -
'p[
i j o>. +
^
."' ih/d'
%F .,
>s em r
N, -
'+4 %EnWDYS -
i; un nNQ'gfi n$y h '^f I2~~l'[559%5i&Mf55iF655YE?MtBYf!NN35{%W@CHEPANCYMmm, n nnns-, ekoff
"' RDhosspancpRedem/3 snw sfreusa - ~tablS ~ - - -
M!M-
@_l Record l1 31 IMMi iMistl%ienikJm414.htgi&{iingsggidEGB$fSlisk33Ri% IRS 3EEpstampmRJMER 4
5
PI MP311, REV. 5 Attachment 6.4 i = 1 Elle Edit l*
DR-MP3-0001 m m - ., -x m.
_.m ginvalidt jtRe, s.o.lu,ti,on. ,SEcomment b_ExitM [ Diacr, epa,nc,y, +
% gwo< < >
m pw gm "
m%+1_g) a q@m@%
h m
s:y 3
,.:.- _ , ;;p , , m,wan.n m -
bif 4 Ho: LDH MP3
-o 4 0001-
~
y+ M HRC <-
Signilicance g ,,.m >
250 o - keve4PP s.m4 ;- r
.e D
[
,h iT
(-
,h.
rs . .o
', Ig" '
J 0 ate Ode'ied:d.u/13/1%7 10 m - ~j3m.= L < ve , - mme. ma 7odle%m 4, ,
yr m m m.#-+ a 5NU .Reenisdiure; . Dispositiorr p 4
acy ?n item 1:T he Station QuaWied Reviewer (50R) Progrem has been implemented in accordance with 9
,@?@@T
'3K ,
- ,4 3 Technical Specificaten 6.5.4.2. Speciication 6.5.4.5 dvects that temporary revishn to procedures for E-N wlhh Quakfied Reviewers ate assigned be orocessed in accordance with Specification 6.5.4.2 in lieu s l R M NMiM QWg%g of Specification 6.0 3. Specdication 6.5.3.2.e provide
- for approval by the Responsible Manager for j M g M Q C 11 the functional oroup responsble for ieview of the technical content of the spectic procedure. The MMMfQ@$ " Rstatement " Station QuaWied Reviewer Program Menager"in S pectication 6.8.3.c is the same s(
Qp$m&a M(pWM q
A %m +
y esponible Manager" mentioned in Specification 6.5.42 e. h p.
m A n;g,f pu 3:aip ny..Ng mrneta m r-m-sm , e m ow-mte m s pres NyIWd w v .-
PW Peeviously ident#iod bp NU 7MYes 4 Ho t'p W Nori4isciepard Ce%?5 6E d d sWBW' $7""yyHoEbidon
$ e ar.wmsm : Per w ding ua S6f +7QNdi@[gy-s .a.m w na 'TTIRE,ostios 7$NA q Uh:
(_p[$@%7 g j $. y N '* C m wagMWsIW1ENU_'SfrO6(EEnMM._,
._ s Mc .
~MqMg M ) NM, M ri>nitistos she aid R ' *
- GoceptandeR,) lot A_oceptable f")~emewMoo4mdiq l yDa. 10A3/1M7 4 R QiEyyij$sh:i span inorna.J N (( Accep'ablegNot t AecsptabledRevieh NeededMDM 10n3/1n7lN BNT Nagw.: san e DonL
- 10A6/1W7 !6 diRC CNeirman:h Seigh AnandL M gy w : nmn;J l(mgy C hsse6(abler No[Accesable dhafisw"Ns Ahenpjable(NotXsceptableOHeyisw NaisdsilM m ng, m ,
' - - > 2 pqygg lon7nny e Hl4_jRecordil lol 577 l >lHj q _ . , _ ,, ,m_ mm ~, .,,,s..,
Y $$.. ;-.-..,...........-,.... -hk - n hh . ~
m,, .4._ , -,, s. _
Zie $ $ Y O&ssk 9dkN ses$%k$ i $t k . .Y. .
Pl MP311, REV. 5 Attachment 6.5 g M[Ile31( AVP Ipcvelopmesit - lIliv irene. y Heportl Edit ylew Beceeds Y$ndow tielp E3 m ,,
s e o see Dn u n coot s-REishM Olsetepensp MwsilW2 *%Iles W!Camaiset nN %na4?gm42ry 4 -' +uwh " ' == .
1Q/)y)27 a= w ~ . ; a ,id;3NN:
ii nW. mM, .. V eAik _ . . . _ , mw
- 1. T he ee.ouen d pet 2 d the dactspancy a artsstaben.
1 1he changes to pecadse DC 1 stanng that the Depetmord Heads my imdam as SQRP Wanages me access edej 3 No changne se popoewi to pmayaph 1.E 3 a 4 d pocedee DC 1. DC 1 rende to rened the appicatie pocedse amovahoosenents n iedrocal SpecFcatane 6.51.7.a. E 517.a.
" E5.4.le and 6 B3 c. T hus, the dontFed decrepacy romans stresdved dm ja 4.1he weponse &ws nd aMess the o.aent of condhon as fotows:
e i
"" a Heve these towwy.nornw d - as,wa wee semed tv 0ualled Revwwers.been approved by pusurmi whose twai/caan.s noot that of 4 SQRP Manages,t e., do the Respanebio i IrwMbaie demased n pengaph1.E3.a.4 of DC 1 mpe omifcahone of the maiagunent pueban?
h 11 past changes hwe ed been poosseed h mocardance enth iochr 4 Stealcabane E 5.1.7.a.
l NtWW B! E 517.a. 6 5 4.2. E 5 4 5 ed 6 Eio. what coriedwa acton is poposed? Do av past tenemey l ' . gygg% danges need aMtonal appovak bdore elske?
nas -
acer
PI-MP311, Rev. 2 l O- Attachmen'. 0.7 CRITERIA FOR POTENTIAL OPERABILITY ISSUE The following criteria shall be used to determine if a DR poses potential operability issue:
Note: Potential Operability issues apply only to those systems that are required to be operable in the current mode of the Unit (Mode 5 or 6 as defined in Table 1.2 of the Technical Specifications).
- 1. Any departure from tne 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.
- 3. Failure to meet the provisions of the Technical Requirements Manual.
^
- 4. C nditions resulting in a Maintenance Rule Functional Fallure (MRFF)
(~)' (10CFR50.65).
l
- 5. Any occurrence that appears to jeopardize radiological protection, or may be a violation of a program, procedure or regulation with radiological implications.
l (v3
PI MP311, REV 4
,,, Attachment 6.8
- CRITERIA FOR CATEGOR17.fMG THE REIATIVE SIGNIFICANCE OF DISCREPANCIES IDENTIFIED BY THE ICAVP 1
- SIGNIFICANCE LEVEL 1 A discrepancy (') that identi6es that the system does not meeting its licensing and design bases and cannot perform its intended function, i.e., has the potential to simultaneously affect redundant trains.
- SiONIFICANCE LEVEL 2 A discrepancy ") that identi6es that a single train of a redundant system does not meet its licensing and design bases and that the tr4n rannot perform its intended function.
4
- SIGNIFICANCE LEVEL 3 A discrepancy ") that identines that a system does not meet its licensing and design i bases but the system is capable of performing its intended function.
- SIGNIFICANCE LEVEL 4 A discrepancy (') that identifies that a systems meets its liasing and design bases, however, there exists minor errors such as minor arithmetic errors that do not significantly aff~ect the resuhs of a calculation or inconsistencies betww.
documents of an editorial nature.
NOTE (1) A discrepancy may identify programmatic, procedural, or design issues or editorial inconsistencies.
O
PI MP3 011 Rev. 5
- Attachment 6.6 Page 1 of 2
SUMMARY
OF AVAll,ABl,E ENTRIES FOR Pt1LLDOWN MENT 1S fjELD ENTRIES Review Group CRG ORG PRG SRG ARG Review Element System Design Modification Design System Installation Modification Installation Operating Procedures Test Procedure Maintenance Procedure Training Procedure Change Process Corrective Action Process Discipline Mechanical Design Electrical Design 1&C Design Structural Design Piping Design Equipment Qualification Operations Maintenance Training Other Discrepancy T),. Drawing Component Data Calculation Licensing Document Test Requirements .
Test implementation Installation Requirements Installation Implementation O&M&T Procedure O&M&T 1mplementation Corrective Action Corrective Actionimplementation Procedure implementation l Design Control Procedure 1
+ . _ _ _ .
m.__.__. . . - _ . _ . _ . _ _ .__ _ _ _ _ ...___ _ _ _ _ _ .._. _ _.. _ _ _ . _ -
PleMP3 011, Rev.' 5 .
Attachment 6.6 Page 2 of 2 l System / Process DGX l HVX N/A NEW '
, QSS RSS SWP Potential Operability issue Yes >
.No:
I y
Y k
Y I
?
!