ML17264A846: Difference between revisions

From kanterella
Jump to navigation Jump to search
Created page by program invented by StriderTol
Created page by program invented by StriderTol
Line 16: Line 16:


=Text=
=Text=
{{#Wiki_filter:CATEGORY, j.lj,REGULATINFORMATION DISTRIBUTION
{{#Wiki_filter:CATEGORY, j.lj, REGULAT INFORMATION DISTRIBUTION
~TEM(RIDS)ACCESSION NBR:9704020118 DOC.DATE:
~TEM (RIDS)ACCESSION NBR:9704020118 DOC.DATE: 96/05/14 NOTARIZED:
96/05/14NOTARIZED:
NO DOCKET FACIAL 50-244 Robert Emmet Ginna Nuclear Plant, Unit 1, Rochester G 05000244 AUTH.NAME'AUTHOR AFFILIATION MECREDY,R.C.'ochester Gas&Electric Corp.RECIP;NAME RECIPIENT AFFILIATION Region 1 (Post 820201)
NODOCKETFACIAL50-244RobertEmmetGinnaNuclearPlant,Unit1,Rochester G05000244AUTH.NAME'AUTHORAFFILIATION MECREDY,R.C.'ochester Gas&ElectricCorp.RECIP;NAME RECIPIENT AFFILIATION Region1(Post820201)


==SUBJECT:==
==SUBJECT:==
Discusses differences
Discusses differences
&documents utilpositionconcerning reportability ofmissedsgrveillances on960224ofTSaISTatGinnaStationperAmend61.'DISTRIBUTION CODE:IEOIDCOPIESRECEIVED:LTR
&documents util position concerning reportability of missed sgrveillances on 960224 of TS a IST at Ginna Station per Amend 61.'DISTRIBUTION CODE: IEOID COPIES RECEIVED:LTR
~ENCL0SIZE:TITLE:General(50Dkt)-Insp Rept/Notice ofViolation ResponseNOTES:License Expdateinaccordance with10CFR2;2.109(9/19/72).
~ENCL 0 SIZE: TITLE: General (50 Dkt)-Insp Rept/Notice of Violation Response NOTES:License Exp date in accordance with 10CFR2;2.109(9/19/72).
'AT05000244RECIPIENT IDCODE/NAME PDl-lPDINTERNAL:
'A T 05000244 RECIPIENT ID CODE/NAME PDl-l PD INTERNAL: AEOD/SPD/RAB DEDRO NRR/DISP/PIPB NRR/DRPM/PECB NUDOCS-ABSTRACT OGC/HDS3 COPIES LTTR ENCL 1 1 1 1 1 1 RECIPIENT ID CODE/NAME VISSING, G..BQihjCCZg FILE CEN FB NRR/DRPM/PERB OE DIR RGN1 FILE 01 COPIES LTTR ENCL EXTERNAL: LITCO BRYCE,J H 1 NRC PDR 1 NOAC NUDOCS FULLTEXT D NOTE TO ALL"RIDS" RECIPIENTS:
AEOD/SPD/RAB DEDRONRR/DISP/PIPB NRR/DRPM/PECB NUDOCS-ABSTRACT OGC/HDS3COPIESLTTRENCL111111RECIPIENT IDCODE/NAME VISSING,G..BQihjCCZg FILECENFBNRR/DRPM/PERB OEDIRRGN1FILE01COPIESLTTRENCLEXTERNAL:
PLEASE HELP US TO REDUCE WASTE.TO HAVE YOUR NAME OR ORGANIZATION REMOVED FROM DISTRIBUTION LISTS'OR REDUCE THE'UMBER OF COPIES RECEIVEDBY YOU OR YOUR ORGANIZATION, CONTACT THE DOCUMENT CONTROL DESK (DCD)ON EXTENSION 415-2083 TOTAL NUMBER OF COPIES REQUIRED: ITTR 18 ENCL N-R-27-1997 89: 15 FRON R.G.KE.DOCLNENT CONTROL TO 913814152182 P.82~~gQQNQKR GA$AIVD EIECNIC CORPORAL i S9 EASTMAN'/AVE, ROCHESlEIi'N Y.Qdl90(X((AREA CCOE7Id SC&27%ROBERT C.hLECQEOY Vri Pwu&ht Hadst Opetol'en'.S.
LITCOBRYCE,JH1NRCPDR1NOACNUDOCSFULLTEXTDNOTETOALL"RIDS"RECIPIENTS:
Nuc!car Regulatory Commission Region I 475 AUendale Road King of Prussia, PA 19406
PLEASEHELPUSTOREDUCEWASTE.TOHAVEYOURNAMEORORGANIZATION REMOVEDFROMDISTRIBUTION LISTS'ORREDUCETHE'UMBER OFCOPIESRECEIVEDBY YOUORYOURORGANIZATION, CONTACTTHEDOCUMENTCONTROLDESK(DCD)ONEXTENSION 415-2083TOTALNUMBEROFCOPIESREQUIRED:
ITTR18ENCL N-R-27-1997 89:15FRONR.G.KE.DOCLNENTCONTROLTO913814152182 P.82~~gQQNQKRGA$AIVDEIECNICCORPORALiS9EASTMAN'/AVE, ROCHESlEIi'N Y.Qdl90(X((
AREACCOE7IdSC&27%ROBERTC.hLECQEOYVriPwu&htHadstOpetol'en'.S.
Nuc!carRegulatory Commission RegionI475AUendaleRoadKingofPrussia,PA19406


==Subject:==
==Subject:==
May14,1996KHERRg~'RRReportability'of MissedTechnical Specification andInscaiccTestingSurvciHanccs Rochester.Gas kElectricCorporation R.E.GinnaNuclearPowerPlantDocketNo.50-244Gentlemen,'n Pebruary24,1996,RGB'mplemented theImprove'd StandardTechnical Specifications
May 14, 1996 KH ERR g~'RR Reportability'of Missed Technical Specification and Inscaicc Testing SurvciHanccs Rochester.Gas k Electric Corporation R.E.Ginna Nuclear Power Plant Docket No.50-244 Gentlemen,'n Pebruary 24, 1996, RGB'mplemented the Improve'd Standard Technical Specifications
{ISTS)atGinnaStationperAmendment No.61.Asarmltofthisconversion, anissuehasbeenraisedwitiiicspc<<ttot!icicpoitability ofiiiis~cdtccliu;vul spa;ifi<<ation audinscivico tating(IST)survciGanccs pcr'0CPR50.73.ThisissueisductothcfactthatpreviousNRCguidanceinthisarea(NUIT-1022) doesnotspecificaHy applytotheISTSinseveralareas.Thepurposeofthisletteristodiscussthesedifferences anddocumentRGkEspositionconcerninS reportabiiity ofthesemissedsurvcillanccs.
{ISTS)at Ginna Station per Amendment No.61.As a rmlt of this conversion, an issue has been raised witii icspc<<t to t!ic icpoitability of iiiis~cd tccliu;vul spa;ifi<<ation aud inscivico ta ting (IST)survciGanccs pcr'0 CPR 50.73.This issue is duc to thc fact that previous NRC guidance in this area (NUIT-1022) does not specificaHy apply to the ISTS in several areas.The purpose of this letter is to discuss these differences and document RGkEs position concerninS reportabiiity of these missed survcillanccs.
In1994,theNRCpublished ascconddraft,revision1toNUREG-1022.
In 1994, the NRC published asccond draft, revision 1 to NUREG-1022.
ThcpurposeofN"REG-1022wastoconsolidateNRC reporting guidelines withrespectto.10CFR50.72and50.73intoonedocumenttohelpachicvoconsistency vithia,thc'nuclear powerindustry.
Thc purpose of N"REG-1022 was to consolidateNRC reporting guidelines with respect to.10 CFR 50.72 and 50.73 into one document to help achicvo consistency vithia, thc'nuclear power industry.MJREG-10~M w(is developed using standard tcchnical specifications (STS)which preceded the ISTS.There are several differences between these two versions of technical spcciGcations which crcatc discrepancies when attempting to use the guidance of MJRECv-1022,.especially for the reportability nf missed techniiml.specifications and IST survei0ances.
MJREG-10~M w(isdeveloped usingstandardtcchnical specifications (STS)whichprecededtheISTS.Thereareseveraldifferences betweenthesetwoversionsoftechnical spcciGcations whichcrcatcdiscrepancies whenattempting tousetheguidanceofMJRECv-1022,.especially forthereportability nfmissedtechniiml
These differences are discussed in detail below.In STS, the relevant specifications in question are 4.0.1 and 4.0.3.These are resta>M below for discussion purposes: 4.0.1 SurvciHance Requirements shall be met during the OPEBATIONAI.
.specifications andISTsurvei0ances.
MODES.or'ther conditions specified for individual I.imiting Conditions for Qperauon unle:s otherwisc stated in an individual Surveillance Requirement,'7704020118 960514 PDR ADOCK 05000244 P~PDR t~.Q~'Q (o u2~
Thesedifferences arediscussed indetailbelow.InSTS,therelevantspecifications inquestionare4.0.1and4.0.3.Theseareresta>Mbelowfordiscussion purposes:
l%R-27-1997 89: 1S FP R.G.KE.DOCUMENT CONTROL$0~9139141S2182 P.83'1 4.0.3 Failure'to perform a Surveillance Requirement within the allowed surveillsni<
 
interval;de6ncd by SpeciQcation 4.0.2, shall constitute noncompliance with the OPERABILITY requiretnents for a Limitina Condition for Operation.
==4.0. 1SurvciHance==
The time limits of the ACTION requirements are applicable at the tiine it is identified that a SurvciUance Requirement has not been performed.
Requirements shallbemetduringtheOPEBATIONAI.
The ACTION requirements may be delayed for up to 24 hours to permit the compli.tion of the surveBIance when the allowable outage time limits of the ACTION requirements are less than 24 hours.SurvciHanco Requixcmcnts do iiot have tv bc performed or inopersblc equipment.
MODES.or'therconditions specified forindividual I.imiting Conditions forQperauonunle:sotherwisc statedinanindividual Surveillance Requirement,
In summary, pcr Specifications 4.0.1 and 4.0,3, if the surveiBance frequency,for a component is exceeded, the subject component mtist be declared inoperable and the limiting condition for'peration (LCO)entered;howcvcr, a delay period of up to 24 hours is provided before the associated ACTIONS must bc performed.
'7704020118 960514PDRADOCK05000244P~PDRt~.Q~'Q(ou2~
Kith respect to reportability, the bases for Specification 4.0.3 state that"the failure to perform a surveillancc~thin the provisions of Specification 4.0.2 is a violation of a Tcchnical SpccUicatioii
l%R-27-1997 89:1SFPR.G.KE.DOCUMENTCONTROL$0~9139141S2182 P.83'14.0.3Failure'toperformaSurveillance Requirement withintheallowedsurveillsni<
~requirement and is, therefore, a reportable event under the requirements of 10 CFR 50.73{a)(2)(i)(B) because itis a condition prohibited by the pla'nt's Technical Specifications."&HAG-1022 further expands on this by stating that a missed technical specification or TAT mirveillancc inust be reported when"enough time has elapsed that, as e result of the missed surveillance, a TS controlled system must bc dcchucd inopcrablc and thc LCO action suiiciiicut has been exceeded." That is, an LEE is required if the time period between the last test and thc test being performed is.greater than the speciGcd testing interval (multiplied by 1.25'per Specification'4.0.2) plus thc completion time for restoring the~R'ected component to operable status.Jn this instance, the aKectcd component may be inoperable for a longer period of tiinc than the STS would allow (i.e., the plant is in a condition.piohibitcd by technical specifications).
interval; de6ncdbySpeciQcation 4.0.2,shallconstitute noncompliance withtheOPERABILITY requiretnents foraLimitinaCondition forOperation.
ln ISTS, there arc significant differences from Specifications 4.0.I and.4.0.3.
ThetimelimitsoftheACTIONrequirements areapplicable atthetiineitisidentified thataSurvciUance Requirement hasnotbeenperformed.
The new versions of these Specifications arc rc8tatcd below from the Ginna Station tc"hnical, spccilicutions:
TheACTIONrequirements maybedelayedforupto24hourstopermitthecompli.tion ofthesurveBIance whentheallowable outagetimelimitsoftheACTIONrequirements arelessthan24hours.SurvciHanco Requixcmcnts doiiothavetvbcperformed orinopersblc equipment.
II Sk 3.0.1 SR shall bc met during thc MODES or other specified conditions in the Applicability for indivirhisl I.COs, unless otherwise stated in the SR.Failure.to meet a SR, whcthcr such failure is expmenced during the performance of ilia Suivcillancc or between performances of thc Surveillance, shall'be Failure to meet thc LCO: Failure to perform a Surveillance within the specified Frequency shaH'bc failure to meet the LCO except as provided in SR.3.0.3.Surveillance do not have to be performed on inopcrablc cquipmcnt, or variables outside specified limits.
Insummary,pcrSpecifications 4.0.1and4.0,3,ifthesurveiBance frequency,for acomponent isexceeded, thesubjectcomponent mtistbedeclaredinoperable andthelimitingcondition for'peration (LCO)entered;howcvcr,adelayperiodofupto24hoursisprovidedbeforetheassociated ACTIONSmustbcperformed.
NAR-27-1997 89: 39 FRQ'l R~6.KE.DOCUNENT CONTROL TO 913814152182 P.82~~'R 3.0.3 If it is discovered that a Surveillance was not performed within its specified Fiequcncy, then compliance with the requirement to declare the LCO not met may be delayed,&om the time of'discovery, up to 24 hours or up to the lirrril of the specified Frequency, whichever is less.This delay is permitted to allow performance of the Surveillance, If the'Surveillance is not performed within the delay period, the LCO must immediately bc declared not met, and the applicable Condition(s) must be entered.Tlicrefore, pcr SR 3.0.1 and 3,0,3, if a surveillance frequency is exceeded, a delay period of up to 24 hours is provided in order to paform the surveillance prior to declaring any component inoperablc and the LCO not met.This is a significant rliffexence from STS in which the coinponent is first declared inoperablc and then a 24 hour delay is provided prior to per&rming thc required actions.Kn addition, with respect to repuitability of a missed survcHlance, there is no longer any discussion in the bases for SR 3.0,3.1 V Based on these difFcreneee, it'is RQkB's position that a.missed surveillance test is not a rcportabio event (i.c., LER)per the ISTS.At no time is the plant outside the ta:hnical specifications in this instance siircc no equlpmcm ls declared inoperable until thc allowed delay period from time of discovery has been exceeded (e.g, 24 hours)or the surveillance is failed upon its pcrfnrmanr.e.
Kithrespecttoreportability, thebasesforSpecification 4.0.3statethat"thefailuretoperformasurveillancc~thin theprovisions ofSpecification
These actions are speci6caHy piovided by SR 3.0.3 v hich is part of the technical specifications'per 10 CPR 50.36.In addition, a missed survciHance ta typically in adrnioistiative issue that does not directly affect plant operation unless thc affected component is failed.Therefore, if upon peforinance of the missed surveillance a'requited component is discovered inoperable, an LBR will be generated in accoahncc with the guidance provided in hKG~-1022 since tho componerrt mrry have been inoperable for a longer period of time than aHovIcd by the ISTS.It is noted that if a missed surveillance test indicates a substantial breakdown in the surveillance testing progrun (e.gsurveillance test has never been performef}, it vmuld be reported per 10 CFR.50.73(a)(%Xi)(B).
 
This is.consistent with NUREG 10 2 guidanco for rcportability of adruiriisu'aiivc control reIated errors.Since the IST program mpircmcrits are in the administrative controls section in ISTS (versus Specification 4.0.5 per STS), this guidance would also apply to raisscd or deficient IST program requirements.
==4.0. 2isaviolation==
Therefore, eFcctr'vo February 24, 1996, ROBOMB will only generate an L ER per 10 CFR 50./3 upon'missed technical specification or IST surveillance if: A component niust be declared iirnlr~sable and the time period between two rrucccssful surveHIMicc tests is greater'than 1.25 time the specified frequency plus the completion time for restoring the comporrerri io operable.status; or.4 (2)Vhc missed surveillance(s) indicate a substantial breakdown in the surveillance testing program, NAR-27-1997 89: 39 FROM R.G.&E.DOClNENT CONTROL TO 913814152182 P.83~~~4 Plebe contact George Wrobef, Manager of Nuclear Safety and Licensing at (7l6)724-8070 if you require any further information.
ofaTcchnical SpccUicatioii
RGEcB would like to suggest that the NRC consider these issues in any future revisions of M JRFG-1022 Ver ly yours, MDE845 Robert C Mecredy XC: U.S.Nuclear Regulatory Commission Mr.Guy Vissing (Mail Stnp 1467)PWR Project Directorate I-j Washington, D.C.20555 U.S.Nuclear Regulatory Commission Mr.Chris Grimes (Mail Stop i 1222)Chief, Technical Specifications Branch Washington, D.C.Z0555 Ginna Senior Resident hspector TOTAL P.83}}
~requirement andis,therefore, areportable eventundertherequirements of10CFR50.73{a)(2)(i)(B) becauseitisacondition prohibited bythepla'nt'sTechnical Specifications."
&HAG-1022 furtherexpandsonthisbystatingthatamissedtechnical specification orTATmirveillancc inustbereportedwhen"enoughtimehaselapsedthat,aseresultofthemissedsurveillance, aTScontrolled systemmustbcdcchucdinopcrablc andthcLCOactionsuiiciiicut hasbeenexceeded."
Thatis,anLEEisrequiredifthetimeperiodbetweenthelasttestandthctestbeingperformed is.greaterthanthespeciGcdtestinginterval(multiplied by1.25'perSpecification'4.0.2) plusthccompletion timeforrestoring the~R'ectedcomponent tooperablestatus.Jnthisinstance, theaKectcdcomponent maybeinoperable foralongerperiodoftiincthantheSTSwouldallow(i.e.,theplantisinacondition
.piohibitcd bytechnical specifications).
lnISTS,therearcsignificant differences fromSpecifications 4.0.Iand.4.0.3.
ThenewversionsoftheseSpecifications arcrc8tatcdbelowfromtheGinnaStationtc"hnical, spccilicutions:
IISk3.0.1SRshallbcmetduringthcMODESorotherspecified conditions intheApplicability forindivirhisl I.COs,unlessotherwise statedintheSR.Failure.tomeetaSR,whcthcrsuchfailureisexpmenced duringtheperformance ofiliaSuivcillancc orbetweenperformances ofthcSurveillance, shall'beFailuretomeetthcLCO:FailuretoperformaSurveillance withinthespecified Frequency shaH'bcfailuretomeettheLCOexceptasprovidedinSR.3.0.3.
Surveillance donothavetobeperformed oninopcrablc cquipmcnt, orvariables outsidespecified limits.
NAR-27-1997 89:39FRQ'lR~6.KE.DOCUNENTCONTROLTO913814152182 P.82~~'R3.0.3Ifitisdiscovered thataSurveillance wasnotperformed withinitsspecified Fiequcncy, thencompliance withtherequirement todeclaretheLCOnotmetmaybedelayed,&omthetimeof'discovery, upto24hoursoruptothelirrrilofthespecified Frequency, whichever isless.Thisdelayispermitted toallowperformance oftheSurveillance, Ifthe'Surveillance isnotperformed withinthedelayperiod,theLCOmustimmediately bcdeclarednotmet,andtheapplicable Condition(s) mustbeentered.Tlicrefore, pcrSR3.0.1and3,0,3,ifasurveillance frequency isexceeded, adelayperiodofupto24hoursisprovidedinordertopaformthesurveillance priortodeclaring anycomponent inoperablc andtheLCOnotmet.Thisisasignificant rliffexence fromSTSinwhichthecoinponent isfirstdeclaredinoperablc andthena24hourdelayisprovidedpriortoper&rming thcrequiredactions.Knaddition, withrespecttorepuitability ofamissedsurvcHlance, thereisnolongeranydiscussion inthebasesforSR3.0,3.1VBasedonthesedifFcreneee, it'isRQkB'spositionthata.missedsurveillance testisnotarcportabio event(i.c.,LER)pertheISTS.Atnotimeistheplantoutsidetheta:hnical specifications inthisinstancesiirccnoequlpmcmlsdeclaredinoperable untilthcalloweddelayperiodfromtimeofdiscovery hasbeenexceeded(e.g,24hours)orthesurveillance isfaileduponitspcrfnrmanr.e.
Theseactionsarespeci6caHy piovidedbySR3.0.3vhichispartofthetechnical specifications'per 10CPR50.36.Inaddition, amissedsurvciHance tatypically inadrnioistiative issuethatdoesnotdirectlyaffectplantoperation unlessthcaffectedcomponent isfailed.Therefore, ifuponpeforinance ofthemissedsurveillance a'requited component isdiscovered inoperable, anLBRwillbegenerated inaccoahncc withtheguidanceprovidedinhKG~-1022 sincethocomponerrt mrryhavebeeninoperable foralongerperiodoftimethanaHovIcdbytheISTS.Itisnotedthatifamissedsurveillance testindicates asubstantial breakdown inthesurveillance testingprogrun(e.gsurveillance testhasneverbeenperformef},
itvmuldbereportedper10CFR.50.73(a)(%Xi)(B).
Thisis.consistent withNUREG102guidancoforrcportability ofadruiriisu'aiivc controlreIatederrors.SincetheISTprogrammpircmcrits areintheadministrative controlssectioninISTS(versusSpecification 4.0.5perSTS),thisguidancewouldalsoapplytoraisscdordeficient ISTprogramrequirements.
Therefore, eFcctr'vo February24,1996,ROBOMBwillonlygenerateanLERper10CFR50./3upon'missedtechnical specification orISTsurveillance if:Acomponent niustbedeclarediirnlr~sable andthetimeperiodbetweentworrucccssful surveHIMicc testsisgreater'than 1.25timethespecified frequency plusthecompletion timeforrestoring thecomporrerri iooperable.status; or.4(2)Vhcmissedsurveillance(s) indicateasubstantial breakdown inthesurveillance testingprogram, NAR-27-1997 89:39FROMR.G.&E.DOClNENTCONTROLTO913814152182 P.83~~~4PlebecontactGeorgeWrobef,ManagerofNuclearSafetyandLicensing at(7l6)724-8070ifyourequireanyfurtherinformation.
RGEcBwouldliketosuggestthattheNRCconsidertheseissuesinanyfuturerevisions ofMJRFG-1022 Verlyyours,MDE845RobertCMecredyXC:U.S.NuclearRegulatory Commission Mr.GuyVissing(MailStnp1467)PWRProjectDirectorate I-jWashington, D.C.20555U.S.NuclearRegulatory Commission Mr.ChrisGrimes(MailStopi1222)Chief,Technical Specifications BranchWashington, D.C.Z0555GinnaSeniorResidenthspectorTOTALP.83}}

Revision as of 12:46, 7 July 2018

Discusses Differences & Documents Util Position Concerning Reportability of Missed Surveillances on 960224 of TS & IST at Ginna Station Per Amend 61
ML17264A846
Person / Time
Site: Ginna 
Issue date: 05/14/1996
From: MECREDY R C
ROCHESTER GAS & ELECTRIC CORP.
To:
NRC OFFICE OF INSPECTION & ENFORCEMENT (IE REGION I)
References
NUDOCS 9704020118
Download: ML17264A846 (5)


Text

CATEGORY, j.lj, REGULAT INFORMATION DISTRIBUTION

~TEM (RIDS)ACCESSION NBR:9704020118 DOC.DATE: 96/05/14 NOTARIZED:

NO DOCKET FACIAL 50-244 Robert Emmet Ginna Nuclear Plant, Unit 1, Rochester G 05000244 AUTH.NAME'AUTHOR AFFILIATION MECREDY,R.C.'ochester Gas&Electric Corp.RECIP;NAME RECIPIENT AFFILIATION Region 1 (Post 820201)

SUBJECT:

Discusses differences

&documents util position concerning reportability of missed sgrveillances on 960224 of TS a IST at Ginna Station per Amend 61.'DISTRIBUTION CODE: IEOID COPIES RECEIVED:LTR

~ENCL 0 SIZE: TITLE: General (50 Dkt)-Insp Rept/Notice of Violation Response NOTES:License Exp date in accordance with 10CFR2;2.109(9/19/72).

'A T 05000244 RECIPIENT ID CODE/NAME PDl-l PD INTERNAL: AEOD/SPD/RAB DEDRO NRR/DISP/PIPB NRR/DRPM/PECB NUDOCS-ABSTRACT OGC/HDS3 COPIES LTTR ENCL 1 1 1 1 1 1 RECIPIENT ID CODE/NAME VISSING, G..BQihjCCZg FILE CEN FB NRR/DRPM/PERB OE DIR RGN1 FILE 01 COPIES LTTR ENCL EXTERNAL: LITCO BRYCE,J H 1 NRC PDR 1 NOAC NUDOCS FULLTEXT D NOTE TO ALL"RIDS" RECIPIENTS:

PLEASE HELP US TO REDUCE WASTE.TO HAVE YOUR NAME OR ORGANIZATION REMOVED FROM DISTRIBUTION LISTS'OR REDUCE THE'UMBER OF COPIES RECEIVEDBY YOU OR YOUR ORGANIZATION, CONTACT THE DOCUMENT CONTROL DESK (DCD)ON EXTENSION 415-2083 TOTAL NUMBER OF COPIES REQUIRED: ITTR 18 ENCL N-R-27-1997 89: 15 FRON R.G.KE.DOCLNENT CONTROL TO 913814152182 P.82~~gQQNQKR GA$AIVD EIECNIC CORPORAL i S9 EASTMAN'/AVE, ROCHESlEIi'N Y.Qdl90(X((AREA CCOE7Id SC&27%ROBERT C.hLECQEOY Vri Pwu&ht Hadst Opetol'en'.S.

Nuc!car Regulatory Commission Region I 475 AUendale Road King of Prussia, PA 19406

Subject:

May 14, 1996 KH ERR g~'RR Reportability'of Missed Technical Specification and Inscaicc Testing SurvciHanccs Rochester.Gas k Electric Corporation R.E.Ginna Nuclear Power Plant Docket No.50-244 Gentlemen,'n Pebruary 24, 1996, RGB'mplemented the Improve'd Standard Technical Specifications

{ISTS)at Ginna Station per Amendment No.61.As a rmlt of this conversion, an issue has been raised witii icspc<<t to t!ic icpoitability of iiiis~cd tccliu;vul spa;ifi<<ation aud inscivico ta ting (IST)survciGanccs pcr'0 CPR 50.73.This issue is duc to thc fact that previous NRC guidance in this area (NUIT-1022) does not specificaHy apply to the ISTS in several areas.The purpose of this letter is to discuss these differences and document RGkEs position concerninS reportabiiity of these missed survcillanccs.

In 1994, the NRC published asccond draft, revision 1 to NUREG-1022.

Thc purpose of N"REG-1022 was to consolidateNRC reporting guidelines with respect to.10 CFR 50.72 and 50.73 into one document to help achicvo consistency vithia, thc'nuclear power industry.MJREG-10~M w(is developed using standard tcchnical specifications (STS)which preceded the ISTS.There are several differences between these two versions of technical spcciGcations which crcatc discrepancies when attempting to use the guidance of MJRECv-1022,.especially for the reportability nf missed techniiml.specifications and IST survei0ances.

These differences are discussed in detail below.In STS, the relevant specifications in question are 4.0.1 and 4.0.3.These are resta>M below for discussion purposes: 4.0.1 SurvciHance Requirements shall be met during the OPEBATIONAI.

MODES.or'ther conditions specified for individual I.imiting Conditions for Qperauon unle:s otherwisc stated in an individual Surveillance Requirement,'7704020118 960514 PDR ADOCK 05000244 P~PDR t~.Q~'Q (o u2~

l%R-27-1997 89: 1S FP R.G.KE.DOCUMENT CONTROL$0~9139141S2182 P.83'1 4.0.3 Failure'to perform a Surveillance Requirement within the allowed surveillsni<

interval;de6ncd by SpeciQcation 4.0.2, shall constitute noncompliance with the OPERABILITY requiretnents for a Limitina Condition for Operation.

The time limits of the ACTION requirements are applicable at the tiine it is identified that a SurvciUance Requirement has not been performed.

The ACTION requirements may be delayed for up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> to permit the compli.tion of the surveBIance when the allowable outage time limits of the ACTION requirements are less than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.SurvciHanco Requixcmcnts do iiot have tv bc performed or inopersblc equipment.

In summary, pcr Specifications 4.0.1 and 4.0,3, if the surveiBance frequency,for a component is exceeded, the subject component mtist be declared inoperable and the limiting condition for'peration (LCO)entered;howcvcr, a delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> is provided before the associated ACTIONS must bc performed.

Kith respect to reportability, the bases for Specification 4.0.3 state that"the failure to perform a surveillancc~thin the provisions of Specification 4.0.2 is a violation of a Tcchnical SpccUicatioii

~requirement and is, therefore, a reportable event under the requirements of 10 CFR 50.73{a)(2)(i)(B) because itis a condition prohibited by the pla'nt's Technical Specifications."&HAG-1022 further expands on this by stating that a missed technical specification or TAT mirveillancc inust be reported when"enough time has elapsed that, as e result of the missed surveillance, a TS controlled system must bc dcchucd inopcrablc and thc LCO action suiiciiicut has been exceeded." That is, an LEE is required if the time period between the last test and thc test being performed is.greater than the speciGcd testing interval (multiplied by 1.25'per Specification'4.0.2) plus thc completion time for restoring the~R'ected component to operable status.Jn this instance, the aKectcd component may be inoperable for a longer period of tiinc than the STS would allow (i.e., the plant is in a condition.piohibitcd by technical specifications).

ln ISTS, there arc significant differences from Specifications 4.0.I and.4.0.3.

The new versions of these Specifications arc rc8tatcd below from the Ginna Station tc"hnical, spccilicutions:

II Sk 3.0.1 SR shall bc met during thc MODES or other specified conditions in the Applicability for indivirhisl I.COs, unless otherwise stated in the SR.Failure.to meet a SR, whcthcr such failure is expmenced during the performance of ilia Suivcillancc or between performances of thc Surveillance, shall'be Failure to meet thc LCO: Failure to perform a Surveillance within the specified Frequency shaH'bc failure to meet the LCO except as provided in SR.3.0.3.Surveillance do not have to be performed on inopcrablc cquipmcnt, or variables outside specified limits.

NAR-27-1997 89: 39 FRQ'l R~6.KE.DOCUNENT CONTROL TO 913814152182 P.82~~'R 3.0.3 If it is discovered that a Surveillance was not performed within its specified Fiequcncy, then compliance with the requirement to declare the LCO not met may be delayed,&om the time of'discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the lirrril of the specified Frequency, whichever is less.This delay is permitted to allow performance of the Surveillance, If the'Surveillance is not performed within the delay period, the LCO must immediately bc declared not met, and the applicable Condition(s) must be entered.Tlicrefore, pcr SR 3.0.1 and 3,0,3, if a surveillance frequency is exceeded, a delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> is provided in order to paform the surveillance prior to declaring any component inoperablc and the LCO not met.This is a significant rliffexence from STS in which the coinponent is first declared inoperablc and then a 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> delay is provided prior to per&rming thc required actions.Kn addition, with respect to repuitability of a missed survcHlance, there is no longer any discussion in the bases for SR 3.0,3.1 V Based on these difFcreneee, it'is RQkB's position that a.missed surveillance test is not a rcportabio event (i.c., LER)per the ISTS.At no time is the plant outside the ta:hnical specifications in this instance siircc no equlpmcm ls declared inoperable until thc allowed delay period from time of discovery has been exceeded (e.g, 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />)or the surveillance is failed upon its pcrfnrmanr.e.

These actions are speci6caHy piovided by SR 3.0.3 v hich is part of the technical specifications'per 10 CPR 50.36.In addition, a missed survciHance ta typically in adrnioistiative issue that does not directly affect plant operation unless thc affected component is failed.Therefore, if upon peforinance of the missed surveillance a'requited component is discovered inoperable, an LBR will be generated in accoahncc with the guidance provided in hKG~-1022 since tho componerrt mrry have been inoperable for a longer period of time than aHovIcd by the ISTS.It is noted that if a missed surveillance test indicates a substantial breakdown in the surveillance testing progrun (e.gsurveillance test has never been performef}, it vmuld be reported per 10 CFR.50.73(a)(%Xi)(B).

This is.consistent with NUREG 10 2 guidanco for rcportability of adruiriisu'aiivc control reIated errors.Since the IST program mpircmcrits are in the administrative controls section in ISTS (versus Specification 4.0.5 per STS), this guidance would also apply to raisscd or deficient IST program requirements.

Therefore, eFcctr'vo February 24, 1996, ROBOMB will only generate an L ER per 10 CFR 50./3 upon'missed technical specification or IST surveillance if: A component niust be declared iirnlr~sable and the time period between two rrucccssful surveHIMicc tests is greater'than 1.25 time the specified frequency plus the completion time for restoring the comporrerri io operable.status; or.4 (2)Vhc missed surveillance(s) indicate a substantial breakdown in the surveillance testing program, NAR-27-1997 89: 39 FROM R.G.&E.DOClNENT CONTROL TO 913814152182 P.83~~~4 Plebe contact George Wrobef, Manager of Nuclear Safety and Licensing at (7l6)724-8070 if you require any further information.

RGEcB would like to suggest that the NRC consider these issues in any future revisions of M JRFG-1022 Ver ly yours, MDE845 Robert C Mecredy XC: U.S.Nuclear Regulatory Commission Mr.Guy Vissing (Mail Stnp 1467)PWR Project Directorate I-j Washington, D.C.20555 U.S.Nuclear Regulatory Commission Mr.Chris Grimes (Mail Stop i 1222)Chief, Technical Specifications Branch Washington, D.C.Z0555 Ginna Senior Resident hspector TOTAL P.83