Jun. 21, 2012 Page 1 of 3 MANUAL HARD COPY DISTRIBUTION DOCUMENT TRANSMITTAL 2012-41789 USER INFORMATION: GERLACH*ROSE M EMPL#:028401 CA#: 0363 Address: NUCSA2 Phone#: 254-3194 TRANSMITTAL INFORMATION: TO: GERLACH*ROSE M 06/21/2012 LOCATION: USNRC FROM: NUCLEAR RECORDS DOCUMENT CONTROL CENTER (NUCSA-2) THE FOLLOWING CHANGES HAVE OCCURRED TO THE HARDCOPY OR ELECTRONIC MANUAL ASSIGNED TO YOU. HARDCOPY USERS MUST ENSURE THE DOCUMENTS PROVIDED MATCH THE INFORMATION ON THIS TRANSMITTAL. WHEN REPLACING THIS MATERIAL IN YOUR HARDCOPY MANUAL, ENSURE THE UPDATE DOCUMENT ID IS THE SAME DOCUMENT ID YOU'RE REMOVING FROM YOUR MANUAL. TOOLS FROM THE HUMAN PERFORMANCE TOOL BAG SHOULD BE UTILIZED TO ELIMINATE THE CHANCE OF ERRORS. ATTENTION: "REPLACE" directions do not affect the Table of Contents, Therefore no TOC will be issued with the updated material. TRM2 - TECHNICAL REQUIREMENTS MANUAL UNIT 2 REMOVE MANUAL TABLE OF CONTENTS DATE: 06/11/2012 ADD MANUAL TABLE OF CONTENTS DATE: 06/20/2012 CATEGORY: DOCUMENTS TYPE: TRM2 Ifv4h
Transcript
Jun. 21, 2012
Page 1 of 3
MANUAL HARD COPY DISTRIBUTION
DOCUMENT TRANSMITTAL 2012-41789
USER INFORMATION:
GERLACH*ROSE M EMPL#:028401 CA#: 0363
Address: NUCSA2
Phone#: 254-3194
TRANSMITTAL INFORMATION:
TO: GERLACH*ROSE M 06/21/2012
LOCATION: USNRC
FROM: NUCLEAR RECORDS DOCUMENT CONTROL CENTER (NUCSA-2)
THE FOLLOWING CHANGES HAVE OCCURRED TO THE HARDCOPY OR ELECTRONIC MANUAL ASSIGNED
TO YOU. HARDCOPY USERS MUST ENSURE THE DOCUMENTS PROVIDED MATCH THE INFORMATION ON
THIS TRANSMITTAL. WHEN REPLACING THIS MATERIAL IN YOUR HARDCOPY MANUAL, ENSURE THE
UPDATE DOCUMENT ID IS THE SAME DOCUMENT ID YOU'RE REMOVING FROM YOUR MANUAL. TOOLSFROM THE HUMAN PERFORMANCE TOOL BAG SHOULD BE UTILIZED TO ELIMINATE THE CHANCE OF
ERRORS.
ATTENTION: "REPLACE" directions do not affect the Table of Contents, Therefore no
TOC will be issued with the updated material.
TRM2 - TECHNICAL REQUIREMENTS MANUAL UNIT 2
REMOVE MANUAL TABLE OF CONTENTS DATE: 06/11/2012
ADD MANUAL TABLE OF CONTENTS DATE: 06/20/2012
CATEGORY: DOCUMENTS TYPE: TRM2
Ifv4h
Jun. 21, 2012
Page 2 of 3
ID: TEXT 3.0
REMOVE: REV:4
ADD: REV: 5
CATEGORY: DOCUMENTS TYPE: TRM2
ID: TEXT 3.8.1
ADD: REV: 3
REMOVE: REV:2
CATEGORY: DOCUMENTS TYPE: TRM2
ID: TEXT 3.8.3
REMOVE: REV:1
ADD: REV: 2
CATEGORY: DOCUMENTS TYPE: TRM2
ID: TEXT 3.8.6
REMOVE: REV:I
ADD: REV: 2
CATEGORY: DOCUMENTS TYPE: TRM2
ID: TEXT B3.0
ADD: REV: 5
REMOVE: REV:4
CATEGORY: DOCUMENTS TYPE: TRM2ID: TEXT B3.8.6
ADD: REV: 3
REMOVE: REV:2
Jun. 21, 2012
Page 3 of 3
CATEGORY: DOCUMENTS TYPE: TRM2
ID: TEXT LOES
ADD: REV: 74
REMOVE: REV:73
ANY DISCREPANCIES WITH THE MATERIAL PROVIDED, CONTACT DCS @ X3107 OR X3136 FOR
ASSISTANCE. UPDATES FOR HARDCOPY MANUALS WILL BE DISTRIBUTED WITHIN 3 DAYS IN
ACCORDANCE WITH DEPARTMENT PROCEDURES. PLEASE MAKE ALL CHANGES AND ACKNOWLEDGE
COMPLETE IN YOUR NIMS INBOX UPON COMPLETION OF UPDATES. FOR ELECTRONIC MANUAL
USERS, ELECTRONICALLY REVIEW THE APPROPRIATE DOCUMENTS AND ACKNOWLEDGE COMPLETE IN
YOUR NIMS INBOX.
SSES MANUAL
Manual Name: TRM2
Manual Title: TECHNICAL REQUIREMENTS MANUAL UNIT 2
Table Of ContentsIssue Dat
Procedure
TEXT LOES
Title:
TEXT TOC
Title:
e: 06/20/2012
Name Rev Issue Date
74 06/20/2012
LIST OF EFFECTIVE SECTIONS
Change ID Change Number
21 12/08/2011
TABLE OF CONTENTS
TEXT 1.1 0 11/19/2002
Title: USE AND APPLICATION DEFINITIONS
TEXT 2.1 1 02/04/2005
Title: PLANT PROGRAMS AND SETPOINTS PLANT PROGRAMS
TEXT 2.2
Title:
10 01/13/2011
PLANT PROGRAMS AND SETPOINTS INSTRUMENT TRIP SETPOINT TABLE
TEXT 3.0 5 06/20/2012
Title: APPLICABILITY TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY
TEXT 3.1.1 1 11/09/2007
Title: REACTIVITY CONTROL SYSTEMS ANTICIPATED TRANSIENT WITHOUT SCRAM ALTERNATE ROD
INJECTION (ATWS-ARI) INSTRUMENTATION
TEXT 3.1.2 0 11/19/2002
Title: REACTIVITY CONTROL SYSTEMS CONTROL ROD DRIVE (CRD) HOUSING SUPPORT
TEXT 3.1.3 4 05/14/2009
Title: REACTIVITY CONTROL SYSTEMS CONTROL ROD BLOCK INSTRUMENTATION
TEXT 3.1.4 0 11/19/2002
Title: REACTIVITY CONTROL SYSTEMS CONTROL ROD SCRAM ACCUMULATORS INSTRUMENTATION AND
SUSQUEHANNA - UNIT 2 TRM / LOES-5 EFFECTIVE DATE 06/12/2012
SUSQUEHANNA STEAM ELECTRIC STATION PPL Rev. 74LIST OF EFFECTIVE SECTIONS (TECHNICAL REQUIREMENTS MANUAL)
Section Title Effective Date
B 3.0 APPLICABILITY BASESPages TRM / B 3.0-1 through TRM / B 3.0-3Page TRM / B 3.0-4Pages TRM / B 3.0-5 through TRM / B 3.0-7Pages TRM / B 3.0-8 through TRM / B 3.0-10Pages TRM / B 3.0-11 and TRM / B 3.0-12Pages TRM / B 3.0-13 and TRM / B 3.0-14Page TRM / B 3.0-15
B 3.1 REACTIVITY CONTROL SYSTEMS BASESPage TRM / B 3.1-1Pages TRM / B 3.1-2 and TRM / B 3.1-3Page B 3.1-4Pages TRM / B 3.1-5 through TRM / B 3.1-7Page TRM / B 3.1-8
B 3.2
B 3.3
CORE OPERATING LIMITS BASESPage B 3.2-1
INSTRUMENTATION BASESPage TRM / B 3.3-1Page TRM / B 3.3-2Page TRM / B-3.3-2aPages TRM / B 3.3-3 and TRM I B 3.3-3aPage TRM / B 3.3-4Page TRM / B 3.3-5Page TRM / B 3.3-6Page TRM / B 3.3-7Page TRM / B 3.3-8Page TRM / B 3.3-9Pages TRM / B 3.3-10 through TRM / B 3.3-13Page TRM / B 3.3-14Page TRM / B 3.3-14aPage TRM / B 3.3-14bPages TRM / B 3.3-15 through TRM / B 3.3-17Pages TRM / B 3.3-18 and TRM / B 3.3-19Pages TRM / B 3.3-19a and TRM / B 3.3-19bPage TRM / B 3.3-19cPages TRM / B 3.3-19d and TRM / B 3.3-19ePage TRM / B 3.3-20Page TRM / B 3.3-21Page TRM / B 3.3-22Page TRM / B 3.3-23Pages TRM / B 3.3-24 and TRM / B 3.3-25
SUSQUEHANNA - UNIT 2 TRM / LOES-6 EFFECTIVE DATE 06/12/2012
SUSQUEHANNA STEAM ELECTRIC STATION PPL Rev. 74LIST OF EFFECTIVE SECTIONS (TECHNICAL REQUIREMENTS MANUAL)
Section Title Effective Date
B 3.4
B 3.5
B 3.6
REACTOR COOLANT SYSTEM BASESPage TRM / B 3.4-1Pages TRM / B 3.4-2 and TRM / B3.4-3Pages TRM / B 3.4-4 and TRM / B 3.4-4aPage TRM / B 3.4-5Page B 3.4-6Page TRM / B 3.4-7
ECCS AND RCIC BASESPages B 3.5-1 and B 3.5-2Pages TRM / B 3.5-3 and TRM / B 3.5-3aPage B 3.5-4Page TRM / B 3.5-5
CONTAINMENT BASESPage TRM / B 3.6-1Page TRM / B 3.6-2Page B 3.6-3Page TRM / B 3.6-4Page TRM / B 3.6-5Page TRM / B 3.6-6Pages TRM / B 3.6-7 through TRM / B 3.6-11
PLANT SYSTEMS BASESPages B 3.7-1 and B 3.7-2Page TRM / B 3.7-3Page TRM / B 3.7-3aPage TRM / B 3.7-4Page TRM / B 3.7-5Pages TRM / B 3.7-6 and TRM / B 3.7-6aPages TRM / B 3.7-7 and TRM / B 3.7-7aPage TRM / B 3.7-8Page TRM / B 3.7-9Page TRM / B 3.7-10Pages TRM / B 3.7-1Oa through TRM / B 3.7-11aPages TRM / B 3.7-12 through TRM / B 3.7-14Page TRM / B 3.7-14aPage TRM / B 3.7-14bPages TRM / B 3.7-15 and TRM / B 3.7-16Pages B 3.7-17 through B 3.7-20Page TRM / B 3.7-21Pages TRM / B 3.7-21a through TRM / 3.7-21gPages TRM / B 3.7-22 and TRM / B 3.7-23Pages TRM / B 3.7-24 through TRM / B 3.7-29
SUSQUEHANNA - UNIT 2 TRM / LOES-7 EFFECTIVE DATE 06/12/2012
SUSQUEHANNA STEAM ELECTRIC STATION PPL Rev. 74LIST OF EFFECTIVE SECTIONS (TECHNICAL REQUIREMENTS MANUAL)
Section Title Effective Date
B 3.8
B.3.9
Page TRM / B 3.7-30Pages TRM / B 3.7-30a and TRM / B 3.7-30bPage TRM / B 3.7-31Page TRM / B 3.7-32Page TRM / B 3.7-33Page TRM / B 3.7-34Page TRM / B 3.7-35Pages TRM / B 3.7-36 and TRM / B 3.7-37Page TRM / B 3.7-38Page TRM / B 3.7-39Page TRM / B 3.7-40
ELECTRICAL POWER BASESPage TRM / B 3.8-1Pages TRM / B 3.8-2 and TRM / B 3.8-2Page TRM / B 3.8-2aPages TRM / B 3.8-3 and TRM / B 3.8-3aPage TRM / B 3.8-4Page TRM / B 3.8-4aPage TRM / B 3.8-5Pages TRM / B 3.8-6 through TRM / B 3.8-16Page TRM / B 3.8-17Page TRM / B 3.8-17aPage TRM / B 3.8-17bPages TRM / B 3.8-18 through TRM I B 3.8-20Pages TRM / B 3.8-21 through TRM / B 3.8-24
REFUELING OPERATIONS BASESPages B 3.9-1 and B 3.9-2Pages B 3.9-3 through B 3.9-7
B 3.10 MISCELLANEOUS BASESPage B 3.10-1Pages TRM / B 3.10-2 and TRM / B 3.10-3Pages TRM / B 3.10-4 and TRM / B 3.10-5
B 3.11 RADIOACTIVE EFFLUENTS BASESPages B 3.11-1 through B 3.11-9Page TRM / B 3.11-10Pages TRM/B 3.11-11 and TRM/B 3.11-11aPages TRM/B 3.11-12 and TRM/B 3.11-13Page TRM / B 3.11-14Page TRM / B 3.11-15Pages B 3.11-16 through B 3.11-19Pages TRM / B 3.11-20 and TRM / B 3.11-20a
SUSQUEHANNA - UNIT 2 TRM / LOES-8 EFFECTIVE DATE 06/12/2012SUSQUEHANNA - UNIT 2 TRM / LOES-8 EFFECTIVE DATE 06/12/2012
SUSQUEHANNA STEAM ELECTRIC STATION PPL Rev. 74LIST OF EFFECTIVE SECTIONS (TECHNICAL REQUIREMENTS MANUAL)
Section Title Effective Date
Page TRM /-B 3.11-21Pages TRM / B 3.11-22 and TRM / B 3.11-23Page TRM / B 3.11-23aPages TRM / B 3.11-24 and TRM / B 3.11-25Pages B 3.11-26 through B 3.11-27Pages TRM / B 3.11-28 and TRM / B 3.11-29Page TRM / B 3.11-30Pages TRM / B 3.11-31 and TRM / B 3.11-32Page TRM / B 3.11-33Pages TRM / B 3.11-34 and TRM / B 3.11-35Page TRM / B 3.11-36
B.3.12 LOADS CONTROL PROGRAM BASESPage TRM / B 3.12-1Page TRM / B 3.12-2Page TRM / B 3.12-3
SUSQUEHANNA - UNIT 2 TRM / LOES-9 EFFECTIVE DATE 06/12/2012
TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY3.0PPL Rev. 5
3.0 TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY
TRO 3.0.1 TROs shall be met during the MODES or other specified conditions in theApplicability, except as provided in TRO 3.0.2.
TRO 3.0.2 Upon discovery of a failure to meet an TRO, the Required Actions of theassociated Conditions shall be met, except as provided in TRO 3.0.5 andTRO 3.0.6.
If the TRO is met or is no longer applicable prior to expiration of the specifiedCompletion Time(s), completion of the Required Action(s) is not required,unless otherwise stated.
TRO 3.0.3 When a TRO is not met, and the associated ACTIONS are not met, anassociated ACTION is not provided, or if directed by the associated ACTIONS,the following actions shall be taken:
1. Take compensatory actions as warranted for exiting TRO 3.0.3commensurate with the safety significance of the condition. Developmentand implementation of the compensatory actions and plan for exit ofTRO 3.0.3 shall be pursued without delay and in a controlled manner andshall be documented in the TRO 3.0.3 entry Condition Report.
2. Initiate a TRO 3.0.3 entry Condition Report that is coded Level 3Evaluation to determine possible changes to the TRO that would precludefuture entry into TRO 3.0.3.
When corrective measures are completed that permit operation in accordancewith the TRO or the TRO actions, completion of the compensatory actions andplan for exiting TRO 3.0.3 is not required.
TRO 3.0.4 When a TRO is not met, entry into a MODE or other specified condition in theApplicability shall only be made:
a. When the associated ACTIONS to be entered permit continued operationin the MODE or other specified condition in the Applicability for anunlimited period of time.
b. After performance of a risk assessment addressing inoperable systemsand components, consideration of the results, determination of theacceptability of entering the MODE or other specified condition in theApplicability, and establishment of risk management actions, ifappropriate; exceptions to this Requirement are stated in the individualTROs, or
c. When an allowance is stated in the individual value, parameter, or otherSpecification.
(continued)
SUSQUEHANNA - UNIT 2 TRM / 3.0-1 EFFECTIVE DATE 06/12/2012
TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY3.0PPL Rev. 5
3.0 TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY
TRO 3.0.4(continued)
Exceptions to this Requirement are stated in the individual Requirements.These exceptions allow entry into MODES or other specified conditions in theApplicability when the associated ACTIONS to be entered allow unit operationin the MODE or other specified condition in the Applicability only for a limitedperiod of time. This Specification shall not prevent changes in MODES orother specified conditions in the Applicability that are required to comply withACTIONS or that are part of a shutdown of the unit.
TRO 3.0.5 Equipment removed from service or declared inoperable to comply withACTIONS may be returned to service under administrative control solely toperform testing required to demonstrate its OPERABILITY, the OPERABILITYof other equipment or variables to be within limits. This is an exception to TRO3.0.2 for the system returned to service under administrative control to performthe testing required to demonstrate OPERABILITY.
TRO 3.0.6 When a supported system TRO is not met solely due to a support system TROor LCO not being met, the Conditions and Required Actions associated withthis supported system are not required to be entered. Only the support systemTRO or LCO ACTIONS are required to be entered. This is an exception toTRO 3.0.2 for the supported system.
When a support system's Required Action directs a supported system to bedeclared inoperable or directs entry into Conditions and Required Actions for asupported system, the applicable Conditions and Required Actions shall beentered in accordance with TRO 3.0.2.
SUSQUEHANNA - UNIT 2 TRM / 3.0-2 EFFECTIVE DATE 06/12/2012
TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY3.0PPL Rev. 5
TRS 3.0.1 TRS shall be met during the MODES or other specified conditions in theApplicability for individual TROs, unless otherwise stated in the TRS. Failureto meet a Surveillance, whether such failure is experienced during theperformance of the Surveillance or between performances of the Surveillance,shall be failure to meet the TRO. Failure to perform a Surveillance within thespecified Frequency shall be failure to meet the TRO except as provided inTRS 3.0.3. Surveillances do not have to be performed on inoperableequipment or variables outside specified limits.
TRS 3.0.2 The specified Frequency for each TRS is met if the Surveillance is performedwithin 1.25 times the interval specified in the Frequency, as measured from theprevious performance or as measured from the time a specified condition ofthe Frequency is met.
For Frequencies specified as "once," the above interval extension does notapply.
If a Completion Time requires periodic performance on a "once per. .. " basis,the above Frequency extension applies to each performance after the initialperformance.
Exceptions to this Requirement are stated in the individual Requirements.
TRS 3.0.3 If it is discovered that a Surveillance was not performed within its specifiedFrequency, then compliance with the requirement to declare the TRO not metmay be delayed, from the time of discovery, up to 24 hours or up to the limit ofthe specified Frequency, whichever is greater. In the event it is determinedthat a Surveillance cannot be performed within its specified Frequency,compliance with the requirement to declare the TRO not met may be delayed,from the expiration of the current Surveillance test interval, up to 24 hours orup to the limit of the specified Frequency, whichever is greater. This delayperiod is permitted to allow performance of the Surveillance. A risk evaluationshall be performed for any Surveillance delayed greater than 24 hours and therisk impact shall be managed.
(continued)
SUSQUEHANNA - UNIT 2 TRM / 3.0-3 EFFECTIVE DATE 3/15/2002
TECHNICAL REQUIREMENT FOR OPERATION (TRO) APPLICABILITY3.0PPL Rev. 5
TRS 3.0.3 If the Surveillance is not performed within the delay period, the TRO must(continued) immediately be declared not met, and the applicable Condition(s) must be
entered.
When the Surveillance is performed within the delay period and theSurveillance is not met, the TRO must immediately be declared not met, andthe applicable Condition(s) must be entered.
Exceptions to this Requirement are stated in the individual Requirements.
TRS 3.0.4 Entry into a MODE or other specified condition in the Applicability of a TROshall not be made unless the TRO's Surveillances have been met within theirspecified Frequency. This provision shall not prevent entry into MODES orother specified conditions in the Applicability that are required to comply withActions or that are part of a shutdown of the unit.
TRS 3.0.4 is only applicable for entry into a MODE or other specified conditionin the Applicability in MODES 1, 2, and 3.
SUSQUEHANNA - UNIT 2 TRM / 3.0-4 EFFECTIVE DATE 11/30/2005
Separate condition entry is allowed for each device.
CONDITION REQUIRED ACTION COMPLETION TIME
A. One or more containment A.1 Deenergize the circuit(s) and 72 hourspenetration conductor declare the affected systemovercurrent protective or component inoperable.devices inoperable.
AND
A.2 Verify affected circuit Once per 7 daysdeenergized.
B. Required Action and B.1 Be in MODE 3. 12 hoursassociated Completion ANDTime for Condition A notmet. B.2 Be in MODE 4. 36 hours
SUSQUEHANNA - UNIT 2 TRM / 3.8-1 EFFECTIVE DATE 04/02/2002
For each circuit breaker found inoperable, an additionalrepresentative sample of Ž10% of all the circuit breakersof the inoperable type shall be functionally tested untilno more failures are found or all circuit breakers of thattype have been functionally tested.
24 months
Perform a functional test on a representative sample of_> 10% of each type of lower voltage circuit breaker.
TRS 3.8.1.2 Perform a functional test on each overcurrent relay. 24 months
---------- NOTE -----------------------------..
The provisions of TRS 3.0.2 are not applicable
TRS 3.8.1.3 Subject each circuit breaker to inspection and 120 monthspreventive maintenance.
SUSQUEHANNA - UNIT 2 TRM / 3.8-2 EFFECTIVE DATE 01/28/2005
1. Separate condition entry is allowed for each Diesel Generator.2. TRO 3.0.4.b is not applicable to DGs.
CONDITION REQUIRED ACTION COMPLETIONTIME
A. TRO requirements not met. A.1 Declare affected DG Immediatelyinoperable.
TECHNICAL REQUIREMENT SURVEILLANCE
SURVEILLANCE FREQUENCY
TRS 3.8.3.1 Inspect diesel in accordance with procedures 5 yearsprepared in conjunction with its manufacturer'srecommendations for this class of standby service.
TRS 3.8.3.2 Verify that the auto-connected loads to each diesel 24 monthsgenerator do not exceed the 2000-hour rating of4700 kW.
(continued)
SUSQUEHANNA - UNIT 2 TRM / 3.8-13 EFFECTIVE DATE 06/12/2012
TRS 3.8.3.3 Verify that the following diesel generator lockout 24 monthsfeatures do not prevent diesel generator startingand/or operation when not required:
a. Engine overspeed.b. Generator differential.c. Engine low lube oil pressure.
TRS 3.8.3.4 For each fuel oil storage tank 10 years
a. Drain the fuel oil;b. Remove the sediment, andc. Clean the tank
TRS 3.8.3.5 Perform a pressure test of those portions of the fuel 10 yearsoil system designed to Section III, Subsection ND ofthe ASME Code in accordance with ASME CodeSection Xl Article IWD-5000.
SUSQUEHANNA - UNIT 2 TRM / 3.8-14 EFFECTIVE DATE 08/31/1998
Emergency Switchgear Room Cooling3.8.6PPL Rev. 2
3.8 Electrical Power
3.8.6 Emergency Switchgear Room Cooling
TRO 3.8.6
APPLICABILITY:
Two Emergency Switchgear Room Cooling subsystems shall beOPERABLE.
Whenever associated emergency switchgear is required to beOPERABLE
ACTIONS
CONDITION REQUIRED ACTION COMPLETIONTIME
A. One required Unit 2 A.1 ---------- NOTE -------------- 30 daysEmergency Switchgear Applicable only in MODESRoom Cooling subsystem 1, 2, or 3.inoperable. -- ------------
Restore subsystem toOPERABLE status.
B. Two required Unit 2 B.1 --------- NOTE ----------- 12 hoursEmergency Switchgear Applicable only in MODESRoom Cooling subsystems 1, 2, or 3.inoperable. -- --------
Restore at least one requiredsubsystem to OPERABLEstatus.
AND (continued)
SUSQUEHANNA - UNIT 2 TRM / 3.8.24 EFFECTIVE DATE 11/30/2011
Emergency Switchgear Room CoolingPPL Rev. 2 3.8.6
ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME
B.2 --------- NOTE ---------------- Immediately
Applicable only in MODES 4, 5,or OPDRVs, COREALTERATIONS, or whenhandling irradiated fuel in thesecondary containment.
Suspend COREALTERATIONS, OPDRVs, andhandling irradiated fuel in thesecondary containment.
AND
B.3 --------- NOTE ----------- 72 hours
Applicable only in MODES 4, 5,or OPDRVs, COREALTERATIONS, or whenhandling irradiated fuel in thesecondary containment.
Restore at least one requiredsubsystem to OPERABLEstatus.
C. Required Action and C.1 Declare affected distribution Immediatelyassociated Completion system inoperable and takeTime of Condition A or B Actions required by - Unit 2not met LCO 3.8.7 or LCO 3.8.8.
D. One required Unit 1 D.1 --------- NOTE ----------- 30 daysEmergency Switchgear Applicable only in Unit 2Room Cooling MODES 1, 2, or 3.subsystem inoperable. -------
Restore subsystem toOPERABLE status.
(continued)
SUSQUEHANNA - UNIT 2 TRM / 3.8.25 EFFECTIVE DATE 06/11/2012
Emergency Switchgear Room CoolingPPL Rev. 2 3.8.6
ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME
E. Two required Unit 1Emergency SwitchgearRoom Coolingsubsystems inoperable.
E. 1 --- - ------------NOTE --------
Applicable only in Unit 2MODES 1, 2, or 3.
AND
E.2
Restore at least one requiredsubsystem to OPERABLEstatus.
--- -------------NOTE --------
Applicable only in Unit 2MODES 4, 5, or OPDRV's,CORE ALTERATIONS, or whenhandling irradiated fuel in thesecondary containment.
Suspend COREALTERATIONS, OPDRVs, andhandling irradiated fuel in thesecondary containment.
- ------NOTE --------
Applicable only in Unit 2MODES 4, 5, or OPDRV's,CORE ALTERATIONS, or whenhandling irradiated fuel in thesecondary containment.
12 hours
Immediately
Immediately
(continued)
AND
E.3
Initiate action to restore onesubsystem to OPERABLEstatus.
SUSQUEHANNA - UNIT 2 TRM / 3.8.25a EFFECTIVE DATE 11/30/2011
Emergency Switchgear Room CoolingPPL Rev. 2 3.8.6
ACTIONS (continued)
CONDITION REQUIRED ACTION COMPLETION TIME
F. Required Action and F.1 Declare affected distribution Immediatelyassociated Completion system inoperable and takeTime of Condition D or E actions required by Unit 1 LCOnot met. 3.8.7 or LCO 3.8.8.
TECHNICAL REQUIREMENT SURVEILLANCE
SURVEILLANCE FREQUENCY
TRS 3.8.6.1 Administratively verify that the Unit 2 Emergency 24 hoursSwitchgear Room Cooling Fans (2V222) areavailable.
TRS 3.8.6.2 Verify that the Emergency Switchgear Room Cooler 92 daysChiller (2K210) will run for at least 60 minutes.
TRS 3.8.6.3 Verify each Emergency Switchgear Room Cooler 24 monthsChiller (2K210) has the capability to maintain thedesign temperature of the emergency switchgear andload center rooms.
SUSQUEHANNA - UNIT 2 TRM / 3.8.25b EFFECTIVE DATE 11/30/2011
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TROs TRO 3.0.1 through TRO 3.0.6 establish the general requirements applicable toall Requirements and apply at all times, unless otherwise stated.
TRO 3.0.1 TRO 3.0.1 establishes the Applicability statement within each individualRequirement as the requirement for when the TRO is required to be met (i.e.,when the unit is in the MODES or other specified conditions of the Applicabilitystatement of each Requirement).
TRO 3.0.2 TRO 3.0.2 establishes that upon discovery of a failure to meet a TRO, theassociated ACTIONS shall be met. The Completion Time of each RequiredAction for an ACTIONS Condition is applicable from the point in time that anACTIONS Condition is entered. The Required Actions establish thoseremedial measures that must be taken within specified Completion Timeswhen the requirements of a TRO are not met. This Requirement establishesthat:
a. Completion of the Required Actions within the specified CompletionTimes constitutes compliance with a Requirement; and
b. Completion of the Required Actions is not required when a TRO is metwithin the specified Completion Time, unless otherwise specified.
There are two basic types of Required Actions. The first type of RequiredAction specifies a time limit in which the TRO must be met. This time limit isthe Completion Time to restore an inoperable system or component toOPERABLE status or to restore variables to within specified limits. If this typeof Required Action is not completed within the specified Completion Time, ashutdown may be required to place the unit in a MODE or condition in whichthe Specification is not applicable.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-1 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.2(continued)
Whether stated as a Required Action or not, correction of the enteredCondition is an action that may always be considered upon entering ACTIONS.The second type of Required Action specifies the remedial measures thatpermit continued operation of the unit that is not further restricted by theCompletion Time. In this case, compliance with the Required' Actions providesan acceptable level of safety for continued operation.
Completing the Required Actions is not required when a TRO is met or is nolonger applicable, unless otherwise stated in the individual Requirements.
The nature of some Required Actions of some Conditions necessitates that,once the Condition is entered, the Required Actions must be completed eventhough the associated Conditions no longer exist. The individual TRO'sActions specify the Required Actions where this is the case. An example ofthis is in Technical Requirement TRO 3.4.1, "Chemistry."
The Completion Times of the Required Actions are also applicable when asystem or component is removed from service intentionally. The reasons forintentionally relying on the ACTIONS include, but are not limited to,modifications, performance of Surveillances, preventive maintenance,corrective maintenance, or investigation of operational problems. EnteringACTIONS for these or for any other reasons must be done in a manner thatdoes not compromise safety.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-2 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.2(continued)
Individual Requirements may specify a time limit for performing a TRS whenequipment is removed from service or bypassed for testing. In this case, theCompletion Times of the Required Actions are applicable when this time limitexpires, if the equipment remains removed from service or bypassed.
When a change in MODE or other specified condition is required to complywith Required Actions, the unit may enter a MODE or other specified conditionin which another Requirement becomes applicable. In this case, theCompletion Times of the associated Required Actions would apply from thepoint in time that the new Requirement becomes applicable and the ACTIONSCondition(s) are entered.
TRO 3.0.3 TRO 3.0.3 establishes the actions that must be implemented when a TRO isnot met and:
a. An associated Required Action and Completion Time is not met and noother Condition applies; or
b. The condition of the unit is not specifically addressed by the associatedACTIONS. This means that no combination of Conditions stated in theACTIONS can be made that exactly corresponds to the actual conditionof the unit. Certain combinations of Conditions may exist such thatentering TRO 3.0.3 is warranted; in such cases, the Actions specificallystate a Condition corresponding to such combinations and also thatTRO 3.0.3 be entered immediately.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-3 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.3(continued)
Because entry into the 3.0.3 ACTION is an escalation of the system, structure,component, or unit condition, a Condition Report is required. The ConditionReport will address plant safety given the nonconformance with the TechnicalRequirement. TROs which affect OPERABILITY of TS Functions will have anassessment of TS OPERABILITY.
Compensatory actions and a plan for exiting TRO 3.0.3 shall be developedand implemented in a timely manner commensurate with the safetysignificance of the entry condition. This will allow for an orderly developmentof actions and plans providing for time to coordinate any actions deemedunwarranted with the station work schedule.
TRO 3.0.3 entries are undesirable and should be avoided whenever possible.Thus, it is important to evaluate the TRO 3.0.3 entry circumstances todetermine if changes to the TRO not met can be made that would preclude theneed for future TRO 3.0.3 entries. Completion of the evaluation is not requiredto exit TRO 3.0.3. The evaluation shall be performed even though TRO 3.0.3has been/will be exited.
TRO 3.0.4 TRO 3.0.4 establishes limitations on changes in MODES or other specifiedconditions in the Applicability when a TRO is not met. It precludes placing theunit in a MODE or other specified condition stated in that Applicability (e.g.,Applicability desired to be entered) when the following exist:
a. Unit conditions are such that the requirements of the TRO would not bemet in the Applicability desired to be entered; and
b. Continued noncompliance with the TRO requirements, if theApplicability were entered, would result in the unit being required to exitthe Applicability desired to be entered to comply with the RequiredActions.
Compliance with Required Actions that permit continued operation of the unitfor an unlimited period of time in a MODE or other specified condition providesan acceptance level of safety for continued operation. This is without regardto the status of the unit before or after the MODE change. Therefore, in suchcases, entry into a MODE or other specified condition in the Applicability maybe made in accordance with the provisions of the Required Actions. Theprovisions of this Requirement should not be interpreted as endorsing thefailure to exercise the good practice of restoring systems or components toOPERABLE status before entering an associated MODE or other specifiedcondition in the Applicability.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-4 EFFECTIVE DATE 01110/2007
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.4 The provisions of TRO 3.0.4 shall not prevent changes in MODES or other(continued) specified conditions in the Applicability that are required to comply with
ACTIONS. In addition, the provisions of TRO 3.0.4 shall not prevent changesin MODES or other specified conditions in the Applicability that result from anyunit shutdown.
TRO 3.0.4 is not applicable to TROs that are identified as APPLICABLE "At alltimes." This term is considered to constitute one inclusive operating conditionthat corresponds to and encompasses all MODES as defined in the TechnicalSpecification, as well as all special operating conditions, including when thereactor vessel is defueled. Entry into any MODE or other special condition isdone within the context of "all times," and, therefore, is not a change within theApplicability to which TRO 3.0.4 applies.
TRO 3.0.4.b allows entry into a MODE or other specified condition in theApplicability with the TRO not met after performance of a risk assessmentaddressing inoperable systems and components, consideration of the results,determination of the acceptability of entering the MODE or other specifiedcondition in the Applicability, and establishment of risk management actions, ifappropriate.
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), whichrequires that risk impacts of maintenance activities to be assessed andmanaged. The risk assessment, for the purposes of TRO 3.0.4(b), must takeinto account all inoperable Technical Requirements Manual equipmentregardless of whether the equipment is included in the normal 10 CFR50.65(a)(4) risk assessment scope. The risk assessments will be conductedusing the procedures and guidance endorsed by Regulatory Guide 1.182,"Assessing and Managing Risk Before Maintenance Activities at NuclearPower Plants." Regulatory Guide 1.182 endorses the guidance in Section 11of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness ofMaintenance at Nuclear Power Plants." These documents address generalguidance for conduct of the risk assessment, quantitative and qualitativeguidelines for establishing risk management actions, and example riskmanagement actions. These include actions to plan and conduct otheractivities in a manner that controls overall risk, increased risk awareness byshift and management personnel, actions to reduce the duration of the
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-5 EFFECTIVE DATE 06/12/2012
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.4 condition, actions to minimize the magnitude of risk increases (establishment(continued) of backup success paths or compensatory measures), and determination that
the proposed MODE change is acceptable. Consideration should also begiven to the probability of completing restoration such that the requirements ofthe TRO would be met prior to the expiration of ACTIONS Completion Timesthat would require exiting the Applicability.
TRO 3.0.4.b may be used with single, or multiple systems and componentsunavailable. NUMARC 93-01 provides guidance relative to consideration ofsimultaneous unavailability of multiple systems and components.
The results of the risk assessment shall be considered in determining theacceptability of entering the MODE or other specified condition in theApplicability, and any corresponding risk management actions. The TRO3.0.4.b risk assessments do not have to be documented.
The Technical Requirements allow continued operation with equipmentunavailable in MODE 1 for the duration of the Completion Time. Since this isallowable, and since in general the risk impact in that particular MODE boundsthe risk of transitioning into and through the applicable MODES or otherspecified conditions in the Applicability of the TRO, the use of the TRO 3.0.4.ballowance should be generally acceptable, as long as the risk is assessed andmanaged as stated above. However, the Emergency Diesel Generators (TRO3.8.3) have been determined to be more important to risk and use of the TRO3.0.4.b allowance is prohibited. A note is included in TRO 3.8.3 stating thatTRO 3.0.4.b is not applicable.
Other exceptions to TRO 3.0.4 are stated in the individual Requirements.Exceptions may apply to all the ACTIONS or to a specific Required Action of aRequirement.
Surveillances do not have to be performed on the associated inoperableequipment (or on variables outside the specified limits), as permitted by TRS3.0.1. Therefore, changing MODES or other specified conditions while in anACTIONS Condition, either in compliance with TRO 3.0.4 or where anexception to TRO 3.0.4 is stated, is not a violation of TRS 3.0.1 or TRS 3.0.4for those surveillances that do not have to be performed due to the associatedinoperable equipment. However, TRSs must be met to ensure OPERABILITYprior to declaring the associated equipment OPERABLE (or variable withinlimits) and restoring compliance with the affected TRO.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-6 EFFECTIVE DATE 06/12/2012
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.5 TRO 3.0.5 establishes the allowance for restoring equipment to service underadministrative controls when it has been removed from service or declaredinoperable to comply with ACTIONS. The sole purpose of this Requirement isto provide an exception to TRO 3.0.2 (e.g., to not comply with the applicableRequired Action(s) to allow the performance of TRSs to demonstrate:
a. The OPERABILITY of the equipment being returned to service; or
b. The OPERABILITY of other equipment; or
c. That variables are within limits
The administrative controls ensure the time the equipment is returned toservice in conflict with the requirements of the ACTIONS is limited to the timeabsolutely necessary to perform the allowed TRSs. This Requirement doesnot provide time to perform any other preventive or corrective maintenance.
An example of demonstrating the OPERABILITY of the equipment beingreturned to service is reopening a containment isolation valve that has beenclosed to comply with Required Actions and must be reopened to perform theTRSs.
An example of demonstrating the OPERABILITY of other equipment is takingan inoperable channel or trip system out of the tripped condition to prevent thetrip function from occurring during the performance of a TRS on anotherchannel in the other trip system. A similar example of appropriate responseduring the performance of an TRS on another channel in the same trip system.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-7 EFFECTIVE DATE 06/12/2012
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 Technical Requirement for Operation (TRO) Applicability
BASES
TRO 3.0.6 TRO 3.0.6 establishes an exception to TRO 3.0.2 for support systems thathave a TRO or LCO specified in the Technical Requirement Specifications(TRS) or Technical Specification (TS). This exception is provided becauseTRO 3.0.2 would require that the Conditions and Required Actions of theassociated inoperable supported system TRO be entered solely due to theinoperability of the support system. This exception is justified because theactions that are required to ensure the plant is maintained in a safe conditionare specified in the support system TRO's or LCO's Required Actions. TheseRequired Actions may include entering the supported system's Conditions andRequired Actions or may specify other Required Actions.
When a support system is inoperable and there is a TRO or LCO specified forit in the TRS or TS, the supported system(s) are required to be declaredinoperable if determined to be inoperable as a result of the support systeminoperability. However, it is not necessary to enter into the supported systems'Conditions and Required Actions unless directed to do so by the supportsystem's Required Actions. The potential confusion and inconsistency ofrequirements related to the entry into multiple support and supported systems'Conditions and Required Actions are eliminated by providing all the actionsthat are necessary to ensure the plant is maintained in a safe condition in thesupport system's Required Actions.
However, there are instances where a support system's Required Action mayeither direct a supported system to be declared inoperable or direct entry intoConditions and Required Actions for the supported system. This may occurimmediately or after some specified delay to perform some other RequiredAction. Regardless of whether it is immediate or after some delay, when asupport system's Required Action directs a supported system to be declaredinoperable or directs entry into Conditions and Required Actions for asupported system, the applicable Conditions and Required Actions shall beentered in accordance with TRO 3.0.2.
SUSQUEHANNA - UNIT 2 TRM / B 3.0-8 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 83.0
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS TRS 3.0.1 through TRS 3.0.4 establish the general requirements applicable toall Requirements and apply at all times, unless otherwise stated.
TRS 3.0.1 TRS 3.0.1 establishes the requirement that TRSs must be met during theMODES or other specified conditions in the Applicability for which therequirements of the TRO apply, unless otherwise specified in the individualTRSs. This Requirement is to ensure that Surveillances are performed toverify the OPERABILITY of systems and components, and that variables arewithin specified limits. Failure to meet a Surveillance within the specifiedFrequency, in accordance with TRS 3.0.2, constitutes a failure to meet a TRO.
Systems and components are assumed to be OPERABLE when theassociated TRSs have been met. Nothing in this Requirement, however, is tobe construed as implying that systems or components are OPERABLE when:
a. The systems or components are known to be inoperable, although stillmeeting the TRSs; or
b. The requirements of the Surveillance(s) are known to be not metbetween required Surveillance performances.
Surveillances do not have to be performed when the unit is in a MODE or otherspecified condition for which the requirements of the associated TRO are notapplicable, unless otherwise specified.
Surveillances, including Surveillances invoked by Required Actions, do nothave to be performed on inoperable equipment because the ACTIONS definethe remedial measures that apply. Surveillances have to be met andperformed in
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-9 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS 3.0.1(continued)
accordance with TRS 3.0.2, prior to returning equipment to OPERABLE status.Upon completion of maintenance, appropriate post maintenance testing isrequired to declare equipment OPERABLE. This includes ensuring applicableSurveillances are not failed and their most recent performance is inaccordance with TRS 3.0.2. Post maintenance testing may not be possible inthe current MODE or other specified conditions in the Applicability due to thenecessary unit parameters not having been established. In these situations,the equipment may be considered OPERABLE provided testing has beensatisfactorily completed to the extent possible and the equipment is nototherwise believed to be incapable of performing its function. This will allowoperation to proceed to a MODE or other specified condition where othernecessary post maintenance tests can be completed.
TRS 3.0.2 TRS 3.0.2 establishes the requirements for meeting the specified Frequencyfor Surveillances and any Required Action with a Completion Time thatrequires the periodic performance of the Required Action on a "once perinterval.
TRS 3.0.2 permits a 25% extension of the interval specified in the Frequency.This extension facilitates Surveillance scheduling and considers plantoperating conditions that may not be suitable for conducting the Surveillance(e.g., transient conditions or other ongoing Surveillance or maintenanceactivities).
The 25% extension does not significantly degrade the reliability that resultsfrom performing the Surveillance at its specified Frequency. This is based onthe recognition that the most probable result of any particular Surveillancebeing performed is the verification of conformance with the TRSs. Theexceptions to TRS 3.0.2 are
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-10 EFFECTIVE DATE 8/31/1998
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRO 3.0.2(continued)
those Surveillances for which the 25% extension of the interval specified inthe Frequency does not apply. These exceptions are stated in theindividual Requirements. As stated in TRS 3.0.2, the 25% extension alsodoes not apply to the initial portion of a periodic Completion Time thatrequires performance on a "once per ..." basis. The 25% extension appliesto each performance after the initial performance. The initial performance ofthe Required Action, whether it is a particular Surveillance or some otherremedial action, is considered a single action with a single Completion Time.One reason for not allowing the 25% extension to this Completion Time isthat such an action usually verifies that no loss of function has occurred bychecking the status of redundant or diverse components or accomplishesthe function of the inoperable equipment in an alternative manner.
The provisions of TRS 3.0.2 are not intended to be used repeatedly merelyas an operational convenience to extend Surveillance intervals (other thanthose consistent with refueling intervals) or periodic Completion Timeintervals beyond those specified.
TRS 3.0.3 TRS 3.0.3 establishes the flexibility to defer declaring affected equipmentinoperable or an affected variable outside the specified limits when aSurveillance has not been completed within the specified Frequency. Adelay period of up to 24 hours or up to the limit of the specified Frequency,whichever is greater, applies from the point in time that it is discovered thatthe Surveillance has not been performed in accordance with TRS 3.0.2, andnot at the time that the specified Frequency was not met.
If a Surveillance cannot be performed within its specified Frequency due tounusual conditions, such as a structure, system, or component configurationthat prevents performance of a test, or performance of the test would havean adverse impact on plant risk, compliance with the requirement to declarethe TRO not met may be delayed. This delay period starts at the expirationof the current Surveillance test interval. The delay can be up to 24 hours orup to the limit of the specified Frequency, whichever is greater.
This delay period provides adequate time to complete Surveillances thathave been missed. This delay period permits the completion of aSurveillance before complying with Required Actions or other remedialmeasures that might preclude completion of the Surveillance.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-11 EFFECTIVE DATE 03/15/2002
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS 3.0.3 The basis for this delay period includes consideration of unit conditions,(continued) adequate planning, availability of personnel, the time required to perform
the Surveillance, the safety significance of the delay in completing therequired Surveillance, and the recognition that the most probable result ofany particular Surveillance being performed is the verification ofconformance with the requirements.
When a Surveillance with a Frequency based not on time intervals, butupon specified unit conditions, operating situations, or requirements ofregulations (e.g., prior to entering MODE 1 after each fuel loading, or inaccordance with 10 CFR 50, Appendix J, as modified by approvedexemptions, etc.) is discovered to not have been performed when specified,TRS 3.0.3 allows for the full delay period of up to the specified Frequency toperform the Surveillance. However, since there is not a time intervalspecified, the missed Surveillance should be performed at the firstreasonable opportunity.
TRS 3.0.3 provides a time limit for, and allowances for the performance of,Surveillances that become applicable as a consequence of MODE changesimposed by Required Actions.
Failure to comply with specified Frequencies for TRSs is expected to be aninfrequent occurrence. Use of the delay period established by TRS 3.0.3 isa flexibility which is not intended to be used as an operational convenienceto extend Surveillance intervals. While up to 24 hours or the limit of thespecified Frequency is provided to perform the missed Surveillance, it isexpected that the missed Surveillance will be performed at the firstreasonable opportunity. The determination of the first reasonableopportunity should include consideration of the impact on plant risk (fromdelaying the Surveillance as well as any plant configuration changesrequired or shutting the plant down to perform the Surveillance) and impacton any analysis assumptions, in addition to unit conditions, planning,availability of
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-12 EFFECTIVE DATE 3/15/2002
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS 3.0.3(continued)
personnel, and the time required to perform the Surveillance. This riskimpact should be managed through the program in place to implement10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide1.182, "Assessing and Managing Risk Before Maintenance Activities atNuclear Power Plants." This Regulatory Guide addresses consideration oftemporary and aggregate risk impacts, determination of risk managementaction thresholds, and risk management action up to and including plantshutdown. The missed Surveillance should be treated as an emergentcondition as discussed in the Regulatory Guide. The risk evaluation may usequantitative, qualitative, or blended methods. The degree of depth and rigorof the evaluation should be commensurate with the importance of thecomponent. Missed Surveillances for important components should beanalyzed quantitatively. If the results of the risk evaluation determine the riskincrease is significant, this evaluation should be used to determine the safestcourse of action. All Surveillances whose Frequency has been extended inaccordance with TRS 3.0.3 will be placed in the Corrective Action Program.
If a Surveillance is not completed within the allowed delay period, then theequipment is considered inoperable or the variable is considered outside thespecified limits and the Completion Times of the Required Actions for theapplicable TRO Conditions begin immediately upon expiration of the delayperiod. If a Surveillance is failed within the delay period, then the equipmentis inoperable, or the variable is outside the specified limits and theCompletion Times of the Required Actions for the applicable TRO Conditionsbegin immediately upon the failure of the Surveillance.
Completion of the Surveillance within the delay period allowed by thisRequirement, or within the Completion Time of the ACTIONS, restorescompliance with TRS 3.0.1.
Exceptions to TRS 3.0.3 are provided in instances where requiringequipment to be considered inoperable, in accordance with TRS 3.0.3, wouldnot provide appropriate remedial measures for the associated condition. Anexample of this is in TRO 3.11.4.1, "Radiological Environmental Monitoring."TRO 3.11.4.1 has surveillances that implement required environmentalsampling and analysis. If a portion of the sampling or analysis is notcompleted as required, the programmatic response is to report the conditionto the Nuclear Regulatory Commission and in most instances describe thecorrective actions taken to correct the condition. There are no result
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-13 EFFECTIVE DATE 11/30/2005
Technical Requirement for Operation (TRO) ApplicabilityB 3.0PPL Rev. 5
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS 3.0.3(continued)
thresholds built into the monitoring and analysis program that would result indeclaring equipment inoperable or in a plant shutdown. Therefore, it isappropriate that the provisions of TRO 3.0.3 be waived for this TRO. Theseexceptions are addressed in the individual Requirements.
TRS 3.0.4 TRS 3.0.4 establishes the requirement that all applicable TRSs must be metbefore entry into a MODE or other specified condition in the Applicability.This Requirement ensures that system and component OPERABILITYrequirements and variable limits are met before entry into MODES or otherspecified conditions in the Applicability for which these systems andcomponents ensure safe operation of the unit.
The provisions of this Requirement should not be interpreted as endorsingthe failure to exercise the good practice of restoring systems or componentsto OPERABLE status before entering an associated MODE or otherspecified condition in the Applicability.
However, in certain circumstances, failing to meet a TRS will not result inTRS 3.0.4 restricting a MODE change or other specified condition change.When a system, subsystem, division, component, device, or variable isinoperable or outside its specified limits, the associated TRS(s) are notrequired to be performed per TRS 3.0.1, which states that Surveillances donot have to be performed on inoperable equipment. When equipment isinoperable, TRS 3.0.4 does not apply to the associated TRS(s) since therequirement for the TRS(s) to be performed is removed. Therefore, failingto perform the Surveillance(s) within the specified Frequency does not resultin an TRS 3.0.4 restriction to changing MODES or other specified conditionsof the Applicability. However, since the TRO is not met in thisinstance, TRO 3.0.4 will govern any restrictions that may (or may not) applyto MODE or other specified condition changes. The provisions of TRS 3.0.4shall not prevent changes in MODES or other specified conditions in theApplicability that are required to comply with ACTIONS. In addition, theprovisions of TRO 3.0.4 shall not prevent changes in MODES or otherspecified conditions in the Applicability that result from any unit shutdown.The precise requirements for performance of TRSs are specified such thatexceptions to TRS 3.0.4 are not necessary. The specific time frames andconditions necessary for meeting the TRSs are specified in the Frequency,in the Surveillance, or both.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.0-14 EFFECTIVE DATE 11/30/2005
Technical Requirement for Operation (TRO) ApplicabilityPPL Rev. 5 B 3.0
B 3.0 TECHNICAL REQUIREMENT SURVEILLANCE (TRS) APPLICABILITY
BASES
TRS 3.0.4(continued)
This allows performance of Surveillances when the prerequisite condition(s)specified in a Surveillance procedure require entry into the MODE or otherspecified condition in the Applicability of the associated TRO prior to theperformance or completion of a Surveillance. A Surveillance that could notbe performed until after entering the TRO Applicability would have itsFrequency specified such that it is not "due" until the specific conditionsneeded are met. Alternately, the Surveillance may be stated in the form ofa Note as not required (to be met or performed) until a particular event,condition, or time has been reached. Further discussion of the specificformats of TRS's annotation is found in Section 1.4, Frequency.
TRS 3.0.4 is only applicable when entering MODE 3 from MODE 4, MODE 2from MODE 3 or 4, or MODE 1 from MODE 2. Furthermore, TRS 3.0.4 isapplicable when entering any other specified condition in the Applicabilityonly while operating in MODE 1, 2, or 3. The requirements of TRS 3.0.4 donot apply in MODES 4 and 5, or in other specified conditions of theApplicability (unless in MODE 1, 2, or 3) because the ACTIONS of individualRequirements sufficiently define the remedial measures to be taken.
SUSQUEHANNA - UNIT 2 TRM / B 3.0-15 EFFECTIVE DATE 3/15/2002
Emergency Switchgear Room CoolingPPL Rev. 3 B 3.8.6
B 3.8.6 Emergency Switchgear Room Cooling
BASES
TRO The Emergency Switchgear Room Cooling (ESRC) system provides heatremoval capability for the Unit 2 emergency switchgear (Room designation11-406 and 11-407) and load center rooms (Room designation 11-507 and11-510) which contain equipment that is required to operate during themitigation of a design basis event. The room cooling system provides theprimary means to remove heat from the equipment located in these rooms.(Reference 1)
Two 100% capacity cooling subsystems provide the normal and emergencyventilation for the emergency switchgear and load center rooms.
This requirement does not include equipment used in the normal coolingmode, which serves no post accident function. It includes the SwitchgearRoom Cooling Direct Expansion (DX) Units. The equipment required for the'A' subsystem of the ESRC system is:
'A' Emergency Switchgear Fan - 2V222A'A' Cooling Coil - 2E296ADX Unit and Associated Equipment - 2K210A
Note that the 'A' DX unit transfers heat to the 'A' ESW subsystem(Technical Specification 3.7.2).
The equipment required for the 'B' subsystem of the ESRC system is:
'B' Emergency Switchgear Fan - 2V222B'B' Cooling Coil - 2E296BDX Unit and Associated Equipment - 2K210B
Note that the 'B' DX unit transfers heat to the 'B' ESW subsystem(Technical Specification 3.7.2).
Additionally, the associated ductwork, dampers and associatedinstrumentation and controls are also required.
Each Unit 2 ESRC subsystem provides cooling for the Unit 2 emergencyswitchgear and load center rooms, which contain equipment from differentelectrical divisions (e.g., the 'A' ESRC subsystem cools both Division I and IIelectrical equipment). Unlike the Unit I ESRC system, no commonequipment is cooled by the Unit 2 ESRC system.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.8-17 EFFECTIVE DATE 11/30/2011
Emergency Switchgear Room CoolingPPL Rev. 3 B 3.8.6
B 3.8.6 Emergency Switchgear Room Cooling
BASES
ACTIONS The Actions are defined to ensure proper corrective measures are taken inresponse to the inoperable components.
These actions are based on the relative impact of ESRC operability on theability of the equipment in the Unit 2 Emergency Switchgear and LoadCenter to perform their safety function. Similar actions for the Unit 1 ESRCsystem is included in the Unit 2 TRM, since the Unit 1 ESRC system coolscommon equipment.
With one required Emergency Switchgear Room Cooling subsysteminoperable (Condition A) in MODES 4 or 5, during OPDRVs, COREALTERATIONS, or when handling irradiated fuel in the secondarycontainment, no action is provided or need be taken in response to thecondition. With one ESRC subsystem inoperable in Modes 1, 2 or 3, theinoperable ESRC subsystem must be restored to OPERABLE status within30 days. With the unit in this condition, the remaining OPERABLE ESRCsubsystem is adequate to perform the cooling function. However, theoverall reliability is reduced since a single failure in the OPERABLEsubsystem results in a loss of the cooling function. The 30 day completiontime is based on the consideration that the remaining subsystem canprovide the required protection, and the availability of alternate non safetycooling methods.
With two required Unit 2 Emergency Switchgear Room Cooling subsystemsinoperable (Condition B), one subsystem must be restored to OPERABLEstatus within 12 hours in Modes 1, 2 or 3. This 12 hour completion time isbased on temperature rise calculations which show that switchgearfunctionality will not be impacted by a loss of switchgear cooling for thistimeframe. In Modes 4 or 5, CORE ALTERATIONS, OPDRVs and handlingirradiated fuel within secondary containment should be suspendedimmediately. This will reduce challenges to systems supported by theESRC systems needed to mitigate the consequences of a fuel handlingevent. Additionally, one subsystem must be restored to OPERABLE statuswithin 72 hours in Modes 4 or 5. This 72 hour completion time is based ontemperature rise calculations which show that switchgear functionality willnot be impacted by a loss of switchgear cooling for this timeframe.
(continued)
SUSQUEHANNA - UNIT 2 TRM / B 3.8-17a EFFECTIVE DATE 06/11/2012
LCO 3.8.7 is entered in the event that the Required Action and associatedCompletion Time of Condition A or B are not met in MODES 1, 2 or 3.LCO 3.8.8 is entered in the event that the Required Action and associatedCompletion Time of Condition B are not met in MODES 4 or 5, or duringOPDRVs, CORE ALTERATIONS, or when handling irradiated fuel in thesecondary containment. Note that some common equipment is located inthe Unit 1 switchgear and load center rooms. If Unit 1 LCO 3.8.7 or LCO3.8.8 is entered, Unit 2 operation will be impacted due to common systemsbeing inoperable. Therefore, loss of one or both Unit 1 ESRC subsystemsrequires entry into Unit 2 TRM 3.8.6 "Emergency Switchgear RoomCooling." Note that the rooms cooled by the Unit 2 ESRC system do notcontain Unit 1 or Common system equipment. Therefore, entry into Unit 1TRO 3.8.6 is not required if the Unit 1 ESRC subsystems are OPERABLEeven if the Unit 2 ESRC system is INOPERABLE.
TRS The TRSs are defined to be performed at the specified Frequency to ensurethat the systems are maintained OPERABLE.
REFERENCE 1. FSAR Section 9.4.2.2
SUSQUEHANNA - UNIT 2 TRM / B 3.8-17b EFFECTIVE DATE 11/30/2011
