ML20161A028

From kanterella
Jump to navigation Jump to search
Technical Specifications - SNM-2514 Renewal
ML20161A028
Person / Time
Site: Humboldt Bay
Issue date: 06/10/2020
From:
Pacific Gas & Electric Co
To:
Office of Nuclear Material Safety and Safeguards
Markley C
Shared Package
ML20161A024 List:
References
Download: ML20161A028 (31)
v • d • e


Text

APPENDIX TECHNICAL SPECIFICATIONS FOR THE HUMBOLDT BAY INDEPENDENT SPENT FUEL STORAGE INSTALLATION*

Docket No. 72-27 Materials License No. SNM-2514 Renewed License

TABLE OF CONTENTS 1.0 USE AND APPLICATION........................................................................................... 1.1-1 1.1 Definitions ......................................................................................................... 1.1-1 1.2 Logical Connectors............................................................................................1.2-1 1.3 Completion Times ............................................................................................. 1.3-1 1.4 Frequency ......................................................................................................... 1.4-1 2.0 APPROVED CONTENTS .......................................................................................... 2.0-1 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY ........................... 3.0-1 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY .......................................... 3.0-2 3.1 Spent Fuel Storage Cask (SFSC) Integrity ........................................................ 3.1-1 3.1.1 Multi-Purpose Canister (MPC-HB) .....................................................................3.1-1 3.1.2 Overpack Heat Removal System....................................................................... 3.1-3 3.1.3 Fuel Cool-Down................................................................................................. 3.1-5 4.0 DESIGN FEATURES ................................................................................................. 4.0-1 4.1 Design Features Significant to Safety................................................................ 4.0-1 4.1.1 Criticality Control ...............................................................................................4.0-1 4.2 Codes and Standards ......... ..............................................................................4.0-1 4.2.1 Alternatives to Design Codes, Standards, and Criteria ...................................... 4.0-1 4.3 Cask Handling ...................................................................................................4.0-2 4.3.1 Cask Transporter ............................................................................................... 4.0-2 4.3.2 Storage Capacity .............. ................ .............................................................. 4.0-2 4.3.3 SFSC Load Handling Equipment ....................................................................... 4.0-2 5.0 ADMINISTRATIVE CONTROLS ................................................................................5.0-1 5.1 Administrative Programs ...................................................................................5.0-1 5.1.1 Technical Specifications (TS) Bases Control Program ......................................5.0-1 5.1.2 Radioactive Effluent Control Program ...............................................................5.0-1 5.1.3 MPC-HB and SFSC Loading, Unloading, and Preparation Program ..................5.0-1 5.1.4 ISFSI Operations Program ................................................................................5.0-2 5.1.5 Cask Transportation Evaluation Program ..........................................................5.0-2 5.1.6 GTCC Waste Cask Loading and Preparation Program......................................5.0-2 HUMBOLDT BAY ISFSI T of C Renewed License

Definitions 1.1 1.0 USE AND APPLICATION 1.1 Definitions

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

The defined terms of this section appear in capitalized type and are applicable throughout these Technical Specifications and Bases.

Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.

DAMAGED FUEL ASSEMBLY DAMAGED FUEL ASSEMBLIES are fuel assemblies with known or suspected cladding defects, as determined by a review of records, greater than pinhole leaks or hairline cracks; empty fuel rod locations that are not filled with solid Zircaloy or stainless steel rods; no longer in the form of an intact fuel assembly and consist of, or contain, debris such as loose fuel pellets, rod segments, etc.; or those that cannot be handled by normal means. This also includes fuel assemblies that are damaged in such a manner as to impair their structural integrity, or have missing or displaced structural components such as grid spacers.

DAMAGED FUEL ASSEMBLIES must be stored in a DAMAGED FUEL CONTAINER.

DAMAGED FUEL CONTAINER DFCs are specially designed enclosures for DAMAGED (DFC)

  • FUEL ASSEMBLIES that permit gaseous and liquid media to escape to the atmosphere in the MPC-HB, while minimizing dispersal of gross particulates within the MPC HB. A DFC can hold one DAMAGED FUEL ASSEMBLY comprised of material up to the equivalent of an INTACT FUEL ASSEMBLY.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.1-1 1.0

Definitions 1.1 1.1 Definitions (continued)

