ML100550636

Developmental Revision B - Technical Requirements Manual Bases B 3.0 - Technical Requirement (TR) and Technical Surveillance Requirement (Tsr) Applicability

ML100550636
Person / Time
Site:	Watts Bar
Issue date:	02/02/2010
From:	Tennessee Valley Authority
To:	Office of Nuclear Reactor Regulation
References
Download: ML100550636 (14)

Text

TR and TSR APPLICABILITY B 3.0 B 3.0 TECHNICAL REQUIREMENT (TR) AND TECHNICAL SURVEILLANCE REQUIREMENT (TSR) APPLICABILITY BASES TRs TR 3.0.1 through TR 3.0.6 establish the general requirements applicable to all Requirements and apply at all times, unless otherwise stated.

TR 3.0.1 TR 3.0.1 establishes the Applicability statement within each individual Requirement as the requirements for when the TR is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Requirement).

TR 3.0.2 TR 3.0.2 establishes that upon discovery of a failure to meet a TR, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered. The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of a TR are not met. This Requirement establishes that:

a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Requirement; and

b. Completion of the Required Actions is not required when a TR 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 TR 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 Requirement 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.

(continued)

Watts Bar - Unit 2 B 3.0-1 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.2 (continued)

Completing the Required Actions is not required when a TR is met or is no longer applicable, unless otherwise stated in the individual Technical Requirements.

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 TR's ACTIONS specify the Required Actions where this is the case. An example of this is in TR 3.4.2, "Pressurizer Temperature 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 not be made for operational convenience. Alternatives that would not result in redundant equipment being inoperable should be used instead. Doing so limits the time both subsystems/trains of a safety function are inoperable and limits the time other conditions exist which result in TR 3.0.3 being entered. Individual Requirements may specify a time limit for performing a TSR 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 Requirement becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Requirement becomes applicable, and the ACTIONS Condition(s) are entered.

(continued)

Watts Bar - Unit 2 B 3.0-2 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.3 (continued)

TR 3.0.3 establishes the actions that must be implemented when a TR is not met and:

a. An associated Required Action and Completion Time is not met and no other Condition applies; or

b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering TR 3.0.3 is warranted; in such cases, the ACTIONS specifically state a Condition corresponding to such combinations and also that TR 3.0.3 be entered immediately.

This Requirement 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 TR and its ACTIONS.

It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.

Upon entering TR 3.0.3, 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> is allowed to prepare for an orderly shutdown before initiating a change in unit operation. This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The time limits specified to 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 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 Requirement applies. The use and interpretation of specified times to complete the actions of TR 3.0.3 are consistent with the discussion of Section 1.3, Completion Times.

(continued)

Watts Bar - Unit 2 B 3.0-3 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.3 (continued)

A unit shutdown required in accordance with TR 3.0.3 may be terminated and TR 3.0.3 exited if any of the following occurs:

a. The TR is now met.

b. A Condition exists for which the Required Actions have now been performed.

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 TR 3.0.3 is exited.

The time limits of TR 3.0.3 allow 37 hours4.282407e-4 days <br />0.0103 hours <br />6.117725e-5 weeks <br />1.40785e-5 months <br /> for the unit to be in MODE 5 when a shutdown is required during MODE 1 operation. If the unit is in a lower MODE of operation when a shutdown is required, the time limit for reaching the next lower MODE applies. If a lower MODE is reached in less time than allowed, however, the total allowable time to reach MODE 5, or other applicable MODE, is not reduced. For example, if MODE 3 is reached in 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br />, then the time allowed for reaching MODE 4 is the next 11 hours1.273148e-4 days <br />0.00306 hours <br />1.818783e-5 weeks <br />4.1855e-6 months <br />, because the total time for reaching MODE 4 is not reduced from the allowable limit of 13 hours1.50463e-4 days <br />0.00361 hours <br />2.149471e-5 weeks <br />4.9465e-6 months <br />. Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to reach a lower MODE of operation in less than the total time allowed.

In MODES 1, 2, 3, and 4, TR 3.0.3 provides actions for Conditions not covered in other Requirements. The requirements of TR 3.0.3 do not apply in MODES 5 and 6 because the unit is already in the most restrictive Condition required by TR 3.0.3. The requirements of TR 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 Requirements sufficiently define the remedial measures to be taken.

Exceptions to TR 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with TR 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in TR 3.3.4, "Seismic Instrumentation". TR 3.3.4 has an Applicability of "At all times". Therefore, this TR can be applicable in any or all MODES. If the TR and the Required Actions of TR 3.3.4 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by (continued)

Watts Bar - Unit 2 B 3.0-4 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.3 (continued) placing the unit in a shutdown condition. The Required Actions are the appropriate Required Actions to complete in lieu of the actions of TR 3.0.3. These exceptions are addressed in the individual Requirements.

TR 3.0.4 TR 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when a TR 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 TR would not be met, in accordance with TR 3.0.4.a, TR 3.0.4.b, or TR 3.0.4.c.

TR 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the TR not met 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. Compliance with 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.

TR 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the TR 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 be assessed and managed. The risk assessment, for the purposes of TR 3.0.4.b, must take into account all inoperable Technical Specification or TRM 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 (continued)

Watts Bar - Unit 2 B 3.0-5 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.4 (continued) 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 TR would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.

