ML011520514

Encl 1 - Standard Format and Content for Technical Specifications for 10 CFR Part 72 Cask Certificates of Compliance (Appendix to Certificate) to 05/31/01 Ltr L Hendricks, Nuclear Energy Institute

ML011520514
Person / Time
Issue date:	05/31/2001
From:	Brach E NRC/NMSS/SFPO
To:	Hendricks L Nuclear Energy Institute
Shared Package
ML011520507	List: ML011520503 ML011520514 ML011520535
References
-nr, L20679
Download: ML011520514 (33)

Text

APPENDIXTOCERTIFICATEOFCOMPLIANCENo.XXXXSTANDARDIZEDTECHNICALSPECIFICATIONSFORTHENRCSAMPLESTORAGECASK TABLEOFCONTENTS1.0USEANDAPPLICATION................................................11.1Definitions......................................................1 1.2LogicalConnectors...............................................41.3CompletionTimes................................................7 1.4Frequency....................................................112.0APPROVEDCONTENTS............................................143.0LIMITINGCONDITIONFOROPERATION(LCO)APPLICABILITY................................................................153.0SURVEILLANCEREQUIREMENT(SR)APPLICABILITY......................163.1FuelIntegrity...................................................173.1.1FuelIntegrityDuringDrying................................17 3.1.2FuelIntegrityDuringBackfillandTransfer.....................19 3.1.3SFSCHeatRemovalSystem...............................213.2CaskIntegrity..................................................233.2.1CaskIntersealPressure...................................233.3CaskCriticalityControlProgram....................................253.3.1DissolvedBoronConcentration..............................25 3.3.2CANISTERWaterTemperature.............................274.0DESIGNFEATURES................................................294.1DesignFeaturesSignificanttoSafety.............................294.1.1CriticalityControl...................................29 4.1.2Materials.........................................294.2CodesandStandards.........................................294.2.1AlternativestoCodes,Standards,andCriteria.................294.2.2Construction/FabricationAlternativestoCodes,Standards,andCriteria..............................304.3StructuralPerformance........................................304.3.1EarthquakeLoads......................................304.3.2DesignG-loads.........................................304.4CaskHandling/CANISTERTransferFacility........................305.0ADMINISTRATIVECONTROLS.......................................315.1AdministrativePrograms..........................................315.1.1RadioactiveEffluentControlProgram.......................31 5.1.2CaskLoading,Unloading,andPreparationProgram.....................................................315.1.3ISFSIOperationsProgram................................32 Page1of32Definitions1.11.0USEANDAPPLICATION1.1Definitions-----------------------------------------------------NOTE--------------------------------------------------------Thedefinedtermsofthissectionappearincapitalizedtypeandareapplicablethroughoutthese TechnicalSpecificationsandBases.[Exampledefinitionsaregivenandchangesoradditional definitionssuchasDAMAGEDFUELorFUELDEBRISmaybeneededtobeconsistentwitha particulardesign.]

---

TermDefinitionACTIONSACTIONSshallbethatpartofaSpecificationthatprescribesRequiredActionstobetakenunderdesignatedConditionswithin specifiedCompletionTimes.[CANISTERTheCANISTERisthesealedSPENTNUCLEARFUELcontainerwhichconsistsofabasketcontainedinacylindricalshellwhichis weldedtoabaseplate,lidwithweldedportcoverplates,and closurering.TheCANISTERprovidestheconfinementboundary forthecontainedradioactivematerials.INTACTFUELASSEMBLYINTACTFUELASSEMBLYisafuelassemblywithoutknownorsuspectedcladdingdefectsgreaterthanapinholeleakora hairlinecrackandwhichcanbehandledbynormalmeans.Afuel assemblyshallnotbeclassifiedasanINTACTFUELASSEMBLY unlesssolidZircaloyorstainlesssteelrodsareusedtoreplace missingfuelrodsandwhichdisplaceanamountofwaterequalto thatdisplacedbytheoriginalfuelrod(s).LOADINGOPERATIONSLOADINGOPERATIONSincludealllicensedactivitiesonanOVERPACKorTRANSFERCASKwhileitisbeingloadedwith fuelassemblies.LOADINGOPERATIONSbeginwhenthefirst fuelassemblyisplacedintheCANISTERandendwhenthe OVERPACKorTRANSFERCASKissuspendedfromorsecured onthetransporter.LOADINGOPERATIONSdoesnotinclude CANISTERtransferbetweentheTRANSFERCASKandthe OVERPACK.(continued)

Page2of32Definitions1.11.1Definitions(continued)OPERABLE/OPERABILITYAsystem,component,ordeviceshallbeOPERABLEorhaveOPERABILITYwhenitiscapableofperformingitsspecified safetyfunction(s)andwhenallnecessaryattendant instrumentation,controls,normaloremergencyelectricalpower, andotherauxiliaryequipmentthatarerequiredforthesystem, component,ordevicetoperformitsspecifiedsafetyfunction(s) arealsocapableofperformingtheirrelatedsupportfunction(s).OVERPACKOVERPACKisthecaskwhichreceivesandcontainsthesealedCANISTERforinterimstorageintheindependentspentfuel storageinstillation(ISFSI).Itprovidesgammaandneutron shielding,andprovidesforventilatedairflowtopromoteheat transferfromtheCANISTERtotheenvirons.TheOVERPACK doesnotincludetheTRANSFERCASK.SPENTFUELSTORAGESFSCsarecontainersapprovedforthestorageofCASKS(SFSCs)spentfuelassembliesattheISFSI.The[XXXX]SFSCSystemconsistsoftheOVERPACKanditsintegralCANISTER.]SPENTNUCLEARFUELSPENTNUCLEARFUELmeansfuelthathasbeenwithdrawnfromanuclearreactorfollowingirradiation,hasundergoneat leastoneyear'sdecaysincebeingusedasasourceofenergyin apowerreactorandhasnotbeenchemicallyseparatedintoits constituentelementsbyreprocessing.SPENTNUCLEARFUEL includesthespecialnuclearmaterial,byproductmaterial,source material,andotherradioactivematerialsassociatedwithfuel

