Text

Developmental Revision B - Technical Requirements Manual 1.0 - Use and Application
	ML100550612
Person / Time
Site:	Watts Bar
Issue date:	02/02/2010
From:	; Tennessee Valley Authority
To:	; Office of Nuclear Reactor Regulation
References
	Download: ML100550612 (24)
	v • d • e

Definitions 1.1 (continued)

Watts Bar - Unit 2 1.1-1 Technical Requirements (developmental) A 1.0 USE AND APPLICATION 1.1 Definitions

NOTE----------------------------------------------------------

The defined terms of this section appear in capitalized type and are applicable throughout these

Technical Requirements and Bases.

Term Definition ACTIONS ACTIONS shall be that part of a Requirement that prescribes Required Actions to be taken under designated Conditions

within specified Completion Times. CHANNEL CALIBRATION A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel so that it responds within the

required range and accuracy to known input. The CHANNEL

CALIBRATION shall encompass the entire channel, including

the required sensor, alarm, interlock, display, and trip

functions. Calibration of instrument channels with resistance

temperature detector (RTD) or thermocouple sensors may

consist of an inplace qualitative assessment of sensor

behavior and normal calibration of the remaining adjustable

devices in the channel. Whenever a sensing element is

replaced, the next required CHANNEL CALIBRATION shall

include an inplace cross calibration that compares the other

sensing elements with the recently installed sensing element.

The CHANNEL CALIBRATION may be performed by means

of any series of sequential, overlapping calibrations or total

channel steps so that the entire channel is calibrated.

CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This

determination shall include, where possible, comparison of

the channel indication and status to other indications or

status derived from independent instrument channels

measuring the same parameter.

Definitions 1.1 1.1 Definitions (continued)

(continued)

Watts Bar - Unit 2 1.1-2 Technical Requirements (developmental) A Term Definition CHANNEL OPERATIONAL TEST (COT)

A COT shall be the injection of a simulated or actual signal

into the channel as close to the sensor as practicable to verify

the OPERABILITY of required alarm, interlock, display, and

trip functions. The COT shall include adjustments, as

necessary, of the required alarm, interlock, and trip setpoints

so that the setpoints are within the required range and accuracy.

CORE ALTERATION CORE ALTERATION shall be the movement of any fuel, sources, or other reactivity control components, within the

reactor vessel with the vessel head removed and fuel in the

vessel. Suspension of CORE ALTERATIONS shall not

preclude completion of movement of a component to a safe

position.

ENGINEERED SAFETY

FEATURE (ESF) RESPONSE

TIME The ESF RESPONSE TIME shall be that time interval from

when the monitored parameter exceeds its ESF actuation

setpoint at the channel sensor until the ESF equipment is

capable of performing its safety function (i.e., the valves

travel to their required positions, pump discharge pressures

reach their required values, etc.). Times shall include diesel

generator starting and sequence loading delays, where

applicable. The response time may be measured by means

of any series of sequential, overlapping, or total steps so that

the entire response time is measured. In lieu of

measurement, response time may be verified for selected

components provided that the components and the

methodology for verification have been previously reviewed

and approved by the NRC.

LEAKAGE LEAKAGE shall be:

a. Identified LEAKAGE

1. LEAKAGE, such as that from pump seals or valve packing (except reactor coolant pump (RCP) seal

water injection or leakoff), that is captured and

conducted to collection systems or a sump or

collecting tank;

Definitions 1.1 1.1 Definitions (continued)

Watts Bar - Unit 2 1.1-3 Technical Requirements (developmental) A LEAKAGE (continued) 2. LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere with the operation of leakage

detection systems or not to be pressure boundary

LEAKAGE; or

3. Reactor Coolant System (RCS) LEAKAGE through a steam generator (SG) tube to the Secondary

System; b. Unidentified LEAKAGE

All LEAKAGE (except RCP seal water injection or

leakoff) that is not identified LEAKAGE;

c. Pressure Boundary LEAKAGE

LEAKAGE (except SG tube LEAKAGE) through a non-

isolable fault in an RCS component body, pipe wall, or

vessel wall. MODE A MODE shall correspond to any one inclusive combination of core reactivity condition, power level, average reactor

coolant temperature, and reactor vessel head closure bolt

tensioning specified in Table 1.1-1 with fuel in the reactor vessel. OPERABLE - OPERABILITYA system, subsystem, train, component, or device shall be

OPERABLE or have OPERABILITY when it is capable of

performing its specified function(s) and when all necessary

attendant instrumentation, controls, normal or emergency

electrical power, cooling and seal water, lubrication, and

other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its

