ML11251A094

Attachment 1, Volume 1, San Onofre Nuclear Generating Station - Improved Technical Specifications Conversion - ITS Chapter 1.0, Use and Application

ML11251A094
Person / Time
Site:	San Onofre
Issue date:	07/29/2011
From:	Southern California Edison Co
To:	Office of Nuclear Reactor Regulation
References
NUREG-1432, Rev. 3.0
Download: ML11251A094 (114)

Text

ATTACHMENT 1 VOLUME 1 SAN ONOFRE NUCLEAR GENERATING STATION IMPROVED TECHNICAL SPECIFICATIONS CONVERSION ITS CHAPTER 1.0 USE AND APPLICATION

, Volume 1, Rev. 0, Page 1 of 114, Volume 1, Rev. 0, Page 1 of 114

LIST OF ATTACHMENTS

1.

ITS Chapter 1.0, Use and Application, Volume 1, Rev. 0, Page 2 of 114, Volume 1, Rev. 0, Page 2 of 114 ITS Chapter 1.0, USE AND APPLICATION, Volume 1, Rev. 0, Page 3 of 114, Volume 1, Rev. 0, Page 3 of 114

Current Technical Specification (CTS) Markup and Discussion of Changes (DOCs), Volume 1, Rev. 0, Page 4 of 114, Volume 1, Rev. 0, Page 4 of 114

Definitions 1.1 1.0 USE AND APPLICATION 1.1 Definitions

---

NOTE-------------------------------------

The defined terms of this section appear in capitalized type and are applicable throughout these Technical Specifications and Bases.

Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.

AXIAL SHAPE INDEX (ASI)

ASI shall be the power generated in the lower half of the core less the power generated in the upper half of the core, divided by the sum of the power generated in the lower and upper halves of the core.

AZIMUTHAL POWER TILT AZIMUTHAL POWER TILT shall be the power asymmetry (Tq) between azimuthally symmetric fuel assemblies.

CHANNEL CALIBRATION A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel output such that it responds within the necessary range and accuracy to known values of the parameter that the channel monitors. The CHANNEL CALIBRATION shall encompass the entire channel, including the required sensor, alarm, display, and trip functions, and shall include the CHANNEL FUNCTIONAL TEST. Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an inplace cross calibration of the sensing elements and normal calibration of the remaining adjustable devices in the channel. Whenever a sensing element is replaced, the next required inplace cross calibration consists of comparing the other sensing elements with the recently installed sensing element.

ITS 1.1 NOTE ACTIONS AXIAL SHAPE INDEX (ASI)

AZIMUTHAL POWER TILT (Tq)

CHANNEL CALIBRATION all devices in the channel required for channel OPERABILITY and qualitative assessment of sensor behavior A12 LA01 A02 (continued)

SAN ONOFRE--UNIT 2 1.1-1 Amendment No. 127, Volume 1, Rev. 0, Page 5 of 114, Volume 1, Rev. 0, Page 5 of 114

Definitions 1.1 1.1 Definitions CHANNEL CALIBRATION The CHANNEL CALIBRATION may be performed by means (continued) of any series of sequential, overlapping, or total channel steps so that the entire channel is calibrated.

CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter.

CHANNEL FUNCTIONAL TEST A CHANNEL FUNCTIONAL TEST shall be:

a.

Analog channels the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY, including required alarms, interlocks, display and trip functions; b.

Bistable channels (e.g., pressure switches and switch contacts) the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY, including required alarm and trip functions; or c.

Digital computer channels the use of diagnostic programs to test digital computer hardware and the injection of simulated process data into the channel to verify OPERABILITY, including alarm and trip functions.

The CHANNEL FUNCTIONAL TEST may be performed by means of any series of sequential, overlapping, or total channel steps so that the entire channel is tested.

CORE ALTERATION CORE ALTERATION shall be the movement or manipulation of any fuel, sources, reactivity control components, or other components, excluding control element assemblies (CEAs) withdrawn into the upper guide structure, affecting reactivity, ITS CHANNEL CALIBRATION CHANNEL CHECK CHANNEL FUNCTIONAL TEST and bistable of all devices in the channel required for channel OPERABILITY, and b

of all devices in the channel required for channel OPERABILITY A05 A03 A03 A03 A03 A05 A04 A03 A03 (continued)

SAN ONOFRE--UNIT 2 1.1-2 Amendment No. 127, Volume 1, Rev. 0, Page 6 of 114, Volume 1, Rev. 0, Page 6 of 114

Definitions 1.1 1.1 Definitions CORE ALTERATION within the reactor vessel with the vessel head (continued) removed and fuel in the vessel. Suspension of CORE ALTERATIONS shall not preclude completion of movement of a component to a safe position.

CORE OPERATING LIMITS The COLR is the unit specific document that REPORT (COLR) provides cycle specific parameter limits for the current reload cycle. These cycle specific parameter limits shall be determined for each reload cycle in accordance with Specification 5.7.1.5. Plant operation within these limits is addressed in individual Specifications.

DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries/gram) that alone would produce the same thyroid dose as the quantity and isotopic mixture of I-131, I-132, I-133, I-134, and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in ICRP-30, Supplement to Part 1, pages 192-212, Tables titled, "Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity."

E AVERAGE E shall be the average (weighted in proportion DISINTEGRATION ENERGY to the concentration of each radionuclide in the reactor coolant at the time of sampling) of the sum of the average beta and gamma energies per disintegration (in MeV) for isotopes, other than iodines, with half lives > 15 minutes, making up at least 95% of the total noniodine activity in the coolant.

ENGINEERED SAFETY The ESF RESPONSE TIME shall be that time interval FEATURE (ESF) RESPONSE from when the monitored parameter exceeds its ESF TIME actuation setpoint at the channel sensor until the ESF equipment is capable of performing its safety function (i.e., the valves travel to their required positions, pump discharge pressures reach their required values, etc.). Times shall include diesel generator starting and sequence loading delays, where applicable. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of ITS CORE OPERATING LIMITS REPORT (COLR)

DOSE EQUIVALENT I-131 ENGINEERED SAFETY FEATURE (ESF)

RESPONSE

TIME INSERT 1 INSERT 2 A04 A01 A13 (continued)

SAN ONOFRE-UNIT 2 1.1-3 Amendment No. 188 l, Volume 1, Rev. 0, Page 7 of 114, Volume 1, Rev. 0, Page 7 of 114

1.1 Insert Page 1.1-3 ITS INSERT 1 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries per gram) that alone would produce the same dose when inhaled as the combined activities of iodine isotopes I-131, I-132, I-133, I-134, and I-135 actually present. The determination of DOSE EQUIVALENT I-131 shall be performed using ICRP-30, 1979, Supplement to Part 1, pages 192-212, Table titled, "Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity."

INSERT 2 DOSE EQUIVALENT XE-133 DOSE EQUIVALENT XE-133 shall be that concentration of Xe-133 (microcuries per gram) that alone would produce the same acute dose to the whole body as the combined activities of noble gas nuclides Kr-85m, Kr-85, Kr-87, Kr-88, Xe-131m, Xe-133m, Xe-133, Xe-135m, Xe-135, and Xe-138 actually present. If a specific noble gas nuclide is not detected, it should be assumed to be present at the minimum detectable activity. The determination of DOSE EQUIVALENT XE-133 shall be performed using effective dose conversion factors for air submersion listed in Table III.1 of EPA Federal Guidance report No. 12, 1993, "External Exposure to Radionuclides in Air, Water, and Soil."

A01 A13 DOSE EQUIVALENT I-131 DOSE EQUIVALENT XE-133, Volume 1, Rev. 0, Page 8 of 114, Volume 1, Rev. 0, Page 8 of 114

Definitions 1.1 1.1 Definitions ENGINEERED SAFETY measurement, response time may be verified for FEATURE (ESF) RESPONSE selected components provided that the components TIME (Continued) and methodology for verification have been previously reviewed and approved by the NRC.

LEAKAGE LEAKAGE shall be:

a.

Identified LEAKAGE 1.

LEAKAGE, such as that from pump seals or valve packing (except reactor coolant pump (RCP) leakoff), that is captured and conducted to collection systems or a sump or collecting tank; 2.

LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere with the operation of leakage detection systems or not to be pressure boundary LEAKAGE; or 3.

Reactor Coolant System (RCS) LEAKAGE through a steam generator to the Secondary System (primary to secondary LEAKAGE).

b.

Unidentified LEAKAGE All LEAKAGE that is not identified LEAKAGE.

c.

Pressure Boundary LEAKAGE LEAKAGE (except primary to secondary LEAKAGE) through a nonisolable fault in an RCS component body, pipe wall, or vessel wall.

MODE A MODE shall correspond to any one inclusive combination of core reactivity condition, power level, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Table 1.1-1 with fuel in the reactor vessel.

ITS LEAKAGE MODE (except RCP leakoff)

A11 (continued)

SAN ONOFRE-UNIT 2 1.1-4 Amendment No. 188 204 l, Volume 1, Rev. 0, Page 9 of 114, Volume 1, Rev. 0, Page 9 of 114

Definitions 1.1 1.1 Definitions OPERABLE OPERABILITY A system, subsystem, train, component, or device shall be OPERABLE when it is capable of performing its specified safety function(s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its specified safety function(s) are also capable of performing their related support function(s).

PHYSICS TESTS PHYSICS TESTS shall be those tests performed to measure the fundamental nuclear characteristics of the reactor core and related instrumentation.

These tests are:

a.

Described in Chapter 14, Initial Test Program of the SONGS Units 2 and 3 UFSAR; b.

Authorized under the provisions of 10 CFR 50.59; or c.

Otherwise approved by the Nuclear Regulatory Commission.

PRESSURE AND The PTLR is the unit specific document that TEMPERATURE LIMITS provides the reactor vessel pressure and REPORT (PTLR) temperature limits, including heatup and cooldown rates, for the current reactor vessel fluence period. These pressure and temperature limits shall be determined for each fluence period in accordance with Specification 5.7.1.6.

RATED THERMAL POWER RTP shall be a total reactor core heat transfer (RTP) rate to the reactor coolant of 3438 MWt.

REACTOR PROTECTIVE The RPS RESPONSE TIME shall be that time interval SYSTEM (RPS) RESPONSE from when the monitored parameter exceeds its RPS TIME trip setpoint at the channel sensor until electrical power to the CEAs drive mechanism is interrupted. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time ITS OPERABLE -

OPERABILITY PHYSICS TESTS PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR)

RATED THERMAL POWER (RTP)

REACTOR PROTECTIVE SYSTEM (RPS)

RESPONSE

TIME or have OPERABILITY A01 (continued)

SAN ONOFRE-UNIT 2 1.1-5 Amendment No. 188,203 l, Volume 1, Rev. 0, Page 10 of 114, Volume 1, Rev. 0, Page 10 of 114

Definitions 1.1 1.1 Definitions REACTOR PROTECTIVE may be verified for selected components provided SYSTEM (RPS) RESPONSE that the components and methodology for TIME (continued) verification have been previously reviewed and approved by the NRC.

SHUTDOWN MARGIN (SDM)

SDM shall be the instantaneous amount of reactivity by which the reactor is subcritical or would be subcritical from its present condition assuming:

a.

All full length CEAs (shutdown and regulating) are fully inserted except for the single CEA of highest reactivity worth, which is assumed to be fully withdrawn. However, with all CEAs verified fully inserted by two independent means, it is not necessary to account for a stuck CEA in the SDM calculation. With any CEAs not capable of being fully inserted, the reactivity worth of these CEAs must be accounted for in the determination of SDM, and b.

There is no change in part length CEA position.

STAGGERED TEST BASIS A STAGGERED TEST BASIS shall consist of the testing of one of the systems, subsystems, channels, or other designated components during the interval specified by the Surveillance Frequency, so that all systems, subsystems, channels, or other designated components are tested during n Surveillance Frequency intervals, where n is the total number of systems, subsystems, channels, or other designated components in the associated function.

THERMAL POWER THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant.

ITS SHUTDOWN MARGIN (SDM)

STAGGERED TEST BASIS THERMAL POWER (continued)

SAN ONOFRE--UNIT 2 1.1-6 Amendment No. 127,200 l, Volume 1, Rev. 0, Page 11 of 114, Volume 1, Rev. 0, Page 11 of 114

Definitions 1.1 Table 1.1-1 (page 1 of 1)

MODES MODE TITLE REACTIVITY CONDITION (keff)

% RATED THERMAL POWER(a)

AVERAGE REACTOR COOLANT TEMPERATURE (EF) 1 Power Operation

$ 0.99

> 5 NA 2

Startup

$ 0.99

1. 5 NA 3

Hot Standby

< 0.99 NA

$ 350 4

Hot Shutdown

< 0.99 NA 350 > Tavg > 200 5

Cold Shutdown(b)

< 0.99 NA

1. 200 6

Refueling© NA NA NA (a)

Excluding decay heat.

(b)

All reactor vessel head closure bolts fully tensioned.

© One or more reactor vessel head closure bolts less than fully tensioned.

ITS Table 1.1-1 SAN ONOFRE--UNIT 2 1.1-7 Amendment No. 127, Volume 1, Rev. 0, Page 12 of 114, Volume 1, Rev. 0, Page 12 of 114

Logical Connectors 1.2 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Specifications (TS) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TS are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and by the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action). The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

EXAMPLES The following examples illustrate the use of logical connectors.

ITS 1.2 Purpose

Background

(continued)

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))

SAN ONOFRE-UNIT 2 1.2-1 Amendment No. 127, Volume 1, Rev. 0, Page 13 of 114, Volume 1, Rev. 0, Page 13 of 114

Logical Connectors 1.2 1.2 Logical Connectors EXAMPLES EXAMPLE 1.2-1 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

LCO not met.

A.1 Verify...

AND A.2 Restore...

In this example the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.

ITS Example 1.2-1 (continued)

))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))))

