Text

Tech Spec and Tech Spec Bases TS-LOEP & TSB-LOES
	ML17248A469
Person / Time
Site:	McGuire, Mcguire
Issue date:	08/29/2017
From:	; Duke Energy Carolinas
To:	; Document Control Desk, Office of Nuclear Reactor Regulation
References
	Download: ML17248A469 (40)
	v • d • e

I.

Distribution:

1.

2.

Boyer, Robert P Gardner, Troy R Duke Energy DOCUMENT TRANSMITTAL FORM Date: 8l29l2017

Purpose:

Issue Released By:

Document Transmittal #: TR-NUC-MC-006948

3. Howell, Pamela T Facility: MCGUIRE NUCLEAR STATION Duke Energi ..

4. Mc Ginnis, Vickie L SUBJECT 13225 Hagers Ferrx Road

5. OPS HUMAN PERFORMANCE -

Tech Sgec and Tech Sgec Bases TS-LOEP & TSB-LOES Document Management

6. OPS TRNG MGR.

7. QATS- MG02DM

8. RESIDENT NRC INSPECT Huntersville, NC 28078

9. SERV _BLDG FILE ROOM - MNSDCRM@duke-energi.com

10. U S NUC REG WASHINGTON, DC 0

11. USNRC

12. WESTINGHOUSE ELECTRIC CO LLC Page 1of1 Document ID 1 2 3 4 5 6 7 8 9 10 11 12 LICN - MC - MNS-TS LOEP - 009 - ISSUED - FYIIE FYIIE FYIIE FYIIE FYIIE R&AIE FYIIE PRINTILP FYIIE R&AIE R&AIE R&AIE LICN - MC - MNS-TS-3.0 - 001 - ISSUED FYIIE FYIIE FYIIE FYIIE FYIIE R&AIE FYIIE PRINTILP FYIIE R&AIE R&AIE R&AIE LICN - MC - MNS-TSB-B 3.0 - 001 - ISSUED FYIIE FYIIE FYIIE FYIIE FYIIE R&AIE FYIIE PRINTILP FYIIE R&AIE R&AIE R&AIE LICN - MC - MNS-TSB-LOES - 014 - ISSUED FYIIE FYIIE FYIIE FYIIE FYIIE R&AIE FYIIE PRINTILP FYIIE R&AIE R&AIE R&AIE Remarks:

McGuire Nuclear Station Technical Specifications LOEP Page Number Amendment Revision Date I*

243/224 7126107 ii 237/219 3/1/07 iii 184/166 9/30/98 iv 184/166 9/30/98 1.1-1 184/166 9/30/98 1.1-2 266/246 6/25/12 1.1-3 237/219 3/1/07 1.1-4 194/175 9/18/00 1.1-5 269/249 5/16/13 1.1-6 261/241 3/29/11

1. 1-7 194/175 9/18/00 1.2-1 184/166 9/30/98 1.2-2 . 184/166 9/30/98 1.2-3 184/166 9/30/98 1.3-1 184/166 9/30/98 1.3-2 184/166 9/30/98 1.3-3 184/166 9/30/98 1.3-4 184/166 9/30/98 1.3-5 184/166 9/30/98 1.3-6 184/166 9/30/98 1.3-7 184/166 9/30/98 1.3-8 184/166 9/30/98 1.3-9 184/166 9/30/98 1.3-10 184/166 9/30/98 1.3-11 184/166 9/30/98 1.3-12 184/166 9/30/98 1.3-13 184/166 9/30/98 1.4-1 184/166 9/30/98 1.4-2 184/166 9/30/98

1.4,;3 184/166 9/30/98 1.4-4 184/166 9/30/98 2.0-1 219/201 1/14/04 McGuire Units 1 and 2 Page 1 Revision 112

