Text

Improved Technical Specification Conversion License Amendment Request, Volume 5, (Revision 1), Section 3.0 - LCO and SR Applicability
	ML081480465
Person / Time
Site:	Davis Besse
Issue date:	05/16/2008
From:	; FirstEnergy Nuclear Operating Co
To:	; Office of Nuclear Reactor Regulation
References
	Download: ML081480465 (65)
	v • d • e

DAVIS-BESSE NUCLEAR POWER STATION UNIT 1 IMPROVED TECHNICAL SPECIFICATION CONVERSION LICENSE AMENDMENT REQUEST VOLUME 5 (Rev. 1)

SECTION 3.0 - LCO AND SR APPLICABILITY

Attachment 1, Volume 5, Rev. 1, Page i of i Summary of Changes ITS Section 3.0 Change Description Affected Pages The changes described in the Davis-Besse Page 24 response to question 200712101459 have been made. This adds a discussion into DOC L01 that Davis-Besse has reviewed the CLIIP requirements for the TSTF-359 changes.

The changes described in the Davis-Besse Page 23 response to question 200712101502 have been made. This adds a commitment into DOC M02 concerning LCO 3.0.8 requirements.

The changes described in the Davis-Besse Page 42 response to question 200712101518 have been made. This makes an editorial change to the ITS LCO 3.0.5 Bases.

The changes described in the Davis-Besse Pages 44 and 56 response to question 200712101520 have been made. This change deletes the reference to TSTF-494T and provides a specific Bases JFD.

The changes described in the Davis-Besse Pages 36, 48, and 55 response to question 200712101521 have been made. This deletes an editorial change to the Bases.

The changes described in the Davis-Besse Page 55 response to question 200712101524 have been made. This corrects a typographical error in a Bases JFD.

Page 1 of 1 Attachment 1, Volume 5, Rev. 1, Page i ofi

Attachment 1, Volume 5, Rev. 1, Page 1 of 63 ATTACHMENT 1 VOLUME 5 DAVIS-BESSE IMPROVED TECHNICAL SPECIFICATIONS CONVERSION ITS SECTION 3.0 LCO and SR APPLICABILITY Revision 1 Attachment 1, Volume 5, Rev. 1, Page 1 of 63

Attachment 1, Volume 5, Rev. 1, Page 2 of 63 LIST OF ATTACHMENTS

1. ITS Section 3.0 Attachment 1, Volume 5, Rev. 1, Page 2 of 63

Attachment 1, Volume 5, Rev. 1, Page 3 of 63 ATTACHMENT I ITS Section 3.0, LCO and SR Applicability 0

Attachment 1, Volume 5, Rev. 1, Page 3 of 63

Attachment 1, Volume 5, Rev. 1, Page 4 of 63 Current Technical Specification (CTS) Markup

and Discussion of Changes (DOCs) 0 Attachment 1, Volume 5, Rev. 1, Page 4 of 63

Attachment 1, Volume 5, Rev. 1, Page 5 of 63 ITS Section 3.0 ITS

._0_ I(LO)APPLICABI~LT 11-Rr6t COOIT~nFA] FOR nPPRATT IANIR Q JFD in the Applicabitity, I L;MVTJNG CONDITJTONFOR OqRATTOHI 3.0.1 IL0rting ndit rerents shallbe 3.0.1 L-j-u.appl*:abT SecMc eduring the 7 (except as MODES or other+conditionrs provided in LCO 3.0.2, 3.0.7, and LCO 3.0.8 e foe ch A020 3.0.2 3.12A an/rassociated erencetoACTth Nrequ withinrements of the Liting the spectfle Condition

, time interval forconstitute shall Operation INSERT 1 ' A03

--

Icompliance with the/ pecification, In the vent the Limiting Condition for IOperation Is resto ~d prior to expiration o the specified time interval, inLCO icompletion of the /ACTION statement Is noarequired. ý -. A04 S 3.0.3 When a a tCt -O is not met, except ,provided) 3.0.3 FlT*Ithe asc e CTO~Irreo-fr-ementsj ction shall be Initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months 9 A04

\.-.--

3.0.4 codtonEnshall-not-bp/made t r y l ntooa n OP *tATI unless ONAL MOtheDE o conditions r o t h e r s pe cofi f tlte i e /Limiting p l c a lConditi l y fo pration ar meT-without reliance on provis ions 4ontained' in the ACl to 1 2 1ts unless*~w* /Tl.] )]Ialnt Or~ts pevn MHODESM] required to comply with ACT0ON _-