SAN ONOFRE-UNIT 2 1.2-2 Amendment No. 127, Volume 1, Rev. 0, Page 14 of 114, Volume 1, Rev. 0, Page 14 of 114

Logical Connectors 1.2 1.2 Logical Connectors EXAMPLES EXAMPLE 1.2-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

LCO not met.

A.1 Trip...

OR A.2.1 Verify...

AND A.2.2.1 Reduce...

OR A.2.2.2 Perform...

OR A.3 Align...

This example represents a more complicated use of logical connectors. Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND.

Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

ITS Example 1.2-2 SAN ONOFRE-UNIT 2 1.2-3 Amendment No. 127, Volume 1, Rev. 0, Page 15 of 114, Volume 1, Rev. 0, Page 15 of 114

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Condition for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

ITS 1.3 Purpose

Background

Description s

A01 (continued)

SAN ONOFRE-UNIT 2 1.3-1 Amendment No. 127, Volume 1, Rev. 0, Page 16 of 114, Volume 1, Rev. 0, Page 16 of 114

Completion Times 1.3 1.3 Completion Times DESCRIPTION However, when a subsequent train, subsystem, component, or (continued) variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e.,

"once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.

ITS Description L01 (continued)

SAN ONOFRE-UNIT 2 1.3-2 Amendment No. 127, Volume 1, Rev. 0, Page 17 of 114, Volume 1, Rev. 0, Page 17 of 114

Completion Times 1.3 1.3 Completion Times (continued)

EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

ITS Example 1.3-1 (continued)

SAN ONOFRE-UNIT 2 1.3-3 Amendment No. 127, Volume 1, Rev. 0, Page 18 of 114, Volume 1, Rev. 0, Page 18 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours When a pump is declared inoperable, Condition A is entered.

If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Condition A and B are exited, and therefore the Required Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still inoperable, Condition A is not re-entered for the second pump. LCO 3.0.3 is entered, since the ACTIONS do not include a Condition for more than one inoperable pump.

The Completion Time clock for Condition A does not stop after LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition A.

ITS ITS Example 1.3-2 (continued)

SAN ONOFRE-UNIT 2 1.3-4 Amendment No. 127, Volume 1, Rev. 0, Page 19 of 114, Volume 1, Rev. 0, Page 19 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-2 (continued)

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for

> 7 days.

ITS (continued)

SAN ONOFRE-UNIT 2 1.3-5 Amendment No. 127, Volume 1, Rev. 0, Page 20 of 114, Volume 1, Rev. 0, Page 20 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-3 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days AND 10 days from discovery of failure to meet the LCO B.

One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 10 days from discovery of failure to meet the LCO C.

One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

OR C.2 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours ITS Example 1.3-3 L01 L01 (continued)

SAN ONOFRE-UNIT 2 1.3-6 Amendment No. 127, Volume 1, Rev. 0, Page 21 of 114, Volume 1, Rev. 0, Page 21 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES Example 1.3-3 (continued)

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e.,

initial entry into Condition A).

The Completion Times of Conditions A and B are modified by a logical connector, with a separate 10 day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO.

The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO.

This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock." In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.

ITS INSERT 3 L01 L01 (continued)

SAN ONOFRE-UNIT 2 1.3-7 Amendment No. 127, Volume 1, Rev. 0, Page 22 of 114, Volume 1, Rev. 0, Page 22 of 114

1.3 Insert Page 1.3-7 INSERT 3 It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.

L01, Volume 1, Rev. 0, Page 23 of 114, Volume 1, Rev. 0, Page 23 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-4 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One or more valves inoperable.

A.1 Restore valve(s) to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis.

Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.

Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including any extensions) expires while one or more valves are still inoperable, Condition B is entered.

ITS Example 1.3-4 (continued)

SAN ONOFRE-UNIT 2 1.3-8 Amendment No. 127, Volume 1, Rev. 0, Page 24 of 114, Volume 1, Rev. 0, Page 24 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)

ACTIONS

---

NOTE----------------------------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A.

One or more valves inoperable.

A.1 Restore valve to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours The Note above the ACTIONS table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

ITS Example 1.3-5 (continued)

SAN ONOFRE-UNIT 2 1.3-9 Amendment No. 127, Volume 1, Rev. 0, Page 25 of 114, Volume 1, Rev. 0, Page 25 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-5 (continued)

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve.

If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition B is restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One channel inoperable.

A.1 Perform SR 3.x.x.x.

OR A.2 Reduce THERMAL POWER to

1. 50% RTP.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> 8 hours B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> ITS Example 1.3-6 (continued)

SAN ONOFRE-UNIT 2 1.3-10 Amendment No. 127, Volume 1, Rev. 0, Page 26 of 114, Volume 1, Rev. 0, Page 26 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-6 (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "Once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance.

If Required Action A.1 is followed and the Required Action is not met within the Completion Time (including the 25%

extension allowed by SR 3.0.2), Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

ITS (continued)

SAN ONOFRE-UNIT 2 1.3-11 Amendment No. 127, Volume 1, Rev. 0, Page 27 of 114, Volume 1, Rev. 0, Page 27 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One subsystem inoperable.

A.1 Verify affected subsystem isolated.

AND A.2 Restore subsystem to OPERABLE status.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (including the 25% extension allowed by SR 3.0.2), Condition B is entered.

ITS Example 1.3-7 (continued)

SAN ONOFRE-UNIT 2 1.3-12 Amendment No. 127, Volume 1, Rev. 0, Page 28 of 114, Volume 1, Rev. 0, Page 28 of 114

Completion Times 1.3 1.3 Completion Times EXAMPLES EXAMPLE 1.3-7 (continued)

The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner.

ITS Immediate Completion Time SAN ONOFRE-UNIT 2 1.3-13 Amendment No. 127, Volume 1, Rev. 0, Page 29 of 114, Volume 1, Rev. 0, Page 29 of 114

Frequency 1.4 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated LCO. An understanding of the correct application of the specified Frequency is necessary for compliance with the SR.

The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Surveillance Requirement (SR) Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be performed until sometime after the associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the SR (i.e., the Surveillance or the Frequency) is stated such that it is only "required" when it can be and should be performed. With an SR satisfied, SR 3.0.4 imposes no restriction.

EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.

ITS Purpose Description Examples 1.4 INSERT 4 INSERT 5 A06 A06 (continued)

SAN ONOFRE-UNIT 2 1.4-1 Amendment No. 127, Volume 1, Rev. 0, Page 30 of 114, Volume 1, Rev. 0, Page 30 of 114

1.4 Insert Page 1.4-1 INSERT 4 Sometimes special situations dictate when the requirements of a Surveillance are to be met.

They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both.

INSERT 5 The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria.

Some Surveillances contain Notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:

a.

The Surveillance is not required to be met in the MODE or other specified condition to be entered; or

b.

The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or

c.

The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.

Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.

A06 A06, Volume 1, Rev. 0, Page 31 of 114, Volume 1, Rev. 0, Page 31 of 114

Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-1 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />) during which the associated Surveillance must be performed at least one time.

Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, an extension of the time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the equipment is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then SR 3.0.3 becomes applicable.

If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of SR 3.0.4.

Example 1.4-1 INSERT 6 A07 (continued)

SAN ONOFRE-UNIT 2 1.4-2 Amendment No. 127, Volume 1, Rev. 0, Page 32 of 114, Volume 1, Rev. 0, Page 32 of 114

1.4 Insert Page 1.4-2 INSERT 6 then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the MODE or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable.

A07, Volume 1, Rev. 0, Page 33 of 114, Volume 1, Rev. 0, Page 33 of 114

Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-2 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits.

Once within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after

$ 25% RTP AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> thereafter Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, and the second is of the type shown in Example 1.4-1. The logical connector "AND" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level < 25% RTP to

$ 25% RTP, the Surveillance must be performed within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

The use of "once" indicates a single performance will satisfy the specified Frequency (assuming no other Frequencies are connected by "AND"). This type of Frequency does not qualify for the 25% extension allowed by SR 3.0.2.

"Thereafter" indicates future performances must be established per SR 3.0.2, but only after a specified condition is first met (i.e., the "once" performance in this example). If reactor power decreases to < 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.

Example 1.4-2 (continued)

SAN ONOFRE-UNIT 2 1.4-3 Amendment No. 127, Volume 1, Rev. 0, Page 34 of 114, Volume 1, Rev. 0, Page 34 of 114

Frequency 1.4 1.4 Frequency EXAMPLES EXAMPLE 1.4-3 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE------------------

Not required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after $ 25% RTP.

Perform channel adjustment.

7 days The interval continues, whether or not the unit operation is

< 25% RTP between performances.

As the Note modifies the required performance of the Surveillance, it is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is < 25% RTP, this Note allows 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after power reaches $ 25% RTP to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency." Therefore, if the Surveillance were not performed within the 7 day (plus 25% per SR 3.0.2) interval, but operation was < 25% RTP, it would not constitute a failure of the SR or failure to meet the LCO.

Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not exceed 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> with power $ 25% RTP.

Once the unit reaches 25% RTP, 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> would be allowed for completing the Surveillance. If the Surveillance were not performed within this 12 hour1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> interval, there would then be a failure to perform a Surveillance within the specified Frequency; MODE changes then would be restricted in accordance with SR 3.0.4 and the provisions of SR 3.0.3 would apply.

Example 1.4-3 the extension allowed by INSERT 7 plus the extension allowed by SR 3.0.2 plus the extension allowed by SR 3.0.2 A09 A08 A09 A10 A06 SAN ONOFRE-UNIT 2 1.4-4 Amendment No. 127, Volume 1, Rev. 0, Page 35 of 114, Volume 1, Rev. 0, Page 35 of 114

1.4 Insert Page 1.4-4a INSERT 7 EXAMPLE 1.4-4 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be met in MODE 1.

Verify leakage rates are within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

A06, Volume 1, Rev. 0, Page 36 of 114, Volume 1, Rev. 0, Page 36 of 114

1.4 Insert Page 1.4-4b INSERT 7 (continued) 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be performed in MODE 1.

Perform complete cycle of the valve.

7 days The interval continues, whether or not the unit operation is in MODE 1, 2, or 3 (the assumed Applicability of the associated LCO) between performances.

As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1.

Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1.

Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.

A06, Volume 1, Rev. 0, Page 37 of 114, Volume 1, Rev. 0, Page 37 of 114

1.4 Insert Page 1.4-4c INSERT 7 (continued) 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Not required to be met in MODE 3.

Verify parameter is within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

A06, Volume 1, Rev. 0, Page 38 of 114, Volume 1, Rev. 0, Page 38 of 114

Definitions 1.1 1.0 USE AND APPLICATION 1.1 Definitions

---

NOTE-------------------------------------

The defined terms of this section appear in capitalized type and are applicable throughout these Technical Specifications and Bases.

Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.

AXIAL SHAPE INDEX (ASI)

ASI shall be the power generated in the lower half of the core less the power generated in the upper half of the core, divided by the sum of the power generated in the lower and upper halves of the core.

AZIMUTHAL POWER TILT AZIMUTHAL POWER TILT shall be the power asymmetry (Tq) between azimuthally symmetric fuel assemblies.

CHANNEL CALIBRATION A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel output such that it responds within the necessary range and accuracy to known values of the parameter that the channel monitors. The CHANNEL CALIBRATION shall encompass the entire channel, including the required sensor, alarm, display, and trip functions, and shall include the CHANNEL FUNCTIONAL TEST. Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an inplace cross calibration of the sensing elements and normal calibration of the remaining adjustable devices in the channel. Whenever a sensing element is replaced, the next required inplace cross calibration consists of comparing the other sensing elements with the recently installed sensing element.

1.1 NOTE ACTIONS AXIAL SHAPE INDEX (ASI)

AZIMUTHAL POWER TILT (Tq)

CHANNEL CALIBRATION all devices in the channel required for channel OPERABILITY and qualitative assessment of sensor behavior A02 A12 LA01 (continued)

SAN ONOFRE-UNIT 3 1.1-1 Amendment No. 116, Volume 1, Rev. 0, Page 39 of 114, Volume 1, Rev. 0, Page 39 of 114

Definitions 1.1 1.1 Definitions ITS 1.1 CHANNEL CALIBRATION The CHANNEL CALIBRATION may be performed by means (continued) of any series of sequential, overlapping, or total channel steps so that the entire channel is calibrated.

CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter.

CHANNEL FUNCTIONAL TEST A CHANNEL FUNCTIONAL TEST shall be:

a.

Analog channels the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY, including required alarms, interlocks, display and trip functions; b.

Bistable channels (e.g., pressure switches and switch contacts) the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY, including required alarm and trip functions; or c.

Digital computer channels the use of diagnostic programs to test digital computer hardware and the injection of simulated process data into the channel to verify OPERABILITY, including alarm and trip functions.

The CHANNEL FUNCTIONAL TEST may be performed by means of any series of sequential, overlapping, or total channel steps so that the entire channel is tested.

CORE ALTERATION CORE ALTERATION shall be the movement or manipulation of any fuel, sources, reactivity control components, or other components, excluding control element assemblies (CEAs) withdrawn into the upper guide structure, affecting reactivity, CHANNEL CALIBRATION CHANNEL CHECK CHANNEL FUNCTIONAL TEST and bistable of all devices in the channel required for channel OPERABILITY, and b.

of all devices in the channel required for channel OPERABILITY A05 A03 A03 A03 A03 A05 A04 (continued)

SAN ONOFRE-UNIT 3 1.1-2 Amendment No. 116, Volume 1, Rev. 0, Page 40 of 114, Volume 1, Rev. 0, Page 40 of 114

Definitions 1.1 1.1 Definitions ITS 1.1 CORE ALTERATION within the reactor vessel with the vessel head (continued) removed and fuel in the vessel. Suspension of CORE ALTERATIONS shall not preclude completion of movement of a component to a safe position.

