Text

Enclosure 2: Hope Creek Generating Station Improved Technical Specifications Conversion - Volume 5
	ML24142A433
Person / Time
Site:	Hope Creek
Issue date:	05/20/2024
From:	; Public Service Enterprise Group
To:	; Office of Nuclear Reactor Regulation
Shared Package
ML24142A428	List: ML24142A407; ML24142A429; ML24142A430; ML24142A431; ML24142A432; ML24142A433; ML24142A434; ML24142A435; ML24142A436; ML24142A437; ML24142A438; ML24142A439; ML24142A440; ML24142A441; ML24142A442; ML24142A443; ML24142A444; ML24142A445; ML24142A446;
References
	LR-N24-0029, LAR H24-02
	Download: ML24142A433 (1)
	v • d • e

ENCLOSURE 2 VOLUME 5 HOPE CREEK GENERATING STATION IMPROVED TECHNICAL SPECIFICATIONS CONVERSION ITS SECTION 3.0 LCO AND SR APPLICABILITY Revision 0

LIST OF ATTACHMENTS

1.

ITS Section 3.0, LCO and SR Applicability

ATTACHMENT 1 ITS Section 3.0, LCO AND SR APPLICABILITY

Current Technical Specifications (CTS) Markup and Discussion of Changes (DOCs)

SECTIONS 3.0 and 4.0 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS A01 ITS 3.0

ITS 3.0 ITS A01 3 /4.0 APPLICABILITY LIMITING CONDITION FOR OPERATION 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding Specifications is required during the OPERATIONAL CONDITIONS or other conditions specified therein; except that upon failure to meet the Limiting Conditions for Operation, the associated ACTION requirements shall be met, and except as provided in LCO 3.0.8, and LCO 3.0.9.

3.0.2 Noncompliance with a Specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals. If the Limiting Condition for Operation is restored prior to expiration of the specified time intervals, completion of the Action requirements is not required.

3.0.3 When a Limiting Condition for Operation is not met, except as provided in the associated ACTION requirements, within one hour action shall be initiated to place the unit in an OPERATIONAL CONDITION in which the Specification does not apply by placing it, as applicable, in:

1.

At least STARTUP 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 .

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. Exceptions to these requirements are stated in the individual Specifications.

This Specification is not applicable in OPERATIONAL CONDITIONS 4 or 5.

3.0.4 When an LCO is not met, entry into an OPERATIONAL CONDITION or other specified condition in the Applicability shall only be made:

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

After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the OPERATIONAL CONDITION 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 OPERATIONAL CONDITIONS or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

HOPE CREEK 3/4 0-1 Amendment No.228 (LCO)

LCO 3.0.1 LCO 3.0.2 LCO 3.0.3 LCO 3.0.4 LCO 3.0.2 Required Actions of the associated Conditions LCOs shall be met MODES in the Applicability, LCO 3.0.2, LCO 3.0.7, met or is no longer applicable Completion Time(s)

Required Action(s)

, unless otherwise stated an and the associated ACTIONS are not met an is not provided, or if directed by the associated ACTIONS MODE or other specified condition MODE 2 MODE 3 MODE 4 7

13 37 LCO is not applicable this Specification LCO 3.0.3 is only applicable in MODES 1, 2, and 3.

MODE MODE MODE discovery of a except as provided in LCO 3.0.5 and LCO 3.0.6.

n in accordance with the LCO or S

completion of the actions required by LCO 3.0.3 is not required MODE A05 A02 A02 A06 A07 A03 A04 Compliance with the Limiting Conditions for Operation contained in the succeeding or other conditions specified A02 A02 A02

ITS 3.0 ITS A01 APPLICABILITY LIMITING CONDITION FOR OPERATION (Continued) 3.0.5 Equipment removed from service or declared inoperable to comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY or the OPERABILITY of other equipment. This is an exception to LCO 3.0.2 for the system returned to service under administrative control to perform the testing required to demonstrate OPERABILITY.

3.0.6 Not used.

3.0.7 Not used.

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

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

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

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

LCO 3.0.9 When one or more required barriers are unable to perform their related support function(s), any supported system LCO(s) are not required to be declared not met solely for this reason for up to 30 days provided that at least one train or subsystem of the supported system is OPERABLE and supported by barriers capable of providing their related support function(s),

and risk is assessed and managed. This specification may be concurrently applied to more than one train or subsystem of a multiple train or subsystem supported system provided at least one train or subsystem of the supported system is OPERABLE and the barriers supporting each of these trains or subsystems provide their related support function(s) for different categories of initiating events.

For the purposes of this specification, the High Pressure Coolant Injection system, the Reactor Core Isolation Cooling system, and the Automatic Depressurization System are considered independent subsystems of a single system.

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

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

HOPE CREEK 3/4 0-2 Amendment No.228 LCO 3.0.5 LCO 3.0.6 LCO 3.0.8 LCO 3.0.7 INSERT 1 INSERT 2 LCO 3.0.9 LCO S

