Text

Technical Specification Bases Changes and Ufsar/Selected Licensee Commitment Changes
	ML18344A048
Person / Time
Site:	Catawba
Issue date:	12/04/2018
From:	Simril T; Duke Energy Carolinas
To:	; Document Control Desk, Office of Nuclear Reactor Regulation
References
	RA-18-0219
	Download: ML18344A048 (250)
	v • d • e

Tom Simril

~a,DUKE Vice President

~ ENERGY" Catawba Nuclear Station Duke Energy CN01VP 4800 Concord Road York, SC 29745 o: 803.701.4251 f: 803. 701.3221 tom.simril@duke-energy.com RA-18-0219 10CFR 50.4 10CFR 50.71(e)

December 4, 2018 U.S. Nuclear Regulatory Commission Document Control Desk Washington, DC 20555-0001

Subject:

Duke Energy Carolinas, LLC Catawba Nuclear Station, Units 1 and 2 Docket Nos. 50-413 and 50-414 Technical Specification Bases Changes and UFSAR/Selected Licensee Commitment Changes Pursuant to 10CFR 50.4, please find attached changes to the Catawba Nuclear Station Technical Specification Bases. These Bases changes were made according to the provisions of Technical Specification 5.5.14, "Technical Specifications (TS) Bases Control Program."

Also, Pursuant to 10 CFR 50.71(e), please find attached changes to the Catawba Nuclear Station Selected Licensee Commitments Manual. This document constitutes Chapter 16 of the Updated Final Safety Analysis Report (UFSAR).

Any questions regarding this information should be directed to Tolani Owusu, Regulatory Affairs, at (803) 701-5385.

I certify that I am a duly authorized officer of Duke Energy Carolinas, LLC, and that the information contained herein accurately represents changes made to the Technical Specification Bases since the previous submittal.

Sincerely,

~~

Tom Simril Vice President, Catawba Nuclear Station

Enclosures:

1) TS Bases Insertion/Removal Instructions

2) TS LOEP and Bases Replacement Pages

3) SLC Manual Insertion/Removal Instructions

4) SLC Manual Replacement Pages WWW.duke-energy.com

Catawba Nuclear Station Technical Specifications Manual and Selected Licensee Commitment Manual Amendments RA-18-0219 December 4, 2018 Page2 xc: w/enclosures Catherine Haney, Regional Administrator U. S. Nuclear Regulatory Commission, Region II Marquis One Tower 245 Peachtree Center Ave., NE Suite 1200 Atlanta, GA 30303-1257 Mike Mahoney NRC Project Manager (CNS)

U.S. Nuclear Regulatory Commission One White Flint North, Mail Stop 08B1A 11555 Rockville Pike Rockville, MD 20852-2746 Joseph Austin, Senior Resident Inspector Catawba Nuclear Station

Enclosure 1 TS Bases Insertion/Removal Instructions

Removal and insertion instructions for Catawba Nuclear Station Tech Spec Bases Changes for February 1, 2018 thru October 31, 2018.

REMOVE THESE PAGES INSERT THESE PAGES LIST OF EFFECTIVE PAGES Pages 1-18 Revision 16 (1/23/18) Pages 1-18 List of Effective Pages Revisions 17-19 have been Revision 20 (10/23/18) superseded by Revision 20 (10/23/18) and therefore do not need to be replaced in your manuals.

TECHNICAL SPECIFICATIONS BASES TAB 3.0 83.0-1-83.0-21 B 3.0-1 -B 3.0-21 Revision 4 Revision 6 TS Bases B 3.0-1 thru 21, Revision 5 was superseded by Revision 6 and although included in this package, does not need to be placed in your manual.

BASES TAB 3.1 B 3.1.8 B 3.1.8-6 8 3.1.8-1-83.1.8-6 Revision 3 Revision 4 BASES TAB 3.4 83.4.10-1-83.4.10-4 B 3.4.10 8 3.4.10-4 Revision 3 Revision 4 8 3.4.12-1-8 3.4.12-13 8 3.4.12 8 3.4.12-13 Revision 5 Revision 6 BASES TAB 3.5 83.5.2-1-83.5.2-11 8 3.5.2-1-83.5.2-11 Revision 4 Revision 5

BASES TAB 3.6 B 3.6.3 B 3.6.3-14 B 3.6.3 B 3.6.3-14 Revision 6 Revision 7 B 3.6.6 B 3.6.6-8 B 3.6.6-1 -B 3.6.6-8 Revision 7 Revision 8 BASES TAB 3.7 B 3.7.1 B 3.7.1-5 B 3.7.1-1-83.7.1-5 Revision 2 Revision 3 B 3.7.2-1 -*s 3.7.2-5 B 3.7:2-1 -B 3.7.2-5 Revision 3 Revision 4 B 3.7.3 B 3.7.3-6 B 3.7.3-1 -B 3.7.3-6 Revision 2 Revision 3 B 3.7.5-1 -B 3.7.5-9 B 3.7.5 B 3.7.5-9 Revision 4 Revision 5 B 3.7.6 B 3.7.6-3 B 3.7.6 B 3.7.6-3 Revision 5 Revision 6 B 3.7.12 B 3.7.12-7 B 3.7.12 B 3.7.12-7 Revision 7 Revision 8 If you have any questions concerning the contents of this Technical Specification Bases update, please contact Toni Lowery at (803) 701-5046.

Enclosure 2 TS LOEP and Bases Replacement Pages

- Catawba Nuclear Station Technical Specifications Page Number List of Effective Pages Amendments Revision Date 177/169 4/08/99 ii 219/214 3/01/05 iii 215/209 6/21/04 iv 173/165 9/30/98 1.1-1 173/165 9/30/98 1.1-2 268/264 6/25/12 1.1-3 . 299/295 10/23/18 1.1-4 268/264 6/25/12 1.1-5 281/277 4/29/16 1.1-6 268/264 6/25/12 1.1.7 179/171 8/13/99 1.2-1 173/165 9/30/98 1.2-2 173/165 9/30/98 1.2-3 173/165 9/30/98 1.3-1 298/294 2/1/18 1.3-2 298/294 2/1/18 1.3-3 298/294 2/1/18 1.3-4 298/294 2/1/18 1.3-5 298/294 2/1/18 1.3-6 298/294 2/1/18 1.3-7 298/294 2/1/18 1.3-8 298/294 2/1/18 1.3-9 298/294 2/1/18 1.3-10 298/294 2/1/18 1.3-11 298/294 2/1/18 1.3-12 298/294 2/1/18 1.3-13 298/294 2/1/18 1.3-14 298/294 2/1/18 1.4-1 173/165 9/30/98 1.4-2 173/165 9/30/98 Catawba Units 1 and 2 Page 1 10/23/18

