ML20210U417

From kanterella
Jump to navigation Jump to search
Rev 4 to PI-MP3-11, Discrepancy Rept Submittal & Closure
ML20210U417
Person / Time
Site: Millstone Dominion icon.png
Issue date: 09/16/1997
From: Bass K, Neri A, Tom Ryan
SARGENT & LUNDY, INC.
To:
Shared Package
ML20210U355 List:
References
PI-MP3-11, NUDOCS 9709190149
Download: ML20210U417 (18)
v • d • e


Text

_ . _ _ _ - _ . _ - . - - ,

PROJECT INSTRUCTION *f*"' -

INSTRUCTION PI-MP3-11 REV. 4 l CCnt: Northeast Utilities Station: Millstone Unit 3

Title:

DISCREPANCY REPORT SUBMITTAL AND CLOSURE l _

h Safety Related _

Non-Safety Related Reviewed By: Approved By:

System Lead Programmatic O&M Lead Accident QA Engineer internal Review Verification Team Lead Mitigation Committee Manager Lead Chairman

, / , Date: i*$*

dbdk 44 d - 6 7A = fidfkkx /nLLA:AM-sk WMG

~

Description vv (' oo ,.

R;v. 4 Revised PI to add requirements for:

l

. NRC SigniScance lerl e Distnbion of Proposed NU Resolutions Page 1 of 10 9709190149 970917 PDR ADOCK 05000423 P PDR

. - - - . . ~ _ ._ ._ _ . - -

PROJECT

~

INSTRUCTION PI-MP3-11 INSTRUCTION REV, 4 l

1.0 PURPOSE 4

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 instruction addresses the preparation of DRs by the ICAVP team, the review of proposed resolutions developed by Northeast Utilities and the trending of 4

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 V 2.4 PI-MP3-03, Review of Plant Modifications Prepared After Receipt of Operating License for Technical Adequacy and for Configuration Control.

2.5 Pi-MP3-04, Programmatic Reviews 4

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 4

2.10 PI-MP3-12, Project File Index 5

Page 2 of 10

t i

~* 6 Y PROJECT ""

INSTRUCTION PI-MP3-11 INSTRUCTION REV. 4 l 3.0 DEFINITIONS 3.1 Accident Mitigation Review Group (ARG) - The subgroup of the ICAVP ,

Verification Team responsible for review of critical characteristics of 1 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.

l 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.

i 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.

3.5 Configuration Review Group (CRG)-The subgroup of the SRG Verification Team responsible for walkdowns to verify the current as

built conditions are in conformance with the design output documents.

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 documentina the discrepant conditions identified by the ICAVP and reportin3 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 10

PROJECT

~

~ 4 ""' INSTRUCTION PI-MP3-11 INSTRUCTION REV. 4 l 4

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 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 Initi.itor, 4

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 external distributions.

4 4.4 IRC Members / Chairman -

Responsible for reviewing DRs and

, dispositions of proposed NU resolutions prepared by the Verification Team and for resolving any comments with the Verification Team.

f))

Page 4 of 10

PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION - REV. 4 l 5.0 PROCEDURE 1he 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 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:

O b.

- oa i"iti tie" 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 databese.

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.

O Page 5 of 10

i k

  • fM"'
PROJECT INSTRUCTION PI MP3-11 INSTRUCTION - REV. 4 l N_qtg 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 eeded
from NU shall be requested per PI-MP3-01.

l

5.2.2 The Initiator shall prepare the Discrepancy Report by entering the following data into the database's " Discrepancy Screen", Attachment 6.2

Note: 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 f3 Review Element
  • Enter Applicable Review Element b Discipline
  • Enter Applicable Organization Discrepancy Type
  • Enter Applicable Discrepr=ncy Type Potential Operability
  • Enter whether the Discrepancy is a j issue Potential Operability Issue using the guidance in Attachment 6.7 i

System / Process Enter by Full Name the system or process being reviewed.

Discrepancy Enter brief title Description Enter detailed description of condition i

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.

'O Page 6 of 10 l

4 i '.

PROJECT INSTRUCTION PI-MP3-11 INSTRUCTION .- REV.-4 l Initiator Enter your name; Last name first followed

[ by first and middle initials (i.e. Doe, J. A.)

l j Date Enter preparation date I

The database will automatically assign DR Nos., revision i level and status.

) 5.2.3 The VT Lead shall review the initial DR draft.

I i 5.2.3.1 if the VT Lead has comments on the DR or determines that additional j information is needed, the VT Lead shall resolve the comments with j the initiator.

! 5.2.3.2 If the VT Lead does not concur with the DR, the VT Lead shall j complete the " Invalid Screen', Attachment 6.3, by entering his name, i date and justification for the invalid disposition. The VT Lead shall