CORE OPERATING LIMITS The COLR is the unit specific document that REPORT (COLR) provides cycle specific parameter limits for the current reload cycle. These cycle specific parameter limits shall be determined for each reload cycle in accordance with Specification 5.7.1.5. Plant operation within these limits is addressed in individual Specifications.

DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries/gram) that alone would produce the same thyroid dose as the quantity and isotopic mixture of I-131, I-132, I-133, I-134, and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in ICRP-30, Supplement to Part 1, pages 192-212, Tables titled, Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity.

E AVERAGE E shall be the average (weighted in proportion DISINTEGRATION ENERGY to the concentration of each radionuclide in the reactor coolant at the time of sampling) of the sum of the average beta and gamma energies per disintegration (in MeV) for isotopes, other than iodines, with half lives > 15 minutes, making up at least 95% of the total noniodine activity in the coolant.

ENGINEERED SAFETY The ESF RESPONSE TIME shall be that time interval FEATURE (ESF) RESPONSE from when the monitored parameter exceeds its ESF TIME actuation setpoint at the channel sensor until the ESF equipment is capable of performing its safety function (i.e., the valves travel to their required positions, pump discharge pressures reach their required values, etc.). Times shall include diesel generator starting and sequence loading delays, where applicable. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of CORE OPERATING LIMITS REPORT (COLR)

DOSE EQUIVALENT I-131 ENGINEERED SAFETY FEATURE (ESF)

RESPONSE

TIME INSERT 1 INSERT 2 A04 A01 A13 (continued)

SAN ONOFRE--UNIT 3 1.1-3 Amendment No. 179 l, Volume 1, Rev. 0, Page 41 of 114, Volume 1, Rev. 0, Page 41 of 114

1.1 Insert Page 1.1-3 ITS INSERT 1 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries per gram) that alone would produce the same dose when inhaled as the combined activities of iodine isotopes I-131, I-132, I-133, I-134, and I-135 actually present. The determination of DOSE EQUIVALENT I-131 shall be performed using ICRP-30, 1979, Supplement to Part 1, pages 192-212, Table titled, "Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity."

INSERT 2 DOSE EQUIVALENT XE-133 DOSE EQUIVALENT XE-133 shall be that concentration of Xe-133 (microcuries per gram) that alone would produce the same acute dose to the whole body as the combined activities of noble gas nuclides Kr-85m, Kr-85, Kr-87, Kr-88, Xe-131m, Xe-133m, Xe-133, Xe-135m, Xe-135, and Xe-138 actually present. If a specific noble gas nuclide is not detected, it should be assumed to be present at the minimum detectable activity. The determination of DOSE EQUIVALENT XE-133 shall be performed using effective dose conversion factors for air submersion listed in Table III.1 of EPA Federal Guidance report No. 12, 1993, "External Exposure to Radionuclides in Air, Water, and Soil."

A01 A13 DOSE EQUIVALENT I-131 DOSE EQUIVALENT XE-133, Volume 1, Rev. 0, Page 42 of 114, Volume 1, Rev. 0, Page 42 of 114

Definitions 1.1 1.1 Definitions ITS 1.1 ENGINEERED SAFETY measurement, response time may be verified for FEATURE (ESF) RESPONSE selected components provided that the components TIME (Continued) and methodology for verification have been previously reviewed and approved by the NRC.

LEAKAGE LEAKAGE shall be:

a.

Identified LEAKAGE 1.

LEAKAGE, such as that from pump seals or valve packing (except reactor coolant pump (RCP) leakoff), that is captured and conducted to collection systems or a sump or collecting tank; 2.

LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere with the operation of leakage detection systems or not to be pressure boundary LEAKAGE; or 3.

Reactor Coolant System (RCS) LEAKAGE through a steam generator to the Secondary System (primary to secondary LEAKAGE).

b.

Unidentified LEAKAGE All LEAKAGE that is not identified LEAKAGE.

c.

Pressure Boundary LEAKAGE LEAKAGE (except primary to secondary LEAKAGE) through a nonisolable fault in an RCS component body, pipe wall, or vessel wall.

MODE A MODE shall correspond to any one inclusive combination of core reactivity condition, power level, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Table 1.1-1 with fuel in the reactor vessel.

ENGINEERED SAFETY FEATURE (ESF)

RESPONSE

TIME LEAKAGE MODE (except RCP leakoff)

A11 (continued)

SAN ONOFRE-UNIT 3 1.1-4 Amendment No. 179,196 l, Volume 1, Rev. 0, Page 43 of 114, Volume 1, Rev. 0, Page 43 of 114

Definitions 1.1 1.1 Definitions ITS 1.1 OPERABLE OPERABILITY A system, subsystem, train, component, or device shall be OPERABLE when it is capable of performing its specified safety function(s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its specified safety function(s) are also capable of performing their related support function(s).

PHYSICS TESTS PHYSICS TESTS shall be those tests performed to measure the fundamental nuclear characteristics of the reactor core and related instrumentation.

These tests are:

a.

Described in Chapter 14, Initial Test Program of the SONGS Units 2 and 3 UFSAR; b.

Authorized under the provisions of 10 CFR 50.59; or c.

Otherwise approved by the Nuclear Regulatory Commission.

RCS PRESSURE AND The PTLR is the unit specific document that TEMPERATURE LIMITS provides the reactor vessel pressure and REPORT (PTLR) temperature limits, including heatup and cooldown rates, for the current reactor vessel fluence period. These pressure and temperature limits shall be determined for each fluence period in accordance with Specification 5.7.1.6.

RATED THERMAL POWER RTP shall be a total reactor core heat transfer (RTP) rate to the reactor coolant of 3438 MWt.

REACTOR PROTECTIVE The RPS RESPONSE TIME shall be that time interval SYSTEM (RPS) RESPONSE from when the monitored parameter exceeds its RPS TIME trip setpoint at the channel sensor until electrical power to the CEAs drive mechanism is interrupted. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time may be verified for selected components provided OPERABLE -

OPERABILITY PHYSICS TESTS PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR)

RATED THERMAL POWER (RTP)

REACTOR PROTECTIVE SYSTEM (RPS)

RESPONSE

TIME or have OPERABILITY A01 A01 (continued)

SAN ONOFRE--UNIT 3 1.1-5 Amendment No. 179,195 l, Volume 1, Rev. 0, Page 44 of 114, Volume 1, Rev. 0, Page 44 of 114

Definitions 1.1 1.1 Definitions ITS 1.1 REACTOR PROTECTIVE that the components and methodology for SYSTEM (RPS) RESPONSE verification have been previously reviewed and TIME (continued) approved by the NRC.

SHUTDOWN MARGIN (SDM)

SDM shall be the instantaneous amount of reactivity by which the reactor is subcritical or would be subcritical from its present condition assuming:

a.

All full length CEAs (shutdown and regulating) are fully inserted except for the single CEA of highest reactivity worth, which is assumed to be fully withdrawn. However, with all CEAs verified fully inserted by two independent means, it is not necessary to account for a stuck CEA in the SDM calculation. With any CEAs not capable of being fully inserted, the reactivity worth of these CEAs must be accounted for in the determination of SDM, and b.

There is no change in part length CEA position.

With any CEAs not capable of being fully inserted, the reactivity worth of these CEAs must be accounted for in the determination of SDM.

STAGGERED TEST BASIS A STAGGERED TEST BASIS shall consist of the testing of one of the systems, subsystems, channels, or other designated components during the interval specified by the Surveillance Frequency, so that all systems, subsystems, channels, or other designated components are tested during n Surveillance Frequency intervals, where n is the total number of systems, subsystems, channels, or other designated components in the associated function.

THERMAL POWER THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant.

REACTOR PROTECTIVE SYSTEM (RPS)

RESPONSE

TIME SHUTDOWN MARGIN (SDM)

STAGGERED TEST BASIS THERMAL POWER SAN ONOFRE--UNIT 3 1.1-6 Amendment No. 116,191 l, Volume 1, Rev. 0, Page 45 of 114, Volume 1, Rev. 0, Page 45 of 114

Definitions 1.1 Table 1.1-1 (page 1 of 1)

MODES MODE TITLE REACTIVITY CONDITION (keff)

% RATED THERMAL POWER(a)

AVERAGE REACTOR COOLANT TEMPERATURE (EF) 1 Power Operation

$ 0.99

> 5 NA 2

Startup

$ 0.99

1. 5 NA 3

Hot Standby

< 0.99 NA

$ 350 4

Hot Shutdown

< 0.99 NA 350 > Tavg > 200 5

Cold Shutdown(b)

< 0.99 NA

1. 200 6

Refueling© NA NA NA (a)

Excluding decay heat.

(b)

All reactor vessel head closure bolts fully tensioned.

© One or more reactor vessel head closure bolts less than fully tensioned.

Table 1.1-1 SAN ONOFRE-UNIT 3 1.1-7 Amendment No. 116, Volume 1, Rev. 0, Page 46 of 114, Volume 1, Rev. 0, Page 46 of 114

Logical Connectors 1.2 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Specifications (TS) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TS are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and by the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action). The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

EXAMPLES The following examples illustrate the use of logical connectors.

ITS Purpose

Background

(continued)

SAN ONOFRE--UNIT 3 1.2-1 Amendment No. 116, Volume 1, Rev. 0, Page 47 of 114, Volume 1, Rev. 0, Page 47 of 114

Logical Connectors 1.2 1.2 Logical Connectors EXAMPLES EXAMPLE 1.2-1 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

LCO not met.

A.1 Verify...

AND A.2 Restore...

In this example the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.

Example 1.2-1 (continued)

SAN ONOFRE--UNIT 3 1.2-2 Amendment No. 116, Volume 1, Rev. 0, Page 48 of 114, Volume 1, Rev. 0, Page 48 of 114

Logical Connectors 1.2 1.2 Logical Connectors EXAMPLES EXAMPLE 1.2-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

LCO not met.

A.1 Trip...

OR A.2.1 Verify...

AND A.2.2.1 Reduce...

OR A.2.2.2 Perform...

OR A.3 Align...

This example represents a more complicated use of logical connectors. Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND.

Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

Example 1.2-2 SAN ONOFRE--UNIT 3 1.2-3 Amendment No. 116, Volume 1, Rev. 0, Page 49 of 114, Volume 1, Rev. 0, Page 49 of 114

Completion Times 1.3 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Condition for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

1.3 Purpose

Background

Description s

A01 (continued)

SAN ONOFRE--UNIT 3 1.3-1 Amendment No. 116, Volume 1, Rev. 0, Page 50 of 114, Volume 1, Rev. 0, Page 50 of 114

1.3 Completion Times (continued)

Completion Times

1.3 DESCRIPTION

However, when a subsequent train, subsystem, component, or (continued) variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability; and b.

Must remain inoperable or not within limits after the first inoperability is resolved.

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />; or b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e.,

"once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..." Example 1.3-3 illustrates one use of this type of Completion Time. The 10 day Completion Time specified for Conditions A and B in Example 1.3-3 may not be extended.

Description L01 (continued)

SAN ONOFRE--UNIT 3 1.3-2 Amendment No. 116, Volume 1, Rev. 0, Page 51 of 114, Volume 1, Rev. 0, Page 51 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

Example 1.3-1 (continued)

SAN ONOFRE--UNIT 3 1.3-3 Amendment No. 116, Volume 1, Rev. 0, Page 52 of 114, Volume 1, Rev. 0, Page 52 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-2 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours When a pump is declared inoperable, Condition A is entered.

If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Condition A and B are exited, and therefore the Required Actions of Condition B may be terminated.

When a second pump is declared inoperable while the first pump is still inoperable, Condition A is not re-entered for the second pump. LCO 3.0.3 is entered, since the ACTIONS do not include a Condition for more than one inoperable pump.

The Completion Time clock for Condition A does not stop after LCO 3.0.3 is entered, but continues to be tracked from the time Condition A was initially entered.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition A.

Example 1.3-2 (continued)

SAN ONOFRE--UNIT 3 1.3-4 Amendment No. 116, Volume 1, Rev. 0, Page 53 of 114, Volume 1, Rev. 0, Page 53 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-2 (continued)

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for

> 7 days.

Example 1.3-1 (continued)

SAN ONOFRE--UNIT 3 1.3-5 Amendment No. 116, Volume 1, Rev. 0, Page 54 of 114, Volume 1, Rev. 0, Page 54 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-3 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days AND 10 days from discovery of failure to meet the LCO B.

One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> AND 10 days from discovery of failure to meet the LCO C.

One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

OR C.2 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours Example 1.3-3 L01 L01 (continued)

SAN ONOFRE--UNIT 3 1.3-6 Amendment No. 116, Volume 1, Rev. 0, Page 55 of 114, Volume 1, Rev. 0, Page 55 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES Example 1.3-3 (continued)

When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e.,

initial entry into Condition A).

The Completion Times of Conditions A and B are modified by a logical connector, with a separate 10 day Completion Time measured from the time it was discovered the LCO was not met. In this example, without the separate Completion Time, it would be possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO.

The separate Completion Time modified by the phrase "from discovery of failure to meet the LCO" is designed to prevent indefinite continued operation while not meeting the LCO.

This Completion Time allows for an exception to the normal "time zero" for beginning the Completion Time "clock." In this instance, the Completion Time "time zero" is specified as commencing at the time the LCO was initially not met, instead of at the time the associated Condition was entered.

Example 1.3-3 INSERT 3 L01 L01 (continued)

SAN ONOFRE--UNIT 3 1.3-7 Amendment No. 116, Volume 1, Rev. 0, Page 56 of 114, Volume 1, Rev. 0, Page 56 of 114

1.3 Insert Page 1.3-7 INSERT 3 It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.

L01, Volume 1, Rev. 0, Page 57 of 114, Volume 1, Rev. 0, Page 57 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-4 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One or more valves inoperable.