part of a 3.0.5 When a system, subsystem, train, component or device Is determined to (orother shutdown of specified be Inoperable solely because Its emergency power source is inoperable, or conditions in the unit solely because its normal power source is inoperable, it maybe considered the OPERABLE for the purpose of satisfying the requirements of its applicable Applicability Limiting Condition for Operation, provided: (I)its corresponding normal or that are

.emergency power source is OPERABLE; and (2)all of its redundant system(s ,

subsystem(s), train(s), component(s) and device(s) are OPERABLE, or likewise satisfy the requirements of this specification. Unless both conditions (1) and (2) are satisfied, within 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months action shall be Initiated to place the unit in a ODOE In whlch the applicable Limiting Conditionfor Operation does I

not apply by placing It as applicable in:

1. At least HOT STANDBY within the next 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months .

2. At least HOT SHUTDOWN within'the following 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , and

3. At least COLD SHUTDOWN within the subsequent 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months .

This Specification is not applicable in MODES 5 or 6' 3.0.5 3.0.6 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 e t 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY. LCO DAVIS-BESSE, UNIT 1 3/4 0-1 Amendment No. "

4 A07 INSERT5 INSERT6 A08 INSERT 7of Page 1 of 8 Attachment 1, Volume 5, Rev. 1, Page 5 of 63

Attachment 1, Volume 5, Rev. 1, Page 6 of 63 ITS Section 3.0 INSERT 1 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6.

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

INSERT 2 are not met, an associated ACTION is not provided, or if directed by the associated]-

ACTIONS,Fth-eunit shall be placed in a MODE or other specified condition in which thej__(ýý LCO is not applicable.

O INSERT 3 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.

Insert Page 3/4 0-1a Page 2 of 8 Attachment 1, Volume 5, Rev. 1, Page 6 of 63

Attachment 1, Volume 5, Rev. 1, Page 7 of 63 ITS Section 3.0 INSERT 4 LCO 3.0.4 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;

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 Specification are stated in the individual Specifications; or

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

Q INSERT 5 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, an evaluation shall be performed in accordance with Specification 5.5.14, "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.

Insert Page 3/4 0-1b Page 3 of 8 Attachment 1, Volume 5, Rev. 1, Page 7 of 63

Attachment 1, Volume 5, Rev. 1, Page 8 of 63 ITS Section 3.0 Q* INSERT 6 LCO 3.0.7 Test Exception LCOs 3.1.8 and 3.1.9 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.

O INSERT 7 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.

Insert Page 3/4 0-1c Page 4 of 8 Attachment 1, Volume 5, Rev. 1, Page 8 of 63 1

Attachment 1, Volume 5, Rev. 1, Page 9 of 63 ITS Section 3.0 ITS

v-*Z(SR) APPLICABILITY rSR.SURVEILUANC13 SR 3.0A1 SR 3.0.2 SR 3.0.1-Ircquimrrts ferX'Lmitinz Condition for Op lon (6120. except as p<5izdbelow. /

.If it Is discovered that a Surveilltncc was not perf*umed within its specified Iequercy, then SR 3.0.3 compliance with the requirement to declare tile LCO not mej may be delayed, trom the tinz 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 feuency, whichever is greater. This delay period It perAtt to allow pcrormace otthe Survyellamnc. A risk evaluation sW be perfonTn, for Lay Surveilance delayed greater than 24 howrs" the risk Impact shall be rmanagedl If the Surveillance is not performcd within the delay peciod, the LCWO must irmmediately be declared not tat, &antfte applicable A s N btu henCf~t Condition(s) Cniins When the Suz-villance is peforomd witlhn the delay period and the S LCO must immediately be declared not met, and the applicable A _

ell is not a the -7 must be ent*r...

A09 SR 3.0.1- Sr me do not have to be performed on inoperable equipment outside limits SR 3.0.4 Eatr ino anOPEATINAL MODE or odr-r g*irsoed applicability condition I "al

,. VO nele Re-kU ¢,m=

(or irmscxvicc Inapectiout and tc.*ng ot"ASMZ CCoddc 11. INER 10 and 3 cornlpoucs dsall be applicable'as follows:

a. Instliice

nspectioa of ASM Code Class 1,2 and 3 componets shall be performed in accordanc with Soction XI of the ASMiIBoiler and Pressure VeIssl Code and applicable See Addenda as required by 10 CF>- 50, Section 50-55a.

InsLrvice Testing of ASME Code Clss 1, 2 and 3 pumps and valves shall be perfotrrid in accordance with the ASM) Code for Operation and Maintenance of Nuclear Power Plant ITS 5.5 1

(ASMuE OM Code) and applicable Addenda a" requirzd by 10 CERSO, Section 50-S5a5 DAVIS-fl ISS, U=I I 314 0-2 Arng:ndmant No. 71,140,145,197,2M0 254 Page 5 of 8 Attachment 1, Volume 5, Rev. 1, Page 9 of 63

Attachment 1, Volume 5, Rev. 1, Page 10 of 63 ITS Section 3.0 Q INSERT 8 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.

INSERT 9 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.

INSERT 10 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 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.

Insert Page 3/4 0-2 Page 6 of 8 Attachment 1, Volume 5, Rev. 1, Page 10 of 63

Attachment 1, Volume 5, Rev. 1, Page 11 of 63 ITS Section 3.0 APPLICABILITY SURVEILLANCE REQUIREMENTS (Continued)

b. Surveillance inter*'als specifiEd in Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda and the ASME.OM Code and applicable Addenda shall be applicable as follows in these Technical Specifications:

ASME Boiler and Pressure Vessel Required frequencies for Code and the ASME OM Code and performing inservice applicable Addenda terminology for inspection and testing inservice inspection and testing activities criteria Weekly At least once per 7 days Monthly At least once per 31 days Semi-quarterly At least once per 46 days Quarterly or every 3 months At least once per 92 days See Semiannually or every 6 months At least once per 184 days ITS 5.5 Every 9 months At least once per 276' days Yearly or annually At least once per 366 days Biennially or every 2 years At least once per 731 days c: The provisions of Specification 4.012.are applicableto the above required frequencies for performing inservice inspection and testing activities.

d. Performance of the above inservice inspection and testing activities shall be in addition to other specified Surveillance Requirements.

e. Nothing in'the ASME Boiler and Pressure Vessel Code or the ASME OM Code shall be construed to supersede the requirements of any Technical Specification.

DAVIS-BESSE, UNIT I 3/4 0-3 Amendment No. 250 Page 7 of 8 Attachment 1, Volume 5, Rev. 1, Page 11 of 63

Attachment 1, Volume 5, Rev. 1, Page 12 of 63 ITS Section 3.0 ITS PLANT SYSTEMS 3/4.7.7 SNUBBERS LIMITING CONDITION FOR OPERATION See -]

CTS 3/4.7.7 J 3.7.7 All safety-related snubbers shall be OPERABLE.

APPLICABILITY: MODES 1, 2, 3 and 4. (MODES 5 and 6 for snubberi located on systems required OPERABLE in those MODES).

ACTION:

LCO a. With one or more snubbers inoperable: 1. within 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months 3.0.8 replace or restore the inoperable, snubber(s) to .OPERABLE status, or 2. verify system operability with the snubber(s)' inoperable by engineering evaluation within 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ; or 3. declare the'supported subsystem inoperable and follow the appropriate ACTION statement for that

,system.

and, for snubbers which have failed. either the visual or functional test:

b. Perform an engineering evaluation within 90 days to determine if any safety-related system or component has been adversely affected by the inoperability of the snubber and if the snubber mode of failure has imparted a See significant effect or degradation on the supported CTS 3/4.7.73 component or system.' The provisions of Technical Specification 3.0.4 are not applicable for the component or system.

SURVEILLANCE EQUI*REMENTS 4.7.7 Each snubber 2 shall be demonstrated OPERABLE by the requirements of the following surveillance programs and pursuant to requirements.of Specification 4.0.5.

4.7.7.1 Visual inspection Program See CTS 314.7.7

'Engineering evaluation is not required when a snubber is removed for surveillance testing provided it is returned to OPERABLE status withir the requirements of ACTION statement a.

2 Safety-related snubbers are listed in the latest revision of applicable surveillance test procedure(s). Snubbers may be added to, or removed See from, safety-related systems and their assigned groups without a CTS 3/4.7.7 License Amendment.

DAVIS-BESSE, UNIT I 3/4 7-20 Amendment No. gV/,1'Ml'.161 0

Page 8 of 8 Attachment 1, Volume 5, Rev. 1, Page 12 of 63

Attachment 1, Volume 5, Rev. 1, Page 13 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY ADMINISTRATIVE CHANGES A01 In the conversion of the Davis-Besse Current Technical Specifications (CTS) to the plant specific Improved Technical Specifications (ITS), certain changes (wording preferences, editorial changes, reformatting, revised numbering, etc.) are made to obtain consistency with NUREG-1430, Rev. 3.1, "Standard Technical Specifications-Babcock and Wilcox Plants" (ISTS).

These changes are designated as administrative changes and are acceptable because they do not result in technical changes to the CTS.

A02 CTS 3.0.1 states, "Limiting Conditions for Operation and ACTION requirements shall be applicable during the OPERATIONAL MODES or other conditions specified for each specification." ITS LCO 3.0.1 states, "LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8." This results in several changes to the CTS.

Certain phrases are revised to be consistent with the equivalent phrase used in the ITS. Specifically, "Limiting Conditions for Operation" is changed to "LCOs" and "OPERATIONAL MODES or other conditions specified" is changed to "MODES or other specified conditions" to be consistent with the ITS definition of MODE and the terminology used in the ITS.

These changes are acceptable because they result in no change in the intent or application of the Technical Specification, but merely reflect editorial preferences used in the ITS.

The phrase "... ACTION requirements shall be applicable during the OPERATIONAL MODES.. ." is moved from CTS 3.0.1 to ITS LCO 3.0.2 which states that upon discovery or a failure to meet an LCO, the Required Actions of the associated Conditions shall be met.

The change is acceptable because moving this information within the Technical Specifications results in no change in the intent or application of ACTIONS.

The phrase "shall be applicable" is replaced in ITS LCO 3.0.1 with the phrase "shall be met." This change is made to be consistent with the ITS terminology and to clarify the concept of an LCO being met (i.e., being in compliance with the requirements of the LCO), versus the LCO being applicable or required (i.e., the requirements in the LCO apply).

This change is acceptable because it is an editorial change that does not change the intent of the requirements.

The phrase "except as provided in LCO 3.0.2, 3.0.7, and 3.0.8" is added in ITS LCO 3.0.1. ITS LCO 3.0.2 describes the appropriate actions to be taken when ITS LCO 3.0.1 is not met. LCO 3.0.7 describes Test Davis-Besse Page 1 of 15 Attachment 1, Volume 5, Rev. 1, Page 13 of 63

Attachment 1, Volume 5, Rev. 1, Page 14 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY Exception LCOs, which are exceptions to other LCOs. LCO 3.0.8 addresses snubber inoperabilities, which is also an exception to other LCOs. LCO 3.0.2 modifies ITS LCO 3.0.1 since the ACTION requirements discussion that is in CTS 3.0.1 has been moved to ITS LCO 3.0.2, as described above.

This change is acceptable because adding the exception for LCO 3.0.2, LCO 3.0.7, and LCO 3.0.8 prevents a conflict within the Applicability section. This addition is needed for consistency in the ITS requirements and does not change the intent or application of the Technical Specifications.

These changes are designated administrative because they are editorial and result in no technical changes to the Technical Specifications.

A03 CTS 3.0.2 states, "Adherence to the requirements of the Limiting Condition for Operation and/or associated ACTION within the specified time interval shall constitute compliance with the specification. In the event the Limiting Condition for Operation is restored prior to expiration of the specified time interval, completion of the ACTION statement is not required." ITS LCO 3.0.2 states "Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LCO 3.0.6. If the LCO is met or is no longer applicable prior to expiration of the specified Completion Time(s), completion of the Required Action(s) is not required unless otherwise stated." This results in several changes to the CTS.

The first sentence in CTS 3.0.2 states, in part, "Adherence to the requirements of the Limiting Condition for Operation and/or associated ACTION ... shall constitute compliance with the specification." This requirement is divided into portions of ITS LCO 3.0.1, "LCOs shall be met" and ITS LCO 3.0.2, "Upon discovery of failure to meet an LCO, the Required Actions of the associated Conditions shall be met."

This change is acceptable because the intent of the CTS requirement is preserved, but the aspects of LCO compliance and the performance of ACTIONS when the LCO is not met are separated.

The phrase "except as provided in LCO 3.0.5" has been added to CTS 3.0.2 since ITS LCO 3.0.5 (LCO 3.0.6) already includes the allowance (CTS 3.0.6 states that the allowance is an exception to Specification 3.0.2).

This change is acceptable because it results in no change in the intent or application of the Technical Specification, but merely reflects an editorial preference.

CTS 3.0.2 is revised to include an exception for ITS LCO 3.0.6. LCO 3.0.6 is a new allowance that takes exception to the ITS LCO 3.0.2 requirement to take the Required Actions when the associated LCO is not 0

Davis-Besse Page 2 of 15 Attachment 1, Volume 5, Rev. 1, Page 14 of 63

Attachment 1, Volume 5, Rev. 1, Page 15 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY met. This exception is included in LCO 3.0.2 to avoid conflicts between the applicability requirements.

This change is acceptable because it includes a reference to a new item in the ITS and results in no change to the CTS. Changes resulting from the incorporation of LCO 3.0.6 are discussed in Discussion of Change (DOC) A07.

The second sentence of CTS LCO 3.0.2 states, "In the event the Limiting Condition for Operation is restored prior to expiration of the specified time interval, completion of the ACTION statement is not required." The sentence is replaced in ITS LCO 3.0.2 with "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."

This change is acceptable because, while worded differently, both the CTS and ITS state that ACTIONS do not have to be completed once the LCO is met or is no longer applicable. ITS LCO 3.0.2 also adds the phrase, "unless otherwise stated." There are some ITS ACTIONS that must be completed, even if the LCO is met or is no longer applicable.

This change is acceptable because it reflects a new feature in the ITS which did not exist in the CTS. The technical aspects of these changes are discussed in the appropriate ITS sections.

These changes are designated as administrative because they are editorial and do not result in technical changes to the Technical Specifications.

A04 CTS LCO 3.0.3 is applicable "When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements." ITS LCO 3.0.3 expands those applicability requirements so that the requirement is applicable "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."

This changes the CTS to add two new applicability conditions.

ITS LCO 3.0.3 is applicable when the LCO is not met and there is no applicable ACTION to be taken.

This change is acceptable because it is consistent with the current understanding and application of CTS 3.0.3.

ITS LCO 3.0.3 is applicable when directed by the associated ACTIONS.

The CTS and the ITS contain such requirements. Any technical changes related to directing LCO 3.0.3 entry in an ACTION will be discussed in the affected Technical Specifications.

This change is acceptable because it is consistent with the current understanding and application of CTS 3.0.3.

Davis-Besse Page 3 of 15 Attachment 1, Volume 5, Rev. 1, Page 15 of 63

Attachment 1, Volume 5, Rev. 1, Page 16 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SIR APPLICABILITY These changes are designated as administrative because they do not result in any technical changes to the Technical Specifications.

A05 CTS 3.0.3, in part, states "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 in a MODE in which the Specification does not apply." CTS 3.0.3 also states the shutdown time limits in sequential order; i.e., each time limit is measured from the completion of the previous step. ITS 3.0.3 states "Actions shall be initiated in 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to place the unit, as applicable, in MODE 3 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months , 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 ." ITS 3.0.3 states the time limits (Completion Times) are from the time the condition was entered. In addition, the MODE titles used in CTS 3.0.3 are replaced with the corresponding MODE numbers in ITS LCO 3.0.3. The stated times in CTS 3.0.3 and ITS LCO 3.0.3 are listed below:

Mode Title CTS Time to Enter Mode ITS Time to Enter Mode

-- (Current Mode) 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to begin action 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to begin action 3 Hot Standby within the next 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months 6 hours 4 Hot Shutdown within the following 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months 6 hours 5 Cold Shutdown within the subsequent 24 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months hours These changes are acceptable because the ITS times are the sum of the CTS times (e.g., the ITS Completion Time of 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months to enter MODE 5 is the same as the sum of the CTS allowance of 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months , 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , and 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months .)

This changes the CTS presentation only, and the time allowed to enter each MODE is unchanged. Using MODE numbers instead of the corresponding MODE titles is an editorial preference that results in no change to the requirements in the Technical Specifications. In addition, the CTS 3.0.3 statement "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 in a MODE in which the Specification does not apply" has been editorially reworded in ITS LCO 3.0.3 to "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..." These changes are acceptable because they result in no change in the intent or application of the Technical Specification, but merely reflect editorial preferences used in the ITS.

These changes are designated as administrative as they im plement the editorial conventions used in the ITS without resulting in technical changes to the Technical Specifications.

A06 CTS 3.0.3 states "Where corrective measures are completed that permit operation under the ACTION requirements, the ACTION may be taken in accordance with the specified time limits as measured from the time of failure to meet the Limiting Condition for Operation." ITS LCO 3.0.3 states "Where corrective measures are completed that permit operation in accordance with the Davis-Besse Page 4 of 15 Attachment 1, Volume 5, Rev. 1, Page 16 of 63

Attachment 1, Volume 5, Rev. 1, Page 17 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY LCO or ACTIONS, completion of the actions required by LCO 3.0.3 is not required. LCO 3.0.3 is applicable in MODES 1, 2, 3, and 4."

This change is acceptable because the changes to CTS 3.0.3 are editorial. Both the CTS and ITS state that LCO 3.0.3 can be exited if the LCO which led to the entry into LCO 3.0.3 is met, or if one of the ACTIONS of that LCO is applicable.

The CTS requirement also specifies that the time to complete the ACTIONS in the LCO is based on the initial failure to meet the LCO. Reentering the LCO after exiting LCO 3.0.3 does not reset the ACTION statement time requirements. This information is not explicitly stated in ITS LCO 3.0.3 but is true under the multiple condition entry concept of the ITS. In addition, the sentence "LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4" is added to ITS LCO 3.0.3. CTS 3.0.3 and ITS LCO 3.0.3 require the unit to be placed only as low as COLD SHUTDOWN (MODE 5). Once the unit is in MODE 5, there are no further requirements.

Thus, CTS 3.0.3 and ITS LCO 3.0.3 are effectively only applicable in MODES 1, 2, 3, and 4, and the addition of the sentence merely reflects editorial preferences used in the ITS.

These changes are designated as administrative because there is no change in the intent or application of the CTS 3.0.3 requirements.

A07 ITS LCO 3.0.6 is added to the CTS to provide guidance regarding the appropriate ACTIONS to be taken when a single inoperability (a support system) also results in the inoperability of one or more related systems (supported system(s)). LCO 3.0.6 states "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, an evaluation shall be performed in accordance with Specification 5.5.14, "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." In the CTS, based on the intent and interpretation provided by the NRC over the years, there has been an ambiguous approach to the combined support/supported inoperability. Some of this history is summarized below:

Guidance provided in the June 13, 1979, NRC memorandum from Brian K. Grimes (Assistant Director for Engineering and Projects) to Samuel E.

Bryan (Assistant Director for Field Coordination) would indicate an intent/interpretation consistent with the proposed LCO 3.0.6, without the necessity of also requiring additional ACTIONS. That is, only the inoperable support system ACTIONS need be taken.

Guidance provided by the NRC in their April 10, 1980, letter to all Licensees, regarding the definition of OPERABILITY and its impact as a Davis-Besse Page 5 of 15 Attachment 1, Volume 5, Rev. 1, Page 17 of 63

Attachment 1, Volume 5, Rev. 1, Page 18 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY support system on the remainder of the CTS, would indicate a similar philosophy of not taking ACTIONS for the inoperable supported equipment. However, in this case, additional actions (similar to the proposed Safety Function Determination Program actions) were addressed and required.

Generic Letter 91-18 and a plain-English reading of the CTS provide an interpretation that inoperability, even as a result of a Technical Specification support system inoperability, requires all associated ACTIONS to be taken.

Certain CTS contain ACTIONS such as "Declare the {supported system) inoperable and take the ACTIONS of {its Specification)." In many cases, the supported system would likely already be considered inoperable. The implication of this presentation is that the ACTIONS of the inoperable supported system would not have been taken without the specific direction to do so.

Considering the history of misunderstandings in this area, the Babcock and Wilcox ISTS, NUREG-1430, Rev. 3, was developed with Industry input and approval of the NRC to include LCO 3.0.6 and a new program, Specification 5.5.14, "Safety Function Determination Program (SFDP)." This change is acceptable since its function is to clarify existing ambiguities and to maintain actions within the realm of previous interpretations. This change is designated as administrative because it does not technically change the

Technical Specifications.

A08 ITS LCO 3.0.7 is added to the CTS. LCO 3.0.7 states "Test Exception LCOs 3.1.8 and 3.1.9 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."

This change is acceptable because the CTS contain test exception specifications that allow certain LCOs to not be met for the purpose of special tests and operations. However, the CTS does not contain the equivalent of ITS LCO 3.0.7.

As a result, there could be confusion regarding which LCOs are applicable during special tests. LCO 3.0.7 was crafted to avoid that possible confusion. LCO 3.0.7 is consistent with the use and application of CTS test exception Specifications and does not provide any new restriction or allowance. This change is designated as administrative because it does not technically change the Technical Specifications.

A09 CTS 4.0.1 states, "Surveillance Requirements shall be applicable during the OPERATIONAL MODES or other conditions specified for individual Limiting Conditions for Operation unless otherwise stated in an individual Surveillance 0 Davis-Besse Page 6 of 15 Attachment 1, Volume 5, Rev. 1, Page 18 of 63

Attachment 1, Volume 5, Rev. 1, Page 19 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY Requirement." CTS 4.0.3 states, "Failure to perform a Surveillance Requirement within the allowed surveillance interval defined by Specification 4.0.2, shall constitute noncompliance with the OPERABILITY requirements for a Limiting Condition for Operation (LCO) except as noted below." CTS 4.0.3 also states, "Surveillance requirements do not have to be performed on inoperable equipment." These allowances have been included in ITS LCO 3.0.1. ITS LCO 3.0.1 states, "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." The changes to the CTS are:

The phrase "shall be applicable" is replaced in ITS SR 3.0.1 with the phrase "shall be met." This change is made to be consistent with the ITS terminology and to clarify the concept of an SR being met (i.e., being in compliance with the requirements of the SR), versus the SR being applicable or required (i.e., the requirements in the SR apply).

This change is acceptable because it is an editorial change that does not change the intent of the requirements.

The second sentence of ITS SR 3.0.1 includes the statement, "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." This changes the CTS by adding the clarification "whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance."

This change is acceptable because it is consistent with the current use and application of the Technical Specifications.

The first sentence in CTS 4.0.3 states, "Failure to perform a Surveillance Requirement within the allowed surveillance interval, defined by Specification 4.0.2, shall constitute non compliance with the OPERABILITY requirements for a Limiting Condition for Operation (LCO),

except as noted below." The last sentence in CTS 4.0.3 states, "Surveillance requirements do not have to be performed on inoperable equipment." The third sentence in ITS SR 3.0.1 states, "Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3." The last statement in ITS SR 3.0.1 states, "Surveillances do not have to be performed on inoperable equipment or variables outside specified limits." The changes the CTS by moving the first sentence of CTS 4.0.3 to the third sentence of SR 3.0.1 and by moving the last sentence of CTS 4.0.3 to the fourth sentence of SR 3.0.1 and adds the term "or variables outside limits."

Davis-Besse Page 7 of 15 Attachment 1, Volume 5, Rev. 1, Page 19 of 63

Attachment 1, Volume 5, Rev. 1, Page 20 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY Proposed SR 3.0.1 is constructed to more completely present the relationship between Surveillance Requirements and meeting the requirements of the LCO. In this regard, the concepts within CTS 4.0.3 are combined with CTS 4.0.1 into proposed SR 3.0.1. All LCOs do not deal exclusively with equipment OPERABILITY. Therefore the clarifying phrase, "or variables outside specified limits" is acceptable.

These changes are acceptable and designated administrative because they move and clarify information within the Technical Specifications.

A10? CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified time interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval." ITS SR 3.0.2 states "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." This results in several changes to the CTS.

ITS SR 3.0.2 adds to the CTS "For Frequencies specified as 'once,' the above interval extension does not apply." This is described in DOC M01.

ITS SR 3.0.2 adds to the CTS "If a Completion Time requires periodic performance on a 'once per. . .' basis, the above Frequency extension applies to each performance after the initial performance." This is described in DOC L02.

CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified time interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval." ITS SR 3.0.2 states, in part, "The specified Frequency for each SR is met if the Surveillance is performed within 1.25 times the interval specified in the Frequency." This change is made to be consistent with the ITS terminology and to clarify the concept of the specified SR Frequency being met.

The change is acceptable since it does not change the intent of the requirements.

ITS SR 3.0.2 is more specific regarding the start of the Frequency by stating, "as measured from the previous performance or as measured from the time a specified condition of the Frequency is met." This direction is consistent with the current use and application of the Technical Specifications.

0 Davis-Besse Page 8 of 15 Attachment 1, Volume 5, Rev. 1, Page 20 of 63

Attachment 1, Volume 5, Rev. 1, Page 21 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY This change is acceptable because the ITS presentation has the same intent as the CTS requirement.

ITS SR 3.0.2 adds to the CTS "Exceptions to this Specification are stated in the individual Specifications."

This change is acceptable because it reflects practices used in the ITS that are not used in the CTS. Any changes to a Technical Specification, by inclusion of such an exception, will be addressed in the affected Technical Specification.

The changes except as discussed in DOC M01 and DOC L02 are designated as administrative because they reflect presentation and usage rules of the ITS without making technical changes to the Technical Specifications.

All CTS 3.0.4, in part, states "This provision shall not prevent passage through OPERATIONAL MODES as required to comply with ACTION statements."

CTS 4.0.4 does not include a similar statement. ITS LCO 3.0.4 and SR 3.0.4, in part, state "This Specification shall not prevent entry 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." This changes the CTS by revising the phrase in CTS 3.0.4 and adding the phrase to CTS 4.0.4.

This change is acceptable because the statements in ITS LCO 3.0.4 and ITS SR 3.0.4 are equivalent to the statement in the CTS. Both are stating that LCO 3.0.4 or SR 3.0.4 shall not prevent a unit shutdown required by the Technical Specifications. The ITS wording recognizes that there are conditions in the Applicability that are not MODES, such as "During movement of irradiated fuel within containment." This change is designated as administrative as there is no change in the intent of the CTS and no additional flexibility is granted.

MORE RESTRICTIVE CHANGES M01 CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified time interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval." ITS SR 3.0.2 states "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." This changes the CTS by adding, "For Frequencies specified as 'once,' the above interval extension does not apply."

The remaining changes to CTS 4.0.2 are discussed in DOC A10 and DOC L02.

The purpose of the 1.25 extension allowance to Surveillance Frequencies is to allow for flexibility in scheduling tests. This change is acceptable because

Frequencies specified as "once" are typically condition-based Surveillances in Davis-Besse Page 9 of 15 Attachment 1, Volume 5, Rev. 1, Page 21 of 63

Attachment 1, Volume 5, Rev. 1, Page 22 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY which the first performance demonstrates the acceptability of the current condition. Such demonstrations should be accomplished within the specified Frequency without extension in order to avoid operation in unacceptable conditions. This change is designated as more restrictive because an allowance to extend Frequencies by 25% is eliminated from some Surveillances.

M02 CTS 3.7.7 Action a provides the actions for inoperable snubbers, and requires one of the following (1, 2, or 3) within 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months when one or more snubbers are inoperable: 1) replace or restore the inoperable snubber(s) to OPERABLE status;