1.4-3 173/165 9/30/98 1.4-4 173/165 9/30/98 2.0-1 210/204 12/19/03 3.0-1 288/284 4/26/17 3.0-2 298/294 2/1/18 3.0-3 235/231 3/19/07 3.0-4 288/284 4/26/17 3.0-5 298/294 2/1/18 3.0-6 235/231 3/19/07 3.1.1-1 263/259 3/29/11 3.1.2-1 296/292 10/23/17 3.1.2-2 263/259 3/29/11 3.1.3-1 173/165 9/30/98 3.1.3-2 275/271 04/14/15 3.1.3-3 173/165 9/30/98 3.1.4-1 173/165 9/30/98 3.1.4-2 173/165 9/30/98 3.1.4-3 263/259 3/29/11 3.1.4-4 263/259 3/29/11 3.1.5-1 173/165 9/30/98 3.1.5-2 263/259 3/29/11 3.1.6-1 173/165 9/30/98 3.1.6-2 173/165 9/30/98 3.1.6-3 263/259 3/29/11 3.1.7-1 173/165 9/30/98 3.1.7-2 173/165 9/30/98 3.1.8-1 291/287 7/26/17 3.1.8-2 263/259 3/29/11 3.2.1-1 173/165 9/30/98 3.2.1-2 173/165 9/30/98 3.2.1-3 263/259 3/29/11 3.2.1-4 263/259 3/29/11 3.2.1-5 263/259 3/29/11 3.2.2-1 173/165 9/30/98 Catawba Units 1 and 2 Page2 10/23/18

- 3.2.2-2 3.2.2-3 3.2.2-4 3.2.3-1 173/165 263/259 263/259 263/259 9/30/98 3/29/11 3/29/11 3/29/11 3.2.4-1 173/165 9/30/98 3.2.4-2 173/165 9/30/98 3.2.4-3 173/165 9/30/98 3.2.4-4 263/259 3/29/11 3.3.1-1 173/165 9/30/98 3.3.1-2 247/240 12/30/08 3.3.1-3 247/240 12/30/08 3.3.1-4

207/201 7/29/03 3.3.1-5 247/240 12/30/08 3.3.1-6 247/240 12/30/08 3.3.1-7 247/240 12/30/08 3.3.1-8 173/165 9/30/98 3.3.1-9 263/259 3/29/11 3.3.1-10 263/259 3/29/11 3.3.1-11 263/259 3/29/11 3.3.1-12 278/274 4/08/16 3.3.1-13 263/259 3/29/11 3.3.1-14 263/259 3/29/11 3.3.1-15 263/259 3/29/11 3.3.1-16 278/274 4/08/16 3.3.1-17 263/259 . 3/29/11 3.3.1-18 263/259 3/29/11 3.3.1-19 278/274 4/08/16 3.3.1-20 263/259 3/29/11 3.3.1-21 263/259 3/29/11 3.3.1-22 263/259 3/29/11 3.3.2-1 173/165 9/30/98 3.3.2-2 247/240 12/30/08 3.3.2-3 247/240 12/30/08 3.3.2-4 247/240 12/30/08 Catawba Units 1 and 2 Page3 10/23/18

3.3.2-5 264/260 6/13/11 3.3.2-6 264/260 6/13/11 3.3.2-7 249/243 4/2/09 3.3.2-8 249/243 4/2/09 3.3.2-9 249/243 4/2/09 3.3.2-10 263/259 3/29/11 3.3.2-11 263/259 3/29/11 3.3.2-12 263/259 3/29/11 3.3.2-13 277/273 12/18/15 3.3.2-14 277/273 12/18/15 3.3.2-15 277/273 12/18/15 3.3.2-16 277/273 12/18/15 3.3.2-17 277/273 12/18/15 3.3.2-18 (new) 277/273 12/18/15 3.3.3-1 219/214 3/1/05 3.3.3-2 219/214 3/1/05 3.3.3-3 263/259 3/29/11 3.3.3-4 219/214 3/1/05 3.3.4-1

213/207 4/29/04 3.3.4-2 263/259 3/29/11 3.3.4-3 272/268 2/27/14 3.3.5-1 173/165 9/30/98 3.3.5-2 277/273 12/18/15 3.3.6-1 196/189 3/20/02 3.3.6-2 263/259 3/29/11 3.3.6-3 196/189 3/20/02 3.3.9-1 207/201 7/29/03 3.3.9-2 207/201 7/29/03 3.3.9-3 263/259 3/29/11 3.3.9-4 263/259 3/29/11 3.4.1-1 210/204 12/19/03 3.4.1-2 210/204 12/19/03 3.4.1-3 263/259 3/29/11 3.4.1-4 283/279 6/02/16 Catawba Units 1 and 2 Page4 10/23/18

- 3.4.1-5 (deleted) 3.4.1-6 (deleted) 3.4.2-1 3.4.3-1 184/176 184/176 173/165 173/165 3/01/00 3/01/00 9/30/98 9/30/98 3.4.3-2 263/259 3/29/11 3.4.3-3 281/277 4/29/16 3.4.3-4 212/206 3/4/04 3.4.3-5 281/277 4/29/16 3.4.3-6 212/206 3/4/04 3.4.4-1 263/259 3/29/11 3.4.5-1 207/201 7/29/03 3.4.5-2 207/201 7/29/03 3.4.5-3 263/259 3/29/11 3.4.6-1 212/206 3/4/04 3.4.6-2 263/259 3/29/11 3.4.6-3 282/278 4/26/17 3.4.7-1 212/206 3/4/04 3.4.7-2 263/259 3/29/11 3.4.7-3 282/278 4/26/17 3.4.8-1 207/201 7/29/03 3.4.8-2 282/278 4/26/17 3.4.9-1 173/165 9/30/98 3.4.9-2 263/259 3/29/11 3.4.10-1 294/290 10/23/17 3.4.10-2 299/295 10/23/18 3.4-11-1 213/207 4/29/04 3.4.11-2 173/165 9/30/98 3.4.11-3 263/259 3/29/11 3.4.11-4 263/259 3/29/11 3.4.12-1 212/206 3/4/04 3.4.12-2 213/207 4/29/04 3.4.12-3 212/206 3/4/04 3.4.12-4 212/206 3/4/04 3.4.12-5 263/259 3/29/11 Catawba Units 1 and 2 Page5 10/23/18