A.1 Restore valve(s) to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis.

Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.

Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including any extensions) expires while one or more valves are still inoperable, Condition B is entered.

Example 1.3-4 (continued)

SAN ONOFRE--UNIT 3 1.3-8 Amendment No. 116, Volume 1, Rev. 0, Page 58 of 114, Volume 1, Rev. 0, Page 58 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-5 (continued)

ACTIONS

---

NOTE----------------------------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A.

One or more valves inoperable.

A.1 Restore valve to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours The Note above the ACTIONS table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

Example 1.3-5 (continued)

SAN ONOFRE--UNIT 3 1.3-9 Amendment No. 116, Volume 1, Rev. 0, Page 59 of 114, Volume 1, Rev. 0, Page 59 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-5 (continued)

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve.

If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition B is restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One channel inoperable.

A.1 Perform SR 3.x.x.x.

OR A.2 Reduce THERMAL POWER to

1. 50% RTP.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> 8 hours B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Example 1.3-5 Example 1.3-6 (continued)

SAN ONOFRE--UNIT 3 1.3-10 Amendment No. 116, Volume 1, Rev. 0, Page 60 of 114, Volume 1, Rev. 0, Page 60 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-6 (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "Once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance.

If Required Action A.1 is followed and the Required Action is not met within the Completion Time (including the 25%

extension allowed by SR 3.0.2), Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

Example 1.3-6 (continued)

SAN ONOFRE--UNIT 3 1.3-11 Amendment No. 116, Volume 1, Rev. 0, Page 61 of 114, Volume 1, Rev. 0, Page 61 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-7 (continued)

ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A.

One subsystem inoperable.

A.1 Verify affected subsystem isolated.

AND A.2 Restore subsystem to OPERABLE status.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> B.

Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (including the 25% extension allowed by SR 3.0.2), Condition B is entered.

Example 1.3-7 (continued)

SAN ONOFRE--UNIT 3 1.3-12 Amendment No. 116, Volume 1, Rev. 0, Page 62 of 114, Volume 1, Rev. 0, Page 62 of 114

1.3 Completion Times (continued)

Completion Times 1.3 EXAMPLES EXAMPLE 1.3-7 (continued)

The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the COMPLETION TIME Required Action should be pursued without delay and in a controlled manner.

Example 1.3-7 Immediate Completion Time SAN ONOFRE--UNIT 3 1.3-13 Amendment No. 116, Volume 1, Rev. 0, Page 63 of 114, Volume 1, Rev. 0, Page 63 of 114

Frequency 1.4 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated LCO. An understanding of the correct application of the specified Frequency is necessary for compliance with the SR.

The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0, Surveillance Requirement (SR) Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be performed until sometime after the associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the SR (i.e., the Surveillance or the Frequency) is stated such that it is only "required" when it can be and should be performed. With an SR satisfied, SR 3.0.4 imposes no restriction.

EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.

ITS Purpose Description Examples 1.4 INSERT 4 INSERT 5 A06 A06 (continued)

SAN ONOFRE--UNIT 3 1.4-1 Amendment No. 116, Volume 1, Rev. 0, Page 64 of 114, Volume 1, Rev. 0, Page 64 of 114

1.4 Insert Page 1.4-1 INSERT 4 Sometimes special situations dictate when the requirements of a Surveillance are to be met.

They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillance, or both.

INSERT 5 The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria.

Some Surveillances contain Notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:

a.

The Surveillance is not required to be met in the MODE or other specified condition to be entered; or

b.

The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or

c.

The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.

Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.

A06 A06, Volume 1, Rev. 0, Page 65 of 114, Volume 1, Rev. 0, Page 65 of 114

1.4 Frequency (continued)

Frequency 1.4 EXAMPLES EXAMPLE 1.4-1 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />) during which the associated Surveillance must be performed at least one time.

Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, an extension of the time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the equipment is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then SR 3.0.3 becomes applicable.

If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, the Surveillance must be performed within the Frequency requirements of SR 3.0.2 prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of SR 3.0.4.

Example 1.4-1 INSERT 6 A07 (continued)

SAN ONOFRE--UNIT 3 1.4-2 Amendment No. 116, Volume 1, Rev. 0, Page 66 of 114, Volume 1, Rev. 0, Page 66 of 114

1.4 Insert Page 1.4-2 INSERT 6 then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the MODE or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable.

A07, Volume 1, Rev. 0, Page 67 of 114, Volume 1, Rev. 0, Page 67 of 114

1.4 Frequency (continued)

Frequency 1.4 EXAMPLES EXAMPLE 1.4-2 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits.

Once within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after

$ 25% RTP AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> thereafter Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, and the second is of the type shown in Example 1.4-1. The logical connector "AND" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level < 25% RTP to

$ 25% RTP, the Surveillance must be performed within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

The use of "once" indicates a single performance will satisfy the specified Frequency (assuming no other Frequencies are connected by "AND"). This type of Frequency does not qualify for the 25% extension allowed by SR 3.0.2.

"Thereafter" indicates future performances must be established per SR 3.0.2, but only after a specified condition is first met (i.e., the "once" performance in this example). If reactor power decreases to < 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.

Example 1.4-2 (continued)

SAN ONOFRE--UNIT 3 1.4-3 Amendment No. 116, Volume 1, Rev. 0, Page 68 of 114, Volume 1, Rev. 0, Page 68 of 114

1.4 Frequency (continued)

Frequency 1.4 EXAMPLES EXAMPLE 1.4-3 (continued)

SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE------------------

Not required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after $ 25% RTP.

Perform channel adjustment.

7 days The interval continues, whether or not the unit operation is

< 25% RTP between performances.

As the Note modifies the required performance of the Surveillance, it is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is < 25% RTP, this Note allows 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after power reaches $ 25% RTP to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency." Therefore, if the Surveillance were not performed within the 7 day (plus 25% per SR 3.0.2) interval, but operation was < 25% RTP, it would not constitute a failure of the SR or failure to meet the LCO.

Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not exceed 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> with power $ 25% RTP.

Once the unit reaches 25% RTP, 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> would be allowed for completing the Surveillance. If the Surveillance were not performed within this 12 hour1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> interval, there would then be a failure to perform a Surveillance within the specified Frequency; MODE changes then would be restricted in accordance with SR 3.0.4 and the provisions of SR 3.0.3 would apply.

Example 1.4-3 the extension allowed by INSERT 7 plus the extension allowed by SR 3.0.2 plus the extension allowed by SR 3.0.2 A08 A09 A09 A06 A10 SAN ONOFRE--UNIT 3 1.4-4 Amendment No. 116, Volume 1, Rev. 0, Page 69 of 114, Volume 1, Rev. 0, Page 69 of 114

1.4 Insert Page 1.4-4a INSERT 7 EXAMPLE 1.4-4 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be met in MODE 1.

Verify leakage rates are within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

A06, Volume 1, Rev. 0, Page 70 of 114, Volume 1, Rev. 0, Page 70 of 114

1.4 Insert Page 1.4-4b INSERT 7 (continued) 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be performed in MODE 1.

Perform complete cycle of the valve.

7 days The interval continues, whether or not the unit operation is in MODE 1, 2, or 3 (the assumed Applicability of the associated LCO) between performances.

As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1.

Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1.

Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.

A06, Volume 1, Rev. 0, Page 71 of 114, Volume 1, Rev. 0, Page 71 of 114

1.4 Insert Page 1.4-4c INSERT 7 (continued) 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Not required to be met in MODE 3.

Verify parameter is within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-6 specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

A06, Volume 1, Rev. 0, Page 72 of 114, Volume 1, Rev. 0, Page 72 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 1 of 7 ADMINISTRATIVE CHANGES A01 In the conversion of the San Onofre Nuclear Generating Station (SONGS)

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-1432, Rev. 3.0, "Standard Technical Specifications-Combustion Engineering Plants" (ISTS) and additional approved Technical Specification Task Force (TSTF) travelers included in the submittal.

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

A02 The CTS definition of CHANNEL CALIBRATION states in part, "The CHANNEL CALIBRATION shall encompass the entire channel including the required sensor, alarm, display, and trip functions." The ITS definition of CHANNEL CALIBRATION states in part, "The CHANNEL CALIBRATION shall encompass all devices in the channel required for channel OPERABILITY..." This changes the CTS by specifying that all devices needed for OPERABILITY are required, in lieu of specifying the individual types of devices.

The replacement in the CTS of "the entire channel, including the required sensor, alarm, display, and trip functions" with wording in the ITS, "all devices in the channel required for OPERABILITY" is acceptable because the statements are equivalent in that both require that all needed portions of the channel be tested.

This change reflects the CTS understanding that the CHANNEL CALIBRATION includes only those portions of the channel needed to perform the safety function. There is ambiguity in the application of the word "required" and whether the list is inclusive or representative. Therefore, this list has been replaced with, "all devices in the channel required for channel OPERABILITY." This clarifies the use of the word "required" and makes clear that the components that are required to be tested or calibrated are only those that are necessary for the channel to perform its safety function. This change will clarify the requirements and allow for consistent application of the definitions, tests, and calibrations.

This change is consistent with TSTF-205. This change is designated as administrative because it does not result in a technical change to the Technical Specifications.

A03 The CTS definition of CHANNEL FUNCTIONAL TEST list separately descriptions of tests for analog channels, bistable channels, and digital computer channels.

The CTS definition also states in part that the test includes, "required alarms, interlocks, display and trip functions." The ITS definition combines the descriptions of analog and bistable channels. The ITS also replaces the reference to "including required alarms, interlocks, display and trip functions,"

with the statement, "all devices in the channel required for channel OPERABILITY." The CTS will be changed to combine the Analog and Bistable Channels and replace reference to "including required alarms, interlocks, display and trip functions," with the statement, "all devices in the channel required for channel OPERABILITY."

, Volume 1, Rev. 0, Page 73 of 114, Volume 1, Rev. 0, Page 73 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 2 of 7 This change is acceptable because the CHANNEL FUNCTIONAL TEST definition for analog channels and bistable channels are the same. The only difference in the CTS is that the bistable definition contains examples of bistable channels. The deletion of the bistable channel examples does not alter the definition. Replacing reference to what each definition includes with an overall statement to test all devices in the channel required for channel OPERABILITY allows does not change what is tested, but ensures no devices are excluded.

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

A04 The CTS contain a Definition of Core Alteration. The ITS do not contain this definition. This changes the CTS by deleting this definition.

This change is acceptable because the term is not used as a defined term in the ITS. Discussion of any technical changes related to the deletion of this term is included in the DOCs for the CTS Section in which the term is used. This change is designated as administrative because it eliminates a defined term that is no longer used.

A05 The CTS definition of CHANNEL CALIBRATION states that it may be performed by means of any series of sequential, overlapping, or total channel steps, "so that the entire channel is calibrated." The ITS definition does not contain, "so that the entire channel is calibrated." The CTS will be changed to exclude this statement.

This proposed deletion to the CTS removes the conflict between the verbatim reading of the definition where it is stated "... of all devices in the channel required for channel OPERABILITY..." and the flexibility of testing permitting a "...

successful test to be the verification of the change of state of a single contact of the relay..." as stated in the individual Bases for the CHANNEL CALIBRATION SRs. This change is designated as administrative because it does not result in a technical change to the Technical Specifications.

A06 CTS Section 1.4 does not contain a discussion and examples on the use of "met" and "perform" exceptions. ITS Section 1.4 contains a discussion and examples of the use of "met" and "performed" exceptions consistent with TSTF-284. CTS Section 1.4 will be revised to add a discussion and examples (1.4-4, 1.4-5, and 1.4-6) of the "met" and "performed" exceptions.

This change revises SRs throughout the TS, as necessary, to appropriately clarify the use of "met" and "perform" exceptions. Similarly, the Writer's Guide provides a distinction between these phrases. The SONGS CTS do not contain this detail; however, various locations throughout the TS provide Notes with "met" and "performed" distinctions. This change does not change the intent of any SR Note. This proposed change will provide for better use, application, and understanding of these Notes. With this clarification, several exceptions that are unclear or have incorrect usage of "met" and "perform" are also corrected. This change clarifies the CTS and does not change the intent, and is therefore designated as administrative.

A07 The second paragraph of the CTS 1.4-1 example discussion states that "the Surveillance must be performed within the Frequency requirements of SR 3.0.2, Volume 1, Rev. 0, Page 74 of 114, Volume 1, Rev. 0, Page 74 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 3 of 7 prior to entry into the MODE or other specified condition. Failure to do so would result in a violation of SR 3.0.4." The ITS states "then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the MODE or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable." This changes the CTS by incorporating the changes of TSTF-485.

The Example 1.4-1, second paragraph discussion is modified to parallel the discussion in the previous paragraph. The previous paragraph discusses Surveillances that exceed the interval without being performed while in the Applicability. The second paragraph is modified to make a similar statement regarding Surveillances that exceed the interval while not being in the Applicability. The second sentence of the second paragraph is modified to reference the provisions of SR 3.0.3. This is necessary as TSTF-359 modifies SR 3.0.4 to recognize that performance of a missed Surveillance may have been extended and prior to performance of the missed Surveillance, but within the time permitted under SR 3.0.3, a MODE change occurs. This change clarifies the TS and thus is administrative.

A08 CTS Section 1.4, Example 1.4-3 contains, in part, the words, plus "25% per" ITS Section 1.4, Example 1.4-3 contains, in part, the words, plus "the extension allowed by" This proposed change to CTS Section 1.4, Example 1.4-3 replaces the words "plus 25% per SR 3.0.2" with the words "plus the extension allowed by SR 3.0.2."

This change is for clarification only to be consistent with NUREG-1432. The intent of the example is not changed, thus this change is administrative.

A09 CTS 1.4, Example 1.4-3 contains a discussion of the SR Frequency, but does not clarify that the 3.0.2 allowances apply to frequencies in Notes in the Surveillance column. ITS 1.4, Example 1.4-3 discussion contains this clarification.