INTACT FUEL ASSEMBLY INTACT FUEL ASSEMBLY is a fuel assembly without known or suspected cladding defects greater than pinhole leaks or hairline cracks and which can be handled by normal means. A fuel assembly shall not be classified as INTACT FUEL ASSEMBLY unless solid Zircaloy or stainless steel rods are used to replace missing fuel rods and which displace an amount of water equal to that displaced by the original fuel rod(s).

LOADING OPERATIONS LOADING OPERATIONS include all licensed activities on an SFSC while it is being loaded with its approved contents. LOADING OPERATIONS begin when the first fuel assembly is placed in the MPC and end when the SFSC is suspended from or secured on the transporter.

MULTl-PURPOSE CANISTER MPC-HB is a sealed SPENT NUCLEAR FUEL container (MPC-HB) that consists of a honeycombed fuel basket contained in a cylindrical canister shell that is welded to a baseplate, lid with welded port cover plates, and closure ring. The MPC-HB provides the confinement boundary for the contained radioactive materials.

OPERABLE/OPERABILITY A system, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing its specified safety function(s) and when all necessary attendant instruments, controls, normal or emergency electrical power, and other auxiliary equipment that are required for the system, component, or device to perform its specific safety function(s) are also capable of performing their related support function(s).

OVERPACK OVERPACK is a cask that receives and contains a sealed MPC-HB for transportation to and interim storage in the independent spent fuel storage installation (ISFSI). It provides the helium retention boundary, gamma and neutron shielding, protection against environmental phenomena, and a set of lifting trunnions for handling.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.1-2 1.0

Definitions 1.1 1.1 Definitions (continued)

SPENT FUEL STORAGE SFSCs are containers approved for the storage of spent CASKS (SFSCs) fuel assemblies at the ISFSI. The HI-STAR HB SFSC System consists of the OVERPACK and its integral MPC HB.

SPENT NUCLEAR FUEL SPENT NUCLEAR FUEL means fuel that has been withdrawn from a nuclear reactor following irradiation, has undergone at least one year's decay since being used as a source of energy in a power reactor and has not been chemically separated into its constituent elements by reprocessing. SPENT NUCLEAR FUEL includes the special nuclear material, byproduct material, source material, and other radioactive materials associated with fuel assemblies, including fuel channels.

STORAGE OPERATIONS STORAGE OPERATIONS include all licensed activities that are performed at the ISFSI while at least one loaded SFSC is in place in the storage vault with the vault lid and all its lid bolts installed.

TRANSPORT OPERATIONS TRANSPORT OPERATIONS include all licensed activities performed on an SFSC loaded with its approved contents when it is being moved to or from the ISFSI. TRANSPORT OPERATIONS begin when the loaded SFSC is first suspended from or secured to the transporter and end when the SFSC is at its destination and no longer secured on or suspended from the transporter.

UNLOADING OPERATIONS UNLOADING OPERATIONS include all licensed activities on an SFSC while its contained MPC-HB is being unloaded of its approved contents. UNLOADING OPERATIONS begin when the SFSC is no longer suspended from the transporter and end when the last of its approved contents is removed from the MPC-HB.

Renewed License HUMBOLDT BAY ISFSI 1.1-3 1.0

Logical Connectors 1.2 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Specifications (TS) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TS are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and by the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action). The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

EXAMPLES The following examples illustrate the use of logical connectors.

EXAMPLE 1.2-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Verify AND A.2 Restore In this example, the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.2-1 1.0

Logical Connectors 1.2 1.2 Logical Connectors EXAMPLES (continued) EXAMPLE 1.2-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Stop OR A.2.1 Verify AND A.2.2.1 Reduce OR A.2.2.2 Perform OR A.3 Remove This example represents a more complicated use of logical connectors.

Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three ACTIONS may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

Renewed License HUMBOLDT BAY ISFSI 1.2-2 1.0

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify the lowest functional capability or performance levels of equipment required for safe operation of the facility. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., equipment or variable not within limits) that requires entering an ACTIONS condition unless otherwise specified, providing the cask system is in a specified condition stated in the Applicability of the LCO.

Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the condition no longer exists or the cask system is not within the LCO Applicability.

Once a Condition has been entered, subsequent subsystems, components, or variables expressed in the Condition, discovered to be not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.3-1 1.0

Completion Times 1.3 1.3 Completion Times (continued)

EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required B.1 Perform Action B.1 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action and AND associated Completion B.2 Perform Action B.2 Time not met. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to complete action B.1 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND complete action B.2 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> is allowed for completion action B.1 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />) is allowed for completing action B.2 from the time that Condition B was entered. If action B.1 is completed within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, the time allowed for completing action B.2 is the next 30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> because the total time allowed for completing action B.2 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.3-2 1.0

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued) EXAMPLE 1.3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One system A.1 Restore system to 7 days not within limit. within limit.

B. Required B.1 Complete action 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action and B.1.

associated AND Completion Time not met. B.2 Complete action 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> B.2.

When a system is determined not to meet the LCO, Condition A is entered. If the system is not restored within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the system is restored after Condition B is entered, Conditions A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.3-3 1.0

Completion Times 1.3 1.3 Completion Times EXAMPLES (continued) EXAMPLE 1.3-3 ACTIONS

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

Separate Condition entry is allowed for each component.

CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Restore 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> compliance with LCO.

B. Required B.1 Complete action 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and B.1 associated AND Completion Time not met. B.2 Complete action 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> B.2 The Note above the ACTIONS table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each component, and Completion Times tracked on a per component basis.

When a component is determined to not meet the LCO, Condition A is entered and its Completion Time starts. If subsequent components are determined to not meet the LCO, Condition A is entered for each component and separate Completion Times start and are tracked for each component.

IMMEDIATE When "Immediately" is used as a Completion Time, the Required COMPLETION Action should be pursued without delay and in a controlled manner.

TIME Renewed License HUMBOLDT BAY ISFSI 1.3-4 1.0

Frequency 1.4 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Limiting Condition for Operation (LCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the SR.

The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Surveillance Requirement (SR) Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be performed until sometime after the associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the SR (i.e., the Surveillance or the Frequency) is stated such that it is only "required" when it can be and should be performed. With an SR satisfied, SR 3.0.4 imposes no restriction.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.4-1 1.0

Frequency 1.4 1.4 Frequency (continued)

EXAMPLES The following examples illustrate the various ways that frequencies are specified.

EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify pressure within limit 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />) during which the associated Surveillance must be performed at least one time. Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, an extension of the time interval to 1.25 times the interval specified in the Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the equipment or variables are outside specified limits, or the facility is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the facility is in a condition specified in the Applicability of the LCO, the LCO is not met in accordance with SR 3.0.1.

If the interval as specified by SR 3.0.2 is exceeded while the facility is not in a condition specified in the Applicability of the LCO for which performance of the SR is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the specified condition. Failure to do so would result in a violation of SR 3.0.4.

(continued)

Renewed License HUMBOLDT BAY ISFSI 1.4-2 1.0

Frequency 1.4 1.4 Frequency EXAMPLES (continued) EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits. Once within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> prior to starting activity AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> thereafter Example 1.4-2 has two Frequencies. The first is a one-time performance Frequency, and the second is of the type shown in Example 1.4-1. The logical connector "AND" indicated that both Frequency requirements must be met. Each time the example activity is to be performed, the Surveillance must be performed within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> prior to starting the activity.

The use of "once" indicates a single performance will satisfy the specified Frequency (assuming no other Frequencies are connected by "AND"). This type of Frequency does not qualify for the 25 percent extension allowed by SR 3.0.2.