2) verify system operability with the snubber(s) inoperable by engineering evaluation; or 3) declare the supported system inoperable and follow the appropriate ACTION statement for that system. In the ITS, the actions for inoperable snubbers are incorporated into ITS 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 either: 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 (i.e., 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months or 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ) snubbers must be able to perform their associated function(s), or the affected system LCO(s) shall be declared not met. This changes the CTS by requiring the risk associated with inoperable snubbers to be assessed and managed and requires the snubbers to be restored to OPERABLE status in all cases, and in certain cases within a more restrictive Completion Time.

The purpose of CTS 3.7.7 Action a is to provide a short time (72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months ) prior to requiring the affected systems to be declared inoperable, to either restore or replace inoperable snubbers or to perform an engineering analyses to assess whether the inoperable snubbers affect the OPERABILITY of the supported components. ITS LCO 3.0.8 requires the risk associated with inoperable required snubbers to be assessed and managed in all instances of snubber inoperability. ITS LCO 3.0.8 also requires all "required" inoperable snubbers to be restored to OPERABLE status within the specified Completion Times. It does not provide an explicit option to perform an engineering evaluation to assess whether the as-found condition of the snubber had no adverse effect on supported components. However, the wording of ITS LCO 3.0.8 (i.e., one or more "required" snubbers) continues to allow this evaluation to be performed.

