Latest revision as of 22:48, 4 February 2020

Text

License Amendment Request to Revise Technical Specifications to Adopt TSTF-529, Rev 4, Clarify Use and Application Rules.
	ML16340A005
Person / Time
Site:	Hatch, Vogtle, Farley
Issue date:	12/01/2016
From:	Pierce C; Southern Nuclear Operating Co
To:	; Document Control Desk, Office of Nuclear Reactor Regulation
References
	N-16-1837
	Download: ML16340A005 (87)
	v • d • e

--& South~r~- Nuclea~ 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 December 1, 2016 Docket Nos.: 50-321 50-348 50-424 NL-16-1837 50-366 50-364 50-425 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 10 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.

Respe~ll~ed, c.rv C.R. Pierce Regulatory Affairs Director CRP/KMO/lac before me this J__ day of Qa.A k O/hl ,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 NL.:~16-1837 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 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. ML16060A441). 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 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 10 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 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 10 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 10 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 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify 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).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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)

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 (continued)

Farley Units 1 and 2 1.3-2 Amendment No. 146 (Unit 1)

Amendment No. 137 (Unit 2)

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After performance of a risk assessment addressing inoperable (continued) 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.

LCO 3.0.5 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.

LCO 3.0.6 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.

LCO 3.0.7 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.

Farley Units 1 and 2 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 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.

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

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per ... "

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

SR 3.0.4 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.

Farley Units 1 and 2 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 The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify 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).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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 HATCH UNIT 1 1.3-1 Amendment No. 195

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)

HATCH UNIT 1 1.3-2 Amendment No. 195

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 management actions, if appropriate.;- !exceptions to this (continued) 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.

LCO 3.0.5 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.

LCO 3.0.6 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.

LCO 3.0.7 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.

HATCH UNIT 1 3.0-2 Amendment No. 246

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.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.

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may-be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

HATCH UNIT 1 3.0-4 Amendment No. 250

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

BACKGROUND Limiting Conditions for Operation (LCOs) specify 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).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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 HATCH UNIT2 1.3-1 Amendment No. 135

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)

HATCH UNIT 2 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

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.

LCO 3.0.5 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.

LCO 3.0.6 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.

LCO 3.0.7 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.

HATCH UNIT 2 3.0-2 Amendment No. 190

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.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.

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 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.

HATCH UNIT2 3.0-4 Amendment No. 194

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

BACKGROUND Limiting Conditions for Operation (LCOs) specify 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).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., 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 0.00111 hours 6.613757e-6 weeks 1.522e-6 months 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.

Vogtle Units 1 and 2 1.3-1 Amendment No. 96 (Unit 1)

Amendment No. 74 (Unit 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.

(continued)

Vogtle Units 1 and 2 1.3-2 Amendment No. 96 (Unit 1)

Amendment No. 74 (Unit 2)

LCO Applicability 3.0 3.0 LCO APPLICABILITY LCO 3.0.4 b. After performance of a risk assessment addressing inoperable (continued) 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.

LCO 3.0.5 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.

LCO 3.0.6 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.

(continued)

Vogtle Units 1 and 2 3.0-2 Amendment No. 137 (Unit 1)

Amendment No. 116 (Unit 2)