- 3.4.12-6 3.4.12-7 3.4.12-8 3.4.13-1 263/259 263/259 263/259 267/263 3/29/11 3/29/11 3/29/11 3/12/12 3.4.13-2 267/263 3/12/12 3.4.14-1 173/165 9/30/98 3.4.14-2 173/165 9/30/98 3.4.14-3 299/295 10/23/18 3.4.14-4 263/259 3/29/11 3.4.15-1 234/230 9/30/06 3.4.15-2 234/230 9/30/06 3.4.15-3 234/230 9/30/06 3.4.15-4 263/259 3/29/11 3.4.16-1 268/264 6/25/12 3.4.16-2 268/264 6/25/12 3.4.16-3(deleted) 268/264 6/25/12 3.4.16-4(deleted) 268/264 6/25/12 3.4.17-1 263/259 3/29/11 3.4.18-1 280/276 4/26/16 3.4.18-2 280/276 4/26/16 3.5.1-1 211/205 12/23/03 3.5.1-2 263/259 3/29/11 3.5.1-3 263/259 3/29/11 3.5.2-1 253/248 10/30/09 3.5.2-2 299/295 10/23/18 3.5.2-3 263/259 3/29/11 3.5.3-1 213/207 4/29/04 3.5.3-2 173/165 9/30/98 3.5.4-1 173/165 9/30/98 3.5.4-2 269/265 7/25/12 3.5.5-1 173/165 9/30/98 3.5.5-2 263/259 3/29/11 3.6.1-1 173/165 9/30/98 3.6.1-2 192/184 7/31/01 Catawba Units 1 and 2 Page 6 10/23/18

3.6.2-1 173/165 9/30/98 3.6.2-2 173/165 9/30/98 3.6.2-3 173/165 9/30/98 3.6.2-4 173/165 9/30/98 3.6.2-5 263/259 3/29/11 3.6.3-1 173/165 9/30/98 3.6.3-2 290/286 7/21/17 3.6.3-3 290/286 7/21/17 3.6.3-4 290/286 7/21/17 3.6.3-5 263/259 3/29/11 3.6.3-6 299/295 10/23/18 3.6.3-7 . .* 192/184 7/31/01 3.6.4-1 263/259 3/29/11 3.6.5-1 173/165 9/30/98 3.6.5-2 263/259 3/29/11 3.6.6-1 282/278 4/26/17 3.6.6-2 299/295 10/23/18 3.6.8-1 213/207 4/29/04 3.6.8-2 263/259 3/29/11 3.6.9-1 253/248 10/30/09 3.6.9-2 263/259 3/29/11 3.6.10-1 173/165 9/30/98 3.6.10-2 289/285 5/08/17 3.6.11-1 263/259 3/29/11 3.6.11-2 263/259 3/29/11 3.6.12-1 263/259 3/29/11 3.6.12-2 263/259 3/29/11 3.6.12-3 263/259 3/29/11 3.6.13-1 256/251 6/28/10 3.6.13-2 263/259 3/29/11 3.6.13-3 263/259 3/29/11 3.6.14-1 173/165 9/30/98 3.6.14-2 263/259 3/29/11 3.6.14-3 270/266 8/6/13 Catawba Units 1 and 2 Page 7 10/23/18

- 3.6.15-1 3.6.15-2 3.6.16-1 3.6.16-2 173/165 263/259 263/259 263/259 9/30/98 3/29/11 3/29/11 3/29/11 3.6.17-1 253/248 10/30/09 3.7.1-1 173/165 9/30/98 3.7.1-2 299/295 10/23/18 3.7.1-3 281/277 4/29/16 3.7.2-1 173/165 9/30/98 3.7.2-2 299/295 10/23/18 3.7.3-1 173/165 9/30/98 3.7.3-2 ,'

299/295 10/23/18 *j 3.7.4-1 294/290 10/23/17 3.7.4-2 263/259 3/29/11 3.7.5-1 295/291 10/23/17 3.7.5-2 173/165 9/30/98 3.7.5-3 299/295 10/23/18 3.7.5-4 263/259 3/29/11 3.7.6-1 294/290 10/23/17 3.7.6-2 263/259 3/29/11 3.7.7-1 253/248 10/30/09 3.7.7-2 263/259 3/29/11 3.7.8-1 271/267 08/09/13 3.7.8-2 271/267 08/09/13 3.7.8-3 271/267 08/09/13 3.7.8-4 271/267 08/09/13 3.7.9-1 263/259 3/29/11 3.7.9-2 263/259 3/29/11 3.7.10-1 250/245 7/30/09 3.7.10-2 260/255 8/9/10 3.7.10-3 289/285 5/08/17 3.7.11-1 198/191 4/23/02 3.7.11-2 263/259 3/29/11 3.7.12-1 253/248 10/30/09 Catawba Units 1 and 2 Page8 10/23/18

- 3.7.12-2 3.7.13-1 3.7.13-2 3.7.14-1 289/285 198/191 289/285 263/259 5/08/17 4/23/02 5/08/17 3/29/11 3.7.15-1 263/259 3/29/11 3.7.16-1 233/229 9/27/06 3.7.16-2 233/229 9/27/06 3.7.16-3 233/229 9/27/06 3.7.17-1 263/259 3/29/11 3.8.1-1 253/248 10/30/09 3.8.1-2 173/165 9/30/98 3.8.1-3. . 253/248 10/30/09 3.8.1-4 173/165 9/30/98 3.8.1-5 263/259 3/29/11 3.8.1-6 263/259 3/29/11 3.8.1-7 263/259 3/29/11 3.8.1-8 263/259 3/29/11 3.8.1-9 292/288 9/08/17 3.8.1-10 263/259 3/29/11 3.8.1-11 263/259 3/29/11 3.8.1-12 292/288 9/08/17 3.8.1-13 292/288 9/08/17 3.8.1-14 292/288 9/08/17 3.8.1-15 263/259 3/29/11 3.8.2-1 173/165 9/30/98 3.8.2-2 207/201 7/29/03 3.8.2-3 173/165 9/30/98 3.8.3-1 175/167 1/15/99 3.8.3-2 263/259 3/29/11 3.8.3-3 263/259 3/29/11 3.8.4-1 173/165 9/30/98 3.8.4-2 263/259 3/29/11 3.8.4-3 292/288 9/08/17 3.8.4-4 292/288 9/08/17 Catawba Units 1 and 2 Page9 10/23/18

- 3.8.4-5 3.8.5-1 3.8.5-2 3.8.6-1 262/258 173/165 207/201 253/248 12/20/10 9/30/98 7/29/03 10/30/09 3.8.6-2 253/248 10/30/09 3.8.6-3 253/248 10/30/09 3.8.6-4 263/259 3/29/11 3.8.6-5 223/218 4/27/05 3.8.7-1 173/165 9/30/98 3.8.7-2 263/259 3/29/11 3.8.8-1 173/165 9/30/98 3.8.8-2.