! review the invalid disposition with the initiator.

lO 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 j 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 l related to the DR, the provisions of PI-MP3-10 for Differing l Professional Opinions may be invoked.

t l 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.

i

! 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 I through 5.2.3.5 above, except that any comments or invalid

dispositions shall be reviewed with both the Initiator and the VT Lead.

Ngjr The reviews associated with Subsections 5.2.3 and 5.2.4 l can be concurrent in a group session.

!O l

i Page 7 of 10 i

g(

PROJECT INSTRUCTION

  • pF"' s INSTRUCTION PI-MP3-11 REV. 4 l l

5.2.5 The IRC shall review the DR. The review process shall be consistent 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.

4 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. The proposed NU DR resolution shall be posted on the internet in accordance with section 5.5.

V 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. 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 e justification 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 l'

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 IF.C) cannot reach agreement p on acceptance of the proposed NU resuutions and anyone has a V

Page 8 of 10 l

ik PROJECT INSTRUCTION

  • p *" INSTRUCTION PI-MP3-11 REV, 4 l

)

safety concem, then the provisions of Pl-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 Nos, status and revision. Hardcopy logs can be generateo from the database.

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.

1

5.5 DR Distribution 5.5.1 initial Issues f 5.5.1.1 The VT Manager shall distributo DRs to the NRC, NEAC, NU and the Public per Subsection 3.3 of Pl-MP3-01. Distribution to the NRC, NEAC, and NU shall be in the form of hardcapies. Distribution to the public shall be via the electronic bulletin board. Posting of the DR's on the electronic bu'letin 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 NUINRCINEAC. 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 Point Of Contact identified in PI-MP3-01. The date

sent shall be entered on the Discrepancy Screen.

1 O

j Page 9 of 10 l

PROJECT INSTRUCTION "fi -

INSTRUCTION PI-MP3-11 REV.4 l 5.5.2 Proposed Resolutions 5.5.2.1 The VT Manager shall distribute accepted (closed) DRs to the NRC, 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.

5.5.2.2 The VT 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 l resolutions to the NRC, NEAC, and NU only, in accordance with Subsection 3.4 of PI-MP3-01. Posting of DR Interaction between NU and the VT on the electronic bulletin board is not required since the hardcopy transmittal to the NRC will be public record.

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.5 Sample Comment Sheet (1 page) l 6.6 Summary of Available Entries for Pulldown Menus (1 page) 6.7 Criteria for Operability Determination (1 page).

6.8 Criteria for Categorizing the Relative Significance of Discrepancies l

Identified by the ICAVP.

I Note: 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.

4 l

Page 10 of 10 l

PROCESSING FINDINGS ininow D crepency Pl* "

  • 8 concur AND RESOLUTIONS  : R"a fDR) mg Attechment s.1 g

d m Review DR re Raund VT Mgmt

, o DR Vend & DR not m vana Nawme Rev6ew OR Hb Ragsud IRC 6 DR Velid & DR not Adequate? Vand v

. Document Besie for Yes Not Decrecent d VT m DR to i

SRC/NEAC/NU & Post ,

% on Fbw4ranac RB f1 h

VT Manager J

Pnmde DR Reeponse to S&L NU v

4 Revww NU Resoonee for Adequecy & poet on Electronic BB VTNT Mgmt Document Reasono for e inedequate/ Submit to Revww NU Response i

NU/NRC/NEAC & Post & VT Acceptence/

, nr.F h an m VT Mgmt iRg a

NU Nc - Response to DR uste Yee

.I T Document Acceptance

& Submd to NRC/NEAC/NU &

Post on Electronse B0 VT Mgmt

[

e mw3,ma,nu.w,.w1,41ami

~,s m ~ base il

1

-. \

1 4

!(

)

4 PI-MP311, Rev. 4 i

Attachment 6.2

. .; %Ilstone 3 K AVI' t)rvelopinent [l)iuseposity Iteport) -

G "l 2

. EElr W 0ll E r m aT.Flii W uiT3 M ifl  !!

New Discrepancy Report I..-

F m. . m ., l,' .m.., ~ '

.m -; ,.m...,4

~

.- ~ m h. ... . r. ..

I h $u , ma -4 . _ m > .. . , . , , a .w ., u .s ._. J

,. ... . . . . . ~

. m.

, . . . . . . - .: u :. .

, ,, a . . .c , .,n. w.~ . . . w;w. .w . c .

. m . . .

~ ; .i , . '. (. k., -' *

.. A .].

