Text

Proposed Improved Tech Specs,Rev F
	ML20076L691
Person / Time
Site:	Hatch
Issue date:	10/19/1994
From:	; GEORGIA POWER CO.
To:	;
Shared Package
ML20076L688	List: HL-4712, Forwards Rev F to Improved Ts,Consisting of Partial Rev to 940225 Amend Request to Convert Current TS to Improved TS Consistent w/NUREG-1433.Rev Result of Site & Generic Effort to Clarify LCO 3.0.4 & Changes in Position Titles; ML20076L691;
References
	NUDOCS 9411040103
	Download: ML20076L691 (114)
	v • d • e

_ _ _

l l.

ATTACIIMENT 1

EDWIN I. IIATCII NUCLEAR PLANT UNIT 1 AND UNIT 2 (MPROVED TECHNICAL SPECIFICATIONS Revision F l

l l

I 1

1

)

9411040103 DR 941019 l p ADOCK 05000321 l PDR

- Edwin I. IIatch Nuclear Plant Improved Technical Snecifications Revision Insertion Instructions Revision F Page Instruction U1 (moroved Specifications Cover sheet Discard 2.0-1 Replace 3.0-1 Replace 3.0-5 Replace 5.0-1 Replace 5.0-3 Replace 5.0-7 Replace UI improved Bases Cover sheet Discard B 3.0-5 Replace B 3.0-6A Add B 3.0-13 Replace B 3.0-14A Add B 3.0-15 Replace U1 C7'S Markun & DOC'"'

Cover sheet Discard 6-12 (8 of 9) Replace 6-13 (9 of 9) Replace ITS 2.0 DOC: 1 Replace ITS 2.0 DOC: 1A Add Insert 3.0-2 (3 of 8) Replace Insert 3.0-5 (7 of 8) Replace ITS 3.8.1 DOC: 2 Replace ITS 3.8.1 DOC: 7 Replace 6-1 (1 of 2) Replace Insert i for ITS 5.1 Replace ITS 5.1 DOC: 1 Replace 6-1 (1 of 7) Replace 6-3 (3 of 7) Replace Insert 2 (7 of 7) Replace ITS 5.2 DOC: 1 Replace 6-23 (1 of 2) Replace ITS 5.5.1 DOC: 1 Replace

a. In replacing each CTS page, reference 'he upper right comer for the appropriate ITS section.

1 of 3

Revision Insertion Instructions Revision F Page Instruction U1 No Sienificant Hazards Determination Cover sheet Discard ITS 3.8.1: 5 Replace U2 Imoroved Specifications Cover sheet Discard 2.0-1 Replace 3.0-1 Replace 3.0-5 Replace 5.0-1 Replace 5.0-3 Replace 5.0-7 Replace U2 Improved Bases Cover sheet Discard B 3.0-5 Replace B 3.0-6A Add B 3.0-13 Replace B 3.0-14A Add B 3.0-15 Replace U2 CTS Markun & DOC'"'

Cover sheet Discard 6-11 (6 of 7) Replace 6-12 (7 of 7) Replace ITS 2.0 DOC: 1 Replace ITS 2.0 DOC: lA Add Insert 3/4 0-1(2) (3 of 9) Replace Insert 3/4 0-2 (7 of 9) Replace ITS 3.0 DOC: 3 Replace ITS 3.0 DOC: 6 Replace ,

ITS 3.0 DOC: 7 Replace ITS 3.0 DOC: 7A Add I ITS 3.8.1 DOC: 2 Replace l ITS 3.8.1 DOC: 9 Replace 6-1 (1 of 2) Replace l Insert I for ITS 5.1 Replace ITS 5.1 DOC: 1 Replace 6-1 (1 of 6) Replace 6-3 (3 of 6) Replace Insert 2 for ITS 5.2 Replace ITS 5.2 DOC: 1 Replace 6-22 (1 of 2) Replace ITS 5.5.1 DOC: 1 Replace ;

i

a. In replacing each CTS page, reference the upper right corner for the appropriate ITS section.

2 of 3

' Revision Insertion Instructions Revision F Paw. Instruction U2 No Significant Hazards Determination Cover sheet Discard ITS 3.0: ~2 Replace ITS 3.0 DOC: 2A Replace ITS 3.8.1 DOC: 10 Replace NUREG I433 Comnarison - Soecifications Cover sheet Discard 2.0-1 Replace 3.0-1 Replace 3.0-5 Replace 5.0-1 Replace Insert A for NUREG 5.1 Replace 5.0-3 Replace 5.0-19 Replace NUREG 1433 Comparison - Bases Cover sheet Discard B 3.0-5 Replace Insert B 3.0-6(B6) Add B 3.0-13 Replace Insert B 3.0-14 (SR 3.0.4) Replace Insert B 3.3-163 (Inser. K) Replace NUREG 1433 - Justification for Deviation Cover sheet Discard 1 ITS 3.0: 1 Replace ,

ITS 5.0: 1 Replace !

l l

3 of 3

l UNIT 1 IMPROVED TECHNICAL SPECIFICATIONS 1

l l

O O

l l

SLs 2.0 l O l C 2.0 SAFETY LIMilS (SLs) 2.1 SLs 2.1.1 Reactor Core SLs 2.1.1.1 With the reactor steam dome pressure < 785 psig or core l flow < 10% rated core flow: l THERMAL POWER shall be s 25% RTP.

2.1.1.2 With the reactor steam dome pressure a 785 psig and core flow d 101 rated core flow: -1 MCPR shall be a 1.07 for two recirculation loop operation or 2 1.08 for single recirculation loop operation.

2.1.1.3 Reactor vessel water level shall be greater than the top of active irradiated fuel.

d 2.1.2 Rex tor Coolant System (RCS) Pressure SL Reactor steam dome pressure shall be s 1325 psig.

2.2 SL Violations 4

With any SL violation, the following actions shall be completed:

2.2.1 Within I hour, notify the NRC Operations Center, in accordance with 10 CFR 50.72, 2.2.2 Within 2 hour2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months s:

2.2.2.1 Restore compliance with all SLs; and 2.2.2.2 Insert all insertable control rods.

2.2.3 Within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months , notify the plant manager, the corporate executive responsible for overall plant nuclear safety, and the offsite review committee.

l (continued)

O HATCH UNIT 1 2.0-1 REVISIONff i

l l

+ - ,

SLs 2.0 2.0 SLs 2.2 SL Violations (continued) 2.2.4 Within 30 days, a Licensee Event Report (LER) shall be prepared pursuant to 10 CFR 50.73. The LER shall be submitted to the NRC, the offsite review commit'.ee, the plant manager, and the corporate executive responsible for overall plant nuclear safety.

2.2.5 Operation of the unit shall not be resumed until authorized by the NRC.

O O

HATCH UNIT 1 2.0-2 REVISICN){

LC0 Ap.plicability 3.0 g

y 3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LC0 3.0.1 LCOs shall be met during the MODES or other specified conditions in the Applicability, except as provided in

~

LC0 3.0.2 and LC0 3.0.7.

LC0 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as provided in LCO 3.0.5 and LC0 3.0.6.

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

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

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

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

LC0 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall not be made except when the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time. This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required (continued)

HATCH UNIT 1 3.0-1 REVISION A l

l LC0 Applicability 3.0 l 3.0 LC0 APPLICABILITY LC0 3.0.4 to comply with ACTIONS or that are part of a shutdown of the (continued) unit. l Exceptions to this Specification are stated in the individual Specifications. These exceptions allow entry into MODES or other specified conditions in the !

Applicability when the associated ACTIONS to be entered allow unit operation in the MODE or other specified I condition in the Applicability only for a limited period of time.

LC0 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, and 3.

LC0 3.0.5 Equipment removed from service or declared inoperable to l comply with ACTIONS may be returned to service under administrative control solely to perform testing required to demonstrate its OPERABILITY, the OPERABILITY of other equipment, or variables to be within limits. This is an exception to LC0 3.0.2 for the system returned to service under administrative control to perform the required testing. h LC0 3.0.6 When a supported system LC0 is not met solely due to a support system LC0 not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LC0 ACTIONS are required to be entered. This is an exception to LC0 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification 5.5.10, " Safety Function Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LC0 in which the loss of safety function exists are required to be entered.

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

(continue 3T HATCH UNIT 1 3.0-2 REVISION ((

SR Applicability-3.0

/~h L/ 3.0 SR APPLICABILITY (continued)

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall not be made unless the LCO's Surveillances have been met within their specified Frequency. This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

SR 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, and 3.

O l

HATCH UNIT 1 3.0-5 REVISION /{

-- - - -. - - . - .~

, Responsibility 5.1 5.0 ADMINISTRATIVE CONTROLS 5.1 Responsibility 5.1.1 The plant manager shall provide direct executive oversight over l all aspects of Plant Hatch.

5.1.2 An assistant plant manager shall be responsible for overall unit l operation, except for the Radiological Environmental Monitoring Program as described below and for delegation.in writing of the succession of this responsibility during his absence. Certain plant support functions shall also be the responsibility of an assistant plant manager.

5.1,3 The plant manager or his designee shall be responsible for the l Radiological Environmental Monitoring Program and for the writing of the Annual Radiological Environmental Operating Report.

. 5.1.4 Each of the individuals in Specification 5.1.1 through.

Specification 5.1.3 is responsible for the accuracy of the procedures needed to implement his responsibilities.

5.1.5 The shift superintendent shall be responsible for the control room command function. During any absence of the shift superintendent from the control room while either unit is in MODE 1, 2, or 3, an individual with an active Senior Reactor Operator (SR0) license shall be designated to assume the control room command function.

During any absence of the shift superintendent from the control l room while both units are in MODE 4 or 5, an individual with an active SRO license or Reactor Operator license shall be designated ,

to assume the control room command function.

1 i

O HATCH UNIT 1 5.0-1 REVISIONh

Organization 5.2 5.0 ADMINISTRATIVE CONTROLS 5.2 Organization l

l 5.2.1 Onsite and Offsite Oraanizations Onsite and offsite organizations shall be established for unit operation and corporate management, resptctively. The onsite and offsite organizations shall include the positions for activities affecting safety of the nuclear power plant.

a. Lines of authority, responsibility, and communication shall be defined and established throughout highest management levels, intermediate levels, and all operating organization positions. These relationships shall be documented and updated, as appropriate, in organization charts, functional descriptions of departmental responsibilities and relationships, and job descriptions for key personnel positions, or in equivalent forms of documentation. These requirements, including plant specific titles of those personnel fulfilling the responsibilities of the positions delineated in these Technical Specifications, shall be documented in the Plant Hatch Unit 1 FSAR;

b. An assistant plant manager shall be responsible for overall safe operation of the plant and shall have control over l 8W those onsite activities necessary for safe operation and maintenance of the plant;

c. The corporate executive responsible for Plant Hatch shall l take any measures needed to ensure acceptable performance of the staff in operating, maintaining, and providing technical support to the plant to ensure nuclear safety; and

d. The individuals who train the operating staff, carry out health physics, or perform quality assurance functions may report to the appropriate onsite manager; however, these individuals shall have sufficient organizational freedom to ensure their independence from operating pressures.

5.2.2 Unit Staff i l

The unit staff organization shall include the following: )

a. A total of three plant equipment operators (PE0s) for the two units is required in all conditions. At least one of (continued)

O HATCH UNIT 1 5.0-2 REVISIONh 1

_ __--___--- ________ -_ _. l

Organization 5.2 m

() 5.2 Organization 5.2.2 Unit Staff

a. (continued) the required PE0s shall be assigned to each reactor containing fuel,

b. At least one licensed Reactor Operator (RO) shall be present in the control room for each unit that contains fuel in the reactor. In addition, while the unit is in MODE 1, 2, or 3, at least one licensed Senior Reactor Operator (SRO) shall be present in the control room.

c. The minimum shift crew composition shall be in accordance with 10 CFR 50.54(m)(2)(i). Shift crew composition may be less than the minimum requirement of 10 CFR 50.54(m)(2)(i) and 5.2.2.a for a period of time not to exceed 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months in order to accommodate unexpected absence of on duty shift crew members provided immediate action is taken to restore the shift crew composition to within the minimum requirements.

d. An individual qualified to implement radiation protection v procedures shall be on site when fuel is in the reactor.

The position may be vacant for not more than 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months , in order to provide for unexpected absence, provided immediate action is taken to fill the required position.

e. Administrative procedures shall be developed and implemented to limit the working hours of unit staff who perform safety related functions (e.g., licensed and non-licensed operations personnel, health physics technicians, key maintenance personnel, etc.).

Adequate shift coverage shall be maintained without routine heavy use of overtime. The objective shall be to have operating personnel work a nominal 40 hour4.62963e-4 days 0.0111 hours 6.613757e-5 weeks 1.522e-5 months week while the unit is operating. However, in the event that unforeseen problems require substantial amounts of overtime to be used, or during extended periods of shutdown for refueling, major maintenance, or major plant modification, on a temporary basis the following guidelines shall be followed:

1. An individual should not be permitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months straight, excluding shift turnover time;

, (continued)

G HATCH UNIT 1 5.0-3 REVISION D

i 1

Organization l 5.2 1 5.2 Organization 5.2.2 Unit Staff l

e. (continued) I 1

2. An individual should not be permitted to work more than l 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months in any 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months period, nor more than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months l in any 48 hour5.555556e-4 days 0.0133 hours 7.936508e-5 weeks 1.8264e-5 months period, nor more than 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months in any '

7 day period, all excluding shift turnover time; l

3. A break of at least 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months should be allowed between work periods, including shift turnover time;

4. Except during extended shutdown periods, the use of overtime should be considered on an individual basis and not for the entire staff on a shift.

Any deviation from the above guidelines shall be authorized l by an assistant plant manager, or by higher levels of (

l management, in accordance with established procedures and l with documentation of the basis for granting the deviation.

Controls shall be included in the procedures such that individual overtime shall be reviewed monthly by an l assistant plant manager or designee to ensure that excessive

, hours have not been assigned. Routine deviation from the above guidelines is not authorized.

f. The operations manager shall hold an active or inactive SR0 l license.

l g. The Shift Technical Advisor (STA) shall provide advisory technical support to the shift supervisor in the areas of l thermal hydraulics, reactor engineering, and plant analysis with regard to the safe operation of the unit. In addition, the STA shall meet the qualifications specified by the Commission Policy Statement on Engineering Expertise on Shift.

l HATCH UNIT 1 5.0-4 REVISION

l Programs and Manuals 5.5

. '5.0 ADMINISTRATIVE CONTROLS 5.5 Programs and Manuals The following programs and manuals shall be established, implemented, and maintained.

5.5.1 Offsite Dose Calculation Manual (ODCM)

a. The ODCM shall contain the methodology and parameters used in the calculation of offsite doses resulting from radioactive gaseous and liquid effluents, in the calculation of gaseous and liquid effluent monitoring alarm and trip setpoints, and in the conduct of the radiological <

environmental monitoring program; and

b. The ODCM shall also contain the radioactive effluent controls and radiological environmental monitoring activities, and descriptions of the information that should be included in the Annual Radiological Environmental-Operating and Radioactive Effluent Release reports required by Specification 5.6.2 and Specification 5.6.3, respectively.

( Licensee initiated changes to the ODCH:

a. Shall be documented and records of reviews performed shall be retained. This documentation shall contain:

1. sufficient information to support the change (s) and appropriate analyses or evaluations justifying the change (s), and

2. a determination that the change (s) maintain the levels of radioactive effluent control required by 10 CFR 20.106, 40 CFR 190, 10 CFR 50.36a, and 10 CFR 50, Appendix I, and does not adversely impact the accuracy c reliability of effluent, dose, or setpoint calculations.

b. Shall become effective after review and acceptance by the I onsite review committee and the approval of the plant manager; and (continued)

HATCH UNIT 1 5.0-7 REVISIONh F

Programs and Manuals 5.5 5.5 Programs and Manuals 5.5.1 Offsite Dose Calculation Manual (00CM) (continued)

c. Shall be submitted to the NRC in the form of a complete, legible copy of the entire ODCH as a part of or concurrent with the Radioactive Effluent Release Report for the period of the report in which any change in the ODCM was made.

Each change shall be identified by markings in the margin of the affected pages, clearly indicating the area of the page that was changed, and shall indicate the date (i.e., month and year) the change was implemented.

5.5.2 Primary Coolant Sources Outside Containment This program provides controls to minimize leakage from those portions of systems outside containment that could contain highly ,

radioactive fluids during a serious transient or accident to !

levels as low as practicable. The systems include the Core Spray, l High Pressure Coolant Injection, Residual Heat Removal, Reactor l Core Isolation Cooling, and Reactor Water Cleanup. The program ;

shall include the following: I

a. Preventive maintenance and periodic visual inspection '

requirements; and I

b. System leak test requirements for each system, to the extent permitted by system design and radiological conditions, at ,

refueling cycle intervals or less. !

5.5.3 Post Accident Samplina This program provides controls that ensure the capability to obtain and analyze reactor coolant; radioactive gases and particulates in plant gaseous effluents; and containment atmosphere samples under accident conditions. The program shall include the following: )

1

a. Training of personnel;

b. Procedures for sampling and analysis; and

c. Provisions for maintenance of sampling and analysis equipment. l (contin,ued)

HATCH UNIT 1 5.0-8 REVISION A

J -,

1 1

UNIT 1 IMPROVED BASES l

i 1

1 l

l 1

l i

i l

i I

1 1

I 1

l l

l 1

I 1

1 1

l l

l 1

___._______I

LC0 Applicability B 3.0 BASES LCO 3.0.3 assemblies in the spent fuel storage pool." Therefore, this (continued) LCO can be applicable in any or all MODES. If the LC0 and the Required Actions of LCO 3.7.8 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LC0 3.7.8 of " Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LC0 3.0.3. These exceptions are addressed in the individual Specifications.

LC0 3.0.4 LC0 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LCO is not met. It precludes placing the unit in a MODE or other specified condition stated in that Applicability l (e.g., Applicability desired to be entered) when the following exist:

a. Unit conditions are such that the requirements of the l LC0 would not be met in the Applicability desired to be entered; and g

b. Continued noncompliance with the LC0 requirements, if the Applicability were entered, would result in the i unit being required to exit the Applicability desired to be entered to comply with the Required Actions. 1 Compliance with Required Actions that permit continued operation of the unit for an unlimited period of time in a l MODE or other specified condition provides an acceptable l level of safety for continued operation. This is without i regard to the status of the unit before or after the MODE l change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions. j The provisions of this Specification should not be '

interpreted as endorsing the failure to exercise the good practice of restoring systems or components to OPERABLE status before entering an associated MODE or other specified condition in the Applicability, j The provisions of LCO 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability (continued)

HATCH UNIT 1 B 3.0-5 REVISION G

LC0 Applicability B 3.0 l BASES ,

LCO 3.0.4 that are required to comply with ACTIONS. In addition, the (continued) provisions of LC0 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability that result from any unit shutdown.

Exceptions to LCO 3.0.4 are stated in the individual Specifications. Exceptions mey apply to all the ACTIONS or to a specific Required Action of a Specification.

LC0 3.0.4 is only applicable when entering MODE 3 from MODE 4, MODE 2 from MODE 3 or 4, or MODE 1 from MODE 2. '

Furthermore, LC0 3.0.4 is applicable when entering any other specified condition in the Applicability only while operating in MODE 1, 2, or 3. The requirements of LC0 3.0.4 do not apply in MODES 4 and 5, or in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the'specified limits), as permitted by SR 3.0.1. Therefore, changing MODES or other specified conditions while in an ACTIONS Condition, either in compliance with LC0 3.0.4 or where an exception to LC0 3.0.4 is stated, is not a violation of SR 3.0.1 or SR 3.0.4 for those Surveillances that do not have to be performed due to the associated inoperable equipment. However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring conipliance with the affected LCO.

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

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

b. The OPERABILITY of other equipment.

(continued)

HATCH UNIT 1 B 3.0-6 REVISIONKf

d LC0 Applicability B 3.0

.q Q BASES LC0 3.0.4 The administrative controls ensure _the time the equipment is (continued) returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to 4 perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance.

O (continued,)

HATCH UNIT 1 B 3.0-X (oA REVISIONKg

SR Applicability B 3.0 m

C BASES SR 3.0.3 period of up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified (continued) Frequency, whichever is less, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met.

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

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

s When a Surveillance with a Frequency based not on time

[d ) intervals, but upon specified unit conditions or operational situations, is discovered not to have been performed when specified, SR 3.0.3 allows the full delay period of 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months to perform the Surveillance.

SR 3.0.3 also provides a time limit for completion of Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions.

Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence. Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used as an operational convenience to extend Surveillance intervals.

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

delay period. If a Surveillance is failed within the delay I period, then the equipment is inoperable, or the variable is outside the specified limits and the Completion Times of the (continued)

HATCH UNIT 1 B 3.0-13 REVISION A l

l l

SR Applicability I B 3.0 BASES l

SR 3.0.3 Required Actions for the applicable LC0 Conditions begin ;

(continued) immediately upon the failure of the Surveillance.

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

l l

SR 3.0.4 SR 3.0.4 establishes the requirement that all applicable SRs must be met before entry into a MODE or other specified I condition in the Applicability. This Specification ensures I that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other 1 specified conditions in the Applicability for which these l systems and components ensure safe operation of the unit. l i

However, in certain circumstances, failing to meet an SR I will not result in SR 3.0.4 restricting a MODE change or )

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

apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance (s) within the specified Frequency, on equipment that is inoperable, does not result in an SR 3.0.4 restriction to changing MODES or other specified conditions of the Applicability. However, since the LC0 is l not met in this instance, LC0 3.0.4 will govern any i restrictions that may (or may not) apply to MODE or other specified condition changes.

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

The provisions of SR 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability l that are required to comply with ACTIONS. In addition, the !

provisions of SR 3.0.4 shall not prevent changes in MODES or 1

(continued) i HATCH UNIT 1 B3.0-1[4- REVISION / F

SR Applicability B 3.0 l BASES SR 3.0.4 other specified conditions in the Applicability that result (continued) from any unit shutdown.

The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not necessary. The specific time frames and conditions necessary for meeting the SRs are specified in the l

1 l

l O l (continued)

HATCH UNIT 1 B 3.0- h H A REVISIONAF

l l

i SR Applicability l B 3.0 1 1

I BASES

]

1 SR 3.0.4 Frequency, in the Surveillance, or both. This allows (continued) performance of Surveillances when the prerequisite condition (s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the ;

Applicability of the associated LC0 prior to the performance or completion of a Surveillance. A Surveillance that could not be performed until after entering the LCO Applicability would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.

SR 3.0.4 is only applicable when entering MODE 3 from MODE 4, MODE 2 from MODE 3 or 4, or MODE 1 from MODE 2.

Furthermore, SR 3.0.4 is applicable when entering any other specified condition in the Applicability only while operating in MODE 1, 2, or 3. The requirements of SR 3.0.4 do not apply in MODES 4 and 5, or in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications C] sufficiently define the remedial measures to be taken.

O s HATCH UNIT 1 B3.0-[ REVISIONff

4) --

UNIT 1 MARKUP OF CURRENT TECHNICAL SPECIFICATIONS AND DISCUSSION OF CHANGES 1

I O

l 4

l O l l

i

~

$2n~bo N 2-. O ADMINISTRATIVE CONTROL 5 I

O

,k. The Radiological Environmental Monitoring Program and the results thereof annually.

W Dnsh 1. The 00CM, Process Control Program, and implementing procedures d A*# at least once per 24 months.

fot S4W CM D

MTWITY m

6.5.2.g. The SR8 shall report to and advise the Vice President-Nuclear on l those areas of responsibility specified in sections 6.5.2.7. and 6.5.2.8.

f RECORD $

6.5.2.10. Records of SR8 activities shall be prepared, approved and distributed as indicated below:

1 i a. Minutes of each SR8 meeting shall be prepared, approved and forwarded to the Vice President-Muclear within 14 days following l ea - eting.

b. Reports of reviews encompassed by section 6.1.2.7. above, shall be prepared, approved and forwarded to the Vice .eresident-Nuclea r l within 14 days following completion of the reviw.

t

c. Audit reports encompassed by section 6.5.2.8. above, shall be forwarded to the Vice President-Nuclear and to the management positions l [..

responsible for the areas audited within 30 days after completion of the audit.

6.6. REPORTA8LE EVENT ACTION 6.6.1. The following actions shall be taken for REPORTABLE EVOWTS:

i a. The Coesnission shall be notified and/or a report submit ted pursuant to the requirements of section 50.73 to 10 CFR part 50, and

b. Each REPORTA8LE EVENT shall be reviewed by the PR8 and the results of this review shall be submitted to the SRB, the Genertl Manager-Nuclear Plants and the Vice President-Nuclear.- .

6.7. SAFETY LIMIT VIOLATION L1 4.7.1. The following actions shall be taken in the event a Safety Limit is

' violated:

L . 7. l. a. The unit shall be placed in at least HOT SHUTDOWN within 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months ,

b. (The Safety Limit violation shall be reported to the Conssission as W (soon as practical and in all cases within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months of occurrence.

..t . .../ m. mv 7. . . ; 4. .. i ,. ,. i .. . . l l' M ({ The Sn . e&as.shall

, sad-44e i ;^ ...... be L. notified

' .e. . "' within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months .

f kvll Mkm3f omd CWw& Wecuhh respnih.h wa)\ffa Y t\uciaM SaQ avd M o$Nlt Thri%) Centmi/hu,.

HATCH - UNIT 1 6-12 Amendment No. 65, 795, JJ6, H 5, 149, 155

- 84s

1 l

1 ADMINISTRATIVE CONTROLS W1od 2-b l l

SAFETY LIMIT VIOLATION (Continued) 1.'2.. O c. A Licensee Event Report shall be prepared pursu to 10 CFR 50.73. !

LJ {). ~) \

d. The Licensee Event Report shall be submitted to e Commission in Nq accordance with .10_CFR 50.73, .^ M and to._. ..., m.. ".0. .L ".......'

]

(p k,' ___ m._,___ _i _ a u_ uu.

i..- -ithin 30 davt

. UU P ? oftfev101st @;ggniw m g gez Np(& m g,and 1 Dq N1 A wle W1M (Aspms5Le,,hr or*1aN p{artlthKAl*'

h

~

s.n. PR0cEmmEs j 6.8.1 Written procedures shall be established, implemented and maintained covering the activities referenced below:

,. bevod a. The applicable procedures recommended in Appendix A of Regulatory Guide 1.33, Revision 2, February 1978 crrk

( _

&(i Co, kl>" ,

b.

c.

Refueling operations.

Surveillance and test activities of safety-related equipment.

d. Security Plan implementation.

e. Emergency Plan implementation.

f. Fire Protection Program taplementation.

g. PROCESS CONTROL PROGRAM implementation.

n. 00CM implementation.

6.8.2 Each procedure of 6.8.1 and other procedures which the General

.t Manager-Muclear Plant, the AGM-PO, or the AGM-P5 has determined to affect nuclear safety, and changes thereto, sha11 be reviewed by the PR8 and approved by the appropriate member of plant management, designated by the General Manager-Nuclear Plant, the AGM-PO, or the AGM-PS prior to implementation. The General Manager-Muclear Plant, the AGM-PO, or the AGM-PS will approve administrative procedures, security plan implementing procedures, and changes thereto. The Manager-Plant Training and Emergency Preparedness shall approve the emergency plan implementing procedures and changes thereto. All other procedures of this specification and changes thereto will be approved by the department head designated by the General Manager-Nuclear Plant, the AGM-PO, or the AGM-PS.

The procedures of this specification shall be reviewed periodically as set forth in administrative procedures, j 6.8.3 Temporary changes to procedures of 6.8.1. above may be made provided:

The intent of the original procedure is not altered.

a.

! HATCH - UMtT 1 6-13 Amendment No. 64, W9, 4M, 446, IM,

( 444, 175 ,

1 hed l

O DISCUSSION OF. CHANGES ITS: SECTION 2.0 - SAFETY LIMITS ADMINISTRATIVE A.1 Reformatting and renumbering requirements are in accordance with the BWR Standard Technical Specifications, NUREG 1433'. As a result, the Technical Specifications should be more readily readable and, therefore, understandable by plant operators, as well as other users. During this reformatting and renumbering process, no technical changes (either actual or interpretational) to the Technical Specifications were made unless they were identified and justified. In the specific case of the Safety Limits and Limiting Safety System Settings section, the new section number is 2.0, and the section has been retitled to only include Safety Limits (see comment A.4 below).

A.2 The reactor pressure limit unit of measure has been changed from psia to

)sig. In addition, the requirement for when the MCPR limit is applicable las been reduced slightly (by adding the " equal to" sign) for consistency with the BWR Standard Technical Specifications, NUREG 1433. While this change is actually more restrictive, since it is so minor, it is considered an administrative change.

A.3 The description of. the actual safety limit violation has been deleted.

This information is more appropriately located in the Bases and does not add any detail needed for compliance with the MCPR Safety Limit.

A.4 The technical content of this requirement is being moved to Section 3.3 of the proposed Technical Specifications in accordance with the format of the BWR Standard Technical Specifications, NUREG 1433. Any technical changes to this requirement will be addressed with the content of the proposed chapter location.

A.5 The wording has been changed from specifying the actual level to the more generic words " greater than the top of active irradiated fuel." The intent is not changed; thus, this is considered an administrative change only.

A.6 A current requirement of 10 CFR 50.36, stating that if a Safety Limit is violated, critical " Operation of the unit will not be resumed until authorized by the NRC" has been added (proposed 2.2.5). Since it is a regulation, the addition of this to the Technical Specifications is considered administrative in nature.

A.7 The current plant specific titles are changed to generic titles. ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

TECHNICAL CHANGE - MORE RESTRICTIVE O a.1 18e limit ee cere fiew 4s new spec 4fiea as ereater than er e ea, te. T8e current Safety Limits do not address the situation when core low is equal HATCH UNIT 1 1 REVISIONfh

. a

( \ DISCUSSION OF CHANGES

,. \ ITS: SECTION 2.0 - SAFETY LIMITS l

ADMINISTRATIVE -

(continued) to the limit. This change resolved a discontinuity between SL 1.1.A and SL 1.1.B in the current Safety Limits.

M.2 The APPLICABILITY of each of the SLs is extended to all MODES of operation. Although it is physically impossible to violate some SLs in some MODES, any SL violation should receive the same attention and response.

I O

l 1

I O l HATCH UNIT 1 hdA REVISIONKf

l I

l i

o Insert 3.0A (continued) 1 t LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall not be made except when the associated ACTIONS to be i i

M.) entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time. This Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required to. comply with ACTIONSg or that are part l of a shutdown of the unit. 7 !

Qto s.0 4 is artly1ylicable 1

%h ,'d a MOOK er Exceptions to this Specification are stated in the l g gpq W,% 4 -

individual Specifications. These exceptions allow entry into MODES or other specified conditions in l

b A# I'D4.jg # the Applicability when the associated ACTIONS to l

l (M60F5 f, 2, and- be entered allow unit operation in the MODE or !

( other specified condition in the Applicability l

( only for a limited period of time.

LCO 3.0.5 Equipment removed from service or declared

.l inoperable to comply with ACTIONS may be returned

to service under. administrative control solely to l

perform testing required to demonstrate its A

( h-lhtj g OPERABILIT Q 4he OPERABILITY of other equipment, ;

-em=seesebbes to be within limits. This is an 1 Os exception to LCO'3.0.2 for the system returned to service under administrative control to perform the required testing.

LCO 3.0.6 When a supported system LCO is not met solely due bM to a support system LCO not being. met, the Conditions and Required Actions associated.with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, additional evaluations and limitations may be required in accordance with Specification

5.5.10, " Safety Function Determination Program J..

(SFDP) . " If_a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss of safety function exists are required to be entered.

O Hatch Unit 1 Insert 3.0-1 M8

Insert 4.0c SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then L- compliance with the requirement to declare the LCO not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whichever is less. This delay period is permitted to allow performance of the Surveillance.

If the Surveillance is not performed within the

, delay period, the LCO must immediately be declared not met, and the applicable Condition (s) must be entered. ,

When the Surveillance is performed within the delay period and the Surveillance is not met, the LCO must immediately be declared not met, and the

. applicable Condition (s) must be entered.

Insert 4.0D SR 3.0.4 Entry into a MODE or other specified condition in j

the Applicability of an LCO shall not be made J- l% i unless the LCo's Surveillances have been met i

l' within their specified Frequency. This provision shall not prevent entry into MODES or other l specified conditions in the Applicability that are

. required to comply with ACTIONS or that are part of a shutdown of the unit.

i QR s.04 is only ylicabk h.wfry hjo a McDEx oNW swihd andHrk in & App // cob /0/y Y in Mope.s I, 2, and 3.

U i-

)-

0 Hatch Unit 1 Insert 3.0 S-

7d 9

DISCUSSION OF CHANGES ITS: SECTION 3.8.1 - AC SOURCES - OPERATING

(

ADMINISTRATIVE (continued)

A.4 These two possible values for the overspeed trip point are fixed by the design of the DG unit. The appropriate value (i.e., the most limiting, j which is 65.5 Hz) is presented in the proposed Technical Specifications. l This presentation eliminates the basis for the accepted value from the l Technical Specifications, moving it to the Bases. Since there is no I difference in the requirement, this is considered administrative. l l

A.5 The details relating to the required day tank load have been moved to a Surveillance Requirement (proposed SR 3.8.1.3). No technical changes are i being made; therefore, this change is considered administrative in nature. ,

1 A.6 These requirements are governed by the definition of OPERABILITY of the DGs as explained in the SR section of the Bases. They are also covered by the respective SRs. Therefore, this "LC0" has been deleted and the change is considered administrative. !

A.7 Proposed Note 1 to SRs 3.8.1.9, 3.8.1.10, and 3.8.1.17 and Note 2 to SR 3.8.1.13 have been added. This allows an engine prelube prior to DG start. The current Specifications do not prohibit this allowance and the addition is provided for clarity. As such, it is considered administrative.

A.8 The Frequency of "every scheduled refueling outage" has been modified to be "18 months", since 18 months is a normal refueling outage schedule.

Note 2 to this SR ensures the SR is performed while the unit is shutdown.

A.9 Proposed Note 3 has been added to clarify that a single test of the swing DG will suffice to meet the requirements of both units. This addition provides clarity and is considered administrative only, since the test is a DG test only (e.g., it does not test unit specific components), and is similar to other notes provided in the Surveillance section. This specific clarification was explicitly added to the Unit 1 CTS by Amendment 192, dated February 24, 1994.

A.10 The requirement to perform this Surveillance after the 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months run has been deleted. As indicated by the

footnote, it is acceptable to perform j the test after a 2 2 hour2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months run at 2 2565 kW. Therefore, since it is already allowed to be performed in this manner, this change is considered administrative. This specific clarification was explicitly added to the Unit 1 CTS by Amendment 192, dated February 24, 1994.

A.11 The format of the proposed Technical Specifications would allow multiple Conditions to be simultaneously entered. Three or more sources could be inoperable, ACTIONS being taken in accordance with the Specification, and proposed LC0 3.0.3 entry conditions not met. To preserve the existing intent of Specification 3.9.A.7.8, ACTION H is proposed. ACTION H will O cover these conditions in which the unit is outside accident analyses.

HATCH UNIT 1 2 REVISIONKf 4

4 ,. .-4 --- _- . _ _ _ _ _- _ _ -__ __ ___ _ _ _ ______ _______ _

I l

I DISCUSSION OF CHANGES ITS: SECTION 3.8.1 - AC SOURCES - OPERATING TECHNICAL CHANGE - LESS RESTRICTIVE (continued)

L.3 The limitation on the time to reach full DG load from a manual synchronization is proposed for deletion. DG loading should be done in accordance with manufacturer's recommendations to minimize wear on the engine. Additionally, placing a time limitation on the operator to accomplish this loading results in an increased potential for error and subsequent unavailability of the DG. The starting, loading, subsequent full load operation, and automatic start and loading testing required by other Technical Specification Surveillances is adequate to confirm the DG's capability without the 120-second loading requirement. In addition, for clarity, Note 2 has been added to this SR to specifically allow gradual loading.

L.4 The Surveillance Frequency has been changed from "specified for the diesel in Specification 4.9.A.2.a.1" (effectively the DG test schedule table) to "31 days". This is because DG failures that result in a more frequent DG test frequency have no impact on this function's ability to perform its intended function.

L.5 The proposed " hot restart" test (proposed SR 3.8.1.13) does not require the restart be a simulated loss of offsite power (auto-start signal). The

" hot restart" is proposed to simply be any start signal, as would be

\ required by the monthly test. Furthermore, the specific requirement to be automatically loaded with emergency loads is excessive; the DG has demonstrated its ability to power loads while " hot" (i.e., the 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months run). Additionally, the automatic loading is an unnecessary repetition of other SRs which confirm the DG ability to accept sequenced loads. DG loading following the hot restart is proposed to be controlled by plant procedures and appropriate manufacturer recommendations for loading following any DG start. This revision allows greater flexibility in scheduling DG testing, while not compromising any necessary demonstration of DG capability. This change was approved as Amendment 192, dated February 24,1994 (note this amendment renumbered this surveillance as 4.9.A.2.a.11).

L.6 The time to reach MODE 4, Cold Shutdown has been extended from 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months to 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months . This provides the necessary time to shut down and cool down the ,

plant in a controlled and orderly manner that is within the capabilities ;

of the unit, assuming the minimum required equipment is OPERABLE. This extra time reduces the potential for a unit upset that could challenge i safety systems. This time is consistent with the BWR Standard Technical l Specifications, NUREG 1433.

l O l l

l l

HATCH UNIT 1 7 j REVISION \ f l

._ l

_- . _- ~

Sp a.%'h'o8 LI '

6.0 ADMINISTRATIVE CONTROLS p [,l 6.1 RESPONSIBILITY g j, [ 6.1.0 [The General Managerjtuclear Plantlshall provide direct executive oversight over all aspects of Plant Hatch.

f,l,2, 6.1.1 the mssistant ueneral Manaaer-Plant Onorations (AGM-P03 shall be r responsible for overall unit operation, except for the Radiological Environmental Monitoring Program as described below and for delegation in writing of the succession of this responsibility during _his absence. Ce_rt ain plant ennnart functinne tsall be the responsibility of ane assistant uenern Enaanr Diant hannet fArd-Pn f, l,3 6.1.2 ThefGeneral ManagerAelaae Planl or his designee shall be responsible for the Radiorogicai tavironmental___ Monitoring Program &sNescrmed in'3 CiDecVication L I9 M Ifor the writing of the Annual Radiological A ,\ l Environmental surve llance Report, g f,l y 6.1.3 Each of theEbove-mentionedndividuals is responsible for the accuracy of the procedures needed to implement his responsibilities.

.2 ORGANIZATIO NMI 6.2.1 0FFSITE AND ONSITE ORGANIZATION N Onsite and offsite organizations shall be established for unit operation and corporate management, respectively. The onsite and offsite organizations shall include the positions for activities affecting the safety of the nuclear power plant,

4. Lines of authority, responsibility, and communication shall be established and defined for the highest management levels through N e Ot* W intermediate levels to and including all operating organization positions. These relationships shall be documented and updated, as f-( g q'T gV appropriate, in the form of organization charts, functional descriptions of departmental responsibilities and relationships, and yT S s f,1' job descriptions for key personnel positions, or in equivalent forms of documentation. These requirements shall be documented in the Orp4' k 4La SW

. Plant Hatch Unit 2 updated FSAR.

b. The AGM-PO shall be responsible for overall unit safe operation and shall have control over those onsite activities necessary for safe operation and maintenance of the plant.

c. The Vice President-Nuclear shall have corporate responsibility for overall alant nuclear safety and shall take any measures needed to ensure acceptable performance of the staff in operating, maintaining and providing technical support to the plant to ensure nuclear safety,

~

k 1

l l

l O

HATCH - UNIT I 6-1 Amendment No. 66, M9, MO, MS, l MG, M6, 190 l l

I Jr L

l INSERT 1 for ITS 5.1 The b juperintendent Jkf(jh M shall be responsible for the control room command funcuon. During any absence of the from the control room while either unit is in MODE 1, 2, or 3, an ,lh individual with an active Senior Reactor Operator (SRO icense shall be designated to assume the control room command function. ]

During any absence of the Ee& from the control room while bothy units are in MODE 4 or 5, an individual with an active SRO license g

or Reactor Operator license shall be designated to assume the control room command function, r 1 fh's (( Suf40lMYN O

O HATCH UNIT 1

.- - .. - . _ _ - - ___--____J

l

\

i 0

, DISCUSSION OF CHANGES ITS: SECTION 5.1 - RESPONSIBILITY 1

ADMINISTRATIVE A.1 Due to relocation of the Radiological Environmental Monitoring Program from the TS, reference to Specification 6.19 is deleted. A description of

, the changes to CTS 6.19 is contained in the discussion of changes for that i TS.

A.2 The term "above-mentioned individuals" - nged to reference the TS (ITS 5.1.1 thtough 5.1.3) where these indiv.. are named.

A.3 The current plant specific titles are changed to generic titles. ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilitiet, to be included in the FSAR. The specific titles do not alter f Se responsibilities delineated in the Technical Specifications. Theref> , his is considered an administrative change only.

TECHNICAL CHANGES - MORE RESTRICTIVE M.1 Proposed ITS 5.1.5 adds requirements to define the control room command function. These requirements are in addition to those in the present TS, and thus, represent a more restrictive change.

l 0 . ,

HATCH UNIT 1 1 REVISION / F

{pgre CRYCh $s 6.0 ADMINISTRATIVE CONTROLS l

% 6.1 RESPONSIBILITY l

6.1.0 The General Manager-Nuclear Plant shall provide direct executive I p oversight over all aspects of Plant Hatch.

of 6.1.1 The Assistant General Manager-Plant Operations (AGM-PO) shall be 9 responsible for overall unit operation, except for the Radiological Orf7y,,5,f> Environmental Monitoring Program as described below and for delegation in writing of the succession of this responsibility during his absence. Certain 2.esg('lg plant support functions shall be the responsibility of the Assistant General Manager-Plant Support (AGM-PS).

4gg 6.1.2 The General Manager-Nuclear Plant or his designee shall be responsible for the Radiological Environmental Monitoring Program as described in Specification 6.19 and for the writing of the Annual Radiological l Environmental Surveillance Report.

6.1.3 Each of the above-mentioned individuals is responsible for the accuracy of the procedures needed to implement his responsibilities. j f 2. 6.2 ORGANIZATION

,f,*2, , l 6.2.1 0FFSITE AND ONSITE ORGANIZATIONS Onsite and offsite organizations shall be established for unit operation and corporate management, respectively. The onsite and offsite organizations shall include the positions for activities affecting the safety of the nuclear power plant.

f *2. h 4 a. Lines of authority, responsibility, and communication shall be established and defined for the highest management levels through p),

- intermediate levels to and including all operating organization (9 )gddk /N4 g fM"j positions. These relationships shall be documented and updated, as Q hk 04 h (2, fhilihM -

appropriate, in the form of organization charts, functional descriptions of departmental responsibilities and relationships, and fy Q(lat job descriptions for key personnel positions, or in equivalent forms Oh b # ;l e r M ed['[Mg in i g of documentation. These requiremilitTeshall be documented in the Plant Hatch Unit ? undated FSAR.

bo.

u$ - ,'2. le dr' b.

_n assisfw+ #kmt memasM)

~ --^ - shall be respons10 e for overall unit safe operation and shall have control over those onsite activities necessary for safe operation and maintenance of the plant.

f,2 , l . C c. The Vice President-Nuclear shall have corporate responsibility for overall plant nuclear safety and shall take any measures needed to ensure acceptable performance of the staff in operating, maintaining and providing technical support to the plant to ensure nuclear safety.

O HATCH - UNIT 1 6-1 Amendment No. 66, M9, +M, M6, Ms, Ms, 190 lof 7

6.0 ADMINISTRATIVE CONTROLS Ij Ac.

p t'caNcn Ik 48-hour period, nor more than 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months in any 7-day period, all excluding shift turnover time.

g,7,7, 4 (3) A break of at least 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months should be allowed between work periods, including shift turnover time. )

(4) Except during extended shetdown periods, the use of overtime should be considered on an individual basis and not for the entire staff on a shift.

Any deviation from the above guidelines shall be authorized by ee- ,

--_ - an u. aru ne or higher level of management, in accordance with ~

f _pa 0,55t5MN established procedures and with documentation of the basis for j

i mag 40 j granting the deviation. Controls shall be included in the procedures 1

( such that individual overtime shall be reviewed monthly by 4he !

??" ^^, ^.L ff" M, or designed to assure that excessive hours have

~

\

not been assigned. Routine deviation from the above guidelines is 4,3 not authorized, g,2,2,[ h.

G ThaIslanager Vfdoaratd ons M Ope M ons Super 1 M dents, a h all t Supervisernsha'l hold a manier reactor operator Itcense.' The p I operator g hall hol Q reactor % erator license g LA.4 O

O - e- > ..> - e - t ho. e. . m . >,s 347

m INSERT 2 FOR ITS 5.2 4

5.2.2.g technical The support to Shift Technical the piift Advisor (STA)[shall pervisorprovide advisory (SS) in the h-areas of thermal hydraulits, reactor engineering, and plant analysis with regard to the safe operation of the unit. In addition, the STA shall meet the qualifications specified by the Commission Policy Statement on Engineering Expertise on Shift.

1 O

O HATCH UNIT 1 74 7

/' DISCUSSION OF CHANGES ITS: SECTION 5.2 - ORGANIZATION ADMINISTRATIVE A.1 The definitions of the various Operational Conditions are located in current Specification 1.0, Definitions, and in the proposed Technical Specifications in ITS 1.1, " Definitions." Therefore, this table notation is unnecessary and has been deleted.

A.2 The current Technical Specification provides examples of the Unit staff positions who perform safety-related functions and whose working hours are limited. Since these examples may not include all positions that could be-limited and since these positions may change, the examples have been generalized. The modification of these examples clarifies present requirements and thus is an administrative change.

A.3 The current plant specific titles are changed to generic titles. ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfi'lling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

O l

l O 1 HATCH UNIT 1 1 REVISIONf{

i

ADMINISTRATIVE CONTROLS n kl6 POST-ACCIDENT SAMPLING AND ANALYSIS A program shall be established, implemented, and maintained to ensure the bekSc65/udof capability to obtain and anal ze samples of reactor coolant, radioactive

( , iodines and particulates in p ant gaseous effluents, and containment b, atmosphere under accident conditions.

T.G, N ffes The program shall include the following:

$ Cade#

(1) Training of personnel, (2) Procedures for sampling and analysis, and p (3) Provisions for maintenance of sampling and analysis equipment.

Q,j 6.17 0FFSITE DOSE CALCULATION MANUAL 7 g pygg g}

6.17.1 Licensee-initiated changes to tTe 00CM shall:

a. Be documented and records of reviews cerformed shall be rmtainedM J e qw rea o N ecnnical a ssgttcation q 0.Z y ints oocumentation Tnait contain:

1) Sufficient information *.o support the change together with the appropriate analyses or evaluations justifying the change (s),

and

2) A determination that the change will maintain the level of radioactive effluent control required by 10 CFR 20.106, 40 CFR Part 190, 10 CFR 50.36a, and Appendix ! to 10 CFR Part 50 and not adversely impact the accuracy or reliability of effinent.

dose, or setpoint calculations. %$ch,n,[/u.).

b. Become effective after review and acceptance by theMand the gq q approval of the C:ncr:1 Nng:r Nier '" g O c. Be submitted to the Commission in the form of a complete, legible copy of the entire OOCH as a part of, or concurrent with, the Annual Radioactive Effluent Release Report for the period of the report in which any change to the 00CM was made. Each change shall be identified by markings in the margin of the affected pages, clearly indicating the area of the page that was changed, and shall indicate the date (e.g., month / year) the change was implemented.

4 .18 RADIOACTIVE EFFLUENTS CONTROL PROGRAM A program shall be established, implemented, and maintained conforming !

with 10 CFR 50.36a for the control of radioactive effluents and for )

maintaining the doses to MEMBERS OF THE PUBLIC from radioactive 1 effluents as low as reasonably achievable. The rogram (1) shall be !

contained in the ODCM, (2) shall be implemented y operating procedures, )

g* g' us5/04 o and (3) shall include remedial actions to be taken whenever the program j Q es e n3, limits are exceeded. The program shall include the following elements:

5.f4,htQs 1) Limitations on the OPERABILITY of radioactive liquid and gaseous l c monitoring instrumentation including surveillance tests and setpoint Ed# . determination in accordance with the melhudolcgy in the 00CH, ;

2) Limitations on the concentrations of radioactive material released in i I liquid effluents to UNRESTRICTED AREAS conforming to 10 CFR Part 20, l Appendix B Table !!, Column 2,

3) Monitoring, sampling, and analysis of radioactive liquid and gaseous effluents in accordance with 10 CFR 20,106 and with the methodology and parameters in the 00CM, O

HATCH - UNIT 1 6-23 Amendment No. M8, H0,190 f

)# ;

l

DISCUSSION OF. CHANGES O* ITS: SECTION 5.5.1 - 0FFSITE DOSE CALCULATION MANUAL ADMINISTRATIVE A.1 The current TS contains a cross-reference to Specification 6.10.2.o for

! record retention. This cross-reference is not included in the proposed TS. The removal of this cross-reference is a presentation preference and thus, is considered an administrative change.

A.2 CTS numbers are changed by the new format of the proposed TS for Section <

5.0. These new TS numbers are indicated in the TS markup.

A.3 The Radiological Environmental Monitoring Program is relocated from the TS as described in the CTS 6.19 Discussion of Changes. Therefore, the deletion of the reference to this removed TS is considered administrative. :

A.4 The current plant specific titles are changed to generic titles. ITS Section 5.2.I.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

O I

I O

HATCH UNIT 1 1 REVISION / F i

_ - _ _ I

7 UNIT 1 NO SIGNIFICANT HAZARDS DETERMINATION O

O l l

1

(Q N0 SIGNIFICANT HAZARDS DETERMINATION ITS: SECTION 3.8.1 - AC SOURCES-0PERATING

't)

L.5 CHANGE In accordance with the criteria set forth in 10 CFR 50.92, Georgia Power Company has evaluated this proposed Technical Specifications change and determined it does not involve a significant hazards consideration based on the following:

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

The diesel generators (DGs) are used to support mitigation of the consequences of an accident; however, they are not considered the initiator of any previously analyzed accident. As such, the elimination of a specific signal requirement to perform the " hot restart" surveillance testing will not increase the probability of any accident previously evaluated. The proposed SR continues to provide adequate assurance of OPERABLE DGs since restart capability is not affected by the start signal or loading capability. Therefore, the proposed change does not involve an increase in the consequences of any accident previously evaluated.

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

f'n L/

The proposed change does not introduce a new mode of plant operation and does not involve physical modification to the plant. Therefore, it does not create the possibility of a new or different kind of accident from any accident previously evaluated.

3. Does this change involve a significant reduction in a margin of safety? l l

This change does not involve a significant reduction in a margin of safety !

since the start capability of the DGs is not affected by the start signal 1 or loading capability. Therefore, the proposed change provides an l equivalent assurance of the capability of the OGs to perform their safety :

function. l 1

This change was approved by the NRC and issued as Amendment 192 in a Safety l Evaluation Report dated February 24, 1994. l l

l O

NmN um i s RmSiONjF

O UNIT 2 IMPROVED TECHNICAL SPECIFICATIONS O i I

I i

1 l

O i

I

SLs 2.0 2.0 SAFETY LIMITS (SLs) 2.1 SLs 2.1.1 Reactor Core SLs 2.1.1.1 With the reactor steam dome pressure < 785 psig or core flow < 10% rated core flow:

THERMAL POWER shall be s 25% RTP.

2.1.1.2 With the reactor steam dome pressure a 785 psig and core flow 210% rated core flow:

MCPR shall be a 1.06 for two recirculation loop operation or 21.07 for single recirculation loop operation.

2.1.1.3 Reactor vessel water level shall be greater than the top of active irradiated fuel.

2.1.2 ]Lqactor Coolant System (RCS) Pressure SL Reactor steam dome pressure shall be s 1325 psig.

j 2.2 SL Violations With any SL violation, the following actions-shall be completed:

f 2.2.1 Within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months , notify the NRC Operations Center, in accordance with 10 CFR 50.72.

2.2.2 Within 2 hour2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months s:

2.2.2.1 Restore compliance with all SLs; and 2.2.2.2 Insert all insertable control rods.

2.2.3 Within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months , notify the plant manager,-the corporate executive responsible for overall plant nuclear safety, and the offsite review committee.

(continued)

HATCH UNIT 2 2.0-1 REVISION [{

l

j

SLs 2.0 2.0 SLs h. 1 1

2.2 SL Violations (continued) 1 2.2.4 Within 30 days, a Licensee Event Rep' ort (LER) shall be prepared )

pursuant to 10 CFR 50.73. The LER shall be submitted to the NRC, !

the offsite review committee, the plant manager, and the corporate executive responsible for overall plant nuclear safety. 1 2.2.5 Operation of the unit shall not be resumed until authorized by the NRC. l l

I l

@1 i

I i

O' HATCH UNIT 2 2.0-2 REVISIONkf

)

LC0 Applicability !

3.0 l I

3.0 LIMITING CONDITION FOR OPERATION (LCO) APPLICABILITY LC0 3.0.1 LCOs shall be met during the MODES or other specified l conditions in the Applicability, except as provided in l LC0 3.0.2 and LC0 3.0.7. j LC0 3.0.2 Upon discovery of a failure to meet an LCO, the Required Actions of the associated Conditions shall be met, except as I provided in LC0 3.0.5 and LC0 3.0.6.

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

LCO 3.0.3 When an LC0 is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, the unit shall be placed in a MODE.

or other specified condition in which the LC0 is not applicable. Action shall be initiated within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months to place the unit, as applicable, in:

a. M0DE 2 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months ;

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

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

Exceptions to this Specification are stated in the individual Specifications.

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

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

LCO 3.0.4 When an LC0 is not met, entry into a MODE or other specified condition in the Applicability shall not be made except when the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time. This !

Specification shall not prevent changes in MODES or other specified conditions in the Applicability that are required 4

(continued)

HATCH UNIT 2 3.0-1 REVISION A

LC0 Applicability 3.0 3.0 LC0 APPLICABILITY l

LC0 3.0.4 to comply with ACTIONS or that are part of a shutdown of the (continued) unit.

1 Exceptions to this Specification are stated in the individual Specifications. These exceptions allow entry 1 into MODES or other specified conditions in the I Applicability when the associated ACTIONS to be entered allow unit operation in the MODE or other specified I condition in the Applicability only for a limited period of l time. !

LCO 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, and 3.

l 1

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

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

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

(continued)

HATCH UNIT 2 3.0-2 REVISIONfp

SR Applicability 3.0 3.0 SR APPLICABILITY (continued)

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LC0 shall not be made unless the LCO's Surveillances have been met within their specified Frequency. This provision shall not prevent entry into MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a shutdown of the unit.

SR 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, and 3.

O O ,

HATCH UNIT 2 3.0-5 REVISIONhf

't

Responsibility 5.1 5.0 ADMINISTRATIVE CONTROLS 5.1 Responsibility 5.1.1 The plant manager shall provide direct' executive oversight over l all aspects of Plant Hatch.

5.1.2 An assistant plant manager shall be responsible for overall unit l operation, except for the Radiological Environmental Monitoring Program as described below and for delegation in writing of the succession of this responsibility during his absence. Certain plant support functions shall also be the responsibility of an assistant plant manager.

5.1.3 The plant manager or his designee shall be responsible for the l Radiological Environmental Monitoring Program and for the writing of the Annual Radiological Environmental Operating Report.

5.1.4 Each of the individuals in Specification 5.1.1 through Specification 5.1.3 is responsible for the accuracy of the procedures needed to implement his responsibilities.

O V

5.1.5 The shift superintendent shall be responsible for the control room command function. During any absence of the shift superintendent from the control room while either unit is in MODE 1, 2, or 3, an individual with an active Senior Reactor Operator (SRO) license shall be designated to assume the control room command function.

During any absence of the shift superintendent from the control l room while both units are in MODE 4 or 5, an individual with an active SR0 license or Reactor Operator license shall be designated to assume the control room command function.

O G

HATCH UNIT 2 5.0-1 REVISION y l

Organization 5.2 5.0 ADMINISTRATIVE CONTROLS 5.2 Organization 5.2.1 Qasite and Offsite Oraanizations Onsite and offsite organizations shall be established for unit operation and corporate management, respectively. The onsite and offsite organizations shall include the positions for activities affecting safety of the nuclear power plant.

a. Lines of authority, responsibility, and communication shall be defined and established throughout highest management levels, intermediate levels, and all operating organization positions. These relationships shall be documented and updated, as appropriate, in organization charts, functional descriptions of departmental responsibilities and relationships, and job descriptions for key personnel positions, or in equivalent forcs of documentation. These requirements, including plant specific titles of those personnel fulfilling the responsibilities of the positions delineated in the Technical Specifications, shall be documented in the Plant Hatch Unit 2 FSAR;

b. An assistant plant manager shall be responsible for overall l safe operation of the plant and shall have control over those onsite activities necessary for safe operation and maintenance of the plant;

c. The corporate executive responsible for Plant Hatch shall l take any measures needed to ensure acceptable performance of the staff in orerating, maintaining, and providing technical support to the plant to ensure nuclear safety; and

d. The individuals who train the operating staff, carry out health physics, or perform quality assurance functions may report to the appropriate onsite manager; however, these individuals shall have sufficient organizational freedom to ensure their independence from operating pressures.

5.2.2 Unit Staff The unit staff organization shall include the following:

a. A total of three plant equipment operators (PE0s) for the two units is required in all conditions. At least one of (continued)

HATCH UNIT 2 5.0-2 REVISION /F

Organization 5.2 O

() 5.2 Organization 5.2.2 Unit Staff

a. (continued) the required PE0s shall be assigned to each reactor containing fuel,

b. At least one licensed Reactor Operator (RO) shall be present in the control room for each unit that contains fuel in the reactor. In addition, while the unit is in MODE 1, 2, or 3, at least one licensed Senior Reactor Operator (SRO) shall be present in the control room.

c. The minimum shift crew composition shall be in accordance with 10 CFR 50.54(m)(2)(i). Shift crew composition may be less than the minimum requirement of 10 CFR 50.54(m)(2)(i) and 5.2.2.a for a period of time not to exceed 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months in order to accommodate unexpected absence of on duty shift crew members provided immediate action is taken to restore the shift crew composition to within the minimum requirements.

~'N d. An individual qualified to implement radiation pr.itection

[d procedures shall be on site when fuel is in the reactor.

The position may be vacant for not more than 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months , in order to provide for unexpected absence, provided immediate action is taken to fill the required position.

e. Administrative procedures shall be developed and implemented to limit the working hours of unit staff who perform safety related functions (e.g., licensed and non-licensed A operations personnel, health physics technicians, key &

maintenance personnel, etc.).

Adequate shift coverage shall be maintained without routine heavy use of overtime. The objective shall be to have operating personnel work a nominal 40 hour4.62963e-4 days 0.0111 hours 6.613757e-5 weeks 1.522e-5 months week while the unit is operating. However, in the event that unforascen problems require substantial amounts of overtime to be used, or during extended periods of shutdown for refueling, major maintenance, or major plant modification, on a temporary basis the following guidelines shall be followed:

1. An individual should not be permitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months straight, excluding shift turnover time; g (continued)

\

HATCH UNIT 2 5.0-3 REVISION D l

1 l

Organization 5.2 5.2 Organization 5.2.2 Unit Staff (continued) l

e. (continued) {

1

2. An individual should not be permitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months in any 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months period, nor more than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months ,

in any 48 hour5.555556e-4 days 0.0133 hours 7.936508e-5 weeks 1.8264e-5 months period, nor more than 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months in any l 7 day period, all excluding shift turnover time, ;

l

3. A break of at least 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months should be allowed between i work periods, including shift turnover time; l

4. Except during extended shutdown periods, the use of ;

overtime should be considered on an individual basis '

and not for the entire staff on a shift.

4 Any deviation from the above guidelines shall be authorized l by an assistant plant manager or by higher levels of l management, in accordance with established procedures and with documentation of the basis for granting the deviation.

Controls shall be included in the procedures such that individual overtime shall be reviewed monthly by an assistant plant manager or designee to ensure that excessive I hours have not been assigned. Routine deviation from the above guidelines is not authorized.

f. The operations manager shall hold an active or inactive SR0 license.

g. The Shift Technical Advisor (STA) shall provide advisory technical support to the shift supervisor in the areas of thermal hydraulics, reactor engineering, and plant analysis with regard to the safe operation of the unit. In addition, the STA shall meet the qualifications specified by the Commission Policy Statement on Engineering Expertise on Shift.

I

. O HATCH UNIT 2 5.0-4 REVISION [f

l Programs and Manuals 5.5 5.0 ADMINISTRATIVE CONTROLS 5.5 Programs and Manuals ;

- i The following programs and manuals shall be established, implemented, and maintained.

5.5.1 Offsite Dose Calculation Manual (ODCM)

a. The ODCM shall contain the methodology and parameters used in the calculation of offsite doses resulting from

' radioactive gaseous and liquid effluents, in the calculation of gaseous and liquid effluent monitoring alarm and trip setpoints, and in the conduct of the radiological environmental monitoring program; and

b. The ODCM shall also contain the radioactive effluent controls and radiological environmental monitoring activities, and descriptions of the ir. formation that should be included in the Annual Radiological Environmental Operating and Radioactive Effluent Release reports required by Specification 5.6.2 and Specification 5.6.3, respectively.

Licensee initiated changes to the ODCM:

a. Shall be documented and records of reviews performed shall be retained. This documentation shall contain:

1. sufficient information to support the change (s) and appropriate analyses or evaluations justifying the change (s),and

2. a determination that the change (s) maintain the levels of radioactive effluent control required by 10 CFR 20.106, 40 CFR 190, 10 CFR 50.36a, and 10 CFR 50, Appendix I, and does not adversely impact the accuracy or reliability of effluent, dose, or setpoint calculations.

b. Shall become effective after review and acceptance by the onsite review committee and the approval of the plant manager; and (continued)

HATCH UNIT 2 5.0-7 REVISIONKp

Programs and Manuals 5.5 5.5 Programs and Manuals ,

5.5.1 Offt.ite Dose Calculation Manual (0DCM) (continued)

c. Shall be submitted to the NRC ir the form of a complete, legible copy of the entire ODCM as a part of or concurrent l with the Radioactive Effident Release Report for the period ,

of the report in which any change in the ODCM was made. j Each change shall be identified by markings in the margin of '

the affected pages, clearly indicating the area of the page l that was changed, and shall indicate the date (i.e., month l and year) the change was implemented.

1 5.5.2 Primary Coolant Sources Outside Containment This program provides controls to minimize leakage from those i portions of systems outside containment that could contain highly l radioactive fluids during a serious transient or accident to levels as low as practicable. The systems include the Core Spray, High Pressure Coolant, Injection, Residual Heat Removal, Reactor l Core Isolation Cooling and Reactor Water Cleanup. The program shall include the following- -

l

a. Preventive maintenance and periodic visual inspection requirements; and

b. System leak test requirements for each system, to the extent permitted by system design and radiological conditions, at refueling cycle intervals or less.

5.5.3 Post Accident Samolina This program provides cont.rols that ensure the capability to obtain and analyze reactor coolant; radioactive gases and particulates in plant gaseous effluents; and containment atmosphere samples under accident conditions. The program shall include the following:

a. Training of personnel;

b. Procedures for sampling and analysis; and

c. Provisions for maintenance of sampling and analysis equipment.

(continued)

HATCH UNIT 2 5.0-8 REVISION A

,n +

0 =12 mimovto msts ,

)

O

LC0 Applicability B 3.0

() BASES LCO 3.0.3 assemblies in the spent fuel storage pool." Therefore, this (continued) LC0 can be applicable in any or all MODES. If the LC0 and the Required Actions of LC0 3.7.8 are not met while in MODE 1, 2 or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LC0 3.7.8 of " Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LC0 3.0.3. These exceptions are addressed in the individual Specifications.

LCO 3.0.4 LCO 3.0.4 establishes limitations on changes in MODES or other specified conditions in the Applicability when an LC0 is not met. It precludes placing the unit in a MODE or other specified condition stated in that Applicability l (e.g., Applicability desired to be entered) when the following exist:

a. Unit conditions are such that the requirements of the l LC0 would not be met in the Applicability desired to

( be entered; and

b. Continued noncompliance with the LC0 requirements, if the Applicability were entered, would result in the unit being required to exit the Applicability desired to be entered to comply with the Required Actions.

Compliance with Required Actions that permit continued operation of the unit for an unlimited period of time in a MODE or other specifiad condition provides an acceptable level of safety for continued operation. This is without regard to the status of the unit before or after the MODE change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions.

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

The provisions of LC0 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability (continued)

HATCH UNIT 2 B 3.0-5 REVISION /({

LC0 Applicability B 3.0 BASES LC0 3.0.4 that are required to cornply with ACTIONS. In addition, the (continued) provisions of LC0 3.0.4 shall not prevent changes in MODES or other specified conditions 'in the Applicability that result from any unit shutdown.

Exceptions to LC0 3.0.4 are stated in the individual Specifications. Exceptions may apply to all the ACTIONS or to a specific Required Action of a Specification.

LC0 3.0.4 is only applicable when entering MODE 3 from MODE 4, MODE 2 from MODE 3 or 4, or MODE 1 from MODE 2.

Furthermore, LC0 3.0.4 is applicable when entering any other specified condition in the Applicability only while operating in MODE 1, 2, or 3. The requirements of LCO 3.0.4 do not apply in MODES 4 and 5, or in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, changing MODES or other specified conditions while in an ACTIONS Condition, either in compliance with LC0 3.0.4 or where an exception to LC0 3.0.4 is stated, is not a violation of SR 3.0.1 or SR 3.0.4 for those Surveillances that do not have to be performed due to the associated inoperable equipment. However, SRs must be met to ensure OPERABILITY prior to declaring the associated equipment OPERABLE (or variable within limits) and restoring compliance with the affected LCO.

LCO 3.0.5 LC0 3.0.5 establishes the allowance for restoring equipment to service under administrative controls when it has been removed from service or declared inoperable to comply with ACTIONS. The sole purpose of this Specification is to 3 provide an exception to LC0 3.0.2 (e.g., to not comply with !

the applicable Required Action (s)) to allow the performance of Srs to demonstrate:

a. The OPERABillTY of the equipment being returned to service; or

b. The OPERABILITY of other equipment.

(continued)

HATCH UNIT 2 B 3.0-6 REVISIONp

LC0 Applicability 8 3.0 i BASES LCO 3.0.5 The administrative controls ensure the time the equipment is (continued) returned to service in conflict with the requirements of the ACTIONS is limited to the time absolutely necessary to perform the allowed SRs. This Specification does not provide time to perform any other preventive or corrective maintenance.

4 J

O (continued)

HATCH UNIT 2 83.0-/@4 REVISIONf{

SR Applicability 4

B 3.0 BASES SR 3.0.3 period of up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified (continued) Frequency, whichever is less, applies from the point in time that it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the time that the specified Frequency was not met.

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

. preclude completion of the Surveillance.

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

When a Surveillance with a frequency based not on time intervals, but upon specified unit conditions or operational O- situations, is discovered not to have been performed when specified, SR 3.0.3 allows the full delay period of 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months to perform the Surveillance.

SR 3.0.3 also provides a time limit for completion of Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions.

] Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence. Use of the delay period established by SR 3.0.3 is a flexibility which is not l- intended to be used as an operational convenience to extend i Surveillance intervals.

If a Surveillance is not completed within the allowed delay period, then the equipment is considered inoperable or the

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

(continued,) J HATCH UNIT 2 B 3.0-13 REVISION A l 4

SR Applicability B 3.0 BASES SR 3.0.3 Required Actions for the applicable LC0 Conditions begin (continued) immediately upon the failure of the Surveillance.

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

SR 3.0.4 SR 3.0.4 establishes the requirement that all applicable SRs must be met before entry into a MODE or other specified condition in the Applicability. This Specification ensures that system and component OPERABILITY requirements and ,

variable limits are met before entry into MODES or other ,

specified conditions in the Applicability for which these l systems and components ensure safe operation of the unit. '

l However, in certain circumstances, failing to meet an SR l

will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a system, subsystem, '

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

apply to the associated SR(s) since the requirement for the SR(s) to be performed is removed. Therefore, failing to perform the Surveillance (s) within the specified Frequency, on equipment that is inoperable, does not result in an SR 3.0.4 restriction to changing MODES or other specified i conditions of the Applicability. However, since the LC0 is not met in this instance, LC0 3.0.4 will govern any ,

restrictions that may (or may not) apply to MODE or other I specified condition changes. )

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

The provisions of SR 3.0.4 shall not prevent changes in MODES or other specified conditions in the Applicability j that are required to comply with ACTIONS. In addition, the !

provisions of SR 3.0.4 shall not prevent changes in MODES or !

(continued)

HATCH UNIT 2 83.0-lk REVISION /F I

l 1

SR Applicability B 3.0 BASES I

l SR 3.0.4 other specified conditions in the Applicability that result (continued) from any unit shutdown.

i The precise requirements for performance of SRs are ,

specified such that exceptions to SR 3.0.4 are not '

9xessary. The specific time frames and conditions necessary for meeting the SRs are specified in the O

i

?

(continued)

HATCH UNIT 2 8 3.0-1/4A REVISION /( p

~.

SR Applicability B 3.0 O

b BASES SR 3.0.4 Frequency, in the Surveillance, or both. This allows (continued) performance of Surveillances when the prerequisite condition (s) specified in a Surveillance procedure require entry into the MODE or other specified condition in the Applicability of the associated LC0 prior to the performance or completion of a Surveillance. A Surveillance that could not be performed i:iitil after entering the LCO Applicability would have its Frequency specified such that it is not "due" until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note as not required (to be met or performed) until a particular event, condition, or time has been reached. Further discussion of the specific formats of SRs' annotation is found in Section 1.4, Frequency.

SR 3.0.4 is only applicable when entering MODE 3 from MODE 4, MODE 2 fror. MODE 3 or 4, or MODE 1 from MODE 2.

Furthermore, SR 3.0.4 is applicable when entering any other specified condition in the Applicability only while operating in MODE 1, 2, or 3. The requirements of SR 3.0.4 do not apply in MODES 4 and 5, or in other specified

, conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

O HATCH UNIT 2 B 3.0-1k$ REVISION y

l -,

I f

l O un'r 2 miaxur OF CuaaEsr rtCasIcit SPECIFICATIONS AND DISCUSSION OF CHANGES l i

l l

4 I

O l

l e

O

he f;e,e 2.0 _

See Ci u ssoa of M Cs ADMINISTRATIVE CONTROLS

& Sw 4*A@aaCad O ~

k.

The Radiological Environmental Monitoring Program and the results thereof annually.

1. The 00CM, Process Contral Program, and implementing procedures at least once per 24 ranths. j l

i AUTHORITY .

6.5.2.9 The SRB shall report to and advise the Vice President-Nuclear on l those areas of responsibility specified in sections 6.5.2.7 and 6.5.2.8.

RECORDS 6.5.2.10 Records of SRB activities shall be prepared, approved and distributed as indicated below:

a. Minutes of each SRB meeting shall be prepared, approved and ,

forwarded to the Vice President-Nuclear within 14 days following 'l each meeting.

b. Reports of reviews encompassed by section 6.5.2.7 above, shall be prepared, approved and forwarded to the Vice P. resident-Nuclear l within 14 days following completion of the review.

c. Audit reports encompassed by section 6.5.2.8 above, shall be forwarded to the Vice President-Nuclear and to the management l

positions responsible for the areas audited within 30 days after completion of the audit.

6.6 REPORTABLE EVENT ACTION 6.6.1 The following actions shall be taken for REPORTABLE EVENTS:

4

a. The Commission shall be notified and/or a report submitted pursuant to the requirements of section 50.73 to 10 CFR part 50, and

b. Each REPORTABLE EVENT shall be reviewed by the PRB, and the results of this review shall be submitted to the SRB, the General Manager- /

Nuclear Plant, and the Vice President-Nue. lear. /

6.7 SAFETY LIMIT VIOLATION g ,.2 6.7.1 The following actions shall be taken in the event a Safety Limit is violated:

2. .'2,2 a. The unit shall be placed in at least HOT SHUTDOWN within 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months .

b. ( The Safety Limit violation shall be reported to the Commission as a .u (,soon as practical and in all cases within 1 hour1.157407e-5 days 2.777778e-4 hours 1.653439e-6 weeks 3.805e-7 months of occurrence.

g,3 ".,4, :-d Vir-

"-- within

'f a ,,,,

24Ahours.

.., nd:f l ,.

'2. 2 3b,..((;;The

".;;.;;; . L'.;';;7, ee-M S shall be notified i an+ Manager, and carfemk 4acdW fy$sM[sr eWief //metf nudd# MM d N ON

' MATCH - UNIT 2 6-11 Amendment No. 47, 48, 80, 86, 9 W7

5@ 1. o ADMINISTRATIVE CONTROLS p ---

()

SAFETY LIMIT VIOLATION-(Continued) l 2 2 9 c. A Licensee Event Report shall be prepared pursuan- to 10 CFR 50.73.

L.)

s d. The Licensee Event Report shall be submitte to the Commission in Il

}A,p accordance with 10 CFR 50.73, and to the the i t #4

% Scacral Nnagcr bclar "' nt, and the yMr "-9d- R inc within 30 days of the violation.

l p, r,w a cor axacu , 4isik. feVit p3

'tWen W ' 6 -

flen} M*0a p\

M **

nadeAr sa044y MMIN i i

I G PROCEDUHth )

" Oi" 5.8.1 Written procedures shall be established, implemented and maintained W e :overing the activities referenced below:

Fa See o CA

'h; A fu. a. The applicable procedures recomended in Appendix A of Regulatory M A* Guide 1.33, Revision 2, February 1978. t

b. Refueling operations.

I

c. Surveillance and test activities of safety related equipment.

d. Security Plan implementation.

p

() e. Emergency Plan implementation. )

f. Fire Protection Program implementation.

g. PROCESS CONTROL PROGRAM implementation.

h. ODCM implementation.

I (6.8.2 Each procedure of 6.8.1 and other procedures which the General Manager-

' Nuclear Plant, the AGM-PO, or the AGM-PS has determined to affect nuclear safety, and changes thereto, shall be reviewed by the PR8 and approved by the appropriate member of plant management, designated by the General Manager-Nuclear Plant, the AGM-PO, or the AGM-PS prior to implementation. The General Manager-Nuclear Plant, the AGM,-PO, or the AGM-PS will approve administrative procedures, security plan implementing procedures, and changes thereto. The -)

Manager-Plant Training and Emergency Preparedness shall approve the emergency plan implementing procedures and changes thereto. All other procedures of this specification and changes thereto will be approved by the department head designated by the General Manager-Nuclear Plant, the AGM-P0, or the AGM-PS.

The procedures of this specification shall be reviewed periodically as set forth in administrative procedures. !'

6.8.3 Temporary changes to procedures of 6.8.1 above may be made provided:

a. The intent of the original procedure is not altered.

() HATCH - UNIT 2 6-12 Amendment No. 4st, 48, 80, 86, 94, 116 7,:n

l 1

i

()

D DISCUSSION OF. CHANGES ITS: SECTION 2.0 - SAFETY LIMITS ADMINISTRATIVE A.1 The technical content of this requirement is being moved to Section 3.3 of the proposed Technical Specifications in accordance with the format of the BWR Standard Technical Specifications, NUREG 1433. Any technical changes to this requirement will be addressed with the content of the proposed chapter location.

A.2 A current requirement of 10 CFR 50.36 stating that if a Safety Limit is violated, critical " Operation of the unit will not be resumed until authorized by the NRC," has been added (proposed 2.2.5). Since it is a regulation, the addition of this to the Technical Specifications is considered administrative in nature.

A3 The current plant specific titles are changed to generic titles. ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those persont el fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

TECHNICAL CHANGE - MORE RESTRICTIVE t

M.1 The APPLICABILITY of each of the SLs is extended to all MODES of l operation. Although it is physically impossible to violate some SLs in l some MODES, any SL violation should receive the same attention and response. !

M.2 Limits on steam dome pressure and core flow are now specified as greater than or equal to. The current Safety Limits do not address the situation when steam dome pressure and core flow are equal to the limits. This change resolved a discontinuity between SL 2.1.1 and SL 2.1.2 in the current Safety Limits. l TECHNICAL CHANGE - LESS RESTRICTIVE

" Generic" l

LA.1 The required action has been made less specific to allow operator I flexibility in determining the best method to restore the water level.

Directions for the methods are included in the appropriate Emergency Operating Procedures. The time frame for completion of the action is 4 consistent with the allowed time to restore other Safety Limit violations. 1

" Specific" L.1 The review of the LER by the Plant Review Board is duplicative of the review performed by the Safety Review Board. Deleting this review i responsibility from the onsite review group provides additional review time for the remaining functions. Since this review is after submittal, HATCH UNIT 2 1 REVISION [

O DISCUSSION OF CHANGES ITS: SECTION 2.0 - SAFETY LIMITS. 4 ADMINISTRATIVE (continued) the offsite review function provides sufficient, adequate, and timely review.

l 1

I

O i

l lO HATCH UNIT 2 h Ik. REVISION %[,

h 3 0,4 is f yf)Cabk $Wmh 15l0 oN0W W OthM~5/4A$it/ doHdi/NM /A Affl'Ni$

Insert 3.0D n Moog$ t, 2j ud 3. , N.

LCO 3.0.4 When an LCO is not met, entry into a MODE or other ;

specified condition in the Applicability.shall not :

be made except when the associated ACTIONS.to be -

entered permit continued operation in the MODE or l OL,z wan other specified condition in the Applicability for

unlimited period of time. This Specification j ,

shall not prevent changes in MODES or other

~

specified conditions in the Applicability that are :

requiredtocomplywithACTIONSgorthatarepartg\

of a shutdown of the unit. Y ll Exceptions to this Specification are stated in the L7.

individual Specifications. These exceptions allow entry into MODES or other specified conditions in

1. the Applicability when the associated ACTIONS to be entered allow unit operation in the MODE or other specified condition in the Applicability only for a limited period of time.

4 Insert 3.0E Or LCO 3.0.5 Equipment removed from service or declared inoperabl to comply with ACTIONS may be returned ,

g3 to service under administrative control solely to perform tes ing required to demonstrate its O- OPERABILITY, the OPERABILITY of other equipment , ! -

l er 'faridles to be within limits. This is an . O exception to LCO 3.0.2 for the system returned to service under administrative control.to perform the required testing.

I I

O Hatch Unit 2 Insert 3/4 0-l( )

h#9

-- -- __a r_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ . _ _ _ - - - _ _

-~

Insert 4.0c k_ - SR 3.0.3 If it is discovered that a Surveillance was not performed within its specified Frequency, then

, compliance with the requirement to declare the LCO not met may be delayed, from the' time of-discovery, up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months or up to the limit of the specified Frequency, whichever is'less. This delay period is permitted to allow performance of the Surveillance.

If the Surveillance is not performed within the delay period, the LCO must immediately be declared .'

not met, and the applicable Condition (s) must be entered.

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

Insert 4.0D i

l SR 3.0.4 Entry into a MODE or other specified. condition in l the Applicability of an LCO shall not be made =l

. unless the LCO's Surveillances~have been met g0 within their specified Frequency. This provision shall not prevent entry into MODES or other

)

specified conditions in the Applicability that are .

odd required to comply with ACTIONS, or that are part t )

"5f a shutdown of the unit. ;

a 3.o.4 a mty qpean Ce .w is a <xa e she 2

( spuifid wdi& a & Ay// cab YHy di NMES is 2, and 3.

k-i J

Hatch Unit 2 Insert 3/4 0- 2.

vas

O DISCUSSION OF. CHANGES ITS: SECTION 3.0 - LC0 AND SR APPLICABILITY ADMINISTRATIVE (continued) ,

A.5 Editorial rewording is consistent with the BWR Standard Technical Specifications, NUREG 1433 or generic changes to the NUREG. During its development, certain wording preferences or English language conventions were adopted which resulted in no technical changes (either actual or interpretational) to the Technical Specifications.

The phrase " Entry into an OPERATIONAL CONDITION or other specified applicability state" has been changed to "When an LC0 is not met, entry into a MODE or other specified condition in the Appl i cabil i ty. . . " This new wording is consistent with the terminology of the BWR Standard Technical Specifications, NUREG 1433.

l The phrase "unless otherwise excepted" has been reworded to be

" Exceptions to this Specification are stated in the individual Specifications." This more clearly states the intent of the original statement. The following proposed sentence is added to clarify the intent of the individual exceptions to LC0 3.0.4: "These Os exceptions allow entry into MODES or other specified conditions in the Applicability when the associated ACTIONS to be entered allow unit operation in the MODE or other specified condition in the Applicability only for a limited period of time."

A.6 Current LC0 3.0.5 has been moved to LC0 3.8.1, "AC Sources - Operating,"

as Required Actions A.2, B.2, and C.I. A time limit on performing the operability determination is also provided in the Completion Time for the Required Actions. For the Discussion of Changes, see LC0 3.8.1, "AC Sources - Operating."

A.7 LC0 3.0.6 is added to provide guidance regarding the appropriate actions to be taken when a single inoperability (e.g., a support system) also results in the inoperability of one or more related systems (e.g.,

supported system (s)). The existing Technical Specifications, and various NRC guidance documents do not have a consistent provided approach to the combined support / supported inoperability.

Guidance provided in the June 13, 1979, NRC memorandum from Brian K.

Grimes (Assistant Director for Engineering and Projects) to Samuel E. Bryan (Assistant Director for Field Coordination) indicates an intent / interpretation consistent with the proposed LC0 3.0.6 --

O HATCH UNIT 2 3 REVISION Y

(~T DISCUSSION OF CHANGES

() ITS: SECTION 3.0 - LC0 AND SR APPLICABILITY ADMINISTRATIVE (continued)

A.12 The statement "This provision shall not prevent entry into MODES or other s)ecified conditions in the Applicability that are required to comply with tie ACTIONS or that are part of a shutdown of the unit" is added following the intent of NRC Generic Letter 87-09 to clarify that the provisions of proposed SR 3.0.4 do not prevent passage to or through lower MODES or other specified conditions to comply with ACTIONS.

A.13 The technical content of this requirement is being moved to Specification 5.5.6. Any technical changes to this requirement will be addressed in the Discussion of Changes for the new Specifications.

A.14 The Bases are completely revised in accordance with the applicable Bases from NUREG 1433. The individual changes that are necessary are made to support the corresponding changes to the Technical Specifications, and the justifications for each are the same as the justifications for the associated change to the Technical Specification.

TECHNICAL CHANGE - MORE RESTRICTIVE p) u M.1 The sentence "For Frequencies specified as 'once,' the above interval extension does not apply" is proposed to be added. This is because the interval extension concept is based on scheduling flexibility for repetitive performances, and these Surveillances are not repetitive in nature and essentially have no interval as measured from the previous performance. This precludes the ability to extend these performances, and is, therefore, an additional restriction. The existing Specification can be seen to allow the extension to apply to all Surveillances.

TECHNICAL CHANGE - LESS RESTRICTIVE L.1 The time to reach MODE 3 (Hot Shutdown) has been extended from 6 hours6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months to 13 hours1.50463e-4 days 0.00361 hours 2.149471e-5 weeks 4.9465e-6 months , and the time to reach MODE 4 (Cold Shutdown) has been extended from 36 hours4.166667e-4 days 0.01 hours 5.952381e-5 weeks 1.3698e-5 months (6 to reach MODE 3 and 30 to reach MODE 4) to 37 hours4.282407e-4 days 0.0103 hours 6.117725e-5 weeks 1.40785e-5 months . In addition, a requirement to be in MODE 2 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months has been added.

The I hour extension is added to provide adequate time to plan the impending shutdown. The 6 hour6.944444e-5 days 0.00167 hours 9.920635e-6 weeks 2.283e-6 months extension in reaching MODE 3 is added to provide the necessary time to shut down the plant from full power conditions in a controlled and orderly manner that is within the capabilities of the unit assuming the minimum required equipment is OPERABLE. This extra time reduces the potential for unit upset that could challenge safety systems. This time is consistent with other similar actions throughout the current Hatch Unit 2 Technical Specifications. To offset this additional time, the unit must be placed in MODE 2 within 7 hours8.101852e-5 days 0.00194 hours 1.157407e-5 weeks 2.6635e-6 months . This will place the unit in a condition where the probability of occurrence and the consequences of most accidents and transients are less than if the unit were still in MODE 1. The proposed actions and times are

(',) consistent with those currently approved the BWR Standard Technical V Specifications, NUREG 1433.

HATCH UNIT 2 6 REVISION $

DISCUSSION OF CHANGES h,^ ITS: SECTION 3.0 - LC0 AND SR APPLICABILITY TECHNICAL CHANGE - LESS RESTRICTIVE (continued)

L.2 The phrase "

...unless the conditions for the Limiting Condition for Operation are met without reliance on provisions contained in the ACTION statements..." was changed to "... except when the associated ACTIONS to be entered permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time." This change removes an unduly restrictive requirement. For an LC0 which has ACTIONS permitting continued operation for an unlimited period of time, entry into a MODE or other specified condition should be permitted in accordance with these ACTIONS. This is consistent with the NRC's regulatory requirements for an LCO. The restriction on a change in a MODE or other specified condition should apply only where the ACTIONS establish a specified time interval in which the LC0 must be met or a shutdown is required. This phrase was changed to be consistent with Generic Letter 87-09 except that the Generic Letter version of Specification 3.0.4 phrase

...and the associated ACTION requires a shutdown if they are not met within a specified time interval" was changed to "... permit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time." This statement is consistent with Generic Letter 87-09, Specification 3.0.4 guidance regarding the changing of MODES while relying upon the ACTION requirements when they permit continued operation for an unlimited period of time. This change also (G) provides consistency for use of proposed LC0 3.0.4, since it is the permitting of continued operation for an unlimited period of time, not the requirement to shut down, that determines the applicability of proposed LC0 3.0.4.

In addition, the phrase "or that are part of a shutdown of the unit" was added SR)[dition 3.0.4 in is only to the end and applicable the first for entry intoparagraph a MODE orand thespecified other sentencecon "LC0 the Applicability in MODES 1, 2, and 3" was added. These changes provide clarity for the actual application of the LC0 3.0.4 and SR 3.0.4 restrictions. Reviews of NUREG 1433 and the Hatch ITS with respect to this change concluded that the potential restrictions eliminated with this l

portion of the change are either: 1) consistent with the allowance discussed above when ACTIONS allow continued operation in the Applicability, 2) consistent with the existing LC0/SR 3.0.4 allowance for entering Applicabilities that would be applicable as a result of complying I with shutdown ACTIONS, or 3) precluded by compliance with the applicable l ACTIONS. I L.3 LC0 3.0.5 is added to provide an exception to LC0 3.0.2 for instances l where restoration of inoperable equipment to an OPERABLE status could not l be performed while continuing to comply with Required Actions. Many l Technical Specifications actions require an inoperable component to be l removed from service, such as: maintaining an isolation valve closed, i disarming a control rod, or tripping an inoperable instrument channel. An :

exception to these Required Actions is necessary to allow the performance Q

G<

of Surveillance Requirements to either demonstrate the OPERABILITY of the equipment being returned to service, or to demonstrate the OPERABILITY or i

l other equipment which otherwise could not be performed without returning l HATCH UNIT 2 7 REVISION [f

DISCUSSION OF CHANGES

('~T q) ITS: SECTION 3.0 - LC0 AND SR APPLICABILITY TECHNICAL CHANGE - LESS RESTRICTIVE (continued) ,

LC0 3.0.5 is necessary to establish an allowance that, although informally utilized in restoration of inoperable equipment, is not formally recognized in the present Technical Specifications. Without this allowance, certain components could not be restored to OPERABLE status and a plant shutdown would ensue. Clearly, it is not the intent or desire that the Technical Specifications preclude the return to service of a suspected OPERABLE component to confirm its OPERABILITY. This allowance is deemed to represent a more stable, safe operation than requiring a plant shutdown to complete the restoration and confirmatory testing.

O 4

o HATCH UNIT 2 REVISIONhf 17A

DISCUSSION OF CHANGES O ITS: SECTION 3.8.1 - AC SOURCES-0PERATING V

ADMINISTRATIVE A.5 (continued)

In addition, since the swing DG is common to both units, SRs that allow one performance to satisfy both units' requirements are allowed to be performed while one unit is not shutdown, provided the SR is being ,

performed from the other unit. Since this is only a change in l I presentation of current practice, this change is considered administrative.

l l A.6 These two possible values for the overspeed trip point are fixed by the design of the DG unit. The appropriate value (i.e., the most limiting, which is 65.5 Hz) is presented in the proposed Technical Specifications. l This presentation eliminates the basis for the accepted value from the 1 Technical Specifications, moving it to the Bases. Since there is no difference in the requirement, this is an editorial presentation preference only. .

l A.7 Proposed Note 1 to SRs 3.8.1.9, 3.8.1.10, and 3.8.1.17 and Note 2 to SR j 3.8.1.13 have been added. This allows an engine prelube prior to DG start. The current Specifications do not prohibit this allowance and the

(~ addition is provided for clarity. As such, it is considered

\ administrative in nature.

A.8 The technical content of this requirement is being moved to Chapter 5.0 of j the proposed Technical Specifications in accordance with the format of the ;

BWR Standard Technical Specifications, NUREG 1433. Any technical changes I to this requirement will be addressed with the content of proposed Specification 5.6.2.

A.9 The requirement to perform this Surveillance after the 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months run has been deleted. As indicated by the *** footnote, it is acceptable to perform the test after a 2 2 hour2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months run at a 2565 kW. Therefore, since it is already allowed to be performed in this manner, this change is considered administrative. This specific clarificatior was explicitly l added to the Unit 2 CTS by Amendment 131, dated February 24, 1994.

A.10 The technical content of current Specifications 4.8.1.1.2.a.2, 4.8.1.1. 2. a.3, 4.8.1.1. 2. a.6, 4.8.1.1. 2.c, and 4.8.1.1.2.d.13 i s bei ng moved to LC0 3.8.3. The technical content of Specifications 4.8.1.1.3.a.4, 4.8.1.1.3.c, and 4.8.1.1.3.d is being moved to LC0 3.8.4 and LC0 3.8.5. The technical content of Specifications 4.8.1.1.3.a.1,2,3, and 4.8.1.1.3.b is being moved to LC0 3.8.6. This is in accordance with the format of the BWR Standard Technical Specifications, NUREG 1433. Any technical changes to these requirements are addressed with the content of the proposed LCOs.

A i

HATCH UNIT 2 2 REVISION %p

DISCUSSION OF CHANGES em ITS: SECTION 3.8.1 - AC SOURCES-OPERATING i) v II.(HNICAL CHANGE - LESS RESTRICTIVE (continued)

L.9 The limitation on the time to reach full DG load from a manual synchronization is proposed for deletion. DG loading should be done in accordance with manufacturer's recommendations to minimize wear on the l engine. Additionally, placing a time limitation on the operator to l accomplish this loading results in an increased potential for error and subsequent unavailability of the DG. The starting, loading, subsequent full load operation, and automatic start and loading testing required by other Technical Specification Surveillances is adequate to confirm the DG's capability without the 120-second loading requirement. In addition, for clarity, Note 2 has been added to this SR to specifically allow gradual loading.

L.10 The proposed " hot restart" test (proposed SR 3.8.1.13) does not require the restart be a simulated loss of offsite power (auto-start signal). The

" hot restart" is proposed to simply be any start signal, as is required by the monthly test. Furthermore, the specific requirement to be automatically loaded with emergency loads is excessive; the DG has demonstrated its ability to power loads while " hot" (i.e., the 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months run). Additionally, the automatic loading is an unnecessary repetition of other SRs which confirm the DG ability to accept sequenced loads. DG Q loading following the hot restart is proposed to be controlled by plant b procedures and appropriate manufacturer recommendations for loading following any DG start. This revision allows greater flexibility in scheduling DG testing while not compromising any necessary demonstration of DG capability. This change was approved as Amendment 131, dated February 24, 1994 (note this Amendment renumbered this test as 4.8.1.1.2.d.14).

L.11 Deleted.

L.12 The current Specification 3.0.5 has been moved to LC0 3.8.1, in the form of Required Actions A.2, B.2, C.2, and 0.1. These new Required Actions are essentially the same as the current 3.0.5, except for the newly provided Completion Times to perform the checks required by current 3.0.5, item (2), and proposed Required Actions A.2, 8.2, C.2 and D.1. This new O

HATCH UNIT 2 9 REVISIONKp

$).aeks'cafieu C, l l p 6.0 ADMINISTRATIVE CONTROLS O

y,l 6.1 RESPONSIBILITY A*3 f.l l 6.1.0 The@neral Manager-Nuclear Planl shall provide direct executive -

oversight over all aspects ot Plant Hatch, f.l.2. 6.1.1 Ghe Assistant Gennral Mananer pinnt Onnrations (AGM-P(D shall be j -

respnsible for overall unit operation, except for the Radiological Environmental Monitoring Program as described below and for delegation in writing of the succession of this responsibility during 11s absence. Certain plant su) port functions shall be the responsibility off e Assistant Genera 1 05anaanr >lant suooort (AGM-P;LT.

A.3 g,l.3 6.1.2 IThe General Manaaer 4uclear lan or his designee _shall be responsible for the Radioloaical Environmental Monitnrinn Program Hs described in

($ecification6.19andJforthewritingoftheAnnualRadiological al l tnvironmental Surveillance Report.

,f,1,4 6.1.3 Eachofthe[above-mentioned)individualsisresponsiblefortheaccuracy of the procedures needed to impiement his responsibilities.

.2 URGANIZATIO SM . Dh sb.

~ .+ . . . n . ..gu ..

6.2.1 0FFSITE AND ONSITE ORGANIZATIONS A Onsite and offsite organizations shall be established for unit operation and corporate management, respectively. The onsite and offsite organizations shall include the positions for activities affecting the safety of the nuclear power plant.

a. Lines of authority, responsibility, and communication shall be established and defined for the highest management levels through t ,

intermediate levels to and including all operating organization !

positions. These relationships shall be documented and updated, as appropriate, in the form of organization charts, functional descriptions of departmental responsibilities and relationships, and I job descriptions for key personnel positions, or in equivalent forms '

of documentation. These requirements shall be documented in the Plant Hatch Unit 2 updated FSAR.

The AGM-P0 shall be responsible for overall unit safe operation and

b. l shall have control over those onsite activities necessary for safe I operation and maintenance of the plant.

c. The Vice President-Nuclear shall have corporate responsibility for overall plant nuclear safety and shall take any measures needed to ensure acceptable performance of the staff in operating, maintaining and providing technical support to the plant to ensure uclear safety.

~

O HATCH - UNIT 2 6-1 Amendment No. 47, 48, 80, 94, 446, 129 I & 2--

l e INSERT 1 for ITS 5.1

( .- i The[fuperintendent ef[fhif t] p shall be responsible for the control room command funcuon. During any absence of the from ' ;

the control room while either unit is in MODE 1, 2, or 3, an jh (

individual with an active Senior Reactor Operator (SRO) license shall be designated to assume the control room command function. !

During any absence of the from the control room while both ,

units are in MODE 4 or 5, an ndividual with an active SRO license or Reactor Operator license shall be designated to assume the control room command function. :

i O

HATCH UNIT Z l

l

DISCUSSION OF CHANGES Os ITS: SECTION 5.1 - RESPONSIBILITY ADMINISTRATIVE A.1 Oue to relocation of the Radiological Environmental Monitoring Program from the TS, reference to Specification 6.19 is deleted. A description of the changes to CTS 6.19 is contained in the Discussion of Changes for that TS.

A.2 The term "above-mentioned individuals" is changed to reference the TS (ITS 5.1.1 through 5.1.3) where these individuals are named.

A.3 The current plant specific titles are changed to generic titles, and ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

TECHNICAL CHANGES - MORE RESTRICTIVE M1 Proposed ITS 5.1.5 adds requirements to define the control room command function. These requirements are in addition to those in the present TS, and thus, represent a more restrictive change.

I 1

1 O

HATCH UNIT 2 1 REVISION \f

See b.s .14 .7 , '

w v.>, e..y;w z gP*ypl ggt,'g (, L

> > % kne 6.0 ADMINISTRATIVE CONTROLS O

Vk -

l "6.1 RESPONSIBILITY 6.1.0 The General Manager-Nuclear Plant shall provide direct executive oversight over all aspects of Plant Hatch. .

6.1.1 The Assistant General Manager-Plant Operations (AGM-PO) shall be l responsible for overall unit operation, except for the Radiological ;

Environmental Monitoring Program as described below and for delegation in '

writing of the succession of this responsibility during his absence. Certain plant support functions shall be the responsibility of the Assistant General Manager-Plant Support (AGM-PS).

6.1.2 The General Manager-Nuclear Plant or his designee shall be responsible for the Radiological Environmental Monitoring Program as described in Specification 6.19 and for the writing of the Annual Radiological l Environmental Surveillance Report.

6.1.3 Each of the above-mentioned individuals is responsible for the accuracy the procedures needed to implement his responsibilities.

f, 2 6.2 ORGANIZATIOR

,z,) 6.2.1 0FFSITE AND ONSITE ORGANIZATIONS Onsite and offsite organizations shall be established for unit operation and corporate management, respectively. The onsite and offsite organizations shall include the positions for activities affecting the safety of the nuclear power plant.

{,1,i. A a. Lines of authority, responsibility, and communication shall be established and defined for the highest management levels through intermediate levels to and including all operating organization positions. These relationships .shall be documented and updated, as appropriate, in the form of organization charts, functional .

descriptions of departmental responsibilities and relationships, and f- '

job descriptions for key personnel positions, or in equivalent forms L. A ;

- (A_ h of documentation. These requirements <shall he rineumontpd in thn A nt Mitch Unit 2 updated FSAR.

f, t ', l . 6 b .

W"W

"- "'~

qmduding

"""shall be responsible fo o?&$h YhWrIn$N$

enj. seg4c NHe

.aii un i c saii: vpimacion ano 5e ofg *?f aks 4

shall have control over those onsite actlyities necessary for safe operation and maintenance of the plant.

p g.g f,2.l.c. c. The W a o-^+^-t fo "^ 1' ;! rt ""&r r!: r6"M Hvc

^+" corporate d shall take/responsibil@ded any measures nee (r a o ensure acceptable performance of the starf in operating, f(// maintaining and providing technical support to the plant to ensure A . 2.

{ nuclear safety.

O HATCH - UNIT 2 6-1 Amendment No. 47, 48, 80, 94, 4 % ,

129 lo%

fjs44$47)en f. 2.

ADMINISTRATIVE CONTROLS O (2) An individual should not be permitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months in any 24-hour period, nor more than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months in any 48-hour period, nor more than 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months in any 7-day period, all excluding shift turnover time.

(3) A break of at least 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months should be allowed between work periods, including shift turnover time.

(4) Except during extended shutdown periods, the use of overtime should be considered on an individual basis and not for the

.T entire staff on a shift.

Any deviation from the above guidelines shall be authorized by e

[O ASd5 7.'."" "^, "Z % or higher level of management, in accordance with i

@f MM7J established procedures and with documentation of the basis for L granting the deviation. Controls shall be included in the procedures such that individual overtime shall be reviewed monthly by ee.

^"" "^

. ".Z 74 or his designee to assure that excessive hours have not been assigned. Routine deviation from the above guidelines is 41 not authodzt d u , _ _

f, 2, '. . [ h.

(h,.i tt Supere aar d serati sorsTshal (ail OMations Suhintendentshd alh ola a senior reactor operator license.

lb The lant ope tors shal ola a reac gr operator icenseg O

/ A.9 i

O HATCH - UNIT 2 6-3 Amendment No. 47, 94, 116 l

Sec l

1 1

I INSERT 2 FOR ITS 5.2 5.2.2.g The Shift Technical Advisor (STA) hall provide advisory technical support to the hift pervisor - (SS) in the I areas of thermal hydraul cs, r ctor engineering, and plant analysis with regard to the safe operation of the unit. In addition, the STA shall meet the qualifications specified by the Commission Policy Statement on Engineering Expertise on Shift.

l O

l l

i I

l HATCH UNIT 2 m

I

[] DISCUSSION OF CHANGES V ITS: SECTION 5.2 - ORGANIZATION ADMINISTRATIVE A.1 The current Technical Specification provides examples of the Unit staff positions who perform safety-related functions and whose working hours are limited. Since these examples may not include all positions that could be limited and since these positions may change, the examples have been generalized. The modification of these examples clarifies present requirements and thus is an administrative change.

A.2 The current plant s;oecific titles are changed to generic titles, and ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

TECHNICAL CHANGES - MORE RESTRICTIVE H.1 CTS 6.2.2.c requires that at least two licensed operators be present in the control room for each reactor in the process of startup, scheduled reactor shutdown, and during recovery from reactor trips. The ITS is more y restrictive by requiring a Senior Reactor Operator to be present in the i control room while the unit is in MODES 1, 2, or 3, in addition to at (d least one licensed Reactor Operator.

M.2 New requirements are being added in the ITS to specify the function of the Shift Technical Advisor (STA). The STA shall provide advisory technical support to the Shift Supervisor in the areas of thermal hydraulics, reactor engineering, and plant analysis with regard to the safe operaticn of the unit.

TECHNICAL CHANGE - LESS RESTRICTIVE

" Generic" LA.1 Details of the minimum shift crew requirements located in current Technical Specifications Table 6.2.2-1 are relocated to plant procedures.

The minimum shift crew requirements for licensed operators and senior operators contained in 10 CFR 50.54 (k), (1), and (m) and do not need to be repeated in the ITS. The minimum shift crew requirements for non-licensed plant equipment operators transferred from present Table 6.2.2-1 to ITS 5.2.2.a. In addition, ITS 5.1.5 contains requirements for the control room command function, ITS 5.2.2.c contains minimum requirements for licensed Reactor Operators and Senior Operators to be present in the control room, and ITS 5.2.2.g contains STA requirements. The relocation of the details of the minimum shift crew requirements to plant procedures is acceptable considering the controls provided by regulations, the p) t remainingrequirementsintheITS,andplantprocedurechangecontrolpy the 10 CFR 50.59 process.

HATCH UNIT 2 1 REVISION y

fpec,' Neat on M. I ^

ADMINISTRATIVE CONTROLS - l 1

r 6.16 POST-ACCIDENT SAMPLING AND ANALYSIS

7[j' A program shall- be established, implemented, and maintained to ensure the f'p i.. -

capability to obtain and anal ze samples of reactor coolant, radioactive iodines and particulates in pfait gaseous effluents, and containment $M'#./

4 atmosphere under accident condition!-

The program shall include the following:

(1) Training of personnel, (2) Procedures for sampling and analysis, and

3) Provisions for maintenance of sampling and analysis equipment.

. 6.17 0FFSITE DOSE CALCULATION MANUAL Ool ; p$nT CY5 D6FZNSEON CDCA 6.17.1 Licensee-initiated changes to tne ODCM shall:

a. Be. documented and records of reviews performed shall be retained as weautreo og Techntesi specificay on 6.10. ho.T This documentation

O4g Thall contain

1) Sufficient information to support the change together with the ap r priate analyses or evaluations justifying.the change s and

2) A determination that the change will maintain the level of radioactive effluent control required by 10 CFR 20.106, 40 CFR Part 190, 10 CFR 50.36a, and Appendix I to 10 CFR

' or reliability of effluent, Part 50 and dose, notoradversely setpoint calculations.

impact the accuracy % @ condh

b. I Become effective after review and acceptance by the#R8 and the .

_gpg h.9 m approval of the C..... ;l "r:;r ':xl;;.. ^'

c. Be submitted to the Commission in the form of a complete, legible copy of the entire ODCM as a part of, or concurrent with, the he D w swo Annual Radioactive Effluent Release Report for the period of the of d d ys reprt in which any change to the ODCM was made. Each change shall i ! 4e rm 5.r.+, be identified by markings in the margin of the affected pages,

., % u,o.

clearly indicateindicating the date (the area of e.g., month / year)the page the change that was changed, and shall was implemented.

[6.18 RADI0 ACTIVE EFFLUENTS CONTROL PROGRAM A program shall be established, implemented, and maintained conforming with 10 CFR 50.36a for the control of radioactive effluents and for maintaining the doses to MEMBERS OF THE PUBLIC from radioactive i effluents as low as reasonably achievable. The program (1) shall be j contained and (3) shall in the ODCM, include reme(2) dial actions to be taken whenever the programshall be implemen limits are exceeded. The program shall include the following elements:

1) Limitations on the OPERABILITY of radioactive liquid and gaseous

!- t monitering instrumentation including surveillance tests and setpoint l ( determination in accordance with the methodology in the 00CM, 4

n \ ,\t o.,\h.#2\s.o.2 HATCH - UNIT 2 6-22 Amendment No. 45, 48, 129 l c4 2--

DISCUSSION OF CHANGES '

, ITS: SECTION 5.5.1 - 0FFSITE DOSE CALCULATION MANUAL i

ADMINISTRATIVE A.1 The current TS ccr,tains a cross-reference to Specification 6.10.2.o for record retention. This c:oss-reference is not included in the proposed TS. The removal of this cross-reference is a presentation preference and, thus, is considered an administrative change.

A.2 CTS numbers are changed by the new format of the proposed TS for Section 5.0. These new TS numbers are indicated in the TS markup.

A3 The Radiological Environmental Monitoring Program is being relocated from the TS as discussed in the changes for CTS 6.19. Therefore, the deletion of the reference to this removed TS is considered administrative.

A.4 The current plant specific titles are changed to generic titles. ITS Section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities to be included in the FSAR. The specific titles do not alter the responsibilities delineated in the Technical Specifications. Therefore, this is considered an administrative change only.

O o

HATCH UNIT 2 1 REVISION [f

1 l

l O

UNIT 2 NO SIGNIFICANT HAZARDS DETERMINATION O

1 l

l l

l 1

i lO l

l l

l

- - - - . _ - - _ - _ - - _ - _ - _ _ _ _ _ _ _ _ _ _ _ _l

O N0 SIGNIFICANT HAZARDS DETERMINATION b ITS: SECTION 3.0 - LCO AND SR APPLICABILITY L.2 CHANGE In accordance with the criteria set forth in 10 CFR 50.92 Georgia Power Company l has evaluated this proposed Technical Specifications change and determined it l does not involve a significant hazards consideration based on the following: l

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

The change to Specification 3.0.4 will allow MODE or other specified condition changes while the plant is in the ACTIONS which do not prohibit continued operation for an unlimited time in the MODE or other specified condition in the Applicability. Since it has been previously determined that continued operation is acceptable for these affected LCOs, and making a MODE or other specified condition change to enter or move through the Applicability results in the same probability and consequences as initially being in the Applicability when the ACTIONS are entered due to an inoperable component, there is no significant increase in the probability or consequences of an accident previously evaluated. In addition, exception to Specification 3.0.4 has already been taken in many of the individual existing ACTION statements. Incorporating the proposed change into LCO 3.0.4 will ensure that exceptions will be consistently

(' applied when justified. Deletion of the individual exceptions will have no impact upon the requirements in the Specifications since the exception to existing Specification 3.0.4 will now be contained within proposed LC0 3.0.4.

The addition of the phrase "or that are part of a shutdown on the unit" and the sentence "LC0 (SR) 3.0.4 is only applicable for entry into a MODE or other specified condition in the Applicability in MODES 1, 2, and 3" added to LC0 3.0.4 and SR 3.0.4, provides clarity for the actual application of the LCO 3.0.4 restrictions. It has been determined that the potential restriction eliminated with this portion of the change are either: 1) consistent with the allowance discussed above when ACTIONS allow continued operation in the Applicability, 2) consistent with the existing LC0 3.0.4 allowance for entering Applicabilities that would be applicable as a result of complying with shutdown ACTIONS, or 3) precluded by compliance with the applicable ACTIONS.

Therefore this change will not result in a significant increase in the probability or consequences of an accident previously evaluated.

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

The proposed change does not necessitate a physical alteration of the plant (no new or different type of equipment will be installed) or changes O in parameters governing normal plant operation. Thus, this change does V not create the possibility of a new or different kind of accident from any accident previously evaluated.

HATCH UNIT 2 2 REVISION \F

. .- . . .. . _- =-- .

l

~

l N0 SIGNIFICANT HAZARDS DETERMINATION i I

ITS: SECTION 3.0 - LC0 AND SR APPLICABILITY L.2 CHANGE (continued)

3. Does this change involve a significant reduction in a margin of safety? l The change to Specification 3.0.4 will allow MODE or other specified condition changes while the plant is in the ACTIONS which do not prohibit continued operation for an unlimited period of time in the MODE or other specified condition in the Applicability. Since it has been previously determined that continued operation is acceptable for these affected LCOs and making a MODE or other specified condition change to enter or move through the Applicability results in the same consequences as initially being in the Applicability when the ACTIONS are entered due to an inoperable component, there is no significant reduction in the margin of safety. In addition, exceptions to Specification 3.0.4 are already contained within many of the applicable existing ACTION statements.

Incorporating the exceptions within proposed LC0 3.0.4 will ensure their consistent application.

The addition of the phrase "or that are part of a shutdown on the unit" and the sentence "LC0 (SR) 3.0.4 is only applicable for entry into a MODE

- or other specified condition in the Applicability in MODES 1, 2, and 3" added to LC0 3.0.4 and SR 3.0.4, provides clarity for the actual application of the LC0 3.0.4 restrictions. It has been determined that the potential restriction eliminated with this portion of the change are either: I) consistent with the allowance discussed abcVe when ACTIONS allow continued operation in the Applicability, 2) consistent with the existing LC0 3.0.4 allowance for entering Applicabilities that would be applicable as a result of complying with shutdown ACTIONS, or 3) precluded by compliance with the applicable ACTIONS.

Therefore this change will not result in a significant decrease in the margin of safety.

O HATCH UNIT 2 LQA REVISION \f

NO SIGNIFICANT HAZARDS DETERMINATION

' i ITS: SECTION 3.8.1 - AC SOURCES - OPERATING L.10 CHANGE In accordance with the criteria set forth in 10 CFR 50.92, Georgia Power Company has evaluated this proposed Technical Specifications change and determined it does not involve a significant hazards considaration based on the following:

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

The diesel generators (DGs) are .used to support mitigation of the

. consequences' of an accident; however, they are not considered as the initiator of any previously analyzed accident. As such, the elimination of a specific signal requirement to perform the " hot restart" surveillance testing will not increase the probability of any accident previously evaluated. The proposed SR continues to provide adequate assurance of OPERABLE DGs since restart capability is not affected by the start signal.

Therefore, the proposed change does not involve an increase in the consequences of any accident previously evaluated.

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

The proposed change does not introduce a new mode of plant operation and does not involve physical modification to the plant. Therefore, it does

not create the possibility of a new or different kind of accident from any

^

accident previously evaluated.

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

This change does not involve a significant reduction in a margin of safety since the start capability of the DGs is not affected by the start signal.

Therefore, the proposed change provides an equivalent assurance of the

capability of the DGs to perform their safety function.

This change was approved by the NRC, and issued as Amendment 131, in an Safety

Evaluation Report dated February 24, 1994.

i 4

. O ,

HATCH UNIT 2 10 REVISIONkk

a - - #

O O '

SLs 2.0 2.0 SAFETY LIMITS (SL's) 2.1 SLs 2.1.1 Reactor Core SLs 2.1.1.1 With the reactor steam done pressure < 785 psig or core flow < 10% rated core flow:

THERMAL POWER shall be s 25% RTP.

2.1.1.2 With the reactor steam done pressure t 785 psig and core flow t 10% rated co flow: ,- .

EPRshallbea for two oo r culation ek operation or a for_s_ ingle ooprecirculationj t ( operation. y n ' g, l . . I, o

~

2.1.1.3 Reactor vessel water level shall be greater than the top of active irradiate p tl

((RCS 2.1.2 Reactor Coolant System sure SL Reactor steam done pressure shall be-esists5aed s 1325 psig.

2.2 SL Violations With any SL violation, the following actions shall be completed:

2.2.1 Within I hour, notify the NRC Operations Center, in accordance with 10 CFR 50.72.

2.2.2 Within 2 hour2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months s: '

2.2.2.1 Restore compliance with all SLs; and L L.2. 2 I_n3*rt all inset tabio control rods.

C P A ty4c.uMerer w Gr A

of Md oM Nd/or 54 h/

2.2.3

!g Within 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months , notify the c "

m er "l at;and e T .'i ;; P = :i d:r.t 420!:20 $+ M 'a; -

m panager--

-5] and the 9 i

v

~p:;ificetien 5.5.2, "[0ff-it:]foffsite reviewe

-5? cified in S ";vi;w end ^. edit") .- o faho.%c),hd ky 1

I {sso6..,3 re c.26 j . (continued)

BWR/4 STS .

2.0-1 Rev. O, 09/28/92 s

, , ,- m-,.

SLs 2.0 2.0 SLs

^

2.2 SL Violations (continued) 150 M# [p 2.2.4 Within 30 days, a License Event Repo'ri(LkR) shall be prepared f pursuant to 10 CFR 50.73. The LER shall be submitted to the NRC, o) theJfoffsite reviewerX yT. 'i;d i- Speci#icatiaa 5.5.2),andthe T

%Eern)(anager--Nucle - "!: ti and " ice ."r :id;r.t -4;I;c.r. -

l

^ r:ti==};

l fami kcorwal<4

& erp%k

% o nachar tcuhd r (25f MA uf<.{y 2.2.5 Operation of the unit shall not be resumed until authorized by the NRC.

l l

BWR/4 STS 2.0-2 Rev. O, 09/28/92

,,a

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

LCO 3.0.2 Upon discovery of a failure to meet an LC0, the Required Actions of thc associated Conditions shall be met, except as provided>in LCO 3.0.6.

(W .

' '?-

'o' If the LCO is met or is no longer applicable rior to s

' ' ~ ~ expiration of the specified Completion Time (s , completion of Required Action (s) is not required, unless otherwise I

LCO 3.0.3 When an U d 5 not met and the associated ACTIONS are not metjjW an associated ACTION is not provid the unit shall j be placed in a MODE or other specified condition in which j

O;c

[m d ' g' ,A

c. e '

e the LCO is not ap licable. Action shall be initiated within I hour to place t e unit, as applicable, in:

,jf ,

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

(C' j i bg W[0 3

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

\%

C

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

\" A4 Exceptions to this Specification are stated in the individual Specifications.

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

LCO 3.0.3 is ap able in MODES 1, 2, and 3.

ph . 6 A.3 vv LCO 3.0.4 When an LCO is not met, entry into a MODE or other specified condition in the Applicability shall not be made except when he associated ACTIONS to be entered perinit continued operation in the MODE or other specified condition in the Applicability for an unlimited period of time. This (continued)

BWRi4 STS 3.0-1 Rev. O, 09/28/92

g LCO Applicability l o , % + a re " t o ' a-3.0 LCO APPLICABILITY ,

7 gM fd# # # "

LCO 3.0.4 Specification shall not prevent changes in MODES or other (continued) specified conditions i the Applicability that are required to comply with ACTIONSy l

Lt,o 3.04 doly M itah Exceptions to this Specification are stated in the for eAn( in+oa Ac0E er other individual Specifications.

SN4fiul cudifb in tk into MODES or other specified conditions in theThese exceptions a AI plicabjldY in MODES t,2, Applicability when the associated ACTIONS to be entered and 3 '

r j allow unit operation in the MODE or other specified condition time.

in the Applicability only for a limited period of '

OT. Q k LCO 3.0.5 i Equipment removed from service or declared inoperable to !

comply with ACTIONS may be returned to service under administrative control solely to perform testing required to O demonstrate its OPERABILITY or the OPERABILITY of other equipment, This is an exception to LCO 3.0.2 for the system !

returned to service under administrative control to perform '

the testing required to demonstrate OPERABILITY. t LCO 3.0.6 When a supported system LCO is not met solely due to a O

support system LCO not being met, the Conditions and Required Actions associated with this supported system are not required to be entered. Only the support system LCO ACTIONS are required to be entered. This is an exception to LCO 3.0.2 for the supported system. In this event, pp ,p/

g g,% additional evaluations wi 1 itations may be required in SA accordince witn specificatio fr:8, " Safety Function

'g.Q Determination Program (SFDP)." If a loss of safety function is determined to exist by this program, the appropriate Conditions and Required Actions of the LCO in which the loss

@ of safety function exists are required to be entered.

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

(continued)

BWR/4 STS 3.0-2 Rev. O, 09/28/92 j

SR Applicability 3.0 3.0 SR APPLICABILITY SR 3.0.3 When the Surveillance is perfonned within the delay period (continued) and the Surveillance is not met, the LCO must famediately be

" declared not met, and the applicable Condition (s) must be entered.

M' The CeapleLen Times of th; n:;uired ^. tien i:;in l-di:t:ly upn f:ibr: t: =:t th: r;;i1kn;;.

SR 3.0.4 Entry into a MODE or other specified condition in the Applicability of an LCO shall not be made unless the LCO's Surveillances have been met within their specified Frequency.

This provision shall not prevent pn:t; thrr;5~

{4ri Yj cr te MODES or other specified conditions (FcWHr= with

+ R:;uiret Actions;or that are f ut of a ch qidew g --

p f 4 h e turn t.

J J -

t l dhe Appl. cab +i +q %a+ o re t

u < c A % cc <r e <g SR 3.04 & cnly aplicab't krwhy ink a F goog ,c ,ther 6peci&d md/M 4

qqt;ca%\M ih MooES l' 1' #N

l l

. 1

%)

BWR/4 STS 3.0-5 Rev. O, 09/28/92

)

i a Responsibility 5.1 5.0 ADMINISTRATIVE CONTROLS 5.1 Responsibility j

l 5.1.1 e [ Plant Superi endent) shall be esponsible for ovh 11 unit j

~ o ation and shall elegate in writi the succession t his !

Also I'

res _

sibility during is absence. :

P. I l 4

Md' # 71$1 B

e @3 r ~ c.1 hor his designe TTSuperintendent in accordance with s\

TitSEwr approved deinistrative pro dures, shall ap ove prior to A implementa on, each propose test or experine and prososed changes and difications to u t systems or equ poent t1at affect' nuclear safety. N j h 5.1. Gamin (S1 Thehhift C;:-"irer %d.shall set)be-hresoonsible for the control room command faiction, managem direct < to this fact 3, 6 Pel si)sted by TtHL ;11%esl 1 f corp or si saa t1/ i

=>1i % ss2e h nnu h to station sonnel . Murin any M h"f*' ,

a>sence or tle M from the contro' r ile,$$t unit s in l

/ MODE 1. 2. or 3. an individual with - v:" Senior Reactor

,1

~b Operator (SRO) license shall be desigYto assume the con room command function. During any absence of the Wrom the control room while 0;^$f/in MODE 4 or 5, an individual with O "A SRO license or eactor Operator license shall be M $ted to assume th control room osmand function I

j'

~

(SH synW C4 h a c t, }f <

N bo4h (t N46 CAO cm j l

~- .

M. 31 )

. 31 O

BWR/4 STS 5.0-1 Rev. O,09/28/92

~

1 Organization 5.2 5.0 ADMINISTRATIVE CONTROLS Q g, m g 4.yg g }

5.2 Organization S[M g py; y g,M fulfn +NtWw Wlau I 4

5.2.1 Onsite and offsite Oraanizations ,

Onsite and offsite organizations shall be established for unit operation and corporate manaflement, respectively. The onsite and offsite organizations shall nelude the positions for activities affecting safety of the nuclear power plant.

a. Lines of authority, res onsibility, and communication shall

& 6'N ee be defined and establis ed throughout highest management g *T N#' levels, intermediate levels, and all o erating organization P.2. positions. These relationships shall e documented and var i I updated, as appropriate, in organization charts, functional FSAR descriptions of departmental responsibilities and relationships, and Job descriptions for key personnel M h2 oaO positions, o equivalent forms of doc tion. These f Phnr #=rtA requirements hall be documented in the % l Vulr ~L -

SA-n b. Hw glent 0.wriat;;iatDshall be responsible for overall safe operation of the plant and shall have control over

. w,,4 M y , $ .r.

those onsite activities necessary for safe operation and maintenance of the plant; g

4 ./ The de ::::!'!M.I co ora executiveb:n:ttied05:??5:S campepe4+ resporisib or everell f eat ...c k r n 'et[ M

end-shall take any measures needed to ensure acceptable h4 performance of the staff in operating, maintaining, and providing technical support to the plant to ensure nuclear j safety; and

d. The individuals who train the operating staff, carry out health physics, or perform quality assurance functions may report to the appropriate onsite manager; however, these individuals shall have sufficient organizational freedom to ensure their independence from operating pressures.

GPI 5.2.2 Unit Staff (<jnelvh % Sollow The unit staff organization shallh es felk:

s e (continued)

BWR/4 STS 5.0-2 Rev. O,09/28/92

., _ _r - se y

INSERT A FOR NUREG 5.1 5.1.1 The plant manager shall provide direct executive l oversight over all aspects of Plant Hatch.

5.1.2 An assistant plant manager shall be responsible for l overall unit operation, except for the Radiological Environmental Monitoring Program as described below and ,

l for delegation in writing of the succession of this responsibility during his absence. Certain plant support functions shall also be the responsibility of an assistant plant manager.

5.1.3 The plant manager or his designee shall be responsible for the Radiological Environmental Monitoring Program and for the writing of the Annual Radiological Environmental Operating Report.

5.1.4 Each of the individuals in Specification 5.1.1 through Specification 5.1.3 is responsible for the accuracy of the procedures needed to implement his responsibilities.

O O

HATCH UNITS 1 AND 2 REVISION Y

Organization 5.2 O 5.2 Organization P.3 Unit Staff (continued)

GP5.2.2 b.

i At least one licensed ReactorJ0perator (RO) shall be present (Anin)bl)v.) in the control roose:: ' d din the reactor. In addition, while the un't is in MODE 1, 2, or 3, at least one 7"glyl, j D licensed Senior Reactor Operator (SRO) shall be present in la~e rT

,j the control room, ra) M!*^ = = M.. ' r T W h h 3 shall be on site when fuel is patecTlon d in the reactor. The position may be vacant for not more

,, g g than 2 hours2.314815e-5 days 5.555556e-4 hours 3.306878e-6 weeks 7.61e-7 months ', in order to provide for unexpected absence, P.1 provided inmediate action is taken to fill the required position.

d. ther a license RO or license SRO limited to el d; p, j ha ling who has no ncurrent resp ibilities dur oper ion shall be pre t during fue direct supervise all CO ALTERATIONS. ndling and sha )f

e. Administrative procedures shall be developed and implemented to limit the workina hours of unit staff who nerforn safety.

related functionnI(e.g. licensed SR0s, ed R0 eal h a op and key tenance Adequate shift coverage shall be maintained without routine 1

' heavy use of overtime. The ob.iective shall be to have

/ f, 5' operating personnel work 9 f* Or !?! .'.nr chi nominal i

[ 40 hour4.62963e-4 days 0.0111 hours 6.613757e-5 weeks 1.522e-5 months week, while the unit is operating. However, in the '

event that unforeseen problems require substantial amounts l

( of overtime to be used, or during extended periods of '

t P, L shutdown for refueling, major maintenance, or major plant

.. modification,'on a temporary basis the following guidelines shall be followed:

1. An individual should not be pemitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months straight, excluding shift turnover time; x 2. An individual should not be permitted to work more than 16 hours1.851852e-4 days 0.00444 hours 2.645503e-5 weeks 6.088e-6 months in any 24 hour2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months period, nor more than 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months in any 48 hour5.555556e-4 days 0.0133 hours 7.936508e-5 weeks 1.8264e-5 months period, nor more than 72 hours8.333333e-4 days 0.02 hours 1.190476e-4 weeks 2.7396e-5 months in any 7 day period, all excluding shift turnover time; 1

y (6 3 , , I a e cns a) o od r e e- I. m v.cl opeahin t yn,u] l . '

ho Hh phy 5. c s +n h n c l a n s , k< y ra a n n n w e f

\ ocesenn# I efc. L (continued)

- l BWR/4 STS 5.0-3 Rev. 0,09/28/92

Organization 5.2 5.2 Organization 5.2.2 Unit Staff (continued)

M 3- 3. A break of at least 8 hours9.259259e-5 days 0.00222 hours 1.322751e-5 weeks 3.044e-6 months should be allowed between

[j,g 0g .

work periods, including shift turnover time;

4. Except during extended shutdown periods, the use of overtime should be considered on an individual basis and not for the entire staff on a shift.

or ky MM" 7Any deviation fromhhe above guidelines shall be authorized leAls v? + m 262-m' by \the [ nt Shrinten t e

@nay" g .

oanqe wit rov admiihstrative or M desg'oNDv rocedures, ne ,K]n) y 7, g (hia leh ls of nagene tfin accordance with established procedures and with documentation of the basis for granting the deviation. p, q Controls shall be inel ded in the procedures such tha individual overtime a1 e reviewed monthly by %?ier.'

u nss%q. Q. . ,, . . . . . . . m . . . ., or esignee to ensure that excess <ve

'z pIM

~

nours nave not been assigned. Routine deviation from the /2.1 WF above guidelines is not authorized.

98 1 I

-3 he amount of overti worked by unit staf mbers

}

7 p sited and cont orning safety relaed in accordance(functions the NRC Policy St shall be ment on

_ working (GenericLette 2). Y

f. The hrskions . anager 5- ". :i:te. t 4ereticc,; ."anage,}-

shall old an { license. g . .,

F g.

3azTova or m a ir.ve P.34Q,2 A The Shift Technical Advisor (ST shall provide a vism y _

IS / technicalsuporttotheghift pervisor $d( Tn the areas @

of thermal h draulics, reactor engineering, and plant analysis with regard to the safe operation of the unit.

f d d n'o n , 7 % srA skall n edT & ganllNeeWoM g .rfea/J L p,:_. ., y, r4 co-e ,.,m . _ e

s /.- p.m y sr.7- ~r

. O BWR/4 STS 5.0-4 Rev. 0, 09/28/92

b;&n:, Program ind Manuals

} 68I 5 Tr u i.n 3 Progr and Manuals 5.7. 2 ProcebCo ol Program (PCP) (con ued)

b. Shall be e tive after reytew and a stance by the g, j [ review metho Specification 5.5.1] a approva f i he [ Plant Superin dent]. l 2 f/ _0ffsite Dese calculation Manual (00CM

a. The 00CM shall contain the methodology and parameters used in the calculation of offsite doses resulting from radioactive gaseous and liquid effluents, in the calculation of gaseous and liquid effluent monitoring alars and trip 6Al [~ setpoints, and in the conduct of thegadiological

_gnvironmentalgonitoringfrogram;and

3. The 00CM shall also contain the gadioactive gffluent

/ontrols and fadiological Rfivironmental fonitoring 8l

, . _ ,m 1--"i r_m = 5. 7.3 and descriptions o e infomation that shou' d be inc' uded in the Annual O Radiological Environmental Operating, and Radioactive Effluent Releas eports required by Specification

)

I

O.^.1.3" and Sp fication @ .0.1 4 , g, 3 ,

Licensee initiated changes to the 00CM:

yes ,,9;y j

a. Shall be documented and records of reviews performed shan be retained. This documentation shall contain:

1. sufficient infomation to support the change (s) together with the appropriate analyses or evaluations justifying the change (s), and

. 2. adeterminationthatthechange(s)maintainthelevels of radioactive effluent control required by 10 CFR 20.106, 40 CFR 190, 10 CFR 50.36a, and

, 10 CFR 50, Appendix I, and not adversely impact the a P.2 accuracy or ability of effluent, dose, or setpoint calculatio -

l b. Shall become effective after review and acceptance by the CC'880 " K i_n r m = ne.: :" ;rr - --- a s. 2 and the approval of thecgi;... y., .C T y; and j

m, y

fhg R fr

~

aw~.g GD (continued)

~

l BWR/4 STS 5.0-19 Rev. 0, 09/28/92

m fr:::dar:hPrograms[andManuals (GnI N Gr.)

l 5. . recedur;5) Program nd Manuals LC Q (EE.S -

g. 7.2Jj Offsite Dose Calculation Manual (ODCN) (continued)

c. Shall be submitted to the NRC in the form of a complete, l

legible copy of the entire ODCH as a part of or concurrent with the Radioactive Effluent Release Report for the period of the report in which any change in the ODCM was made.

Each change shall be identified by markings in the margin of the affected pages, clearly indicating the area of the page that was changed, and shall indicate the date (i.e., month and year) the change was implemented.

e./:2 ') _himary Coolant Sources outside containment P.2 Thi; program provides controls to minimize leakage from those ad A.JD' portions of systems radioactive outside fluids duringcontainment a serious transient that could contain or acciden to highly

levels as low as practicable. Thesystemsinclude:(The P*

" Y' tr :: rB Core Spray, High Pressure Coolant Injection, Residual Heat Removal, Reactor Core Isolation Cooling *"~--- -- ~ ^ ""Q p, .r==ss-r =!:n;.:c w ry = 'r str=3 The program shal' include the following:

E 2.

a. Preventive maintenance and periodic visual inspection requirements; and Sys tw P.ll b. - ntegr:tE leak test requirements for each system t refueling cycle intervals or less.

f.7.2.5 In Plant Ra ation Monitoring N This program pr ides controls to ensure e capability to accurately determi the airborne iodine co entration in vital j areas under accident onditions. This progra hall include the following:

C, P. I

a. Training of personnel,

b. P edures for monitoring, and

c. Provis ns for maintenance of mpling and analysis uipmen f

s to k

J a n p r ~ ', H e ). b y sysh - )ss O a n)

P.ll ra) !.19lca l cor);t' oms, (continued) h BWR/4 STS 5.0-20 Rev. 0,09/28/92

(

O NUREG 1433 COMPARISON DOCUMENT - BASES O

I i

O

LCO Applicability k Id n$be med en % $

d BASES hyloabih% O'edIabe en*e re A.f LCO 3.0.3 assemblies in the spent fuel storage pool." Therefore, this (continued) LCO can be applicable in any or all MODES. If the LCO and

1. the Required Actions of LC0 3.7.8 are not met while in MODE 1, 2, or 3, there is no safety benefit to be gained by placing the unit in a shutdown condition. The Required Action of LCO 3.7.8 of " Suspend movement of irradiated fuel assemblies in the spent fuel storage pool" is the appropriate Required Action to complete in lieu of the actions of LCO 3.0.3. These exceptions are addressed in the individual Specifications.

g.(

I LCO 3.0.4 A \

i LCO 3.0.4 establishes-limitations on changes in MODES or 4 y M't Y[,

'T other specified conditions in the Aoplicability when an LCO

! ghfed in thaf 1--

is not met. It precludes placing the unit in a differer, licab; b e- MODE or other specified conditionpwhen the following exist: l A

f [e ed) a.,o/he requirements of Nd , the "^M r :ther <g. /

t -

/ -:p: ified ceeditien te 5: ::ter:d, r: ::t::tiand pi

'. Continued noncompliance with these LCO requirements %} h.

ZD

I , would result in the unit being required to be 2: :p .

D(gf,,cemelihar.ne-ch + hat f A e =E or wh >va ned :::ditie " e550 th:

Dm -

- ovu ov. .yy.y to comply with the Required

/ Actions.

Compliance with Required Actions that pemit continued

) operation of the unit for an unlimited period of time in a MODE or other specified condition provides an acceptable gg ,Se A - J,mb' b e, level of safety for continued operation. This is without desi red -*T regard to the status of the unit'before or after the MODE e niere1 change. Therefore, in such cases, entry into a MODE or other specified condition in the Applicability may be made in accordance with the provisions of the Required Actions.

The provisions of this Specification should not be interpreted as endorsing the failure to exercise the good c practice of restoring systems or components to OPERABLE f g&n,g uassociskd status beforej a't v t q.

g oo E e 0 % c.sP W fit 0 The provisions of LCO 3.0.4 shall not prevent changes in

( g @ in e s. Q ic A b h MODES or other specified conditions in the Applicability that are required to comply with ACTIONS. In addition, the provisions of LCO 3.0.4 shall not prevent changes in MODES (continued)

'O O,09/28/92 BWR/4 STS B 3.0-5 Rev.

4

. - , . __. . _s.- . . ~ , . .r.--- _ . _ , - - . ,

LCO Applicability BASES *N 7

LC0 3.0.4 or other speci) conditions in the Applicability that (continued) result from a r,ss e shutdown. !

Exceptions to LCO 3.0.4 are stated in the individual Specifications. Exceptions may apply to all the ACTIONS or to a specific Required Action of a Specification. ,

l lNSERT w

'gi Surveillances do not have to be performed on the associated inoperable equipment (or on variables outside the specified limits), as permitted by SR 3.0.1. Therefore, changing MODES or other specified conditions while in an ACTIONS Condition, either in compliance with LCO 3.0.4 or where an exception to LCO 3.0.4 is stated, is not a violation of SR 3.0.1 or SR 3.0.4 for those Surveillances that do not have to be perfomed due to the associated inoperable equipment. However, SRs must be met to ensure OPERABILITY '

prior to declaring the associated equipment OPERABLE (or I variable within limits) and restoring compliance with the affected LCO.

LCO 3.0.5 LCO 3.0.5 establishes the allowance for restoring equipment ;

to service under administrative controls when it has been ;

removed from service or declared inoperable to comply with '

ACTIONS. The sole purpose of this Specification is to provide an exception to LCO 3.0.2 (e.g., to not comply with the applicable Required Action (s)) to allow the perfomance of SRs to demonstrate:

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

b. The OPERABILITY of other equipment.

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

An example of demonstrating the.0PERABILITY of the equipment being returned to service is reopening a containment :

I (continued)

BWR/4 STS B 3.0-6 Rev. O, 09/28/92 O\l l

1

Insert BQ LCO 3.0.4 is only applicable when entering MODE 3 from N0DE 4, MODE 2 from MODE 3 or 4, or MODE 1 from MODE 2. Furthermore, LCO 3.0.4 is appitcable when entering any other specified condition in the Applicability only while operating in MODE 1, 2, or 3. The requirements of LCO 3.0.4 do not apply in MODES 4 and 5, or in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

O O

1..a 0 7 0-b R e visio n f

-. s " g -W e-hv q - - - -

e SR Applicab I 3 ess; O BASES i i SR 3.0.3 period of up to 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months pplies from the point in ti that (continued) it is discovered that the Surveillance has not been performed in accordance with SR 3.0.2, and not at the t me that the specified Frequency was not met.

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

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

When a Surveillance with a Frequency based not on time intervals, but upon specified unit conditions or operational

, situations, is discovered not to have been performed when j specified, SR 3.0.3 allows the full delay period of 24 hours2.777778e-4 days 0.00667 hours 3.968254e-5 weeks 9.132e-6 months I

to perform the Surveillance.

SR 3.0.3 also provides a time limit for completion of Surveillances that become applicable as a consequence of MODE changes imposed by Required Actions.

Failure to comply with specified Frequencies for SRs is expected to be an infrequent occurrence. . Use of the delay period established by SR 3.0.3 is a flexibility which is not intended to be used as an operational convenience to extend l' Surveillance intervals.

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

BWR/4 STS B 3.0-13 Rev. O, 09/28/92 l

L-----.-___-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - _ - - - - - - - _ - - - - - - - - - - - - - - - _ - - - - - - - - - - - - - - - - - - - - - - - - -

SR Applicability B 3.0 BASES SR 3.0.3 Required Actions for the applicable LCO Conditions begin (continued) immediately upon the failure of the Surveillance.

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

SR 3.0.4 SR 3.0.4 establishes the requirement that all applicable SRs must be met before entry into a MODE or other specified condition in the Applicability. This Specification ensures that system and component OPERABILITY requirements and variable limits are met before entry into MODES or other specified conditions in the Applicability for which these systems and components ensure safe operation of the unit.

$ h..,y--......... .rr.. ......r N .s.....m ....m.,

pecified ;; .diti;n; ir. th; Applicobility essecieted ith

. . . . ......_.. .. ... . ......y.

The provisions of SR 3.0.4 shall not prevent changes in g 3,0+g MODES or other specified conditions in the Applicability A

that are required to comply with ACTIONS.J The precise requirements for performance of SRs are specified such that exceptions to SR 3.0.4 are not ecessary. The specific time frames and conditions f_g

ad h I-i on , +he ecessary for meeting the SRs are specified in the pr oW W "5 of SR 3.requency, 0A in the Surveillance, or both. This allows shall not f,e chny5 erformance of Surveillances when the prerequisite y- ondition(s) specified in a Surveillance procedure require in MoDD or entry into the MODE or other specified condition in the 3 n (i ed couch +in's in Applicability of the associated LCO prior to the perfomance OC gfi'g;IHg dhd NIf or completion of a Surveillance. A Surveillance that could Srrrn ag *f 56ddow.not be perfomed until after entering the LCO Applicability ~)woul a , until the specific conditions needed are met. Alternately, the Surveillance may be stated in the form of a Note as not ,

OF required (to be met or performed) until a ) articular event, condition, or time has been reached. Furt1er discussion of the specific formats of SRs' annotation is found in i Section 1.4, Frequency. )

1 p.y h4SER 504 8]

O I

BWR/4 STS B 3.0-14 Rev. O, 09/28/92 l l

l

l i

i l

,a Insert SR 3.0.4 l l

However, in certain circumstances, failing to meet an SR will not result in SR 3.0.4 restricting a MODE change or other specified condition change. When a i system, subsystem, division, component, device, or variable is inoperable or outside its specified limits, the associated SR(s) are not required to be i performed per SR 3.0.1, which states that surveillances do not have to be performed on inoperable equipment. When equipment is inoperable, SR 3.0.4 does not apply to the associated SR(s) since the requirement for the SR(s) to be i performed is removed. Therefore, failing to perform the Surveillance (s) within the specified Frequency, on equipment that is inoperable, does not result in an SR 3.0.4 restriction to changing MODES y other specified conditions of the Applicability. However, since the LC0 is not met in this instance, LC0 3.0.4 will govern any restrictions that may (or may not) apply to MODE or other specified condition changes.

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

Insert 3.0.4 B SR 3.0.4 is only applicable when entering MODE 3 from HODE 4, MODE 2 from MODE

~., 3 or 4, or MODE 1 from MODE 2. Furthermore, SR 3.0.4 is applicable when entering i i any other specified condition in the Applicability only while operating in MODE

'd 1, 2, or 3. The requirements of SR 3.0.4 do not apply in MODES 4 and 5, or in other specified conditions of the Applicability (unless in MODE 1, 2, or 3) because the ACTIONS of individual Specifications sufficiently define the remedial measures to be taken.

(

V

.In s e d B 3 .0 - I'l fh v s ton F

NA\M (

,G

l.L2. Only V INSERT L for orocosed BASES B 3.3.6.1 [ *U1 Only g Allowable Values corrupond to s 215 inches water column for HPCI and s gnw T t

90 inches water column for RCIC, whic are the parameters monitored on control room instruments. .

IM *u2 mle

, O r

O sosaT To 3 33-163

l

] NUREG 1433 COMPARISON DOCUMENT - JUSTIFICATION FOR DEVIATION ;

l O

i

/~' JUSTIFICATION FOR DEVIATION FROM NUREG 1433

(, ITS: SECTION 3.0 - LCO AND SR APPLICABILITY ,

l PLANT SPECIFIC DIFFERENCES P.1 The Specification number is changed to be consistent with the proper number in Section 5.0. The Safety Function ,

Determination Program number was modified to be 5.5.12 by i NUREG change package BWOG-09, Item C.26, but the correct l number for Plant Hatch is 5.5.10. I P.2 Grammatical errors are corrected.

P.3 Brackets are removed since the information is correct.

GENERIC APPROVED /PENDING CHANGES TO NUREG 1433 GA.1 Change approved per package BWOG-01 Items C.10 and C.11, 3/20/93.

GA.2 Change approved per package BWR-02 Items C.6, C.10, and C.11, 3/20/93.

GA.3 Change approved per package BWR-GC Items C.7, C.11 Rev 1,

(,,) C.12, and C.15, 5/20/93 and 7/28/93.

%J GP.4 Changed to be consistent with NUREG change package BWR-26 Item C.1. (BWR-10 involved some of these same changes, but was replaced in its entirety by BWR-26.)

GA.5 Changed to be consistent with NUREG change package BWR-05 Items C.10, and C.13, Rev.2, June 7, 1994.

GA.6 Changed to be consistent with NUREG change package BWR-07, Rev.1, Item Col. The correct Hatch ITS number was also used, 9/8/93.

GA.7 Changed to be consistent with NUREG change package BWR-18, Item C.8, 3/29/94.

The final status of items annotated in the NUREG 1433 Comparison Documents as GP is shown here.

f k

HATCH UNITS 1 AND 2 1 REVISION %f

JUSTIFICATION FOR DEVIATION FROM NUREG 1433 O ITS: SECTION 5.0 - ADMINISTRATIVE CONTROLS PLANT SPECIFIC DIFFERENCES P.1 The current requirements in Technical Specification 6.1,

" Responsibility,H have been used in plRCe of the ITS 5.1.1 provisions. This is a plant preference to retain the current description of the responsibilities of the plant manager, the assistant plant managers. The ITS dcas not-reflect plant specific organization and responsibilities "

assigned to those positions. Plant specific titles are replaced with generic titles and ITS section 5.2.1.a is revised to include a requirement for the plant specific titles of those personnel fulfilling the responsibilities j

to be included in the FSAR. Replacement of plant specific titles and the addition of a reference to the FSAR do not change the responsibilities but prevent amendment requests ,

for administrative changes.

P.2 The brackets have been removed and the proper values /words have been used for each of the two units, or the bracketed material was not used for Plant Hatch. The specifications were renumbered to reflect the deletion of requirements by es other comment numbers.

f

P.3 Current Technical Specifications wording was used to clarify that for dual unit sites, at least one licensed RO shall be present in the control room for each unit that contains fuel in the reactor.

P.4 The examples are generalized for Unit staff positions who perform safety-related work and whose working hours are limited. The examples in the NUREG may not include all the ,

positions affected and are subject to change. As stated in ITS 5.2.2.e, administrative procedures will contain this information and, as such, the generalized words are sufficient.

P.5 The bracketed information is not in the current Technical Specifications and is not retained in the Plant Hatch ITS.

A nominal 40 hour4.62963e-4 days 0.0111 hours 6.613757e-5 weeks 1.522e-5 months work week is specified and is adequate to ensure the intent of the requirement.

P.6 Current Technical Specifications do not require authorization in advance of any deviations from the-overtime guidelines. The "in advance" provision is overly restrictive and may not be practical on back shifts.

P.7 The current Technical Specifications wording for who may approve deviations from the overtime guidelines is used in O place of the NUREG wording. The proposed change follows in the intent of the NUREG by specifying appropriate Plant Hatch levels of management for this approval.

HATCH UNITS 1 AND 2 1 REVISION [f

ML20076L691

Text

Navigation menu

Search