Page Number Amendment Revision Date 3.0-1 3.0-2 3.0-3 3.0-4 295/274 221/203 238/220 295/274 8/23/17 4/29/04 3/29/07 8/23/17 3.0-5 295/274 8/23/17 3.0-6 295/274 8/23/17 3.1.1-1 261/241 . 3/29/11 3.1.2-1 184/166 9/30/98 3.1.2-2 261/241 3/29/11 3.1.3-1 184/166 9/30/98 3.1.3-2 184/166 9/30/98 3.1.3-3 184/166 9/30/98 3.1.4-1 184/166 9/30/98 3.1.4-2 184/166 9/30/98 3.1.4-3 261/241 3/29/11 3.1.4-4 261/241 3/29/11 3.1.5-1 3.1.5-2 3.1.6-1 3.1.6-2 184/166 261/241 184/166 184/166 9/30/98 3/29/11 9/30/98 9/30/98 3.1.6-3* 261/241 3/29/11 3.1.7-1 184/166 9/30/98 3.1.7-2 184/166 9/30/98 3.1.8-1 184/166 9/30/98 3.1.8-2 261/241 3/29/11 3.2.1-1 184/166 9/30/98 3.2.1-2 184/166 9/30/98 3.2.1-3 261/241 3/29/11 3.2.1-4 261/241 3/29/11 3.2.1-5 261/241 3/29/11 3.2.2-1 184/166 9/30/98 3.2.2-2 184/166 9/30/98 3.2.2-3 261/241 3/29/11 3.2.2-4 261/2~1 3/29/11 McGuire Units 1and2 Page2 Revision 112

Page Number Amendment Revision Date

3.2.3-1 3.2.4-1 3.2.4-2 3.2.4".'3 261/241 184/166 184/166 '

184/166 '

3/29/11 9/30/98 9/30/98 9/30/98 3.2.4-4 261/241 3/29/11 3.3.1-1 184/166 9130/98 3.3.1-2 248/228 3/9/09 )

3.3.1-3 248/228 3/9/09 3.3.1-4 216/197 7/29/03 3.3.1-5 250/230 3/9/09 3.3.1-6 ' 248/228 3/9/09 3.3.1-7 248/228 3/9/09 3.3.1-8 184/166 9/30/98 3.3.1-9 261/241 3/29/11 3.3.1-10 261/241 3/29/11 3.3.1-11 261/241 3/29/11

3.3.1-12 3.3.1-13 3.3.1-14 '*

3.3.1-15 283/262 261/241 283/262 283/262 4/8/16 3/29/11 4/8/16 4/8/16 3.3.1-16 287/266 6/21/16 3.3.1-17 283/262 4/8/16 3.3.1-18 219/201 1/14/04 3.3.1-19 219/201 1/14/04 3.3.1-20 184/166 9/30/98 3.3.2-1 184/166 9/30/98 3.3.2-2 250/230 3/9/09 3.3.2-3 248/228 3/9/09 3.3.2-4 248/228 3/9/09 3.3.2-5 248/228 3/9/09 3.3.2-6 198/179 . 4/12/01 '

3.3.2-7 198/179 4/12/01 3.3.2-8 261/241 3/29/11 3.3.2-9 261/241 3/29/11 McGuire Units 1 and 2 Page 3 Revision 112

Page Number Amendment Revision Date 3.3.2-10 3.3.2-11 3.3~2-12 3.3.2-13 272/252 265/245 265/245 265/245 2/28/14 9/12/11 9/12/11 9/12/11 3.3.2-14 293/272 3/8/17 3.3.2-15 272/252 2/28/14 3.3.3-1 221/203 4/29/04 3.3.3-2 227/209 4/4/05 3.3.3-3 261/241 3/29/11 3.3.3-4 227/209 4/4/05 3.3.4-1 221/203 4/29/04 3.3.4-2 261/241 3/29/11 3.3.4-3 184/166 9/30/98 3.3.5-1 184/166 9/30/98 3.3.5-2 261/241 3/29/11 3.3.6-1 Not Used - 243/224 7126107 3.4.1-1 3.4.1-2 3.4.1-3 3.4.1-4 219/201 219/201 261/241 219/201 1/14/04 1/14/04 3/29/11 1/14/04 3.4.2-1 184/166 9/30/98 3.4.3-1 2141195 713103 3.4.3-2 . 261/241 3/29/11 3.4.3-3 214/195 713103 3.4.3-4 214/195 713103 3.4.3-5 214/195 713103 3.4.3-6 214/195 713103 3.4.3-7 214/195 713103 3.4.3-8 214/195 713103 3.4.4-1 261/241 3/29/11 3.4.5-1 216/197 7129103 3.4.5.-2 216/197 7129103 3.4.5-3 261/241 3/29/11 3.4.6-1 216/197 7129103 McGuire Units 1 and 2 Page4 Revision 112

Page Number Amendment Revision Date