263/259 3/29/11 3.8.9-1 173/165 9/30/98 3.8.9-2 173/165 9/30/98 3.8.9-3 263/259 3/29/11 3.8.10-1 207/201 7/29/03 3.8.10-2 263/259 3/29/11 3.9.1-1 263/259 3/29/11 3.9.2-1 215/209 6/21/04 3.9.2-2 263/259 3/29/11 3.9.3-1 227/222 9/30/05 3_9_3.:2 263/259 3/29/11 3.9.4-1 207/201 7/29/03 3.9.4-2 297/293 1/4/18 3.9.5-1 293/289 9/29/17 3.9.5-2 297/293 1/4/18 3.9.6-1 263/259 3/29/11 3.9.7-1 263/259 3/29/11 4.0-1 284/280 6/21/16 4.0-2 233/229 9/27/06 5.1-1 273/269 2/12/15 5.2-1 273/269 2/12/15 5.2-2 273/269 2/12/15 5.2-3 Deleted 9/21/09 Catawba Units 1 and 2 Page 10 10/23/18

- 5.3-1 5.4-1 5.5-1 5.5-2 273/269 173/165 286/282 286/282 2/12/15 9/30/98 9/12/16 9/12/16 5.5-3 173/165 9/30/98 5.5-4 173/165 9/30/98 5.5-5 216/210 8/5/04 5.5-6 299/295 10/23/18 5.5-7 280/276 4/26/16 5.5-8 280/276 4/26/16 5.5-9 280/276 4/26/16 5.5-10 *

280/276 4/26/16 5.5-11 280/276 4/26/16 5.5-12 280/276 4/26/16 5.5-13 280/276 4/26/16 5.5-14 280/276 4/26/16 5.5-15 280/276 4/26/16 5.5-16 280/276 4/26/16 5.5-17 280/276 4/26/16 5.5-18 280/276 4/26/16 5.5-19 280/276 4/26/16 5.6-1 222/217 3/31/05 5.6-2 253/248 10/30/09 5.6-3 222/217 3/31/05 5.6-4 284/280 6/21/16 5.6-5 275/271 4/14/15 5.6-6 280/276 4/26/16 5.7-1 273/269 2/12/15 5.7-2 173/165 9/30/98

Catawba Units 1 and 2 Page 11 10/23/18

- ii iii BASES Revision 1 Revision 2 Revision 1 4/08/99 3/01/05 6/21/04 B 2.1.1-1 Revision O 9/30/98 B 2.1.1-2 Revision 1 12/19/03 B 2.1.1-3 Revision 1 12/19/03 B 2.1.2-1 Revision 0 9/30/98 B 2.1.2-2 Revision O 9/30/98 B 2.1.2-3 Revision 0 9/30/98 B 3.0-1 thru B Revision 6 10/23/18 3.0-21 B 3.1.1-1 thru Revision 3 5/05/11 B 3.1.1-6 B 3.1.2-1 thru Revision 3 11/14/17 B 3.1.2-5 B 3.1.3-1 thru Revision 2 4/14/15 B 3.1.3-6 B 3.1.4-1 thru Revision 1 5/05/11 B 3.1.4-9 B 3.1.5-1 thru Revision 2 5/05/11 B 3.1.5-4 B 3.1.6-1 thru Revision 1 5/05/11 B 3.1.6-6 B 3.1.7-1 Revision O 9/30/98 B 3.1.7-2 Revision 2 1/08/04 B 3.1.7-3 Revision 2 1/08/04 B3.1.7-4 Revision 2 1/08/04 83.1.7-5 Revision 2 1/08/04 B 3.1.7-6 Revision 2 1/08/04 B 3.1.8-1 thru Revision 4 3/28/18 B 3.1.8-6 B 3.2.1-1 thru Revision 4 5/05/11 B 3.2.1.-11 Catawba Units 1 and 2 Page 12 10/23/18

- B 3.2.2-1 thru B 3.2.2-10 B 3.2.3-1 thru B 3.2.3-4 Revision 3 Revision 2 5/05/11 5/05/11 B 3.2.4-1 thru Revision 2 5/05/11 B 3.2.4-7 B 3.3.1-1 thru Revision 8 4/08/16 8.3.3.1-55 B 3.3.2-1 thru Revision 12 12/18/15 B 3.3.2-50 B 3.3.3-1 thru Revision 6 4/11/14 8.3.3:3-16 B 3.3.4-1 thru Revision 2 5/05/11 B 3.3.4-5 B 3.3.5-1 thru Revision 3 12/18/15 B 3.3.5-6 B 3.3.6-1 thru Revision 6 08/02/12 B 3.3.6-5 B 3.3.9-1 thru Revision 3 06/02/14 B 3.3.9-5 B 3.4.1-1 thru Revision 3 5/05/11 B 3.4.1-5 B 3.4.2-1 Revision 0 9/30/98 B 3.4.2-2 Revision 0 9/30/98 B 3.4.2-3 Revision 0 9/30/98 B 3.4.3-1 thru Revision 2 5/05/11 B 3.4.3-6 B 3.4.4-1 thru Revision 2 5/05/11 B 3.4.4-3 B 3.4.5-1 thru Revision 3 5/05/11 B 3.4.5-6 B 3.4.6-1 thru Revision 5 4/26/17 B 3.4.6-6 Catawba Units 1 and 2 Page 13 10/23/18

- B 3.4.7-1 thru B 3.4.7-7 B 3.4.8-1 thru B 3.4.8-4 Revision 7 Revision 4 4/26/17 4/26/17 B 3.4.'9-1 thru Revision 3 08/02/12 B 3.4.9-5 B 3.4.10-1 thru Revision 4 10/23/18 B 3.4.10-4 B 3.4.11-1 thru Revision 4 5/05/11 B 3.4.11-7 B 3.4.12-1 thru Revision 6 10/23/18 B 3.4:12-13 B 3.4. 13-1 thru Revision 7 3/15/12 8 3.4.13-7 B 3.4.14-1 thru Revision 3 5/05/11 B 3.4.14-6 B 3.4.15-1 thru B Revision 6 5/05/11 3.4.15-10 8 3.4.16-1 thru Revision 4 10/23/12 8 3.4.16-5 B 3.4.17-1 thru Revision 2 5/05/11 8 3.4.17-3 8 3.4.18-1 thru Revision 2 4/26/16 8 3.4.18-8 B 3.5.1-1 thru Revision 4 4/26/17 B 3.5.1-8 8 3.5.2-1 thru Revision 5 10/23/18 8 3.5.2-11 B 3.5.3-1 thru Revision 2 4/26/17 B 3.5.3-3 B 3.5.4-1 thru Revision 5 4/11/14 8.3.5.4-5 B 3.5.5-1 thru Revision 1 5/05/11 8 3.5.5-4 Catawba Units 1 and 2 Page 14 10/23/18

