ML20236H653
| ML20236H653 | |
| Person / Time | |
|---|---|
| Site: | Byron, Braidwood  |
| Issue date: | 07/02/1998 |
| From: | COMMONWEALTH EDISON CO. |
| To: | |
| Shared Package | |
| ML20236H619 | List: |
| References | |
| NUDOCS 9807070296 | |
| Download: ML20236H653 (200) | |
Text
{{#Wiki_filter:. _ _ _ _ _ _ _ _ _ _ Definitions 1.1 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 Specifications and Bases.
< Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.
ACTUATION LOGIC TEST- An ACTUATION LOGIC TEST shall be the application of various simulated or actual input combinations in conjunction with each possible interlock logic state and the verification of the required logic output. The ACTUATION LOGIC-TEST, as a minimum, shall include a continuity check of output devices. q AXIAL FLUX DIFFERENCE AFD shall be the difference in normalized flux ig (AFD)' signals between the top and bottom halves of a two section excore neutron detector 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 inputs. The CHANNEL CALIBRATION shall encompass those components, such as sensors, alarms, displays, and trip functions, required to perform
'the specified safety function (s). 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. The CHANNEL CALIBRATION may be performed by means of any l series of sequential, overlap)1ng calibrations or ,
total channel steps so that tie entire channel is ' calibrated. 9907070296 980702 \ b PDR ADOCK 05000454'. p PDR , BYRON - UNITS 1 & 2 1.1-1 6/30/98 Revision A l
Definitions 1.1 1.1. Definitions
- 3. - CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, w ere possible. comparison of the channel
' indication and status to other indications or status derived from independent-instrument channels measuring the same parameter.
CHANNEL OPERATIONAL A COT shall be the injection of a simulated or TEST.(C0T) actual' signal into the channel as close to the L, sensor as practicable to verify OPERABILITY. '/ . including all components in the channel, such as alarms, interlocks displays, and trip' functions, required to perform the.specified safety function (s). The' COT may be performed by means of any series of sequential, overlapping or total ~ channel steps so that the entire channel is tested. 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 reactivity control components. within
. the reactor vessel with the vessel head ~ removed i and fuel in the vessel. _ Suspension of CORE I ALTERATIONS shall not. preclude completion of-movement of a component to a safe position. l 1
L CORE OPERATING LIMITS The COLR is;the unit specific document that
. REPORT (COLR). provides cycle specific 3arameter limits for the current reload cycle. T1ese cycle specific parameter limits shall be determined for each reload cycle in accordance with Specification 5.6.5. Unit operation within these limits is. addressed in individual Specifications.
i l
)
I
.3 BfRON-UNITS 1&2 1.1-2 6/30/98 Revision A '
t
Definitions
- 1.1 1.1 Definitions DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries/ gram) that alone would produce the same thyroid dose as the quantity and isotopic mixture of I-131. I-132. 1-133. 1-134."
and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in Table III of TID-14844 AEC. 1962. " Calculation of Distance Factors for Power and Test Reactor Sites."
$ - AVERAGE $ shall be the average (weighted in proportion to DISINTEGRATION ENERGY the concentration of each radionuclides in the reactor coolant at the time of sampling) of the sum of the average beta and gamma energies (irr MeV) 3er disintegration for non-iodine isotopes, with 1alf lives > 10 minutes, making up at least 95% of the total non-iodine activity in the coolant.
ENGINEERED SAFETY The ESF RESPONSE TIME shall be that time FEATURE (ESF) RESPONSE interval from when the monitored parameter TIME exceeds its ESF actuation setpoint at the channel O 8e" eor ""t41 the ese e "4pme"t 4e ceneb e or performingitssafetyyunction(i.e.,thevalves 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. O BYRON - UNITS 1 & 2 1.1-3 6/30/98 Revision A
Definitions 1.1 g
\.) 1.1 Definitions 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:
- 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) to the Secondary System;
[)
- b. Unidentified LEAKAGE All LEAKAGE (except RCP seal water injection or leakoff) that is not identified LEAKAGE: I
- c. Pressure Boundary LEAKAGE l
),
LEAKAGE (except SG LEAKAGE) through a nonisolable fault in an RCS component body, ! pipe wall, or vessel wall. MASTER RELAY TEST A MASTER RELAY TEST shall consist of energizing each master relay and verifying the OPERABILITY of each relay. The MASTER RELAY TEST shall include a continuity check of each associated slave relay. g l
'G BYRON - UNITS 1 & 2 1.1-4 6/30/98 Revision A
- i L - ___.-______________________________d
Definitions 1.1
,.~
f L 1:1 Definitions ' l 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-0PERABILITY A system, subsystem, train, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing its specified safety function (s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that I are required for the system, subsystem, train. I component, or device to perform its specified safety function (s) are also capable of performing ' their related support function (s). J PHYSICS TESTS PHYSICS TESTS shall be those tests performed to i measure the fundamental nuclear characteristics of i 7.x 4 the reactor core and related instrumentation. ! l - (J These tests are: i I
- a. Described in Chapter 14. Initial Test Program.
of the UFSAR- '
- b. Authorized under the provisions of l 10 CFR 50.59; or ;
- c. Otherwise approved by the Nuclear Regulatory Commission.
l l L L
.g.
N./! ! BYRON - UNITS 1 & 2~ 1.1-5 6/30/98 Revision A 1 L_____-_____ _ _ _ . _
jjy
~ ' ~
}
1
,, , u Definitions 1.1
, ? 4-D.. y' -:1.1 : Definitions
- PRESSURE AND EThe PTLR is the unit specific document that
- TEMPERATURE,LIMITSL provides-the reactor vessel pressure and i
-REPORT (PTLR): temperature limits including heatup and cooldown -
rates, and the pressurizer: Power Operated Relief. Valve (PORV)ilift settings for the current reactor-
. t- vessel fluence period. :These pressure 'and 10" temperature limits shall be determined for each U fluence period in-accordance with '
- o1 Specification 5.6.6; ; Unit operation within these -
g -limits ~is addressed in LC0 3.4.3 "RCS Pressure.
' and Temperature.(P/T). Limits." and LC0 3.4.12.
LH " Low Temperature Overpressure Protection-(LTOP) , ; J:( System'." w
' OUADRANT POWER' TILT OPTR shall be the' ratio of the: maximum upper sRAT10;(OPTR) excore detector, calibrated output to the average
.'of the
-or the; upper excore detector calibrated outputs.
ratio ofc the maximum lower excore detector.
. calibrated output to the average of the lower excore detector calibrated outputs. whichever is greater.
D : RATED THERMAL'POWERJ RTP shall'be a total reactor core heat transfer H 1%/' f(RTP)J:' rate to the reactor coolant of 3411 MWt.
' REACTOR-TRIP
.The:RTS RESPONSE TIME'shall be that time interval
. SYSTEM (RTS) RESPONSE from when the monitored parameter exceeds its RTS 9$ "
TIME 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
# 4j ' '
' sequential, overlapping. or. total steps so that the entire response time-is measured.
1
+
g V. J , Ny h t b
-n.' .
GQ B'YRON - UNITS [1 &' 2 ' 1;1-6 5/14/98 Revision F i i__ i
L Definitions.
, 1.1 q l
fM 1%/ L1.1' . Definitions y
-SHUTDOWN MARGIN (SDMT SDM shall be the instantaneous amount of reactivity by which the reactor is subtritical or would,be.subcritical from its present condition assuming:
- a. All Rod Cluster Control Assemblies (RCCAst 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 hot'zero power temperature.
. SLAVE RELAY TEST A SLAVE RELAY TEST shall consist of energizing each slave relay and verifying the OPERABILITY of each slave relay. The SLAVE RELAY TEST shall include.'as a minimum, a continuity check of' associated testable actuation devices.
O- STAGGERED TEST BASIS A~ STAGGERED TEST BASIS shall consist of the. 4" ~ 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. LTHERMAL' POWER THERMAL POWER shall be the total reactor core heat Y . transfer rate to the reactor coolant. u-O BYRON-ONITS'-1&2 , 1.1-7 6/30/98 Revision A
Definitions 1.1
,r3 V 1.1 Definitions TRIP' ACTUATING DEVICE A TAD 0T shall consist of operating the trip OPERATIONAL TEST actuating device and verifying OPERABILITY, (TADOT) including all components in the. channel such as alarms. interlocks. displays, and trip functions.
required to perform the specified safety function (s). The TADOT may be performed by means of any series of sequential. overlapping, or total channel steps so that the entire trip actuating device is tested. The TADOT shall include adjustment, as necessary, of the trip actuating device so that it actuates at the required setpoint within the required accuracy. 1 (<y ' t _/ 3 l i i
,r V';
BYRON - UNITS 1 & 2 1.1-8 6/30/98 Revision A _ . _ . _ _ _ _ _ _ _ _ . _ _ _ . _ _ . _ __ ___. _. _ ._.J
~
- Definitions 1.1 Table 1.1-1 (page'1 of 1) -
-l
, .7% MOD ES -
-L/ : i
% RATED AVERAGE-REACTIVITY THER L' REACTOR-COOLANT-
" ' MODE- LTITLE CONDITION POWER a; TEMPERATURE n ( k,,,) - '(*F) 9 1.. Power Operation: 2.0.99 >5 .NA
. 2. Startup:- 2 0.99 s5 NA
.l .3
. Hot. Standby- <: 0. 99 - NA- 2 350 4' Hot Shutdown (b) < 0.99 NA- 350 >' T,y > 200
.5 '- ColdSh0tdown(b) - < O. 99 ~ NA- s 200-
-6' Refueling (c) NA NA NA~
.y
-M
[/a_o$0 : r. (a)--; : Excluding decay. heat.
- l> (b),;-lAll' reactor'vesselz head closure bolts fully-tensioned.
- H ' ' ..
l @l -(c): One orimore reactor vessel head closure bolts less than fully tensioned. O r b F g .
,t 2
s ! a ll % - - x'J- - " c- ' H ; BYRON >- UNITS 11 & 2: 1.1-9 5/14/98 Revision F n :.+" , Ot2 ~ - _ _- - 1 k
y I Logical Connectors l j l ' 1.2 1.0 USE AND APPLICATION 1.2 Logical. Connectors
- j. I
- PURPOSE The purpose of this section is to explain the meaning of logical connectors.
- Logical connectors are used in Technical Specifications (TS)
.to discriminate between, and yet connect.' discrete Conditions. Required Actions. Completion Times.
Surveillance, and Frequencies The on1 logical connectors that appear in TS are AND and 08 The p sical 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
.The successive . levels of O number of the
'o24c ere 4ee"t 4eeRe1uired Action).
de ee84t4 "e' e494te or the aea"4 red 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.
EXAMPLES 'The following examples illustrate the use of logical connectors. - - 1 l l BYRON - UNITS 1-& 2 1.2-l' 6/30/98 Revision A _______m___________ _ _ _ _ _ _ _ - -
i Logical' Connectors l 1.2 i
'N -
1;2: Logical Connectors
. es, o
- b / [ ! EXAMPLES.'(continued)
- o,
- ( c- ! ' EXAMPLE 1.2-1 NCTIONS CONDITION RE0llIRED ACTION COMPLETION TIME
. A. LC0 not met. A.1 Verify _ . .
[- i 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. g () L t: f* .
' Q) _' BIRON-UNITS'1&2 1.2-2
. 5/14/98 Revision F ,
4 A .I j L_',' J
Logical Connectors 1.2-
. . 1.2; Logical Connectors.
2
- , EXAMPLES (continued)'
EXAMPLE 1;2 O fl T.g ACTIONS-CONDITION REQUIRED ACTION COMPLETION TIME A; LCO not met. A.1 Tri p . . . 1 A.2.1 Verify . . AND A.2.2.1 Reduce . .
' A.2.2.2. Perform . .
. . .- gg nQ C 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-@ and the left justified' may be' chosen.If placement. A.2:is-chosen Any then one-of boththese A.2.1 three Actions and A.2.2 must be performed as indicated by the-logical- connector /ED. 3
' 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
@ indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.
i i l
} -BYRON 1-.UNITSL1'& 2 1.2-3. 5/14/98 Revision F l
p , , u _= _.= _ __ - - - _ _ _ _ _ _ - - . _ _ _ - - - - - - - - - - - - - - - - - - - - - - - - - - - "
Completion ~ Times 1.3 i
\
(~N 1.0 USE AND APPLICATION 1.3 Completion Times l 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 f i 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 I of discovery of a situation (e.g., inoperable equipment or I 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 f3 Applicability of the LCO. Required Actions must be Uj 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 LC0 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 Recuired Actions of the Condition continue to apply to each adcitional failure, with - Completion Times based on initial entry into the Condition. BYRON - UNITS 1 & 2 1.3-1 6/30/98 Revision A d
4 j Completion Times l 1.3 1.3 Completion Times DESCRIPTION -(continued) However, when a subseauent 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 ' r b. Must remain inoperable or not within limits after the I first inoperability is resolved. The total Completion Time allowed for completing a Required ;
. Action to address the subsequent inoperability-shall be ;
.I< limited to the more restrictive of either: '
- a. The stated Completion Time. as measured from the i initial entry into the Condition, plus an additional i 24 hours: or j
. b. The stated Completion Time as measured from discovery '
_ of the subsequent inoperability. l- The above Completion Time extension does not apply to those , Specifications that have exceptions that allow completely ! se)arate re-entry into the Condition (for each train. 1 su] system, 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 ap)1y to a
- Completion Time With a modified " time zero." T11s modified
- " time zero" may be expressed as a repetitive time 1 (i.e. . "once per 8 hours." where the Completion Time is J
~ 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 i one use of this type of Completion Time. The 10 day ;
Completion Time specified for Conditions A and B in ' L Example 1.3-3 may not be extended. ! l. 1 l i 0, BYRON - UNITS 1 &L2 1.3-2' 6/30/98 Revision A L 1 c_-___-_-_ _. ____ ___ -
.s Completion Times
- 1.3 4
L1.3 Completion Times
; 3, .
l,J '
. EXAMPLES" ' The following examples illustrate the use of Completion g Times with different types of Conditions and changing-
-o Conditions.
;y.
'o .
- Q j EXAMPLE 1.3-1.
@. - ACTIONS
( . CONDITION REQUIRED ACTION COMPLETION TIME M B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time not-- B.2 Be in MODE 5, 36 hours met.
-p
.V ~ Condition B has'two Required Actions.' Each Required Action has its own separate Completion Time. Each Completion Time
~i s referenced to the time that Condition B is entered.
The Required Actions of Condition B are to be in MODE 3 within 6 hours AND in MODE 5 within 36 hours. A total of 4 m 6 hours is' allowed for reaching MODE 3 and.a total of 36 hours-(not 42 hours) is allowed for reaching MODE 5 from the time:that' Condition B was entered. If MODE 3 is reached within.3 hours.;the time allowed for reaching MODE'S is the next 33 hours because the total time allowed for reaching . MODE 5 is 36 hours. If Condition,B is' entered while in MODE 3. the time allowed for reaching MODE 5 is the next'36 hours.
;... x.
[ y-{ l BYRON ~~ UNITS 1 & 2' 1.3-3 5/14/98 Revision F _,[_m_ _ _ _ _ _ _ _ _ . . _ _ _ -_ - - -- - - ' " - " - ' - - - - - " - - - " - - - " - ' - - - - -
Completion Times 1.3 1.3 Completion Times OeJ EXAMPLES (continued) o l EXAMPLE 1.3-2 y -ACTIONS E CONDITION REQUIRED ACTION COMPLETION TIME A. One pum) A.1 Restore pump to 7 days inoperaale. OPERABLE status. B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. Q When a pump is declared inoperabie. Condition A is entered. If the 7 days. Condition pump is not B isrestored to OPERABLE also entered status within 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 ino the second pump.LCO perable. Condition A is not re-entered for 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 LCO 3.0.3 is entered. but continues to be tracked from the time Condition A was initially entered. While in LCO 3.0.3. if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired. LCO 3.0.3 may be exited and operatien~ continued in accordance with Condition A. O BYRON - UNITS 1 & 2 1.3-4
, 5/14/96 Revision F
Completion Times
.1.3 1.3 Completion Times EXAMPLES (continued)
While in LC0 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Com)letion Time for Condition A has expired. LCO 3.0.3 may Je 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. 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 Com)letion Time may be extended if the pump restored to OPEMBLE status was the first inoperable pump. A 24 hour extension to the stated 7 days is allowed provided this does not result in the second pump being inoperable for
> 7 days. .!O V
l l l BYRON - UNITS 1 & 2 1.3-5 6/30/98 Revision A
~
~
Completion Times 1.3 a
.- >1.3' Comoletion Times--
~
LpgV .f EXAMPLES $ (continuedt 3p
- EXAMPL E: 113-3'.-
H' { ' ACTIONS'
. CONDITION REQUIRED ACTION COMPLETION TIME A'. One -.
'A.1 Restore 7 days Function X Function X train train.. to OPERABLE- AND-inoperable. . status.
10 days _from-discovery of failure to meet the LCO B. One B.1' Restore 72 hours Function ~Y -Function Y train train - to OPERABLE. AND inoperable. -status. D',% ' 10 days from
' discovery of-failure to meet-the LC0' r
' v' ~ ~ C. One' - C.1 -Restore . 72 hou'rs Function X Function X-train L . train- to OPERABLE-l . inoperable. status.
~AND QB l_ .
One C.2 Restore 72 hours Function Y- Function Y train train to OPERABLE
- ,, _ inoperable. status'.
l r:
;t
~ BYRON,- UNITS'l'&'2 1.3-6 5/14/98 Revision F 1
s j m__-i____:_[_-____.
- __ i _ _ _1__-_ _ _________._____ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ . _ _ _ __ _ _ _ _ _ . _ . - _ _ _ . _ _ _ _ _ _ _ _ _ _ _ . _ _
I Completion Times ) 1.3 1.3 Completion Times J EXAMPLES (continued) When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Com31etion Times for Condition A and Condition B are tracced 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 LCO was not met. In this exam le, without the separate Completion Time. O V' it would be aossib e to alternate between Conditions A. B. and C in suc1 a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LC0" is designed to preve1t ! indefinite continued operation while not meeting the LCO. . ' 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 LCO was initially not met. ) instead of at the time the associated Ccndition was entered. ! ( - BYRON - UNITS 1 & 2 , 1.3-7 6/30/98 Revision A ____________m-________
[1 Completion Times 1.3 . 1.3: Completion Times l 7
- EXAMPLES -(continued).
fl EXAMPLE-1.'3-4
-[ ACTIONS CONDITION . REQUIRED ACTION COMPLETION TIME A. . One or more A.1 Restore valve (s) 4 hours valves to OPERABLE inoperable. status, fk B. Required . B.1 Be in MODE 3. 6 hours Action and
' associated AND Completion j ' Time not- B.2 Be in MODE.4. 12 hours
' met.
i-
. O'
A single Completion Time is used for any number of valves
.inoaerable at the same time. The Completion Time associated wit 1 Condition A is-basea 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, f
.0nce one of the valves h'as 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 l Com)letion 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 hours provided this does not result in any subsequent valve being inoperable-for > 4 hours.
L 'If the Completion Time of 4 hours (plus the extension) L, -i- expires while one or more valves are still inoperable. l Condition B is entered. t l-c ( -BYRON - UNITS 1 &'2 1.3-8 5/14/98 Revision F y. L-EL _ _ _ _ _ - - - - - _ - - - _ - - - - - - - - - - - - - - - - - -
Completion' Times 1.3 1.3 Completion Times O p' EXAMPLES (continued)
$l ,
EXAMPLE 1.3-5 l ACTIONS NOTE Separate Condition entry is allowed for each inoperable valve.
! CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours ~
valves OPERABLE status. inoperable. B. Required B.1 Be in MODE 3. 6 hours Action and associated AND O comp,etioa Time not B.2 Be in MODE 4. 12 hours met. 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. O BYRON - UNITS 1 & 2 1.3-9 5/14/98 Revision F
4 Completion Times , 13 ' 1 1.3 Completion Times (G.) EXAMPLES c(continuedV 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
. Leach valve and separate Completion Times start and are tracked for e6ch valve. If a valve that caused-entry into-
' Condition B is restored to OPERABLE status, Condition B is T . exited for that valve.
- Since the Note in this example allows multiple Condition entry and tracking of. separate Completion Times. Completion
-* Time extensions.do.not apply, i ,
3l EXAMPLE 1.3-6'
' H-
-{ . ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME
. - A; One channel 'A.1- Perform Once per-inoperable. SR 3.x.x.x, 8 hours 2-A'.2 . Reduce THERMAL 8 hours POWER to
.s 50% RTP. _
~
' B' . Requi red B.1 Be in MODE 3. 6 hours
~
Action and associated Completion <li Time not-met. II L
.G V ~'
' BYRON - UNITS 1 & 2! 1.3-10 5/14/98 Revision F h .
\
E. .., . . . . . _ _ _ _ _ _ _ _ _ ._ -J
Completion Times 1.3 [~'y 1.3 Completion Times v EXAMPLES (continued)' 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 SR 3.0.2. to each performance after the initial performance. The initial 8 hour 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 hour interval. If Required Action A.1 is followed, and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.2). Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours is not met Conditior, B is entered. If after entry into Cordition B. Required Action A.1 or A.2 is met Condition B is exited and operation may then continue in Condition A. O ('T U BYRON - UNITS 1 & 2 1,3-11 6/30/98 Revision A _ _ _ _ _ _ - - _ _ _ _ - - - _ _ l
Completion Times 1.3 , i 1.3 Completion Times p EXAMPLES (continued) o- l a EXAMPLE 1.3-7
.y ACTIONS-CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Verify affected 1 hour subsystem subsystem inoperable. isolated. AND Once per 8 hours thereafter AND A.2 Restore subsystem 72 hours to OPERABLE status.
8 B. Required Action and B.1 Be in MODE 3. 6 hours associated AND Completion Time not B.2 Be in MODE 5, 36 hours met. Required Action A.1 has two Completion Times. The 1 hour Completion Time begins at the time the Condition is entered and each "Once 3er 8 hours thereafter" interval begins upon performance of Required Action A.I. 8 BYRON - UNITS 1 & 2 1.3-12 5/14/98 Revision F i t-
Completion Times 1.3 1.3 Completion Times ( EXAMPLES (continued) If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour or any subsequent 8 hour interval from the previous performance (plus the extension al-lowed by SR 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. i provided the Completion Time for Required Action A.2 has not l expired. l l IMMEDIATE When "Immediately" is used as a Completion Time, the l COMPLETION TIME Required Action should be pursued without delay and in a controlled manner. i l i i l l 1 i O V I BYRON - UNITS 1 & 2 1.3-13 6/30/98 Revision A
Frequency 1.4 1 1.0 USE AND APPLICATION (O~'T 1.4 Frequency l PURPOSE The purpose of this section is to define the proper use and j application of Frequency requirements. j DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequer.cy in which the Surveillance must be met in ord:r to meet the associated Limiting Condition for Operation (LCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the SR. The "specified Frequency" is referred to throughout this , section and each of the Specifications of Section 3.0. - l Surveillance Requirement (SR) Applicability. The "specified l Frequency" consists of the requirements of the Frequency l column of each SR as well as certain Notes in the I Surveillance column that modify performance requirements. ; Situations where a Surveillance could be required (i .e. , its l Frequency could expire), but where it is not possible or not ' desired that it be performed until sometime after the (o') associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts the SR (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 SR satisfied. SR 3.0.4 imposes no restriction. EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1. 2. ' and 3. (g)' BYRON - UNITS 1 & 2 1.4-1 6/30/98 Revision A 4
[ Frequency 1.4
<f.A):. 1.4 : FrequencyL t v .% -
L I -EXAMPLES (continued) @ 'O:. ' Q . EXAMPLE 1.4-1 R H . <c . SURVEILLANCE REQUIREMENTS e SURVEILLANCE FREQUENCY: Perform CHANNEL CHECK. 12. hours
, . Exam)1e 1.4-1 contains the type of'SR most ofte'n encountered
'in tie Technical Specifications (TS). The Frequency.
specifies an interval (12 hours)-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 hours, an .Ih ' extension of the time' interval to. l.25 times.the stated Frequency is allowed by.SR 3.0.2 for operational' flexibility. The' measurement of this interval continues at w all times; even when the SR is' not required to be met per
/
L)- ' SR 3.0.1. (such as when the ecuipment is inoperable, a variable ~is outside specifiec limits, or the unit is outsida the Applicability'of the LCO), . If'the interval specif;ea by SR 3.0.2 is exceeded while the unit is in a MODE or other- 'l specified conditior. in the Applicability of the LCO, and the o performance of the surveillance is not otherwise modified (refer to Example l'4-3), then SR 3.0.3 becomes applicable. If the ; interval as specified by SR 3.0.2.1s. exceeded while the unit is not in a MODE.or.other specified condition in the Applicability of the LCO for which perf.ormance of the SR is required..the Surveillance must be performed within the
, Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would
.' result in a violation of SR 3.0.4.
l 1.' l
- i i
l "0 BYRON - UNITS 1 &'2 1.4 5/14/98 Revision F l
Frequency 1:4
/ h)
O'i 1,4- Frequency g EXAMPLESE(continued) o
;fl EXAMPLE 1.4-2 H SURVEILLANCE REQUIREMENTS
' SURVEILLANCE FREQUENCY' Verify flow is within limits. Once within 12 hours after
= 25% RTP
~AND j s 24 hours
,:7 thereafter I
a Example 1.4-2 has two Frequencies. -The first is a one time performance Frequency, anc the second is of the type shown-
.in Example 1.4-1. . The logical connector."AND" indicates )
fv') ~ _.that both Frequency requirements must be met. Each time reactor power is increased from a-power level < 25% RTP to' l 2 25%'RTP. the Surveillance must-be performed within i 12 hours. i 7 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-SR 3.0.2 "Thereafter" indicates future performances must be.
established per SR 3.0.2. but'only' after a specified ; condition is first met (1.e.. the "once" performance in this example). If' reactor power decreases to < 25% RTP. the measurement of both intervals stops. New intervals start ' L , upon reactor power reaching 25% RTP. ' a J g- 'l r , j L ) 0 -1.4-3 iBYRONf-UNITS.1l&'2 5/14/98 Revision F 4 s
Frequency 1.4 d )s - ,1.41 Frequency L 'g o , EXAMPLES (continuedh
=l.. EXAMPLE 1.4-3
'H' -
4 SURVEILLANCE RE0'UIREMENTS- l i SURVEILLANCE d FREQUENCY. NOTE Not required.to be performed until 12 hours after a 25% RTP. i
. -Perform channel adjustment. 7 days U 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 A}.= operation is < 25% RTP. this. Note allows 12 hours after !
. power reaches.= 25% RTP to perform the Surveillance. 'The l
' Surveillance is:still considered to be 3erformed within the !
. f+ l " '"specified Frequency." Therefore. if t1e Surveillance were i C - om i ' not?)erformed within the 7 day- (plus the extension' allowed.
by 51 3.0.2r interval, but operation was < 25% RTP it would not constitute a. failure of the.SR or failure to meet the
+ 1.. .LCO. ' Also, no violation of SR 3.0.4 occurs when changing =1
. MODES.'even with the 7 day Frequency not met, provided.
.H ,
operation'does not exceed 12 hours with power-a 25% RTP. _.N l Once the unit- reaches' 25% RTP.12' hours would be allowed for !
.~y l. completing the Surveillance. If the Surveillance were not performed within this 12 hour interval, there would then be a failure to perform a Surveillance within the specified i Frequency,' and the provisions of SR 3.0.3 would apply.
1 i L j u j
-BYRON - UNITS 1 &~2-1.4-4 5/14/98 Revision F
Frequency 1.4
. ,m
[ p T1.'4 Frequency 90 - EXAMPLES: (continued): 0-^
-;l EXAMPLE 1.4-4 H-T. , ' ' SURVEILLANCE REQUIREMENTS-SURVEILLANCE FREQUENCY.
NOTE Only required to be performed in MODE 1. , Perform complete cycle of the valve. 7 days i The interval continues, whether or not the unit operation is in MODE 1. 2. or 3 (the assumed Applicability of the associated LCO) between performances. ; As-the Note modifies the required performance of the ] Surveillance. the note.is construed to be part of the
!mL j- "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE-1. this Note allows entry into.and o)eration in MODES 2 and 3 to perform the Surveillance. T1e Surveillance is still considered to be performed within the "specified. Frequency" if completed
- lL prior to MODE l'... Therefore, if the. Surveillance were not performed within the 7 day.(plus the extension allowed by SR 3.0.2). interval, but' operation was not in MODE-1. it
.a would not constitute a failure of the SR or. failure to' meet o .. the LCO. Also, no violation of SR 3.0.4 occurs'when
.i changing MODES, even with the 7 day Frequency not' met.-
o: provided operation does not result,in. entry.into MODE 1. Once the unit reaches MODE 1. the' requirement for the
$.. Surveillance to be performed within its specified Frequency.
t Y. applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to
\l MODE 1. there would then be a failure to perform a
\t . Surveillance within the specified Frequency, and the
; provisions of SR 3.0;3 would apply l
1 0 1.4-5 BYRON - UNITS 1-& 2- 5/14/98 Revision F 'm u..
Definitions 1.1
- 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 Specifications and Bases. Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times. ACTUATION LOGIC TEST An ACTUATION LOGIC TEST shall be the application of various simulated or actual input combinations in conjunction with each possible interlock logic state and the verification of the required logic output. The ACTUATION LOGIC TEST, as a minimum, shall include a continuity check of output devices.
- AXIAL FLUX DIFFERENCE AFD shall be the difference in normalized flux
! (AFD) signals between the top and bottom halves of a U two section excore neutron detector. 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 inputs. The CHANNEL CALIBRATION shall encompass those components such as sensors, alarms, displays, and trip functions. required to perform the specified safety function (s) Calibration of instrument channels with Resistance Temperature Detector (RTD) or thermocouple sensors may consist of an inplace qualitative a:sessment of sensor behavior and normal calibration of the remaining adjustable devices in the channel. The CHANNEL CALIBRATION may be performed by means of any series of seguential, overlapping calibrations or total channel steps so that t1e entire channel is calibrated. BRAIDWOOD - UNITS 1 & 2 1.1-1 6/30/98 Revision A
~
I' Definitions 1.1
'1' 1~ Definitions CHANNEL CHECK A CHANNEL CHECK shall be the.. qualitative i assessment, by observation, of channel behavior i 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.
; CHANNEL OPERATIONAL A COT shall- be the injection of a simulated or
' TEST (C0T) actual signal into the channel as close to the j sensor as practicable to verify OPERABILITY, including all components in the channel. such as alarms, interlocks. displays, and trip functions.
required to perform the specified safety function (s). The COT may be performed by means of any series of sequential, overlapping or total ; channel steps so that the entire channel'is ' tested. The COT shall include adjustments, as ; necessary, of the required alarm. interlock, and i trip setpoints so that the setpoints are within ! the required range and accuracy. - t O CORE ALTERATION CORE ALTERATION shall be the movement of any fuel, sources, or reactivity control components. within the reactor vessel.with.the vessel head removed 4 and fuel in the vessel. Suspension of CORE ! ALTERATIONS'shall not preclude completion of movement of a component to a safe position. -
-CORE OPERATING LIMITS The COLR is the unit specific document that
; REPORT _'(COLR)' provides cycle specific 3arameter limits for the .
current reload cycle. T1ese cycle specific I parameter limits shall be determined for each l reload cycle in accordance with Specification 5.6.5. Unit operation within these limits is addressed in individual Specifications. 1 L BRAIDWOOD - UNITS 1 & 2 1.1-2 6/30/98 Revision A , e i 1________________i-_-_____.-_-___--___.-------- _ - - - - - - - -- -- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - ~ ~ - - - - - - '
, Definitions l 1.1 j ,, 1 \ V 1.1 Definitions DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries/ gram) that alone would produce the same thyroid dose as the quantity and isotopic mixture of I-131, I-132,1-133. I-134. and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in Table III of TID-14844, AEC.1962, " Calculation of Distance Factors for Power and Test Reactor Sites." E - AVERAGE $ shall be the average (weighted in proportion to DISINTEGRATION ENERGY the concentration of each radionuclides in the reactor coolant at the time of sampling) of the sum of the average beta and gamma energies (in MeV) 3er disintegration for non-iodine isotopes, with 1alf lives > 10 minutes, making up at least 95% of the total non-iodine activity in the coolant. ' ENGINEERED SAFETY The ESF RESPONSE TIME shall be that time j FEATURE (ESF) RESPONSE interval from when the monitored parameter j e TIME exceeds its ESF actuation setpoint at the channel (m ! V
)
sensor until the ESF equipment is capable of I 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. v BRAIDWOOD - UNITS 1 & 2 , 1.1-3 6/30/98 Revision A
Definitions i 1.1 1;l Definitions LEAKAGE LEAKAGE shall be:
- a. Identified LEAKAGE
- 1. LEAKAGE, such as that from pump ecais or valve' packing (except Reactar Coolant Hmp (RCP) seal water injection or leako f).
.that is captured and conducted to collection. systems or a sump or. collecting tank:
.2. LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere o 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) 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 LEAKAGE) through a nonisolable fault. in an RCS. component body, pipe wall, or vessel wall.
MASTER RELAY TEST A MASTER RELAY TEST shall consist of energizing " each master relay and verifying the OPERABILITY of each relay. The MASTER RELAY TEST shall include a continuity check of each associated slave relay. BRAIDWOOD - UNITS 1.& 2 1.1-4 6/30/98 Revision A
,q ..
9 Definitions 1.1 1,1. Definitions
> MODE A MODE shall correspond to any one inclusive combination of core reactivi_ty 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.
0PERABLE-0PERABILITY A system, subsystem, train, com)onent, or device, shall be OPERABLE or have' OPERA 31LITY when it is capable of performing its specified safety 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 perform'ing their related support function (s). PHYSICS TESTS
~
PHYSICS TESTS shall be those tests performed to measure the fundamental nuclear characteristics of n( the reactor core and related instrumentation, These' tests'are:
- a. Described in Chapter 14. Initial Test Program.
-of the UFSAR:
- b. Authorized under the provisions of 10 CFR 50.59: or-c, .0therwise approved by the Nuclear Regulatory
-Commission.
O '
'BRAkDWOOD'-UNITS'l&2 1.1-5 6/30/98 Revision A e,
h vi Definitions 1.1 L[) i/ s1.1. . Definitions; y LPRESSUREAND .
' The PTLR is the unit specific document' that TEMPERATURE LIMITS- ~
REPORT 1(PTLR). ;provides temperature thelimits reactor vesselheatup including pressure andand cooldown L ' rates..and the pressurizer Power Operated Relief Valve.(PORV) lift settings for.the current reactor-- vessel fluence period. These pressure and N- temperature limits shall be determined for each 0 fluence period in accordance with j Specification 5.6.6, Unit- operation within these N. .- limits-is addressed in LCO 3.4.3. "RCS Pressure y and Temperature-(P/.T) Limits." and LCO 3.4.12. m " Low Tem
- t . System."perature Overpressure Protection (LTOP) l l0VADRANT POWER TILT QPTR shail be. the ratio of the maximum upper RATIO.(OPTR) excore detector calibrated output to the average Lof the. upper excore detector calibrated outputs.
or the ratio of the maximum lower excore detector calibrated output to the average of th'e lower
.excore detector calibrated outputs, whichever is greater.
; RATED THERMAL POWER .
5A RTP shall be a total reactor. core heat transfer L 1(RTP)) rate-to the' reactor coolant.of 3411 MWt.
. REACTOR TRIPc .
The'RTS RESPONSE. TIME shall be that time interval SYSTEM (RTS) RESPONSE from when the monitored parameter exceeds its RTS TIME: trip setpoint at.the channeT 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. [' ' h$ L
- .BRAIDWOOD~-IUNITS lt& 2L .1.1-6 5/14/98 Revision F e
c) f
Definitions' 1.1
~!b v 1.1 Definitions .
SHUTDOWN MARGIN-(SDM) SDM shall be the instantaneous amount of reactivity by which the reactor is subtritical 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 hot zero power temperature. SLAVE RELAY TEST A SLAVE RELAY TEST shall consist of energizing each slave relay and verifying the OPERABILITY of each slave relay. The SLAVE RELAY TEST shall include, as a minimum, a continuity check of associated testable actuation devices. 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.
THERtiAL POWER- . THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant. O' ^ l BRAIDWOOD UNITS 1 & 2 1.1-7 6/30/98 Revision A
'a f
i Definitions 1.1 , - () _ V 1.1 Definitions i TRIP ACTUATING DEVICE A TADOT shall consist of operating the trip ! OPERATIONAL TEST actuating device and verifying OPERABILITY, l- (TADOT) including all components in the channel such as alarms, interlocks, displays, and trip functions. ' ~ required to perform the specified safety function (s). The TADOT may be performed by means of any series of sequential, overlapping or total channel steps so that the entire trip actuating ! device is tested. The TADOT shall include adjustment as necessary, of the trip actuating i ' device so that it actuates at the required setpoint within the required accuracy. l (3 () BRAIDWOOD - UNITS 1 & 2 1.1-8 6/30/98 Revision A l w____-_._-
^ Definitions 1.1 l i
^V
/[ '
Table 1.1-1 (page 1 of 1) MODES
. % RATED AVERAGE REACTIVITY THE L , REACTOR COOLANT MODE TITLE- CONDITION POWER al TEMPERATURE .
(kW) ( F) l Power Operation = 0,99 > 5- NA-2.. .Startup-. m.0.99 s5. NA 3: Hot Standby- < 0.99 NA = 350 4 ' Hot Shutdown (b) . < 0.99 NA- 350 > T,,, > 200 -
.5- Cold Shutdown (b) < 0.99 NA- s 200-Refueling (c) NA NA NA-3 L.(D
- u. v rp (a) tExcluding decay' heat, -
]9 l}(b) All reactor' vessel head closure bolts fully tensioned.
L, :d y (c)1.0ne or:.more reactor vessel head closure. bolts less than fully tensioned'.
. tc '
l d H 4
]
l.
- i. )
i p I h UNITS 1 & 2: '1.1-9 BRAIDWOOD. '5/14/98 Revision F h I~ t 1 U :. . . ..
. . _ _ _ - _ _ - - . - - - . -. '___:----------------.--.0
Logical Connectors 1.2
, 1.0 USE AND APPLICATION L
1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors. Logical connectors are used in Technical Specifications (TS) to discriminate between, and yet connect, discrete Conditions. Required Actions. Completion Times. Surveillance, and Frequencies. The only logical connectors that appear in TS are AND and QR. 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 (mj v 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. EXAMPLES- The following examples illustrate the use of logical connectors. p) ( BRAIDWOOD - UNITS 1 & 2 1.2-1 6/30/98 Revision A
! l f Logical Connectors j 1.2 i
'1.2 Logical Connectors N EXAMPLES (continued) l 0
l
$l e
EXAMPLE 1.2-1 H ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME ' i A. LC0 not met. A.1 Verify . l i AND I l A.2 Restore . . { I { 4 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 cor.:oleted. G I i
.I h
F l f 0 BRAIDWOOD - UNITS 1 & 2 , 1.2-2 5/14/98 Revision F
Logical Connectors 1.2 1.2 Logical Connectors N EXAMPLES (continued) I C
. l EXAMPLE 1.2-2 H ACTIONS
- t. CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Trip .
E d A.2.1 Verify , AND A.2.2.1 Reduce . 4 2 A.2.2.2 Perform .
,m %
\ )
A.3 Align . l 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 aerformed as indicated by the use of the logical connector 01 and the left justified Any one of these three Actions may be chosen.Ifplacement. 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 2 indicates that A.2.2.1 and A.2.2.2 are alternative choices. only one of which must be performed. L L-t- 0 BRAIDWOOD - UNITS 1 & 2 1.2-3 S/14/98 Revision F I L____..__.____._..__.__ .._. - ._ . . _ _ -._ - - - - - - - - - "
Completion Times 13 I I O 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. T
' BACKGROUND Limiting Conditions'for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit-. The u
. 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).
- .W 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 1 ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the J p Applicability of the LCO. 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 theLunit is not within the LC0 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 l L specifically stated. The Recuired Actions of the Condition I L L continue to apply to each adcitional failure, with j Completion Times based on initial entry into the Condition. '
. . -Lf,
- f. BRAIDWOOD . UNITS 1 & 2 1.3-1 6/30/98 Revision A v
i- !
4 Completion Times 1.3 1.3.. Completion Times DESCRIPTION (continued) However, when a subseauent 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 L first inoperability is resolved.
L 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 extension does not apply to those Specifications that have exceptions that allow completely
'se)arate re-entry into the Condition (for each train.
. su) system, 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 ap)ly to a~ Completion Time with a modified " time zero." T11s modit;ed
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 . . ." Example 1.3-3 illustrates i one use of this type of Completion Time. The 10 day '
Comption Time specified for Conditions A and B in g Example 1.3-3 may not be extended. l l O BRAIDWOOD - UNITS 1 & E 1.3-2 6/30/98 Revision A I i _i__._____.___._____:___.__--_---
Completion Times 1.3
- 1. 3 Completion Times EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing !
g Conditions. O ol EXAMPLE 1.3-1 H ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required B.1 Be in MODE 3. 6 hours Action and ' associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. I p 'u' 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 hours AND in MODE 5 within 36 hours. A total of 6 hours is allowed for reaching MODE 3 and a total of ; 36 hours (not 42 hours) is allowed for reaching MODE 5 from I the time that Condition B was entered. If MODE 3 is reached within 3 hours, the time allowed for reaching MODE 5 is the next 33 hours because the total time allowed for reaching MODE 5 is 36 hours. If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours.
~
O BRAIDWOOD - UNITS 1 & 2 1.3-3 5/14/98 Revision F
Completion Times 1.3
' 1. 3 Completion Times 7 EXAMPLES (continued)
O 4 j EXAMPLE 1.3-2 H { ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump A.1 Restore pump to 7 days inoperable. OPERABLE status. B. Required B.1 Be in MODE 3. 6 hours _ Action and associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. m ( ) 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 also 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 i therefore..the Required Actions of Condition B may be terminated. When a second pump is declared inoperable while the first l pump is still inoperable. Condition A is not're-entered for ' the second pump. LCO 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 LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered. While in LCO 3.0.3, if one of the 'noperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LC0 3.0.3 may be exited and operation continued in accordance with Condition A. ' O BRAIDWOOD - UNITS 1 & 2 1.3-4 5/14/98 Revision F u.- __ . _ . . _ _ _ _ . _ _. _ . _ . _ . . . m. _ _ _ _ _ . . . _ _ _ . _
! l l Completion Times 1.3 l 1.3 Completion Times l EXAMPLES (continued) l While in LCO 3.0.3. if one of the inoperable pumps is restored to OPERABLE status and the Com)letion Time for Condition A has expired. LCO 3.0.3 may 3e 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. On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from i the time the first pump wcs declared inoperable. This ! Com]letion Time may be extended if the pump restored to ! l OPEMBLE status was the first inoperable pump. A 24 hour j l extension to the stated 7 days is allowed provided this i does not result in the second pump being inoperable for
> 7 days.
, i l 10 i U l i i l l l'
- () ,
BRAIDWOOD - UNITS 1 & 2 1.3-5 6/30/98 Revision A
l Completion Times ! 1.3 ! 1.3 Completion Times j EXAMPLES (continued) yl EXAMPLE 1.3-3 ' ( t ACTIONS i
, CONDITION REQUIRED ACTION COMPLETION TIME I
A. One A.1 Restore 7 days Function X Function X train ' train to OPERABLE AND inoperable. status. 10 days from l discovery of ' failure to meet the LC0 i B. One B.1 Restore 72 hear s Function Y Function Y train ; train to OPERABLE AND !
, -m inoperable, status.
( ), 10 days from l discovery of ! failure to meet i the LCO j i C. One C.1 Restore 72 hours l Function X Function X train train to OPERABLE l inoperable. status. ! AND QR One C.2 Restore 72 hours Function Y Function Y train train to OPERABLE incperable. status. i 0 BRAIDWOOD - UNITS 1 & 2 1.3-6 5/14/98 Revision F
Completion Times 1.3 1.3 Completion Times EXAMPLES (continued) When one Function X train and one function Y train are inoperable. Condition A and Condition B are concurrently applicable. The Com)letion Times for Condition A and Condition B are tracted 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 LCO was not met. In this example, without the separate Completion Time, O it would be Jossible to alternate between Conditions A. B. and C in suc1 a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. The separate Completion Time modified by the phrase "from discovery of failure to meet the LC0" is designed to prevent indefinite continued operation while not meeting the LCO. 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 LCO was initially not met.
instead of at the time the associated Condition was entered. O BRAIDWOOD - UNITS 1 & 2 1.3-7 6/30/98 Revision A
Completion Times 1.3 1.3 Completion Times 04 o 1 EXAMPLES (coritinued) 0 l EXAMPLE 1.3-4 ACTIONS h CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve (s) 4 hours-valves to OPERABLE inoperable. status. B. . Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion cTime not B.2 Be in MODE 4. 12 hours met. A single Completion Time is used for any number of valves ino)erable at the same time. The Completion Time associated wit 1 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 Com)letion Time may be extended if the valve restored to OPEMBLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours provided this does not result in any subsequent valve being inoperable for > 4 hours. If the Completion Time of 4 hours (plus the extension) expires while one or more valves are still inoperable.
- Condition B is entered.
i
! /
BRAIDWOOD - UNITS 1 & 2 1.3-8 5/14/98 Revision F I L
l Completion Times 1.3 1.3 Completion Times l 9g EXAMPLES (continued) o l 4l EXAMPL E - 1. 3-5 h ACTIONS T NOTE Separate Condition entry is allowed for each inoperable valve.
. CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours valves OPERABLE status.
inoperable. B. Required B.1 Be in MODE 3. 6 hours Action and associated 4 AND Completion Time not B.2 Be in MODE 4. 12 aours met. 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. l 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 l entered for each valve and separate Completion Times start i and are tracked for each valve.
~
(3 U BRAIDWOOD - UNITS 1 & 2 , 1.3-9 5/14/98 Revision F
-------------_-_-------___-------J
Completion Times 1.3 1.3 Completion Times EXAMPLES (continued) 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. N Since the Note in this example allows multiple Condition o entry and tracking of separate Completion Times. Completion 8 Time extensions do not apply. 0 Hl EXAMPLE 1.3-6 T ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One channel A.1 Perform Once per inoperable. SR 3.x.x.x. 8 hours 2 A.2 Reduce THERMAL 8 hours POWER to-5 50% RTP. B. Required 8.1 Be in MODE 3. 6 hours Action and associated Completion Time not met. BRAIDWOOD - UNITS 1 & 2 1.3-10 5/14/98 Revision F
Completion Times 1.3
,(~') 1.3 Completion Times %)
EXAMPLES (continued) 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 SR 3.0.2, to each performance after the initial performance.
~ The initial 8 hour 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 hour interval. If Required Action A.1 is followed, and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.2). Condition B is entered.
If Required Action A.2 is followed and the Completion Time of 8 hours 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. A V n LJ l BRAIDWD00 - UNITS 1 & 2 1.3-11 6/30/98 Revision A
Completion Times 1.3 1.3 Completion Times 0yf EXAMPLES (continued) c 4 EXAMPLE 1.3-7 Nl { ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Verify affected I hour subsystem subsystem inoperable. isolated. AND Once per 8 hours thereafter AND A.2 Restore subsystem 72 hours to OPERABLE status. 4 B. Required Action and B.1 Be in MODE 3. 6 hours associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. Required Action A.1 has two Completion Times. The 1 hour Completion Time begins at the time the Condition is entered and each "Once per 8 hours thereafter" interval begins upon l performance of Required Action A.1. l l i 9 BRAIDWOOD - UNITS 1 & 2 1.3-12 5/14/98 Revision F I i
Completion Times 1.3 1.3 Completion Times ( EXAMPLES (continued) If after Condition A is entered. Required Action A.1 is not met within either the initial I hour or any subsequent 8 hour interval from the previous performance (plus the extension allowed by SR 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 When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner. I; i l l 4 r l b) BRAIDWOOD - UNITS 1 & 2 1.3-13 6/30/98 Revision A 1
Frequency 1.4 l i (~) V 1.0 USE A@ APPLICATION i i 1.4 Frequency l PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements. l l 4 DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency 1 in which the Surveillance must be met in order to meet the ' associated Limiting Condition for Operation (LCO). An understanding of the correct application of the specified Frequency is necessary for compliance with the SR The "specified Frequency" is referred to throughout this I section and each of the Specifications of Section 3.0, Surveillance Requirement (SR) Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR 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 i' o, desired that it be performed until sometime after the
'Q associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the ;
SR (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 SR satisfied. SR 3.0.4 imposes no l restriction. ' l EXAMPLES The following examples illustrate the various ways that i Frequencies are specified. In these examples, the ; Applicability of the LCO (LCO not shown) is MODES 1. 2. : and 3. j p BRAIDWOOD - UNITS 1 & 2 1.4-1 6/30/98 Revisica A L_____ - _ -
Frequency [ 1.4 4 1,4 Frequency 8 ? O EXAMPLES (continued) 4 l EXAMPLE 1.4-1 N' y SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Exam)le 1.4-1 contains the type of SR most often encountered in t1e Technical Specifications (TS). The Frequency - specifies an interval (12 hours) 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 hours. an extension of the time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per 6 SR 3.0.1 (such as when the ecuipment is inoperable, a variable is outside specifiec limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO. and the performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then SR 3.0.3 becomes applicable. If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LC0 for which performance of the SR is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of SR 3.0.4. 9 BRAIDWOOD - UNITS 1 & 2 1.4-2 5/14/98 Revision F h..
1 Frequency 1.4 . i 1.4 Frequency ef EXAMPLES (continued) 3l W EXAMPLE 1.4-2 { SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits. Once within 12 hours after a 25% RTP AND 24 hours thereafter Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, anc the second is of the type shown-in Example 1.4-1. The logical connector "AND" indicates 4 that both Frequency requirements must be met. Each time reactor power is increased from a power level < 25% RTP to a 25% RTP. the Surveillance must be performed within 12 hours. 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 SR 3.0.2.
"Thereafter" indicates future performances must be established per SR 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% P.TP. the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.
t _f BRAIDWOOD - UNITS 1 & 2 1.4-3 5/14/98 Revision F
y' Frequency. 1.4
. -s 1'.4~ Frequency-qg ' EXAMPLES (continued)'
h'I a EXAMPLE 1:4-3
;'g SURVEILLANCE. REQUIREMENTS t .
SURVEILLANCE ~ FREQUENCY NOTE--
.Not required to be performed until 12 hours'after 2.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 thel
-D- Surveillance, it is construed.to be part of the' "specified-V ' Frequency." Should the 7 day interval be exceeded while operation:is < 25% RTP. this Note allows 12 hours after-
. power reaches a 25% RTP to perform the Surveillance.. The.
Surveillance.is still. considered'to be 3erformed within the dj.. ~"specified Frequency." Therefore. if t1e Surveillance were-a ;not performed within the 7 day (plus the extension allowed
'O by -SR 3.0.2)L interval, but operation was < 25% RTP, it would not. constitute a failure of'the SR or failure to meet the
? ' LCO .' Also,'no violation of SR 3.0.4 occurs when changi
~. MODES; even with the 7 day Frequency not met, provided.ng operation-does not exceed 12 hours with power a 25% RTP.
~
' Once the unit reaches 25% RTP,12 hours would be allowed for
. t.c( l - completing the-Surveillance. If the Surveillance were not performed-within this 12 hour interval, there would then be a failure.to perform.a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.
L .. L: iBRAIDWOOD -. UNITS.1 & 2 1.4-4 5/14/98 Revision F l i ) - _ - .-
Frequency 1.4 Oa 1.4 rrequency f O EXAMPLI:S (continued) e l EXAMPLE 1.4-4
$ SURVEILLANCE REQUIREMENTS t
SURVEILLANCE FREQUENCY NOTE Only required to be performed in MODE 1. Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in MODE 1. 2. or 3 (the assumed Applicability of the associated LCO) between performances. As the Note modifies the required performance of the A Surveillance, the note is construed to be part of the V "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1. this Note allows entry into and o]eratiori in MODES 2'and 3 to perform the Surveillance. T1e Surveillance is still considered to be performed within the "specified Frequency" if completed l prior to MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1. it o
/ would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES. even with the 7 day Frequency not met, o provided operation does not result in entry into MODE 1.
9 ' Once the unit reaches MODE 1. the requirement for the Surveillance to be performed within its specified Frequency H applies and would require that the Surveillance had been pl performed. If the Surveillance were not per.f.ormed prior to (j MODE 1. there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. O
.BRAIDWOOD - UNITS 1 & 2 ,
1.4-5 5/14/98 Revision F
De b b , l.1
't L0 Q$E Aub ADPLIC AT04 i ,q , 1.g DEFINITIONS )
U _ _ _ _ _ _ _ wr c - - - - -- -- - - - - - - - -
' The defined terms of this section appear in capitalized type and are applicable u throughout these Technical Specifications cond pus) , I ACTIOQ g'
eqaml Aebn2 4. Le ideo '
@,eGB ACTIO@shall be that part of a Gechnien Specification stat m.
% <4-prescribes
._.a J1 under designated condition ACTUATION LOGIC TEST
.g TQ j
EEb An ACTUATION LO'GIC TEST shall be the application of various simulated /
-input combinations in conjunction with each possible interlock logic state and verification of the required logic output.
include a continuity checkf as a minimum,Y5f The ACTUATION LOGIC TEST output devices. f shall g l l h dUi49RD CHANNEL OPER4TIONAL TEST (fasert 1-lB$. g EB AdGUIARRD CHANNEL OPERATIONAL TE T shall be the injection of a simulatedE
.b OPERABILITY';f inte lug end/ei d!: td: signal into the channel as close- to the sensor as pracI functf a91 The dEEUG CHANNEL !
OPERATIONAllEtT 1cck and@ Trip Set shall include adjustments, as necessary, of the alarm, inte) range and ac. curacy. points such that the.Setpoints arewithin th required U 3g, (or ,0 c, ,,A, m ,, t,, ,,,,3 w4 AXIAL FLUX _ DIFFERENCE ( ~' # ' ' " I" " "'S cwu (L" !a. *2 **** % '**c 6 AXIAL FLUX DIFFERENCE shall be the difference in normalized flux signals between the top and bottom halves of a two section excore neutron detector. CHANNEL CALIBRATION O A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel such that it responds within the required range and accuracy to known 3A,
=]=:
g' dhchdinf ci inpu@ys the ten: r: unnim u. unuun wn mm.. m , m...,~
, %terled and/er trip functicas5hge,may be Itsr )
. ... , m,y_ - .51 and ela performed by any-series of sequential, overlappin or total channel steps .l- I A J such that the entire channel is calibrated.
g (The cuArpjct cAU6FATIOM) CHANNEL CHECK' G3B A CHANNEL CHECK shall be the qualitative assessmeritsof channel behavior during operation.Wy observationMhis determination shall include, where Q possible, com arison of the channel indication and(ib status with other indications r status derived from independent instrument channels measuring the same parameter.
- O Rv) F .
BYRON - UNITS 1 & 2 1-1
DEFINITIONS' Deen;& 5j.J t.co a.6.1 CONTATNNEhfi INTEGRITY pec; pen # m s.D 1.7 CO AINMENT INTEGRIT shall exist whe .
- r. Addresse d in Sec -Ion F.(,
l O + ~ ~ "*^>+
. All penetrati ns required to b closed during ac dent conditions are either:
- 1) Capab e of being closed by an OPERABLE e tainment automat'c isol ion valve system or
- 2) C1 ed by manual val es, blind flange , or deactivated a omatic valves se ured in their ci ed positions, except as ovided in Table .6-1 of Specific ion 3.6.3.
- b. All quipment hatches are closed and s led,
- c. E hairlockisincompliancewifh erequirementsof edification 3.6. 3. /
- d. The containment akage. rates are ithin the limits 'f Specification 3.6.1.2, and
. The sealing m hanism associate with each nenetr tion (e.o.. weld . ,
A(e bellows. or rinos) is OPERAB E.) - -
- r ---
- AAdassed ss Se4+ih C D i
Set. DOC W S*CSiI" S'O _) :: __
." 00!!T'10LLED4EAKACE sh;il be that-see4-water ficw suppli:d te the re::tel
;;;hnt ;;;; se;ls.1 L' CORE ALTERATION (fuel,sont.eS, or rcuhW/ca>Wo/)
@ CORE ALTERATION shall be the movement Sr ;;ni;;htied of anyvcomponent@l.
within the reactor vessel with the vessel head removed and fuel in the vesse 8 Suspension of CORE ALTERATI0t@shall not preclude completion of movement of a component to a safe;;;m ;rv nive position.
' A, l
O!::*tt CP"'NEL 0"E"":0St TEST 1.20
- O!CITAL CH"'"El 0"E"J.TIO!!AL TEST sh:11 ;nsist of exercising the digit:1 :::;;t:r 5:rdu:ra ;;in; d;;; hs; ;;nipshtien ;r.d inj;;tir.; si :ht]:dj
;r::::: d:t: t: ::rify 0"E"ASIL!TY cf ;h m end/;r trip fur; tier.s. .;
l L.t. BYRON - UNITS 1 & 2 1-2 AMENDMENT NO. 94 3 Lv F d Q .
Otb6Niceti l.)
- Spec 4 cab s.o hMressed in Subs 5.0 O- MFSIM DOSE CAMLATIM MAN \ 6*L DOC M $ccM 6.0 1.18 The OFFSITE DOSE CALCULATION MANUAL (00CN) shall contain the methodology and parameters used in the calculation of offsite doses resulting from radio-active gaseous and liquid effluents, in the calculation,of gaseous and liquid effluent monitoring Alare/ Trip Setpoints,.and in the conduct of the Environ-mental Radiological Monitoring Program. .The ODCN shall also contair (1) the Radioactive Effluent controls and Radiological Environmental Monitoring Programs required by Sections 6.8.4e and f, and (2) descriptions of the -
infosestion that should be included in the Annual' Radiological Environmental Operating and Radioactive Effluent Release Reports required by Specifications '
'6.9.1.6 and 6.9.1.7. /
MERAELE - MERABILIM An sa feb ra.cMied ) ) An ( WMal M CMC.rqCntfl) gg; {
-4rt9-- A system,- subsystem, train, component or device shall OPERASLE or.
have OPERABILITY when i e capable of performing its ,specified function (s),
.and when all_necessary attendant instrumentation, controls,Telectrical power, cooling p al water, lubrication g other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its function (s) are also capable of performing their related support function (s).
@ OPramtrue ftwYts eesomt G e ta s o s e; h e. po eo os a A ah 1.1 .; he i- _ _ _ - ; I n ..
f
- a. --- *y is the unit-specific document that provides 2_ _c:Mlimits for the current fopgeettna) reload cycle. These cycle-specifiq --- - ' 2. limits shall be determined for each reload cycle in accordance/with Specification!".;...el SE E oper tien within thesefeserethel limits la/ addressed in individual specificati6as. Unit I j
( corn a c. Ac .-) 1 g Mmp3
-4rtC- h MODE [ia... , ilshall correspond to any one inclusive combination of core reactivity condition, power level, gg average reactor coolant temperatureYepecified in TableQ pg.M M M the(toCkV VtSSCO and ccacher aesse.1 heact
(,C.lesucc balf fcMioni Aq
\
h AdreS5edM.ser.jbAN.D Sea.DDC., 40e $LCAinn $.0 i 1.2D.s r,snaAA se sne max ---- cassu4mssa pr --- y ..- I (44.4 peig*, 47.8 peig**) for the design basis loss of coolant accident. (Inihai Ted froqr4 A) *
-4,44-- PHYSICS TE S shall be those teste performed to measure the fundamental nuclear charact isti in. Chapter 14 ft 4 of thetore and related instrumentationPb described SAR, Q /uthorised under the provisions of 10 CTP 50.5 g herwise approved PREEauna EdDMDARY N V
e \>R"bythe&r'-imalen.u\ tar a.c.culo%t) l # 4 *
\
-4,G4 -
LEAKAGE M (except steam generator M . 1Taakaa#) through a nonisolable f"ault in a Reactor Coolant System component j body, pipe wall, or vessel wall.f AA0VEO U LUAkkGE' kFah 71cyj [
- Applicable to Unit 1 thrauch cycle 8 aruf to Unit 2.
\**not applicable to imit 2. Applicable to unit i efter cycle 8 1 T AMr,6sd r,- Seche 6,o
Su Dot fw Secha S.O u_ sYRON - UNITS 1 & 2
- 1-4 >* !
AMENDNENT NO. 97 l (bl F i* i
DEFINITIONS D ebniNayts I,l PRESSURE AND TEMPERATURE LIMITS REPQRT (PTLR) 5 qa (q > e.??a The PTLR is the unit-specific document that provides the reactor vessel pressure and temperatt'e limits, including heatup and cooldown rates, q 4 and the pressurizer power operated relief valve (PORV) lift settings for the - ' current reactor vessel fluence period. These pressure and temperature limits shall be determined for each fluence period in accordance with Specification k S.6 6 (hih-h+E. Unit operation within these limits is addressed in LCO 3.4.9 Q u.
"Pressurs@ Temperature Limits," and LCO 3.4. . , " Overpressure Protection D Systenm3"("C l T i t az (i.ou;Tapeaweel ((LTDP))
(iP/r)) O 9
?
O
~
v BYRON - UNITS 1 & 2 1-4 AMENDMENT NO.98 l Rsa F
bebh 1. ll L t o s .2 9 - DEFINITIONS-0 IPAOCSSCONTROL'PROGRAMh t 1.23 The PROCESS CONTR PCP) shall contain the curre s, ,I sampling, analyses, tests, and hete s to ensure that h processing and packaging of solid radio processing of actual or simul such a way as-to as solid wastes wil ased on demonstrated iance with 10 CFR Parts 20, 61, an omplished.in tate regulation a ground requirements, and other requirements governin dis of solid radioactive waste. PURGE - PulldING 1.24 PU Efor PURGING s 1 be any cont lled process of discharging air ~ r gas from aLc nfinement to ma ntain temperat e, pressure, h idity,'concentra ion j f / . 'r o othe operating con tion,-in such manner that rep acement air or g s jis requir d to purify the confinement.p h. 7l5T QUADRANT POWER TILT RATIO d g -QUADRANT-POWER TILT RATIO shall be the ratio of the maximur upper excore etector calibrated output to the' average of the upper excore detector cali-brated outputs, or the ratio of the maximum lower excore detector calibrated-output to the_ average of the lower excore detector calibrated out>uts, whichever
-is areater.1 W1tn one excore detector inoperable, the: remaining tiree detectors 1 h- (f~nall be used for computing the average. J RATED THERMAL' POWER' o
?
3 ," g @ reactor coolint of 3411 MWt.. RATED THERMAL ~~ POWER shall be a total cor heat tr
' REACTOR TRIP SYSTEM RESPONSE TIME ETS
< fib The REACTOR TRIP SYSTEM RESPONSE T shall-be the time interval from when the~ monitored parameter exceeds-its ripfetpointatthechannelsensor-until loss of stationary gripper coil vo age. ,y "REPORTAILE' EVENT-h 1.28 REPORTAB EVENT shall/be any bf tho/e conditions [pecified in)
Sect' n 50.73 of 10 CFR Part 90. f SHUTDOWN MARGIN ~
- a. m. @ ,.
MARGIN shall be the instantaneous ount of. reactivity by which $
' . hc- Gi]B the reac SHUTr is suberitical'or would e,suberiti _1 from its present condition o
~~
assumi : 11 te+>+enne Ad fluster 4ssemblies .:tr~2 ::d :: r: u are fully. inserted except for the single h**majAgf highest reactivity Q worthwhichisassumedtobefullywithdrawn.q $ b n. M & yw s.gc ) j BYRON - UNITS 1 & 2 1-5 AMENDMENT NO. 46 Ra4 V
, _s CTS INSERT (S) i i SECTION 1.0 RJ Definitions 1.1 INSERT 1 5A l Deleted in Revision F INSERT 1 5B (L2 )
The response time may be measured by means of any series of sequdntial, overlapping, or total steps so that the entire response time is measured. INSERT 1-5C (M3 ) r~s b. In MODES 1 and 2, the fuel and moderator temperatures are changed is,) ' to the hot zero power temperature. O I [. INSERT 1 5D (A3 ) (j With any RCCA not capable of being fully inserted, the reactivity worth of the r c RCCA must be accounted for in the determination of SDM; and j l I l
,~
)x / 5/14/98 Revision F I w____.__--__._____
behn hans l. I L @
'N I.I-I TABLE G F) -s] '
(OPEPJ.TICM^.0 MODES REACTIVITY ONDITION, K % RATED (O AVERAGE b0 T MODE eff THERMAL POWER / TEMPERATURE (*O g
- 1. POWER OPERATION > 0.99 >Q p- nc E) NA
- 2. STARTUP 1 0.99 $& e ac"r; NA 9
- 3. HOT STANDBY Mk < 0.99 #NA > 350@r
- 4. HOT SHUTDOWN (b) < 0.99 I(JA -
350 W) T m
> 200,j avg ,
- 5. COLD SHUTD0 b) < 0.99 /NA 1 200 @ j
- 6. REFUELI (1 0.00NA h [NA) e d M0"D NA @
em M 8' Excluding decay heat. "8 *
,r 's @ (c N x ;i : - - re ::: ;; ; ; = fb
(_) tensione(cr'iti the " err :-:rrr7-N vessel head closure bolts less than fully l 9 All reach reueln ' e.cl etw, 643 {,[1, L,g,, UVl l I
~ n, 4h IT5 (re, Led R A)
Sep.
- f. Z - L3 61 Co ..u bs Sec.4 1. 3 - C-ele G L.; 4 S w u 1.4 - E q ~ ry O
BYRON - UNITS'1 & 2 1-9 R t.J F. l
~ /MSE7L7 /- 9A Logical Connectors pap 2 o f W 1.2 q
A_s 1.2 Logical Connectors j. I [ EXAMPLES EXAMPLE 1.2-1
$ (continued)
- s. ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LC0 not met. A. I Veri fy . .
AND l A.2 - Restor e . . . 9 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. I O i l J 1 i I (continued) V. BYRON UNITS 1 & 2 1.2-2 5/14/98 Revision F i ____ _-_ _ __ _.___ _.__- . .- _ _ . _ - _ _ - . __ . _ . _ r.
f,
/tJ 5ERT l- 9 A L gical Connectors
_ fay - 5 o f' ?l j-ri g! ' 1.2 Logical-Connectors
. qf .
l EXAMPLE 1.12-2
.il EXAMPLES; (continued).
f: 4' ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. - LC0 not met. A.1 Trip .. p Verify A.2.'1 ; I AND A.2.2.1 Reduce . . QB A.2.2.2 Perform . 1 08 l
'O ^3 ^'9"...
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 3erformed as
.. indicated by the use of the logical connector 03 and the Lleft 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
~
@ indicates'that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.
l',. .. BYRON - UNITS 1.& 2 1.2-3 5/14/98 Revision F 1 u___....___._.._____ _
7 l l gg .~ Completion Time l } MfL 6 of LI j q
~
j 1.3 Completion Times. (continued) L'
' EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing
-Q ' Conditions.
?L 7l EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME
'B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion. _ .
l Time not B.2 Be in MODE 5. 36 hours met. i Condition ~B has two' Required Actions. Each Required Action i f]' has.its own separate Completion Time.
,is referenced to the time that Condition B is entered.
Each Completion Time L The Required Actions of Condition B are to be in MODE 3 within 6 hours AND in MODE 5 within 36 hours. A total of 6 hours is allowed for reaching MODE 3 and a total of p 36 hours (not 42 hours) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours.. the time allowed-for reaching MODE 5 is the
.next 33 hours because the total time allowed for reaching MODE-5:is 36 hours.
If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours. l L p (continued)
, V BYRON:-. UNITS 1 & 2 1.3-3 5/14/98 Revision F c__ - __---_ _ ___ _ _ _ ______ _ ___-_______-___.-__
f Completion Times lNSE12-T l-9A; I 1.3 i p) q, . 1.3 Completion Times J c4 4 EXAMPLES EXAMPLE 1.3-2 d (continued)
< ACTIONS
. CONDITION REQUIRED ACTION COMPLETION TIME A. One pumi A.1 Restore pump to 7 days 4 inoperaale. OPERABLE status.
B. Required B.1 Be in MODE 3. 6 hours < Action and I associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. i When a pump is declared inoperable. Condition A is entered. O. If the pump is not restored to OPERABLE status within 7 days Condition B is also 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. LCO 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_LCO 3.0.3 is entered but continues to be tracked from l the time Condition A was initially entered. While in LC0 3.0.3. if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired. LC0 3.0.3 may be exited and operation continued in accordance with Condition A. l (continued) L BYRON - UNITS 1 &.2 1.3 5/14/98 Revision F L
.- Completion Times l i /MSE72T /-j4 l 1.3
~
( @y 9 of2' i 1.3_ Completion Times > 1 l: EXAMPLES . EXAMPLE 1.3 .: (continued) ACTIONS k CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Restore 7 days
- Function X Function X train '
i train to OPERABLE AND L inoperable, status., L - 10 days from discovery of l failure to meet
- l. the LC0 l
B. O' ne B.1 Restore . 72 hours Function Y Function Y train L train to OPERABLE AND inoperable. status. Ln 10 days from
-'()
i ' discovery of failure to meet the LCO 1 i L i- C. One C.1 Restore - 72 hours Function'X Function X train ' train to OPERABLE inoperable. status. AND QR L One- C.2 Restore 72 hours L Function Y Ft.nction Y train i ~ train at OPERABLE i , inoperable. status. i (continued) Q. - BYRON - UNITS 1 & 2.- , 1.3-6 5/14/98 Revision F
Completion.Ti g g 7 g94 (49L // of ZI-) 1.3 Completion Times '
? EXAMPLE 1.3-4
*l-EXAMPLES-(continued)-
% ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. ' One or more A.1 Pestore valve (s) 4 hours valves to OPERABLE inoperable. status.
B. Required B.1 Be in MCDE 3. 6 hours Action and associated AND
. Completion
. Time not B.2 Be in MODE 4. 12 hours met.
-O ^ si"9 e como etio" Time is used for e"> "vmber or ve1ve8 ino3erable at the same. time. The Completion Time associated wittCondition- 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 hours provided this does not result in any subsequent valve being inoperable for > 4 hours. If the Completion Time of 4 hours (plus the extension)
-expires while one or more valves are still inoperable.
Condition B is entered. l p (continued)
.J \
l BYRON - UNITS 1<& 2- 1.3-8 5/14/98 Revision F l [
o Completion Times
/NSE7LT l-9A 1.3 11.3 Completion Times b p.
"ol EXAMPLES EXAMPLE 1.3-5 L 2(continued)
ACTIONS NDTE -
- , Separate Condition entry is allowed for each inoperable valve.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours valves OPERABLE status,. inoperable. B. Required B.1 Be in MODE 3. 6 hours Action and associated- AND Completion l Time not B.2 Be in MODE 4. 12 hours
, met.
l 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. l The Note allows Condition A to be entered separately for each inoperable valve. and Completion Times tracked on a'per i 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. (continued)
' BYRON - UNITSL1 & 2 1.3-9 5/14/98 Revision F
f jgggy / p ' Completion Ti fafL /3 6f LI j 1.3 Compl_etion Times EXAMPLES EXAMPLE 1.3-5 (continued) 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.
Since the Note in this example allows multiple Condition entry'and tracking of separate Completion Times, Completion Time extensions do not apply.
}.
$< l- EXAMPLE 1.3-6 g .gAIONS CONDITION. REQUIRED ACTION COMPLETION TIME A. One channel A.1 Perform
' :Q:- inoperable _SR 3.x.x.x. Once'per 8 hours gg A'.2 Reduce THERMAL 8 hours 1 POWER to-5 50% RTP. B. Required B.1 Be in MODE .3. 6 hours ' Action and associated Completion Time not
- - met.
L (continued)
' BYRON - UNITS'1L & 2 1.3-10 5/14/98 Revision F j
. _ _ _ _ _ _ - _ _ _ _ _ _ _ _ _ _ _ _ _ - - - - - - - - - - - _ - - - - - - - - - - - - - - ~ ~ - - - - " ' - ' ~ - ' - ' - - - - " ' ~ - - - - - - - - ~ ~ ~ - - ^
Completion 'imes
, / AlS67LT' /-9M 1.3 1.3 Completion Times I pagc /fsf 2-l}
J q EXAMPLES EXAMPLE 1.3-7 (continued)
$ ACTIONS k CONDITION REQUIRED ACTION COMPLETION TIME A. One A.1 Verify affected 1 hour subsystem subsystem inoperable. isolated. AND Once per 8 hours thereafter AND A.2 Restore subsystem 72 hours to OPERABLE status.
i) s_ B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time not B.2 Be in MODE 5. 36 hours met. , Required Action A.1 has two Completion Times. The 1 hour Completion Time begins at the time the Condition is entered and each "Once 3er 8 hours thereafter" interval begins upon performance of Required Action A.1. 1 I I i n (continued) V BYRON - UNITS 1 & 2 1.3-12 5/14/98 Revision F 1
Frequency lN5GR-T I-9 A , ' 1.4 j ,4go It o f 2I )
.1.4 Frequency A
6 l EXAMPLES EXAMPLE 1.4-1
< .(continued) 4 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Exam)le 1.4-1 contains the type of SR most often encountered in t1e Technical Specifications (TS). The Frequency specifies an interval (12 hours) during which the. associated j Surveillance'must be performed at least one time. J
. Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours, an extension of the-time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the ecuipment is. inoperable, a
.O V variable is outside specifiec limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0 2 is exceeded while the unit is in a MODE or other specified condition. in the Applicability of the LC0. and the -
performance of the Surveillance is not otherwise modified (refer to Example 1.4-3) then SR 3.0.3 becomes applicable. If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE. or other specified condition in the Applicability of the LC0 for which performance of the SR is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of SR 3.0.4. (continued)
' BYRON - UNITS l'& 2 1.4-2 5/14/98 Revision F l
/A/Smr /-94 f"*4"*B
/*f 14 0 f 2 l
.m 1.4 Frequency V g 91 EXAMPLES EXAMPLE 1.4-2 Q
s
. (continued)-
SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits. Once within 12 hours after
= 25% RTP AND 24 h'ours thereafter Example 1,4-2 has two Frequencies. The first is a one time performance Frequency, anc 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 aower is increased from a power level < 25% RTP to D a 25% RT), the Surveillance must be performed within 12 hours.
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 L does not. qualify for the extension allowed by SR 3.0.2. ' l "Thereafter" indicates future performances must be established per SR 3.0.2. but only after 'a specified ! l condition is first met (1..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. I l-9 l i i r
,f- (continued) l BYRON ' UNITS 1 & 2 1,4-3 5/14/98 Revision F l
L-_-__----___----_---__---------__--
Frequen I//JSE7z-r /-9A]
~j fY Ib A ? A,g 1 1.4 Frequency h)
Y _ EXAMPLE 1.4-3'
'9l EXAMPLES (continued) t SURVEILLANCE REQUIREMENTS SURVEILLANCE. FREQUENCY NOTE-Not required to be performed until 12 hours after a 25% RTP.
Perform channel adjustment. 7 days The. interval continues, whether or not the unit operation is
< 25% RTP between performances.
As the Note modifie.s 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 hours after power reaches a 25% RTP to perform the Surveillance. The-Surveillance is still considered to be 3erformed within the rl "specified Frequency." Therefore, if t1e Surveillance were w not performed within the 7 day (plus the extension allowed )
?. by SR 3.0.2) inte'rval, but operation was < 25%' RTP. it would
-O. not constitute a failure of the SR or failure to meet the
<' LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided k
operation does not exceed 12 hours with power a 25% RTP. Once the unit reaches 25% RTP, 12 hours would be allowed for ; completing the Surveillance. If the Surveillance were not ' performed within this 12 hour interval, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply. (continued) BYRON - UNITS 1 & 2 1.4-4 5/14/98 Revision F __.__._._m____ _ _ _ _ _ _ _ _ - _ _ _ _ _ . _ _ . _ _ _ .- c - . . . _ _ _ -____m_.._.._.____.__m_.____m__m_._____-._.__.-m________.____..m_ _ _ . _ _ _ . _ _ _ _ . _ _ _ _ _ __
l/ N SEfLT /- 74 7 Frequenc pqL . 2d o[ 2l 1.4 Frequency
? 'J EXAMPLES- EXAMPL E 1.4-4
'I '(continued)
SURVEILLANCE RE0aIREMENTS SURVEILLANCE FREQUENCY NOTE
. Only required to be performed in MODE 1.
Perform complete cycle of the valve. 7 days The interval continues, whether or not the unit operation is in MODE-1, 2. or 3 (the assumed Applicability of the associated LCO) between performances. As the Note modifies the required performance of the Surveillance, the note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1. this Note allows
]. entry into and o)eration in MODES 2 and 3 to perform the Surveillance. Tie Surveillance is still considered to be performed within the "specified Frequency" if completed prior to MODE 1. Therefore. if 'the Surveillance were not lN performed within the 7 day (plus the extension allowed by-SR 3.0.2) interval, but operation was not in MODE 1. it 8 would not constitute a failure of the SR or failure to meet a the LCO. Also, no violation of SR 3.0.4 occurs when o changing MODES, even with the 7 day Frequency not met.
provided operation does not result in entry into MODE 1. Once the unit reaches MODE 1. the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been ls ]erformed. If the Surveillance were not performed prior to iODE 1. there would then be a failure to perform a . Surveillance within the 'specified Frequency and the l provisions of SR 3.0.3 would apply. h . BYRON - UNITS 1 & 2 1.4-5 5/14/98 Revision F L _ ______ _-___ - -________ _ __ _
Specf,% l.11 Lco 3i.t REACTIVITY CONTROL SYSTEMS ~ 1A - 3 .l, W ij SHUTDOWN MARGIN < T**8 ~ 200'F U"*J L 5,c4 3. t , h Do c 4 5,& 3. I
'4 LIMITING CONDITION FOR OPERATION ;
3.1.1.2. -The SHUTDOWN MARGIN shall be greater than or equal to 1.'3% Ak/k. l APPLICABILITY: ' MODE 5. ACTION: ,
~
- a. With' the SHUTDOWN MARGIN less than 1.3% Ak/k declare both Boron W
Dilution Protection System subsystems inoperable and apply Specifi-cation 3.1.2.7.b.
- b. With the SHUTDOWN MARGIN less than 1% Ak/k,'immediately initiate.and continue baration at greater than or equal to 30 gpm of a solution containing greater than or equal to 7000 ppe boron or equivalent until .the SHUTDOWN MARGIN is restored to greater than or equal to 1% Ak/k.
SURVEILLANCE REQUIREMENTS 4.1.1.2 The SHUTDOWN MARGIN shall be determined to be' greater than or equal-to 1% Ak/k:
- a. Within I hour after detection of an inoperable control rod (s) and at least'once Der 12 hours thereafter While the rod (s) is inoperable.
If the inoperable control rod (s) is immovable or untrippable, the 1.t s m SHUTDOWN MARGIN.shall be verified acceptable with an increased Mneun allowanc'e for the withdrawn worth of the immovable or untrippable Lcontrol rod (s);'and b .' ' At least once per 24 hours by consideration of the following factors: - I
- 1) ' Reactor. Coolant System boron concentration,
- 2) Control rod position,
- 3) Reactor _ Coolant System average temperature,
- 4) Fuel burnup' based on gross thermal energy generation,
- 5) --Xenon concentration, and
- 6) . Samarium concentration.
~
l bc Net Ser % i T See Doc -/.- 6 H.{3.I i-BYRON - UNITS 1 &'2 . 3/4 1-3 Amendment No. 51 PM F
De On h /. / Leo 34/6 l TABLE 4.4-4 (Continued) I TABLE NOTATIONS Until the specific activity of the Reactor Coolant System is restored within its limits. Sample to be taken after a minimum of 2 EFPD and 20 days of POWER OPERATION have elapsed since reactor was last subtritical for 48 hours or longer. A gross radioactivity analysis shall consist of the quantitative measurement of the total specific activity of the reactor coolant except for radionuclides with half-lives less than 10 minutes and all radiciodines. The total specific activity shall be the sum of the degassed beta-gamma activity and the total of all identified gaseous activities in the sample within 2 hours after the sample is taken and extrapolated back to when the sample was taken. Determination of the contributors to the gross specific activity shall be based upon those energy peaks identifiable with a 95% confidence level. The latest available data may be used for pure beta-emitting radionuclides. Radiochemical analysis for E shall consist of the quantitative b ' E measurement of the specific activity for each radionuclides, except for radionuclides with half-lives less than 10 minutes and all radio-iodines, which is identified in the reactor coolant. The specific activities for thase individual radionuclides shall be used in the i determination of E far the reactor coolant sample. Determination of the contributors to E shall be based upon these energy peaks
] Identifiable with a 95% confidence level.
i**** For Unit I through Cycle 8, reactor coolant DOSE EQUIVALENT I-131 ' will be limited to 0.35 microcuries per gram. l'
~
lHussed in %km M&
% ecc fx Sechal:T.y b j O --
1 1
- u. 4 l BYRON - UNITS 1 & 2 3/4 4-31 64 F AMENDMENT NO.101 i Q
l j
- - - _ - - - - - - - - - - - - - - -u
l Deb', L, a ., s 1.)
- 1. 0 USE AAlo Apruernou 1.'# DEFINITIONS
!O - _ _ _ _ _ _ _ _ _ _ noTc _ _ ___ _______ _
@ The defined terms of this section appear in capitalized type and are applicable
_ throughout . _ - . --these Technical Specifications N. ._ad
- - - - _ . . . Bas i: ACTI0h g;,,g 4 4 9 g,g
%+
e .G c ACTIOh..shall be that part of a veeha+ee+ Specification dWh prescribes under designated conditionsMa wG Web T4 ACTUATION LOGIC TEST EB An ACTUATION LOGIC TEST shall be the application of various hCer mbhi4 simulated I input combinations in conjunction with each possible interlock logic state and verification of the required looic output. l ' include a continuity checkC as a minimum.) of output devices.The ACTU h (ENEGG) CHANNEL OPERATIONAL' TEST @,ued @g
.h EB As9NAGID CHANNEL OPERATIONAL TEST fshall be the injection of a simulate "
l signal int.o the channel as close to the/ sensor as practicable to verify j
- OPERABILITY-g
- =, f r.teruck- er.Ca trh functf:-2, q The M13533B CHANNEL OPERATIONAL TEST shall include adjustments, as necessaiy, of the alarm, inter- ]
1a9. ad@ Trip C:tp;i..t: :: :.'. t!..t t!.c ' ~.,si.i,v hita are w i uiin Lne requirec
- range and accuracy. } h CEr w 'ca pdr ad b w of on,. reuw,~re ls . Series 4 No..%i, overl.ppi.9 , ,, al A AXIAL FLUX DIFFERENCE &,,, ,6 ,, %+ u, ,,g, , h. .e l n te
- Fed.
GB AXIAL FLUX DIFFERENCE shall be the difference in normalized flux signals L t between the top and bottom halves of a two section excore neutron detector. CHANNEL CALIBRATION GiB A' CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel such that
" "-- a* inpu 1_ responds within the required range and accuracy to known c.DISERT l The CM*"N1.GAMEP^ TION thd ' .:- ::;; ;n: :" --W'
.qse=s aad ele , %terle:S :nd!:r trip funcdrM. r:gn may be ! p g j
@c% diag +h-such that the perTormedbyg\entirechanneliscalibrated.ny / series
. steps gg g of s'e~@efil.tal, g Ovan e4) 'hl;W Q ~ -
CHANNEL CHECK (iD A CHANNEL CHE_CK shall be the qualitative assessment 4of channel behavior e' v during operation.(by observation 7 This determination shall include, where possible, comparison of the channel indication and@) status with.other indications @r status derived from independent instrument channels measuring the same parameter.
-O BRAIDWOOD UNITS 1 & 2 1-1 (tw F J
I DeEnihevis'/,/ L Lc0 3.6./ L DEFINITIONS Spec h a u n f.D i CONTAINMENT INTEGRITY gh )i,.Sec4;,E3,G Get DOC Fw Sec+ien 3,G 1.7 CONT NMENT INTEGRITY hall exist when i
- a. All penetratio required to be closed during a 'ident condition are either:
Capable of being closed y an OPERABLE c ntainment autom ic i 1) isolat on valve system or
- 2) Clos d by manual val s, blind flange , or deactivated automatic valves se red in their el ed positions, e cept as pr 'vided in Table .6-1 of Specific ion 3.6.3.
- b. All e uipment hatches re closed and s led,
- c. Eac air lock is in ompliance wfth t a requirements Sp ification 3.6.1 3,
- d. he containment 1 akage rates are ithin the limit of Specification
.6.1.2, and
- e. The sealing me anism associate with each pene ation (e.g., we ds, bellows. or 0 inas) is OPERAB E.1 ,
, l
'CO'""0LLED LEAF'.CD su. doc ~Pe Sechsw r.o'
\ .
1 00'?T"0LLED LE'r.'0E :h:11 b: th:t :::1 ::::r fic ::;;11:d t: th: r:::ter-!
-O. (csi:nt
- e. ":::: :::1: .1
.C. ORE ALTERATION (pad,5,veces, or reachty convo
@ CORE ALTERATION shall be the movementP of any component [;D within Suspension theofreactor vessel withhallthe CORE ALTERATIO6 notvessel' preclude head removed completion of movementand of fuel a in the ves component to a safe ermr== .-; positi
'0:0 TAL 0":': L 0"E",'TIO':"L TEST
- .:: : ::::n ::=:t ":"aT:~".L T::T :t:11 =:::t :f ==t:t:0 tt:
- ing d:t:
;:rify 0"E"^."!LITY cf5::: :::ip:1:tica
- d/:r trip::d inj:: ting :i=Aeted)
(digit:1 ~ pre:::: d:t: :r; t:r te 5:rdu:r: :1:= f ::ticas. DOSE E0VIVALENT i-131 A DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcurie / gram) which alone would produce the same thyroid dose as the quantity and isotopic mixture of ~ I-131, I-132, I-133, I-134, and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in Table III of TID-14844, " Calculation of Distance Factors for Power and Test Reactor Sites.' BRAIDWOOD - UNITS 1 & 2 1-2 AMENDMENT NO. 86 u. 4F ij l i 1
Ddin; hm s /,/ g Speckca ken s;o DEFINITIONS O *
- V OFPSITE DOSE CALCULATIDF MANU Mdr4Hed lo fechrn 6.0 .
O tTit. The OFFSITE DOSE CALCULATION MANUAL (ODCM) shall contain the methodology) -l and parameters used in the calculation of offsite doses resulting from radio-l active gaseous and liquid effluents, in the calculation of gaseous and liquid ) ( ' effluent monitoring Alarm / Trip setpoints, and in the conduct of the Environ- ] l: mental Radiological Monitoring Program. The ODCM shall also contain (1) the 1 l Radioactive Effluent Controls and Radiological Environmental Monitoring i Programs required by sections 6.8.4.e and f, and (2) descriptions of the information that should be included in the Annual Radiological Environmental l Operating and Radioactive Effluent Release Reports required by Specifications i 6.9.1.6 and 6. 9.1.7. / SPeCIfied 54 j OPERABLE - OPERABILITY (nor,nal or ernergencV H g
+rt9- A system, subsystem, train, component o device shall be OPERABLE or
- l. have OPERABILITY when it a capable of performin its specified unction (s),
l and when all necessa ttendant inst _rumentation, controls,& electrical power, I l . cooling g seal water, lubrication g other auxiliary equipment that are } required ror the system, subsystem, train, component, or device to perform its# l function (s) are also capable of performing their related support function (s). I AOPERATINC LIMITS REPORT [00Lk) ) l t c we u te. ,4-he. om sa+v A l .
-- i . ii .w- (The ;. _ 70 2r70 - - ~ ;; "3LRA is the unit-specific document that --
. providesTomesatene)1imits for the current W5HEWip reload cycle. These l
cycle-spacif 1_ _ ::=;;11mits shall be determined for each reload cycle in accordance with Specification %.O.1.0 operation within these Sp5HEEEE limits is addressed in individual ification . u na-) Gbrarn w r1 5,(,.
. .: _. m . . . . . - . . , . . c . . .
-tTf0- Air 9P3fWttf9MA4) MODE p e.v-4000&M shall correspond to any one inclusive combination of core reactivity condition, power level, Gli@ average reactor coolant temperatureYeoecified in Table . (s.i-i w.m het .n %c. (eac 4g,e VM56l}
, Dind rear he vc_ssr_t head /
c,lomec. boli +eesioming Nresse'd lif8CSonh.D
, se.e. Doc for Sechrw 5.o 1.20.a P, shil1~be the maximum calculated primary containment pressure (44.4) poig*, 47.5 peig**) for the design basis loss of coolant accident. / l 1 l
n aioHestpogree ) ( renc4or) Wh"' +csts arc : O
+rti- PHYSICS TESTSshallbethoseltesteperformedtomeasure fundamental !
i nuclear characteristic of the# core and related instrumentation scribed i l in Chapter 14 @ f th SAR, g luthorised under the provisions of 10 CFR ! 50.59, o /therwise approved by the Cossaission. I Parssun.o seUNDARY fEAKAC Nuteor ReAata%
+ + 5 4 4,33- {Pstesetnte-99UNDAdHD LEAKAGE (except steam generator @ )
.2 eakaoef) through a nonisolable fault in a Reactor Coolant System component /
bcdy, pipe wall, or vessel wall. / ,, be
)
' 'Asplicable to Unit 1 through cycle 7 and to Unit 2.
{ /* mot appticable to imit 2. Appt(cabletounit1aftercycle7./ g g;g M b fg,c}iOH 6 D 1 St.L OOC .fyr- $tsiinr 6.0 BRAIDWOOD - UNITS 1 & 2 1-4 - h,,um . q Re.v F
DEFINITIONS Defini hovis - I.I p PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR) Q The PTLR is the unit-specific dccument that provides the reactor vesse pressure and temperature limits, including heatup and cooldown rates, h p/ y and the pressurizer power operated relief valve (PORV) lift settings for the 's current reactor vessel fluence period. These pressure and temperature limits 1 shall be determined for each fluence psriod in accordance with Specificati n g (5,6 6T " " ' 'n Unit operation within these limits is addressed in LCO 3.4. g
~ "Pressur' Temperature Limits," and LCO 3.4 . " Overpressure Protecti g Systen$"
on I_ _i ((P/rj 12 L LowTemperab re.] ((LTOP)) O > e o u , I L. 2 u , BRAIDWOOD - UNITS I & 2 1-4a AMENDMENT NO. 89 L. , en L_-___---___---_
Defm.6.3 l. I DEFINITIONS
" PROCESS CONTROL PROGRAM (
1.23 'The PROCESS CONTROL (PCP) shall contain the current formulas D sampling, analyses, tests, and de armin tions to be made to en processing and packaging of solid radioa(ctive-was on demonstrated processing of actual or simulated wet s s714Qe accomplished in such a way as to assure with 10 CFR Parts 20, 61p and_71, State regulations l round requirements, and other requirements gBverning the { o solid radioactive waste. N PURGE-PUR#kNG 1.24 PU E or PURGING sha be any contro11e process of disc ging air or gas
./ / s from a nfinement to mai in temperature, assure, humidity concentration fl5 or oth operating condi ion, in such a man r that replaceae air or gas is p / qquir d to purify the onfinement.)
3 . QUADRANT POWER TILT RATIO - 3 e O QUADRANT POWER TILT RATIO shall be the ratio of the maximum upper excore detector calibrated output to the average of the upper excore detector cali-brated outputs, or the ratio of the maximum lower excore detector calibrated output to the_ average of the lower excore detector calibrated outnuts. whichever is greater. /With one excore detector inoperable, the remaining three detectory (shall be used for computing the average.j -- W re w J b sei b 3. f. See O RATED THERMAL POWER o c.jr S u b 2.2 pwhod _ RATED THERMAL POWER shall be a total & core heat transfer rate to the h @ reactor coolant of 3411 MWt.
. REACTOR TRIP SYSTEM RESPONSE TIME
- dE D The REACTOR TRIP SYSTEM RESPONSE IME shall be the time interval from when the monitored parameter exceeds its ipgetpointatthechannelsensor until loss of stationary gripper coil voltage. i REPORTABLEEVENT(
1.28 A REPORT LE EVENT 10CFR! art 50.hallbeany['fthosecondi/ionsspeci! I edin Sec ion 50.73 / SHUTDOWN MARGIN 4 (Canhol] MCCAd C G SH MARGINshallbetheinstantaneous(amountofreactivitybywhich P l or yould b o pCthe react r7d11 assuming is subcritica/od fiiTT:Wign fluste /e suberiticAl from tits ssemblies 4she presentEED c.-endrech condition are . 4 fully inserted except for the single /Wurn4aE45FaE3M5Wlof ' highest reactivity E worth which is assumed to be fully withdrawn 5 (IntHT l-6 D) b g. D 364J l-5C] bh [y BRAIDWOOD UNITS 1 & 2
~
1-5 AMENDMENT NO. 35 bVF
I CTS INSERT (S)
._~ . SECTION 1.0 Definitions 1.1 l INSERT l'5A l- Deleted in Revision F-l l
INSERT 1 5B (L2 )
' The response time may be measured by means of any series of sequ'ential,
. overlapping, or total steps so that the entire response time is measured.
INSERT 1 5C: (M3 )
+b. :In MODES 1 and 2, the fuel'and moderator temperatures are changed
- to the hot zero power-temperature.
f U
*i:
LC. INSERT 1 SD - (, 19 A)-
.. y W 'With any RCCA'not capable ~of being fully inserted, the reactivity worth of the T- RCCA must be accounted for in the determination of SDM: and.
5/14/98 Revision F-- ' t-
D e f,.,. ko e s 1. I
^
- 1. \ - \
TABLE d 7) _0""ATIO^;AO MODES j c(inACTOR) REACTIVITY
% RATED (4 AVERAGE 400LANT A,
MODE CONDITION, K eff THERMAL POWER
- TEMPERATURE @ )
- 1. POWER OPERATION > 0.99 > 5[ cw_wv]NA
- 2. STARTUP > 0.99 < 55 c2 MO:6 NA
- 3. HOT STANDBY < 0.99 R NA > 350 7 ]
- 4. HOTSHUTDOWh < 0.99 R NA 350[>T A,
> 200 Q **9
- 5. COLD SHUTD0 < 0.99 % NA <200@f
- 6. REFUELI k (Ch @, N A @ RNA E nu s blA @
6 > E-4 lal /Eyeludirg decay heet, d6 **' A,(c.% Fuel ir. the react e tensioned.Or ;ti, trn h::d M-OS #M vessel A.6 Aihead closure bolts less than fully [gk h[6) A ll r-ocive venej head cleure bel 4 r ^ ll-, fen.rdac{ v l OA IT5 (3. L.a 1-9 A) 5e .L \. 7. - L.g k I ce<.e% s Sec &- i 3 - Crpre b Ti.J,i s uL .,, I A - Fr,- ..cy I i i - 1
.tO O
BRAIDWOOD UNITS 1 & 2 1-9 Rea F l i i I
Iyggg7j_94
/
~
Logical Connectors f*$L % of Z/ ) 1.2 Logical' Connectors. 9g
-? l EXAMPLES EXAMPLE 1.2-1
= (continued)
< ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Verify ..
AND A.2 Restore In this example the logical connector AND is used to j indicate that when in Condition A. both Required Actions A.1 ! and A.2 must be completed. I 1" (continued)
):
BRAIDWOOD - UNITS 1 & 2 1.2-2 5/14/98 Revision F c___ _ _______-:___
Logical Conn ~ect . f/NSER T / - f*V3of2l)A,, g' l'2 Logical Connectors
.2l EXAMPLES' EXAMPLE 1.2-2 (continued)
-4 . ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met. A.1 Trip B
A.2.1 Veri fy . . . AND A,2.2 1 Reduce. . 2 A.2.2.2 Perform A.3 . Align .. V( N . 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 @ 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. I 1 bp, BRAIDWOOD - UNITS 'l & 2 1.2-3 5/14/98 Revision F l L -
)
I Completion Tirn
' /d 5ETET /-9A f*ft lo 'o f LI w o l'3, Completion Times (continued) o s
EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions. o (( EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time.not B.2 Be in MODE 5. 36 hours met. l Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time h is referenced to the time that Condition B is entered. The Required Actions of Condition B are to be in MODE 3' within 6 hours AND in MODE 5 within 36 hours. A total of-6 hours is allowed for reaching MODE 3 and a total of 36 hours (not 42 hours) is allowed for reaching MODE 5 from-the time that Condition B was entered. If MODE 3 is reached within 3 hours .the time allowed for reaching MODE 5 is the next 33 hours because the total time allowed for reaching MODE 5 is 36 hours. If-Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours. T (continued)
'BPAIDWOOD - UNITS 1 & 2 1.3-3 5/14/98 Revision F t
I. L .. .
, g j_ q 'i Completion Time
] Pfc 7 oFM g O +T 1.3 Completion Times l -EXAMPLES EXAMPLE 1.3 3 -(continued) k ; ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pumr A.1 Restore pump to 7 days inoperaale. OPERABLE status.
B. Required B.1 Be in MODE 3. 6 hours-Action and . associated AND Completion Time 'not B.2 Be in MODE 5. 36 hours met. I i When-a pump'is declared inoperable..' Condition A is entered. If the pump is 'not restored to OPERABLE status-within h ' 7 days. Condition B is also 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. LCO 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 LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered While in LCO 3.0.3. if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired. LC0 3.0.3 may be' exited and operation continued in accordance with Condition A.
(continued) O BRAIDWOOD - UNITS 1 & 2 1.3-4 5/14/98 Revision F i 4 h- ... . . . o .
. Completion Times-
/gsegr f'"QL ?ofZ//-g) 1.3 Completion Times Oi 41 EXAMPLES . EXAMPi.E 1.3-3 ;
- N (continued) g 4
ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME 1 l ) 7 A. One A.1 Restore 7 days Function X Function X train train to OPERABLE AND inoperable. status .' , l discovery of failure to meet the LC0 I l B. One B.1 Restore 72 hours Function Y Function Y train train to OPERABLE AND inoperable. status. 10 days from. l: G discovery of 'A) failure to meet the LCO C. One C.1 Restore 72 hours Function X Function X train train- to OPERABLE 1 inoperable. status. 4 k AND QB l One C.2 Restore 72 hours Function Y Function Y train train to OPERABLE inoperable. status. (continued) q k) BRAIDWOOD - UNITS 1 & 2- 1.3-6 5/14/98 Revision F j i (
.l
Completion Ti
/A/SE/2-7 /--
/4p4 // d [ ti j 4
. , 1.3 Completion T1mes 4l EXAMPLES EXAMPLE 1.3-4 N
' -(conti ved)
'k' ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One or~ more A.1 Restore valve (s) 4 hours valves to OPERABLE inoperable. status.
.B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion Time not B.2 Be in MODE 4. 12 hours met.
ry A single Completion Time is used for any number of valves () ino)erable at the~same time. The. Completion Time associated wit 1 Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis. Declaring subsepent 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 tinie the first valve was declared inoperable. The Completion Time may be extended if the valve restored to j OPERABLE status was the first inoperable valve. The
. Condition A Completion Time may be extended for up to 4 hours provided this does not result in any subsequent i valve being inoperable for > 4 hours.
If the Completion Time of 4 hours (plus the extension) expires while one or more valves are still inoperable. Condition B is entered, l (continuod) i-0 BRAIDWOOD - UNITS 1 & 2 1.3 8 5/14/98 Revision F
T Completion T1
/N SN /-9A fby 12 sf ZI]
1.3 Completion Times O,4 . j
= EXAMPLE 1 3-5 2l EXAMPLES (continued) g . ACTIONS NOTE Separate Condition entry is allowed for each inoperable valve.
CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours valves OPERABLE status. inoperable. B. Required B.1 Be in MODE 3. 6 hours Action and associated AND Completion
.]
Time not met. B.2 Be in MODE 4. 12 hours The Note above the ACTIONS' Table is a method of modifying how the Completion Time is tracked. If this method of i- 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. l:
- a. ;BRAIDWOOD - UNITS 1 & 2. 1.3-9 (continued) 5/14/98 Revision F i
i___- - _ _ _ _ - - _ - _ _ I
Completion' Times
/#5E7LT /-14) 1.3
& gt'/3 a f2I n 13 Completion Times )
u EXAMPLES EXAMPLE 1.3-5 (continued) 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 Comp 1.etion 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 I exited for that valve. 3 Since the Note in this example allows multiple Condition : entry and tracking of separate Completion Times. Completion 1 j Time extensions do not apply.
~
? 1 1
$! EXAMPLE 1.3-6
~
L 4 ACTIONS CONDITION- REQUIRED ACTION COMPLETION TIME i A. One channel A.1 Perform Once per U<^ inoperable. SR 3.x.x.'x. 8 hours 08 A.2 Reduce THERMAL 8 hours 1 POWER to I s 50% RTP. l I I B. Required B.1 Be in MODE 3. 6 hours - i Action and I !' associated Completion Time not met. i. 1 I-(continued) BRAIDWOOD - UNITS 1 & 2 1.3-10 5/14/98 Revision F
.g -
Completion Ti
/NS6TLT /-94 fagt- /S s F zij
.1.3 Completion Times O2 .? EXAMPLES EXAMPLE 1.3-7
* -(continued)'
~[ ACTIONS
.CONDITIONL REQUIRED ACTION COMPLETION TIME 1
A. One A.1 Verify affected 1 hour subsystem subsystem inoperable.. isolated. AND l Once per 8 hours thereafter AND A.2 Restore subsystem 72 hours l to OPERABLE status. O'd- B. Required' B.1 Be in MODE 3; 6 hours Action and-associated AND-Completion Time not B.2 Be in MODE 5. 36 hours met. l :. Required-Actionh.1-hastwoCompletionTimes. The 1 hour Completion Time begins.at the time the Condition is entered and each "Once 3er 8 hours thereafter" interval begins upon
- performance of Required Action A.1'.
1 L (continued) cb-- BRAIDWOOD - UNITS 1:& 2 123-12 5/14/98 Revision F L
Freque p fay L /t o S 2}
.- 1.4 Frequency.
v -o fl EXAMPLES EXAMPLE 1.4-1
- . (continued)
_ -SURVEILLANCE REQUIREMENTS
, SURVEILLANCE FREQUENCY.
Perform CHANNEL CHECK. 12 hours Exam)le 1.4-1 contains the type of SR most often encountered in tie- Technical Specifications (TS). The Frequency specifies an interval (12 hours) 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 hours, an extension of the time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is.not required to be met per SR 3.0.1 (such as when the ecuipment is inoperable, a r/m variable is outside specifiec limits, or the unit is outside V, the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO. and the performance of the Surveillance is'not otherwise modified (refer to Example 1.4-3). then SR'3.0.3 becomes applicable. If:the interval as specified by SR 3.0.2 is exceeded while -
- the unit is not in a' MODE or other specified condition in the Applicability of the LC0 for which performance of the SR is-required. the Surveillance must be performed within the
- Frequency requirements of SR 3.0.2 prior to entry into the MODE or other-specified condition. Failure to do so would
. result in a violation of SR 3.0.4.
i ? l L (continued) g. BRAIDWOOD - UNITS 1 & 2 1.4-2 5/14/98 Revision F _L____-____________--_-__--
l Frequenc
/NSE72-T /-9A
- pay 9 f ~Z I 1~.4 Frequency V
.c dl. EXAMPLES ' EXAMPLE 1.4-2
< (continued)
- g SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY i
L-t verify flow is within limits. Once within 12 hours after i a 25% RTP AND 24 hours thereafter J l ' Example 1.4-2 has two Frequencies. The-first is a one time-performance Frequency, anc 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 A -reactor aower is increased from a power level < 25% RTP to V 2 25% RT), the Surveillance must be performed within 12 hours. , 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 SR 3.0.2.
"Thereafter" indicates future performances must be established per SR 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.
L o [ i. (continued) BRAIDWOOD - UNITS 1'& 2 , 1.4-3 5/14/98 Revision F
-__-_-_-____-_-_-_O
g } Freque l Pa$ t- zo o f 2A) g 7 1.4 Frequency ( .'f ol EXAMPLE 1.4-3
" EXAMPLES (continued)
( SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY NOTE Not required to be performed until , 12 hours after a 25% RTP. 1 l Perform channel adjustment. 7 days The interval continues whether or not the unit operation is
< 25% RTP between performances.
l 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 o' operation is < 25% RTP this Note allows 12 hours after
'U power reaches a 25% RTP to perform the Surveillance. The Surveillance is still considered to be 3erformed within the d "specified Frequency." Therefore. if t1e Surveillance were I not performed within the 7 day (plus the extension allowed
+ by SR 3.0.2) interval, but operation was < 25% RTP, it would
? not constitute a failure of the SR or failure to meet the e- LCO. Also, no violation of SR 3.0.4 occurs when changing
. MODES, even with the 7 day Frequency not met, provided 6 operation does not exceed 12 hours with power a 25% RTP.
Once the unit reaches 25% RTP. 12 hours would be allowed for
) completing the Surveillance. If the Surveillance were not performed within this 12 hour interval, there would then be a failure to perform a Surveillance within the specified Frequency and the provisions of SR 3.0.3 would apply.
(continued) l
,BRAIDWOOD - UNITS 1 & 2 1 4-4 5/14/98 Revision F i i
l
/td56ET /-94 I Frequency f a j t, 2 1 o f *2- ) [
; 1.4 Frequency-
-], ' EXAMPLE 1.4-4 N* EXAMPLES (continued)- g SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY NOTE Only required to be performed in MODE 1. Perform complete cycle of the' valve. 7 days i The interval continues, whether or not the unit operation is in MODE 1. 2. or 3 (the assumed Applicability of the associated LCO) between performances. As the Note modifies the required performance of the Surveillance, the note is construed to be part of the.
"specified Frequency." Should the 7' day interval be
.A . exceeded while operation is not in MODE 1. this Note allows (/ entry into and o)eration in MODES 2 and 3 to perform the Surveillance. Tle. Surveillance is still considered to be performed within the "specified Frequency" if completed prior to MODE 1. Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1. 'it
.a o
would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when
.d changing MODES, even with the 7 day Frequency not met.
provided operation does not result in entry into MODE 1. h Once the unit reaches MODE 1. the requirement for the Surveillance to be performed within its specified Frequency t applies and would require that the Surveillance had been P 3erformed. If the Surveillance were not performed prior to iODE 1. there would then be a failure to perform a Surveillance within the specified Frequency, and the c provisions of SR 3.0.3 would apply. ( BRAIDWOOD - UNITS 1 & 2 1.4-5 5/14/98 Revision F
$pec $ a h n t.t Lco 3.J l
REACTIVITY CONTROL SYSTEMS ,g k'j l SHUTDOWN MARGIN .T,yg < 200*F hg,,g ,, Q. ,, y, , , , See Doc { ,. s' ,+i,,. 74 LIMITING CONDITION FOR OPERATION 3.1.1.2 The SHUTDOWN MARGIN shall be greater than or equal to 1.3% Ak/k. l APPLICABILITY: MODE 5. ACTION:
- a. With the SHUTDOWN MARGIN less than 1.3% Ak/k declare both Boron . 3 Dilution Protection System subsystems inoperable and apply Specifi- I cation 3.1.2.7.b. I
- b. With the SHUTDOWN MARGIN less than 1% Ak/k, immediately initiate and continue boration at greater than or equal to 30 gpm of a solution containing greater than or equal to 7000 ppe boron or equivalent until the SHUTDOWN MARGIN is restored to greater than or equal to 1% Ak/k.
l SURVEILLANCE REQUIREMENTS 4.1.1.2 The SHUTDOWN MARGIN shall be determined to be greater than or equal to 1% Ak/k:
- a. Within I hour after detection of an inoperable control rod (s) and at least once per 12 hours thereafter while the rod (s) is inoperable.
If the inoperable control rod (s) is immovable or untrippable, the guo c,,a SHUTDOWN MARGIN shall be verified acceptable with an increased Mum allowance for the withdrawn worth of the immovable or untrippable control rod (s): and
- b. At least once per 24 hours by consideration of the following factors:
- 1) Reactor Coolant System boron concentration, l 2) Control rod position, 1 l
- 3) Reactor Coolant System average temperature, l
- 4) Fuel burnup based on gross themal energy ~ generation, ,
l
- 5) Xenon concentration, and
- 6) Samarium concentration.
h p- - L ;- A Mreu ~. L A. 3.1. i Qe _ Ooc % See % 3. I BRAIDWOOD - UNITS 1 &'2 3/4'l-3 Amendment No. 40 fUd E
Definib /*/ L Lo 54. lG TARM 4.4-4 (continued) TABLE NOTATIOsts O
# Until the specific activity of the Reactor coolant system is restored' within its limits.
sample to be taken after a minimum of 2 EFPD and 20 days of POWER OPERATION have elapsed since reactor was last suberitical'for 48 hours or longer. A gross radioactivity analysis shall consist of the quantitative measurement of the total specific activity of the reactor coolant except for radionuclides with half-lives less than 10 minutes and all ' radioiodines. The total specific activity shall be the sur. cf tha degassed beta-gamma activity and the total of all identified gaseous activities in the sample within 2 hours after the sample is taken and extrapolated back to when the sample was taken. Determination of the l contributors to the gross specific activity shall be based upon those l energy peaks identifiable with a 95% confidence level. The latest ( available data may be used for pure beta-emittino radionuclides.
*** ' C radiochemical analysis for E shall consist of the quantitative
{ measurement of the specific activity for each radionuclides, except for radionuclides with half-lives less than 10 minutes and all radio-3 j iodines, which is identified in the reactcr coolant. The specific Hio ) activities for these-individual radionuclides shall be used in the determination of E fgr the reactor coolant sample. Determination of
. the contributors to E shall be based upon these energy peaks .O Qantifiablewitha954confidencelevel.
For Unit 1 through cycle 7, reactor coolant DOSE EQUIVALENT I-131 will be limited to 0.35 microcuries per gram. AoldnSScdinSecken ?.Vlla Set 00C WSectim 3 9 O ~ ~ u
'2W BRAIDWOOD - UNITS 1 & 2 Rs4 F 3/4 4-3*. AMENDMENT NO.92
4 DISCUSSION OF CHANGES TO CTS ITS SECTION 1.0 USE AND APPLICATION ADMINISTRATIVE CHANGES (A) A1 All reformatting, renumbering, and editorial rewording is in accordance with.the Westin house Standard Technical Specifications. NUREG-1431. I During the deve opment-certain wording preferences or English language conventions were adopted. As a result. the Technical Specifications (TS) should be more readily readable, and therefore understandable. by 1 plant operators and other users. During the reformatting, renumbering, i and rewording process, no technical changes (either actual or interpretational) to the TS were' made unless they were identified and justified. l Af The CTS ACTUATION LOGIC TEST and CHANNEL OPERATIONAL TEST definitions have been revised to add the phrase "or actual." in reference to the injected signal as a clarification consistent with NUREG-1431. There is no reason why an actual signal would preclude satisfactory verification or performance of an actuation logic test or channel operational test. . Use of an actual signal instead of a simulated signal will not affect the performance of the associated components. ,
. Operability can be adequately demonstrated in either case since the '
associated components can not discriminate between actual or simulated signals. In addition, the definition of ANALOG CHANNEL OPERATIONAL TEST has been revised to delete the word " ANALOG." Both digital and analog
, -channels exist and are subject to channel operational tests. This
,? change makes the definition more accurate and consistent with the equipment in the plant. This is perceived as the intent of the CTS wording, and therefore, the revised wording more accurately reflects this intent and is considered to be administrative. A-3 The CTS ANALOG CHANNEL OPERATIONAL TEST, CHANNEL CALIBRATION. and. TRIP ACTUATING DEVICE OPERATIONAL TEST definitions have been revised to add the word " required" as a clarification consistent with NUREG-1431. As a requirement for operability of a TS channel. not all channels will have a " required" interlock or alarm function. Conversely, some channels may have a required display function. These changes are perceived as the intent of the CTS ~ wording, and therefore, the revised wording more accurately reflects this intent and is considered to be administrative. L In addition, the definition of CHANNEL CALIBRATION has been revised to clarify what encom) asses the " entire" channel, consistent with NUREG- .l
- 1431, as modified )y TSTF-64. As written, the definition would require !
clarification in multiale locations in the Bases or could lead to misinterpretation of tie requirement. i
~ BYRON /BRAIDWOOD UNITS 1 & 2 1.0 1 5/14/98 Revision F r.
L'
DISCUSSION OF CHANGES TO CTS ITS SECTION 1.0 USE AND APPLICATION A, ' The CTS CHANNEL CALIBRATION definition has been revised to add specific - requirements for thermocouple or RTDs consistent with NUREG-1431. The intent of a Channel Calibration is to adjust the channel output so that - the channel responds with known range and accuracy. Most instrument channels contain an adjustable transmitter-(sensor) which is also subject to drift. Thus. for most channels, a Channel Calibration includes adjustments to'the sensor to reestablish proper input / output-relationships. Certain types of sensing elements,. by.their design, construction, and application have' an inherent resistance to drift. They are designed such'that they have a fixed input / output response Lwhich cannot be adjusted or. changed once installed. When a credible mechanism that can cause change or drift. in this fixed response does not exist. it is unnecessary to test them in the~same manner as the other. remaining devices in the channel to demonstrate proper operation. RTDs and thermocouple are sensing elements that. fall into such a category.
'Thus, for these types of sensors. the appropriate calibration at the Frequencies specified in the CTS would consist of a verification of operability of the sensing element and a calibration of the remaining.
adjustable' devices in the channel. Calibration of the adjustable devices in the channel is performed by applying,the sensing elements' (RTDs or thermocou)les) fixed in)ut/ output relationships to the remainder of the clannels and macing the necessary adjustments to ensure
- range and. accuracy.
~
L~ ' The ITS phrase " verification of OPERABILITY" of.the sensing element s (RTDs or thermocouple), as denoted in the Channel Operational Test. is considered to be explicitly defining the currently accepted method for calibration of these instruments. As such, this is perceived as the intent of the CTS wording, and therefore, the revised wording more accurately reflects this intent and is considered to be administrative.
- lA 3 Not used.
~ D BYRON /BRAIDWOOD i UNITS 1 & 2 . 1.0 2' 5/14/98'Rev'ision F XJ- .
)
m_m___m.____._________.__I_____ _ _ . _ _ _ _ _ _ _ _ __ -~m - _ _ - __ _ -. _J
DISCUSSION OF CHANGES TO CTS ITS SECTION 1.0 - USE AND APPLICATION V A3 The CTS IDENTIFIED LEAKAGE. PRESSURE BOUNDARY LEAKAGE, and UNIDENTIFIED LEAKAGE definitions have been combined into one defined term (LEAKAGE). The definitions of each of the categories of. leakage are' consistent with the CTS definitions. If the new. definition is used in new requirements (which is a technical change)'the Discussion Of Changes for the-individual sections of the TS provide the justification. The combining of the definitions is considered administrative, with no impact of its own. This change is consistent with NUREG-1431. A-n The CTS OPERABLE - OPERABILITY definition has been revised to c1arify the electrical power and functional requirements-for declaring
. operability. Specifically, the CTS power" was revised to "necessary ...normal phraseor"necessary emergency electrical ... electrical power" and the CTS phrase "specified function (s)" was revised to "specified safety function (s)" consistent with NUREG-1431. The non-specific' CTS electrical power requi'rement is . intended to be a requirement for only one source of power to be able to declare operability: however, this definition had a history of being both
- " normal and emergency" in older (pre-1980) licensed TS. Similarly, the phrase "specified function" could be misinterpreted to encompass any non-safety function a system may also perform. The non-specific CTS requirement is to clearly address only safety. function (s) of the system.
These additions provide clarification of the current requirements n without any modification of intent, therefore. the revised wording more 1,) accurately reflects this intent and is considered to be administrative. Au The CTS OPERATIONAL MODE - MODE definition has been replaced with a-
' definition of MODE consistent with NUREG-1431. Since their use is interchangeable this change'is considered editorial. The phrase "....
and reactor vessel head closure bolt tensioning specified in Table 1.1-1
> with fuel in the reactor vessel" was'also added to the definition for clarification.- This intent is conveyed by CTS footnote "**" to Table 1.2. The addition of this phrase maintains the consistency with l
. ]g - NUREG-1431 and is .merely an administrative presentation preference.
h lA u Not used. k l. Q BYRON /BRAIDWOOD.- UNITS 1 & 2 l'.04 5/14/98 Revision F p L - _ - _ .
l DISCUSSION OF CHANGES TO CTS ITS.SECTION 1.0 USE AND APPLICATION p%, An The definition of SHUTDOWN MARGIN has been revised to add the phrase "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" consistent with NUREG-1431. ' This requirement to account for RCCAs not capable of being fully inserted was simpTy moved from CTS ~4.1.1.l.1.a and 4.1.1.2.a Additionally. certain wording preferences or English language conventions were adopted which results in no technical changes (either actual or interpretational) to the TS. As.a result.'the TS
. should be more readily readable.~and.therefore understandable, by plant operators as well as other users.
lay The CTS E-BAR - AVERAGE DISINTEGRATION ENERGY definition has been revised.to add the requirement to assure that at least 95% of the total non-iodine _ activity be included consistent with NUREG-1431. The CTS definition requires that E-bar be the weighted average'in proportion to the concentration of each radionuclides. of the sum of the average beta and gamma energies per disintegration for the radionuclides in a sample. The revision explicitly exempts all iodines and' requires that at least-p J 95% of:the total non-iodine activity with half-lives greater .than 10 minutes in the' coolant be included.. This requirement is.specifically denoted in the' CTS Table 4.4-4. Table Notation ***. This revision to the definition provides clarification of the current requirements without any modification of-intent and.provides a reformatting of-existing requirements. The change is a presentation preference which is editorial in nature and does not involve a technical; change (either 2
' actual or interpretational) to the TS. The change;is consistent with NUREG-1431.
lAn Not.used, i l-l c : ! I f, ! J L l l
)/~T' ;%)
BYRON /BRAIDWOOD
/
UNITS'1.& 2 1.0 7. 5/14/98 Revision F L L 1
- x. ,
1
1 DISCUSSION OF CHANGES TO CTS ITS SECTION 1.0 USE AND APPLICATION TECHNICAL CHANGES - RELOCATIONS (R)
.None.
TECHNICAL CHANGES < MORE RESTRICTIVE (M) M1 The CTS SHUTDOWN MARGIN definition has been revised to add the phrase "In MODES 1 and 2, the fuel and moderator temperatures are changed to
- the hot zero power temperature" consistent with NUREG-1431. This requirement ensures that the power defect due to shutting down the reactor from Modes 1 or 2 is accounted for in the' shutdown margin. This requirement is consistent with current practice. However, with the.
adcition of.this requirement to the SHUTDOWN MARGIN definition. it is
- considered more restrictive. -
M2 The CTS Table 1.2 was revised to ' clarify the head closure status and associated coolant temperatures for plant conditions not previously l satisfying a defined MODE or satisfying more than one MODE consistent l l. with NUREG-1431. This included adding the phrase "All reactor vessel
.. ' head closure bolts fully tensioned" as a footnote consistent with
.l NUREG-1431. The footnote would apply to the HOT SHUTDOWN and COLD SHUTDOWN' defined modes. Clarifying the shutdown MODES with a new n footnote eliminates the _ overlap in defined MODES when the temperature is
-Q above 140*F. It is not the intent of- the TS to allow an option of whether to apply REFUELING MODE aaplicable LCOs or to apply shutdown applicable LCOs. Additionally .tle average coolant temperature and associated reactivity condition for the REFUELING mode are replaced with the notation "NA" consistent with NUREG-1431. The CTS definition of REFUELING would cease to be ap)licable when' average coolant temperature exceeded 140 F. By defining t1e REFUELING mode as including plant conditions with no specific coolant temperature range, sufficiently
. conservative restrictions will be applied by the applicable LCOs during all fueled conditions with the vessel bolts detensioned. In addition, the average coolant temperature in MODE 6 is adequately addressed by the .
decay heat removal requirements of ITS LCO 3.9.5 and ITS LC0 3.9.6. In addition. the'140 F temperature requirement has been relocated to the TRM (see Discussion of Change LA in ITS Section 3.9). Moreover, the 1 reactivity condition for this mocfe will be assured by the provisions of _ITS LC0 3.9.1. The intent of these changes is to provide clarity and completeness in avoiding any misinterpretation. and as such could be considered. administrative. However, since this change eliminates the potential to_ interpret certain plant conditions such that no MODE, or a less restrictive MODE would exist, this change is discussed and - justified as a more restrictive change. L. BYRON /BRAIDWOOD UNITS 1-& 2 1.0 8 5/14/98 Revision F 6
Definitions 1.1
' 1'.1 Definitions PHYSICS TESTS-(continued) g a. Described in Ch ter%14,InitialTest Program (ofthG AR;
- b. Authorized under the provisions of 10 CFR 50.59; or
- c. Otherwise approved by the Nuclear Regulatory Commission. {
' PRESSURE AND The PTLR is the unit specific document that 1
. TEMPERATURE LIMITS REPORT (PT h5arl provides the reactor vessel pressure and temperature limitsgincluding heatup and cooldow h
h t.15A] rates,1for the current reactor vessel fluence period. These pressure and temperature limits On f shall be determined for each fluence period _, , accordance with Specification'5.6.6. ,., j ,; -operation within these assmaamr limits is A;:M W\. Aps./-u
]' So a .e . ad3 Fessed in LC0 3.4.3, '"RCS Pressure and +
f f
/
Temperature (P/T) Limits," and LC0 3.4.12, " Low
., 1 Temperature Overpressure Protection (LTOP) y System."
g b: QUADRANT POWER TILT QPTR shall be the ratio of the maximum upper
- RATIO (QPTR) '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 of the lower '
.excore detector calibrated outputs, whichever is greater.
RATED THERMAL POWER RTP shall be a total reactor core heat transfer
. (RTP)' ' rate to the reactor coolant of 43 BUR MWt.
3414 REACTOR TRIP The RTS RESPONSE TIME shall be that time interval
. SYSTEM ~(RTS). RESPONSE from when the monitored parameter. exceeds its RTS
, ; TIME. 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.
SHUTDOWN MARGIN'(50M) SDM shall be the instantaneous amount of reactivity by which-the reactor is subcritical or would be subcritical from its present condition assuming: l (continued) l WOG STS 1.1-5 Rev 1, 04/07/95
~
L
]
LC0 INSERT (S) SECTION 1.0 Definitions 1.1 l INSERT 1.15A (Ps) and the pressurizer Power Operated Relief Valve (PORV) lift settings . O 1 5/14/98 Revision F
Definitions 1.1 Table 1.1-1 (page 1 of 1) Cd MODES
% RATED AVERAGE REACTIVITY THERMA REACTOR COOLANT MODE TITLE CONDITION POWERta(;
TEMPERATURE (k ,) g (*F) 1 Power Operation 1 0,99 >5 NA 2 Startup 2 0.99 s5 NA 3 Hot Standby < 0.99 NA 21350P 4 Hot Shutdown (b) < 0.99 NA $ 50 [> T. ,> T200 f h 5 Cold Shutdown (b) < 0.99 NA s$00f 6 Refueling (c) . NA NA NA 2
]
/
.(a) Excluding decay heat.
(b) All reactor vessel head closure bolts fully tensioned. g _,
'(c) One or more reactor vessel head closure bolts less than fully tensioned. )h v
O; Rev 1, 04/07/95 WOG STS 1.1-7 l
Logical Connectors 1.2 1.2 Logical Connectors . k
. '(].-
i i \ \ s
\ 9 EXAMPLES . EXAMPLE 1.2-1 ,ich chNN 'TORh (continued)
ACTIONS x
\ \
x x
\-
X --
\
3g M % CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not. met. A.1 Verify . . . MQ A.2 Restore . . . In this example the logical connector MQ is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed. yA 4 b t L i l-(continued) ! [b l WOG STS- 1.2-2 Rev 1, 04/07/95 ' l l
i logical Connectors 1.2 l.2 -Logical. Connectors N _\ \ N. i 1 9 uhe pohocht cNousc
' EXAMPLES (continued)'.
EXAMPLE 1.2-2 A L ' N 3 3
* [
st LACTIONS \ -\ \- CONDITION: REQUIRED ACTION COMPLETION TIME A. LCO.not met. A.1 Trip . . . E A . 2 .1.' Veri fy . .. . - Alf A.2.2.1 L Reduce . . . E (- A.2.2.2 Perform . . . L E
] A.3- Align . . .
This example represents a more complicated use of logic' a'l 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. E 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 ANQ. 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 E indicates that ' A.2.2.1 and A.2.2.2 are alternative choices (.only.one of which must be performed. WOG STS4 1.2-3 Rev 1, 04/07/95 l _:_..-_.__2 ________u_---- _ _ '
Completion Times 1.3
.1.3 Completion Times: '(continued)-
EXAMPLES The following examples illustrate.the use of Completion Times _with different types = of Conditions and changing O Conditions. ? o. A N x- c EXAMPLE ~1.3-1 M ohtmht ACTIONS \ ' N i db
._ CONDITION REQUIRED ACTION COMPLETION TIME l
B. - Required - B.1 Be in MODE 3. 6 hours Action and - associated SR Completion Time not B.2 . Be in MODE 5. 36 hours-met. ' D- 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 hours afgl in _ MODE 5.within 36 hours.. A total of
, - 6 hours is allowed for reaching MODE 3 and a total' of 36 hoursthat the-time (notCon 42 dition B was entered. hours)
If MODE is 3allowed for reaching
- is reached i- within ~3_ hours, the~ time allowed for reaching MODE 5 is_ the next-33 hours because the total ^ time ' allowed for ' reaching .
l MODE 5 is 36 hours. , u If Condition B is antered while in MODE 3, the time allowed l for reaching MODE 5 is the next 36 hours. b l li , M y c (continued) l- -:- s L -WOGLSTS. , 1.3-3 Rev I, 04/07/95
Completion Times 1.3
- I.1.3 ~ Completion Times
. ./ v N s y X A n.h EXAMPLES. .. ' EXAMPLE-1.3-2 ~' Ab coh. o,as b 'o.3hTvy/MenchTvnh)f '
-(continued) ' ' '"
ACTIONS \ \ '\ \ \ \ \ CONDITION REQUIRED-ACTION COMPLETION TIME W DR e-A. One pump- A.1 Restore pump to 7 days E inoperable. OPERABLE status. f g B. Required.. B.1 Be in MODE 3. 6 hours Action and associated gg Completion Time not B.2 .Be in MODE 5. .36 hours met.
< -When a pump is declared inoperable, Condition A is entered.
"h' If.the pump is not restored to OPERABLE. status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to CPERABLE status after -
' Condition B is entered, Condition A and B are exited, and
. therefore, the Required Actions of Condition B may be- J
' terminated.
When a second pump is declared inoperable while the first pump is still inoperable, Condition A is- not re-entered for I the second pump. LCO 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 LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered. s ' While.in LCO 3.0.3, if one of the inoperable pumps is i- restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3~.0.3 may be exited and operation' continued in accordance with Condition A. While in LCO 3.0.3, if one of the' inoperable pumps is i
-restored to OPERABLE status and the Completion Time for !
- g. (continued)
- WOG STS- 1.3-4 Rev 1, 04/07/95 l
Compietion. Times 1.3 '.[~ .1.3.' Completion Times - A N N \ .s o
- EXAMPLES EXAMPLE'1.3-3 utTh -ruhuyJ chu nohimes N
1 N x x x
~(continued) e, ACTIONS- \ \ \ \ '
of> b CONDITION . REQUIRED ACTION -COMPLETION TIME A. One
)
A.1 Restore . 7 days j Function X' Function X train j train: to OPERABLE AND inoperable. status. 4 10 days from discovery of failure to meet ' the LCO B. One B.1 Restore 72 hours Function Y. Function Y train
~
train to OPERABLE AtlQ - inoperable.- status. 10 days-from-discovery of u failure to meet a the LCO. i i
, , )
-C. One. C.1 . Restore- 72 hours !
Function X Function X train : train to OPERABLE inoperable. -status. I atiQ 0.8 One C.2 Restore 72 hours Function Y Function Y train : train to OPERABLE inoperable. status. L l L l (continued)
- WOG STS 1.3-6 Rev 1, 04/07/95 1
L ._ _ . _ _ .
l l l- Completion Times '. 1.3 Q i ( 1.3.. Completion Times x
,9 .
! x x x - f l EXAMPLES EXAMPLE 1.3-4 LTih 'NhohJ CkSLErroknMr. N; (continued) l ACTIONS \ \ \ \ \ M 1 CONDITION REQUIRED ACTION COMPLETION TIME ! 4 hours I
. A. One or more A.1 Restore valve (s) valves - to OPERABLE inoperable. status.
\
. B. Required B.1 Be in MODE 3. 6 hours Action and associated MLQ Completion Time not B.2 Be in MODE 4. 12 hours
- l. met.
hr 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. Tha Condition A Completion Time may te extended for up to 4 hours provided this does not result in any subsequent valve being inoperable for > 4 hours.
'If the Completion Time of 4 hours (43g@HB4the extension)
.Odr expires while one or more valves are still inoperab'te, Condition B is entered.
L f g- (continued) 'V WOG STS-1.3-8 Rev 1, 04/07/95
l l l Completion Times 1.3 m 1,3 Completion Times (] . \ \
\_ \ o EXAMPLES . EXAMPLE 1.3-5 pAgh Ethcohtok 14 (continued) . x x x x >4 ACTIONS
\ N N N ,
EG
- l. ----------------------------NOTE----------------------------
Separate Condition entry is allowed for each inoperable valve. L --__________________________________________________________ i
. -CONDITION REQUIRED ACTION COMPLETION TIME A. One or more A.1 Restore valve to 4 hours valves OPERABLE status.
l inoperable. l B. Required B.1~ Be in MODE 3. 6 hours Action and associated AN,0
& ' Completion V Time not B.2 Be in MODE 4. 12 hours met.
i The Note.above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this e.ethod 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, t- Condition A is entered and its Completion Time starts. If l subsequent valves are declared inoperable, Condition A is entered for each valve-and separate Completion Times start and are tracked for each valve. m (continued) U-
.WOG STS 1.3-9 Rev 1, 04/07/95 L __ __ _-_ _ -
Completion Times 1.3-1.3; Completion Times , EXAMPLES EXAMPLE 1-3-5 . (continued)
'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. Since the Note in this example allows multiple Condition entry and tracking;of separate Completion Times, Completion
'. Time extensions do not apply.
N \ -X x EXAMPLE 1.3-6 /PLE M5 wa NAtown @, j ACTIONS- A N x x_ ~ l i CONDITION REQUIRED ACTION COMPLETION TIME
]
N h - A. One channel inoperable. A.1 Perform SR 3 x.x.x. Once per 8 hours g .. 41 E 2. A.2 Reduce THERMAL 8 hours J4 POWER to s 50% RTP. l 1 B. Required B.1 Be~in MODE 3. 6 hours i Action and. associated Completion n Time not met. i
, (continued)
WOG STS 1.3-10 'Rev 1, 04/07/95 ) [ i c__1..nu.___1_ _ _ . _ . _ __ j
Completion Times
. 1.3 1.3 Completion ~ Times q# x s v < s ,
. EXAMPLES _ . . . EXAMPLE 1.3-7 10LD E Acn0Ns rTH /A omou -vi o (continued) . -
1 E Ev usiom ACTIONS. x x x x x I CONDITION REQUIRED ACTION COMPLETION TIME' N
'A. One A.1_ Verify affected I hour p subsystem. - subsystem e inoperable. isolated. M *9g-Once per Tt 8 hours D thereafter -
M. A.2 -Restore subsystem 72 hours to OPERABLE status. B. Required'. B.1 Be in MODE 3. 6 hours
~ Action and associated M.
Completion
. Time not B.2 Be . in MODE 5. 36 hours met.,
. Required Action A.1 has two' Completion Times. The I hour R
' Completion Time begins at the time the Condition is entered I and each "Once per 8 hours thereafter" interval begins upon performance of Required Action A.I.
If after Condition A is entered, Required Action A.1 is not h met within either the initial I hour or any subsequent
'8 hour interval .from the previous performance (plus the :
extension allowed by SR 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 (continued)
~
IWOGSTS , 1.3-12 Rev 1, 04/07/95. i____. _ _ _ . . _ _ . - _ _ _ . _ - - - - _ _ . ]
x Frequency 1.4 1.4 ' Frequency. s N x V 1 4 EXAMPLES (continued)' EXAMPLE 1.4-1 % U M 6 L E M.EhEC h ' 3
' w*d' SURVEILLANCE REQUIREMDiTS
. SURVEILLANCE FREQUENCY Perform CHANNEL CHECK. 12 hours Example 1.4-1.contains the type of SR most often encountered in the Technical Specifications -(TS). The Frequency )
specifies an interval (12 hours) during which the associated I Surveillance.must.be performed at least one time. Performance of the. Surveillance initiates the subsequent interval. , Although the Frequency is stated as 12 hours, an extension of the time interval to 1.25 times the stated Frequency -is allowed by SR 3.0.2 for operational flexibility. ' The measurement of this interval continues at all times, even when the SR is not required to be met per
.: SR 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 LCO). If the interval- specified by SR 3.0.2'is exceeded while the unit is in a MODE or other specified condition in the- Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then SR 3.0.3 becomes applicable.
If the' interval as specified by SR 3.0.2 is exceeded while the. unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR
'is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would
' result in a' violation of SR 3.0.4..
j l
. l (continued) -l ..10; l WOG STS- 1.4 2 Rev 1, 04/07/95 l
Frequency 1.4 l- - ' 1.4LFrequency: 'T
^
N 9 s N o
-EXAMPLES .. EXAMPLE 1.4-2 .. t.T Pb EdD1iddJCIC f
u L (:
'(continued)- .
' SURVEILLANCE REQUIREMENTS ^
x x 'v d4Y SURVEILLANCE FREQUENCY Verify. flow is within limits. Once within
'12 hours:after 2 25% RTP i- i p
M 24 hours thereafter
. Example. l.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. LThe logical connector "M" indicates
'that'both. Frequency requirements must be' met. Each. time LM reactor' power is increased from a. power level < 25% RTP to 1./ 12.25% RTP,- the Surveillance must'be performed within s
12 hours. N The'use of "once" indicates'a single performance will l satisfy the specified Frequency?(assuming no'other-t Frequencies .are connected by "M"). - This type of Frequency. p '_g Udoes "Thereafter" not' qualify indicates for the@Bextension future performancesallowed must'be by SR 3.0.2. p
' established per SR 3.0.2,. butlonly after a specified
.l . . 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.
(continued)
;WOG STS 1.4-3 Rev 1,- 04/07/95 l
_ _ _ ._ _ _ __ __ J
Frequency 1.4 1.4~ Frequency.. N x N N EXAMPLES: EXAMPLE 1.4-3 00D# ASEO MN
^
coMD b ~ l (continued)' '
\ \
~
, ' SURVEILLANCE REQUIREMENTS \
SURVEILLANCE FREQUENCY'
------------------NOTE--------------_- LL\
.Not required to be performed until 3 12 hours after > 25%.RTP. AA
________________~________________________ kj Perform channel adjustment. 7 days
- The interval . continues, .whether or not the unit , operation'is
< 25% RTP'between performances. a 1
A's 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 elj
{-- 1
- operation is. < 25% RTP, this Note allows 12. hours after power reaches 2.25% RTP to perform the Surveillance.. The Surveillance is still considered to be performed within the
.:-e "specified Frequency." Therefore,.if the Surveillance were y not performed within the 7.. day (plus the extension allowed s by SR 3.0.2) interval, but' operation was .< 25% RTP, it would *-
3 P not constitute a failure of the SR or-failure to meet the LCO. Also, no violation _of SR 3.0.4 occurs-when changing j MODES, even with the-7~ day Frequency not met, provided operation does not exceed 12 hours with power 2 25%'RTP.
. Once the-unit. reaches 25% RTP,12 hours would be allowed or=
. completing the Surveillance. If the Surveillance were not performed within this 12 hour interval, there would then be
.a failure.to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply..
C ' eJ ' c + .. f)sett Mew @nmp Cio O
, tw
' *' R
/D 4 , WOG STS i 1.4-4 Rev 1, 04/07/95 _._--.m....____.____.______mm. . _ _ . _ . - . _ _
LC0 INSERT (S) SECTION 1.0' Frequency 1.4 p.L INSERT 1.4 4A1'_(Cw )- U EXAMPLES. EXAMPLE 1.4-4'
- 1 (continued)
- a3 SURVEILLANCE REQUIREMENTS co' SURVEILLANCE FREQUENCY-
~
g - - NOTE-Only required to be performed in MODE.1. Perform complete cycle of the . valve. 7 days The interval continues, whether or not the unit operation is in MODE 1. 2. 'or 3 (the assumed Applicability of the associated LCO) between performances. As the Note modifies.the required performance of the , dp - Surveillance, the note is construed to be part of the "specified Frequen_cy." Should the 7 day interval-be ' . exceeded while operation is not in MODE 1. this Note allows entry into and operation in MODES 2 and 3 to perform the. Surveillance. Th'e Surveillance is still considered to be-1- performed within the "specified Frequency" if completed
. prior to MODE 1. Therefore. if the Surveillance were not performed within the 7 day-(plus the extension allowed by ,
SR 3.0.2). interval._but operation was not'in MODE 1. it' J N .would not constitute a-failure of the SR or failure to meet , .the LCO. Also, no violation of.SR 3.0.4 occurs when I4 changing MODES, even with the 7 day Frequency not met. provided operation does not result in entry into MODE 1. i i
- 4. 10nce the unit reaches MODE 1-. the-requirement for the i: N Surveillance to be performed within its specified Frequency W -
applies and would require that the Surveillance had been
- f aerformed; If the~ Surveillance were not performed prior to iODE 1. there would then be a failure to perform a L
1 Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply 85 q 5/14/98 Revision F E -- -
JUSTIFICATION'FOR DIFFERENCES TO NUREG 1431 SECTION 1.0 USE AND' APPLICATION
- }
BRACKETED' CHANGES (B) B'1 The brackets were removed and optional wording was retained. Bf The brackets were removed and plant specific value or description was added. B3 The brackets were removed and plant specific . details of DOSE EQUIVALENT
!I-131 were retained.
GENERIC CHANGES (C) C-3 .Not used. Cj This change is consistent with NUREG-1431, as modified by TSTF-19 (NRC Lapproved). gC 3 Not used. Y 'Cf.
.Not use'd.
.Y C 3 The Completion Time' Example 1.3-4 has been revised to clarify the use of R the Completio_n Time extension consistent with other examples. The' q . change is proposed primarily for. consistency and.to improve the NJ
_ understanding of the explanations. Similar changes were made to
.NUREG-1431, Revision 0 via approved' generic change BWR-06.' C.3.
Revision 1..and is consistent with NUREG-1433. Revision 1. Cg The Frequency Example 14-2 has been revised to clarify. the use of the Frequency extension. The change is proposed primarily for. consistency-- Mand to improve the understanding of the explanations. Similar changes were made to NUREG-1431,- Revision 0 via approved generic. change.BWR-06.
'C 3,' Revision 1.-and is consistent with NUREG-1433, Revision 1.
J C, - This change is consistent with NUREG-1431. as modified by TSTF-39, Revision 1.
- p C, This change ~ is consistent with NUREG-1431. as modified by TSTF-64.
j l C, -Not used. i[
. BYRON /BRAIDWOOD UNITS 1 & 2 -
1.0 1 5/14/98 Revision F l] i
k JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 ; SECTION 1.0 USE AND APPLICATION
-C 3 : This change. is consistent with NUREG-1431 as modified by WOG-74 g Revision-2. WOG-74 adds an exam)le' of a Surveillance Note that allows
;i. ' for the SR to "Only required to )e performed. . . .". This example O
parallels-the existing example 14-3-of Notes that allow for the SR to _. .Not' required to be performed...". This example will alleviate '
-g . misunderstanding and provide explicit direction for this category of SR l Notes.
C: u Generic' Change TSTF-52 is associated with the inclusion of 10 CFR 50 Appendix J. Option B. This change relocated many of the from the LCOs to a program in ?- . Appendix Speci ficationJ5.5.16.- details As (including a resu L )lt. L, is no longer retained . in the LCO and is- therefore' deleted as a definition even though .not explicitly - included in the TSTF. O L
! BYRON /BRAIDWOOD' UNITS l'& 2 1.0 2 5/14/98 Revision F L .
u___.____.___..__
l.
~ JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 i SECTION 1.0 USE AND APPLICATION L] PLANT SPECIFIC CHANGES (P)
P3 During the development certain wording preferences. English language conventions, reformatting, renumberin , or editorial ~ rewording o (i consistent with plant specific nomenc ature were ado ted, As a result,
- the Technical Specifications (TS) should be more rea ily readable by..
- and.therefore understandable to. plant operators and other users.
I' 9
~~
During this reformatting, renumbering, and rewording process, no technical changes (either actual-or interpretational) were made to the It .TS unless they were identified and justified. L E l: Lj P, Not used. l P3 Not used. P,. Not used. I P3 The Low Temperature Overpressure Protection enable temperature is
. included in the PTLR definition consistent with the CTS (which
! incorporated this item in recent Amendment Nos 89 and 98 for Braidwood L and Byron respectively). O l , 1 BYRON /BRAIDWOOD UNITS 1 & 2 1.0-3 5/14/98 Revision F i l
SLs 2.0 2.0 SAFETY LIMITS (SLs) 2.1 SLs I 2.1.1 Reactor Core SLs In MODES 1 and 2. the combination of THERMAL POWER Reactor Coolant System (RCS) highest loop average temperature, and
]ressurizer pressure shall not exceed the SLs specified in rigure 2.1.1-1.
2.1.2 .RCS Pressure SL In MODES 1. 2. 3. 4. and 5. the RCS pressure shall be maintained s 2735 psig. 2.2 SL Violations 2.2.1 If SL 2.1.1 is violated, restore compliance and be in MODE 3 within I hour. 2.2.2 If SL 2.1.2 is violated: 2.2.2.1 In MODE 1 or 2. restore compliance and be in MODE 3 within 1 hour. 2.2.2.2 In MODE 3. 4. or 5. restore compliance within 5 minutes. O BYRON - UNITS 1 & 2 2.0-1 6/30/98 Revision A
1 SLs 2.0 000 i 070
- 2471 psia l
w 600 '
= <
}
- D Q p50 psia
= 650 -
5 H G40
-ta
\
psia 630 - N t 620 \ 8 x x G10 (% ' x N
.V 600 ,
g g c>
=
500 l' 500 . 0 20 40 GO 80 100 120 1 i Ej PERCENT OF RATED TIIERMAL POWER di N l g Figure 2.1.1-1 (page 1 of 1) Reactor Core Safety Limits l-h , BYRON'- UNITS.' 1 & 2 2.0-2 5/14/98 Revision F l l
Reactor Core SLs B 2.1.1 B 2.0 -SAFETY LIMITS.(SLs) B 2.1.1- Reactor Core SLs , BASES BACKGROUND. GDC 10 (Ref.~ 1) requires that specified acceptable fuel design limits are not exceeded during steady state i . operation, normal operational transients, and Anticipated f Operational Occurrences (A00s). This is accomplished by having a Departure from Nucleate Boiling (DNB) design basis, which corresponds to a 95% probability at a 95% confidence level (the 95/95 DNB criterion) that DNB will not occur and by requiring that_ fuel _ centerline temperature stays below the melting temperature. l- The restrictions of this SL' prevent overheating of the fuel i and cladding. as well as possible cladding perforation, that l: would result in the release of fission products to the reactor coolant. Overheating of the. fuel-is prevented by maintaining the steady state peak Linear Heat Rate (LHR)
.below the_ level at which fuel centerline melting occurs.
Overheating of the fuel cladding is prevented by restricting l: fuel operation to within the nucleate boiling regime. where .
# the heat transfer coefficient is large and the cladding surface temperature is slightly above the coolant saturation temperature.
l Fuel centerline melting occurs when the local LHR, or powe~r 1 peaking, in a region of the_ fuel is high enough to cause the fuel centerline temperature to reach the melting point of the fuel. Expansion of the pellet upon centerline melting
' may cause the pellet to stress the cladding to the point of L failure, allowing an uncontrolled release of activity to the L reactor coolant, i
O
%.J L BYRON - UNITS 1 & 2 B 2.1.1 - 1 6/15/98 Revision A I t
l
Reactor Core SLs
. B 2.1.1 BASES O BACKGROUND (continued)
Operation above the boundary of the nucleate boiling regime could result in excessive cladding temperature because of the onset of DNB and the resultant sharp reduction in. heat transfer coefficient. Inside~ the steam film high cladding temperatures are reached and a cladding water (zirconium water) reaction may take alace. This chemical reaction results in oxidation of tie fuel cladding to a structurally weaker form. This weaker form may lose its integrity. resulting in an uncontrolled release of activity to the reactor coolant. The proper functioning of the Reactor Protection System (RPS) and Main Steam Safety Valves (MSSVs) prevents violation of the reactor core SLs. APPLICABLE The fuel cladding must not sustain damage as a result of SAFETY ANALYSES normal o)eration and A00s. The reactor core SLs are established to preclude violation of the following fuel design criteria: Og a. The hot fuel pellet in the core must not experience centerline fuel melting; and 0 8
- b. There must be at least 95% probabi'lity at a 95%
O confidence level (the 95/95 DNB criterion) that the hot fuel rod in the core does not experience DNB. N hl The Reactor Trip System setpoints (Ref. 2) specified in g LCO 3.3.1. " Reactor Trip System (RTS) Instrumentation." in combination with all the LCOs, are designed to prevent any anticipated combination of transient conditions for Reactor Coolant System (RCS) highest 100) average temperature. pressurizer pressure, and THERMA POWER level that would result in a Departure from Nucleate Boiling Ratio (DNBR) of less than the DNBR limit and preclude the existence of flow instabilities. O BYRON - UNITS 1 & 2 B 2.1.1 - 2 6/15/98 Revision F
l Reactor Core SLs B 2.1.1
/ BASES d- 3 APPLICABLE SAFETY ANALYSES (continued) l Automatic enforcement of these reactor core SLs is provided by the following functions (Ref. 2):
- a. Pressurizer Pressure - high trip:
Pressurizer Pressure - low trip: b.
- c. Overtemperature AT trip;
- d. Overpower AT trip:
- e. Power Range Neutron Flux trip:
I
- f. Low reactor coolant flow trip; and
- g. Main steam safety valves.
Additional trip functions are provided to backup these functions for specific abnormal conditions. The limitation that the average enthalpy in the hot leg be (q
'j less than or equal to the enthalpy of saturated liquid also ensures that the AT measured by instrumentation, used in the RPS design as a measure of core power. is. proportional to core power.
The SLs represent a design requirement for establishing the RPS trip setpoints identified previously. LCO 3.4.1. "RCS l Pressure. Temperature, and Flow Departure from Nucleate Boiling (DNB) Limits." or the assumed initial conditions of the safety analyses provide more restrictive limits to ensure that the SLs are not exceeded.
-SAFETY LIMITS Figure B 2.1.1-1 shows an example of the reactor core safety limits of THERMAL POWER. RCS pressure, and average temperature for which the minimum DNBR is not less than the safety analyses limit, that fuel centerline temperature remains below melting. that the average enthalpy in the hot leg is less than or equal to the enthalpy of saturated liquid, or that the core exit quality is within the limits defined by the DNBR correlation.
i k BYRON - UNITS 1 & 2 B 2.1.1 - 3 6/15/98 Revision A
--------------- o
Reactor Core SLs ' B 2.1.1 BASES SAFETY LIMITS (continued) The curves are typically derived based on enthalpy hot channel factor limits such as those provided in the COLR. The dashed line of Figure B 2.1.1-1 shows an example of a limit curve at 2235 psig. In addition, it illustrates the various RPS functions that-are designed to prevent the unit from reaching the limit. The SL is higher than the limit calculated when the Axial Flux Difference (AFD) is within-the limits of the F (AI)^ function of the Overtemperature AT reactor trip. Wbenthe AFD is not within the tolerance, the AFD effect on the Overtemperature AT reactor trips will reduce the setpoints to provide protection consistent with the reactor core SLs (Refs. 3 and 4). -
. APPLICABILITY SL 2.1.1 only'a) plies in MODES 1 and 2 because these are the '
only MODES'in w11ch the reactor is critical. Automatic , 3rotection functions are required to be OPERABLE during i
;10 DES 1.and 2 to ensure operation within the reactor core SLs. The MSSVs or automatic protection actions serve to LO JV prevent RCS heatup to the reactor core SL conditions or to initiate a reactor trip function, which forces the unit into-MODE 3. Setpoints for the reactor trip functions are specified in LC0 3.3.1. In N0 DES 3. 4, 5. and 6.
Applicability is not required since the reactor is not generating significant THERMAL POWER. SAFETY LIMITS If SL 2.1.1 is violated, the requirement to go to MODE 3 VIOLATIONS places the unit in a MODE in which this SL is not applicable.
)
The allowed Completion Time of I hour recognizes the I importance of bringing the unit to a MODE of o)eration where this SL is not applicable. and reduces the pro) ability of
- l. -fuel damage.
u BYRON'- UNITS.1 & 2 B 2.1.1 - 4 6/15/98 Revision A
Reactor Core SLs B.2.1.1 j D BASES
.,L]
REFERENCES- 1. 10 CFR 50. Appendix A. GDC 10.
- 2. UFSAR. Section 7.2.
- 3. WCAP-8746-A. March 1977.
- 4. WCAP-9273-NP-A. July 1985.
l { l O l r i l t l i O BYRON - UNITS 1 & 2 B 2.1.1 - 5 6/15/98 Revision A
Reactor Core SLs B 2.1.1 f',- NJ ' 680 ; ., ,
< 1 l
} I i DO NOT OPERATE OT DELTA T I OP DELTA T IN THIS AREA 660 g
y J/ l 4 3 ABOVE AND TO THE { t RIGHT OF LINES b
- i ,
2235 PSIG
,,% NUCLEAR
, g' OVERPOWER 640
,~ ,
%g
\
C 620 \, e y 600 ;
\ x
- O
" S/G SAFETY VALVES g\\
580 \ I \ ACCEPTABLE OPERATION l 560 540 FOR ILLUSTRATION ONLY. DO NOT USE FOR OPERATION. 520 ! I l 0 20 40 60 80 100 120 PERCENT OF RATED THERMAL POWER (%) i Figure B 2.1.1-1 (page 1 of 1) l Reactor Core Safety Limits vs. Boundary of Protection !
/G d
BYRON'- UNITS 1 & 2 B 2.1.1 - 6 6/15/98 Revision A L____________. i
E RCS Pressure SL B 2.1.2 lz i
)("T B 2.0 SAFETY LIMITS (Sli) v B-2.1.2 Reactor Coolant System (RCS) Pressure SL l
BASES ~- BACKGROUND _The SL on RCS pressure protects the integrity of the RCS against overpressurization. In the event of fuel cladding failure, fission products are released into the reactor coolant. The RCS then serves as the primary barrier in preventing the release of fission products into the atmosphere. By establishing an upper limit on RCS pressure. the continued integrity of _ the RCS is ensured. According to
.10 CFR 50. Appendix A. GDC 14. " Reactor Coolant Pressure Boundary." and GDC 15, " Reactor Coolant System Design" (Ref. 1), the Reactor Coolant Pressure Boundary (RCPB) design conditions are not to be exceeded'during normal operation and Anticipated Operational Occurrences (A00s).
Also, in accordance with GDC 28; " Reactivity Limits" (Ref.1) reactivity accidents. including rod ejection. do not result .in damage to the RCPB greater than limited local yielding. js The design pressure of the RCS is 2500 psia. During normal y\ o>eration and A00s. RCS pressure is limited from-exceeding-t1e design pressure by more than 10%, in accordance with SECTION III of the ASME Code.(Ref. 2). To ensure system integrity, all RCS components are hydrostatically tested at 125% of design pressure, according to the ASME Code requirements prior to initial operation when there is no fuel in the core. Following inception of unit operation. RCS components are pressure tested in accordance with the requirements of the approved ISI/IST Program which is based on ASME Code. SECTION XI (Ref. 3). l Over) pressurization of the RCS could result in .a breach of the RCPB reducing the number of protective barriers-designed to prevent radioactive releases from exceeding the limits specified in 10 CFR 100. " Reactor Site Criteria" (Ref. 4). If such a breach occurs in conjunction with a fuel cladding i failure, fission products could enter the containment l atmosphere. BYRON - UNITS 1 & 2 , B ~ 2.1. 2 - 1 6/15/98 Revision A ______ - . _ _ i
RCS Pressure SL B 2.1.2 p' v BASES APPLICABLE The pressurizer safety valves. the Main Steam Safety SAFETY ANALYSES Valves (MSSVs), and the Pressurizer Pressure-High trip have settings established to ensure that the RCS pressure SL will not be exceeded. The RCS pressurizer safety valves are sized to prevent system pressure from exceeding the design 3ressure by more than 10%. as s)ecified in SECTION III of tie ASME Code for Nuclear Power )lant Components (Ref. 2). The transient that establishes the required relief capacity, and hence valve size requirements and lift-settings, is a complete loss of external load without a direct reactor trip. During the transient, no control actions are assumed, except that the MSSVs are assumed to open when the steam pressure reaches the safety valve settings, and nominal feedwater supply is maintained (Ref. 5). The Reactor Trip System setpoints. together with the settings of the MSSVs. provide pressure protection for normal operation and A00s. The Pressurizer Pressure-High trip setpoint is specifically set to provide protection against overpressurization (Ref. 6). The safety analyses
,, for both the high pressure trip and the pressurizer safety ~ (J valves are performed using conservative assumptions relative to pressure control devices (Ref. 5).
More specifically. no credit is taken for operation of the following:
- a. Pressurizer power operated relief valves;
- b. Steam Generator (SG) power operated relief valves;
- c. Steam Dump System;
- d. Reactor Control System;
- e. Pressurizer Level Control System: or
- f. Pressurizer spray valves.
l i t
)
)
O V BYRON - UNITS 1 & 2 B 2.1.2 - 2 6/15/98 Revision A l l l ) l a
RCS Pressure SL B 2.1.2 73 BASES U SAFETY LIMITS The maximum transient pressure allowed in the RCS pressure vessel, pressurizer, and the RCS piping, valves, and fittings under the ASME Code. SECTION III. is 110% of design pressure. Therefore, the SL on maximum allowable RCS pressure is 2735 psig. APPLICABILITY SL 2.1.2 applies in. MODES 1. 2. 3, 4. and 5 because this SL could be approached or exceeded in these MODES due to overpressurization events. The SL is not applicable in
- h. MODE 6 because the reactor vessel head closure bolts are not fully tightened, making it unlikely that the RCS can be 1 pressurized.
D N
'N .l SAFETY LIMIT If SL 2.1.2. "RCS Pressure SL." is violated when the reactor
@ VIOLATIONS is in MODE 1 or 2. the requirement is to restore compliance and be. in MODE 3 within 1 hour.
Exceeding the RCS pressure SL may cause immediate RCS failure and create a potential for radioactive releases in n excess of 10 CFR 100. " Reactor Site Criteria." limits if s (Ref; 4). The allowable Completion Time of 1 hour recognizes the importance of reducing power level to a MODE of operation where the potential for challenges to safety systems is minimized. If the Completion Time is exceeded, actions shall continue in order to restore compliance with the SL and bring the unit to MODE 3. L I r
'J '
BYRON'- UNITS'1 & 2 B 2.1.2 - 3 6/15/98 Revision F
RCS Pressure SL B 2.1.2 p BASES SAFEfY _IMIT VIOLATIONS (continued) l ' If SL 2.1.2 is exceeded in MODE 3. 4. or 5. RCS pressure must be restored to within the SL value within 5 minutes. Exceeding the RCS pressure SL in MODE 3. 4. or 5 is more' severe than exceeding this SL in MODE 1 or 2. since the reactor vessel temperature may be lower and the vessel i material, consequently, less ductile. As such pressure i must be reduced to less than the SL within 5 minutes. If the Completion Time is exceeded, actions shall continue in l order to reduce pressure to less than the SL. The action l does not require reducing MODES, since this would require reducing temperature, which would com30und the problem by adding thermal gradient stresses to t7e existing pressure stress. REFERENCES 1. 10 CFR 50. Appendix A. GDC 14. moc 15. and GDC 28.
- 2. ASME. Boiler and Pressure Vessel Code. SECTION III.
Article NB-7000.
,q 3. . ASME. Boiler and Pressure Vessel Code SECTION XI.
V 4. 10 CFR 100.
- 5. UFSAR. Section 5.2.2.
- 6. UFSAR. Section 7.2.
BYRON - UNITS 1 & 2 B 2.1.2 - 4 6/15/98 Revision A
SLs 2.0 2.0 SAFETY LIMITS (SLs) 2.1 SLs 2.1.1 Reactor Core SLs In MODES I and 2. the combination of THERMAL POWER Reactor Coolant System (RCS) highest loop average temperature, and pressurizer pressure shall not exceed tne SLs specified in Figure 2.1.1-1. 2.1.2 PCS Pressure SL E In MODES 1. 2. 3. 4. and 5. the RCS pressu e shall be maintained s 2735 psig. 2.2 SL Violations E 2.2.1 If SL 2.1.1 is violated. restore compliance and be in MODE 3 within 1 hour. 2.2.2 If.SL 2.1.2 is violated: 2.2.2.1 In MODE 1 or 2. restore compliance and be in MODE 3 within 1 hour. 2.2.2.2 In MODE 3. 4. or 5. restore compliance within 5 minutes. BRAIDWOOD - UNITS 1 & 2 2.0-1 6/30/98 Revision A
i SLs ! 2.0 \ 680 I l
.Of. l 070 .-,
471 psia .
S. L l '
.m -GGO
.=
D' H' 3 2250 psia i, g G50 ,
=
O' H. 640 % 1 w. g psia I 83 x s ps o 620_ N l-o 1 H
$ 610
=
0
't} - 5 g99 N
.x 590 N- 560 C -- 0: 20 40 00 80 '100 120
) Q PERCENT OF RATED TIIERMAL POWER f' s ' Figure 2.1.1-1 (page 1 of 1) Reactor Core Safety Limits I
~BRAIDWOOD - UNITS 1~& 2 2.0-2 5/14/98 Revision F l
l A __a -
Reactor Core SLs B 2.1.1 '0 l 3 9.0 SAFETY. LIMITS (SLs) B 2.1.1 Reactor. Core SLs-
. BASES 1
BACKGROUND; GDC 10 (Ref.1) requires that specified acceptable fuel design limits are not exceeded during steady state l operation.-normal operational transients, and Anticipated Operational Occurrences (A00s). This is accomplished by having a Departure from Nucleate Boiling (DNB) design basis. L which corresponds to a 95% probability at- a 95%. confidence level (the. 95/95 DNB criterion) that DNB will not occur and by requiring that fuel centerline temperature stays below the melting temperature. l The restrictions of. this SL prevent overheating of the fuel and cladding, as well as possible cladding perforation, that would result in the release of fission products to the reactor coolant. Overheating of the fuel is prevented by maintaining the steady state peak Linear Heat Rate (LHR) below the level at which fuel centerline melting occurs. Overheating of .the fuel cladding is prevented by restricting fuel operation to within the nucleate boiling regime, where t' the heat transfer coefficient ~ is large and the cladding surface temperature is slightly above the coolant saturation temperature. ( Fuel' centerline melting occurs when the local LHR, or power. peaking, in a region of the fuel is high enough to cause the fuel centerline temperature to reach the melting _ point of the fuel. -Expansion of the pellet upon centerline melting may cause the pellet to stress the cladding-to the point of failure, allowing an' uncontrolled release of activity to the reactor coolant. 1 1
. BRAIDWOOD - UNITS 1.& 2 B 2.1.1 - 1 6/15/98 Revision A
Rtactor Core SLs B 2.1.1
- 7. 3 BASES
- I BACKGROUND (continued)' l Operation aboveLthe boundary of the nucleate boiling regime could result in excessive cladding temperature because of the onset of DNB and the resultant sharp reduction in heat transfer coefficient. Inside the steam film, hich cladding temperatures are reached, and a cladding water (zirconium water) reaction may take ) lace. This chemical reaction results in oxidation of t1e fuel cladding to a structurally weaker form. This weaker form may lose its integrity.
resulting in an uncontrolled release of activity to the reactor coolant.
- The proper functioning of the Reactor Protection System (RPS) and Main Steam Safety Valves (MSSVs) prevents violation of the reactor core SLs.
APPLICABLE . The fuel cladding must not sustain damage as a result of SAFETY ANALYSES normal o)eration and A00s. The reactor core SLs are established to preclude violation of the following fuel design criteria: l ' (~5 a. The hot fuel pellet in the core must not experience V centerline fuel melting; and oJ 0
- b. There must be at least 95% probability at a 95%
confidence level (the 95/95.DNB criterion) that the f . hot fuel rod in the core does not experience DNB. N T The Reactor Trip System setpoints (Ref. 2) specified in - R LCO 3.3.1, " Reactor Trip System (RTS) Instrumentation." in-j combination with all the LCOs, are designed to prevent any anticipated combination of transient conditions for Reactor Coolant System (RCS) highest loo) average temperature, i' pressurizer 3ressure. and THERMA _ POWER level that would result in a Jeparture from Nucleate Boiling Ratio (DNBR) of less than the DNBR limit' and preclude the existence of flow instabilities. l f BRAIDWOOD - UNITS 1 & 2 B 2.1.1 - 2 6/15/98 Revision F i
Reactor Core SLs I B 2.1.1 y BASES APPLICABLE SAFETY ANALYSES (continued)
. Automatic enforcement of these reactor core SLs is provided by the following functions (Ref. 2):
.a. Pressurizer Pressure - high trip;
- b. Pressurizer Pressure - low trip:
- c. Overtemperature.AT trip:
- d. Overpower AT trip:
- e. Power Range' Neutron Flux trip: .i
- f. - Low reactor coolant flow trip; and 9 Main steam safety valves'.
Additional trip functions are provided to backup these functions for specific abnormal conditions. The limitation that the average enthalpy-in the hot leg be l less than or equal to the enthalpy of saturated liquid also ensures that the AT measured by instrumentation, used in the . RPS. design as a measure of core power, is proportional to
-core power.
, The SLs represent a design requirement for establishing the-RPS trip.setpoints . identified previously. LC0 3.4.1, "RCS l Pressure. Temperature, and Flow Departure from Nucleate j Boiling (DNB) Limits,'" or the assumed initial conditions of i the safety analyses provide more restrictive limits _to ensure that the SLs are not exceeded. SAFETY: LIMITS Figure B 2.1.1-1 shows an example of the reactor core safety limits of THERMAL POWER, RCS pressure, and average temperature for which the minimum DNBR is not less than the safety analyses limit, that fuel centerline temperature remains below melting, that the average enthalpy in the hot leg is-less-than or equal to the enthalpy of saturated liquid, or that the core exit quality is.within the limits defined by the DNBR correlation. OL BRAIDWOOD - UNITS 1 & 2 ' B' 2.1.1 - 3 6/15/98 Revision A i
Reactor Core SLs l B 2.1.1 l BASES (]- SAFETY LIMITS (continued) The curves are typically derived based on enthalpy hot channel factor limits such as those provided in the COLR. ; The dashed line of Figure B 2.1.1-I shows an example of a limit curve at 2235 psig. In addition. it illustrates the vari.ous RPS functions that are designed to prevent the unit from reaching the limit. The SL is higher than the limit calculated when the Axial ! Flux Difference (AFD) is within the limits of the F (AI) function of the Overtemperature AT reactor trip. Wbenthe AFD is not within the tolerance. the AFD effect on the i Overtemperature AT reactor trips will reduce the setpoints l to provide protection consistent with the reactor core SLs 1 (Refs. 3 and 4). APPLICABILITY SL 2.1.1 only a) plies in MODES 1 and 2 because these are the only MODES in w1ich the reactor is critical. Automatic l protection functions are required to be OPERABLE during ' MODES 1 and 2 to ensure operation within the reactor core SLs. The MSSVs or automatic protection actions serve to f) '/ ~ prevent RCS heatup to the reactor core SL conditions or to initiate a reactor trip function which forces the unit into MODE 3. Setpoints for the reactor trip functions are specified in LCO 3.3.1. In MODES 3. 4. 5. and 6. ! Applicability is not required since the reactor is not generating significant THERMAL POWER. SAFETY LIMITS If SL 2.1.1 is violated. the requirement to go to MODE 3 VIOLATIONS places the unit in a MODE in which this SL is not applicable. The allowed Completion Time of 1 hour recognizes the importance of bringing the unit to a MODE of operation where this SL is not applicable, and reduces the pro) ability of fuel damage. I l v. l BRAIDWOOD - UNITS 1 & 2 B 2.1.1 - 4 6/15/98 Revision A L_ _____-__
Reactor Core SLs B 2.1.1 BASES REFERENCES 1. 10 CFR 50. Appendix A. GDC 10.
- 2. UFSAR. Section 7 2.
- 3. WCAP-8746-A. March 1977.
! 4. WCAP-9273-NP-A. July 1985. i i l(/ l l l l I O BRAIDWOOD - UNITS 1 & 2 B 2.1.1 - 5 6/15/98 Revision A
I i Reactor Core SLs B 2.1.1 s .U l l l 680 i 1
! DO NOT OPERATE OT DELTA T OP DELTA T l lN THIS AREA i~
660 g J/ 4 3 { ABOVE AND TO THE !
; RIGHT OF LINES r l '
i
,' l 2235 PSIG j 3
- 640
, p j y'
NU C LE A R--+ OVERPOWER y ~,,, l l
%g s
C 620 , e m 600 ' s x
- O h S/G SAFETY VALVES 580
'y l \
V .
^
560 I i 540
^
FOR ILLUSTRATION ONLY. DO NOT USE FOR OPERATION. 520 I I I O 20 40 60 80 100 120 PERCENT OF RATED THERMAL POWER (%) Figure B 2.1.1-1 (page 1 of 1) Reactor Core Safety Limits vs. Boundary of Protection d(M .
- BRAIDWOOD - UNITS 1 & 2 B 2.1.1 - 6 6/15/98 Revision A
RCS Pressure SL B 2.1.2 B 2.0' SAFETY LIMITS (SLs) O)
\.
B'2.1.2 Reactor. Coolant System ',RCS) Pressure SL BASES BACKGROUND The SL on RCS pressure protects the integrity of the RCS against overpressurization. In the event -of fuel cladding failure.. fission products are released-into the reactor coolant. The RCS then serves as the primary barrier in preventing.the release of fission products into the atmosphere. By establishing an upper limit on RCS pressure, the continued integrity of the RCS .is ensured. According to-10 CFR.50. Appendix A. GDC 14. " Reactor Coolant Pressure Boundary." and GDC 15. " Reactor Coolant System Design" (Ref.1), the Reactor Coolant Pressure Boundary. (RCPB) design conditions are not to be exceeded during normal operation and Anticipated Operational Occurrences (A00s). Also, in accordance with GDC 28. " Reactivity Limits" (Ref.1), reactivity accidents. including rod ejection. do not result in damage to the RCPB greater than limited local yielding. The design pressure of the RCS is 2500 psia. During normal
.O.
D. c o)eration and A00s. RCS pressure is limited from exceeding t1e design pressure by more than 10%. in accordance with i SECTION III of the ASME Code (Ref. 2). To ensure system integrity all RCS components are hydrostatically tested at 125% of design pressure.:according to the ASME Code requirements prior to. initial operation when there is no fuel in the core Following inception of unit operation.
-RCS components are pressure tested in accordance with the requirements of the approved ISI/IST Program which is based I
on ASME Code. SECTION XI (Ref. 3). Over) pressurization of the RCS could result in a breach of the TCPB reducing the number of protective barriers designed
.to prevent radioactive releases from exceeding the limits specified in 10 CFR 100. " Reactor Site Criteria" (Ref. 4).
If such a breach occurs in conjunction with a fuel cladding failure, fission products could enter the containment atmosphere. l l !
)
i O i BRAIDWOOD - UNITS 1 & 2 B 2.1.2 - 1 6/15/98 Revision A
RCS Pressure SL B 2.1.2 pD BASES APPLICABLE The pressurizer safety valves the Main Steam Safety . SAFETY ANALYSES ' . Valves (MSSVs). and the Pressurizer Pressure-High trip have settings. established to ensure that the RCS pressure SL will not be exceeded. The RCS pressurizer safety valves are sized to prevent system pressure from exceeding the design )ressure by more than 10%. as saecified in SECTION III of tle ASME Code for Nuclear Power )lant Components (Ref. 2). The transient that establishes the required relief capacity, and' hence valve size requirements and lift settings, is a complete loss of external. load without a direct reactor trip. During the transient no control actions are assumed except that the MSSVs are assumed to open when the steam pressure reaches the safety valve settings, and nominal feedwater supplyis maintained (Ref. 5). The Reactor Trip System setpoints. together with the' settings of the MSSVs. provide pressure protection for normal operation and A00s. The Pressurizer Pressure-High trip setpoint is specifically set to provide protection against overpressurization (Ref. 6). The safety analyses for both the high' pressure trip and the pressurizer safety .OM valves are performed using conservative assumptions relative to pressure control devices (Ref. 5). More specifically, no credit is taken for operation of the I following: '
- a. Pressurizer power operated relief valves:
a b, Steam Generator (SG) power operated relief valves:
- c. Steam Dump System: I
- d. Reactor Control System:
- e. Pressurizer Level Control System: or i
- f. Pressurizer spray valves. H l-i l
[ i O l
.BRAIDWOOD'- UNITS 1 & 2 B 2.1. 2 - 2 6/15/98 Revision A
_.____.________s
r -.: s RCS Pressure'SLI B 2.1.2. BASESi f5 ,
-{
MU - SAFETY LIMITS LThe maximum transient pressure allowed in the'RCS pressure vessel. pressurizer, and the RCS piping, valves. and
. fittings.under the ASME Code SECTION 'III~ is 110% of design
- pressure. Therefore., the SL on maximum allowable RCS pressureis2735lpsig.
APPLICABILITY : SL 2;1.2 applies in MODES 1, 2, 3. 4 and 5 because this SL could be approached or exceeded in these' MODES: due to overpressurization events. The SL is-not.' applicable-in MODE 6 because the reactor vessel head closure bolts are not-
. to Lfully tightened. making it unlikely that the RCS.can be j, pressurized.
LO: 4 M F SAFETY LIMITt If SL 2.l.2. "RCS Pressure SL." is violated when the reactor 6 : VIOLATIONS is in MODE 1 or 2.~ the requirement is-to restore compliance and be in MODE:3 within 1 hour.
,j Exceeding the.RCS pressure SL may cause immediate RCS failure and create a potential for radioactive releases in V~N excess of 10 CFR 100. " Reactor Site Criteria ~ " : limits d (Ref.,4).
ga ^ The" allowable. Completion Time of 1' hour recognizes the -
, importance of reducing power level to a MODE of operation
~
where the potential for challenges to safety' systems 11s
' minimized; 'If the Completion Time is exceeded, actions
. shalls continue in order to restore compliance with the,SL and bring'the unit,to' MODE 3.
a , 1 & J. f9 _ BRAIDWOOD7- UNITS 1 &'2-
. B 2.1.2 - 3 .
.6/15/98 Revision F
-{'.
( RCS Pressure SL B 2.1.2 (3 BASES ' O : SAFETY LIMIT VIOLATIONS (continued) If SL 2.1.2 is exceeded in MODE 3. 4. or 5. RCS pressure ! must be restored to within the SL value within 5 minutes. Exceeding the RCS pressure SL in MODE 3. 4, or 5 is more i severe than exceeding this SL in MODE 1 or 2, since the ! reactor vessel temperature may be lower and the vessel material, consequently, less ductile. As such, pressure must be reduced to less than the SL within 5 minutes. If the Completion Time is exceeded, actions shall continue in order to reduce pressure to less than the SL. The action does not require reduci'ng MODES. since this would require reducing temperature, which would comaound the problem by adding thermal gradient stresses to t1e existing pressure stress. , REFERENCES 1. 10 CFR 50, Appendix A GDC 14. GDC 15, and GDC 28,
- 2. ASME. Boiler and Pressure Vessel Code. SECTION III.
Article NB-7000. fw 3. ASME, Boiler and Pressure Vessel Code. SECTION XI. I \ V 4. 10 CFR 100.
- 5. UFSAR. Section 5.2.2.
- 6. UFSAR. Section 7.2
\ )
BRAIDWOOD - UNITS 1 & 2 82.1.2-4 6/15/98 Revision A
S t. 2.o l A' 680 . . .
. . . . . . . . . . . . l l
1._ . 670 i
.3411.
pels .* . . .'
., . . . . . . ..,.,. . 3.,.,,. . . ... . . . 3 . c ... ...
i . 4 660- . . . l i
.*1*t* l 33.'S'Q* . . pgg,g .t *. r .* .*
* * * *.* % -
- r *.* *.* - *1*t*r* l
- w. . . . . . . . . . . . .. l 650 .
. .. l g -. . .
r .- - .1r-r..-- ,. t .- - j m . . . . . . . . . . . C . . . . . . . . . . .
. . . .. g.
3 . . . . . . . .
. .. h.
! 2.0.0.0. PF M
] ;. . .. ;. . ;. .. .; . f . , . .;. .' . { . . ;. .;..;.. .. . ;. .
1 630
\... . .
. . 3 . . .
3 . . . Wiri.sm -:- i- - :- .
--:-i-i- --
-i-i-:-
f2 620
. . . . . A. . .
. g.
3 g
. . . . . . . .. 1
>.s.
g> . .. . . . .
.. .r .
. . . .:.s... .
a 610 .' .' .' ' ' ' ' ' -( n . . .
. . . . . . . .' .' 1 1
. s. . .s ..:. . ..>... ... .... .r . . .s...
. . .. .>.s.. .
600 .'. ..' .'.- . . . .' .' .
- . .s....... .. 6.
. . . . . . . N.
3., . . . . . . . . . .... . N...
. . . . . . s V
==.
590
. . . . . p
&) . . .
g
... . .. ...... . .. s . . .. . ~ ... . ..... .
y 580
' ' ' .t )
Q 0
,, . ... n
# % % (1201
'\
.....r. g.
i, _ -- . . w. s iws . ..s .-g
. . - ,_ _ ts u.
PWmr DF R ATED TWERNlAL NnER _ 1 & cc I FIGURE REACTOR CORE SAFETY LIMIT f--f00R LOOF 5 IN OPERATIM - l
.g.,y.. _ .
_ _ _ - _ _ . .__r,.. . waves .- . . . . . _$.... . . ww...,,... ._b . q BYRON - UNITS 1 & 2 2-2 AMENDMENT NO. 65 Ruff
O , i d g n _ i w a mo o wt wt e l t 9 on on n o pf re re t a_ od r o erm l a u rm au V l e i cnr nr e r r y t t t e f u p cf s f s l z g t os ( ) ( on oni oe H n a a 9 i vu l e a % e 4 % ) % e N 3 m b 8 p p
- 0. le1 egn re 8 egn 0 0 o O 2h 5 L 9 m 1 c6 t ne4 na 9 c 6 1 t L 8 u 3 y1 f ap3 a p 4 a 5 A.
3 A k n 1 ck aro2 rs 8 i A. t E e 2 2 m N N N I _ O P d T - n i w a E S no o wt wt S i l mf t 9 on re on P re - I N T pd r o erm l a u rm - R oe a u i T I O or i r cnr y nr s t t t g d N P l u p cf s f s l e O T s ( 9) ( on oni os z l n u E f a i vu e n I S oe 1 1 ) H p e i T % b p t n A T P I 0 m m
- 0. le0 egn re 3 e gn 8
6h 0 0 0 o o N l 9 u 3 c8t na6 na 3 y1 f ap3 ap 2 c 7 0 t C E l 5 a 5 l i A. A. M I 1 n 2 ck ars2 rs 2 e k f U k k N M 1 R
- T S
2 N ou.I M
, E T
h S T Y S P I R T R O T - C A _ E R - e w r r v o e l L o d a p
- r r t a V t w e o c e u i
r o t t a H e p pT - l a c e l n m a R p F M e i t t I un w R P o - t ro e e r o n i - n oL - p yp T r o tt a eh t - cm i ni . l aw eu m nu p yrT e cu t a s - T o ro gP eP i ns eu r c l o o e - I eL 1 2 a u oP _ N C n qt r esns jF o U el t t t T geio nS Cr t l n en - L A N r o t c G e
- r. e aL v
i U n i U n oa vl ro ra fl r o i e n rrbl eP rC m E T u I E ym t o rk oa t e e O a e eo eo b er cr I e t dC dC r f f aB T R S a n n u . . a e C b U U T a b S R N . . U 2 3 4 5 6
. ,/.
F 1 1 1 1 1 7 1 8 1
St. 2,0
.p
- r. _
670 , , . . .. . . . 3471. pels. .
. . . ......s. . , . . . . . ..,.,. .
660 . .. A, ,
'225%* pata r r .- . . . . . . .. .. . . .
.7. . . .. . . .
- 5 r- ..s* r * .- . * =** r *-
Q. .. 650' . g . . ...... . . 1 w . ..
.;... l E 640 .
E . . 2 - 2dod.
- pep : .: : - :.~
- 'm . . .
8. 630 i,E . 3 . . . 3 C .g g .g.,j .*... .. . .
. .: . { . j . . .;. .; . { . . ;. . , *
. { . } . :.
cln 3 620 A. . . ... . . . . . .
. g.
- n, . . ...
...:.:.. . . . .t .
t pm . E. U.U
.. .s....
b-- . . ...
.s ...... ..s.. . .
ht 600 . . . W
~
w q . . ... . . .
. . . ...s.... . ...... . . . . . . s..
w . . .
.. .....s.
- y. ... . . .
\ .
g y ~. . .
. . . . . o
.u....... . . . . . .
. . . . . . . . . ...s.. ... ...
o..... f , 580 0 Zo @ d M #m % k
,%v o..__re. .. g. .. _. m.v. ar__ ,
, v. . 3 i
/8
/;
u.._._.2__n, ..... 1 PeRcetaT- or RATEDTHERt%L fbWER /
/ ' g i
e M l i a.l. t - l Figure G A B Reactor Core Safety Limit / im Ln;.0 !' p.. n . ..< y
. _ . . . . . . l f
p..,,.,4.,_.._a.. _. . .. . ... . , ._; . .. ,... ,__
. . . . ._ . . ,m.... , m,,,,
A i Red F BRAIDWOOD - UNITS 1 & 2 Unit 1 - Amendment No. 56 2-2a Unit 2 - Amendment No. 55 _ . , _ _ _ - _ - - - - - - - _ E_- -- __ _ ----
O (( . i j t p mow o wt n on E l t 8 U pf a re L A o od r o ef l oes p rm au V l e i c g nr s r r y) nt t t E fu p cran f s l z g L osa ()( ere on as H i n vu s e 8 A %e % 8
%f w-m% e t i b 8 p p o
L W O 3 m 9n
- 0. l e1 1 c6drs
.aor rt 8. g n 4 na 0
2h 9c 0 6 5 1 % L 8 u 3 y1 nan 3 ap 4 a 5 8 1 A. A. A 2m 2c2ani 2rs 2e 1 1 2 N N S T N I O iw P no o wt T il t 8 n on E a re S mf T r o cf p rm au N pd P I I oe i r
'c. o ge s nrt s g
R O or y) nt t P l u p cran fs l i 1 T T s ()( ere on os z s n d N E f a 8 t m i vu H p e p e O S oe % %f wu % b u m 3 e 8 0 0 o n I T P % 0. le 0. arto r gn 6h 0 0 % i A I 0 m 3c8drs 6 na 2 c 7 A. A. t R 9 u 3 y1 nan 3 ap 5 a 5 1 1 T 2 N N n N T 1m 2c2ani 2rs 2e 1 1 o E C. M U R ON T S I E M L E T B S A Y T S P I R T R O T C A E ~ R - e
' r v w r e l p
o o d a l r t a V t i
- r o c e u r w e t a H e p pT o t c e l n m l a a R p t i un F W e i t P o R - r o n i t rw s s T r o tt n oo - p yp h i ni a tl eu m cm nu p y
ce T t c as l o l a - T o rw gP eP i nree e oP I o eo 1 2 a u r eunr jF o N C nl tt qt T gsiu nS Cr U e t t l n en rsbs iE e r Gl i i oa ra e eero ym rk L o e n n vl fl n mrul oa A t c mv ae U U ro eo ro eo i b EPTC t o er t e cr N r _ O I a e t el dC n dC n u . . ff a aB e _ T R S a b U U T a b S R C N . . - . . . 7 8 U 2 3 4 5 6 1 1 1 1 1 F 1 1 7 -
LC0 INSERT (S) SECTION 2.0
.(
SLs 2.0 INSERT 2.0 2A (P ) 3 680 070 ,
- ')471 psia e j
000 2250 psia g{ 650 , i::. {' O s c40 s
$ 2000 psia y $ G30 -
> i a
2
\1800 ' psia
.$ N N
~
,$ .010
=
E 000 - 500
~ 580
? O 20 40 00 80 100 120
.2 PERCENT OF. RATED THERMAL POWER i
~
(
'rigure 2.1.1-1 (page 1 of 1)
Reactor Core Safety Limits
-] 5/14/98 Revision F
3 JUSTIFICATION FOR DIFFERENCES TO NUREG-1431 SECTION 2.0 - SAFETY LIMITS (SLs) h:P BRACKETED CHANGES (B)
'B. 3 . The brackets-were removed and a plant specific value was added.
GENERIC' CHANGES (C) C3 This change. is consistent with NUREG-1431. as modified by TSTF-5.
-l Revision 1;(NRC. approved).
PLANT SPECIFIC CHANGES (P) P3 The Reactor Core' Safety Limits figure has been replaced with the plant
. specific figure _(CTS Figure 2.1-la for Braidwood and CTS Figure 2.1-1 for Byron).
g lj i
)
r. h -BYRON /BRAIDWOCD - UNIT l1 & 2 2.0 1 5/14/98 Revision F ___m___iU_'____m _.___[.m_.'. . _ . _ - _ _ _ ._ _ _ . . - _ _ __ _ _ _ _ _ _ _ . -- _ _ _. .2_..___._____ _
i-Reactor Core SLs B 2.1.1 BASES .; h~ Y (M55VsU 1 BACKGROUND The prope functioning of t Reac1pr rotection System
-(continued) g (RPS) and geam e p H5B fety ynlves prevents violation ,
of the reactor core SLs. g) 7 o
<- W APPLICABLE The fuel cladding must not sustain damage as a result of -
SAFETY ANALYSES normal operation and A00s. The reactor core SLs are # established to preclude violation of the following fuel 8 design criteria: g Q There must be at least 95% probability at a 95% confidence level (the 95/95 DNB criterion) that the [I w
@ hot fuel rod in the core does not experience DNBperld .
^
h Uhe hot fuel pellet in the' core must not experience centerline fuel meltingioid) see e W ia u:o 3* i , " Beac b TO s n w-- (nrs) Im*o a. b ." > The Reactor Trip System setpoints (Ref. 2) in combination l withalltheLCOs,aredesignedtoprevent)anyanticipated combination of transient conditions for Reactor CoolantAveuvois-Jg. g ,
"Ylf,[,p ,*J System 1RCS),temperatureJpressure, and THERMAE 7difEOevel O thatwouldresultinaghparturefromf0cleateJ@theiling/ftio (DNBR) of less than the.DNBR limit and preclude -
V existence of flow instabilities. Automatic enforcement of these reactor core SLs is provided by the following functionsg(Rep, zy @
@ a.
Epfressurizer[ressurekrip; t
-- ot.ca, )
. b, pressurizer [ressuretrip; f f
- c. Overtemperature AT trip; (MLha kg m g,_ a . a +, %
- d. Overpower AT trip; gy 4, e.___ Power Ranoe Neutron _El ri ; @ tP 4 dar-l Q .
Los reactar c .t.a+ -fl.~ trip , ua % d, % ,s. g@4 team gameratur safety valves.* The limitation that the average enthalpy in the hot leg be less than or equal to the enthalpy of saturated liquid also ensures that the AT measured by instrumentation, used in the ! RPS design as a measure of core power, is proportional to ' core power.
< (continued)
WOG STS B 2.0-2 Rev 1, 04/07/95 s
RCS Pressure SL B 2.1.2 ('] BASES (continued) APPLICABILITY SL 2.1.2 applies in MODES 1, 2, 3, 4, and 5 because this SL could be approached or exceeded in these MODES due to overpressurization events. The SL is not applicable. in MODE 6 because the reactor vessel head closure bolts are not fully tightened, making it unlikely that the RCS can be 9o pressurized, 1 0 6
. SAFETY LIMIT -The 1: -
pressure 15:=r; 4L. SL vieletions-are-eppMcable to the-ES]- VIOLATIONS .Ci vk c' r-'-'" p o om h. g).l.2 'RCS hswn SL,9 3 If 4hEiEEEiEBBk Sijis violated when the reactor is in j4
@ MODE 1 or 2, the requirement is to restore compliance a.
in MODE 3 within I hour. l Exceeding the RCS pressure SL may cause immediate RCS l 1 failure and create a potential for radioactive releases in ! excess of 10 CFR 100, " Reactor Site Criteria," limits )
\g (Ref. 4). I */ The allowable Completion Time of I hour recognizes the importance of reducing power level to a MODE of operation where the potential for challenges to safety systems is l minimized. 3; m 9 9 9 - ,, ,, m,,y , g., g J ru~ . . 1 .,a,e 4 <ein,. c.y....,meu,.n, x P, ,
(aad b. % d b [VDit] 4s M 0 0 0 3. (D-G 22 @ .;u. 2] @ If(EiiCRGG:iRPP,Rme SL is exceeded in MODE 3, 4, or 5, RCS
@ pressure must be restored to within the SL value within 5 minutes. Exceeding the RCS pressure SL in MODE 3, 4, or 5 1 is more severe than exceeding this SL in MODE 1 or 2, s.ince l the reactor vessel temperature may be lower and the vessel 1 material, consequently, less ductile. As such, pressure 1 must be reduced to less than the SL within 5 minutes.4 The action does not require reducing MODES, since this wou require reducing temperature, which would compound the problem by adding thermal gradient stresses to the existing pressure stress.
[14 4, Cmb h Ti-, b e.,,,J,ci , c.. h;.,, A ll i 42 recluce pemu<. bim A. h@co.Ey e SLW ord.e l (continued) WOG STS B 2.0-9 'Rev 1, 04/07/95 ' 1
' JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 BASES SECTION 2.0 SAFETY LIMITS (SLS)
BRACKETED CHANGES (B) None'.
= GENERIC ~ CHANGES (C)
C3 This change is consistent with NUREG-1431, as modified by TSTF .
- l- Revision 1-(NRC approved). The 3roposed Bases for Reactor Core SLs are modified to be consistent with t1e change made to the Bases for RCS Pressure SL.
C, The. Background section of the Bases for SL 2.12 was revised to clarify Jthe discussion regarding overpressurization. This change is consistent' with NUREG-1431 Revision 0, Change BWR-11. C.10. Revision 1, which was not accurately reflected in NUREG-1431. Revision -1. 4 L L Ei < l h BYRON /BRAIDWOOD UNIT 1 & 2 2.0 1 5/14/98 Revision F i l ____1-__--__ '
JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 BASES
,, SECTION 2.0 - SAFETY LIMITS (SLS)
- 3 V
PLART SPECIFIC CHANG.ES (P) P3 The references have been deleted. added, or revised and renumtored to reflect the appropriate plant specific references. P2 During the development certain wording preferences. English language conventions, reformatting, renumbering, or editorial rewording consistent with plant specific nomenclature were adopted. As a result, the Technical Specifications (TS) should be more readily readable by, and therefore understandable to, plant operators and other users. During this reformatting, renumbering. and rewording technical changes (either actual or interpretational) process, were made no to the TS unless they were identified and justified. P3 Tne Bases have been revised to reflect the plant specific listing of automatic trip functions relating to the enforcement of the reactor core SLs. The Bases were also revised to clarify that there are trip functions which serve as backup to primary functions. This is consistent with UFSAR Section 7.2.1.1.2. P, .Not used. P3 The Bases have been revised to reflect Bases Figure 2.1.1-1 as a typical
,o graph of reactor core safety limits versus boundary of protection. The
(~) figure and associated discussion is regarded as general information since it is used as an example and for illustration purposes only. Since the figure is not used for operation, providing a plant specific discussion could potentially mislead the operators about the use of this Specification. P. The Bases have been revised to reflect the descriptions provided in SL 2.1, This is an editorial preference to improve the clarity and readability of the Bases. P7 The Bases have been revised to reflect that the plant may have approved g exemptions to the ASME Code. Section XI. requirements. Per 10 CFR 50.55a(3) relief from ASME Code requirements can be granted by I NRR if alternative methods provide an acceptable level of quality and
? safety, or if compliance with Code requirements would result in hardship q or unusual difficulty without a compensating increase in quality and safety. These exemptions from ASME Code requirements are common for both H inservice inspection of com)onents and inservice testing of pumps and s- valves. In addition.10 CFR 50.55a(g)(5)(ii) states that if a revised W inservice inspection program conflicts with the Technical Specifications, the Licensee shall apply to the NRC for amendment to the Technical Specifications to the revised program.
BYRON /BRAIDWOOD Unit 1 & 2 2.0 2 5/14/98 Revision F (Vl
. JUSTIFICATION FOR DIFFERENCES TO NUREG-1431 BASES SECTION 2.0 SAFETY LIMITS (SLS)
P, . Not.used. P,. Not.used.
.P w The Bases;have been revised to delete the reference to USAS B31.1. The-components'are designed to.ASME Code. Section III G
h n i t 4 l i 1 L'
-y l
ll1BIRON/BRAIDWOODUNIT 1 & 2 2.0 2a 5/14/98 Revision F 1 I s !
LCO Applicability 3.0 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 and LC0 3.0.7. LC0 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), com)letion of the Required Action (s) is not required unless otlerwise stated. LCO 3.0.3 When an LC0 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 ) laced in a MODE or other specified condition in which the _C0 is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in: O 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 com)leted that permit operation in accordance with the _C0 or ACTIONS. completion of the actions required by LCO 3.0.3 is not required. LC0 3.0.3 is only applicable in MODES 1. 2. 3. and 4.
)
l O BYRON - UNITS 1 & 2 3.0-1 6/30/98 Revision A
r
' ~
LC0 Appl.icability 3.0 [3,0ELCO' Applicability- {} LCO 3.0;4-' When an LC0'is not met, entry into a MODE or other specified condition in the Applicability.shall not be.made except 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. 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.
o uni t .- r 1 Exceptions to this: Specification are stated in the,
..* individuals Specifications.
~
~
LC0 3.0.411s only applicable for entry into a MODE or other-specifiedl condition in the Applicability,in MODES 1. 2. 3. L and.. 4 LCO 3'.0.5 Equipment removed-from service or declared inoperable to-comply with ACTIONS may be returned to service under. bl
# administrative. control solely to perform testing required to L demonstrate its OPERABILITY or the OPERABILITY of-other-
- d. equipment. This is an exception to LCO 3.0.2 for the system
' bl 6 ;
returned to service'under administrative control to perform
. the required testing to_ demonstrate OPERABILITY.
.[
i . 4 I .') 4-s - k f _ BYRON - UNITS 1:& 2 '3.0-2 5/14/98 Revision F __._____..__.m. _ . . . - _ _ _ . _ _ - _ _ _ _ - _ _ . _ _ -
LCO Applicability 3.0 Q V 3.0 LCO Applicability LCO 3.0.6 When a supported system LC0 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 appro]riate Conditions and Required Actions of the LCO in w11ch the loss of safety function exists are required to be entered. When a sup) ort system's Required Action directs a supported system to )e 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 LC0 3.0.2. j L
)
l l i i l i i i 4 l (O y BYRON.- UNITS 1 & 2- , 3.0-3 6/30/98 Revision A
l LCO Applicability
, 3.0 3.0' LCO Applicability
() l LC0 3.0.7 Exception LCOs' 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 Exception LCOs is optional. When an Exception LCO is desired to )e met but is not met, the ACTIONS of the Exception LCO shall
.be met. When.an 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 0 applicable Specifications.
I l 9 LC0 3.0.8 LCOs.. including associated ACTIONS, shall ap)1y to each unit W individually, unless otherwise indicated. Wienever the LC0 T refers to a system or component that is shared by both T units, the ACTIONS will apply to both units simultaneously. I
.ms, v'
4 i i ( )! BYRON - UNITS 1 & 2- 3.0-4 5/14/98 Revision F _ _ _ _ _ _ _ _ _ - _ _ - _ _ _ _ - ___--__a
SR Applicability 3.0
,Q 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY U
SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs. unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to 3erform a Surveillance within the specified Frequency shall Je failure to meet the LCO except as provided in SR 3.0.3. Surveillance do not have to be performed on inoperable equipment or variables outside specified limits. SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency. ~ as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once " the above interval extension does not apply.
- If a Completion Time requires periodic performance on a "once per . . " basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications. I b U BYRON - UNITS 1 & 2 3.0-5 6/30/98 Revision A 1
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY O SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LC0 not met may be delayed from 1 the time of discovery u the specified Frequency,p to 24 hours whichever or upThis is less. to the limit of delay period is permitted to allow performance of the Surveillance. If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met and the applicable Condition (s) must be entered. When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition (s) must be entered. SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall not be made unless.the LCO's Surveillance have been met within their specified Frequency. This provision shall not prevent entry into MODES or other specified conditions in the Ap]licability O that are required to comply with ^CTIO"S or t,et are part of a shutdown of the unit. H? SR 3.0.4 is only applicable for entry into a MODE or other c$ o specified condition in the Applicability in MODES 1. 2. 3. h and 4. W SR 3.0.5 SRs shall apply to each unit individually unless otherwise
@m h o, indicated.
O BYRON - UNITS 1 & 2 3.0-6 5/14/98 Revision F
LCO Applicability B 3.0 f i B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY-
.(^x C)y o i BASES 0
hi y l LCOs LC0 3.0.1 through.LCO 3.0.8 establish the general g requirements applicable to all Specifications and apply at
.N all times unless otherwise stated.
LCO 3.0.1 LC0 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 otherisaecified conditions of the Applicability statement of eac1 Specification). LC'O 3.0.2 LC0 3.0.2 establishes that upon discovery of a failure to meet an LCO. the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered. The Required Actions establish those remedial measures that must be taken within m specified Completion Times when the requirements of an LC0 Q- 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.
f, .j p F l' BYRON.- UNITS 1 & 2 B 3.0 -1 6/16/98' Revision F 1 I m- _ j
LCO Applicability B 3.0 (3 BASES O LC0 3.0.2 (continued) 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 .iction specifies the remedial measures th6t permit continued operation of the ! unit that is not further restricted by the Completion Time. In this case, compliance with the Required Actions provides i an acceptable level of safety for continued operation. j Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications. The nature of some Required Actions of some Conditions I
\ necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Condition no longer exists. In this instance, the individual LCO's ACTIONS specify the Required Actions.
An example of this is in LC0 3.4.3. "RCS Pressure and Temperature (P/T) Limits." l l i O ( V BYRON - UNITS 1 & 2 B 3.0 - 2 6/16/98 Revision A I L---- -- -- . i
/- LCO Applicability B 3.0 BASES-LC0 3.0.2 (continued)~ The Com)letion Times of the Requireli Actions are also applica)le--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 Surveillance, 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 i function are inoperable and limits the time other conditions ( exist which may result in LCO 3.0.3 being entered. -
' Individual Specifications may specify a time . limit for i Jerforming an SR when equipment is removed from service or aypassed 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 and the new LC0 is not met.
In this case..the Completion Times of the new Required Actions would_ apply from the Joint in time that the new Specification becomes applica)le, and the ACTIONS Condition (s) are entered. l l i I i O B 3.0 -3 l iBYRON - UNITS 1.& 2 6/16/98 Revision A
- . p.: ,
LCO Applicability B 3.0
' BASES LCO 3.0.3 LC0 3.0.3 establishes the actions that must be implemented when an LC0 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 i addressed by the associated ACTIONS. This means that no single Condition or combination of Conditions stated in the ACTIONS can be made that corresponds to the' actual condition of the unit. Sometimes, possible combinations of Conditions are such that entering LC0 3.0.3 is warranted. In such cases. the Conditions corresponding to such combinations state that LCO 3.0.3 shall be entered immediately.
This Specification delineates the time limits for placing 1 the unit in a safe MODE or other s)ecified condition when operation cannot be maintained witlin the limits for safe operation as defined by the LC0 and its ACTIONS. It is not intended to be used as an operational convenience that permits 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 LC0 3.0.3. I hour is allowed to prepare for an L orderly shutdown before initiating a change in unit L o 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 l- the electrical grid. The time limits specified to reach lower MODES of operation permit the shutdown to proceed in a l 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 unit upset that could challenge safety systems under L conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LC0 3.0.3 are consistent with the discussion of Section 1.3.
-Completion Times.
ll BYRON - UNITS 1 & 2 B 3.0-4 6/16/98 Revision A
LC0 Applicability B 3.0 l 1 l [] v BASES {
\
LCO 3.0.3 (continued) j A unit shutdown required in accordance with LC0 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.
- c. ACTIONS exist that do not have expired Com)letion Times. These Completion Times are applica)le 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 LC0 3.0.3 allow 37 hours from MODE 1. 2. ! 3 or 4 for the unit to be in MODE 5 when a shutdown is l 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 i MODE is reached in less time than allowed, however, the ; total allowable time to reach MODE 5, or other applicable l MODE, is not reduced. For example, if MODE 3 is reached in '
/i 2 hours, then the time allowed for reaching MODE 4 is the V next 11 hours, because the total time for reaching MODE 4 is l
not reduced from the allowable limit of 13 hours. Therefore, if remedial measures are completed that would i Jermit a return to MODE 1. a penalty is not incurred by l 1aving to reach 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 LC0 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 specifiec 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. V BYRON - UNITS 1 & 2 B 3.0 - 5 6/16/98 Revision A
LC0 Applicability B 3.0 i BASES ~ LCO 3.0.3 (continued) Exceptions to LC0 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LC0 3.0.3. would not provide remedial measures for the associated condition of the unit. -An exam
." Spent Fuel' Pool Water Level."LC0ple 3.7.14 of thishas is inanLC0 3.7,14.
Applicability of "During movement of irradiated fuel assemblies in the spent fuel-pocl." Therefore, this LCO can ' be applicable in any or all MODES. If-the LC0 and the Required Actions of LC0 3.7.14 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.14 of " Suspend movement of irradiated fuel assemblies in the spent fuel pool" is the appropriate Required Action to complete in lieu of the actions of LC0 3.0.3. These exceptions'are addressed in the individual Specifications.
LCO _3.0.4- LC0 3.0.4 establishes limitations on changes in MODES or other specified cond.itions in the A) placability when an LCO is not met. It precludes placing t1e unit ~1n a different (] MODE or other specified condition stated in that-A) placability (e.g.. Applicability desired to be entered) w1en the following exist:
- a. Unit conditions are.such that the requirements of the LCO would not be met in the Applicability desired to be entered: and
- b. Continued noncompliance with the LC0 requirements, if the-A) placability were entered, would result in the unit )eing required to exit the A) placability desired to be entered to comply with the Required Actions.
l l 0 BYRON - UNITS 1:&.2 , B 3.0 - 6 6/16/98 Revision A
f l- , LCO Applicability B 3.0 BASES-n ,M' L LC0 '3.0.4 (continued): 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 l 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.
,, The provisions of this Specification should not.be
' " interpreted as endorsing the. failure-to exercise the good E
practice of restoring ~ systems.or components to OPERABLE status before entering an. associated MODE or other specified h condition in the Applicability.
.The. provisions of LC0 3.0.4.shall not prevent changes in.
MODES or other'specified' conditions in the Applicability-
"m that'are required to' comply with ACTIONS. In addition the-
. provisions of LC0 3.0.4 shall not 3revent changes in MODES Lor other specified conditions in tie Applicability that j k. . result from any unit' shutdown.
q.
' Exceptions to;LCO 3.0.4 are stated in the individual
~
o
.m n Specifications. - The-exceptions- allow ' entry into MODES or 1(
V
) i -
other specified conditions in the Applicability when the
- g. nassociated ACTIONS 1to'be entered do not provide for Econtinued operation for an unlimited period of time.
H- Exceptions may apply to all the ACTIONS or to a-specific g -Required Action of a Specification. , f LC0 3.0.4'is' only ap31icable when entering MODE 4 from V MODE 5. MODE 3 from 10DE 4 MODE 2 from MODE 3..or MODE 1 y from MODE 2. Furthermore. LCO 3.0.4 is applicable when ; entering any other;specified condition in the' Applicability 1 only while' operating in MODE 1. 2. 3. or 4. .The requirements of LC0 3.0.4 do not'a) ply in MODES 5 and 6. or in other specified conditions of tie Applicability (unless - in MODErl.' 2. 3. or 4) because the ACTIONS:of individual Specifications sufficiently define the. remedial measures to be taken.
..~ ' i y, '
I
,e 6
f* y' '\ DBYRON' UNITS 1 & 2 . B 3. 0 '- 7 6/16/98 Revision F l
^
... .1.. 9
LC0 Applicability B 3.0 q. V BASES LCO 3.0.4 (continued) Surveillance 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, changing MODES.or other specified conditions while in an ACTIONS Condition, in compliance with LCO 3.0.4 or where an exception to LCO 3.0.4 is stated. is not a violation of
' SR 3.0.1 or SR 3.0.4 for those Surveillance that do not have to be performed due to the associated 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
- g affected LCO.
LCO 3.0.5 LC0 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 LCO is to provide an exception to LCO 3.0.2 (e.g.. to not comply with the h applicable Required Action (s)) to allow the performance of i o required testing to demonstrate: Oagl a. The OPERABILITY of the equipment being returned to service: .or i
.(l g
- 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 required testing to demonstrate OPERABILITY. ' This Specification 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 required testing. l l L
]}
V
- . BYRON - UNITS 1 & 2 ,
B 3.0 - 8 6/16/98 Revision F l [ . . . 2>
LCO Applicability B 3.0 BASES LC0f3.0 5 (continued)-
- An example' of demonstrating.the OPERABILITY of.other eg.uiament is taking an inoperable. channel or trip system out Lof tie 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 -j
-h
.taking an inoperable channel or trip system out of the 1J tripped condition.to permit' the logic to function' and g . indicate the appropriate response during the performance of y ^ required testing _ on another channel in the same trip system.
;p }[ ..
c g LC0 3.0 61 LC0 3.0.6 establishes an exception to LCO 3.0.2 for support 3 zsystems that have an;LCO specified in the Technical Specifications (TS). This exception is provided because LC0.3.0.2 would require that the. Conditions and Required. Actions'of.the. associated inoperable < supported system LC0 be.
' entered solely due to-the .inoperability of the support system. This exception is justified because the actions
?that arel 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 7h-: -
supported system's Conditions and Required Actions or may specify other Required Actions Whenasupportsystemisinoperableand'thereis'anLCO specified for it in the TS,' the supported-system (s)- are required to be declared ino)erable-if determined to be . inoperable.as a result- of tie support: system inoperability.
. -However, it_ is not necessary-to enter into the supported systems' Conditions and Required Actions unless directed to
't' . da so~ by the support system's Required Actions. The i
potential confusion a'nd ' inconsistency o.f requirements related to the' entry:into multiple support and supported systems' 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 t
system'sLRequired Actions. t; .
^< i BYRON 1- UNITS'l & 2' r 'B 3.0 - 9 '6/16/98 Revision F iJ .s -
};
-m___.__im__----_ _ _ . - _ _ - - - - - - - - - - - - - - - - - ' - - - - - - - - - ~ - - - - - - - - " - - - - - - - - - - - - - - ~ ~ " - - ' " - ~ ' ^ - ' ' ^ - - - - - - ~ ~ ~ ~ '--
LC0 Applicability B 3.0 LBASES-LC0 3.0.6 (continued) However. there are instances where a support system's Required Action may declared inoperableoreither directdirect entry a supported into. system Conditions and to be 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 Recuired Actions for a supported system, the applicable Concitions and Required Actions shall be entered in accordance with LCO 3.0.2.
f- Specification 5.5.15. " Safety Function Determination Program (SFDP)." ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LC0 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 L result of the support system inoperability and_ corresponding exception to entering sunorted system Conditions and Required Actions. The 59P 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. 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.
O y
~
BYRON'.- UNITS-l'& 2 B 3.0 - 10 6/16/98 Revision A
p LCO Applicability
. B 3.0
(~
., BASES.
)
-9};
'1 i: u s iCO:34.7 ThereL are certain special tests and operations required to-
- l._ be performed at various times over the life of the unit.
o: These.special tests and operations are necessary to , ni demonstrate selsct unit performance characteristics. to p . perform special maintenance a'ctivities. and to perform
- N ~[ s)ecial evolutions. Exception LCOs'(e.g., LCO 3.1.8.
X ">HYSICS TESTS: Exceptions-MODE 2") allow specifled
'D -
; Technical Specification (U) 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 s)ecified, all:the.other TS requirements remain unchanged.
j T11s will ensure all . appropriate requirements of the. MODE or - other specified condition not directly associated with or L 0- -
!s' . required to be changed to perform the special test or 3, io : operation will remain'in effect.
The Applicability of an Exception LC0 represents a condition 4 not:necessarily in compliance with the normal requirements'
- O~ ~ ' of the TS. Compliance with Exception LCOs is. optional. - A'
.special operation may ~be. performed,either. under the prov
[
.otheisions of the TS r applicable appropriate requirements. Exception
.'If-itLC0 or underto.:
is desired the L -. 3erform the special operation'under the provisions of the L - Exception LCO,.the requirements of the-Exception LC0 shall.
~
be-followed. [' - LC0:L3.0.8 :LCO 3.0.8 establishes-the applicability of each 3 l Specification'to both Unit-1 and.. Unit:2 operation. Whenever. o" a. req'uirement> applies to 'only.one. unit or is different for
-f):
each unit . this will:be identified 'in the a)propriate section:of the Specification. (e.g. , Applica ulity. R , Surveillance, etc.) with parenthetical reference.' Notes, or-N other appropriate presentation within the body of the T- requirement. - H-ll
'^
- 1/ N - {;
U ' m BNON-UNITS'1&2: i B 3.0 - 11 - 6/16/98 Revision F l L - a M' b( '
.s l" . . . .
]
SR Applicability B 3.0-B3.0-SURVEI[.LANCEREQUIREMENT(SR) APPLICABILITY I sD w [ ' BASES 4 , .. O .
$ S SRs- .SR 3.0.1 through SR 3.0.5 establish the general requirements
'H- . applicable to all Specifications and apply at all times.
4 3 unless otherwise stated. k. LSR ' 3.0.1' SR 3.0.1' establishes.the requirement that SRs must be met i during the MODES 'or other specified conditions ~ in the 1 Applicability for. which the requirements of the LC0 apply; ! unless otherwise.specified in the-individual SRs. This. 1 Specification is to ensure that Surveillance are performed 1
, Eto 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.
Systems and'com)onents are assumed to be OPERABLE'when the. associated SRs lave been-met. Nothing.in this ..
- Specification, however. is to be construed as implying that 1 systems or components are OPERABLE when:
- a. :The systems or components'are known to be inoperable, A although still meeting the-SRs: L or-i b; The requirements of the Surveillance (s) are known not y to be. met between required Surveillance performances. ;
' Surveillance 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. l 1 unless otherwise specified. The SRs associated with an :
- Exception LC0 are only applicable when the Exception LC0 is 1
~used as an allowable exception to the requirements of a Specification .;
u_.
> Unplanned events may. satisfy the requirements (including 'l
- f. -
- applicable ' acceptance criteria) for a given SR. In this _
case, the. unplanned . event may be credited as fulfilling the l
. performance of the SR. This allowance . includes those SRs !
i whose performance is normally precluded in a given MODE or , other specified condition. I
'Yf .
[Q ' IBYRON-UNITS 1.&'2' B 3.0 - 12 6/16/98 Revision F.
.g LLJ _ A.___ _ - _ _
SR Applicability B 3.0 _ BASES SR 3.0.1 (continued) i Surveillance, including Surveillance . invoked by Required Actions, do not have to be performed on inoperable equipment , because the ACTIONS define the remedial measures that. apply. ! Surveillance 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 30st maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillance 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 )ossible and the' l equipment is not otherwise believed to ]e incapable of i 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.
./ N.
L) SR 3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for. Surveillance 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 unit operating conditions that may not be suitable for_ conducting the Surveillance (e.g... transient conditions or other ongoing Surveillance or maintenance activities). l ( l n nv BYRON ~-'. UNITS 1'&.2 B 3.0 - 13 6/16/98 Revision A ! u_ _ _ _ _. _____ _ _-
SR Applicability B 3.0 l
~BASESi SR J3.0.2 (continued) t The 25% extension does not significantly degrade the
- reliability thdt 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 exceptions to SR.3.0.2 are those Surveillance for
.e which:the 25%. extension of the interval specified in' the Frequency does not apply;
- 7. These. exceptions are stated in h' the individual Specifications. An example of where SR 3.0.2
- f. does not ap)ly is the Containment Leakage Rate Testing .
Program. :Tle requirements of regulations take precedence
'N.- over the TS. The TS cannot in and of themselves extend a g test interval specified in the regulations, 4
As' stated in'SR 3.0.2,.the-25%-extensien 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%
y extension to this Completion Time is that such an action lg 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, i
;: tJ:
I g 1 BYRON.- UNITS 1 & 2 B 3.0 6/16/98 Revision F a
SR Applicability B 3.0 BASES < 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 within the specified Frequency. A delay Seriod of up to 24 hours or up to the limit of the specified Trequency, whichever is less, 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 tnat the specified Frequency was not met. This delay period provides adequate time to complete Surveillance 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 fcr this delay period includes consideration of j unit conditions, adequate planning, availability of I 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
'b) requirements. When a Surveillance with a Frequency based not on time intervals. but upon specified unit conditions or operational situations, is discovered not to have been performed when specified. SR 3.0.3 allows the full delay period of 24 hours to perform the Surveillance.
SR 3 0.3 also provides a delay period for completion of Surveillance that become applicable as a consequence of MODE changes imposed by Required Actions or a reactor trip. 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. I (VD BYRON - UNITS 1 & 2 B 3. 0 - 15 6/16/98 Revision A l .
SR Applicability B 3.0 _ JBASES:
;SR i3.0.3:(continuedF
-c 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-1 Completion Times-of the Required Actions for the applicable LCO-Conditions begin:immediately upon expiration of the Ldelay 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
- g ._ ,
OPERABILITY. requirements;and' variable limits are met before
'j-r
. entry 11nto MODES or other specified conditions'in the w ' Applicability for which these systems and components ensure-
.O 'safesoperation ofJthe unit.
DO A),' = The provisions of this Specification should not be interpreted as endorsing the failure.to exercise the good a y practice of restoring systems .or_ component to OPERABLE. m .
' . status before entering an-associated. MODE or other specified.
'Y -condition.in the Applicability.
p , e p Q~ ' ~ L BYRON '- UNITS 1 & 2 .B 3.0 .16 6/16/98 Revision F L w= _ _ -
SR Applicability B30 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. train, 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 surveillance do not have to.be performed on inoperable equipment. When equipment is inoperable. SR 3.0.4 does not a) ply to the associated SR(s) since the requirement for the S1(s) to be performed'is removed. Therefore, failing to perform the Surveillance (s) within the specified Frequency, on equipment that is inoperable, 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. LC0 3.0.4 will govern any restrictions that may (or may not) apply to MODE.or other specified condition-changes.
t The provisions of SR 3.0.4 shall not prevent changes in
..d MODES or other:specified conditions in the Applicability 20' 4
that are required to comply with ACTIONS. In addition, the. prnvisions of LCO 3.0.4 shall not 3revent changes in MODES 0 orLother specified conditions in tie Applicability that (q ;M ,
, l- .' result'from any unit shutdown.
k A' 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 s)ecified in the Frequency, in the Surveillance,:or )oth. This allows
-performance of Surveillance when the prerequisite condition (s) specified-in a Surveillance procedure require
. entry into the MODE or other specified condition'in the L Applicability ' fothe associated LCO prior to the performance
;or completion of a Surveillance. A Surveillance that could not be performed until'after entering the LCO 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 aerformed) until a 3 articular event.. condition, or time has )een reached. Furt1er discussion ~of the; specific formats of SRs' annotation is found in Section 1 4. Frequency.
}]~- . BYRON-UNITS 1&'2-
. B 3. 0 6/16/98 Revision F
SR Applicability B 3. 0 BASES-
,r3
(.) SR 3.0'4 (continued) SR 3.0.4 is only applicable when entering MODE 4 from
, MODE 5. MODE 3 from MODE 4. MODE 2 from MODE 3. or MODE 1 o .from MODE 2. Furthermore. SR 3.0.4 is applicable when
, entering any other specified condition in the Applicability g only while operating in MODE 1. 2. 3. or 4. The
- j. 3 requirements of SR 3.0.4 do not ap)1y in MODES 5 and 6. or in other specified conditions of tie App'.4cability (unless H in MODE 1, 2. 3. or 4) because the ACTIOL of individual
- w Specifications sufficiently define the remedial measures to t
be taken.
.y SR 3.0.5 SR 3.0.5 establishes the applicability of each Surveillance o to both Unit 1 and Unit 2 operation. Whenever a requirement n; a) plies to only one unit, or is different for each unit.
H t1is will be identified with parenthetical reference.~ Notes, g or other appropriate presentation within the SR. 23 G
\
~!. BYRON - UNITS 1 & 2 B 3.0 - 18 6/16/98 Revision F I l
LCO Applicability 3.0 l 3.0 LIMITING' CONDITION FOR OPERATION (LCO) APPLICABILITY LC0 3.0 1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LC0 3.0.2 and LCO 3.0.7. LCO 3.0.2 Upon discovery of a failure to meet an LCO. the Required I Actions of the associated Conditions shall be met except as j provided in LC0 3.0.5 and LCO 3.0.6. If the LC0 is met or is no longer applicable prior to expiration of the specified Completion Time (s), comaletion of the Required Action (s) is not required unless otlerwise stated. LCO 3.0.3 When an LC0 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 ) laced in a MODE or other specified condition in which the _C0 is not a plicable. Action shall be initiated within 1 hour to p ace the unit. as applicable. in: I
- a. MODE 3 within 7 hours;
- b. MODE 4 within 13 hours: and
- c. MODE 5 within 37 hours. j i
Exceptions to this Specification are stated in the individual Specifications. Where corrective' measures are completed that permit operation in accordance with the LC0 or ACTIONS. completion of the actions required by LC0 3.0.3 is not required. LC0 3.0.3 is only applicable in MODES 1, 2, 3. and 4. t . , \ 4 l l' BRAIDWOOD - UNITS 1 & 2 3.0-1 6/30/98 Revision A L_-_. _ _ - - . _
LCO Applicability
., 3.0 3.0- LCO Applicability
[v -LC0'3.0.4 When'an LCO is not met, entry into a MODE or other specified condition in the Applicability shall not be made except when the associated ACTIONS to be entered permit continued operation in ths MODE or other specified condition in the Applicability for an uniimite'd period of time. This 9 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.
., o -
i O Exceptions to this Specification are stated in the
~"I' individual Specifications.
H. I o
- LCO 3.0.4 is only applicable for entry into a MODE or other t specified condition in the Applicability in MODES 1. 2. 3.
and 4. LC0 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under
@' administrative control solely to perform testing required to e demonstrate its OPERABILITY or the OPERABILITY of other
.i ,, i*9 equipment. This is an exception to LC0 3.0.2 for the system returned to service under administrative control to perform
'd ' M the required testing to demonstrate OPERABILITY.
g l 73
.V 3.0-2
. BRAIDWOOD - UNITS 1 & 2 5/14/98 Revision F
LCO Applicability 3.0
.3.0 LC0 Applicability LCO 3.0.6 When a supported system LC0 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 LC0 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 appro)riate Conditions and Required Actions of the LCO in w1ich the loss of safety function exists are required to be entered.
When a sup) ort system's Required Action directs a supported system to ]e 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 LC0 3.0.2. O I l l O l
.BRAIDWOOD - UNITS 1 & 2 3.0-3 6/30/98 Revision A l
LC0 Applicability 3.0 4
,. 3.0 LC0 Applicability L)
LC0'3.0.7 Exception LCOs allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other K TS requirements remain unchanged. Compliance with Exce) tion LCOs is optional. When an Exception LCO.is desired to 3e met but is'not met. the ACTIONS of the Exception LCO shall be met. When an 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.
O f f I LCO 3.0.8 LCOs,-including associated ACTIONS, shall ap)ly to each unit individually, unless otherwise indicated. Wienever the tC0 H refers to a system or component that is shared by both i@ units, the ACTIONS wi'll apply to both units simultaneously. i i f ! 1 l l Y (J BRAIDWOOD - UNITS 1 & 2- 3.0-4 5/14/98 Revision F i t l L
SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY
~
SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LC0. Failure to
)erform a Surveillance within the specified Frequency shall
]e failure to meet the LCO except as.provided in SR 3.0.3.
Surveillance do not have to be performed on inoperable equipment or variables outside specified' limits. SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met. For Frequencies specified as "once." the above interval extension does not apply. O If a Completion Time requires periodic performance on a Q "once per . . ." basis, the above Frequency extension applies to each performance after the initial performance. Exceptions to this Specification are stated in the individual Specifications. f (O
.v BRAIDWOOD - UNITS 1 & 2 ,
3.0-5 6/30/98 Revision A
SR Applicability 3.0 a
-3.0:MSURVEILLANCEREQUIREMENT-(SR) APPLICABILITY L-hh :SR 13.0.3 If it is discovered that a Surveillance was not performed
,within-its'specified Frequency, then . compliance with the' . -
requirement to declare the LC0 not met may'be delayed, from the time of. discovery, u l
. 'the specified Frequency,p to.24-hoursless.
whichever.is or upThis to thedelay limit of- ' ' . period..is permitted to allow performance of the 7 . Surveillance. If the-Surveillance.is not performed within the delay
. period; the. LC0 must immediately be declared not met, and
- the applicable Condition (s),must be entered.
When the Surveillance is performed within the delay period L 'and the Surveillance is not met, the LC0 must immediately be S: declared not. met..and the' applicable' Condition (s) must be Lentered. LSRL3.0.4 ' Entry into a MODE oriother specified condition in the Applicability'of .an' LC0 shall- not- be made'unless the LC0's
- Surve111ances have been met within their specified
- Frequency. This provision shall not prevent: entry into
; <-c - MODES or other specified-conditions in the Applicability h
f( that:are required to' comply'with ACTIONS or tlat are'part of:
+ a shutdown of the unit.
;0=
WI SR 3.0.4 is only applicableLfor entry into a MODE or other
;b '
. specified condition. i_n the Applicability-in MODES.1.' 2. 3.
'and 4.'
$(c 4
.SRT3,0.5 SRs shall apply to each unit individually unless otherwise indicated ~.
4 0" ~ ' BRAIDWOOD - UNITS 1 &~2 3.0-6
.5/14/98 Revision F
]
__._....___________.______________________________w
l L'C0 Applicability B 3.0
......+ iB 3.0: LIMITING CONDITION FOR-0PERATION (LCO) APPLICABILITY d.%
C O
-BASES 0.
. or ,
.: H 4 LCOs LLC 0 3.0.1 through LCO 3.0.8 establish the general 4- <
requirements applicable to all Specifications 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 s)ecified conditions of the Applicability. statement of eac1 Specification).
- LCO 3.0.2 LC0 3 0.2-establishes:that upon discovery of. a failure to :
meet.an LCO.-the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS
- Condition isl applicable from the point in time:that an ACTIONS Condition is entered.- The' Required Actions
' establish those remedial measures that must be'taken within
's o .._speci.fied Completion Times when the requirements of an LC0 -
(( - are not met. This Specification establishes that:
'a. ' Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification: ~ and.
lb. .-Completion of the Required Actions is not required-when an LCO is met within the specified: Completion. Time. :unless ?otherwise. speci fied. l
;3 g.i ,
)
;BRAIDWOODL-. UNITS 1 &'2o.
. B 3.0 - 1 6/16/98 Revision F 7v ] .. .
{s ,
*' ' 1 l
LC0 Applicability B 3.0 () LJ BASES LC0 3.0.2 (continued) 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. fm 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 Condition no longer exists. In this instance, the individual LCO's ACTIONS specify the Required Actions. An example of this is in LCO 3.4.3 "RCS Pressure and Temperature (P/T) Limits." O, V i BRAIDWOOD - UNITS 1 & 2 B 3.0 - 2 6/16/98 Revision A
LCO Applicability B 3.0
, BASES LCO 3.0.2 (continued)
) The Com)letion Times of the Required Actions are also applica)le when a system or component is removed from service intentionally. The reasons for intentionally. relying on the ACTIONS include, but are not limited to.- E performance of Surveillance. preventive maintenance. l . corrective maintenance or investigation of operational problems. Enter.ing 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 may result in LC0 3.0.3 being entered. 1 Individual Specifications may specify a time limit for aerforming an SR when equipment is removed from service'or
)ypassed for testing. In this case, the Completion Tim s of :
the Required Actions are applicable when this time limit i expires. if the equipment remains removed from service or j bypassed. When a change in MODE or other specified condition is O recuired to comply with Required Actions, the unit may enter a F0DE or other specified condition in which another Specification becomes applicable and the new LC0 is not met. In this'cate, the Completion Times of;the new Required Actions would apply from the )oint in time that the new Specification becomes applica)le, and the ACTIONS Condition (s).are entered. l l l O - BRAIDWOOD - UNITS 1 & 2 B 3.0 - 3 6/16/98 Revision A ____-__.._--__.__._2__-b_ - - - -
LCO Applicability B 3.0 BASES LC0 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 single Condition or combination of Conditions stated in the ACTIONS can be made that 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 Conditions corresponding to such combinations state that LCO 3.0.3 shall be entered immediately. -
This Specification delineates the time limits for placing the unit in a safe MODE or other s)ecified condition when operation cannot be mainta4.ied witlin the limits for safe operation as defined by t: e LCO and its ACTIONS. It is not intended to be used as u operational convenience that permits voluntary removal of redundant systems or components from service in lieu of other alternatives that would not (cl v result in redundant systems or components being inoperable. j Upon entering LCO 3.0.3. I hour is allowed to prepare for an orderly shutdown before initiating a change in unit operation. This includes time to permit the opera.or 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 j i components of the Reactor Coolant System and the potential ' l for a unit upset that could challenge safety systems under l conditions to which this Specification applies. The use and I interpretation of specified times to complete the actions of l LC0 3.0.3 are consistent with the discussion of Section 1.3. Completion Times. 1 (3/ BRAIDWOOD - UNITS 1 & 2 83.0-4 6/16/98 Revision A
LCO Applicability B 3.0 p] L. BASES LC0 3.0.3 (continued) 1 A unit shutdown required in accordance with LC0 3.0.3 may be terminated and LCO 3.0.3 exited if any of the following occurs:
- a. The LC0 is now met.
- b. A Condition exists for which the Required Actions have now been performed.
- c. ACTIONS exist that do not have expired Com)letion Times. These Completion Times are applica)le from the J
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 from MODE 1. 2. .
- 3. or 4 for the unit to be in MODE 5 when a shutdown is )
required during MODE 1 operation. If the unit is in a lower i MODE of operatien 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 appliceble ,
- MODE. is not reduced. For example, if MODE 3 is raached in
[]- 2 hours, then the time allowed for reaching MODE 4 is the next 11 hours, because the total time for reaching MODE 4 is not reduced from the allowable limit of 13 hours. Therefore, if remedial measures are completed that would aermit a return to MODE 1. a penalty is not incurred by I laving'to reach a lower MODE of operation in less than the ! total time allowed. In MODES 1, 2, 3, and 4. LC0 3.0.3 provides actions for Conditions not covered in other Specifications. The requirements of~LC0 3.0.3 do not apply in MODES 5 and 6 because the unit is already in the most restrictive Condition required by LC0 3.0.3. The requirements of ; LCO 3.0.3 do not apply in other specifiec conditions of the i Applicability (unless in MODE 1, 2. 3. or 4) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.
- 1 l
(} ! (/ BRAIDWOOD - UNITS 1 & 2 B 3.0-5 6/16/98 Revision A 1
l 1' LCO Applicability B 3.0 1 (d BASES LC0 3,0.3 (continued) l Exceptions to LC0 3.0.3 are provided in instances where ! requiring a unit shutdown, in accordance with LCO 3.0.3. would not provide remedial measures for the associated condition of the unit. An exam
" Spent Fuel Pool Water Level." LCO ple of this has 3.7.14 is inan LC0 3.7.14 Applicability of "During movement of irradiated fuel !
assemblies in the spent fuel pool." Therefore, this LC0 can be applicable in any or all MODES. If the LC0 and the Re
- 2. quired Actions of LCO 3.7.14 are not met while in MODE 1. l 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.14 of " Suspend movement of irradiated fuel ,
assemblies in the spent fuel pool" is the appropriate ! Required Action to complete in lieu of the actions of : LC0 3.0.3. These exceptions are addressed in the individual l Speci fications. 1 LCO 3.0.4 LC0 3.0.4 establishes limitations on changes in MODES or other specified conditions in the A) placability when an LC0 y is not met. It precludes placing tie unit in a different b MODE or other specified condition stated in that i A) placability (e.g. Applicability desired to be entered) i w1en the foliowing exist: j
- a. Unit conditions are such that the requirements of the I LC0 would not be met in the Applicability desired to i
'be entered; and '
l
- b. Continued noncompliance with the LC0 requirements, if '
the A) placability were entered. would result in the unit )eing required to exit the A) placability desired to be entered to comply with the lequired Actions. i l BRAIDWOOD - UNITS 1 & 2 B 3.0 -6 6/16/98 Revision A l
L LCO Applicability- ; B 3.0 Lc l l
.. BASES l .LC0.3.0.4.(continued)~ 'i
; Compliance with Required Actions that permit continued .i 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. 1 The provisions of this . Specification sho'uld 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 LC0 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 3revent changes in MODES or other specifi.ed conditions in' tie Applicability that
,j: result from.any. unit shutdown.
Exceptions to.LCO 3.0.4:are stated in the individual Specifications. The exceptions allow entry into MODES or Jhq L other, specified conditions in the Applicability when' the
~!- associated ACTIONS to be entered do not provide'for 1
? ' continued operation for an ~ unlimited period of time.
O 1 Exceptions:may apply to all. the ACTIONS or to a specific-
. Required Action of.a Specification.
n
.g :LCO 3.0:4Lis only. applicable when' entering MODE 4 from Ve MODE 5.' MODE 3 from MODE 4. MODE-2 from MODE 3. or MODE 1 from' MODE 2. Furthermore. LCO 3.0.4 is' applicable when y , entering anyEother specified condition in the Applicability.
._only while operating in MODE 1. 2. 3. or.4. .The
^
requirements of LCO 3.0.4 do not a) ply in MODES 5 and 6. or in other specified conditions of t1e Applicability (unless
+ in MODE l'. 2 _-3. or 4) because the ACTIONS of individual Spe 'ications'sufficiently define the remedial measures to be taken. i r
I
.BRAIDWOOD - UNITS 1:& 2 .. B 3.0 - 7 6/16/98 Revision F :
L i-
l LCD Applicability B 3.0 BASES ,y V LCO 3.0.4 (continued) . Surveillance 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, changing MODES or other specified conditions while in an ACTIONS Condition, in compliance with LCO 3.0.4 or where an
-exception to'LCO 3.0.4 is stated..is not a violation of l SR 3.0.1 or SR 3.0.4 for those Surveillance that do not (
have to be performed due to the associated 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. LC0~ 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 LC0 is to provide an (0 - 0- exception to LCO 3 0.2 (e.g., to not comply with the applicable Required Action (s)) to allow the performance of I required testing to demonstrate: f)o '" y l r6 a. The OPERABILITY of the equipment being returned to service; or Yl 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 required testing to demonstrate OPERABILITY.
This Specification 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 required testing. BRAIDWOOD - UNITS l'& 2 B .3'. 0 - 8 6/16/98 Revision F
-_________-__D
LCO Applicability
, B 3.0 BASES ~
- LCO. 3.0.5 (continued)
An example of-demonstrating the OPERABILITY of other equi) ment.is taking an inoperable channel or trip system out '
- t. ' of.tle tripped condition to prevent the trip function from occurring during the performance of. required testing on L g another channel in the other trip system. A similar example L. o.' of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the
- o. ' tripped condition to permit the logic-to function and 4 indicate the appropriate response during the performance of required testing on another channel in the same tripLsystem.
.q g.
Q. LCOL 3.0.6. LCO 3.0.6 establishes an exception to LC0 3.0.2 for support
~
systems that have an LCO specified in the Technical
? Specifications (TS). This exception is provided because LCO 3.0.2 would require that the Conditions and Required .
Actions ~ of the associated inoperable supported system LC0 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 A Actions. .These Required Actions may include entering the Q: -
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-o _ required to be declared ino)erable if determined to be-inoperable-as- a . result of_ t1e 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 Lrelated.to the entry.into multi le support and supported systems
- Conditions and Require 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 Requi_ red Actions.
i s
- . . l
.g .
BRAIDWOOD.- UNITS 1 & 2 B 3.0-9 6/16/98 Revision F J 1 C' _ _ . _ _ _ _ _ _ _ _ _ _ , . _ _ . _ _ _ . . _ . _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _
LCO Applicability B 3.0 (] v BASES LC0 3.0.6 (continued) 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 Recuired Actions for a supported system, the applicable Concitions and Required Actions snall be entered in accordance with LCO 3.0.2. Specification 5.5.15. " Safety Function Determination Program (SFDP)." ensures loss of safet appropriate actions are taken.y function Upon entry is detected into LCO and 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 sunorted system Conditions and y) f Required Actions. The SDP 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 l that the sup)orted systems of the redundant OPERABLE support ! system are 0)ERABLE. 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 LCO in which the loss of safety function exists are required to be entered. i (vD BRAIDWOOD - UNITS 1 & 2 B 3.0 - 10 6/16/98 Revision A L_________ _ _ _ - _ .
LC0 Applicability L B 3.0 BASES Q h .. LCO-3.0.7 There are certain special. tests and. operations required to s o.- be performed at various times over the life of the unit. T4 These special' tests and operations are necessary to demonstrate select unit performance characteristics, to inj : perform special maintenance-activities, and to perform
*. , l special evolutions. Exception LCOs (e.g.. LC0 3;1.8,
" PHYSICS TESTS Exceptions-MODE 2") allow specified
% Technical-Specification (TS) . requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed 1f required to comply with the requirements of these TS. Unless otherwise-
's)ecified, all the other..TS requirements remain unchanged.
T11s will ensure all appropriate requirements 'of the MODE or A other specified condition not directly associated with or
-? required to be changed to perform the special test or -
$ operation will remain.in effect.
N The Applicability of. an Exception LCO represents a condition H. not necessarily in compliance with the normal requirements y1 # of the TS. Compliance with Exception LCOs is optional A special operation may be performed either.under-the'
-provisions of the appropriate Exception LCO or under the.
.other applicable TS requirements. If it is desired to
.w' 3erform the:special operation under the provisions of the' Exception LCO.- the.feguirements of the Exception LC0 shall be followed.-
o- . . . r ,LC0 3.0.8 LCO 3.0,8 establishes the applicability of each o . Specification to both Unit 1 and Unit 2 operation. Whenever
.nj: ja requirement applies to only one unit, or is different for-
~
each unit. this will be identified in the.a)propriate
-H section of the Specification (e.g. . Applica)ility.
^
(Y Surveillance, etc.) with parenthetical reference. Notes. or . ; other appropriate presentation within'the body of the
~
requirement. L., r { 10'. -
'BRAIDWOOD'- UNITS'1 &'2. B 3. 0 - 11' '6/16/98 Revision F- ;
. l
. c' i 1-
E [ ^ SR Applicability
.B 3.0 IB 3.03SURVEILLANCE REQUIREMENT (SR) APPLICABILITY po
- d n o- BASES: '
i, i . T h.h' SRs1 :SR 3.0.1 through SR 3.0.5 establish the general requirements y> . ap licable.to all Specifications and apply at all times. I x g ,y un ess otherwise stated , *. SR13.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 requi'rements of the LC0 apply, unless otherwise specified in the individual SRs. This Specification is to ensure that Surve111ances are. performed
.to verify thef 0PERABILITY of systems and components, and t 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.
Systems and com)onents are assumed to be OPERABLE when the L associated SRs lave been met. Nothing in this. %' SpecificationJhowever. is to be construed as implying that
. systems or components are OPERABLE when: '
JA ac The systems or. components are known:to be inoperable
.. M although still meeting the SRs: or ..
z y: *
- b. TherequirementsoftheSurveillance(s)areknown!not-to be met between required Surveillance performances.
- m. Surveillance do not have to be performed when the unit is-y "in a MODE or. other specified condition for which the',
i ' requirements of.the associated LC0 are not applicable ~, 1 J unless' otherwise specified. The SRs associated with an Exception LCO are' only applicable when the' Exception LC0 is used as an allowable exception-to the requirements of a-Specification.
.o
.)
Unplanned events may satisfy the requirements (including 4~' p ' 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.
,r t ..
1CI ?
~!
BRAIDWOOD.- UNITS l'& 2' B ' 3' 0 - 12 6/16/98 Revision F
SR Applicability B 3.0 T BASES l (O SR 3.0.1 (continued) Surveillance. including Surveillance invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillance 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 )ost maintenance testing .is required to declare equipment OPERABLE. This includes ensuring applicable Surveillance 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 0PERABLE provided-testing has.been satisfactorily. completed to the extent Jossible and the equipment is'not otherwise believed to )e 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.
O ' i
-SR -3.0.2: SR 3.0.2 establishes the requirements for meeting the specified Frequency .for Surveillance and any Required l1 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; unit operating conditions that may not be suitable for conducting the Surveillance (e.g..
transient conditions or other ongoing Surveillance or ! maintenance. activities). !
.y i
uO BRAIDWOOD'- UNITS'1 & 2 B 3.0 - 13 6/16/98 Revision A / .
i SR-Applicability B-3.0
~ BASES D
%) :SRL 3.0.2 (continued) lThe.25% extension'does not significantly degrade the reli. ability..that results from performing the Surveillance at V , Tits specified Frequency. This is based on the recognition
.that the most probable result of any particular Surveillance being performed is the verification 06conformance with the
'SRs. The exceptions to SR 3.0.2 are those Surveillance for 7 gwhich the 25% extension of the-interval specified in the Frequency does not' apply. These exceptions are stated in dn, . I. the individual / Specifications. An example of where SR 3.0 2 A
ldoes not apply is-the Containment Leakage Rate Testing
.y . Program. The requirements of regulations take precedence .
over the.TS. The-TS cannot in and of themselves extend'a d3 -test ' interval specified in the regulations.
.As's'tated 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. The initia1; performance.of performance after the initial the Required Action; whether it is a particular Surveillance or some other remedial action' is considered a' single action with a single' Completion Time.E One' reason for not allowing'the-25%-
r m, extension to this Completion Time'is.that such an action - y(~" '
' usually ' verifies.that no loss of function has occurred by checking the1 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
' g'~ refueling intervals) or periodic -Completion Time intervals beyond those.specified.
s
, i 1
, [ f-
,- i t
l(}" 3 l .BRAIDWOOD'- ONI N 1'&'2. . B 3. 0 - 14 i 6/16/98 Revision F 9 a
SR Applicability B 3.0 BASES 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 within the specified Frequency. A delay
)eriod of up to 24 hours or up to the limit of the specified
- requency, whichever is less, 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 Surveillance 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
.i
' required Surveillance, and the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the.
Oe requirements. When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions or operational situations, is discovered'not to have been performed when specified, SR 3.0.3 allows the full delay period of 24 hours to perform the Surveillance, SR 3.0.3 also provides a delay period for completion of Surveillance that become applicable as a consequence of n MODE changes imposed by Required Actions or a reactor trip. ! W Failure to comply with specified Frequencies.for SRs is 4 expected to be an infrequent occurrence. Use of the delay
. period established by SR 3.0.3.is a flexibility which is not n
" intended to be used as an operational convenience to extend 1 Surveillance intervals.
i BRAIDWOOD - UNITS 1 & 2~ B 3.0 - 15 6/16/98 Revision A
s r' o . SR Applicability-B 3.0 g , BASES
- 33 -
1.f uSR53.0;3E(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 LC0 Conditions' begin
. .immediately-upon the failure of the Surveillance.
~Compietion 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 y uirements and variable limits- are met.before
(". .; ;_0PERABILITY reh5 or other specified conditions in the
. . entry into MOD
.D' Applicability for which these systems-and components; ensure; Q ' safe. operation of the. unit.
L A The provisions of this~ Specification should not be 4 interpreted as endorsing.the failure to exercise the good-
- k practice-of restoring systems or component'to OPERABLE
% ' status before entering an associated MODE or other specified '
% condition in the Applicability.
i y V# BRAIDWOOD -iUNITS 1 &'2; B 3.0 - 16 6/16/98 Revision F u_=___ _ _ _ _ _ _ _ _
- _ _ - - - - _ _ - _- -- -_ . _ = - _
L 1 Y SR Applicability B'3.0 1
' BASES ^
M
~
JSRL3;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,
. train, component.: device, or variable is' inoperable or.
loutside its specified -limits the associated SR(s) are not-
^
trequired to be performed. per SR 3.0.1. which states that surveillance do not have to be performed on inoperable
-equ pment. When equipment is inoperable. SR 3.0.4 does not
- aap y.to the associated SR(s) since the requirement for the S1(s)=to be performed is removed' Therefore. failing'to perform the Surveillance (s)-within.the specified Frequency.
~on equipment that is inoperable, does not result in an SR 3.0.4 restriction to changing MODES or other.specified conditions'of the Applicability. However, since the LC0 is not metLin this instance. LCO 3.0.4 will govern any restrictions that. may (or may not) apply to MODE or other specified ' condition changes.
hf .The. provisions of SR 3.'0.4 sht11 not prevent changes in MODES or other specified conditions in the. Applicability to :that'are required to comply with ACTIONS. In addition the provisions of-LC0 3.0.4 shall not 3revent chan es in MODES Lor:other.specified conditions in t1e Applicabi ityLthat (r"N1 )j H l result from any unit shutdown. The precise requirements for' performance of SRs are L' specified such that exceptions to.SR 3.0.4 are not. necessary. JThe ' specific time frames and conditions
- necessary for meeting the SRs are'saecified in the.
' Frequency, in the Surveillance. or aoth. ;This allows
. . performance of Surveillance when the prerequisite condition (s) specified in a Surveillance procedure require !
entry into the MODE or other specified condition in.the j i
. Applicability of'the associated LCO prior to the performance or completion of.a. Surveillance. A Surveillance that could I
, a not be performed until after entering the LCO 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 ) articular event, o N
condition.' or~ time has'3een reached. Furt1er discussion of the specific formats of SRs* annotation is' found in
;Section l'.4~. Frequency.
l
. - ..h x 1 .7 4 BRAIDWOODVUNITS l'&'2 ' ' B 3.' 0 - 17 :6/16/98 Revision F ! .c g
x=_ -
l SR Applicability j B 3.0 ) BASES
~7 U SR 3.0.4 (continued) )
SR 3.0.4 is only applicable when entering MODE 4 from I. MODE 5. MODE 3 from MODE 4. MODE 2 from MODE 3. or MODE 1 i from MODE 2. Furthermore, SR 3.0.4 is applicable when o entering any other. specified ~ condition in the Applicability j ni only while operating in MODE 1, 2. 3. or 4. The ) requirements of SR 3.0.4 do not ap)1y in MODES 5 and 6. or N in other specified conditions of t1e Applicability (unless i
'E A in MODE 1. 2, 3, or 4) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken, l,
o - tf SR 3.0.5 SR 3.0.5 establishes the applicability of each Surveillance to both Unit 1 and Unit 2 operation. Whenever a requirement 1 a) plies to only one unit, or is different for each unit, . Q tais will be identified with parenthetical reference. Notes, or other appropriate presentation within the SR. A
,n As- j i
l i jm ' BRAIDWOOD - UNITS 1 & 2' B 3.0 - 18 6/16/98 Revision F a__ .__
1 CC) A PPbbl% 3.0 (5/' LI".ITINC CONDIT!0ME FOR ODEPaTIO" At:0 SL'""E!LtdE DEQUIREu@ [-#44) APPLICABILITY} (Reoion w/wserl LIMITING CONDITION FOR OPERATION Iu e) ( 3 o.l A) no 3.0.1]JCompliance with the Limiting Conditions for Operation contained in th'es Q succeedingspecificationsisrequireddurinatheOPERATIONALMODESorotherj [ conditions specified therein; err;t th tJMhon failure to meet-the Limiting T t (Conditions for Operation, the associated s ..,. ACTION
--..~..~requirements
- ~ .~ ~ ~
shall be met,. j Rio 3l0.2NNenceT H=aca with a :pe:ificatter :h:1' exi:t ch:r th: eq 9 r :nt of g th: Li ' tin;; Cendit4aa 'er Oper:tien :nd :::::f:t d ^.CTIO!? require. nt: :: nat et "!tF - th :g :i'f:d ti:: ir,t:rv:h. If the Limiting Condition for - - - j Operation is restored prior to expirati'on of 'the specified time intervals, Orla' ' -/ ' ompletion of the ACTION requirements is not requiredv'" **'we =O h"+
'3.0-tB Dco 3.0.37 When a Limiting Condition for Operation is not met, except as provide 3
Iin the associated ACTION requirements, within 1 hour action shall be initiated to place the unit in a MODE in which the specification does not apply b placing it, as applicable, in: epInce w7
- a. At least HOT STANDBY within the next 6 hours, s b.
h4 { At least HOT SHUTDOWN within th L 3 o.tc)
- c. At least COLD SHUTDOWN within th following6 subsecuent 24hours,andj(
hours / Where corrective measures are completed that permit operation under the ACTION requirements, the action may be t? ken in accordance with the specified time limits ) as measured from the time of failure to meet the Limiting Condition for Operation. I Exceptions to these requirements are stated in the individ0al specifications. t This specification is not applicable in MODE 5 or 6.
~
Entry into an OPERATIONAL MODE or other specifie'd condition shall not N*".aM x-Cu c 3. 0_. 4'> 5.o- tb j 3 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 interval. U. T Entry into an OPERATIONAL MODE or specified condition g g I' may be made in accordance with ACTION requirements when conformance to tham e4 permits continued operation of the facility for an unlimited period of time. { $ This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements. Exceptions to these requirements i are stated in the individual specifications] 3 0 8 34:t- Limiting Conditions for Operation including the associated ACTION require-ments shall apply to each unit individually unless otherwise indicatedges m towr.J ^ m ~ JK (Whenever the Limiting Conditions for Operation re'ers to systems or components which are shared by both units, the AC. ON requirements it 9<l 3g 4 will apply to both units simultaneously. gta r
- b. Wh' ever the Limit unit, his w Cond1 e identified in for Operation apiT M ~ to only PPLICABILITi s ttion the b 4
specifi on; and G c. enever cer n portions of a specification ntair; ting param- , V eters, Setpoints, etc., which are diffe for each unit, ' will 8 ) he identified in pa ntheses, footn 5 or body of the requiremen . k Ndos.o. SWInsteri % err __(Eo 3 oa}@ InstitT (t c o A o. -i BYRON - UNIT 51 & 2 (3.o.igj 3.o.ir, 3/4 0-1 Jo-ic AMENDM NO. 49 hjy ;q Red Y
- t
CTS INSERT (S) SECTION 3.0 (- V LC0 3.0 l INSERT 3.0 1D (L3) 5 .When an LCO is not met, entry into a MODE or other specified condition in the o Applicability shall not be made except when the associated ACTIONS to be D n entered permit continued operation in the MODE or other specified condition in M the Applicability for an unlimited period of time. This Specification shall not prevent changes in MODES or other specified conditions in the y Applicability that are required to comply with ACTIONS or that are part of a Qy shutdown of the unit. Exceptions to this Specification are stated in the individual Specifications. LCO 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, 3. and 4. INSERT 3.0 1E (L2 ) Equipment removed from service or declared inoperable to comply with ACTIONS o b may be returned to service under administrative control solely to perform tj' o' testing required to demonstrate its OPERABILITY or the OPERABILITY of other d l equipment. This is an exception to LCO 3.0.2 for the system returned to rf service under administrative control to perform the required testing to
- demonstrate OPERABILITY.
r% 5/14/98 Revision F V
N A Mefel ?? P. 3o l ProgrW and MM 5.5 i
@PPLICABILITYK SURVEILLANCE REQUIREMENTS (Continued)
ASME BOILER AND PRESSURE VESSEL REQUIRED FREQUENCIES FOR
/ COEE AND APPLICABLE ADDENDA PERFORMING INSERVICE TE,tMIN0 LOGY FOR INSERVICE
{ INSPECTION AND TESTING INSPECTION AND TESTING ACTIVITIES ACTIVITIES g*j *3 s Weekly At least once per 7 days Sub E.S. J Monthly At least once per 31 days b'# # M I Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months. At least once per 184 days " i Seckna 5.0 Every 9 months At least once per 276 days Yearly or annually At least "once per 366 days
- c.
- The provisions of Specification 4.0.2 are applicable to the above j required frequencies for performing inservice inspection and testing i activities;
- d. Performance of the above inservice inspection and testing activities E
.shall be in addition to other specified Surveillance Requirements; and '
!e. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed tt to supersede the requirements of any. Technical Specification.
' 3
/C] se3.o.r4-fh4 Surveillance Requirements shall-apply to each unit individually unless otherwise indicated ps stateam.. e -o m ea un 5 h *':
Q U Ttions or whenever cert - ns of ah.0.a ror inaiviauas
- ntain surveillance specificam l parameters 4
.n for each unit, which will be ident theses, f s or body of the requirement.
. i O
BYRON - UNITS 1 & 2 3/4 0-3 QA] f
LCO app M O .5.0 gf' L "!T!"O ca"SITIONS-F0* OPERATION-ANS-SLHtVElbtANGE-#EWIAM
N ~ ' (APPLICA8I LITYL > 'O LIMITING CONDITION FOR OPERATION (LcOh h p M w/IWERT, 3 She -IAJ h3.0.1)[ompliancewiththeLimitingConditionsforOperationcontainedintheh (succeeding specifications is required. duriro the_0PERATIONAL MODES or other / .
As lconditions'specified therein; emeept--the4J@on failure to meet the Limiting (Conditions for Doeration,t thec acemeanciated ACTION r=airm.ts shall be met, n a., w .r.a a . . ao .ws ..s .r o .<., Lco 3.0. ~ 5:d un;; ;f th e ==c m ceti- th:1Leximen the ng;;;nt er
'the Lfeftin; Cerd!t!:: fr- Wet 4- end :::ee4eted AG:FION-requirements-are OA2 -et =+ uthS Q .ynified th; ht:n:h. If the Limiting Condition for -
Operation is restored prior to expiration of the specified time intervals, i %* */ kompletion of the ACTION requirements is not required %h'" *~"e =hD MEU e v3.o_ i t, LL?c) 3.0.l) When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements, within 1 hour' action shall be initiated 3 to place the unit in a MODE in which the specification does not appi placing it, as applicable, in: rhpm @
- a. At least HOT. STAND 8Y within the next 6 hours : M. W
- b. AtleastNOTSHUTDOWNwithinthefollowing6 hours,any L 3.0 Ic )
- c. At least COLD SHUTDOWN within the ubsecuent 24 hours.1 t
.Where corrective measures are completed that permit operation under the ACTION D q requirements, the action may be taken in accordance with the.specified time limits c as measured from the time of failure to meet the Limiting Condition for Operation.
Exceptions to these requirements are stated in the individual specifications. j
@(ThisspecificationisnotapplicableinMODE5or6. [
3.4) Entry into an'0PERATIONAL MODE or other specified condition shall no ntwa % l be made when the conditions for the Limiting Conditions- f Operation are not 3-
\
met and the associated ACTION requires a shutdown if the are not met within < specified time interval. Entry into an OPERATIONAL MOD or specified conditio G may be made in accordance with ACTION requirements when conformance to them L5 g permits continued operation of the facility for an unlimited period of time. 4 This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements. Exceptions to these requirements are stated in the individual specifications. J.0,8 0 Limiting Conditions for Operation including the associated ACTION require-ments shall apply to each unit individually unless otherwise indicate N inwt] q y Cwhenever the timitin, Conditions for Operation refers to systems or i4.1 components which are shared by both units, the ACTION requirements will apply to both units simultaneously. )f hr b. WpevertheLimitingCyoft1ons forsaperan on .yviiwe i.e un ; , his will b ntified in the AP)t! ILITY sect
^
y one of the % f specifi , nd
- c. W er cart eters, Setpoints, portions of a specification e c., which are different in o (ingparam-r each unit, thi will g
body of the requiremen w n Lt be identified in_ pare ases, footnotes e $F BRAIDWOOD - UNITS 1 & 2 , 3/4 0-1 AMEN 0 MENT NO. 38 0 D4 F N@h
l CTS INSERT (S) SECTION 3.0 I
'/-
LC0 3.0 p lINSERT 3.0 1D (Ls)
> When an LCO is not met, entry into a MODE or other specified condition in the O Applicability shall not be m'ade except when the associated ACTIONS to be 4
entered permit continued operation in the MODE or other specified condition in 9 the Applicability for an unlimited period of time. This Specification shall tu not prevent changes in MODES or other specified conditions in the wlA]plicabilitythatarerequiredtocomplywithACTIONSorthatarepartofa slutdown of the unit. Exceptions to this Specification are stated in the individual Specifications. LCO 3.0.4 is only applicable for eritry into a MODE or other specified condition in the Applicability in MODES 1. 2. 3. and 4. INSERT 3.0 1E (L,) h Equipment removed from service or declared inoperable to comply with ACTIONS
~
o may be returned to service under administrative control solely to perform i' ') f testing required to demonstrate its OPERABILITY or the OPERABILITY of other g equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing to f demonstrate OPERABILITY. i (~': 5/14/98 Revision F
')
I L J
5 A t w \i A li g 5.0 Etograms e.J bak5 5 i hPPLICA j O suaverua~ce asoutacae"'l > <c t4 SME BOILER AND PRESSURE VESSEL REQUIRED FREQUENCIES FOR CODE AND APPLICABLE ADDENDA - - PERFORMING INSERVICE TERMIN0 LOGY FOR INSERVICE INSPECTION AND TESTING ~ INSPECTION AND TESTING ACTIVITIES ACTIVITIES 7 Weekly At least once per 7 days Udrus d i Monthly At least once per 31 days Seebo 5. 5 ', Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days he 00C b / Every 9 months At least once per 276 days (Suhh 5.0 / _ Yearly or annually At least once per 366 days
- c. )
The provisions of Specification 4.0.2 are applicable to the above required frequencies for performing inservice inspection and testing , activities; -
- d. Performance of the above inservice inspection and testing activities
-- - ,t. 1 te ir,cdditicr. Lo cL .a. spaci f!ad ~.. .*i;
- e.. e ~
- eyv . ei ...n . oivu
- e. Nothing in the ASME Boiler and Pressure Ve'ssel Code shall be construe to supersede the requirements of any Technical Specification-sit 3 0.f
( 4-076- Surveillance Requirements shall apply to each unit individually unleu l ' Q v otherwiseindicatedfassaseoinspectricatin3.0.5forindiviualspecifical
- 4. ions or henever cert n portions of a sp ification contain surveillance s
Lg, l parame rs different r each unit, which ill ba identified in parenthese ! footn es or body of he reovirement. ? e Lt. O l 4 cat r= v i i BRAIDWOOD - UNITS 1 & 2' 3/4 0-3 Oe Pa F
DISCUSSION OF CHANGES TO CTS ITS SECTION 3.0 - LC0 AND SR APPLICABILITY O TECHNICAL CHANGES - LESS RESTRICTIVE " Generic" (LA) LA 3 CTS LCO 3.0.5 and SR 4.0.6 provides guidance that clarifies the applicability of each LCO or surveillance activity for dual unit operation, as well as specific examples for exceptions to the guidance. The structure of the ITS provides specific examples for clarification of dual unit operation requirements, restrictions and exemptions, to be 3' detailed within the Bases. The specific detailed guidance in 9 CTS LC0 3.0.5.b. 3.0.5.c and portioris of SR 4.0.6. does not provide M added exemptions or restrictions to the TS and direct application of the TS selection criteria is not appropriate. Thus. this information is to
.gl be relocated to the Bases for ITS LC0 3.0.8 and SR 3.0.5. The g requirements of ITS Chapter 1.0. Section 3.0. and the format and structure of the ITS are adequate to ensure the correct interpretation l of the ITS. AS sJCh. the specific detailed guidance in CTS LCO 3.0.5 and SR 4.0.6 are not needed to provide adequate protection of the public health and safety.
O BYRON /BRAIDWOOD UNITS 1 & 2 3.0 9 5/14/98 Revision F O
; e DISCUSSION OF CHANGES TO CTS ITS SECTION 3.0 LC0 AND SR APPLICABILITY L3 CTS LC0 310.4 and. CTS SR 4.0.4 are applicable for entry into all MODES.
The proposed change revises the applicability of these Specifications to'
- i. not prevent' unit shutdowns and will apply only to entry into MODES 1, 2..
! i3 and 4. .This change.is less restrictive in that it will allow MODE ! > > ! changes from either direction into MODES 5 and 6 while operating within-
'9 an Action with a finite period or prior to performance of a SR, .This
- Q 1- change is also less restrictive in that MODE changes that are a' part of-g a' unit shutdown are not prevented.. All ITS Actions were evaluated for.
' individual acceptability of this change Based on this evaluation where MODE change restrictions.were determined to be required in MODES 5 and 6.- or in' MODES 1. 2, 3, and 4 during unit shutdown Notes containing the appropriate MODE change restrictions are. added to the individual Specifications.
-gg 1
I I l i f 1. BYRON /BRAIDWOOO UNITS 1 & 2- 3.0 12a- 5/14/98 Revision F
1 LCO Applicability 3.0
-3.0 LCO APPLICABILITY O LCO 3.0.4 Specification shall not prevent changes in MODES or other (continued) specified conditions in the Applicability that are required j
to comply with ACTIONS or that are part of a shutdown of the 1 11. unit. 5 *3 Exceptions to this Specific _ation are stated in the p individual Specifications.f These exceptions allg>(entry q into MODES ofr other specified' conditions in the/ { o
- Applicabi.l'ity when the assodiated ACTIONS to be entered I d OCG~allowunitoperationinJh'eMODEorothersp6cified 2 condition in the Applicability only for a/imited period of l 4
[ timeg LCO3.0.4isonlyapplicableforentryintoaMODEoroth specified condition in the Applicability in MODES 1, 2, 3, 4 and 4. wers's Note: LCO 3.0.4 has been revised so that cha n MODES or other specified conditions in th Applica -Qythatarepartofashutdownofthe it shall not be prevented. In addition, LC0 3.0.4 ha een revised so that it is o7n applicable for entry o a MODE or other specified condition n the y Applicabi 6y in MODES 1, 2, 3, and 4. The MODE change restrict s in LCO 3.0.4 were A @c previously kpplicable in al ES. Before this version of V LC0 3.0.4 can be impleme on ant-specific basis, the licensee must review e existing tec cal specifications to determine wher specific restrictions , Required Act shouldbeincludedinindiv$DEchangesor ic 1 LCOs to justify t - change; such an evaluation should be .arized , in a rix of all existing LCOs to facilitate NRC staff j r ew of a conversion to the STS. _ ] LCO 3.0.5 . Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under p administrative control solely to perform testing required to b
/ demonstrate its OPERABILITY <ap the OPERABILITY of other ?
[ o var ,'blee /f quipmenta This is an exce,ption to LCO 3.0.2 for% Qth b JA . returned to service under administrative control to perform li .h. thegestingfrequirec)todemonstrateOPERABILITY. t BQ j i i ( MM _ l l l f (continued) ('> ' Rev 1, 04/07/95 WOG STS- 3.0-2
LCO Applicability 3.0 Chou be 9- rned) O 3.0 'LCO APPLICABILITY- (continue'd) 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, "
" h - c(n fiti: Oevaluatior? : d -"m:= r; 5: r ;uir @ in accordance with' Specification 5.5.15, " Safety tunction i
. 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 hb GER Exception .LCOsEL i 9. 2 : .:e. e.: . : , ;- ; 2. = 15 allow specified Technical Specification ("S) requirements to be changed to~ permit performance of special. tests and g.
5 operations. Unless otherwise specified, all-other TS requirements remain unchanged. : Compliance withGED Exception-LCOs is optional. When " IException LCO is ' desired to be met but is not met, the ACTIONS of the EED Exception LC0 shall be met. When M _lException LCD 1s 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. I e Lco 3,o.1 lNSE72 r 3.0- 3 A 3' wm k- t k C ' 3.0-3 Rev 1, 04/07/95 I WOG STS-l L'
I l I 1 l ? l LCO INSERT (S) SECTION 3.0 U,. LC0 Applicability 3.0
, INSERT 3.0 3A (P3 )
O n LCO 3.0.8 LCOs, including associated ACTIONS, shall ap]ly to each unit j individually. unless otherwise indicated. Wienever the LCO refers to a system or component that is shared by both units. the ACTIONS will apply to both units simultaneously. (3
's)
G 5/14/98 Revision F L)-
)
I 1
L SR Applicability
.i.
3.0
'3.0! SR APPLICABIL'ITY.
SR' 3.0.3 . . declared not met, and' the applicable Condition (s) must be
-(continued) entered.
m T.
, SR 3.0.4 Entry into a MODE or.other specified condition in t'he d Applicability of:an'LCO shall not be made unless the LCO's %
Surve111ances have been met within-their.specified Frequency. This provision.shall: not prevent: entry into f; E MODES or other. specified conditions in the Applicability u that are required to comply with ACTIONS or that are part of.. a shutdown of the unit. 1.L - SR 3.0.4 is only applicable for entry into, a MODE or other
- g-and4.specified condition :in the Applicability in M00ES.1, 2, y -
iewer's Note: SR 3.0.4 has been revised so that c ' es
- i NODES or' other specified conditions .in the Appl ility
- that ar art of'a shutdown of the unit shall' be L prevented. addition, SR 3.0.4 has been vised so that it.is only. app cable.for entry into E or other i
-g specified conditioii'i('the Applica ty in M00ES.1,-2, 3, l-<- . and 4. The MODE change restri ons.in SR13.0.4 were 3
f previously applicable in~ a ES.. Before this version of
. SR 3.0.4 'can be imple d on'asplant-specific basis, the-licensee must revi e existingftechnical specifications to~ determine wh specific restrictions 9 n MODE changes or Required Ac ns should be included in indtv4 ual LCOs- to -
justify is. change; such an evaluation shoul(d) umarized in atrix of all, existing LCOs to facilitate NRC ta kg view of a conversion to the STS. r
'Sl? '5,0 5
. [lNGELT" 3.0-5h \ g k
@ 32 x @-
v s 1 1 LW .
.V WOG STS. 3.0-5 Rev 1, 04/07/95-
)
I
LC0 INSERT (S) SECTION 3.0 SR Applicability 3.0 O d INSERT 3.0 5A (P3) (w w SR 3.0.5 SRs shall apply to each unit individually, unless otherwise ( indicated. 4 O E I s'14'98 nevisio" r O
- .y l
JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 SECTION 3.0 LC0 AND APPLICABILITY l0 BRACKETED CHANGES (B) L B3 The. brackets were removed. and th'e information labeled as " Reviewer's 1 Pote" was deleted. Reviewer's Notes are used as guidance information in i toe development-and review of the document and are not retained in the plant specific ITS.-
- GJNERIC CHANGES 2(C) l-C This change is consistent with NUREG-1431. as modified by TSTF-6.
l lr t Revision 1 (NRC approved). C. 2 -Not.used.
#gv.l ' ( _Not used.
Ce - This_ change.is consistent with NUREG-1431. as' modified by TSTF-12.
~ Revision l'(NRC approved).
' 94-o ,[* [)1 'Not S
C used, i
'C 6 .
This change is' consistent with NUREG-1431. as modified by TSTF-104 (NRC q ' approved). i ;C n - This change is consistent' with NUREG-1431. as modified by TSTF-136 (NRC approved). M 4 ' C, This change is consistent with NUREG-1431~ as modified by TSTF-166 (NRC b' approved).
- i. ,
L' l L i D~ ' BYRON /BRAIDWOOD - UNITS 1 & 2 3.0 1 5/14/98 Revision F
. D.
-_ _ _ _ _ _ _ _ _ _ _ _ _ _ - - ___=_____ _ _ _ _ _ _ _ _ _ . _ _ _ _ _. -_ - _ = _ _ _
JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 SECTION 3.0 - LC0 AND APPLICABILITY
. p ..
n
- t PLANT SPECIFIC CHANGES (P) o
. Q[P 1 -Not~used.
Y P2 LC0 3.0'.7 and associated Bases were revised to refer to " Exception LCOs," rather than " Test Exception LCOs." The change allows exception-to apply ~to.more_than testing such as special tests and operations. P3 ITS LCO 3.0.8 and'SR 3.0.5 are included (consistent with CTS LCO 3.0.5 and'SR 4.0.6) to clarify the application of the single set of Technical Specifications to dual units.'
~
. m
. 2.
E
.sm 10; ~
~
] ' BYRON /BRAIDWOOD . UNITS 1 & 2 3.0 2 5/14/98 Revision F l-
LCO Applicability B 3.0 B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES e LL ? } LCOs
@ LCO 3.0.1 through LCO 3. kestablishthegeneral requirements applicable to 11 Specifications and apply at all times, unless otherwise stated.
}-
k LCO 3.0.1 LCO 3.0.1 establishes the Applicability ' statement within each individual Specification as the requirement for when the LCD is required to be met (i.e., when the unit is in the MODES or other specified conditions of the App.licability 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 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 an LC0 9 are not met. This Specification establishes that:
- a. Completion of the Required Actions within the specified Completion Times constitutes compliance with a Specification; and
- b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering (continued) O WOG STS B 3.0-1 Rev 1, 04/07/95
1 LC0 Applicability B 3.0 BASES LCO 3.0.4 that are required to comply with ACTIONS. In addition, the
' (continued) provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability sthat ,
result from any unit shutdown. gn,,Ng a g_gg , 3 g .g Exceptions to LC0 3.0.4 are stated in x thexindividual x x T S hnsert B3.oM specifications.t Exceptions ito a specific Required mayofapply Action to all the ACTIONS or a Specification. I LCO 3.0.4 is only applicable when entering MODF 4 from M00E-5, M00E 3 from MODE 4,'M00E 2 from MODE 3, or MODE 1 from MODE 2. Furthermore, LCO 3.0.4 is applicable when "
'\ .\ ' \. entering any_other specified gondition in the Applicability "b3
~
uht % only while operating in M00E01, 2, 3, or 4. The requirements of LC0 3.0.4 do not apply in MODES 5 and 6, or 3 o: i in other specified conditions of the Applicability.(unless W "1 in MODE l, 2, 3, . or 4) because the ACTIONS of individual 5 ) Specifi@ cations sufficier tly define the remedial measures to it ' be taken. f[In some gae6 (e.g., .. these ACTIONS pro de a'
- M Hote that ates ".M ile'this LCO is n met, entry ' oa MODE or othe ecified condition in the _ lic ity is. f/
not permij dd,- less required to comply wit IONS." l O6 2 This Jore-is a re rement explicitly preggcing it.to .l j u. yaE or other spec ledconditionof)MeApplicabili . Surveillance do not have to be performed on the associated inoperable equipment (or on variables outside the specified
!11mits), as permitted by.SR 3.0.1. Therefore, changing MODES or other specified conditions while in an ACTIONS Condition, in compliance with LCO 3.0.4 or where an !'
. exception to LCO 3.0.4 is stated, is not.a violation of E SR 3.0.1 or SR 3.0.4 for those Surveillance that do not have to be performed due to the associated inoperable,
; equipment. However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or L variable within limits) and restoring compliance with the l affected LCO. ,
~LCO 3.0.5 - LCO 3.0.5 establishes the allowance for restoring equipment l to service under administrative controls when it has been .
removed from service or declared inoperable to comply with n ACTIONS. The sole purpose of this W is to LCCO (continued) 1 LO; p' WOG STS. B 3.0-6 Rev I, 04/07/95 L L
' BASES'. INSERT (S)
SECTION 3.0
'[. .
Bases 3.0 AlINSERTB3.06A Qs g .0 l; - Deleted in Revision. F l
;~ m INSERT B' 3'.0 66 '(C3 )
The exceptions allow 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. 3' RI0 . . .. Jgl .. INSERT B 3.0 6C d Deleted.in Revision F
-l 5/14/98 Revision F e-. _- r -._ _ : __-____=___--______----_-._-__.____--______-____:___-_-___-__--____--__-----.__._____-___-__L
LCO Applicability B 3.0 - BASES LCO 3.0.5 provide an exception to LCO 3.0.2 (e.g., to not comply with (continued) the a plicable Required Action (s)) to allow the performance of to demonstrate:
% uired +edviq9 0 Qo
- a. " The OPERABILITY of the equipment being returned to service; or A \ N w f.
i b.
% v The OPERABILITY of other equipment. 3C
-e 6-1 4 The administrative controls ensure the time the equipment is Eg
' ' v
\ T returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to repted4eding perform theOllend ""f. This Specification does not b 4tmondmie. --pfDWoe time to perform any other preventive or corrective SPE%BluTYJ maintenance. -
An example of demons'trating the OPERABILITY of the equipment OCio 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 thc @ .3
' ~\ \
An example of demonstrating the OPERABILITY of other NWk 'S 4 equipment is taking an inoperable channel or trip system out f L eu- pie ' of the tripped condition to prevent the trip function from ( h
- ha9
- v. w , ." @. Y }\ in the other trip system.A occurring during of the performance o similar example g [y %,
. Q^(^g j demonstrating the OPERABILITY of other equipment is taking
,, an inoperable channel or trip system out of the tripped 4
h i.ed wa condition to permit the logic to function and i te the it u&cd 6sa appropriate response during the performance of on , era 4p 6 cs M n., - n. nother channel in the same trip system. 1 (o LCO 3.0.6 LCO 3.0.6 establishes an exception to LCO 3.0.2 for support
]mk -
systems that have an LCO specified in the Technical 4-
-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 '
(continued)-
.WOG STS. B 3.0-7 Rev 1, 04/07/95
LCO Applicability 8 3.0
.' ;ES LCO 3.0.6 system are OPERABLE, thereby ensuring safety function is (continued) retained. 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.
( (e.o. , LCO 3.0.7 ( There are certai'n special tests and operations required toI be performed at various times over the life of the unit. These special tests and operations are necessary to # c demonstrate select unit performance characteristics, to g perform special maintenance activities, and to perform special evolutions. GED Exception LCOs C 11 r m ( ig} 3, C3 d.:.-n. ar: 3.4.;;D allow specified Technical ig C9 Specification (TS) requirements to be changed to permit s 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 T5 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 dEEEEEE eption LCO represents a j condition not necessarily in compliance with the normal requirements of the TS. Compliance with M Exception LCOs h is optional. A special operation may be performed either '$A ot under the provisions of the appropriate Eltib Exception LCO *; or under the other applicable TS requirements. If it is ; desired to perform the special operation under the provisions of the (EE D Exception LCO, the requirements of 5 the @ Exception LCO shall be followed. C o L IMercr 8 3.0- 9A? *b 3m
'O *dv O
WOG STS B 3.0-9 Rev 1, 04/07/95
l BASES INSERT (S) SECTION 3.0 O Bases 3.0 INSERT B 3.0 9A (P6 ) LCO 3.0.8 LC0 3.0.8 establishes the applicability of each
~
Specification to both Unit 1 and Unit 2 operation. Whenever 7 a requirement applies to only one unit, or is different for o each unit this will be identified in the a3propriate
$ section of the Specification (e.g. . Applica)ility.
Surveillance, etc.) with parenthetical reference., Notes, or l y other appropriate presentation within the body of the requ1rement.
,n L) l q 5/14/98 Revision F C/
SR Applicability B 3.0 B 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY O BASES y SRs SR 3.0.1 tothrough applicable tablish tions SR 3.0.f, all Specifica the general and requirements apply at all j times, Tc unless otherwise stated. $ 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 Surveillance 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. 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: Q a. The systems or components are known to be inoperable, although still meeting the SRs; or i
- b. The requirements of the Surveillance (s) are known not to be met between required Surveillance performances.
Surveillance 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, 5 unless otherwise specified. The SRs associated with a: Nam fxceptiogare only applicable when the@ gfceptiontis used as afrtallowable exception to the requirements of a D Specification. h Q3.0-10A) Surveillance, including Surveillance invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillance have to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status. (continued) O B 3.0-10 WOG STS Rev 1, 04/07/95
f I SR Applicability l B 3.0 L f-BASES SR 3.0.1 Upon comple' tion of maintenance, appropriate post maintenance (continued) testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillance are not failed b' " 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. SR 3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillance and any Required Action with a Completion Time.that requires the periodic performance of the Required Action on a "once per . . ." interval . . NI n SR 3.0.2 permits a 25% xtension of i.is interval specified U in the Frequency. This extension facilitates Surveillance scheduling and considerST5Doperating conditions that may , not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or l { maintenance e.ctivities). 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 ]
1 that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. The exceptions to SR 3.0.2 are those Surveillance for which the 25% extension of the interval specified in the Frequency does not apply. These exceptions are stated in the individual Specifications. ' An example of where SR 3., 2 does not apply isfa Sury'e111ance withf Frequency of "in C ccordance wiTh70 CFR/50. Aopendix 7. as modified /bv - oorovad/avaiti e:. # The requirements of regulations take u. d
' fprecedenceovertheTS. The TS cannot in and of themselves extend a test interval specified in the regulations. [ 16) g
-G hc Contain ment Lect 00e Rde Te:Vmo Program] $
i (continued)
] WOG STS B 3.0-11 Rev 1, 04/07/95 l
E l' q:
}
SR Applicability
. B 3.0
.8ASES ,
O '
.o SR 3.0.4 The provisions of this-Specification should not'be
-(continued) interpreted as endorsing the failure to exercise the good. kjg practice of restoring systems or component to OPERABLE status before entering an associated MODE or other specified- 3 condition in the Applicability.. fyg
~
'However, in certain2 circumstances,'failing to meet an SR Y will not result in SR 3.0.4 restricting a MODE change or
'other specified condition change.- When a system,' subsystem,
.@ Mrem deutzsam, 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
~'
_ surveillance 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 8'" % ,# w performadoes.not the result Surveillance in an SR(s) within 3.0.4 the specified restriction Frequency to changing' MODES
$ L%4nw=M4 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.
<j-The. provisions of.SR 3.0.4 shall not prevent changes in MODES o'r other specified conditions in the Applicability -)
that are required to comply with ACTIONS. In addition, the
)
'g .
provisions of LCO 3.0.4 shall not prevent changes in MODES or other.specified conditions in the Applicability that l {d n a- # M !
- u. -
~Mg; 6i sg1 4 % result from any- unit shutdown. i
~r The precise requirements for performance of SRs are
@g 3,
- N * ' M *% specified such that exceptions to SR 3.0.4 'are not
~ \ 3. '
- N 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 Surveillance when the prerequisite condition (s) specified in a Surveillance procedure require 4 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 i not be performed until'after entering the LCO Applicability, 1 - 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 j required (to be met or performed) until a particular event, ! (continued)
,W !
- %A 1
WOG S'TS B 3.0-14 Rev 1, 04/07/95 l l
SR Applic' ability B 3.0' BASES _ ().
. SR 3.0.4.- .
condition, or time has been reached. Further discussion of (continued) the specific formats of SRs' annotation is found in ; Section 1~.4, Frequency. (Mo0Ej j
. SR 3.0.4 is only ' applicable entering MODE 4'from MODE 5, MODE 3 from MODE 4,
@ from MODE 2. 'Furthermore.
entering any other specified ondition in the Applicability-2 from MODE'3,,or MODE I 0.4 is applicable when ^ T only while operating in MOD 1, 2, 3, or 4. -The . LL 1: requirements of SR 3.0.4 do not apply.in MODES 5 and 6, or j in oth specified conditions of the Applicability (unless 3 e _ in MOD 1, 2, 3, or 4) because the ACTIONS of individual-
-c M k , o,o s
- Specif tions sufficiently define the: remedial measures to QG q v
r be taken. s s s lMSE2T- 8 5.0-ISA [ q w.~ p E b y l l
't' l i- i l
i i h - WOG STS .B 3.0-15 Rev 1, 04/07/95 9
3 BASES INSERT (S) 4 SECTION 3.0
"'s (O Bases 3.0 INSERT B 3.0 15A (P3 )
? SR 3.0.5 SR 3.0.'5 establishes the applicability of each Surveillance j to both Unit 1 and Unit 2 operation. Whenever a requirement a) plies to only one unit. or is different for each unit.
i# t11s will be identified with parenthetical reference. Notes. or other appropriate presentation within the SR. (l v 5/14/98 Revision F , (-)
\
f I
l i JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 BASES SECTION 3.0 LC0 AND APPLICABILITY Q BRACKETED CHANGES (B)
'None.
GENERIC CHANGES (C) C3 Not used. i.
'C2 This change.is consistent with NUREG-1431 as modified by TSTF-8.
Revision 2 (NRC' approved). C, a This change is consistent with NUREG-1431 as modified by TSTF-12. l -- Revision 1 (NPC approved). C4 Not used. AA 3 '#h C3 Not used. 6g y,0 ii
. C. This change is consistent with NUREG-1431 as modified by TSTF-52. An editorial clarification was made to retain the discussion of the 25%
l Surveillance extension proposed for deletion in TSTF-52.
,p'l C, Not used. \ '#
C,' ' This change'is consistent with NUREG-1431. as modified by TSTF-104 (NRC approved). C, This change is consistent with NUREG-1431. as modified by TSTF-136 (NRC l approved). ' 7A2 to-ULC 3 This change is consistent with NUREG-1431. as modified by TSTF-165 (NRC approved)
~
l i-L 1. UNITS 1 & 2 3.0-1 fu] BYRON /BRAIDWOOD 5/14/98 Revision F
= _ _ _ _ _ _ _ _ _ _ _ _ _ _ - _ - _ _ _ _ - __-__ __ .
L L JUSTIFICATION FOR DIFFERENCES TO NUREG 1431 BASES SECTION 3.0 LC0 AND APPLICABILITY
.c .
d PLANT SPECIFIC CHANGES (P) Pr .During the development certain wording preferences. English language conventions. . reformatting, renumbering, or editorial rewording
, consistent with plant specific nomenclature were adopted. As a result, l the -Technical Specifications (TS) should be more readily readable by.
i and therefore understandable to, plant operators and other users. During this reformatting, renumbering. and rewording process, no technical changes (either actual or. interpretational) were made to the TS unless they were identified and justified.
.d-l.
' h 0lP 2 Not used.
-Q o -P:
N 3 .The change proposes to delete the word " routine" to maintain consistency with the wording of the Bases for LC0 3.0.2. The Bases for LCO 3.0.2 states that " Intentional entry into ACTIONS should not be made for operational convenience." This does not state any provision for
" routine" or "non-routine" within the condition.
P. LCO section of the Bases for Section 3.0 was . revised to specify the last I
'LC0 of.the section. The last LCO discussed is LC0 3.0.7 which was added in by NUREG-1431. Revision 0. Change NRC-03. C.5 to address test exception.LCOs. This change is provided to be consistent ~with the
. change provided in NUREG-1431. Revision 1 and with the remainder of the 4 .section.
2 P3 LC0 3.0.7 and associated Bases were revised to refer to " Exception LCOs" 1 ;h I rather than " Test Exception LCOs.." -The change allows exceptions to
'Ek l apply to more tnan testing such as special test and operations. l P. .ITS LC0 3.0.'8 and SR 3.0.5 are' included (consistent with CTS LCO 3.0.5 g and SR 4.0.6) to clarify the application'of the single set of Technical i Specifications to dual units.
ho
.Q :
_ BYRON /BRAIDWOOD UNITS 1 & 2 3.0 2 5/14/98 Revision F
.NO SIGNIFICANT HAZARDS EVALUATION L
ITS SECTION 3.0 - LCO AND SR APPLICABILITY
, ' TECHNICAL CHANGE LESS RESTRICTIVE "Soecific"
("LO Labeled Comments / Discussions) Commonwealth Edison Company (Comed) has evaluated each of the proposed Technical Specification changes identified as " Technical Change - Less Restrictive-(Specific)" in accordance with the criteria set forth.in 10 CFR 50.92 and has determined that the proposed changes do not involve a significant hazards consideration. The bases for the determination _that the proposed changes do not involve a significant hazards consideration is an evaluation of these changes against each of the criteria in-10 CFR 50.92. The criteria and the conclusions of the evaluation are presented below. I 1. Does the change involve a significant increase in the probability or j consequences of an accident previously evaluated? f5 'The proposed change revises- the applicability of these Specifications to
.p -
not prevent unit shutdowns and will apply only to entry into MODES 1. 2. g 3 and 4. The change does not result in any hardware changes. The-change will-not allow continuous operation such that a single failure will preclude the associated function from being performed. .It is overly conservative' to preclude a plant shutdown 'or to preclude MODE
-~ changes from either direction into MODES 5 a~nd-6 while operating within
- . an Action with a finite period or prior to performance of a SR.
Therefore the probability.of-occurrence or the consequences of an accident previously evaluated are not.significantly increased'since the
.. limitations imposed by the Actions are unchanged from that previously.
-evaluated.
- 2. Does the change create _the possibility of'a new or different kind of
. ~ accident.from any acc1 dent previously evaluated?
The proposed change does not necessitate a physical alteration of the plant (no new or'different type of equipment will be installed) or changes in parameters governing normal plant operation. Thus, this change will not create the possibility of a new or different kind of accident from any accident previously evaluated. A BYRON /BRAIDWOOD UNITS 1 & 2 -3.0 14a 5/14/98 Revision F V j
N0 SIGNIFICANT HAZARDS EVALUATION ITS SECTION 3.0 - LC0 AND SR APPLICABILITY O l 3. Does this change involve a significant reduction in a margin of safety? hO The increased flexibility to. change Modes or other conditions in the Applicability while relying on the Actions is acceptable based primarily i on an evaluation that identified those specifications which must Q continue to a] ply LCO 3.0.4. and SR 3.0.4 (restriction Notes are included rf to preclude t11s flexibility in conditions that may adversely impact safety if this relaxation were allowed. Therefore, the margin of safety is not significantly impacted. As such, any reduction in the margin of safety will be insignificant and offset by the benefit gained in plant safety due to allowing plant shutdowns. O ] l BYRON /BRAIDWOOD - UNITS 1 & 2 '3.0-14b 5/14/98 Revision F}}