assemblies.[STORAGEOPERATIONSSTORAGEOPERATIONSincludealllicensedactivitiesthatareperformedattheISFSIwhileanSFSCcontainingspentfuelis sittingonastoragepadwithintheISFSIperimeter.STORAGE OPERATIONSdoesnotincludeCANISTERtransferbetweenthe TRANSFERCASKandtheOVERPACK.TRANSFERCASKTRANSFERCASKsarecontainersdesignedtocontaintheCANISTERduringandafterloadingofspentfuelassembliesand totransfertheCANISTERtoorfromtheOVERPACK.(continued)

Page3of32Definitions1.11.1Definitions(continued)TRANSPORTOPERATIONSTRANSPORTOPERATIONSincludealllicensedactivitiesperformedonanOVERPACKorTRANSFERCASKloadedwith oneormorefuelassemblieswhenitisbeingmovedtoandfrom theISFSI.TRANSPORTOPERATIONSbeginwhenthe OVERPACKorTRANSFERCASKisfirstsuspendedfromor securedonthetransporterandendwhentheOVERPACKor TRANSFERCASKisatitsdestinationandnolongersecuredon orsuspendedfromthetransporter.TRANSPORTOPERATIONS includetransferoftheCANISTERbetweentheOVERPACKand theTRANSFERCASK.UNLOADINGOPERATIONSUNLOADINGOPERATIONSincludealllicensedactivitiesonanSFSCtobeunloadedofthecontainedfuelassemblies.

UNLOADINGOPERATIONSbeginwhentheOVERPACKor TRANSFERCASKisnolongersuspendedfromorsecuredon thetransporterandendwhenthelastfuelassemblyisremoved fromtheSFSC.UNLOADINGOPERATIONSdonotinclude CANISTERtransferbetweentheTRANSFERCASKandthe OVERPACK.]

Page4of32LogicalConnectors1.21.0USEANDAPPLICATION 1.2LogicalConnectorsPURPOSEThepurposeofthissectionistoexplainthemeaningoflogicalconnectors.LogicalconnectorsareusedinTechnicalSpecifications(TS)todiscriminatebetween,andyetconnect,discreteConditions,Required Actions,CompletionTimes,Surveillances,andFrequencies.Theonly logicalconnectorsthatappearinTSareANDandOR.Thephysicalarrangementoftheseconnectorsconstituteslogicalconventionswith specificmeanings.BACKGROUNDSeverallevelsoflogicmaybeusedtostateRequiredActions.Theselevelsareidentifiedbytheplacement(ornesting)ofthelogical connectorsandbythenumberassignedtoeachRequiredAction.The firstleveloflogicisidentifiedbythefirstdigitofthenumberassignedtoa RequiredActionandtheplacementofthelogicalconnectorinthefirst levelofnesting(i.e.,leftjustifiedwiththenumberoftheRequiredAction).

Thesuccessivelevelsoflogicareidentifiedbyadditionaldigitsofthe RequiredActionnumberandbysuccessiveindentionsofthelogical connectors.WhenlogicalconnectorsareusedtostateaCondition,CompletionTime,Surveillance,orFrequency,onlythefirstleveloflogicisused,andthe logicalconnectorisleftjustifiedwiththestatementoftheCondition, CompletionTime,Surveillance,orFrequency.(continued)

Page5of32LogicalConnectors1.21.2LogicalConnectors(continued)EXAMPLESThefollowingexamplesillustratetheuseoflogicalconnectors.EXAMPLE1.2-1ACTIONSCONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1Verify...

ANDA.2Restore...Inthisexample,thelogicalconnectorANDisusedtoindicatethatwheninConditionA,bothRequiredActionsA.1andA.2mustbecompleted.(continued)

Page6of32LogicalConnectors1.21.2LogicalConnectors(continued)EXAMPLESEXAMPLE1.2-2(continued)ACTIONSCONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1Stop...

ORA.2.1Verify...

ANDA.2.2.1Reduce...

ORA.2.2.2Perform...

ORA.3Remove...Thisexamplerepresentsamorecomplicateduseoflogicalconnectors.RequiredActionsA.1,A.2,andA.3arealternativechoices,onlyoneof whichmustbeperformedasindicatedbytheuseofthelogicalconnector