S A06 A07

Insert Page 3/4 0-2 ITS 3.0 INSERT 1 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.9, "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 2 LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.

A06 A07

ITS 3.0 ITS A01 APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the OPERATIONAL CONDITIONS or other specified conditions in the Applicability for individual Limiting Conditions for Operation, unless otherwise stated in the Surveillance Requirement. 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 Limiting Condition for Operation.

Failure to perform a Surveillance within the specified frequency shall be a failure to meet the Limiting Condition for Operation, except as provided in Specification 4.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.

4.0.2 Each Surveillance Requirement shall be performed within its specified surveillance interval with a maximum allowable extension not to exceed 25 percent of the specified surveillance interval.

4.0.3 If it is discovered that a Surveillance was not performed within its specified frequency, then compliance with the requirement to declare the Limiting Condition for Operation 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. The delay period is only applicable when there is a reasonable expectation the Surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the Limiting Condition for Operation must immediately be declared not met and the applicable Actions must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the Limiting Condition for Operation must immediately be declared not met and the applicable Actions must be entered.

4.0.4 Entry into an OPERATIONAL CONDITION 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 4.0.3. When an LCO is not met due to Surveillances not having been met, entry into an OPERATIONAL CONDITION or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.

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

HOPE CREEK 3/4 0-3 Amendment No. 214 SR 3.0.1 SR 3.0.2 SR 3.0.3 SR 3.0.4 (SR)

MODES s

F 3

The specified Frequency for e 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.

INSERT 3 Condition(s)

MODE 3

MODE MODES Condition(s)

F F

A08 M01 R

L01 3

3 3

3

Insert Page 3/4 0-3 ITS 3.0 INSERT 3 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.

L01 M01 A08

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 1 of 6 ADMINISTRATIVE CHANGES A01 In the conversion of the Hope Creek Generating Station (HCGS) 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-1433, Rev. 5.0, "Standard Technical Specifications - General Electric BWR/4 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 phrase, Compliance with the Limiting Conditions for Operation contained in the succeeding Specifications is required is replaced with the phrase, "LCOs shall be met..." This convention and the phrase that a Limiting Condition for Operation (LCO) is met or not met, is applied consistently throughout the ISTS. CTS 3.0.1 and CTS 3.0.4 defined term OPERATIONAL CONDITION is changed to MODE and other conditions specified therein is changed to specified conditions in the Applicability. This terminology is consistent with the ITS definition of MODE and the terminology is applied consistently throughout the ISTS. The CTS phrase, except as provided in LCO 3.0.8 and LCO 3.0.9 is changed to, except as provided in LCO 3.0.2, LCO 3.0.7, LCO 3.0.8, and LCO 3.0.9. ITS LCO 3.0.2 addresses the requirement for meeting the associated Actions if an LCO is not met. LCO 3.0.7 addresses Special Operations LCOs, which are exceptions to other LCOs and is discussed in the Discussion of Changes (DOC) for ITS LCO 3.0.7 (DOC A07). The ITS requirements remain unchanged from the CTS, although the ITS uses a combination of ITS LCO 3.0.1 and LCO 3.0.2.

This change is acceptable because adding the exception for LCO 3.0.7 prevents a conflict within the Applicability section and the change results in no change in the intent or application of the Technical Specifications, but merely reflects editorial preferences used in the ISTS.

A03 The CTS 3.0.2 sentence Noncompliance with a Specification shall exist when the requirements of the Limiting Condition for Operation and associated ACTION requirements are not met within the specified time intervals is removed.

Elimination of the definition of noncompliance is administrative in that neither the CTS nor ITS make use of the term. The exception to LCO 3.0.5 is already addressed in CTS 3.0.5 and the inclusion of LCO 3.0.2 is administrative. The exception to LCO 3.0.6 is addressed in the DOC for ITS LCO 3.0.6 (DOC A06).

The CTS phrase restored is changed to met or is no longer applicable; time intervals is changed to Completion Time(s); and Action requirements is changed to Required Action(s), to be consistent with the ISTS. The term unless otherwise stated is added because some ITS LCOs explicitly state an exception to ITS 3.0.2 and these exceptions avoid potential misapplication of those requirements.

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 2 of 6 These changes are acceptable because they result in no change in the intent or application of the Technical Specifications, but merely reflect editorial preferences used in the ITS.

A04 The CTS 3.0.3 phrase, except as provided in the associated ACTION requirements is replaced with and the associated Actions are not met, an associated Action is not provided, or if directed by the associated Actions to cover all potential possibilities that require entry into LCO 3.0.3. Operational Condition is changed to MODE or other specified condition to be consistent with ISTS and this change is applied consistently throughout the ITS.