3.4.6-2 3.4.6-3 3.4.7-1 3.4.7-2 261/241 285/264 216/197 216/197 3/29/11 4/26/17 7/29/03 7/29/03 3.4.7-3 285/264 4/26/17 3.4.8-1 216/197 7/29/03 3.4.8-2 285/264 4/26/17 3.4.9-1 184/166 9/30/98 3.4.9-2 261/241 3/29/11 3.4.10-1 184/166 9/30/98 3.4.10-2 184/166 9/30/98 3.4-11-1 221/203 4/29/04 3.4.11-2 184/166 9/30/98 3.4-11-3 184/166 9/30/98 3.4.11-4 261/241 3/29/11 3.4.12-1 184/166 9/30/98

3.4.12-2 3.4.12-3 3.4.12-4 3.4.12-5 221/203 214/195 275/255 261/241 4/29/04 713103 12/11/14 3/29/11 3.4.12-6 261/241 3/29/11 3.4.13-1 237/219 3/1/07 3.4.13-2 261/241 3/29/11 3.4.14-1 184/166 9/30/98 3.4.14-2 184/166 9/30/98 3.4.14-3 261/241 3/29/11 3.4.14-4 261/241 3/29/11 3.4.15-1 235/217 9/30/06 3.4.15-2 235/217 9/30/06 3.4.15-3 235/217 9/30/06 3.4.15-4 261/241 3/29/11 3.4.16-1 266/246 6/25/12 3.4.16-2 266/246 6/25/12 3.4.17-1 261/241 3/29/11 McGuire Units 1 and 2 Page 5 Revision 112

Page Number Amendment Revision Date 3.4.18-1 3.4.18-2 3.5.1-1 3.5.1-2 284/263 284/263 218/200 261/241 4/26/16 4/26/16 12/23/03 3/29/11 3.5.2-1 282/261 3/16/16 3.5.2-2 285/264 4/26/17 3.5.2-3 261/241 3/29/11 3.5.3-1 221/203 4/29/04' 3.5.3-2 184/166 9/30/98 3.5.4-1 184/166 9/30/98 3.5.4-2 272/2~2 2/28/14 3.5.5-1* 184/166 9/30/98 3.5.5-2 261/241 3/29/11 3.6.1-1 207/188 9/4/02 3.6.1-2 207/188 9/4/02 3.6.2-1 184/166 9/30/98 3.6.2-2 3.6.2-3 3.6.2-4 3.6.2-5 184/166 184/166 184/166 261/241 9/30/98' 9/30/98 9/30/98 3/29/.11 3.6.3-1 243/224 7126107 3.6.3-2 184/166 9/30/98 3.6.3-3 184/166 9/30/98 3.6.3-4 184/166 9/30/98 3.6.3-5 261/241 3/29/11 3.6.3-6 261/241 3/29/11 3.6.3-7 207/188 9/4/02 3.6.4-1 261/241 3/29/11 3.6.5-1 184/166 9/30/98.

3.6.5-2 261/241 3/29/11 3.6.6-1 285/264 4/26/17 3.6.6-2 285/264. 4/26/17 3.6.7-1 Not Used - 227/209 4/4/05 3.6.8-1 221/203 4/29/04 McGuire Units 1 and 2 Page 6 Revision 112

Page Number Amendment Revision Date

3.6.8-2 3.6.9-1 3.6.9-2 3."6.10-1 261/241 184/166 261/241 184/166 3/29/11 9/30/98 3/29/11 9/30/98 3.6.10-2. 296/275 8/15/17 3.6.11-1 261/241 3/29/11 3.6.11-2 261/241 3/29/11 3.6.12~1 261/241 3/29/11 3.6.12-2 261/241 3/29/11 3.6.12-3 261/241 3/29/11 3.6.13-1 292/271 6/21/17 3.6.13-2 292/271 6/21/17 3.6.13-3 292/271 6/21/17 3.6.14-1 294/273 6/21/17 3.6.14-2 270/250 7/16/13 3$14-3 261/241 .. 3/29/11