ORandtheleftjustifiedplacement.AnyoneofthesethreeACTIONSmaybechosen.IfA.2ischosen,thenbothA.2.1andA.2.2mustbe performedasindicatedbythelogicalconnectorAND.RequiredActionA.2.2ismetbyperformingA.2.2.1orA.2.2.2.Theindented positionofthelogicalconnector

ORindicatesthatA.2.2.1andA.2.2.2arealternativechoices,onlyoneofwhichmustbeperformed.

Page7of32CompletionTimes1.31.0USEANDAPPLICATION 1.3CompletionTimesPURPOSEThepurposeofthissectionistoestablishtheCompletionTimeconventionandtoprovideguidanceforitsuse.BACKGROUNDLimitingConditionsforOperation(LCOs)specifythelowestfunctionalcapabilityorperformancelevelsofequipmentrequiredforsafeoperation ofthefacility.TheACTIONSassociatedwithanLCOstateConditions thattypicallydescribethewaysinwhichtherequirementsoftheLCOcan failtobemet.SpecifiedwitheachstatedConditionareRequired Action(s)andCompletionTimes(s).DESCRIPTIONTheCompletionTimeistheamountoftimeallowedforcompletingaRequiredAction.Itisreferencedtothetimeofdiscoveryofasituation (e.g.,equipmentorvariablenotwithinlimits)thatrequiresenteringan ACTIONSConditionunlessotherwisespecified,providingtheCask SystemisinaspecifiedconditionstatedintheApplicabilityoftheLCO.

RequiredActionsmustbecompletedpriortotheexpirationofthe specifiedCompletionTime.AnACTIONSConditionremainsineffect andtheRequiredActionsapplyuntiltheConditionnolongerexistsorthe CaskSystemisnotwithintheLCOApplicability.OnceaConditionhasbeenentered,subsequentsubsystems,components,orvariablesexpressedintheCondition,discoveredtobe notwithinlimits,willnotresultinseparateentryintotheConditionunlessspecificallystated.TheRequiredActionsoftheConditioncontinueto applytoeachadditionalfailure,withCompletionTimesbasedoninitial entryintotheCondition.(continued)

Page8of32CompletionTimes1.31.3CompletionTimes(continued)EXAMPLESThefollowingexamplesillustratetheuseofCompletionTimeswithdifferenttypesofConditionsandchangingConditions.EXAMPLE1.3-1ACTIONSCONDITIONREQUIREDACTIONCOMPLETIONTIMEB.RequiredActionand associated Completion Timenot met.B.1PerformActionB.1.ANDB.2PerformActionB.2.12hours36hoursConditionBhastwoRequiredActions.EachRequiredActionhasitsownseparateCompletionTime.EachCompletionTimeisreferencedtothe timethatConditionBisentered.TheRequiredActionsofConditionBaretocompleteactionB.1within12hoursANDcompleteactionB.2within36hours.Atotalof12hoursisallowedforcompletingactionB.1andatotalof36hours(not48hours)is allowedforcompletingactionB.2fromthetimethatConditionBwas entered.IfactionB.1iscompletedwithin6hours,thetimeallowedfor completingactionB.2isthenext30hoursbecausethetotaltimeallowed forcompletingactionB.2is36hours.(continued)

Page9of32CompletionTimes1.31.3CompletionTimes(continued)EXAMPLESEXAMPLE1.3-2(continued)ACTIONSCONDITIONREQUIREDACTIONCOMPLETIONTIMEA.Onesystemnotwithinlimit.A.1Restoresystemtowithinlimit.7daysB.RequiredActionandassociated Completion Timenotmet.B.1CompleteactionB.1.ANDB.2CompleteactionB.2.12hours36hoursWhenasystemisdeterminednottomeettheLCO,ConditionAisentered.Ifthesystemisnotrestoredwithin7days,ConditionBisalso enteredandtheCompletionTimeclocksforRequiredActionsB.1 andB.2start.IfthesystemisrestoredafterConditionBisentered, ConditionsAandBareexited,andtherefore,theRequiredActionsof ConditionBmaybeterminated.(continued)

Page10of32CompletionTimes1.31.3CompletionTimes(continued)EXAMPLESEXAMPLE1.3-3(continued)ACTIONS

---

NOTE-------------------------------------------

SeparateConditionentryisallowedforeachcomponent.

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1RestorecompliancewithLCO.4hoursB.RequiredActionandassociated Completion Timenotmet.B.1CompleteactionB.1.ANDB.2CompleteactionB.2.6hours12hoursTheNoteabovetheACTIONStableisamethodofmodifyinghowtheCompletionTimeistracked.Ifthismethodofmodifyinghowthe CompletionTimeistrackedwasapplicableonlytoaspecificCondition, theNotewouldappearinthatConditionratherthanatthetopofthe ACTIONSTable.TheNoteallowsConditionAtobeenteredseparatelyforeachcomponentandCompletionTimestrackedonapercomponentbasis.

WhenacomponentisdeterminedtonotmeettheLCO,ConditionAis enteredanditsCompletionTimestarts.Ifsubsequentcomponentsare determinedtonotmeettheLCO,ConditionAisenteredforeach componentandseparateCompletionTimesstartandaretrackedfor eachcomponent.IMMEDIATEWhen"Immediately"isusedasaCompletionTime,theRequiredCOMPLETIONActionshouldbepursuedwithoutdelayandinacontrolledmanner.