Specifically, Example 1.4-3 is being revised to clarify the applicability of the 25%

allowance of SR 3.0.2 to time periods discussed in NOTES in the "SURVEILLANCE" column as well as to time periods in the "FREQUENCY" column. This is accomplished by adding the phrase "(plus the extension allowed by SR 3.0.2)" in two additional places in the discussion for Example 1.4-3.

The "specified Frequency" includes time periods discussed in Notes in the "Surveillance" column, in addition to time periods listed in the "Frequency" column, as stated in the second paragraph for this example. Therefore, the provisions of SR 3.0.2 (which permit a 25% grace period to facilitate surveillance scheduling and avoid plant operating conditions that may not be suitable for conducting the test) also apply to the time periods listed in Notes in the "SURVEILLANCE" column. This is because SR 3.0.2 states that "The specified Frequency (emphasis added) for each SR is met if the Surveillance is performed within 1.25 times the interval specified" Therefore, Example 1.4-3 is revised to be consistent with the above statements. The Example currently explicitly recognizes that the 25% extension allowed by SR 3.0.2 is applicable to the time period listed in the "FREQUENCY" column, but it does not explicitly recognize that the SR 3.0.2 extension is applicable to the time period listed in the NOTE in, Volume 1, Rev. 0, Page 75 of 114, Volume 1, Rev. 0, Page 75 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 4 of 7 the "SURVEILLANCE" column. The change to the Example provides this explicit recognition by copying the phrase "(plus the extension allowed by SR 3.0.2)" in two additional portions of the discussion for this Example. This change clarifies the Example without changing the intent and is therefore an administrative change.

A10 CTS Section 1.4, Example 1.4-3 contains, in part, the words, "MODE changes then would be restricted in accordance with SR 3.0.4." ITS Section 1.4, Example 1.4-3 does not contain these words. This proposed change to CTS Section 1.4, Example 1.4-3 deletes the words "MODE changes then would be restricted in accordance with SR 3.0.4."

These words are being deleted from a discussion in the Example concerning Surveillance Requirements not completed within the specified Frequency. SR 3.0.4 is the SR Applicability requirement for this situation and adequately covers the requirements. It is not necessary to provide the cross reference to the applicable SR. This change does not change the intent of the Example and makes the San Onofre discussion consistent with NUREG-1432. This clarification change is therefore administrative.

A11 The CTS definition of Unidentified LEAKAGE is "All LEAKAGE that is not identified LEAKAGE." The ITS definition of Unidentified LEAKAGE is "All LEAKAGE (except RCP leakoff) that is not identified LEAKAGE." This changes the CTS by specifically including the RCP leakoff exception to the Unidentified LEAKAGE definition.

This change adds an exception to RCP leakoff to the definition of Unidentified LEAKAGE consistent with NUREG-1432, as revised by the NRC approved TSTF-040. The exception for controlled leakage from NUREG-0123 was revised in the definition of identified LEAKAGE but not in the definition of Unidentified LEAKAGE. This is considered a change to make the different LEAKAGE definitions consistent and as such it is considered an administrative change.

A12 The CTS definition of CHANNEL CALIBRATION states "Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an in place cross calibration of the sensing elements and normal calibration of the remaining adjustable devices in the channel." The ITS definition of CHANNEL CALIBRATION states "Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an in place qualitative assessment of sensor behavior and normal calibration of the remaining adjustable devices in the channel." This changes the CTS by replacing the "cross calibration of the sensing elements" words with "qualitative assessment of sensor behavior."

The replacing of the CTS description of a qualitative assessment of sensor behavior with the actual words does not change the way instrument channels with RTDs or thermocouples are calibrated. This change is acceptable because RTDs and thermocouples are designed such that they have a fixed input/output response, which cannot be adjusted or changed once installed. Calibration of a channel containing an RTD or thermocouple is performed by applying the RTD or thermocouple fixed input/output relationship to the remainder of the channel, and, Volume 1, Rev. 0, Page 76 of 114, Volume 1, Rev. 0, Page 76 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 5 of 7 making the necessary adjustments to the adjustable devices in the remainder of the channel to obtain the necessary output range and accuracy. The ITS CHANNEL CALIBRATION for channels containing RTDs and thermocouples is consistent with the CTS calibration practices of these channels. This change is designated as administrative because it does not result in a technical change to the Technical Specifications.

A13 The CTS includes a definition of E bar - AVERAGE DISINTEGRATION ENERGY. The ITS does not include this definition, but does include a definition of DOSE EQUIVALENT XE-133. This changes the CTS by deleting the E bar definition and replacing it with DOSE EQUIVALENT XE-133.

This change is acceptable because the term E bar - AVERAGE DISINTEGRATION ENERGY is no longer being used. Discussion of any technical changes related to the deletion of this term is included in the DOCs for the CTS Section in which the term is used. This change is designated as administrative because it deletes a defined term that is no longer used.

MORE RESTRICTIVE CHANGES None RELOCATED SPECIFICATIONS None REMOVED DETAIL CHANGES LA01 (Type 4 - Removal of LCO, SR, or other TS Requirement to the LCS, UFSAR, ODCM, QAP, CLRT Program, IST Program, ISI Program, or Surveillance Frequency Control Program) The CTS definition of CHANNEL CALIBRATION contains the following detail about RTD and thermocouple calibrations:

"Whenever a sensing element is replaced, the next required inplace cross calibration consists of comparing the other sensing elements with the recently installed sensing element." The ITS definition of CHANNEL CALIBRATION does not contain this statement (as changed by TSTF-019). This changes the CTS by moving the details of the CHANNEL CALIBRATION test following replacement of sensing devices to the Bases for ITS 3.3.11, "Post Accident Monitoring Instrumentation," and ITS 3.3.12, "Remote Shutdown System."

The removal of these details for performing Surveillance Requirements from the Technical Specification is acceptable since this type of information is not necessary to be included in the Technical Specifications to provide adequate protection of public health and safety. The affected instruments continue to require a CHANNEL CALIBRATION to be performed. Therefore, the details on how to perform a CHANNEL CALIBRATION following replacement of sensing elements do not need to appear in the definition. Also, this change is acceptable because this type of procedural detail will be adequately controlled in the ITS, Volume 1, Rev. 0, Page 77 of 114, Volume 1, Rev. 0, Page 77 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 6 of 7 Bases. Changes to the Bases are controlled by the Technical Specifications Bases Control Program in Chapter 5. This change is designated as a less restrictive removal of detail change because procedural details for performing Technical Specification requirements are being removed from the Technical Specifications.

LESS RESTRICTIVE CHANGES L01 CTS 1.3, in part, contains discussions and an example (Example 1.3-3) of the following situation. If an LCO requires OPERABILITY of two systems, it is possible to enter the Condition for one inoperable system and before restoring the first system, the second system becomes inoperable. With the second system inoperable, the first system is restored to OPERABLE status. Before restoring the second system, the first system becomes inoperable again, and so on. Under this scenario, it would be theoretically possible to operate indefinitely without ever meeting the LCO. This also could occur with LCOs which require one only system to be OPERABLE, but for which the Conditions describe two or more mutually exclusive causes of inoperability. Therefore, to prevent this from occurring a second Completion Time was included that limited the time the LCO was not met. ITS Section 1.3 will delete this discussion and revise the example in conjunction with TSTF-439. In addition the ITS will include a requirement in the administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. The proposed change to the CTS will delete the second Completion Times and revise CTS Section 1.3 to reflect the ITS.

This change was initiated due to the problems the second Completion Time presents when Completion Times are extended by risk informed methodology by complicating the presentation of the ITS and complicating the implementation of risk-informed Completion Times. Deleting the second Completion Time is acceptable due to other regulatory requirements that are now present that were not present when the second Completion Time was proposed.

The two regulatory programs in place which provide a strong disincentive to continued operation with concurrent multiple inoperabilities of the type the second Completion Times were designed to prevent are the Maintenance Rule,10 CFR 50.65, and the Reactor Oversight Process, NEI 99-02.

The Maintenance Rule requires each licensee to monitor the performance of System, Structures, and Components (SSCs) against licensee-established goals to ensure that the SSCs are capable of fulfilling their intended functions. This Rule also considers all inoperable risk-significant equipment and not just those in the same system or those governed by the same LCO. The risk assessments performed prior to maintenance activities are governed by Regulatory Guide 1.182. Any issues associated with equipment inoperability are monitored by the NRC Resident Inspector and reported in the Corrective Action Program.

The Reactor Oversight Process: NEI 99-02, "Regulatory Assessment Performance Indicator Guideline," describes the tracking and reporting of performance indicators to support the NRCs Reactor Oversight Process (ROP)., Volume 1, Rev. 0, Page 78 of 114, Volume 1, Rev. 0, Page 78 of 114

DISCUSSION OF CHANGES ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 7 of 7 The NEI document is endorsed by RIS 2001-11, "Voluntary Submission of Performance Indicator Data." NEI 99-02, Section 2.2, describes the Mitigating Systems Cornerstone. NEI 99-02 specifically addresses emergency AC Sources (which encompasses the AC Sources and Distribution System LCOs), and the Auxiliary Feedwater system. Extended unavailability of these systems due to multiple entries into the ACTIONS would affect the NRCs evaluation of the licensees performance under the ROP.

In addition to these regulatory programs, a requirement is being added to TS Section 1.3 which requires the licensees to have administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls should consider plant risk and shall limit the maximum contiguous time of failing to meet the LCO. This Technical Specification requirement, when considered with the regulatory processes discussed above, provide an equivalent or superior level of plant safety without the unnecessary complication of the Technical Specifications by second Completion Times on some Specifications.

, Volume 1, Rev. 0, Page 79 of 114, Volume 1, Rev. 0, Page 79 of 114

Improved Standard Technical Specifications (ISTS) Markup and Justification for Deviations (JFDs), Volume 1, Rev. 0, Page 80 of 114, Volume 1, Rev. 0, Page 80 of 114

Definitions 1.1 CEOG STS 1.1-1 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.0 USE AND APPLICATION 1.1 Definitions

---

NOTE-----------------------------------------------------------

The defined terms of this section appear in capitalized type and are applicable throughout these Technical Specifications and Bases.

Term Definition ACTIONS ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within specified Completion Times.

AXIAL SHAPE INDEX (ASI)

ASI shall be the power generated in the lower half of the core less the power generated in the upper half of the core, divided by the sum of the power generated in the lower and upper halves of the core.

ASI = (LOWER - UPPER) / (LOWER + UPPER)

AZIMUTHAL POWER TILT (Tq) AZIMUTHAL POWER TILT shall be the power asymmetry

- Digital between azimuthally symmetric fuel assemblies.

AZIMUTHAL POWER TILT (Tq) AZIMUTHAL POWER TILT shall be the maximum of the

- Analog difference between the power generated in any core quadrant (upper or lower) (Pquad) and the average power of all quadrants (Pavg) in that half (upper or lower) of the core, divided by the average power of all quadrants in that half (upper or lower) of the core.

Tq = Max l (Pquad - Pavg) / Pavg l CHANNEL CALIBRATION A CHANNEL CALIBRATION shall be the adjustment, as necessary, of the channel output such that it responds within the necessary range and accuracy to known values of the parameter that the channel monitors. The CHANNEL CALIBRATION shall encompass all devices in the channel required for channel OPERABILITY and the CHANNEL FUNCTIONAL TEST. Calibration of instrument channels with resistance temperature detector (RTD) or thermocouple sensors may consist of an inplace qualitative assessment of sensor behavior and normal calibration of the remaining adjustable devices in the channel. The CHANNEL CALIBRATION may be performed by means of any series of sequential, overlapping, or total channel steps.

ACTIONS AXIAL SHAPE INDEX (ASI)

AZIMUTHAL POWER TILT (Tq)

CHANNEL CALIBRATION NA Definitions 3

3 1, Volume 1, Rev. 0, Page 81 of 114, Volume 1, Rev. 0, Page 81 of 114

Definitions 1.1 CEOG STS 1.1-2 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.1 Definitions CHANNEL CHECK A CHANNEL CHECK shall be the qualitative assessment, by observation, of channel behavior during operation. This determination shall include, where possible, comparison of the channel indication and status to other indications or status derived from independent instrument channels measuring the same parameter.

CHANNEL FUNCTIONAL TEST A CHANNEL FUNCTIONAL TEST shall be:

a.

Analog and bistable channels - the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY of all devices in the channel required for channel OPERABILITY, and

b.

Digital computer channels - the use of diagnostic programs to test digital computer hardware and the injection of simulated process data into the channel to verify OPERABILITY of all devices in the channel required for channel OPERABILITY.

The CHANNEL FUNCTIONAL TEST may be performed by means of any series of sequential, overlapping, or total channel steps so that the entire channel is tested.

CORE ALTERATION CORE ALTERATION shall be the movement of any fuel, sources, or reactivity control components [excluding control element assemblies (CEAs) withdrawn into the upper guide structure], within the reactor vessel with the vessel head removed and fuel in the vessel. Suspension of CORE ALTERATIONS shall not preclude completion of movement of a component to a safe position.

CORE OPERATING LIMITS The COLR is the unit specific document that provides cycle REPORT (COLR) specific parameter limits for the current reload cycle. These cycle specific parameter limits shall be determined for each reload cycle in accordance with Specification 5.6.3. Plant operation within these limits is addressed in individual Specifications.

DOSE EQUIVALENT I-131 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries/gram) that alone would produce the same thyroid dose as the quantity and isotopic mixture of I-131, I-132, I-133, I-134, and I-135 actually present. The thyroid dose conversion factors used for this calculation shall be those listed in CHANNEL CHECK CHANNEL FUNCTIONAL TEST TSTF-471-A CORE OPERATING LIMITS REPORT (COLR)

TSTF-490-A INSERT 1 CORE ALTERATION DOSE EQUIVALENT I-131 6