3.6.15-1 3.6.15-2 3.6.16-1 3.6.16-2 184/166 261/241 261/241 261/241 9/30/98 3/29/11 3/29/11 3/29/11 3.7.1-1 184/166 9/30/98 3.7.1-2. 184/166 9/30/98 3.7.1-3 269/249 5/16/13 3.7.2-1 184/166 9/30/98 3.7.2-2 184/166 9/30/98 3.7.3-1 184/166 9/30/98 3.7.3-2 184/166 9/30/98 3.7.4-1 221/203 4/29/04 3.7.4-2 261/241 3/29/11 3.7.5-1 282/261 3/16/16 3.7.5-2 282/261 3/16/16 3.7.5-3 261/241 3/29/11 3.7.5-4 261/241 3/29/11 3.7.6-1 282/261 3/16/16 McGuire Units 1 and 2 Page 7 Revision 112

Page Number Amendment Revision Date 3.7.6-2 3.7.7-1 3.7.7-2 3.7.8-1 261/241 282/261 282/261 261/241 3/29/11 3/16/16 3/16/16 3/29/11 3.7.8-2 261/241 3/29/11 3.7.9-1 282/261 3/16/16 3.7.9-2 249/229 1/30/09 3.7.9-3 282/261 3/16/16 3.7.9-4 296/275 8/15/17 3.7.10-1 184/166 9/30/98 3.7.10-2 261/241 3/29/11 3.7.11-1 282/261 3/16/16 3.7.11-2 261/241 3/29/11 3.7.12-1 261/241 3/29/11 3.7.12-2 261/241 3/29/11 3.7.13-1 261/241 3/29/11 3.7.14-1 3.7.15-1 3.7.15-2 3.7.15-3 261/241 225/207 225/207 225/207 3/29/11 3/17/05 3/17/05 3/17/05 3.7.15-4 225/207 3/17/05 3.7.15-5 225/207 3/17/05 3.7.15-6 225/207 3/17/05 3.7.15-7 225/207 3/17/05 3.7.15-8 225/207 3/17/05 3.7.15-9 225/207 . 3/17/05 3.7.15-10 225/207 3/17/05 3.7.15-11 225/207 3/17/05 3.7.15-12 225/207 3/17/05 3.7.15-13 225/207 3/17/05 3.7.15-14 225/207 3/17/05 3.7.15-15 225/207 3/17/05 3.7.15-16 225/207 3/17/05 3.7.15-17 225/207 3/17/05 McGuire Units 1 and 2 Page 8 Revision 112

Page Number Amendment Revision Date

3.7.15-18 3.7.15-19 3.7.15-20 3.7.15-21 225/207 225/207 225/207 225/207 3/17/05 3/17/05 3/17/05 3/17/05 3.7.15-22 225/207 3/17/05 3.7.15-23 225/207 3/17/05 3.7.15-24 225/207 3/17/05 3.7.15-25 225/207 3/17/05 3.7.15-26 . 225/207 3/17/05 3.7.15-27 225/207 3/17/05 3.7.15-28 225/207 3/17/05 3.7.15-29 225/207 3/17/05 3.7.15-30 225/207 3/17/05 3.7.15-31 225/207 3/17/05 3.7.15-32 225/207 3/17/05 3.7.16-1 261/241 3/29/11

3.8.1-1 3.8.1-2 3.8.1-3 3.8.1-4 221/203 184/166 293/272 184/166 4/29/04 9/30/98 3/8/17 9/30/98 3.8.1-5 261/241 3/29/11 3.8.1-6 261/241 3/29/11 3.8.1-7 261/241 3/29/11 3.8.1-8 261/241 3/29/11 3.8.1-9 261/241 3/29/11 3.8.1-10 261/241 3/29/11 3.8.1-11 261/241 3/29/11 3.8.1-12 261/241 3/29/11 3.8.1-13 261/241 3/29/11 3.8.1-14 261/241 3/29/11 3.8.1-15 261/241 3/29/11 3.8.2-1 184/166 9/30/98 3.8.2-2 216/197 7/29/03 3.8.2-3 184/166 9/30/98 McGuire Units 1and2 Page9 Revision 112

