ML16340A005
ML16340A005 | |
Person / Time | |
---|---|
Site: | Hatch, Vogtle, Farley ![]() |
Issue date: | 12/01/2016 |
From: | Pierce C R Southern Nuclear Operating Co |
To: | Document Control Desk, Office of Nuclear Reactor Regulation |
References | |
N-16-1837 | |
Download: ML16340A005 (87) | |
Text
--&
December 1, 2016 Charles R. Pierce Regulatory Affairs Director 40 Inverness Center Parkway Post Office Box 1295 Birmingham, AL 35242 205 992 7872 tel 205 992 7601 fax crpierce@southernco.com Docket Nos.: 50-321 50-348 50-424 50-366 50-364 50-425 NL-16-1837 U.S. Nuclear Regulatory Commission ATIN: Document Control Desk Washington, D. C. 20555-0001 Joseph M. Farley Nuclear Plant -Units 1 and 2 Edwin I. Hatch Nuclear Plant -Units 1 and 2 Vogtle Electric Generating Plant -Units 1 and 2 License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Revision 4, "Clarify Use and Application Rules" Ladies and Gentlemen:
In accordance with the. provisions of 1 O CFR 50.90, Southern Nuclear Operating Company (SNG) is submitting a request for an amendment to the Technical Specifications (TS) for Joseph M. Farley Nuclear Plant (FNP), Units 1 and 2, Edwin I. Hatch Nuclear Plant (HNP), Units 1 and 2, and Vogtle Electric Generating Plant (VEGP), Units 1 and 2. The proposed amendment would modify TS requirements in Section 1.3 and Section 3.0 regarding Limiting Condition for Operation (LGO) and Surveillance Requirement (SR) usage. These changes are consistent with NRG-approved Technical Specifications Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules." Enclosure 1 provides a description and assessment of the proposed changes. Enclosure 2 provides the existing TS pages marked up to show the proposed changes. Enclosure
- 3 provides revised (clean) TS pages. Enclosure 4 provides, for information only, existing TS Bases pages marked to show the proposed changes. SNG requests approval of the proposed license amendment by December 8, 2017. The proposed changes would be implemented within ( 90) days of issuance of the amendment.
This letter contains no NRG commitments.
If you have any questions, please contact Ken McElroy at 205.992.7369.
U. S. Nuclear Regulatory Commission NL-16-1837 Page2 Mr. C. R. Pierce states he is Regulatory Affairs Director of Southern Nuclear Operating Company, is authorized to execute this oath on behalf of Southern Nuclear Operating Company and, to the best of his knowledge and belief, the facts set forth in this letter are true.
c.rv C.R. Pierce Regulatory Affairs Director CRP/KMO/lac before me this J__ day of Q a.A O/hl k , 2016. My commission expires: ) D -o-Zl> / 1 *
Enclosures:
- 1) Description and Assessment
- 2) FNP, HNP, and VEGP Technical Specification Marked Up Pages 3) FNP, HNP, and VEGP Technical Specification Clean Typed Pages 4) FNP, HNP, and VEGP Technical Specification Bases Marked Up Pages (for information only) cc: Southern Nuclear Operating Company Mr. S. E. Kuczynski, Chairman, President
& CEO Mr. D. G. Bost, Executive Vice President
& Chief Nuclear Officer Mr. M. D. Meier, Vice President-Regulatory Affairs Mr. D. R. Madison, Vice President
-Fleet Operations Mr. B. J. Adams, Vice President
-Engineering Ms. C. A. Gayheart Vice President
-Farley Mr. D. R. Vineyard Vice President
-Hatch Mr. B. K. Taber, Vice President
-Vogtle 1 & 2 Ms. B. L. Taylor, Regulatory Affairs Manager -Farley Mr. G. L. Johnson, Regulatory Affairs Manager-Hatch Mr. D. D. Sutton, Regulatory Affairs Manager -Vogtle 1 & 2 RType: Farley=CFA04.054; Hatch=CHA02.004; Vogtle=CVC7000 U. S. Nuclear Regulatory Commission Ms. C. Haney, Regional Administrator Mr. R. E. Martin, NRR Senior Project Manager -Vogtle 1 & 2 Mr. S. A. Williams, NRR Senior Project Manager -Farley Mr. M. D. Orenak, NRR Project Manager -Hatch Mr. D. H. Hardage, Senior Resident Inspector
-Hatch Mr. P. K. Niebaum, Senior Resident Inspector-Farley Ms. N. R. Childs, Senior Resident Inspector
-Vogtle 1 & 2 U. S. Nuclear Regulatory Commission Page 3 Alabama Department of Public Health David Walter, Director, Alabama Office of Radiation Control State of Georgia Mr. J. H. Turner, Environmental Director Protection Division Joseph M. Farley Nuclear Plant, Units 1 and 2 Edwin I. Hatch Nuclear Plant, Units 1 and 2 Vogtle Electric Generating Plant, Units 1 and 2 License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Revision 4, "Clarify Use and Application Rules" Enclosure 1 Description and Assessment Enclosure 1 to NL-16-1837 Description and Assessment
1.0 DESCRIPTION
The proposed change revises Section 1.3, "Completion Times," and Section 3.0, "LCO Applicability" of the Technical Specifications (TS) to clarify the use and application of the TS usage rules, as described below: Section 1.3 is revised to clarify "discovery." Section 1.3 to revised to discuss exceptions to starting the Completion Time at condition entry. Limiting Condition for Operation (LCO) 3.0.4.b is revised to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. Surveillance Requirement (SR) 3.0.3 is revised to allow application of SR 3.0.3 when an SR has not been previously performed and to clarify the application of SR 3.0.3. 2.0 ASSESSMENT
2.1 Applicability
of Safety Evaluation Southern Nuclear Operating Company (SNC) has reviewed the safety evaluation for Technical Specifications Task Force (TSTF) Traveler TSTF-529 provided to the TSTF in a letter dated April 21, 2016 (NRC ADAMS Accession No. ML 16060A441).
This included a review of the NRC staff's evaluation, as well as the information provided in TSTF-529.
As described in the subsequent paragraphs, SNC has concluded that the justifications presented in the TSTF-529 proposal and the safety evaluation prepared by the NRC staff are applicable to Joseph M. Farley Nuclear Plant (FNP), Units 1 and 2, Edwin I. Hatch Nuclear Plant (HNP), Units 1 and 2, and Vogtle Electric Generating Plant (VEGP), Units 1 and 2, and justify this amendment for the incorporation of the changes to the FNP Units 1 and 2, HNP Units 1 and 2, and VEGP Units 1 and 2 TS. 2.2 Variations SNC is not proposing any variations from the TS changes described in TSTF-529 or the applicable parts of the NRC staff's' safety evaluation dated April 21, 2016. One difference from the proposed TS Bases changes described in TSTF-529 should be noted for VEGP Units 1 and 2. Under the TS Bases section LCO 3.0.4, TSTF-529 proposes changing the examples applicable to LCO 3.0.4.c from (e.g., Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature Coefficient) to (e.g., RCS Specific Activity).
This particular change to the VEGP Units 1 and 2 TS Bases was implemented in an earlier amendment, and, therefore, requires no further modification in order to meet the changes described in TSTF-529.
E1-2 Enclosure 1 to NL-16-1837 Description and Assessment
3.0 REGULATORY
ANALYSIS 3.1 No Significant Hazards Consideration Analysis Southern Nuclear Operating Company (SNC) requests adoption of Technical Specifications Task Force (TSTF) Traveler TSTF-529, "Clarify Use and Application Rules," that is an NRC-approved change to the Standard Technical Specifications (STS), into the Joseph M. Farley Nuclear Plant (FNP), Units 1 and 2, Edwin I. Hatch Nuclear Plant (HNP), Units 1 and 2, and Vogtle Electric Generating Plant (VEGP), Units 1 and 2 Technical Specifications (TS). The proposed change revises Section 1.3, "Completion Times," and Sections 3.0, "LCO Applicability" and "SR Applicability" of the TS to clarify the use and application of the TS usage rules and revise the application of Surveillance Requirement (SR) 3.0.3. The revision of Section 1.3 clarifies the concept of "discovery" that a Limiting Condition for Operation (LCO) is not met and describes existing exceptions to the start of Completion Times in the TS. In addition, an editorial change is made to LCO 3.0.4.b in order to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. Lastly, SR 3.0.3 is revised to allow the application of SR 3.0.3 when an SR has not been previously performed.
SNC has evaluated whether or not a significant hazards consideration is involved with the proposed amendment by focusing on the three standards set forth in 1 O CFR 50.92, "Issuance of amendment," as discussed below: 1. Does the proposed amendment involve a significant increase in the probability or consequences of an accident previously evaluated?
Response:
No. The proposed changes to Section 1.3 and LCO 3.0.4 have no effect on the requirement for systems to be Operable and have no effect on the application of TS actions. The proposed change to SR 3.0.3 states that the allowance may only be used when there is a reasonable expectation the surveillance will be met when performed.
Since the proposed change does not significantly affect system Operability, the proposed change will have no significant effect on the initiating events for accidents previously evaluated and will have no significant effect on the ability of the systems to mitigate accidents previously evaluated.
Therefore, it is concluded that this change does not involve a significant increase in* the probability or consequences of an accident previously evaluated.
- 2. Does the proposed amendment create the possibility of a new or different kind of accident from any accident previously evaluated?
Response:
No. The proposed change to the TS usage rules does not affect the design or function of any plant systems. The proposed change does not change the E1-3 Enclosure 1 to NL-16-1837 Description and* Assessment Operability requirements for plant systems or the actions taken when plant systems are not operable.
Therefore, it is concluded that this change does not create the possibility of a new or different kind of accident from any accident previously evaluated.
- 3. Does the proposed amendment involve a significant reduction in a margin of safety? Response:
No. The proposed change clarifies the application of Section 1.3 and LCO 3.0.4 and does not result in changes in plant operation.
SR 3.0.3 is revised to allow application of SR 3.0.3 when a SR has not been previously performed if there is a reasonable expectation that the SR will be met when performed.
This expands the use of SR 3.0.3 while ensuring the affected system is capable of performing its safety function.
As a result, plant safety is either improved or unaffected.
Therefore, it is concluded that this change does not involve a significant reduction in a margin of safety. Based on the above, SNC concludes that the proposed change does not involve a significant hazards consideration under the standards set forth in 1 O CFR 50.92(c), and, accordingly, a finding of "no significant hazards consideration" is justified.
4.0 ENVIRONMENTAL
EVALUATION The proposed change would change a requirement with respect to installation or use of a facility component located within the restricted area, as defined in 1 O CFR 20, or would change an inspection or surveillance requirement.
However, the proposed change does not involve (i) a significant hazards consideration, (ii) a significant change in the types or significant increase in the amounts of any effluents that may be released offsite, or (iii) a significant increase in individual or cumulative occupational radiation exposure.
Accordingly, the proposed change meets the eligibility criterion for categorical exclusion set forth in 10 CFR 51.22(c)(9).
Therefore, pursuant to 10 CFR 51.22(b), no environmental impact statement or environmental assessment need be prepared in connection with the proposed change. E1-4 Joseph M. Farley Nuclear Plant, Units 1 and 2 Edwin I. Hatch Nuclear Plant, Units 1 and 2 Vogtle Electric Generating Plant, Units 1 and 2 License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Revision 4, "Clarify Use and Application Rules" Enclosure 2 FNP, HNP, and VEGP Technical Specification Marked Up Pages Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied. such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks. such as testing. without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded.
the Completion Time begins at that point. The exceptions may also be incomorated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating," Required Action B.2. requires declaring required feature(s) supported by an inoperable diesel generator.
inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discoverv of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Farley Units 1 and 2 1.3-1 Amendment No. 146 (Unit 1) Amendment No. 137 (Unit 2)
Farley Units 1 and 2 Completion Times 1.3 Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.
unless otherwise specified.
Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.
unless otherwise specified.
However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within 1.3-2 (continued)
Amendment No. 146 (Unit 1) Amendment No. 137 (Unit 2)
LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 Farley Units 1 and 2 b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.;-
!exceptions to this Specification are stated in the individual Specifications),;,, or c. When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.
When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with specification 5.5.15, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Test Exception LCO 3.1.8 allows specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Test Exception LCOs is optional.
When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.
3.0-2 Amendment No. 173 (Unit 1) Amendment No. 166 (Unit 2)
SR Applicability 3:0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 SR 3.0.4 Farley Units 1 and 2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. Entry into a MODE or other specified condition in the Applicability of an LCO shall only be made when the LCO's Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4. 3.0-4 Amendment No. 173 (Unit 1) Amendment No. 166 (Unit 2)
Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION HATCH UNIT 1 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified.
the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing. without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incoroorated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discoverv of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions 1.3-1 Amendment No. 195 HATCH UNIT 1 Completion Times 1.3 for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.
unless otherwise specified.
Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.
unless otherwise specified.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability: (continued) 1.3-2 Amendment No. 195 LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 HATCH UNIT 1 c. management actions, if appropriate.;-
!exceptions to this specification are stated in the individual Specificationsl;;;
or When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY, or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing. When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.10, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Special Operations LCOs in Section 3.1 O allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Special Operations LCOs is optional.
When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.
3.0-2 Amendment No. 246 SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 HATCH UNIT 1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may-be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed > 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 Amendment No. 250 Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION HATCH UNIT2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing. without starting the Completion Time. While utilizing the Note. should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded.
the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating." Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator.
inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discoverv of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions 1.3-1 Amendment No. 135 HATCH UNIT 2 Completion Times 1.3 for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition, unless otherwise specified.
Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability: (continued) 1.3-2 Amendment No. 135 SR Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 management actions, if appropriate;-
!exceptions to this specification (continued) are stated in the individual Specifications),;,, or LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 HATCH UNIT 2 c. When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY, or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing. When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.10, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Special Operations LCOs is optional.
When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.
3.0-2 Amendment No. 190 SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 HATCH UNIT2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... "basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed > 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 Amendment No. 194 Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION Vogtle Units 1 and 2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied. such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks. such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incornorated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator.
inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
1.3-1 Amendment No. 96 (Unit 1) Amendment No. 74 (Unit 2)
Vogtle Units 1 and 2 Completion Times 1.3 If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.
unless otherwise specified.
Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
1.3-2 (continued)
Amendment No. 96 (Unit 1) Amendment No. 74 (Unit 2)
LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 Vogtle Units 1 and 2 b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate-;-
{exceptions to this Specification are stated in the individual Specificationsl; or c. When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.
When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.15, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. 3.0-2 (continued)
Amendment No. 137 (Unit 1) Amendment No. 116 (Unit 2)
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 Vogtle Units 1 and 2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 Amendment No. 125 (Unit 1) Amendment No. 103 (Unit 2)
Joseph M. Farley Nuclear Plant, Units 1 and 2 Edwin I. Hatch Nuclear Plant, Units 1 and 2 Vogtle Electric Generating Plant, Units 1 and 2 License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Revision 4, "Clarify Use and Application Rules" Enclosure 3 FNP, HNP, and VEGP Technical Specification Clean Typed Pages Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION Farley Units 1 and 2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating," Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
1.3-1 (continued)
Amendment No. Amendment No. (Unit 1) (Unit 2)
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
Farley Units 1 and 2 If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.
Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:
- a. Must exist concurrent with the first inoperability; and 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 extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, 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. (continued) 1.3-2 Amendment No. (Unit 1) Amendment No. (Unit 2)
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
EXAMPLES Farley Units 1 and 2 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
... " The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE 1.3-1 ACTIONS CONDITION B. Required Action and associated Completion Time not met. REQUIRED ACTION COMPLETION TIME B.1 Be in MODE 3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> B.2 Be in MODE 5. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition Bis entered. The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. 1.3-3 (continued)
Amendment No. Amendment No. (Unit 1) (Unit 2)
LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 Farley Units 1 and 2 b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications);
or c. When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.
When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, an evaluation shall be performed in accordance with specification 5.5.15, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Test Exception LCO 3.1.8 allows specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Test Exception LCOs is optional.
When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.
3.0-2 Amendment No. (Unit 1) Amendment No. (Unit 2)
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 Farley Units 1 and 2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 Amendment No. (Unit 1) Amendment No. (Unit 2)
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.4 Farley Units 1 and 2 Entry into a MODE or other specified condition in the Applicability of an LCO shall only be made when the LCO's Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4. This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. 3.0-5 Amendment No. (Unit 1) Amendment No. (Unit 2)
Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION HATCH UNIT 1 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., I inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating, " Required Action 8.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability. (continued) 1.3-1 Amendment No.
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
HATCH UNIT 1 If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.
Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The , subsequent inoperability:
- a. Must exist concurrent with the first inoperability; and 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. (continued) 1.3-2 Amendment No.
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
EXAMPLES HATCH UNIT 1 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
... " The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE 1.3-1 ACTIONS CONDITION B. Required Action and associated Completion Time not met. REQUIRED ACTION COMPLETION TIME 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 /> 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 /> Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition Bis entered. The Required Actions of Condition B are to be in MODE 3 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND in MODE 4 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />) is allowed for reaching MODE 4 from the time that Condition B was entered. If MODE 3 is reached within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, the time allowed for reaching MODE 4 is the next 30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> because the total time allowed for reaching MODE 4 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 4 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. (continued) 1.3-3 Amendment No.
LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 HATCH UNIT 1 c. management actions, if appropriate (exceptions to this specification are stated in the individual Specifications);
or When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY, or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing. When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.10, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Special Operations LCOs is optional.
When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.
3.0-2 (continued)
Amendment No.
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 HATCH UNIT 1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
I If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed > 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 (continued)
Amendment No.
Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION HATCH UNIT2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating, " Required Action B.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability. (continued) 1.3-1 Amendment No.
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
- a. HATCH UNIT 2 If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.
Once a Condition has been entered, subsequent divisions, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:
Must exist concurrent with the first inoperability; and 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. (continued) 1.3-2 Amendment No.
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
EXAMPLES HATCH UNIT 2 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
... " The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE 1.3-1 ACTIONS CONDITION B. Required Action and associated Completion Time not met. REQUIRED ACTION COMPLETION TIME 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 /> 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 /> Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition Bis entered. The Required Actions of Condition B are to be in MODE 3 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> AND in MODE 4 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br />) is allowed for reaching MODE 4 from the time that Condition B was entered. If MODE 3 is reached within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />, the time allowed for reaching MODE 4 is the next 30 hours3.472222e-4 days <br />0.00833 hours <br />4.960317e-5 weeks <br />1.1415e-5 months <br /> because the total time allowed for reaching MODE 4 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 4 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. (continued) 1.3-3 Amendment No.
SR Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 LCO 3.0.7 HATCH UNIT2 c. management actions, if appropriate (exceptions to this specification are stated in the individual Specifications);
or When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY, or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing. When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.10, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. Special Operations LCOs in Section 3.1 O allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations.
Unless otherwise specified, all other TS requirements remain unchanged.
Compliance with Special Operations LCOs is optional.
When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.
3.0-2 (continued)
Amendment No.
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 HATCH UNIT 2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed > 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 (continued)
Amendment No.
Completion Times 1.3 1.0 USE AND APPLICATION
1.3 Completion
Times PURPOSE BACKGROUND DESCRIPTION Vogtle Units 1 and 2 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use. Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s). The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Unless otherwise specified, the Completion Time begins when a senior licensed operator on the operating shift crew with responsibility for plant operations makes the determination that an LCO is not met and an ACTIONS Condition is entered. The "otherwise specified" exceptions are varied, such as a Required Action Note or Surveillance Requirement Note that provides an alternative time to perform specific tasks, such as testing, without starting the Completion Time. While utilizing the Note, should a Condition be applicable for any reason not addressed by the Note, the Completion Time begins. Should the time allowance in the Note be exceeded, the Completion Time begins at that point. The exceptions may also be incorporated into the Completion Time. For example, LCO 3.8.1, "AC Sources -Operating, " Required Action 8.2, requires declaring required feature(s) supported by an inoperable diesel generator, inoperable when the redundant required feature(s) are inoperable.
The Completion Time states, "4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> from discovery of Condition B concurrent with inoperability of redundant required feature(s)." In this case* the Completion Time does not begin until the conditions in the Completion Time are satisfied.
Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.
1.3-1 Amendment No. Amendment No. (continued) (Unit 1) (Unit 2)
Completion Times 1.3 1.3 Completion Times DESCRIPTION continued)
Vogtle Units 1 and 2 If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the discovery of the situation that required entry into the Condition, unless otherwise specified.
Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition, unless otherwise specified.
However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended.
To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:
- a. Must exist concurrent with the first inoperability; and 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 extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, 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.
1.3-2 (continued)
Amendment No. Amendment No. (Unit 1) (Unit 2)
Completion Times 1.3 1.3 Completion Times DESCRIPTION (continued)
EXAMPLES Vogtle Units 1 and 2 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
... " The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE 1.3-1 COMPLETION TIMES ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required B.1 Be in MODE 3. 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Action and associated AND Completion Time not B.2 Be in MODE 5. 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> met. Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered. The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. 1.3-3 (continued)
Amendment No. Amendment No. (Unit 1) (Unit 2)
LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 (continued)
LCO 3.0.5 LCO 3.0.6 Vogtle Units 1 and 2 b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications);
or c. When an allowance is stated in the individual value, parameter, or other Specification.
This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit. Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment.
This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.
When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.15, "Safety Function Determination Program (SFDP)." 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 support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2. 3.0-2 Amendment No. Amendment No. (continued) (Unit 1) (Unit 2)
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SR 3.0.2 SR 3.0.3 Vogtle Units 1 and 2 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once," the above interval extension does not apply. If a Completion Time requires periodic performance on a "once per ... " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance.
The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed.
A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered. 3.0-4 Amendment No. Amendment No. (continued) (Unit 1) (Unit 2)
Joseph M. Farley Nuclear Plant, Units 1 and 2 Edwin I. Hatch Nuclear Plant, Units 1 and 2 Vogtle Electric Generating Plant, Units 1 and 2 License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Revision 4, "Clarify Use and Application Rules" Enclosure 4 FNP, HNP, and VEGP Technical Specification Bases Marked Up Pages (For Information Only)
LCO Applicability B 3.0 B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LC Os LCO 3.0.1 LCO 3.0.2 Farley Units 1 and 2 LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated. LCO 3.0.1 establishes the Applicability statement within each individual Specification as the requirement for when the LCO is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Specification).
LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered. unless otherwise specified.
The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that: a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification; and
- b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as *a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.)
The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further (continued)
B 3.0-1 Revision 35 BASES LCO 3.0.3 Farley Units 1 and 2 LCO Applicability B 3.0 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and: a. An associated Required Action and Completion Time is not met and no other Condition applies; or b.
- The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering LCO 3.0.3 is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that LCO 3.0.3 be entered immediately.
This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.
Upon entering LCO 3.0.3, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to prepare for an orderly shutdown before initiating a change in unit operation.
This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The time limits specified to enter feaGA-lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE.
This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, Completion Times. A unit shutdown required in accordance with LCO 3.0.3 may be terminated and LCO 3.0.3 exited if any of the following occurs: a. The LCO is now met. b. The LCO is no longer applicable, (continued)
B 3.0-3 Revision O BASES LCO 3.0.3 (continued)
Farley Units 1 and 2 LCO Applicability B 3.0 tr..c. A Condition exists for which the Required Actions have now been performed.
&;-d. ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time LCO 3.0.3 is exited. The time limits of Specification
3.0.3 allow
37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br /> for the unit to be in MODE 5 when a shutdown is required during MODE 1 operation.
If the unit is in a lower MODE of operation when a shutdown is required, the time limit for i=easRentering the next lower MODE applies. If a lower MODE is fea6Rentered in less time than allowed, however, the total allowable time to reach enter MODE 5, or other applicable MODE, is not reduced. For example, if MODE 3 is reachentered in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, then the time allowed for t=eaGAentering MODE 4 is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br />, because the total time for t=eaGAentering MODE 4 is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />. Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to reach enter a lower MODE of operation in less than the total time allowed. In MODES 1, 2, 3, and 4, LCO 3.0.3 provides actions for Conditions not covered in other Specifications.
The requirements of LCO 3.0.3 do not apply in MODES 5 and 6 because the unit is already in the most restrictive Condition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, 3, or 4) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken. Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.13, "Fuel Storage Pool Water Level." LCO 3.7.13 has an Applicability of "During movement of irradiated fuel assemblies in the fuel storage pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.13 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition.
The Required Action of LCO 3.7.13 of "Suspend movement of irradiated fuel assemblies in the fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications.
B 3.0-4 Revision O BASES LCO 3.0.4 Farley Units 1 and 2 LCO Applicability B 3.0 LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the LCO would not be met, in accordance with either LCO 3.0.4a, LCO 3.0.4b, or LCO 3.0.4c. LCO 3.0.4a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into permit continued operation in the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation.
This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entry into the Applicabilityin accordance 1 Nith the provisions of the Required Actions. For example. LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified in condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequently placed in the tripped condition within the Completion Time, which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation, use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered. LCO 3.0.4b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.
The risk assessment may use quantitative, qualitative, or blended approaches, and the risk assessment will be conducted using the plant program, procedures, and criteria in place to implement 10 CFR B 3.0-5 Revision 33 BASES LCO 3.0.4 (continued)
Farley Units 1 and 2 LCO Applicability B 3.0 personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and determination that the proposed MODE change is acceptable.
Consideration should also be given to the probability of completing restoration such that the requirements of the LCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.
LCO 3.0.4b may be used with single, or multiple systems and components unavailable.
NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.
The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The LCO 3.0.4b risk assessments do not have to be documented.
The Technical Specifications allow continued operation with equipment unavailable in MODE 1 for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular MODE bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the LCO, the use of the LCO 3.0.4b allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, there is a small subset of systems and components that have been determined to be more important to risk and use of the LCO 3.0.4b allowance is prohibited.
The LCOs governing these systems and components contain Notes prohibiting the use of LCO 3.0.4b by stating that LCO 3.0.4b is not applicable.
LCO 3.0.4c allows entry into a MODE or other specified condition in the Applicability with the LCO not met based on a Note in the Specification which states LCO 3.0.4c is applicable.
These specific allowances permit entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered do not provide for continued operation for an unlimited period of time and a risk assessment has not been performed.
This allowance may apply to all the ACTIONS or to a specific Required Action of a Specification.
The risk assessments performed to justify the use of LCO 3.0.4b usually only consider systems and components.
For this reason, LCO 3.0.4c is typically applied to Specifications which describe values and parameters (e.g., RCS Specific ActivityContainment Air Temperature, Containment Pressure, Moderator Temperature B 3.0-7 Revision 33 BASES LCO 3.0.4 (continued)
LCO 3.0.5 Farley Units 1 and 2 LCO Applicability B 3.0 Coefficient}, and may be applied to other Specifications based on NRC plant-specific approval.
The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.
The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown.
In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, MODE 3 to MODE 4, and MODE 4 to MODE 5. Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the Technical Specification.
Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment.
However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected LCO. LCO 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s))
to allow the performance of required testing to demonstrate:
- a. The OPERABILITY of the equipment being returned to service; or b. The OPERABILITY of other equipment. (continued)
B 3.0-9 Revision 33 BASES LCO 3.0.5 (continued)
Farley Units 1 and 2 LCO Applicability B 3.0 The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the required testing to demonstrate OPERABILITY.
This Specification does not provide time to perform any other preventive or corrective maintenance.
LCO 3.0.5 should not be used in lieu of other practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE.
LCO 3.0.5 is not intended to be used repeatedly.
An example of demonstrating equipment is OPERABLE with the Required Actions not met is opening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System (RCS) Pressure Isolation Valve (PIV) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit. An example of demonstrating the OPERABILITY of the equipment being returned to service is reopening a containment isolation valve that has been closed to comply *.vith Required Actions and must be reopened to perform the required testing. Examples of demonstrating equipment OPERABILITY include instances in which it is necessarv to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action. if there is no Required Action Note for this pumose. An example of veritving OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples An example of demonstrating the OPERABILITY of other equipment areffi taking an inoperable channel or trip system out of the tripped condition 1Lto prevent the trip function from occurring during the performance of required testing on another channel in the other trip A similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response during the performance of required testing on another channel in the same trip system. The administrative controls in LCO 3.0.5 apply in all cases to systems or components in Chapter 3 of the Technical Specifications.
as long as the testing could not be conducted while complying with the Required Actions. This includes the realignment or repositioning of redundant or alternate equipment or trains previously manipulated to comply with ACTIONS. as well as equipment removed from service or declared inoperable to comply with ACTIONS. B3.0-10 Revision 33 BASES SR 3.0.2 (continued)
SR 3.0.3 Farley Units 1 and 2 SR Applicability B 3.0 As stated in SR 3.0.2, the 25% extension also does not apply to the initial portion of a periodic Completion Time that requires performance on a "once per ... " basis. The 25% extension applies to each performance after the initial performance.
The initial performance of the Required Action, whether it is a particular Surveillance or some other remedial action, is considered a single action with a single Completion Time. One reason for not allowing the 25% extension to this Completion Time is that such an action usually verifies that no loss of function has occurred by checking the status of redundant or diverse components or accomplishes the function of the inoperable equipment in an alternative manner. The provisions of SR 3.0.2 are not intended to be used repeatedly merely as an operational convenience to extend Surveillance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified.
SR 3.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been completed performed within the specified Frequency.
A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met. This delay period provides adequate time to perform complete Surveillances that have been missed. This delay period permits the performance completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude performance completion of the Surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the Surveillance, the safety significance of the delay in completing the required Surveillance, and the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements.
B 3.0-18 Revision 35 BASES SR 3.0.3 (continued)
Farley Units 1 and 2 SR Applicability B 3.0 When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance.
However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.
SR 3.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions. SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits, and it is expected that the Surveillance will be met when performed.
Many factors should be considered such as the period of time since the Surveillance was last performed.
or whether the Surveillance.
or a portion thereof, has ever been performed, and any other indications, tests, or activities that might support the expectation that the Surveillance will be met when performed.
An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR. but previous successful performances of the SR included the relay contact: the adjacent.
physically connected relay contacts were tested during the SR performance:
the subject relay contact has been tested by another SR: or historical operation of the subject relay contact has been successful.
It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment.
The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance.
If the Surveillance has been performed recently.
a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.
For Surveillances that have not been performed for a long period or that have never been performed, a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is OPERABLE.
The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.
Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence.
Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used repeatedly as--aA operational B 3.0-20 Revision 35 Farley Units 1 and 2 SR Applicability 8 3.0 convenience to extend Surveillance intervals.
While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity.
The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance.
This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRG Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." The Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown.
The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component.
Missed Surveillances for important components should be analyzed quantitatively.
If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program. (continued) 8 3.0-21 Revision 35 LCO Applicability
- B 3.0 B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LCOs *-LCO 3.0.1 LCO 3.0.2 HATCH UNIT 1 LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated. LCO 3.0.1 establishes the Applicability statement within each individual Specification as the requirement for when the LCO is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Specification).
LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered, unless otherwise specified.
The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that: a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification; and b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.)
The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this (continued)
B 3.0-1 REVISION 52 BASES (continued)
LCO 3.0.3 HATCH UNIT 1 LCO Applicability B 3.0 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and: a. An associated Required Action and Completion Time is not met and no other Condition applies; or b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering LCO 3.0.3 is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that LCO 3.0.3 be entered immediately.
This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.
Upon entering LCO 3.0.3, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to prepare for an orderly shutdown before initiating a change in unit operation.
This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The time limits specified to raaffi enter lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE.
This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, "Completion Times." A unit shutdown required in accordance with LCO 3.0.3 may be terminated and LCO 3.0.3 exited if any of the following occurs: a. The LCO is now met. b. The LCO is no longer applicable, (continued)
B 3.0-3 REVISION 0 BASES LCO 3.0.3 (continued)
HATCH UNIT 1 LCO Applicability B 3.0 c.b-:-A Condition exists for which the Required Actions have now been performed.
d.s-:-ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time LCO 3.0.3 is exited. The time limits of Specification
3.0.3 allow
37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br /> for the unit to be in MODE 4 when a shutdown is required during MODE 1 operation.
If the unit is in a lower MODE of operation when a shutdown is required, the time limit for reaffientering the next lower MODE applies. If a lower MODE is reachentered in less time than allowed, however, the total allowable time to reach enter MODE 4, or other applicable MODE, is not reduced. For example, if MODE 2 is reachentered in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, then the time allowed for reaffientering MODE 3 is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br />, because the total time for reaffientering MODE 3 is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />. Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to reaffi...enter a lower MODE of operation in less than the total time allowed. In MODES 1, 2, and 3, LCO 3.0.3 provides actions for Conditions not covered in other Specifications.
The requirements of LCO 3.0.3 do not apply in MODES 4 and 5 because the unit is already in the most restrictive Condition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken. Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.8, "Spent Fuel Storage Pool Water Level." LCO 3.7.8 has an Applicability of "During movement of irradiated fuel assemblies in the spent fuel storage pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.8 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition.
The Required Action of LCO 3.7.8 of "Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications. (continued)
B 3.0-4 REVISION 0 BASES (continued)
LCO 3.0.4 HATCH UNIT 1 LCO Applicability B 3.0 LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the LCO would not be met, in accordance with either LCO 3.0.4.a, LCO 3.0.4.b, or LCO 3.0.4.c. LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into permit continued operation in the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation.
This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entrv into the Applicabilityin accordance
'Nith the provisions in the Required /\ctions.
For example LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequently placed in the tripped condition within the Completion Time. which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation, use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entrv into the MODE include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered. LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.
The risk assessment may use quantitative, qualitative, or blended approaches, and the risk assessment will be conducted using the (continued)
B 3.0-5 REVISION 49 BASES LCO 3.0.4 (continued)
HATCH UNIT 1 LCO Applicability B 3.0 condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and determination that the proposed MODE change is acceptable.
Consideration should also be given to the probability of completing restoration such that the requirements of the LCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.
LCO 3.0.4.b may be used with single or multiple systems and components unavailable.
NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.
The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The LCO 3.0.4.b risk assessments do not have to be documented.
The Technical Specifications allow continued operation with equipment unavailable in MODE 1 for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular mode bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the LCO, the use of the LCO 3.0.4.b allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, there is a small subset of systems and components that have been determined to be more important to risk, and use of the LCO 3.0.4.b is prohibited.
The LCOs governing these systems and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is not applicable.
LCO 3.0.4.c allows entry into a MODE or other specified condition of the Applicability with the LCO not met based on a Note in the Specification which states LCO 3.0.4.c is applicable.
These specific allowances permit entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered do not provide for continued operation for an unlimited period of time and a risk assessment has not been performed.
This allowance may apply to all the ACTIONS or to a specific Required Action of a Specification.
The risk assessments performed to justify the use of LCO 3.0.4.b usually only consider systems and components.
For this reason, LCO 3.0.4.c is typically applied to Specifications which describe values and parameters (e.g., RCS Specific ActivityDF)well Air Temperature, Dryv1ell Pressure, MCPR) and may be applied to other Specifications based on NRG plant-specific approval. (continued)
B 3.0-7 REVISION 49 BASES LCO 3.0.4 (continued)
LCO 3.0.5 HATCH UNIT 1 LCO Applicability B 3.0 The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.
The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown.
In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4. Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the Technical Specification.
Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits) as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment.
However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected LCO. LCO 3.0.5 establishes the allowance for restoring' equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 [e.g., to not comply with the applicable Required Action(s)]
to allow the performance of SRs to demonstrate:
- a. The OPERABILITY of the equipment being returned to service; or b. The OPERABILITY of other equipment.
The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance.
LCO 3.0.5 should not be used in lieu of other (continued)
B 3.0-8 REVISION 49 HATCH UNIT 1 LCO Applicability B 3.0 practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE.
LCO 3.0.5 is not intended to be used repeatedly.
An example of demonstrating equipment is OPERABLE with the Required Actions not met is opening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System <RCS) Pressure Isolation Valve (PIV) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit. (continued)
B 3.0-9 REVISION 49 BASES LCO 3.0.5 (continued)
LCO 3.0.6 HATCH UNIT 1 LCO Applicability B 3.0 /\n example of demonstrating the OPERABILITY of the equipment being returned to service is reopening a containment isolation valve that has been closed to comply with Required Actions and must be reopened to perform the SRs. Examples of demonstrating equipment OPERABILITY include instances in which it is necessary to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action. if there is no Required Action Note for this pumose. An example of veritving OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples An example of demonstrating the OPERABILITY of other equipment arei-s taking an inoperable channel or trip system out of the tripped condition 1Lto prevent the trip function from occurring during the performance of an SR on another channel in the other trip or 2). A similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response during the performance of an SR on another channel in the same trip system. The administrative controls in LCO 3.0.5 apply in all cases to systems or components in Chapter 3 of the Technical Specifications.
as long as the testing could not be conducted while complying with the Required Actions. This includes the realignment or repositioning of redundant or alternate equipment or trains previously manipulated to comply with ACTIONS. as well as equipment removed from service or declared inoperable to comply with ACTIONS. LCO 3.0.6 establishes an exception to LCO 3.0.2 for support systems that have an LCO specified in the Technical Specifications (TS). This exception is provided because LCO 3.0.2 would require that the Conditions and Required Actions of the associated inoperable supported system LCO be entered solely due to the inoperability of the support system. This exception is justified because the actions that are required to ensure the plant is maintained in a safe condition are specified in the support system LCO's Required Actions. These Required Actions may include entering the supported system's Conditions and Required Actions or may specify other Required Actions. When a support system is inoperable and there is an LCO specified for it in the TS, the supported system(s) are required to be declared inoperable if determined to be inoperable as a result of the support (continued)
B 3.0-10 REVISION 49 BASES SR 3.0.2 (continued)
SR 3.0.3 HATCH UNIT 1 SR Applicability B 3.0 precedence over the TS. Therefore, when a test interval is specified in the regulations, the test interval cannot be extended by the TS, and the SR includes a Note in the Frequency stating, "SR 3.0.2 is not applicable." An example of an exception when the test interval is specified in the regulations is the Note in the Primary Containment Leakage Rate Testing Program, "SR 3.0.2 is not applicable." This exception is provided because the program already includes extension of test intervals.
As stated in SR 3.0.2, the 25% extension also does not apply to the initial portion of a periodic Completion Time that requires performance on a "once per. .. " basis. The 25% extension applies to each performance after the initial performance.
The initial performance of the Required Action, whether it is a particular Surveillance or some other remedial action, is considered a single action with a single Completion Time. One reason for not allowing the 25% extension to this Completion Time is that such an action usually verifies that no loss of function has occurred by checking the status of redundant or diverse components or accomplishes the function of the inoperable equipment in an alternative manner. The provisions of SR 3.0.2 are not intended to be used repeatedly, merely as an operational convenience to extend Surveillance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified.
SR 3.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been performed completed within the specified Frequency.
A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met. This delay period provides adequate time to complete perform Surveillances that have been missed. This delay period permits the performance completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude performance completion of the Surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the Surveillance, the safety significance of the delay in completing the required Surveillance, and the recognition that (continued)
B 3.0-17 REVISION 52 BASES SR 3.0.3 (continued)
HATCH UNIT 1 SR Applicability B 3.0 the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements.
When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance.
However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.
SR 3.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions. SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits. and it is expected that the Surveillance will be met when performed.
Many factors should be considered.
such as the period of time since the Surveillance was last performed or whether the Surveillance.
or a portion thereof. has ever been performed.
and any other indications.
tests. or activities that might support the expectation that the Surveillance will be met when performed.
An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR. but previous successful performances of the SR included the relay contact: the adjacent.
physically connected relay contacts were tested during the SR performance:
the subject relay contact has been tested by another SR: or historical operation of the subject relay contact has been successful.
It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment.
The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance.
If the Surveillance has been performed recently.
a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.
For Surveillances that have not been performed for a long period or that have never been performed.
a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is OPERABLE.
The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.
Failure to comply with specified Frequencies for SRs is expected to (continued)
B 3.0-18 REVISION 52 BASES SR 3.0.3 (continued)
SR 3.0.4 HATCH UNIT 1 SR Applicability B 3.0 be an infrequent occurrence.
Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used repeatedly as an operational convenience to extend Surveillance intervals.
While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity.
The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance.
This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown.
The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component.
Missed Surveillances for important components should be analyzed quantitatively.
If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program. If a Surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the variable is considered outside the specified limits and the Completion Times of the Required Actions for the applicable LCO Conditions begin immediately upon expiration of the delay period. If a Surveillance is failed within the delay period, then the equipment is inoperable, or the variable is outside the specified limits and the Completion Times of the Required Actions for the applicable LCO Conditions begin immediately upon the failure of the Surveillance.
Completion of the Surveillance within the delay period allowed by this Specification, or within the Completion Time of the ACTIONS, restores compliance with SR 3.0.1. SR 3.0.4 establishes the requirement that all applicable SRs must be met before entry into a MODE or other specified condition in the (continued)
B 3.0-19 REVISION 52 LCO Applicability B 3.0 B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LCOs LCO 3.0.1 LCO 3.0.2 HATCH UNIT 2 LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated. LCO 3.0.1 establishes the Applicability statement within each individual Specification as the requirement for when the LCO is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Specification).
LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered, unless otherwise specified.
The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that: a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification; .and b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or a condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.)
The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this (continued)
B 3.0-1 REVISION 58 BASES (continued)
LCO 3.0.3 HATCH UNIT2 LCO Applicability B 3.0* LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and: a. An associated Required Action and Completion Time is not met and no other Condition applies; or b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering LCO 3.0.3 is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that LCO 3.0.3 be entered immediately.
This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.
Upon entering LCO 3.0.3, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to prepare for an orderly shutdown before initiating a change in unit operation.
This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The time limits specified to f0affi enter lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE.
This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, "Completion Times." A unit shutdown required in accordance with LCO 3.0.3 may be terminated and LCO 3.0.3 exited if any of the following occurs: a. The LCO is now met. b. The LCO is no longer applicable. (continued)
B 3.0-3 REVISION 0 BASES LCO 3.0.3 (continued)
HATCH UNIT 2 LCO Applicability B 3.0 c.&.. A Condition exists for which the Required Actions have now been performed.
d.&.-ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time LCO 3.0.3 is exited. The time limits of Specification
3.0.3 allow
37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br /> for the unit to be in MODE 4 when a shutdown is required during MODE 1 operation.
If the unit is in a lower MODE of operation when a shutdown is required, the time limit for reachentering the next lower MODE applies. If a lower MODE is fea6Rentered in less time than allowed, however, the total allowable time to reach enter MODE 4, or other applicable MODE, is not reduced. For example, if MODE 2 is reachentered in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, then the time allowed for fea6Rentering MODE 3 is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br />, because the total time for reachentering MODE 3 is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />. Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to--f08*Renter a lower MODE of operation in less than the total time allowed. In MODES 1, 2, and 3, LCO 3.0.3 provides actions for Conditions not covered in other Specifications.
The requirements of LCO 3.0.3 do not apply in MODES 4 and 5 because the unit is already in the most restrictive Condition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken. Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.8, "Spent Fuel Storage Pool Water Level." LCO 3.7.8 has an Applicability of "During movement of irradiated fuel assemblies in the spent fuel storage pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.8 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition.
The Required Action of LCO 3.7.8 of "Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications. (continued)
B 3.0-4 REVISION 55 BASES (continued)
LCO 3.0.4 HATCH UNIT 2 LCO Applicability B 3.0 LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the LCO would not be met, in accordance with either LCO 3.0.4.a, LCO 3.0.4.b, or LCO 3.0.4.c. LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into permit continued operation in the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS Required /\ctions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation.
This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entrv into the Applicabilityin accordance with the provisions in the Required Actions. For example. LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequently placed in the tripped condition within the Completion Time. which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation.
use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered. LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.
The risk assessment may use quantitative, qualitative, or blended approaches, and the risk assessment will be conducted using the (continued)
B 3.0-5 REVISION 55 BASES LCO 3.0.4 (continued)
HATCH UNIT2 LCO Applicability B 3.0 condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and determination that the proposed MODE change is acceptable.
Consideration should also be given to the probability of completing restoration such that the requirements of the LCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.
LCO 3.0.4.b may be used with single or multiple systems and components unavailable.
NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.
The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The LCO 3.0.4.b risk assessments do not have to be documented.
The Technical Specifications allow continued operation with equipment unavailable in MODE 1 for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular mode bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the LCO, the use of the LCO 3.0.4.b allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, there is a small subset of systems and components that have been determined to be more important to risk, and use of the LCO 3.0.4.b is prohibited.
The LCOs governing these systems and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is not applicable.
LCO 3.0.4.c allows entry into a MODE or other specified condition of the Applicability with the LCO not met based on a Note in the Specification which states LCO 3.0.4.c is applicable.
These specific allowances permit entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered do not provide for continued operation for an unlimited period of time and a risk assessment has not been performed.
This allowance may apply to all the ACTIONS or to a specific Required Action of a Specification.
The risk assessments performed to justify the use of LCO 3.0.4.b usually only consider systems and components.
For this reason, LCO 3.0.4.c is typically applied to Specifications which describe values and parameters (e.g., RCS Specific ActivityDrywell Air Temperature, Drywell Pressure, MCRP) and may be applied to other Specifications based on NRC plant-specific approval. (continued)
B 3.0-7 REVISION 55 BASES LCO 3.0.4 (continued)
LCO 3.0.5 HATCH UNIT 2 LCO Applicability B 3.0 The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.
The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown.
In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4. Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the Technical Specification.
Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits) as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment.
However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (of variable within limits) and restoring compliance with the affected LCO. LCO 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 [e.g., to not comply with the applicable Required Action(s)]
to allow the performance of SRs to demonstrate:
- a. The OPERABILITY of the equipment being returned to service; or b. The OPERABILITY of other equipment.
The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance.
LCO 3.0.5 should not be used in lieu of other (continued)
B 3.0-8 REVISION 55 BASES LCO 3.0.5 (continued)
LCO 3.0.6 HATCH UNIT 2 LCO Applicability B 3.0 practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE.
LCO 3.0.5 is not intended to be used repeatedly.
An example of demonstrating equipment is OPERABLE with the Required Actions not met is opening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System <RCS) Pressure Isolation Valve (PIV) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit. An example of demonstrating the OPERABILITY of the equipment being returned to service is reopening a containment isolation valve that has been closed to comply *.vith Required Actions and must be reopened to perform the SRs. Examples of demonstrating equipment OPERABILITY include instances in which it is necessarv to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action. if there is no Required Action Note for this puroose. An example of veritving OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples An example of demonstrating the OPERABILITY of other equipment areffi taking an inoperable channel or trip system out of the tripped condition jj)o prevent the trip function from occurring during the performance of an SR on another channel in the other trip system. or A similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response during the performance of an SR on another channel in the same trip system. The administrative controls in LCO 3.0.5 apply in all cases to systems or components in Chapter 3 of the Technical Specifications.
as long as the testing could not be conducted while complying with the Required Actions. This includes the realignment or repositioning of redundant or alternate equipment or trains previously manipulated to comply with ACTIONS. as well as equipment removed from service or declared inoperable to comply with ACTIONS. LCO 3.0.6 establishes an exception to LCO 3.0.2 for support systems that have an LCO specified in the Technical Specifications (TS). This exception is provided because LCO 3.0.2 would require that the Conditions and Required Actions of the associated inoperable (continued)
B 3.0-9 REVISION 55 BASES SR 3.0.2 (continued)
SR 3.0.3 HATCH UNIT 2 SR Applicability B 3.0 precedence over the TS. Therefore, when a test interval is specified in the regulations, the test interval cannot be extended by the TS, and the SR includes a Note in the Frequency stating, "SR 3.0.2 is not applicable." An example of an exception when the test interval is specified in the regulations is the Note in the Primary Containment Leakage Rate Testing Program, "SR 3.0.2 is not applicable." This exception is provided because the program already includes extension of test intervals.
As stated in SR 3.0.2, the 25% extension also does not apply to the initial portion of a periodic Completion Time that requires performance on a "once per. .. " basis. The 25% extension applies to each performance after the initial performance.
The initial performance of the Required Action, whether it is a particular Surveillance or some other remedial action, is considered a single action with a single Completion Time. One reason for not allowing the 25% extension to this Completion Time is that such an action usually verifies that no loss of function has occurred by checking the status of redundant or diverse components or accomplishes the function of the inoperable equipment in an alternative manner. The provisions of SR 3.0.2 are not intended to be used repeatedly, merely as an operational convenience to extend Surveillance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified.
SR 3.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been performed completed within the specified Frequency.
A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met. This delay period provides adequate time to complete perform Surveillances that have been missed. This delay period permits the performance completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude performance completion of the Surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the Surveillance, the safety significance of the delay in completing the required Surveillance, and the recognition that (continued)
B 3.0-16 REVISION 58 BASES SR 3.0.3 (continued)
HATCH UNIT 2 SR Applicability B 3.0 the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements.
When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance.
However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.
SR 3.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions. SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits, and it is expected that the Surveillance will be met when performed.
Many factors should be considered, such as the period of time since the Surveillance was last performed, or whether the Surveillance, or a portion thereof, has ever been performed, and any other indications.
tests, or activities that might support the expectation that the Surveillance will be met when performed.
An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR. but previous successful performances of the SR included the relay contact: the adjacent, physically connected relay contacts were tested during the SR performance:
the subject relay contact has been tested by another SR: or historical operation of the subject relay contact has been successful.
It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance.
If the Surveillance has been performed recently.
a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.
For Surveillances that have not been performed for a long period or that have never been performed, a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is OPERABLE.
The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination. (continued)
B 3.0-17 REVISION 58 HATCH UNIT 2 SR Applicability 8 3.0 Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence.
Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used repeatedly as an operational convenience to extend Surveillance intervals.
While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity.
The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance.
This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown.
The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component.
Missed Surveillances for important components should be analyzed quantitatively.
If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program. (continued) 8 3.0-18 REVISION 58 LCO Applicability 8 3.0 8 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LC Os LCO 3.0.1 LCO 3.0.2 Vogtle Units 1 and 2 LCO 3.0.1 through LCO 3.0.9 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated. LCO 3.0.1 establishes the Applicability statement within each individual Specification as the requirement for when the LCO is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Specification).
LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered, unless otherwise specified.
The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that: a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification; and b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering (continued)
B 3.0-1 Rev. 1-9/06 BASES LCO 3.0.3 Vogtle Units 1 and 2 LCO Applicability B 3.0 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and: a. An associated Required Action and Completion Time is not met and no other Condition applies; or b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering LCO 3.0.3 is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that LCO 3.0.3 be entered immediately.
This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.
Upon entering LCO 3.0.3, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to prepare for an orderly shutdown before initiating a change in unit operation.
This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The time limits specified to enter feaGl:l-.lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE.
This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, Completion Times. (continued)
B 3.0-3 Revision No. O BASES LCO 3.0.3 (continued)
Vogtle Units 1 and 2 LCO Applicability B 3.0 A unit shutdown required in accordance with LCO 3.0.3 may be terminated and LCO 3.0.3 exited if any of the following occurs: a. The LCO is now met. b. The LCO is no longer applicable.
&.-c. A Condition exists for which the Required Actions have now been performed.
Er.Cl. ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time LCO 3.0.3 is exited. The time limits of Specification
3.0.3 allow
37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br /> for the unit to be in MODE 5 when a shutdown is required during MODE 1 operation.
If the unit is in a lower MODE of operation when a shutdown is required, the time limit for feaffientering the next lower MODE applies. If a lower MODE is reachentered in less time than allowed, however, the total allowable time toreach enter MODE 5, or other applicable MODE, is not reduced. For example, if MODE 3 is reachentered in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, then the time allowed for feaffientering MODE 4 is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br />, because the total time for feaffientering MODE 4 is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />. Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to feaGA-.enter a lower MODE of operation in less than the total time allowed. In MODES 1, 2, 3, and 4, LCO 3.0.3 provides actions for Conditions not covered in other Specifications.
The requirements of LCO 3.0.3 do not apply in MODES 5 and 6 because the unit is already in the most restrictive Condition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, 3, or 4) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken. Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.15, "Fuel Storage Pool Water Level." LCO 3.7.15 has (continued)
B 3.0-4 Revision No. O BASES LCO 3.0.3 (continued)
LCO 3.0.4 Vogtle Units 1 and 2 an Applicability of "During movement of irradiated fuel LCO Applicability B 3.0 assemblies in the fuel storage pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3. 7 .15 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition.
The Required Action of LCO 3. 7.15 of "Suspend movement of irradiated fuel assemblies in the fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications.
LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requirements of the LCO would not be met, in accordance with either LCO 3.0.4a, LCO 3.0.4b, or LCO 3.0.4c. LCO 3.04a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into permit continued operation in the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation.
This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entry into the Applicability in accordance with the provisions of the Required Actions. For example, LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified in condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequently placed in the tripped condition within the Completion Time, which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation, use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entrv into the MODE include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered. LCO 3.0.4b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk (continued)
B 3.0-5 Rev. 2-6/05 NOTE This page has been included in the package to demonstrate that the change outlined in LCO Applicability revision 4 of TSTF-529, to modify the last *sentence in the first paragraph, was B 3.0 completed under an earlier amendment to the Vogtle Technical Specifications.
BASES LCO 3.0.4 (continued)
Vogtle Units 1 and 2 continued operation for an unlimited period of time and a risk assessment has not been performed.
This allowance may apply to all ACTIONS or to a specific Required Action of a Specification.
The risk assessments performed to justify the use of LCO 3.0.4b usually only consider systems and components.
For this reason, LCO 3.0.4c is typically applied to Specifications which describe values and parameters (e.g., RCS Specific Activity), and may be applied to other Specifications based on NRC plant-specific approval.
The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good praCtice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.
The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown.
In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, MODE 3 to MODE 4, and MODE 4 to MODE 5. Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the Condition is resolved, the LCO is met, or the unit is not within the Applicability of the Technical Specification.
Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment.
However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected LCO. (continued)
B 3.0-8 Rev. 2-6/05 BASES (continued)
LCO 3.0.5 Vogtle Units 1 and 2 LCO Applicability B 3.0 LCO 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s))
to allow the performance of SRs to demonstrate:
- a. The OPERABILITY of the equipment being returned to service; or or b. The OPERABILITY of other equipment.
The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance.
LCO 3.0.5 should not be used in lieu of other practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE.
LCO 3.0.5 is not intended to be used repeatedly.
An example of demonstrating equipment is OPERABLE with the Required Actions not met is opening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System (RCS) Pressure Isolation Valve (PIV) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit. An example of demonstrating the OPERABILITY of the equipment being returned to service is reopening a containment isolation valve that has been closed to comply *nith Required Actions and must be reopened to perform the SRs. Examples of demonstrating equipment OPERABILITY include instances in which it is necessarv to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action, if there is no Required Action Note for this purnose. An example of verifying OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples An example of demonstrating the OPERABILITY of other equipment areffi taking an inoperable channel or trip system out of the tripped condition jlto prevent the trip function from occurring during the performance of an SR on another channel in the other trip J\ similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response (continued)
B 3.0-9 Rev. 1 -6/05 LCO 3.0.6 Vogtle Units 1 and 2 LCO Applicability B 3.0 during the performance of an SR on another channel in the same trip system. The administrative controls in LCO 3.0.5 apply in all cases to systems or components in Chapter 3 of the Technical Specifications.
as long as the testing could not be conducted while complying with the Required Actions. This includes the realignment or repositioning of redundant or alternate equipment or trains previously manipulated to comply with ACTIONS. as well as equipment removed from service or declared inoperable to comply with ACTIONS. LCO 3.0.6 establishes an exception to LCO 3.0.2 for support systems that have an LCO specified in the Technical Specifications (TS). This exception is provided because LCO 3.0.2 would require that the Conditions and Required Actions of the associated inoperable supported system LCO be entered solely due to the inoperability of the support system. This exception is justified because the actions that are required to ensure the unit is maintained in a safe condition are specified in the support system LCO's Required Actions. These Required Actions may include entering the supported system's Conditions and Required Actions or may specify other Required Actions. (continued)
B 3.0-10 Rev. 1 -6/05 BASES SR 3.0.2 (continued)
SR 3.0.3 Vogtle Units 1 and 2 SR Applicability B 3.0 The provisions of SR 3.0.2 are not intended to be used repeatedly merely as an operational convenience to extend Surveillance intervals (other than those consistent with Refueling intervals) or periodic Completion Time intervals beyond those specified.
SR 3.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been completed performed within the specified Frequency.
A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met. This delay period provides adequate time to perform complete Surveillances that have been missed. This delay period permits the performance completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude performance completion of the Surveillance.
The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the Surveillance, the safety significance of the delay in completing the required Surveillance, and the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements.
When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 1 O CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance.
However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.
SR 3.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions. SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits. and it is expected that the Surveillance will be met when performed.
Many factors should be considered, such as the period of time since the Surveillance was last performed.
or whether the Surveillance.
or a portion thereof. has ever been performed.
and any other indications.
tests. or activities that might support the (continued)
B 3.0-17 Rev. 4-9/06 Vogtle Units 1 and 2 SR Applicability B 3.0 expectation that the Surveillance will be met when performed.
An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR. but previous successful performances of the SR included the relay contact: the adjacent.
physically connected relay contacts were tested during the SR performance:
the subject relay contact has been tested by another SR: or historical operation of the subject relay contact has been successful.
It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment.
The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance.
If the Surveillance has been performed recently.
a review of the Surveillance historv and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.
For Surveillances that have not been performed for a long period or that have never been performed.
a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is OPERABLE.
The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.
Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence.
Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used repeatedly as an operational convenience to extend Surveillance intervals.
While up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified Frequency is provided to perform (continued) 83.0-18 Rev. 4-9/06