CTS 3.0.3, in part, states that within one hour action shall be initiated to place the unit in an OPERATIONAL CONDITION in which the Specification does not apply by placing it, as applicable, in: at least STARTUP within the next 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , at least HOT SHUTDOWN within the following 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months , and at least COLD SHUTDOWN within the subsequent 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months . ITS LCO 3.0.3 states that action shall be initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to place the unit, as applicable, in MODE 2 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months , MODE 3 within 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months , and MODE 4 within 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months . This changes the CTS by using the sum of the times (i.e., the ITS Completion Time of 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months to enter MODE 4 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 ) instead of sequential times (i.e., each time is measured from the completion of the previous step). The stated times in CTS 3.0.3 and ITS 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 2

Hot Standby within the next 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months 7 hours 3

Hot Shutdown within the following 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months 13 hours 4

Cold Shutdown within the subsequent 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months 37 hours The purpose of CTS 3.0.3 is to establish the shutdown requirements that must be implemented when an LCO is not met and the condition is not specifically addressed in the associated ACTION requirements. The delineated time limit allows the unit to be placed in a safe shutdown MODE when the plant cannot be maintained within the limits for safe operation. The time limit, specified in CTS 3.0.3 to reach the lower MODES of operation, permits the shutdown to proceed in a controlled manner that is well within the specified maximum cooldown rate.

Furthermore, the time limit is within the cooldown capabilities of the plant assuming only the minimum required equipment is OPERABLE. In the CTS, this is accomplished by allowing a total of 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months for the plant to be in MODE 4 when a shutdown is required during the MODE of Operation. In the ITS, the time limits for ITS 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 4 when a shutdown is required during MODE 1 operation. If the unit is in a lower mode of operation when an ITS LCO 3.0.3 shutdown is required, the time limit for

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 3 of 6 reaching the next lower MODE applies (i.e., if the plant is in MODE 2, 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months is allowed to reach MODE 3). ITS 3.0 Bases gives a detailed discussion on the use of applying the allowed outage times when the unit is in a lower MODE when ITS LCO 3.0.3 is entered. This is further explained, with examples, in the discussion of Section 1.3, "Completion Times." This change is acceptable because ITS and CTS both allow 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months to reach MODE 4 from power operation.

These changes are considered changes to the CTS presentation and are designated as administrative as they apply rules of usage established by ITS without resulting in technical changes to the Technical Specifications.

A05 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 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, and 3."

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, CTS 3.0.3 states This specification is not applicable in MODES 4 or

5. ITS LCO 3.0.3 states LCO 3.0.3 is only applicable in MODES 1, 2, and 3.

CTS 3.0.3 and ITS LCO 3.0.3 require the unit to be placed only as low as COLD SHUTDOWN (MODE 4). Once the unit is in MODE 4, there are no further requirements. Thus, CTS 3.0.3 and ITS LCO 3.0.3 are effectively only applicable in MODES 1, 2, and 3, 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.

A06 ITS LCO 3.0.6 is added to the CTS. ITS LCO 3.0.6 provides guidance regarding appropriate Actions to be taken when a support system inoperability also results in the inoperability of one or more related supported systems. ITS includes LCO 3.0.6 and a Safety Function Determination Program (Specification 5.5.9) to resolve the application of LCOs to support and supported systems. Since the function of ITS LCO 3.0.6 is to clarify existing ambiguities and to maintain consistency with previous interpretations, this new provision is considered an administrative change with no impact on safety.

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 4 of 6 A07 ITS LCO 3.0.7 is added to the CTS. ITS LCO 3.0.7 states "Special Operations LCOs is Section 3.10 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 Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications."

This change is acceptable because the CTS contain test exception specifications in CTS Section 3/4.10 that allow certain LCOs to not be met for the purpose of special 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 operations. LCO 3.0.7 was crafted to avoid possible confusion. LCO 3.0.7 is consistent with the use and application of CTS Special Operations 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.

A08 CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified surveillance interval with a maximum allowable extension not to exceed 25% 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 change is made to be consistent with the ITS terminology and to clarify the concept of the specified SR Frequency being met. The change results in multiple changes to the CTS.

ITS SR 3.0.2 is more specific regarding the state 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 Technical Specifications.

This change is acceptable because the ITS intent is the same 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.

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 5 of 6 ITS SR 3.0.2 adds to the CTS "For Frequencies specified as "once," the above interval extension does not apply." This change 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 change is covered by DOC L01.

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

MORE RESTRICTIVE CHANGES M01 CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified surveillance interval with a maximum allowable extension not to exceed 25% 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 DOCs A08 and L01.

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 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 for some Surveillances.

RELOCATED SPECIFICATIONS None REMOVED DETAIL CHANGES None

DISCUSSION OF CHANGES ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 6 of 6 LESS RESTRICTIVE CHANGES L01 (Category 7 - Relaxation of Surveillance Frequency) CTS 4.0.2 states, "Each Surveillance Requirement shall be performed within the specified surveillance interval with a maximum allowable extension not to exceed 25% 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 DOCs A08 and M01.