Page Number Amendment Revision Date 3.8.3-1 3.8.3-2 3.8.3-3 3.8.4-1 184/166 267/247 261/241 274/254 9/30/98 9/29/12 3/29/11 9/10/14 3.8.4-2 261/241 3/29/11 3.8.4-3 261/241 3/29/11 3.8.4-4 260/240 12/20/10 3.8.5-1 184/166 9/30/98 3.8.5-2 216/197 7/29/03 3.8.6-1 184/166 . 9/30/98 3.8.6-2 261/241 3/29/11 3.8.6-3 261/241 3/29/11 3.8.6-4 184/166 9/30/98 3.8.7-1 261/241 3/29/11 3.8.8-1 184/166 9/30/98 3.8.8-2 261/241 3/29/11 3.8.9-1 3.8.9-2 3.8.10-1 3.8.10-2 184/166 261/241 216/197 261/241 9/30/98 3/29/11 7/29/03 3/29/11 3.9.1-1 261/241 3/29/11 3.9.2-1 261/241 3/29/11 3.9.3-1 216/197 . 7/29/03 3.9.3-2 261/241 3/29/11 3.9.4-1 236/218 12/22/06 3.9.4-2 261/241 3/29/11 3.9.5-1 216/197 7/29/03 3.9.5-2 285/264 4/26/17 3.9.6-1 216/197 7/29/03 3.9.6-2 285/264 4/26/17 3.9.7-1 261/241 3/29/11 4.0.1 288/267 6/21/16 4.0.2 225/207 3/17/05 5.1-1 276/256 2/12/15 McGuire Units 1and2 Page 10 Revision 112

{

Page Number Amendment Revision Date

5.2-1 5.2-2 5.3-1 5.4-1 276/256 276/256 276/256 184/166 2/12/15 2/12/15 2/12/15 9/30/98 5.5-1 290/269 9/26/16 5.5-2 290/269 9/26/16 5.5-3 184/166 9/30/98 5.5-4 184/166 9/30/98 5.5-5 223/205 8/5/04 5.5-6 284/263 4/26/16 5.5-7 284/263 4/26/16 5.5-8 284/263 4/26/16 5.5-9 237/219 3/1/07 5.5-10 237/219 3/1/07 5.5-11 237/219 3/1/07 5.5-12 237/219 3/1/07

5.5-13 5.5-14 5.5-15 5.5-16 237/219 249/229 261/241 261/241 3/1/07 1/30/09 3/29/11 3/29/11 5.6-1 226/208 3/1/07 5.6-2 226/208 3/1/07 5.6-3 226/208 3/1/07 5.6-4 288/267 6/21/16 5.6-5 284/263 4/26/16 5.7-1 276/256 2/12/15 5.7-2 184/166 9/30/98

McGuire Units 1and2 Page 11 Revision 112

LCO Applicability 3.0 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LCO 3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, 3.0. 7, 3.0.8, and 3.0.10.

LCO 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be r:net, except as provided in LCO 3.0.5 and LCO 3.0.6.

If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated. **

LCO 3.0.3 When an LCO is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE or other specified condition in which the LCO is not applicable. Action shall be initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to place the unit, as applicable, in:

a. MODE 3 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months ;

b.

c.

MODE 4 within 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months ; and MODE 5 within 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months .

Exceptions to this Specification are stated in the individual Specifications.

Where corrective measures are completed that permit operation in accordance with the LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required.

LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4 .

McGuire Units 1 and 2 3.0-1 Amendment Nos. 295/274

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0A When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

a. When the* associated ACTIONS to be entered* permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time; or

b. 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; exceptions to this Specificatio"ri are stated in the individual Specifications; or

c. When an allowance is stated in the individual value, parameter, or other Specification.

This Specification shall not prevent changes in MODES or other specified

conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

LCO 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to 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.

McGuire Units 1 and 2 3.0-2 Amendment Nos. 221/203 (continued)

LCO Applicability 3.0 3.0 LCO APPLICABILITY (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 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.

LCO 3.0.8 When one or more required snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:

a. *the snubbers not able to perform their associated support function(s) are associated with only one train or subsystem of a multiple train or subsystem supported system or are associated with a single train or subsystem supported system and are able to perform their associated support function within 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; or

b. the snubbers not able to perform their associated support function(s) are associated with more than one train or subsystem of a multiple train or subsystem supported system and are able to perform their associated support function within 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months .

At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.

LCO 3.0.9 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 identified in 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 will be identified in parentheses or footnotes. (For example, " ... flow rate

McGuire Units 1 and 2 of 54,000 cfm (Unit 1) or 43,000 cfm (Unit 2) ... ").

3.0-3 Amendment Nos. 238/220

LCO Applicability 3.0 3.0 LCO APPLICABILITY (continued)

LCO 3.0.10

When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s), and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

If the required OPERABLE train or subsystem becomes inoperable while this specification is in use, it must be restored to OPERABLE status within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or the provisions of this specification cannot be applied to the trains or subsystems supported by the barriers that cannot perform their related support function(s).

At the end of the specified period, the required barriers must be able to perform their related support function(s) or the supported system LCO(s) shall be declared not met.

McGuire Units 1 and 2 3.0-4 Amendment Nos. 295/274

SR Applicability 3.0 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY SR 3.0.1 SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR.

Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

SR 3.0.2 The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency, as measured from the previous performance or as measured from the time a specified condition of the Frequency is met.

For Frequencies specified as "once," the above interval extension does not apply.

If a Completion Time requires periodic performance on a "once per ... "

basis, the above Frequency extension applies to each performance after the initial performance.

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, 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, whichever is greater. This delay period is permitted to allow performance of the Surveillance. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months , and the risk impact shall be managed.

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 .

McGuire Units 1 and 2 3.0-5 (continued)

Amendment Nos. 295/274

SR Applicability 3.0 3.0 SR APPLICABILITY (continued)

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall only be made when the LCO's Surveillances have been met

. within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.

This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

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-6 Amendment Nos. 295/274

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

b.

Completion of the Required Adions within the specified Completion Times constitutes compliance with a Specification; and 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 .

McGuire Units 1 and 2 B 3.0-1 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued)

Completing the Required Actions is nqt 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 ACTIONS 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 tinie 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*a~sociated Required Actions would apply from the point in time that the new Specification becomes applicable, and the ACTIONS c.ondition(s) are entered.

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 McGuire Units 1 and 2 B 3.0-2 Revision No. 152

LCO Applicability B 3.0 BASES LCO . (continued)

b. Tlie 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. 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 existing LCO 3.0.3 are not complete, but there is reasonable assurance that corrective measures will be completed in time to still allow for an orderly unit shutdown, commencing a load decrease may be delayed until that time. The time limits specified to reach lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE. This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this 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.

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. A Condition exists for which the Required Actions have now been performed.

c. ACTIONS exist that do not have expired Completion Times. These Completion Times are applicable from the point in time that the Condition is initially entered and not from the time LCO 3.0.3 is exited.

McGuire Units 1 and 2 B 3.0-3 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued)

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 reaching the next lower MODE applies. If a lower MODE is reached in less time than allowed, however, the total allowable time to reach MODE 5, or other applicable MODE, is not reduced. For example, if MODE 3 is reached in 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months , then the time allowed for reaching 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 reaching 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 reach a lower MODE of operation in less than the total time allowed.