ITS LCO 3.0.8.a applies when one or more snubbers are not capable of providing their associated support function(s) to a single subsystem of a multiple subsystem supported system or to a single subsystem supported system. ITS 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 snubber(s) before declaring the supported system inoperable, provided only a single subsystem is affected. This 72 hour8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months time is consistent with the CTS. However, ITS LCO 3.0.8.b applies when one or more snubbers are not capable of providing their associated support function(s) to more than one subsystem of a multiple subsystem supported system, and allows 12 hours1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months to restore the snubber(s) before declaring the Davis-Besse Page 10 of 15 Attachment 1, Volume 5, Rev. 1, Page 22 of 63

Attachment 1, Volume 5, Rev. 1, Page 23 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY supported system inoperable. This 12 hour1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months time is more restrictive than the CTS.

The 12 hour1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months Completion Time is acceptable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while the snubber(s) are not capable of performing their associated support function. Furthermore, ITS LCO 3.0.8 requires that risk be assessed and managed. This risk assessment is not required in the CTS.

The Bases for ITS LCO 3.0.8 provides guidance on how the risk must be assessed. 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 ITS LCO 3.0.8 should be considered with respect to other plant maintenance activities, and integrated into the existing Maintenance Rule process to the extent possible so that maintenance on any unaffected train or subsystem is properly controlled, and emergent issues are properly addressed.

The risk assessment need not be quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function. Furthermore, Davis-Besse has reviewed the additional provisions discussed in the CLIIP's Model Safety Evaluation (in Federal Register Notice 69 FR 68412, November 24, 2004),

Section 3.2, and will ensure appropriate plant procedures and administrative controls will be used to implement the applicable Tier 2 Restrictions. Specifically:

a) at least one EFW train (including a minimum set of supporting equipment required for its successful operation) not associated with the inoperable snubber(s) must be available when LCO 3.0.8.a is used; b) at least one EFW train (including a minimum set of supporting equipment required for its successful operation) not associated with the inoperable snubber(s), or some alternative means of core cooling must be available when LCO 3.0.8.b is used; and c) every time the provisions of LCO 3.0.8 are used, Davis-Besse will confirm that at least one train of systems supported by the inoperable snubbers would remain capable of performing their required safety or support functions for postulated design loads other than seismic loads. In addition, a record of the design function of the inoperable snubber (i.e., seismic vs. non-seismic), implementation of any applicable Tier 2 restrictions, and the associated plant configuration shall be available on a recoverable basis for NRC staff inspection. These Tier 2 Restrictions are also more restrictive than what is currently required by the Davis-Besse CTS. This change is designated as more restrictive because inoperable snubbers must be restored to OPERABLE status under certain conditions within a more restrictive Completion Time and the risk associated with inoperable snubbers must always be assessed and managed.

RELOCATED SPECIFICATIONS None REMOVED DETAIL CHANGES None Davis-Besse Page 11 of 15 Attachment 1, Volume 5, Rev. 1, Page 23 of 63

Attachment 1, Volume 5, Rev. 1, Page 24 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY LESS RESTRICTIVE CHANGES L01 CTS 3.0.4 states, "Entry into an OPERATIONAL MODE or other specified applicability conditions shall not be made unless the conditions of the Limiting Condition for Operation are met without reliance on provisions contained in the ACTION statements unless otherwise excepted." CTS 4.0.4 states, "Entry into an OPERATIONAL MODE or other specified applicability condition shall not be made unless the Surveillance Requirements(s) associated with the Limiting Condition for Operation have been performed within the stated surveillance interval or as otherwise specified." ITS LCO 3.0.4 states "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; 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 Specification 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." ITS SR 3.0.4 states, "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 changes the CTS by providing allowances for entry into a MODE or other specified condition in the Applicability when an LCO is not met.

The purpose of LCO 3.0.4 is to provide guidance when an LCO is not met and entry into a MODE or other specified condition in the Applicability is desired.

Davis-Besse has reviewed the safety evaluation dated March 28, 2003, which was published in the Federal Register to support this change through the Consolidated Line Item Improvement Process. This review included a review of the NRC staffs evaluation, as well as the supporting information provided to support TSTF-359, rev. 8. Davis-Besse has concluded that the justifications presented in the TSTF proposal and the safety evaluation prepared by the NRC staff are applicable to Davis-Besse and justify the incorporation of this change into the Davis-Besse Technical Specifications. Therefore, the change is considered acceptable.

In addition, the proposed Bases for LCO 3.0.4 and SR 3.0.4 is consistent with that provided in the TSTF, except for minor editorial changes that do not change the intent of the TSTF Bases. The proposed Bases provides details on how to implement the new requirement. Specifically, 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 Davis-Besse Page 12 of 15 Attachment 1, Volume 5, Rev. 1, Page 24 of 63

Attachment 1, Volume 5, Rev. 1, Page 25 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY entry into a MODE or other specified condition in the Applicability with the LCO not met 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. 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.

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 assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." These documents address general guidance for conduct of-the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and 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. NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components. The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions. The 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 systems and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is Davis-Besse Page 13 of 15 Attachment 1, Volume 5, Rev. 1, Page 25 of 63

Attachment 1, Volume 5, Rev. 1, Page 26 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY not applicable. These systems and components are the ECCS Low Pressure Injection Subsystem, the Auxiliary Feedwater System and Motor Driven Feedwater Pump train, and the emergency diesel generators (ITS 3.5.3, ITS 3.7.5, and ITS 3.8.1, respectively). 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 that describe values and parameters. 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 condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4. 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 Specifications. 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 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. This change is designated as less restrictive because entry into MODES or other specified conditions in the Applicability of a Specification might be made with an LCO not met as long as the plant is in compliance with LCO 3.0.4.

L02 CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified time interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval." ITS SR 3.0.2 states "The specified Frequency for each SR is met ifthe 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." This changes the CTS by adding, "If a Completion Time requires periodic performance on a 'once per. . .' basis, the above Frequency extension applies to each performance after the initial performance." The remaining changes to CTS 4.0.2 are discussed in DOC A10 and DOC M01.

Davis-Besse Page 14 of 15 Attachment 1, Volume 5, Rev. 1, Page 26 of 63

Attachment 1, Volume 5, Rev. 1, Page 27 of 63 DISCUSSION OF CHANGES ITS SECTION 3.0, LCO AND SR APPLICABILITY This change is acceptable because the 25 percent Frequency extension given to provide scheduling flexibility for Surveillances is equally applicable to Required Actions that must be performed periodically. The initial performance is excluded because the first performance demonstrates the acceptability of the current condition. Such demonstrations should be accomplished within the specified Completion Time without extension in order to avoid operation in unacceptable conditions. This change is designated as less restrictive because additional time is provided to perform some periodic Required Actions.

Davis-Besse Page 15 of 15 Attachment 1, Volume 5, Rev. 1, Page 27 of 63

Attachment 1, Volume 5, Rev. 1, Page 28 of 63 Improved Standard Technical Specifications (ISTS) Markup and Justification for Deviations (JFDs)

Attachment 1, Volume 5, Rev. 1, Page 28 of 63

Attachment 1, Volume 5, Rev. 1, Page 29 of 63 LCO Applicability 3.0 CTS 3.01 LIMITING OONDITION FOR OPERATION (LCO)APPLICABILITY O 3/4 3.0.1 LCO 3.0.1 LCOs shall bernet during the MODES orother specified conditions in ,the Applicability, except as provided ih LO'3.0.2, LCO 3.0.71 and LCd 3.0.8.

3.0.2 LCO 3.0.2, Upon discovery 6f a.failure :to mfleet ah LCOO.the Required Actions of'the associated Conditions shall be met, 6xc-6ptaa(sprovided in LCQO3.0 5.and LCO 3A.08*

If the LCO is: met or is no longer appli cab e. priorto expiration of the specified CompletionTime(s), completion of the Required Actionr(s):i S:not required, unless otherwise stated.

3.0.3 LCO 3.0.3 When an LCOis 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 LCOis not applicable. Action shall be initiated withinl hour to place the unit, as applicable, in:

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

b. MODE4 within 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months and

c. MODE 5 within 37: hours'. 0 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.

304 LCO 3..0;4 When an LCO is not met, entryinto 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;

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 Specification are stated in the. individual Specifications or 0