This change is acceptable because the 25% 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 with 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.

Improved Standard Technical Specifications (ISTS) Markup and Justification for Deviations (JFDs)

LCO Applicability 3.0 General Electric BWR/4 STS 3.0-1 Rev. 5.0 CTS Hope Creek Amendment XXX 1

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

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

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

a.

MODE 2 within [7] hours,

b.

MODE 3 within 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months , and

c.

MODE 4 within 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months .

Exceptions to this Specification are stated in the individual Specifications.

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

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

REVIEWER'S NOTE-----------------------------------

The brackets around the time provided to reach MODE 2 allow a plant to extend the time from 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months to a plant specific time. Before the time can be changed, plant specific data must be provided to support the extended time.

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; 3.0.1 3.0.2 3.0.3 3.0.4 2

3

LCO Applicability 3.0 General Electric BWR/4 STS 3.0-2 Rev. 5.0 CTS Hope Creek Amendment XXX 1

LCO Applicability LCO 3.0.4 (continued)

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.

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

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

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

LCO 3.0.7 Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met.

When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.

3.0.5 DOC A06 DOC A07 3.0.4 9

1

LCO Applicability 3.0 General Electric BWR/4 STS 3.0-3 Rev. 5.0 CTS Hope Creek Amendment XXX 1

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

a.

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

b.

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

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

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

[ For the purposes of this specification, the [High Pressure Coolant Injection/High Pressure Core Spray] System, the [Reactor Core Isolation Cooling] System, and the [Automatic Depressurization System] are considered independent subsystems of a single system. ]

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

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

3.0.8 3.0.9 2

SR Applicability 3.0 General Electric BWR/4 STS 3.0-4 Rev. 5.0 CTS Hope Creek Amendment XXX 1

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

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the Surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months and the risk impact shall be managed.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the applicable Condition(s) must be entered.

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.

4.0.1 4.0.2 4.0.3 4.0.4 DOC L01 DOC M01

SR Applicability 3.0 General Electric BWR/4 STS 3.0-5 Rev. 5.0 CTS Hope Creek Amendment XXX 1

SR Applicability SR 3.0.4 (continued)

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

4.0.4

JUSTIFICATION FOR DEVIATIONS ITS 3.0, LCO AND SR APPLICABILITY Hope Creek Page 1 of 1

1. Changes are made (additions, deletions, and/or changes) to the ISTS which reflect the plant specific nomenclature, number, reference, system description, analysis, or licensing basis description.

2. The ISTS contains bracketed information and/or values that are generic to all General Electric BWR/4 vintage plants. The brackets are removed and the proper plant specific information/value is changed to reflect the current licensing basis.

3. The Reviewers Note has been deleted. This information is for the NRC reviewer to be keyed into what is needed to meet this requirement. This Note is not meant to be retained in the final version of the plant specific submittal.

Improved Standard Technical Specifications (ISTS) Bases Markup and Bases Justification for Deviations (JFDs)

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-1 Rev. 5.0 Hope Creek Revision XXX 1

B 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY BASES LCOs LCO 3.0.1 through LCO 3.0.9 establish the general requirements applicable to all Specifications and apply at all times, unless otherwise stated.

LCO 3.0.1 LCO 3.0.1 establishes the Applicability statement within each individual Specification as the requirement for when the LCO is required to be met (i.e., when the unit is in the MODES or other specified conditions of the Applicability statement of each Specification).

LCO 3.0.2 LCO 3.0.2 establishes that upon discovery of a failure to meet an LCO, the associated ACTIONS shall be met. The Completion Time of each Required Action for an ACTIONS Condition is applicable from the point in time that an ACTIONS Condition is entered, unless otherwise specified.

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

a.

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

b.

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

There are two basic types of Required Actions. The first type of Required Action specifies a time limit in which the LCO must be met. This time limit is the Completion Time to restore an inoperable system or component to OPERABLE status or to restore variables to within specified limits. If this type of Required Action is not completed within the specified Completion Time, a shutdown may be required to place the unit in a MODE or condition in which the Specification is not applicable. (Whether stated as a Required Action or not, correction of the entered Condition is an action that may always be considered upon entering ACTIONS.) The second type of Required Action specifies the remedial measures that permit continued operation of the unit that is not further restricted by the Completion Time. In this case, compliance with the Required Actions provides an acceptable level of safety for continued operation.

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-2 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.2 (continued)

The nature of some Required Actions of some Conditions necessitates that, once the Condition is entered, the Required Actions must be completed even though the associated Conditions no longer exist. The individual LCO's ACTIONS specify the Required Actions where this is the case. An example of this is in LCO 3.4.10, "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. The ACTIONS for not meeting a single LCO adequately manage any increase in plant risk, provided any unusual external conditions (e.g., severe weather, offsite power instability) are considered. In addition, the increased risk associated with simultaneous removal of multiple structures, systems, trains or components from service is assessed and managed in accordance with 10 CFR 50.65(a)(4). Individual Specifications may specify a time limit for performing an SR when equipment is removed from service or bypassed for testing. In this case, the Completion Times of the Required Actions are applicable when this time limit expires, if the equipment remains removed from service or bypassed.

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

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