- B 3.6.1-1 B 3.6.1-2 B 3.6.1-3 B 3.6.1-4 Revision 1 Revision 1 Revision 1 Revision 1 7/31/01 7/31/01 7/31/01 7/31/01 B 3.6.1-5 Revision 1 7/31/01 B 3.6.2-1 thru Revision 2 5/05/11 B 3.6.2-8 B 3.6.3-1 thru Revision 7 10/23/18 B 3.6.3-14 B 3.6.4-1 thru Revision 2 5/05/11 B 3.6.4-4 B 3.6.5-1 thru .Revision 3 07/27/13 B 3.6.5-4 B 3.6.6-1 thru Revision 8 10/23/18 B 3.6.6-8 B 3.6.8-1 thru Revision 3 5/05/11 B 3.6.8-5 B 3.6.9-1 thru Revision 6 5/05/11 B 3.6.9-5 B 3.6.10-1 thru Revision 3 9/05/17 B 3.6.10-6 B 3.6.11-1 thru Revision 5 5/05/11 B 3.6.11-6 B 3.6.12-1 thru Revision 5 5/05/11 83.6.12-11 B 3.6.13-1 thru B Revision 4 5/05/11 3.6.13-9 B 3.6.14-1 thru Revision 2 4/11/14 B 3.6.14-5 B 3.6.15-1 thru Revision 1 5/05/11 B 3.6.15-4 B 3.6.16-1 thru Revision 3 5/05/11 B 3.6.16-4 B 3.6.17-1 Revision 1 3/13/08 Catawba Units 1 and 2 Page 15 10/23/18

B 3.6.17-2 Revision O 9/30/98 B 3.6.17-3 Revision O 9/30/98 B 3.6.17-4 Revision 0 9/30/98 B 3.6.17-5 Revision 1 3/13/08 B 3.7.1-1 thru Revision 3 10/23/18 3.7.1-5 B 3.7.2-1 thru Revision 4 10/23/18 B 3.7.2-5 B 3.7.3-1 Revision 3 10/23/18 B 3.7.3-6 B 3.7.4-1 thru Revision 3 11/14/17 B 3.7.4-4 B 3.7.5-1 thru Revision 5 10/23/18 B 3.7.5-9 B 3.7.6-1 thru Revision 6 9/10/18 B 3.7.6-3 B 3.7.7-1 thru Revision 2 5/05/11 B 3.7.7-5 B 3.7.8-1 thru Revision 5 8/09/13 B 3.7.8-8 B 3.7.9-1 thru Revision 3 5/05/11 B 3.7.9-4 B 3.7.10-1 thru B Revision 11 9/05/17 3.7.10-9 B 3.7.11-1 thru Revision 3 10/24/11 B 3.7.11-4 B 3.7.12-1 thru Revision 8 3/28/18 B 3.7.12-7 B 3.7.13-1 thru Revision 5 9/05/17 B 3.7.13-5 B 3.7.14-1 thru Revision 2 5/05/11 B 3.7.14-3 B 3.7.15-1 thru Revision 2 5/05/11 B 3.7.15-4 Catawba Units 1 and 2 Page 16 10/23/18

B 3.7.16-1 Revision 2 9/27/06 B 3.7.16-2 Revision 2 9/27/06 B 3.7.16-3 Revision 2 9/27/06 B 3.7.16-4 Revision O 9/27/06 B 3.7.17-1 thru Revision 2 5/05/11 B 3.7.17-3 B 3.8.1-1 thru Revision 6 10/30/17 8.3.8.1-30 B 3.8.2-1 Revision 0 9/30/98 B 3.8.2-2 Revision 0 9/30/98 B 3.8.2-3 Revision 0 9/30/98 B 3.8.2:-4 Revision 1 5/10/05 B 3.8.2-5 Revision 2 5/10/05 B 3.8.2-6 Revision 1 5/10/05 B 3.8.3-1 thru Revision 4 5/05/11 B 3.8.3-8 B 3.8.4-1 thru Revision 11 10/30/17 83.8.4.11 B 3.8.5-1 Revision O 9/30/98 B 3.8.5-2 Revision 2 7/29/03 B 3.8.5-3 Revision 1 7/29/03 B 3.8.6-1 thru Revision 4 5/05/11 B 3.8.6-7 B 3.8.7-1 thru Revision 3 5/05/11 B 3.8.7-4 B 3.8.8-1 thru Revision 3 5/05/11 B 3.8.8-4 B 3.8.9-1 thru Revision 2 5/05/11 B 3.8.9-10 B 3.8.10-1 thru Revision 3 5/05/11 B 3.8.10-4 B 3.9.1-1 thru Revision 3 5/05/11 B 3.9.1-4 Catawba Units 1 and 2 Page 17 10/23/18

B 3.9.2-1 thru Revision 6 3/21/17 B 3.9.2-3 B 3.9.3-1 thru Revision 4 5/05/11 B 3.9.3-5

B 3.9.4-1 thru Revision 6 1/23/18 B 3.9.4-6 B 3.9.5-1 thru Revision 6 1/23/18 B 3.9.5-5 B 3.9.6-1 thru Revision 2 5/05/11 B 3.9.6-3 B 3.9.7-1 thru Revision 1 5/05/11 83.9/-3

Catawba Units 1 and 2 Page 18 10/23/18

LCO Applicability B 3.0 B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LCOs LCO 3.0.1 through LCO 3.0.10 establish the general 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).

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, unless otherwise specified.

The Required Actions establish those remedial measures that must be taken within specified Completion Times when the requirements of an LCO are not met. This Specification establishes that:

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

b. Completion of the Required Actions is not required when an LCO is met within the specified Completion Time, unless otherwise specified.

There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable.

(Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.) The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this case, compliance with the Required Actions provides an acceptable level of safety for continued operation.

Catawba Units 1 and 2 B 3.0-1 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.2 (continued)

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 necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTION S specify the Required Actions where this is the case. An example of this is in LCO 3.4.3, "RCS Pressure and Temperature (PIT) Limits."

The Completion Times of the Required Actions are also applicable when a system or component is removed from service intentionally. The reasons for intentionally relying on the ACTIONS include, but are not limited to, performance of Surveillances, preventive maintenance, corrective maintenance, modifications, or investigation of operational problems. Entering ACTIONS for these reasons must be done in a manner that does not compromise safety. Intentional entry into ACTIONS should not be made for operational convenience. Alternatives that would not result in redundant equipment being inoperable should be used instead. Doing so limits the time both subsystems/trains of a safety function are inoperable and limits the time other conditions exist which result in LCO 3.0.3 being entered. Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.

when a change .in MODE or other specified condition is required to comply with Required Actions, the unit may enter a MODE or other specified condition in which another Specification becomes applicable. In this case, the Completion Times of the associated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS Condition(s) are entered.

Catawba Units 1 and 2 B 3.0-2 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.3 LCO 3.0.3 establishes the actions that must be implemented when an LCO is not met and:

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

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

This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. It is not intended to be used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatives that would not result in redundant systems or components being inoperable.

Upon entering LCO 3.0.3, 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months is allowed to prepare for an orderly shutdown before initiating a change in unit operation. This includes time to permit the operator to coordinate the reduction in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The LCO phrase, "Action shall be initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months . .. "