In MODES 1, 2, 3, and 4, LCO 3.0.3 provides actions for Conditions not covered in other Specifications. The requirements of 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 .

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.13, "Spent Fuel Pool (SFP) Water Level."

LCO 3. 7.13 has an Applicability of "During movement of irradiated fuel assemblies in the sperit fuel pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3. 7.13 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.13 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 individual Specifications.

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 requirements of the LCO would not be met, in accordance with 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 McGuire Units 1 and 2 B 3.0-4 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued) entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time. Compliance with Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change.

Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions.

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 risk assessment will be conducted using the plant program, procedures, and criteria in place to implement 10 CFR 50.65(a)(4), which requires that risk impacts of maintenance activities to be assessed and managed. The risk assessments, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specifications 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 determination that the proposed MODE change is acceptable. Consideration should also be given to the probability of completing restoration such that the requirements of the 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.

McGuire Units 1 and 2 B 3.0-5 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued)

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

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 system 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. In this context, a unit shutdown is defined as a change in MODE or other specified conditi.on 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.

McGuire Units 1 and 2 B 3.0-6 Revision No. 152

LCO Applicability B 3.0 BASES LCO (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 compliance 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.

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

An example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to prevent the trip function from occurring during the performance of an SR on another channel in the other trip system. A similar example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped condition to permit the logic to function and indicate the appropriate response during the performance of an SR on another channel in the same trip system .

McGuire Units 1 and 2 B 3.0-7 Revision No. 152

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

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 McGuire Units 1 and 2 B 3.0-8 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued) 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.

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.o.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 Specification (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

McGuire Units 1 and 2 system's LCO(s) must be declared not met and the Conditions and Required Actions entered in accordance with LCO 3.0.2.

B 3.0-9 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued)

LCO 3.0.8 a applies when one or more required snubbers are not capable of providing their associated support junction(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 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 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) before declaring th.e 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 required 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 vulneral:>ility 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 McGuire Units 1 and 2 remain OPERABLE when required ba~riers are not capable of providing their related support function(s).