specified safety function(s) are also capable of performing

their related support function(s).

Definitions 1.1 1.1 Definitions (continued)

(continued)

Watts Bar - Unit 2 1.1-4 Technical Requirements (developmental) B Term Definition QUADRANT POWER TILT RATIO (QPTR)

QPTR shall be the ratio of the maximum upper excore

detector calibrated output to the average of the upper excore

detector calibrated outputs, or the ratio of the maximum lower

excore detector calibrated output to the average lower excore

detector calibrated outputs, whichever is greater.

RATED THERMAL POWER (RTP) RTP shall be a total reactor core heat transfer rate to the

reactor coolant of 3411 MWt.

REACTOR TRIP SYSTEM (RTS) RESPONSE TIME The RTS RESPONSE TIME shall be that time interval from

when the monitored parameter exceeds its RTS trip setpoint

at the channel sensor until loss of stationary gripper coil

voltage. The response time may be measured by means of

any series of sequential, overlapping, or total steps so that

the entire response time is measured. In lieu of

measurement, response time may be verified for selected

components provided that the components and the

methodology for verification have been previously reviewed

and approved by the NRC. SHUTDOWN MARGIN (SDM) SDM shall be the in stantaneous amount of reactivity by which the reactor is subcritical or would be subcritical from its

present condition assuming:

a. All rod cluster control assemblies (RCCAs) are fully inserted except for the single RCCA of highest reactivity

worth, which is assumed to be fully withdrawn. With any

RCCA not capable of being fully inserted, the reactivity

worth of the RCCA must be accounted for in the

determination of SDM; and

b. In MODES 1 and 2, the fuel and moderator temperatures are changed to the nominal zero power design level.

Definitions 1.1 1.1 Definitions (continued)

Watts Bar - Unit 2 1.1-5 Technical Requirements (developmental) A Term Definition STAGGERED TEST BASIS A STAGGERED TEST BASIS shall consist of the testing of one of the systems, subsystems, channels, or other

designated components during the interval specified by the

Surveillance Frequency so that all systems, subsystems, channels, or other designated components are tested during

n Surveillance Frequency intervals, where n is the total number of systems, subsystems, channels, or other

designated components in the associated function. THERMAL POWER THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant.

TRIP ACTUATING DEVICE

OPERATIONAL TEST (TADOT) TADOT shall consist of operating the trip actuating device

and verifying OPERABILITY of required alarm, interlock, display, and trip functions. The TADOT shall include

adjustment, as necessary, of the trip actuating device so that

it actuates at the required setpoint within the required accuracy.

Definitions 1.1 Watts Bar - Unit 2 1.1-6 Technical Requirements (developmental) A Table 1.1-1 (page 1 of 1)

MODES MODE TITLE REACTIVITY CONDITION (k eff) % RATED THERMAL POWER (a) AVERAGE REACTOR COOLANT TEMPERATURE

( F) 1 Power Operation 0.99 > 5 NA 2 Startup 0.99 5 NA 3 Hot Standby < 0.99 NA 350 4 Hot Shutdown (b) < 0.99 NA 350 > Tavg > 200 5 Cold Shutdown (b) < 0.99 NA 200 6 Refueling (c) NA NA NA (a) Excluding decay heat.

(b) All reactor vessel head closure bolts fully tensioned.

(c) One or more reactor vessel head closure bolts less than fully tensioned.

Logical Connectors 1.2 (continued)

Watts Bar - Unit 2 1.2-1 Technical Requirements ( developmental) A 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Requirements (TRs) to

discriminate between, and yet connect, discrete Conditions, Required

Actions, Completion Times, Surveillances, and Frequencies. The only

logical connectors that appear in TRs are AND and OR. The physical arrangement of these connectors constitutes logical conventions with

specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical

connectors and by the number assigned to each Required Action. The

first level of logic is identified by the first digit of the number assigned to a

Required Action and the placement of the logical connector in the first

level of nesting (i.e., left justified with the number of the Required Action).

The successive levels of logic are identified by additional digits of the

Required Action number and by successive indentations of the logical

connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

Logical Connectors 1.2 1.2 Logical Connectors (Continued)

(continued)

Watts Bar - Unit 2 1.2-2 Technical Requirements ( developmental) AEXAMPLES The following examples illustrate the use of logical connectors. EXAMPLE 1.2-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. TR not met.

A.1 Verify . . .

AND A.2 Restore . . .

In this example the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.

Logical Connectors 1.2 1.2 Logical Connectors Watts Bar - Unit 2 1.2-3 Technical Requirements ( developmental) A EXAMPLES (continued)

