ML030380532

Tech Spec Page for License Amendment Nos. 280 & 271, Missed Surveillances

ML030380532
Person / Time
Site:	Sequoyah
Issue date:	02/05/2003
From:	NRC/NRR/DLPM/LPD2
To:
References
TAC MB6267, TAC MB6268
Download: ML030380532 (12)

Text

APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0'1 Surveillance Requirements shall be met during the MODES or other specified conditions In the Applicability for Individual Limiting Condition for Operation, unless otherwise stated in the Individual Surveillance Requirement. Failure to meet a Surveillance Requirement, whether such failure Is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the Uimiting Condition for Operation. Failure to perform a Surveillance within the specified surveillance interval shagl be failure to meet the Limiting Conditions 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 the 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 surveillance Interval (including the allowed extension per Specification 4.0.2), then compliance with the requirement to declare the Umiting Condition for Operation not met may be delayed, from the time of discovery, up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> or up to the limit of the specified surveillance Interval, whichever is greater. This delay period Is permitted to allow performance of the Surveillance. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> 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 ACTION(s) 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 ACTION(s) must be entered.

4.0.4 Entry Into an OPERATIONAL MODE or other specified condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation have been performed within the specified surveillance Interval or as otherwise specified. This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements.

4.0.5 Surveillance Requirements for inservice inspection and testing of ASME Code Class 1, 2 and 3 components shall be as follows:

Inservice Inspection Program This program provides controls for inservice Inspection of ASME Code Class 1, 2, and 3 components, Including applicable supports. The program shall Include the following:

a. Provisions that inservice testing of ASME Code Class 1, 2 and 3 components shall be performed in accordance with Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50.55a;

b. The provisions of SR 4.0.2 are applicable to the frequencies for performing inservice Inspection activities;

c. Inspection of each reactor coolant pump flywheel per the recommendation of Regulation Position c.4.b of Regulatory Guide 1.14, Revision 1, August 1975 or in lieu of Position c.4.b(1) and c.4.b(2), a qualified in-place ultrasonic examination over the volume from the Inner bore of the flywheel to the circle one-half of the outer radius or a surface examination (magnetic particle and/or liquid penetrant) of exposed surfaces of the removed flywheels may be conducted at approximately 10-year Intervals coinciding with the Inservice Inspection schedule as required by ASME Section XI; and

d. Nothing In the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirement of any TS.

SEQUOYAH - UNIT 1 3/4 0-2 Amendment No. 78, 162,208,274, 280

APPLICABILITY BASES instead, provided the other specified conditions are satisfied. In this case, this would mean that for one division the emergencypower source must be OPERABLE (as must be the components supplied by the emergency power source) and all redundant systems, subsystems, trains, components and devices in both divisions must also be OPERABLE. Ifthese conditions are not satisfied, action is required in accordance with this specification'.

InMODES 5 or 6, Specification 3.0.5 is not appliclable, and thus the indlvidual ACTION statements for each applicable Limiting Condition for Operation in these MODES must be adhered to.