B 3.0-10. Revision No. 152

LCO Applicability 8 3.0 BASES LCO (continued)

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.10 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) associated with the Sl.lpported 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

McGuire Units 1 and 2 Barriers," dated April 2, 2001 ).

8 3.0-11 Revision No. 152

LCO Applicability B 3.0 BASES LCO (continued)

The provisions of LCO 3.0.10 are justified bec:ause 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).

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 McGuire Units 1 and 2 B 3.0-12 Revision No. 152

LCO Applicability B 3.0 BASES

. LCO (continued) 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) .

McGuire Units 1 and 2 B 3.0-13 Revision No. 152

B 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY BASES SRs SR 3.0.1 through SR 3.0.5 establish the general requirements applicable to all Specifications and apply at all times, unles~ 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 Surveillances are performed to verify the OPERABILITY of systems and components, and that variables are within specified limits. Failure to meet a Surveillance within the specified Frequency, in accordance with SR 3,0.2, constitutes a failure to meetan 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.

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 unplanned event may be credited as fulfilling the performance of the SR. This allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.

Surveillances, including Surveillances invoked by Required Actions, do not have to be performed on inoperable equipment because the ACTIONS define the remedial measures that apply. Surveillances have to be met and performed in accordance with SR 3.0.2, prior to returning equipment to OPERABLE status.

McGuire Units t and 2 B 3.0-14 Revision No. 152