a.

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

b.

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-3 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.3 (continued)

This Specification delineates the time limits for placing the unit in a safe MODE or other specified condition when operation cannot be maintained within the limits for safe operation as defined by the LCO and its ACTIONS. Planned entry into LCO 3.0.3 should be avoided. If it is not practicable to avoid planned entry into LCO 3.0.3, plant risk should be assessed and managed in accordance with 10 CFR 50.65(a)(4), and the planned entry into LCO 3.0.3 should have less effect on plant safety than other practicable alternatives.

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 enter lower MODES of operation permit the shutdown to proceed in a controlled and orderly manner that is well within the specified maximum cooldown rate and within the capabilities of the unit, assuming that only the minimum required equipment is OPERABLE. This reduces thermal stresses on components of the Reactor Coolant System and the potential for a plant upset that could challenge safety systems under conditions to which this Specification applies. The use and interpretation of specified times to complete the actions of LCO 3.0.3 are consistent with the discussion of Section 1.3, Completion Times.

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

a.

The LCO is now met,

b.

The LCO is no longer applicable,

c.

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

d.

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

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 4 when a shutdown is required during MODE 1 operation. If the unit is in a lower MODE of operation when a shutdown is required, the time limit for entering the next lower MODE applies. If a lower MODE is entered in

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-4 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.3 (continued) less time than allowed, however, the total allowable time to enter MODE 4, or other applicable MODE, is not reduced. For example, if MODE 2 is entered in 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months , then the time allowed for entering MODE 3 is the next 11 hours1.273148e-4 days 0.00306 hours 1.818783e-5 weeks 4.1855e-6 months , because the total time for entering MODE 3 is not reduced from the allowable limit of 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months . Therefore, if remedial measures are completed that would permit a return to MODE 1, a penalty is not incurred by having to enter a lower MODE of operation in less than the total time allowed.

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

Exceptions to LCO 3.0.3 are provided in instances where requiring a unit shutdown, in accordance with LCO 3.0.3, would not provide appropriate remedial measures for the associated condition of the unit. An example of this is in LCO 3.7.8, "Spent Fuel Storage Pool Water Level." LCO 3.7.8 has an Applicability of "During movement of irradiated fuel assemblies in the spent fuel storage pool." Therefore, this LCO can be applicable in any or all MODES. If the LCO and the Required Actions of LCO 3.7.8 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LCO 3.7.8 of "Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications.

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

LCO 3.0.4.a allows entry into a MODE or other specified condition in the Applicability with the LCO not met when the associated ACTIONS to be entered following entry into the MODE or other specified condition in the Applicability will permit continued operation within the MODE or other specified condition for an unlimited period of time. Compliance with ACTIONS that permit continued operation of the unit for an unlimited period of time in a MODE or other specified condition provides an 7

1 1

1 7

7 7

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-5 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.4 (continued) acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made and the Required Actions followed after entry into the Applicability.

For example, LCO 3.0.4.a may be used when the Required Action to be entered states that an inoperable instrument channel must be placed in the trip condition within the Completion Time. Transition into a MODE or other specified condition in the Applicability may be made in accordance with LCO 3.0.4 and the channel is subsequently placed in the tripped condition within the Completion Time, which begins when the Applicability is entered. If the instrument channel cannot be placed in the tripped condition and the subsequent default ACTION ("Required Action and associated Completion Time not met") allows the OPERABLE train to be placed in operation, use of LCO 3.0.4.a is acceptable because the subsequent ACTIONS to be entered following entry into the MODE include ACTIONS (place the OPERABLE train in operation) that permit safe plant operation for an unlimited period of time in the MODE or other specified condition to be entered.

LCO 3.0.4.b allows entry into a MODE or other specified condition in the Applicability with the LCO not met after performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and establishment of risk management actions, if appropriate.

The risk assessment may use quantitative, qualitative, or blended approaches, and the 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.160, "Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." Regulatory Guide 1.160 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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-6 Rev. 5.0 Hope Creek Revision XXX 1

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

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-7 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.4 (continued)

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

The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown. In this context, a unit shutdown is defined as a change in MODE or other specified 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.

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

a.

The OPERABILITY of the equipment being returned to service or

b.

The OPERABILITY of other equipment.

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-8 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.5 (continued) other preventive or corrective maintenance. LCO 3.0.5 should not be used in lieu of other practicable alternatives that comply with Required Actions and that do not require changing the MODE or other specified conditions in the Applicability in order to demonstrate equipment is OPERABLE. LCO 3.0.5 is not intended to be used repeatedly.

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