3.0.6 LCO 3.0.6 establishes the allowance -for restoring equipment to serv.ceunder 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 LCOs 3.0.1 and 3.0.2 (e.g., to not comply

'with the applicable Required Action[s]) to allow the performanceof SRst0 demonstrate:

a. "TheOPERABILITY 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 Inconflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs.

This Specification does not provide time to perform any other preventive or corrective maintenance.

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

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

4.0.1 SR 4.0.1 establishes the requirement that surveillances must be met during the OPERATIONAL MODES or other specified conditions Inthe Applicability for which the requirements of the Limiting Condition for Operation apply, unless otherwise specified Inthe individual Surveillance Requirement. The purposes of this Specification is to ensure that Surveillances are performed to verify the operational status of systems and components and that variables are within specified limits to ensure safe operation of the facility when the plant is in a MODE or other specified condition for which associated Limiting Condition for Operation are applicable. Failure to meet a Surveillance Requirement within the specified surveillance interval, in accordance with SR 4.0.2, constitutes a failure to meet a Limiting Condition for Operation.

Systems and components are assumed to be OPERABLE when the associated Surveillance Requirements have been met. Nothing inthis 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 Surveillance Requirements; or

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

SEQUOYAH - UNIT 1 B 3/4 0-3 Amendment No. 78, 162,202, 280

APPLICABILITY BASES Surveillances do not have to be performed when the unit Is in an OPERATIONAL MODE for which the requirements of the associated Umiting Condition for Operation do not apply unless otherwise specified.

SThe Surveillance Requirements- associated with a.Speclal Test Exception are only applicable when the.

Special Test Exception Is used as an allowable exception to the requirements of a specification.

Surveillance Requirements do not have to be performed on inoperable equipment because the ACTION requirements define the remedial measures that apply. However, the Surveillance Requirements have to:

be met to demonstrate that the Inoperable equipment has been restored 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 4.0.2. Post maintenance testing may not be possible in the current OPERATIONAL 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 an OPERATIONAL MODE or other specified condition where other necessary post maintenance tests can be completed.

Some examples of this process are:

a. Auxiliary feedwater (AFW) pump turbine maintenance during refueling that requires testing at steam pressures > 800 psi. However, Ifother appropriate testing is satisfactorily completed, the AFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to perform the testing.

b. High pressure safety Injection (HPI) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with HPI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.

4.0.2 Specification 4.0.2 established the limit for which the specified time Interval for Surveillance Requirements may be extended. It permits an allowable extension of the normal surveillance Interval to facilitate surveillance scheduling and consideration of plant operating conditions that may not be suitable for conducting the surveillance; e.g., transient conditions or other ongoing surveillance or maintenance activities. It also provides flexibility to accommodate the length of a fuel cycle for surveillances that are performed at each refueling outage and are specified with an 18-month surveillance Interval. ItIs not intended that this provision be used repeatedly as a convenience to extend surveillance Intervals beyond that specified for surveillances that are not performed during refueling outages. The limitation of Specification 4.0.2 Is based on engineering judgement and the recognition that the most probable result of any particular surveillance being performed Is the verification of conformance with the Surveillance Requirements. This provision Is sufficient to ensure that the reliability ensured through surveillance activities is not significantly degraded beyond that obtained from the specified surveillance Interval.

4.0.3 SR 4.0.3 establishes the flexibility to defer declaring affected equipment Inoperable or an affected variable outside the specified limit when a Surveillance has not been completed within the specified Frequency. A delay period of up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> or up to the limit of the specified surveillance Interval, whichever is greater, applies from the point in time that It Is discovered that the Surveillance has not been performed In accordance with Specification 4.0.2, and not at the time that the specified surveillance Interval was not met SEQUOYAH - UNIT 1 B 3/4 0-3a Amendment No. 78, 162,202,280

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

The basis for this delay period Includes consideration of the unit conditions, adequate planning, availability of personnel, the time required to perforrn 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 surveillance 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 Jfuel 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, Specification 4.0.3 allows for the full delay period of up to the specified surveillance Interval to perform the Surveillance. However, since there Is not a time Interval specified, the missed Surveillance should be performed at the first reasonable opportunity.

Specification 4.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes Imposed by required ACTIONS.

Failure to comply with the specified surveillance Interval for the Specification Is expected to be an Infrequent occurrence. Use of the delay period established by Surveillance Requirement 4.0.3 is a flexibility which Is not Intended to be used as an operational convenience to extend Surveillance Intervals.

While up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> or the limit of the specified surveillance interval 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 dsk Impact should be managed through the program In place to Implement 10 CFR 50.65(a)(4) and its Implementation guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk Impacts, determination of risk management action thresholds, and risk management action up to and Including plant shutdown. The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the Importance of the component. Missed Surveillances for Important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk Increase Is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program.

If a Surveillance is not completed within the allowed delay period, then the equipment Is considered inoperable or the variable Is considered outside the specification limits and the entry Into the ACTION requirements for the applicable IUmiting Conditions for Operation begins 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 entry Into the ACTION requirements or the applicable Urmiting Conditions for Operation begins Immediately upon the failure of the Surveillance.

Completion of the Surveillance within the delay period allowed by this Specification, or within the Allowed Outage Time of the ACTIONS, restores compliance with Specification 4.0.1.

SEQUOYAH - UNIT 1 B 3/4 0-4 Amendment No. 78,280

ADMINISTRATIVE CONTROLS J. Technical Specification (TS) Bases Control Program This program provides a means for processing changes to the Bases of TSs.

a.; Changes to the Bases of the TS shall be made under appropriate administrative controls

-and reviews.

b. Ucensees may make changes to Bases without prior NRC approval provided the

.changes do not require either of the following:

1. A change In the TS Incorporated in the license or

-2.

A change to the updated FSAR or Bases that requires NRC approval pursuant to 10 CFR 50.59.

c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR..

d. Proposed changes that meet the criteria of Specification 6.8.4.j.b above shall be reviewed and approved by the NRC prior to Implementation. Changes to the Bases Implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71 (e).

6.9 REPORTING REQUIREMENTS ROUTINE REPORTS 6.9.1 In addition to the applicable reporting requirements of Title 10, Code of Federal Regulations, the following reports shall be submitted In accordance with 10 CFR 50.4.

STARTUP REPORT 6.9.1.1 DELETED 6.9.1.2 DELETED 6.9.1.3 DELETED ANNUAL REPORTS 1/

6.9.1.4 Annual reports covering the activities of the unit as described below for the previous calendar year shall be submitted prior to March 1 of each year. The Initial report shall be submitted prior to March I of the year following Initial criticality.

6.9.1.5 Reports required on an annual basis shall Include a tabulation on an annual basis for the number of station, utility and other personnel (including contractors) receiving exposures greater than 100 mrern/yr and their associated man rem exposure according to work and job functions g reactor operations and surveillance, inservice inspection, routine maintenance, special maintenance.

1/ A single submittal may be made for a multiple unit station. The submittal should combine those sections that are common to all units at the station.

_2 This tabulation supplements the requirements of § 20.2206 of 10 CFR Part 20.

SEQUOYAH - UNIT I 6-11 Amendment No. 12, 32, 58, 72, 74, 148, 174, 233, 280

APPLICABILITY SURVEILLANCE REQUIREMENTS 4.0.1 Surveillance Requirements shall be met during the MODES or other specified conditions In the Applicability for Individual Limiting Condition for Operation, unless otherwise stated in the Individual Surveillance Requirement. Failure to meet a Surveillance Requirement, 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 surveillance Interval shall be failure to meet the Limiting Conditions 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 the specified surveillance Interval with a maximum allowable extension not to exceed 25 percent of the specified sunieillance interval.

4.0.3 If it Is discovered that a Surveillance was not performed within its specified surveillance Interval (including the allowed extension per Specification 4.0.2), 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 hours1 days <br />0.143 weeks <br />0.0329 months <br /> or up to the limit of the specified surveillance Interva!, whichever is greater. This delay period is permitted to allow performance of the Surveillance. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> 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 ACTION(s) 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 ACTION(s) must be entered.

4.0.4 Entry Into an OPERATIONAL MODE or other specified condition shall not be made unless the Surveillance Requirement(s) associated with the Limiting Condition for Operation have been performed within the specified surveillance Interval or as otherwise specified. This provision shall not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements.

4.0.5 Surveillance Requirements for inservice Inspection and testing of ASME Code Class 1, 2 and 3 components shall be applicable as follows:

Inservice Inspection Program This program provides controls for Inservice Inspection of ASME Code Class 1, 2, and 3 components, including applicable supports. The program shall Include the following:

a. Provisions that Inservice testing of ASME Code Class 1, 2 and 3 components shall be performed in accordance with Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50.55a;

b. The provisions of SR 4.0.2 are applicable to the frequencies for performing inservice Inspection activities;

c. Inspection of each reactor coolant pump flywheel per the recommendation of Regulation Position c.4.b of Regulatory Guide 1.14, Revision 1, August 1975 or in lieu of Position c.4.b(1) and c.4.b(2), a qualified in-place ultrasonic examination over the volume from the Inner bore of the flywheel to the circle one-half of the outer radius or a surface examination (magnetic particle and/or liquid penetrant) of exposed surfaces of the removed flywheels may be conducted at approximately 10-year intervals coinciding with the Inservice Inspection schedule as required by ASME Section XI; and

d. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirement of any TS.

SEQUOYAH - UNIT 2 314 0-2 Amendment Nos. 69, 152, 198, 263, 271

BASES 3.0.5 (Continued) specified conditions are satisfied. In this case, this would mean that for one division the emergency power source must be OPERABLE (as must be the components supplied by the emergency power source) and all redundant systems, subsystems, trains, components and devices in both divisions must also be OPERABLE. If these conditions are not satisfied, action is required in accordance with this specification.

In MODES 5 or 6, Specification 3.0.5 Is not applicable, and thus the Individual ACTION statements for each applicable Umiting Condition for Operation In these MODES must be adhered to..

3.0.6 LCO 3.0.6 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 LCOs 3.0.1 and 3.0.2 (e.g., to not comply with the applicable Required Action[sD to allow the performance of SRs to demonstrate:

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

b. The OPERABILITY of other equipment.

The administrative controls ensure the time the equipment is returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs.

This Specification does not provide time to perform any other preventive or corrective maintenance.

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

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

4.0.1 SR 4.0.1 establishes the requirement that surveillances must be met during the OPERATIONAL MODES or other specified conditions In the Applicability for which the requirements of the Limiting Condition for Operation apply, unless otherwise specified in the individual Surveillance Requirement. The purposes of this Specification is to ensure that Surveillances are performed to verify the operational status of systems and components and that variables are within specified limits to ensure safe operation of the facility when the plant is In a MODE or other specified condition for which associated Umiting Condition for Operation are applicable. Failure to meet a Surveillance Requirement within the specified surveillance interval, in accordance with SR 4.0.2, constitutes a failure to meet a Limiting Condition for Operation.

Systems and components are assumed to be OPERABLE when the associated Surveillance Requirements 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 Surveillance Requirements; or SEQUOYAH - UNIT 2 B 3/4 0-3 Amendment No. 69, 152, 192, 271

APPLICABILITY BASES

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

Surveillances do not have to be performed when the unit Is In an OPERATIONAL MODE for which the requirements of the associated Limiting Condition for Operation do not apply unless otherwise specified.

The Surveillance Requirements associated with a Special Test Exception are only applicable when the Special Test Exception Is used as an allowable exception to the requirements of a specification.

Surveillance Requirements do not have to be performed on Inoperable equipment because the ACTION requirements define the remedial measures that apply. However, the Surveillance Requirements have.to be met to demonstrate that the inoperable equipment has been restored 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 4.0.2. Post maintenance testing may not be possible in the current OPERATIONAL MODE or other specified conditions Inthe 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 an OPERATIONAL MODE or other specified condition where other necessary post maintenance tests can be completed.

Some examples of this process are:

a. Auxiliary feedwater (AFW) pump turbine maintenance during refueling that requires testing at steam pressures > 800 psi. However, ifother appropriate testing Is satisfactorily completed, the AFW System can be considered OPERABLE. This allows startup and other necessary testing to proceed until the plant reaches the steam pressure required to'perform the testing.

b. High pressure safety Injection (HPI) maintenance during shutdown that requires system functional tests at a specified pressure. Provided other appropriate testing is satisfactorily completed, startup can proceed with HPI considered OPERABLE. This allows operation to reach the specified pressure to complete the necessary post maintenance testing.

4.0.2 Specification 4.0.2 established the limit for which the specified time interval for Surveillance Requirements may be extended. It permits an allowable extension of the normal surveillance Interval to facilitate surveillance scheduling and consideration of plant operating conditions that may not be suitable for conducting the surveillance; e.g., transient conditions or other ongoing surveillance or maintenance activities. Italso provides flexibility to accommodate the length of a fuel cycle for surveillances that are performed at each refueling outage and are specified with an 18-month surveillance Interval. It is not Intended that this provision be used repeatedly as a convenience to extend surveillance intervals beyond that specified for surveillances that are not performed during refueling outages. The limitation of Specification 4.0.2 Is based on engineering judgement and the recognition that the most probable result of any particular surveillance being performed Is the verification of conformance with the Surveillance Requirements. This provision Is sufficient to ensure that the reliability ensured through surveillance activities Is not significantly degraded beyond that obtained from the specified surveillance Interval.

SEQUOYAH - UNIT 2 B 314 0-3a Amendment Nos. 69,152, 192, 271

BASES 4.0.3 SR 4.0.3 establishes the flexibility to defer declaring affected equipment Inoperable or an affected variable outside the specified limit when a Surveillance has not been completed within the specified Frequency. A delay period of up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> orup to the limit of the specified surveillance Interval, whichever is greater, applies from the point in time that it Is discovered that the Surveillance has not been performed In accordance with Specification 4.0.2, and not at the time that the specified surveillance Interval was not met.

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

The basis for this delay period Includes consideration of the 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 surveillance 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, Specification 4.0.3 allows for the full delay period of up to the specified surveillance Interval to perform the Surveillance. However, since there is notea time Interval specified, the missed Surveillance should be performed at the first reasonable opportunity.

Specification 4.0.3 provides a time limit for, and allowances for the performance of, Surveillances that become applicable as a consequence of MODE changes Imposed by required ACTIONS.

Failure to comply with the specified surveillance interval for the Specification Is expected to be an infrequent occurrence. Use of the delay period established by Surveillance Requirement 4.0.3 is a flexibility which is not Intended to be used as an operational convenience to extend Surveillance intervals.

While up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> or the limit of the specified surveillance interval is provided to perform the missed Surveillance, it is expected that the missed Surveillance will be performed at the first reasonable opportunity. The determination of the first reasonable opportunity should include consideration of the impact on plant risk (from delaying the Surveillance as well as any plant configuration changes required or shutting the plant down to perform the Surveillance) and Impact on any analysis assumptions, in addition to unit conditions, planning, availability of personnel, and the time required to perform the Surveillance.

This risk impact should be managed through the program In place to Implement 10 CFR 50.65(a)(4) and its Implementation guidance, NRC Regulatory Guide 1.182, "Assessing and Managing Risk Before Maintenance Activities at Nuclear Power Plants." This Regulatory Guide addresses consideration of temporary and aggregate risk impacts, determination of risk management action thresholds, and risk management action up to and including plant shutdown. The missed Surveillance should be treated as an emergent condition as discussed in the Regulatory Guide. The risk evaluation may use quantitative, qualitative, or blended methods. The degree of depth and rigor of the evaluation should be commensurate with the importance of the component. Missed Surveillances for Important components should be analyzed quantitatively. If the results of the risk evaluation determine the risk Increase is significant, this evaluation should be used to determine the safest course of action. All missed Surveillances will be placed in the licensee's Corrective Action Program.

SEQUOYAH - UNIT 2 B 3/4 0-4 Amendment No. 69, 271

BASES 4.0.3 (Continued)

If a Surveillance is not completed within the allowed delay period, then the equipment is considered Inoperable or the. variable Is considered outside the.specification limits and the entry into the ACTION requirements for the applicable Umiting Conditions for Operation begins Immediately upon expiration of the delay penod. If a Surveillance is failed within the delay period, then the equipment is Inoperable, or the

.variable is.outside thespecified limits and the entry into the ACTION requirements or the applicable Limiting Conditions for Operation begins Immediately upon the failure of the Surveillance.

Completion of the Surveillance within the delay period allowed by this Specification, or within the Allowed Outage Time of the ACTIONS, restores compliance with Specification 4.0.1.

4.0.4 This specification establishes the requirement that all applicable surveillances must entry into an OPERATIONAL MODE or other condition of operation specified In the Applicability be met before statement. The purpose of this specification is to ensure that system and component OPERABILITY requirements or parameter limits are met before entry into a MODE or condition for which these systems

• and-components ensure safe operation of the facility. This provision applies to changes in OPERATIONAL MObES or other specified conditions associated with plant shutdown as well .

as startup.

Under the provisions of this specification, the applicable Surveillance Requirements must be within the specified surveillance Interval to ensure that the Limiting Conditions for Operation performed are met during Initial plant startup or following a plant outage.

When a shutdown is required to comply with ACTION requirements, the provisions of Specification.4.0.4 do not apply because this would delay placing the facility In a lower MODE of operation.

4.0.5 This specification ensures that Inservice Inspection of ASME Code Class 1, 2 and 3 components and Inservice testing of ASME Code Class 1, 2 and 3 pumps and valves will be performed in accordance with a periodically updated version of Section Xl of the ASME Boiler and Pressure Vessel Code and Addenda as required by 10 CFR 50.55a.

This specification includes a clarification of the frequencies for performing the Inservice Inspection and testing activities required by Section XI of the ASME Boiler and Pressure Vessel Code and Addenda. This clarification is provided to ensure consistency In surveillance Intervals throughoutapplicable Technical Specifications and to remove any ambiguities relative to the frequencies for performing these the required Inservice inspection and testing activities.

Under the terms of this specification, the more restrictive requirements of the Specifications take precedence over the ASME Boiler and Pressure Vessel Code and Technical Addenda. For example, the requirements of Specification 4.0.4 to perform surveillanceapplicable activities entry Into an OPERATIONAL MODE or other specified applicability condition takes precedence prior to ASME Boiler and Pressure Vessel Code provision which allows pumps to be tested up to one over the week after return to normal operation. And for example, the Technical Specification definition of OPERABLE does not grant a grace period before a device that Is not capable of performing its specified function is declared inoperable and takes precedence over the ASME Boiler and Pressure Vessel Code provision which allows a valve to be incapable of performing Its specified function for up to 24 hours1 days <br />0.143 weeks <br />0.0329 months <br /> before being declared Inoperable.

SEQUOYAH - UNIT 2 B 3/4 0-5 Amendment No. 69, 198, 271

ADMINISTRATIVE CONTROLS

b. Air lock testing acceptance criteria are:

.1). Overall air lock leakage rate'is *i 0.05 L, when tested at >: P,.

2) For each door, leakage rate is _< 0.01 L, when pressurized to > 6 psig for at least two minutes.

The provisions of SR 4.0.2 do not apply to the test frequencies specified in the Containment Leakage Rate Testing Program.

The provisions of SR 4.0.3 are applicable to the Containment Leakage Rate Testing Program.

C1onfiguration Risk Management Program The Configuration Risk Management Program (CRMP) provides a proceduralized risk-informed assessment to manage the risk associated with equipment inoperability. The program applies to Technical Specification structures, systems, or components for which a risk-informed allowed outage time has been granted. The program shall Include the following elements:

a. Provisions for the control and Implementation of a Level 1 at-power Internal events PRA informed methodology. The assessment shall be capable of evaluating the applicable plant configuration.

b. Provisions for performing an assessment prior to entering the Umiting Condition for Operation (LCO) Action for preplanned activities.

c. Provisions for performing an assessment after entering the LCO Action for unplanned entry into the LCO Action.

d. Provisions for assessing the need for additional actions after the discovery of additional equipment out of service conditions while In the LCO Action.

e. Provisions for considering other applicable risk significant contributors such as Level 2 issues and external events, qualitatively or quantitatively.

J. Technical Specification (TS) Bases Control Program This program provides a means for processing changes to the Bases of 'these TSs.

a. Changes to the Bases of the TS shall be made under appropriate administrative controls and reviews.

b. Licensees may make changes to Bases without prior NRC approval provided the changes do not require either of the following:

1. A change In the TS Incorporated in the license or

2. A change to the updated FSAR or Bases that requires NRC approval pursuant to 10 CFR 50.59.

c. The Bases Control Program shall contain provisions to ensure that the Bases are maintained consistent with the FSAR.

d. Proposed changes that meet the criteria of Specification 6.8.4.J.b above shall be reviewed and approved by the NRC prior to implementation. Changes to the Bases implemented without prior NRC approval shall be provided to the NRC on a frequency consistent with 10 CFR 50.71 (e).

SEQUOYAH - UNIT 2 6-10 Amendment No. 28, 50,64,66,134,207,223, 231, 271_

ADMINISTRATIVE CONTROLS 6.9 REPORTING REQUIREMENTS ROUTINE REPORTS 6.9.1 In addition to the applicable reporting requirements of Title 10, Code of Federal Regulations, the following reports shall be submitted In accordance with 10 CFR 50.4.

STARTUP REPORT 6.9.1.1 DELETED . . ' " . '

S~~~~~~~~..

6.9.1.2 DELETED.,

6.9.1.3 DELETED ANNUAL REPORTS 6.9.1.4 Annual reports covering the activities of the unit as described below for the previous calendar year shall be submitted prior to March Iof each year. The Initial report shall be submitted prior to March I of the year following Initial criticality.

6.9.1.5 Reports required on an annual basis shall include a tabulation on an annual basis for the number of station, utility and other personnel (including contractors) receMng exposures greater than 100 mrem/yr and their associated man rem exposure according to work and job functions,/ e.g., reactor operations and surveillance, inservice Inspection, routine maintenance, special maintenance (describe maintenance),

waste processing, and refueling. The dose assignment to various duty functions may be estimates based on pocket dosimeter, TLD, or film badge measurements. Small exposures totalling less than 20% of the Individual total dose need not be accounted for. In the aggregate, at least 80% of the total whole body dose received from external sources shall be assigned to specific major work functions.

Ifthe results of specific activity analysis In which the primary coolant exceeded the limits of specification 3.4.8.a, then the following Information shall be Included along with the results of specific actMty analysis results In which the'primary coolant exceeded the limits of the specifications: (1) Reactor power history starting 48 hours2 days <br />0.286 weeks <br />0.0658 months <br /> prior to the first sample in which the limit was exceeded; (2) Results of the last Isotopic analysis for radio-Iodine performed prior to exceeding the limit, results of analysis while the limit was exceeded and results of one analysis after the radiolodine activity was reduced to less than the limit Each result should Include date and time of sampling and the radiolodine concentrations; (3) Clean up system flow history starting 48 hours2 days <br />0.286 weeks <br />0.0658 months <br /> prior to the first sample In which the limit was exceeded; (4) Graph of the 1-131 concentration and one other radlolodine isotope concentration In microcurles per gram as a function of time for the duration of the specific activity above the steady-state level; and (5) The time duration when the specific activity of the primary coolant exceeded the radioiodine limit

'/A single submittal may be made for a multiple unit station. The submittal should combine those sections that are common to all units at the station.

I/This tabulation supplements the requirements of § 20.2206 of 10 CFR Part 20.

SEQUOYAH - UNIT 2 6-11 Amendment Nos. 34, 50, 66, 107, 134, 165, 223, 271