does not mean that an actual change in load must be commenced by the end of the 1-hour period (Reference 1). The action initiated at the end of the 1-hour period may be administrative in nature, such as preparing shutdown procedures. If at the end of 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months , corrective measures which would allow exiting LCO 3.0.3 are not complete, but there is reasonable assurance that they will be completed with enough time remaining to still allow for an orderly unit shutdown, if required, commencing a load decrease may be delayed until that time. The time limits specified to enter lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE. This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, Completion Times.

Catawba Units 1 and 2 B 3.0-3 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.3 (continued)

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

a. The LCO is now met,

b. The LCO is no longer applicable,

c. A Condition exists for which the Required Actions have now been performed, or

d. ACTIONS exist that do not have expired Completion Times. These Completion Times.are applicable from th~ point in time that the ..

Condition is initially entered and not from the time LCO 3.0.3 is exited.

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

In MODES 1, 2, 3, and 4, LCO 3.0.3 provides actions for Conditions not covered in other Specifications. The requirements of LCO 3.0.3 do not apply in MODES 5 and 6 because the unit is already in the most restrictive Condition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability (unless in MODE 1, 2, 3, or 4) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

Catawba Units 1 and 2 B 3.0-4 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.3 (continued)

Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.14, "Spent Fuel Pool (SFP) Water Level."

LCO 3.7.14 has an Applicability of "During movement of irradiated fuel assemblies in the spent fuel pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.14 are not met while in MODE 1, 2, 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 LCO 3.0.3. These exceptions are addressed in the i.ndividual Specification$.

LCO 3.0.4 LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It allows placing the unit in a MODE or other specified condition stated in that Applicability (e.g., the Applicability desired to be entered) when unit conditions are such that the requiremen ts of the LCO would not be met, in accordance with either LCO 3.0.4.a, LCO 3.0.4.b, or LCO 3.0.4.c.

LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entry into the Applicability.

For example, LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequent ly placed in the tripped condition within the Completion Time, which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation, use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entry into the MODE Catawba Units 1 and 2 B 3.0-5 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.4 (continued) include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered.

LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate The risk assessment may use quantitative, qualitative, or blended approaches, and the ris~ assessment will be conducted using the plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and dete,rmination that the proposed MODE change is acceptable. Consideration should also be given to the probability of completing restoration such that the requirements of the LCO would be met prior to the expiration of ACTIONS Completion Times that would require exiting the Applicability.

LCO 3.0.4.b may be used with single, or multiple systems and components unavailable. NU MARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components.

The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The LC03.0. 4.b risk assessments do not have to be documented.

Catawba Units 1 and 2 B 3.0-6 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.4 (continued)

The Technical Specifications allow continued operation with equipment unavailable in MODE 1 for the duration of the Completion Time. Since this is allowable, and since in general the risk impact in that particular MODE bounds the risk of transitioning into and through the applicable MODES or other specified conditions in the Applicability of the LCO, the use of the LCO 3.0.4.b allowance should be generally acceptable, as long as the risk is assessed and managed as stated above. However, there is a small subset of systems and components that have been determined to be more important to risk and use of the LCO 3.0.4.b allowance is prohibited. The LCOs governing these systems and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is not applicable.

LCO 3.0.4.c allows entry into a MODE or other specified condition in the Applicability with the LCO not met based on a Note in the Specification which states LCO 3.0.4.c is applicable. These specific allowances permit entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered do not provide for continued operation for an unlimited period of time and a risk assessment has not been performed. This allowance may apply to all the ACTIONS or to a specific Required Action of a Specification. The risk assessments performed to justify the use of LCO 3.0.4.b usually only consider systems and components. For this reason, LCO 3.0.4.c is typically applied to Specifications which describe values and parameters (e.g., RCS Specific Activity).

The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. lh this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, MODE 3 to MODE 4, and MODE 4 to MODE 5.

Catawba Units 1 and 2 B 3.0-7 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.4 (continued)

Upon entry into a MODE or other specified condition in the Applicability with the LCO not met, LCO 3.0.1 and LCO 3.0.2 require entry into the applicable Conditions and Required Actions until the condition is resolved, until the LCO is met, or until the unit is not within the Applicability of the Technical Specification.

Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for any Surveillances that have not been performed on inoperable equipment. However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliqnce with the affected LCO.

LCO 3.0.5 LCO 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action(s)) to allow the performance of SRs to demonstrate:

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

b. The OPERABILITY of other equipment.

The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance .. LCO 3.0.5 should not be used in lieu of other practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE. LCO 3.0.5 is not intended to be used repeatedly.

An example of demonstrating equipment is OPERABLE with the Required Actions not met is opening a manual valve that was closed to comply with Required Actions to isolate a flowpath with excessive Reactor Coolant System {RCS) Pressure Isolation Valve {PIV) leakage in order to perform testing to demonstrate that RCS PIV leakage is now within limit.

Examples of demonstrating equipment OPERABILITY include instances in which it is necessary to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action, if there is Catawba Units 1 and 2 B 3.0-8 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.5 (continued) no Required Action Note for this purpose. An example of verifying OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples of demonstrating the OPERABILITY of other equipment are taking an inoperable channel or trip system out of the tripped condition 1) to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system, or 2) to permit the logic to function and indicate the appropriate response during the performance of required testing on another channel in the same trip system .

. The administrative co.ntrols in LCO 3.0.5 apply in all cases to systems or components in Chapter 3 of the Technical Specifications, as long as the testing could not be conducted while complying with the Required Actions. This includes the realignment or repositioning of redundant or alternate equipment or trains previously manipulated to comply with ACTIONS, as well as equipment removed from service or declared inoperable to comply with ACTIONS.

LCO 3.0.6 LCO 3.0.6 establishes an exception to LCO 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 LCO be entered solely due to the inoperability of the support system. This exception is justified because the actions that are required to ensure the unit is maintained in a safe condition are specified in the support system LCO's Required Actions. These Required Actions may include entering the supported system's Conditions and Required Actions or may specify other Required Actions.

When a support system is inoperable and there is an LCO specified for it in the TS, the supported system(s) are required to be declared inoperable if determined to be inoperable as a result of the support system inoperability. However, it is not necessary to enter into the supported systems' Conditions and Required Actions unless directed to do so by the support system's Required Actions. The potential confusion and inconsistency of requirements related to the entry into multiple support and supported systems' LCOs' Conditions and Required Actions are eliminated by providing all the actions that are necessary to ensure the unit is maintained in a safe condition in the support system's Required Actions.

Catawba Units 1 and 2 B 3.0-9 Revision No. 5

LCO Applicability B 3.0 BASES LCO 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 Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

Specification 5.5.15, "Safety Function Determination Program (SFDP),"