Examples of demonstrating equipment OPERABILITY include instances in which it is necessary to take an inoperable channel or trip system out of a tripped condition that was directed by a Required Action, if there is no Required Action Note for this purpose. An example of verifying OPERABILITY of equipment removed from service is taking a tripped channel out of the tripped condition to permit the logic to function and indicate the appropriate response during performance of required testing on the inoperable channel. Examples of demonstrating the OPERABILITY of other equipment are taking an inoperable channel or trip system out of the tripped condition 1) to prevent the trip function from occurring during the performance of required testing on another channel in the other trip system, or 2) to permit the logic to function and indicate the appropriate response during the performance of required testing on another channel in the same trip system.

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-9 Rev. 5.0 Hope Creek Revision XXX 1

BASES 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 plant is maintained in a safe condition are specified in the support system LCO's Required Actions. These Required Actions may include entering the supported system's Conditions and Required Actions or may specify other Required Actions.

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

However, there are instances where a support system's Required Action may either direct a supported system to be declared inoperable or direct entry into Conditions and Required Actions for the supported system.

This may occur immediately or after some specified delay to perform some other Required Action. Regardless of whether it is immediate or after some delay, when a support system's Required Action directs a supported system to be declared inoperable or directs entry into Conditions and Required Actions for a supported system, the applicable Conditions and Required Actions shall be entered in accordance with LCO 3.0.2.

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

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

1 9

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-10 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.6 (continued)

The following examples use Figure B 3.0-1 to illustrate loss of safety function conditions that may result when a TS support system is inoperable. In this figure, the fifteen systems that comprise Train A are independent and redundant to the fifteen systems that comprise Train B.

To correctly use the figure to illustrate the SFDP provisions for a cross train check, the figure establishes a relationship between support and supported systems as follows: the figure shows System 1 as a support system for System 2 and System 3; System 2 as a support system for System 4 and System 5; and System 4 as a support system for System 8 and System 9. Specifically, a loss of safety function may exist when a support system is inoperable and:

a.

A system redundant to system(s) supported by the inoperable support system is also inoperable (EXAMPLE B 3.0.6-1),

b.

A system redundant to system(s) in turn supported by the inoperable supported system is also inoperable (EXAMPLE B 3.0.6-2), or

c.

A system redundant to support system(s) for the supported systems (a) and (b) above is also inoperable (EXAMPLE B 3.0.6-3).

For the following examples, refer to Figure B 3.0-1.

EXAMPLE B 3.0.6-1 If System 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.

EXAMPLE B 3.0.6-2 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.

EXAMPLE B 3.0.6-3 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

11.

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-11 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.6 (continued)

Figure B 3.0-1 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 accordance with 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 sources also 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).

When loss of safety function is determined to exist, and the SFDP requires entry into the appropriate 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 4

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-12 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.6 (continued) address the inoperabilities of that system 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.0.7 There are certain special tests and operations required to be performed at various times over the life of the unit. These special tests and operations are necessary to demonstrate select unit performance characteristics, to perform special maintenance activities, and to perform special evolutions.

Special Operations LCOs in Section 3.10 allow specified 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 Special Operations LCO represents a condition not necessarily in compliance with the normal requirements of the TS.

Compliance with Special Operations LCOs is optional. A special operation may be performed either under the provisions of the appropriate Special Operations LCO or under the other applicable TS requirements. If it is desired to perform the special operation under the provisions of the Special Operations LCO, the requirements of the Special Operations LCO shall be followed. When a Special Operations LCO requires another LCO to be met, only the requirements of the LCO statement are required to be met regardless of that LCO's Applicability (i.e., should the requirements of this other LCO not be met, the ACTIONS of the Special Operations LCO apply, not the ACTIONS of the other LCO). However, there are instances where the Special Operations LCO ACTIONS may direct the other LCOs' ACTIONS be met. The Surveillances of the other LCO are not required to be met, unless specified in the Special Operations LCO. If conditions exist such that the Applicability of any other LCO is met, all the other LCO's requirements (ACTIONS and SRs) are required to be met concurrent with the requirements of the Special Operations LCO.

LCO 3.0.8 LCO 3.0.8 establishes conditions under which systems are considered to remain capable of performing their intended safety function when associated snubbers are not capable of providing their associated support function(s). This LCO states that the supported system is not considered to be inoperable solely due to one or more snubbers not capable of performing their associated support function(s). This is appropriate because a limited length of time is allowed for maintenance, testing, or

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-13 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.8 (continued) repair of one or more snubbers not capable of performing their associated support function(s) and appropriate compensatory measures are specified in the snubber requirements, which are located outside of the Technical Specifications (TS) under licensee control. The snubber requirements do not meet the criteria in 10 CFR 50.36(c)(2)(ii), and, as such, are appropriate for control by the licensee.

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

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

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-14 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.9

REVIEWER'S NOTES--------------------------------