BWOG STS 3.0-1 Rev. 3.1, 12/01/05 0

Attachment 1, Volume 5, Rev. 1, Page 29 of 63

Attachment 1, Volume 5, Rev. 1, Page 30 of 63 LO .Applicability 3.0 CTS 3.0 LCO Applicabili ty 3.0.4 LCO 3.0.4 (continued) ct When an allowance is stated in.the individual.value,:.parameter,.or other Specification, entry This&Specification: shall not prevent, .e in, lOOES&,oi 0ther specified.

0 conditions in the Applicabiitfy that, are required to comply,.withACTIONS or that are part of a shutdown of the unit.

3.0.6 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'OPERABIllTY or the, OPERABILITY of other equipment. This is an exception to LCO.G.3.0.2 for.,

the system returned to service underadrhinistrative control to. perform the:

testing required to demonstrate OPERABILITY.

DOC LCOG 3.0.6 When a supported system LCO is not met solely, due to a suppoIrt system A07 LCO not being met,'the Conditions and Required Actions associa tedlwith this supported system are not required to. belentered. Qnlylthe support system LCO ACTIONS are required*to.. be,.entered. This is-an exception to LOG 3.0.2 for the supported system. In this event, an evaluation, shall be performed in accordance with .Specification 5.5. ,j"Safety Function Determination Program (SFDP)." If a loss of safety function is determined 0 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.

'31 DOC A08 LCO 3.0.7 [I* Test Exception LCOsfJ3.-l.*, 3.1t 1 11Jand 3 allow specified Technical Specification (TS) requirements to be changed to permit 0

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 otherspecified condition in theApplicability shallbe made in accordance with the other applicable Specifications.

BWOG STS 3.0-2 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 30 of 63

Attachment 1, Volume 5, Rev. 1, Page 31 of 63 LCd Applicability 3;~0 CTS 3.0 LCO Applicability, 3.7.7 LCO 3:0:8 When one or more required snubbers,.are unable, toperform their Action a associateld 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 perf0rm ltheir associated1support

-function(s) are associated with only: one train or subsystem ofa, multiple train or subsystem supported System.or are asseciated.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 assbci ated support function(s) are associated with more than one train or.subsystem. of a multiple train or subsystem supported system and are abletio perform iheir 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 met.

system LCO(s) shall be declared not BWOG STS 3.0-3 Rev. 3., 12/01105 Attachment 1, Volume 5, Rev. 1, Page 31 of 63

Attachment 1, Volume 5, Rev. 1, Page 32 of 63 SR Applicability 3.0 a CTS 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY 4.0.1, SR 3.0.1 SRs shall be-met.during the MODES or other specified conditions inthe 4.0.3 Applicability for individual LCOs, unless otherwise stated in the SRI..

Failure to meet a.Surveillance, whether such failure is experienced during the performance of the'Surveillance or between performances:of the Surveillance, shall be f6ilure to meet the LCO- Failure to perform a Surveillance within the.specified Frequency shall be failure to nieet 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.

4.0.2 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 meadsudr from the previous performance or as measured from *the time a spedified :condition of the Frequency is met.

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

If a Completioh Time requifes periodic.performanrce oni 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.

4.0.3 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 hod*s 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.

4.0.4 SR 3.0.4 Entry into aMODE or other specified condition in theApplicabilityof an LCOshall 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 orother specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.

BWOG STS 3.0-4 Rev. 3.0, 03/31/04 1 40 Attachment 1, Volume 5, Rev. 1, Page 32 of 63

Attachment 1, Volume 5, Rev. 1, Page 33 of 63 SR :Applicability 3.0

. CTS 4.0.4 3.0 SR Applicability SR 3.0.4 (continued)

This provision shall not prevent entry into MODES Or other specified, conditions in the'rApplicability that"arerequired to comply with ACTIONS or that are part of a shutdoWn of the unit.

BWOG STS 3.0-5 Rev. 30', 03131104 Attachment 1, Volume 5, Rev. 1, Page 33 of 63

Attachment 1, Volume 5, Rev. 1, Page 34 of 63 JUSTIFICATION FOR DEVIATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY

1. These punctuation corrections have been made consistent with the Writer's Guide for the Improved Standard Technical Specifications, TSTF-GG-05-01, Section 5.1.3.

2. The brackets have been removed and the proper plant specific information/value has been provided.

3. The words "changes in" in LCO 3.0.4 has been changed to "entry into" to be consistent with the terminology used in SR 3.0.4.

4. The correct LCO number has been provided.

Davis-Besse Page 1 of 1 Attachment 1, Volume 5, Rev. 1, Page 34 of 63

Attachment 1 ,.Volume 5, Rev. 1, Page 35 of 63 Improved Standard Technical Specifications (ISTS) Bases Markup and Justification for Deviations (JFDs)

Attachment 1, Volume 5, Rev. 1, Page 35 of 63

Attachment 1, Volume 5, Rev. 1, Page 36 of 63 LCO APPLICABI LITY B3.0 B 3.0 LIMITI.NG.*CNDITION FOR OPERATION (LCO). APPLICABILITY BASES LCOs LCO3.0.1 through LCO 3.0.8 establish the general requirements applicable to0all 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 isapplicable 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. Completion of the Required.Actions within the specified Completion Times constitutes compliance with a Specification and b.- Completion of the Required Actions is not required when an LCO is 0

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

Completing the Required Actions is not required when an LCO is met or is no longer applicable, unless otherwise stated in the individual Specifications.

BWOG STS B 3.0-1 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 36 of 63

Attachment 1, Volume 5, Rev. 1, Page 37 of 63 LCO APPLICABILITY

ýB 3.0 BASES LCO 3.0.2, (continued):

The natureof 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.(P/T) Limits."

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

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

LCO 3.0.3 LCO .3.0.3 establishes the actions thatmust be implemented when an LCO is not met and either:

a. An associated Required Action and Completion Time is not met and no other Condition appliesor BWOGSTS B 3.0-2 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 37 of 63

Attachment 1, Volume 5, Rev. 1, Page 38 of 63 LCO APPLICABILITY B3.0

BASES LCO 3.0.3 (continued)

b. The condition of the unit is not specifically addressed by the associated ACTIONS. This means that no combination of Conditions stated in the ACTIONS can be made that exactly corresponds to the.

actual condition of the Unit. Sometimes, possible combinations of Conditions are such that entering LCO 3.0.3 is warranted; in such casesthe 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 safeoperation as defined by theLCO..and its ACTIONS. It is not intended to be, used as an operational convenience that permits routine voluntary removal of redundant systems or components from service in lieu of other alternatiVes that Would not result in redundant systems Or components being inoperable.