.[ ' . . .

~ . .~ . a, i

3 n .E w.

,. t.m; ;,w, %#mmw m .

m .4 ', y . c %. m -

1

. . , ~

,%e . . ';: l

. gr_=y..

~*.,.' 4*

, a+-. .

- 8 -sw ,,

l

. .. f.

k' ..A p. fi ,.~ so n"/ g '

3- e..u . ; .

. ;. L. . , , . . . . .

c..

6.

.,,p M* , . . , . y q. g, 4,! y{i'j/(, p,;t'( ' y -

,.s.

i . . . . .t', , g 7 u 1.  %'3 , ' , '

. . 't. W ; [ 3..

$wk;.j;cf; j. .Q j..QMg i.R w s.y 7 e 7: $ ..r.

j 4g y g: ;.g p..q, r - . 3

.. , s ,

' Ve&g ' w , s+;,.B, iia #@

. .g.: genw. mg , 9 J's yi 9

7;- ;; . 3.; ym; y , .

. .. ,y,

(

i . . . , .

M :r

... 7 -

a..b .. . . _ . . . a. s . . _

49f! M Y.

umn.:.

' %M Of5't rn"' .' !

n a rfa a .t.L.a.u.a.. m i . >

_ . . . . . . . . . _ . . . . . _ . . . . . . . . . . . . . - . . . . . . . . _ . . . . ~ . . . . . - . . , . . . . . . . . . . .

.  % . . s

, J:

.T 4

'.... wc ., .

g y

.g ;

9 .

wc . .,

,. F i i I . .. b

. , } ,[ 'M 5- ' -

-. ] 7, .

, ,)..p

?. ' #  ! # *: '

( },yl,. ff .

_l ' , . ,.

'V' .

'~

q

e; . ,; y fx.ja.@

t r , t 3 1, - . I . , ...

y; ...f 4 , .

p ~~

,g .@m 7

..,g 9 :. . c.

wy p,

j , en fr ph i ' i, , e i ... ; ;w u. <.

- n. u,

, ,.  : -- 1;p i w . . %,n.

. ,*~

u ,, , ~( .,,.,,.,3, r .w u. . . , y

.s.. . . , ,

. , ; . . G.wy

='

x;pMQ.gg c; y c r-...

pQ9g qhm p  ;; w ;- n. +

.. , .: s'n

g;;;lgeg 9 a.y k v.m y em.g;& . m x__ -

' . @d%@y%W ,

Q [.3 ; .Q: i - gg '

ihy @ . . . .tn

. :ww.Ey;.'y":iqyggas vg pg7 :gg q ' y ye g;q s i

i 4

I e

9 i

PI MP3-11, Rev. 4 Attachment 6.3 1

Elle Edit Ylew Becords Window ticip {

DH-NP3-0009 l lDintep ' glifwildg

i'A00estihiiant m au mu,-

m e ewanrm. ,.

c . m- .

wn.gbox,am.y mww sma mem m w.x.:cm.m.,

m ag g_-

S 7 M.wh;p"5 wka M ,# ,u 2M %r#E u%naan m :0 ns

,.a N i1 W M A.,12s*u fife x.naam , A'sI ma spijMjmWls ' C!iiLg'b?.0H99tR $ F@y::g? r@G. N.. MRP:P% 3:P_J'F"4M?FT9" " :yF ~

4

.u ..

  • i. >M M_ > - won,~

swie justicaton for invand dierepecy

a pp. a,

'E'

(.- _

w - -

NIi

  • ) $

a -

$ -i S

5 t?

.1

i w- 8

., L . .

i

!I D

wagem===am ga_l*<g%[r$mmumgewramaemwsps;;

p(El e M Disiempiwsp'Beiv,iew Chegke,N gam @eihiinues'DISCREPADIC%p" u.nyucyg em gy n . y wweyyymgnumme y .

_M111 Record 1 loi 1 ItlMI yw--,, .

.__~y yng,yym;g,n;,g;gg m mm

- % . __ AsME2M &tadthka@ehnsM M MDsess.g diMIg g A TR h,m ,lus,;in n i m,L W.gs T,.aa 3 w

l PI-MP3-11, Rev. 4 Attachment 6.4 l

le Edit Ylew Becords Window lielp  :

DR-NP3-0007 i g*gry *

gg - rg4 M h%~ '

BR MI l(iD.R,NP3 j

w- 0007 j gg kh gh g..p gg p, g g g ggg# -

. 4 b

up --@.f

.:me- 2M g. vjm; -..mmw..jQ,jgj;fgjggjpg..

m m _?_ - .~.J ,ggfjjgjg . _ - _ . . _ . - . . ._ iJg .~. . . ~ .=

~T S&Tese Resoluton Descrption m

Y00 is su b

L E

k cJN 'E*"VQW rtts t iM1 M w 'h 1MG Ru?d d%Ws3P Ne's'A RM5N%WWE"desTeh@i5 gmmxme%ws -

re a,p,mgsam m ,,wma ca a,s.%emem.reml

-*%ue Jd ym~,my. m

,mA__ _ -

E .-- .WN!TS - elf '

g- mE-s wm:rane~ vaca.m u.a.d-n adjs/12/iss7 mw

.. ww enne ~ ~c ~~

$>H ( '" V ..

g4 gg.;  :, my, ~ ., , ,

s . . . ~ oay Ir;housigew g*ensismus.gsim oighg m'

-s . . . - -

P~" ^~r ~ "used e s ~

-_ 1a mm_atunn,n%!4sn,WM_g s na _ma=nlays,

- a n m W%a,am,:nn- a wc, 1 flRecord 1 of 2 l+DH m;u_,,mumnp.mpeggggggggeyggg;ggggggggggg gggg ggg

\

4 PI-MP3-11, Rev. 4

J Attachment 6.5 i

N E ll j' ile Edit Ylew Becords Window Help i

i DFI44P3-0007

~-

<:y; :,.-i aos x .. .

u2 .. wiE % u .

I_  ! I. %k fMi i m  :

i f?0??hh$$$iN!&!ENhkh5bb5hb hkY jf Sample AejectonJustlication nm=  ::

i 1

, 'i nos

> ra.

\

a i

l;  ?

t

!  ?

f 1

I l

0 hh 4w 1

~~

- . - . _ _ -3p2EmiMEWlP4WNRM5m? 5N9 he n $egd$ilgs!0 Tom Secolution Boww4 wwwywsweesramm;esawspw sow Chec iot

$me!5Fhops.75SEmiFuMMm*N!

urn to RESOLUT1001M,,gggg mauwee e segg;gpg  ;

,.y m%

Record 1 of 2 F

7 ??py e

,g gggggg gr g j l

l

i I: PI.MP3-Oll, Rev.1 i$ Attachment 6.6

. l

}

i

SUMMARY

OF AVATI.ABLE ENTRIM FOR PIII T.nOWN MENUS 3

BELR ENTRIES I Review Group CRG 4

ORG

PRG SRG ARG j Review Element System Design 3

Modi 6 cation Daign System Installation i

ModificationInstallation l

IOg UIOS i Test Procedure J

Maintenance Procedure Training Procedure Change Process 4 Corrective Action Process Disciphne

j. MechanicalDesign Electrical Design IAC Design i

Structural Design li Piping Design i

Equipment Qualification Operations i

i Maintenance 4

Training 1

Discrepancy Type Drawing

Component Data Calculation i

Licensing Document i

Test Requirements Installation Requirements

[

Ia*=% don Implementation i

f O&M&T Procedure

! O&M&T Implementation Corrective Action Procedure Implementation Change Process Potential Operability Issue Yes No

t j

4 PI-MP3-11, Rev. 2 l Attachment 6.7 i

CRITERIA FOR POTENTIAL OPERABILITY ISSUE l 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 cunent mode of the Unit (Mode 5 or 6 as defined in Table 1.2 of the Technical Specifications).

! 1. Any departure from the conditions of the operating license, Technical i

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, iO V
4. Conditions resulting in a Maintenance Rule Funt,tional Failure (MRFF)

(10CFR50.65),

5. Any occurrence that appears to jeopardize radiological protcetion, or may be a 4

violation of a program, procedure or regulation with radiological implications, j

l

PI MP3-11, REV. 4 Attachment 6.8 CRITERIA POR CATEGORIZING THE RELATIVE SIGNIFICANCE OF DISCREPANCIES IDENTIFIED BY THE ICAVP

  • SIGNIFICANCE LEVEL 1 A discrepancy <ut hat identifies 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.

l

  • SIGNIFICANCE LEVEL 2 A discrepancy (D that identifies that a single train of a redundant system does not meet its licensing and design bases and that the train cannot perform its intended function.

. SIGNIFICANCE LEVEL 3 A discrepancy (D that identifies that a system does not meet its licensing and design bases but the system is capable ofperforming its intended function.

  • SIGNIFICANCE LEVEL 4 A discrepancy (D that identifies that a systems meets its licensing and design bases, however, there exists minor errors such as minor arithmetic errors that do not signific mtly affect the results of a calculation or inconsistencies between documents of an editorial nature.

NOTE (1) A discrepancy may identify programmatic, procedural, or design issues or editorial inconsistencies.

O

Retrieved from "https://kanterella.com/w/index.php?title=ML20210U417&oldid=3306279"