Adoption of LCO 3.0.9 requires the licensee to make the following commitments:

1. [LICENSEE] commits to the guidance of NUMARC 93-01, Revision [4F], Section 11, which provides guidance and details on the assessment and management of risk during maintenance.

2. [LICENSEE] commits to the guidance of NEI 04-08, "Allowance for Non Technical Specification Barrier Degradation on Supported System OPERABILITY (TSTF-427) Industry Implementation Guidance," March 2006.

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

Barriers are doors, walls, floor plugs, curbs, hatches, installed structures or components, or other devices, not explicitly described in Technical Specifications, that support the performance of the safety function of systems described in the Technical Specifications. This LCO states that the supported system is not considered to be inoperable solely due to required barriers not capable of performing their related support function(s) under the described conditions. LCO 3.0.9 allows 30 days before declaring the supported system(s) inoperable and the LCO(s) associated with the supported system(s) not met. A maximum time is placed on each use of this allowance to ensure that as required barriers are found or are otherwise made unavailable, they are restored.

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

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

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

3

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-15 Rev. 5.0 Hope Creek Revision XXX 1

BASES LCO 3.0.9 (continued)

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

REVIEWER'S NOTE-----------------------------------

LCO 3.0.9 may be expanded to other initiating event categories provided plant-specific analysis demonstrates that the frequency of the additional initiating events is bounded by the generic analysis or if plant-specific approval is obtained from the NRC.

Loss of coolant accidents; High energy line breaks; Feedwater line breaks; Internal flooding; External flooding; Turbine missile ejection; and Tornado or high wind.

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

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

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

LCO 3.0.9 may be applied to one or more trains or subsystems of a system supported by barriers that cannot provide their related support function(s), provided that risk is assessed and managed (including consideration of the effects on Large Early Release and from external events). If applied concurrently to more than one train or subsystem of a multiple train or subsystem supported system, the barriers supporting each of these trains or subsystems must provide their related support function(s) for different categories of initiating events. For example, LCO 3.0.9 may be applied for up to 30 days for more than one train of a multiple train supported system if the affected barrier for one train 3

LCO Applicability B 3.0 General Electric BWR/4 STS B 3.0-16 Rev. 5.0 Hope Creek Amendment XXX 1

BASES LCO 3.0.9 (continued) protects against internal flooding and the affected barrier for the other train protects against tornado missiles. In this example, the affected barrier may be the same physical barrier but serve different protection functions for each train.

[The [HPCI (High Pressure Coolant Injection) / HPCS (High Pressure Core Spray)] and RCIC (Reactor Core Isolation Cooling) systems are single train systems for injecting makeup water into the reactor during an accident or transient event. The RCIC System is not a safety system, nor required to operate during a transient, therefore, it does not have to meet the single failure criterion. The [HPCI / HPCS] System provides backup in case of a RCIC System failure. The ADS (Automatic Depressurization System) and low pressure ECCS coolant injection provide the core cooling function in the event of failure of the [HPCI / HPCS] System during an accident. Thus, for the purposes of LCO 3.0.9, the [HPCI /

HPCS] System, the RCIC System, and the ADS are considered independent subsystems of a single system and LCO 3.0.9 can be used on these single train systems in a manner similar to multiple train or subsystem systems.]

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

2

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-17 Rev. 5.0 Hope Creek Revision XXX 1

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 apply at all times, unless otherwise stated.

SR 3.0.2 and SR 3.0.3 apply in Chapter 5 only when invoked by a Chapter 5 Specification.

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 within the 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 components are OPERABLE when:

a.

The systems or components are known to be inoperable, although still meeting the SRs or

b.

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

Surveillances do not have to be performed when the unit is in a MODE or other specified condition for which the requirements of the associated LCO are not applicable, unless otherwise specified. The SRs associated with a Special Operations LCO are only applicable when the Special Operations 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 allowance includes those SRs whose performance is normally precluded in a given MODE or other specified condition.

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-18 Rev. 5.0 Hope Creek Revision XXX 1

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.0.2, prior to returning equipment to OPERABLE status.

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

Some examples of this process are:

a.

Control Rod Drive maintenance during refueling that requires scram testing at > [800 psi]. However, if other appropriate testing is satisfactorily completed and the scram time testing of SR 3.1.4.3 is satisfied, the control rod can be considered OPERABLE. This allows startup to proceed to reach [800 psi] to perform other necessary testing.

b.

High pressure coolant injection (HPCI) maintenance during shutdown that requires system functional tests at a specified pressure.

Provided other appropriate testing is satisfactorily completed, startup can proceed with HPCI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance 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 not be suitable for conducting the Surveillance (e.g., transient conditions or other ongoing Surveillance or maintenance activities).

psig psig 2

2 1

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-19 Rev. 5.0 Hope Creek Revision XXX 1

BASES SR 3.0.2 (continued)