TIME Page11of32Frequency1.41.0USEANDAPPLICATION 1.4FrequencyPURPOSEThepurposeofthissectionistodefinetheproperuseandapplicationofFrequencyrequirements.DESCRIPTIONEachSurveillanceRequirement(SR)hasaspecifiedFrequencyinwhichtheSurveillancemustbemetinordertomeettheassociatedLimiting ConditionforOperation(LCO).Anunderstandingofthecorrect applicationofthespecifiedFrequencyisnecessaryforcompliancewith theSR.The"specifiedFrequency"isreferredtothroughoutthissectionandeachoftheSpecificationsofSection3.0,SurveillanceRequirement(SR)

Applicability.The"specifiedFrequency"consistsoftherequirementsof theFrequencycolumnofeachSR.SituationswhereaSurveillancecouldberequired(i.e.,itsFrequencycouldexpire),butwhereitisnotpossibleornotdesiredthatitbe performeduntilsometimeaftertheassociatedLCOiswithinits Applicability,representpotentialSR3.0.4conflicts.Toavoidthese conflicts,theSR(i.e.,theSurveillanceortheFrequency)isstatedsuch thatitisonly"required"whenitcanbeandshouldbeperformed.With anSRsatisfied,SR3.0.4imposesnorestriction.(continued)

Page12of32Frequency1.41.4Frequency(continued)EXAMPLESThefollowingexamplesillustratethevariouswaysthatFrequenciesarespecified.EXAMPLE1.4-1SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYVerifypressurewithinlimit.12hoursExample1.4-1containsthetypeofSRmostoftenencounteredintheTechnicalSpecifications(TS).TheFrequencyspecifiesaninterval (12hours)duringwhichtheassociatedSurveillancemustbeperformed atleastonetime.PerformanceoftheSurveillanceinitiatesthe subsequentinterval.AlthoughtheFrequencyisstatedas12hours,an extensionofthetimeintervalto1.25timestheintervalspecifiedinthe FrequencyisallowedbySR3.0.2foroperationalflexibility.The measurementofthisintervalcontinuesatalltimes,evenwhentheSRis notrequiredtobemetperSR3.0.1(suchaswhentheequipmentor variablesareoutsidespecifiedlimits,orthefacilityisoutsidethe ApplicabilityoftheLCO).IftheintervalspecifiedbySR3.0.2is exceededwhilethefacilityisinaconditionspecifiedintheApplicabilityof theLCO,theLCOisnotmetinaccordancewithSR3.0.1.IftheintervalasspecifiedbySR3.0.2isexceededwhilethefacilityisnotinaconditionspecifiedintheApplicabilityoftheLCOforwhich performanceoftheSRisrequired,theSurveillancemustbeperformed withintheFrequencyrequirementsofSR3.0.2priortoentryintothe specifiedcondition.FailuretodosowouldresultinaviolationofSR 3.0.4(continued)

