ML20237A041

From kanterella
Jump to navigation Jump to search
Suppl 8 to Improved TS Noting Differences Between Two Units. Proposed Changes Require That Specs & Surveillances Apply to Each Unit Individually,Unless Otherwise Noted,Consistent W/Version of Current TS Prior to Amends 166 & 148
ML20237A041
Person / Time
Site: Mcguire, McGuire  Duke Energy icon.png
Issue date: 08/05/1998
From:
DUKE POWER CO.
To:
Shared Package
ML20237A040 List:
References
NUDOCS 9808130043
Download: ML20237A041 (33)
v • d • e


Text

_ _ - - _ _ _ _ _ _ _ _ _ - _ _ - _ _ _ _ _ _

ESFAS InStrum nt tion 3.3.2 Tr.ble 3.3.2-1 (page 4 of 6)

Engineered Safety Feature Actuation System instrumentation

{

l APPLICABLE MODES OR OTHER l

SPECIFIED REQUIRED SURVEILLANCE ALLOWABLE TRIP i FUNCTION CONDITIONS CHANNELS CONDITIONS REQUIREMENTS VALUE SETPOINT

6. Auxiliary Feedwater (continued).
c. Safety injection Refer to Function 1 (Safety injection) for all initiation functions and requirements.
d. Station Blackout (1) Loss of 1,2,3 3 per bus D SR 3.3.2.7 a 3122 V a3174 voltage SR 3.3.2.9 (Unit 1) . (Urdt 1}

z 3108 V 23157

- (Unit 2) with (Unit 2)

  • 8.5
  • 0.5 sec 45 V with time delay 8.5
  • 0.5 sec time delay

{2) Degraded 1,2,3 3 per bus D SR 3.3.2.7 g 3661 V g 3678.5 V Voltage - SR 3.3.2.9 (Unit 1) (Unit 1) 2 3685.5 V g 3703 V (Unit 2) (Unit 2) with 5 11 sec with5 11 with St and see with Si s 600 sec ands 600 without 61 sec without time delay Si time delay

e. Trip of all Main 1,2(a) 1 per MFW K SR 3.3.2.7 NA NA Feedwater pump SR 3.32.9 Pumps
f. Auxiliary 1,2,3 2 per MDP, N,0 SR 3.3.2.7 2 1 psig a 2 psig Feedwater Pump 4 per TDP SR 3.3.2.8 Suction Transfer SR 3.3.2.9 on Suction Pressure Low
7. Automatic Switchover to Containment Sump
a. Refueling Water 1,2,3 3 P SR 3.32.1 g 175.85 a180 Storage Tank SR 3.3.2.3 inches inches (RWST) Level . SR 3.3.2.8 Low SR 3.3.2.9 Coincident with Refor to Function 1 (Safety injection) for all initiation functions and requirements.

Safetyinjection I

i (continued)

(a) Above the P 11 (Pressurizer Pressure) Interlock.

l . MCGuire Units 1 and 2 3.3.2-13 Amendrnent No.

9908130043 990805 PDR ADOCK 05000369 F PDR a

l

(

LOP DG Start Instrumentation 3.3.5 SURVEILLANCE REQUIREMENTS l SURVEILLANCE FREQUENCY l

SR 3.3.5.1 Perform TADOT. 31 days SR 3.3.5.2 Perform CHANNEL CALIBRATION with Trip 'Setpoint and 18 months Allowable Value as follows:

a. Loss of voltage Allowable Value 2 3122 V (Unit 1) 2 3108 V (Unit 2) with a time delay of 8.5 i 0.5 second.

Loss of voltage Trip Setpoint 23174 (Unit 1) 2 3122 V (Unit 2)

  • 45 V with a time delay of  !

8.5

  • 0.5 second.
b. Degraded voltage Allowable Value 2 3661 V (Unit
1) g 3685.5 V (Unit 2) with a time delay of s 11 seconds with Si and s 600 seconds without St.

Degraded voltage Trip Setpoint 2 3578.5 V (Unit

1) 2 3703 V (Unit 2) with a time de ay of s 11 seconds with Si and s 600 secon< ,s without SI.

1 i

l t

l l

I I

McGuire Units 1 and 2 3.3.5-2 Amendment No. i

RCS P/T Limits 3.4.3 MATERIAL PROPERTY BASIS LIMITING MATERIALS: LOWER SHELL LONGITUDINAL WELDS 3-442A and LOWER SHELL PLATE D5013-2 LIMITING ART AT 16 EFPY

% t,149.5 deg. F

%-t,102.0 deg. F 2500 , , , i i , ,

i i i i i i r , e LEAK TEST LIMIT [ i

[

2250 I

[ I

[ [

I I f f I f f 2000 r I

l I l

_ I I g I I g 1750 UNACCEPTABLE f I OPERATION i i t I I S I I f1500 [ /

g g i i

I

)

f j 1250 [ ACCEPTABLE e I OPERATION g i I

.I 1000 -- /

g - HEATUP RATES TO f Z 60 'F/HR

/

/

B

] 750 j '

a1  ? -

j CRmCAuTY LIMIT

-- 7 BASED ON INSERVICE 500 HYDROSTATIC TEST TEMPERATURE (282 F) l FOR THE SERVICE j

] PERIOD UP TO 16 EFPY I O

O 100 200 300 400 500 Reactor Beltline Region Fluid Temperature (Deg. F) l I

i Figure 3.4.3-1 RCS Heatup Limitations )

(UNIT 1 ONLY) . l (Without margins for Instrumentation Errors)

NRC REG GUIDE 1.99, Rev. 2 l Applicable for the first 16 EFPY l McGuire Units 1 and 2 3.4.3-3 Amendment No.

l ,

_ _ _ _ _ _ _ _ _ _ _ - _ _ _ _ _ _ _ - . _ . _ _ _ _ _ _ _ _ _ _ _ J

RCS P/T Limits 3.4.3 MATERIAL PROPERTY BASIS LIMITING MATERIALS; LOWER SHELL FORGING 04 LIMITING ART AT 16 EFPY

%-t.104 deg. F

%-t.102.0 deg. F l IIIIiiiI f 7-~ TEST LIMIT 1 J 9

2250 [

f 1 J

1 l---l- -.l 2w0 <

l l

,I___{

f f E uw g UNACCEPTABLE l

F .

l F

g OPERATION ----j j a i5w f j___ _}f g i I y / /

}W1250 f

[---[ J i y _

/ ACCEPTABLE l

OPERATION 1000 /

g Ei /

/ ___,

h 750 t'l l

~---4RlTICALITY LIMIT BASED ON lNSERVICE HYDROSTATIC 500 ----TEST TEMPERATURE (236 F)

FOR THE SERVICE PERIOD UP to 16 EFPY 250 .

1 0

0 50 100 150 200 250 300 350 400 450 500 Belftine Region Fluid Temperature (Dog. F)

Figure 3A.3-1 RCS Heatup Limitations (Unit 2 Only)

(Without margins for Instrumentation Errors)

NRC REG GUIDE 1.99, Rev. 2 Applicable for the First 16 EFPY

! McGuire Units 1 and 2 3.4.3-4 Amendment No.

l l

L----------------

RCS P/T Limits 3.4.3 MATERIAL PROPERTY basis l UMITING MATERIALS; LOWER SHELL LONGITuDINALWELDs 3-442A and LOWER SHELL PLATE B5013-2

' LtMITING ART AT 16 EFPY

% t,149.5 deg. F

%-t.102.0 deg. F 2500 i , , , i i i f I I I I I I ,

i I

UNACCEPTABLE 2250 OPERATION A I

I I

2000 ,#

1

$ [

g 1750 /

e E I i

f1500 /

/ ACCEPTABLE f OPERATION

~g 1250 ,

/

i E /

.I 1000 /

COOLDOWN , [

B . RATES ' '

g 750 - e F,/HR, ,

rf -0 'FMR ,.-7f

_20 'FMR - JHf/

500 --40 'FMR Id(([ ~~

/

~60 'FMR

-100 'FMR i/

250 --

0 0 100 200 300 400 500 Reactor Beltline Region Fluid Temperature (Deg. F)

Figure 3.4.3-2 RCS Cooldown Limitations (UNIT 1 ONLY)

Cooldown Rates up to 100 deg. F/HR (Without margins for instrumentation Errors)

NRC REG GUIDE 1.99, Rev. 2 i Applicable for the first 16 EFPY McGuire Units 1 and 2 3.4.3-5 Amendment No.

u_________ . _ _ _ _ _ _ _ _ _ . - _ __ _ _ _ _ _ _ _ _ . - - - - - - - - - - -

-j

RCS P/T Limits -

MATERIAL PROPERTY BAslS '

LIMmNG MATERIALS; LOWER SHELLFORGING 04 LIMITING ART AT 16 EFPY:

%-t.104 deg. F

%-t, 73 deg. F 2500 l~

I 2250 I

I 2000 '

.., J O I 1750- UNACCEPTABLE j g OPERATION f R f

. 1 E 1500 /

3 J d  !

j 1250 /

/

1000 -- COOLDOWN J RATES

  • F/HR g f
r f 750 - ; [yf
j. 0 *FN ' ' -

__/

~20*FAr t

500-- 40 *FAr

~ 60*FAr '

W((

100 *FAr 250 O

O 50 100 150 200 250 300 ~ 350 400 450 500 Reactor Beltline Region Fluid Temperature (DEG. F)

Figure 3.4.3-2 RCS Cooldown Limitations (UNIT 2 ONLY)

Cooldown Rates up to 100 deg F/HR (without Margins for Instrumentation Errors)  ;

NRC REG GUIDE 1.99, Rev. 2 '

- Applicable for the First 16 EFPY McGuire Units 1 and 2 3.4.3-8 Amendment No.

- s. .

' LI - :--

D: sign Featuras L 4.0 4.0- DESIGN FEATURES 4.1 Site Location l The McGuire Nuclear Station site is located at latitude 35 degrees,25 minutes,59 L seconds north and longitude 80 degrees,56 minutes,55 seconds west. The Universal F-Transverse Mercator Grid Coordinates are E 504,669,256, and N 3,920,870,471. The site is in northwestern Mecklenburg County, North Carolina,17 miles north-northwest of

- - Charlotte, North Carolina.

l 4.2 Reactor Core

'4.2.1 Fuel Assemblies The reactor shall contain 193 fuel assemblies. Each assembly shall consist of a matrix of Zircalloy fuel rods with an initial composition of natural or slightly enriched uranium dioxide (UO2 ) as fuel material. Limited substitutions of zirconium alloy or stainless steel filler rods for fuel rods, in accordance with

' approved applications of fuel rod configurations, may be used. Fuel assemblies shall be limited to those fuel designs that have been analyzed with applicable NRC staff approved codes and methods and shown by tests or analyses to

' comply with all fuel safety design bases. A limited number of lead test assemblies that have not completed representative testing may be placed in nonlimiting core regions.

4.2.2 Control Rod Assemblies The reactor core shall contain 53 control rod assemblies. The control material shall be silver indium cadmium (Unit 1) silver indium cadmium and boron carbide (Unit 2) as approved by the NRC.

4.3' Fuel Storage 4.3.1. Criticality 4.3.1.1 The spent fuel storage racks are designed and shall be maintained with;

a. Fuel assemblies having a maximum nominal U-235 enrichment of 4.75 weight percent;

, b. IQ s 0.95 if fully flooded with unborated water, which includes l-an allowance for uncertainties as described in Section 9.1 of the UFSAR; L (continued)

McGuire Un'its 1 and 2 4.0-1 Amendment No.

Progrtms end Minuils 5.5 5.5 Programs and Manuals 5.5.11 Ventilation Filter Testina Proaram (VFTP) (continued)

ESF Ventilation System Penetration Flowrate Annulus Ventilation <1% 8000 cfm Control Area Ventilation < 0.05% 2000 cfm Aux. Bldg. Filtered Exhaust (2 fans)(Unit 1) <1% 45,700 cfm Aux. Bldg. Filtered Exhaust (2 fans)(Unit 2) <1% 40,50 cfm Containment Purge (non-ESF) (2 fans) <1% 21,0C0 cfm Fuel Bldg. Ventilation (non-ESF) <1% 35,000 cfm

b. Demonstrate for each of the ESF systems that an inplace test of the charcoal adsorber shows the following penetration and system bypass when tested in accordance with Regulatory Guide 1.52, Revision 2, and ANSI N510-1975 (N510-1980 for Auxiliary Building Filtered Exhaust) at the flowrate specified below
  • 10%.

ESF Ventilation System Penetration Flowrate Annulus Ventilation <1% 8000 cfm Control Area Ventilation < 0.05% 2000 cfm Aux Bldg. Filtered Exhaust (2 fans)(Unit 1) <1% 45,700 cfm Aux. Bldg. Filtered Exhaust (2 fans)(Unit 2) <1% 40,500 cfm Containment Purge (non-EOF) (2 fans) <1% 21,000 cfm Fuel Bldg. Ventilation (non-ESF) <1% 35,000 cfm

c. Demonstrate for each of the ESF systems that a laboratory test of a sample of the charcoal adsorber, when obtained as described in Regulatory Guide 1.52, Revision 2, shows the methyl lodide penetration less than the value specified below when tested in accordance with ASTM D3803-1979 (ASTM D3803-1989 for Annulus and Control Area Systems) at the temperature and relative humidity (RH) specified below.

ESF Ventilation System Penetration RH Temp.

Annulus Ventilation <4% 2 95 % 5 30 C Control Area Ventilation < 0.95% 2 95 % $ 30*C Aux. Bldg. Filtered Exhaust < 10% 2 95 % 5 30*C Containment Purge (non-ESF) <1% 2 95% < 80*C Fuel Bldg. Ventilation (non-ESF) <1% 2 95 % s 80*C

d. Demonstrate for each of the ESF systems that the pressure drop across ,

the combined HEPA filters, the prefilters, and the charcoal adsorbers is less than the value specified below when tested in accordance with Regulatory Guide 1.52, Revision 2, and ANSI N510-1975 at the flowrate specified below 10%.

(continued)

McGuire Units 1 and 2 5.5-14 Amendment No.

I ----------- - - . _ _ -_- -- _ -- -- . - - - - - - - . - . - - - - - - - - - -

Programs cnd M nuels '

5.5 i

5.5 Programs and Manuals i 5.5.11 Ventilation Filter Testina Proaram (VFTP) (continued)

ESF Ventilation System Delta P Flowrate Annulus Ventilation 6.0 in wg 8000cfm l Control Area Ventilation . .

5.0 in wg 2000 cfm -

l Aux. Bldg. Filtered Exhaust (2 fans)(Unit 1) 6.0 in wg 45,700 cfm

! Aux. Bldg. Filtered Exhaust (2 fans)(Unit 2) 6.0 in wg 40,500 cfm Containment Purge (non-ESF) (2 fans) 6.0 in wg ' 21,000 cfm Fuel Bldg. Ventilation (non-ESF) 6.0 in wg 35,000 cfm j

! e. Demonstrate that the heaters for each of the ESF systems dissipate the 1 value specified below when tested in accordance with ANSI N510-1975.

l ESF Ventilation System Wattage @ 600 VAC Annulus Ventilation 43.0 6.4kW

' Control Area Ventilation 10.0 1.0 kW .

The provisions of SR 3.0.2 and SR 3.0.3 are applicable to the VFTP test frequencies.

5.5.12 Explosive Gas and Storaae Tank Radioactivity Monitorina Prooram l This program provides controls for potentially explosive gas mixtures contained in the Waste Gas Holdup System, the quantity of radioactivity contained in gas storage tanks or fed into the offgas treatment system, and the quantity of radioactivity contained in unprotected outdoor liquid storage tanks. The gaseous radioactivity quantities shall be determined following the methodology in Branch Technical Position (BTP) ETSB 11 5, " Postulated Radioactive Release due to Waste Gas System Leak or Failure". The liquid radwaste quantities shall be determined in accordance with Standard Review Plan, Section 15.7.3,

" Postulated Radioactive Release due to Tank Failures".

The program shallinclude:

a. The limits for concentrations of hydrogen and oxygen in the Waste Gas Holdup System and a surveillance program to ensure the limits are maintained. Such limits shall be appropriate to the system's design criteria (i.e., whether or not the system is designed to withstand a hydrogen explosion);

(continued)

McGuire Units 1 and 2 5.5-15 Amendment No.

ENCLOSURE 2

~

MCGUIRE NUCLEAR STATION CHANGES TO ITS SECTION 3.0 t

- -_-- --- a

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be retumed to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the required testing to demonstrate OPERABILITY.

LCO 3.0.6 When a supported system LCO is not met solely due to a support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.15, " Safety Function Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

When a support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

LCO 3.0.7 Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCo ls 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 LCO 3.0.8 LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

9

a. Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units j simultaneously; l l
b. Whenever the LCO applies to only one unit, this will be !dentified in the Applicability section of the Specification; and (continued) j McGuire Units 1 and 2 3.0-2 Amendment No.

l l

l L __ _____- _ _ _ _ _ _ - _ _ _ _ _

LCO Applicability l 3.0 l 3.0 LCO APPLICABILITY (continued)

c. Whenever certain portions of a Specification contain operating parameters, setpoints etc., which are different for each unit, this will be identified in parentheses or footnotes. (For example, "... flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)...").

l-McGuire Units 1 and 2 3.0-3 Amendment No.

I'

- --__________-_-_A

(f' j i

SR Applicability 3.0 l

i i 3.0 SR APPLICABILITY (continued) l 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 I into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS.

SR 3.0.5 Surveillance Requirements shall apply to each unit individually unless otherwise indicated as stated in LCO 3.0.8 for individual Specifications or whenever certain portions of a Specification contain surveillance parameters different for each unit, which will be identified in parentheses or footnotes.

McGuire Units 1 and 2 3.0-5 Amendment No.

l t

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ - - _ _ - _ _ _ _ - _ . - - - - - - - - - _ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -- -- - - - - - - - - - - - - ~~

1 LC0 Applicability B 3.0 i

l ~l

8 3.0 -LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY

. BASES.

t LCOs 'LCD 3.0.1-through LC0 3.0.8 establish the general l requirements applicable to all Specifications and apply at all times, _unless otherwise stated.

~ LC0z 3.0.1 LC0 3.0.1' establishes the Applicability statement within each individual Specification at the requirement for when the LC0 is required to be met (i.e., when'the unit is in the-

, MODES or other specified conditions of the Applicability L statement of each Specification).

LC0; 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 L Condition is applicable from the point _in time that an-

, ACTIONS Condition is entered. The Required Actions l establish those remedial measures ~ that_must be taken within

specified Completion Times when the requirements of an LCO

!. are not_ met. This Specification establishes that:

V

l. a. Completion of the Required Actions within the
specified Completion Times constitutes compliance with L a Specificati_on; 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 al time limit in which the LC0 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 Ltype 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. (Whetherstatedas.a Required Action.or not, correction'of the entered Condition is:an action that may always be considered upon entering (continued)

LMcGuire Units 1 and ? 8 3.0-1 Supplement 8 1

LCO Applicability B 3.0 I

BASES LC0 3.0.7 allow specified Technical Specification (TS) requirements to (continued) be changed to permit performances of these. special tests and operations, which otherwise could not be perforned if required to comply with the requirements of these TS.

Unless otherwise specified, all tiie other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.

The Applicability of a Test Exception LC0 represents a condition not necessarily in compliance with the nornal requirements of the TS. Compliance with Test Exception LCOs is optional. A special operation may be perforned either under the provisions of the appropriate Test Exception LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Test Exception LCO, the requirements of the Test Exception LC0 shall be followed. I LC0 3.0.8 LC0 3.0.8 delineates the applicability of each specification to Unit 1 and Unit 2 operations.

i l

4 i

l McGuire Units 1 and 2 B 3.0-9 Supplement 8

SR Applicability B 3.0

' i B 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY BASES l SRs SR 3.0.1 through SR 3.0.5 establish the general requirements applicable to all Specifications and apply at all times, i 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 LC0 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 te be OPERABLE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that I systems or conponents are OPERABLE when:

a. The systems or components are known to be inoperable, although still meeting the SRs; or
b. The requirements of the Surveillance (s) are known not to be met between required Surveillance performances.

Surveillance do not have to be performed when the unit is L in a MODE or other specified condition for which the requirements of the associated LC0 are not applicable, unless otherwise specified. The SRs associated with a test exception are only applicable when the test exception is used as an allowable exception to the requirements of a Specification.

Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this

l. case, the unplanned event may be credited as fulfilling' the l performance of the SR. This allowance includes those SRs whose _ performance is normally precluded in a given MODE or l other specified condition.

I Surveillance, including Surve111ances invoked by Required Actions, do not have to be performed on inoperable equipment

=

(continued)

McGuire Units') and 2 B 3.0-10 Supplement 8 h

SR Applicability B 3.0 BASES SR 3.0.4 the Surveillance may be stated in the form of a Note as not (continued) required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.

SR 3.0.5 SR 3.0.5 delineates the applicability of the surveillance activities to Unit 1 and Unit 2 operations.

McGuire Units 1 and 2 8 3.0-15 Supplement 8

. - _ _ - _ = .

Specification 3.0 INSERT 5 (continued)

LCO 3.0.7 Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performan< of special tests and operations. Unless g'q otherwise specified, all other TS requirements remain l unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the l Applicability shall be made in accordance with the other l applicable Specifications.

LCO 3.0.8 LCOs including the associated ACTIONS shall apply to each unit individually unless othenvise indicated as follows:

p,g a. Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS willapply to both units simultaneously;

b. Whenever the LCO applies to only one unit, this will be identifiedin the Applicability sect!on of the Specification; and i c. Whenever certain portions of a Specification contain operating parameters, sctpoints etc., which are different for each unit, this willbe identifiedin parentheses or footnotes.

(For example, "... flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)...').

l-e I

McGuire . / Pt 4df

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

INSERT 9 A.lb l 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 Applicability that are required to comply with ACTIONS.

INSERT 10 glz SR 3.0.5 Surveillance Requirements shall apply to each unit individually unless otherwise indicated as statedin LCO 3.0.8 forindividual i Specifications or whenever certain portions of a Specification )

contain surveillance parameters different for each unit, which will be identified in parentheses or footnotes.

l L

McGuire /

Specification 3.0 INSERT 5 (continued)

LCO 3.0.7 Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performance of special tests and operations. Unless gq otherwise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, tho ACTIONS of the Test Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

LCO 3.0.8 LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

p,g a. Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units simultaneously;

b. Whenever the LCO applies to only one unit, this will be identifiedin the Applicability section of the Specification; and
c. Whenever certain ponions of a Specification contain operating parameters, setpoints etc., which are different for each unit, this willbe identifiedin parentheses or footnotes.

(For example, "... flow rate of 54.000 cfm (Unit 1) or 43,000 cfm (Unit 2)...').

l l

1 McGuire L NN I

Specification 3.0 INSERT 8 If it is discovered that a Surveillance was not performed within its specified

, Frequency, then compliance with the requirement to declare the LCO not, met l may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whichever is less. This delay period is permitted to l allow performance of the Surveillance.

1 If the Surveillance is not performed within the delay period, the LCO must l 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.

l lNSERT 9 A.it l

Entry into a MODE or other specified condition in the Applicability of an LCO

'shall not be made unicss 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 Applicability that are required to comply with ACTIONS.

INSERT 10 glz SR 3.0.5 Surveillance Requirements shall apply to each unit individually unless otherwise indicated as stated in LCO 3.0.8 for individual Specifications or whenever certain portions of a Specification contain surveillance parameters different for each unit, which will be identified in parentheses or footnotes.

l l

L l

McGuire 2. j 1

1 I

Discussien of Chrngas l SIctirn 3.0 - LC0 cnd SR Applic:bility i

ADMINISTRATIVE CHANGES I A.11 The technical content of CTS 4.0.5 has been moved to ITS Specification 5.5.8, " Inservice Testing Program". Any technical I changes to this requirement are addressed in the Discussion of  !

Changes for Section 5.5. The movement of these requirements within the TS is considered administrative. This change is consistent with NUREG-1431.

A.12 The CTS for each unit is currently contained within separate volumes. The ITS combines both Units 1 and 2 into a single volume, consistent with the CTS prior to Amendments 166 and 148.

ITS LCO 3.0.8 and SR 3.0.5 are added to clearly state that each individual specification and surveillance requirement applies to each unit independently, unless otherwise specifically stated. In those instances, the specification or surveillance denotes limits for each unit individually, or the specification is identified as only being applicable to a particular unit. This is consistent with CTS 3.0.5 and 4.0.6 which existed prior to the above amendments. This change is administrative since it only restates the requirements which already exist when each unit is provided in separate volumes and maintains all of the technical requirements.

l I

e l

I McGuire Units 1 and 2 Page A - 5 Supplement 85/20/97l

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

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 reouired to be entered. This is an exception to LC0 3.0.2 for the supported system. In this event, .

additional evaluations and limitations may be required in accordance with Specification 5.5.15,

  • Safety Function .

Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss

-of safety function exists are required to be entered.

When a support syston's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system. the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

LCO 3.0.7 Test Exception LCOs (3.1.9. 3.1<f0. 3.1.1Z and 3.4.19L(3.1.t and 3 9.1g allow specified Technicai :$ edification ("S) requirements to be changed to permit performance of special tests-;.1d h operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Test Exception LCOs is optional. When a Test Exception LCO is desired to be met but is not met, the ACTIONS of the Test-Exception LCO shall be met. When a Test Exception LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall be made in accordance with the other applicable Specifications.

i (continued) 3.0 3 Rev 1, 04/07/%

m l

I:

INSERT 1 LCO 3.0.8 LCOs including the associated ACTIONS shall apply to each unit individually unless otherwise indicated as follows:

a. Whenever the LCO refers to systems or components which are shared by both units, the ACTIONS will apply to both units simultaneously;
b. Whenever the LCO applies to only one unit, this will be identifiedin the Applicability section of the Specification; and
c. Whenever certain portions of a Specification contain operating parameters, setpoints etc., which are different for each unit, this willbe identified in parentheses or footnotes.

(For example, "... flow rate of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2)...').

l h

l INSERTPqe 3.0-3 l

McGuire l L____-_ _____-__-_-_-______-_-_-:______--_____ . _ _ _ _ _ _ _ _ _ _ - _ _ - - - - - - _ _ _ _ _ - - - _ _ _ - _ - _ _ _ _ . - - _ . _ _ _ _ . _ _ _ _ _ _ -

, Sa Applicability l 3.0 1

3.0 SR APPLICABILITY l SR 3.0.3 declared not met, and the applicable Condition (s) must be (continued) entered.

SR 3.0.4 Entry in'to a MODE or other specified condition in the l

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 Applicability that are required to comply with ACTIONSt t r tigrarepart op g (a snutMwn of/the unip.

^

SR 3.0.4 1 only applicable for en y into a MODE or r specifi condition in the Appli ility in MODES 1 3 and 4.

Rev r's Note: SR 3.0.4 as been revised so at changes i or other specifi conditions in t placability t are part of a sh of the unit sh not be

~

prevented. In additi . SR 3.0.4 has revised so that -

/ it is only applica for entry into a or other '

specified condit in the Applicabil' y in MODES 1, 2. 3.

and 4. The change restrictio in SR 3.0.4 were previously a icable in all M00E'. Before this version f SR 3.0.4.c implemented on plant specific basis, licensee st review the exis ng technical specifica ons to de* ine where specific restrictions on MODE ch s or R Actions should neluded in individual CDs to j ify this change: su an evaluation should , summarized n a matrix of all ex ing LCOs to facilitat W RC staff review of a convers n to the STS. /

tv --

- QNsecTb ,

i p[ 3.0 5 Rev 1. 04/07/95 M dnet l

INSERT 2 SR 3.0.5 Surveillance Requirements shall apply to each unit individually unless otherwise indicated as stated in LCO 3.0.8 for individual Specifications or whenever certain portions of a Specification contain surveillance parameters different for each unit, which will be identified in parentheses or footnotes.

INSERTPage 3.0-5 McGuire l

LCO Applicability B 3.0 8 3.0 LIMITING CONDITION FOR OPE"!!'ON (LCO) APPLICABILITY BASES LCOs LCO 3.0.1 through LCO 3.0. ish the general c5 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 specified conditions of the Applicability statement of each Specification).

LC0 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 specified 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
b. Completion of the Required Actions is not required-when an LC0 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 LC0 must be met. This time limit is the Completion T1ee 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 ccapleted within the specified Completion Time, a shutdown may be required to place the unit in a MO3E 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)

M B 3.0 1 Rev 1, 04/07/95 liicAwvs s

I

LCO Applicability B 3.0 ,

l BASES j LC0 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 LC0 in which the loss of safety function exists are required to be entered.

LCO 3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit.

These special tests and operations are necessary to demonstrate select unit performance characteristics, to ,

ij perform special maintenance activities, and to oerfore j 3U6Od spectatevolutions. Test Exception LCOs 3.1,K 3.1.16;) l C3.I.11Jnd 3.X.19Dallow specified Technica  !

3 .4. Specification (TS) requirements to be cM'ged to permit performances of these special tests and c rations, which )

otherwise could not be performed if requi, red to comply with the requirements of these TS. Unless otherwise specified.

all the other TS requirements remain unchanged. This will j ensure all appropriate requirements of the MODE or other {

specified condition not directly associated with or required I to be changed to perform the special test or operation wil?

remain in effect.

The Applicability of a Test Exception LCO represents a condition not necessarily in compliance with the normal requirements of the TS. Compliance with Test Exception LCOs is optional. A special operstion may be performed either under the provisions of the appropriate Test Exception LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the  !

provisions of the Test Exception LCO, the requirements of the Test Exception LC0 shall be followed.

O@ sed}<

1 B 3.0 9 Rev 1, 04/07/95 m .

l

INSERT LCO 3.0.8 LCO 3.0.8 delineates the applicability of each specification to Unit 1 and Unit 2 operation.

I l

Insett Page B 3.0-9 u.u,, I \

SR Applicability B 3.0 l 1

B 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY BASES SRs SR 3.0.1 through SR 3.0.[ tablish the neral applicable to all Specifications and app y at a1Nuirements imes, 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:

a. The systems or components are known to be inoperable, although still meeting the SRs; or
b. The requirements of the Surveillance (s) are known not to be met between required Surveillance performances.

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 LC0 are not applicable, unless otherwise specified. The SRs associated with a test exception are only applicable when the test exception is O7 used as an allowable exception to the requirements of a Specification.

( MisettT 2 )--- durveillancesincludingSurveillancesinvokedbyRequired 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 retu. ming equipment to OPERABLE sta hs.

(continued)

B 3.0 10 Rev 1. 04/07/95 W [OG m

s I

SR Applicability B 3.0 BASES l 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.

dx .s.u.* is ly applicable entering MODE 4 f

[ MODE 5. 3 from MODE 4 2 from H0DE 3 MODE 1]

from 2. Furthermore. 3.0.4 is applicab when enter t.ny other specif d condition in the licabilit) $

on1 iile operating in S1,2.3.or4./Ihe r uirements of SR 3. do not apply in ' r.S 5 and 6. o i n other specified itions of the App cability (unie s '

. in MODES 1. 2. 3, 4) because the ACT of indivi 1 l:

Specifications fficiently define t remedial meas s to -

J l

be t: sten. -

l msmy I

I I

i l

1 i

B 3.0 15 Rev 1. 04/07/95

/4c.6uwt l

INSERT SR 3.0.5 SR 3.0.5 delineates the applicability of the surveillance activities to Unit 1 and Unit 2 operations.

[-

L i

insert Page B 3.0-15 1

McGuire l

_ - - - - _ _ _ _ _ _ _ _ _ - _ _ _ _ . _ _ _ _

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