When a Section 5.5, "Programs and Manuals," specification states that the provisions of SR 3.0.2 are applicable, a 25% extension of the testing interval, whether stated in the specification or incorporated by reference, is permitted.

The 25% extension does not significantly degrade the reliability that results from performing the Surveillance at its specified Frequency. This is based on the recognition that the most probable result of any particular Surveillance being performed is the verification of conformance with the SRs.

The exceptions to SR 3.0.2 are those Surveillances for which the 25%

extension of the interval specified in the Frequency does not apply.

These exceptions are stated in the individual Specifications. The requirements of regulations take precedence over the TS. Examples of where SR 3.0.2 does not apply are the Primary Containment Leakage Rate Testing Program required by 10 CFR 50, Appendix J, and the inservice testing of pumps and valves in accordance with applicable American Society of Mechanical Engineers Operation and Maintenance Code, as required by 10 CFR 50.55a. These programs establish 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 directly or by reference.

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

The provisions of SR 3.0.2 are not intended to be used repeatedly 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 performed within the specified Frequency. A delay period of up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whichever is greater, applies from the point in time that it is

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-20 Rev. 5.0 Hope Creek Revision XXX 1

BASES SR 3.0.3 (continued) 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.

When a Section 5.5, "Programs and Manuals," specification states that the provisions of SR 3.0.3 are applicable, it permits the flexibility to defer declaring the testing requirement not met in accordance with SR 3.0.3 when the testing has not been completed within the testing interval (including the allowance of SR 3.0.2 if invoked by the Section 5.5 specification).

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

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

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

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

SR 3.0.3 is only applicable if there is a reasonable expectation the associated equipment is OPERABLE or that variables are within limits, and it is expected that the Surveillance will be met when performed.

Many factors should be considered, such as the period of time since the Surveillance was last performed, or whether the Surveillance, or a portion thereof, has ever been performed, and any other indications, tests, or activities that might support the expectation that the Surveillance will be

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-21 Rev. 5.0 Hope Creek Revision XXX 1

BASES SR 3.0.3 (continued) met when performed. An example of the use of SR 3.0.3 would be a relay contact that was not tested as required in accordance with a particular SR, but previous successful performances of the SR included the relay contact; the adjacent, physically connected relay contacts were tested during the SR performance; the subject relay contact has been tested by another SR; or historical operation of the subject relay contact has been successful. It is not sufficient to infer the behavior of the associated equipment from the performance of similar equipment. The rigor of determining whether there is a reasonable expectation a Surveillance will be met when performed should increase based on the length of time since the last performance of the Surveillance. If the Surveillance has been performed recently, a review of the Surveillance history and equipment performance may be sufficient to support a reasonable expectation that the Surveillance will be met when performed.

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

Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence. Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used repeatedly to extend Surveillance intervals. While up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or the limit of the specified Frequency is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity. The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance. This risk impact should be managed through the program in place to implement 10 CFR 50.65(a)(4) and its implementation guidance, NRC Regulatory Guide 1.160, "Monitoring the Effectiveness of Maintenance at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown. The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-22 Rev. 5.0 Hope Creek Revision XXX 1

BASES SR 3.0.3 (continued) the importance of the component. Missed Surveillances for important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensees 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.

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

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

SR Applicability B 3.0 General Electric BWR/4 STS B 3.0-23 Rev. 5.0 Hope Creek Revision XXX 1

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

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

The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the Frequency, in the Surveillance, or both. This allows performance of Surveillances when the prerequisite condition(s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LCO prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCOs Applicability, would have its Frequency specified such that it is not "due" until the specific conditions needed are met.

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

JUSTIFICATION FOR DEVIATIONS ITS 3.0 BASES, LCO AND SR APPLICABILITY Hope Creek Page 1 of 1

1. Changes are made (additions, deletions, and/or changes) to the ISTS Bases which reflect the plant specific nomenclature, number, reference, system description, analysis, or licensing basis description.

2. The ISTS contains bracketed information and/or values that are generic to all General Electric BWR/4 vintage plants. The brackets are removed and the proper plant specific information/value is changed to reflect the current licensing basis.

3. The Reviewers Note has been deleted. This information is for the NRC reviewer to be keyed into what is needed to meet this requirement. This Note is not meant to be retained in the final version of the plant specific submittal. As part of Amendment 228 (ADAMS Accession No. ML21098A087), PSEG Nuclear committed to assess and manage risk in accordance with the guidance of NUMARC 93-01, Rev. 4F, Section 11 and NEI 04-08 whenever a barrier is unavailable and the requirements of LCO 3.0.9 are applied.

4. The ISTS text is modified to remove an unnecessary space. This is an editorial deviation from the NUREG.

Specific No Significant Hazards Considerations (NSHCs)

DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS 3.0, LCO AND SR APPLICABILITY HOPE CREEK Page 1 of 1 There are no specific No Significant Hazards Considerations for this Specification.

ML24142A433

Text

Navigation menu

Search