ML112660160: Difference between revisions

From kanterella
Jump to navigation Jump to search
(Created page by program invented by StriderTol)
 
(Created page by program invented by StriderTol)
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{Adams
#REDIRECT [[TSTF-11-15, Transmittal of TSTF-529, Revision 0, Clarify Use and Application Rules]]
| number = ML112660160
| issue date = 09/21/2011
| title = Transmittal of TSTF-529, Revision 0, Clarify Use and Application Rules
| author name = Browning R A, Croft W E, Steelman W J, Stringfellow N J
| author affiliation = BWR Owners Group, PWR Owners Group, Technical Specifications Task Force, B & W Nuclear Energy, Inc (B&W NE), Combustion Engineering, Inc, Westinghouse Electric Co
| addressee name =
| addressee affiliation = NRC/Document Control Desk, NRC/NRR
| docket = PROJ0753
| license number =
| contact person =
| case reference number = TSTF-11-15, TSTF-529, Rev 0
| document type = Letter
| page count = 205
| project =
| stage = Request
}}
 
=Text=
{{#Wiki_filter:11921 Rockville Pike, Suite 100, Rockville, MD  20852 Phone: 301-984-4400, Fax: 301-984-7600 Administration by EXCEL Services Corporation TECHNICAL SPECIFICATIONS TASK FORCE A JOINT OWNERS GROUP ACTIVIT Y TSTF September 21, 2011 TSTF-11-15 PROJ0753 
 
Attn:  Document Control Desk
 
U. S. Nuclear Regulatory Commission Washington, DC 20555-0001
 
==SUBJECT:==
Transmittal of TSTF-529, Revision 0, "Clarify Use and Application Rules" Enclosed for NRC review is Revision 0 of TSTF-529, "Clarify Use and Application Rules."
TSTF-529 is applicable to all plant types. The TSTF requests that the NRC bill the Boiling Water Reactor Owners' Group and the Pressurized Water Reactor Owners Group for the review of this Traveler.
Should you have any questions, please do not hesitate to contact us.
 
Norman J. Stringfellow (PWROG/W) Roy A. Browning (BWROG)
 
William J. Steelman (PWROG/CE) Wendy E. Croft (PWROG/B&W)
 
Enclosure
 
cc: Robert Elliott, Technical Specifications Branch, NRC  Michelle Honcharik, Licensing Processes Branch, NRC
 
TSTF-529, Rev. 0 BWROG-121, Rev. 0NUREGs Affected:Clarify Use and Application RulesTechnical Specifications Task Force Improved Standard Technical Specifications Change Traveler14301431143214331434Classification1) Technical ChangeRecommended for CLIIP?:YesCorrection or Improvement:Im provementNRC Fee Status:Not ExemptBenefit: Increases Operator Understanding See attached.Revision History Affected Technical SpecificationsOG Revision 0Revision Status:ActiveOriginal IssueRevision Descri ption:Revision Proposed by:TSTFOwners Group Review InformationDate Originated by  OG:27-May-10Owners Group Comments(No Comments)Date:17-Jun-11Owners Group Resolution:ApprovedTSTF Review InformationTSTF Received Date:25-Aug-11Date Distributed for Review25-Aug-11TSTF Comments:(No Comments)Date:21-Sep-11TSTF Resolution:ApprovedOG Review Completed:BWOG CEOGWOG BWROGNRC Review InformationNRC Received Date:
21-Sep-11 1.3Completion Times 21-Sep-11Traveler Rev. 3. Copyright(C) 2011, EXCEL Services Corporation. Use by EXCEL Services associates, utility clients, and the U.S. Nuclear Regulatory Commission is granted. All other use without written permission is prohibited.
TSTF-529, Rev. 0 BWROG-121, Rev. 0LCO  3.0 BasesLCO ApplicabilitySR  3.0 BasesLCO ApplicabilityLCO  3.0.2 BasesLCO ApplicabilitySR  3.0.2 BasesLCO ApplicabilityLCO  3.0.3 BasesLCO ApplicabilitySR  3.0.3 BasesLCO ApplicabilityLCO  3.0.4LCO ApplicabilityLCO  3.0.4 BasesLCO ApplicabilityLCO  3.0.5LCO ApplicabilityLCO  3.0.5 BasesLCO Applicability 21-Sep-11Traveler Rev. 3. Copyright(C) 2011, EXCEL Services Corporation. Use by EXCEL Services associates, utility clients, and the U.S. Nuclear Regulatory Commission is granted. All other use without written permission is prohibited.
TSTF-529, Rev. 0  Page 1 1.0  Description The proposed change will revise Sections 1.3, "Completion Times," and Section 3.0, "LCO Applicability" of the Technical Specifi cations (TS) and the TS Bases for Section 3.0, "LCO Applicability" and "SR Applicability," to clarify the use a nd application of the TS usage rules.
2.0 Proposed Change The following changes to the Techni cal Specifications are proposed: 1. Section 1.3 and the Bases of LCO 3.0.2 are modified to clarify and provide an example of "time of discovery." 2. An addition is made to Section 1.3 for Westinghouse plants (NUREG-1431) to discuss the Westinghouse-specific instrumentation Notes that allow entering a Condition and not starting the Completion Time until expiration of a time allowance in a Note. 3. LCO 3.0.4.a is modified to clarify that Required Actions must be followed after entry into the Modes and other specifie d conditions in the Applicability. An example is added to the Bases. 4. An editorial change is made to LCO 3.0.4.b to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. The LCO 3.0.4.a Bases are revised. 5. LCO 3.0.5 is reworded to be consistent with the other LCO 3.0 specifications and to eliminate unnecessary restrictions.
In addition to TS Bases changes that re flect the proposed changes to the TS, the following TS Bases changes are proposed: 6. The introductory paragraphs of the LCO 3.0 and SR 3.0 Bases, and the SR 3.0.2 Bases are modified to state that the usage rules are applicable to Chapter 3 of the TS and to clarify their use when invoked from Chapter 5. 7. The Bases of LCO 3.0.2, LCO 3.03, SR 3.0.2, and SR 3.0.3 are revised to replace the term "Operational Convenience," with the intention from Generic Letter 87-09 of "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." 8. Changes are made to the Bases of LCO 3.0.3 and SR 3.0.3 to use consistent terminology. 9. The LCO 3.0.3 Bases are corrected to state that a unit shutdown may be terminated and LCO 3.0.3 exited if the LCO is no longer applicable.
TSTF-529, Rev. 0  Page 2 10. The LCO 3.0.4.c Bases are modified to replace a misleading TS reference. 11. The LCO 3.0.5 Bases are modified to clar ify that LCO 3.0.5 should not be used if there are other alternatives to demonstrate Operability that maintain compliance with Actions. An inaccurate exampl e in the LCO 3.0.5 Bases is replaced. 12. The SR 3.0.3 Bases are modified to clar ify when SR 3.0.3 may be applied and to state expectations for applying SR 3.0.3 when an SR has not been performed for
 
an extended period. A model application is included in the proposed change. The model may be used by licensees desiring to adopt TSTF-529 followi ng publication by the N RC of the Notice of Availability in the Federal Register.
 
===3.0 Background===
In January and February 2009, the Technical Specifications Task Force (TSTF) and NRC met to discuss questions and possible ambiguities on the application of the Improved
 
Standard Technical Specifications (ISTS). The topics for discussion were gathered from both the NRC and the industry. In all, ten areas of ambiguity were discussed. In almost all cases, the TSTF and the NRC reached ag reement on the application of the ISTS or agreed on a process to reach agreement. The TSTF agreed to prepare a TSTF Traveler for NRC review to clarify the TS use and application rules in LCO 3.0 and SR 3.0, to document areas of agreement in the TS and Bases, and present proposed resolutions for the remaining areas under question. The TSTF queried the industry and identified several areas in Section 1.3, LCO 3.0 and SR 3.0 that would benefit from clarification. These clarifications are generally minor or editorial, but routinely generate questions from licensee and NRC staff and are, therefore, worthy of correction.
4.0 Technical Analysis 4.1 Revise Section 1.3 and the Bases of LCO 3.0.2 to Clarify and to Provide an Example of "Time of Discovery" Section 1.3 states that the Completion Time is "referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits)."  LCO 3.0.2 states, "Upon discovery of a failure to meet an LC O, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6."  The
 
LCO 3.0.2 Bases state, "LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met."  Understanding "time of discovery" is fundamental in applying Required Actions and associated Completion Times.
There occasionally is confusion by both NRC and industry staff on the meaning of "time of discovery."  Much of this confusio n results from differing guidance depending on whether one is considering Technical Specification compliance or reportability.
TSTF-529, Rev. 0  Page 3 Therefore, it is worthwhile to provide additional information in the Bases on "time of discovery" as it relates to Technical Specification compliance. The proposed change makes the following revi sion to the "Description" section of Section 1.3: "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. The time of discovery is when the LCO is declared not met. Th e time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a co mponent is inoperab le following improper maintenance performed in the past. Th e time of discovery (when the LCO is declared not met) is subsequent to bo th the time of occurrence (the improper maintenance), the time when it is identifie d that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable." (The struck-out text is removed. The text in italics is added.)
The proposed change adds the following to the LCO 3.0.2 Bases: "The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of id entification and evaluation of the degraded or nonconforming condition." This position is consistent with the historical NRC position. For example, in a memorandum from H. L. Thompson, Director, Division of Licensing, to R. Starostecki, Director, Division of Reactor Projects, Region 1, dated August 9, 1985, Mr. Thompson stated, "It is NRR's position that the time limitation of action requirements are applicable from the point in time that it is recognized that the requirements of a limiting condition of operation are not met. This is as noted by your example and proposed interpretation. It was also noted in your memo that this issue is further complicated by recent trends in NRC enforcement which cite the historical inoperability of equipment as a factor in determining the significance of loss of function violations." This position is also consistent with recent NRC guidance in NRC Inspection Manual, Part 9900: Technical Guidance, "Operability Determinations & Functionality Assessments for Resolution of Degraded or Nonconforming Conditions Adverse to Quality or Safety."  Section 4.8, "Operator Awareness and Responsibilities," states: "A senior licensed operator on the operat ing shift crew with responsibility for plant operations makes the declaration of operability, i.e., 'makes the call' on whether an SSC described in TSs is operable or inoperable."
TSTF-529, Rev. 0  Page 4 The Part 9900 guidance in conjunction with the LCO 3.0.2 Bases make clear that discovery is when a senior licensed op erator on the operating shift crew with responsibility for plant operations declares an LCO not met.
To our knowledge, the proposed change does not represent a point of disagreement between the NRC and the industry.
In addition, the Bases of LCO 3.0.2 are revised to eliminate a minor discrepancy between the Technical Specifications (Section 1.3) a nd the Bases. Section 1.3 states that a Completion Time is referenced to the time of discovery of a situ ation that requires entering an ACTIONS Condition unless otherwise specified. LCO 3.0.2 makes a similar statement but without the qualifier, "unless otherwise sp ecified."  The LCO 3.0.2 Bases are revised to state: "The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time th at an ACTIONS Condition is entered unless otherwise specified
." This change to the LCO 3.0.2 Bases is also rela ted to the proposed ch ange to Section 1.3 discussed in the following section. 4.2 Revise Section 1.3 to Discuss Instrume ntation Required Action Notes in NUREG-1431 (Westinghouse plants)
A paragraph is added to Section 1.3 for We stinghouse plants (NUREG-1431) to discuss the Westinghouse-specific instrumentation No tes that allow entering a Condition and not starting the Completion Time until after expiration of a time allowance in the Note. The LCO 3.0.2 Bases state, "The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered."  In the vast majority of cases, this is true. However, in NUREG-1431, Specification 3.3.1, " Reactor Trip System," and Specification 3.3.2, "Engineered Safety Feature Actuation System Instrumentation," some Required Actions contain Notes which defer the start of the Completion Time. These Notes are similar to, "One channel may be bypassed for up to 12 hours for surveillance testing and setpoint adjustment."  It is
 
recognized that placing the train in bypass re nders the train inopera ble, but starting the Completion Time is deferred in accordance with the Notes. The addition of these Notes was justified in NRC-approved Topical Reports (for example, WCAP-14333-P-A, Rev. 1, October 1998). It is not the inten tion of the proposed change to justify the addition of the Notes. Th e only proposed change is to describe the exception to the typical application of Completion Times.
The proposed change will add the fo llowing to Section 1.3 in NUREG-1431:  "The Completion Time is referenced to the time of entering an ACTIONS Condition unless otherwise specified. One of the "otherwise specified" cases is a Required Action modified by a Note which provides an alternative time to TSTF-529, Rev. 0  Page 5 perform specific tasks (i.e., "One channel may be bypassed for up to 12 hours for surveillance testing and setpoint adjustment.")  Starting the Completion Time is deferred in accordance with the Note. While utilizing the Note, should the 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." 4.3 Clarifications to LCO 3.0.4.a In the memorandum "Final Task Interface Agreement - Reevaluation of Implementation of Limiting Condition for Operation 3.0.4a, 'Mode Change Limitations,' At Palisades Nuclear Plant (TIA2009-005)," dated September 17, 2009 (ADAMS Accession Number ML092540032), the NRC issued a response to a Task Interface Agreement (TIA) request documenting the Staff position regarding the ap plication of Technical Specification LCO 3.0.4. The NRC's stated position in the response to TIA 2008-002, was
" ...while-completing the TS required actions to be entered before conducting a mode transition with inoperable equipment establis hes the basis for continued operation, the completion of those actions is not a requirement for compliance with LCO 3.0.4a." The proposed change modifies LCO 3.0.4, which currently states: "When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made: a. When the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; ..." LCO 3.0.4.a is clarified to state: "a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time"  (Added text is in italics). In a complementary change, the Bases of LC O 3.0.4.a are revised to reflect the wording change to LCO 3.0.4.a and to add an exampl e of the application of LCO 3.0.4. The example addresses a frequent question by clarifying that it is not necessary that every possible set of Required Actions allow c ontinued operation in the MODE or other specified condition in the Applicability for an unlimited period of time, only that a set of Required Actions allow continued operation. For example, it is not necessary to assume that the licensee does not perform the Required Actions, such as placing a channel in trip or starting a piece of equipment. The proposed Bases state: "For example, LCO 3.0.4.a may be used wh en the Required Action states that an inoperable [train-PWR][subsystem-BWR] be restored to OPERABLE status within the Completion Time, and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE [train][subsystem] to be placed in operation. Use of LCO 3.0.4.a is acceptable because the associated TSTF-529, Rev. 0  Page 6 ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE [train][subsystem] in operation) that permit plant operation for an unlimited period of time in the MODE or ot her specified condition to be entered." 4.4 Editorial Clarification to LCO 3.0.4.b LCO 3.0.4 contains three options, la beled paragraphs a, b, and c.
Paragraph a ends with a semicolon and Paragraph b ends with ", or".
This presentation is consistent with the ordered list format as described TSTF-GG-05-01, "Writers Guide for Plant-Specific Improved Technical Specifications," excep t that Paragraph b should end with a semicolon, such as "; or".
LCO 3.0.4.b states: "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 specifie d condition in the Applicability, and establishment of risk management actions, if appropriate; exceptions to this Specification are stated in the individual Specifications, or" The separation of the majority of the text from the "o r" conjunction by the phrase regarding exceptions has misled some readers to interpret the "or" statement to only apply to the phrase regarding exceptions and to believe that LCO 3.0.4.a, b, and c apply concurrently. The sentence is clarified by placing the statem ent regarding exceptions in parenthesis and to replace the ending comma with a semicolon: "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 specifie d condition in the Applicability, and establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the in dividual Specifications); or".
The Bases are also revised to clarify this point. The introductory paragraph of LCO 3.0.4 is revised to insert the word "either" as follows:
  "in accordance with either LCO 3.0.4.a, LCO 3.0.4.b, or LCO 3.0.4.c" (Added text is in italics). 4.5 Reword LCO 3.0.5 to be Consistent with the Other LCO 3.0 Specifications and Eliminate Unnecessary Restrictions LCO 3.0.5 states: "Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative c ontrol solely to perform testing required to dem onstrate its OPERABILITY or the OPERABILITY of other equipment. Th is is an exception to LCO 3.0.2 for the TSTF-529, Rev. 0  Page 7 system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY." LCO 3.0.5 provides a necessary flexibility to f acilitate restoring equipment to Operability (or to perform Surveillances required to verify Operability). LCO 3.0.5 is an exception to LCO 3.0.2, but it cu rrently is not consistent with LCO 3.0.2 and the other LCO 3.0 usage rules. LCO 3.0.2 addresses when the LCO is not met, but LCO 3.0.5 discusses only demonstrating Operability. Not all LCOs require demonstrating Operability, such as LCOs on variables. LCO 3.0.5 is revised to be consistent with LCO 3.0.2 by referring to "demonstrating the LCO is met" versus "demonstrating OPERABILITY." The proposed change revises LCO 3.0.5 to state:
"The Required Actions of Conditions are not required to be met under administrative control solely to perform testing required to demonstrate that the LCO is met or that other LCOs are met. This is an exception to LCO 3.0.2 to perform the testing required to demonstrate the LCO is met or that other LCOs are met." (Additions are in italics).
The LCO 3.0.5 Bases are revised to be cons istent with this change to the LCO. The revised LCO 3.0.5 wording will also allow LCO 3.0.5 to be used in some additional situations. The existing LCO 3.0.5 wording only allows equipment removed from service to be returned to service. This addresses the majority of situations, however, it does not address all situations in which LC O 3.0.5 could be used. In some Technical Specifications, ACTIONS involve the placement of redundant or alternate equipment or trains into service, or the repositioning (opening or closing) of components. Allowing LCO 3.0.5 to be used in these situations does not change the intent of the allowance. An example is the Pressurizer Power Operated Relief Valves (PORVs) for Pressurized Water Reactors (PWRs). If a PORV is inoperable, the Required Action is to close the associated block valve in order to isolate the inoperable PORV. Once the PORV is repaired, it may be necessary to stroke the PORV in order to demonstrate its Operability.
The closed block valve must be opened so that system pressure is restored to the PORV, allowing the PORV to be stroked. As currently written, the Required Action to close the block valve does not fall under the LCO 3.0.5 allowance because it does not involve "equipment removed from service or declared inoperable." While the proposed change will allow LCO 3.0.5 to be applied in additional situations, the proposed change does not alter the in tent of LCO 3.0.5. Th e purpose of LCO 3.0.5 remains to provide an exception to LCO 3.0.2, to allow required testing to demonstrate the LCO is met or that other LCOs are met. The required testing in all cases will
 
continue to be conducted under administrativ e controls to ensure the time when the system is not in compliance with the ACTIONS is limited to the time necessary to perform the required testing.
TSTF-529, Rev. 0  Page 8 4.6 LCO 3.0 and SR 3.0 Applicability Clarified in Bases The LCO 3.0 and SR 3.0 Applicability specifica tions apply to Chapter 3 of the Technical Specifications and apply to specifications in Chapter 5, "Administrative Controls," only when explicitly stated in the Chapter 5 Specification. This issue was questioned and
 
resolved with the NRC during the development of TSTF-52-A, "Implement 10 CFR 50, Appendix J, Option B."  In response to an NRC comment that the Administrative Controls Containment Leakage Rate Testing Program should contain a statement that SR 3.0.2 does not apply, the TSTF responded,  "The proposed change is addressed with revised wording. It has long been the NRC and Industry position that Secti on 3.0 does not apply to Chapter 5. A review of the Revision 2 ITS reveals that there are no instances in which ITS 5.0 programs have been made which state that Section 3.0 provisions do not apply, only that it does apply. To avoid confus ion by stating in one location that SR 3.0.2 does not apply (thereby implying that it does apply in other locations), the statement 'Nothing in these Technical Speci fications shall be construed to modify the testing Frequencies required by 10 CFR 50, Appendix J.'  This addresses the issue of licensee's miscons truing the SR 3.0.2 allowance and applying it to the 10 CFR 50, Appendix J, tes ting frequencies."  The NRC accepted this resolution and appr oved TSTF-52 on April 14, 2000. Note that there are no Administrative Controls programs that state that LCO 3.0 or SR 3.0 specifications do not apply, only notations th at specific LCO 3.0 or SR 3.0 specifications do apply.
The introductory paragraph of the Bases to LCO 3.0, "LCO Applicability," states, "LCO 3.0.1 through LCO 3.0.8 establish the general requireme nts applicable to all Specifications and apply at all times, unle ss otherwise stated."  The introductory paragraph of the Bases to SR 3.0, "SR Applicability," states, "SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated."  These statements have sometimes led to confusion on whether the LCO 3.0 and SR 3.0 applicability specifi cations apply to Chapter 5 when not specifically referenced in a Chapter 5 Specification.
To clarify this issue and avoid future que stions, the LCO 3.0 intr oductory paragraph is proposed to be revised to state: "LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through [PWR: 3.9 / BWR: 3.10]
and apply at all times, unless otherwise stated."
The SR 3.0 introductory paragra ph is revised to state,  "SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through [PWR: 3.9 / BWR: 3.10]
and apply at all times, unless otherwise stated.
SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification." (Added words are in italics).
TSTF-529, Rev. 0  Page 9 In a complementary change, the Bases of SR 3.0.2 are revised. The Bases currently state: "The exceptions to SR 3.0.2 are those Surv eillances for which the 25% extension of the interval specified in the Freque ncy does not apply. These exceptions are stated in the individual Specifications. The requireme nts of regulations take precedence over the TS. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the
 
regulations. " As stated in the introductory paragraph, SR 3.0.2 does not apply to Programs in Chapter 5 of TS unless specifically stated and the Containment Leakage Rate Testing Program does not state that SR 3.0.2 applies. However, in a number of Surveillances in Chapter 3 of the TS, the Containment Leakage Rate Testing Program is referenced in the Frequency Column, thereby directing the reader to the Program to find the applicable Frequencies.
Therefore, the SR 3.0.2 Bases paragraph shown above is proposed to be replaced with: "There are exceptions to SR 3.0.2 for cer tain Surveillances to which the 25% extension of the interval specified in the Frequency may not be applied. These exceptions are stated in the individual Specifications. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Star ting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program which does not referen ce SR 3.0.2. SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations. The TS cannot in and of them selves extend a test interval specified in the regulations." The proposed change is consistent with th e current application of LCO 3.0 and SR 3.0 and only serves to explicitly state the existing TS usage rules in a readily accessible
 
location. 4.7 Replace the Undefined Term "Operationa l Convenience" Used in the Bases of LCO 3.0.2, LCO 3.0.3, SR 3.0.2, and SR 3.0.3 The term "operational convenience" appears four times in the Bases of each ISTS NUREG: in the Bases of LCO 3.0.2, LCO 3.0.3, SR 3.0.2, and SR 3.0.3. It does not appear in the Specifications. The ISTS LCO 3.0.2 Bases state:  "The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or TSTF-529, Rev. 0  Page 10 investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should not be made for operational convenience. Additionally, if intentional entry into ACTIONS would result in redundant equipment being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/divisions of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered" (emphasis added). The ISTS LCO 3.0.3 Bases state: "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" (emphasis added).
The ISTS SR 3.0.2 Bases state:  "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" (emphasis added).
The ISTS SR 3.0.3 Bases state: "Failure to comply with specified Fre quencies for SRs is expected to be an infrequent occurrence. Use of the de lay period established by SR 3.0.3 is a flexibility which is not intended to be used as an operational convenience to extend Surveillance intervals. While up to 24 hours 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...." (Emphasis added). Use of the term "operational convenience" in the Bases of the T echnical Specifications (TS) has changed and been expanded from its original use and intent, and the revised Bases have created difficulty in interpreting and applying th e current guidance. Bases revisions are proposed to replace this term with information reflecting its original intent, to avoid such interpretati on and application issues. The term "operational convenience" first appeared in several 1987-era documents. Its first use is in the model Bases markups att ached to Generic Lette r (GL) 87-09, "Sections 3.0 and 4.0 of the Standard Technical Specifi cations (STS) on the Applicability of Limiting Conditions for Operation and Surveillance Requirements," dated June 4, 1987
[copies of the applicable Model PWR Bases pages from GL 87-09 Enclosure 3 are attached for information]. In the two GL 87-09 Bases sections where the term "operational convenience" is used, it is equated with "(routine) voluntary removal of a TSTF-529, Rev. 0  Page 11 system(s) or component(s) from service in lieu of other alternatives that would not result in redundant systems or components bei ng inoperable."  Also, the operational convenience concept is only linked to intentiona l entries into Actions that directly contain a shutdown requirement. As stated, "It is not intended that the shutdown ACTION requirements be used as an operational convenience which permits (routine) voluntary removal of a system(s) or component(s) from service in lieu of othe r alternatives that would not result in redundant systems or com ponents being inoperable" (emphasis added). The term "operational convenience" was not utilized in the Bases for Surveillance Requirement 4.0.2 (now called SR 3.0.2) or in the Bases for SR 4.0.3 (now SR 3.0.3). The question of potential misinterpretation of the proposed words in GL 87-09 was raised almost immediately by the industry. For example, in a meeting held with Carolina Power & Light on September 17, 1987 [see attached], when the intent of the GL words were still fresh, the NRC clarified that the words were only intended to limit intentional entry into ACTIONS when the situation involves redundant systems being out of service. The staff stated that, for both Bases sentences, "-the point of clarification is that the last echelon of defense should not be removed from service such that this would invoke a prompt shutdown action requirement, in lieu of other alternatives that would not result in redundant systems being out of service simultaneously." The third 1987 document (Attachment 3) is an Inspection Manual Part 9900 Technical Guidance document, "Standard Technical Specifications (STS) Section 3.0.3 Limiting Conditions for Operation."  Similar to th e above, the operational convenience words are linked to situations in which redundant safety systems would be out of service, and it explains that the concern is for situations in which entry into ACTIONS would show a disregard for plant safety. In the 1991 time frame, during the developmen t of Revision 0 of the ISTS NUREGs, the above described concept was broken down into several separate sentences. The January 1991 NRC "Draft Report for Comment" vers ion of the ISTS NUREGs, the LCO 3.0.2 Bases states: "It is not intended that intentional entry into ACTIONS be made for operational convenience. Intentional entry into ACTIONS Conditions with shutdown Required Actions (i.e., Actions requiri ng a change in MODE) is strongly discouraged and should be considered only in extreme circumstances. This is to limit routine voluntary removal of redundant equipment from se rvice in lieu of other alternatives th at would not result in redundant equipment being inoperable." The intention was to capture the original concept in these new sentences, but the intent was lost due to fragmentation. Additional changes made during the development of the ISTS (some at the request of the industry) resulted in the term " operational convenience" becoming separated from the concept of "(routine) voluntary removal of a system(s) or component(s) from service in lieu of other a lternatives that would not result in redundant systems or components being inope rable."  It was also separated from the link to Actions that directly involve a shutdown requirement. In addition, the term was introduced into the SR 3.0.2 Bases in circumstances in which the GL 87-09 intent was not applicable.
TSTF-529, Rev. 0  Page 12 The June 1992 "Proof and Review" version of the ISTS NUREGs added the term to the SR 3.0.3 Bases, again in circumstances that are not consistent with the original intent, as the Surveillance Requirements usage rules are not related to entry into ACTIONS.
In 1999, in a revision to an NRC Inspecti on Manual Part 9900 Technical Guidance document, "Voluntary Entry into Limiting Conditions for Operation Action Statements to Perform Preventative Maintenance," (Attachment 4) the phrase "simply for operational convenience" was introduced into a paragra ph in Section B that discusses intentional entries into ACTIONS. Similar to ho w this concept was addressed in the 1987 documents, it links the operational conveni ence concern to situations "such as intentionally creati ng a loss of function situati on or entering LCO 3.0.3-"
The loss of the original intention of the term "operational convenience" has lead to confusion on the use of the term. Since 2000, th ere have been two citations in inspection reports for entering, or planning to enter, Ac tions as an operational convenience.  (Quad Cities in 2007, ADAMS Accession Number ML072080425; and Oconee in 2000, NRC
 
Integrated Inspection Report 50-269/99-09, 50-270/99-09, and 50-287/99-09.)  In both cases, the circumstances were not related to voluntary removal of redundant systems or components from service. Licensees are unc lear on what is, and is not, considered "operational convenience" in the absence of any definition in the TS.
The proposed change revises the Bases of LCO 3.0.2, LCO 3.0.3, SR 3.0.2, and SR 3.0.3 to restore the original intent and to eliminate the incorrect application of the term "operational convenience."  This proposed change does not lessen the requirements on licensees to consider safety when entering Actions, nor does it remove the ability of the NRC to respond should licensees inappropriate ly enter Actions. Since 1987, the practice of voluntary entries into Acti ons has received a significant amount of attention and has even been the subject of rulemaking: 10 CF R 50.65, the Maintenance Rule. The industry is now required to consider the effect on plant risk when equipment is inoperable and Actions are entered. Licensees track and report unavailability of safety systems under the NRC's Reactor Oversight Process. The NRC performs inspections on these evaluations and unavailability is reported under the Mitigating System Performance Index.
Intentional entries are subject to licensee examinations of the net effect on safety, through a balancing of the benefits to be gained by such an entry against the objective of minimizing unavailability.
The Bases of LCO 3.0.2 currently state: "Intentional entry into ACTIONS should not be made for operational convenience.
Additionally, if intentional entry in to ACTIONS would result in redundant equipment being inoperable, alterna tives should be used instead."  These sentences are proposed to be replaced with: "Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Inte ntional entry into ACTIONS should not be used for voluntary removal of redundant systems or components from service in TSTF-529, Rev. 0  Page 13 lieu of other alternatives that would not result in redundant systems or components being inoperable." This change does not alter the intent and is consistent with the intent as stated by the NRC, while eliminating the undefined term "operational convenience." The Bases of LCO 3.0.3 currently state: "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." The second sentence is revised to state: "It is not intended to be used to permit 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." This change does not alter the intent and is consistent with the intent as stated by the NRC, while eliminating the undefined term "operational convenience." The Bases of SR 3.0.2 currently state: "The provisions of SR 3.0.2 are not intended to be used repeatedly merely as an operational convenience to extend Survei llance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified." The sentence is revised to state: "The provisions of SR 3.0.2 are not inte nded to be used repeatedly to extend Surveillance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified." This change does not alter the intent, while eliminating the inconsistent use of the term "operational convenience." The Bases of SR 3.0.3 currently state: "Failure to comply with specified Fre quencies for SRs is expected to be an infrequent occurrence. Use of the delay period establis hed by SR 3.0.3 is a flexibility which is not intended to be used as an operational convenience to extend Surveillance intervals."
TSTF-529, Rev. 0  Page 14 The second sentence is revised to state: "Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used to extend Surveillance intervals." This change does not alter the intent, while eliminating the inconsistent use of the term "operational convenience." 4.8 Revise the Bases of LCO 3.0.3 and SR 3.0.3 to Improve Terminology The LCO 3.0.3 Bases make several references to "reaching" a lower MODE instead of the more common usage of "entering" a MODE. The term "reaching" is ambiguous as it's not clear whether the MODE is entered. In seven locations in the LCO 3.0.3 Bases, the phrase "reaching" a MODE is replaced with "entering" a MODE. The SR 3.0.3 Bases make three references to "completing" a Survei llance. Specification SR 3.0.3 uses the term "performing" a Surveillance. The term "performed" is defined in
 
the "Description" section of Specification 1.4, "Use and Application, Frequency."  To improve consistency between the Specifications and the Bases, the term "perform" is substituted in the Bases for "complete." These changes do not represent any change in intent, but are made for consistency within the ISTS. 4.9 Correct LCO 3.0.3 Bases to Acknowledge a Unit Shutdown may be Terminated and LCO 3.0.3 Exited if the LCO is No Longer Applicable The LCO 3.0.3 Bases state: "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. A Condition exists for which the Required Actions have now been performed, or
: c. 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." This list is incomplete. As stated in LCO 3.0.2, "If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated."  The list in the LCO 3.0.3 Bases does not acknowledge that a unit shutdown may be terminated and LCO 3.0.3 exited if the LCO is no longer applicable (i.e., the LCO that was not met which lead to entry into LCO 3.0.3).
TSTF-529, Rev. 0  Page 15 The proposed change adds to the list a new paragraph b which states, "The LCO is no longer applicable," and the subsequent list items are renumbered.
This change does not represent any change in intent, but is made for consistency within the ISTS. 4.10 Modify the LCO 3.0.4.c Bases to Co rrect a Misleading TS Reference The Bases to LCO 3.0.4.c state: "The risk assessments performed to ju stify the use of LCO 3.0.4.b usually only consider systems and components. Fo r this reason, LCO 3.0.4.c is typically applied to Specifications which describe values and parameters (e.g., [Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature Coefficient]), and may be a pplied to other Specifications based on NRC plant specific approval."
Although the list of specif ications to which LCO 3.0.4.c is ty pically applied is in brackets (i.e., plant specific), the parenthetical phrase is misleading. In the ISTS, LCO 3.0.4.c is only applied to only one specification, "RCS Specific Activity."  This specification is not listed in the Bases and the listed specifications in the ISTS do not allow application of LCO 3.0.4.c. For consistency with in the ISTS, the bracketed list of Specifications is replaced with "(e.g., RCS Specific Activity)." 4.11 Modify the LCO 3.0.5 Bases to Clarify that LCO 3.0.5 Should Not be Used if there are Other Alternatives that Maintain Compliance with Actions.
Many specifications contain provisions which allow Required Actions to not be followed to facilitate repair or testing. For example, the instrumentation specifications may allow channels to be placed in bypass, the containment air lock specification contains an Actions Note which allows entry and exit to perform repairs, and the containment isolation valve specification cont ains an Actions Note which allows isolated penetration flow paths to be unisolated under administrativ e control. In these cases, the risks and benefits of not following the Required Acti on were generically ev aluated and accepted and, in some cases, additional restrictions are applied (such as a time limit for keeping an instrument channel in bypass). When the specification does not provide an allowance to not follow a Required Action in order to establish the LCO is met, LCO 3.0.5 may be used. LCO 3.0.5 states: "Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative c ontrol solely to perform testing required to dem onstrate its OPERABILITY or the OPERABILITY of other equipment. Th is is an exception to LCO 3.0.2 for the system returned to service under admini strative control to perform the testing required to demonstrate OPERABILITY."
TSTF-529, Rev. 0  Page 16 Proposed changes to LCO 3.0.5 ar e discussed in Section 4.5. Because LCO 3.0.5 applies in many circumstances, it's not possible to generically evaluate every possible application and, therefore, its use should be minimized. As stated in the LCO 3.0.5 Bases,  "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." In cases in which the Specification's ACTIONS or Surveillances contain allowances that permit testing to establish the LCO is met, li censees should use those features instead of LCO 3.0.5 as those features have been specifi cally evaluated and ar e consistent with LCO 3.0.2. In order to clarify this point, LCO 3.0.5 is modified by adding the following: "LCO 3.0.5 should not be used in lieu of other practicable alternatives that comply with ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met. LCO 3.0.5 is not intended to be used repetitively." The proposed change is consistent with th e intent of LCO 3.0.5 and provides additional guidance to licensees to avoid misinterpretation.
In a related change, an incorrect exampl e in the LCO 3.0.5 Bases is replaced. The existing example cites the containment isolati on valve specification. As noted above, the containment isolation valve specification contains an Actions Note which eliminates the need to use LCO 3.0.5 to unisolate a penetration to perform Operab ility testing. A new example referencing manual valves closed to isolate Reactor Coolant System Pressure Isolation Valve leakage replaces the containment isolation valve example. For NUREG-1430, -1432, -1433, and -1434 (Babcock & Wilcox (B&W), Combustion Engineering (CE), Boiling Water Reactor (BWR)/4 and BWR/6 plants), the other existing example in the LCO 3.0.5 Bases regarding instrument channels is retained. NUREG-1431 (Westinghouse plants) contains Required Acti ons Notes which allow channel testing in lieu of LCO 3.0.5, so this example is not applicable and is deleted. The example of verifying that other equipment is Operable is deleted as most relevant examples reference equipment described in the same LCO, such as Pressure Operated Relief Valves (PORVs)
 
and block valves. 4.12 Modify the SR 3.0.3 Bases to Clarify when SR 3.0.3 May be Applied As stated in SR 3.0.1, SR 3.0.3 is an exception to the requirement that a Surveillance be performed within the specified Frequency.
SR 3.0.3 states, "If it is discovered that a Surveillance was not performed..."  SR 3.0.3 is not an exception to the requirement for SRs to be met during the Modes or other spec ified conditions in the Applicability. This is a key consideration in the application of SR 3.0.3.
TSTF-529, Rev. 0  Page 17 The terms "met" and "performed" are defi ned in Section 1.4, "Use and Application, Frequency" of the ISTS. It states: "The use of 'met' or 'performed' in these instances conveys specific meanings. A Surveillance is 'met' only when the acceptance criteria ar e satisfied. Known failure of the requirements of a Survei llance, even without a Surveillance specifically being 'performed,' constitutes a Surveillance not 'met.' 'Performance' refers only to the requirement to specifically determine the ability to meet the acceptance criteria." The Bases of SR 3.0.3 also state that SR 3.0.3 is an exception to performing the SR within the specified Frequency, not to the requirement an SR be met. The Bases state; "The basis for this delay period includes ... the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements."  The Bases of SR 3.0.3 also state: "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 th e applicable LCO Conditions begin immediately upon the failure of the Surveillance."  Therefore, if an SR has not been performed within the specifie d Frequency and it is known that the acceptance criteria of the SR are not met, then the equipment is inoperable and SR 3.0.3 cannot be applied.
NRC Inspection Manual, Part 9900: Technical Guidance, "Operability Determinations & Functionality Assessments for Resolution of Degraded or Nonconforming Conditions Adverse to Quality or Safety," Section 3.9 states: "The discovery of a degraded or nonconforming condition may call the operability of one or more SSCs [structures, systems, or components] into question. A subsequent determination of operability should be based on the licensee's 'reasonable expectation,' from the evidence collected, that the SSCs are operable and that the operability determination will support that expectation. Reasonable expectation does not mean absolute assurance that the SSCs are operable. The SSCs may be considered opera ble when there is evidence that the possibility of failure of an SSC has in creased, but not to the point of eroding confidence in the reasonable expectation that the SSC rema ins operable. The supporting basis for the reasonable expectation of SSC operability should provide a high degree of confidence that the SSCs remain operable. It should be noted that the standard of 'reasonable expectation' is a high sta ndard, and that there is no such thing as an indeterminate state of operability; an SSC is either operable or inoperable."
TSTF-529, Rev. 0  Page 18 This standard of "reasonable e xpectation" is directly applicable to the question of whether a licensee may apply SR 3.0.3 to an SR that has not been performed within its specified Frequency because in both cases the question to be addressed is whether the associated equipment is believed to be Operable or that variables are within limits. If the licensee has a reasonable expectation that performance of the SR will confirm that the equipment
 
is Operable or a variable to be verified is within limits, then SR 3.0.3 may be applied to the SR which has not been performed. If the licensee does not ha ve this reasonable expectation, then under SR 3.0.1 the SR is not met and the associated LCO is not met. In most cases, discovery of an SR that has not been performed within the specified Frequency occurs when a single performance has been missed. In that case, a review of the surveillance history and equipment performance may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. However, in some cases an SR, or portions of an SR, may not have been performed for more than one Frequency period, or may not have ever been performed. In that case, establishing a reasonable expectation that the SR is met is more difficult. The licensee will consider other indications, tests, or activities for an indication of whether the Surveillance will be met when performed. 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 performan ce of the Surveillance. For long delays or for Surveillances that have never been successfully performed, a more rigorous evaluation, documented in sufficient detail to explain the basis for the determination, should be performed. The preceding discussion is proposed to be captured in the SR 3.0.3 Bases with the following addition: "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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have b een tested, the relay contacts have been tested by another SR, or hi storical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis for the determination, should be completed to compensate for the lack of performance history."
TSTF-529, Rev. 0  Page 19 The proposed Bases wording is consistent wi th the existing requirements of SR 3.0.3 and the philosophy of "met" and "performed" SRs as described in Section 1.4 of the Technical Specifications.
The proposed Bases are also consistent with the intent of SR 3.0.3 as stated in Generic Letter 87-09. It states, "It is overly conservative to assume that systems or components are inoperable when a surveillance has not been performed because the vast majority of surveillances do in fact demonstrate that systems or components are operable. When a surveillance is missed, it is primarily a question of operability that ha s not been verified by the performance of a Surveillance Requirement."  The fact that SRs must be met in order to apply SR 3.0.3 to SRs that have not been performed with in their specified Frequency implements the assumption that systems or components are operable.
Conclusion The proposed changes are consistent with th e current intent of Section 1.3, and LCO 3.0 and SR 3.0 and their associated Bases and will increase the clarity and allow consistent application of the Improved Sta ndard Technical Specifications.
5.0  Regulatory Analysis 5.1 No Significant Hazards Consideration The TSTF has evaluated whether or not a significant hazards consid eration is involved with the proposed generic change by focu sing on the three standards set forth in 10 CFR 50.92, "Issuance of amendment," as discussed below:
: 1. Does the proposed change involve a significant increase in the probability or consequences of an accident previously evaluated?
Response: No.
 
The proposed change revises Section 1.3, "Completion Times," and Section 3.0, "LCO Applicability" of the Technical Specifications (TS) and the TS Bases for Section 3.0, "LCO Applicability" and "SR A pplicability," to clarify the use and application of the TS usage rules. Secti on 1.3 is modified to cl arify the concept of "time of discovery" and to describe an existing allowance specific to
 
NUREG-1431, "Standard Technical Specifications, Westinghouse Plants."  LCO 3.0.4.a is modified to clarify that Required Actions must be followed after entry into the Modes and other specified conditions in the Applicability. An editorial change is made to LCO 3.0.4.b to clar ify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. LCO 3.0.5 is reworded to be consistent with the other LCO 3.0 specifications. The proposed change to LCO 3.0.4.a and LCO
 
3.0.4.b are for clarification and will not affect the implementation of the Technical Specifications (TS). The proposed change to LCO 3.0.5 will allow LCO 3.0.5 to be applied in a small number of circumstances in which it cannot be applied today.
TSTF-529, Rev. 0  Page 20 The proposed change to Section 1.3, LCO 3.0.4, and LCO 3.0.5 has no effect on the requirement for systems to be Operable and will not have a significant effect
 
on the application of TS actions. 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 cha nge does not involve a significant increase in the probability or consequences of an accident previously evaluated.
: 2. Does the proposed change create the po ssibility 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 ch ange does not change the Operability requirements for plant systems and facilitates restoring inoperable equipment to Operable status. The proposed change clarifies the current application of LCOs. The proposed change to LCO 3.0.4 will not affect plant operation when LCO 3.0.4 is applied. The proposed change to LCO 3.0.5 slightly expands the circumstances in which LCO 3.0.5 can be applied. Testing to confirm Operability allowed under the proposed change to LCO 3.0.5 will be performed under procedural control in accordance with the licensee's quality assurance process and will not introduce and new or different accident initiators.
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 change involve a signi ficant reduction in a margin of safety?
Response: No.
The proposed change clarifies the app lication of Section 1.3 and LCO 3.0.4 and does not result in changes in plant operati on. As a result, plant safety is either improved or unaffected. The proposed ch ange to LCO 3.0.5 allows testing to establish Operability to be performed, which improves plant safety.
Therefore, it is concluded that this cha nge does not involve a significant reduction in a margin of safety.
Based on the above, the TSTF concludes that the proposed change presents no significant hazards considerations under the standards set forth in 10 CFR 50.92(c), and, accordingly, a finding of "no significant hazards consideration" is justified.
TSTF-529, Rev. 0  Page 21 5.2 Applicable Regulatory Requirements/Criteria Title 10 of the Code of Federal Regulations, Paragraph 50.36, requires Technical Specifications and describes the Limiti ng Conditions for Operation (LCOs) and Surveillances. The proposed change clarifies the implementation of the Technical Specifications required by 10 CFR 50.36.
Based on the considerations discussed above, (1) there is reasonabl e assurance that the health and safety of the public will not be endangered by operation in the proposed manner, (2) such activities will be conducted in compliance with the Commission's regulations, and (3) the approva l of the proposed change will not be inimical to the common defense and security or to th e health and safety of the public. 6.0 Environmental Consideration A review has determined that 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 hazard s 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. 7.0 References
: 1. Generic Letter 87-09, "Sections 3.0 And 4.0 of Standard Tech Specs on Limiting Conditions For Operation And Surveillance Requirements," dated June 6, 1987 (Attachment 1).
: 2. NRC memorandum, "Summary of Meeting Held on September 17, 1987 Relating to Generic Letter 87-09," dated October 20, 1987 (Attachment 2).
: 3. Inspection Manual Part 9900 Technical Guidance document, "Standard Technical Specifications (STS) Section 3.0.3 Limiting Conditions for Operation" (Attachment 3).
: 4. NRC Inspection Manual Part 9900 Technical Guidance document, "Voluntary Entry into Limiting Conditions for Operation Action Statements to Perform Preventative Maintenance," (Attachment 4).
: 5. NRC Enforcement Manual, Revision 7, October 1, 2010.
 
TSTF-529, Rev. 0
 
Attachment 1 Generic Letter 87-09, "Sections 3.0 and 4.0 of Standard Tech Specs on Limiting Conditions For Operation And Surveillance Requirements," dated June 6, 1987 TSTF-529, Rev. 0
*< ? ,
* NUCLEAR REGULA ORY COMMISSION WASHINGTO
* D. C. 205&5 June 4, 1987 TO ALL LIGHT WATER REACTOR LICENSEES AND APPLICANTS Gentlemen:
 
==SUBJECT:==
SECTIONS 3.0 AND 4.0 OF THE STANDARD TECHNICAL SPECIFICATIONS (ST5) ON APPLICABILITY OF LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS (Generfc Letter 87-09) . As a part of recent initiatives to improve Technical Specifications (TS). the NRC, in cooperation with the Atomic Industrial Forum (AIF', has developed a . program for TS improvements.
One of the elements of this program the implementation of short-term improvements to resolve immediate concerns that have been identified in investigations of T5 problems by both NRC and AIF. The guidance provided in this generic letter addresses three specffic problems that have been encountered with the general requirements on the applicability of Limiting Conditions for Operation (LCO) and Surveillance Requirements in Sections 3.0 and 4.0 of the STS. There are five enclosures to this GeneriC letter. Enclosure 1 applies to both PWR and BWR STS and provides a complete discussion of the three problems and the staff's position on acceptable modifications of the T5 to resolve them. These modifications' should result in improved T5 for all plants and are consistent with the recommendations of NUREG-1024. -Technical Specifications Enhancing the Safety Impact" and the Corrmission PO'1-icy Statement on Technical Specification Improvements.
Enclosures 2 and 4 provide Sections 3.0 and 4.0 of the PWR and BWR S1S', respectively, which incorporate*'the mOdiffcations being made by this Generic Letter. Enclosures 3 and 5: (a) provfde the staff's update of the bases for the PWR and BWR STS, respectivel.y; (b) re.fleet the modifications of Sections 3.0 and 4.0 of the S1S; and (c) include fmproved bases for the unchanged requirements in these sections.
The staff concludes that these modffications will result in improved TS for all plants. licensees and applicants are encouragea to propose changes to their 1S that are consistent wfth the guidance provided fn the enclosures; however. these changes are voluntary fora" licensees and current OL applicants.
The staff would like to point out three important pOints connected with the present 1S effort. First. it is aware that the TS can be clarified, simplified.
and streamlined both as a whole and with respect to the specifications that are the subject of this Generfe Letter. Nonetheless, in keeping with its short-term and purposefully narrow focus, it decided to keep these proposed modifications: (a1 focused on the three problems; (b) relatively simple; and ec l consistent with the phrasing of existing TS. Second, after the resolution of these and other identified TS problems, the staff will notify licensees and applicants of its conclusions and resulting proposals for additional short-term T5 improvements.
Finally, the staff is not proposing to formally amend the STS at this time. Instead the changes will be factored into the development of the new STS anticipated as a part of the implementation of the Commission's PoliCY Statement on Technical Specification Improvements.
8706090039 TSTF-529, Rev. 0-2 .. The following is a sUIm1ary of the three problems covered by the enclosures.
The first problem involves unnecessary restrict10ns on mode changes by Specification 3.0.4 and inconsistent application of exceptions to it. The practical solution is to change tHis specification to define the condftions under which its requirements apply. With respect to unnecessary mode changes. Specification 3.0.4 unduly restricts facility operation when conformance with Action Requirements provides.
an acceptable level of s3fety for continued operation.
For an LCO that has Action Requirements permitting continued operation for an unlimited period of time. entry into an operation mode or other specified condition of operation should be permitted in accordance with the Action Requirements.
The solution also resolves the problew of inconsistent application of exceptions to SpeCification 3.0.4: (a) which' delays startup under conditions in which conformance to the Action Requirements establishes an acceptable level of safety for unlimited continued operation of the facility.;
and (b) which delays a return to power operation when the facility is required to be in a lower mode of operation as a consequence of other Action Requirements.
The second problem involves unnecessary shutdowns caused by Specification
.4.0.3 when surveillance intervals are inadvertently exceeded.
The solution is to clarify the applicabi11ty of the Action Requirements, to specify a specific acceptable time limit for completing a missed surveillance in certain circumstances.
and to clarify when a missed surveillance constitutes a violation of the Operabi1ity Requirements of an LCD. It is overly conservative to assume that *systems or components -Ire inoperable when a surveillance has not been performed because the vast majority of surveillances do in fact demonstrate that systems or components are operable.
When a surveillance is missed, it is primarily a question of operability that has not been verified by the performance of a Surveillance Requirement.
Because the allowable outage time limits of some Action Requirements do not provide an appropriate time for performing a missed surveillance before Shutdown ReqUirements apply. the TS should include a time limit that allows a delay of . required actions to permit the performance of the missed surveillance based on consideration of plant conditions, adequate planning t availability of personnei.
the time required to perform the surveiiiance, and. of course, the safety significance of the delay in completing the surveillance.
The staff has concluded that 24 hours is an acceptable time limit for completing' missed surveillance when the allowable outage times of the Action Requirements are less than this, limit. or when time is needed to obtain a temporary waiver of the Surveillance Requirement.
The third problem involves two possible conflicts between Specifications 4.0.3 . and 4.0.4. The first conflict arises because Specification 4.0.4 prohibits entry into an operational mode or other specified condition when Surveillance Requirements have not been performed within the specified surveillance interval.
A conflict with this requirement exists when a mode change is required as a consequence of Action Requirements and when the Surveillance . Requirements that become applicable have not been performed within the specifled surveillance interval.
Specification 4.0.4 should not be used to prevent passage through or to operational modes as required to comply with jI,ct10n . Requirements because to do so: (aj would increase the potential for a plant * ..
TSTF-529, Rev. 0
* -3
* upset; and (b) would challenge safety systems. Also. certain surveil'ance( should be allowed to be performed during a shutdown to comply with Action Requirements.
Along with the modification of Specification 4.0.3 to permit a del.r of up to 24 hours fn the applicability of Action Requirements.
Specificatfon 4.0.4 has been clarified to allow passage through or to . operational modes as required to comply with Actfon Requfrements.
A second conflict could arise because. when Surveillance Requirements Cln only be completed after entry into a mode or speCified condition for which the Survefllance Requirements apply, an exception to the requirements of Specification 4.0.4 is allowed. However, upon entry into this mode or condition, the requirements of Specification 4.0.3 may not be met because the Surveillance Requirements may not have been performed within the allowed surveillance interval.
Therefore.
to avoid any conflict between Specifications 4.0.3 and 4.0.4. the staff wants to make clear: (a) that it is not the intent of Specification 4.0.3 that the Action Requirements preclude the performance of surveillances allowed under any exception to Specificatfon 4.0.4i and (b) that the delay of up to 24 hours in Specification 4.0.3 for the applicability of . Action Requirements now provides an appropriate time limit for the completion of those Surveillance Requirements that become applicable as a consequence of allowance of any exception to Specification 4.0.4 * . If you have any questions on this matter. please contact your project manager.
 
==Enclosures:==
 
As stated Sincerely, . . Frank
** Assocfate Dfrector for Projects Office of Nuclear Reactor Regulation TSTF-529, Rev. 0 I I I ,
* INTRODUCTION Enclosure 1 to Generic Letter 87-09 ALTERNATIVES TO THE STS REQUIREMENTS TO RESOLVE THREE SPECIFIC PROBLEMS WITH LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS_
Generic Letter 87-09 discusses three problems regard1ng the general requirements of Sections 3.0 and 4.0 of theSTS on the applicability of Limiting Conditions for Operation (LCO) and Surveillance Requirements.
The guidance provided in this enclosure addresses alternatives to the Standard Technical Specifications (ST5) to resolve these problems.
Problem #1 --UNNECESSARY RESTRICTIONS ON MODE CHANGES (Specification 4.0.3) BACKGROUND The definition of an LCO is given in 10 CFR 50.36 as the lowest functional capability or performance level of equipment requfred for safe operation of the Further, it is stated that when an LCO of a nuclear reactor is not met, the licensee shall shut down the reactor or follow any remedial action permitted by the TS unt'n the condition can be met. "" Consistent with NRC's regulatory requirements for an LCO. the T5 include two baSic types of Action Requirements that are applicable when the LCO is not met. The first specifies -the remedial actions that permit continued operation of the facility not restricted by the time limits of Action Requirements.
In this case, conformance to the Action an acceptable leve' of safety for continued operation of the facility, and operation lilY proceed indefinitely as long as the remedial Action Requirements are met. The second type of Action Requirement specifies a time limit in which the LCO must be met. This time limit is the time allowed to restore an inoperable system or cOllponent to operable status or to restore parameters within specified lill1ts. If these actions are not completed within the allowable outage time limits, action must be to shut down the facility by placing it in a mode or condition of operation in which the LCO does not apply_ Specification 3.0.4 of the STS states that entry into an operational model or other specified condition shall not be made unless the LCD is met without reliance on the provfsfons of the Action Requirements.
Its intent is to ensure that a higher mode of operation is not entered when equipment is inoperable or when parameters exceed their specified limits. This precludes a plant startup -when actions are being taken to satisfy an LCO, Which --if not completed within the time limits of the Action Requirements would result in a plant shutdown to comply with the Petian ReqUirements.
lThe BWR STS use the term "operational condition" instead of the term "operational mode" that is used in PWR STS. As used here, "operational model. means "operational condition" for BWRs.
TSTF-529, Rev. 0 Specification 3.0.4 also precludes entering a mode or specified condition if an LeO is not met. even if the Action Requirements would permit continued operation of the facility for an unlimited period of time. Generally, the individual specifications that have Action Requirements which allow continued operation note that Specification 3.0.4 does not,apply.
However, exceptions to Specification 3.0.4 have not been consistently applied and their bases are not well documented.
For example. approximately two*thfrds of the actions permit continued operation in the Westingbouse STS are exempt from Specification 3.0.4. Although the staff encourages the maintenance of all plant systems and components in an operable condition as a good practice, the T5 generally have not precluded entering a mode with inoperable equipment when the Action . Requirements include remedial measures that provide an acceptable level of safety for continued operation.
o STATEMENT OF THE Inconsistent application of exceptions to Specification 3.0.4 impacts the operatfon (if the facility in two First. it delays startup under " .. conditions in which confonnance to the Action Requirements establishes an acceptable level of safety for unlimited continued operation of the facility.
Second. it delays a return to power operation when the facility is required to be in a lower mode of operation as a consequence of other Action Requirements.
In this case, the LeO must be met without reliance on the Action Requirements before returning the facility to that operational mode or other specified condition for which unlimited continued operation was previously permitted in accordance with the Action Requirements.
o STAFF POSITION Jt>. Specification 3.0.4 unduly restricts facility operation when conformance to the Action Requirements provides an acceptable level of for continued operation.
For an lCO that has Action Requirements permitting continued operati"on for an unlimited period of time, entry into an operational mode or other specified condition of operation should be permitted in accordance with those Action Requirements.
This is consistent with NRC's regulatory requirements for an LCO. The restriction on a change in operational modes or other specified conditions should apply only where the Action Requirements establish a specif1ed time interval in which the LeO must be met or a shutdown of the facility would be required.
However, nothing 1n this staff position should be interpreted as endorsing or encouraging a plant startup with inoperable equipment.
The staff believes that good practice should dictate that the plant startup should normally be initiated only when all required equipment is operable and that startup with inoperable equipment must be the exception rather than the rule. o CHANGE TO SPECIFICATION 3.D.4 The practical solution to this problem is'not the modif;cat10n of TS to note that Specification 3.0.4 does not apply, but rather a change to Specification 3.0.4 to define the conditions under which its requirements do apply. Therefore, Specification 3.0.4 will be revised to state: .. 2 -*
TSTF-529, Rev. 0 Q "Entry into an OPERATIONAL MODE or other specified condition' shall not be made when the conditions for the Limiting Conditions for Operation are not met and the associated ACTION requires a shutdown if they are not met within a specified time interva1.
Entry into an OPEP-ATIONAL MODE or specified condition may be made in accordance with ACTION requirements when conformance to them perm1ts continued operation of the facility for an unlimited period of time." CHANGES TO INDIVIDUAL SPECIFICATIONS EXEMPT FROM SPECIFICATION 3.0.4 As a consequence of modification described above to Specification 3.0.4, individual specifications with Action Requirements permitting continued operation no longer need to indicate that Specification 3.0.4 does not apply. They should be revised to delete the noted exception to avoid confusion about the applicability of Specification 3.0.4. However, exceptions to Specification 3.0.4 should not be deleted for individual specifications if a mode change would be precluded by Specification 3.0.4 as revised. For example, some specifications would not satisfy the provisions under which mode changes are permitted by the revision to Specification 3.0.4 and, therefore, the exception to Specification 3.0.4 need not be deleted. It is not the staff's intent that the revision of SpeCification 3.0.4 should result in more restrictive reqUirements for individual speCifications.
Problem 12 --UNNECESSARY SHUTDOWNS CAUSED BY INADVERTENT SURPASSING OF SUPVEIltANCE INTERVALS (Specification 4.0.3) BACKGROUND eo Surveillance ReqUirements are defined in 10 CFR 50.36 as those relating to calibration, or inspection to ensure that the necessary quality of systems and components is maintained, that the facility will be within the safety limits, and that the LCO will be met. Consistent with the NRC's regulatory framework for Surveillance Requirements, Specification 4.0.3 states that the failure to perform a surveillance within the specified time interval shall constitute a failure to meet the LCO's Operability Requirements.
Therefore, if a Surveillance Requirement is not met as a result of the failure to schedule the performance of the surveillance, the LCO would not be met. Consequently, the Action Requirements must be met as when a surveillance verifies that a system or component is inoperable.
Generally, the Action Requirements include a specified time interval (i.e., allowable outage limit) that permits corrective action to be taken to satisfy the LCD. When such a specified time interval ;s included in the Action Requirements, the completion of a missed surveillance within this time interval satisfies Specification 4.0.3. o STATEMENT OF PROBLEM Some Action Requirements have allowable outage time limits of only one or two , . hours and do not establish a practical time limit for the completion of a missed Survei11ance Requirement.
If surveillances cannot be completed within these TSTF-529, Rev. 0 time limits, a plant shutdown would usually be required.
Even if the Action Requirements include remedial measures that would pennit continued operation, they may be stated in such a way that they could prevent the perfonnance of the required surveillance.
A plant shutdown would also be required if the missed surveillance applies to more than the minimum number of systems or components reouired to be operable for operation under the allowable outage time limits of the Action Requirements.
In this case, the individual specification or Specification 3.0.3 would require a shutdown. . 1f a plant shutdown is required before' a missed surveillance is completed, it is likely that it would be conducted when the plant is being shut down because completion of a missed surveillance would tenninate the shutdown requirement.
This is undesirable since it increases the risk to the plant and public safety for two reasons. First, the plant would be in a transient state involving changing plant conditions that offer the potential for an upset that could lead to a demand for the system or component being tested. This would occur when the system or component is. either out of service to allow performance of the .surveillance test or there fs a lower level of confidence in 1ts operability because the nannal surveillance interval was exceeded., If the surveillance did , demonstrate that the system or component was inoperable, it usually would be preferable to restore it to operable status before making a major change in plant operating' conditions.
Second, a shutdown would increase the pressure on the plant to expeditiously complete the required surveillance so that the plant could be returned to power operation.
This would further increase the 'potential for a plant upset when both the ,shutdown and survetllance activities place a demand on the plant operators.
o STAFF POSITrON . It is overly conservative to assume that systems or components are inoperable when ,a surveillance requirement has not been performed.
The oppOSite fs in fact the case; the vast majority of surveil lances demonstrate that ,systems or components in fact are operable.
When a surveillance is missed, it is primarily a question of operabflity that has not been verified by the performance of the required surveillance.
Because the allowable outage time limits of some Action Requirements do not provide an appropriate time limit for performing a missed surveillance before shutdown requirements may apply. the TS should include a time limit that would allow a delay of the required actfons to permit the performance of the missed surveillance.
This time limit should be based on considerations of plant conditions, adequate planning, availability of personnel, the time required to perform the surveillance, as well as the safety Significance of the delay in COMpletion of the surveillance.
After reviewing possible limits, the staff has concluded that, based on these conSiderations, ?4 hours would be an acceptable time limit for completing a missed surveillance when the allowable outage times of the Action Requirements are less than this tiMP limit or when shutdown Action Requirements apply. The 24-hour time limit would balance the risks associated with an allowance for ccrnpletin9 the surveillance within this period against the risks associated with the potertial for a plant upset and challenge to safety c systems when the alternative is a shutdown to comply with Action Requirements " before thp surveillance can be completed.
TSTF-529, Rev. 0
'1 r t J ' :e I * , Although a missed surveillance would generally be cmpleted in less t1'me than this 24-hour limit allows, special circumstances may require additional time to ensure that the surveillance can be conducted fn a safe manner. The time , l1mfts of Action Requirements for surveillances should start when it is identified that Survefllance Requirements have not been performed.
except when the Z4-hour delay fs allowed fn the fmplementation,of the Action Requfrements.
Where the 24-hour time lfmit is allowed, the time lfm1ts of the Action' Requirements are applicable either at the end of the, 24-hour limit if the . surveillance has not been completed or at the time the surveillance is performed if the system or componeltt is found to be inoperable.
/ Sever.l issues need to be clariffed regarding the additional 24-hour time , limit. First, thfs limit does not waive compliance wfth Specif1catfon 4.0.3. Under Specification 4.0.3, the faflure to perform a Surveillance Requirement wfll continue to constitute noncompliance with the Operability P.equ1rements of an LCO and to bring into play the applicable Action Requirements'.
Second, Specifications 3.0.2 and 4.0.3 should not be misinterpreted.
Specification 3.0.2 notes that a TS is being complied with the Action Requirements are met within the specified time intervals.
Although Specification 4.0.2 provides an allowance for extending the surveillance interval and allows for the completion of the surveillance within this time fnterval without violation of this Specification, under Specification 4.0.3 nonperformance of a Surveillance Requirement.
within th, allowed surveillance 1nterval defined by Specification 4.0.2, constitutes a violation of the ,Operability Requirements of an LCO. as defined by Specification 4.0.3, and is subject to enforcement action. ' To avoid any conflict among or misread1ng of Specffications 3.0.2, 4.0.3, and 4.0.2, the staff wishes to make clear (lJ that Specfficat10n 3.0.2 shall not be construed to imply, that the completion of a missed surveillance w1thfn the allowable outage time limits of the Action Requirements
--whether or not the additional 24 M hour time limit 1s 1ncluded --negates the vfolation of Specificat10n 4.0.3, and (2) that the failure to perform a surveillance withfn the allowable surveillance interval defined by Specification 4.0.2 constitutes a reportable event under 10 CFR 50.73(a)(2)(i}(8) because it is a condition prohibited by the plant1s TS. Third, even though an addit10nal 24-hour time limit may apply for missed surveillances, another consideratfon is the possfbility that plant conditions may preclude the performance of the speciffed requirements.
The provisfon of a 24-hour delay in the application of the Action Requirements for the completion of a missed surveillance would provide time to obtain a temporary waiver of a Surveillance Requirement that could not otherwise be completed because of current plant conditions.
If a surveillance can be performed only when the plant 1s ,shut down, there are only two options available to licensees when a missed surveillance is discovered durfng power operation and continued operation'is not allowed under the Action Reouirements.
The first is to shut down the plant and perform the required surveillance.
The other option is to seek relief from the Surveillance Requirement.
Such relief would result in the processing of a T5 amendment.
As a matter of existing policy. a temporary wafver of compliance with a TS that would unnecessarily require a shutdown or "
TSTF-529, Rev. 0 , . delay startup absence of some relief may be granted by NRC. A temporary waiver of compliance may be granted if the licensee has demonstrated in a e written submittal.
provided before the TS LCO expired, that the facil ity can 'safely continue to operate w,thout compliance with the TS during the time it will take to process the TS amendment,request.
o CHANGE TO SPECIFICATION 4.0.3 Specification 4 .. 0.3 w111 be revised Isfollow$
to clarify when a missed surveillance constitutes a violation of the Operability Requirements of an LCO and to clarify the applicability of the Action Requirements and, the time during which the' limits apply: "Fa 11 ure to perform a Surveil 1 ance Requi rement wi thi n the a 11 owed surveillance interval, defined by Specification 4.0.2. shall constitute noncompliance" with the OPERABILITY requirements for a Limiting Condition for Operation., The time limits of the ACTION requirements are applicable at the time it is identified that a Surveillance Requirement has not been performed.
The ACTION requirements may be delayed for up to 24 hours to permit the cOllPletion of the surveillance when the allowable outage time limits of the ACTION requirements are less than 24 hours." Specification 4.0.3 previously included the statement that exceptions to it are stated in individual specifications.
This statement is deleted because Specification 4.0.3 is* always applicable, i.e., the impl'ed exceptions for individual specifications do not exist. Problem 13 --CONflICTS BETWEEN SPECIFICATtONS 4.0.3 AND 4.0.4 RELATEb To MODE CHANGES {specification 4.0.4} There.are two parts of the general problem of conflicts between Specifications 4.0.,3 and 4.0.4 related tOlDOde changes. Each of these parts is discussed separately below. Part 1 --SURVEILLANCE REQUIREMENTS THAT BECOME APPLICABLE DUE TO ACTION REQUIREMENTs o STATEMENT OF THE PROBLEM C" .. ,. Specification 4.0.4 prohibits entry into an operational mode or other specified condition when Surveillance Requirements have not been performed with1n the specified surveillance interval.
First, a conflict with this TS exists when a mode change is required as a consequence of shutdown Action Requirements and when the Surve'i11ance Requirements that become applicable have not been performed within the specified surveillance interval.
For instance, the plant could previously have been in a mode for which the Surveillance Requirements were not applicable and, therefore.
the surveillance may not have been performed within the specified time interval.
Consequently, the Action Requirements of the LCO associated with these Surveillance Requirements apply and the unit may have to be placed in a lower mode of operation than that required by the* , original shutdown Action Requirements, or other remedial actions may have to be TSTF-529, Rev. 0 If:*I. ,\?" ...... : t I
* taken. if the surveillance cannot be completed within the time limits for these actions. This is a second problem that may be encountered.
The first problem arises because conformance with Specification 4.0.4 would . requfre the performance of these. surveillances before entering a mode for whfch they apply. Source and intennediate range nuclear instrumentation and cold* overpressure protection systems in PWRs are examples of systems for which Survef 11 ance . Requi rements may become app 1 i cab 1 e as a consequence*
of 'mode. . . changes to comply with shutdown Action P.equirements.
The second problem has been mitigated by the change in Specification 4.0.3 to a delay of up to 24 hours in the applicability of the Action Requirements, thereby placing an appropriate time limit on the completion of Surveillance Requirements that become appl icable as a consequence of mode changes to comply w1th Requirements.
However, the first problem can be further resolved by a change to Spec1fication 4.0.4. . o STAFF POSITION The potential for a plant upset and challenge to safety systems is heightened if* surveillances are performed during a shutdown to comply with Action Requirements.
It is not the intent of Specificat10n 4.0.4 to prevent passage through or to operational modes to comply with Action Requirements and it should not apply when mode changes are imposed by Action Requirements.
Accordingly.
Specification, 4.0.4 should be modified to note that its. provisions shall not prevent passage through or to operational modes as required to comply with ' Action Requirements.
A 5i.milar provision is included in Specification 3.0.4
* o CHANGE TO SPECIFICATION 4.0.4 The following will clarify Specification 4.0.4 for mode changes as a consequence of Action Requirements: -This provision shall not prevent passage through or to OPERATIONAL as required to comply with ACTION Requirements.
a Part 2 --SURVEILLANCE REQUIREMENTS FOR EXCEPTIONS TO SPECIFICATION 4.0.4 (> STATEMENT OF THE PROBLEM An exception to Specification 4.0.4 is allowed when Surveillance Requirements can be completed only after entry into a mode or specified condition for which they apply. For example, the TS on power distribution limits are generally exempt from Specification 4.0.4. However, upon entry into the mode or specified.condition.
Specification 4.0.3 may not be met because the Survei 11ance Requirements may not have been perfonned within the allowed surveillance interval.
Generally, these Surveillance Requirements apply to redundant systems, and Specification 3.0.3 would apply because they are treated as inoperable under Specification 4.0.3. Therefore, allowance of an exception to Specification 4.0.4 can create a conflict with Specification 4.0.3. 7 -
TSTF-529, Rev. 0 o STAFF POSITION It is not the intent of Spp.cification 4.0.3 that the Action Requirements should preclude the performance of surveillances when an exception to Specification 4.0.4 is allowed. However, since Specification 4.0.3 has been changed to permit a delay of up to 24 hours in the appl i'cability of the Action Requirements, an appropriate time limit now exists for the completion of those Surveillance Requirements that become applicable when an exception to Specification 4.0.4 is al1owed.
TSTF-529, Rev. 0 , . Enclosure 2 to Generic Letter 87-09 3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS 3/4.0 "APPLICABILITY
[NOTE: On,ly Specifications 3.0.4. 4.0.3, and 4.0.4 are being modified, as shown in the underlined provisions.
The other speciffcations are shown for information only.) LIMITING CONDITIONS FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding specifications is required during the OPERATIONAL MODES or other conditions specified therein; except that upon failure to the Limiting Conditions for Operation, the associated ACTION requirements shall be met. 3.0.2 Noncomplfance wfth a specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals.
If the Limiting Condition for . Operation is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required.
3.0.3 When a Limiting Condition for Operation is not met, except as prov1ded in the associated ACTION requirements, with1n 1 hour action shall be inftiated to place it. as applicable, in: a. At least HOT STANDBY within the next 6 hours, b. At least HOT SHUTDOWN within the following 6 hours, and c. At least COLD SHUTDOWN within the subsequent 24 hours. Where corrective measures are completed that permit operation under the ACTION requirements, the action may be taken in accordance with the specified time limits as measured from the time of fa11ure to meet the Limiting Condition for Operation.
Exceptions to these requirements are stated 1n the indiVidual specificat10ns.
This specif1cation is not applicable in. MODES 5 or 6. PWR STS 3/4.0 .. 1 TSTF-529, Rev. 0 APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements sha'll be met during the OPERATIONAL MODES or other conditions specified for individual Limiting Conditions for Operation unless otherwise stated in an individual Surveillance ReqUirement.
4.0.2 Each Surveillance Requirement shall be performed within the specified time interval with: a. A maximum allowable extension not to exceed 25% of the surveillance interval, but b. The combined time interval for any three consecutive surveillance intervals shall not exceed 3.25 times the specified surveillance interval.
4.0.5 Surveillance Requirements for 1nservice inspection and testing of ASME Code Class 1, 2, and 3 cOII'Iponents shall be applicable as follows: a. Inservice inspection of ASME Ccde 1, 2, and 3 components and inservice testing of ASME Code Class 1, 2, and 3 pumps and valves shall be performed in accordance with Section XI of the Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50, Section SO.55a(g), except where specific written relief has been granted by the Commission pursuant to 10 CFR 50, Section 50.55a(g)(6)(i).
: b. Surveillance intervals specified in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda for the inservfce inspection and testinp activities required by the ASME Boiler and PWR STS 3/4.0-2 (
TSTF-529, Rev. 0 APPLI CAB ILITY SURVEILLANCE REQUIREMENTS Pressure Vess.l Code .rid applfcable Addenda shall be applicable as follows in these Technical Specifications: . ASME Bofler and Pressure Vessel Code and applicable Addenda terminology for 1nservice inspection and testing activities Weekly Monthly Quarterly or ever" 3 months Semiannually or every 6 months Every 9 months Yearly or annually Required frequencies for performih9 inservice inspection Ind testing activities Xt ieast once per 7 days At least once per 31 days At least once per 92 days At 1 east once per 184 days At least once per 276 days At least once per 366 days c. The provisions of Specification 4.0.2 are applicable to the above . requfred frequencies for performing inservfce inspection and testing activitfes. . d. Performance of the above fnserv1ce inipection and testing activities shall be in addition to other specified Surveillance Requirements.
: e. PWR STS Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specffication. 3/4.0 ... 3 TSTF-529, Rev. 0
", : " I Enclosure 3 to Generic Letter 87-09 * : s 'enc osure provides r.evised Bases for all specifications in Sections 3.0 and 4.0.J BASES Specification 3.0.1 through 3.0.4 estabHsh the, general requirements applicable to Limiting conditions for Operation.
These requirements are based on the requirements for Limiting Conditions for Operation stated in the Code of ' Federal Regulations.
10 CFR 50.36(c)(2): , ftLimiting conditions for operation are the lowest functional capability or performance levels of equipment required for safe operation of the facility.
When a limiting condition for operation of a nuclear reactor is not met, the licensee shall shut down the reactor or follow any remedial action permitted by the technical specification until the condition can be met.-SpeCification 3.0.1 establishes the Applicability statement within each ind,vfdual specification as the requirement for when (i.e., in which OPERATIONAL MODES or other specified conditions) conformance to the Limiting Conditions for Operation is required for safe operation of the facility_
The ACTION requirements establish those remedial measures that must be taken within specified time lfmfts when the requirements of a Limiting Condftfon for Operation are not met. There are two basic types of ACTION reqUirements. first specifies the remedial meaSures that permit continued operation of the facility which is not further restricted by the time limits of the ACTION requirements.
In this case, conformance to the ACTION requirements provides an acceptable level of safety for un1imited continued operation as long as the ACTION requirements
' continue to be met. The second type of ACTION requirement specifies a time 1imit in which conformance to the conditions of the Limiting Condition for Operation must be met. This time limit is the allowable outage time to restore an inoperable system or component to OPERABLE status or for restoring parameters within specified limits. If these actions are not completed within the allowable outage time limits, a shutdown is required to place the facility in a MODE or condition in which the specification no longer applies. It is not intended that the shutdown ACTION requirements be used as an operational convenience which permits (routine) voluntary removal of a system{s) or component(s) from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.
The specified time l1mits of the ACTION requirements are applicable from the point in time it is identified that a Limiting Condition for Operation is not met. The time limits of the ACTION requirements are also applicable when a system or 'component is removed from service for surveillance testing or investigation of operational problems.
Individual specifications may include a specified time limit for the completion of 8 Surveillance Requirement when . equipment is removed from service. In this case, the allowable outage time PWR STS B 3/4.0-1 TSTF-529, Rev. 0 3/4.0 APPLICABILITY BASES (Can't) limits of the ACTION requirements are, applicable when this limit expires if the surveillance has not been completed.
When a shutdown is required to comply with ACTION requirements, the plant may have entered a MODE in w!1ich a new specification becomes applicable.
In this case, the time limits of the ACTION requirements would apply from the point in time that the new specification becomes applicable if the requirements of the limiting Condition for Operation are not met. Shecification 3.0.2 establishes that noncompliance with a specification exists w en the reouirements of the Limiting Condition for Operation are not met and the associated ACTION requirements have not been implemented within the specified time interva1.
The purpose of this specification is to clarify that (1) implementation of the ACTION requirements within the specified time interval constitutes compliance with a specification and (2) completion of the remedial measures of the ACTION requirements is not required when compliance with a Limiting Condition of Operation is restored within the time interval specified in the associated ACTION requirements.
Specification 3.0.3 establishes the shutdown ACTION requirements that must be implemented when a Limiting Condition for Operation 1s not met and the condition is not specifically addressed by the associated ACTION requirements. ( The purpose of this specification is to delineate the time limits for placing. l ..... the unit in a safe shutdown MODE when plant operation cannot be maintained , within the limits for safe operation defined by the Limiting Conditions for "':" Operation and its ACTION reqUirements.
It is not to be used as an operational convenience which 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.
One hour is allowed to prepare for an orderly shutdown before initiating a change in plant operation.
This time permits 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 reach 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 cooldown capabilities of the facility assuming only the minimum required equipment
;s OPERABLE.
This reduces thermal stresses on components of the primary coolant system and the potential for a plant upset that could challenge safety systems under conditions for which this specification applies. If remedial measures permitting limited continued operation of the facility under the provisions of the ACTION requirements are completed.
the shutdown may be terminated.
The time limits of the ACTION requirements are applicable from the point in time there was a failure to meet a limiting Condition for Operation.
Therefore, the shutdown may be terminated if the ACTION requirements have been met or the time limits of the ACTION requirements have not expired., thus providing an allowance for the completion of the required actions. PWR STS B 3/4.0-2 TSTF-529, Rev. 0 I f 'II' 3/4.0 APPLICABILITY BASES (Con't) The time limits of Specification-3.0.3 allow 37 hours for the plant to be in the COLD SHUTDOWN MOOE when a shutdown is required during the POWER MODE of operation.
If the plant is in a lower MODE of operation when a shutdown is required.
the time limit for reach-jng the next lower ,.,ODE of operation plies. However, if a lower MODE of operation is reached in less time than allowed, the total allowable time to reach COLD SHUTDOWN, or other applicable MODE. is not reduced. For example, if HOT STANDBY is reached in 2 hours, the time allowed to reach HOT SHUTDOWN is the next 11 hours because the total t'jnle to reach HOT SHUTDOWN is not reduced from the allowable limit of 13 hours. Therefore, if remedial measures are completed that would permit a return to POWER operation, a penalty is not incurred by having to reach a lower MODE of operation in less than the total time allowed. The same principle appltes with regard to the allowable outage ttme limits of the ACTION requirements.
if compliance with the ACTION requirements for one specification results in entry into a MODE or condition of operation for another specification in which the requirements of the Limiting Condition for Operation are not met. If the new specification becomes applicable in less .time than specified.
the difference may be added to the allowable outage time limits of the second specification.
However, the allowable outage time limits of ACTION requirements for a higher MODE of operation may not be used to extend the allowable outage time that is applicable when a Limiting Condition for Operation is not met in a lower MODE of operation. . The shutdown requirements of Specification 3.0.3 de not apply in MODES 5. and 6, because the ACTION reqUirements of individual specifications define the remedial measures to be taken. . Specification 3.0.4 establishes limitations on MODE changes when a Limiting Condition for Operation is not met. It precludes placing the facility in a higher MODE of operatfon when the requirements for a limiting Condition for Operation are not met and continued noncompliance to these conditions would result in a shutdown to comply with the ACTION requirements if a change in HODES were permitted.
The of this specification is to ensure that facility operation
;s not initiated or that higher MODES of operation are not entered when corrective actton is being taken to obtain compliance with a speCification by restoring equipment to OPERABLE status or parameters to specified limits. Compliance with ACTION requirements that permit continued operation of the facility for an unlimited period of time provides an able level of safety for continued operation without regard to the status of the plant before or after a MODE change. Therefore.
in this case. entry into an OPERATIONAL MODE or other specified condition may be made in accordance with the provisions of the ACTION requirements.
The provisions of this specification should not. however. be interpreted as endorsing thefallure to .exercise good practice in restoring systems or components to OPERABLE status before plant startup. PWR STS B 3/4.0-3 TSTF-529, Rev. 0 3/4.0 APPLICABILIj!
BASES (Con't) When a shutdown is required to comply wfth ACTION requfrements, the provisions of Specification 3.0.4 do not apply because they would delay placing the facility in a lower MODE of operation.
Specifications 4.0.1 through 4.0.5 establish the general requirements applicable to Surveillance Requirements.
These requirements are based on the Surveillance Requirements stated in the Code of Federal Regulations, , lOCFR 50.36{c)(3):
'" "Surveillance requirements are requ1rements relating to test. tion. or fnspection to ensure that the necessary qualfty of systems and components is maintained.
that facility operation will be within safety limits, and that the limiting conditions of operation will be met." Specification 4.0.1 establishes the requirement that surveillances must be performed dur1ng the OPERATIONAL MODES or other conditions for which the requirements of the Limiting Conditions for Operation apply unless otherwise stated fn an fndividual Surveillance Requirement.
The purpose of this specf-' f1cation is to ensure that surveillances are performed to verify the tional status of systems and components and that parameters are within fied limits to ensure safe operation of the facility when the piant is in a MODE or other specified condition for whfch the associated Limiting Conditions for Operation are applicatile.
Surveillance Requirements do not have to be ( performed when the facility is in an OPERATIONAL MODE for which the requirements
(,'0' of the associated Limitfng Condition for not apply unless otherwise specified.
The Surveillance Requirements associated with a Special Test "-Exception are only applicable when the Special Test Exception is used as an allowable exception to the requirements of a speciffcation.
Specification 4.0.2 establishes the conditions under which the specified time interval for Surveillance Requirements may be extended.
Item a.
an allowable extension of the normal surveillance interval to facilitate surveillance scheduling and consideration of plant operating conditions that may not be, suitable for conducting the surveillance; e.g., transient conditions or other ongoing surveillance or maintenance activities.
Item b. limits the use of the provisions of item a. to ensure that it is not used repeatedly to extend the surveillance interval beyond that specified.
The limits of Specification 4.0.2 are based on engineering judgment and the recognition that the most probable result of any particular surveillance being performed is the verification of conformance with the Surveillance Requirements.
These provisions are SUfficient to ensure that the reliability ensured through surveillance activities is not significantly degraded beyond that obtafned from the specified surveillance interval.
Specification 4.0.3 establishes the failure to perform a Surveillance
' Requirement within the allowed surveillance interval, defined by the provisions of Specification 4.0.2, as a condition that constitutes a faflure to meet the OPEPABILITY requirements for a Limiting Condition for Operation.
Under the PWR STS R 3/4.0 ... 4 ,
TSTF-529, Rev. 0 I I I j ! ! , j
* 314.0 APPLICABILITY BASE'S (Can't) , provfsions of this specification, ,systems and components are assumed to be when Surveillance Requirements have been satisfactorily performed withfn the specified time interval.
However, nothing in thfs provision'is to be construed as implying that systems or components are OPERABLE when they are found or known to be inoperable although still meeting the Surveillance Requirements.
This specification also clarifies that the ACTION requirements are applicable when Surveillance Requirements have not been completed within the allowed surveillance interval and that the time limits of the ACTION requirements apply from the point in time it is identified that a surveillance has not been performed and not at the time that the allowed surveillance interval was exceeded.
Completion of the Surveillance Requirement with1n the allowable outage time limits of the ACTION requ1rements restores complfance wfth the requ.irements of Specification 4.0.3. However, this does not negate the fact that the failure to have performed the survei llance within the allowed survefllance interval, defined by the provisions of Specif1cation 4.0.2, was a violation of the OPERABILITY requirements of a Limiting Condition for Operation that'is subject to enforcement action. Further, the failure to perform a surveillante within the provisions of Specification 4.0.2 is a violation of a Technical SpeCification requirement and 1s. therefore.
a reportable event under the requirements of 10 CFR SO.73(a)(2)(i)(B) because 1t is a condition prohibited by the plant's Technical Specifications.
If the aliowable outage tilne limits of the ACTION requirements are less than 24 hours or a shutdown is required to comply with ACTION requirements.
e.g., .Specif.ication 3.0.3, a 24-hour allowance is providtd to permit a delay in implementing the ACTION requirements.
This provides an adequate time limit to complete Surveillance Requirements that have not been performed.
The purpOSe of thfs allowance is to 'permit the completion of a surveillance before a shutdown is required to comply with ACTION requirements or before other remedial measures would be required that may preclude completion of a surveillance.
The basfs for this allowance includes consideration for plant conditions, adequate planning.
availability of personnel, the time required to perform the surveillance, and the safety significance of the delay in completing the required surveillance.
This provision also provides a time limit for the completion of Surveillance Requirements that become applicable as a consequence of MODE changes 1mposed by ACTION requirements and for completing Surveillance Requirements that are applicable when an exception to the requirements of Specification 4.0.4 is allowed. If a surveillance is not completed within the 24-hour allowance, the time limits of the ACTION reqUirements are applicable at that time. When a surveillance 1s performed within the 24-hour allowance and the Surveillance Requirements are not met, the time limits of the ACTION requ1 rernents are applicable at the time that the, surveillance is tenninated.
Surveillance Requirements do not have to be performed on inoperable equipment because the ACTION requirements define the remedial measures that apply. However, the Surveillance Requirements have to be met to demonstrate that \V, inoperable equipment has been restored to OPERABLE status. PWR STS B 3/4.0-5 '.
TSTF-529, Rev. 0 3/4.0 APPLICABILITY BASES (Can't) Specification 4.0.4 establishes the requirement th,t all applicable surveillances must be met before entry into an OPERATIONAL MODE or other condition of operation specified in the Applicability statement.
The purpose of th1$ specification is to ensure that system and component OPERABILITY requirements or parameter limits are met before entry into a MODE or condition for which these systems and components ensure safe of the facility.
This provisfon applies to changes in OPERATIONAL or other specified conditions associated with plant shutdown as well as startup. Under the provisions of this specification.
the applfcable Surveillance Requfrements must be performed within the specified surveillance interval to ensure that the Limiting Conditions for Operation are met during initial plant startup or follOWing a plant outage. When a shutdown is required to comply with ACTION requirements, the provisions of Specffication 4.0.4 dO not apply because this would delay placing the facility in a lower MODE of operation.
4.0.5 establishes the requirement that inservice inspection of A ME Code Class 1. 2. and 3 components and ir.serv1ce testing of ASME Code Class 1, 2, and 3 pumps and valves shall be performed in accordance with a periodically.updatedversion of Section XI of the ASME Boiler and Pressure Vessel Code and Addenda as required by 10 CFR 50.55a. These requirements apply except when relief has been provided in writing by the Commission
* .... This specification includes a clarification of the frequencies for performing the 1nservice inspection and testing activities required by Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda. This clarification is provided to ensure consistenty in surveillance intervals throughout the. Technical Specifications and to remove any ambiguities relative to the frequencfes for performing the required inservice inspection and testing activities. . Under the terms of this the more restrictive requirements of the TeChnical Specifications take precedence over the ASME Soiler and Pressure Vessel Code and applicable Addenda. The requirements of Specification 4.0.4 to perform surveillance activities before entry into an OPERATIONAL.
MODE or other specified condition takes precedence over the ASME Boiler and Pressure Vessel Code provision which allows pumps and valves to be tested up to one week after return to normal operation.
The Technical Specification definition of OPERABLE does not allow a grace period before a component, that 1s not capable of performing its specified function, is declared inoperable and takes precedence over the ASME Boiler and Pressure Vessel Code provision which allows a valve to be incapable of performfng its specffied function for up to 24 hours before being declared inoperable.
PWR STS 8.3/4.0-6
-.
TSTF-529, Rev. 0
',:: , "'f'
,"", 'l' : ' Enclosure 4 to Generic Letter 87-09 3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS 3/4.0 APPLICABILITY
[NOTE: Only Specifications 3.0.4, 4.0.3, and 4.0.4 are being modified, as shown in the underlined provisions.
The other specifications are shown for information only.] LIMITING CONDITIONS FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation ,contained in the succeeding Specifications is required during the OPERATIONAL CONDITIONS or other conditions specified therein; except that upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be met. 3.0.2 Noncompliance with a Specification shall exist when the requirements of the Lfmiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals.
If the Limiting Condition for Operation 1s restored prior to exp1ration of the specified time intervals, complet10n of the ACTION requirements fs not required.
3.Q.3 When a Limiting Condition for Operatior.
is not met, except as provided in the associated ACTION requirements, w1thin one hour action shall be inftiated to place the unit in an CONDITION in wh1ch the Specification does not apply by placing it. as applfcable, 1n: 1., At least STARTUP within the next 6 hourS: 2. At least HOT SHUTDOWN within the following 6 hours. and 3. At least COLD SHUTDOWN within the subsequent 24 hours. Where corrective measures are cOlflpleted that permit operation under the ACTION requ1rements, the action may be taken in accordance with the specified time limits as measured from the time of failure to meet the Limit1ng Condition for Operation.
Excppt-io"s to these requireme"ts are stated in the indfyfdual Specifications
.. This specification is not applfcable in OPERATIONAL CONDITION 4 or 5. BWR STS 3/4.0-1 TSTF-529, Rev. 0.1 APPLICABILITY SURVEILLANCE REQUIREMFNTS 4.0.1 Surveillance Requirements shal1 be met during the OPERATIONAL CONDITIONS or other conditions specified for individual Limiting Conditions for Operation unless otherwise stated in an individual Surveillance . Requirement.
4.0.2 Each Surveillance Requirement shall be performed with1n the specified time interval with: I.. A maximum allowab.1e extension not to exceed 25% of the surveillance interval, but b.The combined time interval for any 3 consecutive surveillance intervals shall not exceed 3.25 t1mes the specified surveillance interval.
I/j 4.0.3 Failure to perform a Surveillance Requ1rement within the allowed surveillance interval.
defined b, Spec1ficat;on 4.0.2. shall constitute noncompliance with the OPERABILt Y requirements for a Limiting Condition for Operation.
The time limits of the ACTION reQuirements applicable at the time it 15 identified that a Survefllance Re,u1rement has not been performed.
The ActIoN requirements may be delayed or up to 24 hours to &#xa5;erm1t the comx,etion of the surveillance when the allowable outaTe time im1ts of the eTION requirements are less than 24 hours. Survei lance 4 .. Requ1 rements do not have to be performed on 1nope14b1e equ1 pment. ..... 4.0.4 Entry into an OPERATIONAL CONDITION or other specified applicable condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation have been performed within the applicable surveillance interval or as otherwise specified.
This provision shall not Rrevent passage through or to OPERATIONAL CONDITIONS as required to comp 1 y wit ACTION requ i rements * . 4.0.5 Surveillance Requirements for inserv1ce inspection and testing of ASME Code Class 1, 2, and 3 components shall be applicable as follows: a. Inservice inspection of ASHE Code elas.s 1. 2, and 3 components and 1nservice testing of ASHE Code Class 1, 2. and 3 pumps and valves shall be performed in accordance with Section XI of the ASHE Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50, Section 50.55a(g), except where specific written relief has been granted by the Commission pursuant to 10 CFR 50, Section 50.55a(9)(6)(1,. . b. Surveillance intervals specified in Section XI of the ASHE Boiler and Pressure Vessel Code and applicable Addenda for the inservice inspection and testing activities required by the ASHE Boiler and BWR STS 3/4.0-2 TSTF-529, Rev. 0. ;-" 4' t{. " APPLI CABILITY SURVEILLANCE REQUIREMENTS Pressure Vessel Code and applicable Addenda shall follows 1n these Specificat10ns:
be app11cable as ASHE Boiler and Pressur! Vessel Required frequenc1es Code and applicable Addenda for performing inservice terMinology for inservice inspection and testing inse!ction and testing activities activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months Every 9 IIOnths At . least once per 184 days At least once per 216 days Yearly or annually At least once per 366 days c. The provfsions of Specification 4.0.2 are applicable to the above required frequencies for performing inserv1ce inspection and testing activitfes.
: d. Performance of the above inservice inspection andtestfng activities shall be in addition to other spec1fied Surveillance Requirements.
e .. Nothing in the ASHE Bofler and Pressure Vessel Code shall be construed to supersede the requirements of any Technical Specification. BWR STS 3/4.0-3 TSTF-529, Rev. 0
(:0' ;" . Enclosure 5 to Generic Letter 87-09 3/4 LIMITING CONDITIONS FOR OPE'RATION AND SliRVEILLANCE' PFgUIREMENTS 3/4.0 ApPLICABILITY . [NOTE: This enclosure provides revised Bases for all speCifications in Sections 3.0 and 4.0.J BASES Specifications 3.0.1 through 3.0.4 establish the general requirements applicable to limiting Conditions for Operation.
These requirements are based on the requirements for Conditions for Operation stated in the Code of Federal Regulations, 10 CFR 50.36(c)(2): "Limiting conditions for operation are the lowest functional capability or performance levels of equipment required for safe operation of the . facility.
When a limiting condition for operation of a nuclear reactor is not met, the licensee shall shut down the reactor or follow any remedial action permitted by the technical specification until the conditfon can be met.n . Specification 3.0.1 establishes the Applicability statement within each individual specification as the requirement for when (f.e., in which OPERATIONAL CONDITIONS or other specif1ed conditions) confo'rmance to the Limiting Conditions for Operation is requ;red for safe operation of the facility.
The ACTION requ1rements establish those remedial measures that must be taken within specif1ed time limits when the requirements of a Limiting Condition for Operation are not met. It is not intended that the shutdown ACTION requirements he used IS an operational convenience which pennits (routine) voluntary removal of a system(s) or component(s) .from servfce in lieu of other alternatives that would not result in redundant systems or components being fnoperable.
There are two basic types of ACTION requirements.
The first specifies the remedial measures that permit continued operation of the facility which is not further restricted by the time limits of the ACTION requirements.
In th1s case, conformance to the ACTION requirements provides an acceptable level of safety for unlimited continued operation as long as the ACTION requirements to be met. The second type of ACTION requirement specifies a time limit in which confonnance to the conditions.
of the Limiting Condition for Operation must be met. Th1s time limit is the allowable outage time to restore an inoperable system or component to OPERABLE status or for restoring parameters within specified limits. If these actions are not completed within the allowable outage time limits, a shutdown is required to place the facility in an OPERATIONAL CONDITION or other specif1ed condition in which the specification no longer applies. The specified time limits of the ACTION requirements are from the point in time it is identified that a Limiting for Operation is not met. The time limits of the ACTION requirements are also applicable when a system or component is removed from service for surveillance testing or investigation of operational problems.
Indiv1dual specifications may include a specified time limit for the completion of a Surveillance Requirement when BWR STS B 3/4.0-1 TSTF-529, Rev. 0
 
Attachment 2 NRC Memorandum, "Summary of Meeting Held on September 17, 1987 Relating to Generic Letter 87-09," dated October 20, 1987 TSTF-529, Rev. 0
/ , \ \ UNITiOrr.a.ru NUCLEAR REGULATORY COMMISSION D. c. .... OCT! 0 T9S7 OOCY.ET NOS: 50*325/324
& 50-400 LICENSEE:
CArolina Power Light Company FACILITY:
Shearon Harris, Unit 1
 
==SUBJECT:==
 
==SUMMARY==
OF MEETING HELD ON S&#xa3;PT&#xa3;MS&#xa3;R
: 17. 1ge1 RELATING TO GENERIC LETTER 87-09 A metting was held with representAtiYes of the Caro11na Power & Light in Bethesda.
MO. on 11, 1981 to discuss Generic Letter
*Sections 3.0 and 4.0 of the Standard Techn1ca1 Specifications (STS) on the applicability of Limiting Conditions for Operation and Surveillance Requirtments" dated June 4, 1987. as it relates to the Shearon Harris Unit 1 And the Srunswick Units 1 & 2 nuclear power plants. A list of attendees 1s 4ttachtd.
expressed concern about the potential for m1sinterpretation of the sentence underlined below, for ease of reference.
and which on a 3/4.0-1 of Inclosure 3 to Generic 87.09. Th. concern expressed fs that it could prohibit CPlL from gOing voluntarily into I Limiting Condition for Operaticn (LeO) 1n clrtain Just1ff&ble instances.
An txampie of such an instanct would bt if
* 1eak developed in a SI,l whieh in itself would not rendlr the inoperable but had the potlnt1., for rlndering the pump inoperable at a future date. CP&L would likl the option of voluntarily entering I LeO by isolating the and making tne required w1thout being cited for such action. The HRC sta1f noted that the underlined stCtion of the Sases for Specification 3.0.1. noted above. would not to the exampl. cited by CP&L since it is not I casl in whicn redundant s1stens would be out of sirvici. The staff noted that in addition to the two basic types 01 action requirements that art noted in the ,second paragraQh of the Sases for 3.0.1. a third type would define time limits for directly placing the plant in a shutdown condition.
It was neted that the sentence in question, underlined abave. that was a ,concern to CPIL was intended to apply to this of snutdown action requirement.
The staff noted that a Similar sintenci is includld in the Bases for Specification 3.0.3. In bath cases the point of clarification is that the last echelon of defense should not be removed service such that this would invoke a prompt shutdown ,action requirement.
in i,1eu of other tives that would not rtsult in redundant systems being out of servici simultaneously.
TSTF-529, Rev. 0
.. 'I. '.
LI!lkp.d f('lr D c1a.'iflcaUon of whln (I milled is "tpol'led untlur the LElt I.lll r , H"f !t(\rr stalud that If l\ rn1$ud lurvelllancp is not within the l1Clw1Incr.
fnr til('
1 nlfH'VII 1 ,H IH'{wiclt'c1 hy It he T"I-. 15 ct'nsistont with tho clnl'ifieallon of the LER Rlih thal I! p,'ovlcJccJ III NUREG-lOrZ.
SuppleOif.mt
: 11. CfJ&L aakod I r thOI'A WcH nlly I fltM1CP hp.twHefl lhe words tlflI11ul'e to "'t,lll ,\lid the wo,'d!l II non r.onlp11"nce with" \'Ihlch is C'II I','enl'y In Spnciflcatlo'1 4.0.3 or G(lIl(1r1r h" tar U7 .. 09. Tho
!-l&lted they hot.h mt!lln th.! SllRlG 41H.I thol It dO(,!1 110 t. lmposl" lillY /lOW I ,'ement , cc: See nox t paoo III lOt-;: S(lr ,\lld( hi'll 1 PI';I Onuck 1 (' Y hh It; ... . i i Udrl C. Ilurk'py, Pl'oJect ManGue,' Pt'nJ ('c t [lIn*; lUI',l te 11-1 IJivh lun ur 1:r.IIClOl' Pl'oJecls 1/l1 TSTF-529, Rev. 0
 
Attachment 3 Inspection Manual Part 9900 Technical Guidance document, "Standard Technical Specifications (STS) Section 3.0.3 Limiting Conditions for Operation" 
 
.. ' . .''''''' -:--UNITeO sr AT'ES NUCLEAA RIGULATOAY COMMISSfON W.$HtHGTON.
: o. e. 20IIf ' NRC INSPECTION MANUAL !LB6 PART 99CO: TECHNICAL GUIUAHC! STANDARD TECHNICAL SPEC!FlCATICHS STS SECTION 3.0.3 LIMITING FOR OPERATION I, A. PURPOSE .. To provide guidance en -Standard rlc:nnic:ai Specific:ations (STSLSectiOff 3.0.3 t as it r,l,tes to limiting for OPfrlt1,on (loCO). .' s . Reg,ions II I and V hive reported the incorrect us. 0' the pM2'41s10ns of STS , Sect;on 3.0.3 by 1icensees.
As an ex,mp1." Technic., Specific.tion 3.1.A.5.b for, O.,.esden anc Qu.d Cities, and simnar for other estab11sh .the c:on'tainment ox)'gen r'Quirement$
eluring' the ,4 hours pr10r to a shutdown, i'nc1 attar the N'etor moat switch has betn placefi in the ryn position on startup. If the oxygen-,"owab1. . the tlchn1ea' limit for mort than 24 hours prior to shutdown , fOr more thAn 24 hours after the reactor mode, .witch has been p11ctd in the i rJn position on startup, the p1ant is in v1ulat1on of the Ind should be .shut dewn 1 n accordanc!
with the Lea. However, the , ican... proposed to !"4 tnter LeO 3.0.3 at the end of the Z4-hour per10d .nd usa tnt of Leo 3.0.3 to nava an addition.'
'2 hour1 to shut down the p1ant. Technical
* Spec:1f1c;at1on J. 7.A.S.b, oefinesthe two conditions fa .. which oxygen eoncen-r tra:1on C.1n be exceeded.
FOr eith.r condition, an txp11cit Z4-hour time limit .;.. for $hutting down is pro4/1ded.
There Ire no ather c1rcumst.nclS which ar. not accounted for, Inc STS 3.0.3 does not app'Y. Tn. basic 1nfoMltat1on p,"ov1d.d tc.R ... 1ons I'! I Ind V the us. 01 STS 3.0.3 is diseu.,.d in the s.ct10n below. a. " 1 c. DISCUSSION i I.CO 1$ defined in STS 3.0.3 is not intended to be used IS an optrlt1onal "
Which redundant s,1ety systems to be out of serviCt for a i limited period of t1me. Its intended pu."ose 11 to provide guidance on the time limits for In shutdown when the 'nci1vidual LCD or ACTION stat.ments in other sflee1f1clt1ons cannot tM with. Voluntary tntry into LeO 3.0.3 d.1 1berat.ly r1lmOves 'lne l.st litte 0" d.f*,,5e .ga1nst potentially harmful events. Doing so allows removal of I system fram when the redund.nt system is .1rtldy An,'ct1on Hlh weld !! snow a disrl9ard for plant safety and ,s unac=eptab..
it a so SIIOU 1"* emphasfztd tijat removal of a sy,tam from service is ,just1fied only for ma1ntlnence, or repair purposes.
Issue Date: oa/31/87 TSTF-529, Rev. 0
 
Attachment 4 NRC Inspection Manual Part 9900 Technical Guidance document, "Voluntary Entry into Limiting Conditions for Operation Action Statements to Perform Preventative Maintenance" O' / UNITED STATES NUCLEAR REGULATORY COMMISSION WASHINGTON, D.C. :me, CIIII1 NRC INSPECTION MANUAL PART 9900: TECHNICAL GUIDANCE
* MAINTENANCE
-VOLUNTARY ENTRY INTO LIMITING CONDITIONS FOR OPERATION ACTION STATEMENTS TO PERFORM PREVENTIVE MAINTENANCE A. PURPOSE aTSS lCOPt1. TG To provide a set of safety princip1es for the performance of preventive maintenance (PH) at licensed nuclear reactor faCllit1es when the performance of the PM requires renaering the affected system or equipment inoperable (on-Line PM). Although these principles apply primarily to PM durinq power operation, they also apply tQ PM on that must be OPERABLE during shutdCWl evolutions such as fuel handling or m1d-loop operation:
This guidance provides qualitative criteria to assist in recognizing abuses of on-line PM. If such abuses are noted, they should be discussed with NRC management befOre they are discussed with the licensee.
This should ensure that , the guidance is applied in a reasonable and manner for all licensees. . .0 B. BACKGROUND The NRC has not previously established guidance on taking equipment out of service to perform PM because the NRC did not expect licensees to routinely perform such PM when technical specifications require the equipment to be OPERABLE.
Rather. it was expected' that most PH that necessitated taking equipment out of service would be accomplished at a time when the safety function performed by the equ; pment was not needed. (e. 9 &deg;
* when the fac; 1; ty is shutdOVtfl).
Perform; n9 such PH (e. g.. emergency d; ese 1 generator overhaul at power) requi res intentionally entering the technical specifications (TS) limrtt1ng conditions for operation (LCD> for the affected system. If a licensee does this. it* rust complete the PM and restore compliance with the LCO OPERABILITY requirements within the time specified in the appropriate action statement of the LCO (i.e., the allowed outage time CAOl1). Intentional entry into an action stetement of an LCO is not a violation or the TS in certain cases. such as allycrea_ting:_a loss or function situation or entering LCO 3.0.3 simply for convenieDce).:'
For example. T5 a1low licensees to perform much surveillance testing during power operation.
even though such testing requires entry into LCO action statements.
TS pennit entry into LCD action statements to perform surveillance testing for a number of reasons. One reason is that the time needed to perform most surveillances;s usually only a small fraction of the ACT specified in the action statement. . AnotheOr reason is' that the benefit to safety (increased level of assurance of reliability and verificat10n of OPERABILITY) derived from meeting surveillance requirements
;s considered to more than compensate for the risk to safety from Issue Date: 04/20/99 9900 Maintenance " / UNrTED STATES NUCLEAR REGULATORY COMMISSION WA8HINGTON.
D.C. =. I11III1 NRC INSPECTION MANUAL PART 9900: TECHNICAL GUIDANCE
* MAINTENANCE
-VOLUNTARY ENTRY INTO LIMITING CONDITIONS FOR OPERATION ACTION STATEMENTS TO PERFORM PREVENTIVE MAINTENANCE A. PURPOSE aTSS lCOPM.TG To provide a set of safety princ1ples for the performance of preventive maintenance (PH) at licensed nuclear reactor fac1l1ties when the performance of the PM requires renaer1ng the affected system or equipment inoperable (on-Line PH). Although these principles apply primarily to PM durinq power operation.
they also apply tQ PM on that must be OPERABLE during shutdCWl evolutions such as fuel handling or mid-loop operation:
This gUidance provides qualitative criteria to assist in recognizing abuses of on-line PM. If such abuses are noted. they should be discussed with NRC management befOre they are discussed with the licensee.
This should ensure that . the guidance is applied in a reasonable and manner for all licensees. . .. B. BACKGROllND The NRC has not previously established guidance on taking equipment out of servi ce to perform PM because the NRC d1 d not expect 1; censees to routi ne 1 y perform such PM when technical specifications require the equipment to be OPERABLE.
Rather. it was expected' that most PH that necessitated taking equipment out of service would be accomplished at a time when the safety function performed by the equ; pment was not needed. (e. 9 . . when the faci1 i ty is shutdovm).
Perform1ng such PM (e.g .. emergency diesel generator overhaul at power) requires intentionally entering thetedhnical specifications (TS) linrtt1ng conditions for operation (LCD> for the affected system. If is licensee does this. it'rrust complete the PM and restore compliance with the LCD OPERABILITY requirements within the time specified in the appropriate action statement of the LCO (i.e .. the allowed outage time (ADD>. Intentional entry into an action sutement of an LCO is not a violation of the TS (except in certain cases. such allY , c;rea , ting:, a loss of function situation or entering LCO 3.0.3 simply for convenience>.
:' For exampl e. 15 allow 1 icensees to perform nuch surveillance testing du-ring power operation.
even though such testing requires entry into LCO action statements.
15 penmt entry into LCD statements to perform surveillance testing for a number of reasons. One reason 1s that the time needed to perfonn most surveillances is usually only a small fraction of the ACT speci fi ed in the action statement. , ' Anothe'r reason is' that the benefit to safety (1 ncreased 1 eve 1 of assurance of reliab111ty and verification of OPERABILITY) derived from meeting surveillance requ1rements
;s cons1dered to more than compensate for the risk to safety from Issue Date: 04/20/99 9900 Maintenance 
 
facility in an LCO action statement for a small fraction of the The NRC staff has noticed a trend at many licensed nuclear facilities to perform increasing amounts of PM during power operation (on-line PH) rather than during shutdown conditions.
By performing lIDre on-line PM. licensees must intentionally enter into LCOs more frequently than before and use more of the AOTs than would norma 11 y be used by survei 11 ance test; ng a lone. Thi s cou 1 d cause the toU 1 unavailability of equipment over each operating cycle (or the total time that a facllity operates at increased risK because it is not complying with LCO OPERABILITY and is vulnerable to single failures) to become greater than originally contemplated when TS were established.
Of special concern is intentional entry into LCOs to perform PM near the end of an operating cycle primarily in order to shorten the refueling outage. The NRC is only to quantitatively study the Significance to safety (riSk.) of the trend to perform more PM during po.Ner operation'.
Therefore.
the NRC can not yet establish quantitative criteria by which the NRC or a licensee can determine the net effect on safety that on-line PM would have at a facility.
Until studies concerning the risk of on-line PH are completed.
this guidance establishes conseryative pr1nc1ples for safely performing PM that involves entering into LCO action statements.-
C. OISaJSSION A licensee may talce eguipment out of service to perform PM during operation of the facility (on-line PM) if it expects the reliability of the to ilq)rove such that the overa 1 1 r1 sk to ,sa fe operat; on of the faci 1 i ty 1 d decrease.
Licensees' expectations should take into account that such practlce may 1ncrease the unaval1ab1lity of the eqUipment.
When performing PM on equipment not in TS (i.e .* eQUipment that has no TS ACT). licensees should be sensitive to the embodied by the TS definition of OPERABILITY and the effect upon the OPERABILITY of 1$ eqUipment.
If a licensee has a reasalable expectation that an on-line 'PM program will improve safety by making equipment more reliable.
then the licensee can implement that program even though it may 1ncrease the unavailability of equipment.
The licensee should be able to justify such an expectation of improved safety. Part of this justification should be based upon adherence to the follow1ng tive safety principles:
: 1. Performance of a PM action on-'1ne rather than during shutdown should iq)rove safety (as descr1bed above) and be warranted by operational
-necesS1ty.
not just by the convenience of shortening a refueling outage. 2. The licensee should not abuse the allowance to perform a PM action an-line by repeatedly entering and eXit1ng LCO action statements.
The licensee should carefully plan the PM action to prevent such abuse, 3. While performing an on-line PM action. the licensee should avoid remov'1ng other equipment from service. Confidence in the OPERABILITY of the independent eqUipment that is redundant (or diverse) to the affected equipment should be h1gh. If a piece of equipment is OPERABLE.
but is degraded.
or is trending towards a degraded condition.
the licensee should not rerrcve its redundant counterpart equipment from service for a routine PM action. 9900 Maintenance . Issue Date: 04/20/99 ,
facility in an LCO action statement for a small fraction of the The NRC staff has noticed a trend at many licensed nuclear facilities to perform increasing amounts of PM dur1ng power operation (on-line PH) rather than during shutdown conditions.
By perfonning lIDre on-line PM. licensees must intentionally enter 1nto LCOs more frequently than before and use more of the AOTs than would normally be used by surve111ance testing alone. This could cause the total unavailability of equipment over each operating cycle (or the total time that a fac1l1ty operates at increased riSK because it ;s not complying with LCO OPERABILITY and is vulnerable to single failures) to become greater than originally contemplated when TS were established.
Of special concern is intentional entry into LCOs to perform PM near the end of an operating cycle primarily in order to shorten the refueling outage. The NRC is only to quantitatively study the Significance to safety (riSk.) of the trend to perform more PH during potJer operation'.
Therefore.
the NRC can not yet establish quantitative criteria by whiCh the NRC or a licensee can determine the net effect on safety that on-line PH would have at a facility.
Until studies concern1.ng the risk. of on-line PH are completed.
this guidance establishes conservative prinCiples for safely performing PM that involves entering into LCO action statements.-
C. OISOJSSION Ali censee may talce egui pment out of serv1 ce to perform PM duri ng operation of the facility (on-line PM) if 1t expects the reliability of the to i1q)rove such that the overall to ,safe operation of the facility shol:o'ld decrease.
L 1 censees' expectations should take into account that such pract 1 ce may increase the unaval1ab1l1ty of the equipment.
When performing PM on equipment not in TS (i.e., equ1lJ1S1t that has no 15 ACT). licensees should be sensitive to the embodied by the TS def1nition of OPERABILITY and the effect upon the OPERABILITY of TS equ1 pment. If a licensee has a reasooable expectation that an on-line 'PM program will improve safety by making equipment more reliable.
then the licensee can implement that program even though it may 1ncrease the unavailability of equipment.
The licensee should be able to justify such an expectation of improved safety. Part of this justification should be based upon adherence to the follow1ng tive safety principles:
: 1. Performance of a PM action on-line rather than during shutdown should 1f11)rove safety (as described above) and be warranted by operational
-necesSity, not just by the convenience of shortening a refueling outage. 2. The 11 censee shool d not abuse the allowance to perform a PM action on-1 i ne by repeatedly entering and exiting LCO action statements.
The licensee should carefully plan the PM action to prevent such abuse, 3. While performing an on-line PM action. the l1censee should avoid remov-1ng other equipment from service. Confidence in the OPERABILITY of the independent eqUipment that 1s redundant (or diverse) to the affected equipment should be h1gh. If a p1ece of equipment is OPERABLE.
but ;s degraded.
or 1$ trending towards a degraded condition.
the licensee should not rerrcve its redundant counterpart equipment from service for a routine PM action. 9900 Maintenance Issue Date: 04/20/99 , 
.. / 4. While performing an on-l1ne PH act1on. the licensee should avoid perfonn1ng other test1ng or maintenance that would 1ncrease the lik.el1hood of a transient.
The licensee should have reason to expect that the facility will cont1nue to operate 1n a stable manner. (The basis of th1S expectation should include a consideration of degraded or out of service balance of plant equ1pment.)
END Issue Date: 04/20/99 -3
* 9900 Ha1ntenance
.. ./ 4. While performing an on*l1ne PM act1on. the licensee should avoid perform1ng other test1ng or maintenance that would 1ncrease the l1Kel1hood of a transient.
The licensee should have reason to expect that the facility cont1nue to operate 1n a stable manner. (The basis of th1S expectation should 1nelude a considerat10n of degraded or out of service belance of plant eQU1pment.)
END Issue Date: 04/20/99 -3
* 9900 Maintenance TSTF-529, Rev. 0 Model Application for Adoption of TSTF-529
 
TSTF-529, Rev. 0  Page 1 [DATE] 10 CFR 50.90
 
ATTN: Document Control Desk
 
U.S. Nuclear Regulatory Commission Washington, DC 20555-0001 
 
==SUBJECT:==
PLANT NAME DOCKET NO. 50-[xxx] APPLICATION TO REVISE TECHNICAL SPECIFICATIONS TO
 
ADOPT TSTF-529, "CLARIFY US E AND APPLICATION RULES" 
 
==Dear Sir or Madam:==
Pursuant to 10 CFR 50.90, [LICENSEE] is submitting a request for an amendment to the Technical Specifications (TS) for [PLANT NAME, UNIT NOS.]. The proposed amendment would modify TS requirements in Section 1.3 and Section 3.0 regarding LCO usage and the TS Bases for Section 3.0 regarding Limiting Condition for Operation (LCO) usage and Surveillance Requirement (SR) usage. These changes are consistent with NRC-approved Revision 0 to TSTF Standard Technical Specification (STS) Traveler TSTF-529, "Clarify Use and Application Rules."  The availability of this TS improvement was announced in the Federal Regi ster on [Date] ([ ] FR
[ ]) as part of the consolidated line item improvement process (CLIIP). Attachment 1 provides a description and assessment of the proposed changes. Attachment 2 provides the existing TS pages marked up to show the proposed changes. Attachment 3 provides revi sed (clean) TS pages. Attachment 4 provides existing TS Bases pages marked to show the proposed changes. Approval of the proposed amendment is requested by [date]. Once approved, the amendment shall be implemented within [    ] days. In accordance with 10 CFR 50.91, a copy of this application, with attachments, is being provided to the designated [STATE] Official.
TSTF-529, Rev. 0  Page 2 [In accordance with 10 CFR 50.30(b), a license amendment request must be executed in a signed original under oath or affirmation. This can be accomplished by attaching a notarized affidavit confirming the signature authority of the signatory, or by including the following statement in the cover letter: "I declare under penalty of perjury that the foregoing is true and correct. Executed on (date)." The alternative statement is pursuant to 28 USC 1746. It does not require notarization.] If you should have any questions regarding this submittal, please contact [NAME, TELEPHONE NUMBER].
Sincerely, 
 
[Name, Title]
 
Attachments:  1. Description and Assessment
: 2. Proposed Technical Specif ications Changes (Mark-Up)  3. Revised Technical Specifications Pages
: 4. Proposed Technical Specificat ions Bases Changes (Mark-Up)
 
cc: NRC Project Manager NRC Regional Office
 
NRC Resident Inspector
 
State Contact TSTF-529, Rev. 0  Page 3 ATTACHMENT 1 - 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) and the TS Bases for Section 3.0, "LCO Applicability" and "SR Applicability," to clarify the us e and application of the TS usage rules.
* Section 1.3 and the Bases of LCO 3.0.2 are modified to clarify and to provide an example of "time of discovery."  ------------------
--------------------- REVIEWER'S NOTE-----
---------------
------------  The following paragraph is only appli cable to Westinghouse NSSS plants.  ---------------
------------------
------------------
-----------------
------------------
------------
* [An addition is made to Section 1.3 to discuss instrumentation Notes that allow entering a Condition and not starting the Completion Time until expiration of the time allowance in the Notes.]
* LCO 3.0.4.a is modified to clarify that Required Actions must be followed after entry into the Modes and other specified conditions in the Applicability. An example is added to the Bases.
* An editorial change is made to LC O 3.0.4.b to clarify that LCO 3.0.4.a, LCO 3.0.4.b, and LCO 3.0.4.c are independent options. The LCO 3.0.4.a Bases are revised to support the clar ification.
* LCO 3.0.5 is reworded to be consistent w ith the other LCO 3.0 specifications and to eliminate unnecessary restrictions.
In addition to TS Bases changes that re flect the proposed changes to the TS, the following TS Bases changes are proposed consistent with TSTF-529.
* The introductory paragraphs of the LCO 3.0 and SR 3.0 Bases, and the SR 3.0.2 Bases are modified to state that the usage rules are applicable to Chapter 3 of the TS and to clarify their use when invoked from Chapter 5.
* The Bases of LCO 3.0.2, LCO 3.03, SR 3.0.2, a nd SR 3.0.3 are revised to replace the term "Operational Convenience," with the intention from Generic Letter 87-09 of "voluntary removal of redundant systems or components from servi ce in lieu of other alternatives that would not result in redundant systems or components being inoperable."
* Changes are made to the Bases of LCO 3.0.3 and SR 3.0.3 to use consistent terminology.
TSTF-529, Rev. 0  Page 4
* The LCO 3.0.3 Bases are corrected to state that a unit shutdown may be terminated and LCO 3.0.3 exited if the LC O is no longer applicable.
* The LCO 3.0.4.c Bases are modified to replace a misleading TS reference.
* The LCO 3.0.5 Bases are modified to clar ify that LCO 3.0.5 should not be used if there are other alternatives to demonstrate Operability that maintain compliance with Actions. An inaccurate example in the LCO 3.0.5 Bases is replaced.
* The SR 3.0.3 Bases are modified to clarify when SR 3.0.3 may be applied and to state expectations for applying SR 3.0.3 to SRs that have not been performed for an extended period.
 
==2.0 ASSESSMENT==
2.1 Applicability of Published Safety Evaluation
  [LICENSEE] has reviewed the model safety evaluation dated [DAT E] as part of the Federal Register Notice of Av ailability. This review in cluded a review of the NRC staff's evaluation, as well as the information provided in TSTF-529.  [As described in the subsequent paragraphs, ][LICEN SEE] has concluded that the justifications presented in the TSTF-529 proposal and the model safety evaluation prepared by the NRC staff are applicable to [PLANT, UNIT NOS.] and justify this amendment for the incorporation of the changes to the [PLANT] TS. 2.2 Optional Changes and Variations
  [LICENSEE is not proposing a ny variations or deviations from the TS changes described in the TSTF-529, Revision 0, or the applicable parts of the NRC staff's model safety evaluation dated [DATE].]  [LICENSEE is proposing the following variations from the TS changes described in the TSTF-529, Revisi on 0, or the applicab le parts of the NRC staff's model safety evaluation dated [DATE].]  ------------------
--------------------- REVIEWER'S NOTE-----
---------------
------------  Omission of one or more changes proposed in TSTF-529 is an acceptable variation from the Traveler.  ---------------
------------------
------------------
-----------------
------------------
------------  [The [PLANT] TS utilize different [numbering][and][titles] than the Standard Technical Specifications on which TSTF-529 was base
: d. Specifically, [describe differences between the plant-specific TS numbering an d/or titles and the TSTF-529 numbering and titles.]  These differences are administrativ e and do not affect th e applicability of TSTF-529 to the [PLANT] TS.]
TSTF-529, Rev. 0  Page 5 3.0 REGULATORY ANALYSIS 3.1 No Significant Hazards Consideration Determination
[LICENSEE] requests adoption of TSTF-529, Revision 0, "Clarify Use and Application Rules," which is an approved change to the st andard technical specifications (STS), into the [PLANT NAME, UNIT NOS] tec hnical specifications (TS). 
[LICENSEE] has evaluated whether or not a si gnificant hazards cons ideration is involved with the proposed amendment(s) by focu sing on the three standards set forth in 10 CFR 50.92, "Issuance of amendment," as discussed below:
: 1. Does the proposed change involve a significant increase in the probability or consequences of an accident previously evaluated?
Response: No.
 
The proposed change revises Section 1.3, "Completion Times," and Section 3.0, "LCO Applicability" of the Technical Specifications (TS) and the TS Bases for Section 3.0, "LCO Applicability" and "SR A pplicability," to clarify the use and application of the TS usage rules. Secti on 1.3 is modified to cl arify the concept of "time of discovery" and to describe an existing allowance specific to NUREG-1431, "Standard Technical Specifications, Westinghouse Plants."  LCO 3.0.4.a is modified to clarify that Required Actions must be followed after entry into the Modes and other specified conditions in the Applicability. An editorial change is made to LCO 3.0.4.b to clarify that LCO 3.0.4.a, LCO 3.0.4.b, a nd LCO 3.0.4.c are independent options. LCO 3.0.5 is reworded to be consistent w ith the other LCO 3.0 specifications. The proposed change to LCO 3.0.4.a and LCO 3.0.4.b are for clarification and will not affect the implementation of the Technical Specifications (TS). The proposed change to LCO 3.0.5 will allow LCO 3.0.5 to be applied in a small number of circumstances in which it cannot be applied today.
The proposed change to Section 1.3, LC O 3.0.4, and LCO 3.0.5 has no effect on the requirement for systems to be Operable and will not have a significant effect on the application of TS actions.
Since the proposed change doe s 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 signi ficant increase in the probability or consequences of an accident previously evaluated.
TSTF-529, Rev. 0  Page 6 2. Does the proposed change create the possibi lity 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 cha nge does not change the Operability requirements for plant systems and facilitates restoring inoperable equipment to Operable status. The proposed change clarifies the current application of LCOs. The proposed change to LCO 3.0.4 will not affect plant operation when LCO 3.0.4 is
 
applied. The proposed change to LCO 3.0.5 slightly expands the circumstances in which LCO 3.0.5 can be applied. Testing to confirm Operability allowed under the proposed change to LCO 3.0.5 will be performed under procedural control in accordance with the licensee's quality assurance process and will not introduce and new or different accident initiators.
Therefore, it is concluded that this change does not create the possi bility of a new or different kind of accident from any accident previously evaluated.
: 3. Does the proposed change involve a signi ficant reduction in a margin of safety?
Response: No.
 
The proposed change clarifies the applic ation of Section 1.3 and LCO 3.0.4 and does not result in changes in plant operation. As a result, plant safety is either improved or unaffected. The proposed change to LCO 3.0.5 allows testing to establish Operability to be performed, which improves plant safety.
Therefore, it is concluded that this change does not involve a si gnificant reduction in a margin of safety. Based on the above, [LICENSEE] concludes that the proposed change presents no 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 with in 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 consideratio n, (ii) a significant ch ange 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 occupa tional radiation exposure.
Accordingly, the proposed change meets the el igibility 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.
TSTF-529, Rev. 0
 
Improved Technical Specifications Mark-Up
 
Completion Times 1.3    BWOG STS 1.3-1 Rev. 3.1, 12/01/05  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. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a component is inoperable following improper maintenance performed in the past. The time of discovery (when the LCO is declared not met) is subsequent to both the time of occurrence (the improper maintenance), the time when it is identified that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable.
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 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.
 
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.
However, when a subsequent train, subsystem, component, or variable, expressed in the Condition, is discovered to be inoperable or not within LCO  Applicability 3.0    BWOG STS 3.0-1 Rev. 3.1, 12/01/05  3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
LCO  3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8.
LCO  3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.
 
If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required, unless otherwise stated.
 
LCO  3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
: a. MODE 3 within 7 hours,
: b. MODE 4 within 13 hours, and
: c. MODE 5 within 37 hours.
 
Exceptions to this Specification are stated in the individual Specifications.
Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.
 
LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.
LCO  3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:
: a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; 
: 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 LCO  Applicability 3.0    BWOG STS 3.0-2 Rev. 3.1, 12/01/05 3.0  LCO  Applicability
 
LCO  3.0.4  (continued)
: 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 The Required Actions of ConditionsEquipment removed from service or declared inoperable to comply with ACTIONS are not required to be may b e met returned to service under administrative control solely to perform testing required to demonstrate the LCO is met or that other LCOs are met its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system return ed to service under administrative control to perform the testing required to demonstrate OPERABILITYthe LCO is met or that other LCOs are met.
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 LCOs [3.1.9, 3.1.10, 3.1.11, and 3.4.19] allow 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.
 
LCO  Applicability 3.0    BWOG STS 3.0-3 Rev. 3.1, 12/01/05 3.0  LCO  Applicability
 
LCO  3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:
: a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours; or
: b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours. 
 
At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-1  Rev. 3.1, 12/01/05  B 3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
BASES LCOs LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times, unless otherwise stated.
LCO  3.0.1 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 LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. 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 case, compliance with the Required Actions provides an acceptable level of safety for continued operation. 
 
Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-2  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.2  (continued)
The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.3, "RCS Pressure and Temperature (P/T)
Limits."
The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. Reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Intentional entry into ACTIONS should not be used for 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. made for operational convenience. Additionally, if intentional entry into ACTIONS would result in redundant equipment being inoperable, alternatives should be used instead.
Doing so limits the time both subsystems/trains of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed. When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable and the ACTIONS Condition(s) are entered.
 
LCO  3.0.3 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and either:
: a. An associated Required Action and Completion Time is not met and no other Condition applies or
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-3  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.3  (continued)
: 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 to permit 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 hour 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 reach 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,  c b. A Condition exists for which the Required Actions have now been performed, or
 
d c. 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.
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-4  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.3  (continued)
 
The time limits of LCO 3.0.3 allow 37 hours 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 entering reaching the next lower MODE applies. If a lower MODE is reached entered 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 reached entered in 2 hours, then the time allowed for reaching entering MODE 4 is the next 11 hours, because the total time for reaching entering MODE 4 is not reduced from the allowable limit of 13 hours. 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 L CO 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.14, "Fuel Storage Pool Water Level."  LCO 3.7.14 has an Applicability of "During movement of irradiated fuel assemblies in 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.14 are not met while in MODE 1, 2, 3, or 4, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LCO 3.7.14 of "Suspend movement of irradiated fuel assemblies in 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 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 APPLICABILITY B 3.0    BWOG STS B 3.0-5  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
 
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 permit continued operationfollowing entry into 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 in accordance with the provisions of the Required Actions.
For example, LCO 3.0.4.a may be used when the Required Action states that an inoperable train be restored to OPERABLE status within the Completion Time, 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 associated ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit 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 plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."  Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93
-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."  These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management LCO APPLICABILITY B 3.0    BWOG STS B 3.0-6  Rev. 3.1, 12/01/05  actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management 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 APPLICABILITY B 3.0    BWOG STS B 3.0-7  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
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 allowance 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 in 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 Activity[Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature 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.
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-8  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
 
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 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 provides an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) under administrative controls for the sole purpose of allowing to allow the performance of required testing to demonstrate either:
: a. The LCO is met, The OPERABILITY of the equipment being returned to service or 
: b. Other LCOs are metThe OPERABILITY of other equipment.
LCO 3.0.5 allows Required Actions to not be followed temporarily in order to demonstrate an LCO is met without exiting the Applicability of the Specification.
The administrative controls ensure the time the Required Actions are not met 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 the LCO is metOPERABILITY. 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 LCO APPLICABILITY B 3.0    BWOG STS B 3.0-9  Rev. 3.1, 12/01/05  practicable alternatives that comply with ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met.
LCO 3.0.5 is not intended to be used repeatedly
. An example of demonstrating the LCO is met 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.
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-10  Rev. 3.1, 12/01/05  BASES LCO  3.0.5  (continued)
An other example of demonstrating the LCO is met OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. 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.
 
LCO  3.0.6 LCO 3.0.6 establishes an exception to LCO 3.0.2 for support ed systems that have a support system 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.
 
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 system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the unit is maintained in a safe condition in the support system's Required Actions. However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system.
This may occur immediately or after some specified delay to perform some other Required Action. Regardless of whether it is immediate or after some delay, 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 APPLICABILITY B 3.0    BWOG STS B 3.0-11  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (continued)
 
Specification 5.5.15, "Safety Function Determination Program (SFDP)," ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6. Cross train checks to identify a loss of safety function for those support systems that support multiple and redundant safety systems are required. The cross train check verifies that the supported systems of the remaining OPERABLE support systems are OPERABLE, thereby ensuring safety function is retained.  [ A loss of safety function may exist when a support system is inoperable, and:
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1),  b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE
 
B 3.0.6-2), or 
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3).
EXAMPLE B 3.0.6
-1  If System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5.
 
EXAMPLE B 3.0.6
-2  If System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5.
 
EXAMPLE B 3.0.6
-3  If System 2 of Train A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8, 9, 10 and
: 11. ]
 
If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-12  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (continued)
 
  [ Figure B 3.0-1 Configuration of Trains and Systems ]
This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordance with the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sources also acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-13  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (continued)
When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists, consideration must be given to the specific type of function affected. Where a loss of function is solely due to a single Technical Specification support system (e.g., loss of automatic start due to inoperable instrumentation, or loss of pump suction source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilities of that system without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO is the LCO for the supported system. LCO  3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions. Test Exception LCOs [3.1.8, 3.1.9, and 3.4.19] allow specified Technical Specification (TS) requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed if required to comply with the requirements of these TS.
Unless otherwise specified, all the other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.
The Applicability of a Test Exception LCO represents a condition not necessarily in compliance with the normal requirements of the TS. Compliance with Test Exception LCOs is optional. A special operation may be performed either under the provisions of the appropriate Test Exception LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Test Exception LCO, the requirements of the Test Exception LCO shall be followed.
LCO  3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more snubbers not capable of performing their associated
 
LCO APPLICABILITY B 3.0    BWOG STS B 3.0-14  Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.8  (continued)
 
support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.
If the allowed time expires and the snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2. LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours to restore the snubber(s) before declaring the supported system inoperable. The 72 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.
LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system.
LCO 3.0.8.b allows 12 hours to restore the snubber(s) before declaring the supported system inoperable. The 12 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function.
 
LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or subsystem is properly controlled, and emergent issues are properly addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function.
 
SR Applicability B 3.0    BWOG STS B 3.0-15  Rev. 3.1, 12/01/05  B 3.0  SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
 
BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times, unless otherwise stated. SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification.
 
SR  3.0.1 SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3.0.2, constitutes a failure to meet an LCO. Surveillances may be performed by means of any series of sequential, overlapping, or total steps provided the entire Surveillance is performed within the specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed by means of any series of sequential, overlapping, or total steps.
Systems and components are assumed to be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when:
: a. The systems or components are known to be inoperable, although still meeting the SRs or
: b. The requirements of the Surveillance(s) are known to be not met between required Surveillance performances.
 
Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a Special Test Exception (STE) LCO are only applicable when the STE LCO is used as an allowable exception to the requirements of a Specification.
 
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanned event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.
 
SR Applicability B 3.0    BWOG STS B 3.0-16  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.1  (continued)
Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.
 
Some examples of this process are:
: a. Emergency feedwater (EFW) pump turbine maintenance during refueling that requires testing at steam pressures > 800 psi. However, if other appropriate testing is satisfactorily completed, the EFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to perform the EFW pump testing. 
: b. High pressure injection (HPI) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with HPI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.
 
SR  3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per ..." interval.
SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).
 
SR Applicability B 3.0    BWOG STS B 3.0-17  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.2  (continued)
 
The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. There are exceptions to SR 3.0.2 for certain are those Surveillances to for which the 25% extension of the interval specified in the Frequency may not be applieddoes not apply. These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Starting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program which does not reference SR 3.0.2.
SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations
.An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the regulations.
 
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 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 hours 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 SR Applicability B 3.0    BWOG STS B 3.0-18  Rev. 3.1, 12/01/05  accordance with SR 3.0.2, and not at the time that the specified Frequency was not met.
 
SR Applicability B 3.0    BWOG STS B 3.0-19  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.3  (continued)
 
This delay period provides an adequate time to complete perform Surveillances that have been missed. This delay period permits the completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude completion performance 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 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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have been tested, the relay contacts have been tested by another SR, or historical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis SR Applicability B 3.0    BWOG STS B 3.0-20  Rev. 3.1, 12/01/05  for the determination, should be completed to compensate for the lack of performance history.
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 as an operational convenience to extend Surveillance intervals. While up to 24 hours 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
 
SR Applicability B 3.0    BWOG STS B 3.0-21  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.3  (continued) 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 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 Applicability.
This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. 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.
 
A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.
 
SR Applicability B 3.0    BWOG STS B 3.0-22  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.4  (continued)
 
However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed.
Therefore, failing to perform the Surveillance(s) within the specified Frequency does not
 
result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.
The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 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.
The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.
 
Completion Times 1.3    WOG STS 1.3-1 Rev. 3.1, 12/01/05    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. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a component is inoperable following improper maintenance performed in the past. The time of discovery (when the LCO is declared not met) is subsequent to both the time of occurrence (the improper maintenance), the time when it is identified that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable.
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 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.
 
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.
However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within Completion Times 1.3    WOG STS 1.3-2 Rev. 3.1, 12/01/05    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 Completion Times 1.3    WOG STS 1.3-3 Rev. 3.1, 12/01/05 1.3  Completion Times
 
DESCRIPTION (continued)
: b. Must remain inoperable or not within limits after the first inoperability is resolved.
 
The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:
: a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours 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.
 
The above Completion Time extension does not apply to a Completion Time with a modified "time zero."  This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified
 
by the phrase "from discovery . . ."  The Completion Time is referenced to the time of entering an ACTIONS Condition unless otherwise specified. One of the "otherwise specified" cases is a Required Action modified by a Note which provides an alternative time to perform specific tasks (i.e., "One channel may be bypassed for up to 12 hours for surveillance testing and setpoint adjustment.")  Starting the Completion Time is deferred in accordance with the Note. While utilizing the Note, should the Condition be applicable for any reason not addressed by the Note, the Completion Time begins.
Should the time allowance in the Note expire, the Completion Time begins. EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.
EXAMPLE  1.3-1 ACTIONS LCO Applicability 3.0    WOG STS 3.0-1 Rev. 3.1, 12/01/05  3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
LCO  3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8.
LCO  3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.
 
If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated.
 
LCO  3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
: a. MODE 3 within 7 hours,
: b. MODE 4 within 13 hours, and
: c. MODE 5 within 37 hours.
 
Exceptions to this Specification are stated in the individual Specifications.
Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.
 
LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.
LCO  3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:
: a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; 
: 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 LCO Applicability 3.0    WOG STS 3.0-2 Rev. 3.1, 12/01/05 3.0  LCO Applicability
 
LCO  3.0.4  (continued)
: 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 The Required Actions of Conditions Equipment removed from service or declared inoperable to comply with ACTIONS may be are not required to be met returned to service under administrative control solely to perform testing required to demonstrate its the LCO is met or that other LCOs are metOPERABILITY 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 the LCO is met or that other LCOs are met 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 LCOs [3.1.8 and 3.4.19] allow 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.
 
LCO Applicability 3.0    WOG STS 3.0-3 Rev. 3.1, 12/01/05 3.0  LCO Applicability
 
LCO  3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:
: a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours; or
: b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours. 
 
At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.
 
LCO  Applicability B 3.0    WOG STS B 3.0-1 Rev. 3.1, 12/01/05  B 3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
BASES LCOs  LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times, unless otherwise stated.
LCO  3.0.1  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  LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. 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 case, compliance with the Required Actions provides an acceptable level of safety for continued operation.
Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.
 
LCO  Applicability B 3.0    WOG STS B 3.0-2 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.2  (continued)
 
The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.3, "RCS Pressure and Temperature (P/T) Limits."
The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Intentional entry into ACTIONS should not be made used for 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. operational convenience. Additionally, if intentional entry into ACTIONS would result in redundant equipment being inoperable, alternatives should be used instead.
Doing so limits the time both subsystems/trains of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed. When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS Condition(s) are entered.
 
LCO  3.0.3  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 LCO  Applicability B 3.0    WOG STS B 3.0-3 Rev. 3.1, 12/01/05  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.
 
LCO  Applicability B 3.0    WOG STS B 3.0-4 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.3  (continued)
 
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 to permit 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 hour 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 reach 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, c b. A Condition exists for which the Required Actions have now been performed, or d c. 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 LCO 3.0.3 allow 37 hours 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 reaching entering the next lower MODE applies. If a lower MODE is reached entered 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 reached entered in 2 hours, then the time LCO  Applicability B 3.0    WOG STS B 3.0-5 Rev. 3.1, 12/01/05  allowed for reaching entering MODE 4 is the next 11 hours, because the total time for reaching entering LCO  Applicability B 3.0    WOG STS B 3.0-6 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.3  (continued)
MODE 4 is not reduced from the allowable limit of 13 hours. 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.15, "Fuel Storage Pool Water Level."  LCO 3.7.15 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.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  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 permit continued operation in following entry into 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 Required Actions 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 in accordance with the provisions of the Required Actions.
 
LCO  Applicability B 3.0    WOG STS B 3.0-7 Rev. 3.1, 12/01/05 For example, LCO 3.0.4.a may be used when the Required Action states that an inoperable train be restored to OPERABLE status within the Completion Time, 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 associated ACTION S to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit plant operation for an unlimited period of time in the MODE or other specified condition to be entered
.
LCO  Applicability B 3.0    WOG STS B 3.0-8 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
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 plant program, procedures, and criteria in place to implement
 
10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."  Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93
-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."  These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management 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.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.
 
LCO  Applicability B 3.0    WOG STS B 3.0-9 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
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 allowance 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 in 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 Activity[Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature 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.
LCO  Applicability B 3.0    WOG STS B 3.0-10 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.4  (continued)
 
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  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 provides an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) under administrative controls for the sole purpose of allowing to allow the performance of required testing to demonstrate:
: a. The LCO is met ,  OPERABILITY of the equipment being returned to service or    b. Other LCOs are metThe OPERABILITY of other equipment. LCO 3.0.5 allows Required Actions to not be followed temporarily in order to demonstrate an LCO is met without exiting the Applicability of the Specification.
The administrative controls ensure the time the Required Actions are not met 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 the LCO is metOPERABILITY. 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 ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met.
LCO 3.0.5 is not intended to be used repeatedly
. An example of demonstrating the LCO is metOPERABILITY of the equipment being returned to service with the Required Actions not met is reopening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System LCO  Applicability B 3.0    WOG STS B 3.0-11 Rev. 3.1, 12/01/05  (RCS) Pressure Isolation Valve (PI V) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit.containment isolation valve that has been closed to comply with Required Actions and must be reopened to perform the required testing.
An example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. 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.
LCO  Applicability B 3.0    WOG STS B 3.0-12 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  LCO 3.0.6 establishes an exception to LCO 3.0.2 for support ed systems that have a support system 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.
 
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 system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the unit is maintained in a safe condition in the support system's Require d
Actions.
However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system.
This may occur immediately or after some specified delay to perform some other Required Action. Regardless of whether it is immediate or after some delay, 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.
Specification 5.5.15, "Safety Function Determination Program (SFDP)," ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6.
LCO  Applicability B 3.0    WOG STS B 3.0-13 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (continued)
 
Cross train checks to identify a loss of safety function for those support systems that support multiple and redundant safety systems are required.
The cross train check verifies that the supported systems of the redundant OPERABLE support system are OPERABLE, thereby ensuring safety function is retained. 
[ A loss of safety function may exist when a support system is inoperable, and:
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1), 
: b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE B 3.0.6-2), or 
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3). EXAMPLE B 3.0.6
-1  If System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5.
EXAMPLE B 3.0.6
-2  If System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5.
EXAMPLE B 3.0.6
-3  If System 2 of Train A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8, 9, 10 and
: 11. ]  If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
 
LCO  Applicability B 3.0    WOG STS B 3.0-14 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (continued)
    [ Figure B 3.0-1 Configuration of Trains and Systems ]    This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordance with the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sources also acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).
When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists, consideration must be given to the specific type of function affected. Where a loss of function is solely due to a single Technical Specification support system (e.g., loss of automatic start due to inoperable instrumentation, or loss of pump suction
 
LCO  Applicability B 3.0    WOG STS B 3.0-15 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.6  (contin ued) source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilities of that system without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO is the LCO for the supported system.
LCO  3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions. Test Exception LCOs [3.1.8 and 3.4.19] allow specified Technical Specification (TS) requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed if required to comply with the requirements of these TS.
Unless otherwise specified, all the other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.
 
The Applicability of a Test Exception LCO represents a condition not necessarily in compliance with the normal requirements of the TS. Compliance with Test Exception LCOs is optional. A special operation may be performed either under the provisions of the appropriate Test Exception LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Test Exception LCO, the requirements of the Test Exception LCO shall be followed.
LCO  3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubbe r requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.
 
LCO  Applicability B 3.0    WOG STS B 3.0-16 Rev. 3.1, 12/01/05  BASES
 
LCO  3.0.8  (continued)
 
If the allowed time expires and the snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2.
LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours to restore the snubber(s) before declaring the supported system inoperable. The 72 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.
 
LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system.
LCO 3.0.8.b allows 12 hours to restore the snubber(s) before declaring the supported system inoperable. The 12 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function.
 
LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or subsystem is properly controlled, and emergent issues are properly addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function.
 
SR  Applicability B 3.0    WOG STS B 3.0-17  Rev. 3.1, 12/01/05  B 3.0  SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
 
BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times, unless otherwise stated. SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification
.
SR  3.0.1 SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3.0.2, constitutes a failure to meet an LCO. Surveillances may be performed by means of any series of sequential, overlapping, or total steps provided the entire Surveillance is performed within the specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed by means of any series of sequential, overlapping, or total steps.
Systems and components are assumed to be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when: 
: a. The systems or components are known to be inoperable, although still meeting the SRs; or
: b. The requirements of the Surveillance(s) are known not to be met between required Surveillance performances.
Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a test exception are only applicable when the test exception is used as an allowable exception to the requirements of a Specification.
 
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanned ev ent may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.
 
Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have SR  Applicability B 3.0    WOG STS B 3.0-18  Rev. 3.1, 12/01/05  to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.
 
SR  Applicability B 3.0    WOG STS B 3.0-19  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.1  (conti nued)
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.
 
Some examples of this process are:
: a. Auxiliary feedwater (AFW) pump turbine maintenance during refueling that requires testing at steam pressures >
800 psi. However, if other appropriate testing is satisfactorily completed, the AFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to perform the testing. 
: b. High pressure safety injection (HPI) maintenance during shutdown
 
that requires system functional tests at a specified pressure.
Provided other appropriate testing is satisfactorily completed, startup can proceed with HPI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.
 
SR  3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per . . ." interval.
SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).
The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. There are exceptions to SR 3.0.2 for certain are those Surveillances for to which the
 
SR  Applicability B 3.0    WOG STS B 3.0-20  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.2  (contin ued) 25% extension of the interval specified in the Frequency does may not be appliednot apply. These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Starting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program which does not reference SR 3.0.2. SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the regulations.
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 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 hours 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 completion of a Surveillance before complying with Required Actions or SR  Applicability B 3.0    WOG STS B 3.0-21  Rev. 3.1, 12/01/05  other remedial measures that might preclude completion performance 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. 
 
SR  Applicability B 3.0    WOG STS B 3.0-22  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.3  (continued)
 
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 limit s, 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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have been tested, the relay contacts have been tested by another SR, or historical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient t o provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis for the determination, should be completed to compensate for the lack of performance history.
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 as an operational convenience to extend Surveillance intervals. While up to 24 hours 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 SR  Applicability B 3.0    WOG STS B 3.0-23  Rev. 3.1, 12/01/05  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.
 
SR  Applicability B 3.0    WOG STS B 3.0-24  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.3  (continued)
 
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 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 Applicability.
 
This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. 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.
 
A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.
However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this
 
SR  Applicability B 3.0    WOG STS B 3.0-25  Rev. 3.1, 12/01/05  BASES
 
SR  3.0.4  (continued) instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has
 
been delayed in accordance with SR 3.0.3.
 
The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 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.
The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met.
Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.
 
Completion Times 1.3    CEOG STS 1.3-1 Rev. 3.1, 12/01/05 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. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a component is inoperable following improper maintenance performed in the past. The time of discovery (when the LCO is declared not met) is subsequent to both the time of occurrence (the improper maintenance), the time when it is identified that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable. 
 
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 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.
 
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.
However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within LCO  Applicability 3.0    CEOG STS 3.0-1 Rev. 3.1, 12/01/05 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
LCO  3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8.
LCO  3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.
 
If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required, unless otherwise stated.
 
LCO  3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
: a. MODE 3 within 7 hours,
: b. [MODE 4 within 13] hours, and
: c. MODE 5 within 37 hours.
 
Exceptions to this Specification are stated in the individual Specifications.
Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.
 
LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.
LCO  3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:
: a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; 
: 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.
LCO  Applicability 3.0    CEOG STS 3.0-2 Rev. 3.1, 12/01/05 3.0 LCO Applicability
 
LCO  3.0.4  (continued)
 
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 The Required Actions of Conditions Equipment removed from service or declared inoperable to comply with ACTIONS may be are not required to be met returned to service under administrative control solely to perform testing required to demonstrate the LCO is met or that other LCOs are met 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 OPERABILITYthe LCO is met or that other LCOs are met.
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 Special test exception (STE) LCOs [in each applicable LCO section] 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 STE LCOs is optional. When an STE LCO is desired to be met but is not met, the ACTIONS of the STE LCO shall be met. When an STE 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.
LCO  3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed
 
and managed, and:
 
LCO  Applicability 3.0    CEOG STS 3.0-3 Rev. 3.1, 12/01/05 3.0 LCO Applicability
 
LCO  3.0.8  (continued)
: a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours; or
: b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours.
At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.
 
LCO  Applicability B 3.0    CEOG STS B 3.0-1  Rev. 3.1, 12/01/05 B 3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
BASES LCOs LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times unless otherwise stated.
LCO  3.0.1 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 LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. 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 case, compliance with the Required Actions provides an acceptable level of safety for continued operation.
 
Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.
LCO  Applicability B 3.0    CEOG STS B 3.0-2  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.2  (continued)
 
The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.3, "RCS Pressure and
 
Temperature (P/T) Limits."  The Completion Times of the Required Actions are also applicable when
 
a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety.
Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Intentional entry into ACTIONS should not be used made for operational convenience. Additionally, if intentional entry into ACTIONS voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant equipment systems or components being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/trains of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.
 
When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable and the ACTIONS Condition(s) are entered.
LCO  3.0.3 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and either:
: 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 LCO  Applicability B 3.0    CEOG STS B 3.0-3  Rev. 3.1, 12/01/05 cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that LCO 3.0.3 be entered immediately.
LCO  Applicability B 3.0    CEOG STS B 3.0-4  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
 
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 perm its to permit 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 hour 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 reach 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, b c. A Condition exists for which the Required Actions have now been performed, or c 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 LCO 3.0.3 allow 37 hours 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
 
reaching entering the next lower MODE applies. If a lower MODE is reached entered in less time than allowed, however, the total allowable time to reach enter LCO  Applicability B 3.0    CEOG STS B 3.0-5  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
 
MODE 5, or other applicable MODE, is not reduced. For example, if MODE 3 is reached entered in 2 hours, then the time allowed for reaching entering MODE 4 is the next 11 hours, because the total time for reaching entering MODE 4 is not reduced from the allowable limit of 13 hours. 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.16, "Fuel Storage Pool Water Level."  LCO 3.7.16 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.16 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.16 of "Suspend movement of irradiated fuel assemblies in 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.
[ The requirement to be in MODE 4 in 13 hours is plant specific and depends on the ability to cool the pressurizer and degas. ]
LCO  3.0.4 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  Applicability B 3.0    CEOG STS B 3.0-6  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
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 permit continued operation in following entry into 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 Required Actions 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 in accordance with the provisions of the Required Actions.
 
For example, LCO 3.0.4.a may be used when the Required Action states that an inoperable train be restored to OPERABLE status within the Completion Time, 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 associated ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit 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 plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."  Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."  These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management LCO  Applicability B 3.0    CEOG STS B 3.0-7  Rev. 3.1, 12/01/05 actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management 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  Applicability B 3.0    CEOG STS B 3.0-8  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
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 unava ilability 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 allowance 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 in 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 Activity[Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature Coefficien t]), 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.
LCO  Applicability B 3.0    CEOG STS B 3.0-9  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applic ability 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 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 provides an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow under administrative controls for the sole purpose of allowing the performance of required testing to demonstrate either:
: a. The LCO is met, OPERABILITY of the equipment being returned to se rvice or 
: b. Other LCOs are metThe OPERABILITY of other equipment.
LCO 3.0.5 allows Required Actions to not be followed temporarily in order to demonstrate an LCO is met without exiting the Applicability of the Specification.
The administrative controls ensure the time the Required Actions are not met 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 the LCO is met 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 LCO  Applicability B 3.0    CEOG STS B 3.0-10  Rev. 3.1, 12/01/05 practicable alternatives that comply with ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met.
LCO 3.0.5 is not intended to be used repeatedly.
 
LCO  Applicability B 3.0    CEOG STS B 3.0-11  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.5  (continued)
 
An example of demonstrating the LCO is met OPERABILITY of the equipment with the Required Actions not met 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 required testing 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 other example of demonstrating the LCO is met the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. A simila r 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.
 
LCO  3.0.6 LCO 3.0.6 establishes an exception to LCO 3.0.2 for supported systems that have a support system 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.
 
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 system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the unit is maintained in a safe condition in the support system's Required Actions.
 
However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system. This may occur immediately or after some specified delay to perform LCO  Applicability B 3.0    CEOG STS B 3.0-12  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
some other Required Action. Regardless of whether it is immediate or after some delay, 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.
Specification 5.5.15, "Safety Function Determination Program (SFDP),"
ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function ex ists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6.
Cross train checks to identify a loss of safety function for those support systems that support multiple and redundant safety systems are required. The cross train check verifies that the supported systems of the redundant OPERABLE support system are OPERABLE, thereby ensuring safety function is retained.  [ A loss of safety function may exist when a support system is inoperable, and:
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1), 
: b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE B 3.0.6-2), or
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3).
EXAMPLE B 3.0.6-1 If System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5.
 
EXAMPLE B 3.0.6-2
 
If System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5.
LCO  Applicability B 3.0    CEOG STS B 3.0-13  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
EXAMPLE B 3.0.6-3
 
If System 2 of Train A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8, 9, 10 and
: 11. ]  If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
  [ Figure B 3.0-1 Configuration of Trains and Systems ]
This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordance with the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sources also acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).
LCO  Applicability B 3.0    CEOG STS B 3.0-14  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists, consideration must be given to the specific type of function affected. Where a loss of function is solely due to a single Technical Specification support system (e.g., loss of automatic start due to inoperable instrumentation, or loss of pump suction source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilities of that system without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO is the LCO for the supported system. LCO  3.0.7 Special tests and operations are required at various times over the unit's life to demonstrate performance characteristics, to perform maintenance activities, and to perform special evaluations. Because TS normally preclude these tests and operations, special test exceptions (STEs) allow specified requirements to be changed or suspended under controlled conditions. STEs are included in applicable sections of the Specifications. Unless otherwise specified, all other TS requirements remain unchanged and in effect as applicable. This will ensure that all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed or suspended to perform the special test or operation will remain in effect.
 
The Applicability of an STE LCO represents a condition not necessarily in compliance with the normal requirements of the TS. Compliance with STE LCOs is optional.
A special test may be performed under either the provisions of the appropriate STE LCO or the other applicable TS requirements. If it is desired to perform the special test under the provisions of the STE LCO, the requirements of the STE LCO shall be followed. This includes the SRs specified in the STE LCO.
 
Some of the STE LCOs require that one or more of the LCOs for normal operation be met (i.e., meeting the STE LCO requires meeting the specified normal LCOs). The Applicability, ACTIONS, and SRs of the specified normal LCOs, however, are not required to be met in order to meet the STE LCO when it is in effect. This means that, upon failure to meet a specified normal LCO, the associated ACTIONS of the STE LCO LCO  Applicability B 3.0    CEOG STS B 3.0-15  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.7  (continued)
 
apply, in lieu of the ACTIONS of the normal LCO. Exceptions to the above do exist. There are instances when the Applicability of the specified normal LCO must be met, where its ACTIONS must be taken, where certain of its Surveillances must be performed, or where all of these requirements must be met concurrently with the requirements of the STE LCO. Unless the SRs of the specified normal LCOs are suspended or changed by the special test, those SRs that are necessary to meet the specified normal LCOs must be met prior to performing the special test. During the conduct of the special test, those Surveillances need not be performed unless specified by the ACTIONS or SRs of the STE LCO.
 
ACTIONS for STE LCOs provide appropriate remedial measures upon failure to meet the STE LCO. Upon failure to meet these ACTIONS, suspend the performance of the special test and enter the ACTIONS for all LCOs that are then not met. Entry into LCO 3.0.3 may possibly be required, but this determination should not be made by considering only the failure to meet the ACTIONS of the STE LCO.
 
LCO  3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber
 
requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.
 
If the allowed time expires and the snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2.
LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours to restore the snubber(s) before declaring the supported system 
 
LCO  Applicability B 3.0    CEOG STS B 3.0-16  Rev. 3.1, 12/01/05 BASES LCO  3.0.8  (continued)
 
inoperable. The 72 hour Completion Time is reasonable based on the low probability of a seismic event c oncurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.
LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system.
LCO 3.0.8.b allows 12 hours to restore the snubber(s) before declaring the supported system inoperable. The 12 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function.
 
LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or subsystem is properly controlled, and emergent issues are properly addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated
 
support function.
 
SR  Applicability B 3.0    CEOG STS B 3.0-17  Rev. 3.1, 12/01/05 B 3.0  SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
 
BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through 3.9 and apply at all times, unless otherwise stated. SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification.
 
SR  3.0.1  SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3.0.2, constitutes a failure to meet an LCO. Surveillances may be performed by means of any series of sequential, overlapping, or total steps provided the entire Surveillance is performed within the specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed by means of any series of sequential, overlapping, or total steps.
 
Systems and components are assumed to be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when either:
: a. The systems or components are known to be inoperable, although still meeting the SRs or
: b. The requirements of the Surveillance(s) are known to be not met between required Surveillance performances.
Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a special test exception (STE) are only applicable when the STE is used as an allowable exception to the requirements of a Specification.
 
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanned event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.
 
Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have SR  Applicability B 3.0    CEOG STS B 3.0-18  Rev. 3.1, 12/01/05 to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.
SR  Applicability B 3.0    CEOG STS B 3.0-19  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.1  (continued)
 
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.
 
Some examples of this process are:
: a. Auxiliary feedwater (AFW) pump turbine maintenance during refueling that requires testing at steam pressures > 800 psi. However, if other appropriate testing is satisfactorily completed, the AFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to perform the testing.
: b. High pressure safety injection (HPSI) maintenance during shutdown that requires system functional tests at a specified pressure.
Provided other appropriate testing is satisfactorily completed, startup can proceed with HPSI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.
 
SR  3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per..." interval.
SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).
SR  Applicability B 3.0    CEOG STS B 3.0-20  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.2  (continued)
 
The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the
 
SRs. The re are exceptions to SR 3.0.2 for certain are those Surveillances to for which the 25% extension of the interval specified in the Frequency may not be applieddoes not apply. These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Starting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program which does not reference SR 3.0.2. SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations.
An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulatio ns. The TS cannot in and of themselves extend a test interval specified in the regulations.
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 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 complet ed performed within the specified Frequency. A delay period of up to 24 hours 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 SR  Applicability B 3.0    CEOG STS B 3.0-21  Rev. 3.1, 12/01/05 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 completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude completion performance of the Surveillance.
 
SR  Applicability B 3.0    CEOG STS B 3.0-22  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
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 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discover ed 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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have been tested, the relay contacts have been tested by another SR, or historical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis for the determination, should be completed to compensate for the lack of performance history.
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 as an operational convenience to extend Surveillance intervals. While up to 24 hours or the SR  Applicability B 3.0    CEOG STS B 3.0-23  Rev. 3.1, 12/01/05 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 
 
SR  Applicability B 3.0    CEOG STS B 3.0-24  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
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 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 Applicability.
 
This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. 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. 
 
A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.
 
SR  Applicability B 3.0    CEOG STS B 3.0-25  Rev. 3.1, 12/01/05 BASES SR  3.0.4  (continued)
 
However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change.
When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.
The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 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. 
 
The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met.
Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.
 
Completion Times 1.3    BWR/4 STS 1.3-1 Rev. 3.1, 12/01/05 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. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a component is inoperable following improper maintenance performed in the past. The time of discovery (when the LCO is declared not met) is subsequent to both the time of occurrence (the improper maintenance), the time when it is identified that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable.
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 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.
 
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.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not LCO  Applicability 3.0    BWR/4 STS 3.0-1 Rev. 3.1, 12/01/05 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
LCO  3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8.
LCO  3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.
 
If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required, unless otherwise stated.
 
LCO  3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
: a. MODE 2 within [7] hours,
: b. MODE 3 within 13 hours, and
: c. MODE 4 within 37 hours.
 
Exceptions to this Specification are stated in the individual Specifications.
Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.
 
LCO 3.0.3 is only applicable in MODES 1, 2, and 3.
  -----------------------------------REVIEWER'S NOTE-----------------------------------
The brackets around the time provided to reach MODE 2 allow a plant to extend the time from 7 hours to a plant specific time. Before the time can be changed, plant specific data must be provided to support the extended time.  --------------------------------------------------------------------------------------------------
 
LCO  3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:
: a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; LCO  Applicability 3.0    BWR/4 STS 3.0-2 Rev. 3.1, 12/01/05 LCO  Applicability
 
LCO  3.0.4  (continued)
: 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.
 
LCO  3.0.5 The Required Actions of Conditions Equipment removed from service or declared inoperable to comply with ACTIONS may be are not required to be met returned to service under administrative control solely to perform testing required to demonstrate the LCO is met or that other LCOs are met 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 the LCO is met or that other LCOs are met 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.12, "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 LCO  Applicability B 3.0    BWR/4 STS B 3.0-1  Rev. 3.1, 12/01/05 B 3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
BASES LCOs LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through 3.10 and apply at all times, unless otherwise stated.
LCO  3.0.1 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 LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. The Completion Time of each Required Action for a n 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 case, compliance with the Required Actions provides an acceptable level of safety for continued operation.
 
Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.
 
LCO  Applicability B 3.0    BWR/4 STS B 3.0-2  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.2  (continued)
The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.10, "RCS Pressure and Temperature (P/T)
Limits."
The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Intentional entry into ACTIONS should not be made used for operational convenience. Additionally, if intentional entry into ACTIONS voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components equipment being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/divisions of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.
When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS Condition(s) are entered.
LCO  3.0.3 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
 
LCO  Applicability B 3.0    BWR/4 STS B 3.0-3  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
: 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 to permit 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 hour 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 reach 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.
c b. A Condition exists for which the Required Actions have now been performed, or
 
d c. 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.
LCO  Applicability B 3.0    BWR/4 STS B 3.0-4  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
 
The time limits of LCO 3.0.3 allow 37 hours 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 reaching entering the next lower MODE applies. If a lower MODE is reached entered 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 reached entered in 2 hours, then the time allowed for reaching entering MODE 3 is the next 11 hours, because the total time for reaching entering MODE 3 is not reduced from the allowable limit of 13 hours. 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, 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.
 
LCO  3.0.4 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  Applicability B 3.0    BWR/4 STS B 3.0-5  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continu ed)  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 permit continued operation in following entry into 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 Required ActionsACTIONS 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 in accordance with the provisions of the Required Actions.
For example, LCO 3.0.4.a may be used when the Required Action states that an inoperable subsystem be restored to OPERABLE status within the Completion Time, and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE subsystem to be placed in operation. Use of LCO 3.0.4.a is acceptable because the associated ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE subsystem in operation) that permit 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 ris k 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 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included
 
in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."  Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93
-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."  These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management LCO  Applicability B 3.0    BWR/4 STS B 3.0-6  Rev. 3.1, 12/01/05 actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management 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  Applicability B 3.0    BWR/4 STS B 3.0-7  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
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 allowance 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 in 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 Activity[Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature 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.
 
LCO  Applicability B 3.0    BWR/4 STS B 3.0-8  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
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 meet, 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 Specifications.
 
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 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 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 provides an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow under administrative controls for the sole purpose of allowing the performance of required testing to demonstrate:  a. The LCO is met, The OPERABILITY of the equipment being returned to service or 
: b. Other LCOs are metThe OPERABILITY of other equipment.
LCO 3.0.5 allows Required Actions to not be followed temporarily in order to demonstrate an LCO is met without exiting the Applicability of the Specification.
The administrative controls ensure the time the Required Actions are not met 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 the LCO is metOPERABILITY. 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 LCO  Applicability B 3.0    BWR/4 STS B 3.0-9  Rev. 3.1, 12/01/05 practicable alternatives that comply with ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met.
LCO 3.0.5 is not intended to be used repeatedly
. An example of demonstrating t he LCO is metOPERABILITY of the equipment 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.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 required testin
: g.
LCO  Applicability B 3.0    BWR/4 STS B 3.0-10  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.5  (continued)
An other example of demonstrating the LCO is met OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. 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.
 
LCO  3.0.6 LCO 3.0.6 establishes an exception to LCO 3.0.2 for support ed systems that have a support system 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 system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the plant is maintained in a safe condition in the support system's Required Actions. However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system.
This may occur immediately or after some specified delay to perform some other Required Action. Regardless of whether it is immediate or after some delay, 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  Applicability B 3.0    BWR/4 STS B 3.0-11  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
Specification 5.5.12, "Safety Function Determination Program (SFDP)," ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6.
Cross division checks to identify a loss of safety function for those support systems that support safety systems are required. The cross division check verifies that the supported systems of the redundant OPERABLE support system are OPERABLE, thereby ensuring safety function is retained.  [ A loss of safety function may exist when a support system is inoperable, and:
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1),  b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE
 
B 3.0.6-2), or 
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3).
EXAMPLE B 3.0.6
-1  If System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5.
 
EXAMPLE B 3.0.6
-2  If System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5.
 
EXAMPLE B 3.0.6
-3  If System 2 of Train A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8, 9, 10 and
: 11. ]
LCO  Applicability B 3.0    BWR/4 STS B 3.0-12  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
 
    [ Figure B 3.0-1 Configuration of Trains and Systems ]  This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordance with the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sources also acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).