EXAMPLE 1.2-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. TR not met.

A.1 Trip . . .

OR A.2.1 Verify . . .

AND A.2.2.1 Reduce . . .

OR A.2.2.2 Perform . . .

OR A.3 Align . . .

This example represents a more complicated use of logical connectors.

Required Actions A.1, A.2, and A.3 are alternative choices, only one of

which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be

performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented

position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

Completion Times 1.3 (continued)

Watts Bar - Unit 2 1.3-1 Technical Requirements ( developmental) A 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 Technical Requirements (TRs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an TR

state Conditions that typically describe the ways in which the

requirements of the TR 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

TR. 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 TR Applicability.

If situations are discovered that require entry into more than one

Condition at a time within a single TR (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.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-2 Technical Requirements ( developmental) A DESCRIPTION (continued)

However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this

Completion Time extension, two criteria must first be met. The

subsequent inoperability:

a. Must exist concurrent with the first inoperability; and

b. Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to

address the subsequent inoperability shall be limited to the more

restrictive of either:

a. The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months ; 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 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months ," 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 . . ." Example 1.3-3 illustrates one use of

this type of Completion Time. The 10 day Completion Time specified for

Conditions A and B in Example 1.3-3 may not be extended.

Completion Times 1.3 1.3 Completion Times (continued)

(continued)

Watts Bar - Unit 2 1.3-3 Technical Requirements (3 developmental) AEXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and

associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND B.2 Be in MODE 5.

36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the

time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND in MODE 5 within 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months . A total of 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months (not 42 hours4.861111e-4 days 0.0117 hours 6.944444e-5 weeks 1.5981e-5 months ) is allowed for

reaching MODE 5 from the time that Condition B was entered. If MODE 3

is reached within 3 hours3.472222e-5 days 8.333333e-4 hours 4.960317e-6 weeks 1.1415e-6 months , the time allowed for reaching MODE 5 is the

next 33 hours3.819444e-4 days 0.00917 hours 5.456349e-5 weeks 1.25565e-5 months because the total time allowed for reaching MODE 5 is

36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months .

If Condition B is entered while in MODE 3, the time allowed for reaching

MODE 5 is the next 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months .

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-4 Technical Requirements (3 developmental) AEXAMPLES (continued) EXAMPLE 1.3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B. Required Action and associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND B.2 Be in MODE 5.

36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is entered

and the Completion Time clocks for Required Actions B.1 and B.2 start. If

the inoperable pump is restored to OPERABLE status after Condition B is

entered, Condition A and B are exited, and therefore, the Required

Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still

inoperable, Condition A is not re-entered for the second pump. TR 3.0.3

is entered, since the ACTIONS do not include a Condition for more than

one inoperable pump. The Completion Time clock for Condition A does

not stop after TR 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

While in TR 3.0.3, if one of the inoperable pumps is restored to

OPERABLE status and the Completion Time for Condition A has not

expired, TR 3.0.3 may be exited and operation continued in accordance

with Condition A.

While in TR 3.0.3, if one of the inoperable pumps is restored to

OPERABLE status and the Completion Time for Condition A has expired, TR 3.0.3 may be exited and operation continued in accordance with

Condition B. The Completion Time for Condition B is tracked from the

time the Condition A Completion Time expired.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-5 Technical Requirements (3 developmental) AEXAMPLES EXAMPLE 1.3-2 (continued)

On restoring one of the pumps to OPERABLE status, the Condition A

Completion Time is not reset, but continues from the time the first pump

was declared inoperable. This Completion Time may be extended if the

pump restored to OPERABLE status was the first inoperable pump. A

24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months extension to the stated 7 days is allowed, provided this does not

result in the second pump being inoperable for > 7 days.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-6 Technical Requirements (3 developmental) AEXAMPLES (continued) EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X train inoperable.

A.1 Restore Function X train to OPERABLE

status. 7 days AND 10 days from

discovery of failure to

meet the TR B. One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE

status 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months AND 10 days from

discovery of failure to

meet the TR C. One Function X train inoperable.

C.1 Restore Function X train to OPERABLE

status. 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months AND OR One Function Y

train inoperable C.2 Restore Function Y train to OPERABLE

status. 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-7 Technical Requirements (3 developmental) AEXAMPLES EXAMPLE 1.3-3 (continued)

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each

train starting from the time each train was declared inoperable and the

Condition was entered. A separate Completion Time is established for

Condition C and tracked from the time the second train was declared

inoperable (i.e., the time the situation described in Condition C was

discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required

Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e., initial entry

into Condition A).

The Completion Times of Conditions A and B are modified by a logical

connector with a separate 10 day Completion Time measured from the

time it was discovered the TR was not met. In this example, without the

separate Completion Time, it would be possible to alternate between

Conditions A, B, and C in such a manner that operation could continue

indefinitely without ever restoring systems to meet the TR. The separate

Completion Time modified by the phrase "from discovery of failure to

meet the TR" is designed to prevent indefinite continued operation while

not meeting the TR. This Completion Time allows for an exception to the

normal "time zero" for beginning the Completion Time "clock". In this

instance, the Completion Time "time zero" is specified as commencing at

the time the TR was initially not met, instead of at the time the associated

Condition was entered.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-8 Technical Requirements (3 developmental) AEXAMPLES (continued) EXAMPLE 1.3-4 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One or more valves inoperable.

A.1 Restore valve(s) to OPERABLE status.

4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months B. Required Action and

associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND B.2 Be in MODE 4.

12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months

A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is

based on the initial entry into Condition A and is not tracked on a per

valve basis. Declaring subsequent valves inoperable, while Condition A

is still in effect, does not trigger the tracking of separate Completion

Times.

Once one of the valves has been restored to OPERABLE status, the

Condition A Completion Time is not reset, but continues from the time the

first valve was declared inoperable. The Completion Time may be

extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months provided this does not result in any subsequent valve being

inoperable for > 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months .

If the Completion Time of 4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months (including the extension) expires while

one or more valves are still inoperable, Condition B is entered.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-9 Technical Requirements (3 developmental) AEXAMPLES (continued) EXAMPLE 1.3-5 ACTIONS --------------------------------------------NOTE--------------------------------------------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more valves inoperable.

A.1 Restore valve to OPERABLE status.

4 hours4.62963e-5 days 0.00111 hours 6.613757e-6 weeks 1.522e-6 months B. Required Action and associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND B.2 Be in MODE 4.

12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months The Note above the ACTIONS table is a method of modifying how the Completion Time is tracked. If this method of modifying how the

Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the

ACTIONS table.

The Note allows Condition A to be entered separately for each inoperable

valve, and Completion Times tracked on a per valve basis. When a valve

is declared inoperable, Condition A is entered and its Completion Time

starts. If subsequent valves are declared inoperable, Condition A is

entered for each valve and separate Completion Times start and are

tracked for each valve.

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve. If the Completion Times associated

with subsequent valves in Condition A expire, Condition B is entered

separately for each valve and separate Completion Times start and are

tracked for each valve. If a valve that caused entry into Condition B is

restored to OPERABLE status, Condition B is exited for that valve.

Completion Times 1.3 1.3 Completion Times (continued)

Watts Bar - Unit 2 1.3-10 Technical Requirements (3 developmental) AEXAMPLES EXAMPLE 1.3-5 (continued)

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One channel inoperable.

A.1 Perform SR 3.x.x.x.

Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months OR A.2 Reduce THERMAL POWER to 50% RTP.

8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months B. Required Action and associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "Once per" Completion Time, which

qualifies for the 25% extension, per TSR 3.0.2, to each performance after

the initial performance. The initial 8 hour9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months interval of Required Action A.1

begins when Condition A is entered and the initial performance of

Required Action A.1 must be complete within the first 8 hour9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months interval. If

Required Action A.1 is followed, and the Required Action is not met within

the Completion Time (plus the extension allowed by TSR 3.0.2),

Condition B is entered. If Required Action A.2 is followed and the

Completion Time of 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

Completion Times 1.3 1.3 Completion Times Watts Bar - Unit 2 1.3-11 Technical Requirements ( developmental) AEXAMPLES (continued) EXAMPLE 1.3-7 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One subsystem inoperable A.1 Verify affected subsystem isolated.

1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months AND Once per 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months

thereafter AND A.2 Restore subsystem to OPERABLE

status. 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months B. Required Action and associated

Completion

Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months AND B.2 Be in MODE 5.

36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months Completion Time begins at the time the Condition is entered and each "Once per

8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months thereafter" interval begins upon performance of Required

Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either

the initial 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months or any subsequent 8 hour9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months interval from the previous

performance (plus the extension allowed by TSR 3.0.2), Condition B is

entered. The Completion Time clock for Condition A does not stop after

Condition B is entered, but continues from the time Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance

with Condition A, provided the Completion Time for Required Action A.2

has not expired.

IMMEDIATE

COMPLETION

TIME When "Immediately" is used as a Completion Time, the Required Action

should be pursued without delay and in a controlled manner.

Frequency 1.4 (continued)

Watts Bar - Unit 2 1.4-1 Technical Requirements ( developmental) A 1.0 USE AND APPLICATION 1.4 Frequency

PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Technical Surveillance Requirement (TSR) has a specified Frequency in which the Surveillance must be met in order to meet the

associated Technical Requirement (TR). An understanding of the correct

application of the specified Frequency is necessary for compliance with

the TSR.

The "specified Frequency" is referred to throughout this section and each

of the Requirements of Section 3.0, Technical Surveillance Requirement (TSR) Applicability. The "specified Frequency" consists of the

requirements of the Frequency column of each TSR as well as certain

Notes in the Surveillance column that modify performance requirements.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be

performed until sometime after the associated TR is within its

Applicability, represent potential TSR 3.0.4 conflicts. To avoid these

conflicts, the TSR (i.e., the Surveillance or the Frequency) is stated such

that it is only "required" when it can be and should be performed. With an

TSR satisfied, TSR 3.0.4 imposes no restriction.

Frequency 1.4 1.4 Frequency (Continued)

(continued)

Watts Bar - Unit 2 1.4-2 Technical Requirements ( developmental) AEXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the TR (TR not shown) is MODES 1, 2, and 3.

EXAMPLE 1.4-1 TECHNICAL SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK.

12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months Example 1.4-1 contains the type of TSR most often encountered in the TRs. The Frequency specifies an interval (12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months ) during which the

associated Surveillance must be performed at least one time.

Performance of the Surveillance initiates the subsequent interval.

Although the Frequency is stated as 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months , an extension of the time

interval to 1.25 times the interval specified in the Frequency is allowed by

TSR 3.0.2 for operational flexibility. The measurement of this interval

continues at all times, even when the TSR is not required to be met per

TSR 3.0.1 (such as when the equipment is inoperable, a variable is

outside specified limits, or the unit is outside the Applicability of the TR).

If the interval specified by TSR 3.0.2 is exceeded while the unit is in a

MODE or other specified condition in the Applicability of the TR, and the

performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then TSR 3.0.3 becomes applicable.

If the interval as specified by TSR 3.0.2 is exceeded while the unit is not

in a MODE or other specified condition in the Applicability of the TR for

which performance of the TSR is required, the Surveillance must be

performed within the Frequency requirements of TSR 3.0.2 prior to entry

into the MODE or other specified condition. Failure to do so would result

in a violation of TSR 3.0.4.

Frequency 1.4 1.4 Frequency (continued)

Watts Bar - Unit 2 1.4-3 Technical Requirements ( developmental) AEXAMPLES (continued) EXAMPLE 1.4-2 TECHNICAL SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits.

Once within 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months after 25% RTP AND 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months thereafter

Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, and the second is of the type shown in Example 1.4-1. The

logical connector " AND" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level

< 25% RTP to 25% RTP, the Surveillance must be performed within 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

The use of "once" indicates a single performance will satisfy the specified

Frequency (assuming no other Frequencies are connected by " AND"). This type of Frequency does not qualify for the extension allowed by

TSR 3.0.2. "Thereafter" indicates future performances must be

established per TSR 3.0.2, but only after a specified condition is first met (i.e., the "once" performance in this example). If reactor power decreases

to < 25% RTP, the measurement of both intervals stops. New intervals

start upon reactor power reaching 25% RTP.

Frequency 1.4 1.4 Frequency Watts Bar - Unit 2 1.4-4 Technical Requirements ( developmental) AEXAMPLES (continued) EXAMPLE 1.4-3 TECHNICAL SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

NOTE----------------------------

Not required to be performed until 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months after 25% RTP.

Perform channel adjustment.

7 days The interval continues, whether or not the unit operation is < 25% RTP between performances.

As the Note modifies the required performance of the Surveillance, it is construed to be part of the "specified Frequency." Should the 7 day

interval be exceeded while operation is < 25% RTP, this Note allows 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months after power reaches 25% RTP to perform the Surveillance.

The Surveillance is still considered to be performed within the "specified Frequency." Therefore, if the Surveillance were not performed within the

7 day interval (plus the extension allowed by TSR 3.0.2), but operation

was < 25% RTP, it would not constitute a failure of the TSR or failure to

meet the TR. Also, no violation of TSR 3.0.4 occurs when changing

MODES, even with the 7 day Frequency not met, provided operation does not exceed 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months with power 25% RTP.

Once the unit reaches 25% RTP, 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months would be allowed for

completing the Surveillance. If the Surveillance were not performed

within this 12 hour1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months interval, there would then be a failure to perform a

Surveillance within the specified Frequency and the provisions of

TSR 3.0.3 would apply.

ML100550612

Text

Navigation menu

Search