1 5.7.1.5 11, Volume 1, Rev. 0, Page 82 of 114, Volume 1, Rev. 0, Page 82 of 114

1.1 Insert Page 1.1-2 INSERT 1 DOSE EQUIVALENT I-131 shall be that concentration of I-131 (microcuries per gram) that alone would produce the same dose when inhaled as the combined activities of iodine isotopes I-131, I-132, I-133, I-134, and I-135 actually present.

The determination of DOSE EQUIVALENT I-131 shall be performed using

---

Reviewers Note -------------------------------

The first set of thyroid dose conversion factors shall be used for plants licensed to 10 CFR 100.11. The following Committed Dose Equivalent (CDE) or Committed Effective Dose Equivalent (CEDE) conversion factors shall be used for plants licensed to 10 CFR 50.67.

[thyroid dose conversion factors from:

a. Table III of TID-14844, AEC, 1962, "Calculation of Distance Factors for Power and Test Reactor Sites," or

b. Table E-7 of Regulatory Guide 1.109, Rev. 1, NRC, 1977, or

c. ICRP-30, 1979, Supplement to Part 1, page 192-212, Table titled, "Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity," or

d. Table 2.1 of EPA Federal Guidance Report No. 11, 1988, "Limiting Values of Radionuclide Intake and Air Concentration and Dose Conversion Factors for Inhalation, Submersion, and Ingestion."

OR Committed Dose Equivalent (CDE) or Committed Effective Dose Equivalent (CEDE) dose conversion factors from Table 2.1 of EPA Federal Guidance Report No. 11.]

TSTF-490-A 4

5 5

7 s

9, Volume 1, Rev. 0, Page 83 of 114, Volume 1, Rev. 0, Page 83 of 114

Definitions 1.1 CEOG STS 1.1-3 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.1 Definitions DOSE EQUIVALENT I-131 (continued)

[Table III of TID-14844, AEC, 1962, "Calculation of Distance Factors for Power and Test Reactor Sites," or those listed in Table E-7 of Regulatory Guide 1.109, Rev. 1, NRC, 1977, or ICRP 30, Supplement to Part 1, page 192-212, Table titled, "Committed Dose Equivalent in Target Organs or Tissues per Intake of Unit Activity"].

- AVERAGE shall be the average (weighted in proportion to the DISINTEGRATION ENERGY concentration of each radionuclide in the reactor coolant at the time of sampling) of the sum of the average beta and gamma energies per disintegration (in MeV) for isotopes, other than iodines, with half lives > [15] minutes, making up at least 95%

of the total noniodine activity in the coolant.

ENGINEERED SAFETY The ESF RESPONSE TIME shall be that time interval from FEATURE (ESF) RESPONSE when the monitored parameter exceeds its ESF actuation TIME setpoint at the channel sensor until the ESF equipment is capable of performing its safety function (i.e., the valves travel to their required positions, pump discharge pressures reach their required values, etc.). Times shall include diesel generator starting and sequence loading delays, where applicable. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time may be verified for selected components provided that the components and methodology for verification have been previously reviewed and approved by the NRC.

LEAKAGE LEAKAGE shall be:

a.

Identified LEAKAGE

1.

LEAKAGE, such as that from pump seals or valve packing (except reactor coolant pump (RCP) seal water injection or leakoff), that is captured and conducted to collection systems or a sump or collecting tank,

2.

LEAKAGE into the containment atmosphere from sources that are both specifically located and known either not to interfere with the operation of leakage detection systems or not to be pressure boundary LEAKAGE, or INSERT 2 TSTF-490-A TSTF-490-A ENGINEERED SAFETY FEATURE (ESF)

RESPONSE

TIME LEAKAGE

- AVERAGE DISINTEGRA-TION ENERGY DOSE EQUIVALENT I-131 1

1, Volume 1, Rev. 0, Page 84 of 114, Volume 1, Rev. 0, Page 84 of 114

1.1 Insert Page 1.1-3 INSERT 2 DOSE EQUIVALENT XE-133 DOSE EQUIVALENT XE-133 shall be that concentration of Xe-133 (microcuries per gram) that alone would produce the same acute dose to the whole body as the combined activities on noble gas nuclides Kr-85m, Kr-85, Kr-87, Kr-88, Xe-131m, Xe-133m, Xe-133, Xe-135m, Xe-135, and Xe-138 actually present. If a specific noble gas nuclide is not detected, it should be assumed to be present at the minimum detectable activity. The determination of DOSE EQUIVALENT XE-133 shall be performed using [effective dose conversion factors for air submersion listed in Table III.1 of EPA Federal Guidance report No. 12, 1993, "External Exposure to radionuclides in Air, Water, and Soil" or the average gamma disintegration energies as provided in ICRP Publication 38, "Radionuclide Transformations," or similar source.]

TSTF-490-A 5

5 7

U2/U3 CTS DOC A13, Volume 1, Rev. 0, Page 85 of 114, Volume 1, Rev. 0, Page 85 of 114

Definitions 1.1 CEOG STS 1.1-4 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.1 Definitions LEAKAGE (continued)

3.

Reactor Coolant System (RCS) LEAKAGE through a steam generator to the Secondary System (primary to secondary LEAKAGE),

b.

Unidentified LEAKAGE All LEAKAGE (except RCP seal water injection or leakoff) that is not identified LEAKAGE, and

c.

Pressure Boundary LEAKAGE LEAKAGE (except primary to secondary LEAKAGE) through a nonisolable fault in an RCS component body, pipe wall, or vessel wall.

MODE A MODE shall correspond to any one inclusive combination of core reactivity condition, power level, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Table 1.1-1 with fuel in the reactor vessel.

OPERABLE - OPERABILITY A system, subsystem, train, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing its specified safety function(s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that are required for the system, subsystem, train, component, or device to perform its specified safety function(s) are also capable of performing their related support function(s).

PHYSICS TESTS PHYSICS TESTS shall be those tests performed to measure the fundamental nuclear characteristics of the reactor core and related instrumentation.

These tests are:

a.

Described in Chapter [14, Initial Test Program] of the

FSAR,

b.

Authorized under the provisions of 10 CFR 50.59, or

c.

Otherwise approved by the Nuclear Regulatory Commission.

MODE OPERABLE -

OPERABILITY PHYSICS TESTS U

LEAKAGE 5

1 1

1 7

7, Volume 1, Rev. 0, Page 86 of 114, Volume 1, Rev. 0, Page 86 of 114

Definitions 1.1 CEOG STS 1.1-5 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1

1.1 Definitions PRESSURE AND The PTLR is the unit specific document that provides the TEMPERATURE LIMITS reactor vessel pressure and temperature limits, including REPORT (PTLR) heatup and cooldown rates, for the current reactor vessel fluence period. These pressure and temperature limits shall be determined for each fluence period in accordance with Specification 5.6.3.

RATED THERMAL POWER RTP shall be a total reactor core heat transfer rate to the (RTP) reactor coolant of [3410] MWt.

REACTOR PROTECTION The RPS RESPONSE TIME shall be that time interval from SYSTEM (RPS) RESPONSE when the monitored parameter exceeds its RPS trip setpoint at TIME the channel sensor until electrical power to the CEAs drive mechanism is interrupted. The response time may be measured by means of any series of sequential, overlapping, or total steps so that the entire response time is measured. In lieu of measurement, response time may be verified for selected components provided that the components and methodology for verification have been previously reviewed and approved by the NRC.

SHUTDOWN MARGIN (SDM)

SDM shall be the instantaneous amount of reactivity by which the reactor is subcritical or would be subcritical from its present condition assuming:

a.

All full length CEAs (shutdown and regulating) are fully inserted except for the single CEA of highest reactivity worth, which is assumed to be fully withdrawn. However, with all CEAs verified fully inserted by two independent means, it is not necessary to account for a stuck CEA in the SDM calculation. With any CEAs not capable of being fully inserted, the reactivity worth of these CEAs must be accounted for in the determination of SDM, and

[ b.

There is no change in part length CEA position. ]

STAGGERED TEST BASIS A STAGGERED TEST BASIS shall consist of the testing of one of the systems, subsystems, channels, or other designated components during the interval specified by the Surveillance Frequency, so that all systems, subsystems, channels, or other designated components are tested during n Surveillance Frequency intervals, where n is the total number of systems, subsystems, channels, or other designated components in the associated function.

THERMAL POWER THERMAL POWER shall be the total reactor core heat transfer rate to the reactor coolant.

PRESSURE AND TEMPERATURE LIMITS REPORT (PTLR)

RATED THERMAL POWER REACTOR PROTECTIVE SYSTEM (RPS)

RESPONSE

TIME SHUTDOWN MARGIN (SDM)

THERMAL POWER 3438 PROTECTIVE 5

5 2

6 1

5.7.1.6 10 TSTF-425-A is not completely incorporated, Volume 1, Rev. 0, Page 87 of 114, Volume 1, Rev. 0, Page 87 of 114

Definitions 1.1 CEOG STS 1.1-6 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1

Table 1.1-1 (page 1 of 1)

MODES MODE TITLE REACTIVITY CONDITION (keff)

% RATED THERMAL POWER(a)

AVERAGE REACTOR COOLANT TEMPERATURE (F) 1 Power Operation 0.99

> 5 NA 2

Startup 0.99 5

NA 3

Hot Standby

< 0.99 NA

[350]

4 Hot Shutdown(b)

< 0.99 NA

[350] > Tavg > [200]

5 Cold Shutdown(b)

< 0.99 NA

[200]

6 Refueling(c)

NA NA NA (a)

Excluding decay heat.

(b)

All reactor vessel head closure bolts fully tensioned.

(c)

One or more reactor vessel head closure bolts less than fully tensioned.

Table 1.1-1 5

5 5, Volume 1, Rev. 0, Page 88 of 114, Volume 1, Rev. 0, Page 88 of 114

Logical Connectors 1.2 CEOG STS 1.2-1 Rev. 3.0, 03/31/04 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.

Logical connectors are used in Technical Specifications (TS) to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in TS are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meanings.

BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and by the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action).

The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.

When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.

EXAMPLES The following examples illustrate the use of logical connectors.

Purpose

Background

Examples 1, Volume 1, Rev. 0, Page 89 of 114, Volume 1, Rev. 0, Page 89 of 114

Logical Connectors 1.2 CEOG STS 1.2-2 Rev. 3.0, 03/31/04 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.2 Logical Connectors EXAMPLES (continued)

EXAMPLE 1.2-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.

A.1 Verify...

AND A.2 Restore...

In this example the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.

Example 1.2-1 1, Volume 1, Rev. 0, Page 90 of 114, Volume 1, Rev. 0, Page 90 of 114

Logical Connectors 1.2 CEOG STS 1.2-3 Rev. 3.0, 03/31/04 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.2 Logical Connectors EXAMPLES (continued)

EXAMPLE 1.2-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.

A.1 Trip...

OR A.2.1 Verify...

AND A.2.2.1 Reduce...

OR A.2.2.2 Perform...

OR A.3 Align...

This example represents a more complicated use of logical connectors.

Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.

Example 1.2-2 1, Volume 1, Rev. 0, Page 91 of 114, Volume 1, Rev. 0, Page 91 of 114

Completion Times 1.3 CEOG STS 1.3-1 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.0 USE AND APPLICATION 1.3 Completion Times PURPOSE The purpose of this section is to establish the Completion Time convention and to provide guidance for its use.

BACKGROUND Limiting Conditions for Operation (LCOs) specify minimum requirements for ensuring safe operation of the unit. The ACTIONS associated with an LCO state Conditions that typically describe the ways in which the requirements of the LCO can fail to be met. Specified with each stated Condition are Required Action(s) and Completion Time(s).

DESCRIPTION The Completion Time is the amount of time allowed for completing a Required Action. It is referenced to the time of discovery of a situation (e.g., inoperable equipment or variable not within limits) that requires entering an ACTIONS Condition unless otherwise specified, providing the unit is in a MODE or specified condition stated in the Applicability of the LCO. Required Actions must be completed prior to the expiration of the specified Completion Time. An ACTIONS Condition remains in effect and the Required Actions apply until the Condition no longer exists or the unit is not within the LCO Applicability.

If situations are discovered that require entry into more than one Condition at a time within a single LCO (multiple Conditions), the Required Actions for each Condition must be performed within the associated Completion Time. When in multiple Conditions, separate Completion Times are tracked for each Condition starting from the time of discovery of the situation that required entry into the Condition.

Once a Condition has been entered, subsequent trains, subsystems, components, or variables expressed in the Condition, discovered to be inoperable or not within limits, will not result in separate entry into the Condition, unless specifically stated. The Required Actions of the Condition continue to apply to each additional failure, with Completion Times based on initial entry into the Condition.

However, when a subsequent train, subsystem, component, or variable expressed in the Condition is discovered to be inoperable or not within limits, the Completion Time(s) may be extended. To apply this Completion Time extension, two criteria must first be met. The subsequent inoperability:

a.

Must exist concurrent with the first inoperability and

b.

Must remain inoperable or not within limits after the first inoperability is resolved.

Purpose

=

Background===

Description 1, Volume 1, Rev. 0, Page 92 of 114, Volume 1, Rev. 0, Page 92 of 114

Completion Times 1.3 CEOG STS 1.3-2 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times DESCRIPTION (continued)

The total Completion Time allowed for completing a Required Action to address the subsequent inoperability shall be limited to the more restrictive of either:

a.

The stated Completion Time, as measured from the initial entry into the Condition, plus an additional 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or

b.

The stated Completion Time as measured from discovery of the subsequent inoperability.

The above Completion Time extensions do not apply to those Specifications that have exceptions that allow completely separate re-entry into the Condition (for each train, subsystem, component, or variable expressed in the Condition) and separate tracking of Completion Times based on this re-entry. These exceptions are stated in individual Specifications.

