ML16231A041: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
||
Line 18: | Line 18: | ||
=Text= | =Text= | ||
{{#Wiki_filter: | {{#Wiki_filter:UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 Septanber '29, 2016 Mr. Charles R. Pierce Regulatory Affairs Director Southern Nuclear Operating Company, Inc. | ||
'29, 2016 Southern Nuclear Operating Company, Inc. P.O. Box 1295 I Bin 038 Birmingham, AL 35201-1295 | P.O. Box 1295 I Bin 038 Birmingham, AL 35201-1295 | ||
==SUBJECT:== | ==SUBJECT:== | ||
EDWIN I. HATCH NUCLEAR PLANT, UNIT NOS. 1AND2 -ISSUANCE OF AMENDMENTS REGARDING MULTIPLE TECHNICAL SPECIFICATION CHANGES (CAC NOS. MF5026 AND MF5027) | EDWIN I. HATCH NUCLEAR PLANT, UNIT NOS. 1AND2 - ISSUANCE OF AMENDMENTS REGARDING MULTIPLE TECHNICAL SPECIFICATION CHANGES (CAC NOS. MF5026 AND MF5027) | ||
==Dear Mr. Pierce:== | ==Dear Mr. Pierce:== | ||
The U.S. Nuclear Regulatory Commission (NRC or the Commission) has issued the enclosed Amendment No. 279 to Renewed Facility Operating License No. DPR-57 and Amendment No. 223 to Renewed Facility Operating License No. NPF-5 for the Edwin I. Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2, respectively. | |||
The amendments consist of changes to the Technical Specifications (TSs) in response to your application dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016. The amendments revise Technical Specifications (TSs) by adopting 18 previously NRG-approved Technical Specifications Task Force (TSTF) travelers, two TSTF T-travelers, and one feature of the Improved Standard Technical Specifications (ISTS) not associated with a traveler. | The U.S. Nuclear Regulatory Commission (NRC or the Commission) has issued the enclosed Amendment No. 279 to Renewed Facility Operating License No. DPR-57 and Amendment No. 223 to Renewed Facility Operating License No. NPF-5 for the Edwin I. Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2, respectively. The amendments consist of changes to the Technical Specifications (TSs) in response to your application dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016. | ||
Southern Nuclear Operating Company, Inc. (SNC) stated that these changes would increase the consistency between the HNP TSs, the ISTS for Boiling Water Reactor/4 plants (NUREG-1433), and the TSs of the other plants in the SNC fleet. | The amendments revise Technical Specifications (TSs) by adopting 18 previously NRG-approved Technical Specifications Task Force (TSTF) travelers, two TSTF T-travelers, and one feature of the Improved Standard Technical Specifications (ISTS) not associated with a traveler. Southern Nuclear Operating Company, Inc. (SNC) stated that these changes would increase the consistency between the HNP TSs, the ISTS for Boiling Water Reactor/4 plants (NUREG-1433), and the TSs of the other plants in the SNC fleet. | ||
C.R. Pierce A copy of the related Safety Evaluation is also enclosed. | |||
Notice of Issuance will be included in the Commission's biweekly Federal Register notice. Docket Nos. 50-321 and 50-366 | C.R. Pierce A copy of the related Safety Evaluation is also enclosed. Notice of Issuance will be included in the Commission's biweekly Federal Register notice. | ||
Michael D. Orenak, Project Manager Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Docket Nos. 50-321 and 50-366 | |||
==Enclosures:== | ==Enclosures:== | ||
: 1. Amendment No. 279 to DPR-57 2. Amendment No. 223 to NPF-5 3. Safety Evaluation cc w/enclosures: | : 1. Amendment No. 279 to DPR-57 | ||
Distribution via Listserv | : 2. Amendment No. 223 to NPF-5 | ||
Renewed Facility Operating License No. DPR-57 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 1 | : 3. Safety Evaluation cc w/enclosures: Distribution via Listserv | ||
: 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-57 is hereby amended to read as follows: (2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 279, are hereby incorporated in the license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance. | |||
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. | |||
GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-321 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 279 Renewed License No. DPR-57 | |||
: 1. The Nuclear Regulatory Commission (the Commission) has found that: | |||
A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 1 (the facility) Renewed Facility Operating License No. DPR-57 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 1 | |||
E. The issuance of this amendment is in accordance with 1O CFR Part 51 of the Commission's regulations and all applicable requirements have been satisfied. | |||
: 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-57 is hereby amended to read as follows: | |||
(2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 279, are hereby incorporated in the license. | |||
Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. | |||
: 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance. | |||
FOR THE NUCLEAR REGULATORY COMMISSION | |||
~~~ | |||
Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation | |||
==Attachment:== | ==Attachment:== | ||
Changes to Renewed DPR-57 and Technical Specifications Date of Issuance: | Changes to Renewed DPR-57 and Technical Specifications Date of Issuance: Septanber '29, 2016 | ||
Septanber | |||
'29, 2016 | ATTACHMENT TO LICENSE AMENDMENT NO. 279 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 RENEWED FACILITY OPERATING LICENSE NO. DPR-57 DOCKET NO. 50-321 Replace the following pages of the License and the Appendix A, Technical Specifications (TSs), | ||
with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. | |||
Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-2 1.3-2 1.3-6 1.3-6 1.3-7 1.3-7 1.4-1 1.4-1 1.4-2 1.4-2 1.4-3 1.4-3 1.4-5 1.4-5 1.4-6 1.4-7 3.1-10 3.1-10 3.1-17 3.1-17 3.3-4 3.3-4 3.3-5 3.3-5 3.3-7 3.3-7 3.3-16 3.3-16 3.3-25 3.3-25 3.3-48 3.3-48 3.3-49 3.3-49 3.3-50 3.3-50 3.3-51 3.3-51 3.3-52 3.3-52 3.3-53 3.3-53 3.3-54 3.3-54 3.3-55 3.3-55a 3.3-55b 3.5-1 3.5-1 3.5-2 3.5-2 3.6-8 3.6-8 3.6-9 3.6-9 3.6-11 3.6-11 | |||
3.6-22 3.6-22 3.6-23 3.6-23 3.6-35 3.6-35 3.6-36 3.6-36 3.6-37 3.6-37 3.6-38 3.6-38 3.6-39 3.6-39 3.6-40 3.6-40 3.8-2 3.8-2 3.8-4 3.8-4 3.8-10 3.8-10 3.8-11 3.8-11 3.8-12 3.8-12 3.8-13 3.8-13 3.8-14 3.8-14 3.8-15 3.8-15 3.8-16 3.8-16 3.8-17 3.8-17 3.8-18 3.8-18 3.8-29 3.8-29 3.8-30 3.8-30 3.8-37 3.8-37 5.0-9 5.0-9 5.0-10 5.0-10 5.0-13 5.0-13 5.0-14 5.0-14 5.0-15 5.0-15 | |||
for sample analysis or instrumentation calibration, or associated with radioactive apparatus or components; (6) Southern Nuclear, pursuant to the Act and 10 CFR Parts 30 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility. | |||
(C) This renewed license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations in 10 CFR Chapter I; Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions specified or incorporated below: | |||
(1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2804 megawatts thermal. | |||
(2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Plan (Appendix B), as revised through Amendment No. 279 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. | |||
The Surveillance Requirement (SR) contained in the Technical Specifications and listed below, is not required to be performed immediately upon implementation of Amendment No. 195. The SR listed below shall be successfully demonstrated before the time and condition specified: | |||
SR 3.8.1.18 shall be successfully demonstrated at its next regularly scheduled performance. | SR 3.8.1.18 shall be successfully demonstrated at its next regularly scheduled performance. | ||
(3) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained in the updated Fire Hazards Analysis and Fire Protection Program for the Edwin I. Hatch Nuclear Plant, Units 1 and 2, which was originally submitted by letter dated July 22, 1986. Southern Nuclear may make changes to the fire protection program without prior Commission approval only if the changes Renewed License No. DPR-57 Amendment No. 279 Completion Times 1.3 1.3 Completion Times DESCRIPTION | (3) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained in the updated Fire Hazards Analysis and Fire Protection Program for the Edwin I. Hatch Nuclear Plant, Units 1 and 2, which was originally submitted by letter dated July 22, 1986. Southern Nuclear may make changes to the fire protection program without prior Commission approval only if the changes Renewed License No. DPR-57 Amendment No. 279 | ||
The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either: a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours; or b. The stated Completion Time as measured from discovery of the subsequent inoperability. | Completion Times 1.3 1.3 Completion Times DESCRIPTION a. Must exist concurrent with the first inoperability; and (continued) | ||
The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. | : b. Must remain inoperable or not within limits after the first inoperability is resolved. | ||
These exceptions are stated in individual Specifications. | The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either: | ||
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery | : a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours; or | ||
... " 1.3-2 | : b. The stated Completion Time as measured from discovery of the subsequent inoperability. | ||
Amendment No. 279 1.3 Completion Times EXAMPLES | The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications. | ||
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery ... " | |||
B. One Function Y | (continued) | ||
HATCH UNIT 1 1.3-2 Amendment No. 279 | |||
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued) | |||
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X A.1 Restore 7 days subsystem Function X inoperable. subsystem to OPERABLE status. | |||
When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. | B. One Function Y B.1 Restore 72 hours subsystem Function Y inoperable. subsystem to OPERABLE status. | ||
The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered). | C. One Function X C.1 Restore 72 hours subsystem Function X inoperable. subsystem to OPERABLE AND status. | ||
If Required Action C.2 is completed within the specified Completion Time, Conditions Band C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A). It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. (continued) 1.3-7 Amendment No. 279 Frequency 1.4 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE | One Function Y OR subsystem inoperable. C.2 Restore 72 hours Function Y subsystem to OPERABLE status. | ||
Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Limiting Conditions 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. | (continued) | ||
The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements. | HATCH UNIT 1 1.3-6 Amendment No. 279 | ||
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. 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. | Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued) | ||
With an SR satisfied, SR 3.0.4 imposes no restriction. | When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered). | ||
The use of "met" or "performed" in these instances conveys specific meanings. | If Required Action C.2 is completed within the specified Completion Time, Conditions Band C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A). | ||
A Surveillance is "met" only when the acceptance criteria are satisfied. | It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. | ||
Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. | (continued) | ||
Some surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. | HATCH UNIT 1 1.3-7 Amendment No. 279 | ||
For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: (continued) 1.4-1 Amendment No. 279 1.4 | |||
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. | |||
The following examples illustrate the various ways that Frequencies are specified. | DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Limiting Conditions for Operation (LCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the SR. | ||
In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3. EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours) during which the associated Surveillance must be performed at least one time. Performance of the Surveillance initiates the subsequent interval. | The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Surveillance Requirement (SR) | ||
Although the Frequency is stated as 12 hours, 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. | Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements. | ||
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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable. (continued) 1.4-2 Amendment No. 279 1.4 Frequency EXAMPLES | Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. | ||
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. | |||
The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable. | The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. Some surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: | ||
EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE Verify flow is within limits. | (continued) | ||
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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level < 25% RTP to<::: 25% RTP, the Surveillance must be performed within 12 hours. 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 extension allowed by SR 3.0.2. "Thereafter" indicates 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). | HATCH UNIT 1 1.4-1 Amendment No. 279 | ||
If reactor power decreases to < 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP. (continued) 1.4-3 Amendment No. 279 1.4 Frequency EXAMPLES | |||
Frequency 1.4 1.4 Frequency DESCRIPTION a. The Surveillance is not required to be met in the MODE or other (continued) specified condition to be entered; or | |||
------------------------------N()TE--------------------------- | : b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or | ||
()n ly required to be met in M()DE 1. Verify leakage rates are within limits. | : c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed. | ||
Therefore, if the Surveillance were not performed within the 24 hour (plus the extension allowed by SR 3.0.2) interval, but the unit was not in M()DE 1, there would be no failure of the SR nor failure to meet the LC(). Therefore, no violation of SR 3.0.4 occurs when changing M()DES, even with the 24 hour Frequency exceeded, provided the M()DE change was not made into M()DE 1. Prior to entering M()DE 1 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations. | ||
------------------------------N()TE--------------------------- | EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3. | ||
()nly required to be performed in M()DE 1. Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assigned Applicability of the associated LC()) between performances. (continued) 1.4-5 Amendment No. 279 1.4 Frequency EXAMPLES | EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours) 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 hours, 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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable. | ||
(continued) | |||
The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1. Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. | HATCH UNIT 1 1.4-2 Amendment No. 279 | ||
If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------NOTE--------------------------- | Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-1 (continued) | ||
Not required to be met in MODE 3. Verify parameter is within limits. 24 hours Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. | If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable. | ||
Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued) 1.4-6 Amendment No. 279 1.4 Frequency EXAMPLES | EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits. Once within 12 hours after | ||
<:: 25% RTP 24 hours 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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level | |||
< 25% RTP to<::: 25% RTP, the Surveillance must be performed within 12 hours. | |||
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 extension allowed by SR 3.0.2. | |||
"Thereafter" indicates 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 reactor power decreases to | |||
< 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP. | |||
(continued) | |||
HATCH UNIT 1 1.4-3 Amendment No. 279 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-4 (continued) | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------N()TE--------------------------- | |||
()n ly required to be met in M()DE 1. | |||
Verify leakage rates are within limits. 24 hours Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in M()DE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour (plus the extension allowed by SR 3.0.2) interval, but the unit was not in M()DE 1, there would be no failure of the SR nor failure to meet the LC(). Therefore, no violation of SR 3.0.4 occurs when changing M()DES, even with the 24 hour Frequency exceeded, provided the M()DE change was not made into M()DE 1. Prior to entering M()DE 1 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. | |||
EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------N()TE--------------------------- | |||
()nly required to be performed in M()DE 1. | |||
Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assigned Applicability of the associated LC()) between performances. | |||
(continued) | |||
HATCH UNIT 1 1.4-5 Amendment No. 279 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-5 (continued) | |||
As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. | |||
Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1. | |||
Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. | |||
EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------NOTE--------------------------- | |||
Not required to be met in MODE 3. | |||
Verify parameter is within limits. 24 hours Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued) | |||
HATCH UNIT 1 1.4-6 Amendment No. 279 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-6 (continued) violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. | |||
HATCH UNIT 1 1.4-7 Amendment No. 279 | |||
Control Rod Scram Times 3.1.4 SURVEILLANCE REQUIREMENTS | |||
-----------------------------------------------------------N 0 TE------------------------------------------------------------ | -----------------------------------------------------------N 0 TE------------------------------------------------------------ | ||
0 | 0 uring single control rod scram time Surveillances, the control rod drive (CRD) pumps shall be isolated from the associated scram accumulator. | ||
SR 3.1.4.1 | SURVEILLANCE FREQUENCY SR 3.1.4.1 Verify each control rod scram time is within the Prior to exceeding limits of Table 3.1.4-1 with reactor steam dome 40% RTP after each pressure<::: 800 psig. reactor shutdown | ||
800 psig. Verify, for a representative sample, each tested control rod scram time is within the limits of Table 3.1.4-1 with reactor steam dome pressure <::: 800 psig. | <:: 120 days SR 3.1.4.2 Verify, for a representative sample, each tested In accordance with control rod scram time is within the limits of the Surveillance Table 3.1.4-1 with reactor steam dome pressure Frequency Control | ||
<::: 800 psig. Program SR 3.1.4.3 Verify each affected control rod scram time is Prior to declaring within the limits of Table 3.1.4-1 with any reactor control rod steam dome pressure. OPERABLE after work on control rod or CRD System that could affect scram time SR 3.1.4.4 Verify each affected control rod scram time is Prior to exceeding within the limits of Table 3.1.4-1 with reactor 40% RTP after fuel steam dome pressure<::: 800 psig. movement within the affected core cell Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time HATCH UNIT 1 3.1-10 Amendment No. 279 | |||
800 psig. | |||
APPLICABILITY: | SLC System 3.1.7 3.1 REACTIVITY CONTROL SYSTEMS 3.1.7 Standby Liquid Control (SLC) System LCO 3.1.7 Two SLC subsystems shall be OPERABLE. | ||
MODES 1 and 2. ACTIONS CONDITION REQUIRED ACTION A. Sodium pentaborate A.1 Restore sodium solution not within pentaborate solution to Region A limits of within Region A limits. Figure 3.1.7-1 or 3.1.7-2, but within the Region B limits. B. One SLC subsystem B.1 Restore SLC inoperable for reasons subsystem to other than Condition A. OPERABLE status. C. Two SLC subsystems C.1 Restore one SLC inoperable for reasons subsystem to other than Condition A. OPERABLE status. D. Required Action and D.1 Be in MODE 3. associated Completion Time not met. HATCH UNIT 1 3.1-17 | APPLICABILITY: MODES 1 and 2. | ||
SR 3.3.1.1.2 | ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Sodium pentaborate A.1 Restore sodium 72 hours solution not within pentaborate solution to Region A limits of within Region A limits. | ||
------------------------------ | Figure 3.1.7-1 or 3.1.7-2, but within the Region B limits. | ||
N ot required to be performed until 12 hours after THERMAL 24% RTP. Verify the absolute difference between the average power range monitor (APRM) channels and the calculated power is s 2% RTP while operating 24% RTP. | B. One SLC subsystem B.1 Restore SLC 7 days inoperable for reasons subsystem to other than Condition A. OPERABLE status. | ||
N ot required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. Perform CHANNEL FUNCTIONAL TEST. | C. Two SLC subsystems C.1 Restore one SLC 8 hours inoperable for reasons subsystem to other than Condition A. OPERABLE status. | ||
D. Required Action and D.1 Be in MODE 3. 12 hours associated Completion Time not met. | |||
HATCH UNIT 1 3.1-17 Amendment No. 279 | |||
SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. SR 3.3.1.1.10 | |||
----------------------------NOTE------------------------------ | RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued) | ||
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. ------------------------------------------------------------------ | SURVEILLANCE FREQUENCY SR 3.3.1.1.2 ------------------------------N 0 TE---------------------------- | ||
Perform CHANNEL FUNCTIONAL TEST. SR 3.3.1.1.11 Verify Turbine Stop Valve -Closure and Turbine Control Valve Fast Closure, Trip Oil Pressure -Low Functions are not bypassed when THERMAL POWER 27.6% RTP. SR 3.3.1.1.12 Perform CHANNEL FUNCTIONAL TEST. | N ot required to be performed until 12 hours after THERMAL POWER~ 24% RTP. | ||
Verify the absolute difference between the In accordance with average power range monitor (APRM) channels the Surveillance and the calculated power is s 2% RTP while Frequency Control operating at~ 24% RTP. Program SR 3.3.1.1.3 (Not used.) | |||
SR 3.3.1.1.4 ----------------------------N 0 TE------------------------------ | |||
N ot required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. | |||
HATCH UNIT 1 3.3- | Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.5 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.6 (Not used.) | ||
(continued) | |||
HATCH UNIT 1 3.3-4 Amendment No. 279 | |||
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued) | |||
SURVEILLANCE FREQUENCY SR 3.3.1.1.7 (Not used.) | |||
SR 3.3.1.1.8 Calibrate the local power range monitors. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.10 ----------------------------NOTE------------------------------ | |||
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. | |||
------------------------------------------------------------------ | |||
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.11 Verify Turbine Stop Valve - Closure and In accordance with Turbine Control Valve Fast Closure, Trip Oil the Surveillance Pressure - Low Functions are not bypassed Frequency Control when THERMAL POWER is~ 27.6% RTP. Program SR 3.3.1.1.12 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program (cont1 n ued) | |||
HATCH UNIT 1 3.3-5 Amendment No. 279 | |||
RPS Instrumentation 3.3.1.1 Table 3.3.1.1-1(page1 of3) | |||
: 2. Separate Condition entry is allowed for each channel. CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A.1 Place channel in trip. 12 hours for channels inoperable. | Reactor Protection System Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION D.1 REQUIREMENTS VALUE | ||
Functions 2.a, 2.b, 6.b, 7.a, and 7.b AND 24 hours for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b B. -------------- | : 1. Intermediate Range Monitor | ||
: a. Neutron Flux - High 2 2(d) G SR 3.3.1.1.1 ::; 120/125 SR 3.3.1.1.4 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.1 ::; 120/125 SR 3.3.1.1.5 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 | |||
: b. lnop 2 2(d) G SR 3.3.1.1.4 NA SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.5 NA SR 3.3.1.1.15 | |||
: 2. Average Power Range Monitor | |||
: a. Neutron Flux - High 2 3(c) G SR 3.3.1.1.1 => 20% RTP (Setdown) SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13 | |||
: b. Simulated Thermal 3(c) F SR 3.3.1.1.1 => 0.57W+ | |||
Power- High SR 3.3.1.1.2 56.8% RTP SR 3.3.1.1.8 and SR 3.3.1.1.10 :>115.5% | |||
SR 3.3.1.1.13 RTP(b) | |||
: c. Neutron Flux - High 3(c) F SR 3.3.1.1.1 s 120% RTP SR 3.3.1.1.2 SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13 | |||
: d. lnop 1, 2 3(c) G SR 3.3.1.1.10 NA continued (a) With any control rod withdrawn from a core cell containing one or more fuel assemblies. | |||
(b) 0.57W + 56.8% - 0.57 tiW RTP when reset for single loop operation per LCO 3.4.1, "Recirculation Loops Operating." | |||
(c) Each APRM channel provides inputs to both trip systems. | |||
(d) One channel in each quadrant of the core must be OPERABLE whenever the IRMs are required to be OPERABLE. Both the RWM and a second licensed operator must verify compliance with the withdrawal sequence when less than three channels in any trip system are OPERABLE. | |||
HATCH UNIT 1 3.3-7 Amendment No. 279 | |||
Control Rod Block Instrumentation 3.3.2.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2.1.2 Verify by administrative Immediately methods that startup with RWM inoperable has not been performed in the last 12 months. | |||
AND C.2.2 Verify movement of During control rod control rods is in movement compliance with banked position withdrawal sequence (BPWS) by a second licensed operator or other qualified member of the technical staff. | |||
D. RWM inoperable during D.1 Verify movement of During control rod reactor shutdown. control rods is in movement compliance with BPWS by a second licensed operator or other qualified member of the technical staff. | |||
E. One or more Reactor Mode E.1 Suspend control rod Immediately Switch - Shutdown Position withdrawal. | |||
channels inoperable. | |||
AND E.2 Initiate action to fully Immediately insert all insertable control rods in core cells containing one or more fuel assemblies. | |||
HATCH UNIT 1 3.3-16 Amendment No. 279 | |||
PAM Instrumentation 3.3.3.1 Table 3.3.3.1-1(page1of1) | |||
Post Accident Monitoring Instrumentation CONDITIONS REFERENCED REQUIRED FROM REQUIRED FUNCTION CHANNELS ACTION D.1 | |||
: 1. Reactor Steam Dome Pressure 2 E | |||
: 2. Reactor Vessel Water Level | |||
: a. -317 inches to -17 inches 2 E | |||
: b. -150 inches to +60 inches 2 E | |||
: c. 0 inches to +60 inches 2 E | |||
: d. 0 inches to +400 inches 1 NA | |||
: 3. Suppression Pool Water Level | |||
: a. 0 inches to 300 inches 2 E | |||
: b. 133 inches to 163 inches 2 E | |||
: 4. Drywell Pressure | |||
: a. -1 O psig to +90 psig 2 E | |||
: b. -5 psig to +5 psig 2 E C. 0 psig to +250 psig 2 E | |||
: 5. Drywell Area Radiation (High Range) 2 F | |||
: 6. Penetration Flow Path Primary Containment Isolation 2 per penetration flow E Valve Position path (a)(b) | |||
: 7. (Deleted) | |||
: 8. (Deleted) 2(C) E | |||
: 9. Suppression Pool Water Temperature 6 E | |||
: 10. Drywell Temperature in Vicinity of Reactor Level Instrument Reference Leg | |||
: 11. Diesel Generator (DG) Parameters 1 per DG NA | |||
: a. Output Voltage 1 per DG NA | |||
: b. Output Current 1 per DG NA | |||
: c. Output Power 1 per DG NA | |||
: d. Battery Voltage 2 E | |||
: 12. RHR Service Water Flow (a) Not required for isolation valves whose associated penetration flow path is isolated by at least one closed and deactivated automatic valve, closed manual valve, blind flange, or check valve with flow through the valve secured. | |||
(b) Only one position indication channel is required for penetration flow paths with only one installed control room indication channel. | |||
(c) Monitoring each of four quadrants. | |||
HATCH UNIT 1 3.3-25 Amendment No. 279 | |||
Primary Containment Isolation Instrumentation 3.3.6.1 3.3 INSTRUMENTATION 3.3.6.1 Primary Containment Isolation Instrumentation LCO 3.3.6.1 The primary containment isolation instrumentation for each Function in Table 3.3.6.1-1 shall be OPERABLE. | |||
APPLICABILITY: According to Table 3.3.6.1-1. | |||
ACTIONS | |||
----------------------------------------------------------N 0 TES----------------------------------------------------------- | |||
: 1. Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls. | |||
: 2. Separate Condition entry is allowed for each channel. | |||
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A.1 Place channel in trip. 12 hours for channels inoperable. Functions 2.a, 2.b, 6.b, 7.a, and 7.b AND 24 hours for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b B. ---------------N 0 TE------------- B.1 Restore isolation 1 hour Not applicable for capability. | |||
Function 5.c. | |||
------------------------------------ | |||
One or more automatic Functions with isolation capability not maintained. | One or more automatic Functions with isolation capability not maintained. | ||
C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel. (continued) | C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel. | ||
HATCH UNIT 1 3.3-48 Amendment No. 279 ACTIONS (continued) | (continued) | ||
CONDITION D. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | HATCH UNIT 1 3.3-48 Amendment No. 279 | ||
E. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | |||
F. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued) | ||
G. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | CONDITION REQUIRED ACTION COMPLETION TIME D. As required by Required D.1 Isolate associated main 12 hours Action C.1 and referenced steam line (MSL). | ||
H. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | in Table 3.3.6.1-1. | ||
OR Required Action and associated Completion Time of Condition F or G not met. HATCH UNIT 1 | OR D.2.1 Be in MODE 3. 12 hours AND D.2.2 Be in MODE4. 36 hours E. As required by Required E.1 Be in MODE 2. 6 hours Action C.1 and referenced in Table 3.3.6.1-1. | ||
CONDITION I. As required by Required 1.1 Action C.1 and referenced in Table 3.3.6.1-1. | F. As required by Required F.1 Isolate the affected 1 hour Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s). | ||
OR 1.2 J. As required by Required J.1 Action C.1 and referenced in Table 3.3.6.1-1. | G. As required by Required G.1 Isolate the affected 24 hours Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s). | ||
OR J.2 | H. As required by Required H.1 Be in MODE 3. 12 hours Action C.1 and referenced in Table 3.3.6.1-1. AND OR H.2 Be in MODE 4. 36 hours Required Action and associated Completion Time of Condition F or G not met. | ||
(continued) | |||
: 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function. | HATCH UNIT 1 3.3-49 Amendment No. 279 | ||
: 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours provided the associated Function maintains isolation capability. | |||
SURVEILLANCE SR 3.3.6.1.1 Perform CHANNEL CHECK. | Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued) | ||
Amendment No. 279 Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued) | CONDITION REQUIRED ACTION COMPLETION TIME I. As required by Required 1.1 Declare Standby Liquid 1 hour Action C.1 and referenced Control (SLC) System in Table 3.3.6.1-1. inoperable. | ||
SURVEILLANCE SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. | OR 1.2 Isolate the Reactor 1 hour Water Cleanup (RWCU) System. | ||
SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. | J. As required by Required J.1 Initiate action to restore Immediately Action C.1 and referenced channel to OPERABLE in Table 3.3.6.1-1. status. | ||
SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. | OR J.2 Initiate action to isolate Immediately the Residual Heat Removal (RHR) | ||
SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. HATCH UNIT 1 3.3-51 | Shutdown Cooling System. | ||
: a. Reactor Vessel Water Level -1,2,3 2 D SR 3.3.6.1.1 | SURVEILLANCE REQUIREMENTS | ||
<: -113 inches Low Low Low, Level 1 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ----------------------------------------------------------N 0 TES----------------------------------------------------------- | ||
: b. Main Steam Line Pressure -2 E SR 3.3.6.1.3 | : 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function. | ||
<= 825 psig Low SR 3.3.6.1.6 | : 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours provided the associated Function maintains isolation capability. | ||
: c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 | SURVEILLANCE FREQUENCY SR 3.3.6.1.1 Perform CHANNEL CHECK. In accordance with the Surveillance Frequency Control Program (continued) | ||
::; 138% rated Flow-High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | HATCH UNIT 1 3.3-50 Amendment No. 279 | ||
: d. Condenser Vacuum -Low 1, 2 D SR 3.3.6.1.3 | |||
<: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 | Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued) | ||
:5194°F Temperature | SURVEILLANCE FREQUENCY SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program HATCH UNIT 1 3.3-51 Amendment No. 279 I | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 1 of 5) | ||
::; 200°F Temperature | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | : 1. Main Steam Line Isolation | ||
: a. Reactor Vessel Water Level - 1,2,3 2 D SR 3.3.6.1.1 <: -113 inches Low Low Low, Level 1 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: b. Main Steam Line Pressure - 2 E SR 3.3.6.1.3 <= 825 psig Low SR 3.3.6.1.6 | |||
: c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 ::; 138% rated Flow- High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: d. Condenser Vacuum - Low 1, 2 D SR 3.3.6.1.3 <: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum | |||
: e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 :5194°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 ::; 200°F Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 2. Primary Containment Isolation | : 2. Primary Containment Isolation | ||
: a. Reactor Vessel Water Level 1,2,3 2 H SR 3.3.6.1.1 | : a. Reactor Vessel Water Level 1,2,3 2 H SR 3.3.6.1.1 <: 0 inches | ||
<: 0 inches -Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. Drywell Pressure -High 1,2,3 2 H SR 3.3.6.1.1 | : b. Drywell Pressure - High 1,2,3 2 H SR 3.3.6.1.1 ::; 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed. | ||
::; 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed. (b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels. | (b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels. | ||
HATCH UNIT 1 3.3-52 Amendment No. 279 Primary Containment Isolation Instrumentation 3.3.6.1 Table3.3.6.1-1 (page2of5) | HATCH UNIT 1 3.3-52 Amendment No. 279 | ||
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 2. Primary Containment Isolation (continued) | |||
C. Drywell Radiation | Primary Containment Isolation Instrumentation 3.3.6.1 Table3.3.6.1-1 (page2of5) | ||
-1,2,3 F SR 3.3.6.1.1 s 138 R/hr High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
: d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation | : 2. Primary Containment Isolation (continued) | ||
-High SR 3.3.6.1.3 SR 3.3.6.1.6 | C. Drywell Radiation - 1,2,3 F SR 3.3.6.1.1 s 138 R/hr High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: e. Refueling Floor Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation | : d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6 | ||
-High SR 3.3.6.1.3 SR 3.3.6.1.6 | : e. Refueling Floor Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6 | ||
: 3. High Pressure Coolant Injection (HPCI) System Isolation | : 3. High Pressure Coolant Injection (HPCI) System Isolation | ||
: a. HPCI Steam Line Flow -1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | : a. HPCI Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 | : b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 <! 100 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
<! 100 psig Pressure -Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure -High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: d. Drywell Pressure -High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : e. HPCI Pipe Penetration Roorr 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: e. HPCI Pipe Penetration Roorr 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature | : f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 s 169°F Ambient Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 1 3.3-53 Amendment No. 279 | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 s 169°F Ambient Temperature | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 3 of 5) | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 1 3.3-53 Amendment No. 279 Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 3 of 5) Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 3. HPCI System Isolation (continued) | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
: g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 | : 3. HPCI System Isolation (continued) | ||
:;; 16 minutes Temperature | : g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :;; 16 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays | ||
-Time Delay SR 3.3.6.1.6 15 seconds Relays h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 | : h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 :;; 42°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:;; 42°F Differential Temperature | : i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :;; 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 | |||
:;; 169°F Temperature | |||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 4. Reactor Core Isolation Cooling (RCIC) System Isolation | : 4. Reactor Core Isolation Cooling (RCIC) System Isolation | ||
: a. RCIC Steam Line Flow -1,2,3 F SR 3.3.6.1.1 | : a. RCIC Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 :;; 306% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:;; 306% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 2! 60 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 :;; 20 psig Diaphragm Pressure - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 2! 60 psig Pressure -Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 | : d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 :;; 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:;; 20 psig Diaphragm Pressure -SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | : e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :;; 169°F Ambient Area SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: d. Drywell Pressure -High 1,2,3 F SR 3.3.6.1.1 | : f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :;; 31 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays continued HATCH UNIT 1 3.3-54 Amendment No. 279 | ||
:;; 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5) | ||
:;; 169°F Ambient Area SR 3.3.6.1.2 Temperature | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | : 4. RCIC System Isolation (continued) | ||
: f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 | : g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :S 42°F Area Differential SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:;; 31 minutes Temperature | : h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :S 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-Time Delay SR 3.3.6.1.6 15 seconds Relays continued HATCH UNIT 1 3.3-54 Amendment No. 279 Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5) Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 4. RCIC System Isolation (continued) | |||
: g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 | |||
:S 42°F Area Differential SR 3.3.6.1.2 Temperature | |||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 | |||
:S 169°F Temperature | |||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 5. RWCU System Isolation | : 5. RWCU System Isolation | ||
: a. Area Temperature | : a. Area Temperature - High 1,2,3 1 per area F SR 3.3.6.1.1 :S 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-High 1,2,3 1 per area F SR 3.3.6.1.1 | : b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 :S 67°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:S 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : c. SLC System Initiation 1,2 1(C) SR 3.3.6.1.6 NA | ||
: b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 | : d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 <: -47 inches Level - Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:S 67°F Differential Temperature | |||
-SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: c. SLC System Initiation 1,2 1(C) SR 3.3.6.1.6 NA d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 | |||
<: -47 inches Level -Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 6. RHR Shutdown Cooling System Isolation | : 6. RHR Shutdown Cooling System Isolation | ||
: a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 | : a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 :S 145 psig Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:S 145 psig Pressure -High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. Reactor Vessel Water 3,4,5 2 (d) J SR 3.3.6.1.1 <: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continued) | ||
: b. Reactor Vessel Water 3,4,5 2 (d) J SR 3.3.6.1.1 | (c) SLC System Initiation only inputs into one of the two trip systems. | ||
<: 0 inches Level -Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continued) (c) SLC System Initiation only inputs into one of the two trip systems. (d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained. | (d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained. | ||
HATCH UNIT 1 3.3-55a Amendment No. 279 | HATCH UNIT 1 3.3-55a Amendment No. 279 | ||
APPLICABILITY: | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 5 of 5) | ||
MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig. ACTIONS ----------------------------------------------------------N 0 TE------------------------------------------------------------- | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
: 7. Traversing lncore Probe System Isolation | |||
subsystem(s) to OPERABLE status. OR One LPCI pump in both LPCI subsystems inoperable. | : a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 2! 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
B. Required Action and B.1 Be in MODE 3. 12 hours associated Completion Time of Condition A not AND met. B.2 Be in MODE 4. 36 hours (continued) | : b. Drywell Pressure - High 1,2,3 2 G SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 HATCH UNIT 1 3.3-55b Amendment No. 279 | ||
HATCH UNIT 1 3.5-1 Amendment No. 279 ACTIONS (continued) | |||
CONDITION C. HPCI System inoperable. | ECCS - Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.1 ECCS - Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic Depressurization System (ADS) function of six of seven safety/relief valves shall be OPERABLE. | ||
APPLICABILITY: MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig. | |||
AND | ACTIONS | ||
OR | ----------------------------------------------------------N 0 TE------------------------------------------------------------- | ||
LCO 3.0.4.b is not applicable to HPCI. | |||
AND | CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable. subsystem(s) to OPERABLE status. | ||
A.2 ------------N 0 TES----------- | OR One LPCI pump in both LPCI subsystems inoperable. | ||
: 1. Isolation devices in high radiation areas may be verified by use of administrative means. 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. -------------------------------- | B. Required Action and B.1 Be in MODE 3. 12 hours associated Completion Time of Condition A not AND met. | ||
Verify the affected penetration flow path is isolated. | B.2 Be in MODE 4. 36 hours (continued) | ||
HATCH UNIT 1 3.5-1 Amendment No. 279 | |||
B.1 Isolate the affected Only applicable to penetration flow path by penetration flow paths with use of at least one two PCIVs. closed and de-activated | |||
------------------------------------ | ECCS - Operating 3.5.1 ACTIONS (continued) | ||
automatic valve, closed manual valve, or blind One or more penetration flange. flow paths with two PCIVs inoperable except due to leakage not within limit. HATCH UNIT 1 3.6-8 PC | CONDITION REQUIRED ACTION COMPLETION TIME C. HPCI System inoperable. C.1 Verify by administrative 1 hour means RCIC System is OPERABLE. | ||
AND C.2 Restore HPCI System 14 days to OPERABLE status. | |||
D. HPCI System inoperable. D.1 Restore HPCI System 72 hours to OPERABLE status. | |||
AND OR Condition A entered. | |||
D.2 Restore low pressure 72 hours ECCS injection/spray subsystem to OPERABLE status. | |||
E. Two or more ADS valves E.1 Be in MODE 3. 12 hours inoperable. | |||
AND OR E.2 Reduce reactor steam 36 hours Required Action and dome pressure to associated Completion =:;; 150 psig. | |||
Time of Condition C or D not met. | |||
F. Two or more low pressure F.1 Enter LCO 3.0.3. Immediately ECCS injection/spray subsystems inoperable for reasons other than Condition A. | |||
SR 3.6.1.3. | OR HPCI System and two or more ADS valves inoperable. | ||
-------------------------- | HATCH UNIT 1 3.5-2 Amendment No. 279 | ||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. 2. Not required to be met for PCIVs that are open under administrative controls. | |||
Verify each primary containment isolation | PC IVs 3.6.1.3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) A.2 ------------N 0 TES----------- | ||
: 1. Isolation devices in high radiation areas may be verified by use of administrative means. | |||
: 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | |||
-------------------------------- | |||
Verify the affected Once per 31 days for penetration flow path is isolation devices isolated. outside primary containment AND Prior to entering MODE 2 or 3 from MODE 4 if primary containment was de-inerted while in MODE 4, if not performed within the previous 92 days, for isolation devices inside primary containment B. -------------N 0 TE--------------- B.1 Isolate the affected 1 hour Only applicable to penetration flow path by penetration flow paths with use of at least one two PCIVs. closed and de-activated | |||
------------------------------------ automatic valve, closed manual valve, or blind One or more penetration flange. | |||
flow paths with two PCIVs inoperable except due to leakage not within limit. | |||
(continued) | |||
HATCH UNIT 1 3.6-8 Amendment No. 279 | |||
PC IVs 3.6.1.3 ACTIONS (continued) | |||
C.2 | CONDITION REQUIRED ACTION COMPLETION TIME C. ---------------N 0 TE------------- C.1 Isolate the affected 4 hours except for Only applicable to penetration flow path by excess flow check penetration flow paths with use of at least one valve (EFCV) line and only one PCIV. closed and de-activated penetrations with a | ||
Initiate action to suspend OPDRVs. SURVEILLANCE REQUIREMENTS SR 3.6.4.1.1 SR 3.6. | ------------------------------------- automatic valve, closed closed system manual valve, or blind One or more penetration flange. AND flow paths with one PCIV inoperable except due to 72 hours for leakage not within limits. AND EFCV line and penetrations with a C.2 -----------NOTES---------- closed system | ||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | |||
-------------------------------- | |||
Verify the affected Once per 31 days penetration flow path is isolated. | |||
D. One or more penetration D.1 Restore leakage to 4 hours flow paths with leakage not within limit. | |||
within limit. | |||
E. Required Action and E.1 Be in MODE 3. 12 hours associated Completion Time of Condition A, B, C, AND or D not met in MODE 1, 2, or 3. E.2 Be in MODE 4. 36 hours (continued) | |||
HATCH UNIT 1 3.6-9 Amendment No. 279 | |||
PC IVs 3.6.1.3 SURVEILLANCE REQUIREMENTS (continued) | |||
SURVEILLANCE FREQUENCY SR 3.6.1.3.2 ------------------------------N 0 TES--------------------------- | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Not required to be met for PCIVs that are open under administrative controls. | |||
Verify each primary containment isolation manual In accordance with valve and blind flange that is located outside the Surveillance primary containment and not locked, sealed, or Frequency Control otherwise secured and is required to be closed Program during accident conditions is closed. | |||
SR 3.6.1.3.3 -----------------------------N 0 TES---------------------------- | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Not required to be met for PCIVs that are open under administrative controls. | |||
Verify each primary containment manual isolation Prior to entering valve and blind flange that is located inside MODE 2 or 3 from primary containment and not locked, sealed, or MODE 4 if primary otherwise secured and is required to be closed containment was during accident conditions is closed. de-inerted while in MODE 4, if not performed within the previous 92 days SR 3.6.1.3.4 Verify continuity of the traversing incore probe In accordance with (Tl P) shear isolation valve explosive charge. the Surveillance Frequency Control Program SR 3.6.1.3.5 Verify the isolation time of each power operated, In accordance with automatic PCIV, except for MSIVs, is within limits. the lnservice Testing Program (continued) | |||
HATCH UNIT 1 3.6-11 Amendment No. 279 | |||
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and B.1 Reduce THERMAL 12 hours associated Completion POWER until all Time of Condition A not OPERABLE IRM met. channels s 25/40 divisions of full scale on Range 7. | |||
C. Suppression pool average C.1 Suspend all testing that Immediately temperature> 105°F. adds heat to the suppression pool. | |||
AND Any OPERABLE IRM channel > 25/40 divisions of full scale on Range 7. | |||
AND Performing testing that adds heat to the suppression pool. | |||
D. Suppression pool average D.1 Place the reactor mode Immediately temperature> 110°F. switch in the shutdown position. | |||
AND D.2 Determine suppression Once per 30 minutes pool average temperature. | |||
AND D.3 Be in MODE 4. 36 hours (continued) | |||
HATCH UNIT 1 3.6-22 Amendment No. 279 | |||
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME E. Suppression pool average E.1 Depressurize the 12 hours temperature > 120°F. reactor vessel to | |||
< 200 psig. | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.2.1.1 Verify suppression pool average temperature is In accordance with within the applicable limits. the Surveillance Frequency Control Program 5 minutes when performing testing that adds heat to the suppression pool HATCH UNIT 1 3.6-23 Amendment No. 279 | |||
Secondary Containment 3.6.4.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2 Suspend CORE Immediately ALTERATIONS. | |||
AND C.3 Initiate action to Immediately suspend OPDRVs. | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.1.1 Verify all secondary containment equipment In accordance with hatches are closed and sealed. the Surveillance Frequency Control Program SR 3.6.4.1.2 Verify one secondary containment access door in In accordance with each access opening is closed. the Surveillance Frequency Control Program SR 3.6.4.1.3 -----------------------------NOTE----------------------------- | |||
The number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | The number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | ||
Verify secondary containment can be drawn down to 0.20 inch of vacuum water gauge in s 120 seconds using required standby gas treatment (SGT) subsystem(s). | Verify secondary containment can be drawn In accordance with down to ~ 0.20 inch of vacuum water gauge in the Surveillance s 120 seconds using required standby gas Frequency Control treatment (SGT) subsystem(s). Program (continued) | ||
3.6-35 | HATCH UNIT 1 3.6-35 Amendment No. 279 | ||
Amendment No. 279 Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SR 3.6.4.1.4 | |||
-----------------------------N 0 TE------------------------------ | Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.6.4.1.4 -----------------------------N 0 TE------------------------------ | ||
Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | ||
Verify the secondary containment can be In accordance with maintained ;;:: 0.20 inch of vacuum water gauge the Surveillance for 1 hour using required SGT subsystem(s) at Frequency Control a flow rate~ 4000 cfm per subsystem. Program HATCH UNIT 1 3.6-36 Amendment No. 279 | |||
SCI Vs 3.6.4.2 3.6 CONTAINMENT SYSTEMS 3.6.4.2 Secondary Containment Isolation Valves (SCIVs) | |||
LCO 3.6.4.2 Each SCIV shall be OPERABLE. | |||
APPLICABILITY: MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE ALTERATIONS, During operations with a potential for draining the reactor vessel (OPDRVs). | |||
ACTIONS | |||
----------------------------------------------------------NOTES---------- | |||
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies. | ||
5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. | 5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following: | ||
The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. | : a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: | ||
The purpose of the program is to establish the following: | : 1. An API gravity or an absolute specific gravity within limits, | ||
: a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: 1. An API gravity or an absolute specific gravity within limits, 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and 3. A water and sediment content within limits; b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued) | : 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and | ||
HATCH UNIT 1 5.0-13 Amendment No. 279 Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued) | : 3. A water and sediment content within limits; | ||
Safety Function Determination Program (SFDP) This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following: | : b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued) | ||
: a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected; | HATCH UNIT 1 5.0-13 Amendment No. 279 | ||
: b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists; c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and d. Other appropriate limitations and remedial or compensatory actions. A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. | |||
For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable. (continued) | Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued) | ||
HATCH UNIT 1 5.0-14 Amendment No. 279 Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 | : c. Total particulate concentration of the fuel oil is ~ 10 mg/liter when tested every 92 days. | ||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies. | ||
: a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews. b. Licensees may make changes to Bases without prior NRG approval provided the changes do not require either of the following: | 5.5.10 Safety Function Determination Program (SFDP) | ||
: 1. A change in the TS incorporated in the license; or 2. A change to the updated FSAR or Bases that requires NRG approval pursuant to 10 CFR 50.59. c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR. d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRG prior to implementation. | This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following: | ||
Changes to the Bases implemented without prior NRG approval shall be provided to the NRG on a frequency consistent with 10 CFR 50.71(e). (continued) | : a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected; | ||
HATCH UNIT 1 5.0-15 Amendment No. 279 UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF | : b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists; | ||
Renewed Facility Operating License No. NPF-5 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 2 | : c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and | ||
: 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-5 is hereby amended to read as follows: (2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 223 are hereby incorporated in the license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance. | : d. Other appropriate limitations and remedial or compensatory actions. | ||
A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and: | |||
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or | |||
: b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or | |||
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable. | |||
(continued) | |||
HATCH UNIT 1 5.0-14 Amendment No. 279 | |||
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 Safety Function Determination Program (SFDP) (continued) | |||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system. | |||
5.5.11 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications. | |||
: a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews. | |||
: b. Licensees may make changes to Bases without prior NRG approval provided the changes do not require either of the following: | |||
: 1. A change in the TS incorporated in the license; or | |||
: 2. A change to the updated FSAR or Bases that requires NRG approval pursuant to 10 CFR 50.59. | |||
: c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR. | |||
: d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRG prior to implementation. Changes to the Bases implemented without prior NRG approval shall be provided to the NRG on a frequency consistent with 10 CFR 50.71(e). | |||
(continued) | |||
HATCH UNIT 1 5.0-15 Amendment No. 279 | |||
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC. | |||
GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-366 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 223 Renewed License No. NPF-5 | |||
: 1. The Nuclear Regulatory Commission (the Commission) has found that: | |||
A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 2 (the facility) Renewed Facility Operating License No. NPF-5 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 2 | |||
E. The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commission's regulations and all applicable requirements have been satisfied. | |||
: 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-5 is hereby amended to read as follows: | |||
(2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 223 are hereby incorporated in the license. | |||
Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. | |||
: 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance. | |||
FOR THE NUCLEAR REGULATORY COMMISSION Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation | |||
==Attachment:== | ==Attachment:== | ||
Changes to Renewed NPF-5 and Technical Specifications Date of Issuance: | Changes to Renewed NPF-5 and Technical Specifications Date of Issuance: Septenber 29, Xl16 | ||
Septenber 29, Xl16 | |||
The removal of these conditions shall be made by an amendment to the license supported by a favorable evaluation by the Commission. (a) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained 2 The original licensee authorized to possess, use, and operate the facility with Georgia Power Company (GPC). Consequently, certain historical references to GPC remain in certain license conditions. | ATTACHMENT TO LICENSE AMENDMENT NO. 223 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 RENEWED FACILITY OPERATING LICENSE NO. NPF-5 DOCKET NO. 50-366 Replace the following pages of the License and the Appendix A, Technical Specifications (TSs), | ||
Renewed License No. NPF-5 Amendment No. 223 Completion Times 1.3 1.3 Completion Times DESCRIPTION | with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change. | ||
Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-2 1.3-2 1.3-6 1.3-6 1.3-7 1.3-7 1.4-1 1.4-1 1.4-2 1.4-2 1.4-3 1.4-3 1.4-5 1.4-5 1.4-6 1.4-7 3.1-10 3.1-10 3.1-17 3.1-17 3.3-4 3.3-4 3.3-5 3.3-5 3.3-7 3.3-7 3.3-16 3.3-16 3.3-25 3.3-25 3.3-48 3.3-48 3.3-49 3.3-49 3.3-50 3.3-50 3.3-51 3.3-51 3.3-52 3.3-52 3.3-53 3.3-53 3.3-54 3.3-54 3.3-55 3.3-55a 3.3-55b 3.5-1 3.5-1 3.5-2 3.5-2 3.6-8 3.6-8 3.6-9 3.6-9 3.6-11 3.6-11 | |||
The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either: a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours; or b. The stated Completion Time as measured from discovery of the subsequent inoperability. | |||
The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. | 3.6-22 3.6-22 3.6-23 3.6-23 3.6-34 3.6-34 3.6-35 3.6-35 3.6-36 3.6-36 3.6-37 3.6-37 3.6-38 3.6-38 3.6-40 3.6-40 3.8-2 3.8-2 3.8-4 3.8-4 3.8-10 3.8-10 3.8-11 3.8-11 3.8-12 3.8-12 3.8-13 3.8-13 3.8-14 3.8-14 3.8-15 3.8-15 3.8-16 3.8-16 3.8-17 3.8-17 3.8-18 3.8-18 3.8-29 3.8-29 3.8-30 3.8-30 3.8-38 3.8.38 5.0-9 5.0-9 5.0-10 5.0-10 5.0-13 5.0-13 5.0-14 5.0-14 5.0-15 5.0-15 | ||
These exceptions are stated in individual Specifications. | |||
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery | (6) Southern Nuclear, pursuant to the Act and 1O CFR Parts 30 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility. | ||
... " (continued) 1.3-2 Amendment No. 223 1.3 Completion Times EXAMPLES | (C) This renewed license shall be deemed to contain, and is subject to, the conditions specified in the following Commission regulations in 10 CFR Chapter I: Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions 2 specified or incorporated below: | ||
(1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2,804 megawatts thermal, in accordance with the conditions specified herein. | |||
B. One Function Y subsystem inoperable. | (2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Protection Plan (Appendix B); as revised through Amendment No. 223 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan. | ||
C. One Function X subsystem inoperable. | (3) Additional Conditions The matters specified in the following conditions shall be completed to the satisfaction of the Commission within the stated time periods following the issuance of the renewed license or within the operational restrictions indicated. The removal of these conditions shall be made by an amendment to the license supported by a favorable evaluation by the Commission. | ||
(a) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained 2 | |||
The original licensee authorized to possess, use, and operate the facility with Georgia Power Company (GPC). Consequently, certain historical references to GPC remain in certain license conditions. | |||
Renewed License No. NPF-5 Amendment No. 223 | |||
The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered). | Completion Times 1.3 1.3 Completion Times DESCRIPTION a. Must exist concurrent with the first inoperability; and (continued) | ||
If Required Action C.2 is completed within the specified Completion Time, Conditions Band Care exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A). It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. (continued) 1.3-7 Amendment No. 223 Frequency 1.4 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE | : b. Must remain inoperable or not within limits after the first inoperability is resolved. | ||
Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Limiting Conditions 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 total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either: | ||
The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements. | : a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours; or | ||
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. 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. | : b. The stated Completion Time as measured from discovery of the subsequent inoperability. | ||
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. | The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications. | ||
With an SR satisfied, SR 3.0.4 imposes no restriction. | The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery ... " | ||
The use of "met" or "performed" in these instances conveys specific meanings. | (continued) | ||
A Surveillance is "met" only when the acceptance criteria are satisfied. | HATCH UNIT 2 1.3-2 Amendment No. 223 | ||
Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. | |||
Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. | Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued) | ||
For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: (continued) 1.4-1 Amendment No. 223 1.4 | ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X A.1 Restore 7 days subsystem Function X inoperable. subsystem to OPERABLE status. | ||
B. One Function Y B.1 Restore 72 hours subsystem Function Y inoperable. subsystem to OPERABLE status. | |||
The following examples illustrate the various ways that Frequencies are specified. | C. One Function X C.1 Restore 72 hours subsystem Function X inoperable. subsystem to OPERABLE AND status. | ||
In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3. EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours) during which the associated Surveillance must be performed at least one time. Performance of the Surveillance initiates the subsequent interval. | One Function Y OR subsystem inoperable. C.2 Restore 72 hours Function Y subsystem to OPERABLE status. | ||
Although the Frequency is stated as 12 hours, 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. | (continued) | ||
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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable. (continued) 1.4-2 Amendment No. 223 1.4 Frequency EXAMPLES | HATCH UNIT 2 1.3-6 Amendment No. 223 | ||
The surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable. | Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued) | ||
EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE Verify flow is within limits. | When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered). | ||
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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level < 25% RTP to;:: 25% RTP, the Surveillance must be performed within 12 hours. 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 extension allowed by SR 3.0.2. "Thereafter" indicates 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 Required Action C.2 is completed within the specified Completion Time, Conditions Band Care exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A). | ||
If reactor power decreases to < 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP. (continued) 1.4-3 Amendment No. 223 I 1.4 Frequency EXAMPLES | It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. | ||
(continued) | |||
------------------------------N 0 TE----------------------------- | HATCH UNIT 2 1.3-7 Amendment No. 223 | ||
0 | |||
Therefore, if the Surveillance were not performed within the 24 hour (plus the extension allowed by SR 3.0.2) interval, but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | 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. | ||
------------------------------N 0 TE----------------------------- | DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated Limiting Conditions for Operation (LCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the SR. | ||
0 n | 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, as well as certain Notes in the Surveillance column that modify performance requirements. | |||
The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1 . Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed, If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. | ||
------------------------------N 0 TE----------------------------- | 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. | ||
N ot required to be met in MODE 3. Verify parameter is within limits. 24 hours Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. | The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: | ||
Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued) 1.4-6 Amendment No. 223 1.4 Frequency EXAMPLES | (continued) | ||
HATCH UNIT 2 1.4-1 Amendment No. 223 | |||
Frequency 1.4 1.4 Frequency DESCRIPTION a. The Surveillance is not required to be met in the MODE or other (continued) specified condition to be entered; or | |||
: b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or | |||
: c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed. | |||
Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations. | |||
EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3. | |||
EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours) 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 hours, 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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable. | |||
(continued) | |||
HATCH UNIT 2 1.4-2 Amendment No. 223 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-1 (continued) | |||
If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, then SR 3.0.4 becomes applicable. The surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable. | |||
EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits. Once within 12 hours after | |||
;:: 25% RTP 24 hours 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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level | |||
< 25% RTP to;:: 25% RTP, the Surveillance must be performed within 12 hours. | |||
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 extension allowed by SR 3.0.2. | |||
"Thereafter" indicates 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 reactor power decreases to | |||
< 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP. | |||
(continued) | |||
HATCH UNIT 2 1.4-3 Amendment No. 223 I | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-4 (continued) | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------N 0 TE----------------------------- | |||
0 nly required to be met in MODE 1. | |||
Verify leakage rates are within limits. 24 hours Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour (plus the extension allowed by SR 3.0.2) interval, but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. | |||
EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------N 0 TE----------------------------- | |||
0 n Iy required to be performed in MODE 1. | |||
Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in MODE 1, 2, or 3 (the assumed Applicability of the associated LCO) between performances. | |||
(continued) | |||
HATCH UNIT 2 1.4-5 Amendment No. 223 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-5 (continued) | |||
As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. | |||
Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1 . | |||
Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed, If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. | |||
EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | |||
------------------------------N 0 TE----------------------------- | |||
N ot required to be met in MODE 3. | |||
Verify parameter is within limits. 24 hours Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued) | |||
HATCH UNIT 2 1.4-6 Amendment No. 223 | |||
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-6 (continued) violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. | |||
HATCH UNIT 2 1.4-7 Amendment No. 223 | |||
Control Rod Scram Times 3.1.4 SURVEILLANCE REQUIREMENTS | |||
-----------------------------------------------------------N 0 TE------------------------------------------------------------ | -----------------------------------------------------------N 0 TE------------------------------------------------------------ | ||
0 u ring single control rod scram time Surveillances, the control rod drive (CRD) pumps shall be isolated from the associated scram accumulator. | 0 u ring single control rod scram time Surveillances, the control rod drive (CRD) pumps shall be isolated from the associated scram accumulator. | ||
SR 3.1.4.1 | SURVEILLANCE FREQUENCY SR 3.1.4.1 Verify each control rod scram time is within the Prior to exceeding limits of Table 3.1.4-1 with reactor steam dome 40% RTP after each pressure~ 800 psig. reactor shutdown | ||
Verify each affected control rod scram time is within the limits of Table 3.1.4-1 with reactor steam dome | ~ 120 days SR 3.1.4.2 Verify, for a representative sample, each tested In accordance with control rod scram time is within the limits of the Surveillance Table 3.1.4-1 with reactor steam dome pressure Frequency Control | ||
APPLICABILITY: | ~ 800 psig. Program SR 3.1.4.3 Verify each affected control rod scram time is Prior to declaring within the limits of Table 3.1.4-1 with any reactor control rod steam dome pressure. OPERABLE after work on control rod or CRD System that could affect scram time SR 3.1.4.4 Verify each affected control rod scram time is Prior to exceeding within the limits of Table 3.1.4-1 with reactor 40% RTP after fuel steam dome pressure~ 800 psig. movement within the affected core cell Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time HATCH UNIT 2 3.1-10 Amendment No. 223 | ||
MODES 1 and 2. ACTIONS CONDITION REQUIRED ACTION A. Sodium pentaborate A.1 Restore sodium solution not within pentaborate solution to Region A limits of within Region A limits. Figure 3.1.7-1or3.1.7-2, but within the Region B limits. B. One SLC subsystem B.1 Restore SLC inoperable for reasons subsystem to other than Condition A. OPERABLE status. C. Two SLC subsystems C.1 Restore one SLC inoperable for reasons subsystem to other than Condition A. OPERABLE status. D. Required Action and D.1 Be in MODE 3. associated Completion Time not met. HATCH UNIT 2 3.1-17 | |||
SLC System 3.1.7 3.1 REACTIVITY CONTROL SYSTEMS 3.1.7 Standby Liquid Control (SLC) System LCO 3.1.7 Two SLC subsystems shall be OPERABLE. | |||
----------------------------- | APPLICABILITY: MODES 1 and 2. | ||
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Sodium pentaborate A.1 Restore sodium 72 hours solution not within pentaborate solution to Region A limits of within Region A limits. | |||
Not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. Perform CHANNEL FUNCTIONAL TEST. Perform CHANNEL FUNCTIONAL TEST. | Figure 3.1.7-1or3.1.7-2, but within the Region B limits. | ||
B. One SLC subsystem B.1 Restore SLC 7 days inoperable for reasons subsystem to other than Condition A. OPERABLE status. | |||
C. Two SLC subsystems C.1 Restore one SLC 8 hours inoperable for reasons subsystem to other than Condition A. OPERABLE status. | |||
SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. SR 3.3.1.1.10 | D. Required Action and D.1 Be in MODE 3. 12 hours associated Completion Time not met. | ||
-----------------------------NOTE----------------------------- | HATCH UNIT 2 3.1-17 Amendment No. 223 | ||
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. ------------------------------------------------------------------ | |||
Perform CHANNEL FUNCTIONAL TEST. | RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued) | ||
SURVEILLANCE FREQUENCY SR 3.3.1.1.2 -----------------------------N 0 TE----------------------------- | |||
N ot required to be performed until 12 hours after THERMAL POWER;?: 24% RTP. | |||
Verify the absolute difference between the In accordance with average power range monitor (APRM) channels the Surveillance and the calculated power is s 2% RTP while Frequency Control operating at;?: 24% RTP. Program SR 3.3.1.1.3 (Not used.) | |||
SR 3.3.1.1.4 -----------------------------NOTE----------------------------- | |||
D. | Not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. | ||
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.5 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.6 (Not used.) | |||
(continued) | |||
HATCH UNIT 2 3.3-4 Amendment No. 223 | |||
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued) | |||
SURVEILLANCE FREQUENCY SR 3.3.1.1.7 (Not used.) | |||
SR 3.3.1.1.8 Calibrate the local power range monitors. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.10 -----------------------------NOTE----------------------------- | |||
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours after entering MODE 2. | |||
------------------------------------------------------------------ | |||
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.11 Verify Turbine Stop Valve - Closure and In accordance with Turbine Control Valve Fast Closure, Trip Oil the Surveillance Pressure - Low Functions are not bypassed Frequency Control when THERMAL POWER is~ 27.6% RTP. Program SR 3.3.1.1.12 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program (continued) | |||
HATCH UNIT 2 3.3-5 Amendment No. 223 | |||
RPS Instrumentation 3.3.1.1 Table 3.3.1.1-1 (page 1 of 3) | |||
Reactor Protection System Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION D.1 REQUIREMENTS VALUE | |||
: 1. Intermediate Range Monitor | |||
: a. Neutron Flux - High 2 2(d) G SR 3.3.1.1.1 $ 120/125 SR 3.3.1.1.4 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.1 $ 120/125 SR 3.3.1.1.5 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 | |||
: b. lnop 2 2(d) G SR 3.3.1.1.4 NA SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.5 NA SR 3.3.1.1.15 | |||
: 2. Average Power Range Monitor | |||
: a. Neutron Flux - High 2 3(c) G SR 3.3.1.1.1 :> 20% RTP (Setdown) SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13 | |||
: b. Simulated Thermal 3(c) F SR 3.3.1.1.1 :> 0.57W+ | |||
Power- High SR 3.3.1.1.2 56.8% RTP SR 3.3.1.1.8 and:> 115.5% | |||
SR 3.3.1.1.10 RTP(b) | |||
SR 3.3.1.1.13 | |||
: c. Neutron Flux - High 3(c) F SR 3.3.1.1.1 :> 120% RTP SR 3.3.1.1.2 SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13 | |||
: d. lnop 1, 2 3(c) G SR 3.3.1.1.10 NA continued) | |||
(a) With any control rod withdrawn from a core cell containing one or more fuel assemblies. | |||
(b) 0.57W + 56.8% - 0.57 tiW RTP when reset for single loop operation per LCO 3.4.1, "Recirculation Loops Operating." | |||
(c) Each APRM channel provides inputs to both trip systems. | |||
(d) One channel in each quadrant of the core must be OPERABLE whenever the IRMs are required to be OPERABLE. Both the RWM and a second licensed operator must verify compliance with the withdrawal sequence when less than three channels in any trip system are OPERABLE. | |||
HATCH UNIT 2 3.3-7 Amendment No. 223 | |||
Control Rod Block Instrumentation 3.3.2.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2.1.2 Verify by administrative Immediately methods that startup with RWM inoperable has not been performed in the last 12 months. | |||
AND C.2.2 Verify movement of During control rod control rods is in movement compliance with banked position withdrawal sequence (BPWS) by a second licensed operator or other qualified member of the technical staff. | |||
D. RWM inoperable during D.1 Verify movement of During control rod reactor shutdown. control rods is in movement compliance with BPWS by a second licensed operator or other qualified member of the technical staff. | |||
E. One or more Reactor Mode E.1 Suspend control rod Immediately Switch - Shutdown Position withdrawal. | |||
channels inoperable. | |||
AND E.2 Initiate action to fully Immediately insert all insertable control rods in core cells containing one or more fuel assemblies. | |||
HATCH UNIT 2 3.3-16 Amendment No. 223 | |||
PAM Instrumentation 3.3.3.1 Table 3.3.3.1-1(page1of1) | |||
Post Accident Monitoring Instrumentation CONDITIONS REFERENCED REQUIRED FROM REQUIRED FUNCTION CHANNELS ACTION D.1 | |||
: 1. Reactor Steam Dome Pressure 2 E | |||
: 2. Reactor Vessel Water Level | |||
: a. -317 inches to -17 inches 2 E | |||
: b. -150 inches to +60 inches 2 E | |||
: c. 0 inches to +60 inches 2 E | |||
: d. 0 inches to +400 inches 1 NA | |||
: 3. Suppression Pool Water Level | |||
: a. 0 inches to 300 inches 2 E | |||
: b. 133 inches to 163 inches 2 E | |||
: 4. Drywell Pressure | |||
: a. -10 psig to +90 psig 2 E | |||
: b. -5 psig to +5 psig 2 E | |||
: c. O psig to +250 psig 2 E | |||
: 5. Drywell Area Radiation (High Range) 2 F | |||
: 6. Penetration Flow Path Primary Containment Isolation 2 per penetration flow E Valve Position path(a)(b) | |||
: 7. (Deleted) | |||
: 8. (Deleted) 2(C) E | |||
: 9. Suppression Pool Water Temperature 6 E | |||
: 10. Drywell Temperature in Vicinity of Reactor Level Instrument Reference Leg | |||
: 11. Diesel Generator (DG) Parameters 1 per DG NA | |||
: a. Output Voltage 1 per DG NA | |||
: b. Output Current 1 per DG NA | |||
: c. Output Power 1 per DG NA | |||
: d. Battery Voltage 2 E | |||
: 12. RHR Service Water Flow (a) Not required for isolation valves whose associated penetration flow path is isolated by at least one closed and deactivated automatic valve, closed manual valve, blind flange, or check valve with flow through the valve secured. | |||
(b) Only one position indication channel is required for penetration flow paths with only one installed control room indication channel. | |||
(c) Monitoring each of four quadrants. | |||
HATCH UNIT 2 3.3-25 Amendment No. 223 | |||
Primary Containment Isolation Instrumentation 3.3.6.1 3.3 INSTRUMENTATION 3.3.6.1 Primary Containment Isolation Instrumentation LCO 3.3.6.1 The primary containment isolation instrumentation for each Function in Table 3.3.6.1-1 shall be OPERABLE. | |||
APPLICABILITY: According to Table 3.3.6.1-1. | |||
ACTIONS | |||
----------------------------------------------------------N 0 TES----------------------------------------------------------- | |||
: 1. Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls. | |||
: 2. Separate Condition entry is allowed for each channel. | |||
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A.1 Place channel in trip. 12 hours for channels inoperable. Functions 2.a, 2.b, 6.b, 7.a, and 7.b AND 24 hours for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b B. --------------N 0 TE-------------- B.1 Restore isolation 1 hour Not applicable for capability. | |||
Function 5.c. | |||
------------------------------------ | |||
One or more automatic Functions with isolation capability not maintained. | One or more automatic Functions with isolation capability not maintained. | ||
C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel. (continued) | C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel. | ||
HATCH UNIT 2 3.3-48 Amendment No. 223 ACTIONS (continued) | (continued) | ||
CONDITION D. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | HATCH UNIT 2 3.3-48 Amendment No. 223 | ||
E. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | |||
F. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued) | ||
G. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | CONDITION REQUIRED ACTION COMPLETION TIME D. As required by Required D.1 Isolate associated main 12 hours Action C.1 and referenced steam line (MSL). | ||
H. As required by Required Action C.1 and referenced in Table 3.3.6.1-1. | in Table 3.3.6.1-1. | ||
OR Required Action and associated Completion Time of Condition F or G not met. HATCH UNIT 2 | OR D.2.1 Be in MODE 3. 12 hours AND D.2.2 Be in MODE 4. 36 hours E. As required by Required E.1 Be in MODE 2. 6 hours Action C.1 and referenced in Table 3.3.6.1-1. | ||
CONDITION I. As required by Required I. 1 Action C.1 and referenced in Table 3.3.6.1-1. | F. As required by Required F.1 Isolate the affected 1 hour Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s). | ||
OR 1.2 J. As required by Required J.1 Action C.1 and referenced in Table 3.3.6.1-1. | G. As required by Required G.1 Isolate the affected 24 hours Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s). | ||
OR J.2 | H. As required by Required H.1 Be in MODE 3. 12 hours Action C.1 and referenced in Table 3.3.6.1-1. AND OR H.2 Be in MODE 4. 36 hours Required Action and associated Completion Time of Condition F or G not met. | ||
(continued) | |||
: 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function. | HATCH UNIT 2 3.3-49 Amendment No. 223 | ||
: 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours provided the associated Function maintains isolation capability. | |||
SURVEILLANCE SR 3.3.6.1.1 Perform CHANNEL CHECK. | Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued) | ||
Amendment No. 223 Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued) | CONDITION REQUIRED ACTION COMPLETION TIME I. As required by Required I. 1 Declare Standby Liquid 1 hour Action C.1 and referenced Control (SLC) System in Table 3.3.6.1-1. inoperable. | ||
SURVEILLANCE FREQUENCY SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. | OR 1.2 Isolate the Reactor 1 hour Water Cleanup (RWCU) System. | ||
In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. | J. As required by Required J.1 Initiate action to restore Immediately Action C.1 and referenced channel to OPERABLE in Table 3.3.6.1-1. status. | ||
In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. | OR J.2 Initiate action to isolate Immediately the Residual Heat Removal (RHR) | ||
In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1. 7 --------------------------- | Shutdown Cooling System. | ||
SURVEILLANCE REQUIREMENTS | |||
Channel sensors are excluded. | ----------------------------------------------------------N 0 TES----------------------------------------------------------- | ||
------------------------------------------------------------------- | : 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function. | ||
Verify the ISOLATION SYSTEM RESPONSE In accordance with TIME is within limits. the Surveillance Frequency Control Program HATCH UNIT 2 3.3-51 Amendment No. 223 I Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 1 of 5) Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 1. Main Steam Line Isolation | : 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours provided the associated Function maintains isolation capability. | ||
: a. Reactor Vessel Water 1,2,3 2 D SR 3.3.6.1.1 | SURVEILLANCE FREQUENCY SR 3.3.6.1.1 Perform CHANNEL CHECK. In accordance with the Surveillance Frequency Control Program (continued) | ||
<:: -113 inches Level -Low Low Low, SR 3.3.6.1.2 Level 1 SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1.7 | HATCH UNIT 2 3.3-50 Amendment No. 223 | ||
: b. Main Steam Line 2 E SR 3.3.6.1.3 | |||
<:: 825 psig Pressure -Low SR 3.3.6.1.6 | Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued) | ||
: c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 s 138% rated Flow-High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1. 7 d. Condenser Vacuum -Low 1, 2 D SR 3.3.6.1.3 | SURVEILLANCE FREQUENCY SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1. 7 ---------------------------N0 TE------------------------------- | ||
<:: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 S194°F Temperature | Channel sensors are excluded. | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ------------------------------------------------------------------- | ||
: f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 s 200°F Temperature | Verify the ISOLATION SYSTEM RESPONSE In accordance with TIME is within limits. the Surveillance Frequency Control Program HATCH UNIT 2 3.3-51 Amendment No. 223 I | ||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 1 of 5) | |||
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | |||
: 1. Main Steam Line Isolation | |||
: a. Reactor Vessel Water 1,2,3 2 D SR 3.3.6.1.1 <:: -113 inches Level - Low Low Low, SR 3.3.6.1.2 Level 1 SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1.7 | |||
: b. Main Steam Line 2 E SR 3.3.6.1.3 <:: 825 psig Pressure - Low SR 3.3.6.1.6 | |||
: c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 s 138% rated Flow- High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1. 7 | |||
: d. Condenser Vacuum - Low 1, 2 D SR 3.3.6.1.3 <:: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum | |||
: e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 S194°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 s 200°F Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 2. Primary Containment Isolation | : 2. Primary Containment Isolation | ||
: a. Reactor Vessel Water 1,2,3 2 H SR 3.3.6.1.1 | : a. Reactor Vessel Water 1,2,3 2 H SR 3.3.6.1.1 <:: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
<:: 0 inches Level -Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. Drywell Pressure - | ||
: b. Drywell Pressure -High 1,2,3 2 H SR 3.3.6.1.1 s 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed. (b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels. | High 1,2,3 2 H SR 3.3.6.1.1 s 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed. | ||
HATCH UNIT 2 3.3-52 Amendment No. 223 | (b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels. | ||
HATCH UNIT 2 3.3-52 Amendment No. 223 | |||
: c. Drywell Radiation | |||
-High 1,2,3 F SR 3.3.6.1.1 s 138 R/hr SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 2 of 5) | ||
: d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr Radiation | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
-High SR 3.3.6.1.3 SR 3.3.6.1.6 | : 2. Primary Containment Isolation (continued) | ||
: e. Refueling Floor Exhaust 1,2,3 2 H SR 3.3.6.1.1 | : c. Drywell Radiation - High 1,2,3 F SR 3.3.6.1.1 s 138 R/hr SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6 | |||
: a. HPCI Steam Line Flow -1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | : e. Refueling Floor Exhaust Radiation - High 1,2,3 2 H SR 3.3.6.1.1 SR 3.3.6.1.3 SR 3.3.6.1.6 s 80 mR/hr I | ||
: b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 100 psig Pressure -Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : 3. High Pressure Coolant Injection (HPCI) System Isolation | ||
: c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure -High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : a. HPCI Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: d. Drywell Pressure -High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 ~ 100 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: e. HPCI Pipe Penetration Room 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature | : c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: f. Suppression Pool Area Ambient 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature | : e. HPCI Pipe Penetration Room 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 2 3.3-53 Amendment No. 223 | : f. Suppression Pool Area Ambient 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 2 3.3-53 Amendment No. 223 | ||
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 3. HPCI System Isolation (continued) | |||
: g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 | Primary Containment Isolation Instrumentation 3.3.6.1 Table3.3.6.1-1 (page3of5) | ||
:s: 16 minutes Temperature | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
-Time Delay SR 3.3.6.1.6 15 seconds Relays h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 | : 3. HPCI System Isolation (continued) | ||
:s:42°F Differential Temperature | : g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :s: 16 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays | ||
-SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | : h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 :s:42°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 | : i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :s: 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:s: 169°F Temperature | |||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 4. Reactor Core Isolation Cooling (RCIC) System Isolation | : 4. Reactor Core Isolation Cooling (RCIC) System Isolation | ||
: a. RCIC Steam Line Flow -1,2,3 F SR 3.3.6.1.1 | : a. RCIC Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 :s: 307% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:s: 307% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 ~ 60 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 :s: 20 psig Diaphragm Pressure - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 60 psig Pressure -Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 | : d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 :s: 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
:s: 20 psig Diaphragm Pressure -SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | : e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :s: 169°F Ambient Area SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: d. Drywell Pressure -High 1,2,3 F SR 3.3.6.1.1 | : f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :s: 31 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays continued) | ||
:s: 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | HATCH UNIT 2 3.3-54 Amendment No. 223 | ||
: e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 | |||
:s: 169°F Ambient Area SR 3.3.6.1.2 Temperature | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5) | ||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | ||
: f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 | : 4. RCIC System Isolation (continued) | ||
:s: 31 minutes Temperature | : g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :542°F Area Differential SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-Time Delay SR 3.3.6.1.6 15 seconds Relays continued) | : h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 s; 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
HATCH UNIT 2 3.3-54 Amendment No. 223 Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5) Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE 4. RCIC System Isolation (continued) | |||
: g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 | |||
:542°F Area Differential SR 3.3.6.1.2 Temperature | |||
-High SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 s; 169°F Temperature | |||
-High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 5. RWCU System Isolation | : 5. RWCU System Isolation | ||
: a. Area Temperature | : a. Area Temperature - High 1,2,3 1 per area F SR 3.3.6.1.1 s; 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
-High 1,2,3 1 per area F SR 3.3.6.1.1 s; 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 s; 67°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 s; 67°F Differential Temperature | : c. SLC System Initiation 1,2 1(c) SR 3.3.6.1.6 NA | ||
-SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6 | : d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 ;;:: -47 inches Level - Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: c. SLC System Initiation 1,2 1 (c) SR 3.3.6.1.6 NA d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 | |||
;;:: -47 inches Level -Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: 6. RHR Shutdown Cooling System Isolation | : 6. RHR Shutdown Cooling System Isolation | ||
: a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 s; 145 psig Pressure -High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | : a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 s; 145 psig Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
: b. Reactor Vessel Water 3,4,5 2(d) J SR 3.3.6.1.1 | : b. Reactor Vessel Water 3,4,5 2(d) J SR 3.3.6.1.1 ;;:: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continue ) | ||
;;:: 0 inches Level -Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continue ) (c) SLC System Initiation only inputs into one of the two trip systems. (d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained. | (c) SLC System Initiation only inputs into one of the two trip systems. | ||
HATCH UNIT 2 3.3-55a Amendment No. 223 Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 5 of 5) Primary Containment Isolation Instrumentation FUNCTION 7. Traversing lncore Probe System Isolation | (d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained. | ||
: a. Reactor Vessel Water | HATCH UNIT 2 3.3-55a Amendment No. 223 | ||
APPLICABILITY: | |||
MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig. ACTIONS ---------------------------------------------------------------NOTE-------------------------------------------------------- | Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 5 of 5) | ||
LCO 3.0.4.b is not applicable to HPCI. CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable. | Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM ALLOWABLE SPECIFIED PER TRIP REQUIRED SURVEILLANCE VALUE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS | ||
subsystem(s) to OPERABLE status. OR One LPCI pump in both LPCI subsystems inoperable. | : 7. Traversing lncore Probe System Isolation | ||
B. Required Action and B.1 Be in MODE 3. 12 hours associated Completion Time of Condition A not AND met. B.2 Be in MODE 4. 36 hours (continued) | : a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 ~ 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | ||
HATCH UNIT 2 3.5-1 Amendment No. 223 ACTIONS (continued) | : b. Drywell Pressure - High 1,2,3 2 G SR 3.3.6.1.1 :s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 HATCH UNIT 2 3.3-55b Amendment No. 223 | ||
CONDITION C. HPCI System inoperable. | |||
ECCS - Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.1 ECCS - Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic Depressurization System (ADS) function of six of seven safety/relief valves shall be OPERABLE. | |||
AND | APPLICABILITY: MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig. | ||
ACTIONS | |||
---------------------------------------------------------------NOTE-------------------------------------------------------- | |||
LCO 3.0.4.b is not applicable to HPCI. | |||
CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable. subsystem(s) to OPERABLE status. | |||
OR One LPCI pump in both LPCI subsystems inoperable. | |||
B. Required Action and B.1 Be in MODE 3. 12 hours associated Completion Time of Condition A not AND met. | |||
B.2 Be in MODE 4. 36 hours (continued) | |||
HATCH UNIT 2 3.5-1 Amendment No. 223 | |||
ECCS - Operating 3.5.1 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME C. HPCI System inoperable. C.1 Verify by administrative 1 hour means RCIC System is OPERABLE. | |||
AND C.2 Restore HPCI System 14 days to OPERABLE status. | |||
D. HPCI System inoperable. D.1 Restore HPCI System 72 hours to OPERABLE status. | |||
AND OR Condition A entered. | |||
D.2 Restore low pressure 72 hours ECCS injection/spray subsystem to OPERABLE status. | |||
E. Two or more ADS valves E.1 Be in MODE 3. 12 hours inoperable. | |||
AND OR E.2 Reduce reactor steam 36 hours Required Action and dome pressure to associated Completion :s; 150 psig. | |||
SR 3.6.1.3. | Time of Condition C or D not met. | ||
-------------------------- | F. Two or more low pressure F.1 Enter LCO 3.0.3. Immediately ECCS injection/spray subsystems inoperable for reasons other than Condition A. | ||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. 2. Not required to be met for PCIVs that are open under administrative controls. | OR HPCI System and two or more ADS valves inoperable. | ||
Verify each primary containment isolation | HATCH UNIT 2 3.5-2 Amendment No. 223 | ||
Verify each | PC IVs 3.6.1.3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) A.2 ------------N 0 TES----------- | ||
: 1. Isolation devices in high radiation areas may be verified by use of administrative means. | |||
: 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | |||
-------------------------------- | |||
110°F. AND D.2 AND D.3 HATCH UNIT 2 | Verify the affected Once per 31 days for penetration flow path is isolation devices isolated. outside primary containment AND Prior to entering MODE 2 or 3 from MODE 4 if primary containment was de-inerted while in MODE 4, if not performed within the previous 92 days, for isolation devices inside primary containment B. --------------N 0 TE--------------- 8.1 Isolate the affected 1 hour Only applicable to penetration flow path by penetration flow paths with use of at least one two PCIVs. closed and de-activated | ||
------------------------------------- automatic valve, closed manual valve, or blind One or more penetration flange. | |||
flow paths with two PCIVs inoperable except due to leakage not within limit. | |||
(continued) | |||
HATCH UNIT 2 3.6-8 Amendment No. 223 | |||
PC IVs 3.6.1.3 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME C. --------------NOTE--------------- C.1 Isolate the affected 4 hours except for Only applicable to penetration flow path by excess flow check penetration flow paths with use of at least one valve (EFCV) line and only one PCIV. closed and de-activated penetrations with a | |||
------------------------------------- automatic valve, closed closed system manual valve, or blind One or more penetration flange. AND flow paths with one PCIV inoperable except due to 72 hours for leakage not within limits. AND EFCV line and penetrations with a C.2 ----------NO TES----------- closed system | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | |||
-------------------------------- | |||
Verify the affected Once per 31 days penetration flow path is isolated. | |||
D. One or more penetration D.1 Restore leakage to 4 hours flow paths with leakage not within limit. | |||
within limit. | |||
E. Required Action and E.1 Be in MODE 3. 12 hours associated Completion Time of Condition A, B, C, AND or D not met in MODE 1, 2, or 3. E.2 Be in MODE 4. 36 hours (continued) | |||
HATCH UNIT 2 3.6-9 Amendment No. 223 | |||
PC IVs 3.6.1.3 SURVEILLANCE REQUIREMENTS (continued) | |||
SURVEILLANCE FREQUENCY SR 3.6.1.3.2 ------------------------------N 0 TES--------------------------- | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Not required to be met for PCIVs that are open under administrative controls. | |||
Verify each primary containment isolation manual In accordance with valve and blind flange that is located outside the Surveillance primary containment and not locked, sealed, or Frequency Control otherwise secured and is required to be closed Program during accident conditions is closed. | |||
SR 3.6.1.3.3 -----------------------------N 0 TES---------------------------- | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
: 2. Not required to be met for PCIVs that are open under administrative controls. | |||
Verify each primary containment manual isolation Prior to entering valve and blind flange that is located inside MODE 2 or 3 from primary containment and not locked, sealed, or MODE 4 if primary otherwise secured and is required to be closed containment was during accident conditions is closed. de-inerted while in MODE 4, if not performed within the previous 92 days SR 3.6.1.3.4 Verify continuity of the traversing incore probe In accordance with (TIP) shear isolation valve explosive charge. the Surveillance Frequency Control Program SR 3.6.1.3.5 Verify the isolation time of each power operated, In accordance with automatic PCIV, except for MSIVs, is within limits. the Inservice Testing Program (continued) | |||
HATCH UNIT 2 3.6-11 Amendment No. 223 | |||
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and B.1 Reduce THERMAL 12 hours associated Completion POWER until all Time of Condition A not OPERABLE I RM met. channels s 25/40 divisions of full scale on Range 7. | |||
C. Suppression pool average C.1 Suspend all testing that Immediately temperature> 105°F. adds heat to the suppression pool. | |||
AND Any OPERABLE IRM channel > 25/40 divisions of full scale on Range 7. | |||
AND Performing testing that adds heat to the suppression pool. | |||
D. Suppression pool average D.1 Place the reactor mode Immediately temperature> 110°F. switch in the shutdown position. | |||
AND D.2 Determine suppression Once per 30 minutes pool average temperature. | |||
AND D.3 Be in MODE 4. 36 hours (continued) | |||
HATCH UNIT 2 3.6-22 Amendment No. 223 | |||
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME E. Suppression pool average E.1 Depressurize the 12 hours temperature> 120°F. reactor vessel to | |||
< 200 psig. | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.2.1.1 Verify suppression pool average temperature is In accordance with within the applicable limits. the Surveillance Frequency Control Program AND 5 minutes when performing testing that adds heat to the suppression pool HATCH UNIT 2 3.6-23 Amendment No. 223 | |||
Secondary Containment 3.6.4.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2 Suspend CORE Immediately ALTERATIONS. | |||
AND C.3 Initiate action to Immediately suspend OPDRVs. | |||
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.1.1 Verify all secondary containment equipment In accordance with hatches are closed and sealed. the Surveillance Frequency Control Program SR 3.6.4.1.2 Verify one secondary containment access door in In accordance with each access opening is closed. the Surveillance Frequency Control Program SR 3.6.4.1.3 -----------------------------N 0 TE----------------------------- | |||
Th e number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | Th e number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | ||
Verify secondary containment can be drawn down to 0.20 inch of vacuum water gauge in s 120 seconds using required standby gas treatment (SGT) subsystem(s). | Verify secondary containment can be drawn In accordance with down to ~ 0.20 inch of vacuum water gauge in the Surveillance s 120 seconds using required standby gas Frequency Control treatment (SGT) subsystem(s). Program (continued) | ||
3.6-34 | HATCH UNIT 2 3.6-34 Amendment No. 223 | ||
Amendment No. 223 Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SR 3.6.4.1.4 | |||
-----------------------------N 0 TE------------------------------ | Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.6.4.1.4 -----------------------------N 0 TE------------------------------ | ||
Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration. | ||
Verify the secondary containment can be maintained | Verify the secondary containment can be In accordance with maintained ;:: 0.20 inch of vacuum water gauge the Surveillance for 1 hour using required SGT subsystem(s) at Frequency Control a flow rates 4000 cfm per subsystem. Program HATCH UNIT 2 3.6-35 Amendment No. 223 | ||
;:: 0.20 inch of vacuum water gauge for 1 hour using required SGT subsystem(s) at a flow rates 4000 cfm per subsystem. | |||
3.6-35 | SC IVs 3.6.4.2 3.6 CONTAINMENT SYSTEMS 3.6.4.2 Secondary Containment Isolation Valves (SCIVs) | ||
LCO 3.6.4.2 Each SCIV shall be OPERABLE. | |||
MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE AL TE RATIONS, During operations with a potential for draining the reactor vessel (OPDRV). | APPLICABILITY: MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE AL TE RATIONS, During operations with a potential for draining the reactor vessel (OPDRV). | ||
ACTIONS | |||
: 1. Penetration flow paths may be unisolated intermittently under administrative controls. | ----------------------------------------------------------N0 TES------------------------------------------------------------- | ||
: 2. Separate Condition entry is allowed for each penetration flow path. 3. Enter applicable Conditions and Required Actions for systems made inoperable by SCIVs. CONDITION A. One or more penetration | : 1. Penetration flow paths may be unisolated intermittently under administrative controls. | ||
: 2. Separate Condition entry is allowed for each penetration flow path. | |||
: 1. Isolation devices in high radiation areas may be verified by use of administrative means. 3.6-36 | : 3. Enter applicable Conditions and Required Actions for systems made inoperable by SCIVs. | ||
Amendment No. 223 ACTIONS CONDITION A. (continued) | CONDITION REQUIRED ACTION COMPLETION TIME A. One or more penetration A.1 Isolate the affected 8 hours flow paths with one SCIV penetration flow path by inoperable. use of at least one closed and de-activated automatic valve, closed manual valve, or blind flange. | ||
AND A.2 -----------NOTES----------- | |||
: 1. Isolation devices in high radiation areas may be verified by use of administrative means. | |||
(continued) | |||
HATCH UNIT 2 3.6-36 Amendment No. 223 | |||
LCO 3.0.3 is not applicable. | |||
------------------------------- | SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | ||
------------------------------- | |||
3.6-37 SCI Vs 3.6.4.2 COMPLETION TIME | Verify the affected Once per 31 days penetration flow path is isolated. | ||
B. One or more penetration B.1 Isolate the affected 4 hours flow paths with two SCIVs penetration flow path by inoperable. use of at least one closed and de-activated automatic valve, closed manual valve, or blind flange. | |||
D.2 | C. Required Action and C.1 Be in MODE 3. 12 hours associated Completion Time of Condition A or B AND not met in MODE 1, 2, or 3. | ||
Initiate action to suspend OPDRVs. SURVEILLANCE REQUIREMENTS SR 3.6.4.2.1 | C.2 Be in MODE 4. 36 hours D. Required Action and D.1 -------------N 0 TE---------- | ||
associated Completion LCO 3.0.3 is not Time of Condition A or B applicable. | |||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. 2. Not required to be met for SCIVs that are open under administrative controls. | not met during movement ------------------------------- | ||
Verify each secondary containment isolation manual valve and blind flange that is not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. | of irradiated fuel assemblies in the Suspend movement of Immediately secondary containment, irradiated fuel during CORE assemblies in the ALTERATIONS, or during secondary containment. | ||
OPDRVs. | |||
OR One required Unit 1 SGT subsystem inoperable for reasons other than Condition A. C. Required Action and | (continued) | ||
HATCH UNIT 2 3.6-37 Amendment No. 223 | |||
------------------------------------------- | |||
SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME D. (continued) | |||
OR D.2.1 Suspend movement of irradiated fuel assemblies in secondary containment. | D.2 Suspend CORE Immediately ALTERATIONS. | ||
AND D.2.2 Suspend CORE ALTERATIONS. | AND D.3 Initiate action to Immediately suspend OPDRVs. | ||
AND D.2.3 Initiate action to suspend OPDRVs. 3.6-40 | SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.2.1 ----------------------------N 0 TES---------------------------- | ||
: 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means. | |||
LCO 3.0.4.b is not applicable to DGs. CONDITION REQUIRED ACTION COMPLETION TIME A. One required offsite circuit A.1 Perform SR 3.8.1.1 for 1 hour inoperable. | : 2. Not required to be met for SCIVs that are open under administrative controls. | ||
OPERABLE required offsite circuits. | Verify each secondary containment isolation In accordance with manual valve and blind flange that is not locked, the Surveillance sealed, or otherwise secured and is required to be Frequency Control closed during accident conditions is closed. Program SR 3.6.4.2.2 Verify the isolation time of each power operated, In accordance with automatic SCIV is within limits. the Surveillance Frequency Control Program SR 3.6.4.2.3 Verify each automatic SCIV actuates to the In accordance with isolation position on an actual or simulated the Surveillance actuation signal. Frequency Control Program HATCH UNIT 2 3.6-38 Amendment No. 223 | ||
AND Once per 8 hours thereafter AND A.2 Declare required 24 hours from discovery feature(s) with no offsite of no offsite power to power available one 4160 V ESF bus inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. | |||
feature(s) | SGT System 3.6.4.3 ACTIONS (continued) | ||
AND A.3 Restore required offsite 72 hours circuit to OPERABLE status. B. One Unit 2 or the swing DG B.1 Perform SR 3.8.1.1 for 1 hour inoperable. | CONDITION REQUIRED ACTION COMPLETION TIME B. One required Unit 2 SGT B.1 Restore required SGT 7 days subsystem inoperable. subsystem to OPERABLE status. | ||
OPERABLE required offsite circuit(s). | OR One required Unit 1 SGT subsystem inoperable for reasons other than Condition A. | ||
AND Once per 8 hours thereafter AND (continued) | C. Required Action and C.1 Be in MODE 3. 12 hours associated Completion Time of Condition A or B AND not met in MODE 1, 2, or 3. | ||
HATCH UNIT 2 3.8-2 Amendment No. 223 | C.2 Be in MODE 4. 36 hours D. Required Action and ------------------N 0 TE----------------- | ||
B.4 (continued) | associated Completion LCO 3.0.3 is not applicable. | ||
C. One required Unit 1 DG C.1 Perform SR 3.8.1.1 for inoperable. | Time of Condition A or B ------------------------------------------- | ||
OPERABLE required offsite circuit(s). | not met during movement of irradiated fuel D.1 Place remaining Immediately assemblies in the OPERABLE SGT secondary containment, subsystem(s) in during CORE operation. | ||
AND C.2 Declare required feature(s), supported by the inoperable DG, inoperable when the redundant required feature(s) are inoperable. | ALTERATIONS, or during OPDRVs. OR D.2.1 Suspend movement of Immediately irradiated fuel assemblies in secondary containment. | ||
AND C.3.1 Determine OPERABLE DG(s) are not inoperable due to common cause failure. OR C.3.2 Perform SR 3.8.1.2.a for OPERABLE DG(s). HATCH UNIT 2 3.8-4 AC Sources -Operating 3.8.1 | AND D.2.2 Suspend CORE Immediately ALTERATIONS. | ||
AND D.2.3 Initiate action to Immediately suspend OPDRVs. | |||
(continued) | |||
HATCH UNIT 2 3.6-40 Amendment No. 223 | |||
Credit may be taken for unplanned events that satisfy this SR. Verify automatic and manual transfer of unit power supply from the normal offsite circuit to the alternate offsite circuit. ----------------------------N 0 TES----------------------------- | AC Sources - Operating 3.8.1 ACTIONS | ||
: 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | ---------------------------------------------------------------NOTE-------------------------------------------------------- | ||
For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls. | LCO 3.0.4.b is not applicable to DGs. | ||
Credit may be taken for unplanned events that satisfy this SR. 2. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. Verify each DG rejects a load greater than or equal to its associated single largest post-accident load, and: a. Following load rejection, the frequency is s 65.5 Hz; and b. Within 3 seconds following load rejection, the voltage is;;:: 3740 V ands 4580 V. 3.8-10 FREQUENCY | CONDITION REQUIRED ACTION COMPLETION TIME A. One required offsite circuit A.1 Perform SR 3.8.1.1 for 1 hour inoperable. OPERABLE required offsite circuits. AND Once per 8 hours thereafter AND A.2 Declare required 24 hours from discovery feature(s) with no offsite of no offsite power to power available one 4160 V ESF bus inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. feature(s) | ||
AND A.3 Restore required offsite 72 hours circuit to OPERABLE status. | |||
B. One Unit 2 or the swing DG B.1 Perform SR 3.8.1.1 for 1 hour inoperable. OPERABLE required offsite circuit(s). AND Once per 8 hours thereafter AND (continued) | |||
: 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | HATCH UNIT 2 3.8-2 Amendment No. 223 | ||
For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls. | |||
Credit may be taken for unplanned events that satisfy this SR. 2. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable. | AC Sources - Operating 3.8.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. (continued) B.4 (continued) AND 14 days for the swing diesel with maintenance restrictions met C. One required Unit 1 DG C.1 Perform SR 3.8.1.1 for 1 hour inoperable. OPERABLE required offsite circuit(s). AND Once per 8 hours thereafter AND C.2 Declare required 4 hours from feature(s), supported by discovery the inoperable DG, of Condition C inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. feature(s) | ||
: 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. Verify each DG operating at a power factors 0.88 does not trip and voltage is maintained s 4800 V during and following a load rejection 2775 kW. | AND C.3.1 Determine OPERABLE 24 hours DG(s) are not inoperable due to common cause failure. | ||
Amendment No. 223 AC Sources -Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SR 3.8.1.9 | OR C.3.2 Perform SR 3.8.1.2.a for 24 hours OPERABLE DG(s). | ||
----------------------------N 0 TES----------------------------- | (continued) | ||
: 1. All DG starts may be preceded by an engine prelube period. 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | HATCH UNIT 2 3.8-4 Amendment No. 223 | ||
Credit may be taken for unplanned events that satisfy this SR. Verify on an actual or simulated loss of offsite power signal: a. De-energization of emergency buses; b. Load kdding from emergency buses; and c. DG auto-starts from standby condition and: 1. Energizes permanently connected loads in s 12 seconds, 2. Energizes auto-connected shutdown loads through automatic load sequence timing devices, 3. Maintains steady state voltage ;:; 3740 V ands; 4243 V, 4. Maintains steady state frequency | |||
;:; 58.8 Hz and s 61.2 Hz, and 5. Supplies permanently connected and auto-connected shutdown loads for ;:; 5 minutes. | AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued) | ||
Amendment No. 223 AC Sources -Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SR 3.8.1.10 | SURVEILLANCE FREQUENCY SR 3.8.1.6 ----------------------------N 0 TE------------------------------- | ||
---------------------------N 0 TES---------------------------- | T his Surveillance shall not normally be performed in MODE 1 or 2. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | ||
: 1. All DG starts may be preceded by an engine prelube period. 2. This Surveillance shall not normally be performed in MODE 1 or 2. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | Verify automatic and manual transfer of unit power In accordance with supply from the normal offsite circuit to the the Surveillance alternate offsite circuit. Frequency Control Program SR 3.8.1.7 ----------------------------N 0 TES----------------------------- | ||
Credit may be taken for unplanned events that satisfy this SR. Verify on an actual or simulated Emergency Core Cooling System (ECCS) initiation signal each DG auto-starts from standby condition and: | : 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls. | ||
Amendment No. 223 | Credit may be taken for unplanned events that satisfy this SR. | ||
: 2. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. | |||
Credit may be taken for unplanned events that satisfy this SR. Verify each DG's non-critical automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal. 3.8-14 | Verify each DG rejects a load greater than or In accordance with equal to its associated single largest post-accident the Surveillance load, and: Frequency Control Program | ||
Amendment No. 223 AC Sources -Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SR 3.8.1.12 | : a. Following load rejection, the frequency is s 65.5 Hz; and | ||
: b. Within 3 seconds following load rejection, the voltage is;;:: 3740 V ands 4580 V. | |||
: 1. Momentary transients outside the load and power factor ranges do not invalidate this test. 2. This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. | (continued) | ||
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | HATCH UNIT 2 3.8-10 Amendment No. 223 | ||
If either of the other two DGs becomes inoperable, this Surveillance shall be suspended. | |||
Credit may be taken for unplanned events that satisfy this SR. 3. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable. | AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.8 -----------------------------N 0 TES---------------------------- | ||
: 4. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. Verify each DG operating at a power factors 0.88 operates for <! 24 hours: a. For<! 2 hours loaded 2: 3000 kW; and b. For the remaining hours of the test loaded <! 2775 kW and s 2825 kW. 3.8-15 | : 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls. | ||
Credit may be taken for unplanned events that satisfy this SR. | |||
: 2. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable. | |||
: 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. | |||
Verify each DG operating at a power factors 0.88 In accordance with does not trip and voltage is maintained s 4800 V the Surveillance during and following a load rejection of~ 2775 kW. Frequency Control Program (continued) | |||
HATCH UNIT 2 3.8-11 Amendment No. 223 | |||
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.9 ----------------------------N 0 TES----------------------------- | |||
: 1. All DG starts may be preceded by an engine prelube period. | |||
: 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify on an actual or simulated loss of offsite In accordance with power signal: the Surveillance Frequency Control | |||
: a. De-energization of emergency buses; Program | |||
: b. Load kdding from emergency buses; and | |||
: c. DG auto-starts from standby condition and: | |||
: 1. Energizes permanently connected loads in s 12 seconds, | |||
: 2. Energizes auto-connected shutdown loads through automatic load sequence timing devices, | |||
: 3. Maintains steady state voltage | |||
;:; 3740 V ands; 4243 V, | |||
: 4. Maintains steady state frequency | |||
;:; 58.8 Hz and s 61.2 Hz, and | |||
: 5. Supplies permanently connected and auto-connected shutdown loads for ;:; 5 minutes. | |||
(continued) | |||
HATCH UNIT 2 3.8-12 Amendment No. 223 | |||
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.10 ---------------------------N 0 TES---------------------------- | |||
: 1. All DG starts may be preceded by an engine prelube period. | |||
: 2. This Surveillance shall not normally be performed in MODE 1 or 2. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify on an actual or simulated Emergency Core In accordance with Cooling System (ECCS) initiation signal each DG the Surveillance auto-starts from standby condition and: Frequency Control Program | |||
: a. Ins 12 seconds after auto-start achieves voltage~ 3740 V, and after steady state conditions are reached, maintains voltage | |||
~ 3740 V ands 4243 V; | |||
: b. Ins 12 seconds after auto-start achieves frequency ~ 58.8 Hz, and after steady state conditions are reached, maintains frequency ~ 58.8 Hz and s 61.2 Hz; and | |||
: c. Operates for ~ 5 minutes. | |||
(continued) | |||
HATCH UNIT 2 3.8-13 Amendment No. 223 | |||
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.11 --------------------------N 0 TE--------------------------------- | |||
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify each DG's non-critical automatic trips are In accordance with bypassed on actual or simulated loss of voltage the Surveillance signal on the emergency bus concurrent with an Frequency Control actual or simulated ECCS initiation signal. Program (continued) | |||
HATCH UNIT 2 3.8-14 Amendment No. 223 | |||
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.12 ---------------------------NOTES------------------------------ | |||
: 1. Momentary transients outside the load and power factor ranges do not invalidate this test. | |||
: 2. This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. If either of the other two DGs becomes inoperable, this Surveillance shall be suspended. | |||
Credit may be taken for unplanned events that satisfy this SR. | |||
: 3. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable. | |||
: 4. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. | |||
Verify each DG operating at a power factors 0.88 In accordance with operates for <! 24 hours: the Surveillance Frequency Control | |||
: a. For<! 2 hours loaded 2: 3000 kW; and Program | |||
: b. For the remaining hours of the test loaded | |||
<! 2775 kW and s 2825 kW. | |||
(continued) | |||
HATCH UNIT 2 3.8-15 Amendment No. 223 | |||
Verify | AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued) | ||
: | SURVEILLANCE FREQUENCY SR 3.8.1.13 ---------------------------NOTES------------------------------ | ||
: 1. This Surveillance shall be performed within 5 minutes of shutting down the DG after the DG has operated ~ 2 hours loaded | |||
~ 2565 kW. Momentary transients outside of load range do not invalidate this test. | |||
: 2. All DG starts may be preceded by an engine prelube period. | |||
: 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units. | |||
Verify each DG starts and achieves, in In accordance with | |||
::;; 12 seconds, voltage ~ 37 40 V and frequency the Surveillance | |||
~ 58.8 Hz; and after steady state conditions are Frequency Control reached, maintains voltage~ 3740 V and::;; 4243 V Program and frequency~ 58.8 Hz and ::;; 61.2 Hz. | |||
SR 3.8.1.14 ---------------------------N 0 TE-------------------------------- | |||
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify each DG: In accordance with the Surveillance | |||
: a. Synchronizes with offsite power source Frequency Control while loaded with emergency loads upon a Program simulated restoration of offsite power; | |||
: b. Transfers loads to offsite power source; and | |||
: c. Returns to ready-to-load operation. | |||
(continued) | |||
HATCH UNIT 2 3.8-16 Amendment No. 223 | |||
In accordance with the Surveillance | AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued) | ||
SURVEILLANCE FREQUENCY SR 3.8.1.15 ---------------------------NOTE------------------------------- | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
------------------------------------------------------------------ | |||
Verify with a DG operating in test mode and In accordance with connected to its bus, an actual or simulated ECCS the Surveillance initiation signal overrides the test mode by: Frequency Control Program | |||
: a. Returning DG to ready-to-load operation; and | |||
: b. Automatically energizing the emergency load from offsite power. | |||
SR 3.8.1.16 -----------------------------NOTE------------------------------ | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
------------------------------------------------------------------- | |||
Verify interval between each sequenced load block In accordance with is within 10% of design interval for each load the Surveillance sequence timing device. Frequency Control Program (continued) | |||
HATCH UNIT 2 3.8-17 Amendment No. 223 | |||
Frequency Control | AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.17 ----------------------------N 0 TES----------------------------- | ||
: 1. All DG starts may be preceded by an engine prelube period. | |||
: 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify, on an actual or simulated loss of offsite In accordance with power signal in conjunction with an actual or the Surveillance simulated ECCS initiation signal: Frequency Control Program | |||
: a. De-energization of emergency buses; | |||
: b. Load shedding from emergency buses; and | |||
: c. DG auto-starts from standby condition and: | |||
: 1. Energizes permanently connected loads in ::; 12 seconds, | |||
: 2. Energizes auto-connected emergency loads through automatic load sequence timing devices, | |||
: 3. Achieves steady state voltage | |||
~ 3740 V and::; 4243 V, | |||
: 4. Achieves steady state frequency | |||
~ 58.8 Hz and::; 61.2 Hz, and | |||
: 5. Supplies permanently connected and auto-connected emergency loads for ~ 5 minutes. | |||
(continued) | |||
HATCH UNIT 2 3.8-18 Amendment No. 223 | |||
Program | DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.4.7 -----------------------------N 0 TES---------------------------- | ||
: 1. The modified performance discharge test in SR 3.8.4.8 may be performed in lieu of the service test in SR 3.8.4.7. | |||
: 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
Verify battery capacity is adequate to supply, and In accordance with maintain in OPERABLE status, the required the Surveillance emergency loads for the design duty cycle when Frequency Control subjected to a battery service test. Program (continued) | |||
HATCH UNIT 2 3.8-29 Amendment No. 223 | |||
SR | DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS (continued) | ||
SURVEILLANCE FREQUENCY SR 3.8.4.8 -------------------------------N 0 TE---------------------------- | |||
Verify | Th is Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | ||
Verify battery capacity is ;;:: 80% of the In accordance with manufacturer's rating when subjected to a the Surveillance performance discharge test or a modified Frequency Control performance discharge test. Program 12 months when battery shows degradation or has reached 85% of expected life with capacity < 100% of manufacturer's rating 24 months when battery has reached 85% of expected life with capacity ;;:: 100% of manufacturer's rating SR 3.8.4.9 For required Unit 1 DC sources, the SRs of Unit 1 In accordance with Specification 3.8.4 are applicable. applicable SRs HATCH UNIT 2 3.8-30 Amendment No. 223 | |||
Distribution Systems - Operating 3.8.7 ACTIONS (continued) | |||
CONDITION REQUIRED ACTION COMPLETION TIME B. One or more (Unit 2 or B.1 Restore DG DC 12 hours swing bus) DG DC electrical power electrical power distribution distribution subsystem subsystems inoperable. to OPERABLE status. | |||
C. One or more (Unit 2 or C.1 Restore AC electrical 8 hours swing bus) AC electrical power distribution power distribution subsystem to subsystems inoperable. OPERABLE status. | |||
D. One Unit 2 station service D.1 Restore Unit 2 station 2 hours DC electrical power service DC electrical distribution subsystem power distribution inoperable. subsystem to OPERABLE status. | |||
E. Required Action and E.1 Be in MODE 3. 12 hours associated Completion Time of Condition A, B, C, AND or D not met. | |||
E.2 Be in MODE 4. 36 hours F. Two or more electrical F.1 Enter LCO 3.0.3. Immediately power distribution subsystems inoperable that result in a loss of function. | |||
HATCH UNIT 2 3.8-38 Amendment No. 223 | |||
the | Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.4 Radioactive Effluent Controls Program (continued) | ||
: c. Monitoring, sampling, and analysis of radioactive liquid and gaseous effluents in accordance with 10 CFR 20.1302 and with the methodology and parameters in the ODCM; | |||
: d. Limitations on the annual and quarterly doses or dose commitment to a member of the public from radioactive materials in liquid effluents released from each unit to unrestricted areas, conforming to 10 CFR 50, Appendix I; | |||
: e. Determination of cumulative dose contributions from radioactive effluents for the current calendar quarter and current calendar year in accordance with the methodology and parameters in the ODCM at least every 31 days. Determination of projected dose contributions from radioactive effluents in accordance with the methodology in the ODCM at least every 31 days; | |||
: f. Limitations on the functional capability and use of the liquid and gaseous effluent treatment systems to ensure that appropriate portions of these systems are used to reduce releases of radioactivity when the projected doses in a period of 31 days would exceed 2% of the guidelines for the annual dose or dose commitment, conforming to 10 CFR 50, Appendix I; | |||
: g. Limitations on the dose rate resulting from radioactive material released in gaseous effluents to areas beyond the site boundary as follows: | |||
: 1) For noble gases, less than or equal to a dose rate of 500 mrem/year to the total body and less than or equal to a dose rate of 3000 mrem/year to the skin, and | |||
: 2) For iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half-lives greater than 8 days, less than or equal to a dose rate of 1500 mrem/year to any organ; | |||
: h. Limitations on the annual and quarterly air doses resulting from noble gases released in gaseous effluents from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I; | |||
: i. Limitations on the annual and quarterly doses to a member of the public from iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half lives> 8 days in gaseous effluents released from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I; and | |||
: j. Limitations on the annual dose or dose commitment to any member of the public due to releases of radioactivity and to radiation from uranium fuel cycle sources, conforming to 40 CFR 190. | |||
(continued) | |||
HATCH UNIT 2 5.0-9 Amendment No. 223 | |||
Programs and Manuals 5.5 5.5 Programs and Manuals (continued) 5.5.5 Component Cyclic or Transient Limit This program provides controls to track FSAR Section 5.2, cyclic and transient occurrences, to ensure that reactor coolant pressure boundary components are maintained within the design limits. | |||
5.5.6 lnservice Testing Program This program provides controls for inservice testing of ASME Code Class 1, 2, and 3 components including applicable supports. | |||
: a. Testing frequencies specified in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda are as follows: | |||
ASME Boiler and Pressure Vessel Code and Applicable Required Frequencies Addenda Terminology for for Performing lnservice lnservice Testing Activities Testing Activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days Yearly or annually At least once per 366 days | |||
: b. The provisions of SR 3.0.2 are applicable to the frequencies for performing inservice testing activities; | |||
: c. The provisions of SR 3.0.3 are applicable to inservice testing activities; and | |||
: d. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specification. | |||
5.5.7 Ventilation Filter Testing Program (VFTP) | |||
A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2. | |||
(continued) | (continued) | ||
HATCH UNIT 2 5.0-10 Amendment No. 223 | |||
HATCH UNIT 2 | |||
Amendment No. 223 | |||
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.8 Explosive Gas and Storage Tank Radioactivity Monitoring Program (continued) | |||
The program shall include: | |||
: a. The limits for the concentrations of hydrogen in the main condenser offgas treatment system and a surveillance program to ensure the limits are maintained. Such limits shall be appropriate to the system's design criteria (i.e., whether or not the system is designed to withstand a hydrogen explosion); and | |||
: b. A surveillance program to ensure that the quantity of radioactivity contained in all outdoor liquid radwaste tanks that are not surrounded by liners, dikes, or walls capable of holding the tanks' contents and that do not have tank overflows and surrounding area drains connected to the liquid radwaste treatment system is less than the amount that would result in concentrations less than the limits of 10 CFR 20, Appendix B, Table 2, Column 2, at the nearest potable water supply and the nearest surface water supply in an unrestricted area, in the event of an uncontrolled release of the tanks' contents. | |||
The program shall include: a. The limits for the concentrations of hydrogen in the main condenser offgas treatment system and a surveillance program to ensure the limits are maintained. | |||
Such limits shall be appropriate to the system's design criteria (i.e., whether or not the system is designed to withstand a hydrogen explosion); | |||
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies. | ||
5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. | 5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following: | ||
The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. | : a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: | ||
The purpose of the program is to establish the following: | : 1. An API gravity or an absolute specific gravity within limits, | ||
: a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: 1. An API gravity or an absolute specific gravity within limits, 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and 3. A water and sediment content within limits; b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued) | : 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and | ||
HATCH UNIT 2 5.0-13 Amendment No. 223 Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued) | : 3. A water and sediment content within limits; | ||
Safety Function Determination Program (SFDP) This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following: | : b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued) | ||
: a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected; | HATCH UNIT 2 5.0-13 Amendment No. 223 | ||
: b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists; c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and d. Other appropriate limitations and remedial or compensatory actions. A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. | |||
For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable. (continued) | Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued) | ||
HATCH UNIT 2 5.0-14 Amendment No. 223 Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 | : c. Total particulate concentration of the fuel oil is :::; 10 mg/liter when tested every 92 days. | ||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system. Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies. | ||
: a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews. b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following: | 5.5.10 Safety Function Determination Program (SFDP) | ||
: 1. A change in the TS incorporated in the license; or 2. A change to the updated FSAR or Bases that requires NRC approval pursuant to 10 CFR 50.59. c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR. d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRC prior to implementation. | This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following: | ||
Changes to the Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71(e). | : a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected; | ||
HATCH UNIT 2 5.0-15 | : b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists; | ||
Amendment No. 223 UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION AMENDMENT NO. 279 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-57 AND AMENDMENT NO. 223 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-5 SOUTHERN NUCLEAR OPERATING COMPANY. INC. EDWIN I. HATCH NUCLEAR PLANT. UNIT NOS. 1 AND 2 DOCKET NOS. 50-321 AND 50-366 | : c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and | ||
: d. Other appropriate limitations and remedial or compensatory actions. | |||
A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and: | |||
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or | |||
: b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or | |||
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable. | |||
(continued) | |||
HATCH UNIT 2 5.0-14 Amendment No. 223 | |||
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 Safety Function Determination Program (SFDP) (continued) | |||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system. | |||
5.5.11 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications. | |||
: a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews. | |||
: b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following: | |||
: 1. A change in the TS incorporated in the license; or | |||
: 2. A change to the updated FSAR or Bases that requires NRC approval pursuant to 10 CFR 50.59. | |||
: c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR. | |||
: d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRC prior to implementation. Changes to the Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71(e). | |||
(continued) | |||
HATCH UNIT 2 5.0-15 Amendment No. 223 | |||
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION AMENDMENT NO. 279 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-57 AND AMENDMENT NO. 223 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-5 SOUTHERN NUCLEAR OPERATING COMPANY. INC. | |||
EDWIN I. HATCH NUCLEAR PLANT. UNIT NOS. 1 AND 2 DOCKET NOS. 50-321 AND 50-366 | |||
==1.0 INTRODUCTION== | |||
By application dated October 10, 2014 (Agencywide Documents Access and Management System (ADAMS) Accession No. ML14288A226), as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016 (ADAMS Accession Nos. ML16116A201, ML15288A232, and ML16239A309, respectively), Southern Nuclear Operating Company, Inc. | |||
(SNC, the licensee), requested changes to the Technical Specifications (TSs) for the Edwin I. | |||
Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2. The proposed changes would incorporate 21 generic changes to the HNP TSs. Specifically, SNC requests to adopt 18 previously U.S. | |||
Nuclear Regulatory Commission (NRC)-approved Technical Specifications Task Force (TSTF) travelers, two TSTF T-travelers, and one feature of NUREG-1433, Revision 4, "Standard Technical Specifications - General Electric BWR/4 Plants" (ADAMS Accession Nos. | |||
ML12104A192 and ML12104A193), known as the Improved Standard Technical Specifications (ISTS) not associated with a traveler. SNC stated that these changes would increase the consistency between the HNP TSs, the ISTS for boiling water reactor (BWR)/4 plants, and the TSs of the other plants in the SNC fleet. The proposed changes are listed below. | |||
The requested TSTFs for NRC approval are: | |||
: 1. TSTF-30-A, Revision 3, "Extend the Completion Time for inoperable isolation valve to a closed system to 72 hours" | |||
: 2. TSTF-45-A, Revision 2, "Exempt verification of CIVs [containment isolation valves] that are not locked, sealed or otherwise secured" | |||
: 3. TSTF-46-A, Revision 1, "Clarify the CIV surveillance to apply only to automatic isolation valves" | |||
: 4. TSTF-222-A, Revision 1, "Control Rod Scram Time Testing (BWR)" | |||
Enclosure 3 | |||
: 5. TSTF-264-A, Revision 0, "3.3.9 and 3.3.10 - Delete flux monitors specific overlap requirement SRs [surveillance requirements)" | |||
: 6. TSTF-269-A, Revision 2, "Allow administrative means of position verification for locked or sealed valves" | |||
: 7. TSTF-273-A, Revision 2, "SFDP [Safety Function Determination Program] Clarifications" | |||
: 8. TSTF-283-A, Revision 3, "Modify Section 3.8 Mode restriction Notes" | |||
: 9. TSTF-284-A, Revision 3, "Add 'Met vs. Perform' to Specification 1.4, Frequency" | |||
: 10. TSTF-295-A, Revision 0, "Modify Note 2 to Actions of PAM [Post-Accident Monitoring] | |||
Table to Allow Separate Condition Entry for Each Penetration" | |||
: 11. TSTF-306-A, Revision 2, "Add Action to LCO [Limiting Condition for Operation] 3.3.6.1 to give option to isolate the penetration" | |||
: 12. TSTF-308-A, Revision 1, "Determination of Cumulative and Projected Dose Contributions in RECP [Radioactive Effluent Controls Program)" | |||
: 13. TSTF-318-A, Revision 0, "Revise 3.5.1 for one LPCI [low pressure coolant injection] | |||
pump inoperable in each of two ECCS [emergency core cooling system] divisions" | |||
: 14. TSTF-322-A, Revision 2, "Secondary Containment and Shield Building Boundary Integrity SRs" | |||
: 15. TSTF-323-A, Revision 0, "EFCV [Excess Flow Check Valve] Completion Time to 72 hours" | |||
: 16. TSTF-37 4-A, Revision 0, "Revision to TS 5.5.13 and associated TS Bases for Diesel Fuel Oil" | |||
: 17. TSTF-400-A, Revision 1, "Clarify SR on Bypass of DG [Diesel Generator] Automatic Trips" | |||
: 18. TSTF-439-A, Revision 2, "Eliminate Second Completion Times Limiting Time From Discovery of Failure To Meet an LCO" T-travelers are travelers that have not been approved by the NRC staff, but have been approved by the TSTF. The following T-travelers are being requested for NRC approval: | |||
: 19. TSTF-458-T, Revision 0, "Removing Restart of Shutdown Clock for Increasing Suppression Pool Temperature" | |||
: 20. TSTF-464-T, Revision 0, "Clarify the Control Rod Block Instrumentation Required Action" | |||
In addition, SNC requested one change for NRC approval that reflects ISTS requirements that were not added by a traveler: | |||
: 21. ISTS Adoption #1 - Revise the 5.5.7 Introductory Paragraph to be Consistent with the ISTS The supplements dated May 4, 2015, October 15, 2015, and August 26, 2016, provided additional information that clarified the application, did not expand the scope of the application as originally noticed, and did not change the NRC staff's original proposed no significant hazards consideration determination as published the Federal Register on March 31, 2015 (80 FR 17095; July 19, 1995). | |||
==2.0 REGULATORY EVALUATION== | |||
Title 10 of the Code of Federal Regulations (10 CFR) Section 50.36, "Technical specifications," | |||
requires TSs for nuclear reactors to include items in the following categories: (1) safety limits, limiting safety system settings, and limiting control settings; (2) LCOs; (3) SRs; (4) design features; and (5) administrative controls. The regulation does not specify the particular requirements to be included in a plant's TSs. | |||
On July 22, 1993, the Commission published the "Final Policy Statement on Technical Specifications Improvements for Nuclear Power Reactors" (58 FR 39132). This Final Policy Statement discussed criteria for determining which items must be included in the TS as LCOs. | |||
These criteria were subsequently incorporated into 1O CFR 50.36 (60 FR 36953). Specifically, 10 CFR 50.36(c)(2)(ii) requires that an LCO be established for each item meeting one or more of the following criteria: | |||
Criterion 1: Installed instrumentation that is used to detect, and indicate in the control room, a significant abnormal degradation of the reactor coolant pressure boundary. | |||
Criterion 2: A process variable, design feature, or operating restriction that is an initial condition of a design basis accident or transient analysis that either assumes the failure of or presents a challenge to the integrity of a fission product barrier. | |||
Criterion 3: A structure, system, or component that is part of the primary success path and which functions or actuates to mitigate a design basis accident or transient that either assumes the failure of or presents a challenge to the integrity of a fission product barrier. | |||
Criterion 4: A structure, system, or component which operating experience or probabilistic risk assessment has shown to be significant to public health and safety. | |||
In determining the acceptability of TS changes, the NRC staff considers the requirements of 1O CFR 50.36 using the guidance in the ISTS and the associated Bases for the safety limits and LCOs, and the references cited in the Bases. As discussed in the Final Policy Statement, the NRC staff reviews, on a case-by-case basis, whether enforceable regulatory controls (e.g., | |||
10 CFR 50.59) are needed for material moved to licensee-controlled documents, such as the updated safety analysis report, the Technical Requirements Manual, the TS Bases, the Quality Assurance Plan, etc. The NRC staff determines that plant-specific adoptions of ISTS format and content provide continued, adequate protection for the public health and safety when (1) the change is editorial, administrative, or provides clarification (i.e., no requirements are materially altered); (2) the change is more restrictive than the licensee's current requirement; or (3) the change is less restrictive than the licensee's current requirement, but nonetheless still affords adequate assurance of safety when judged against current regulatory standards and the facility's licensing basis. | |||
The NRC staff used the ISTS, Revision 4, issued in April 2012, in its review of the TS changes proposed by SNC. The NRC staff also referred to the TSTF travelers associated with the ISTS changes proposed for adoption by SNC. The NRC staff notes that in September 1992, the Commission issued the ISTSs (NUREG-1430 through NUREG-1434), which were developed using the guidance and criteria contained in the Commission's Final Policy Statement (58 FR 39132). In the current revisions of NUREG-1430 through NUREG-1434, the word "improved" has been dropped from the titles, therefore, throughout the rest of this safety evaluation, standard technical specifications (STS) is used in place of ISTS for consistency, except when it is contained in a document's title. | |||
== | ==3.0 TECHNICAL EVALUATION== | ||
3.1 TSTF-30-A. Revision 3, "Extend the Completion Time for inoperable isolation valve to a closed system to 72 hours" TSTF-323-A. Revision 0. "Excess Flow Check Valve (EFCV) Completion Time to 72 hours" TSTF-30-A, Revision 3, revised BWR STS 3.6.1.3, "Primary Containment Isolation Valves (PCIVs)," Actions Condition C, "One or more penetration flow paths with one PCIV [primary containment isolation valve] inoperable," which is only applicable to penetration flow paths with one PCIV. Specifically, TSTF-30-A, Revision 3, revised the Completion Times for Required Action C.1 to allow 72 hours, instead of 4 hours, to isolate an inoperable PCIV in a closed system. | |||
TSTF-323-A, Revision 0, extended the Completion Time to 72 hours for inoperable CIVs where there was only a single valve on the containment penetration. This was in recognition that these penetrations were designed with some other acceptable barrier (e.g., closed system). The NRC's approval of TSTF-323, Revision 0, preceded the NRC's approval of TSTF-30, Revision 3, since TSTF-323-A was approved in March of 1999, whereas TSTF-30-A was approved by the NRC in a letter dated August 16, 1999. As a result, approval of the TSTS-323-A, Revision 0, change preceded approval of, and was subsumed assumed, in the final version (Revision 3) of TSTF-30. | |||
HNP TS LCO 3.6.1.3, Condition C, is applicable to penetration flow paths with only one PCIV. | |||
With one or more penetration flow paths with one PCIV inoperable, except due to leakage not within limits, Required Action C.1 requires isolation of the affected penetration flow path by use of at least one closed and deactivated automatic valve, closed manual valve, or blind flange. | |||
Current Completion Time for Required Action C.1 of HNP TS 3.6.1.3 states: | |||
4 hours except for excess flow check valve (EFCV) line, 12 hours for EFCV line Revised Required Action C.1 Completion Time of HNP TS 3.6.1.3 would state: | |||
4 hours except for excess flow check valve (EFCV) and penetrations with a closed system 72 hours for EFCV line and penetrations with a closed system | |||
===NRC Staff Evaluation=== | |||
In the supplement dated May 4, 2015, the licensee provided clarification on the scope of Required Action C.1 where a Completion Time of 4 hours would be retained for penetrations with only one PCIV that is not associated with a closed system or an EFCV. Specifically, the licensee provided examples of penetrations that are covered under 10 CFR Part 50, Appendix A, General Design Criterion 56, "Primary Containment Isolation," in both HNP, Units 1 and 2 (e.g., drywell pressure instrument, torus water level instrument, and traversing in-core probe nitrogen purge line). The licensee also stated that these allowed configurations are consistent with guidance in Regulatory Guide (RG) 1.11, "Instrument Lines Penetrating the Primary Reactor Containment" (ADAMS Accession No. ML100250396). | In the supplement dated May 4, 2015, the licensee provided clarification on the scope of Required Action C.1 where a Completion Time of 4 hours would be retained for penetrations with only one PCIV that is not associated with a closed system or an EFCV. Specifically, the licensee provided examples of penetrations that are covered under 10 CFR Part 50, Appendix A, General Design Criterion 56, "Primary Containment Isolation," in both HNP, Units 1 and 2 (e.g., drywell pressure instrument, torus water level instrument, and traversing in-core probe nitrogen purge line). The licensee also stated that these allowed configurations are consistent with guidance in Regulatory Guide (RG) 1.11, "Instrument Lines Penetrating the Primary Reactor Containment" (ADAMS Accession No. ML100250396). | ||
The NRC staff reviewed the referenced RG 1.11 and HNP, Unit No. 1, Final Safety Analysis Report (FSAR), Subsection 5.2.2.5.4, and HNP, Unit No. 2, FSAR Subsection 6.2.5.3.3, and found that the Completion Time of 4 hours is applicable in these cases. The changes proposed for corresponding PCIV and EFCV action requirements in TS 3.6.1.3 conform to the changes made to the STS by TSTF-30-A, Revision 3, and TSTF-323-A, Revision 0. The BWR/4 design (such as the HNP design) includes a class of single-isolation valve penetrations (i.e., instrumentation lines with an EFCV) that were inadvertently not included in the markup for TSTF-30, Revision 2. That approved traveler extended the Completion Time to 72 hours for inoperable PCIVs in containment penetration flow paths with just one PCIV. The NRC staff has determined that these single-PCIV penetrations used in closed systems provide an acceptable second barrier. Similarly, a Completion Time of 72 hours for inoperable EFCVs is acceptable because EFCVs are installed on penetrations that provide acceptable barriers in the event that the single isolation valve failed. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the changes to TS 3.6.1.3 are acceptable. | The NRC staff reviewed the referenced RG 1.11 and HNP, Unit No. 1, Final Safety Analysis Report (FSAR), Subsection 5.2.2.5.4, and HNP, Unit No. 2, FSAR Subsection 6.2.5.3.3, and found that the Completion Time of 4 hours is applicable in these cases. The changes proposed for corresponding PCIV and EFCV action requirements in TS 3.6.1.3 conform to the changes made to the STS by TSTF-30-A, Revision 3, and TSTF-323-A, Revision 0. The BWR/4 design (such as the HNP design) includes a class of single-isolation valve penetrations (i.e., | ||
3.2 TSTF-45-A. | instrumentation lines with an EFCV) that were inadvertently not included in the markup for TSTF-30, Revision 2. That approved traveler extended the Completion Time to 72 hours for inoperable PCIVs in containment penetration flow paths with just one PCIV. The NRC staff has determined that these single-PCIV penetrations used in closed systems provide an acceptable second barrier. Similarly, a Completion Time of 72 hours for inoperable EFCVs is acceptable because EFCVs are installed on penetrations that provide acceptable barriers in the event that the single isolation valve failed. | ||
Revision 2, "Exempt verification of CIVs that are not locked. sealed or otherwise secured" The NRC approved this change to the STS Revision 1 on July 26, 1999. TSTF-45-A, Revision 2, revised BWR/4 STS 3.6.1.3, "Primary Containment Isolation Valves (PCIVs)," and STS 3.6.4.2, "Secondary Containment Isolation Valves (SCIVs)," by changing valve position verification SRs. Current TS SR 3.6.1.3.2 states: Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and is required to be closed during accident conditions is closed. Revised TS SR 3.6.1.3.2 would state (with the inserted portion in bold): Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. Current TS SR 3.6.1.3.3 states: Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and is required to be closed during accident conditions is closed. Revised TS SR 3.6.1.3.3 would state (with the inserted portion in bold): Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. Current TS SR 3.6.4.2.1 states: Verify each secondary containment isolation manual valve and blind flange that is required to be closed during accident conditions is closed. Revised TS SR 3.6.4.2.1 would state (with the inserted portion in bold): Verify each secondary containment isolation manual valve and blind flange that is not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. NRC Staff Evaluation | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | ||
TSTF-45-A states that the proposed change is consistent with the valve position verification requirement for valves that have a function during an accident in other system TSs. The NRC staff reviewed the proposed changes and determined they are consistent with current HNP SR 3.5.1.2, which requires that each ECCS subsystem be demonstrated operable, in part, by performance of a valve alignment of each valve that is in the flow path that is not locked, sealed, or otherwise secured valves. Multiple HNP systems, such as the reactor core isolation cooling system and the residual heat removal suppression pool cooling system, spray, and drywell spray, are also demonstrated to be operable, in part, by verifying that each valve in the flow path of the system that is not locked, sealed, or otherwise secured in position, is in its correct position (SRs 3.6.2.3.1, 3.6.2.4.1, 3.6.2.5.1, and 3.6.3.1.2, respectively). | |||
Additionally, the changes proposed for HNP TS SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are the same as those contained in TSTF-45-A. | Based on the above, the NRC staff concludes that the changes to TS 3.6.1.3 are acceptable. | ||
3.2 TSTF-45-A. Revision 2, "Exempt verification of CIVs that are not locked. sealed or otherwise secured" The NRC approved this change to the STS Revision 1 on July 26, 1999. TSTF-45-A, Revision 2, revised BWR/4 STS 3.6.1.3, "Primary Containment Isolation Valves (PCIVs)," and STS 3.6.4.2, "Secondary Containment Isolation Valves (SCIVs)," by changing valve position verification SRs. | |||
Current TS SR 3.6.1.3.2 states: | |||
Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and is required to be closed during accident conditions is closed. | |||
Revised TS SR 3.6.1.3.2 would state (with the inserted portion in bold): | |||
Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. | |||
Current TS SR 3.6.1.3.3 states: | |||
Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and is required to be closed during accident conditions is closed. | |||
Revised TS SR 3.6.1.3.3 would state (with the inserted portion in bold): | |||
Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. | |||
Current TS SR 3.6.4.2.1 states: | |||
Verify each secondary containment isolation manual valve and blind flange that is required to be closed during accident conditions is closed. | |||
Revised TS SR 3.6.4.2.1 would state (with the inserted portion in bold): | |||
Verify each secondary containment isolation manual valve and blind flange that is not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed. | |||
===NRC Staff Evaluation=== | |||
TSTF-45-A states that the proposed change is consistent with the valve position verification requirement for valves that have a function during an accident in other system TSs. The NRC staff reviewed the proposed changes and determined they are consistent with current HNP SR 3.5.1.2, which requires that each ECCS subsystem be demonstrated operable, in part, by performance of a valve alignment of each valve that is in the flow path that is not locked, sealed, or otherwise secured valves. Multiple HNP systems, such as the reactor core isolation cooling system and the residual heat removal suppression pool cooling system, spray, and drywell spray, are also demonstrated to be operable, in part, by verifying that each valve in the flow path of the system that is not locked, sealed, or otherwise secured in position, is in its correct position (SRs 3.6.2.3.1, 3.6.2.4.1, 3.6.2.5.1, and 3.6.3.1.2, respectively). Additionally, the changes proposed for HNP TS SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are the same as those contained in TSTF-45-A. | |||
The NRC staff concludes that excluding locked, sealed, or otherwise secured valves from periodic position verification is acceptable because these valves were verified to be in the correct position upon being locked, sealed, or otherwise secured. The position of these valves is controlled administratively, and periodic visual verification is not necessary. | The NRC staff concludes that excluding locked, sealed, or otherwise secured valves from periodic position verification is acceptable because these valves were verified to be in the correct position upon being locked, sealed, or otherwise secured. The position of these valves is controlled administratively, and periodic visual verification is not necessary. | ||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes that the changes to SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are acceptable. | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | ||
3.3 TSTF-46-A. | Based on the above, the NRC staff concludes that the changes to SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are acceptable. | ||
Revision 1. "Clarify the CIV surveillance to apply only to automatic isolation valves" The NRC did not issue a letter approving this change to STS, Revision 1; however, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-46-A revises STS SR 3.6.3.5 to delete the reference to verifying the isolation time of "each power operated" CIV and only require verification of each "automatic isolation valve." Current TS SR 3.6.1.3.5 states: Verify the isolation time of each power operated and each automatic PCIV, except for MSIVs, is within limits. Revised TS SR 3.6.1.3.5 would state (with the removed portion in strikeout and additions in bold): Verify the isolation time of each pmver operated and each power operated, automatic PCIV, except for MSIVs, is within limits. Current TS SR 3.6.4.2.2 states: Verify the isolation time of each power operated and each automatic SCIV is within limits. Revised TS SR 3.6.4.2.2 would state (with the removed portion in strikeout): | 3.3 TSTF-46-A. Revision 1. "Clarify the CIV surveillance to apply only to automatic isolation valves" The NRC did not issue a letter approving this change to STS, Revision 1; however, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-46-A revises STS SR 3.6.3.5 to delete the reference to verifying the isolation time of "each power operated" CIV and only require verification of each "automatic isolation valve." | ||
Verify the isolation time of each power operated, and each automatic SCIV is within limits. NRC Staff Evaluation | Current TS SR 3.6.1.3.5 states: | ||
The original wording states that the surveillance applied to power operated or automatic containment isolation valves, which could result in an interpretation that power operated valves that do not receive an automatic closure signal for design-basis events are also required to have a closure time associated with them. These changes removed the unintended requirement to verify isolation times of non-automatic power operated CIVs. The changes proposed for the corresponding CIV SRs in HNP TS 3.6.1.3 and TS 3.6.4.2 are the same as those contained in TSTF-46-A. | Verify the isolation time of each power operated and each automatic PCIV, except for MSIVs, is within limits. | ||
The NRC staff has determined that these changes only clarify the intended scope of CIVs covered by the existing surveillances and are, therefore, administrative in nature. Because the current scope of these surveillances has not changed, there is no impact to safety. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes that the proposed changes to SRs 3.6.1.3 and 3.6.4.2 are acceptable. | Revised TS SR 3.6.1.3.5 would state (with the removed portion in strikeout and additions in bold): | ||
3.4 TSTF-222-A, Revision 1. "Control Rod Scram Time Testing" TSTF-222-A revised BWR STS 3.1.4, "Control Rod Scram Times." TS 3.1.4, "Control Rod Scram Times," SRs 3.1.4.1 and 3.1.4.4, are revised to only require scram time testing of control rods that are in an affected core cell. Current TS SR 3.1.4.1 has a Frequency of: Prior to exceeding 40% RTP [rated thermal power] after fuel movement within the reactor vessel Prior to exceeding 40% RTP after each reactor shutdown 120 days | Verify the isolation time of each pmver operated and each power operated, automatic PCIV, except for MSIVs, is within limits. | ||
Prior to exceeding 40% RTP after fuel movement within the affected core cell. Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time. NRC Staff Evaluation | |||
The changes to SR 3.1.4.1 and SR 3.1.4.4 result in only the affected control rod requiring testing after fuel movement. | Current TS SR 3.6.4.2.2 states: | ||
If a control rod is not affected by fuel movement, there is no basis for expecting that the control rod will perform differently than during the previous scram time test. The NRC staff has determined that these changes only clarify the intent of the existing requirements and do not reduce the testing currently required for demonstrating control rod operability. | Verify the isolation time of each power operated and each automatic SCIV is within limits. | ||
Therefore, there is no impact to safety since control rod scram time testing will be performed following any fuel movement that could affect the scram time. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes that the proposed changes to SR 3.1.4.1 and 3.1.4.4 are acceptable. | Revised TS SR 3.6.4.2.2 would state (with the removed portion in strikeout): | ||
3.5 TSTF-264-A, Revision 0, "3.3.9 and 3.3.10 -Delete flux monitors specific overlap requirement SRs" TSTF-264-A was submitted to the NRC on May 9, 1998; approved on July 26, 1999; and incorporated into Revision 2 of NUREG-1433, "Standard Technical Specifications | Verify the isolation time of each power operated, and each automatic SCIV is within limits. | ||
-General Electric Plants (BWR/4)," which was published on June 30, 2001. Revision 4 of NUREG-1433 contains many improvements over STS Revision 0, which was issued in 1992. One objective of these improvements was to make TS requirements in the five STS NUREGs consistent for systems that perform essentially the same functions, where possible. | |||
Such an improvement was approved by the NRC in TSTF-264-A. 3.5.1 Current HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification TS 3.3.1.1, "Reactor Protection System (RPS) Instrumentation," SRs 3.3.1.1.6 and 3.3.1.1.7, require verification of overlap for the source range (neutron flux) monitor (SRM) and intermediate range (neutron flux) monitor (IRM) indications, and for the IRM and average power range (neutron flux) monitor (APRM) indications, respectively. | ===NRC Staff Evaluation=== | ||
The Bases for these SRs explain what constitutes acceptable overlap in each case and state, in part, that: Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block. Overlap between the SRMs and IRMs similarly exists when, prior to withdrawing an SRM from the fully inserted position, its associated IRMs have cleared their downscale rod block Allowable Values, prior to the SRM having reached its upscale rod block Allowable Value. The Frequency of SR 3.3.1.1.6 (IRM-SRM overlap verification) is, "Prior to withdrawing SRMs from the fully inserted position." The surveillance column note in SR 3.3.1.1.7 (APRM-IRM overlap verification) states, "Only required to be met during entry into MODE 2 from MODE 1." The Frequency of SR 3.3.1.1.7 is, "In accordance with the Surveillance Frequency Control Program." SR 3.3.1.1.1 requires a channel check of IRM and APRM channels in accordance with the surveillance frequency control program (SFCP). As specified in TS Table 3.3.1.1-1, in Mode 2, SR 3.3.1.1.6 applies to RPS Function 1.a, IRM Neutron Flux -High, and SR 3.3.1.1.7 applies to RPS Function 1.a, and Function 2.a, APRM Neutron Flux -High (Setdown). | The original wording states that the surveillance applied to power operated or automatic containment isolation valves, which could result in an interpretation that power operated valves that do not receive an automatic closure signal for design-basis events are also required to have a closure time associated with them. These changes removed the unintended requirement to verify isolation times of non-automatic power operated CIVs. | ||
In addition, SR 3.3.1.1.1 applies to both Function 1.a and Function 2.a 3.5.2 Proposed HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification The proposed change revises HNP TS 3.3.1.1, "RPS Instrumentation," by deleting SR 3.3.1.1.6 and SR 3.3.1.1.7, which verify the SRM-IRM neutron flux indication overlap and the IRM-APRM neutron flux indication overlap, respectively. | The changes proposed for the corresponding CIV SRs in HNP TS 3.6.1.3 and TS 3.6.4.2 are the same as those contained in TSTF-46-A. The NRC staff has determined that these changes only clarify the intended scope of CIVs covered by the existing surveillances and are, therefore, administrative in nature. Because the current scope of these surveillances has not changed, there is no impact to safety. | ||
TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7. Current TS SR 3.3.1.1.6 states: Verify the source range monitor (SRM) and intermediate range monitor (IRM) channels overlap. Revised TS SR 3.3.1.1.6 would state: (Not used.) Current TS SR 3.3.1.1. 7 states: -----------------------------N()TE:------------------------------ | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | ||
()nly required to be met during entry into M()DE: 2 from M()DE: 1. Verify the IRM and APRM channels overlap. Revised TS SR 3.3.1.1.7 would state: (Not used.) A Channel Check is currently required for Functions 1.a and 2.a with a Frequency of "In accordance with the Surveillance Frequency Control Program." HNP TS Section 1.1 defines a Channel Check as follows (the same as the STS definition): | Based on the above, the NRC staff concludes that the proposed changes to SRs 3.6.1.3 and 3.6.4.2 are acceptable. | ||
A CHANNE:L CHE:CK shall be the qualitative assessment, by observation, of channel behavior during operation. | 3.4 TSTF-222-A, Revision 1. "Control Rod Scram Time Testing" TSTF-222-A revised BWR STS 3.1.4, "Control Rod Scram Times." TS 3.1.4, "Control Rod Scram Times," SRs 3.1.4.1 and 3.1.4.4, are revised to only require scram time testing of control rods that are in an affected core cell. | ||
This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter. | Current TS SR 3.1.4.1 has a Frequency of: | ||
TSTF-264-A did not propose changes to this definition in the STS because it may be interpreted as requiring SRM-IRM and IRM-APRM neutron flux indication overlap verification for the IRM-and APRM-associated RPS Functions that are required to be operable in Mode 2 (i.e., Functions 1.a and 2.a). With this interpretation, the present indication overlap verifications may be considered redundant to the channel check SR SNC stated that it will relocate the existing discussions of the SR 3.3.1.1.6 and SR 3.3.1.1.7 overlap verification requirements from the existing Bases to the Bases for SR 3. 3.1.1.1. Specifically, the licensee plans to add the following paragraph to SR 3.3.1.1.1 Bases: The agreement criteria includes an expectation of one decade of overlap when transitioning between neutron flux instrumentation. | Prior to exceeding 40% RTP [rated thermal power] after fuel movement within the reactor vessel Prior to exceeding 40% RTP after each reactor shutdown ~ 120 days | ||
The overlap between SRMs and IRMs must be demonstrated prior to withdrawing SRMs from the fully inserted position since indication is being transitioned from the SRMs to the IRMs. This will ensure that reactor power will not be increased into a neutron flux | |||
The overlap between IRMs and APRMs is of concern when reducing power into the IRM range (entry into MODE 2 from MODE 1 ). On power increases, the system design will prevent further increases (by initiating a rod block) if adequate overlap is not maintained. | TS SR 3.1.4.4 has a Frequency of: | ||
Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block. Overlap between SRMs and IRMs similarly exists when, prior to withdrawing the SRMs from the fully inserted position, IRMs are above mid-scale on range 1 before SRMs have reached the upscale rod block. If overlap for a group of channels is not demonstrated (e.g., IRM/APRM overlap), the reason for the failure of the Surveillance should be determined and the appropriate channel(s) declared inoperable. | Prior to exceeding 40% RTP after work on control rod or CRD [control rode drive] | ||
Only those appropriate channels that are required in the current MODE or condition should be declared inoperable. | System that could affect scram time TS SRs 3.1.4.1 and 3.1.4.4 are revised, which deletes the Frequency shown in bold text above from SR 3.1.4.1, and adds a new Frequency as shown in bold text below to SR 3.1.4.4 with an AND statement: | ||
NRC Staff Evaluation | Prior to exceeding 40% RTP after fuel movement within the affected core cell. | ||
In adopting TSTF-264-A, the HNP TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7. | Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time. | ||
This is in lieu of removing these rows and renumbering the existing subsequent SRs, as done in the traveler's markup of NUREG-1433, Revision 1. In addition, the references to these SRs in HNP TS Table 3.3.1.1-1 are removed. References to SR 3.3.1.1.6 and SR 3.3.1.1.7 in the Bases for HNP TS 3.3.1.2, "SRM Instrumentation," will be replaced by references to SR 3.3.1.1.1. | |||
No changes were needed to HNP TS 3.3.1.2 requirements on SRM channel operability, actions, or surveillances in Mode 2 with IRMs on Range 2 or below. SNC stated that it would maintain the existing neutron flux monitor channel indication overlap criteria by relocating the discussion of the criteria to the Bases for HNP TS SR 3.3.1.1.1 for RPS Functions 1.a and 2.a. The overlap check will be performed when SR 3.3.1.1.1 is performed for RPS Functions 1.a and 2.a. Although the TS Bases are a licensee-controlled document, changes to the TS Bases are controlled by the 10 CFR 50.59 process. The NRC staff finds that the licensee continues to uphold the previously approved definition of overlap and will maintain compliance with the requirement to verify SRM-IRM and IRM-APRM indication overlap at the necessary ranges of reactor power by performing the channel check specified for TS 3.3.1.1 Functions 1.a and 2.a at the Frequencies stated in the SFCP. The NRC staff has determined that the proposed changes are in accordance with NRC-approved TSTF-264, Revision 0, with no technical deviations, are consistent with STS Revision 4.0, and the overlap check will still be performed during surveillance testing. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes the proposed changes to SR 3.3.1.1.6, SR 3.3.1.1.7, and Table 3.3.1.1 1 of HNP TS 3.3.1.1 to be acceptable. | ===NRC Staff Evaluation=== | ||
3.6 TSTF-269-A. | The changes to SR 3.1.4.1 and SR 3.1.4.4 result in only the affected control rod requiring testing after fuel movement. If a control rod is not affected by fuel movement, there is no basis for expecting that the control rod will perform differently than during the previous scram time test. The NRC staff has determined that these changes only clarify the intent of the existing requirements and do not reduce the testing currently required for demonstrating control rod operability. Therefore, there is no impact to safety since control rod scram time testing will be performed following any fuel movement that could affect the scram time. | ||
Revision 2. "Allow administrative means of position verification for locked or sealed valves" The NRC approved this change to STS Revision 1 on July 27, 1999. TSTF-269-A revised STS 3.6.1.3, "Primary Containment Isolation Valves," and 3.6.4.2, "Secondary Containment Isolation Valves," by adding a note that isolation devices that are locked, sealed, or otherwise secured may be verified by use of administrative means. Current TS 3.6.1.3, Required Action C.2 for Condition C, "One or more penetration flow paths with one PCIV inoperable except due to leakage not within limit," requires: | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | ||
Based on the above, the NRC staff concludes that the proposed changes to SR 3.1.4.1 and 3.1.4.4 are acceptable. | |||
3.5 TSTF-264-A, Revision 0, "3.3.9 and 3.3.10 - Delete flux monitors specific overlap requirement SRs" TSTF-264-A was submitted to the NRC on May 9, 1998; approved on July 26, 1999; and incorporated into Revision 2 of NUREG-1433, "Standard Technical Specifications - General Electric Plants (BWR/4)," which was published on June 30, 2001. Revision 4 of NUREG-1433 contains many improvements over STS Revision 0, which was issued in 1992. One objective of these improvements was to make TS requirements in the five STS NUREGs consistent for systems that perform essentially the same functions, where possible. Such an improvement was approved by the NRC in TSTF-264-A. | |||
3.5.1 Current HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification TS 3.3.1.1, "Reactor Protection System (RPS) Instrumentation," SRs 3.3.1.1.6 and 3.3.1.1.7, require verification of overlap for the source range (neutron flux) monitor (SRM) and intermediate range (neutron flux) monitor (IRM) indications, and for the IRM and average power range (neutron flux) monitor (APRM) indications, respectively. The Bases for these SRs explain what constitutes acceptable overlap in each case and state, in part, that: | |||
Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block. Overlap between the SRMs and IRMs similarly exists when, prior to withdrawing an SRM from the fully inserted position, its associated IRMs have cleared their downscale rod block Allowable Values, prior to the SRM having reached its upscale rod block Allowable Value. | |||
The Frequency of SR 3.3.1.1.6 (IRM-SRM overlap verification) is, "Prior to withdrawing SRMs from the fully inserted position." The surveillance column note in SR 3.3.1.1.7 (APRM-IRM overlap verification) states, "Only required to be met during entry into MODE 2 from MODE 1." | |||
The Frequency of SR 3.3.1.1.7 is, "In accordance with the Surveillance Frequency Control Program." | |||
SR 3.3.1.1.1 requires a channel check of IRM and APRM channels in accordance with the surveillance frequency control program (SFCP). | |||
As specified in TS Table 3.3.1.1-1, in Mode 2, SR 3.3.1.1.6 applies to RPS Function 1.a, IRM Neutron Flux - High, and SR 3.3.1.1.7 applies to RPS Function 1.a, and Function 2.a, APRM Neutron Flux - High (Setdown). In addition, SR 3.3.1.1.1 applies to both Function 1.a and Function 2.a 3.5.2 Proposed HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification The proposed change revises HNP TS 3.3.1.1, "RPS Instrumentation," by deleting SR 3.3.1.1.6 and SR 3.3.1.1.7, which verify the SRM-IRM neutron flux indication overlap and the IRM-APRM neutron flux indication overlap, respectively. TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7. | |||
Current TS SR 3.3.1.1.6 states: | |||
Verify the source range monitor (SRM) and intermediate range monitor (IRM) channels overlap. | |||
Revised TS SR 3.3.1.1.6 would state: | |||
(Not used.) | |||
Current TS SR 3.3.1.1. 7 states: | |||
-----------------------------N()TE:------------------------------ | |||
()nly required to be met during entry into M()DE: 2 from M()DE: 1. | |||
Verify the IRM and APRM channels overlap. | |||
Revised TS SR 3.3.1.1.7 would state: | |||
(Not used.) | |||
A Channel Check is currently required for Functions 1.a and 2.a with a Frequency of "In accordance with the Surveillance Frequency Control Program." HNP TS Section 1.1 defines a Channel Check as follows (the same as the STS definition): | |||
A CHANNE:L CHE:CK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter. | |||
TSTF-264-A did not propose changes to this definition in the STS because it may be interpreted as requiring SRM-IRM and IRM-APRM neutron flux indication overlap verification for the IRM-and APRM-associated RPS Functions that are required to be operable in Mode 2 (i.e., | |||
Functions 1.a and 2.a). With this interpretation, the present indication overlap verifications may be considered redundant to the channel check SR SNC stated that it will relocate the existing discussions of the SR 3.3.1.1.6 and SR 3.3.1.1.7 overlap verification requirements from the existing Bases to the Bases for SR 3. 3.1.1.1. | |||
Specifically, the licensee plans to add the following paragraph to SR 3.3.1.1.1 Bases: | |||
The agreement criteria includes an expectation of one decade of overlap when transitioning between neutron flux instrumentation. The overlap between SRMs and IRMs must be demonstrated prior to withdrawing SRMs from the fully inserted position since indication is being transitioned from the SRMs to the IRMs. This will ensure that reactor power will not be increased into a neutron flux | |||
region without adequate indication. The overlap between IRMs and APRMs is of concern when reducing power into the IRM range (entry into MODE 2 from MODE 1). On power increases, the system design will prevent further increases (by initiating a rod block) if adequate overlap is not maintained. Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block. | |||
Overlap between SRMs and IRMs similarly exists when, prior to withdrawing the SRMs from the fully inserted position, IRMs are above mid-scale on range 1 before SRMs have reached the upscale rod block. | |||
If overlap for a group of channels is not demonstrated (e.g., IRM/APRM overlap), | |||
the reason for the failure of the Surveillance should be determined and the appropriate channel(s) declared inoperable. Only those appropriate channels that are required in the current MODE or condition should be declared inoperable. | |||
===NRC Staff Evaluation=== | |||
In adopting TSTF-264-A, the HNP TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7. This is in lieu of removing these rows and renumbering the existing subsequent SRs, as done in the traveler's markup of NUREG-1433, Revision 1. In addition, the references to these SRs in HNP TS Table 3.3.1.1-1 are removed. References to SR 3.3.1.1.6 and SR 3.3.1.1.7 in the Bases for HNP TS 3.3.1.2, "SRM Instrumentation," will be replaced by references to SR 3.3.1.1.1. No changes were needed to HNP TS 3.3.1.2 requirements on SRM channel operability, actions, or surveillances in Mode 2 with IRMs on Range 2 or below. | |||
SNC stated that it would maintain the existing neutron flux monitor channel indication overlap criteria by relocating the discussion of the criteria to the Bases for HNP TS SR 3.3.1.1.1 for RPS Functions 1.a and 2.a. The overlap check will be performed when SR 3.3.1.1.1 is performed for RPS Functions 1.a and 2.a. Although the TS Bases are a licensee-controlled document, changes to the TS Bases are controlled by the 10 CFR 50.59 process. The NRC staff finds that the licensee continues to uphold the previously approved definition of overlap and will maintain compliance with the requirement to verify SRM-IRM and IRM-APRM indication overlap at the necessary ranges of reactor power by performing the channel check specified for TS 3.3.1.1 Functions 1.a and 2.a at the Frequencies stated in the SFCP. | |||
The NRC staff has determined that the proposed changes are in accordance with NRC-approved TSTF-264, Revision 0, with no technical deviations, are consistent with STS Revision 4.0, and the overlap check will still be performed during surveillance testing. | |||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | |||
Based on the above, the NRC staff concludes the proposed changes to SR 3.3.1.1.6, SR 3.3.1.1.7, and Table 3.3.1.1 1 of HNP TS 3.3.1.1 to be acceptable. | |||
3.6 TSTF-269-A. Revision 2. "Allow administrative means of position verification for locked or sealed valves" The NRC approved this change to STS Revision 1 on July 27, 1999. TSTF-269-A revised STS 3.6.1.3, "Primary Containment Isolation Valves," and 3.6.4.2, "Secondary Containment Isolation Valves," by adding a note that isolation devices that are locked, sealed, or otherwise secured may be verified by use of administrative means. | |||
Current TS 3.6.1.3, Required Action C.2 for Condition C, "One or more penetration flow paths with one PCIV inoperable except due to leakage not within limit," requires: | |||
Verify the affected penetration flow path is isolated. | Verify the affected penetration flow path is isolated. | ||
With a Frequency of: Once per 31 days Current TS 3.6.4.2, Required Action A.2 for Condition A, "One or more penetration flow paths with one SCIV inoperable," requires: | With a Frequency of: | ||
Once per 31 days Current TS 3.6.4.2, Required Action A.2 for Condition A, "One or more penetration flow paths with one SCIV inoperable," requires: | |||
Verify the affected penetration flow path is isolated. | Verify the affected penetration flow path is isolated. | ||
With a Frequency of: Once per 31 days. Revised TS 3.6.1.3 and TS 3.6.4.2 would add the following NOTE in the subject Required Actions C.2 and A.2, respectively. | With a Frequency of: | ||
Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. NRC Staff Evaluation | Once per 31 days. | ||
The NRC staff has reviewed the proposed changes to TS 3.6.1.3 and TS 3.6.4.2 and has determined that administrative controls for such isolation valves have proven to be adequate to ensure the valves are maintained in the positions required by the plant safety analyses when primary and secondary containment are required to be operable. | Revised TS 3.6.1.3 and TS 3.6.4.2 would add the following NOTE in the subject Required Actions C.2 and A.2, respectively. | ||
The licensee did not propose a change to Action E since HNP TSs do not contain an equivalent in STS 3.6.1.3. The NRC staff has determined that this is acceptable because TSTF-269-A modification of STS 3.6.1.3 was marked as optional for licensees and HNP TS 3.6.1.3 Action E contains the shutdown | Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means. | ||
: 3. 7 TSTF-273-A, Revision 2, "SFDP [Safety Function Determination Program] Clarifications" The NRC approved TSTF-273-A, Revision 2, to STS Revision 1, as documented in a letter from William Beckner, NRC, to James Davis, Nuclear Energy Institute (NEI), dated August 16, 1999 (ADAMS Accession No. ML16237A031). | |||
TSTF-273-A modified STS 5.5.12, "Safety Function Determination Program (SFDP)," which implements the requirements of LCO 3.0.6. HNP TS 5.5.10, "Safety Function Determination Program (SFDP)," is similar to STS 5.5.12 and contains the following paragraphs: | ===NRC Staff Evaluation=== | ||
The NRC staff has reviewed the proposed changes to TS 3.6.1.3 and TS 3.6.4.2 and has determined that administrative controls for such isolation valves have proven to be adequate to ensure the valves are maintained in the positions required by the plant safety analyses when primary and secondary containment are required to be operable. The licensee did not propose a change to Action E since HNP TSs do not contain an equivalent in STS 3.6.1.3. The NRC staff has determined that this is acceptable because TSTF-269-A modification of STS 3.6.1.3 was marked as optional for licensees and HNP TS 3.6.1.3 Action E contains the shutdown | |||
For the purpose of this program, a loss of safety function may exist when a support system is inoperable. | |||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. The proposed change adds the following statements (shown in bold) in those paragraphs: | requirements in the instance when Required Actions and associated Completion Times of Conditions A, B, C, and D are not met. | ||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | |||
For the purpose of this program, a loss of safety function may exist when a support system is inoperable. | Based on the above, the NRC staff concludes that the changes to TS 3.6.1.3 and TS 3.6.4.2 are acceptable. | ||
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by the inoperability of a single Technical Specification support system, the | : 3. 7 TSTF-273-A, Revision 2, "SFDP [Safety Function Determination Program] Clarifications" The NRC approved TSTF-273-A, Revision 2, to STS Revision 1, as documented in a letter from William Beckner, NRC, to James Davis, Nuclear Energy Institute (NEI), dated August 16, 1999 (ADAMS Accession No. ML16237A031). TSTF-273-A modified STS 5.5.12, "Safety Function Determination Program (SFDP)," which implements the requirements of LCO 3.0.6. HNP TS 5.5.10, "Safety Function Determination Program (SFDP)," is similar to STS 5.5.12 and contains the following paragraphs: | ||
SNC proposed to revise TS 5.5.10 by incorporating TSTF-273-A, Revision 2, changes without deviations. | A loss of safety function exists when, assuming no concurrent single failure, a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable. | ||
The changes to TS 5.5.10, and the Bases for LCO 3.0.6, are intended to clarify the intent of LCO 3.0.6 in the event a single inoperable TS support system makes both redundant subsystems of a supported system inoperable (a loss of safety function condition). | and The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. | ||
The STS were developed such that the LCO actions for a single support system inoperability would be addressed by that support system's actions, without cascading to the supported system's LCO actions. LCO 3.0.6 establishes this exception to LCO 3.0.2 for support systems that have an LCO specified in the TSs. However, LCO 3.0.6 also requires an evaluation under the SFDP to ensure that a loss of safety function does not exist. The NRC staff concludes that these changes do not affect the design, operation, or maintenance of HNP, but only provide clarity for determining when a loss of safety function condition exists and what LCO actions are required to be taken when a safety function is lost. By clarifying the intent of the existing requirements of the SFDP and LCO 3.0.6, these changes remove an ambiguity that could lead to a misinterpretation of those requirements. | The proposed change adds the following statements (shown in bold) in those paragraphs: | ||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the changes to TS 5.5.10 are acceptable. | A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable. | ||
3.8 TSTF-283-A. | and The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by the inoperability of a single Technical Specification support system, the | ||
Revision 3, "Modify Section 3.8 Mode restriction Notes" TSTF-283-A revised certain SR notes in BWR/4 STS 3.8.1, "AC Sources Operating," and 3.8.4, "DC Sources Operating," to allow full or partial performance of the SRs in the prohibited Modes to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced. | |||
appropriate Conditions and Required Actions to enter are those of the support system. | |||
===NRC Staff Evaluation=== | |||
SNC proposed to revise TS 5.5.10 by incorporating TSTF-273-A, Revision 2, changes without deviations. The changes to TS 5.5.10, and the Bases for LCO 3.0.6, are intended to clarify the intent of LCO 3.0.6 in the event a single inoperable TS support system makes both redundant subsystems of a supported system inoperable (a loss of safety function condition). The STS were developed such that the LCO actions for a single support system inoperability would be addressed by that support system's actions, without cascading to the supported system's LCO actions. LCO 3.0.6 establishes this exception to LCO 3.0.2 for support systems that have an LCO specified in the TSs. However, LCO 3.0.6 also requires an evaluation under the SFDP to ensure that a loss of safety function does not exist. | |||
The NRC staff concludes that these changes do not affect the design, operation, or maintenance of HNP, but only provide clarity for determining when a loss of safety function condition exists and what LCO actions are required to be taken when a safety function is lost. | |||
By clarifying the intent of the existing requirements of the SFDP and LCO 3.0.6, these changes remove an ambiguity that could lead to a misinterpretation of those requirements. | |||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | |||
Based on the above, the NRC staff concludes that the changes to TS 5.5.10 are acceptable. | |||
3.8 TSTF-283-A. Revision 3, "Modify Section 3.8 Mode restriction Notes" TSTF-283-A revised certain SR notes in BWR/4 STS 3.8.1, "AC Sources Operating," and 3.8.4, "DC Sources Operating," to allow full or partial performance of the SRs in the prohibited Modes to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced. | |||
The revised surveillances (SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8) currently have notes prohibiting their performance in Modes 1 or 2, or in Modes 1, 2, or 3. The notes are modified to state that while normally prohibited "in Modes 1 or 2," or "in Modes 1, 2, or 3," the surveillance may be performed to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced. | The revised surveillances (SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8) currently have notes prohibiting their performance in Modes 1 or 2, or in Modes 1, 2, or 3. The notes are modified to state that while normally prohibited "in Modes 1 or 2," or "in Modes 1, 2, or 3," the surveillance may be performed to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced. | ||
* Current TS SR 3.8.1.6 NOTE states, in part, that: This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold) in part, that: This Surveillance shall not normally be performed in MODE 1 or 2. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | * Current TS SR 3.8.1.6 NOTE states, in part, that: | ||
Credit may be taken for unplanned events that satisfy this SR | This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR. | ||
* Current TS SR 3.8.1.7 NOTE 1 states, in part, that: This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. | |||
Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | The revised NOTE would state (with the added text in bold) in part, that: | ||
For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. | This Surveillance shall not normally be performed in MODE 1 or 2. | ||
Credit may be taken for unplanned events that satisfy this SR | However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR | ||
* Current TS SR 3.8.1.8 NOTE 1 states, in part, that: This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. | * Current TS SR 3.8.1.7 NOTE 1 states, in part, that: | ||
Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold): This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that: | ||
For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. | This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR | ||
Credit may be taken for unplanned events that satisfy this SR | * Current TS SR 3.8.1.8 NOTE 1 states, in part, that: | ||
* Current TS SR 3.8.1.9 NOTE 2 states, in part, that: This Surveillance shall not be performed in MODE 1, 2 or 3. However, credit may be taken for unplanned events that satisfy this SR | This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold): | ||
Credit may be taken for unplanned events that satisfy this SR. | This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR | ||
* Current TS SR 3.8.1.10 NOTE 2 states, in part, that: This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1 or 2. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | * Current TS SR 3.8.1.9 NOTE 2 states, in part, that: | ||
Credit may be taken for unplanned events that satisfy this SR. | This Surveillance shall not be performed in MODE 1, 2 or 3. However, credit may be taken for unplanned events that satisfy this SR | ||
* Current TS SR 3.8.1.11 NOTE states, in part, that: This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | |||
Credit may be taken for unplanned events that satisfy this SR. | The revised NOTE would state (with the added text in bold) in part, that: | ||
* Current TS SR 3.8.1.12 NOTE 2 states, in part, that: This Surveillance shall not be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. | This Surveillance shall not normally be performed in MODE 1, 2, or 3. | ||
If either of the other two DGs becomes inoperable, this surveillance shall be suspended. | However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | ||
Credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. | * Current TS SR 3.8.1.10 NOTE 2 states, in part, that: | ||
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or | This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR. | ||
If either of the other two DGs becomes inoperable, this surveillance shall be suspended. | The revised NOTE would state (with the added text in bold), in part, that: | ||
Credit may be taken for unplanned events that satisfy this SR. | This Surveillance shall not normally be performed in MODE 1 or 2. | ||
* Current TS SR 3.8.1.14 NOTE states, in part, that: This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | ||
Credit may be taken for unplanned events that satisfy this SR. | * Current TS SR 3.8.1.11 NOTE states, in part, that: | ||
* Current TS SR 3.8.1.15 NOTE states, in part, that: This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that: | ||
Credit may be taken for unplanned events that satisfy this SR. | This Surveillance shall not normally be performed in MODE 1, 2, or 3. | ||
* Current TS SR 3.8.1.16 NOTE states, in part, that: This Surveillance shall not be performed in MODE 1. 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | ||
Credit may be taken for unplanned events that satisfy this SR. | * Current TS SR 3.8.1.12 NOTE 2 states, in part, that: | ||
* Current TS SR 3.8.1.17 NOTE 2 states, in part, that: This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold), in part, that: This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | This Surveillance shall not be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. If either of the other two DGs becomes inoperable, this surveillance shall be suspended. Credit may be taken for unplanned events that satisfy this SR. | ||
Credit may be taken for unplanned events that satisfy this SR. | The revised NOTE would state (with the added text in bold), in part, that: | ||
* Current TS SR 3.8.4.7 NOTE 2 states: This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold): This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or | ||
Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.4.8 NOTE states: This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR. The revised NOTE would state (with the added text in bold): This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. | enhanced. If either of the other two DGs becomes inoperable, this surveillance shall be suspended. Credit may be taken for unplanned events that satisfy this SR. | ||
Credit may be taken for unplanned events that satisfy this SR. * -As appropriate per unit (i.e., 1 for Unit No. 1 or 2 for Unit No. 2) Deviation from TSTF-283-A: | * Current TS SR 3.8.1.14 NOTE states, in part, that: | ||
The licensee explained a deviation between the proposed changes and the approved traveler for SR 3.8.4.6 as follows: The Hatch Unit 1 and 2 SR 3.8.4.6 does not contain the Note that is modified, so the changes are therefore not applicable to these Hatch SRs. NRC Staff Evaluation | This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. | ||
The revised NOTE would state (with the added text in bold), in part, that: | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. | |||
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.1.15 NOTE states, in part, that: | |||
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. | |||
The revised NOTE would state (with the added text in bold), in part, that: | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. | |||
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.1.16 NOTE states, in part, that: | |||
This Surveillance shall not be performed in MODE 1. 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. | |||
The revised NOTE would state (with the added text in bold), in part, that: | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. | |||
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.1.17 NOTE 2 states, in part, that: | |||
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR. | |||
The revised NOTE would state (with the added text in bold), in part, that: | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3. | |||
However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.4.7 NOTE 2 states: | |||
This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR. | |||
The revised NOTE would state (with the added text in bold): | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* Current TS SR 3.8.4.8 NOTE states: | |||
This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR. | |||
The revised NOTE would state (with the added text in bold): | |||
This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR. | |||
* - As appropriate per unit (i.e., 1 for Unit No. 1 or 2 for Unit No. 2) | |||
Deviation from TSTF-283-A: | |||
The licensee explained a deviation between the proposed changes and the approved traveler for SR 3.8.4.6 as follows: | |||
The Hatch Unit 1 and 2 SR 3.8.4.6 does not contain the Note that is modified, so the changes are therefore not applicable to these Hatch SRs. | |||
===NRC Staff Evaluation=== | |||
Initially, when the NRC staff reviewed the proposed changes to the SR notes for HNP, Unit Nos. 1 and 2, some mismatches in the application of the changes were identified when compared to TSTF-283-A, Revision 3. Consequently, the licensee corrected these mismatches in the May 4, 2015, supplement. | Initially, when the NRC staff reviewed the proposed changes to the SR notes for HNP, Unit Nos. 1 and 2, some mismatches in the application of the changes were identified when compared to TSTF-283-A, Revision 3. Consequently, the licensee corrected these mismatches in the May 4, 2015, supplement. | ||
The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS in NUREG-1433 for BWR/4 plants issued in June 30, 2001. The intent of the TSTF is to allow testing of the emergency diesel generators (EDGs) and Class | The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS in NUREG-1433 for BWR/4 plants issued in June 30, 2001. The intent of the TSTF is to allow testing of the emergency diesel generators (EDGs) and Class 1E batteries in modes not currently allowed for the purpose of maintaining or reestablishing system or component operability (e.g., post-corrective maintenance testing), provided the licensee performs a safety assessment, as described in the application, that determines the safety of the plant would be maintained or enhanced by conducting the operability testing before the testing begins. | ||
The change will also improve the licensee's flexibility in responding to an event during shutdown when other engineered safety feature (ESF) equipment may be out of service. The NRC staff reviewed the licensee's justification for the deviation for SR 3.8.4.6 and concludes the justification to be acceptable because the applicable note does not exist in the current SR 3.8.4.6. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the changes to SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8 are acceptable. | The NRC staff reviewed the proposed changes to SR notes in TS 3.8.1 for the alternating current (AC) electrical power sources and TS 3.8.4 for the direct current (DC) electrical power sources and has determined they would provide flexibility in outage scheduling and reduce outage critical path time, since these EDGs and battery surveillance tests would no longer have to be performed during an outage. In addition, the changes will potentially allow avoiding a plant shutdown if corrective maintenance (planned or unplanned) performed during power operation results in the need to perform any of the above surveillances to demonstrate operability. The change will also improve the licensee's flexibility in responding to an event during shutdown when other engineered safety feature (ESF) equipment may be out of service. | ||
3.9 TSTF-284-A. | The NRC staff reviewed the licensee's justification for the deviation for SR 3.8.4.6 and concludes the justification to be acceptable because the applicable note does not exist in the current SR 3.8.4.6. | ||
Revision 3, "Add 'Met vs. Perform' to Specification 1.4, Frequency" TSTF-284-A, Revision 3, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | ||
The change inserts a discussion paragraph into TS 1.4, and several new examples are added to facilitate the use and application of SR notes that utilize the terms "met" | Based on the above, the NRC staff concludes that the changes to SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8 are acceptable. | ||
* Current TS 1.4 "Frequency," the third paragraph states: Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4-4 discusses these special situations. | 3.9 TSTF-284-A. Revision 3, "Add 'Met vs. Perform' to Specification 1.4, Frequency" TSTF-284-A, Revision 3, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). The change inserts a discussion paragraph into TS 1.4, and several new examples are added to facilitate the use and application of SR notes that utilize the terms "met" | ||
and "perform." The changes also modify certain SRs to appropriately use the "met" and "perform" exceptions. | |||
* Current TS 1.4 "Frequency," the third paragraph states: | |||
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4-4 discusses these special situations. | |||
Revised TS 1.4 "Frequency," the third paragraph would state (with the deleted section shown in strikethrough): | Revised TS 1.4 "Frequency," the third paragraph would state (with the deleted section shown in strikethrough): | ||
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4 4 discusses these special situations. | Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4 4 discusses these special situations. | ||
Current TS 1.4 "Frequency," the fifth paragraph states: The use of "met" or "performed" in these instances conveys specific meanings. | Current TS 1.4 "Frequency," the fifth paragraph states: | ||
A Surveillance is "met" only when the acceptance criteria are satisfied. | The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. | ||
Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. | |||
SR 3.0.4 restrictions would not apply if both the following conditions are satisfied. | SR 3.0.4 restrictions would not apply if both the following conditions are satisfied. | ||
: a. The Surveillance is not required to be performed; and b. The Surveillance is not required to be met or, even if required to be met, is known not to be failed. Revised TS 1.4 "Frequency," the fifth paragraph would state (with the added text in bold and the deleted text in strikethrough): | : a. The Surveillance is not required to be performed; and | ||
The use of "met" or "performed" in these instances conveys specific meanings. | : b. The Surveillance is not required to be met or, even if required to be met, is known not to be failed. | ||
A Surveillance is "met" only when the acceptance criteria are satisfied. | Revised TS 1.4 "Frequency," the fifth paragraph would state (with the added text in bold and the deleted text in strikethrough): | ||
Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. | The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. SR 3.0.4 restrictions would not apply if both the following conditions are satisfied. | ||
SR 3.0.4 restrictions would not apply if both the following conditions are satisfied. c. The Surveillance is not required to be performed, and d. The Surveillance is required to be met or, even if it is required to be met, is known not to be failed. Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. | : c. The Surveillance is not required to be performed, and | ||
For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: | : d. The Surveillance is required to be met or, even if it is required to be met, is known not to be failed. | ||
: a. The Surveillance is not required to be met in the MODE or other specified condition to be entered; or b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed. Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations. | Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied: | ||
TS 1.4, "Frequency," currently includes examples up through Example 1.4-4 regarding the Frequency Based on a Specified Condition. | : a. The Surveillance is not required to be met in the MODE or other specified condition to be entered; or | ||
The proposed change would also add Examples 1.4-5 and 1.4-6. EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | : b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or | ||
--------------------------------N()TE-------------------------------- | : c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed. | ||
()nly required to be performed in M()DE 1. 7 days ------------------------------------------------------------------------- | Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations. | ||
Perform complete cvcle of the valve. The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assumed Applicability of the associated LC()) between performances. | TS 1.4, "Frequency," currently includes examples up through Example 1.4-4 regarding the Frequency Based on a Specified Condition. The proposed change would also add Examples 1.4-5 and 1.4-6. | ||
As the note modifies the required performance of the Surveillance, the note is construed to be part of the "specified Frequency." Should the 7 day interval be | EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | ||
The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day frequency not met, provided operation does not result in entry into MODE 1. Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified frequency applies and would require that the Surveillance had been performed. | --------------------------------N()TE-------------------------------- | ||
If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | ()nly required to be performed in M()DE 1. 7 days | ||
--------------------------------N 0 TE-------------------------------- | ------------------------------------------------------------------------- | ||
Not required to be met in MODE 3. 24 hours ------------------------------------------------------------------------- | Perform complete cvcle of the valve. | ||
Verify parameter is within limits. Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. | The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assumed Applicability of the associated LC()) between performances. | ||
Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. NRC Staff Evaluation | As the note modifies the required performance of the Surveillance, the note is construed to be part of the "specified Frequency." Should the 7 day interval be | ||
The change in TSTF-284-A, Revision 3, is to modify ISTSs, Section 1.4, "Frequency," and to clarify the usage of the terms "met" and "performed" in order to facilitate the application of SR notes. Two new SR Examples, 1.4-5 and 1.4-6, are added to illustrate the application of the terms. STS Section 1.4, "Frequency," defines the proper use and application of SR frequency requirements in the STS format. It states that, "An understanding of the correct application of the specified frequency is necessary for compliance with the SR." It also establishes that, "The specified frequency consists of the requirements of the frequency column of each SR as well as certain NOTES in the Surveillance column that modify performance requirements." The purpose of TSTF-284, Revision 3, was to clarify and make consistent the use of notes in the surveillance column that modify frequency requirements. | |||
In adopting TSTF-284, Revision 3, a licensee must verify that NOTES such as those illustrated by these four examples are used properly and only as necessary. | exceeded while operation is not in MODE 1, this note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day frequency not met, provided operation does not result in entry into MODE 1. | ||
This includes ensuring the associated Bases are also correct. Proper application of these NOTES in the individual SRs in the NUREGs was verified. | Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. | ||
The staff has determined that the proposed changes and HNP adoption of the TSTF changes conforms to the guidance provided in NUREG-1433. | EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY | ||
These changes are administrative in nature because they only serve to clarify the meaning of the terms "met" and "performed" as used in SR notes throughout the HNP TSs. This change serves to improve TS usefulness by clarifying terminology usage and providing additional examples of the application of SR notes. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the proposed changes to TS 1.4 are acceptable. | --------------------------------N 0 TE-------------------------------- | ||
3.10 TSTF-295-A, Revision 0, "Modify Note 2 to Actions of PAM [Post-Accident Monitoring] | Not required to be met in MODE 3. 24 hours | ||
Table to Allow Separate Condition Entrv for Each Penetration" The NRC approved this change to STS Revision 1 on December 21, 1999. TSTF-295-A revised Table 3.3.3.1-1 of STS 3.3.3.1, "Post Accident Monitoring (PAM) Instrumentation," by (1) prefacing the title of Function 8, "Primary Containment Isolation Valve (PCIV) Position," with the phrase "Penetration Flow Path," and (2) prefacing the title of Function 13, "Suppression Pool Water Temperature," with "Relief Valve Discharge Location." These changes were made to clarify how to apply the actions note to these two functions. | ------------------------------------------------------------------------- | ||
The actions note states, "Separate Condition entry is allowed for each Function." The changes clarify that separate condition entry is allowed for each penetration flow path for the PAM PCIV position indication function and for each relief valve discharge location suppression pool temperature indication. | Verify parameter is within limits. | ||
The change proposed for corresponding HNP TS 3.3.3.1, Function 6, "Primary Containment Isolation Valve Position," is the same as the changes made to the STS by TSTF-295-A. | Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. | ||
The licensee did not propose a change to TS 3.3.3.1, Function 9, "Suppression Pool Water Temperature," because of its plant-specific system design as explained by the licensee in its application. | Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour Frequency were not met), SR 3.0.4 would require satisfying the SR. | ||
Current TS Table 3.3.3.1-1, Function 6, states: Primary Containment Isolation Valve Position | |||
The NRC staff has determined that this change is administrative because it only clarifies the intended application of action requirements for inoperable channels of HNP TS 3.3.3.1 Function 6 and is consistent with the TS action requirements for PCIVs. This change does not reduce any existing action requirements for these PAM functions and does not affect plant safety. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes the proposed change to TS Table 3.3.3.1-1 to be acceptable. | ===NRC Staff Evaluation=== | ||
3.11 TSTF-306-A. | The change in TSTF-284-A, Revision 3, is to modify ISTSs, Section 1.4, "Frequency," and to clarify the usage of the terms "met" and "performed" in order to facilitate the application of SR notes. Two new SR Examples, 1.4-5 and 1.4-6, are added to illustrate the application of the terms. | ||
Revision 2, "Add Action to LCO 3.3.6.1 to give option to isolate the penetration" The NRC approved this change to STS Revision 1 on July 13, 2000. TSTF-306-A revised STS 3.3.6.1, "Primary Containment Isolation Instrumentation," by changing the requirements for the two Traversing In-core Probe (TIP) containment isolation instrumentation functions. | |||
Specifically, TSTF-306-A would add functions for TIP system isolation (7.a and 7.b) to STS Table 3.3.6.1-1. | STS Section 1.4, "Frequency," defines the proper use and application of SR frequency requirements in the STS format. It states that, "An understanding of the correct application of the specified frequency is necessary for compliance with the SR." It also establishes that, "The specified frequency consists of the requirements of the frequency column of each SR as well as certain NOTES in the Surveillance column that modify performance requirements." The purpose of TSTF-284, Revision 3, was to clarify and make consistent the use of notes in the surveillance column that modify frequency requirements. | ||
Previously, these functions had been included under Primary Containment Isolation Functions 2.a, "Reactor Vessel Water Level -Low Level 3," and 2.b, "Drywell Pressure -High," respectively. | In adopting TSTF-284, Revision 3, a licensee must verify that NOTES such as those illustrated by these four examples are used properly and only as necessary. This includes ensuring the associated Bases are also correct. Proper application of these NOTES in the individual SRs in the NUREGs was verified. The staff has determined that the proposed changes and HNP adoption of the TSTF changes conforms to the guidance provided in NUREG-1433. These changes are administrative in nature because they only serve to clarify the meaning of the terms "met" and "performed" as used in SR notes throughout the HNP TSs. This change serves to improve TS usefulness by clarifying terminology usage and providing additional examples of the application of SR notes. | ||
TSTF-306-A also revised the actions of STS 3.3.6.1 by listing the new function numbers in the two Completion Times for Required Action A.1. Because these TIP system isolation functions are manual functions, the traveler specified that actions Condition G must be entered immediately upon entering Condition C, "Required Action and associated Completion Time of Condition A or B not met." This action is appropriate because Table 3.3.6.1-1 specifies entering actions Condition G for the other manual isolation instrumentation functions. | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | ||
Furthermore, to be consistent with a similar Note in STS 3.6.1.3, "Primary Containment Isolation," the traveler also added a Note to the STS 3.3.6.1 actions table that states, "Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls." In TS 3.3.6.1, the proposed change adds the following NOTE in the LCO ACTIONS: Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls. Additionally, Current TS 3.3.6.1, Completion Time for Required Action A.1 states: 12 hours for Functions 2.a, 2.b, and 6.b 24 hours for Functions other than Functions 2.a, 2.b, and 6.b Revised TS 3.3.6.1, Completion Time for Required Action A.1 would state: 12 hours for Functions 2.a, 2.b, 6.b, 7.a, and 7.b 24 hours for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b TS 3.3.6.1 is revised to add the following new Condition G. Additionally, as a result, existing LCO Conditions G, H, and I change to H, I, and J, respectively, and LCO Table 3.3.6.1-1 is revised accordingly. | Based on the above, the NRC staff concludes that the proposed changes to TS 1.4 are acceptable. | ||
G. As required by Required G.1 Isolate the affected 24 hours Action C.1 and referenced in penetration flow path(s). Table 3.3.6.1-1. | 3.10 TSTF-295-A, Revision 0, "Modify Note 2 to Actions of PAM [Post-Accident Monitoring] | ||
LCO Table 3.3.6.1-1 is revised to add the new functions 7a and 7b: [see next page] | Table to Allow Separate Condition Entrv for Each Penetration" The NRC approved this change to STS Revision 1 on December 21, 1999. TSTF-295-A revised Table 3.3.3.1-1 of STS 3.3.3.1, "Post Accident Monitoring (PAM) Instrumentation," by (1) prefacing the title of Function 8, "Primary Containment Isolation Valve (PCIV) Position," with the phrase "Penetration Flow Path," and (2) prefacing the title of Function 13, "Suppression Pool Water Temperature," with "Relief Valve Discharge Location." These changes were made to clarify how to apply the actions note to these two functions. The actions note states, "Separate Condition entry is allowed for each Function." The changes clarify that separate condition entry is allowed for each penetration flow path for the PAM PCIV position indication function and for each relief valve discharge location suppression pool temperature indication. | ||
The change proposed for corresponding HNP TS 3.3.3.1, Function 6, "Primary Containment Isolation Valve Position," is the same as the changes made to the STS by TSTF-295-A. The licensee did not propose a change to TS 3.3.3.1, Function 9, "Suppression Pool Water Temperature," because of its plant-specific system design as explained by the licensee in its application. | |||
: a. Reactor Vessel Water | Current TS Table 3.3.3.1-1, Function 6, states: | ||
Primary Containment Isolation Valve Position | |||
Revised TS Table 3.3.3.1-1, Function 6, would state: | |||
Penetration Flow Path Primary Containment Isolation Valve Position | |||
===NRC Staff Evaluation=== | |||
The NRC staff has determined that this change is administrative because it only clarifies the intended application of action requirements for inoperable channels of HNP TS 3.3.3.1 Function 6 and is consistent with the TS action requirements for PCIVs. This change does not reduce any existing action requirements for these PAM functions and does not affect plant safety. | |||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | |||
Based on the above, the NRC staff concludes the proposed change to TS Table 3.3.3.1-1 to be acceptable. | |||
3.11 TSTF-306-A. Revision 2, "Add Action to LCO 3.3.6.1 to give option to isolate the penetration" The NRC approved this change to STS Revision 1 on July 13, 2000. TSTF-306-A revised STS 3.3.6.1, "Primary Containment Isolation Instrumentation," by changing the requirements for the two Traversing In-core Probe (TIP) containment isolation instrumentation functions. | |||
Specifically, TSTF-306-A would add functions for TIP system isolation (7.a and 7.b) to STS Table 3.3.6.1-1. Previously, these functions had been included under Primary Containment Isolation Functions 2.a, "Reactor Vessel Water Level - Low Level 3," and 2.b, "Drywell Pressure | |||
- High," respectively. TSTF-306-A also revised the actions of STS 3.3.6.1 by listing the new function numbers in the two Completion Times for Required Action A.1. Because these TIP system isolation functions are manual functions, the traveler specified that actions Condition G must be entered immediately upon entering Condition C, "Required Action and associated Completion Time of Condition A or B not met." This action is appropriate because Table 3.3.6.1-1 specifies entering actions Condition G for the other manual isolation instrumentation functions. Furthermore, to be consistent with a similar Note in STS 3.6.1.3, "Primary Containment Isolation," the traveler also added a Note to the STS 3.3.6.1 actions table that states, "Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls." | |||
In TS 3.3.6.1, the proposed change adds the following NOTE in the LCO ACTIONS: | |||
Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls. | |||
Additionally, Current TS 3.3.6.1, Completion Time for Required Action A.1 states: | |||
12 hours for Functions 2.a, 2.b, and 6.b 24 hours for Functions other than Functions 2.a, 2.b, and 6.b Revised TS 3.3.6.1, Completion Time for Required Action A.1 would state: | |||
12 hours for Functions 2.a, 2.b, 6.b, 7.a, and 7.b 24 hours for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b TS 3.3.6.1 is revised to add the following new Condition G. Additionally, as a result, existing LCO Conditions G, H, and I change to H, I, and J, respectively, and LCO Table 3.3.6.1-1 is revised accordingly. | |||
G. As required by Required G.1 Isolate the affected 24 hours Action C.1 and referenced in penetration flow path(s). | |||
Table 3.3.6.1-1. | |||
LCO Table 3.3.6.1-1 is revised to add the new functions 7a and 7b: | |||
[see next page] | |||
APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE | |||
: 7. Traversing lncore Probe System Isolation | |||
: a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 ~ 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 | |||
: b. Drywell Pressure - 1,2,3 2 G SR 3.3.6.1.1 s 1.92 psig High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 NRC Staff Evaluation of the Proposed Changes to TS Requirements for PC IVs: | |||
The NRC staff has determined that this change does not reduce the level of safety currently afforded by the HNP TSs because the added allowance stated in the added Note is already permitted by TS 3.6.1.3 and is consistent with the intent of the HNP TS requirements for primary containment penetration flow paths with automatically actuated PC IVs. The addition of this allowance also increases the usability of HNP TSs by clarifying that flow paths isolated to comply with TS 3.3.6.1 action requirements (except for the 18-inch purge valve penetration flow paths) may also be unisolated intermittently under administrative controls .. | |||
Associated with this change is enumeration of the existing actions table note in TS 3.3.6.1 regarding separate condition entry for each primary containment isolation instrumentation channel, as Note 2. The NRC staff concludes that this administrative change conforms to the STS format convention for Notes and has no effect on plant safety. | |||
Based on the above, the NRC staff concludes that the changes regarding TS requirements for PCIVs are acceptable. | |||
NRC Staff Evaluation of Proposed Changes Regarding the TIP System Isolation: | NRC Staff Evaluation of Proposed Changes Regarding the TIP System Isolation: | ||
The revised LCO and action requirements for TIP system isolation allow TIP penetration flow path isolation rather than a unit shutdown in the event supporting automatic isolation instrumentation function channels are inoperable. | The revised LCO and action requirements for TIP system isolation allow TIP penetration flow path isolation rather than a unit shutdown in the event supporting automatic isolation instrumentation function channels are inoperable. This relaxation is appropriate because requiring a unit shutdown is overly restrictive for inoperable TIP system isolation instrumentation. The TIP system uses a small bore penetration (approximately 1/2 inch), and its isolation in a design-basis event is assumed to be accomplished by the manually operated shear valves. The ability to manually isolate the TIP system by either the normal automatic isolation valve (TIP system ball valves) or the shear valve(s) would be unaffected by inoperable instrumentation. Therefore, the option to isolate the penetration and to continue plant operation is provided. In order to implement this allowance, a separate isolation instrumentation function is being provided for the TIP system. The Completion Time provided to isolate the penetration is 24 hours, which is the Completion Time provided in the STS for penetration isolation when a manual containment isolation instrumentation function is inoperable. | ||
This relaxation is appropriate because requiring a unit shutdown is overly restrictive for inoperable TIP system isolation instrumentation. | |||
The TIP system uses a small bore penetration (approximately 1/2 inch), and its isolation in a design-basis event is assumed to be accomplished by the manually operated shear valves. The ability to manually isolate the TIP system by either the normal automatic isolation valve (TIP system ball valves) or the shear valve(s) would be unaffected by inoperable instrumentation. | |||
Therefore, the option to isolate the penetration and to continue plant operation is provided. | |||
In order to implement this allowance, a separate isolation instrumentation function is being provided for the TIP system. The Completion Time provided to isolate the penetration is 24 hours, which is the Completion Time provided in the STS for penetration isolation when a manual containment isolation instrumentation function is inoperable. | |||
These changes are consistent with the discussion of the TIP system ball and shear valves on HNP, Unit No. 1, FSAR pages 5.2-14 and 7.5-22, that TIP system isolation is accomplished by manual actuation of the ball valves, or by manual actuation of the shear valves in case a deployed TIP cannot be withdrawn. | These changes are consistent with the discussion of the TIP system ball and shear valves on HNP, Unit No. 1, FSAR pages 5.2-14 and 7.5-22, that TIP system isolation is accomplished by manual actuation of the ball valves, or by manual actuation of the shear valves in case a deployed TIP cannot be withdrawn. | ||
The NRC staff concludes that the small expected penetration leakage rate from a guide tube leak in the reactor pressure vessel allows adequate time for the operator to manually isolate the flow path with the shear valve. Also, the probability of an event requiring automatic isolation of a TIP system guide tube penetration flow path is low. Based on the small expected leakage rate and low probability of an event, the proposed 24-hour Completion Time of proposed new Required Action G.1 provides reasonable assurance of adequate protection of public health and safety. The other changes to TS 3.3.6.1 associated with the new action to isolate the TIP penetration flow path in 24 hours are administrative in nature because they only change the presentation of the existing LCO and action requirements for Functions 2.a and 2.b for the TIP ball valves and do not affect plant safety. The NRC staff concludes that the requirements of | The NRC staff concludes that the small expected penetration leakage rate from a guide tube leak in the reactor pressure vessel allows adequate time for the operator to manually isolate the flow path with the shear valve. Also, the probability of an event requiring automatic isolation of a TIP system guide tube penetration flow path is low. Based on the small expected leakage rate and low probability of an event, the proposed 24-hour Completion Time of proposed new Required Action G.1 provides reasonable assurance of adequate protection of public health and safety. | ||
Revision 1. "Determination of Cumulative and Projected Dose Contributions in RECP" The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-308-A modified NUREG-1433, STS 5.5.4, "Radioactive Effluent Controls Program," to describe the original intent of the dose projections. | The other changes to TS 3.3.6.1 associated with the new action to isolate the TIP penetration flow path in 24 hours are administrative in nature because they only change the presentation of the existing LCO and action requirements for Functions 2.a and 2.b for the TIP ball valves and do not affect plant safety. | ||
Current HNP TS 5.5.4, paragraph | The NRC staff concludes that the requirements of 1O CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | ||
Based on the above, the NRC staff concludes that the changes to TS 3.3.6.1 and Table 3.3.6.1-1 are acceptable. | |||
The regulation at | 3.12 TSTF-308-A. Revision 1. "Determination of Cumulative and Projected Dose Contributions in RECP" The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-308-A modified NUREG-1433, STS 5.5.4, "Radioactive Effluent Controls Program," to describe the original intent of the dose projections. | ||
Generic Letter (GL) 89-01, "Implementation of Programmatic Controls for Radiological Effluent Technical Specifications in the Administrative Controls Section of the Technical Specifications and the Relocation of Procedural Details of PETS to the Offsite Dose Calculation Manual or to the Process Control Program," dated January 31, 1989 (ADAMS Accession No. ML031140051), provides guidance in support of implementing programmatic controls in TSs for radioactive effluents and for radiological environmental monitoring that conforms to the applicable regulatory requirements. | Current HNP TS 5.5.4, paragraph e. states: | ||
The regulation at | Determination of cumulative and projected dose contributions from radioactive effluents for the current calendar quarter and current calendar year, in accordance with the methodology and parameters in the ODCM [offsite dose calculation manual], at least every 31 days. | ||
Therefore, TSTF-308-A was developed and subsequently approved by the NRC | The proposed change revises paragraph e. in its entirety as follows: | ||
The NRC staff reviewed the changes proposed by the licensee that were prepared using the guidance in TSTF-308-A. | Determination of cumulative dose contributions from radioactive effluents for the current calendar quarter and current calendar year in accordance with the methodology and parameters in the ODCM at least every 31 days. | ||
The NRC staff concludes that the revised wording for the HNP TSs clarifies the reporting requirements for projected doses, thus ensuring consistency with the requirements of 10 CFR 50.36a and 10 CFR 20.1302 and, therefore, is acceptable. | Determination of projected dose contributions from radioactive effluents in accordance with the methodology in the ODCM at least every 31 days. | ||
3.13 TSTF-318-A. | |||
Revision 0, "Revise 3.5.1 for one LPCI pump inoperable in each of two ECCS divisions" The proposed change adds a provision to Condition A of Specification 3.5.1, "ECCS -Operating," to allow one LPCI pump to be inoperable in each subsystem for a period of 7 days. Current TS 3.5.1, Condition A, states: One low pressure ECCS injection/spray subsystem inoperable. | ===NRC Staff Evaluation=== | ||
Revised TS 3.5.1, Condition A, would state: One low pressure ECCS injection/spray subsystem inoperable. | The regulation at 1O CFR 50.36a(a)(2), "Technical specifications on effluents from nuclear power reactors," requires each licensee to submit a report to the NRC that will allow an estimation of the maximum potential annual radiation doses to the public resulting from effluent releases. Generic Letter (GL) 89-01, "Implementation of Programmatic Controls for Radiological Effluent Technical Specifications in the Administrative Controls Section of the Technical Specifications and the Relocation of Procedural Details of PETS to the Offsite Dose Calculation Manual or to the Process Control Program," dated January 31, 1989 (ADAMS Accession No. ML031140051), provides guidance in support of implementing programmatic controls in TSs for radioactive effluents and for radiological environmental monitoring that conforms to the applicable regulatory requirements. The regulation at 1O CFR 20.1302, "Compliance with dose limits for individual members of the public," paragraph (b), requires that a licensee show compliance with the annual dose limit in 10 CFR 20.1301, "Dose limits for individual members of the public," demonstrating by measurement or calculation that the total effective dose equivalent to the individual likely to receive the highest dose from the licensed operation does not exceed the annual dose limit. | ||
GL 89-01 combined two SRs, the cumulative and projected dose determinations, into one program element. In combining these requirements, the new program element can be interpreted to require determining projected dose contributions for the calendar quarter and current calendar year every 31 days. This wording was misleading and resulted in misinterpretation of the intent of the original STS and was not consistent with the original surveillance. Therefore, TSTF-308-A was developed and subsequently approved by the NRC | |||
to not require dose projections for a calendar quarter and a calendar year every 31 days (i.e., to describe the actual intent of the dose projections). | |||
The NRC staff reviewed the changes proposed by the licensee that were prepared using the guidance in TSTF-308-A. The NRC staff concludes that the revised wording for the HNP TSs clarifies the reporting requirements for projected doses, thus ensuring consistency with the requirements of 10 CFR 50.36a and 10 CFR 20.1302 and, therefore, is acceptable. | |||
3.13 TSTF-318-A. Revision 0, "Revise 3.5.1 for one LPCI pump inoperable in each of two ECCS divisions" The proposed change adds a provision to Condition A of Specification 3.5.1, "ECCS - | |||
Operating," to allow one LPCI pump to be inoperable in each subsystem for a period of 7 days. | |||
Current TS 3.5.1, Condition A, states: | |||
One low pressure ECCS injection/spray subsystem inoperable. | |||
Revised TS 3.5.1, Condition A, would state: | |||
One low pressure ECCS injection/spray subsystem inoperable. | |||
One LPCI pump in both LPCI subsystems inoperable. | One LPCI pump in both LPCI subsystems inoperable. | ||
Current TS 3.5.1, Required Action A.1 for Condition A, states: Restore low pressure ECCS injection/spray subsystem to OPERABLE status. Revised TS 3.5.1, Required Action A.1 for Condition A, would state: Restore low pressure ECCS injection/spray subsystem(s) to OPERABLE status. Current TS 3.5.1, Condition D, states: HPCI System inoperable. | Current TS 3.5.1, Required Action A.1 for Condition A, states: | ||
Restore low pressure ECCS injection/spray subsystem to OPERABLE status. | |||
Revised TS 3.5.1, Required Action A.1 for Condition A, would state: | |||
Restore low pressure ECCS injection/spray subsystem(s) to OPERABLE status. | |||
Current TS 3.5.1, Condition D, states: | |||
HPCI System inoperable. | |||
One low pressure ECCS injection/spray subsystem inoperable. | One low pressure ECCS injection/spray subsystem inoperable. | ||
Revised TS 3.5.1, Condition D, would state: HPCI System inoperable. Condition A entered. Current TS 3.5.1, Condition F, states, in part: Two or more low pressure ECCS injection/spray subsystems inoperable. | Revised TS 3.5.1, Condition D, would state: | ||
Revised TS 3.5.1, Condition F, would state, in part: Two or more low pressure ECCS injection/spray subsystems inoperable for reasons other than Condition A. NRC Staff Evaluation | HPCI System inoperable. | ||
The NRC staff documented its approval of TSTF-318-A, Revision 0, in a letter from William Beckner, NRC to James Davis, NEI dated June 29, 1999 (ADAMS Accession No. ML16237A030). The NRC staff reviewed the proposed changes and determined that TSTF-318 is applicable to HNP and is consistent with NUREG-1433. | |||
The NRC staff has determined that the proposed change allows the TSs to recognize an additional LPCI configuration that continues to ensure the design-basis analysis is met and is bounded by the currently allowed configuration. | Condition A entered. | ||
The NRC staff also determined that the proposed change is an improvement of the current TS requirements, which would require entry into LCO 3.0.3 and a plant shutdown in the event of one inoperable pump in each LPCI subsystem. | Current TS 3.5.1, Condition F, states, in part: | ||
Since the LPCI pumps also serve as RHR pumps, the proposed amendment would preclude the licensee having to put the plant in the RHR shutdown cooling configuration at a time when RHR capability is degraded. | Two or more low pressure ECCS injection/spray subsystems inoperable. | ||
Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO. and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the proposed changes to TS 3.5.1 are acceptable. | Revised TS 3.5.1, Condition F, would state, in part: | ||
3.14 TSTF-322-A. | Two or more low pressure ECCS injection/spray subsystems inoperable for reasons other than Condition A. | ||
Revision 2. "Secondary Containment and Shield Building Boundary Integrity SRs" TSTF-322-A, Revision 2, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). | |||
TSTF-322-A modified the secondary containment boundary integrity and shield building boundary integrity SRs to clarify their intent. Current TS SR 3.6.4.1.3 states: Verify required SGT subsystem(s) will draw down the secondary containment to 0.20 inch of vacuum water gauge in s 120 seconds. Revised TS SR 3.6.4.1.3 would state: Verify secondary containment can be drawn down to :::: 0.20 inch of vacuum water gauge in s 120 seconds using required standby gas treatment (SGT) subsystem(s). | ===NRC Staff Evaluation=== | ||
Current TS SR 3.6.4.1.4 states: Verify required SGT subsystem(s) can maintain :::: 0.20 inch of vacuum water gauge in the secondary containment for 1 hour at a flow rate s 4000 cfm [cubic feet per minute] for each subsystem. | The NRC staff documented its approval of TSTF-318-A, Revision 0, in a letter from William Beckner, NRC to James Davis, NEI dated June 29, 1999 (ADAMS Accession No. ML16237A030). The NRC staff reviewed the proposed changes and determined that TSTF-318 is applicable to HNP and is consistent with NUREG-1433. The NRC staff has determined that the proposed change allows the TSs to recognize an additional LPCI configuration that continues to ensure the design-basis analysis is met and is bounded by the currently allowed configuration. The NRC staff also determined that the proposed change is an improvement of the current TS requirements, which would require entry into LCO 3.0.3 and a plant shutdown in the event of one inoperable pump in each LPCI subsystem. Since the LPCI pumps also serve as RHR pumps, the proposed amendment would preclude the licensee having to put the plant in the RHR shutdown cooling configuration at a time when RHR capability is degraded. | ||
Revised TS SR 3.6.4.1.4 would state: Verify the secondary containment can be maintained | Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO. and the appropriate remedial measures are specified if the LCO is not met. | ||
:::: 0.20 inch of vacuum water gauge for 1 hour using required SGT subsystem(s) at a flow rate s 4000 cfm per subsystem. | Based on the above, the NRC staff concludes that the proposed changes to TS 3.5.1 are acceptable. | ||
NRC Staff Evaluation | 3.14 TSTF-322-A. Revision 2. "Secondary Containment and Shield Building Boundary Integrity SRs" TSTF-322-A, Revision 2, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). TSTF-322-A modified the secondary containment boundary integrity and shield building boundary integrity SRs to clarify their intent. | ||
Current TS SR 3.6.4.1.3 states: | |||
Verify required SGT subsystem(s) will draw down the secondary containment to | |||
~ 0.20 inch of vacuum water gauge in s 120 seconds. | |||
Revised TS SR 3.6.4.1.3 would state: | |||
Verify secondary containment can be drawn down to :::: 0.20 inch of vacuum water gauge in s 120 seconds using required standby gas treatment (SGT) subsystem(s). | |||
Current TS SR 3.6.4.1.4 states: | |||
Verify required SGT subsystem(s) can maintain :::: 0.20 inch of vacuum water gauge in the secondary containment for 1 hour at a flow rate s 4000 cfm [cubic feet per minute] for each subsystem. | |||
Revised TS SR 3.6.4.1.4 would state: | |||
Verify the secondary containment can be maintained :::: 0.20 inch of vacuum water gauge for 1 hour using required SGT subsystem(s) at a flow rate s 4000 cfm per subsystem. | |||
===NRC Staff Evaluation=== | |||
The changes to the secondary containment SRs in HNP TS 3.6.4.1 conform to the intent of the changes made to the STS by TSTF-322-A, with the exception of the surveillance frequency. | The changes to the secondary containment SRs in HNP TS 3.6.4.1 conform to the intent of the changes made to the STS by TSTF-322-A, with the exception of the surveillance frequency. | ||
The surveillance frequency is controlled by the SFCP, which is a program developed subsequent to the approval of TSTF-322-A. | The surveillance frequency is controlled by the SFCP, which is a program developed subsequent to the approval of TSTF-322-A. The NRC staff reviewed the TS changes and has determined that they clarify the intent of the drawdown tests for demonstrating operability of the secondary containment. If an SGT subsystem is inoperable, TS 3.6.4.3 specifies appropriate action requirements; it does not imply that the secondary containment is inoperable. The proposed changes only clarify the intended meaning of the existing SRs; therefore, they are administrative in nature and have no safety impact. | ||
The NRC staff reviewed the TS changes and has determined that they clarify the intent of the drawdown tests for demonstrating operability of the secondary containment. | Additionally, the NRC staff has determined that that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SRs provide the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | ||
If an SGT subsystem is inoperable, TS 3.6.4.3 specifies appropriate action requirements; it does not imply that the secondary containment is inoperable. | Based on the above, the NRC staff concludes that the changes to SR 3.5.4.1.3 and SR 3.6.4.1.4 are acceptable. | ||
The proposed changes only clarify the intended meaning of the existing SRs; therefore, they are administrative in nature and have no safety impact. Additionally, the NRC staff has determined that that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SRs provide the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes that the changes to SR 3.5.4.1.3 and SR 3.6.4.1.4 are acceptable. | 3.15 TSTF-323-A. Revision 0. "EFCV [Excess Flow Check Valve] Completion Time to 72 hours" As stated in Section 3.1 of this safety evaluation, the TSTF-323-A change preceded the approval of, and was subsumed in, the final version (Revision 3) of TSTF-30. Therefore, Section 3.1 of this safety evaluation discusses the licensee's proposed adoption of both TSTF-30 and TSTF-323-A changes and provides the NRC staff's assessment. | ||
3.15 TSTF-323-A. | |||
Revision 0. "EFCV [Excess Flow Check Valve] Completion Time to 72 hours" As stated in Section 3.1 of this safety evaluation, the TSTF-323-A change preceded the approval of, and was subsumed in, the final version (Revision | 3.16 TSTF-37 4-A, Revision 0, "Revision to TS 5.5.13 and associated TS Bases for Diesel Fuel Oil" The NRC staff documented its approval of TSTF-374-A, Revision 0, in a letter from Thomas H. | ||
Boyce, NRC, to the TSTF dated January 13, 2005 (ADAMS Accession No. ML050130309), and the NRC approved this change to STS Revision 2 on April 14, 2006. TSTF-374-A revises STS 5.5.9, "Diesel Fuel Oil Testing Program," diesel fuel oil testing program (DFOTP) to remove references to the specific American Society for Testing and Materials (ASTM) standard from the administrative controls section of TSs and alternatively places them in a licensee-controlled document. Specific criteria are added to establish the acceptability of new fuel oil for use prior to, and following, the addition to storage tanks. The DFOTP of HNP, Unit Nos. 1 and 2, is located at TS 5.5.9, while the STS DFOTP is located at TS 5.5.1 O; however, this difference in numbering is immaterial to the proposed change. | |||
Specific criteria are added to establish the acceptability of new fuel oil for use prior to, and following, the addition to storage tanks. The DFOTP of HNP, Unit Nos. 1 and 2, is located at TS 5.5.9, while the STS DFOTP is located at TS 5.5.1 O; however, this difference in numbering is immaterial to the proposed change. Current TS 5.5.9 states: A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. | Current TS 5.5.9 states: | ||
The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. | A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following: | ||
The purpose of the program is to establish the following: | : a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil; and | ||
: a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil; and b. Total particulate concentration of the fuel oil is 10 mg [milligram]/liter when tested every 92 days utilizing the guidance provided in ASTM D-2276, Method A-2 or A-3. The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies. | : b. Total particulate concentration of the fuel oil is ~ 10 mg [milligram]/liter when tested every 92 days utilizing the guidance provided in ASTM D-2276, Method A-2 or A-3. | ||
Revised TS 5.5.9 would state: A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies. | ||
The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. | Revised TS 5.5.9 would state: | ||
The purpose of the program is to establish the following: | A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following: | ||
: a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: 1. An API [American Petroleum Institute] | : a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has: | ||
gravity or an absolute specific gravity within limits, 2. A flash point and kinematic viscosity within limits for ASTM 2D fuel oil, and | : 1. An API [American Petroleum Institute] gravity or an absolute specific gravity within limits, | ||
NRC Staff Evaluation | : 2. A flash point and kinematic viscosity within limits for ASTM 2D fuel oil, and | ||
The NRC staff has reviewed the changes to the DFOTP in TS 5.5.9. For HNP, the result is a specification closer to the STS than the previous specification. | : 3. A water and sediment content within limits; | ||
The former requirements, which were subject to interpretation, " ... fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil," are replaced by more objective tests for American Petroleum Institute gravity or specific gravity, flash point and kinematic viscosity, and sediment and water content. A specific time limit of 31 days is added for new fuel to storage tanks, and particulate content testing requirements are retained. | : b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 2D fuel oil; and | ||
Additionally, because of significant differences between this licensee's TS bases and the STS bases, this licensee will control the removed ASTM requirements in a license-controlled procedure. | : c. Total particulate concentration of the fuel oil is s 10 mg/liter when tested every 92 days. | ||
The licensee states that future changes are also subject to a 10 CFR 50.59 review as they would be in the TS Bases. The NRC staff has determined that the proposed changes to TS 5.5.9 conform to the intent of TSTF-37 4-A. Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(5) continue to be met because the revised TSs provide the appropriate administrative controls to ensure the necessary quality of the fuel oil is maintained. | The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies. | ||
===NRC Staff Evaluation=== | |||
The NRC staff has reviewed the changes to the DFOTP in TS 5.5.9. For HNP, the result is a specification closer to the STS than the previous specification. The former requirements, which were subject to interpretation, " ... fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil," are replaced by more objective tests for American Petroleum Institute gravity or specific gravity, flash point and kinematic viscosity, and sediment and water content. A specific time limit of 31 days is added for new fuel to storage tanks, and particulate content testing requirements are retained. Additionally, because of significant differences between this licensee's TS bases and the STS bases, this licensee will control the removed ASTM requirements in a license-controlled procedure. The licensee states that future changes are also subject to a 10 CFR 50.59 review as they would be in the TS Bases. The NRC staff has determined that the proposed changes to TS 5.5.9 conform to the intent of TSTF-37 4-A. | |||
Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(5) continue to be met because the revised TSs provide the appropriate administrative controls to ensure the necessary quality of the fuel oil is maintained. | |||
Based on the above, the NRC staff concludes that the proposed changes to TS 5.5.9 are acceptable. | Based on the above, the NRC staff concludes that the proposed changes to TS 5.5.9 are acceptable. | ||
3.17 TSTF-400-A, Revision 1. "Clarify SR on Bypass of DG [Diesel Generator) | 3.17 TSTF-400-A, Revision 1. "Clarify SR on Bypass of DG [Diesel Generator) Automatic Trips" The NRCs approval of TSTF-400-A, Revision 1, is documented by letter to the TSTF dated November 13, 2004 (ADAMS Accession No. ML043200067). The proposed change revises TS 3.8.1, "AC Sources - Operating," Surveillance 3.8.1.11, to clarify that the intent of the SR is to test the non-critical emergency DG automatic trips. The numbering of SRs in the HNP TSs is different from the STS numbering. STS SR 3.8.1.13 corresponds to SR 3.8.1.11 in the HNP TSs. This has no effect on the requested change. | ||
Automatic Trips" The NRCs approval of TSTF-400-A, Revision 1, is documented by letter to the TSTF dated November 13, 2004 (ADAMS Accession No. ML043200067). | |||
The proposed change revises TS 3.8.1, "AC Sources -Operating," Surveillance 3.8.1.11, to clarify that the intent of the SR is to test the non-critical emergency DG automatic trips. The numbering of SRs in the HNP TSs is different from the STS numbering. | Current TS SR 3.8.1.11 states, in part that: | ||
STS SR 3.8.1.13 corresponds to SR 3.8.1.11 in the HNP TSs. This has no effect on the requested change. Current TS SR 3.8.1.11 states, in part that: Verify each DG's automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal except: a. Engine overspeed; | Verify each DG's automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal except: | ||
: b. Generator differential current; and c. Low lube oil pressure. | : a. Engine overspeed; | ||
Revised TS SR 3.8.1.11 would state: Verify each DG's non-critical automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal. NRC Staff Evaluation | : b. Generator differential current; and | ||
The changes to SR 3.8.1.11 and the associated TS bases state that the SR only verifies that non-critical DG trips are bypassed. | : c. Low lube oil pressure. | ||
The non-critical DG trips are bypassed during design-basis accidents and provide an alarm on an abnormal engine condition. | Revised TS SR 3.8.1.11 would state: | ||
The NRC staff reviewed this change and has determined that it provides clarification, and no STS requirements are materially altered. Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. Based on the above, the NRC staff concludes that the changes to SR 3.8.1.11 are acceptable. | Verify each DG's non-critical automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal. | ||
3.18 TSTF-439-A. | |||
Revision 2. "Eliminate Second Completion Times Limiting Time From Discovery of Failure To Meet an LCO" The NRC approved TSTF-439-A, Revision 2, in a letter dated January 11, 2006 (ADAMS Accession No. ML060120272). | ===NRC Staff Evaluation=== | ||
TSTF-439-A revised the STS by eliminating the second Completion Times limiting time from discovery of failure to meet an LCO from the affected Required Actions and modifies the example in TS 1.3. These Completion Times (henceforth referred to as "second Completion Times") are joined by an "AND" logical connector to the condition-specific Completion Time and state, "X days from discovery of failure to meet the LCO" (where "X" varies by specification). | The changes to SR 3.8.1.11 and the associated TS bases state that the SR only verifies that non-critical DG trips are bypassed. The non-critical DG trips are bypassed during design-basis accidents and provide an alarm on an abnormal engine condition. The NRC staff reviewed this change and has determined that it provides clarification, and no STS requirements are materially altered. | ||
HNP TSs 3.1. 7, "Standby Liquid Control (SLC) System"; 3.6.4.3, "Standby Gas Treatment (SGT) System"; 3.8.1, "AC Sources -Operating"; | Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met. | ||
and 3.8.7, "Distribution Systems -Operating," contain Required Actions with a second Completion Time to establish a limit on the maximum time allowed for any combination of conditions that result in a single continuous failure to meet | Based on the above, the NRC staff concludes that the changes to SR 3.8.1.11 are acceptable. | ||
* Current TS 3.1.7, Completion Time for Required Action A.1, states: 72 hours 10 days from discovery of failure to meet the LCO Revised TS 3.1.7, Completion Time for Required Action A.1, would state: 72 hours | 3.18 TSTF-439-A. Revision 2. "Eliminate Second Completion Times Limiting Time From Discovery of Failure To Meet an LCO" The NRC approved TSTF-439-A, Revision 2, in a letter dated January 11, 2006 (ADAMS Accession No. ML060120272). TSTF-439-A revised the STS by eliminating the second Completion Times limiting time from discovery of failure to meet an LCO from the affected Required Actions and modifies the example in TS 1.3. These Completion Times (henceforth referred to as "second Completion Times") are joined by an "AND" logical connector to the condition-specific Completion Time and state, "X days from discovery of failure to meet the LCO" (where "X" varies by specification). | ||
* Current TS 3.6.4.3, Completion Time for Required Action 8.1, states: 7 days 30 days from discovery of failure to meet the LCO Revised TS 3.6.4.3, Completion Time for Required Action 8.1, would state: 7 days | HNP TSs 3.1. 7, "Standby Liquid Control (SLC) System"; 3.6.4.3, "Standby Gas Treatment (SGT) System"; 3.8.1, "AC Sources - Operating"; and 3.8.7, "Distribution Systems - Operating," | ||
* Current TS 3.8.1, Completion Time for Required Action A.3, states: 72 hours 17 days from discovery of failure to meet LCO 3.8.1.a, b, or c Revised TS 3.8.1, Completion Time for Required Action A.3, would state: 72 hours | contain Required Actions with a second Completion Time to establish a limit on the maximum time allowed for any combination of conditions that result in a single continuous failure to meet | ||
* Current TS 3.8.1, Completion Time for Required Action 8.4, states: 72 hours for a Unit 1 DG with the swing DG not inhibited or maintenance restrictions not met | |||
* Current TS 3.8.7, Completion Time for Required Action B.1, states: 12 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action B.1, would state: 12 hours | the LCO. The proposed change deletes these second Completion Times from the affected Required Actions. | ||
* Current TS 3.8.7, Completion Time for Required Action C.1, states: 8 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action C.1, would state: 8 hours | * Current TS 3.1.7, Completion Time for Required Action A.1, states: | ||
* Current TS 3.8.7, Completion Time for Required Action D.1, states: 2 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8. 7, Completion Time for Required Action D.1, would state: 2 hours The proposed change also revises TS Section 1.3, Example 1.3-3 (as shown below), to remove the discussion of second Completion Times and to revise the discussion in that example to state that alternating between conditions in such a manner that operation could continue indefinitely, without restoring systems to meet the LCO, is inconsistent with the basis of the Completion Times and is inappropriate. | 72 hours 10 days from discovery of failure to meet the LCO Revised TS 3.1.7, Completion Time for Required Action A.1, would state: | ||
72 hours | |||
* Current TS 3.6.4.3, Completion Time for Required Action 8.1, states: | |||
7 days 30 days from discovery of failure to meet the LCO Revised TS 3.6.4.3, Completion Time for Required Action 8.1, would state: | |||
7 days | |||
* Current TS 3.8.1, Completion Time for Required Action A.3, states: | |||
72 hours 17 days from discovery of failure to meet LCO 3.8.1.a, b, or c Revised TS 3.8.1, Completion Time for Required Action A.3, would state: | |||
72 hours | |||
* Current TS 3.8.1, Completion Time for Required Action 8.4, states: | |||
72 hours for a Unit 1 DG with the swing DG not inhibited or maintenance restrictions not met | |||
14 days for a Unit 1 DG with the swing DG inhibited from automatically aligning to Unit 2 and maintenance restrictions met 72 hours for the swing diesel with maintenance restrictions not met 14 days for the swing diesel with maintenance restrictions met 17 days from discovery of failure to meet LCO 3.8.1.a, b, or c Revised TS 3.8.1, Completion Time for Required Action B.4, would state: | |||
72 hours for a Unit 1 DG with the swing DG not inhibited or maintenance restrictions not met 14 days for a Unit 1 DG with the swing DG inhibited from automatically aligning to Unit 2 and maintenance restrictions met 72 hours for the swing diesel with maintenance restrictions not met 14 days for the swing diesel with maintenance restrictions met | |||
* Current TS 3.8.7, Completion Time for Required Action B.1, states: | |||
12 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action B.1, would state: | |||
12 hours | |||
* Current TS 3.8.7, Completion Time for Required Action C.1, states: | |||
8 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action C.1, would state: | |||
8 hours | |||
* Current TS 3.8.7, Completion Time for Required Action D.1, states: | |||
2 hours 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8. 7, Completion Time for Required Action D.1, would state: | |||
2 hours The proposed change also revises TS Section 1.3, Example 1.3-3 (as shown below), to remove the discussion of second Completion Times and to revise the discussion in that example to state that alternating between conditions in such a manner that operation could continue indefinitely, without restoring systems to meet the LCO, is inconsistent with the basis of the Completion Times and is inappropriate. | |||
The proposed changes to TS 1.3, "Completion Times," are as follows: | The proposed changes to TS 1.3, "Completion Times," are as follows: | ||
* The last paragraph on TS page 1.3-2 currently states, in part, that: Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended. | * The last paragraph on TS page 1.3-2 currently states, in part, that: | ||
Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended. | |||
The proposed change deletes the above statement. | The proposed change deletes the above statement. | ||
* Example 1.3-3 currently reflects for Conditions A and B, a first Completion Time of 7 days and 72 hours, respectively, and a second Completion Time as "AND 10 days from discovery of failure to meet the LCO," for both conditions. | * Example 1.3-3 currently reflects for Conditions A and B, a first Completion Time of 7 days and 72 hours, respectively, and a second Completion Time as "AND 10 days from discovery of failure to meet the LCO," for both conditions. Condition C in the example does not contain a second Completion Time. | ||
Condition C in the example does not contain a second Completion Time. The proposed change revises Example 1.3-3 to eliminate the second Completion Times, "10 days from discovery of failure to meet the LCO," from Conditions A and B. | The proposed change revises Example 1.3-3 to eliminate the second Completion Times, "10 days from discovery of failure to meet the LCO," from Conditions A and B. | ||
* TS Section 1.3, the last paragraph currently describes second Completion Time as follows: The Completion Times of Conditions A and B are modified by a logical connector, with a separate | * TS Section 1.3, the last paragraph currently describes second Completion Time as follows: | ||
The Completion Times of Conditions A and B are modified by a logical connector, with a separate 1O day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO. This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered. | |||
The proposed change replaces the above paragraph with the following: | |||
It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. | It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended. | ||
As stated in Section 4.0, "Commitments," of the application, SNC specifies the following commitment regarding its proposed change: SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." The licensee also stated that the procedure will be revised prior to implementation of the proposed TS change. NRC Staff Evaluation | As stated in Section 4.0, "Commitments," of the application, SNC specifies the following commitment regarding its proposed change: | ||
The Maintenance Rule (10 CFR 50.65(a)(1 | SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." | ||
)), requires licensees to monitor the performance or conditions of structures, systems, and components (SSCs) in a manner sufficient to provide reasonable assurance that SSCs are capable of fulfilling their intended functions. | The licensee also stated that the procedure will be revised prior to implementation of the proposed TS change. | ||
If the performance or condition of an SSC does not meet established goals, appropriate corrective action is required to be taken. The NRC resident inspectors monitor the licensee's corrective action program and can take action if the licensee's maintenance program allows the systems | |||
A goal of the TSs is to provide adequate assurance of the availability and reliability of equipment needed to prevent, and if necessary, mitigate, accidents and transients. | ===NRC Staff Evaluation=== | ||
The Maintenance Rule shares this goal and operates through a dynamic and comprehensive process. The objective of the cornerstone is to monitor the availability, reliability, and capability of systems that mitigate the effects of initiating events to prevent core damage. Licensees also reduce the likelihood of reactor accidents by maintaining the availability and reliability of mitigating systems. Mitigating systems include those systems associated with safety injection, decay heat removal, and their support systems, such as emergency AC power systems (which encompasses the AC sources distribution system LCOs, as noted by the licensee), and the auxiliary feedwater system. Inputs to the mitigating systems cornerstone include both inspection procedures and performance indicators to ensure that all reactor oversight process objectives are being met. Satisfactory licensee performance within the mitigation systems reactor oversight process cornerstone provides reasonable assurance in monitoring the inappropriate use of TS condition Completion Times. The NRC approved this change to the STS on January 11, 2006. TSTF-439-A revised Example 1.3-3 of the TSs to state, in part, "There shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended." SNC provided a regulatory commitment to revise Operations Procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." The licensee will revise the procedure prior to implementation of the proposed change. The NRC staff concludes that the proposed changes establish a new TS convention to appropriately limit the time allowed for the plant to operate in any combination of LCO conditions that could result in a single continuous failure to meet the LCO. The new convention meets the intent of the Completion Times. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) remain unaffected by the proposed changes and would continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. Based on the above, the NRC staff concludes that the changes to TSs 1.3, 3.1.7, 3.6.4.3, 3.8.1, and 3.8.7, are acceptable. 3.19 TSTF-458-T. | The Maintenance Rule (10 CFR 50.65(a)(1 )), requires licensees to monitor the performance or conditions of structures, systems, and components (SSCs) in a manner sufficient to provide reasonable assurance that SSCs are capable of fulfilling their intended functions. If the performance or condition of an SSC does not meet established goals, appropriate corrective action is required to be taken. The NRC resident inspectors monitor the licensee's corrective action program and can take action if the licensee's maintenance program allows the systems | ||
Revision 0. "Removing Restart of Shutdown Clock for Increasing Suppression Pool Temperature" TSTF-458-T, Revision 0, revises BWR STS 3.6.2.1, "Suppression Pool Average Temperature," to remove a potential ambiguity between Actions D and E that would allow resetting of the shutdown Completion Time clock. Current TS 3.6.2.1, Condition D, states: Suppression pool average temperature | |||
> 110°F but s 120°F. Revised TS 3.6.2.1, Condition D, would state: Suppression pool average temperature | required by a single LCO to become concurrently inoperable multiple times. The performance and condition monitoring activities required by 10 CFR 50.65 (a)(1) and (a)(2) would identify if poor maintenance practices resulted in multiple entries into the actions of the TSs and unacceptable unavailability of these SSCs. The effectiveness of these performance monitoring activities, and associated corrective actions, is evaluated at least every refueling cycle, not to exceed 24 months, per 10 CFR 50.65 (a)(3). | ||
> 110°F. Current TS 3.6.2.1, Required Action D.2, states: Verify suppression pool average temperature s 120°F. Revised TS 3.6.2.1, Required Action D.2, would state: Determine suppression pool average temperature. | Prior to 10 CFR 50.65, TSs were the primary rules governing operations, including what equipment must normally be in service, how long equipment can be out of service, compensatory actions, and surveillance testing to demonstrate equipment readiness. A goal of the TSs is to provide adequate assurance of the availability and reliability of equipment needed to prevent, and if necessary, mitigate, accidents and transients. The Maintenance Rule shares this goal and operates through a dynamic and comprehensive process. | ||
Current TS 3.6.2.1, Required Actions E.1 and E.2, states: E.1 Depressurize the reactor vessel to < 200 psig. AND E.2 Be in MODE 4. With Required Action E.2 having a Completion Time of: 36 hours Revised TS 3.6.2.1 would state: Required Action E.2 and its associated Completion Time of 36 hours are deleted, resulting in Required Action E.1 remaining: | The objective of the cornerstone is to monitor the availability, reliability, and capability of systems that mitigate the effects of initiating events to prevent core damage. Licensees also reduce the likelihood of reactor accidents by maintaining the availability and reliability of mitigating systems. Mitigating systems include those systems associated with safety injection, decay heat removal, and their support systems, such as emergency AC power systems (which encompasses the AC sources distribution system LCOs, as noted by the licensee), and the auxiliary feedwater system. Inputs to the mitigating systems cornerstone include both inspection procedures and performance indicators to ensure that all reactor oversight process objectives are being met. Satisfactory licensee performance within the mitigation systems reactor oversight process cornerstone provides reasonable assurance in monitoring the inappropriate use of TS condition Completion Times. | ||
E.1 Depressurize the reactor vessel to < 200 psig. NRC Staff Evaluation | The NRC approved this change to the STS on January 11, 2006. TSTF-439-A revised Example 1.3-3 of the TSs to state, in part, "There shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended." SNC provided a regulatory commitment to revise Operations Procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." The licensee will revise the procedure prior to implementation of the proposed change. | ||
AT-traveler, such as TSTF-458-T, Revision 0, is prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those | The NRC staff concludes that the proposed changes establish a new TS convention to appropriately limit the time allowed for the plant to operate in any combination of LCO conditions that could result in a single continuous failure to meet the LCO. The new convention meets the intent of the Completion Times. | ||
The NRC does not review nor approve T-travelers, and the proposed changes under T-travelers are not incorporated in the respective STS. The NRC staff reviewed these changes and determined that they ( 1) clarify the scope of Condition D and the intent of specified actions in Condition D, and (2) remove a redundant action in Condition E to eliminate an ambiguity between specified actions for existing Conditions D and E. Thus, these changes are of administrative nature and do not affect the technical content of specified TS requirements. | Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) remain unaffected by the proposed changes and would continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met. | ||
Specifically, this eliminates having two Required Actions and Completion Times, both directing entry into MODE 4 with staggered Completion Times. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the revised LCO conditions provide appropriate requirements to ensure that the LCO will be met. Based on the above, the NRC staff concludes that the changes to TS 3.6.2.1 are acceptable. | Based on the above, the NRC staff concludes that the changes to TSs 1.3, 3.1.7, 3.6.4.3, 3.8.1, and 3.8.7, are acceptable. | ||
3.20 TSTF-464-T. | |||
Revision 0, "Clarify the Control Rod Block Instrumentation Required Action" The proposed change clarifies the wording of Required Action C.2.1.2 of HNP TS 3.3.2.1, "Control Rod Block Instrumentation," to align with the TS Bases, Section 3.3.2.1. Current Hatch TS, and Proposed Changes: Current TS 3.3.2.1, Required Action C.2.1.2, states: Verify by administrative methods that startup with RWM [rod worth minimizer] | 3.19 TSTF-458-T. Revision 0. "Removing Restart of Shutdown Clock for Increasing Suppression Pool Temperature" TSTF-458-T, Revision 0, revises BWR STS 3.6.2.1, "Suppression Pool Average Temperature," | ||
inoperable has not been performed in the last calendar year. Revised TS 3.3.2.1, Required Action C.2.1.2, would state: Verify by administrative methods that startup with RWM inoperable has not been performed in the last 12 months. NRC Staff Evaluation | to remove a potential ambiguity between Actions D and E that would allow resetting of the shutdown Completion Time clock. | ||
AT-traveler, such as TSTF-464-T, Revision 0, was prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those requirements. | Current TS 3.6.2.1, Condition D, states: | ||
The NRC did not review nor approve T-travelers, and the proposed changes under T-travelers were not incorporated in the respective STS. The NRC staff reviewed the proposed change and determined that the current ambiguity of the phrase "last calendar year" does not provide assurance that the appropriate remedial measures are performed if the LCO is not met. Replacing the phrase "last calendar year" with the proposed phrase "last 12 months" provides additional clarity and assurance that appropriate remedial measures are performed if the LCO is not met. Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2)will be met with the proposed change because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO. Based on the above, the NRC staff concludes that the change to TS 3.3.2.1 is acceptable. | Suppression pool average temperature > 110°F but s 120°F. | ||
3.21 STS Adoption #1 -Revise the 5.5.7 Introductory Paragraph to be Consistent with the ISTS The licensee proposed to adopt the formatting and language in the STS, NUREG-1433, STS for General Electric BWR/4 Plants, Revision 4. Current TS 5.5. 7, "Ventilation Filter Testing Program (VFTP)," the introductory paragraph states: The VFTP will establish the required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, or: 1) after any structural maintenance on the HEPA filter or charcoal adsorber housings, 2) following painting, fire or chemical release in any ventilation zone communicating with the system, or 3) after every 720 hours of charcoal adsorber operation. | Revised TS 3.6.2.1, Condition D, would state: | ||
TS 5.5.7 is revised to state: A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2. NRC Staff Evaluation | Suppression pool average temperature > 110°F. | ||
The changes proposed for HNP TS 5.5.7 are similar to the wording in STS 5.5.8. This change removes detail from TS 5.5.7 and makes reference to RG 1.52, "Design, Testing, and Maintenance Criteria for Post-Accident Engineered-Safety-Feature Atmosphere Cleanup System Air Filtration and Adsorption Units of Light-Water-Cooled Nuclear Power Plants." The list of requirements for the program that the licensee proposed to remove are covered in Section C.6.b of RG 1.52 and TS SR 3.0.1. The NRC staff reviewed the proposed changes and determined that incorporating the requirement by reference for the VFTP is acceptable because detail can be removed from the TSs while maintaining the testing requirement. | Current TS 3.6.2.1, Required Action D.2, states: | ||
This simplifies the TSs and allows wording and formatting to be consistent with the STS, encouraging uniformity between the HNP units and the SNC fleet. Additionally, the NRC staff concludes that the requirements of | Verify suppression pool average temperature s 120°F. | ||
Based on the above, the NRC staff concludes that the changes to TS 5.5.7 are acceptable. 4.0 REGULATORY COMMITMENTS SNC provided two regulatory commitments with the LAR. The first regulatory commitment states: A statement will be added to the FSAR similar to the following regarding the performance of logic testing for critical emergency diesel generator trip functions: | Revised TS 3.6.2.1, Required Action D.2, would state: | ||
The critical emergency diesel generator protective trip functions (i.e., engine overspeed, generator differential current, and low lube oil pressure) are tested periodically per station procedures. | Determine suppression pool average temperature. | ||
The critical protective trip functions are tested by inputting or simulating appropriate signals and demonstrating that the associated instrumentation logic will function to actuate a trip of the emergency diesel generator. | Current TS 3.6.2.1, Required Actions E.1 and E.2, states: | ||
This regulatory commitment is related to the adoption of TSTF-400 (discussed in Section 3.17 of this safety evaluation). | E.1 Depressurize the reactor vessel to < 200 psig. | ||
The NRC staff reviewed the commitment and found that it provides additional information clarifying the testing of the EOG trip functions. | AND E.2 Be in MODE 4. | ||
The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.17 of this safety evaluation. | With Required Action E.2 having a Completion Time of: | ||
The second regulatory commitment states: SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." This regulatory commitment is related to the adoption of TSTF-439 (discussed in Section 3.18 of this safety evaluation). | 36 hours Revised TS 3.6.2.1 would state: | ||
The NRC staff reviewed the commitment and finds that it specifies a location for the administrative controls of TSTF-439-A. | Required Action E.2 and its associated Completion Time of 36 hours are deleted, resulting in Required Action E.1 remaining: | ||
The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.18 of this safety evaluation. | E.1 Depressurize the reactor vessel to < 200 psig. | ||
===NRC Staff Evaluation=== | |||
AT-traveler, such as TSTF-458-T, Revision 0, is prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those | |||
requirements. The NRC does not review nor approve T-travelers, and the proposed changes under T-travelers are not incorporated in the respective STS. | |||
The NRC staff reviewed these changes and determined that they ( 1) clarify the scope of Condition D and the intent of specified actions in Condition D, and (2) remove a redundant action in Condition E to eliminate an ambiguity between specified actions for existing Conditions D and E. Thus, these changes are of administrative nature and do not affect the technical content of specified TS requirements. Specifically, this eliminates having two Required Actions and Completion Times, both directing entry into MODE 4 with staggered Completion Times. | |||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the revised LCO conditions provide appropriate requirements to ensure that the LCO will be met. | |||
Based on the above, the NRC staff concludes that the changes to TS 3.6.2.1 are acceptable. | |||
3.20 TSTF-464-T. Revision 0, "Clarify the Control Rod Block Instrumentation Required Action" The proposed change clarifies the wording of Required Action C.2.1.2 of HNP TS 3.3.2.1, "Control Rod Block Instrumentation," to align with the TS Bases, Section 3.3.2.1. | |||
Current Hatch TS, and Proposed Changes: | |||
Current TS 3.3.2.1, Required Action C.2.1.2, states: | |||
Verify by administrative methods that startup with RWM [rod worth minimizer] | |||
inoperable has not been performed in the last calendar year. | |||
Revised TS 3.3.2.1, Required Action C.2.1.2, would state: | |||
Verify by administrative methods that startup with RWM inoperable has not been performed in the last 12 months. | |||
===NRC Staff Evaluation=== | |||
AT-traveler, such as TSTF-464-T, Revision 0, was prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those requirements. The NRC did not review nor approve T-travelers, and the proposed changes under T-travelers were not incorporated in the respective STS. | |||
The NRC staff reviewed the proposed change and determined that the current ambiguity of the phrase "last calendar year" does not provide assurance that the appropriate remedial measures are performed if the LCO is not met. Replacing the phrase "last calendar year" with the proposed phrase "last 12 months" provides additional clarity and assurance that appropriate remedial measures are performed if the LCO is not met. | |||
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2)will be met with the proposed change because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO. | |||
Based on the above, the NRC staff concludes that the change to TS 3.3.2.1 is acceptable. | |||
3.21 STS Adoption #1 - Revise the 5.5.7 Introductory Paragraph to be Consistent with the ISTS The licensee proposed to adopt the formatting and language in the STS, NUREG-1433, STS for General Electric BWR/4 Plants, Revision 4. | |||
Current TS 5.5. 7, "Ventilation Filter Testing Program (VFTP)," the introductory paragraph states: | |||
The VFTP will establish the required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, or: 1) after any structural maintenance on the HEPA filter or charcoal adsorber housings, 2) following painting, fire or chemical release in any ventilation zone communicating with the system, or | |||
: 3) after every 720 hours of charcoal adsorber operation. | |||
TS 5.5.7 is revised to state: | |||
A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2. | |||
===NRC Staff Evaluation=== | |||
The changes proposed for HNP TS 5.5.7 are similar to the wording in STS 5.5.8. This change removes detail from TS 5.5.7 and makes reference to RG 1.52, "Design, Testing, and Maintenance Criteria for Post-Accident Engineered-Safety-Feature Atmosphere Cleanup System Air Filtration and Adsorption Units of Light-Water-Cooled Nuclear Power Plants." The list of requirements for the program that the licensee proposed to remove are covered in Section C.6.b of RG 1.52 and TS SR 3.0.1. The NRC staff reviewed the proposed changes and determined that incorporating the requirement by reference for the VFTP is acceptable because detail can be removed from the TSs while maintaining the testing requirement. This simplifies the TSs and allows wording and formatting to be consistent with the STS, encouraging uniformity between the HNP units and the SNC fleet. | |||
Additionally, the NRC staff concludes that the requirements of 1O CFR 50.36(c)(5) continue to be met because the revised TS administrative controls testing program maintains its implementation requirements. | |||
Based on the above, the NRC staff concludes that the changes to TS 5.5.7 are acceptable. | |||
4.0 REGULATORY COMMITMENTS SNC provided two regulatory commitments with the LAR. | |||
The first regulatory commitment states: | |||
A statement will be added to the FSAR similar to the following regarding the performance of logic testing for critical emergency diesel generator trip functions: | |||
The critical emergency diesel generator protective trip functions (i.e., | |||
engine overspeed, generator differential current, and low lube oil pressure) are tested periodically per station procedures. The critical protective trip functions are tested by inputting or simulating appropriate signals and demonstrating that the associated instrumentation logic will function to actuate a trip of the emergency diesel generator. | |||
This regulatory commitment is related to the adoption of TSTF-400 (discussed in Section 3.17 of this safety evaluation). The NRC staff reviewed the commitment and found that it provides additional information clarifying the testing of the EOG trip functions. The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.17 of this safety evaluation. | |||
The second regulatory commitment states: | |||
SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." | |||
This regulatory commitment is related to the adoption of TSTF-439 (discussed in Section 3.18 of this safety evaluation). The NRC staff reviewed the commitment and finds that it specifies a location for the administrative controls of TSTF-439-A. The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.18 of this safety evaluation. | |||
==5.0 STATE CONSULTATION== | ==5.0 STATE CONSULTATION== | ||
In accordance with the Commission's regulations, the Georgia State official was notified of the proposed issuance of the amendments on June 22, 2016. The State official had no comments. | In accordance with the Commission's regulations, the Georgia State official was notified of the proposed issuance of the amendments on June 22, 2016. The State official had no comments. | ||
==7.0 CONCLUSION== | ==6.0 ENVIRONMENTAL CONSIDERATION== | ||
The amendments change a requirement with respect to the installation or use of facility components located within the restricted area as defined in 10 CFR Part 20 and change SRs. | |||
The NRC staff has determined that the amendments involve no significant increase in the amounts and no significant change in the types of any effluents that may be released offsite and that there is no significant increase in individual or cumulative occupational radiation exposure. | |||
The Commission has previously issued a proposed finding that the amendments involve no significant hazards consideration, and there has been no public comment on such finding (80 FR 17095; March 31, 2015). Accordingly, the amendments meet the eligibility criteria for | |||
categorical exclusion set forth in 10 CFR 51.22(c)(9). Pursuant to 10 CFR 51.22(b), no environmental impact statement or environmental assessment need be prepared in connection with the issuance of the amendments. | |||
==7.0 CONCLUSION== | |||
The Commission has concluded, based on the considerations discussed above, that: (1) there is reasonable assurance that the health and safety of the public will not be endangered by operation in the proposed manner, (2) there is reasonable assurance that such activities will be conducted in compliance with the Commission's regulations, and (3) the issuance of the amendments will not be inimical to the common defense and security or to the health and safety of the public. Principal Contributors: | The Commission has concluded, based on the considerations discussed above, that: (1) there is reasonable assurance that the health and safety of the public will not be endangered by operation in the proposed manner, (2) there is reasonable assurance that such activities will be conducted in compliance with the Commission's regulations, and (3) the issuance of the amendments will not be inimical to the common defense and security or to the health and safety of the public. | ||
Craig Harbuck, NRO Hien Le, NRO Margaret Chernoff, NRR Caroline Tilton, NRR Khadijah West, NRR Ravinder Grover, NRR Date: September 29, 2016 | Principal Contributors: Craig Harbuck, NRO Theodore Tjader, NRO Hien Le, NRO Derek Scully, NRO Margaret Chernoff, NRR Matthew Hamm, NRR Caroline Tilton, NRR Pete Snyder, NRR Khadijah West, NRR Larry Wheeler, NRR Ravinder Grover, NRR Date: September 29, 2016 | ||
ML16231A041 *by e-mail OFFICE NRR/DORL/LPL2-1 /PM NRR/DORL/LPL2-1 /LA NRR/DSS/STSB/BC* | |||
NAME MOrenak LRonewicz AKlein DATE 8/23/2016 8/23/2016 7/27/2016 OFFICE OGC NLO wlcomments NRR/DORL/LPL2-1 /BC NRR/DORL/LPL2-1/PM NAME Jlindell MMarkley MOrenak DATE 9/06/2016 9/29/2016 9/29/2016}} | |||
*by e-mail OFFICE NRR/DORL/LPL2-1 | |||
/PM NRR/DORL/LPL2-1 | |||
/LA NRR/DSS/STSB/BC* | |||
NAME MOrenak LRonewicz AKlein DATE 8/23/2016 8/23/2016 7/27/2016 OFFICE OGC NLO wlcomments NRR/DORL/LPL2-1 | |||
/BC NRR/DORL/LPL2-1/PM NAME Jlindell MMarkley MOrenak DATE 9/06/2016 9/29/2016 9/29/2016 |
Revision as of 14:58, 30 October 2019
ML16231A041 | |
Person / Time | |
---|---|
Site: | Hatch |
Issue date: | 09/29/2016 |
From: | Michael Orenak Plant Licensing Branch II |
To: | Pierce C Southern Nuclear Operating Co |
Orenak M, NRR/DORL/LPL2-1 | |
References | |
CAC MF5026, CAC MF5027 | |
Download: ML16231A041 (172) | |
Text
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 Septanber '29, 2016 Mr. Charles R. Pierce Regulatory Affairs Director Southern Nuclear Operating Company, Inc.
P.O. Box 1295 I Bin 038 Birmingham, AL 35201-1295
SUBJECT:
EDWIN I. HATCH NUCLEAR PLANT, UNIT NOS. 1AND2 - ISSUANCE OF AMENDMENTS REGARDING MULTIPLE TECHNICAL SPECIFICATION CHANGES (CAC NOS. MF5026 AND MF5027)
Dear Mr. Pierce:
The U.S. Nuclear Regulatory Commission (NRC or the Commission) has issued the enclosed Amendment No. 279 to Renewed Facility Operating License No. DPR-57 and Amendment No. 223 to Renewed Facility Operating License No. NPF-5 for the Edwin I. Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2, respectively. The amendments consist of changes to the Technical Specifications (TSs) in response to your application dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016.
The amendments revise Technical Specifications (TSs) by adopting 18 previously NRG-approved Technical Specifications Task Force (TSTF) travelers, two TSTF T-travelers, and one feature of the Improved Standard Technical Specifications (ISTS) not associated with a traveler. Southern Nuclear Operating Company, Inc. (SNC) stated that these changes would increase the consistency between the HNP TSs, the ISTS for Boiling Water Reactor/4 plants (NUREG-1433), and the TSs of the other plants in the SNC fleet.
C.R. Pierce A copy of the related Safety Evaluation is also enclosed. Notice of Issuance will be included in the Commission's biweekly Federal Register notice.
Michael D. Orenak, Project Manager Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation Docket Nos. 50-321 and 50-366
Enclosures:
- 1. Amendment No. 279 to DPR-57
- 2. Amendment No. 223 to NPF-5
- 3. Safety Evaluation cc w/enclosures: Distribution via Listserv
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC.
GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-321 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 279 Renewed License No. DPR-57
- 1. The Nuclear Regulatory Commission (the Commission) has found that:
A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 1 (the facility) Renewed Facility Operating License No. DPR-57 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 1
E. The issuance of this amendment is in accordance with 1O CFR Part 51 of the Commission's regulations and all applicable requirements have been satisfied.
- 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. DPR-57 is hereby amended to read as follows:
(2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 279, are hereby incorporated in the license.
Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.
- 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance.
FOR THE NUCLEAR REGULATORY COMMISSION
~~~
Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation
Attachment:
Changes to Renewed DPR-57 and Technical Specifications Date of Issuance: Septanber '29, 2016
ATTACHMENT TO LICENSE AMENDMENT NO. 279 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 1 RENEWED FACILITY OPERATING LICENSE NO. DPR-57 DOCKET NO. 50-321 Replace the following pages of the License and the Appendix A, Technical Specifications (TSs),
with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.
Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-2 1.3-2 1.3-6 1.3-6 1.3-7 1.3-7 1.4-1 1.4-1 1.4-2 1.4-2 1.4-3 1.4-3 1.4-5 1.4-5 1.4-6 1.4-7 3.1-10 3.1-10 3.1-17 3.1-17 3.3-4 3.3-4 3.3-5 3.3-5 3.3-7 3.3-7 3.3-16 3.3-16 3.3-25 3.3-25 3.3-48 3.3-48 3.3-49 3.3-49 3.3-50 3.3-50 3.3-51 3.3-51 3.3-52 3.3-52 3.3-53 3.3-53 3.3-54 3.3-54 3.3-55 3.3-55a 3.3-55b 3.5-1 3.5-1 3.5-2 3.5-2 3.6-8 3.6-8 3.6-9 3.6-9 3.6-11 3.6-11
3.6-22 3.6-22 3.6-23 3.6-23 3.6-35 3.6-35 3.6-36 3.6-36 3.6-37 3.6-37 3.6-38 3.6-38 3.6-39 3.6-39 3.6-40 3.6-40 3.8-2 3.8-2 3.8-4 3.8-4 3.8-10 3.8-10 3.8-11 3.8-11 3.8-12 3.8-12 3.8-13 3.8-13 3.8-14 3.8-14 3.8-15 3.8-15 3.8-16 3.8-16 3.8-17 3.8-17 3.8-18 3.8-18 3.8-29 3.8-29 3.8-30 3.8-30 3.8-37 3.8-37 5.0-9 5.0-9 5.0-10 5.0-10 5.0-13 5.0-13 5.0-14 5.0-14 5.0-15 5.0-15
for sample analysis or instrumentation calibration, or associated with radioactive apparatus or components; (6) Southern Nuclear, pursuant to the Act and 10 CFR Parts 30 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.
(C) This renewed license shall be deemed to contain and is subject to the conditions specified in the following Commission regulations in 10 CFR Chapter I; Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions specified or incorporated below:
(1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2804 megawatts thermal.
(2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Plan (Appendix B), as revised through Amendment No. 279 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.
The Surveillance Requirement (SR) contained in the Technical Specifications and listed below, is not required to be performed immediately upon implementation of Amendment No. 195. The SR listed below shall be successfully demonstrated before the time and condition specified:
SR 3.8.1.18 shall be successfully demonstrated at its next regularly scheduled performance.
(3) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained in the updated Fire Hazards Analysis and Fire Protection Program for the Edwin I. Hatch Nuclear Plant, Units 1 and 2, which was originally submitted by letter dated July 22, 1986. Southern Nuclear may make changes to the fire protection program without prior Commission approval only if the changes Renewed License No. DPR-57 Amendment No. 279
Completion Times 1.3 1.3 Completion Times DESCRIPTION a. Must exist concurrent with the first inoperability; and (continued)
- b. Must remain inoperable or not within limits after the first inoperability is resolved.
The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:
- a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or
- b. The stated Completion Time as measured from discovery of the subsequent inoperability.
The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery ... "
(continued)
HATCH UNIT 1 1.3-2 Amendment No. 279
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X A.1 Restore 7 days subsystem Function X inoperable. subsystem to OPERABLE status.
B. One Function Y B.1 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> subsystem Function Y inoperable. subsystem to OPERABLE status.
C. One Function X C.1 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> subsystem Function X inoperable. subsystem to OPERABLE AND status.
One Function Y OR subsystem inoperable. C.2 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> Function Y subsystem to OPERABLE status.
(continued)
HATCH UNIT 1 1.3-6 Amendment No. 279
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered).
If Required Action C.2 is completed within the specified Completion Time, Conditions Band C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A).
It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.
(continued)
HATCH UNIT 1 1.3-7 Amendment No. 279
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 Conditions 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, as well as certain Notes in the Surveillance column that modify performance requirements.
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both.
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.
The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. Some surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:
(continued)
HATCH UNIT 1 1.4-1 Amendment No. 279
Frequency 1.4 1.4 Frequency DESCRIPTION a. The Surveillance is not required to be met in the MODE or other (continued) specified condition to be entered; or
- b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or
- c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.
Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.
EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.
EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable.
(continued)
HATCH UNIT 1 1.4-2 Amendment No. 279
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-1 (continued)
If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable.
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 /> after
<:: 25% RTP 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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level
< 25% RTP to<::: 25% RTP, 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 />.
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 extension allowed by SR 3.0.2.
"Thereafter" indicates 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 reactor power decreases to
< 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.
(continued)
HATCH UNIT 1 1.4-3 Amendment No. 279
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-4 (continued)
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N()TE---------------------------
()n ly required to be met in M()DE 1.
Verify leakage rates are within limits. 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in M()DE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> (plus the extension allowed by SR 3.0.2) interval, but the unit was not in M()DE 1, there would be no failure of the SR nor failure to meet the LC(). Therefore, no violation of SR 3.0.4 occurs when changing M()DES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the M()DE change was not made into M()DE 1. Prior to entering M()DE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.
EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N()TE---------------------------
()nly required to be performed in M()DE 1.
Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assigned Applicability of the associated LC()) between performances.
(continued)
HATCH UNIT 1 1.4-5 Amendment No. 279
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-5 (continued)
As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1.
Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1.
Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.
EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
NOTE---------------------------
Not required to be met in MODE 3.
Verify parameter is within limits. 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued)
HATCH UNIT 1 1.4-6 Amendment No. 279
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-6 (continued) violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.
HATCH UNIT 1 1.4-7 Amendment No. 279
Control Rod Scram Times 3.1.4 SURVEILLANCE REQUIREMENTS
N 0 TE------------------------------------------------------------
0 uring single control rod scram time Surveillances, the control rod drive (CRD) pumps shall be isolated from the associated scram accumulator.
SURVEILLANCE FREQUENCY SR 3.1.4.1 Verify each control rod scram time is within the Prior to exceeding limits of Table 3.1.4-1 with reactor steam dome 40% RTP after each pressure<::: 800 psig. reactor shutdown
<:: 120 days SR 3.1.4.2 Verify, for a representative sample, each tested In accordance with control rod scram time is within the limits of the Surveillance Table 3.1.4-1 with reactor steam dome pressure Frequency Control
<::: 800 psig. Program SR 3.1.4.3 Verify each affected control rod scram time is Prior to declaring within the limits of Table 3.1.4-1 with any reactor control rod steam dome pressure. OPERABLE after work on control rod or CRD System that could affect scram time SR 3.1.4.4 Verify each affected control rod scram time is Prior to exceeding within the limits of Table 3.1.4-1 with reactor 40% RTP after fuel steam dome pressure<::: 800 psig. movement within the affected core cell Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time HATCH UNIT 1 3.1-10 Amendment No. 279
SLC System 3.1.7 3.1 REACTIVITY CONTROL SYSTEMS 3.1.7 Standby Liquid Control (SLC) System LCO 3.1.7 Two SLC subsystems shall be OPERABLE.
APPLICABILITY: MODES 1 and 2.
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Sodium pentaborate A.1 Restore sodium 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> solution not within pentaborate solution to Region A limits of within Region A limits.
Figure 3.1.7-1 or 3.1.7-2, but within the Region B limits.
B. One SLC subsystem B.1 Restore SLC 7 days inoperable for reasons subsystem to other than Condition A. OPERABLE status.
C. Two SLC subsystems C.1 Restore one SLC 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> inoperable for reasons subsystem to other than Condition A. OPERABLE status.
D. Required Action and D.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met.
HATCH UNIT 1 3.1-17 Amendment No. 279
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.1.1.2 ------------------------------N 0 TE----------------------------
N ot required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after THERMAL POWER~ 24% RTP.
Verify the absolute difference between the In accordance with average power range monitor (APRM) channels the Surveillance and the calculated power is s 2% RTP while Frequency Control operating at~ 24% RTP. Program SR 3.3.1.1.3 (Not used.)
SR 3.3.1.1.4 ----------------------------N 0 TE------------------------------
N ot required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.5 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.6 (Not used.)
(continued)
HATCH UNIT 1 3.3-4 Amendment No. 279
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.1.1.7 (Not used.)
SR 3.3.1.1.8 Calibrate the local power range monitors. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.10 ----------------------------NOTE------------------------------
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.11 Verify Turbine Stop Valve - Closure and In accordance with Turbine Control Valve Fast Closure, Trip Oil the Surveillance Pressure - Low Functions are not bypassed Frequency Control when THERMAL POWER is~ 27.6% RTP. Program SR 3.3.1.1.12 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program (cont1 n ued)
HATCH UNIT 1 3.3-5 Amendment No. 279
RPS Instrumentation 3.3.1.1 Table 3.3.1.1-1(page1 of3)
Reactor Protection System Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION D.1 REQUIREMENTS VALUE
- a. Neutron Flux - High 2 2(d) G SR 3.3.1.1.1 ::; 120/125 SR 3.3.1.1.4 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.1 ::; 120/125 SR 3.3.1.1.5 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15
- b. lnop 2 2(d) G SR 3.3.1.1.4 NA SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.5 NA SR 3.3.1.1.15
- 2. Average Power Range Monitor
- a. Neutron Flux - High 2 3(c) G SR 3.3.1.1.1 => 20% RTP (Setdown) SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13
- b. Simulated Thermal 3(c) F SR 3.3.1.1.1 => 0.57W+
Power- High SR 3.3.1.1.2 56.8% RTP SR 3.3.1.1.8 and SR 3.3.1.1.10 :>115.5%
SR 3.3.1.1.13 RTP(b)
- c. Neutron Flux - High 3(c) F SR 3.3.1.1.1 s 120% RTP SR 3.3.1.1.2 SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13
- d. lnop 1, 2 3(c) G SR 3.3.1.1.10 NA continued (a) With any control rod withdrawn from a core cell containing one or more fuel assemblies.
(b) 0.57W + 56.8% - 0.57 tiW RTP when reset for single loop operation per LCO 3.4.1, "Recirculation Loops Operating."
(c) Each APRM channel provides inputs to both trip systems.
(d) One channel in each quadrant of the core must be OPERABLE whenever the IRMs are required to be OPERABLE. Both the RWM and a second licensed operator must verify compliance with the withdrawal sequence when less than three channels in any trip system are OPERABLE.
HATCH UNIT 1 3.3-7 Amendment No. 279
Control Rod Block Instrumentation 3.3.2.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2.1.2 Verify by administrative Immediately methods that startup with RWM inoperable has not been performed in the last 12 months.
AND C.2.2 Verify movement of During control rod control rods is in movement compliance with banked position withdrawal sequence (BPWS) by a second licensed operator or other qualified member of the technical staff.
D. RWM inoperable during D.1 Verify movement of During control rod reactor shutdown. control rods is in movement compliance with BPWS by a second licensed operator or other qualified member of the technical staff.
E. One or more Reactor Mode E.1 Suspend control rod Immediately Switch - Shutdown Position withdrawal.
channels inoperable.
AND E.2 Initiate action to fully Immediately insert all insertable control rods in core cells containing one or more fuel assemblies.
HATCH UNIT 1 3.3-16 Amendment No. 279
PAM Instrumentation 3.3.3.1 Table 3.3.3.1-1(page1of1)
Post Accident Monitoring Instrumentation CONDITIONS REFERENCED REQUIRED FROM REQUIRED FUNCTION CHANNELS ACTION D.1
- 1. Reactor Steam Dome Pressure 2 E
- a. -317 inches to -17 inches 2 E
- b. -150 inches to +60 inches 2 E
- c. 0 inches to +60 inches 2 E
- d. 0 inches to +400 inches 1 NA
- 3. Suppression Pool Water Level
- a. 0 inches to 300 inches 2 E
- b. 133 inches to 163 inches 2 E
- 4. Drywell Pressure
- a. -1 O psig to +90 psig 2 E
- b. -5 psig to +5 psig 2 E C. 0 psig to +250 psig 2 E
- 5. Drywell Area Radiation (High Range) 2 F
- 6. Penetration Flow Path Primary Containment Isolation 2 per penetration flow E Valve Position path (a)(b)
- 7. (Deleted)
- 8. (Deleted) 2(C) E
- 9. Suppression Pool Water Temperature 6 E
- 10. Drywell Temperature in Vicinity of Reactor Level Instrument Reference Leg
- a. Output Voltage 1 per DG NA
- b. Output Current 1 per DG NA
- c. Output Power 1 per DG NA
- d. Battery Voltage 2 E
- 12. RHR Service Water Flow (a) Not required for isolation valves whose associated penetration flow path is isolated by at least one closed and deactivated automatic valve, closed manual valve, blind flange, or check valve with flow through the valve secured.
(b) Only one position indication channel is required for penetration flow paths with only one installed control room indication channel.
(c) Monitoring each of four quadrants.
HATCH UNIT 1 3.3-25 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 3.3 INSTRUMENTATION 3.3.6.1 Primary Containment Isolation Instrumentation LCO 3.3.6.1 The primary containment isolation instrumentation for each Function in Table 3.3.6.1-1 shall be OPERABLE.
APPLICABILITY: According to Table 3.3.6.1-1.
ACTIONS
N 0 TES-----------------------------------------------------------
- 1. Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls.
- 2. Separate Condition entry is allowed for each channel.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A.1 Place channel in trip. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> for channels inoperable. Functions 2.a, 2.b, 6.b, 7.a, and 7.b AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b B. ---------------N 0 TE------------- B.1 Restore isolation 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Not applicable for capability.
Function 5.c.
One or more automatic Functions with isolation capability not maintained.
C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel.
(continued)
HATCH UNIT 1 3.3-48 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME D. As required by Required D.1 Isolate associated main 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action C.1 and referenced steam line (MSL).
in Table 3.3.6.1-1.
OR D.2.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND D.2.2 Be in MODE4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> E. As required by Required E.1 Be in MODE 2. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action C.1 and referenced in Table 3.3.6.1-1.
F. As required by Required F.1 Isolate the affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s).
G. As required by Required G.1 Isolate the affected 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s).
H. As required by Required H.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action C.1 and referenced in Table 3.3.6.1-1. AND OR H.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action and associated Completion Time of Condition F or G not met.
(continued)
HATCH UNIT 1 3.3-49 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME I. As required by Required 1.1 Declare Standby Liquid 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Action C.1 and referenced Control (SLC) System in Table 3.3.6.1-1. inoperable.
OR 1.2 Isolate the Reactor 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Water Cleanup (RWCU) System.
J. As required by Required J.1 Initiate action to restore Immediately Action C.1 and referenced channel to OPERABLE in Table 3.3.6.1-1. status.
OR J.2 Initiate action to isolate Immediately the Residual Heat Removal (RHR)
Shutdown Cooling System.
SURVEILLANCE REQUIREMENTS
N 0 TES-----------------------------------------------------------
- 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function.
- 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> provided the associated Function maintains isolation capability.
SURVEILLANCE FREQUENCY SR 3.3.6.1.1 Perform CHANNEL CHECK. In accordance with the Surveillance Frequency Control Program (continued)
HATCH UNIT 1 3.3-50 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program HATCH UNIT 1 3.3-51 Amendment No. 279 I
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 1 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 1. Main Steam Line Isolation
- a. Reactor Vessel Water Level - 1,2,3 2 D SR 3.3.6.1.1 <: -113 inches Low Low Low, Level 1 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Main Steam Line Pressure - 2 E SR 3.3.6.1.3 <= 825 psig Low SR 3.3.6.1.6
- c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 ::; 138% rated Flow- High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Condenser Vacuum - Low 1, 2 D SR 3.3.6.1.3 <: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum
- e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 :5194°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 ::; 200°F Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- 2. Primary Containment Isolation
- a. Reactor Vessel Water Level 1,2,3 2 H SR 3.3.6.1.1 <: 0 inches
- Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Drywell Pressure - High 1,2,3 2 H SR 3.3.6.1.1 ::; 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed.
(b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels.
HATCH UNIT 1 3.3-52 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 Table3.3.6.1-1 (page2of5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 2. Primary Containment Isolation (continued)
C. Drywell Radiation - 1,2,3 F SR 3.3.6.1.1 s 138 R/hr High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6
- e. Refueling Floor Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr I Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6
- 3. High Pressure Coolant Injection (HPCI) System Isolation
- a. HPCI Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6
- b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 <! 100 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- e. HPCI Pipe Penetration Roorr 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 s 169°F Ambient Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 1 3.3-53 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 3 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 3. HPCI System Isolation (continued)
- g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :;; 16 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays
- h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 :;; 42°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :;; 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 4. Reactor Core Isolation Cooling (RCIC) System Isolation
- a. RCIC Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 :;; 306% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6
- b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 2! 60 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 :;; 20 psig Diaphragm Pressure - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 :;; 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :;; 169°F Ambient Area SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :;; 31 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays continued HATCH UNIT 1 3.3-54 Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 4. RCIC System Isolation (continued)
- g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :S 42°F Area Differential SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :S 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 5. RWCU System Isolation
- a. Area Temperature - High 1,2,3 1 per area F SR 3.3.6.1.1 :S 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 :S 67°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- c. SLC System Initiation 1,2 1(C) SR 3.3.6.1.6 NA
- d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 <: -47 inches Level - Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 6. RHR Shutdown Cooling System Isolation
- a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 :S 145 psig Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Reactor Vessel Water 3,4,5 2 (d) J SR 3.3.6.1.1 <: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continued)
(c) SLC System Initiation only inputs into one of the two trip systems.
(d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained.
HATCH UNIT 1 3.3-55a Amendment No. 279
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 5 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 7. Traversing lncore Probe System Isolation
- a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 2! 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Drywell Pressure - High 1,2,3 2 G SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 HATCH UNIT 1 3.3-55b Amendment No. 279
ECCS - Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.1 ECCS - Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic Depressurization System (ADS) function of six of seven safety/relief valves shall be OPERABLE.
APPLICABILITY: MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig.
ACTIONS
N 0 TE-------------------------------------------------------------
LCO 3.0.4.b is not applicable to HPCI.
CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable. subsystem(s) to OPERABLE status.
OR One LPCI pump in both LPCI subsystems inoperable.
B. Required Action and B.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A not AND met.
B.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 1 3.5-1 Amendment No. 279
ECCS - Operating 3.5.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME C. HPCI System inoperable. C.1 Verify by administrative 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> means RCIC System is OPERABLE.
AND C.2 Restore HPCI System 14 days to OPERABLE status.
D. HPCI System inoperable. D.1 Restore HPCI System 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> to OPERABLE status.
AND OR Condition A entered.
D.2 Restore low pressure 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> ECCS injection/spray subsystem to OPERABLE status.
E. Two or more ADS valves E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> inoperable.
AND OR E.2 Reduce reactor steam 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action and dome pressure to associated Completion =:;; 150 psig.
Time of Condition C or D not met.
F. Two or more low pressure F.1 Enter LCO 3.0.3. Immediately ECCS injection/spray subsystems inoperable for reasons other than Condition A.
OR HPCI System and two or more ADS valves inoperable.
HATCH UNIT 1 3.5-2 Amendment No. 279
PC IVs 3.6.1.3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) A.2 ------------N 0 TES-----------
- 1. Isolation devices in high radiation areas may be verified by use of administrative means.
- 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days for penetration flow path is isolation devices isolated. outside primary containment AND Prior to entering MODE 2 or 3 from MODE 4 if primary containment was de-inerted while in MODE 4, if not performed within the previous 92 days, for isolation devices inside primary containment B. -------------N 0 TE--------------- B.1 Isolate the affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Only applicable to penetration flow path by penetration flow paths with use of at least one two PCIVs. closed and de-activated
automatic valve, closed manual valve, or blind One or more penetration flange.
flow paths with two PCIVs inoperable except due to leakage not within limit.
(continued)
HATCH UNIT 1 3.6-8 Amendment No. 279
PC IVs 3.6.1.3 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME C. ---------------N 0 TE------------- C.1 Isolate the affected 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> except for Only applicable to penetration flow path by excess flow check penetration flow paths with use of at least one valve (EFCV) line and only one PCIV. closed and de-activated penetrations with a
automatic valve, closed closed system manual valve, or blind One or more penetration flange. AND flow paths with one PCIV inoperable except due to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for leakage not within limits. AND EFCV line and penetrations with a C.2 -----------NOTES---------- closed system
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days penetration flow path is isolated.
D. One or more penetration D.1 Restore leakage to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> flow paths with leakage not within limit.
within limit.
E. Required Action and E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A, B, C, AND or D not met in MODE 1, 2, or 3. E.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 1 3.6-9 Amendment No. 279
PC IVs 3.6.1.3 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.6.1.3.2 ------------------------------N 0 TES---------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for PCIVs that are open under administrative controls.
Verify each primary containment isolation manual In accordance with valve and blind flange that is located outside the Surveillance primary containment and not locked, sealed, or Frequency Control otherwise secured and is required to be closed Program during accident conditions is closed.
SR 3.6.1.3.3 -----------------------------N 0 TES----------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for PCIVs that are open under administrative controls.
Verify each primary containment manual isolation Prior to entering valve and blind flange that is located inside MODE 2 or 3 from primary containment and not locked, sealed, or MODE 4 if primary otherwise secured and is required to be closed containment was during accident conditions is closed. de-inerted while in MODE 4, if not performed within the previous 92 days SR 3.6.1.3.4 Verify continuity of the traversing incore probe In accordance with (Tl P) shear isolation valve explosive charge. the Surveillance Frequency Control Program SR 3.6.1.3.5 Verify the isolation time of each power operated, In accordance with automatic PCIV, except for MSIVs, is within limits. the lnservice Testing Program (continued)
HATCH UNIT 1 3.6-11 Amendment No. 279
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and B.1 Reduce THERMAL 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion POWER until all Time of Condition A not OPERABLE IRM met. channels s 25/40 divisions of full scale on Range 7.
C. Suppression pool average C.1 Suspend all testing that Immediately temperature> 105°F. adds heat to the suppression pool.
AND Any OPERABLE IRM channel > 25/40 divisions of full scale on Range 7.
AND Performing testing that adds heat to the suppression pool.
D. Suppression pool average D.1 Place the reactor mode Immediately temperature> 110°F. switch in the shutdown position.
AND D.2 Determine suppression Once per 30 minutes pool average temperature.
AND D.3 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 1 3.6-22 Amendment No. 279
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME E. Suppression pool average E.1 Depressurize the 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> temperature > 120°F. reactor vessel to
< 200 psig.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.2.1.1 Verify suppression pool average temperature is In accordance with within the applicable limits. the Surveillance Frequency Control Program 5 minutes when performing testing that adds heat to the suppression pool HATCH UNIT 1 3.6-23 Amendment No. 279
Secondary Containment 3.6.4.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2 Suspend CORE Immediately ALTERATIONS.
AND C.3 Initiate action to Immediately suspend OPDRVs.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.1.1 Verify all secondary containment equipment In accordance with hatches are closed and sealed. the Surveillance Frequency Control Program SR 3.6.4.1.2 Verify one secondary containment access door in In accordance with each access opening is closed. the Surveillance Frequency Control Program SR 3.6.4.1.3 -----------------------------NOTE-----------------------------
The number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration.
Verify secondary containment can be drawn In accordance with down to ~ 0.20 inch of vacuum water gauge in the Surveillance s 120 seconds using required standby gas Frequency Control treatment (SGT) subsystem(s). Program (continued)
HATCH UNIT 1 3.6-35 Amendment No. 279
Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.6.4.1.4 -----------------------------N 0 TE------------------------------
Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration.
Verify the secondary containment can be In accordance with maintained ;;:: 0.20 inch of vacuum water gauge the Surveillance for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> using required SGT subsystem(s) at Frequency Control a flow rate~ 4000 cfm per subsystem. Program HATCH UNIT 1 3.6-36 Amendment No. 279
SCI Vs 3.6.4.2 3.6 CONTAINMENT SYSTEMS 3.6.4.2 Secondary Containment Isolation Valves (SCIVs)
LCO 3.6.4.2 Each SCIV shall be OPERABLE.
APPLICABILITY: MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE ALTERATIONS, During operations with a potential for draining the reactor vessel (OPDRVs).
ACTIONS
NOTES-------------------------------------------------------------
- 1. Penetration flow paths may be unisolated intermittently under administrative controls.
- 2. Separate Condition entry is allowed for each penetration flow path.
- 3. Enter applicable Conditions and Required Actions for systems made inoperable by SCIVs.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more penetration A.1 Isolate the affected 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> flow paths with one SCIV penetration flow path by inoperable. use of at least one closed and deactivated automatic valve, closed manual valve, or blind flange.
AND A.2 -----------NOTES-----------
- 1. Isolation devices in high radiation areas may be verified by use of administrative means.
(continued)
HATCH UNIT 1 3.6-37 Amendment No. 279
SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days penetration flow path is isolated.
B. One or more penetration B.1 Isolate the affected 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> flow paths with two SCIVs penetration flow path by inoperable. use of at least one closed and deactivated automatic valve, closed manual valve, or blind flange.
C. Required Action and C.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A or B AND not met in MODE 1, 2, or 3.
C.2 Be in MODE4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> D. Required Action and D.1 -------------N 0 TE-----------
associated Completion LCO 3.0.3 is not Time of Condition A or B applicable.
not met during movement --------------------------------
of irradiated fuel assemblies in the Suspend movement of Immediately secondary containment, irradiated fuel during CORE assemblies in the ALTERATIONS, or during secondary containment.
(continued)
HATCH UNIT 1 3.6-38 Amendment No. 279
SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME D. (continued) AND D.2 Suspend CORE Immediately ALTERATIONS.
D.3 Initiate action to Immediately suspend OPDRVs.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.2.1 ----------------------------N 0 TES----------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for SCIVs that are open under administrative controls.
Verify each secondary containment isolation In accordance with manual valve and blind flange that is not locked, the Surveillance sealed, or otherwise secured and is required to be Frequency Control closed during accident conditions is closed. Program SR 3.6.4.2.2 Verify the isolation time of each power operated, In accordance with automatic SCIV is within limits. the Surveillance Frequency Control Program SR 3.6.4.2.3 Verify each automatic SCIV actuates to the In accordance with isolation position on an actual or simulated the Surveillance actuation signal. Frequency Control Program HATCH UNIT 1 3.6-39 Amendment No. 279
SGT System 3.6.4.3 3.6 CONTAINMENT SYSTEMS 3.6.4.3 Standby Gas Treatment (SGT) System LCO 3.6.4.3 The Unit 1 and Unit 2 SGT subsystems required to support LCO 3.6.4.1, "Secondary Containment," shall be OPERABLE.
APPLICABILITY: MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE AL TERA TIONS, During operations with a potential for draining the reactor vessel (OPDRVs).
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One required Unit 1 SGT A.1 Restore required Unit 1 30 days from subsystem inoperable SGT subsystem to discovery of failure to while: OPERABLE status. meet the LCO
- 2. Unit 1 reactor building-to-refueling floor plug not installed.
B. One required Unit 2 SGT B.1 Restore required SGT 7 days subsystem inoperable. subsystem to OPERABLE status.
OR One required Unit 1 SGT subsystem inoperable for reasons other than Condition A.
(continued)
HATCH UNIT 1 3.6-40 Amendment No. 279
AC Sources - Operating 3.8.1 ACTIONS
N 0 TE-------------------------------------------------------------
LCO 3.0.4.b is not applicable to DGs.
CONDITION REQUIRED ACTION COMPLETION TIME A. One required offsite circuit A.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable. OPERABLE required offsite circuits. AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND A.2 Declare required 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> from discovery feature(s) with no offsite of no offsite power to power available one 4160 V ESF bus inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. feature(s)
AND A.3 Restore required offsite 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> circuit to OPERABLE status.
B. One Unit 1 or the swing B.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> DG inoperable. OPERABLE required offsite circuit(s). AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND (continued)
HATCH UNIT 1 3.8-2 Amendment No. 279
AC Sources - Operating 3.8.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. (continued) B.4 (continued) AND 14 days for the swing diesel with maintenance restrictions met C. One required Unit 2 DG C.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable OPERABLE required offsite circuit( s). AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND C.2 Declare required 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery feature(s), supported by of Condition C the inoperable DG, concurrent with inoperable when the inoperability of redundant required redundant required feature(s) are inoperable. feature(s)
AND C.3.1 Determine OPERABLE 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> DG(s) are not inoperable due to common cause failure.
OR C.3.2 Perform SR 3.8.1.2.a for 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> OPERABLE DG(s).
(continued)
HATCH UNIT 1 3.8-4 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.6 -----------------------------NOTE------------------------------
This Surveillance shall not normally be performed in MODE 1 or 2. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify automatic and manual transfer of unit power In accordance with supply from the normal offsite circuit to the the Surveillance alternate offsite circuit. Frequency Control Program SR 3.8.1.7 ----------------------------N0 TES-----------------------------
- 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 1 controls.
Credit may be taken for unplanned events that satisfy this SR.
- 2. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG rejects a load greater than or In accordance with equal to its associated single largest post-accident the Surveillance load, and: Frequency Control Program
- a. Following load rejection, the frequency is s 65.5 Hz; and
- b. Within 3 seconds following load rejection, the voltage is~ 3740 V ands 4580 V.
(continued)
HATCH UNIT 1 3.8-10 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.8 ---------------------------NOTES------------------------------
- 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 1 controls.
Credit may be taken for unplanned events that satisfy this SR.
- 2. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable.
- 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG operating at a power factor s 0.88 In accordance with does not trip and voltage is maintained s 4800 V the Surveillance during and following a load rejection of<:: 2775 kW. Frequency Control Program (continued)
HATCH UNIT 1 3.8-11 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.9 ----------------------------N 0 TES-----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify on an actual or simulated loss of offsite In accordance with power signal: the Surveillance Frequency Control
- a. De-energization of emergency buses; Program
- b. Load shedding from emergency buses; and
- c. DG auto-starts from standby condition and:
- 1. Energizes permanently connected loads in :s; 12 seconds,
- 2. Energizes auto-connected shutdown loads through automatic load sequence timing devices,
- 3. Maintains steady state voltage
~ 3740 V and :s; 4243 V,
- 4. Maintains steady state frequency
~ 58.8 Hz and :s; 61.2 Hz, and
- 5. Supplies permanently connected and auto-connected shutdown loads for ~ 5 minutes.
(continued)
HATCH UNIT 1 3.8-12 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.10 ----------------------------N 0 TES-----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1 or 2. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify on an actual or simulated Emergency Core In accordance with Cooling System (ECCS) initiation signal each DG the Surveillance auto-starts from standby condition and: Frequency Control Program
- a. Ins 12 seconds after auto-start achieves voltage~ 3740 V, and after steady state conditions are reached, maintains voltage
~ 3740 V ands 4243 V;
- b. In s 12 seconds after auto-start achieves frequency~ 58.8 Hz, and after steady state conditions are reached, maintains frequency~ 58.8 Hz and s 61.2 Hz; and
- c. Operates for ~ 5 minutes.
(continued)
HATCH UNIT 1 3.8-13 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.11 ---------------------------N 0 TE--------------------------------
T his Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
In accordance with Verify each DG's non-critical automatic trips are the Surveillance bypassed on actual or simulated loss of voltage Frequency Control signal on the emergency bus concurrent with an Program actual or simulated ECCS initiation signal.
(continued)
HATCH UNIT 1 3.8-14 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.12 ----------------------------N 0 TES-----------------------------
- 1. Momentary transients outside the load and power factor ranges do not invalidate this test.
- 2. This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. If either of the other two DGs becomes inoperable, this surveillance shall be suspended.
Credit may be taken for unplanned events that satisfy this SR.
- 3. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable.
- 4. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG operating at a power factors 0.88 In accordance with operates for ~ 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />s: the Surveillance Frequency Control
- a. For~ 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> loaded ~ 3000 kW; and Program
- b. For the remaining hours of the test loaded
~ 2775 kW and s 2825 kW.
(continued)
HATCH UNIT 1 3.8-15 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.13 -----------------------------N 0 TES----------------------------
- 1. This Surveillance shall be performed within 5 minutes of shutting down the DG after the DG has operated ~ 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> loaded
~ 2565 kW. Momentary transients outside of load range do not invalidate this test.
- 2. All DG starts may be preceded by an engine prelube period.
- 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG starts and achieves, in In accordance with s 12 seconds, voltage~ 3740 V and frequency the Surveillance
~ 58.8 Hz; and after steady state conditions are Frequency Control reached, maintains voltage~ 3740 V ands 4243 V Program and frequency~ 58.8 Hz and s 61.2 Hz.
SR 3.8.1.14 ----------------------------N 0 TE-------------------------------
T his Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY providec an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify each DG: In accordance with the Surveillance
- a. Synchronizes with offsite power source Frequency Control while loaded with emergency loads upon a Program simulated restoration of offsite power;
- b. Transfers loads to offsite power source; and
- c. Returns to ready-to-load operation.
(continued)
HATCH UNIT 1 3.8-16 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.15 ----------------------------N 0 TE-------------------------------
T his Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
In accordance with Verify with a DG operating in test mode and the Surveillance connected to its bus, an actual or simulated ECCS Frequency Control initiation signal overrides the test mode by: Program
- a. Returning DG to ready-to-load operation; and
- b. Automatically energizing the emergency load from offsite power.
SR 3.8.1.16 -----------------------------N 0 TE------------------------------
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify interval between each sequenced load In accordance with block is within +/- 10% of design interval for each the Surveillance load sequence timing device. Frequency Control Program (continued)
HATCH UNIT 1 3.8-17 Amendment No. 279
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.17 -----------------------------N 0 TES----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify, on an actual or simulated loss of offsite In accordance with power signal in conjunction with an actual or the Surveillance simulated ECCS initiation signal: Frequency Control Program
- a. De-energization of emergency buses;
- b. Load shedding from emergency buses; and
- c. DG auto-starts from standby condition and:
- 1. Energizes permanently connected loads in s 12 seconds,
- 2. Energizes auto-connected emergency loads through automatic load sequence timing devices,
- 3. Achieves steady state voltage
~ 3740 V ands 4243 V,
- 4. Achieves steady state frequency
~ 58.8 Hz and s 61.2 Hz, and
- 5. Supplies permanently connected and auto-connected emergency loads for~ 5 minutes.
(continued)
HATCH UNIT 1 3.8-18 Amendment No. 279
DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.4.6 Verify each required battery charger supplies In accordance with
- 400 amps for station service subsystems, and the Surveillance
- 100 amps for DG subsystems at ;
- : 129 V for Frequency Control
- 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br />. Program SR 3.8.4.7 -----------------------------N 0 TES----------------------------
- 1. The modified performance discharge test in SR 3.8.4.8 may be performed in lieu of the service test in SR 3.8.4.7.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify battery capacity is adequate to supply, and In accordance with maintain in OPERABLE status, the required the Surveillance emergency loads for the design duty cycle when Frequency Control subjected to a battery service test. Program (continued)
HATCH UNIT 1 3.8-29 Amendment No. 279
DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.4.8 -----------------------------N 0 TE------------------------------
T his Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify battery capacity is~ 80% of the In accordance with manufacturer's rating when subjected to a the Surveillance performance discharge test or a modified Frequency Control performance discharge test. Program 12 months when battery shows degradation or has reached 85% of expected life with capacity < 100% of manufacturer's rating 24 months when battery has reached 85% of expected life with capacity ~ 100% of manufacturer's rating SR 3.8.4.9 For required Unit 2 DC sources, the SRs of Unit 2 In accordance with Specification 3.8.4 are applicable. applicable SRs HATCH UNIT 1 3.8-30 Amendment No. 279
Distribution Systems - Operating 3.8.7 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME B. One or more (Unit 1 or B.1 Restore DG DC 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> swing bus) DG DC electrical power electrical power distribution distribution subsystem subsystems inoperable. to OPERABLE status.
C. One or more (Unit 1 or C.1 Restore AC electrical 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> swing bus) AC electrical power distribution power distribution subsystem to subsystems inoperable. OPERABLE status.
D. One Unit 1 station service D.1 Restore Unit 1 station 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> DC electrical power service DC electrical distribution subsystem power distribution inoperable. subsystem to OPERABLE status.
E. Required Action and E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A, B, C, AND or D not met.
E.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> F. Two or more electrical F.1 Enter LCO 3.0.3. Immediately power distribution subsystems inoperable that result in a loss of function.
HATCH UNIT 1 3.8-37 Amendment No. 279
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.4 Radioactive Effluent Controls Program (continued)
- c. Monitoring, sampling, and analysis of radioactive liquid and gaseous effluents in accordance with 1O CFR 20.1302 and with the methodology and parameters in the ODCM;
- d. Limitations on the annual and quarterly doses or dose commitment to a member of the public from radioactive materials in liquid effluents released from each unit to unrestricted areas, conforming to 1O CFR 50, Appendix I;
- e. Determination of cumulative dose contributions from radioactive effluents for the current calendar quarter and current calendar year in accordance with the methodology and parameters in the ODCM at least every 31 days. Determination of projected dose contributions from radioactive effluents in accordance with the methodology in the ODCM at least every 31 days;
- f. Limitations on the functional capability and use of the liquid and gaseous effluent treatment systems to ensure that appropriate portions of these systems are used to reduce releases of radioactivity when the projected doses in a period of 31 days would exceed 2% of the guidelines for the annual dose or dose commitment, conforming to 10 CFR 50, Appendix I;
- g. Limitations on the dose rate resulting from radioactive material released in gaseous effluents to areas beyond the site boundary as follows:
- 1) For noble gases, less than or equal to a dose rate of 500 mrem/year to the total body and less than or equal to a dose rate of 3000 mrem/year to the skin, and
- 2) For iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half-lives greater than 8 days, less than or equal to a dose rate of 1500 mrem/year to any organ;
- h. Limitations on the annual and quarterly air doses resulting from noble gases released in gaseous effluents from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I;
- i. Limitations on the annual and quarterly doses to a member of the public from iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half lives > 8 days in gaseous effluents released from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I; and
- j. Limitations on the annual dose or dose commitment to any member of the public due to releases of radioactivity and to radiation from uranium fuel cycle sources, conforming to 40 CFR 190.
(continued)
HATCH UNIT 1 5.0-9 Amendment No. 279
Programs and Manuals 5.5 5.5 Programs and Manuals (continued) 5.5.5 Component Cyclic or Transient Limit This program provides controls to track FSAR Section 4.2, cyclic and transient occurrences, to ensure that reactor coolant pressure boundary components are maintained within the design limits.
5.5.6 lnservice Testing Program This program provides controls for inservice testing of ASME Code Class 1, 2, and 3 components including applicable supports.
- a. Testing frequencies specified in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda are as follows:
ASME Boiler and Pressure Vessel Code and Applicable Required Frequencies Addenda Terminology for for Performing lnservice lnservice Testing Activities Testing Activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days Yearly or annually At least once per 366 days
- b. The provisions of SR 3.0.2 are applicable to the frequencies for performing inservice testing activities;
- c. The provisions of SR 3.0.3 are applicable to inservice testing activities; and
- d. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specification.
5.5.7 Ventilation Filter Testing Program (VFTP)
A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2.
(continued)
HATCH UNIT 1 5.0-10 Amendment No. 279
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.8 Explosive Gas and Storage Tank Radioactivity Monitoring Program (continued)
The program shall include:
- a. The limits for the concentrations of hydrogen in the main condenser offgas treatment system and a surveillance program to ensure the limits are maintained. Such limits shall be appropriate to the system's design criteria (i.e., whether or not the system is designed to withstand a hydrogen explosion); and
- b. A surveillance program to ensure that the quantity of radioactivity contained in all outdoor liquid radwaste tanks that are not surrounded by liners, dikes, or walls capable of holding the tanks' contents and that do not have tank overflows and surrounding area drains connected to the liquid radwaste treatment system is less than the amount that would result in concentrations less than the limits of 1O CFR 20, Appendix B, Table 2, Column 2, at the nearest potable water supply and the nearest surface water supply in an unrestricted area, in the event of an uncontrolled release of the tanks' contents.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies.
5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following:
- a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has:
- 1. An API gravity or an absolute specific gravity within limits,
- 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and
- 3. A water and sediment content within limits;
- b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued)
HATCH UNIT 1 5.0-13 Amendment No. 279
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued)
- c. Total particulate concentration of the fuel oil is ~ 10 mg/liter when tested every 92 days.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies.
5.5.10 Safety Function Determination Program (SFDP)
This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following:
- a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected;
- b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists;
- c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and
- d. Other appropriate limitations and remedial or compensatory actions.
A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and:
- a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or
- b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or
- c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable.
(continued)
HATCH UNIT 1 5.0-14 Amendment No. 279
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 Safety Function Determination Program (SFDP) (continued)
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system.
5.5.11 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications.
- a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews.
- b. Licensees may make changes to Bases without prior NRG approval provided the changes do not require either of the following:
- 1. A change in the TS incorporated in the license; or
- 2. A change to the updated FSAR or Bases that requires NRG approval pursuant to 10 CFR 50.59.
- c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR.
- d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRG prior to implementation. Changes to the Bases implemented without prior NRG approval shall be provided to the NRG on a frequency consistent with 10 CFR 50.71(e).
(continued)
HATCH UNIT 1 5.0-15 Amendment No. 279
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SOUTHERN NUCLEAR OPERATING COMPANY, INC.
GEORGIA POWER COMPANY OGLETHORPE POWER CORPORATION MUNICIPAL ELECTRIC AUTHORITY OF GEORGIA CITY OF DALTON, GEORGIA DOCKET NO. 50-366 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 AMENDMENT TO RENEWED FACILITY OPERATING LICENSE Amendment No. 223 Renewed License No. NPF-5
- 1. The Nuclear Regulatory Commission (the Commission) has found that:
A. The application for amendment to the Edwin I. Hatch Nuclear Plant, Unit No. 2 (the facility) Renewed Facility Operating License No. NPF-5 filed by Southern Nuclear Operating Company, Inc. (the licensee), acting for itself; Georgia Power Company; Oglethorpe Power Corporation; Municipal Electric Authority of Georgia; and City of Dalton, Georgia (the owners), dated October 10, 2014, as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016, complies with the standards and requirements of the Atomic Energy Act of 1954, as amended (the Act), and the Commission's rules and regulations as set forth in 10 CFR Chapter I; B. The facility will operate in conformity with the application, the provisions of the Act, and the rules and regulations of the Commission; C. There is reasonable assurance (i) that the activities authorized by this amendment can be conducted without endangering the health and safety of the public, and (ii) that such activities will be conducted in compliance with the Commission's regulations set forth in 10 CFR Chapter I; D. The issuance of this amendment will not be inimical to the common defense and security or to the health and safety of the public; and Enclosure 2
E. The issuance of this amendment is in accordance with 10 CFR Part 51 of the Commission's regulations and all applicable requirements have been satisfied.
- 2. Accordingly, the license is hereby amended by page changes to the Technical Specifications as indicated in the attachment to this license amendment, and paragraph 2.C.(2) of Renewed Facility Operating License No. NPF-5 is hereby amended to read as follows:
(2) Technical Specifications The Technical Specifications contained in Appendix A and the Environmental Protection Plan contained in Appendix B, as revised through Amendment No. 223 are hereby incorporated in the license.
Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.
- 3. This license amendment is effective as of its date of issuance and shall be implemented within 120 days from the date of issuance.
FOR THE NUCLEAR REGULATORY COMMISSION Michael T. Markley, Chief Plant Licensing Branch 11-1 Division of Operating Reactor Licensing Office of Nuclear Reactor Regulation
Attachment:
Changes to Renewed NPF-5 and Technical Specifications Date of Issuance: Septenber 29, Xl16
ATTACHMENT TO LICENSE AMENDMENT NO. 223 EDWIN I. HATCH NUCLEAR PLANT, UNIT NO. 2 RENEWED FACILITY OPERATING LICENSE NO. NPF-5 DOCKET NO. 50-366 Replace the following pages of the License and the Appendix A, Technical Specifications (TSs),
with the attached revised pages. The revised pages are identified by amendment number and contain marginal lines indicating the areas of change.
Remove Pages Insert Pages License License 4 4 TSs TSs 1.3-2 1.3-2 1.3-6 1.3-6 1.3-7 1.3-7 1.4-1 1.4-1 1.4-2 1.4-2 1.4-3 1.4-3 1.4-5 1.4-5 1.4-6 1.4-7 3.1-10 3.1-10 3.1-17 3.1-17 3.3-4 3.3-4 3.3-5 3.3-5 3.3-7 3.3-7 3.3-16 3.3-16 3.3-25 3.3-25 3.3-48 3.3-48 3.3-49 3.3-49 3.3-50 3.3-50 3.3-51 3.3-51 3.3-52 3.3-52 3.3-53 3.3-53 3.3-54 3.3-54 3.3-55 3.3-55a 3.3-55b 3.5-1 3.5-1 3.5-2 3.5-2 3.6-8 3.6-8 3.6-9 3.6-9 3.6-11 3.6-11
3.6-22 3.6-22 3.6-23 3.6-23 3.6-34 3.6-34 3.6-35 3.6-35 3.6-36 3.6-36 3.6-37 3.6-37 3.6-38 3.6-38 3.6-40 3.6-40 3.8-2 3.8-2 3.8-4 3.8-4 3.8-10 3.8-10 3.8-11 3.8-11 3.8-12 3.8-12 3.8-13 3.8-13 3.8-14 3.8-14 3.8-15 3.8-15 3.8-16 3.8-16 3.8-17 3.8-17 3.8-18 3.8-18 3.8-29 3.8-29 3.8-30 3.8-30 3.8-38 3.8.38 5.0-9 5.0-9 5.0-10 5.0-10 5.0-13 5.0-13 5.0-14 5.0-14 5.0-15 5.0-15
(6) Southern Nuclear, pursuant to the Act and 1O CFR Parts 30 and 70, to possess, but not separate, such byproduct and special nuclear materials as may be produced by the operation of the facility.
(C) This renewed license shall be deemed to contain, and is subject to, the conditions specified in the following Commission regulations in 10 CFR Chapter I: Part 20, Section 30.34 of Part 30, Section 40.41 of Part 40, Section 50.54 of Part 50, and Section 70.32 of Part 70; all applicable provisions of the Act and the rules, regulations, and orders of the Commission now or hereafter in effect; and the additional conditions 2 specified or incorporated below:
(1) Maximum Power Level Southern Nuclear is authorized to operate the facility at steady sate reactor core power levels not in excess of 2,804 megawatts thermal, in accordance with the conditions specified herein.
(2) Technical Specifications The Technical Specifications (Appendix A) and the Environmental Protection Plan (Appendix B); as revised through Amendment No. 223 are hereby incorporated in the renewed license. Southern Nuclear shall operate the facility in accordance with the Technical Specifications and the Environmental Protection Plan.
(3) Additional Conditions The matters specified in the following conditions shall be completed to the satisfaction of the Commission within the stated time periods following the issuance of the renewed license or within the operational restrictions indicated. The removal of these conditions shall be made by an amendment to the license supported by a favorable evaluation by the Commission.
(a) Fire Protection Southern Nuclear shall implement and maintain in effect all provisions of the fire protection program, which is referenced in the Updated Final Safety Analysis Report for the facility, as contained 2
The original licensee authorized to possess, use, and operate the facility with Georgia Power Company (GPC). Consequently, certain historical references to GPC remain in certain license conditions.
Renewed License No. NPF-5 Amendment No. 223
Completion Times 1.3 1.3 Completion Times DESCRIPTION a. Must exist concurrent with the first inoperability; and (continued)
- b. Must remain inoperable or not within limits after the first inoperability is resolved.
The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:
- a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or
- b. The stated Completion Time as measured from discovery of the subsequent inoperability.
The above Completion Time extension does not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each division, subsystem, component or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.
The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery ... "
(continued)
HATCH UNIT 2 1.3-2 Amendment No. 223
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X A.1 Restore 7 days subsystem Function X inoperable. subsystem to OPERABLE status.
B. One Function Y B.1 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> subsystem Function Y inoperable. subsystem to OPERABLE status.
C. One Function X C.1 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> subsystem Function X inoperable. subsystem to OPERABLE AND status.
One Function Y OR subsystem inoperable. C.2 Restore 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> Function Y subsystem to OPERABLE status.
(continued)
HATCH UNIT 2 1.3-6 Amendment No. 223
Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)
When one Function X subsystem and one Function Y subsystem are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each subsystem, starting from the time each subsystem was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second subsystem was declared inoperable (i.e., the time the situation described in Condition C was discovered).
If Required Action C.2 is completed within the specified Completion Time, Conditions Band Care exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected subsystem was declared inoperable (i.e., initial entry into Condition A).
It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.
(continued)
HATCH UNIT 2 1.3-7 Amendment No. 223
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 Conditions 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, as well as certain Notes in the Surveillance column that modify performance requirements.
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both.
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.
The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:
(continued)
HATCH UNIT 2 1.4-1 Amendment No. 223
Frequency 1.4 1.4 Frequency DESCRIPTION a. The Surveillance is not required to be met in the MODE or other (continued) specified condition to be entered; or
- b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or
- c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.
Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.
EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.
EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 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 is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Examples 1.4-3 and 1.4-4), then SR 3.0.3 becomes applicable.
(continued)
HATCH UNIT 2 1.4-2 Amendment No. 223
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-1 (continued)
If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, then SR 3.0.4 becomes applicable. The surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the mode or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable.
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 /> after
- 25% RTP 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" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level
< 25% RTP to;:: 25% RTP, 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 />.
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 extension allowed by SR 3.0.2.
"Thereafter" indicates 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 reactor power decreases to
< 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.
(continued)
HATCH UNIT 2 1.4-3 Amendment No. 223 I
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-4 (continued)
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N 0 TE-----------------------------
0 nly required to be met in MODE 1.
Verify leakage rates are within limits. 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> (plus the extension allowed by SR 3.0.2) interval, but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.
EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N 0 TE-----------------------------
0 n Iy required to be performed in MODE 1.
Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in MODE 1, 2, or 3 (the assumed Applicability of the associated LCO) between performances.
(continued)
HATCH UNIT 2 1.4-5 Amendment No. 223
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-5 (continued)
As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1.
Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1 .
Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed, If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.
EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N 0 TE-----------------------------
N ot required to be met in MODE 3.
Verify parameter is within limits. 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no (continued)
HATCH UNIT 2 1.4-6 Amendment No. 223
Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-6 (continued) violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.
HATCH UNIT 2 1.4-7 Amendment No. 223
Control Rod Scram Times 3.1.4 SURVEILLANCE REQUIREMENTS
N 0 TE------------------------------------------------------------
0 u ring single control rod scram time Surveillances, the control rod drive (CRD) pumps shall be isolated from the associated scram accumulator.
SURVEILLANCE FREQUENCY SR 3.1.4.1 Verify each control rod scram time is within the Prior to exceeding limits of Table 3.1.4-1 with reactor steam dome 40% RTP after each pressure~ 800 psig. reactor shutdown
~ 120 days SR 3.1.4.2 Verify, for a representative sample, each tested In accordance with control rod scram time is within the limits of the Surveillance Table 3.1.4-1 with reactor steam dome pressure Frequency Control
~ 800 psig. Program SR 3.1.4.3 Verify each affected control rod scram time is Prior to declaring within the limits of Table 3.1.4-1 with any reactor control rod steam dome pressure. OPERABLE after work on control rod or CRD System that could affect scram time SR 3.1.4.4 Verify each affected control rod scram time is Prior to exceeding within the limits of Table 3.1.4-1 with reactor 40% RTP after fuel steam dome pressure~ 800 psig. movement within the affected core cell Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time HATCH UNIT 2 3.1-10 Amendment No. 223
SLC System 3.1.7 3.1 REACTIVITY CONTROL SYSTEMS 3.1.7 Standby Liquid Control (SLC) System LCO 3.1.7 Two SLC subsystems shall be OPERABLE.
APPLICABILITY: MODES 1 and 2.
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. Sodium pentaborate A.1 Restore sodium 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> solution not within pentaborate solution to Region A limits of within Region A limits.
Figure 3.1.7-1or3.1.7-2, but within the Region B limits.
B. One SLC subsystem B.1 Restore SLC 7 days inoperable for reasons subsystem to other than Condition A. OPERABLE status.
C. Two SLC subsystems C.1 Restore one SLC 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> inoperable for reasons subsystem to other than Condition A. OPERABLE status.
D. Required Action and D.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time not met.
HATCH UNIT 2 3.1-17 Amendment No. 223
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.1.1.2 -----------------------------N 0 TE-----------------------------
N ot required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after THERMAL POWER;?: 24% RTP.
Verify the absolute difference between the In accordance with average power range monitor (APRM) channels the Surveillance and the calculated power is s 2% RTP while Frequency Control operating at;?: 24% RTP. Program SR 3.3.1.1.3 (Not used.)
SR 3.3.1.1.4 -----------------------------NOTE-----------------------------
Not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.5 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.6 (Not used.)
(continued)
HATCH UNIT 2 3.3-4 Amendment No. 223
RPS Instrumentation 3.3.1.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.1.1.7 (Not used.)
SR 3.3.1.1.8 Calibrate the local power range monitors. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.9 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.10 -----------------------------NOTE-----------------------------
For Function 2.a, not required to be performed when entering MODE 2 from MODE 1 until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after entering MODE 2.
Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.1.1.11 Verify Turbine Stop Valve - Closure and In accordance with Turbine Control Valve Fast Closure, Trip Oil the Surveillance Pressure - Low Functions are not bypassed Frequency Control when THERMAL POWER is~ 27.6% RTP. Program SR 3.3.1.1.12 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program (continued)
HATCH UNIT 2 3.3-5 Amendment No. 223
RPS Instrumentation 3.3.1.1 Table 3.3.1.1-1 (page 1 of 3)
Reactor Protection System Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION D.1 REQUIREMENTS VALUE
- a. Neutron Flux - High 2 2(d) G SR 3.3.1.1.1 $ 120/125 SR 3.3.1.1.4 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.1 $ 120/125 SR 3.3.1.1.5 divisions of full SR 3.3.1.1.13 scale SR 3.3.1.1.15
- b. lnop 2 2(d) G SR 3.3.1.1.4 NA SR 3.3.1.1.15 5(a) 2(d) H SR 3.3.1.1.5 NA SR 3.3.1.1.15
- 2. Average Power Range Monitor
- a. Neutron Flux - High 2 3(c) G SR 3.3.1.1.1 :> 20% RTP (Setdown) SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13
- b. Simulated Thermal 3(c) F SR 3.3.1.1.1 :> 0.57W+
Power- High SR 3.3.1.1.2 56.8% RTP SR 3.3.1.1.8 and:> 115.5%
SR 3.3.1.1.10 RTP(b)
SR 3.3.1.1.13
- c. Neutron Flux - High 3(c) F SR 3.3.1.1.1 :> 120% RTP SR 3.3.1.1.2 SR 3.3.1.1.8 SR 3.3.1.1.10 SR 3.3.1.1.13
- d. lnop 1, 2 3(c) G SR 3.3.1.1.10 NA continued)
(a) With any control rod withdrawn from a core cell containing one or more fuel assemblies.
(b) 0.57W + 56.8% - 0.57 tiW RTP when reset for single loop operation per LCO 3.4.1, "Recirculation Loops Operating."
(c) Each APRM channel provides inputs to both trip systems.
(d) One channel in each quadrant of the core must be OPERABLE whenever the IRMs are required to be OPERABLE. Both the RWM and a second licensed operator must verify compliance with the withdrawal sequence when less than three channels in any trip system are OPERABLE.
HATCH UNIT 2 3.3-7 Amendment No. 223
Control Rod Block Instrumentation 3.3.2.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2.1.2 Verify by administrative Immediately methods that startup with RWM inoperable has not been performed in the last 12 months.
AND C.2.2 Verify movement of During control rod control rods is in movement compliance with banked position withdrawal sequence (BPWS) by a second licensed operator or other qualified member of the technical staff.
D. RWM inoperable during D.1 Verify movement of During control rod reactor shutdown. control rods is in movement compliance with BPWS by a second licensed operator or other qualified member of the technical staff.
E. One or more Reactor Mode E.1 Suspend control rod Immediately Switch - Shutdown Position withdrawal.
channels inoperable.
AND E.2 Initiate action to fully Immediately insert all insertable control rods in core cells containing one or more fuel assemblies.
HATCH UNIT 2 3.3-16 Amendment No. 223
PAM Instrumentation 3.3.3.1 Table 3.3.3.1-1(page1of1)
Post Accident Monitoring Instrumentation CONDITIONS REFERENCED REQUIRED FROM REQUIRED FUNCTION CHANNELS ACTION D.1
- 1. Reactor Steam Dome Pressure 2 E
- a. -317 inches to -17 inches 2 E
- b. -150 inches to +60 inches 2 E
- c. 0 inches to +60 inches 2 E
- d. 0 inches to +400 inches 1 NA
- 3. Suppression Pool Water Level
- a. 0 inches to 300 inches 2 E
- b. 133 inches to 163 inches 2 E
- 4. Drywell Pressure
- a. -10 psig to +90 psig 2 E
- b. -5 psig to +5 psig 2 E
- c. O psig to +250 psig 2 E
- 5. Drywell Area Radiation (High Range) 2 F
- 6. Penetration Flow Path Primary Containment Isolation 2 per penetration flow E Valve Position path(a)(b)
- 7. (Deleted)
- 8. (Deleted) 2(C) E
- 9. Suppression Pool Water Temperature 6 E
- 10. Drywell Temperature in Vicinity of Reactor Level Instrument Reference Leg
- a. Output Voltage 1 per DG NA
- b. Output Current 1 per DG NA
- c. Output Power 1 per DG NA
- d. Battery Voltage 2 E
- 12. RHR Service Water Flow (a) Not required for isolation valves whose associated penetration flow path is isolated by at least one closed and deactivated automatic valve, closed manual valve, blind flange, or check valve with flow through the valve secured.
(b) Only one position indication channel is required for penetration flow paths with only one installed control room indication channel.
(c) Monitoring each of four quadrants.
HATCH UNIT 2 3.3-25 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 3.3 INSTRUMENTATION 3.3.6.1 Primary Containment Isolation Instrumentation LCO 3.3.6.1 The primary containment isolation instrumentation for each Function in Table 3.3.6.1-1 shall be OPERABLE.
APPLICABILITY: According to Table 3.3.6.1-1.
ACTIONS
N 0 TES-----------------------------------------------------------
- 1. Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls.
- 2. Separate Condition entry is allowed for each channel.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more required A.1 Place channel in trip. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> for channels inoperable. Functions 2.a, 2.b, 6.b, 7.a, and 7.b AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b B. --------------N 0 TE-------------- B.1 Restore isolation 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Not applicable for capability.
Function 5.c.
One or more automatic Functions with isolation capability not maintained.
C. Required Action and C.1 Enter the Condition Immediately associated Completion referenced in Time of Condition A or B Table 3.3.6.1-1 for the not met. channel.
(continued)
HATCH UNIT 2 3.3-48 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME D. As required by Required D.1 Isolate associated main 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action C.1 and referenced steam line (MSL).
in Table 3.3.6.1-1.
OR D.2.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND D.2.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> E. As required by Required E.1 Be in MODE 2. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action C.1 and referenced in Table 3.3.6.1-1.
F. As required by Required F.1 Isolate the affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s).
G. As required by Required G.1 Isolate the affected 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Action C.1 and referenced penetration flow in Table 3.3.6.1-1. path(s).
H. As required by Required H.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Action C.1 and referenced in Table 3.3.6.1-1. AND OR H.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action and associated Completion Time of Condition F or G not met.
(continued)
HATCH UNIT 2 3.3-49 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME I. As required by Required I. 1 Declare Standby Liquid 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Action C.1 and referenced Control (SLC) System in Table 3.3.6.1-1. inoperable.
OR 1.2 Isolate the Reactor 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Water Cleanup (RWCU) System.
J. As required by Required J.1 Initiate action to restore Immediately Action C.1 and referenced channel to OPERABLE in Table 3.3.6.1-1. status.
OR J.2 Initiate action to isolate Immediately the Residual Heat Removal (RHR)
Shutdown Cooling System.
SURVEILLANCE REQUIREMENTS
N 0 TES-----------------------------------------------------------
- 1. Refer to Table 3.3.6.1-1 to determine which SRs apply for each Primary Containment Isolation Function.
- 2. When a channel is placed in an inoperable status solely for performance of required Surveillances, entry into associated Conditions and Required Actions may be delayed for up to 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> provided the associated Function maintains isolation capability.
SURVEILLANCE FREQUENCY SR 3.3.6.1.1 Perform CHANNEL CHECK. In accordance with the Surveillance Frequency Control Program (continued)
HATCH UNIT 2 3.3-50 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.3.6.1.2 Perform CHANNEL FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.3 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.4 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.5 Perform CHANNEL CALIBRATION. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1.6 Perform LOGIC SYSTEM FUNCTIONAL TEST. In accordance with the Surveillance Frequency Control Program SR 3.3.6.1. 7 ---------------------------N0 TE-------------------------------
Channel sensors are excluded.
Verify the ISOLATION SYSTEM RESPONSE In accordance with TIME is within limits. the Surveillance Frequency Control Program HATCH UNIT 2 3.3-51 Amendment No. 223 I
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 1 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 1. Main Steam Line Isolation
- a. Reactor Vessel Water 1,2,3 2 D SR 3.3.6.1.1 <:: -113 inches Level - Low Low Low, SR 3.3.6.1.2 Level 1 SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1.7
- b. Main Steam Line 2 E SR 3.3.6.1.3 <:: 825 psig Pressure - Low SR 3.3.6.1.6
- c. Main Steam Line 1,2,3 2 per D SR 3.3.6.1.1 s 138% rated Flow- High MSL SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6 SR 3.3.6.1. 7
- d. Condenser Vacuum - Low 1, 2 D SR 3.3.6.1.3 <:: 7 inches Hg 2(a), 3(a) SR 3.3.6.1.6 vacuum
- e. Main Steam Tunnel 1,2,3 6 D SR 3.3.6.1.1 S194°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Turbine Building Area 1,2,3 16(b) D SR 3.3.6.1.2 s 200°F Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- 2. Primary Containment Isolation
- a. Reactor Vessel Water 1,2,3 2 H SR 3.3.6.1.1 <:: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Drywell Pressure -
High 1,2,3 2 H SR 3.3.6.1.1 s 1.92 psig I SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued (a) With any turbine stop valve not closed.
(b) With 8 channels per trip string. Each trip string shall have 2 channels per main steam line, with no more than 40 ft separating any two OPERABLE channels.
HATCH UNIT 2 3.3-52 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 2 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 2. Primary Containment Isolation (continued)
- c. Drywell Radiation - High 1,2,3 F SR 3.3.6.1.1 s 138 R/hr SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Reactor Building Exhaust 1,2,3 2 H SR 3.3.6.1.1 s 80 mR/hr Radiation - High SR 3.3.6.1.3 SR 3.3.6.1.6
- e. Refueling Floor Exhaust Radiation - High 1,2,3 2 H SR 3.3.6.1.1 SR 3.3.6.1.3 SR 3.3.6.1.6 s 80 mR/hr I
- 3. High Pressure Coolant Injection (HPCI) System Isolation
- a. HPCI Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 s 303% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6
- b. HPCI Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 ~ 100 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- c. HPCI Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 s 20 psig Diaphragm Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- e. HPCI Pipe Penetration Room 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Suppression Pool Area Ambient 1,2,3 F SR 3.3.6.1.1 s 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 continued HATCH UNIT 2 3.3-53 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 Table3.3.6.1-1 (page3of5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 3. HPCI System Isolation (continued)
- g. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :s: 16 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays
- h. Suppression Pool Area 1,2,3 F SR 3.3.6.1.1 :s:42°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- i. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 :s: 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 4. Reactor Core Isolation Cooling (RCIC) System Isolation
- a. RCIC Steam Line Flow - 1,2,3 F SR 3.3.6.1.1 :s: 307% rated High SR 3.3.6.1.2 steam flow SR 3.3.6.1.5 SR 3.3.6.1.6
- b. RCIC Steam Supply Line 1,2,3 2 F SR 3.3.6.1.1 ~ 60 psig Pressure - Low SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 C. RCIC Turbine Exhaust 1,2,3 2 F SR 3.3.6.1.1 :s: 20 psig Diaphragm Pressure - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- d. Drywell Pressure - High 1,2,3 F SR 3.3.6.1.1 :s: 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- e. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :s: 169°F Ambient Area SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- f. Suppression Pool Area 1,2,3 F SR 3.3.6.1.4 :s: 31 minutes Temperature - Time Delay SR 3.3.6.1.6 15 seconds Relays continued)
HATCH UNIT 2 3.3-54 Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 4 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 4. RCIC System Isolation (continued)
- g. RCIC Suppression Pool 1,2,3 F SR 3.3.6.1.1 :542°F Area Differential SR 3.3.6.1.2 Temperature - High SR 3.3.6.1.5 SR 3.3.6.1.6
- h. Emergency Area Cooler 1,2,3 F SR 3.3.6.1.1 s; 169°F Temperature - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 5. RWCU System Isolation
- a. Area Temperature - High 1,2,3 1 per area F SR 3.3.6.1.1 s; 150°F SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Area Ventilation 1,2,3 1 per area F SR 3.3.6.1.1 s; 67°F Differential Temperature - SR 3.3.6.1.2 High SR 3.3.6.1.5 SR 3.3.6.1.6
- c. SLC System Initiation 1,2 1(c) SR 3.3.6.1.6 NA
- d. Reactor Vessel Water 1,2,3 2 F SR 3.3.6.1.1 ;;:: -47 inches Level - Low Low, Level 2 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- 6. RHR Shutdown Cooling System Isolation
- a. Reactor Steam Dome 1,2,3 F SR 3.3.6.1.1 s; 145 psig Pressure - High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Reactor Vessel Water 3,4,5 2(d) J SR 3.3.6.1.1 ;;:: 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 (continue )
(c) SLC System Initiation only inputs into one of the two trip systems.
(d) Only one trip system required in MODES 4 and 5 when RHR Shutdown Cooling System integrity maintained.
HATCH UNIT 2 3.3-55a Amendment No. 223
Primary Containment Isolation Instrumentation 3.3.6.1 Table 3.3.6.1-1 (page 5 of 5)
Primary Containment Isolation Instrumentation APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM ALLOWABLE SPECIFIED PER TRIP REQUIRED SURVEILLANCE VALUE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS
- 7. Traversing lncore Probe System Isolation
- a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 ~ 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Drywell Pressure - High 1,2,3 2 G SR 3.3.6.1.1 :s 1.92 psig SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 HATCH UNIT 2 3.3-55b Amendment No. 223
ECCS - Operating 3.5.1 3.5 EMERGENCY CORE COOLING SYSTEMS (ECCS) AND REACTOR CORE ISOLATION COOLING (RCIC) SYSTEM 3.5.1 ECCS - Operating LCO 3.5.1 Each ECCS injection/spray subsystem and the Automatic Depressurization System (ADS) function of six of seven safety/relief valves shall be OPERABLE.
APPLICABILITY: MODE 1, MODES 2 and 3, except high pressure coolant injection (HPCI) and ADS valves are not required to be OPERABLE with reactor steam dome pressure s 150 psig.
ACTIONS
NOTE--------------------------------------------------------
LCO 3.0.4.b is not applicable to HPCI.
CONDITION REQUIRED ACTION COMPLETION TIME A. One low pressure ECCS A.1 Restore low pressure 7 days injection/spray subsystem ECCS injection/spray inoperable. subsystem(s) to OPERABLE status.
OR One LPCI pump in both LPCI subsystems inoperable.
B. Required Action and B.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A not AND met.
B.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 2 3.5-1 Amendment No. 223
ECCS - Operating 3.5.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME C. HPCI System inoperable. C.1 Verify by administrative 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> means RCIC System is OPERABLE.
AND C.2 Restore HPCI System 14 days to OPERABLE status.
D. HPCI System inoperable. D.1 Restore HPCI System 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> to OPERABLE status.
AND OR Condition A entered.
D.2 Restore low pressure 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> ECCS injection/spray subsystem to OPERABLE status.
E. Two or more ADS valves E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> inoperable.
AND OR E.2 Reduce reactor steam 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Required Action and dome pressure to associated Completion :s; 150 psig.
Time of Condition C or D not met.
F. Two or more low pressure F.1 Enter LCO 3.0.3. Immediately ECCS injection/spray subsystems inoperable for reasons other than Condition A.
OR HPCI System and two or more ADS valves inoperable.
HATCH UNIT 2 3.5-2 Amendment No. 223
PC IVs 3.6.1.3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) A.2 ------------N 0 TES-----------
- 1. Isolation devices in high radiation areas may be verified by use of administrative means.
- 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days for penetration flow path is isolation devices isolated. outside primary containment AND Prior to entering MODE 2 or 3 from MODE 4 if primary containment was de-inerted while in MODE 4, if not performed within the previous 92 days, for isolation devices inside primary containment B. --------------N 0 TE--------------- 8.1 Isolate the affected 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Only applicable to penetration flow path by penetration flow paths with use of at least one two PCIVs. closed and de-activated
automatic valve, closed manual valve, or blind One or more penetration flange.
flow paths with two PCIVs inoperable except due to leakage not within limit.
(continued)
HATCH UNIT 2 3.6-8 Amendment No. 223
PC IVs 3.6.1.3 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME C. --------------NOTE--------------- C.1 Isolate the affected 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> except for Only applicable to penetration flow path by excess flow check penetration flow paths with use of at least one valve (EFCV) line and only one PCIV. closed and de-activated penetrations with a
automatic valve, closed closed system manual valve, or blind One or more penetration flange. AND flow paths with one PCIV inoperable except due to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for leakage not within limits. AND EFCV line and penetrations with a C.2 ----------NO TES----------- closed system
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days penetration flow path is isolated.
D. One or more penetration D.1 Restore leakage to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> flow paths with leakage not within limit.
within limit.
E. Required Action and E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A, B, C, AND or D not met in MODE 1, 2, or 3. E.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 2 3.6-9 Amendment No. 223
PC IVs 3.6.1.3 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.6.1.3.2 ------------------------------N 0 TES---------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for PCIVs that are open under administrative controls.
Verify each primary containment isolation manual In accordance with valve and blind flange that is located outside the Surveillance primary containment and not locked, sealed, or Frequency Control otherwise secured and is required to be closed Program during accident conditions is closed.
SR 3.6.1.3.3 -----------------------------N 0 TES----------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for PCIVs that are open under administrative controls.
Verify each primary containment manual isolation Prior to entering valve and blind flange that is located inside MODE 2 or 3 from primary containment and not locked, sealed, or MODE 4 if primary otherwise secured and is required to be closed containment was during accident conditions is closed. de-inerted while in MODE 4, if not performed within the previous 92 days SR 3.6.1.3.4 Verify continuity of the traversing incore probe In accordance with (TIP) shear isolation valve explosive charge. the Surveillance Frequency Control Program SR 3.6.1.3.5 Verify the isolation time of each power operated, In accordance with automatic PCIV, except for MSIVs, is within limits. the Inservice Testing Program (continued)
HATCH UNIT 2 3.6-11 Amendment No. 223
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and B.1 Reduce THERMAL 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion POWER until all Time of Condition A not OPERABLE I RM met. channels s 25/40 divisions of full scale on Range 7.
C. Suppression pool average C.1 Suspend all testing that Immediately temperature> 105°F. adds heat to the suppression pool.
AND Any OPERABLE IRM channel > 25/40 divisions of full scale on Range 7.
AND Performing testing that adds heat to the suppression pool.
D. Suppression pool average D.1 Place the reactor mode Immediately temperature> 110°F. switch in the shutdown position.
AND D.2 Determine suppression Once per 30 minutes pool average temperature.
AND D.3 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (continued)
HATCH UNIT 2 3.6-22 Amendment No. 223
Suppression Pool Average Temperature 3.6.2.1 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME E. Suppression pool average E.1 Depressurize the 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> temperature> 120°F. reactor vessel to
< 200 psig.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.2.1.1 Verify suppression pool average temperature is In accordance with within the applicable limits. the Surveillance Frequency Control Program AND 5 minutes when performing testing that adds heat to the suppression pool HATCH UNIT 2 3.6-23 Amendment No. 223
Secondary Containment 3.6.4.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME C. (continued) C.2 Suspend CORE Immediately ALTERATIONS.
AND C.3 Initiate action to Immediately suspend OPDRVs.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.1.1 Verify all secondary containment equipment In accordance with hatches are closed and sealed. the Surveillance Frequency Control Program SR 3.6.4.1.2 Verify one secondary containment access door in In accordance with each access opening is closed. the Surveillance Frequency Control Program SR 3.6.4.1.3 -----------------------------N 0 TE-----------------------------
Th e number of standby gas treatment (SGT) subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration.
Verify secondary containment can be drawn In accordance with down to ~ 0.20 inch of vacuum water gauge in the Surveillance s 120 seconds using required standby gas Frequency Control treatment (SGT) subsystem(s). Program (continued)
HATCH UNIT 2 3.6-34 Amendment No. 223
Secondary Containment 3.6.4.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.6.4.1.4 -----------------------------N 0 TE------------------------------
Th e number of SGT subsystem(s) required for this Surveillance is dependent on the secondary containment configuration, and shall be one less than the number required to meet LCO 3.6.4.3, "Standby Gas Treatment (SGT) System," for the given configuration.
Verify the secondary containment can be In accordance with maintained ;:: 0.20 inch of vacuum water gauge the Surveillance for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> using required SGT subsystem(s) at Frequency Control a flow rates 4000 cfm per subsystem. Program HATCH UNIT 2 3.6-35 Amendment No. 223
SC IVs 3.6.4.2 3.6 CONTAINMENT SYSTEMS 3.6.4.2 Secondary Containment Isolation Valves (SCIVs)
LCO 3.6.4.2 Each SCIV shall be OPERABLE.
APPLICABILITY: MODES 1, 2, and 3, During movement of irradiated fuel assemblies in the secondary containment, During CORE AL TE RATIONS, During operations with a potential for draining the reactor vessel (OPDRV).
ACTIONS
N0 TES-------------------------------------------------------------
- 1. Penetration flow paths may be unisolated intermittently under administrative controls.
- 2. Separate Condition entry is allowed for each penetration flow path.
- 3. Enter applicable Conditions and Required Actions for systems made inoperable by SCIVs.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more penetration A.1 Isolate the affected 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> flow paths with one SCIV penetration flow path by inoperable. use of at least one closed and de-activated automatic valve, closed manual valve, or blind flange.
AND A.2 -----------NOTES-----------
- 1. Isolation devices in high radiation areas may be verified by use of administrative means.
(continued)
HATCH UNIT 2 3.6-36 Amendment No. 223
SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. (continued) 2. Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
Verify the affected Once per 31 days penetration flow path is isolated.
B. One or more penetration B.1 Isolate the affected 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> flow paths with two SCIVs penetration flow path by inoperable. use of at least one closed and de-activated automatic valve, closed manual valve, or blind flange.
C. Required Action and C.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A or B AND not met in MODE 1, 2, or 3.
C.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> D. Required Action and D.1 -------------N 0 TE----------
associated Completion LCO 3.0.3 is not Time of Condition A or B applicable.
not met during movement -------------------------------
of irradiated fuel assemblies in the Suspend movement of Immediately secondary containment, irradiated fuel during CORE assemblies in the ALTERATIONS, or during secondary containment.
(continued)
HATCH UNIT 2 3.6-37 Amendment No. 223
SCI Vs 3.6.4.2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME D. (continued)
D.2 Suspend CORE Immediately ALTERATIONS.
AND D.3 Initiate action to Immediately suspend OPDRVs.
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY SR 3.6.4.2.1 ----------------------------N 0 TES----------------------------
- 1. Valves and blind flanges in high radiation areas may be verified by use of administrative means.
- 2. Not required to be met for SCIVs that are open under administrative controls.
Verify each secondary containment isolation In accordance with manual valve and blind flange that is not locked, the Surveillance sealed, or otherwise secured and is required to be Frequency Control closed during accident conditions is closed. Program SR 3.6.4.2.2 Verify the isolation time of each power operated, In accordance with automatic SCIV is within limits. the Surveillance Frequency Control Program SR 3.6.4.2.3 Verify each automatic SCIV actuates to the In accordance with isolation position on an actual or simulated the Surveillance actuation signal. Frequency Control Program HATCH UNIT 2 3.6-38 Amendment No. 223
SGT System 3.6.4.3 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME B. One required Unit 2 SGT B.1 Restore required SGT 7 days subsystem inoperable. subsystem to OPERABLE status.
OR One required Unit 1 SGT subsystem inoperable for reasons other than Condition A.
C. Required Action and C.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A or B AND not met in MODE 1, 2, or 3.
C.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> D. Required Action and ------------------N 0 TE-----------------
associated Completion LCO 3.0.3 is not applicable.
Time of Condition A or B -------------------------------------------
not met during movement of irradiated fuel D.1 Place remaining Immediately assemblies in the OPERABLE SGT secondary containment, subsystem(s) in during CORE operation.
ALTERATIONS, or during OPDRVs. OR D.2.1 Suspend movement of Immediately irradiated fuel assemblies in secondary containment.
AND D.2.2 Suspend CORE Immediately ALTERATIONS.
AND D.2.3 Initiate action to Immediately suspend OPDRVs.
(continued)
HATCH UNIT 2 3.6-40 Amendment No. 223
AC Sources - Operating 3.8.1 ACTIONS
NOTE--------------------------------------------------------
LCO 3.0.4.b is not applicable to DGs.
CONDITION REQUIRED ACTION COMPLETION TIME A. One required offsite circuit A.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable. OPERABLE required offsite circuits. AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND A.2 Declare required 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> from discovery feature(s) with no offsite of no offsite power to power available one 4160 V ESF bus inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. feature(s)
AND A.3 Restore required offsite 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> circuit to OPERABLE status.
B. One Unit 2 or the swing DG B.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable. OPERABLE required offsite circuit(s). AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND (continued)
HATCH UNIT 2 3.8-2 Amendment No. 223
AC Sources - Operating 3.8.1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. (continued) B.4 (continued) AND 14 days for the swing diesel with maintenance restrictions met C. One required Unit 1 DG C.1 Perform SR 3.8.1.1 for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> inoperable. OPERABLE required offsite circuit(s). AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter AND C.2 Declare required 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from feature(s), supported by discovery the inoperable DG, of Condition C inoperable when the concurrent with redundant required inoperability of feature(s) are redundant required inoperable. feature(s)
AND C.3.1 Determine OPERABLE 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> DG(s) are not inoperable due to common cause failure.
OR C.3.2 Perform SR 3.8.1.2.a for 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> OPERABLE DG(s).
(continued)
HATCH UNIT 2 3.8-4 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.6 ----------------------------N 0 TE-------------------------------
T his Surveillance shall not normally be performed in MODE 1 or 2. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify automatic and manual transfer of unit power In accordance with supply from the normal offsite circuit to the the Surveillance alternate offsite circuit. Frequency Control Program SR 3.8.1.7 ----------------------------N 0 TES-----------------------------
- 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls.
Credit may be taken for unplanned events that satisfy this SR.
- 2. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG rejects a load greater than or In accordance with equal to its associated single largest post-accident the Surveillance load, and: Frequency Control Program
- a. Following load rejection, the frequency is s 65.5 Hz; and
- b. Within 3 seconds following load rejection, the voltage is;;:: 3740 V ands 4580 V.
(continued)
HATCH UNIT 2 3.8-10 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.8 -----------------------------N 0 TES----------------------------
- 1. This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit 2 controls.
Credit may be taken for unplanned events that satisfy this SR.
- 2. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable.
- 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG operating at a power factors 0.88 In accordance with does not trip and voltage is maintained s 4800 V the Surveillance during and following a load rejection of~ 2775 kW. Frequency Control Program (continued)
HATCH UNIT 2 3.8-11 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.9 ----------------------------N 0 TES-----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify on an actual or simulated loss of offsite In accordance with power signal: the Surveillance Frequency Control
- a. De-energization of emergency buses; Program
- b. Load kdding from emergency buses; and
- c. DG auto-starts from standby condition and:
- 1. Energizes permanently connected loads in s 12 seconds,
- 2. Energizes auto-connected shutdown loads through automatic load sequence timing devices,
- 3. Maintains steady state voltage
- 3740 V ands; 4243 V,
- 4. Maintains steady state frequency
- 58.8 Hz and s 61.2 Hz, and
- 5. Supplies permanently connected and auto-connected shutdown loads for ;:; 5 minutes.
(continued)
HATCH UNIT 2 3.8-12 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.10 ---------------------------N 0 TES----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1 or 2. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify on an actual or simulated Emergency Core In accordance with Cooling System (ECCS) initiation signal each DG the Surveillance auto-starts from standby condition and: Frequency Control Program
- a. Ins 12 seconds after auto-start achieves voltage~ 3740 V, and after steady state conditions are reached, maintains voltage
~ 3740 V ands 4243 V;
- b. Ins 12 seconds after auto-start achieves frequency ~ 58.8 Hz, and after steady state conditions are reached, maintains frequency ~ 58.8 Hz and s 61.2 Hz; and
- c. Operates for ~ 5 minutes.
(continued)
HATCH UNIT 2 3.8-13 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.11 --------------------------N 0 TE---------------------------------
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify each DG's non-critical automatic trips are In accordance with bypassed on actual or simulated loss of voltage the Surveillance signal on the emergency bus concurrent with an Frequency Control actual or simulated ECCS initiation signal. Program (continued)
HATCH UNIT 2 3.8-14 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.12 ---------------------------NOTES------------------------------
- 1. Momentary transients outside the load and power factor ranges do not invalidate this test.
- 2. This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. If either of the other two DGs becomes inoperable, this Surveillance shall be suspended.
Credit may be taken for unplanned events that satisfy this SR.
- 3. If grid conditions do not permit, the power factor limit is not required to be met. Under this condition, the power factor shall be maintained as close to the limit as practicable.
- 4. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG operating at a power factors 0.88 In accordance with operates for <! 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />s: the Surveillance Frequency Control
- a. For<! 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> loaded 2: 3000 kW; and Program
- b. For the remaining hours of the test loaded
<! 2775 kW and s 2825 kW.
(continued)
HATCH UNIT 2 3.8-15 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.13 ---------------------------NOTES------------------------------
- 1. This Surveillance shall be performed within 5 minutes of shutting down the DG after the DG has operated ~ 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> loaded
~ 2565 kW. Momentary transients outside of load range do not invalidate this test.
- 2. All DG starts may be preceded by an engine prelube period.
- 3. For the swing DG, a single test at the specified Frequency will satisfy this Surveillance for both units.
Verify each DG starts and achieves, in In accordance with
- 12 seconds, voltage ~ 37 40 V and frequency the Surveillance
~ 58.8 Hz; and after steady state conditions are Frequency Control reached, maintains voltage~ 3740 V and::;; 4243 V Program and frequency~ 58.8 Hz and ::;; 61.2 Hz.
SR 3.8.1.14 ---------------------------N 0 TE--------------------------------
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify each DG: In accordance with the Surveillance
- a. Synchronizes with offsite power source Frequency Control while loaded with emergency loads upon a Program simulated restoration of offsite power;
- b. Transfers loads to offsite power source; and
- c. Returns to ready-to-load operation.
(continued)
HATCH UNIT 2 3.8-16 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.1.15 ---------------------------NOTE-------------------------------
This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify with a DG operating in test mode and In accordance with connected to its bus, an actual or simulated ECCS the Surveillance initiation signal overrides the test mode by: Frequency Control Program
- a. Returning DG to ready-to-load operation; and
- b. Automatically energizing the emergency load from offsite power.
SR 3.8.1.16 -----------------------------NOTE------------------------------
This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify interval between each sequenced load block In accordance with is within 10% of design interval for each load the Surveillance sequence timing device. Frequency Control Program (continued)
HATCH UNIT 2 3.8-17 Amendment No. 223
AC Sources - Operating 3.8.1 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.1.17 ----------------------------N 0 TES-----------------------------
- 1. All DG starts may be preceded by an engine prelube period.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify, on an actual or simulated loss of offsite In accordance with power signal in conjunction with an actual or the Surveillance simulated ECCS initiation signal: Frequency Control Program
- a. De-energization of emergency buses;
- b. Load shedding from emergency buses; and
- c. DG auto-starts from standby condition and:
- 1. Energizes permanently connected loads in ::; 12 seconds,
- 2. Energizes auto-connected emergency loads through automatic load sequence timing devices,
- 3. Achieves steady state voltage
~ 3740 V and::; 4243 V,
- 4. Achieves steady state frequency
~ 58.8 Hz and::; 61.2 Hz, and
- 5. Supplies permanently connected and auto-connected emergency loads for ~ 5 minutes.
(continued)
HATCH UNIT 2 3.8-18 Amendment No. 223
DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS continued SURVEILLANCE FREQUENCY SR 3.8.4.7 -----------------------------N 0 TES----------------------------
- 1. The modified performance discharge test in SR 3.8.4.8 may be performed in lieu of the service test in SR 3.8.4.7.
- 2. This Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify battery capacity is adequate to supply, and In accordance with maintain in OPERABLE status, the required the Surveillance emergency loads for the design duty cycle when Frequency Control subjected to a battery service test. Program (continued)
HATCH UNIT 2 3.8-29 Amendment No. 223
DC Sources - Operating 3.8.4 SURVEILLANCE REQUIREMENTS (continued)
SURVEILLANCE FREQUENCY SR 3.8.4.8 -------------------------------N 0 TE----------------------------
Th is Surveillance shall not normally be performed in MODE 1, 2, or 3, except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
Verify battery capacity is ;;:: 80% of the In accordance with manufacturer's rating when subjected to a the Surveillance performance discharge test or a modified Frequency Control performance discharge test. Program 12 months when battery shows degradation or has reached 85% of expected life with capacity < 100% of manufacturer's rating 24 months when battery has reached 85% of expected life with capacity ;;:: 100% of manufacturer's rating SR 3.8.4.9 For required Unit 1 DC sources, the SRs of Unit 1 In accordance with Specification 3.8.4 are applicable. applicable SRs HATCH UNIT 2 3.8-30 Amendment No. 223
Distribution Systems - Operating 3.8.7 ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME B. One or more (Unit 2 or B.1 Restore DG DC 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> swing bus) DG DC electrical power electrical power distribution distribution subsystem subsystems inoperable. to OPERABLE status.
C. One or more (Unit 2 or C.1 Restore AC electrical 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> swing bus) AC electrical power distribution power distribution subsystem to subsystems inoperable. OPERABLE status.
D. One Unit 2 station service D.1 Restore Unit 2 station 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> DC electrical power service DC electrical distribution subsystem power distribution inoperable. subsystem to OPERABLE status.
E. Required Action and E.1 Be in MODE 3. 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> associated Completion Time of Condition A, B, C, AND or D not met.
E.2 Be in MODE 4. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> F. Two or more electrical F.1 Enter LCO 3.0.3. Immediately power distribution subsystems inoperable that result in a loss of function.
HATCH UNIT 2 3.8-38 Amendment No. 223
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.4 Radioactive Effluent Controls Program (continued)
- c. Monitoring, sampling, and analysis of radioactive liquid and gaseous effluents in accordance with 10 CFR 20.1302 and with the methodology and parameters in the ODCM;
- d. Limitations on the annual and quarterly doses or dose commitment to a member of the public from radioactive materials in liquid effluents released from each unit to unrestricted areas, conforming to 10 CFR 50, Appendix I;
- e. Determination of cumulative dose contributions from radioactive effluents for the current calendar quarter and current calendar year in accordance with the methodology and parameters in the ODCM at least every 31 days. Determination of projected dose contributions from radioactive effluents in accordance with the methodology in the ODCM at least every 31 days;
- f. Limitations on the functional capability and use of the liquid and gaseous effluent treatment systems to ensure that appropriate portions of these systems are used to reduce releases of radioactivity when the projected doses in a period of 31 days would exceed 2% of the guidelines for the annual dose or dose commitment, conforming to 10 CFR 50, Appendix I;
- g. Limitations on the dose rate resulting from radioactive material released in gaseous effluents to areas beyond the site boundary as follows:
- 1) For noble gases, less than or equal to a dose rate of 500 mrem/year to the total body and less than or equal to a dose rate of 3000 mrem/year to the skin, and
- 2) For iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half-lives greater than 8 days, less than or equal to a dose rate of 1500 mrem/year to any organ;
- h. Limitations on the annual and quarterly air doses resulting from noble gases released in gaseous effluents from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I;
- i. Limitations on the annual and quarterly doses to a member of the public from iodine-131, iodine-133, tritium, and all radionuclides in particulate form with half lives> 8 days in gaseous effluents released from each unit to areas beyond the site boundary, conforming to 10 CFR 50, Appendix I; and
- j. Limitations on the annual dose or dose commitment to any member of the public due to releases of radioactivity and to radiation from uranium fuel cycle sources, conforming to 40 CFR 190.
(continued)
HATCH UNIT 2 5.0-9 Amendment No. 223
Programs and Manuals 5.5 5.5 Programs and Manuals (continued) 5.5.5 Component Cyclic or Transient Limit This program provides controls to track FSAR Section 5.2, cyclic and transient occurrences, to ensure that reactor coolant pressure boundary components are maintained within the design limits.
5.5.6 lnservice Testing Program This program provides controls for inservice testing of ASME Code Class 1, 2, and 3 components including applicable supports.
- a. Testing frequencies specified in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda are as follows:
ASME Boiler and Pressure Vessel Code and Applicable Required Frequencies Addenda Terminology for for Performing lnservice lnservice Testing Activities Testing Activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days Yearly or annually At least once per 366 days
- b. The provisions of SR 3.0.2 are applicable to the frequencies for performing inservice testing activities;
- c. The provisions of SR 3.0.3 are applicable to inservice testing activities; and
- d. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specification.
5.5.7 Ventilation Filter Testing Program (VFTP)
A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2.
(continued)
HATCH UNIT 2 5.0-10 Amendment No. 223
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.8 Explosive Gas and Storage Tank Radioactivity Monitoring Program (continued)
The program shall include:
- a. The limits for the concentrations of hydrogen in the main condenser offgas treatment system and a surveillance program to ensure the limits are maintained. Such limits shall be appropriate to the system's design criteria (i.e., whether or not the system is designed to withstand a hydrogen explosion); and
- b. A surveillance program to ensure that the quantity of radioactivity contained in all outdoor liquid radwaste tanks that are not surrounded by liners, dikes, or walls capable of holding the tanks' contents and that do not have tank overflows and surrounding area drains connected to the liquid radwaste treatment system is less than the amount that would result in concentrations less than the limits of 10 CFR 20, Appendix B, Table 2, Column 2, at the nearest potable water supply and the nearest surface water supply in an unrestricted area, in the event of an uncontrolled release of the tanks' contents.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Explosive Gas and Storage Tank Radioactivity Monitoring Program surveillance frequencies.
5.5.9 Diesel Fuel Oil Testing Program A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following:
- a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has:
- 1. An API gravity or an absolute specific gravity within limits,
- 2. A flash point and kinematic viscosity within limits for ASTM 20 fuel oil, and
- 3. A water and sediment content within limits;
- b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 20 fuel oil; and (continued)
HATCH UNIT 2 5.0-13 Amendment No. 223
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.9 Diesel Fuel Oil Testing Program (continued)
- c. Total particulate concentration of the fuel oil is :::; 10 mg/liter when tested every 92 days.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies.
5.5.10 Safety Function Determination Program (SFDP)
This program ensures loss of safety function is detected and appropriate actions taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other appropriate limitations and remedial or compensatory actions may be identified to be taken as a result of the support system inoperability and corresponding exception to entering supported system Condition and Required Actions. This program implements the requirements of LCO 3.0.6. The SFDP shall contain the following:
- a. Provisions for cross division checks to ensure a loss of the capability to perform the safety function assumed in the accident analysis does not go undetected;
- b. Provisions for ensuring the plant is maintained in a safe condition if a loss of function condition exists;
- c. Provisions to ensure that an inoperable supported system's Completion Time is not inappropriately extended as a result of multiple support system inoperabilities; and
- d. Other appropriate limitations and remedial or compensatory actions.
A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable, and:
- a. A required system redundant to system(s) supported by the inoperable support system is also inoperable; or
- b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable; or
- c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable.
(continued)
HATCH UNIT 2 5.0-14 Amendment No. 223
Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.10 Safety Function Determination Program (SFDP) (continued)
The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by inoperability of a single Technical Specification support system, the appropriate Conditions and Required Actions to enter are those of the support system.
5.5.11 Technical Specifications (TS) Bases Control Program This program provides a means for processing changes to the Bases of these Technical Specifications.
- a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews.
- b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following:
- 1. A change in the TS incorporated in the license; or
- 2. A change to the updated FSAR or Bases that requires NRC approval pursuant to 10 CFR 50.59.
- c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR.
- d. Proposed changes that meet the criteria of item b above shall be reviewed and approved by the NRC prior to implementation. Changes to the Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71(e).
(continued)
HATCH UNIT 2 5.0-15 Amendment No. 223
UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. 20555-0001 SAFETY EVALUATION BY THE OFFICE OF NUCLEAR REACTOR REGULATION AMENDMENT NO. 279 TO RENEWED FACILITY OPERATING LICENSE NO. DPR-57 AND AMENDMENT NO. 223 TO RENEWED FACILITY OPERATING LICENSE NO. NPF-5 SOUTHERN NUCLEAR OPERATING COMPANY. INC.
EDWIN I. HATCH NUCLEAR PLANT. UNIT NOS. 1 AND 2 DOCKET NOS. 50-321 AND 50-366
1.0 INTRODUCTION
By application dated October 10, 2014 (Agencywide Documents Access and Management System (ADAMS) Accession No. ML14288A226), as supplemented by letters dated May 4, 2015, October 15, 2015, and August 26, 2016 (ADAMS Accession Nos. ML16116A201, ML15288A232, and ML16239A309, respectively), Southern Nuclear Operating Company, Inc.
(SNC, the licensee), requested changes to the Technical Specifications (TSs) for the Edwin I.
Hatch Nuclear Plant (HNP), Unit Nos. 1 and 2. The proposed changes would incorporate 21 generic changes to the HNP TSs. Specifically, SNC requests to adopt 18 previously U.S.
Nuclear Regulatory Commission (NRC)-approved Technical Specifications Task Force (TSTF) travelers, two TSTF T-travelers, and one feature of NUREG-1433, Revision 4, "Standard Technical Specifications - General Electric BWR/4 Plants" (ADAMS Accession Nos.
ML12104A192 and ML12104A193), known as the Improved Standard Technical Specifications (ISTS) not associated with a traveler. SNC stated that these changes would increase the consistency between the HNP TSs, the ISTS for boiling water reactor (BWR)/4 plants, and the TSs of the other plants in the SNC fleet. The proposed changes are listed below.
The requested TSTFs for NRC approval are:
- 1. TSTF-30-A, Revision 3, "Extend the Completion Time for inoperable isolation valve to a closed system to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />"
- 2. TSTF-45-A, Revision 2, "Exempt verification of CIVs [containment isolation valves] that are not locked, sealed or otherwise secured"
- 3. TSTF-46-A, Revision 1, "Clarify the CIV surveillance to apply only to automatic isolation valves"
- 4. TSTF-222-A, Revision 1, "Control Rod Scram Time Testing (BWR)"
Enclosure 3
- 5. TSTF-264-A, Revision 0, "3.3.9 and 3.3.10 - Delete flux monitors specific overlap requirement SRs [surveillance requirements)"
- 6. TSTF-269-A, Revision 2, "Allow administrative means of position verification for locked or sealed valves"
- 7. TSTF-273-A, Revision 2, "SFDP [Safety Function Determination Program] Clarifications"
- 8. TSTF-283-A, Revision 3, "Modify Section 3.8 Mode restriction Notes"
- 9. TSTF-284-A, Revision 3, "Add 'Met vs. Perform' to Specification 1.4, Frequency"
- 10. TSTF-295-A, Revision 0, "Modify Note 2 to Actions of PAM [Post-Accident Monitoring]
Table to Allow Separate Condition Entry for Each Penetration"
- 11. TSTF-306-A, Revision 2, "Add Action to LCO [Limiting Condition for Operation] 3.3.6.1 to give option to isolate the penetration"
- 12. TSTF-308-A, Revision 1, "Determination of Cumulative and Projected Dose Contributions in RECP [Radioactive Effluent Controls Program)"
- 13. TSTF-318-A, Revision 0, "Revise 3.5.1 for one LPCI [low pressure coolant injection]
pump inoperable in each of two ECCS [emergency core cooling system] divisions"
- 14. TSTF-322-A, Revision 2, "Secondary Containment and Shield Building Boundary Integrity SRs"
- 15. TSTF-323-A, Revision 0, "EFCV [Excess Flow Check Valve] Completion Time to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />"
- 17. TSTF-400-A, Revision 1, "Clarify SR on Bypass of DG [Diesel Generator] Automatic Trips"
- 18. TSTF-439-A, Revision 2, "Eliminate Second Completion Times Limiting Time From Discovery of Failure To Meet an LCO" T-travelers are travelers that have not been approved by the NRC staff, but have been approved by the TSTF. The following T-travelers are being requested for NRC approval:
- 19. TSTF-458-T, Revision 0, "Removing Restart of Shutdown Clock for Increasing Suppression Pool Temperature"
- 20. TSTF-464-T, Revision 0, "Clarify the Control Rod Block Instrumentation Required Action"
In addition, SNC requested one change for NRC approval that reflects ISTS requirements that were not added by a traveler:
- 21. ISTS Adoption #1 - Revise the 5.5.7 Introductory Paragraph to be Consistent with the ISTS The supplements dated May 4, 2015, October 15, 2015, and August 26, 2016, provided additional information that clarified the application, did not expand the scope of the application as originally noticed, and did not change the NRC staff's original proposed no significant hazards consideration determination as published the Federal Register on March 31, 2015 (80 FR 17095; July 19, 1995).
2.0 REGULATORY EVALUATION
Title 10 of the Code of Federal Regulations (10 CFR) Section 50.36, "Technical specifications,"
requires TSs for nuclear reactors to include items in the following categories: (1) safety limits, limiting safety system settings, and limiting control settings; (2) LCOs; (3) SRs; (4) design features; and (5) administrative controls. The regulation does not specify the particular requirements to be included in a plant's TSs.
On July 22, 1993, the Commission published the "Final Policy Statement on Technical Specifications Improvements for Nuclear Power Reactors" (58 FR 39132). This Final Policy Statement discussed criteria for determining which items must be included in the TS as LCOs.
These criteria were subsequently incorporated into 1O CFR 50.36 (60 FR 36953). Specifically, 10 CFR 50.36(c)(2)(ii) requires that an LCO be established for each item meeting one or more of the following criteria:
Criterion 1: Installed instrumentation that is used to detect, and indicate in the control room, a significant abnormal degradation of the reactor coolant pressure boundary.
Criterion 2: A process variable, design feature, or operating restriction that is an initial condition of a design basis accident or transient analysis that either assumes the failure of or presents a challenge to the integrity of a fission product barrier.
Criterion 3: A structure, system, or component that is part of the primary success path and which functions or actuates to mitigate a design basis accident or transient that either assumes the failure of or presents a challenge to the integrity of a fission product barrier.
Criterion 4: A structure, system, or component which operating experience or probabilistic risk assessment has shown to be significant to public health and safety.
In determining the acceptability of TS changes, the NRC staff considers the requirements of 1O CFR 50.36 using the guidance in the ISTS and the associated Bases for the safety limits and LCOs, and the references cited in the Bases. As discussed in the Final Policy Statement, the NRC staff reviews, on a case-by-case basis, whether enforceable regulatory controls (e.g.,
10 CFR 50.59) are needed for material moved to licensee-controlled documents, such as the updated safety analysis report, the Technical Requirements Manual, the TS Bases, the Quality Assurance Plan, etc. The NRC staff determines that plant-specific adoptions of ISTS format and content provide continued, adequate protection for the public health and safety when (1) the change is editorial, administrative, or provides clarification (i.e., no requirements are materially altered); (2) the change is more restrictive than the licensee's current requirement; or (3) the change is less restrictive than the licensee's current requirement, but nonetheless still affords adequate assurance of safety when judged against current regulatory standards and the facility's licensing basis.
The NRC staff used the ISTS, Revision 4, issued in April 2012, in its review of the TS changes proposed by SNC. The NRC staff also referred to the TSTF travelers associated with the ISTS changes proposed for adoption by SNC. The NRC staff notes that in September 1992, the Commission issued the ISTSs (NUREG-1430 through NUREG-1434), which were developed using the guidance and criteria contained in the Commission's Final Policy Statement (58 FR 39132). In the current revisions of NUREG-1430 through NUREG-1434, the word "improved" has been dropped from the titles, therefore, throughout the rest of this safety evaluation, standard technical specifications (STS) is used in place of ISTS for consistency, except when it is contained in a document's title.
3.0 TECHNICAL EVALUATION
3.1 TSTF-30-A. Revision 3, "Extend the Completion Time for inoperable isolation valve to a closed system to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />" TSTF-323-A. Revision 0. "Excess Flow Check Valve (EFCV) Completion Time to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />" TSTF-30-A, Revision 3, revised BWR STS 3.6.1.3, "Primary Containment Isolation Valves (PCIVs)," Actions Condition C, "One or more penetration flow paths with one PCIV [primary containment isolation valve] inoperable," which is only applicable to penetration flow paths with one PCIV. Specifically, TSTF-30-A, Revision 3, revised the Completion Times for Required Action C.1 to allow 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />, instead of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />, to isolate an inoperable PCIV in a closed system.
TSTF-323-A, Revision 0, extended the Completion Time to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for inoperable CIVs where there was only a single valve on the containment penetration. This was in recognition that these penetrations were designed with some other acceptable barrier (e.g., closed system). The NRC's approval of TSTF-323, Revision 0, preceded the NRC's approval of TSTF-30, Revision 3, since TSTF-323-A was approved in March of 1999, whereas TSTF-30-A was approved by the NRC in a letter dated August 16, 1999. As a result, approval of the TSTS-323-A, Revision 0, change preceded approval of, and was subsumed assumed, in the final version (Revision 3) of TSTF-30.
HNP TS LCO 3.6.1.3, Condition C, is applicable to penetration flow paths with only one PCIV.
With one or more penetration flow paths with one PCIV inoperable, except due to leakage not within limits, Required Action C.1 requires isolation of the affected penetration flow path by use of at least one closed and deactivated automatic valve, closed manual valve, or blind flange.
Current Completion Time for Required Action C.1 of HNP TS 3.6.1.3 states:
4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> except for excess flow check valve (EFCV) line, 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> for EFCV line Revised Required Action C.1 Completion Time of HNP TS 3.6.1.3 would state:
4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> except for excess flow check valve (EFCV) and penetrations with a closed system 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for EFCV line and penetrations with a closed system
NRC Staff Evaluation
In the supplement dated May 4, 2015, the licensee provided clarification on the scope of Required Action C.1 where a Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> would be retained for penetrations with only one PCIV that is not associated with a closed system or an EFCV. Specifically, the licensee provided examples of penetrations that are covered under 10 CFR Part 50, Appendix A, General Design Criterion 56, "Primary Containment Isolation," in both HNP, Units 1 and 2 (e.g., drywell pressure instrument, torus water level instrument, and traversing in-core probe nitrogen purge line). The licensee also stated that these allowed configurations are consistent with guidance in Regulatory Guide (RG) 1.11, "Instrument Lines Penetrating the Primary Reactor Containment" (ADAMS Accession No. ML100250396).
The NRC staff reviewed the referenced RG 1.11 and HNP, Unit No. 1, Final Safety Analysis Report (FSAR), Subsection 5.2.2.5.4, and HNP, Unit No. 2, FSAR Subsection 6.2.5.3.3, and found that the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> is applicable in these cases. The changes proposed for corresponding PCIV and EFCV action requirements in TS 3.6.1.3 conform to the changes made to the STS by TSTF-30-A, Revision 3, and TSTF-323-A, Revision 0. The BWR/4 design (such as the HNP design) includes a class of single-isolation valve penetrations (i.e.,
instrumentation lines with an EFCV) that were inadvertently not included in the markup for TSTF-30, Revision 2. That approved traveler extended the Completion Time to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for inoperable PCIVs in containment penetration flow paths with just one PCIV. The NRC staff has determined that these single-PCIV penetrations used in closed systems provide an acceptable second barrier. Similarly, a Completion Time of 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for inoperable EFCVs is acceptable because EFCVs are installed on penetrations that provide acceptable barriers in the event that the single isolation valve failed.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to TS 3.6.1.3 are acceptable.
3.2 TSTF-45-A. Revision 2, "Exempt verification of CIVs that are not locked. sealed or otherwise secured" The NRC approved this change to the STS Revision 1 on July 26, 1999. TSTF-45-A, Revision 2, revised BWR/4 STS 3.6.1.3, "Primary Containment Isolation Valves (PCIVs)," and STS 3.6.4.2, "Secondary Containment Isolation Valves (SCIVs)," by changing valve position verification SRs.
Current TS SR 3.6.1.3.2 states:
Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and is required to be closed during accident conditions is closed.
Revised TS SR 3.6.1.3.2 would state (with the inserted portion in bold):
Verify each primary containment isolation manual valve and blind flange that is located outside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed.
Current TS SR 3.6.1.3.3 states:
Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and is required to be closed during accident conditions is closed.
Revised TS SR 3.6.1.3.3 would state (with the inserted portion in bold):
Verify each primary containment manual isolation valve and blind flange that is located inside primary containment and not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed.
Current TS SR 3.6.4.2.1 states:
Verify each secondary containment isolation manual valve and blind flange that is required to be closed during accident conditions is closed.
Revised TS SR 3.6.4.2.1 would state (with the inserted portion in bold):
Verify each secondary containment isolation manual valve and blind flange that is not locked, sealed, or otherwise secured and is required to be closed during accident conditions is closed.
NRC Staff Evaluation
TSTF-45-A states that the proposed change is consistent with the valve position verification requirement for valves that have a function during an accident in other system TSs. The NRC staff reviewed the proposed changes and determined they are consistent with current HNP SR 3.5.1.2, which requires that each ECCS subsystem be demonstrated operable, in part, by performance of a valve alignment of each valve that is in the flow path that is not locked, sealed, or otherwise secured valves. Multiple HNP systems, such as the reactor core isolation cooling system and the residual heat removal suppression pool cooling system, spray, and drywell spray, are also demonstrated to be operable, in part, by verifying that each valve in the flow path of the system that is not locked, sealed, or otherwise secured in position, is in its correct position (SRs 3.6.2.3.1, 3.6.2.4.1, 3.6.2.5.1, and 3.6.3.1.2, respectively). Additionally, the changes proposed for HNP TS SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are the same as those contained in TSTF-45-A.
The NRC staff concludes that excluding locked, sealed, or otherwise secured valves from periodic position verification is acceptable because these valves were verified to be in the correct position upon being locked, sealed, or otherwise secured. The position of these valves is controlled administratively, and periodic visual verification is not necessary.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes that the changes to SRs 3.6.1.3.2, 3.6.1.3.1, and 3.6.4.2.1 are acceptable.
3.3 TSTF-46-A. Revision 1. "Clarify the CIV surveillance to apply only to automatic isolation valves" The NRC did not issue a letter approving this change to STS, Revision 1; however, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-46-A revises STS SR 3.6.3.5 to delete the reference to verifying the isolation time of "each power operated" CIV and only require verification of each "automatic isolation valve."
Current TS SR 3.6.1.3.5 states:
Verify the isolation time of each power operated and each automatic PCIV, except for MSIVs, is within limits.
Revised TS SR 3.6.1.3.5 would state (with the removed portion in strikeout and additions in bold):
Verify the isolation time of each pmver operated and each power operated, automatic PCIV, except for MSIVs, is within limits.
Current TS SR 3.6.4.2.2 states:
Verify the isolation time of each power operated and each automatic SCIV is within limits.
Revised TS SR 3.6.4.2.2 would state (with the removed portion in strikeout):
Verify the isolation time of each power operated, and each automatic SCIV is within limits.
NRC Staff Evaluation
The original wording states that the surveillance applied to power operated or automatic containment isolation valves, which could result in an interpretation that power operated valves that do not receive an automatic closure signal for design-basis events are also required to have a closure time associated with them. These changes removed the unintended requirement to verify isolation times of non-automatic power operated CIVs.
The changes proposed for the corresponding CIV SRs in HNP TS 3.6.1.3 and TS 3.6.4.2 are the same as those contained in TSTF-46-A. The NRC staff has determined that these changes only clarify the intended scope of CIVs covered by the existing surveillances and are, therefore, administrative in nature. Because the current scope of these surveillances has not changed, there is no impact to safety.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes that the proposed changes to SRs 3.6.1.3 and 3.6.4.2 are acceptable.
3.4 TSTF-222-A, Revision 1. "Control Rod Scram Time Testing" TSTF-222-A revised BWR STS 3.1.4, "Control Rod Scram Times." TS 3.1.4, "Control Rod Scram Times," SRs 3.1.4.1 and 3.1.4.4, are revised to only require scram time testing of control rods that are in an affected core cell.
Current TS SR 3.1.4.1 has a Frequency of:
Prior to exceeding 40% RTP [rated thermal power] after fuel movement within the reactor vessel Prior to exceeding 40% RTP after each reactor shutdown ~ 120 days
TS SR 3.1.4.4 has a Frequency of:
Prior to exceeding 40% RTP after work on control rod or CRD [control rode drive]
System that could affect scram time TS SRs 3.1.4.1 and 3.1.4.4 are revised, which deletes the Frequency shown in bold text above from SR 3.1.4.1, and adds a new Frequency as shown in bold text below to SR 3.1.4.4 with an AND statement:
Prior to exceeding 40% RTP after fuel movement within the affected core cell.
Prior to exceeding 40% RTP after work on control rod or CRD System that could affect scram time.
NRC Staff Evaluation
The changes to SR 3.1.4.1 and SR 3.1.4.4 result in only the affected control rod requiring testing after fuel movement. If a control rod is not affected by fuel movement, there is no basis for expecting that the control rod will perform differently than during the previous scram time test. The NRC staff has determined that these changes only clarify the intent of the existing requirements and do not reduce the testing currently required for demonstrating control rod operability. Therefore, there is no impact to safety since control rod scram time testing will be performed following any fuel movement that could affect the scram time.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes that the proposed changes to SR 3.1.4.1 and 3.1.4.4 are acceptable.
3.5 TSTF-264-A, Revision 0, "3.3.9 and 3.3.10 - Delete flux monitors specific overlap requirement SRs" TSTF-264-A was submitted to the NRC on May 9, 1998; approved on July 26, 1999; and incorporated into Revision 2 of NUREG-1433, "Standard Technical Specifications - General Electric Plants (BWR/4)," which was published on June 30, 2001. Revision 4 of NUREG-1433 contains many improvements over STS Revision 0, which was issued in 1992. One objective of these improvements was to make TS requirements in the five STS NUREGs consistent for systems that perform essentially the same functions, where possible. Such an improvement was approved by the NRC in TSTF-264-A.
3.5.1 Current HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification TS 3.3.1.1, "Reactor Protection System (RPS) Instrumentation," SRs 3.3.1.1.6 and 3.3.1.1.7, require verification of overlap for the source range (neutron flux) monitor (SRM) and intermediate range (neutron flux) monitor (IRM) indications, and for the IRM and average power range (neutron flux) monitor (APRM) indications, respectively. The Bases for these SRs explain what constitutes acceptable overlap in each case and state, in part, that:
Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block. Overlap between the SRMs and IRMs similarly exists when, prior to withdrawing an SRM from the fully inserted position, its associated IRMs have cleared their downscale rod block Allowable Values, prior to the SRM having reached its upscale rod block Allowable Value.
The Frequency of SR 3.3.1.1.6 (IRM-SRM overlap verification) is, "Prior to withdrawing SRMs from the fully inserted position." The surveillance column note in SR 3.3.1.1.7 (APRM-IRM overlap verification) states, "Only required to be met during entry into MODE 2 from MODE 1."
The Frequency of SR 3.3.1.1.7 is, "In accordance with the Surveillance Frequency Control Program."
SR 3.3.1.1.1 requires a channel check of IRM and APRM channels in accordance with the surveillance frequency control program (SFCP).
As specified in TS Table 3.3.1.1-1, in Mode 2, SR 3.3.1.1.6 applies to RPS Function 1.a, IRM Neutron Flux - High, and SR 3.3.1.1.7 applies to RPS Function 1.a, and Function 2.a, APRM Neutron Flux - High (Setdown). In addition, SR 3.3.1.1.1 applies to both Function 1.a and Function 2.a 3.5.2 Proposed HNP TS Requirements for Nuclear Instrumentation Neutron Flux Indication Overlap Verification The proposed change revises HNP TS 3.3.1.1, "RPS Instrumentation," by deleting SR 3.3.1.1.6 and SR 3.3.1.1.7, which verify the SRM-IRM neutron flux indication overlap and the IRM-APRM neutron flux indication overlap, respectively. TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7.
Current TS SR 3.3.1.1.6 states:
Verify the source range monitor (SRM) and intermediate range monitor (IRM) channels overlap.
Revised TS SR 3.3.1.1.6 would state:
(Not used.)
Current TS SR 3.3.1.1. 7 states:
N()TE:------------------------------
()nly required to be met during entry into M()DE: 2 from M()DE: 1.
Verify the IRM and APRM channels overlap.
Revised TS SR 3.3.1.1.7 would state:
(Not used.)
A Channel Check is currently required for Functions 1.a and 2.a with a Frequency of "In accordance with the Surveillance Frequency Control Program." HNP TS Section 1.1 defines a Channel Check as follows (the same as the STS definition):
A CHANNE:L CHE:CK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter.
TSTF-264-A did not propose changes to this definition in the STS because it may be interpreted as requiring SRM-IRM and IRM-APRM neutron flux indication overlap verification for the IRM-and APRM-associated RPS Functions that are required to be operable in Mode 2 (i.e.,
Functions 1.a and 2.a). With this interpretation, the present indication overlap verifications may be considered redundant to the channel check SR SNC stated that it will relocate the existing discussions of the SR 3.3.1.1.6 and SR 3.3.1.1.7 overlap verification requirements from the existing Bases to the Bases for SR 3. 3.1.1.1.
Specifically, the licensee plans to add the following paragraph to SR 3.3.1.1.1 Bases:
The agreement criteria includes an expectation of one decade of overlap when transitioning between neutron flux instrumentation. The overlap between SRMs and IRMs must be demonstrated prior to withdrawing SRMs from the fully inserted position since indication is being transitioned from the SRMs to the IRMs. This will ensure that reactor power will not be increased into a neutron flux
region without adequate indication. The overlap between IRMs and APRMs is of concern when reducing power into the IRM range (entry into MODE 2 from MODE 1). On power increases, the system design will prevent further increases (by initiating a rod block) if adequate overlap is not maintained. Overlap between IRMs and APRMs exists when sufficient IRMs and APRMs concurrently have onscale readings such that the transition between MODE 1 and MODE 2 can be made without either APRM downscale rod block, or IRM upscale rod block.
Overlap between SRMs and IRMs similarly exists when, prior to withdrawing the SRMs from the fully inserted position, IRMs are above mid-scale on range 1 before SRMs have reached the upscale rod block.
If overlap for a group of channels is not demonstrated (e.g., IRM/APRM overlap),
the reason for the failure of the Surveillance should be determined and the appropriate channel(s) declared inoperable. Only those appropriate channels that are required in the current MODE or condition should be declared inoperable.
NRC Staff Evaluation
In adopting TSTF-264-A, the HNP TS 3.3.1.1 retains the surveillance number designators but replaces the surveillance statement and any associated surveillance note with the phrase "(Not used.)" and leaves the frequency column blank in the SRs table rows for existing SR 3.3.1.1.6 and SR 3.3.1.1.7. This is in lieu of removing these rows and renumbering the existing subsequent SRs, as done in the traveler's markup of NUREG-1433, Revision 1. In addition, the references to these SRs in HNP TS Table 3.3.1.1-1 are removed. References to SR 3.3.1.1.6 and SR 3.3.1.1.7 in the Bases for HNP TS 3.3.1.2, "SRM Instrumentation," will be replaced by references to SR 3.3.1.1.1. No changes were needed to HNP TS 3.3.1.2 requirements on SRM channel operability, actions, or surveillances in Mode 2 with IRMs on Range 2 or below.
SNC stated that it would maintain the existing neutron flux monitor channel indication overlap criteria by relocating the discussion of the criteria to the Bases for HNP TS SR 3.3.1.1.1 for RPS Functions 1.a and 2.a. The overlap check will be performed when SR 3.3.1.1.1 is performed for RPS Functions 1.a and 2.a. Although the TS Bases are a licensee-controlled document, changes to the TS Bases are controlled by the 10 CFR 50.59 process. The NRC staff finds that the licensee continues to uphold the previously approved definition of overlap and will maintain compliance with the requirement to verify SRM-IRM and IRM-APRM indication overlap at the necessary ranges of reactor power by performing the channel check specified for TS 3.3.1.1 Functions 1.a and 2.a at the Frequencies stated in the SFCP.
The NRC staff has determined that the proposed changes are in accordance with NRC-approved TSTF-264, Revision 0, with no technical deviations, are consistent with STS Revision 4.0, and the overlap check will still be performed during surveillance testing.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes the proposed changes to SR 3.3.1.1.6, SR 3.3.1.1.7, and Table 3.3.1.1 1 of HNP TS 3.3.1.1 to be acceptable.
3.6 TSTF-269-A. Revision 2. "Allow administrative means of position verification for locked or sealed valves" The NRC approved this change to STS Revision 1 on July 27, 1999. TSTF-269-A revised STS 3.6.1.3, "Primary Containment Isolation Valves," and 3.6.4.2, "Secondary Containment Isolation Valves," by adding a note that isolation devices that are locked, sealed, or otherwise secured may be verified by use of administrative means.
Current TS 3.6.1.3, Required Action C.2 for Condition C, "One or more penetration flow paths with one PCIV inoperable except due to leakage not within limit," requires:
Verify the affected penetration flow path is isolated.
With a Frequency of:
Once per 31 days Current TS 3.6.4.2, Required Action A.2 for Condition A, "One or more penetration flow paths with one SCIV inoperable," requires:
Verify the affected penetration flow path is isolated.
With a Frequency of:
Once per 31 days.
Revised TS 3.6.1.3 and TS 3.6.4.2 would add the following NOTE in the subject Required Actions C.2 and A.2, respectively.
Isolation devices that are locked, sealed, or otherwise secured may be verified by administrative means.
NRC Staff Evaluation
The NRC staff has reviewed the proposed changes to TS 3.6.1.3 and TS 3.6.4.2 and has determined that administrative controls for such isolation valves have proven to be adequate to ensure the valves are maintained in the positions required by the plant safety analyses when primary and secondary containment are required to be operable. The licensee did not propose a change to Action E since HNP TSs do not contain an equivalent in STS 3.6.1.3. The NRC staff has determined that this is acceptable because TSTF-269-A modification of STS 3.6.1.3 was marked as optional for licensees and HNP TS 3.6.1.3 Action E contains the shutdown
requirements in the instance when Required Actions and associated Completion Times of Conditions A, B, C, and D are not met.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to TS 3.6.1.3 and TS 3.6.4.2 are acceptable.
- 3. 7 TSTF-273-A, Revision 2, "SFDP [Safety Function Determination Program] Clarifications" The NRC approved TSTF-273-A, Revision 2, to STS Revision 1, as documented in a letter from William Beckner, NRC, to James Davis, Nuclear Energy Institute (NEI), dated August 16, 1999 (ADAMS Accession No. ML16237A031). TSTF-273-A modified STS 5.5.12, "Safety Function Determination Program (SFDP)," which implements the requirements of LCO 3.0.6. HNP TS 5.5.10, "Safety Function Determination Program (SFDP)," is similar to STS 5.5.12 and contains the following paragraphs:
A loss of safety function exists when, assuming no concurrent single failure, a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable.
and The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
The proposed change adds the following statements (shown in bold) in those paragraphs:
A loss of safety function exists when, assuming no concurrent single failure, no concurrent loss of offsite power or no concurrent loss of onsite diesel generator(s), a safety function assumed in the accident analysis cannot be performed. For the purpose of this program, a loss of safety function may exist when a support system is inoperable.
and The SFDP identifies where a loss of safety function exists. If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered. When a loss of safety function is caused by the inoperability of a single Technical Specification support system, the
appropriate Conditions and Required Actions to enter are those of the support system.
NRC Staff Evaluation
SNC proposed to revise TS 5.5.10 by incorporating TSTF-273-A, Revision 2, changes without deviations. The changes to TS 5.5.10, and the Bases for LCO 3.0.6, are intended to clarify the intent of LCO 3.0.6 in the event a single inoperable TS support system makes both redundant subsystems of a supported system inoperable (a loss of safety function condition). The STS were developed such that the LCO actions for a single support system inoperability would be addressed by that support system's actions, without cascading to the supported system's LCO actions. LCO 3.0.6 establishes this exception to LCO 3.0.2 for support systems that have an LCO specified in the TSs. However, LCO 3.0.6 also requires an evaluation under the SFDP to ensure that a loss of safety function does not exist.
The NRC staff concludes that these changes do not affect the design, operation, or maintenance of HNP, but only provide clarity for determining when a loss of safety function condition exists and what LCO actions are required to be taken when a safety function is lost.
By clarifying the intent of the existing requirements of the SFDP and LCO 3.0.6, these changes remove an ambiguity that could lead to a misinterpretation of those requirements.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to TS 5.5.10 are acceptable.
3.8 TSTF-283-A. Revision 3, "Modify Section 3.8 Mode restriction Notes" TSTF-283-A revised certain SR notes in BWR/4 STS 3.8.1, "AC Sources Operating," and 3.8.4, "DC Sources Operating," to allow full or partial performance of the SRs in the prohibited Modes to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced.
The revised surveillances (SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8) currently have notes prohibiting their performance in Modes 1 or 2, or in Modes 1, 2, or 3. The notes are modified to state that while normally prohibited "in Modes 1 or 2," or "in Modes 1, 2, or 3," the surveillance may be performed to reestablish operability, provided an assessment determines the safety of the plant is maintained or enhanced.
- Current TS SR 3.8.1.6 NOTE states, in part, that:
This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold) in part, that:
This Surveillance shall not normally be performed in MODE 1 or 2.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR
- Current TS SR 3.8.1.7 NOTE 1 states, in part, that:
This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR
- Current TS SR 3.8.1.8 NOTE 1 states, in part, that:
This Surveillance shall not be performed in MODE 1 or 2, except for the swing DG. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold):
This Surveillance shall not normally be performed in MODE 1 or 2, except for the swing DG. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. For the swing DG, this Surveillance shall not be performed in MODE 1 or 2 using the Unit [1 or 2]* controls. Credit may be taken for unplanned events that satisfy this SR
- Current TS SR 3.8.1.9 NOTE 2 states, in part, that:
This Surveillance shall not be performed in MODE 1, 2 or 3. However, credit may be taken for unplanned events that satisfy this SR
The revised NOTE would state (with the added text in bold) in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.10 NOTE 2 states, in part, that:
This Surveillance shall not be performed in MODE 1 or 2. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1 or 2.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.11 NOTE states, in part, that:
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.12 NOTE 2 states, in part, that:
This Surveillance shall not be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. If either of the other two DGs becomes inoperable, this surveillance shall be suspended. Credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1 or 2, unless the other two DGs are OPERABLE. However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or
enhanced. If either of the other two DGs becomes inoperable, this surveillance shall be suspended. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.14 NOTE states, in part, that:
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.15 NOTE states, in part, that:
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.16 NOTE states, in part, that:
This Surveillance shall not be performed in MODE 1. 2, or 3. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, this surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.1.17 NOTE 2 states, in part, that:
This Surveillance shall not be performed in MODE 1, 2, or 3. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold), in part, that:
This Surveillance shall not normally be performed in MODE 1, 2, or 3.
However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.4.7 NOTE 2 states:
This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold):
This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- Current TS SR 3.8.4.8 NOTE states:
This Surveillance shall not be performed in MODE 1, 2, or 3, except for the swing DG battery. However, credit may be taken for unplanned events that satisfy this SR.
The revised NOTE would state (with the added text in bold):
This Surveillance shall not normally be performed in MODE 1, 2, or 3 except for the swing DG battery. However, portions of the surveillance may be performed to reestablish OPERABILITY provided an assessment determines the safety of the plant is maintained or enhanced. Credit may be taken for unplanned events that satisfy this SR.
- - As appropriate per unit (i.e., 1 for Unit No. 1 or 2 for Unit No. 2)
Deviation from TSTF-283-A:
The licensee explained a deviation between the proposed changes and the approved traveler for SR 3.8.4.6 as follows:
The Hatch Unit 1 and 2 SR 3.8.4.6 does not contain the Note that is modified, so the changes are therefore not applicable to these Hatch SRs.
NRC Staff Evaluation
Initially, when the NRC staff reviewed the proposed changes to the SR notes for HNP, Unit Nos. 1 and 2, some mismatches in the application of the changes were identified when compared to TSTF-283-A, Revision 3. Consequently, the licensee corrected these mismatches in the May 4, 2015, supplement.
The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS in NUREG-1433 for BWR/4 plants issued in June 30, 2001. The intent of the TSTF is to allow testing of the emergency diesel generators (EDGs) and Class 1E batteries in modes not currently allowed for the purpose of maintaining or reestablishing system or component operability (e.g., post-corrective maintenance testing), provided the licensee performs a safety assessment, as described in the application, that determines the safety of the plant would be maintained or enhanced by conducting the operability testing before the testing begins.
The NRC staff reviewed the proposed changes to SR notes in TS 3.8.1 for the alternating current (AC) electrical power sources and TS 3.8.4 for the direct current (DC) electrical power sources and has determined they would provide flexibility in outage scheduling and reduce outage critical path time, since these EDGs and battery surveillance tests would no longer have to be performed during an outage. In addition, the changes will potentially allow avoiding a plant shutdown if corrective maintenance (planned or unplanned) performed during power operation results in the need to perform any of the above surveillances to demonstrate operability. The change will also improve the licensee's flexibility in responding to an event during shutdown when other engineered safety feature (ESF) equipment may be out of service.
The NRC staff reviewed the licensee's justification for the deviation for SR 3.8.4.6 and concludes the justification to be acceptable because the applicable note does not exist in the current SR 3.8.4.6.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(3) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to SRs 3.8.1.6, 3.8.1.7, 3.8.1.8, 3.8.1.9, 3.8.1.10, 3.8.1.11, 3.8.1.12, 3.8.1.14, 3.8.1.15, 3.8.1.16, 3.8.1.17, 3.8.4.7, and 3.8.4.8 are acceptable.
3.9 TSTF-284-A. Revision 3, "Add 'Met vs. Perform' to Specification 1.4, Frequency" TSTF-284-A, Revision 3, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). The change inserts a discussion paragraph into TS 1.4, and several new examples are added to facilitate the use and application of SR notes that utilize the terms "met"
and "perform." The changes also modify certain SRs to appropriately use the "met" and "perform" exceptions.
- Current TS 1.4 "Frequency," the third paragraph states:
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4-4 discusses these special situations.
Revised TS 1.4 "Frequency," the third paragraph would state (with the deleted section shown in strikethrough):
Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both. Example 1.4 4 discusses these special situations.
Current TS 1.4 "Frequency," the fifth paragraph states:
The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria.
SR 3.0.4 restrictions would not apply if both the following conditions are satisfied.
- a. The Surveillance is not required to be performed; and
- b. The Surveillance is not required to be met or, even if required to be met, is known not to be failed.
Revised TS 1.4 "Frequency," the fifth paragraph would state (with the added text in bold and the deleted text in strikethrough):
The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria. SR 3.0.4 restrictions would not apply if both the following conditions are satisfied.
- c. The Surveillance is not required to be performed, and
- d. The Surveillance is required to be met or, even if it is required to be met, is known not to be failed.
Some Surveillances contain notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:
- a. The Surveillance is not required to be met in the MODE or other specified condition to be entered; or
- b. The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or
- c. The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.
Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.
TS 1.4, "Frequency," currently includes examples up through Example 1.4-4 regarding the Frequency Based on a Specified Condition. The proposed change would also add Examples 1.4-5 and 1.4-6.
EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N()TE--------------------------------
()nly required to be performed in M()DE 1. 7 days
Perform complete cvcle of the valve.
The interval continues, whether or not the unit operation is in M()DE 1, 2, or 3 (the assumed Applicability of the associated LC()) between performances.
As the note modifies the required performance of the Surveillance, the note is construed to be part of the "specified Frequency." Should the 7 day interval be
exceeded while operation is not in MODE 1, this note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day frequency not met, provided operation does not result in entry into MODE 1.
Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.
EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY
N 0 TE--------------------------------
Not required to be met in MODE 3. 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />
Verify parameter is within limits.
Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO.
Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.
NRC Staff Evaluation
The change in TSTF-284-A, Revision 3, is to modify ISTSs, Section 1.4, "Frequency," and to clarify the usage of the terms "met" and "performed" in order to facilitate the application of SR notes. Two new SR Examples, 1.4-5 and 1.4-6, are added to illustrate the application of the terms.
STS Section 1.4, "Frequency," defines the proper use and application of SR frequency requirements in the STS format. It states that, "An understanding of the correct application of the specified frequency is necessary for compliance with the SR." It also establishes that, "The specified frequency consists of the requirements of the frequency column of each SR as well as certain NOTES in the Surveillance column that modify performance requirements." The purpose of TSTF-284, Revision 3, was to clarify and make consistent the use of notes in the surveillance column that modify frequency requirements.
In adopting TSTF-284, Revision 3, a licensee must verify that NOTES such as those illustrated by these four examples are used properly and only as necessary. This includes ensuring the associated Bases are also correct. Proper application of these NOTES in the individual SRs in the NUREGs was verified. The staff has determined that the proposed changes and HNP adoption of the TSTF changes conforms to the guidance provided in NUREG-1433. These changes are administrative in nature because they only serve to clarify the meaning of the terms "met" and "performed" as used in SR notes throughout the HNP TSs. This change serves to improve TS usefulness by clarifying terminology usage and providing additional examples of the application of SR notes.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the proposed changes to TS 1.4 are acceptable.
3.10 TSTF-295-A, Revision 0, "Modify Note 2 to Actions of PAM [Post-Accident Monitoring]
Table to Allow Separate Condition Entrv for Each Penetration" The NRC approved this change to STS Revision 1 on December 21, 1999. TSTF-295-A revised Table 3.3.3.1-1 of STS 3.3.3.1, "Post Accident Monitoring (PAM) Instrumentation," by (1) prefacing the title of Function 8, "Primary Containment Isolation Valve (PCIV) Position," with the phrase "Penetration Flow Path," and (2) prefacing the title of Function 13, "Suppression Pool Water Temperature," with "Relief Valve Discharge Location." These changes were made to clarify how to apply the actions note to these two functions. The actions note states, "Separate Condition entry is allowed for each Function." The changes clarify that separate condition entry is allowed for each penetration flow path for the PAM PCIV position indication function and for each relief valve discharge location suppression pool temperature indication.
The change proposed for corresponding HNP TS 3.3.3.1, Function 6, "Primary Containment Isolation Valve Position," is the same as the changes made to the STS by TSTF-295-A. The licensee did not propose a change to TS 3.3.3.1, Function 9, "Suppression Pool Water Temperature," because of its plant-specific system design as explained by the licensee in its application.
Current TS Table 3.3.3.1-1, Function 6, states:
Primary Containment Isolation Valve Position
Revised TS Table 3.3.3.1-1, Function 6, would state:
Penetration Flow Path Primary Containment Isolation Valve Position
NRC Staff Evaluation
The NRC staff has determined that this change is administrative because it only clarifies the intended application of action requirements for inoperable channels of HNP TS 3.3.3.1 Function 6 and is consistent with the TS action requirements for PCIVs. This change does not reduce any existing action requirements for these PAM functions and does not affect plant safety.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes the proposed change to TS Table 3.3.3.1-1 to be acceptable.
3.11 TSTF-306-A. Revision 2, "Add Action to LCO 3.3.6.1 to give option to isolate the penetration" The NRC approved this change to STS Revision 1 on July 13, 2000. TSTF-306-A revised STS 3.3.6.1, "Primary Containment Isolation Instrumentation," by changing the requirements for the two Traversing In-core Probe (TIP) containment isolation instrumentation functions.
Specifically, TSTF-306-A would add functions for TIP system isolation (7.a and 7.b) to STS Table 3.3.6.1-1. Previously, these functions had been included under Primary Containment Isolation Functions 2.a, "Reactor Vessel Water Level - Low Level 3," and 2.b, "Drywell Pressure
- High," respectively. TSTF-306-A also revised the actions of STS 3.3.6.1 by listing the new function numbers in the two Completion Times for Required Action A.1. Because these TIP system isolation functions are manual functions, the traveler specified that actions Condition G must be entered immediately upon entering Condition C, "Required Action and associated Completion Time of Condition A or B not met." This action is appropriate because Table 3.3.6.1-1 specifies entering actions Condition G for the other manual isolation instrumentation functions. Furthermore, to be consistent with a similar Note in STS 3.6.1.3, "Primary Containment Isolation," the traveler also added a Note to the STS 3.3.6.1 actions table that states, "Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls."
In TS 3.3.6.1, the proposed change adds the following NOTE in the LCO ACTIONS:
Penetration flow paths except for 18 inch purge valve penetration flow paths may be unisolated intermittently under administrative controls.
Additionally, Current TS 3.3.6.1, Completion Time for Required Action A.1 states:
12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> for Functions 2.a, 2.b, and 6.b 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> for Functions other than Functions 2.a, 2.b, and 6.b Revised TS 3.3.6.1, Completion Time for Required Action A.1 would state:
12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> for Functions 2.a, 2.b, 6.b, 7.a, and 7.b 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> for Functions other than Functions 2.a, 2.b, 6.b, 7.a, and 7.b TS 3.3.6.1 is revised to add the following new Condition G. Additionally, as a result, existing LCO Conditions G, H, and I change to H, I, and J, respectively, and LCO Table 3.3.6.1-1 is revised accordingly.
G. As required by Required G.1 Isolate the affected 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Action C.1 and referenced in penetration flow path(s).
Table 3.3.6.1-1.
LCO Table 3.3.6.1-1 is revised to add the new functions 7a and 7b:
[see next page]
APPLICABLE CONDITIONS MODES OR REQUIRED REFERENCED OTHER CHANNELS FROM SPECIFIED PER TRIP REQUIRED SURVEILLANCE ALLOWABLE FUNCTION CONDITIONS SYSTEM ACTION C.1 REQUIREMENTS VALUE
- 7. Traversing lncore Probe System Isolation
- a. Reactor Vessel Water 1,2,3 2 G SR 3.3.6.1.1 ~ 0 inches Level - Low, Level 3 SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6
- b. Drywell Pressure - 1,2,3 2 G SR 3.3.6.1.1 s 1.92 psig High SR 3.3.6.1.2 SR 3.3.6.1.5 SR 3.3.6.1.6 NRC Staff Evaluation of the Proposed Changes to TS Requirements for PC IVs:
The NRC staff has determined that this change does not reduce the level of safety currently afforded by the HNP TSs because the added allowance stated in the added Note is already permitted by TS 3.6.1.3 and is consistent with the intent of the HNP TS requirements for primary containment penetration flow paths with automatically actuated PC IVs. The addition of this allowance also increases the usability of HNP TSs by clarifying that flow paths isolated to comply with TS 3.3.6.1 action requirements (except for the 18-inch purge valve penetration flow paths) may also be unisolated intermittently under administrative controls ..
Associated with this change is enumeration of the existing actions table note in TS 3.3.6.1 regarding separate condition entry for each primary containment isolation instrumentation channel, as Note 2. The NRC staff concludes that this administrative change conforms to the STS format convention for Notes and has no effect on plant safety.
Based on the above, the NRC staff concludes that the changes regarding TS requirements for PCIVs are acceptable.
NRC Staff Evaluation of Proposed Changes Regarding the TIP System Isolation:
The revised LCO and action requirements for TIP system isolation allow TIP penetration flow path isolation rather than a unit shutdown in the event supporting automatic isolation instrumentation function channels are inoperable. This relaxation is appropriate because requiring a unit shutdown is overly restrictive for inoperable TIP system isolation instrumentation. The TIP system uses a small bore penetration (approximately 1/2 inch), and its isolation in a design-basis event is assumed to be accomplished by the manually operated shear valves. The ability to manually isolate the TIP system by either the normal automatic isolation valve (TIP system ball valves) or the shear valve(s) would be unaffected by inoperable instrumentation. Therefore, the option to isolate the penetration and to continue plant operation is provided. In order to implement this allowance, a separate isolation instrumentation function is being provided for the TIP system. The Completion Time provided to isolate the penetration is 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />, which is the Completion Time provided in the STS for penetration isolation when a manual containment isolation instrumentation function is inoperable.
These changes are consistent with the discussion of the TIP system ball and shear valves on HNP, Unit No. 1, FSAR pages 5.2-14 and 7.5-22, that TIP system isolation is accomplished by manual actuation of the ball valves, or by manual actuation of the shear valves in case a deployed TIP cannot be withdrawn.
The NRC staff concludes that the small expected penetration leakage rate from a guide tube leak in the reactor pressure vessel allows adequate time for the operator to manually isolate the flow path with the shear valve. Also, the probability of an event requiring automatic isolation of a TIP system guide tube penetration flow path is low. Based on the small expected leakage rate and low probability of an event, the proposed 24-hour Completion Time of proposed new Required Action G.1 provides reasonable assurance of adequate protection of public health and safety.
The other changes to TS 3.3.6.1 associated with the new action to isolate the TIP penetration flow path in 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> are administrative in nature because they only change the presentation of the existing LCO and action requirements for Functions 2.a and 2.b for the TIP ball valves and do not affect plant safety.
The NRC staff concludes that the requirements of 1O CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to TS 3.3.6.1 and Table 3.3.6.1-1 are acceptable.
3.12 TSTF-308-A. Revision 1. "Determination of Cumulative and Projected Dose Contributions in RECP" The NRC did not issue a letter approving this change to STS Revision 1. However, this change was incorporated by the NRC into Revision 2 of the STS issued in April 2001. TSTF-308-A modified NUREG-1433, STS 5.5.4, "Radioactive Effluent Controls Program," to describe the original intent of the dose projections.
Current HNP TS 5.5.4, paragraph e. states:
Determination of cumulative and projected dose contributions from radioactive effluents for the current calendar quarter and current calendar year, in accordance with the methodology and parameters in the ODCM [offsite dose calculation manual], at least every 31 days.
The proposed change revises paragraph e. in its entirety as follows:
Determination of cumulative dose contributions from radioactive effluents for the current calendar quarter and current calendar year in accordance with the methodology and parameters in the ODCM at least every 31 days.
Determination of projected dose contributions from radioactive effluents in accordance with the methodology in the ODCM at least every 31 days.
NRC Staff Evaluation
The regulation at 1O CFR 50.36a(a)(2), "Technical specifications on effluents from nuclear power reactors," requires each licensee to submit a report to the NRC that will allow an estimation of the maximum potential annual radiation doses to the public resulting from effluent releases. Generic Letter (GL) 89-01, "Implementation of Programmatic Controls for Radiological Effluent Technical Specifications in the Administrative Controls Section of the Technical Specifications and the Relocation of Procedural Details of PETS to the Offsite Dose Calculation Manual or to the Process Control Program," dated January 31, 1989 (ADAMS Accession No. ML031140051), provides guidance in support of implementing programmatic controls in TSs for radioactive effluents and for radiological environmental monitoring that conforms to the applicable regulatory requirements. The regulation at 1O CFR 20.1302, "Compliance with dose limits for individual members of the public," paragraph (b), requires that a licensee show compliance with the annual dose limit in 10 CFR 20.1301, "Dose limits for individual members of the public," demonstrating by measurement or calculation that the total effective dose equivalent to the individual likely to receive the highest dose from the licensed operation does not exceed the annual dose limit.
GL 89-01 combined two SRs, the cumulative and projected dose determinations, into one program element. In combining these requirements, the new program element can be interpreted to require determining projected dose contributions for the calendar quarter and current calendar year every 31 days. This wording was misleading and resulted in misinterpretation of the intent of the original STS and was not consistent with the original surveillance. Therefore, TSTF-308-A was developed and subsequently approved by the NRC
to not require dose projections for a calendar quarter and a calendar year every 31 days (i.e., to describe the actual intent of the dose projections).
The NRC staff reviewed the changes proposed by the licensee that were prepared using the guidance in TSTF-308-A. The NRC staff concludes that the revised wording for the HNP TSs clarifies the reporting requirements for projected doses, thus ensuring consistency with the requirements of 10 CFR 50.36a and 10 CFR 20.1302 and, therefore, is acceptable.
3.13 TSTF-318-A. Revision 0, "Revise 3.5.1 for one LPCI pump inoperable in each of two ECCS divisions" The proposed change adds a provision to Condition A of Specification 3.5.1, "ECCS -
Operating," to allow one LPCI pump to be inoperable in each subsystem for a period of 7 days.
Current TS 3.5.1, Condition A, states:
One low pressure ECCS injection/spray subsystem inoperable.
Revised TS 3.5.1, Condition A, would state:
One low pressure ECCS injection/spray subsystem inoperable.
One LPCI pump in both LPCI subsystems inoperable.
Current TS 3.5.1, Required Action A.1 for Condition A, states:
Restore low pressure ECCS injection/spray subsystem to OPERABLE status.
Revised TS 3.5.1, Required Action A.1 for Condition A, would state:
Restore low pressure ECCS injection/spray subsystem(s) to OPERABLE status.
Current TS 3.5.1, Condition D, states:
HPCI System inoperable.
One low pressure ECCS injection/spray subsystem inoperable.
Revised TS 3.5.1, Condition D, would state:
HPCI System inoperable.
Condition A entered.
Current TS 3.5.1, Condition F, states, in part:
Two or more low pressure ECCS injection/spray subsystems inoperable.
Revised TS 3.5.1, Condition F, would state, in part:
Two or more low pressure ECCS injection/spray subsystems inoperable for reasons other than Condition A.
NRC Staff Evaluation
The NRC staff documented its approval of TSTF-318-A, Revision 0, in a letter from William Beckner, NRC to James Davis, NEI dated June 29, 1999 (ADAMS Accession No. ML16237A030). The NRC staff reviewed the proposed changes and determined that TSTF-318 is applicable to HNP and is consistent with NUREG-1433. The NRC staff has determined that the proposed change allows the TSs to recognize an additional LPCI configuration that continues to ensure the design-basis analysis is met and is bounded by the currently allowed configuration. The NRC staff also determined that the proposed change is an improvement of the current TS requirements, which would require entry into LCO 3.0.3 and a plant shutdown in the event of one inoperable pump in each LPCI subsystem. Since the LPCI pumps also serve as RHR pumps, the proposed amendment would preclude the licensee having to put the plant in the RHR shutdown cooling configuration at a time when RHR capability is degraded.
Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(2) continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO. and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the proposed changes to TS 3.5.1 are acceptable.
3.14 TSTF-322-A. Revision 2. "Secondary Containment and Shield Building Boundary Integrity SRs" TSTF-322-A, Revision 2, was approved by the NRC as documented in a letter from William Beckner, NRC, to James Davis, NEI, dated February 16, 2000 (ADAMS Accession No. ML003684596). TSTF-322-A modified the secondary containment boundary integrity and shield building boundary integrity SRs to clarify their intent.
Current TS SR 3.6.4.1.3 states:
Verify required SGT subsystem(s) will draw down the secondary containment to
~ 0.20 inch of vacuum water gauge in s 120 seconds.
Revised TS SR 3.6.4.1.3 would state:
Verify secondary containment can be drawn down to :::: 0.20 inch of vacuum water gauge in s 120 seconds using required standby gas treatment (SGT) subsystem(s).
Current TS SR 3.6.4.1.4 states:
Verify required SGT subsystem(s) can maintain :::: 0.20 inch of vacuum water gauge in the secondary containment for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> at a flow rate s 4000 cfm [cubic feet per minute] for each subsystem.
Revised TS SR 3.6.4.1.4 would state:
Verify the secondary containment can be maintained :::: 0.20 inch of vacuum water gauge for 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> using required SGT subsystem(s) at a flow rate s 4000 cfm per subsystem.
NRC Staff Evaluation
The changes to the secondary containment SRs in HNP TS 3.6.4.1 conform to the intent of the changes made to the STS by TSTF-322-A, with the exception of the surveillance frequency.
The surveillance frequency is controlled by the SFCP, which is a program developed subsequent to the approval of TSTF-322-A. The NRC staff reviewed the TS changes and has determined that they clarify the intent of the drawdown tests for demonstrating operability of the secondary containment. If an SGT subsystem is inoperable, TS 3.6.4.3 specifies appropriate action requirements; it does not imply that the secondary containment is inoperable. The proposed changes only clarify the intended meaning of the existing SRs; therefore, they are administrative in nature and have no safety impact.
Additionally, the NRC staff has determined that that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SRs provide the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes that the changes to SR 3.5.4.1.3 and SR 3.6.4.1.4 are acceptable.
3.15 TSTF-323-A. Revision 0. "EFCV [Excess Flow Check Valve] Completion Time to 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />" As stated in Section 3.1 of this safety evaluation, the TSTF-323-A change preceded the approval of, and was subsumed in, the final version (Revision 3) of TSTF-30. Therefore, Section 3.1 of this safety evaluation discusses the licensee's proposed adoption of both TSTF-30 and TSTF-323-A changes and provides the NRC staff's assessment.
3.16 TSTF-37 4-A, Revision 0, "Revision to TS 5.5.13 and associated TS Bases for Diesel Fuel Oil" The NRC staff documented its approval of TSTF-374-A, Revision 0, in a letter from Thomas H.
Boyce, NRC, to the TSTF dated January 13, 2005 (ADAMS Accession No. ML050130309), and the NRC approved this change to STS Revision 2 on April 14, 2006. TSTF-374-A revises STS 5.5.9, "Diesel Fuel Oil Testing Program," diesel fuel oil testing program (DFOTP) to remove references to the specific American Society for Testing and Materials (ASTM) standard from the administrative controls section of TSs and alternatively places them in a licensee-controlled document. Specific criteria are added to establish the acceptability of new fuel oil for use prior to, and following, the addition to storage tanks. The DFOTP of HNP, Unit Nos. 1 and 2, is located at TS 5.5.9, while the STS DFOTP is located at TS 5.5.1 O; however, this difference in numbering is immaterial to the proposed change.
Current TS 5.5.9 states:
A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following:
- a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil; and
- b. Total particulate concentration of the fuel oil is ~ 10 mg [milligram]/liter when tested every 92 days utilizing the guidance provided in ASTM D-2276, Method A-2 or A-3.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies.
Revised TS 5.5.9 would state:
A diesel fuel oil testing program to implement required testing of both new fuel oil and stored fuel oil shall be established. The program shall include sampling and testing requirements and acceptance criteria, all in accordance with applicable ASTM Standards. The purpose of the program is to establish the following:
- a. Acceptability of new fuel oil for use prior to addition to storage tanks by determining that the fuel oil has:
- 1. An API [American Petroleum Institute] gravity or an absolute specific gravity within limits,
- 2. A flash point and kinematic viscosity within limits for ASTM 2D fuel oil, and
- 3. A water and sediment content within limits;
- b. Within 31 days following addition of the new fuel oil to storage tanks, verify that the properties of the new fuel oil, other than those addressed in a., above, are within limits for ASTM 2D fuel oil; and
- c. Total particulate concentration of the fuel oil is s 10 mg/liter when tested every 92 days.
The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the Diesel Fuel Oil Testing Program surveillance frequencies.
NRC Staff Evaluation
The NRC staff has reviewed the changes to the DFOTP in TS 5.5.9. For HNP, the result is a specification closer to the STS than the previous specification. The former requirements, which were subject to interpretation, " ... fuel oil has not become contaminated with other products during transit, thus altering the quality of the fuel oil," are replaced by more objective tests for American Petroleum Institute gravity or specific gravity, flash point and kinematic viscosity, and sediment and water content. A specific time limit of 31 days is added for new fuel to storage tanks, and particulate content testing requirements are retained. Additionally, because of significant differences between this licensee's TS bases and the STS bases, this licensee will control the removed ASTM requirements in a license-controlled procedure. The licensee states that future changes are also subject to a 10 CFR 50.59 review as they would be in the TS Bases. The NRC staff has determined that the proposed changes to TS 5.5.9 conform to the intent of TSTF-37 4-A.
Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(5) continue to be met because the revised TSs provide the appropriate administrative controls to ensure the necessary quality of the fuel oil is maintained.
Based on the above, the NRC staff concludes that the proposed changes to TS 5.5.9 are acceptable.
3.17 TSTF-400-A, Revision 1. "Clarify SR on Bypass of DG [Diesel Generator) Automatic Trips" The NRCs approval of TSTF-400-A, Revision 1, is documented by letter to the TSTF dated November 13, 2004 (ADAMS Accession No. ML043200067). The proposed change revises TS 3.8.1, "AC Sources - Operating," Surveillance 3.8.1.11, to clarify that the intent of the SR is to test the non-critical emergency DG automatic trips. The numbering of SRs in the HNP TSs is different from the STS numbering. STS SR 3.8.1.13 corresponds to SR 3.8.1.11 in the HNP TSs. This has no effect on the requested change.
Current TS SR 3.8.1.11 states, in part that:
Verify each DG's automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal except:
- a. Engine overspeed;
- b. Generator differential current; and
- c. Low lube oil pressure.
Revised TS SR 3.8.1.11 would state:
Verify each DG's non-critical automatic trips are bypassed on actual or simulated loss of voltage signal on the emergency bus concurrent with an actual or simulated ECCS initiation signal.
NRC Staff Evaluation
The changes to SR 3.8.1.11 and the associated TS bases state that the SR only verifies that non-critical DG trips are bypassed. The non-critical DG trips are bypassed during design-basis accidents and provide an alarm on an abnormal engine condition. The NRC staff reviewed this change and has determined that it provides clarification, and no STS requirements are materially altered.
Additionally, the NRC staff has determined that the requirements of 10 CFR 50.36(c)(3) continue to be met because the revised SR provides the appropriate surveillance to ensure the necessary quality of components is maintained and the LCO will be met.
Based on the above, the NRC staff concludes that the changes to SR 3.8.1.11 are acceptable.
3.18 TSTF-439-A. Revision 2. "Eliminate Second Completion Times Limiting Time From Discovery of Failure To Meet an LCO" The NRC approved TSTF-439-A, Revision 2, in a letter dated January 11, 2006 (ADAMS Accession No. ML060120272). TSTF-439-A revised the STS by eliminating the second Completion Times limiting time from discovery of failure to meet an LCO from the affected Required Actions and modifies the example in TS 1.3. These Completion Times (henceforth referred to as "second Completion Times") are joined by an "AND" logical connector to the condition-specific Completion Time and state, "X days from discovery of failure to meet the LCO" (where "X" varies by specification).
HNP TSs 3.1. 7, "Standby Liquid Control (SLC) System"; 3.6.4.3, "Standby Gas Treatment (SGT) System"; 3.8.1, "AC Sources - Operating"; and 3.8.7, "Distribution Systems - Operating,"
contain Required Actions with a second Completion Time to establish a limit on the maximum time allowed for any combination of conditions that result in a single continuous failure to meet
the LCO. The proposed change deletes these second Completion Times from the affected Required Actions.
- Current TS 3.1.7, Completion Time for Required Action A.1, states:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 10 days from discovery of failure to meet the LCO Revised TS 3.1.7, Completion Time for Required Action A.1, would state:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />
- Current TS 3.6.4.3, Completion Time for Required Action 8.1, states:
7 days 30 days from discovery of failure to meet the LCO Revised TS 3.6.4.3, Completion Time for Required Action 8.1, would state:
7 days
- Current TS 3.8.1, Completion Time for Required Action A.3, states:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 17 days from discovery of failure to meet LCO 3.8.1.a, b, or c Revised TS 3.8.1, Completion Time for Required Action A.3, would state:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />
- Current TS 3.8.1, Completion Time for Required Action 8.4, states:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for a Unit 1 DG with the swing DG not inhibited or maintenance restrictions not met
14 days for a Unit 1 DG with the swing DG inhibited from automatically aligning to Unit 2 and maintenance restrictions met 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for the swing diesel with maintenance restrictions not met 14 days for the swing diesel with maintenance restrictions met 17 days from discovery of failure to meet LCO 3.8.1.a, b, or c Revised TS 3.8.1, Completion Time for Required Action B.4, would state:
72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for a Unit 1 DG with the swing DG not inhibited or maintenance restrictions not met 14 days for a Unit 1 DG with the swing DG inhibited from automatically aligning to Unit 2 and maintenance restrictions met 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> for the swing diesel with maintenance restrictions not met 14 days for the swing diesel with maintenance restrictions met
- Current TS 3.8.7, Completion Time for Required Action B.1, states:
12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action B.1, would state:
12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />
- Current TS 3.8.7, Completion Time for Required Action C.1, states:
8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8.7, Completion Time for Required Action C.1, would state:
8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />
- Current TS 3.8.7, Completion Time for Required Action D.1, states:
2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> 16 hours from discovery of failure to meet LCO 3.8.7.a Revised TS 3.8. 7, Completion Time for Required Action D.1, would state:
2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> The proposed change also revises TS Section 1.3, Example 1.3-3 (as shown below), to remove the discussion of second Completion Times and to revise the discussion in that example to state that alternating between conditions in such a manner that operation could continue indefinitely, without restoring systems to meet the LCO, is inconsistent with the basis of the Completion Times and is inappropriate.
The proposed changes to TS 1.3, "Completion Times," are as follows:
- The last paragraph on TS page 1.3-2 currently states, in part, that:
Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.
The proposed change deletes the above statement.
- Example 1.3-3 currently reflects for Conditions A and B, a first Completion Time of 7 days and 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />, respectively, and a second Completion Time as "AND 10 days from discovery of failure to meet the LCO," for both conditions. Condition C in the example does not contain a second Completion Time.
The proposed change revises Example 1.3-3 to eliminate the second Completion Times, "10 days from discovery of failure to meet the LCO," from Conditions A and B.
- TS Section 1.3, the last paragraph currently describes second Completion Time as follows:
The Completion Times of Conditions A and B are modified by a logical connector, with a separate 1O day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO. This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock". In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.
The proposed change replaces the above paragraph with the following:
It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.
As stated in Section 4.0, "Commitments," of the application, SNC specifies the following commitment regarding its proposed change:
SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed."
The licensee also stated that the procedure will be revised prior to implementation of the proposed TS change.
NRC Staff Evaluation
The Maintenance Rule (10 CFR 50.65(a)(1 )), requires licensees to monitor the performance or conditions of structures, systems, and components (SSCs) in a manner sufficient to provide reasonable assurance that SSCs are capable of fulfilling their intended functions. If the performance or condition of an SSC does not meet established goals, appropriate corrective action is required to be taken. The NRC resident inspectors monitor the licensee's corrective action program and can take action if the licensee's maintenance program allows the systems
required by a single LCO to become concurrently inoperable multiple times. The performance and condition monitoring activities required by 10 CFR 50.65 (a)(1) and (a)(2) would identify if poor maintenance practices resulted in multiple entries into the actions of the TSs and unacceptable unavailability of these SSCs. The effectiveness of these performance monitoring activities, and associated corrective actions, is evaluated at least every refueling cycle, not to exceed 24 months, per 10 CFR 50.65 (a)(3).
Prior to 10 CFR 50.65, TSs were the primary rules governing operations, including what equipment must normally be in service, how long equipment can be out of service, compensatory actions, and surveillance testing to demonstrate equipment readiness. A goal of the TSs is to provide adequate assurance of the availability and reliability of equipment needed to prevent, and if necessary, mitigate, accidents and transients. The Maintenance Rule shares this goal and operates through a dynamic and comprehensive process.
The objective of the cornerstone is to monitor the availability, reliability, and capability of systems that mitigate the effects of initiating events to prevent core damage. Licensees also reduce the likelihood of reactor accidents by maintaining the availability and reliability of mitigating systems. Mitigating systems include those systems associated with safety injection, decay heat removal, and their support systems, such as emergency AC power systems (which encompasses the AC sources distribution system LCOs, as noted by the licensee), and the auxiliary feedwater system. Inputs to the mitigating systems cornerstone include both inspection procedures and performance indicators to ensure that all reactor oversight process objectives are being met. Satisfactory licensee performance within the mitigation systems reactor oversight process cornerstone provides reasonable assurance in monitoring the inappropriate use of TS condition Completion Times.
The NRC approved this change to the STS on January 11, 2006. TSTF-439-A revised Example 1.3-3 of the TSs to state, in part, "There shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended." SNC provided a regulatory commitment to revise Operations Procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed." The licensee will revise the procedure prior to implementation of the proposed change.
The NRC staff concludes that the proposed changes establish a new TS convention to appropriately limit the time allowed for the plant to operate in any combination of LCO conditions that could result in a single continuous failure to meet the LCO. The new convention meets the intent of the Completion Times.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) remain unaffected by the proposed changes and would continue to be met because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO, and the appropriate remedial measures are specified if the LCO is not met.
Based on the above, the NRC staff concludes that the changes to TSs 1.3, 3.1.7, 3.6.4.3, 3.8.1, and 3.8.7, are acceptable.
3.19 TSTF-458-T. Revision 0. "Removing Restart of Shutdown Clock for Increasing Suppression Pool Temperature" TSTF-458-T, Revision 0, revises BWR STS 3.6.2.1, "Suppression Pool Average Temperature,"
to remove a potential ambiguity between Actions D and E that would allow resetting of the shutdown Completion Time clock.
Current TS 3.6.2.1, Condition D, states:
Suppression pool average temperature > 110°F but s 120°F.
Revised TS 3.6.2.1, Condition D, would state:
Suppression pool average temperature > 110°F.
Current TS 3.6.2.1, Required Action D.2, states:
Verify suppression pool average temperature s 120°F.
Revised TS 3.6.2.1, Required Action D.2, would state:
Determine suppression pool average temperature.
Current TS 3.6.2.1, Required Actions E.1 and E.2, states:
E.1 Depressurize the reactor vessel to < 200 psig.
AND E.2 Be in MODE 4.
With Required Action E.2 having a Completion Time of:
36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Revised TS 3.6.2.1 would state:
Required Action E.2 and its associated Completion Time of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> are deleted, resulting in Required Action E.1 remaining:
E.1 Depressurize the reactor vessel to < 200 psig.
NRC Staff Evaluation
AT-traveler, such as TSTF-458-T, Revision 0, is prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those
requirements. The NRC does not review nor approve T-travelers, and the proposed changes under T-travelers are not incorporated in the respective STS.
The NRC staff reviewed these changes and determined that they ( 1) clarify the scope of Condition D and the intent of specified actions in Condition D, and (2) remove a redundant action in Condition E to eliminate an ambiguity between specified actions for existing Conditions D and E. Thus, these changes are of administrative nature and do not affect the technical content of specified TS requirements. Specifically, this eliminates having two Required Actions and Completion Times, both directing entry into MODE 4 with staggered Completion Times.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2) continue to be met because the revised LCO conditions provide appropriate requirements to ensure that the LCO will be met.
Based on the above, the NRC staff concludes that the changes to TS 3.6.2.1 are acceptable.
3.20 TSTF-464-T. Revision 0, "Clarify the Control Rod Block Instrumentation Required Action" The proposed change clarifies the wording of Required Action C.2.1.2 of HNP TS 3.3.2.1, "Control Rod Block Instrumentation," to align with the TS Bases, Section 3.3.2.1.
Current Hatch TS, and Proposed Changes:
Current TS 3.3.2.1, Required Action C.2.1.2, states:
Verify by administrative methods that startup with RWM [rod worth minimizer]
inoperable has not been performed in the last calendar year.
Revised TS 3.3.2.1, Required Action C.2.1.2, would state:
Verify by administrative methods that startup with RWM inoperable has not been performed in the last 12 months.
NRC Staff Evaluation
AT-traveler, such as TSTF-464-T, Revision 0, was prepared by the industry to provide further clarification of specific TS requirements, without changing the intent or scope of those requirements. The NRC did not review nor approve T-travelers, and the proposed changes under T-travelers were not incorporated in the respective STS.
The NRC staff reviewed the proposed change and determined that the current ambiguity of the phrase "last calendar year" does not provide assurance that the appropriate remedial measures are performed if the LCO is not met. Replacing the phrase "last calendar year" with the proposed phrase "last 12 months" provides additional clarity and assurance that appropriate remedial measures are performed if the LCO is not met.
Additionally, the NRC staff concludes that the requirements of 10 CFR 50.36(c)(2)will be met with the proposed change because the minimum performance level of equipment needed for safe operation of the facility is contained in the LCO.
Based on the above, the NRC staff concludes that the change to TS 3.3.2.1 is acceptable.
3.21 STS Adoption #1 - Revise the 5.5.7 Introductory Paragraph to be Consistent with the ISTS The licensee proposed to adopt the formatting and language in the STS, NUREG-1433, STS for General Electric BWR/4 Plants, Revision 4.
Current TS 5.5. 7, "Ventilation Filter Testing Program (VFTP)," the introductory paragraph states:
The VFTP will establish the required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, or: 1) after any structural maintenance on the HEPA filter or charcoal adsorber housings, 2) following painting, fire or chemical release in any ventilation zone communicating with the system, or
- 3) after every 720 hours0.00833 days <br />0.2 hours <br />0.00119 weeks <br />2.7396e-4 months <br /> of charcoal adsorber operation.
TS 5.5.7 is revised to state:
A program shall be established to implement the following required testing of Engineered Safety Feature (ESF) filter ventilation systems at the frequencies specified in Regulatory Guide 1.52, Revision 2, Sections C.5.c and C.5.d, and in accordance with Regulatory Guide 1.52, Revision 2.
NRC Staff Evaluation
The changes proposed for HNP TS 5.5.7 are similar to the wording in STS 5.5.8. This change removes detail from TS 5.5.7 and makes reference to RG 1.52, "Design, Testing, and Maintenance Criteria for Post-Accident Engineered-Safety-Feature Atmosphere Cleanup System Air Filtration and Adsorption Units of Light-Water-Cooled Nuclear Power Plants." The list of requirements for the program that the licensee proposed to remove are covered in Section C.6.b of RG 1.52 and TS SR 3.0.1. The NRC staff reviewed the proposed changes and determined that incorporating the requirement by reference for the VFTP is acceptable because detail can be removed from the TSs while maintaining the testing requirement. This simplifies the TSs and allows wording and formatting to be consistent with the STS, encouraging uniformity between the HNP units and the SNC fleet.
Additionally, the NRC staff concludes that the requirements of 1O CFR 50.36(c)(5) continue to be met because the revised TS administrative controls testing program maintains its implementation requirements.
Based on the above, the NRC staff concludes that the changes to TS 5.5.7 are acceptable.
4.0 REGULATORY COMMITMENTS SNC provided two regulatory commitments with the LAR.
The first regulatory commitment states:
A statement will be added to the FSAR similar to the following regarding the performance of logic testing for critical emergency diesel generator trip functions:
The critical emergency diesel generator protective trip functions (i.e.,
engine overspeed, generator differential current, and low lube oil pressure) are tested periodically per station procedures. The critical protective trip functions are tested by inputting or simulating appropriate signals and demonstrating that the associated instrumentation logic will function to actuate a trip of the emergency diesel generator.
This regulatory commitment is related to the adoption of TSTF-400 (discussed in Section 3.17 of this safety evaluation). The NRC staff reviewed the commitment and found that it provides additional information clarifying the testing of the EOG trip functions. The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.17 of this safety evaluation.
The second regulatory commitment states:
SNC commits to revise Operations procedure 31GO-OPS-006-0 to include a statement similar to the following: "Alternating between LCO Conditions, in order to allow indefinite continued operation while not meeting the LCO, is not allowed."
This regulatory commitment is related to the adoption of TSTF-439 (discussed in Section 3.18 of this safety evaluation). The NRC staff reviewed the commitment and finds that it specifies a location for the administrative controls of TSTF-439-A. The NRC staff did not use the regulatory commitment as a basis for its conclusion for Section 3.18 of this safety evaluation.
5.0 STATE CONSULTATION
In accordance with the Commission's regulations, the Georgia State official was notified of the proposed issuance of the amendments on June 22, 2016. The State official had no comments.
6.0 ENVIRONMENTAL CONSIDERATION
The amendments change a requirement with respect to the installation or use of facility components located within the restricted area as defined in 10 CFR Part 20 and change SRs.
The NRC staff has determined that the amendments involve no significant increase in the amounts and no significant change in the types of any effluents that may be released offsite and that there is no significant increase in individual or cumulative occupational radiation exposure.
The Commission has previously issued a proposed finding that the amendments involve no significant hazards consideration, and there has been no public comment on such finding (80 FR 17095; March 31, 2015). Accordingly, the amendments meet the eligibility criteria for
categorical exclusion set forth in 10 CFR 51.22(c)(9). Pursuant to 10 CFR 51.22(b), no environmental impact statement or environmental assessment need be prepared in connection with the issuance of the amendments.
7.0 CONCLUSION
The Commission has concluded, based on the considerations discussed above, that: (1) there is reasonable assurance that the health and safety of the public will not be endangered by operation in the proposed manner, (2) there is reasonable assurance that such activities will be conducted in compliance with the Commission's regulations, and (3) the issuance of the amendments will not be inimical to the common defense and security or to the health and safety of the public.
Principal Contributors: Craig Harbuck, NRO Theodore Tjader, NRO Hien Le, NRO Derek Scully, NRO Margaret Chernoff, NRR Matthew Hamm, NRR Caroline Tilton, NRR Pete Snyder, NRR Khadijah West, NRR Larry Wheeler, NRR Ravinder Grover, NRR Date: September 29, 2016
ML16231A041 *by e-mail OFFICE NRR/DORL/LPL2-1 /PM NRR/DORL/LPL2-1 /LA NRR/DSS/STSB/BC*
NAME MOrenak LRonewicz AKlein DATE 8/23/2016 8/23/2016 7/27/2016 OFFICE OGC NLO wlcomments NRR/DORL/LPL2-1 /BC NRR/DORL/LPL2-1/PM NAME Jlindell MMarkley MOrenak DATE 9/06/2016 9/29/2016 9/29/2016