ensures loss of safety function is detected and appropriate actions are taken. Upon entry into LCO 3.0.6, an evaluation shall be made to determine if loss of safety function exists. Additionally, other limitations, remedial actions, or compensatory actions may be identified as a result of the support system inoperability and corresponding exception to entering supported system Conditions and Required Actions. The SFDP implements the requirements of LCO 3.0.6.

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.

LCO 3.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions. Test Exception LCOs 3.1.8 and 3.4.17 allow specified Technical Specification (TS) requirements to be changed to permit performances of these special tests and operations, which otherwise could not be performed if required to comply with the requirements of these TS. Unless otherwise specified, all the other TS requirements remain unchanged. This will ensure all appropriate requirements of the MODE or other specified condition not directly associated with or required to be changed to perform the special test or operation will remain in effect.

Catawba Units 1 and 2 B 3.0-10 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.7 (continued)

The Applicability of a Test Exception LCO represents a condition not necessarily in compliance with the normal requirements of the TS.

Compliance with Test Exception LCOs is optional. A special operation may be performed either under the provisions of the appropriate Test Exception LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Test Exception LCO, the requirements of the Test Exception LCO shall be followed.

LCO 3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers.are not capable of providing their associated ..

support function(s). This LCO states that the supported system is not

- considered to be inoperable solely due to one or more required snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or repair of one or more required snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.

If the allowed time expires and the required snubber(s) are unable to perform their associated support function(s), the affected supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2.

LCO 3.0.8.a applies when one or more required snubbers are not capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem supported system or to a single train or subsystem supported system. LCO 3.0.8.a allows 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months to restore the required snubber(s) before declaring the supported system inoperable. The 72 hour8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months Completion Time is reasonable based 6n the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the required snubber(s) are not capable of performing their associated support function and due to the availability of the redundant train of the supported system.

LCO 3.0.8.b applies when one or more required snubbers are not capable of providing their associated support function(s) to more than one train or subsystem of a multiple train or subsystem supported system. LCO 3.0.8.b allows 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months to restore the required snubber(s)

Catawba Units 1 and 2 B 3.0-11 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.8 (continued) before declaring the supported system inoperable. The 12 hour1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the required snubber(s) are not capable of performing their associated support function.

LCO 3.0.8 requires that risk be assessed and managed. Industry and NRC guidance* on the implementation of 10 CFR 50.65(a)(4) (the Maintenance Rule) does not address seismic risk. However, use of LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or

. subsystem is properly controlled, and emergent issues are properly.*

addressed. The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more required snubbers are not able to perform their associated support function.

LCO 3.0.9 LCO 3.0.9 delineates the applicability of each specification to Unit 1 and Unit 2 operations.

LCO 3.0.10 LCO 3.0.10 establishes conditions under which systems. described in the Technical Specifications are considered to remain OPERABLE when required barriers are not capable of providing their related support function(s).

As stated in NEI 04-08, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY (TSTF-427)

Industry Implementation Guidance," March 2006, if the inability of a barrier to perform its support function does not render a supported system governed by the Technical Specifications inoperable (see NRC Regulatory Issues Summary 2001-09, Control of Hazard Barriers, dated April 2, 2001 ), the provisions of LCO 3.0.1 O are not necessary, as the supported system is Operable.

Barriers are doors, walls, floor plugs, curbs, hatches, installed structures or components, or other devices, not explicitly described in Technical Specifications, that support the performance of the safety function of systems described in the Technical Specifications. This LCO states that the supported system is not considered to be inoperable solely due to required barriers not capable of performing their related support function(s) under the described conditions. LCO 3.0.10 allows 30 days before declaring the supported system(s) inoperable and the LCO(s)

Catawba Units 1 and 2 B 3.0-12 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.10 (continued) associated with the supported system(s) not met. A maximum time is placed on each use of this allowance to ensure that as required barriers are found or are otherwise made unavailable, they are restored.

However, the allowable duration may be less than the specified maximum time based on the risk assessment.

If the allowed time expires and the barriers are unable to perform their related support function(s), the supported system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2.

This provision does not apply to barriers which support ventilation systems or to fire barriers. The Technical Specifications for ventilation systems provide specific Conditions for inoperable barriers. Fire barriers are addressed by other regulatory requirements and associated plant programs. This provision does not apply to barriers which are not required to support system OPERABILITY (see NRC Regulatory Issue Summary 2001-09, "Control of Hazard Barriers," dated April 2, 2001).

The provisions of LCO 3.0.10 are justified because of the low risk associated with required barriers not being capable of performing their related support function. This provision is based on consideration of the following initiating event categories:

Loss of coolant accidents;

High energy line breaks;

Feedwater line breaks;

Internal flooding;

External flooding;

Turbine missile ejection; and

Tornado or high wind.

The risk impact of the barriers which cannot perform their related support function(s) must be addressed pursuant to the risk assessment and management provision of the Maintenance Rule, 10 CFR 50.65 (a)(4),

and the associated implementation guidance, Regulatory Guide 1.160, "Monitoring the Effectiveness of Maintenance at Nuclear Power Plants."

Regulatory Guide 1.160 endorses the guidance in Section 11 of NUMARC 93-01, Revision 4A, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." This guidance provides for the consideration of dynamic plant configuration issues, emergent conditions, and other aspects pertinent to plant operation with the barriers unable to perform their related support function(s). These considerations may result in risk management and other compensatory actions being required during the period that barriers are unable to perform their related support function(s).

Catawba Units 1 and 2 B 3.0-13 Revision No. 5

LCO Applicability B 3.0 BASES LCO 3.0.10 (continued)

LCO 3.0.10 may be applied to one or more trains or subsystems of a system supported by barriers that cannot provide their related support function(s), provided that risk is assessed and managed (including consideration of the effects on Large Early Release and from external events). If applied concurrently to more than one train or subsystem of a multiple train or subsystem supported system, the barriers supporting each of these trains or subsystems must provide their related support function(s) for different categories of initiating events. For example, LCO 3.0.10 may be applied for up to 30 days for more than one train of a multiple train supported system if the affected barrier for one train protects against internal flooding and the affected barrier for the other train protects against tornado missiles. In this example, the affected barrier may be the same physical barrier but serve different protection functions for each train. If during the time that LCO 3.0.10 is being used, the required OPERABLE train or subsystem becomes inoperable, it must be restored to OPERABLE status within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months .

Otherwise, the train(s) or subsystem(s) supported by barriers that cannot perform their related support function(s) must be declared inoperable and the associated LCOs declared not met. This 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months period provides time to respond to emergent conditions that would otherwise likely lead to entry into LCO 3.0.3 and a rapid plant shutdown, which is not justified given the low probability of an initiating event which would require the barrier(s) not capable of performing their related support function(s). During this 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months period, the plant risk associated with the existing conditions is assessed and managed in accordance with 10 CFR 50.65(a)(4).

Gatawba Units 1 and 2 B 3.0-14 Revision No. 5