"Thereafter" indicated future performances must be established per SR 3.0.2, but only after a specified condition is first met (i.e., the "once performance in this example). If the specified activity is cancelled or not performed, the measurement of both intervals stops. New intervals start upon preparing to restart the specified activity.

Renewed License HUMBOLDT BAY ISFSI 1.4-3 1.0

Approved Contents 2.0 2.0 APPROVED CONTENTS 2.1 Functional and Operating Limits 2.1.1 Spent Fuel To Be Stored INTACT FUEL ASSEMBLIES and DAMAGED FUEL ASSEMBLIES meeting the limits specified in Tables 2.1-1 and 2.1-2 may be stored in the SFSC System.

2.1.2 GTCC Waste To Be Stored Greater-than-Class-C (GTCC) waste meeting the description in Section 3.1 of the Humboldt Bay ISFSI SAR may be stored in one cask at the ISFSI.

2.2 Functional and Operating Limits Violations If any Fuel Specifications or Loading Conditions of 2.1 are violated, the following ACTIONS shall be completed:

1. The affected fuel assemblies shall be placed in a safe condition.
2. Within 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />, notify the NRC Operations Center.
3. Within 30 days, submit a special report which describes the cause of the violation, and ACTIONS taken to restore compliance and prevent recurrence.

Renewed License HUMBOLDT BAY ISFSI 2.0-1 2.0

Approved Contents 2.0 TABLE 2.1-1 MPC-HB-HB FUEL ASSEMBLY LIMITS A. Allowable Contents (Notes 1 and 2)

1. Uranium oxide, INTACT FUEL ASSEMBLIES and DAMAGED FUEL ASSEMBLIES, with or without channels, meeting the criteria specified in Table 2.1-2 and the following specifications.

Cladding type ZR (Notes 3 and 4)

Planar-Average Initial enrichment 2.60 and 2.08 wt% 235U.

Post-irradiation cooling time per 29 years assembly Average burnup per assembly 23,000 MWD/MTU Decay heat per assembly 50 Watts Decay heat per SFSC 2000 Watts Fuel assembly length 96.91 inches (nominal design)

Fuel assembly width 4.70 inches (nominal design)

Fuel assembly weight 400 lb (including channel and DFC)

B. Quantity per MPC-HB: Up to 80 fuel assemblies.

C. DAMAGED FUEL ASSEMBLIES must be stored in a DAMAGED FUEL CONTAINER.

Allowable Loading Configurations: Up to 28 DAMAGED FUEL ASSEMBLIES in DAMAGED FUEL CONTAINERS, can be stored in the peripheral fuel storage locations as shown in Figure 2.1-1, or up to 40 DAMAGED FUEL ASSEMBLIES in DAMAGED FUEL CONTAINERS, can be stored in a checkerboard pattern as shown in Figure 2.1-2. The remaining fuel storage locations may be filled with INTACT FUEL assemblies meeting the above applicable specifications, or with INTACT FUEL assemblies optionally stored in DFCs.

NOTE 1: Fuel assemblies with channels may be stored in any fuel cell location.

NOTE 2: The total quantity of damaged fuel permitted in a single DAMAGED FUEL CONTAINER is limited to the equivalent weight and special nuclear material quantity of one intact fuel assembly.

NOTE 3: ZR means any-zirconium-based fuel cladding material authorized for use in a commercial nuclear power plant reactor.

NOTE 4: Storage as a DAMAGED FUEL ASSEMBLY of material in the form of loose debris consisting of zirconium clad pellets, stainless steel clad pellets, unclad pellets or rod segments up to a maximum of one equivalent fuel assembly is allowed.

Renewed License HUMBOLDT BAY ISFSI 2.0-2 2.0

Approved Contents 2.0 TABLE 2.1-2 FUEL ASSEMBLY CHARACTERISTICS (Note 1)

Fuel Assembly Type GE Type II GE Type Ill, Exxon Type Ill & IV Design Initial U (kg/assy.) 78 78 No. of Fuel Rods 49 36 Fuel Rod Cladding O.D. (in.) 0.486 0.5585 Fuel Rod Cladding I.D. (in.) 0.426 0.505 Fuel Pellet Dia. (in.) 0.411 0.488 Fuel Rod Pitch (in.) 0.631 0.740 Active Fuel Length (in.) 80 80 No. of water rods 0 0 Channel Thickness (in) 0.060 0.060 NOTE 1: All dimensions are design nominal values. Maximum and minimum dimensions are specified to bound variations in design nominal values among fuel assemblies.

Renewed License HUMBOLDT BAY ISFSI 2.0-3 2.0

FIGURE 2.1-1 Approved Contents 2.0 CONFIGURATION 1: DAMAGED FUEL IN PERIPHERAL CELLS OF BASKET ONLY HUMBOLDT BAY 2.0-4 Renewed License ISFSI 2.0

Approved Contents 2.0 FIGURE 2.1-2 CONFIGURATION 2: CHECKERBOARD OF DAMAGED FUEL AND INTACT FUEL Renewed License HUMBOLDT BAY 2.0-5 ISFSI 2.0

LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during specified conditions in the Applicability, except as provided in LCO 3.0.2 LCO 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met.

If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required, unless otherwise stated.

LCO 3.0.3 Not applicable.

LCO 3.0.4 When an LCO is not met, entry into a specified condition in the Applicability shall not be made except when the associated ACTIONS to be entered permit continued operation in the specified condition in the Applicability for an unlimited period of time. This Specification shall not prevent changes in specified conditions in the Applicability that are required to comply with ACTIONS or that are related to the unloading of an SFSC.

LCO 3.0.5 Not applicable.

Renewed License HUMBOLDT BAY ISFSI 3.0-1 3.0

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from 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 limit of the specified Frequency, whichever is less. This delay period is permitted to allow performance of the Surveillance.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

SR 3.0.4 Entry into a specified condition in the Applicability of an LCO shall not be made unless the LCOs Surveillances have been met within their specified Frequency. This provision shall not prevent entry into specified conditions in the Applicability that are required to comply with Actions or that are related to the unloading of an SFSC.

Renewed License HUMBOLDT BAY ISFSI 3.0-2 3.0

MPC-HB 3.1.1 3.1 SFSC INTEGRITY 3.1.1 MULTl-PURPOSE CANISTER (MPC-HB)

LCO 3.1.1 The MPC-HB shall be dry and helium filled.

APPLICABILITY: During TRANSPORT OPERATIONS and STORAGE OPERATIONS ACTIONS

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

Separate Condition entry is allowed for each MPC-HB CONDITION REQUIRED ACTION COMPLETION TIME A. MPC-HB cavity drying A.1. Perform an engineering 7 days acceptance criterion not evaluation to determine the met. quantity of moisture left in the MPC-HB.

AND 30 days A.2 Develop and initiate corrective actions necessary to return the MPC-HB to an analyzed condition.

B. MPC-HB helium backfill B.1 Perform an engineering 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> pressure limit not met. evaluation to determine the impact of helium pressure differential.

AND B.2 Develop and initiate 14 days corrective actions necessary to return the MPC-HB to an analyzed condition.

(continued)

Renewed License HUMBOLDT BAY ISFSI 3.1-1 3.0

MPC-HB 3.1.1 ACTIONS (continued)

CONDITION REQUIRED ACTION COMPLETION TIME C. MPC-HB helium leak rate C.1 Perform an engineering 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> limit for vent and drain port evaluation to determine the cover plate welds not met. impact of increased helium leak rate on heat removal capacity.

AND C.2 Develop and initiate 7 days corrective actions necessary to return the MPC-HB to an analyzed condition.

D. Required Actions and D.1 Remove all fuel assemblies 30 days associated Completion from the MPC-HB.

Times not met.

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.1.1.1 Verify MPC-HB cavity vacuum drying pressure is 3 torr Once, prior to for 30 min. TRANSPORT OPERATIONS.

OR While recirculating helium through the MPC-HB cavity, verify that the gas temperature exiting the demoisturizer is 21°F for 30 min or the dew point of the gas exiting the MPC is 22.9°F for 30 min.

SR 3.1.1.2 Verify MPC-HB helium backfill pressure is 45.2 psig and Once, prior to 48.8 psig at a reference temperature of 70°F. TRANSPORT OPERATIONS.

SR 3.1.1.3 Verify that the total helium leak rate through the MPC-HB Once, prior to vent and drain port cover plate welds is 1.0E-7 atm- TRANSPORT cc/sec (He). OPERATIONS.

Renewed License HUMBOLDT BAY ISFSI 3.1-2 3.0

Overpack Heat Removal System 3.1.2 3.1 SFSC INTEGRITY 3.1.2 OVERPACK Heat Removal System LCO 3.1.2 The OVERPACK shall be dry and helium filled.

APPLICABILITY: During TRANSPORT OPERATIONS and STORAGE OPERATIONS ACTIONS

NOTE-----------*-------------------------------------------------

Separate Condition entry is allowed for each OVERPACK CONDITION REQUIRED ACTION COMPLETION TIME A. OVERPACK annulus drying A.1. Perform an engineering 7 days acceptance criterion not evaluation to determine the met. quantity of moisture left in the OVERPACK.

AND A.2 Develop and initiate 30 days corrective actions necessary to return the OVERPACK to an analyzed condition.

B. OVERPACK annulus B.1 Perform.an engineering 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> helium backfill pressure evaluation to determine the limit not met. impact of helium pressure differential.

AND B.2 Develop and initiate 30 days corrective actions necessary to return the OVERPACK to an analyzed condition.

Renewed License HUMBOLDT BAY ISFSI 3.1-3 3.0

Overpack Heat Removal System 3.1.2 C. OVERPACK helium leak C.1 Perform an engineering 7 days rate limit not met evaluation to determine impact of increased helium leak rate on heat removal capability and off-site dose release effects.

AND 30 days C.2 Develop and initiate corrective actions necessary to return the OVERPACK to analyzed condition.

Renewed License HUMBOLDT BAY ISFSI 3.1-4 3.0

Overpack Heat Removal System 3.1.2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.1.2.1 Verify OVERPACK annulus vacuum drying pressure is Once, prior to 3 torr for 30 min. TRANSPORT OPERATIONS SR 3.1.2.2 Verify OVERPACK annulus helium backfill pressure is Once, prior to 10 psig and 14 psig TRANSPORT OPERATIONS SR 3.1.2.3 Verify that the total helium leak rate through the Once, prior to OVERPACK closure plate inner mechanical seal, the TRANSPORT OVERPACK vent port plug seal and the OVERPACK drain OPERATIONS port plug seal is 4.3E-6 atm-cc/sec (He).

Renewed License HUMBOLDT BAY ISFSI 3.1-5 3.0

Fuel Cool-Down 3.1.3 3.1 SFSC INTEGRITY 3.1.3 Fuel Cool-Down LCO 3.1.3 The MPC-HB cavity bulk helium temperature shall be 200°F.

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

The LCO is only applicable to wet UNLOADING OPERATIONS.

APPLICABILITY: During UNLOADING OPERATIONS prior to re-flooding.

ACTIONS

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

Separate Condition entry is allowed for each MPC-HB CONDITION REQUIRED ACTION COMPLETION TIME A. MPC-HB cavity bulk Helium A.1 Establish MPC-HB cavity Prior to initiating MPC temperature not within limit. bulk Helium temperature HB re-flooding within limit. operations.

AND A.2 Ensure adequate heat 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> transfer from the MPC-HB to the environment SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.1.3.1 Ensure via analysis or direct measurement that the MPC Prior to MPC-HB HB cavity bulk helium temperature is 200°F. re-flooding operations.

Renewed License HUMBOLDT BAY ISFSI 3.1-6 3.0

Design Features 4.0 4.0 DESIGN FEATURES 4.1 Design Features Significant to Safety 4.1.1 Criticality Control

a. MULTl-PURPOSE CANISTER (MPC-HB) MPC-HB
1. Fuel cell pitch: 5.83 in.
2. 10 B loading in the neutron absorbers: 0.01 g/cm2 4.2 Codes and Standards The American Society of Mechanical Engineers Boiler and Pressure Vessel Code (ASME Code), 1995 Edition with Addenda through 1997, is the governing Code for the HI-STAR HB System, except for Sections V and IX. For activities governed by Section V and IX, the latest effective Code Edition is applicable.

Any specific alternatives to these codes and standards, and the codes and standards for other components followed for the Humboldt Bay ISFSI storage system, are provided in the Humboldt Bay ISFSI Safety Analysis Report (SAR).

4.2.1 Alternatives to Design Codes, Standards, and Criteria Approved alternatives to the ASME Code are listed in SAR Table 3.4-5. Changes to these alternatives or new alternatives may be used when authorized by the Director of the Office of Nuclear Material Safety and Safeguards or designee. The licensee should demonstrate that:

a. The proposed alternative would provide an acceptable level of quality and safety, or
b. Compliance with the specified requirements of the ASME Code would result in hardship or unusual difficulty without a compensating increase in the level of quality and safety.

Requests for alternatives as described in this section shall be submitted in accordance with 10 CFR 72.4.

(continued)

Renewed License HUMBOLDT BAY ISFSI 4.0-1 4.0

Design Features 4.0 4.0 DESIGN FEATURES (continued) 4.3 Cask Handling 4.3.1 Cask Transporter A cask transporter is used to transport the SFSC between the power plant and the ISFSI. The requirements for the cask transporter are as follows:

a. Except for the period of time in which the loaded SFSC is being moved on the rail dolly, TRANSPORT OPERATIONS shall be conducted using the cask transporter.
b. The cask transporter fuel tank shall not contain > 50 gallons of diesel fuel at any time.
c. The cask transporter shall be designed, fabricated, inspected, maintained, operated, and tested in accordance with the applicable guidelines of NUREG-0612.
d. The cask transporter lifting towers shall have redundant drop protection features.

4.3.2 Storage Capacity The Humboldt Bay ISFSI can accommodate up to 400 spent fuel assemblies. The ISFSI storage capacity can accommodate up to six SFSCs.

4.3.3 SFSC Load Handling Equipment Lifting of a SFSC outside of structures governed by 10 CFR 50 shall be performed with load handling equipment that is designed, fabricated, inspected, maintained, operated and tested in accordance with the applicable guidelines of NUREG-0612, "Control of Heavy Loads at Nuclear Power Plants."

Renewed License HUMBOLDT BAY ISFSI 4.0-2 4.0

Administrative Controls 5.0 5.0 ADMINISTRATIVE CONTROLS 5.1 Administrative Programs The following programs shall be established, implemented, and maintained:

5.1.1 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these TS.

a. Changes to the TS Bases shall be made under appropriate administrative controls and reviews.
b. Changes to the TS Bases may be made without prior NRC approval in accordance with the criteria in 10 CFR 72.48.
c. The TS Bases Control Program shall contain provisions to ensure that the TS Bases are maintained consistent with the Humboldt Bay ISFSI SAR.
d. Proposed changes that do not meet the criteria of 5.1.1.b above shall be reviewed and approved by the NRC prior to implementation. Changes to the TS Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 72.48 (d) (2).

5.1.2 Radioactive Effluent Control Program

a. This program is established and maintained to implement the requirements of 10 CFR 72.44 (d) or 72.126, as appropriate.
b. This program will provide limits on surface contamination of the OVERPACK and GTCC cask and verification of meeting those limits prior to removal of a loaded OVERPACK or GTCC cask from the refueling building.

5.1.3 MPC-HB and SFSC Loading, Unloading, and Preparation Program This program shall be established and maintained to implement Humboldt Bay ISFSI SAR Section 10.2 requirements for loading fuel and components into MPC-HBs, unloading fuel and components from MPC-HBs, and preparing the MPC-HBs for storage in the SFSCs. The requirements of the program for loading and preparing the MPC-HB shall be complete prior to removing the MPC-HB from the Refueling Building. The program provides for evaluation and control of the following requirements during the applicable operation:

a. Verify that the acceptance criteria for drying are met to ensure short term fuel temperature limits are not violated and the MPC-HB and OVERPACK are adequately dry.
b. Verify that the MPC-HB and OVERPACK inerting backfill pressures and purity assure adequate heat transfer and corrosion control.
c. Verify that leak testing assures adequate OVERPACK integrity.
d. Verify surface dose rates on the SFSCs are consistent with the offsite dose analysis.
e. During MPC-HB re-flooding, verify the MPC cavity bulk helium temperature is such that water quenching or flashing does not occur.
f. Loading is to be independently verified by a cognizant engineer to ensure that the fuel assemblies in the MPCs are placed in accordance with the original loading plan.

(continued)

Renewed License HUMBOLDT BAY ISFSI 5.0-1 5.0

Administrative Controls 5.0 5.0 ADMINISTRATIVE CONTROLS 5.1.4 ISFSI Operations Program This program will implement the Humboldt Bay ISFSI SAR requirements for ISFSI operations. It will include criteria to be verified and controlled:

a. SFSC cask storage location.
b. Design features listed in Section 4.0 and design basis ISFSI parameters consistent with the Humboldt Bay ISFSI SAR analysis.

5.1.5 Cask Transportation Evaluation Program This program will evaluate and control the transportation of loaded SFSCs between the HBPP Refueling Building and the ISFSI storage vault. Included in this program will be pre-transport evaluation and control during transportation of the following:

  • Transportation route road surface conditions.
  • Onsite hazards along the transportation route.
  • Security, including control of the 100 meter boundary.
  • Transporter control functions and operability.
  • Offsite marine hazards from barge transport.
  • Severe weather.

5.1.6 GTCC Cask Loading and Preparation Program This program shall be established and maintained to implement Humboldt Bay ISFSI SAR Section 3.1 requirements for loading a GTCC cask and preparing the GTCC cask for storage in the ISFSI. The requirements of the program for loading and preparing the GTCC cask shall be complete prior to removing the GTCC cask from the refueling building. The program provides for evaluation and control of the following requirements during the applicable operation:

a. Verify surface dose rates on the GTCC cask are consistent with the offsite dose analysis.
b. Verify that any effluents from the GTCC cask comply with 10 CFR 20 requirements.

Renewed License HUMBOLDT BAY ISFSI 5.0-2 5.0

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