SR Applicability B 3.0 BASES SURVEILLANCE REQUIREMENT (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 requirements of regulations. The TS cannot in and of themselves extend a test interval specified in regulations.

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 performance on a

McGuire Units 1 and 2 B 3.0-15 Revision No. 152

SR Applicability B 3.0 BASES SURVEILLANCE REQUIREMENT (continued)

"once per ... " basis. The 25% extension applies to each performance after the initial performance. The initial performance of the Required Action; whether it is a particular Surveillance or some other remedial action, is considered a single action with a single Completion Time. One rea~on 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 redundant or diverse components or the action accomplishes the function of the inoperable equipment in an alternative manner.

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

SR 3.0.3 SR 3.0.3 establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a Surveillance has not been completed within the specified Frequency. A delay 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, whichever 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 Frequency was not met.

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

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

When a Surveillance with a Frequency based not on time

. intervals, but upon specified unit conditions, operating situations, or require,ments of regulations (e.g., prior to entering MODE 1 after each fuel loading, or in accordance with 10 CfTR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 McGuire Units *1 and 2 B 3.0-16 Revision No. 152

SR Applicability B 3.0 BASES SURVEILLANCE REQUIREMENT (continued) 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.

Failure to comply with specified Frequencies for SRs is expected

to be an infrequent occurrence. Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used as an operational convenience to extend Surveillance intervals. 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 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 actior:i 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 McGuire Units 1 and 2 B 3.0-17 Revision No. 152

SR Applicability B 3.0 BASES SURVEILLANCE REQUIREMENT (continued) is failed within the delay period, then the equipment is inoperable, or the v.ariable 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 OPERABLE status before

. entering an associated MODE o( 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 Surveillance not being met in accordance with LCO 3.0.4.

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 v~riable 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 ail 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.

McGuire Units 1 and 2 B 3.0-18 Revision No. 152

SR Applicability 8 3.0 BASES SURVEILLANCE REQUIREMENT (continued)

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 Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed 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 .

McGuire Units 1 and 2 8 3.0-19 Revision No. 152

McGuire Nuclear Station Technical Specification Bases LOES TS Bases are revised by section Page Number Revision Revision Date BASES (Revised per section)

Revision 87 8/15/07 ii Revision 87 8/15/07 iii Revision 87 8/15/07 8 2.1.1 Revision 51 01/14/04 8 2.1.2 Revision 109 9/20/10 8 3.0 Revision 152 8/23/17 8 3.1.1 Revision 115 3/29/11 8 3.1.2 Revision 115 3/29/1.1 8 3.1.3 Revision 136 5/14/15 8 3.1.4 Revision 115 3/29/11 8 3.1.5 Revision 115 3/29/11

8 3.1.6 8 3.1.7 8 3.1.8 8 3.2.1 Revision 115 Revision 58 Revision 115 Revision 115 3/29/11 06/23/04 3/29/11 3/29/11 B 3.2.2 Revision 115 3/29/11 8 3.2.3 Revision 115 3/29/11 B 3.2.4 Revision 115 3/29/11 8 3.3.1 Revision 146 1/17/17 8 3.3.2 Revision 138 12/9/15 8 3.3.3 Revision 122 10/25/12 8 3.3.4 Revision 115 3/29/11 8 3.3.5 Revision 115 3/29/11 8 3.3.6 Not Used - Revision 87 6/29/06 B 3.4.1 Revision 115 3/29/11 8 3.4.2 Revision 0 9/30/98 8 3.4.3 Revision 115 3/29/11

B 3.4.4 8 3.4.5 McGuire Units 1 and 2 Revision 115 Revision 115 Page 1 3/29/11 3/29/11 Revision 136

Page Number Amendment Revision Date B 3.4.6 B 3.4.7 B 3.4.8 B 3.4.9 Revision 149 Revision 149 Revision 149 Revision 115 4/26/17 4/26/17 4/26/17 3/29/11 B 3.4.10 Revision 102 8/17/09 B 3.4.11 Revision 115 3/29/11 B 3.4.12 Revision 134 1/8/15 B 3.4.13 Revision 126 5/1/13 B 3.4.14 Revision 115 3/29/11 B 3.4.15 Revision 115 3/29/11 B 3.4.16 Revision 121 8/5/09 B 3.4.17 Revision 115 3/29/11 B 3.4.18 Revision 144 4/26/16 B 3.5.1 Revision 148 4/15/17 B 3.5.2 Revision 149 4/26/17 B 3.5.3 Revision 149 4/26/17 B 3.5.4 B 3.5.5 B 3.6.1 B 3.6.2 Revision 122 Revision 115 Revision 53 Revision 115 10/25/12 3/29/11 2/17/04 3/29/11 B 3.6.3 Revision 115 3/29/11 B 3.6.4 Revision 115 3/29/11 B 3.6.5 Revision 115 3/29/11 B 3.6.6 Revision 149 4/26/17 B 3.6.7 Not Used - Revision 63 414105 B 3.6.8 Revision 115 3/29/11 B 3.6.9 Revision 131 4/14/14 B 3.6.10 Revision 150 8/15/17 B 3.6.11 Revision 138 12/9/15 B 3.6.12 Revision 138 12/9/15 B 3.6.13 Revision 151 6/21/17 B 3.6.14 Revision 151 6/21/17 B 3.6.15 B 3.6.16 McGuire Units 1 and 2 Revision 147 Revision 130 Page2 3/15/17 4/7/14 Revision 136

Page Number Amendment Revision Date

8 3.7.1 8 3.7.2 8 3.7.3 8 3.7.4 Revision 129 Revision 105 Revision 102 Revision 115 10/24/13 2/22/10 8/17/09 3/29/11 8 3.7.5 Revision 115 3/29/11 8 3.7.6 Revision 127 8/2/13 8 3.7.7 Revision 140 3/16/16 8 3.7.8 Revision 128 10/2/13 8 3.7.9 Revision 150 8/15/17 8 3.7.10 Revision 115 3/29/11 8 3.7.11 Revision 115 3/29/11 8 3.7.12 Revision 115 3/29/11 83.7.13 Revision 115 3/29/11 8 3.7.14 Revision 115 3/29/11 8 3.7.15 Revision 66 6/30/05 8 3.7.16 Revision 115 3/29/11

8 3.8.1 8 3.8.2 8 3.8.3 8 3.8.4 Revision 115 Revision 92 Revision 123 Revision 137 3/29/11 1/28/08 9/29/12 8/26/15 B 3.8.5 Revision 41 7/29/03 8 3.8.6 Revision 115 3/29/11 8 3.8.7 Revision 115 3/29/11 8 3.8.8 Revision 115 3/29/11 8 3.8.9 Revision 115 3/29/11 8 3.8.10 Revision 115 3/29/11 8 3.9.1 Revision 115 3/29/11 8 3.9.2 Revision 115 3/29/11 8 3.9.3 Revision 142 4/8/16 8 3.9.4 Revision 115 3/29/11 8 3.9.5 Revision 149 4/26/17 8 3.9.6 Revision 149 4/26/17 8 3.9.7 Revision 115 3/29/11 McGuire Units 1and2 Page 3 Revision 136

ML17248A469

Text

Purpose:

Navigation menu

Search