Page13of32Frequency1.41.4Frequency(continued)EXAMPLES(continued)EXAMPLE1.4-2SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYVerifyflowiswithinlimits.Oncewithin12hourspriorto startingactivity AND24hoursthereafterExample1.4-2hastwoFrequencies.ThefirstisaonetimeperformanceFrequency,andthesecondisofthetypeshowninExample1.4-1.The logicalconnector"AND"indicatesthatbothFrequencyrequirementsmustbemet.Eachtimetheexampleactivityistobeperformed,the Surveillancemustbeperformedwithin12hourspriortostartingthe activity.Theuseof"once"indicatesasingleperformancewillsatisfythespecifiedFrequency(assumingnootherFrequenciesareconnectedby"AND

").ThistypeofFrequencydoesnotqualifyforthe25%extensionallowedby SR3.0.2."Thereafter"indicatesfutureperformancesmustbeestablishedperSR3.0.2,butonlyafteraspecifiedconditionisfirstmet(i.e.,the"once" performanceinthisexample).Ifthespecifiedactivityiscanceledornot performed,themeasurementofbothintervalsstops.Newintervalsstart uponpreparingtorestartthespecifiedactivity.

Page14of32ApprovedContents2.02.0APPROVEDCONTENTS2.1CaskcontentsshallbelimitedtoSPENTNUCLEARFUELinitiallyapprovedbytheNRCinAppendix[X.XX]oftheFSAR,throughtheissuanceofacaskCertificateof Compliance.2.2ProposedalternativestocontentslistedinAppendix[X.XX]oftheFSARmaybeauthorizedbytheDirectorofTheOfficeofNuclearMaterialSafetyandSafeguardsor designee.Therequestforsuchalternativecontentsshoulddemonstratethat:1.Theproposedalternativecontentswouldprovideanacceptablelevelofsafety,and 2.Theproposedalternativecontentsareconsistentwiththeapplicablerequirements.

Requestsforalternativestocontentsshallbesubmittedinaccordancewith10CFR72.4.[AdescriptionofthefuelparameterstobelistedinAppendix[X.XX]isprovidedbelow:FissileIsotopes(UO 2vs.MOX)MaximumInitial[PlanarAverage]Enrichment FuelClass(e.g.,14x14,15x15)NumberofFuelRods NumberofWaterHolesMaximumAssemblyAverageBurnup MinimumCoolingTimeafterReactorShutdown MinimumActiveFuelAverageEnrichment CladdingMaterial Non-FuelHardware(e.g.,BPRA/TPAs(coolingtimeandburnup))

MaximumWeightperStorageLocation(includingfuelchannelsandnon-fuel hardware)

MaximumDecayHeatperStorageLocation FuelCondition(intact,damagedordebris)TochangetheseparametersrequiresNRCapproval.Allotherfuelparameters,alsoidentifiedintheFSAR,canbechangedthroughthe10CFR72.48process.Theparameterlistmayneed tobemodifiedbasedonuniquefeaturesofaparticulardesignorforspecializedareassuchas highburnupfuelandburnupcredit.Thislistisintendedforintactfuel.Asaresult,thelistmay needtobemodifiedifdamagedfuelorfueldebrisisstoredinthecask.Whenpreferentialloadingconfigurationsarepartofthedesignbasis,theyneedtobeincludedinthecontentsdescription.]

Page15of32LCOApplicability3.03.0LIMITINGCONDITIONFOROPERATION(LCO)APPLICABILITYLCO3.0.1LCOsshallbemetduringspecifiedconditionsintheApplicability,exceptasprovidedinLCO3.0.2.

---

LCO3.0.2UpondiscoveryofafailuretomeetanLCO,theRequiredActionsoftheassociatedConditionsshallbemet.IftheLCOismetorisnolongerapplicablepriortoexpirationofthespecifiedCompletionTime(s),completionoftheRequiredAction(s)isnot required,unlessotherwisestated.

---

LCO3.0.3Notapplicable.

---

LCO3.0.4WhenanLCOisnotmet,entryintoaspecifiedconditionintheApplicabilityshallnotbemadeexceptwhentheassociatedACTIONStobeenteredpermitcontinued operationinthespecifiedconditionintheApplicabilityforanunlimitedperiodof time.ThisSpecificationshallnotpreventchangesinspecifiedconditionsinthe ApplicabilitythatarerequiredtocomplywithACTIONSorthatarerelatedtothe unloadingofanSFSC.LCO3.0.5Notapplicable.

Page16of32SRApplicability3.03.0SURVEILLANCEREQUIREMENT(SR)APPLICABILITYSR3.0.1SRsshallbemetduringthespecifiedconditionsintheApplicabilityforindividualLCOs,unlessotherwisestatedintheSR.FailuretomeetaSurveillance,whether suchfailureisexperiencedduringtheperformanceoftheSurveillanceorbetween performancesoftheSurveillance,shallbefailuretomeettheLCO.Failureto performaSurveillancewithinthespecifiedFrequencyshallbefailuretomeetthe LCOexceptasprovidedinSR3.0.3.Surveillancesdonothavetobeperformedon equipmentorvariablesoutsidespecifiedlimits.

---

SR3.0.2ThespecifiedFrequencyforeachSRismetiftheSurveillanceisperformedwithin1.25timestheintervalspecifiedintheFrequency,asmeasuredfromtheprevious performanceorasmeasuredfromthetimeaspecifiedconditionoftheFrequency ismet.ForFrequenciesspecifiedas"once,"theaboveintervalextensiondoesnotapply.IfaCompletionTimerequiresperiodicperformanceona"onceper..."basis,the aboveFrequencyextensionappliestoeachperformanceaftertheinitial performance.ExceptionstothisSpecificationarestatedintheindividualSpecifications.

---

SR3.0.3IfitisdiscoveredthataSurveillancewasnotperformedwithinitsspecifiedFrequency,thencompliancewiththerequirementtodeclaretheLCOnotmetmay bedelayed,fromthetimeofdiscovery,upto24hoursoruptothelimitofthe specifiedFrequency,whicheverisless.Thisdelayperiodispermittedtoallow performanceoftheSurveillance.IftheSurveillanceisnotperformedwithinthedelayperiod,theLCOmustimmediatelybedeclarednotmet,andtheapplicableCondition(s)mustbeentered.

WhentheSurveillanceisperformedwithinthedelayperiodandtheSurveillanceis notmet,theLCOmustimmediatelybedeclarednotmet,andtheapplicable Condition(s)mustbeentered.SR3.0.4EntryintoaspecifiedconditionintheApplicabilityofanLCOshallnotbemadeunlesstheLCO'sSurveillanceshavebeenmetwithintheirspecifiedFrequency.

ThisprovisionshallnotprevententryintospecifiedconditionsintheApplicability thatarerequiredtocomplywithActionsorthatarerelatedtotheunloadingofan

SFSC.

Page17of32FuelIntegrityDuringDrying3.1.13.1FuelIntegrity3.1.1FuelIntegrityDuringDryingLCO3.1.1Thetimeafterdrainingthe[CANISTER/Cask]andbeforeheliumbackfilloperationiscompleteshallnotexceed[X]days[thevacuumdryingtimemaybeafunctionof decayheatinatableorchart].[NOTE:Thetimespecification[X]mayberelocatedtoanadministrativeprogramifamethodologyforcalculatingfueltemperaturebasedondecayheatandheatuptimeisapprovedbytheNRC.]APPLICABILITY:DuringLOADINGOPERATIONS.ACTIONS:-------------------------------------------------NOTE------------------------------------------------------------

SeparateConditionentryisallowedforeach[CANISTER/Cask].

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1Verifyadequateheatremovaltoprevent exceedingashort-termfuel temperaturelimit.

ANDA.2Completeheliumbackfilloperation.Immediately[X]daysB.RequiredActionsandassociated CompletionTimesnot met.B.1Place[CANISTER/Cask]in[asafecondition.The applicantshallproposean appropriateconditionand completiontimeforits design.]Immediately(continued)

Page18of32FuelIntegrityDuringDrying3.1.1SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYSR3.1.1Verifythetimeafterdrainingthe[CANISTER/Cask]andbeforeheliumbackfilloperationiscompleted

is[X]days.SR3.0.4doesnotapply.Once,priortoTRANSPORT operations Page19of32FuelIntegrityDuringBackfillandTransfer3.1.23.1FuelIntegrity3.1.2FuelIntegrityDuringBackfillandTransferLCO3.1.2ThetimeaftercompletionofheliumbackfilloperationanduntiltheCANISTERisinsertedintothestoragecaskshallnotexceed[X]days[the timemaybeafunctionofdecayheatinatableorchart].[NOTE:ThisLCOmaynotbeneedediftheassociatedcasksandapprovedcontentsprovideadequatecoolingtopreventapproachingshort-termfueltemperaturelimits.Thetimespecification[X]mayberelocatedtoanadministrativeprogramifamethodologyforcalculatingfueltemperaturebasedondecayheatandheatuptimeisapprovedbytheNRC.AsimilartypeLCOmaybeneededforUNLOADINGoperations.]APPLICABILITY:DuringLOADINGOPERATIONS.ACTIONS:-------------------------------------------------NOTE------------------------------------------------------------

SeparateConditionentryisallowedforeachCANISTER.

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1Verifyadequateheatremovaltopreventexceedingashort-term fueltemperaturelimit.

ANDA.2CompleteCANISTERtransfer.Immediately[X]daysB.RequiredActionsandassociated CompletionTimesnot met.B.1PlaceCANISTERin[asafecondition.Theapplicantshall proposeanappropriate conditionandcompletiontime foritsdesign.]Immediately(continued)

Page20of32FuelIntegrityDuringBackfillandTransfer3.1.2SURVEILLANCEFREQUENCYSR3.1.2VerifythatthetimeaftercompletionofheliumbackfilloperationanduntilinsertionoftheCANISTERinto thestoragecaskis[X]days.SR3.0.4doesnotapply.Once,priortoTRANSPORT operations Page21of32SFSCHeatRemovalSystem3.1.3Note:thisLCOisonlyapplicabletocaskdesignswithcoolingvents.3.1FuelIntegrity3.1.3SFSCHeatRemovalSystemLCO3.1.3TheSFSCHeatRemovalSystemshallbeOPERABLE APPLICABILITY:WhileCANISTERisinthestorageOVERPACK.

ACTIONS:----------------------------------------------------NOTE---------------------------------------------------------

SeparateConditionentryisallowedforeachSFSC.

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.LCOnotmet.A.1RestoreSFSCHeatRemovalSystemtoOPERABLEstatus.

ORA.2.1Verifyadequateheatremovaltoprevent exceedingshort-termfuel temperaturelimit; ANDA.2.2RestoreSFSCHeatRemovalSystemto OPERABLEstatus.[8]hoursImmediately[30]daysB.RequiredActionsandassociatedCompletion Timesnotmet.B.1PlaceSFSCin[asafecondition.Theapplicantshall proposeanappropriate conditionandcompletiontime foritsdesign.]Immediately(continued)

Page22of32SFSCHeatRemovalSystem3.1.3SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYSR3.1.3VerifyallOVERPACKinletandoutletairductsarefreeofblockage.ORForOVERPACKSwithtemperaturemonitoringequipment,verifythedifferencebetweentheaverage OVERPACKairoutlettemperatureandISFSIambient temperatureis[XX oForC].[24]hours[24]hours Page23of32CaskIntersealPressure3.2.1Note:Requiredonlyforthosecaskswithboltedclosuresandanintersealpressuremonitoring system.3.2CaskIntegrity3.2.1CaskIntersealPressureLCO3.2.1ThecaskintersealminimumpressureshallbemaintainedatthevaluelistedinSectionxxxxoftheFSAR,asupdated.APPLICABILITY:DuringSTORAGEOPERATIONS.

ACTION:

---

NOTE---------------------------------------------------------SeparateConditionentryisallowedforeachSFSC.

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.Caskintersealpressurebelowlimit.A.1Re-establishcaskintersealpressureabovelimit.[7]daysB.RequiredActionandassociatedCompletion timenotmet.B.1PlaceSFSCin[asafecondition.Theapplicantshall proposeanappropriate conditionandcompletiontime foritsdesign.][30]days(continued)

Page24of32CaskIntersealPressure3.2.1SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYSR3.2.1Verifycaskintersealheliumpressureabovelimit.SR3.2.2Performachanneloperationaltesttoverifyproperfunctionofpressureswitch/transduceroncask overpressuresystem.[7]daysOnce,within[7]daysof commencing storageoperations andevery[36]

monthsthereafter Page25of32DissolvedBoronConcentration3.3.1Note:Requiredonlyforthosecasksthattakecreditforboroninthewaterforcriticalitycontrol.NotneededforBWRplants.3.3CaskCriticalityControlProgram3.3.1DissolvedBoronConcentrationLCO3.3.1Thedissolvedboronconcentrationinthewaterofthe[CANISTER/Cask]cavityshallbe[XXX]ppmb.[NOTE:Theboronconcentration[XXX]mayberelocatedtoanadministrativeprogramifamethodologyforcalculatingk-effofthespentfuelstorage[CANISTER/Cask]isapprovedbytheNRC.]APPLICABILITY:DuringLOADINGOPERATIONSandUNLOADINGOPERATIONSwithwaterandatleastonefuelassemblyinthe[CANISTER/Cask]ACTIONS:CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.Dissolvedboronconcentrationnotmet.A.1Suspendloadingoffuelassembliesintocaskandany otheractionsthatincrease reactivity.

ANDA.2Restoreboronconcentrationtoexceedlimit.

ANDA.3Removeallfuelassembliesfromcask.ImmediatelyImmediately[24]hours(continued)

Page26of32DissolvedBoronConcentration3.3.1SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYSR3.3.1.1Verifythedissolvedboronconcentrationismetusingtwoindependentmeasurements.Within[4]hourspriorto commencing LOADING OPERATIONS ANDevery[48]hoursthereafterwhilethe caskisinthespent fuelpoolorwhile waterisinthecaskSR3.3.1.2Verifythedissolvedboronconcentrationismetusingtwoindependentmeasurements.Within[4]hourspriorto commencing UNLOADING OPERATIONS ANDevery[48]hoursthereafterwhilethe caskisinthespent fuelpoolorwhile waterisinthecask Page27of32[CANISTER/Cask]WaterTemperature3.3.2Note:Thisspecificationisonlyrequiredif:a.Boroncreditisassumedinthecriticalityanalysis,and/orb.Optimummoderationisnotassumedinthecriticalityanalysis.3.3.2[CANISTER/Cask]WaterTemperatureLCO3.3.2Thetemperatureofthewaterinthecanistershallbe200F[alternatively,inlieuofatemperaturelimit,atimelimitcanbeappliedthatisbasedondecay heat].APPLICABILITY:DuringLOADINGandUNLOADINGOPERATIONS.

ACTIONS:

---

NOTE----------------------------------------------------------SeparateConditionentryisallowedforeach[CANISTER/Cask]system.

---

CONDITIONREQUIREDACTIONCOMPLETIONTIMEA.[CANISTER/Cask]watertemperaturelimitnotmet.A.1Restore[CANISTER/Cask]watertemperaturetobelow limit.[2]hoursB.RequiredActionandAssociatedCompletion timenotmet.B.1Place[CANISTER/Cask]in[asafecondition.Theapplicant shallproposeanappropriate conditionandcompletiontime foritsdesign.]Immediately(continued)

Page28of32CANISTERWaterTemperature3.3.2SURVEILLANCEREQUIREMENTSSURVEILLANCEFREQUENCYSR3.3.2Verifytemperatureofthewaterinthe[CANISTER/Cask]hasnotexceeded200F.Oncewithin[18]hoursafter

[TRANSFER CASKwithloaded CANISTER/Cask]

isremovedfrom fuelpool ANDEvery[30]minutesthereafter Page29of32DesignFeatures4.04.0DESIGNFEATURES4.1DesignFeaturesSignificanttoSafety4.1.1CriticalityControl

[Itemslistedin4.1.1arethosewhichwouldhaveasignificanteffectonsafetyifalteredormodified.Item1and/or2mayberemovediftheapplicationincludesananalysiswhich showsthattheparameterdoesnotsignificantlyaffectcriticalitysafetyintheparticular design.]1.Fluxtrapsizeorfuelcellspacing:>[X.XX]in.2.10BloadingintheBoralneutronabsorbers:>[X.XX]g/cm 2[4.1.2Materials1.Protectivecoatingsusedinsidethecask2.NeutronAbsorbersandShields 3.ContainmentBoundarySealsInsteadofspecifyingamaterialdirectly,theapplicantmayproposeasetofperformancestandardsalongwithproposedmethodsfordeterminingthatthematerialwillmeetthe applicablestandards.Note:Section4.1.2maybeincorporatedintotheCaskDescriptioninCondition1.b.oftheCertificateofComplianceiftheapplicantprefers.]4.2CodesandStandards Thefollowingprovidesinformationonthegoverningcodesforcomponentsofthe[XXX]caskdesign:CaskComponentApplicableCodesEditions/YearsImportanttoSafety[XXXX][XXXXXX][XXXXX]4.2.1AlternativestoCodes,Standards,andCriteriaTable[X.XX]oftheFSARlistsapprovedalternativestothe[code(s)ofrecord]forthedesignoftheCaskSystem.(continued)

Page30of32DesignFeatures4.04.2.2Construction/FabricationAlternativestoCodes,Standards,andCriteriaProposedalternativestothe[code(s)ofrecord]includingalternativesallowedbyTableX.XXoftheFSARmaybeusedwhenauthorizedbytheDirectoroftheOffice ofNuclearMaterialSafetyandSafeguardsordesignee.Therequestforsuch alternativesshoulddemonstratethat:1.Theproposedalternativeswouldprovideanacceptablelevelofqualityandsafety,or2.Compliancewiththespecifiedrequirementsofthe[codeofrecord]wouldresultinhardshiporunusualdifficultywithoutacompensatingincreaseinthelevelof qualityandsafety.Requestsforalternativesshallbesubmittedinaccordancewith10CFR72.4.4.3StructuralPerformance4.3.1EarthquakeLoadsThespentfuelstoragecaskdesignearthquakeloadonthetopsurfaceoftheISFSIpadshallnotexceed:HorizontalPeakAccelerationineachofthetwoorthogonalDirectionsCorrespondingVerticalPeak Accelerations[XX][XX]4.3.2DesignG-loadsThefissionproductbarrierdesigng-loadsduetopostulatedhandlingaccidentsshallnotexceed:FissionProductBarrierEndDropSideDropTipover[Caskand/orCANISTER][XX][XX][XX]4.4CaskHandling/CANISTERTransferFacility[Notethatcertaindesignsmayrequireaspecificationforoperationsoutside ofthePart50facility.]

Page31of32AdministrativeControls5.05.0ADMINISTRATIVECONTROLS5.1AdministrativeProgramsThefollowingprogramsshallbeestablished,implemented,andmaintained:5.1.1RadioactiveEffluentControlProgramAprogramshallbeestablishedthatincludes:

1.Implementationoftherequirementsof[10CFR72.44(d)or72.126,asappropriate].2.LimitsonthesurfacecontaminationandverificationofmeetingthoselimitspriortoremovalofthecaskfromthePart50structure,3.LimitsontheleakagerateandverificationofmeetingthoselimitspriortoremovalofthecaskfromthePart50structure,and,4.Aneffluentmonitoringprogram,ifthesurfacecontaminationlimitsaregreaterthanthevaluesspecifiedin[RegulatoryGuide1.86oranNRC-approved methodologyintheFSARcanbeinsertedinplaceofRG-1.86];oriftheleakage ratelimitsaregreaterthanthevaluesspecifiedas"leaktight"in[ANSIN14.5-1997"LeakageTestsonPackagesforShipment"oranNRC-approved methodologyintheFSARcanbeinsertedinplaceofANSIN14.5].5.1.2CaskLoading,Unloading,andPreparationProgramAprogramshallbeestablishedtoimplementtheFSARrequirementsforloadingfuelandcomponentsintothecask,unloadingfuelandcomponentsfromthecask,and preparingthecaskforstorage.Therequirementsoftheprogramforloadingand preparingthecaskshallbecompletepriortoremovingthecaskfromthe10CFR Part50structure.[Items1,5,and6areassociatedwithrequirementsthatwill remainintheSTS,however,theprocessforestablishingthespecifiedactionlimit maybemovedtothisadministrativeprogramifamethodofevaluationacceptableto theNRCispresentedintheFSAR.Items2,3,and4havebeenrelocatedfromthe LCOsectiontothisadministrativeprogrambecauseitisfeltthatNRCapproved methodsofevaluationwillberelativelyeasytodevelop.Ifappropriatemethodsare notpresentedintheFSAR,theseitemswillretainLCOs.]Ataminimum,theprogramshallestablishcriteriathatneedtobeverifiedtoaddressFSARcommitmentsandregulatoryrequirementsfor:1.Vacuumdryingtimesandpressurestoassurethattheshort-termfueltemperaturelimitsarenotviolatedandthecaskisadequatelydry,2.Inertingpressureandpuritytoassureadequateheattransferandcorrosioncontrol,3.Leaktestingtoassureadequatecaskintegrityandconsistencywiththeoffsitedoseanalysis,(continued)

Page32of32AdministrativeControls5.05.0AdministrativeControls(continued)4.Surfacedoseratestoassureproperloadingandconsistencywiththeoffsitedoseanalysis,5.Ambientandpoolwatertemperaturetoassureadequatesubcriticalityandmaterialductility,6.Spentfuelpoolboronconcentrationtoverifytheacceptablesubcriticalitymargin, and7.[Cladoxidationthicknessforhigh-burnupfuelinaccordancewithISG-11orotherNRC-approvedmethodologyifhigh-burnupfuelisincludedinthecontents.]Theprogramshallincludecompensatorymeasuresandappropriatecompletiontimesiftheprogramrequirementsarenotmet.5.1.3ISFSIOperationsProgramAprogramshallbeestablishedtoimplementtheFSARrequirementsforISFSIOperations.Ataminimum,theprogramshallestablishcriteriathatneedtobeverifiedfor:

1.Minimumcaskcenter-to-centerspacing,2.Padparameters(i.e.,padthickness,concretestrength,soilmodulus,reinforcement,etc.)thatareconsistentwiththeFSARanalysis,and3.Maximumliftingheightsforthecasksystemtoensurethattheg-loadlimitsinthetableinSection4.3.2aremetforthedesignbasisevents.