The above Completion Time extension does not apply to a Completion Time with a modified "time zero." This modified "time zero" may be expressed as a repetitive time (i.e., "once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br />," where the Completion Time is referenced from a previous completion of the Required Action versus the time of Condition entry) or as a time modified by the phrase "from discovery..."

EXAMPLES The following examples illustrate the use of Completion Times with different types of Conditions and changing Conditions.

EXAMPLE 1.3-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Condition B has two Required Actions. Each Required Action has its own separate Completion Time. Each Completion Time is referenced to the time that Condition B is entered.

Example 1.3-1 1, Volume 1, Rev. 0, Page 93 of 114, Volume 1, Rev. 0, Page 93 of 114

Completion Times 1.3 CEOG STS 1.3-3 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

The Required Actions of Condition B are to be in MODE 3 within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> AND in MODE 5 within 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />. A total of 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> is allowed for reaching MODE 3 and a total of 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br /> (not 42 hours4.861111e-4 days <br />0.0117 hours <br />6.944444e-5 weeks <br />1.5981e-5 months <br />) is allowed for reaching MODE 5 from the time that Condition B was entered. If MODE 3 is reached within 3 hours3.472222e-5 days <br />8.333333e-4 hours <br />4.960317e-6 weeks <br />1.1415e-6 months <br />, the time allowed for reaching MODE 5 is the next 33 hours3.819444e-4 days <br />0.00917 hours <br />5.456349e-5 weeks <br />1.25565e-5 months <br /> because the total time allowed for reaching MODE 5 is 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

If Condition B is entered while in MODE 3, the time allowed for reaching MODE 5 is the next 36 hours4.166667e-4 days <br />0.01 hours <br />5.952381e-5 weeks <br />1.3698e-5 months <br />.

EXAMPLE 1.3-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One pump inoperable.

A.1 Restore pump to OPERABLE status.

7 days B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours When a pump is declared inoperable, Condition A is entered. If the pump is not restored to OPERABLE status within 7 days, Condition B is also entered and the Completion Time clocks for Required Actions B.1 and B.2 start. If the inoperable pump is restored to OPERABLE status after Condition B is entered, Conditions A and B are exited, and therefore, the Required Actions of Condition B may be terminated.

Example 1.3-2 1, Volume 1, Rev. 0, Page 94 of 114, Volume 1, Rev. 0, Page 94 of 114

Completion Times 1.3 CEOG STS 1.3-4 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has not expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition A.

While in LCO 3.0.3, if one of the inoperable pumps is restored to OPERABLE status and the Completion Time for Condition A has expired, LCO 3.0.3 may be exited and operation continued in accordance with Condition B. The Completion Time for Condition B is tracked from the time the Condition A Completion Time expired.

On restoring one of the pumps to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first pump was declared inoperable. This Completion Time may be extended if the pump restored to OPERABLE status was the first inoperable pump. A 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> extension to the stated 7 days is allowed, provided this does not result in the second pump being inoperable for > 7 days.

1, Volume 1, Rev. 0, Page 95 of 114, Volume 1, Rev. 0, Page 95 of 114

Completion Times 1.3 CEOG STS 1.3-5 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

EXAMPLE 1.3-3 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One Function X train inoperable.

A.1 Restore Function X train to OPERABLE status.

7 days B. One Function Y train inoperable.

B.1 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> C. One Function X train inoperable.

AND One Function Y train inoperable.

C.1 Restore Function X train to OPERABLE status.

OR C.2 Restore Function Y train to OPERABLE status.

72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> 72 hours When one Function X train and one Function Y train are inoperable, Condition A and Condition B are concurrently applicable. The Completion Times for Condition A and Condition B are tracked separately for each train starting from the time each train was declared inoperable and the Condition was entered. A separate Completion Time is established for Condition C and tracked from the time the second train was declared inoperable (i.e., the time the situation described in Condition C was discovered).

Example 1.3-3 1, Volume 1, Rev. 0, Page 96 of 114, Volume 1, Rev. 0, Page 96 of 114

Completion Times 1.3 CEOG STS 1.3-6 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

If Required Action C.2 is completed within the specified Completion Time, Conditions B and C are exited. If the Completion Time for Required Action A.1 has not expired, operation may continue in accordance with Condition A. The remaining Completion Time in Condition A is measured from the time the affected train was declared inoperable (i.e., initial entry into Condition A).

It is possible to alternate between Conditions A, B, and C in such a manner that operation could continue indefinitely without ever restoring systems to meet the LCO. However, doing so would be inconsistent with the basis of the Completion Times. Therefore, there shall be administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls shall ensure that the Completion Times for those Conditions are not inappropriately extended.

EXAMPLE 1.3-4 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One or more valves inoperable.

A.1 Restore valve(s) to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours A single Completion Time is used for any number of valves inoperable at the same time. The Completion Time associated with Condition A is based on the initial entry into Condition A and is not tracked on a per valve basis. Declaring subsequent valves inoperable, while Condition A is still in effect, does not trigger the tracking of separate Completion Times.

Example 1.3-4 1, Volume 1, Rev. 0, Page 97 of 114, Volume 1, Rev. 0, Page 97 of 114

Completion Times 1.3 CEOG STS 1.3-7 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

Once one of the valves has been restored to OPERABLE status, the Condition A Completion Time is not reset, but continues from the time the first valve was declared inoperable. The Completion Time may be extended if the valve restored to OPERABLE status was the first inoperable valve. The Condition A Completion Time may be extended for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> provided this does not result in any subsequent valve being inoperable for > 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br />.

If the Completion Time of 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> (including the extension) expires while one or more valves are still inoperable, Condition B is entered.

EXAMPLE 1.3-5 ACTIONS

---

NOTE--------------------------------------------

Separate Condition entry is allowed for each inoperable valve.

CONDITION REQUIRED ACTION COMPLETION TIME A. One or more valves inoperable.

A.1 Restore valve to OPERABLE status.

4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 4.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 12 hours The Note above the ACTIONS Table is a method of modifying how the Completion Time is tracked. If this method of modifying how the Completion Time is tracked was applicable only to a specific Condition, the Note would appear in that Condition rather than at the top of the ACTIONS Table.

Example 1.3-5 1, Volume 1, Rev. 0, Page 98 of 114, Volume 1, Rev. 0, Page 98 of 114

Completion Times 1.3 CEOG STS 1.3-8 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

The Note allows Condition A to be entered separately for each inoperable valve, and Completion Times tracked on a per valve basis. When a valve is declared inoperable, Condition A is entered and its Completion Time starts. If subsequent valves are declared inoperable, Condition A is entered for each valve and separate Completion Times start and are tracked for each valve.

If the Completion Time associated with a valve in Condition A expires, Condition B is entered for that valve. If the Completion Times associated with subsequent valves in Condition A expire, Condition B is entered separately for each valve and separate Completion Times start and are tracked for each valve. If a valve that caused entry into Condition B is restored to OPERABLE status, Condition B is exited for that valve.

Since the Note in this example allows multiple Condition entry and tracking of separate Completion Times, Completion Time extensions do not apply.

EXAMPLE 1.3-6 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One channel inoperable.

A.1 Perform SR 3.x.x.x.

OR A.2 Reduce THERMAL POWER to 50% RTP.

Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> 8 hours B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> Example 1.3-6 1, Volume 1, Rev. 0, Page 99 of 114, Volume 1, Rev. 0, Page 99 of 114

Completion Times 1.3 CEOG STS 1.3-9 Rev. 3.1, 12/01/05 U2/U3 CTS San Onofre -- Draft Amendment XXX 1.3 Completion Times EXAMPLES (continued)

Entry into Condition A offers a choice between Required Action A.1 or A.2. Required Action A.1 has a "once per" Completion Time, which qualifies for the 25% extension, per SR 3.0.2, to each performance after the initial performance. The initial 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval of Required Action A.1 begins when Condition A is entered and the initial performance of Required Action A.1 must be complete within the first 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval. If Required Action A.1 is followed and the Required Action is not met within the Completion Time (plus the extension allowed by SR 3.0.2),

Condition B is entered. If Required Action A.2 is followed and the Completion Time of 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> is not met, Condition B is entered.

If after entry into Condition B, Required Action A.1 or A.2 is met, Condition B is exited and operation may then continue in Condition A.

EXAMPLE 1.3-7 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. One subsystem inoperable.

A.1 Verify affected subsystem isolated.

AND A.2 Restore subsystem to OPERABLE status.

1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> AND Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> B. Required Action and associated Completion Time not met.

B.1 Be in MODE 3.

AND B.2 Be in MODE 5.

6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br /> 36 hours Example 1.3-7 1, Volume 1, Rev. 0, Page 100 of 114, Volume 1, Rev. 0, Page 100 of 114

Completion Times 1.3 CEOG STS 1.3-10 Rev. 3.0, 03/31/04 U2/U3 CTS San Onofre -- Draft Amendment XXX 1

1.3 Completion Times EXAMPLES (continued)

Required Action A.1 has two Completion Times. The 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> Completion Time begins at the time the Condition is entered and each "Once per 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> thereafter" interval begins upon performance of Required Action A.1.

If after Condition A is entered, Required Action A.1 is not met within either the initial 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> or any subsequent 8 hour9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> interval from the previous performance (plus the extension allowed by SR 3.0.2), Condition B is entered. The Completion Time clock for Condition A does not stop after Condition B is entered, but continues from the time Condition A was initially entered. If Required Action A.1 is met after Condition B is entered, Condition B is exited and operation may continue in accordance with Condition A, provided the Completion Time for Required Action A.2 has not expired.

IMMEDIATE When "Immediately" is used as a Completion Time, the Required Action COMPLETION TIME should be pursued without delay and in a controlled manner.

Immediate Completion Time, Volume 1, Rev. 0, Page 101 of 114, Volume 1, Rev. 0, Page 101 of 114

Frequency 1.4 CEOG STS 1.4-1 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.0 USE AND APPLICATION 1.4 Frequency PURPOSE The purpose of this section is to define the proper use and application of Frequency requirements.

DESCRIPTION Each Surveillance Requirement (SR) has a specified Frequency in which the Surveillance must be met in order to meet the associated LCO. An understanding of the correct application of the specified Frequency is necessary for compliance with the SR.

The "specified Frequency" is referred to throughout this section and each of the Specifications of Section 3.0.2, Surveillance Requirement (SR)

Applicability. The "specified Frequency" consists of the requirements of the Frequency column of each SR, as well as certain Notes in the Surveillance column that modify performance requirements.

Sometimes special situations dictate when the requirements of a Surveillance are to be met. They are "otherwise stated" conditions allowed by SR 3.0.1. They may be stated as clarifying Notes in the Surveillance, as part of the Surveillances, or both.

Situations where a Surveillance could be required (i.e., its Frequency could expire), but where it is not possible or not desired that it be performed until sometime after the associated LCO is within its Applicability, represent potential SR 3.0.4 conflicts. To avoid these conflicts, the SR (i.e., the Surveillance or the Frequency) is stated such that it is only "required" when it can be and should be performed. With an SR satisfied, SR 3.0.4 imposes no restriction.

The use of "met" or "performed" in these instances conveys specific meanings. A Surveillance is "met" only when the acceptance criteria are satisfied. Known failure of the requirements of a Surveillance, even without a Surveillance specifically being "performed," constitutes a Surveillance not "met." "Performance" refers only to the requirement to specifically determine the ability to meet the acceptance criteria.

Some Surveillances contain Notes that modify the Frequency of performance or the conditions during which the acceptance criteria must be satisfied. For these Surveillances, the MODE-entry restrictions of SR 3.0.4 may not apply. Such a Surveillance is not required to be performed prior to entering a MODE or other specified condition in the Applicability of the associated LCO if any of the following three conditions are satisfied:

Purpose Description U2/U3 CTS 1

9 9, Volume 1, Rev. 0, Page 102 of 114, Volume 1, Rev. 0, Page 102 of 114

Frequency 1.4 CEOG STS 1.4-2 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency DESCRIPTION (continued)

a.

The Surveillance is not required to be met in the MODE or other specified condition to be entered; or

b.

The Surveillance is required to be met in the MODE or other specified condition to be entered, but has been performed within the specified Frequency (i.e., it is current) and is known not to be failed; or

c.

The Surveillance is required to be met, but not performed, in the MODE or other specified condition to be entered, and is known not to be failed.

Examples 1.4-3, 1.4-4, 1.4-5, and 1.4-6 discuss these special situations.

EXAMPLES The following examples illustrate the various ways that Frequencies are specified. In these examples, the Applicability of the LCO (LCO not shown) is MODES 1, 2, and 3.

Examples U2/U3 CTS 1, Volume 1, Rev. 0, Page 103 of 114, Volume 1, Rev. 0, Page 103 of 114

Frequency 1.4 CEOG STS 1.4-3 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-1 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Perform CHANNEL CHECK.

12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> Example 1.4-1 contains the type of SR most often encountered in the Technical Specifications (TS). The Frequency specifies an interval (12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />) during which the associated Surveillance must be performed at least one time. Performance of the Surveillance initiates the subsequent interval. Although the Frequency is stated as 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, an extension of the time interval to 1.25 times the stated Frequency is allowed by SR 3.0.2 for operational flexibility. The measurement of this interval continues at all times, even when the SR is not required to be met per SR 3.0.1 (such as when the equipment is inoperable, a variable is outside specified limits, or the unit is outside the Applicability of the LCO). If the interval specified by SR 3.0.2 is exceeded while the unit is in a MODE or other specified condition in the Applicability of the LCO, and the performance of the Surveillance is not otherwise modified (refer to Example 1.4-3), then SR 3.0.3 becomes applicable.

If the interval as specified by SR 3.0.2 is exceeded while the unit is not in a MODE or other specified condition in the Applicability of the LCO for which performance of the SR is required, then SR 3.0.4 becomes applicable. The Surveillance must be performed within the Frequency requirements of SR 3.0.2, as modified by SR 3.0.3, prior to entry into the MODE or other specified condition or the LCO is considered not met (in accordance with SR 3.0.1) and LCO 3.0.4 becomes applicable.