LCO Applicability B 3.0 BASES REFEREN CES 1. Letter from Christoph er I. Grimes, Chief, Technical Specifications Branch, Division of Operating Reactor Support, to Frederick J.

Hebdon, Director, Project Directorate 11-4, Division of Reactor Projects 1/11, "Use of Shutdown Times for Corrective Maintena nce (TIA 92-08)," Decembe r 11, 1992.

Catawba Units 1 and 2 B 3.0-15 Revision No. 5

SR Applicability B 3.0 B 3.0 SURVEIL LANCE REQUIRE MENT (SR) APPLICA BILITY BASES SRs SR 3.0.1 through SR 3.0.5 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated.

SR 3.0.1 SR 3.0.1 establishe s the requireme nt 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 Surveillan ces are performed to verify the OPERAB ILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequenc y, in accordance with SR 3.0.2, constitutes a failure to meet an LCO.

Systems and compone nts are assumed to be OPERAB LE when the associated SRs have been met. Nothing in this Specification, however, is to be construed as implying that systems or compone nts are OPERAB LE when:

a. The systems or compone nts are known to be inoperable, although still meeting the SRs; or

b. The requireme nts of the Surveillance(s) are known not to be met between required Surveillance performances.

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

Unplanned events may satisfy the requirements (including applicable acceptance criteria) for a given SR. In this case, the unplanne d event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performan ce is normally precluded in a given MODE or other specified condition.

Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipmen t because the ACTIONS define the remedial measures that apply. Surveillan ces have to be met and performed in accordan ce with SR 3.0.2, prior to returning equipment to OPERAB LE status.

Catawba Units 1 and 2 B 3.0-16 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.1 (continued)

Upon completion of maintenance, appropriate post maintenance testing is required to declare equipment OPERABLE. This includes ensuring applicable Surveillances are not failed and their most recent performance is in accordance with SR 3.0.2. Post maintenance testing may not be possible in the current MODE or other specified conditions in the Applicability due to the necessary unit parameters not having been established. In these situations, the equipment may be considered OPERABLE provided testing has been satisfactorily completed to the extent possible and the equipment is not otherwise believed to be incapable of performing its function. This will allow operation to proceed to a MODE or other specified condition where other necessary post maintenance tests can be completed.

SR 3.0.2 SR 3.0.2 establishes the requirements for meeting the specified Frequency for Surveillances and any Required Action with a Completion Time that requires the periodic performance of the Required Action on a "once per ... " interval.

SR 3.0.2 permits a 25% extension of the interval specified in the Frequency. This extension facilitates Surveillance scheduling and considers plant operating conditions that may not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).

The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs. The exceptions to SR 3.0.2 are those Surveillances for which the 25% extension of the interval specified in the Frequency does not apply.

These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. An example of where SR 3.0.2 does not apply is in the Containment Leakage Rate Testing Program. This program establishes testing requirements and Frequencies in accordance with the requirements of regulations. The TS cannot in and of themselves extend a test interval specified in the regulations.

Catawba Units 1 and 2 B3.0-17 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.2 (continued)

As stated in SR 3.0.2, the 25% extension also does not apply to the initial portion of a periodic Completion Time that requires performan ce on a "once per ... " basis. The 25% extension applies to each performan ce after the initial performance. The initial performance of the Required Action, whether it is a particular Surveillance or some other remedial action, is considered a single action with a single Completion Time. One reason for not allowing the 25% extension to this Completion Time is that such an action usually verifies that no loss of function has occurred by checking the status of redundan t or diverse components or the action accomplishes the function of the inoperable equipmen t in an alternative manner.

The provisions of SR 3.0.2 are not intended to be used repeatedly to extend Surveillance intervals (other than those consistent with refueling intervals) or periodic Completion Time intervals beyond those specified.

SR 3.0.3 SR 3.0.3 establishes the flexibility to defer declaring affected equipmen t inoperable or an affected variable outside the specified limits when a Surveillance has not been performed within the specified Frequency. A delay period of up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whicheve r is greater, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequenc y was not met.

This delay period provides adequate time to perform Surveillances that have been missed. This delay period permits the performan ce of a Surveillance before complying with Required Actions or other remedial measures that might preclude performance of the Surveillance.

The basis for this delay period includes consideration of unit conditions, adequate planning, availability of personnel, the time required to perform the Surveillance, the safety significance of the delay in completing the required Surveillance, and the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the requirements.

Catawba Units 1 and 2 B 3.0-18 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.3 (continued)

When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions, operating situations, or requirements of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance. However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.

SR 3.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes imposed.by Required Actions. .

SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits, and it is expected that the Surveillance will be met when performed. Many factors should be considered, such as the period of time since the Surveillance was last performed, or whether the Surveillance, or a portion thereof, has ever been performed, and any other indications, tests, or activities that might support the expectation that the Surveillance will be met when performed. An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR, but previous successful performances of the SR included the relay contact; the adjacent, physically connected relay contacts were tested during the SR performance; the subject relay contact has been tested by another SR; or historical operation of the subject relay contact has been successful. It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment. The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance. If the Surveillance has been performed recently, a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.

For Surveillances that have not been performed for a long period or that have never been performed, a rigorous evaluation based on objective evidence should provide a high degree of confidence that the equipment is OPERABLE. The evaluation should be documented in sufficient detail to allow a knowledgeable individual to understand the basis for the determination.

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 repeatedly to extend Surveillance intervals. While up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable Catawba Units 1 and 2 B 3.0-19 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.3 (continued) opportunity. The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance. This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant .shutdown. The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component. Missed Surveillances for important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program.

If a Surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the variable is considered outside the specified limits and the Completion Times of the Required Actions for the applicable LCO Conditions begin immediately upon expiration of the delay period. If a Surveillance is failed within the delay period, then the equipment is inoperable, or the variable is outside the specified limits and the Completion Times of the Required Actions for the applicable LCO Conditions begin immediately upon the failure of the Surveillance.

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

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

This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to Catawba Units 1 and 2 B 3.0-20 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.4 (continued)

OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

A provision is included to allow entry into a MODE or other specified condition in the Applicability when an LCO is not met due to a Surveillance not being met in accordance with LCO 3.0.4.

I However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change.

When a system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be performed, per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance has not been performed within the specified Frequency, provided the requirement to declare the LCO not met has been delayed in accordance with SR 3.0.3.

The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of SR 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is defined as a change in MODE or other specified condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, MODE 3 to MODE 4, and MODE 4 to MODE 5.

The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Catawba Units 1 and 2 B 3.0-21 Revision No. 5

SR Applicability B 3.0 BASES SR 3.0.4 (continued)

Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be perform ed until after entering the LCO's Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note, as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.

SR 3.0.5 SR 3.0.5 delineates the applicability of the surveillance activities to Unit 1

and Unit 2 operations.

Catawba Units 1 and 2 B 3.0-22 Revision No. 5