LCO  Applicability B 3.0    BWR/4 STS B 3.0-13  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists, consideration must be given to the specific type of function affected. Where a loss of function is solely due to a single Technical Specification support system (e.g., loss of automatic start due to inoperable instrumentation, or loss of pump suction source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilities of that system without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO is the LCO for the supported system. LCO  3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions. Special Operations LCOs in Section 3.10 allow specified TS requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed if required to comply with the requirements of these TS. Unless otherwise specified, all the other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.
The Applicability of a Special Operations LCO represents a condition not necessarily in compliance with the normal requirements of the TS. Compliance with Special Operations LCOs is optional. A special operation may be performed either under the provisions of the appropriate Special Operations LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Special Operations LCO, the requirements of the Special Operations LCO shall be followed. When a Special Operations LCO requires another LCO to be met, only the requirements of the LCO
 
statement are required to be met regardless of that LCO's Applicability (i.e., should the requirements of this other LCO not be met, the ACTIONS of the Special Operations LCO apply, not the ACTIONS of the other LCO). However, there are instances where the Special Operations LCO ACTIONS may direct the other LCOs' ACTIONS be met. The Surveillances of the other LCO are not required to be met, unless specified in the Special Operations LCO. If conditions exist such that the Applicability of any other LCO is met, all the other LCO's requirements (ACTIONS and SRs) are required to be met concurrent with the requirements of the Special Operations LCO.
 
LCO  Applicability B 3.0    BWR/4 STS B 3.0-14  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.
 
If the allowed time expires and the snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2. LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours to restore the snubber(s) before declaring the supported system inoperable. The 72 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.
LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system.
LCO 3.0.8.b allows 12 hours to restore the snubber(s) before declaring the supported system inoperable. The 12 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function.
LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or
 
LCO  Applicability B 3.0    BWR/4 STS B 3.0-15  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.8  (continued)
 
subsystem is properly controlled, and emergent issues are properly addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function.
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-16  Rev. 3.1, 12/01/05 B 3.0  SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
 
BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through 3.10 and apply at all times, unless otherwise stated. SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification.
 
SR  3.0.1 SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3.0.2, constitutes a failure to meet an LCO. Surveillances may be performed by means of any series of sequential, overlapping, or total steps provided the entire Surveillance is performed within the specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed by means of any series of sequential, overlapping, or total steps.
 
Systems and components are assumed to be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when:
: a. The systems or components are known to be inoperable, although still meeting the SRs or
: b. The requirements of the Surveillance(s) are known to be not met between required Surveillance performances.
 
Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a Special Operations LCO are only applicable when the Special Operations LCO is used as an allowable exception to the requirements of a Specification.
 
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanned event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-17  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.1  (continued)
Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.
 
Some examples of this process are:
: a. Control Rod Drive maintenance during refueling that requires scram testing at >
[800 psi]. However, if other appropriate testing is satisfactorily completed and the scram time testing of SR 3.1.4.3 is satisfied, the control rod can be considered OPERABLE. This allows startup to proceed to reach [800 psi] to perform other necessary testing. b. High pressure coolant injection (HPCI) maintenance during shutdown that requires system functional tests at a specified pressure.
Provided other appropriate testing is satisfactorily completed, startup can proceed with HPCI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.
SR  3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per..." interval.
SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-18  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.2  (continued)
 
The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. There are exceptions to SR 3.0.2 for certain are those Surveillances to for which the 25% extension of the interval specified in the Frequency may not be applieddoes not apply. These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Starting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Primary Containment Leakage Rate Testing Program which does not reference SR 3.0.2. SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations. An example of where SR 3.0.2 does not apply is in the Primary Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the regulations.
 
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 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 hours 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 SR  Applicability B 3.0    BWR/4 STS B 3.0-19  Rev. 3.1, 12/01/05 accordance with SR 3.0.2, and not at the time that the specified Frequency was not met.
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-20  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
This delay period provides adequate time to complete pe rform Surveillances that have been missed. This delay period permits the completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude completion performance 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 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 o f, 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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have been tested, the relay contacts have been tested by another SR, or historical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis SR  Applicability B 3.0    BWR/4 STS B 3.0-21  Rev. 3.1, 12/01/05 for the determination, should be completed to compensate for the lack of performance history.
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 as an operational convenience to extend Surveillance intervals. While up to 24 hours 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
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-22  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
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 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 Applicability.
This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. 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.
 
A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.
 
SR  Applicability B 3.0    BWR/4 STS B 3.0-23  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.4  (continue d)
However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.
The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 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.
The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met.
Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.
 
Completion Times 1.3    BWR/6 STS 1.3-1 Rev. 3.1, 12/01/05 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. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. For example, it may be established that a component is inoperable following improper maintenance performed in the past. The time of discovery (when the LCO is declared not met) is subsequent to both the time of occurrence (the improper maintenance), the time when it is identified that the component is degraded or nonconforming, and the time required to determine that the degraded or nonconforming component is inoperable.
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 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.
 
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.
However, when a subsequent division, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not LCO  Applicability 3.0    BWR/6 STS 3.0-1 Rev. 3.1, 12/01/05 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
LCO  3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8.
LCO  3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.
 
If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required, unless otherwise stated.
 
LCO  3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
: a. MODE 2 within 7 hours,
: b. MODE 3 within 13 hours, and
: c. MODE 4 within 37 hours.
 
Exceptions to this Specification are stated in the individual Specifications.
Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.
 
LCO 3.0.3 is only applicable in MODES 1, 2, and 3.
LCO  3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:
: a. When the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; 
: 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.
LCO  Applicability 3.0    BWR/6 STS 3.0-2 Rev. 3.1, 12/01/05 LCO  Applicability
 
LCO  3.0.4  (continued)
 
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 The Required Actions of Conditions Equipment removed from service or declared inoperable to comply with ACTIONS may be are not required to be met returned to serv ice under administrative control solely to perform testing required to demonstrate the LCO is met or that other LCOs are met its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under a dministrative control to perform the testing required to demonstrate OPERABILITYthe LCO is met or that other LCOs are met.
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.12, "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 LCO 3.0.7 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.
LCO  Applicability 3.0    BWR/6 STS 3.0-3 Rev. 3.1, 12/01/05 LCO  Applicability
 
LCO  3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:
: a. the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours; or
: b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours. 
 
At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-1  Rev. 3.1, 12/01/05 B 3.0  LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY
 
BASES LCOs LCO 3.0.1 through LCO 3.0.8 establish the general requirements applicable to all Specifications in Section 3.1 through 3.10 and apply at all times, unless otherwise stated.
LCO  3.0.1 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 LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The time of discovery is when the LCO is declared not met. The time of discovery is subsequent to both the time of occurrence of a degraded or nonconforming condition and the time of identification and evaluation of the degraded or nonconforming condition. The Completion Time of each Required Action for a n 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 case, compliance with the Required Actions provides an acceptable level of safety for continued operation.
 
Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-2  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.2  (continued)
The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.11, "RCS Pressure and Temperature (P/T)
Limits."
The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should be done in a manner that examines and balances the net effect on safety. Intentional entry into ACTIONS should not be made used for operational convenience. Additionally, if intentional entry into ACTIONS voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant equipment systems or components being inoperable, alternatives should be used instead. Doing so limits the time both subsystems/divisions of a safety function are inoperable and limits the time conditions exist which may result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.
When a change in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS Condition(s) are entered.
LCO  3.0.3 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
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-3  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
: 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 to permit 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 hour 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 reach ente r 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.
c b. A Condition exists for which the Required Actions have now been performed, or
 
d c. 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.
LCO  Applicability B 3.0    BWR/6 STS B 3.0-4  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.3  (continued)
 
The time limits of LCO 3.0.3 allow 37 hours 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 reaching entering the next lower MODE applies. If a lower MODE is reached entered 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 reached entered in 2 hours, then the time allowed for reaching entering MODE 3 is the next 11 hours, because the total time for reaching entering MODE 3 is not reduced from the allowable limit of 13 hours. 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, 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.7, "Fuel Pool Water Level."  LCO 3.7.7 has an Applicability of "During movement of irradiated fuel assemblies in the associated 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.7 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.7 of "Suspend movement of irradiated fuel assemblies in the associated fuel storage pool(s)" 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 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  Applicability B 3.0    BWR/6 STS B 3.0-5  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continue d)  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 permit continued operation in following entry into 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 Required ActionsACTIONS 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 in accordance with the provisions of the Required Actions.
For example, LCO 3.0.4.a may be used when the Required Action states that an inoperable subsystem be restored to OPERABLE status within the Completion Time, and the subsequent default ACTION ("Required Action and associated Completion Time not met")
allows the OPERABLE subsystem to be placed in operation. Use of LCO 3.0.4.a is acceptable because the associated ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE subsystem in operation) that permit 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 plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."  Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93
-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."  These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management LCO  Applicability B 3.0    BWR/6 STS B 3.0-6  Rev. 3.1, 12/01/05 actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management 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  Applicability B 3.0    BWR/6 STS B 3.0-7  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
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 allowance 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 in 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 Activity[Containment Air Temperature, Containment Pressure, MCPR, Moderator Temperature 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.
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-8  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.4  (continued)
 
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 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 provides an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow under administrative controls for the sole purpose of allowing the performance of required testing to demonstrate:
: a. The LCO is met, OPERABILITY of the equipment being returned to service or 
: b. Other LCOs are metThe OPERABILITY of other equipment.
LCO 3.0.5 allows Required Actions to not be followed temporarily in order to demonstrate an LCO is met without exiting the Applicability of the Specification.
The administrative controls ensure the time the Required Actions are not met 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 OPERABILITYthe LCO is met. 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 LCO  Applicability B 3.0    BWR/6 STS B 3.0-9  Rev. 3.1, 12/01/05 practicable alternatives that comply with ACTIONS and that do not require changing MODE and other specified conditions in the Applicability, in order to demonstrate the LCO is met or that other LCOs are met.
LCO 3.0.5 is not intended to be used repeatedly
. An example of demonstrating the LCO is met OPERABILITY of the equipment 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.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 required testing
.
LCO  Applicability B 3.0    BWR/6 STS B 3.0-10  Rev. 3.1, 12/01/05 BASES LCO  3.0.5  (continued)
An other example of demonstrating the LCO is met OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system. 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.
LCO  3.0.6 LCO 3.0.6 establishes an exception to LCO 3.0.2 for support ed systems that have a support system 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 system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the plant is maintained in a safe condition in the support system's Required Actions. However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system.
This may occur immediately or after some specified delay to perform some other Required Action. Regardless of whether it is immediate or after some delay, 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  Applicability B 3.0    BWR/6 STS B 3.0-11  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
Specification 5.5.12, "Safety Function Determination Program (SFDP)," ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6.
Cross division checks to identify a loss of safety function for those support systems that support safety systems are required. The cross division check verifies that the supported systems of the redundant OPERABLE support system are OPERABLE, thereby ensuring safety function is retained.  [ A loss of safety function may exist when a support system is inoperable, and:
: a. A required system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1),  b. A required system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE
 
B 3.0.6-2), or 
: c. A required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3).
EXAMPLE B 3.0.6
-1  If System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5.
 