U2/U3 CTS Example 1.4-1 1, Volume 1, Rev. 0, Page 104 of 114, Volume 1, Rev. 0, Page 104 of 114

Frequency 1.4 CEOG STS 1.4-4 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-2 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY Verify flow is within limits.

Once within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after 25% RTP AND 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> thereafter Example 1.4-2 has two Frequencies. The first is a one time performance Frequency, and the second is of the type shown in Example 1.4-1. The logical connector "AND" indicates that both Frequency requirements must be met. Each time reactor power is increased from a power level

< 25% RTP to 25% RTP, the Surveillance must be performed within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />.

The use of "once" indicates a single performance will satisfy the specified Frequency (assuming no other Frequencies are connected by "AND").

This type of Frequency does not qualify for the extension allowed by SR 3.0.2. "Thereafter" indicates future performances must be established per SR 3.0.2, but only after a specified condition is first met (i.e., the "once" performance in this example). If reactor power decreases to

< 25% RTP, the measurement of both intervals stops. New intervals start upon reactor power reaching 25% RTP.

U2/U3 CTS Example 1.4-2 1, Volume 1, Rev. 0, Page 105 of 114, Volume 1, Rev. 0, Page 105 of 114

Frequency 1.4 CEOG STS 1.4-5 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-3 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Not required to be performed until 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after 25% RTP.

Perform channel adjustment.

7 days The interval continues, whether or not the unit operation is < 25% RTP between performances.

As the Note modifies the required performance of the Surveillance, it is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is < 25% RTP, this Note allows 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> after power reaches 25% RTP to perform the Surveillance.

The Surveillance is still considered to be performed within the "specified Frequency." Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was

< 25% RTP, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not exceed 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> with power 25% RTP.

Once the unit reaches 25% RTP, 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> would be allowed for completing the Surveillance. If the Surveillance were not performed within this 12 hour1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> interval, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.

(plus the extension allowed by SR 3.0.2)

(plus the extension allowed by SR 3.0.2)

TSTF-475-A TSTF-475-A U2/U3 CTS Example 1.4-3 1, Volume 1, Rev. 0, Page 106 of 114, Volume 1, Rev. 0, Page 106 of 114

Frequency 1.4 CEOG STS 1.4-6 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-4 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be met in MODE 1.

Verify leakage rates are within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-4 specifies that the requirements of this Surveillance do not have to be met until the unit is in MODE 1. The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), but the unit was not in MODE 1, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change was not made into MODE 1. Prior to entering MODE 1 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

1 U2/U3 CTS DOC A06, Volume 1, Rev. 0, Page 107 of 114, Volume 1, Rev. 0, Page 107 of 114

Frequency 1.4 CEOG STS 1.4-7 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-5 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be performed in MODE 1.

Perform complete cycle of the valve.

7 days The interval continues, whether or not the unit operation is in MODE 1, 2, or 3 (the assumed Applicability of the associated LCO) between performances.

As the Note modifies the required performance of the Surveillance, the Note is construed to be part of the "specified Frequency." Should the 7 day interval be exceeded while operation is not in MODE 1, this Note allows entry into and operation in MODES 2 and 3 to perform the Surveillance. The Surveillance is still considered to be performed within the "specified Frequency" if completed prior to entering MODE 1.

Therefore, if the Surveillance were not performed within the 7 day (plus the extension allowed by SR 3.0.2) interval, but operation was not in MODE 1, it would not constitute a failure of the SR or failure to meet the LCO. Also, no violation of SR 3.0.4 occurs when changing MODES, even with the 7 day Frequency not met, provided operation does not result in entry into MODE 1.

Once the unit reaches MODE 1, the requirement for the Surveillance to be performed within its specified Frequency applies and would require that the Surveillance had been performed. If the Surveillance were not performed prior to entering MODE 1, there would then be a failure to perform a Surveillance within the specified Frequency, and the provisions of SR 3.0.3 would apply.

1 U2/U3 CTS DOC A06, Volume 1, Rev. 0, Page 108 of 114, Volume 1, Rev. 0, Page 108 of 114

Frequency 1.4 CEOG STS 1.4-8 Rev. 3.1, 12/01/05 San Onofre -- Draft Amendment XXX 1.4 Frequency EXAMPLES (continued)

EXAMPLE 1.4-6 SURVEILLANCE REQUIREMENTS SURVEILLANCE FREQUENCY

---

NOTE-----------------------------

Only required to be met in MODE 3.

Verify parameter is within limits.

24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Example 1.4-[6] specifies that the requirements of this Surveillance do not have to be met while the unit is in MODE 3 (the assumed Applicability of the associated LCO is MODES 1, 2, and 3). The interval measurement for the Frequency of this Surveillance continues at all times, as described in Example 1.4-1. However, the Note constitutes an "otherwise stated" exception to the Applicability of this Surveillance. Therefore, if the Surveillance were not performed within the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> interval (plus the extension allowed by SR 3.0.2), and the unit was in MODE 3, there would be no failure of the SR nor failure to meet the LCO. Therefore, no violation of SR 3.0.4 occurs when changing MODES to enter MODE 3, even with the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency exceeded, provided the MODE change does not result in entry into MODE 2. Prior to entering MODE 2 (assuming again that the 24 hour2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> Frequency were not met), SR 3.0.4 would require satisfying the SR.

1 Not 8

5 U2/U3 CTS DOC A06, Volume 1, Rev. 0, Page 109 of 114, Volume 1, Rev. 0, Page 109 of 114

JUSTIFICATION FOR DEVIATIONS ITS 1.0, USE AND APPLICATION San Onofre Unit 2 and 3 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. This change deletes an extra line that is not consistent with the Writers Guide for the Improved Standard Technical Specifications, TSTF-GG-05-01.

3. These are deletions to Analog specific entries in the ISTS and the Digital labels to identify that an entry is Digital. SONGS Unit 2 and 3 are Digital plants; therefore, Analog entries and specific labels that identify an entry is digital are not required.

4. This "Reviewers Note" is being deleted. The Reviewers Note is for the NRC reviewer during the NRC review and will not be part of the plant specific SONGS ITS.

5. The ISTS contains bracketed information and/or values that are generic to all Combustion Engineering vintage plants. The brackets are removed and the proper plant specific information/value is provided. This is acceptable since the information/value is changed to reflect the current licensing basis.

6. The Specification number has been changed to be consistent with changes made to the applicable Specifications in other Sections.

7. Correct punctuation is used and is consistent with the Writers Guide for the Improved Standard Technical Specifications, TSTF-GG-05-01.

8. The word "Only" has been change to "Not" consistent with TSTF-284, Rev. 3. This TSTF was previously approved and was incorporated into NUREG-1432, Rev. 2.

However, this portion of the TSTF was inadvertently incorporated incorrectly.

9. Typographical/grammatical error corrected.

10. TSTF-425-A has not been incorporated for the definition of STAGGERED TEST BASIS. The Control Room Envelope Habitability program in Chapter 5 (ITS 5.5.2.16) maintains a testing requirement of 24 months on a STAGGERED TEST BASIS. Therefore, the definition of STAGGERED TEST BASIS must be maintained.

11. The ISTS definition of CHANNEL FUNCTIONAL TEST states that the CHANNEL FUNCTIONAL TEST may be performed by means of any series of sequential, overlapping, or total channel steps so that the entire channel is tested. TSTF-205-A deleted the statement "so that the entire channel is tested" from all of the NUREGs.

Although the ISTS still maintains the words "so that the entire channel is tested" it is apparent that TSTF-205-A intended to delete these words. Therefore, the words "so that the entire channel is tested" will not be maintained in the ITS definition of CHANNEL FUNCTIONAL TEST., Volume 1, Rev. 0, Page 110 of 114, Volume 1, Rev. 0, Page 110 of 114

Specific No Significant Hazards Considerations (NSHCs), Volume 1, Rev. 0, Page 111 of 114, Volume 1, Rev. 0, Page 111 of 114

DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 1 of 3 10 CFR 50.92 EVALUATION FOR LESS RESTRICTIVE CHANGE L01 Southern California Edison (SCE) is updating the San Onofre Nuclear Generating Station (SONGS) TS to the Improved Technical Specifications (ITS) as outlined in NUREG-1432, Rev. 3.0, "Standard Technical Specifications, Combustion Engineering Plants" and additional approved Technical Specification Task Force (TSTF) travelers included in this submittal. The proposed change involves making the Current Technical Specifications (CTS) less restrictive. Below is the description of this less restrictive change and the determination of No Significant Hazards Considerations for conversion to NUREG-1432, Rev. 3.0.

CTS 1.3, in part, contains discussions and an example (Example 1.3-3) of the following situation. If an LCO requires OPERABILITY of two systems, it is possible to enter the Condition for one inoperable system and before restoring the first system, the second system becomes inoperable. With the second system inoperable, the first system is restored to OPERABLE status. Before restoring the second system, the first system becomes inoperable again, and so on. Under this scenario, it would be theoretically possible to operate indefinitely without ever meeting the LCO. This also could occur with LCOs which require one only system to be OPERABLE, but for which the Conditions describe two or more mutually exclusive causes of inoperability. Therefore, to prevent this from occurring a second Completion Time was included that limited the time the LCO was not met. ITS Section 1.3 will delete this discussion and revise the example in conjunction with TSTF-439. In addition the ITS will include a requirement in the administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. The proposed change to the CTS will delete the second Completion Times and revise CTS Section 1.3 to reflect the ITS.

This change was initiated due to the problems the second Completion Time presents when Completion Times are extended by risk informed methodology by complicating the presentation of the ITS and complicating the implementation of risk-informed Completion Times. Deleting the second Completion Time is acceptable due to other regulatory requirements that are now present that were not present when the second Completion Time was proposed.

The two regulatory programs is place which provide a strong disincentive to continued operation with concurrent multiple inoperabilities of the type the second Completion Times were designed to prevent are the Maintenance Rule,10 CFR 50.65, and the Reactor Oversight Process, NEI 99-02.

The Maintenance Rule requires each licensee to monitor the performance of System, Structures, and Components (SSCs) against licensee-established goals to ensure that the SSCs are capable of fulfilling their intended functions. This Rule also considers all inoperable risk-significant equipment and not just those in the same system or those governed by the same LCO. The risk assessments performed prior to maintenance activities are governed by Regulatory Guide 1.182. Any issues associated with, Volume 1, Rev. 0, Page 112 of 114, Volume 1, Rev. 0, Page 112 of 114

DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 2 of 3 equipment inoperability are monitored by the NRC Resident Inspector and reported in the Corrective Action Program.

The Reactor Oversight Process: NEI 99-02, "Regulatory Assessment Performance Indicator Guideline," describes the tracking and reporting of performance indicators to support the NRCs Reactor Oversight Process (ROP). The NEI document is endorsed by RIS 2001-11, "Voluntary Submission of Performance Indicator Data." NEI 99-02, Section 2.2, describes the Mitigating Systems Cornerstone. NEI 99-02 specifically addresses emergency AC Sources (which encompasses the AC Sources and Distribution System LCOs), and the Auxiliary feedwater system. Extended unavailability of these systems due to multiple entries into the ACTIONS would affect the NRCs evaluation of the licensees performance under the ROP.

In addition to these regulatory programs, a requirement is being added to TS Section 1.3 which requires the licensees to have administrative controls to limit the maximum time allowed for any combination of Conditions that result in a single contiguous occurrence of failing to meet the LCO. These administrative controls should consider plant risk and shall limit the maximum contiguous time of failing to meet the LCO. This Technical Specification requirement, when considered with the regulatory processes discussed above, provide an equivalent or superior level of plant safety without the unnecessary complication of the Technical Specifications by second Completion Times on some Specifications.

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

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

Response: No.

The proposed change eliminates certain Completion Times from the Technical Specifications. Completion Times are not an initiator to any accident previously evaluated. As a result, the probability of an accident previously evaluated is not affected. The consequences of an accident during the revised Completion Time are no different than the consequences of the same accident during the existing Completion Times. As a result, the consequences of an accident previously evaluated are not affected by this change. The proposed change does not alter or prevent the ability of structures, systems, and components (SSCs) from performing their intended function to mitigate the consequences of an initiating event within the assumed acceptance limits. The proposed change does not affect the source term, containment isolation, or radiological release assumptions used in evaluating the radiological consequences of an accident previously evaluated. Further, the proposed change does not increase the types or amounts of radioactive effluent that may be released offsite, nor significantly increase individual or cumulative occupational/public radiation exposures. The proposed change is consistent with the safety analysis assumptions and, Volume 1, Rev. 0, Page 113 of 114, Volume 1, Rev. 0, Page 113 of 114

DETERMINATION OF NO SIGNIFICANT HAZARDS CONSIDERATIONS ITS 1.0, USE AND APPLICATIONS San Onofre Unit 2 and 3 Page 3 of 3 resultant consequences.

Therefore, the proposed change does not involve a significant increase in the probability or consequences of an accident previously evaluated.

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

Response: No.

The change does not involve a physical alteration of the plant (i.e., no new or different type of equipment will be installed) or a change in the methods governing normal plant operation. The change does not alter any assumptions made in the safety analysis.

Therefore, the proposed change does not create the possibility of a new or different kind of accident from any accident previously evaluated.

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

Response: No.

The proposed change to delete the second Completion Time does not alter the manner in which safety limits, limiting safety system settings or limiting conditions for operation are determined. The safety analysis acceptance criteria are not affected by this change. The proposed change will not result in plant operation in a configuration outside of the design basis.

Therefore, the proposed change does not involve a significant reduction in a margin of safety.

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

, Volume 1, Rev. 0, Page 114 of 114, Volume 1, Rev. 0, Page 114 of 114