Upon entering LCO 3.0.3, 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months is allowed to prepare for an orderly shutdown~before initiating a change in unit operation. This includes time to permit the operator to coordinate the reduction.in electrical generation with the load dispatcher to ensure the stability and availability of the electrical grid. The 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 ofspecified times to complete the actions of LCO :3.0.3 are consistent with the discussion of Section 1.3,tCompletion Time 4 1(

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 LCOis now melt-1 _

b. A Condition exists for which the Required Actions have now been performed 5 9 r o

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.

BWOG STS B 3.0-3 Rev. 3.1, 12/101105 Attachment 1, Volume 5, Rev. 1, Page 38 of 63

Attachment 1, Volume 5, Rev. 1, Page 39 of 63 LCO APPLICABILIT B3.0

.BASES LCO 3.0.3 (continued)

The time limits of LCO 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 isreached 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 hot apply in MODES 5 and 6 because the unitt.is already in the most restrictivetondition required by LCO 3.0.3. The requirements of LCO 3.0.3 do not apply in other specified conditions of the Applicability 0

(unless in MODE 1, 2, 3, or 4) because the ACTIONS ofiindividual Specifications sufficiently define the remedial measures to be taken.

Exceptions to LOG 3.0.3 are provided in instances where requiring a unit shutdown, in. accordance with LCO 320.3, would not provide appropriate remedial measures for the associated condition of the.unit. An example.

e o fthis is in LCO 3.7.14, ,"FuelS Pool Water Level." LCO 3.7.14 has an Applicability of "During movement of irradiated fuel assemblies in st uel s pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.14 are ndt mbt while in MODE 1, 2, 3, or 4, there is no safety benefit to. be gained by placing the unit in a shutdown condition. The Required Action of spent L 3 "Suspend movement ofirradiated fuel assemblies inhfuel 3

[* pool" is the appropriate Required Action to complete in lieu of the actions of LGO 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 MODEor other specified condition stated in that Applicability (?j,, the Applicability desired to be entered) when unit i (.)

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.

BWOG STS B 3.0-4 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 39 of 63

Attachment 1, Volume 5, Rev. 1, Page 40 of 63 LCO APPLICABILITY B 3.0 BASES LCO. 3.0.4 (continued)

LOG 3.0A.a allows entry into.a MODE or:other specified condition in the Applicability with the LCO not met:when the associated ACTIONS to be entered 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. requir.es-tW risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at.Nuclear Power Plants." Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk managementactions, 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 requireexitingthe Applicability.

BWOG STS B 3.0-5 Rev. 3.1, 12/01105 Attachment 1, Volume 5, Rev. 1, Page 40 of 63

Attachment 1, Volume 5, Rev. 1, Page 41 of 63 LCO APPLICABILITY B.3.0

BASES LCO 3.0.4 (continuedcl LCO 3.0.4.b may be Used with singleaor multiple systems and components unavailable. NUMARC 93-01 provides guidance relative toý consideration of sim.ultaneous unavailability. of multiple systems and components.

Theresults 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 operationwith 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 therisk 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 havebeen determined to be more important to risk and use of the LCO 3.0.4.b allowance is prohibited. The LCOs governing these systems and components contain Notes prohibitingthe 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 inthe Specification which states LCO 3:0.4.c is applicable. These specific allowances permit entry into MODES or other specified conditions in theApplicability 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 justifythe use of LCO.3.0.4.b usually only consider systems and components. Forthis reason, LCO 3.0:4.c is typically applied to Specifications which describe values and arameters (.e.g.,j[ontainment Air Temperature, Containment Pressure, [ t oderator Temperature }0 CoefficientD, and may be applied to other Specifications based on NRC plant specific approval.

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.

BWOG STS B 3.0-6 Rev. 3.1 ,12101/05 Attachment 1, Volume 5, Rev. 1, Page 41 of 63

Attachment 1, Volume 5, Rev. 1, Page 42 of 63 LCO APPLICABI LITY B 3.0 BASES LCO 3.0.4 (continued) entt to The provisions of LCO 3.0.4 shall not prevent cap4 sTin.MODES or S

other specified conditions in the Applicability that are required to comply Fi-iH91nto with ACTIONS. In addition, the provisions of LCO 3.0.4.shall not prevent 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.

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 LCO3.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 compliancewith the affected LCO.

LCO 3.0.5 LCO 3.0.5 establishes the allowance for restoring equipment.to service under administrative controlswhenit 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 30.2 (e.g., to not comply with the applicable Required Action(s)) to allow the performance of required testing to demonstrate either;

a. The OPERABILITY of the equipment being returned toservice or

b. The OPERABILITY of other equipment. 5 The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform.the required testing to demonstrate OPERABILITY. This Specification does not provide time to perform any other preventive or corrective maintenance.

LAn example of demonstrating the OPERABILITY of the equipment being returned to service is eopening a containment isolation valve that has been closed to comply with Required Actions and SD must be reopened to perform the required testing.

BWOG STS B 3.0-7 Rev. 3.1, 12/01105 Attachment 1, Volume 5, Rev. 1, Page 42 of 63

Attachment 1, Volume 5, Rev. 1, Page 43 of 63 LCO APPLICABILITY B 3.0 BASES LCO 3.0.5 (continued)

An example of demonstrating the OPERABILITY of other equipment is taking an inoperable channel or trip system out of the tripped cbnditionto0 prevent the trip function from occurring during the performance of.

required testing on another channel in the other trip system. A similar example of demonstrating the OPERABILITY of otherequipment 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 required testing on another channel in the same trip system.

LCO 3.0.6 LCO.3.0.6 establishes an exception to LCO 3.0.2 for supported systems.

that have a support system 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 safecondition: are specified in the support systern LCO's Required Actions. These RequiredActions may include entering the supported systenVi3Conditipns and Required Actions or may specify other Required Actions.

0 When a support system is inoperable and there isan 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'. LCO*'Conditions and Required Actions are 0 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 Reqluired 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 accordancewith LCO 3.0.2.

BWOG STS B 3.0-8 Rev. 3.1,12/01105 0

Attachment 1, Volume 5, Rev. 1, Page 43 of 63

Attachment 1, Volume 5, Rev. 1, Page 44 of 63 LCO APPLICABILITY B 3.0 B'ASES LCO 3.0.6 (continue Specification 5.5. ,"Safety Function Determination Program (SFDP),"

ensures loss of safetyfunction 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 systemConditions and Required Actions. The SFDP imrn*m*.nt.* th*~ r*rli*r*n. (f I Cf 3 0*%

One aspect of the SFDP is he provision for cross train checks. The SFDP requires ross train checks to identify a loss of safety function for those support the performance of systems that support multiple and redundant safety systems re ire The cross train check verifies that the supported systems of the remaining OPERABLE support systems are OPERABLE, thereby ensuring safety function is retained. E]A loss of safety function may exist when a support system is inoperable, and:

0

a. A required system redundant to system(s) supported by the.

inoperable support system is also inoperable (EXAMPLE B 3 .0. 6 -1)m

b. A required system redundant to system(s) in turn supported by the 0

inoperable-supported system is also inoperable (EXAMPLE B 3.0.6-2)mor 0 c A.required system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3). 0 r-YArADI F- Q-A 0 l-Y - DI-.L_ I- ",,.".n..

C-1

-* I (Refer to FicgiureB3.0-1)

(Referto*iou 1) i

.10, an d 0 If System. 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in su rtedSystem 5 r'V,~ ,,trAnr- r 0 n t~ - tl*f*-r tn Fin,,r., R B 30-1t ]'

IMAJ-xVir-LIM D O.U.U-' F'-'--

If System 2 of Train.A is inoperable, and System 11 of Train B is inoperable, aloss of safety function exists in System 11 jwhiclisin turn jsupporte,ýystemn 5]

EXAMPLE B 3.0.6&3 (Referto Figure B3.0-1)

If System 2,of Train.A is inoperable, and System 1 of Train B is inoperable, a loss of safety function exists in Systems 2, 4, 5, 8,,9, 10 and L1.w 0 0

If this evaluation determines that a loss of safety function exists, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

BWOG STS B 3.0-9 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 44 of 63

Attachment 1, Volume 5, Rev. 1, Page 45 of 63 LCO APPLICABILITY B 3.0 BASES LCO 31A06 "(continued)

TRAINA TRAINB system 8 System 9 SySttm 4 S 4s System9 Systm 9 System 2 System 2 System10 System 12 System S Systse II System.1 system 2I System I System 12 0

System I Sypurm , System 12 System 13 System 3 Syste. 14 System 14 SystemI System 7

-System 19 System ¶0 TFigure B 3.0-1 0

Imove to end of Section Configuration of Trains and Systems This loss of safety function does not require the assumption of additional single failures or loss of offsite power. Since operations are being restricted in accordancewith the ACTIONS of the support system, any resulting temporary loss of redundancy or single failure protection is taken into account. Similarly, the ACTIONS for inoperable offsite circuit(s) and inoperable diesel.generator(s) provide the necessary restriction for cross train inoperabilities. This explicit cross train verification for inoperable AC electrical power sourcesalso acknowledges that supported system(s) are not declared inoperable solely as a result of inoperability of a normal or emergency electrical power source (refer to the definition of OPERABILITY).

BWOG STS B 3.0-10 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 45 of 63

Attachment 1, Volume 5, Rev. 1, Page 46 of 63 LCO APPLICABILITY B 3.0

BASES LCO 3.0.6 (continued)

When loss of safety function is determined to exist, and the SFDP requires entry into the apprdpriate Conditions and Required Actions of the LCO in which the loss of safety function exists., consideration must be given to the specific type of function affected. ýWhere a loss of function is solely due to a single Technical Specification support system (e.g., loss of automatic start due to .inoperable instrumentation, or loss of pump suction source due to low tank level) the appropriate LCO is the LCO for the support system. The ACTIONS for a support system LCO adequately address the inoperabilifles of thatsystem without reliance on entering its supported system LCO. When the loss of function is the result of multiple support systems, the appropriate LCO, is the LCO for the supported system.

LCO 3.0L7 There are certain special tests and operations required to. be performed at various tinies 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.843,1.99 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 LOOrepresents a condition not necessarly 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 TestException LCO .shall be followed.

LCO 3.0.8 LCO 3.0.8 establishes conditions under which:systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due t.oone or more snubbers not capable of performing theirassociated support function(s). This is appropriate because a limited length of time~is allowed for maintenance, testing, or repair of one or more. snubbers notcapable of performing their associated BWOG STS B 3.0-11 Rev. 3.1,. 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 46 of 63

Attachment 1, Volume 5, Rev. 1, Page 47 of 63 LCO APPLICABI.LITY B 3.0 BAS.ES LCO. 3.0.8 (continued) support function(s) and appropriate compensatory measures are specified in the snubber requirements,.which are located outside of the Technical Specifications (TS) under licensee control. 7The S u er requirements/o not meet the criteriax 10:CFR 50.36(c)(2 (ii), and, as Isuch, are aplpropriate for control by te licensee.

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

LCO 3.0.8.a applies when one ormoresnubbers are not.capable of providing their associated support function(s) to a single train or subsystem of a multiple train or subsystem: supported systemr 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 snubber(s) before d eclaring-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 eventconcurrent with an event that would require operation of the supported system occurring while the: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 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 snubber(s) before declaring the supported system inoperable. The 12 hour1.388889e-4 days 0.00333 hours 1.984127e-5 weeks 4.566e-6 months Completion Time is reasonable based on the low probability of a seismic event concurrent with an event that would require operation of the supported system occurring while .the 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..n anyunaffected train or Subsystem is properly controlled, and emergent issues: are properly addressed. The risk assessment need not be. quantified, but may be a qualitative awareness of the vulnerability of systems and components when one or more snubbers are not able to perform their associated support function.

[NER from]

page B 3.0-10 BWOG STS B 3.0-12 Rev. 3.1, 12101/05 Attachment 1, Volume 5, Rev. 1, Page 47 of 63

Attachment 1, Volume 5, Rev. 1, Page 48 of 63 SR Applicability B 3.0 B 3.0 SURVEILLANCE REQUIREMENT (SR) APPLICABILITY BASES SRs SR 3.0.1 through SR 3.0.4 establish the general requirements applicable.

to all Specifications.and applyat all times, unless otherwise statedý SR 3.0.1 SR 3.0.1 establishes the requirement that SRs must be met during the MODES or other specified conditions in the Applicability for which.the requirements of the LCO apply, unless otherwise specified in the individual SRs. This Specification is to ensure that 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 meet an.LCO. Surveillances may be performed by means of any series of sequential,. overlapping, or total steps provided the entire Surveillance is performed withinthe specified Frequency. Additionally, the definitions related to instrument testing (e.g., CHANNEL CALIBRATION) specify that these tests are performed .by means of any series of sequential, overlapping, .or total steps.

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 componrents are OPERABLE when:

a. The systems or components are known to be. inoperable, although still meeting the SRsor EZ O

(

b. The requirements of the Surveillance(s) are known to.be.nht 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 wta Test ExceptionL!E LCO are onlyapplicable when the I LCO 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 allowan e includes tho SRs whose perf rmance is normally precluded a given BMODE or o Ber specified *onR1ion.5 BWOG STS B 3.0-13 .Rev. 3.1, 12/01/05-Attachment 1, Volume 5, Rev. 1, Page 48 of 63

Attachment 1, Volume 5, Rev. 1, Page 49 of 63 SR Applicability B 3.0

BASES SR 3.0.1 (continued)

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.02,.prior to returning equipmentto OPERABLE status.

Upon completion ofmaintenance, 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 canbe completed.

Some examples of this process are:

j ýj Auxiliary feedwater (AFW) ](

a. I Emergen.-cTufeedcater EF pump turbine maintenance during.

refueling that requires testing at steam pressures > 800 psi.

However, if other appropriate testing is satisfactorily completed, the

[7 System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the Ststeam pressure required to perform the Etesting.~

b. High pressure i jection (HPI) main enance during sh tdown that requires syste functional tests a/a specified press re. Provided other appropri te testing is satisf 'torilycompleted,/startup can INSERT1 proceed with P1 considered OP RABLE. This all ws operation to K reach the sp cified pressure to c/bmplete the nece sary post maintenanc testing. /

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 notbe suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).

BWOG STS B 3.0-14 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 49 of 63

Attachment 1, Volume 5, Rev. 1, Page 50 of 63 B 3.0 0 INSERT 1 Main steam safety valve (MSSV) lift setpoint verification performed in-situ requires hot conditions. Provided other appropriate ANSI/ASME OM Code test requirements are satisfactorily completed, startup can proceed and MODE 3 entered with the MSSVs considered OPERABLE. This allows operation to reach the necessary conditions to perform the in-situ lift setpoint verification.

0 Insert Page B 3.0-14 Attachment 1, Volume 5, Rev. 1, Page 50 of 63

Attachment 1, Volume 5, Rev. 1, Page 51 of 63 SR Applicability B 3.0 BASES SR 3.0.2 (continued)

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 probableresult of any particular Surveillance being performed is, the verification of conformance with the SRs. The exceptions to SR 3.0.2 are those Surveillancesfor which the 25% extension of the interval specified in the Frequency does not apply.

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

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 "once per ..." basis. The 25% extension applies to each performance after the initial performance. The initial performance of the Required Action, whether it is a particular Surveillance or some.other remedial action, is considered a single action with a single Completion Time. One.

reason such anfor not allowing the 25% extension to this Completion Time is that action usually verifies that no.loss of function has occurred by checking the status of redundant or diverse components or accomplishes the function of the inoperable.equipment in analternative 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 fromthe 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.

BWOG STS B 3.0-15 Rev. 3.1, 12101105 Attachment 1, Volume 5, Rev. 1, Page 51 of 63

Attachment 1, Volume 5, Rev. 1, Page 52 of 63 SR Applicability B.3.0

BASES SR .3.0.3 (continued)

This delay period provides an 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 toperform 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 requirements of regulations (e.g., prior to entering MODE I after each fuel loading, or in accordance with 10 CFR 50, Appendix J, as modified by approved exemptions, etc.) is discovered to not have been performed when specified, SR 3.0.3 allows for the full delay period of up to the specified Frequency to perform the Surveillance. However, since there is not a time interval specified, the missed Surveillance should be performed at the first reasonable opportunity.

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

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, N C Regulatory Guide 1.1 82, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."

This Regulatory Guide addresses consideration of temporary and BWOGSTS B 3.0-16 Rev. 3.1, 12101/05 Attachment 1, Volume 5, Rev. 1, Page 52 of 63

Attachment 1, Volume 5, Rev. 1, Page 53 of 63 SR Applicability B 3.0

BASES SR 3.0.3 (continued) aggregate risk impacts, determination of risk management action thresholds, and risk management action up.to and including plant shutdown. The missed Surveillance should be treated as an emergent condition as.discussed in the Regulatory Guide. The risk evaluation may use quantitative; qualitative, or blended methods. The degree of depth

.and rigor of'the evaluation should be commensurate with the importance of thecomponent. Missed Surveillances for important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's.Corrective Action Program.

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

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

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

This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit. The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability.

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

BWOG STS B 3.0-17 Rev. 3.1, 12101/05 Attachment 1, Volume 5, Rev. 1, Page 53 of 63

Attachment 1, Volume 5, Rev. 1, Page 54 of 63 SR Applicability B 3.0

BASES SR 3.0.4 (continued)

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

When a. system, subsystem, division, component, device, or variable is inoperable or outside its'specified limits,. the associated SR(s) are not required to be performed, per SR 3.0.1, which states that/urveillances do not have to be performed on inoperable equipment. When equipment is.

inoperable, SR. 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance(s) Within the specified Frequency does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LCO is not met in this instance, LCO 3.0.4 will govern any restrictions that may (or may not) apply to MODE or:other specified.condition changes. SR 3.0.4 does not restrict changing MODES or other specified conditions of the Applicability when a Surveillance, has' not been performed within the specified Frequency, provided lheretquirement to declare the LCO not met has been delayed in, accordance with SR 3.0.3:

The provisions of SR 3.0.4 shall not prevent entry into MODES or other specified conditions in the.Applicability that are required to comply with f tAOT!ONS..S In addition, the provisions of SR3.0.4 shall not prevent MODES or other specified conditions in the. Applicability that result from.any unit shutdown.. In this context, a unit shutdown is defined S

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 hot 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 hasbeen reached. Further discussion of the specific formats of SRs' annotation is found in Section 1A4, Frequency.*--. ,

BEO BWOG STS B 3.0-18 Rev. 3.1, 12/01/05 Attachment 1, Volume 5, Rev. 1, Page 54 of 63

Attachment 1, Volume 5, Rev. 1, Page 55 of 63 JUSTIFICATION FOR DEVIATIONS ITS SECTION 3.0 BASES, LCO AND SR APPLICABILITY

1. Not used.

2. These punctuation corrections have been made consistent with the Writer's Guide for the Improved Standard Technical Specifications, TSTF-GG-05-01, Section 5.1.3.

3. Typographical/grammatical error corrected.

4. The brackets have been removed and the proper plant specific information/value has been provided.

5. The example added to the Bases of LCO 3.0.5 is made to be consistent with the standard for other types of reactors (i.e., NUREG-1433 Rev. 3.1 for the General Electric Boiling Water Reactors).

6. The Figure has been moved to the end of the Section, consistent with the format of the ITS.

7. These changes are made to be consistent with LCO 3.0.7.

8. The ITS SR 3.0.1 Bases allows credit to be taken for unplanned events that satisfy Surveillances. The Bases further states that this allowance also includes those SRs whose performance is normally precluded in a given MODE or other specified condition. This portion of the allowance has been deleted. As documented in Part 9900 of the NRC Inspection Manual, Technical Guidance - Licensee Technical Specifications Interpretations, and in the Bases Control Program (ITS 5.5.13),

neither the Technical Specifications Bases nor Licensee generated interpretations can be used to change the Technical Specification requirements. Thus, if the Technical Specifications preclude performance of an SR in certain MODES (as is the case for some SRs in ITS Section 3.8), the Bases cannot change the Technical Specifications requirement and allow the SR to be credited for being performed in the restricted MODES, even if the performance is unplanned.

9. Changes have been made for consistency with similar discussions/terminology in the Bases.

10. These changes are made to be consistent with changes made to LCO 3.0.4.

11. The plant specific terminology has been incorporated. Furthermore, a new plant specific example has been provided since the example in part b is not applicable for Davis-Besse.

12. Changes made for enhanced clarity.

13. This statement has been deleted since the Davis-Besse ITS submittal does not state the snubbers do not meet the 10CFR50.36(c)(2)(ii) criteria. This is also consistent with the NRC SERs for DC Cook Units 1 and 2 and Monticello ITS amendments.

14. Changes made to be consistent with chages made to ITS 3.7.14.

15. The correct LCO number has been provided.

Davis-Besse Page 1 of 2 Attachment 1, Volume 5, Rev. 1, Page 55 of 63

Attachment 1, Volume 5, Rev. 1, Page 56 of 63 JUSTIFICATION FOR DEVIATIONS ITS SECTION 3.0 BASES, LCO AND SR APPLICABILITY

16. The following fixes to incorrect statements for the examples in the LCO 3.0.6 Bases have been made. Specifically:

1) Example B 3.0.6-1 is changed from "if System 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in supported System 5" to "IfSystem 2 of Train A is inoperable and System 5 of Train B is inoperable, a loss of safety function exists in Systems 5, 10, and 11." Examining Figure B 3.0-1, it is clear that if there is a loss of safety function in System 5, there is also a loss of safety function in the systems supported by System 5, i.e., Systems 10 and 11. This relationship is explicitly listed in Example B 3.0.6-3 and to not do so here is inconsistent and confusing as it leads the reader to believe that Systems 10 and 11 do not have a loss of safety function. Furthermore, System 5 of Train B is not a supported System of System 2 of Train A, since they are in different trains.

Thus, the word "supported" has been deleted.

2) Example B 3.0.6-2 is changed from "IfSystem 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11 which is in turn supported by System 5" to "if System 2 of Train A is inoperable, and System 11 of Train B is inoperable, a loss of safety function exists in System 11."

The phrase "which in turn is supported by System 5" is confusing. System 5 is not inoperable and does not lead to the loss of safety function. Examples B 3.0.6-1 and B 3.0.6-3 do not discuss OPERABLE support systems. This phrase adds no, value and leads the reader to believe there is some special relationship with System 5 which does not exist.

Davis-Besse needs to make these changes since the current wording in the ISTS 3.0.6 Bases are not correct. Furthermore, these changes are consistent with industry approved TSTF-494T.

Davis-Besse Page 2 of 2 Attachment 1, Volume 5, Rev. 1, Page 56 of 63

Attachment 1, Volume 5, Rev. 1, Page 57 of 63 Specific No Significant Hazards Considerations (NSHCs)

Attachment 1, Volume 5, Rev. 1, Page 57 of 63

Attachment 1, Volume 5, Rev. 1, Page 58 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY 10 CFR 50.92 EVALUATION FOR LESS RESTRICTIVE CHANGE L01 Davis-Besse is converting to the Improved Technical Specifications (ITS) as outlined in NUREG-1430, Rev. 3.1, "Standard Technical Specifications, Babcock and Wilcox Plants." The proposed change involves making the Current Technical Specifications (CTS) less restrictive. Below is the description of this less restrictive change and the determination of No Significant Hazards Considerations for conversion to NUREG-1430.

CTS 3.0.4 states, "entry into an OPERATIONAL MODE or other specified applicability conditions shall not be made unless the conditions of the Limiting Condition for Operation are met without reliance on provisions contained in the ACTION statements unless otherwise excepted. CTS 4.0.4 states, "Entry into an OPERATIONAL MODE or other specified applicability condition shall not be made unless the Surveillance Requirements(s) associated with the Limiting Condition for Operation have been performed with the stated surveillance interval or as otherwise specified. ITS LCO 3.0.4 states "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; 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 Specification 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." ITS SR 3.0.4 states, "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 changes the CTS by providing allowances for entry into a MODE or other specified condition in the Applicability when an LCO is not met.

The purpose of LCO 3.0.4 is to provide guidance when an LCO is not met and entry into a MODE or other specified condition in the Applicability is desired. The change is acceptable because LCO 3.0.4 provides the appropriate guidance to enter the Applicability when an LCO is not met. 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 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. LCO 3.0.4.b Davis-Besse Page 1 of 6 Attachment 1, Volume 5, Rev. 1, Page 58 of 63

Attachment 1, Volume 5, Rev. 1, Page 59 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY 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 risk impacts of maintenance activities to be assessed and managed. The risk assessment, for the purposes of LCO 3.0.4.b, must take into account all inoperable Technical Specification equipment regardless of whether the equipment is included in the normal 10 CFR 50.65(a)(4) risk assessment scope. The risk assessments will be conducted using the procedures and guidance endorsed by Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants."

Regulatory Guide 1.182 endorses the guidance in Section 11 of NUMARC 93-01, "Industry Guideline for Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." These documents address general guidance for conduct of the risk assessment, quantitative and qualitative guidelines for establishing risk management actions, and example risk management actions. These include actions to plan and conduct other activities in a manner that controls overall risk, increased risk awareness by shift and management personnel, actions to reduce the duration of the condition, actions to minimize the magnitude of risk increases (establishment of backup success paths or compensatory measures), and 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.

NUMARC 93-01 provides guidance relative to consideration of simultaneous unavailability of multiple systems and components. The results of the risk assessment shall be considered in determining the acceptability of entering the MODE or other specified condition in the Applicability, and any corresponding risk management actions.

The 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 systems and components contain Notes prohibiting the use of LCO 3.0.4.b by stating that LCO 3.0.4.b is not applicable. These systems and components are the ECCS Low Pressure Injection Subsystem, the Auxiliary Feedwater System and Motor Driven Feedwater Pump train, and the emergency diesel generators (ITS 3.5.3, ITS 3.7.5, and ITS 3.8.1, respectively).

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, Davis-Besse Page 2 of 6 Attachment 1, Volume 5, Rev. 1, Page 59 of 63

Attachment 1, Volume 5, Rev. 1, Page 60 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SIR APPLICABILITY LCO 3.0.4.c is typically applied to Specifications that describe values and parameters.

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 condition in the Applicability associated with transitioning from MODE 1 to MODE 2, MODE 2 to MODE 3, and MODE 3 to MODE 4. 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 Specifications. Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SIR 3.0.1.

Therefore, utilizing LCO 3.0.4 is not a violation of SR 3.0.1 or SR 3.0.4 for 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. This change is designated as less restrictive because entry into MODES or other specified conditions in the Applicability of a Specification might be made with an LCO not met as long as the plant is in compliance with LCO 3.0.4.

An evaluation has been performed to determine whether or not a significant hazards consideration is involved with these proposed Technical Specification changes by focusing on the three standards set forth in 10 CFR 50.92, "Issuance of amendment," as discussed below:

1. Does the proposed change involve a significant increase in the probability or consequences of an accident previously evaluated?

Response: No.

The proposed change allows entry into a MODE or other specified condition in the applicability of a Technical Specification (TS), while in a TS condition statement and the associated required actions of the TS. Being in a TS condition and the associated required actions is not an initiator of any accident previously evaluated. Therefore, the probability of an accident previously evaluated is not significantly increased. The consequences of an accident while relying on the required actions as allowed by proposed LCO 3.0.4, are no different than the consequences of an accident while entering and relying on the required actions while starting in a condition of applicability of the TS. Therefore, the consequences of an accident previously evaluated are not significantly affected by this change. The addition of a requirement to assess and manage the risk introduced by this change will further minimize possible concerns. Therefore, this change does not involve a significant increase in the probability or consequences of an accident previously evaluated.

.2. Does the proposed change create the possibility of a new or different kind of accident from any accident previously evaluated?

Response: No.

Davis-Besse Page 3 of 6 Attachment 1, Volume 5, Rev. 1, Page 60 of 63

Attachment 1, Volume 5, Rev. 1, Page 61 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY The proposed change does not involve a physical alteration of the plant (no new or different type of equipment will be installed). Entering into a MODE or other specified condition in the applicability of a TS, while in a TS condition statement and the associated required actions of the TS, will not introduce new failure modes or effects and will not, in the absence of other unrelated failures, lead to an accident whose consequences exceed the consequences of accidents previously evaluated. The addition of a requirement to assess and manage the risk introduced by this change will further minimize possible concerns. Thus, this change does not create the possibility of a new or different kind of accident previously evaluated.

3. Does the proposed change involve a significant reduction in a margin of safety?

Response: No.

The proposed change allows entry into a MODE or other specified condition in the applicability of a TS condition statement and the associated required actions of the TS. The TS allow operation of the plant without the full complement of equipment through the conditions for not meeting the TS LCO. The risk associated with this allowance is managed by the imposition of required actions that must be performed within the prescribed completion times. The net effect of being in a TS condition on the margin of safety is not considered significant. The proposed change does not alter the required actions or completion times of the TS. The proposed change allows TS conditions to be entered, and the associated required actions and completion times to be used in new circumstances. In most cases, this use is predicated upon the performance of a risk assessment and the management of plant risk. The change also eliminates current allowances for utilizing required actions and completion times in similar circumstances, without assessing and managing risk. The net change to the margin of safety is insignificant. Therefore, this change does not involve a significant reduction in a margin of safety.

Based on the above, it is concluded that the proposed change presents no significant hazards consideration under the standards set forth in 10 CFR 50.92(c), and, accordingly, there is a finding of "no significant hazards consideration."

Davis-Besse Page 4 of 6 Attachment 1, Volume 5, Rev. 1, Page 61 of 63

Attachment 1, Volume 5, Rev. 1, Page 62 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY 10 CFR 50.92 EVALUATION I FOR LESS RESTRICTIVE CHANGE L02 Davis-Besse is converting to the Improved Technical Specifications (ITS) as outlined in NUREG-1430, Rev. 3.1, "Standard Technical Specifications, Babcock and Wilcox Plants." The proposed change involves making the Current Technical Specifications (CTS) less restrictive. Below is the description of this less restrictive change and the determination of No Significant Hazards Considerations for conversion to NUREG-1430.

CTS 4.0.2 states "Each Surveillance Requirement shall be performed within the specified time interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval." ITS SR 3.0.2 states "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." This changes the CTS by adding, "If a Completion Time requires periodic performance on a 'once per.. .' basis, the above Frequency extension applies to each performance after the initial performance." The remaining changes to CTS 4.0.2 are discussed in DOC A10 and DOC M01.

This change is acceptable because the 25 percent Frequency extension given to provide scheduling flexibility for Surveillances is equally applicable to Required Actions which must be performed periodically. The initial performance is excluded because the first performance demonstrates the acceptability of the current condition. Such demonstrations should be accomplished within the specified Completion Time without extension in order to avoid operation in unacceptable conditions. This change is designated as less restrictive because additional time is provided to perform some periodic Required Actions.

An evaluation has been performed to determine whether or not a significant hazards consideration is involved with these proposed Technical Specification changes by focusing on the three standards set forth in 10 CFR 50.92, "Issuance of amendment," as discussed below:

1. Does the proposed change involve a significant increase in the probability or consequences of an accident previously evaluated?

Response: No.

The proposed change allows the Completion Time for periodic actions to be extended by 25 percent. This change does not significantly affect the probability of an accident. The length of time between performance of Required Actions is not an initiator to any accident previously evaluated. The consequences of any accident previously evaluated are the same during the Completion Time or during any extension of the Completion Time. As a result, the consequences of any accident previously evaluated are not significantly increased. Therefore, the Davis-Besse Page 5 of 6 Attachment 1, Volume 5, Rev. 1, Page 62 of 63

Attachment 1, Volume 5, Rev. 1, Page 63 of 63 DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS SECTION 3.0, LCO AND SR APPLICABILITY proposed change does not involve a significant increase in the probability or consequences of an accident previously evaluated.

2. Does the proposed change create the possibility of a new or different kind of accident from any accident previously evaluated?

Response: No.

The proposed change allows the Completion Time for periodic actions to be extended by 25 percent. This change will not physically alter the plant (no new or different type of equipment will be installed). Also, the change does not involve any new or revised operator actions. Therefore, the proposed change does not create the possibility of a new or different kind of accident from any previously evaluated.

3. Does the proposed change involve a significant reduction in a margin of safety?

Response: No.

The proposed change allows the Completion Time for periodic actions to be extended by 25 percent. The 25 percent extension allowance is provided for scheduling convenience and is not expected to have a significant effect on the average time between Required Actions. As a result, the Required Actions will continue to provide appropriate compensatory measures for the subject Condition. Therefore, the proposed change does not involve a significant reduction in a margin of safety.

Based on the above, it is concluded that the proposed change presents no significant hazards consideration under the standards set forth in 10 CFR 50.92(c), and, accordingly, there is a finding of "no significant hazards consideration."

Davis-Besse Page 6 of 6 Attachment 1, Volume 5, Rev. 1, Page 63 of 63

v t e Letter Sequence Request
TAC:MD6398, Increase Flexibility in Mode Restraints, Addition of LCO 3.0.8, Inoperability of Snubbers, Deletion of E BAR Definition and Revision to RCS Specific Activity Tech Spec, Changes to Reflect Revision of 10 CFR 50.55A, Limit Inservice Testing Program SR 3.0.2 Application to Frequencies of 2 Years or Less, Eliminate Second Completion Times Limiting Time from Discovery of Failure to Meet an LCO, Correct Example 1.4-1, Containment Structural Integrity, TSTF-28, Correct LCO 3.0.6 Bases, Add Restriction for Lowest LOOP Tave During Mode 2 Physics Testing (Approved, Closed) TAC:MD6319, DC Electrical Rewrite - Update to TSTF-360, Eliminate Use of Term Core Alterations in Actions and Notes, Provide Actions for One Steam Supply to Turbine Driven Afw/Efw Pump Inoperable, DC Electrical Rewrite, Clarification of Required Features in 3.8.1 Actions (Approved, Closed)
Initiation Request, Request, Request, Request, Request, Request, Request Acceptance, Acceptance, Acceptance, Acceptance Supplement, Supplement Administration Meeting, Meeting, Meeting Questions 18 June 2008 20 June 2008 Answers 23 July 2008 3 September 2008 Results Approval Other: L-08-161, Copy of Applicable Portions of the NRC and Davis-Besse Improved Technical Specifications Conversion Website - Sections 3.0, 3.1, 3.2, 3.4, and 3.6 and Chapter 4.0, L-08-241, Attachment 1, Applicable Portions of the U.S. Nuclear Regulatory Commission (NRC) and Davis-Besse Nuclear Power Station (DBNPS) Improved. Technical Specification (ITS) Conversion Website, Section 3.5 RAIs, L-08-338, Copy of Improved Technical Specifications (ITS), L-08-378, Implementation of Improved Technical Specification Amendment No. 279, ML073531253, ML081350505, ML082000451, ML082270661, ML082270662, ML082270663, ML082270664, ML082270665, ML082270666, ML082270667, ML082270669, ML082270670, ML082600577, ML082840099, ML082900630, ML082900882, ML082910125
MONTHYEAR2008-02-04 [Table View]

ML081480465

Text

Navigation menu

Search