EXAMPLE B 3.0.6
-2  If System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5.
 
EXAMPLE B 3.0.6
-3  If System 2 of Train A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8, 9, 10 and
: 11. ]
 
If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-12  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
    [ Figure B 3.0-1 Configuration of Trains and Systems ]
This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordance with the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sources also acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).
 
When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists, consideration must be given to the specific type of function affected. Where a loss of function is
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-13  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.6  (continued)
 
solely due to a single Technical Specification support system (e.g., loss of automatic start due to inoperable instrumentation, or loss of pump suction source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilities of that system without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO is the LCO for the supported system. LCO  3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions.
Special Operations LCOs in Section 3.10 allow specified TS requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed if required to comply with the requirements of these TS. Unless otherwise specified, all the other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.
The Applicability of a Special Operations LCO represents a condition not necessarily in compliance with the normal requirements of the TS.
Compliance with Special Operations LCOs is optional. A special operation may be performed either under the provisions of the appropriate Special Operations LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Special Operations LCO, the requirements of the Special Operations LCO shall be followed. When a Special Operations LCO requires another LCO to be met, only the requirements of the LCO statement are required to be met regardless of that LCO's Applicability (i.e., should the requirements of this other LCO not be met, the ACTIONS of the Special Operations LCO apply, not the ACTIONS of the other LCO). However, there are instances where the Special Operations LCO ACTIONS may direct the other LCOs' ACTIONS be met. The Surveillances of the other LCO are not required to be met, unless specified in the Special Operations LCO. If conditions exist such that the Applicability of any other LCO is met, all the other LCO's requirements (ACTIONS and SRs) are required to be met concurrent with the requirements of the Special Operations LCO.
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-14  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable o f
performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.
 
If the allowed time expires and the snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2. LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours to restore the snubber(s) before declaring the supported system inoperable. The 72 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.
LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system.
LCO 3.0.8.b allows 12 hours to restore the snubber(s) before declaring the supported system inoperable.
The 12 hour Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function.
LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or
 
LCO  Applicability B 3.0    BWR/6 STS B 3.0-15  Rev. 3.1, 12/01/05 BASES
 
LCO  3.0.8  (continued)
 
subsystem is properly controlled, and emergent issues are properly addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function.
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-16  Rev. 3.1, 12/01/05 B 3.0  SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
 
BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable to all Specifications in Section 3.1 through 3.10 and apply at all times, unless otherwise stated.
SR 3.0.1 through SR 3.0.4 apply in Chapter 5 only when invoked by a Chapter 5 Specification.
 
SR  3.0.1 SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3.0.2, constitutes a failure to meet an LCO. Surveillances may be performed by means of any series of sequential, overlapping, or total steps provided the entire Surveillance is performed within the specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed by means of any series of sequential, overlapping, or total steps.
 
Systems and components are assumed to be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or components are OPERABLE when:
: a. The systems or components are known to be inoperable, although still meeting the SRs or
: b. The requirements of the Surveillance(s) are known to be not met between required Surveillance performances.
 
Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a Special Operations LCO are only applicable when the Special Operations LCO is used as an allowable exception to the requirements of a Specification.
 
Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanned event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-17  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.1  (continued)
Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.
Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed. Some examples of this process are:
: a. Control Rod Drive maintenance during refueling that requires scram testing at >
[800 psi]. However, if other appropriate testing is satisfactorily completed and the scram time testing of SR 3.1.4.3 is satisfied, the control rod can be considered OPERABLE. This allows startup to proceed to reach [800 psi] to perform other necessary testing. 
: b. Reactor Core Isolation Cooling (RCIC) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with RCIC considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.
 
SR  3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per..." interval.
 
SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-18  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.2  (continued)
 
The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. The re are exceptions to SR 3.0.2 for certain are those Surveillances to for which the 25% extension of the interval specified in the Frequency may not be applieddoes not apply. These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. For those Surveillances in Chapter 3 whose Frequency refers to a Program in Section 5.5, the referenced Program specification must be examined to determine if SR 3.0.2 applies. For example, the Diesel Fuel Oil Testing Program is referenced in Specification 3.8.3, "Diesel Fuel Oil, Lube Oil, and Starting Air," and the program invokes SR 3.0.2. An example of where SR 3.0.2 does not apply is in the Primary Containment Leakage Rate Testing Program which does not reference SR 3.0.2.
SR 3.0.2 is not applicable because the Program establishes Frequencies to meet the requirements of regulations. An example of where SR 3.0.2 does not apply is in the Primary Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the regulations.
 
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 remedia l 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 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 hours 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 SR  Applicability B 3.0    BWR/6 STS B 3.0-19  Rev. 3.1, 12/01/05 accordance with SR 3.0.2, and not at the time that the specified Frequency was not met.
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-20  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
This delay period provides adequate time to complete perform Surveillances that have been missed. This delay period permits the completion of a Surveillance before complying with Required Actions or other remedial measures that might preclude completion performance 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 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 o f, 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 would be a relay contact that has never been tested in accordance with a particular SR, but the adjacent, physically connected relay contacts have been tested, the relay contacts have been tested by another SR, or historical operation of the actuated equipment has been successful. 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. A review of the Surveillance history may be sufficient to provide a reasonable expectation that the Surveillance will be met when performed. For Surveillances that have never been performed, a more rigorous evaluation, documented in sufficient detail to explain the basis for the determination, should be completed to compensate for the lack of performance history.
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-21  Rev. 3.1, 12/01/05 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 as an operational convenience to extend Surveillance intervals. While up to 24 hours 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
 
SR  Applicability B 3.0    BWR/6 STS B 3.0-22  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.3  (continued)
 
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 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 Applicability.
 
This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. 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.
 
A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.
SR  Applicability B 3.0    BWR/6 STS B 3.0-23  Rev. 3.1, 12/01/05 BASES
 
SR  3.0.4  (continu ed)
However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.
The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 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.
 
The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met.
Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.}}

Latest revision as of 18:47, 9 November 2018

Redirect to:

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