TR 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 TR 3.0.4.b risk assessments do not have to be documented.

TRs 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 TR, the use of the TR 3.0.4.b allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, a small subset of systems and components may be determined to be more important to risk and therefore, the use of the TR 3.0.4.b allowance will be prohibited. The TRs governing these system and components will contain Notes prohibiting the use of TR 3.0.4.b by stating that TR 3.0.4.b is not applicable.

(continued)

Watts Bar - Unit 2 B 3.0-6 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.5 (continued)

TR 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 Requirement is to provide an exception to TR 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow the performance of TSRs to demonstrate:

a. The OPERABILITY of the equipment being returned to service; or

b. The OPERABILITY of other equipment.

The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed TSRs. This requirement does not provide time to perform any other preventive or corrective maintenance.

An example of demonstrating the OPERABILITY of the equipment being returned to service is reopening a containment isolation valve that has been closed to comply with Required Actions and must be reopened to perform the TSRs.

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 a TSR 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 a TSR on another channel in the same trip system.

TR 3.0.6 TR 3.0.6 establishes an exception to TR 3.0.2 for support systems that have a TR specified in the Technical Requirements. This exception is provided because TR 3.0.2 would require that the Conditions and Required Actions of the associated inoperable supported system TR 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 TR's Required Actions. These Required Actions may include entering the supported system's Conditions and Required Actions or may specify other Required Actions.

(continued)

Watts Bar - Unit 2 B 3.0-7 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TRs TR 3.0.6 (continued)

When a support system is inoperable and there is a TR specified for it in the Technical Requirements, the supported system(s) is 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' TRs' 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 TR 3.0.2.

Technical Specification 5.7.2.18, "Safety Function Determination Program (SFDP)," ensures loss of safety function is detected and appropriate actions are taken. Upon entry into TR 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 TR 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. If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the TR in which the loss of safety function exists are required to be entered.

Watts Bar - Unit 2 B 3.0-8 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.1 through TSR 3.0.4 establish the general requirements applicable to all Technical Surveillance Requirements and apply at all times, unless otherwise stated.

TSR 3.0.1 TSR 3.0.1 establishes the requirement that TSRs must be met during the MODES or other specified conditions in the Applicability for which the requirements of the TR apply, unless otherwise specified in the individual TSRs. This Requirement 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 TSR 3.0.2, constitutes a failure to meet a TR.

Systems and components are assumed to be OPERABLE when the associated TSRs have been met. Nothing in this Requirement, 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 TSRs; 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 TR are not applicable, unless otherwise specified.

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

Watts Bar - Unit 2 B 3.0-9 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.1 (continued)

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.

TSR 3.0.2 TSR 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.

TSR 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 TSRs. The exceptions to TSR 3.0.2 are those Surveillances for which the 25% extension of the interval specified in the Frequency does not apply.

These exceptions are stated in the individual Requirements. An example of where TSR 3.0.2 does not apply is a Surveillance with a Frequency of "in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions." The requirements of regulations take precedence over the TRs. The TRs cannot in and of themselves extend a test interval specified in the regulations. Therefore, there is a Note in the Frequency stating, "TSR 3.0.2 is not applicable."

As stated in TSR 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 (continued)

Watts Bar - Unit 2 B 3.0-10 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.2 (continued) 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 TSR 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.

TSR 3.0.3 TSR 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 within the specified Frequency.

A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with TSR 3.0.2, and not at the time that the specified Frequency was not met.

This delay period provides adequate time to complete 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 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, TSR 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.

(continued)

Watts Bar - Unit 2 B 3.0-11 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.3 (continued)

TSR 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.

Failure to comply with specified Frequencies for TSRs is expected to be an infrequent occurrence. Use of the delay period established by TSR 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 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity. The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance. This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide 1.182, Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants. This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown. The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component. Missed Surveillances for important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program.

If a Surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the variable is considered outside the specified limits and the Completion Times of the Required Actions for the applicable TR 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 TR Conditions begin immediately upon the failure of the Surveillance.

(continued)

Watts Bar - Unit 2 B 3.0-12 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.3 (continued)

Completion of the Surveillance within the delay period allowed by this Requirement, or within the Completion Time of the ACTIONS, restores compliance with TSR 3.0.1.

TSR 3.0.4 TSR 3.0.4 establishes the requirement that all applicable TSRs must be met before entry into a MODE or other specified condition in the Applicability.

This TSR 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 the TR 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 a TR is not met due to Surveillance not being met in accordance with TR 3.0.4.

However, in certain circumstances, failing to meet a TSR will not result in TSR 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 TSR(s) are not required to be performed, per TSR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment.

When equipment is inoperable, TSR 3.0.4 does not apply to the associated TSR(s) since the requirement for the TSR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in a TSR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the TR is not met in this instance, TR 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. TSR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a TSR has not been performed within the specified Frequency, provided the requirement to declare the TR not met has been delayed in accordance with TSR 3.0.3.

(continued)

Watts Bar - Unit 2 B 3.0-13 Technical Requirements (developmental) A

TR and TSR APPLICABILITY B 3.0 BASES TSRs TSR 3.0.4 (continued)

The provisions of TSR 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 TSR 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 TSR 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 TR prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the TRs 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.

Watts Bar - Unit 2 B 3.0-14 Technical Requirements (developmental) A