RS-13-009, Operational Requirements Manual (Orm) 2013

Operational Requirements Manual (Orm) 2013

ML13016A360
Person / Time
Site:	Clinton
Issue date:	01/10/2013
From:	Exelon Generation Co
To:	Office of Nuclear Reactor Regulation
References
RS-13-009
Download: ML13016A360 (165)

Text

Clinton Power Station

Operational Requirements Manual (ORM) 2013 Clinton Power Station, Unit 1 Facility Operating License No. NPF-62 NRC Docket No. STN 50-461

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 1 Rev. 67 October 2009

1.0 PURPOSE

The purpose of this manual is to specify requirements which have been removed from the Clinton Technical Specifications as a result of the conversion to Improved Technical Specifications.

1.1 DEFINITIONS

ACTION 1.1.1 ACTION shall be that part of an Operational Requirement that prescribes required actions to be taken under designated conditions with specified completion times.

ACTUAL TRIP SETPOINT (ATSP) 1.1.2 The actual trip value of the sensed pro cess variable found in the conclusion of the setpoint calculation. It is equivalent to or more conservative than the Nominal Trip Setpoint (NTSP). The ATSP, as such, may provide additional margin to the process or analytical limit.

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

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

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 2 Rev. 67 October 2009 CHANNEL FUNCTIONAL TEST 1.1.5 A CHANNEL FUNCTIONAL TEST shall be the injection of a simulated or actual signal into the channel as close to the sensor as practicable to verify OPERABILITY of all

devices in the channel required for OPERABILITY. The CHANNEL FUNCTION TEST may be performed by means of any series of sequential, overlapping, or total channel steps. CORE ALTERATION 1.1.6 CORE ALTERATION shall be the movement of any fuel, sources, or reactivity control components within the reactor vessel with the vessel head removed and fuel in the vessel.

The following exceptions are not considered to be CORE ALTERATIONS: a. Movement of source range monitors, local power range monitors, intermediate range monitors, traversing incore probes, or special movable detectors (including undervessel replacement); and b. Control rod movement, provided there are no fuel assemblies in the associated core cell.

Suspension of CORE ALTERATIONS shall not preclude completion of movement of a component to a safe position.

FUNCTIONAL-FUNCTIONALITY 1.1.7 A system, subsystem, train, component, or device shall be FUNCTIONAL or have FUNCTIONALITY when it is capable of performing its specified function, as set forth in the current licensing basis. FUNCTIONALITY does not apply to specified safety functions, but does apply to the ability of non-TS SSCs to perform other specified functions that have a necessary support function.

LOGIC SYSTEM FUNCTIONAL TEST 1.1.8A LOGIC SYSTEM FUNCTIONAL TEST shall be a test of all logic components required for OPERABILITY of a logic circuit, from as close to the sensor as practicable up to, but not including, the actuated device, to verify OPERABILITY. The LOGIC SYSTEM FUNCTIONAL TEST may be performed by m eans of any series of sequential, overlapping, or total system steps so that the entire logic system is tested.

MODE 1.1.9 A MODE shall correspond to any one inclusive combination of mode switch position, average reactor coolant temperature, and reactor vessel head closure bolt tensioning with fuel in the reactor vessel as specified in the CPS Technical Specifications.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 3 Rev. 67 October 2009 NOMINAL TRIP SETPOINT (NTSP) 1.1.10 The calculated limiting value of the sensed process variable at which a trip could have been set. The actual trip value (ATSP) may be more conservative than the limiting value.

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

SELF TEST SYSTEM 1.1.12 The SELF TEST SYSTEM (STS) shall be that automatic test system designed to continually monitor the solid state nuclear system protection system (NSPS) functional circuitry by injecting short-duration pulses into circuits a nd verifying proper circuit response to various input combinations.

The SELF TEST SYSTEM is designed to maintain surveillance over all NSPS cabinet ci rcuitry essential to the Reactor Protection System, Emergency Core Cooling Systems, Reactor Core Isolation Cooling System, and the Nuclear Steam Supply Shutoff System on a continuous cyclic basis.

The SELF TEST SYSTEM may be used to pe rform various surveilla nce testing functions to satisfy technical specifications requirements for those components it is designed to monitor. The STS may be used to augment conventional testing methods to perform CHANNEL CHECKS, CHANNEL FUNCTIONAL TESTS, CHANNEL CALIBRATIONS, RESPONSE TIME TESTS and LOGIC SYSTEM FUNCTIONAL TESTS provided that OPERABILITY of the STS has first been verified.

SITE BOUNDARY 1.1.13 The SITE BOUNDARY shall be that line beyond which the land is neither owned, nor leased, nor otherwise controlled by the licensee.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 4 Rev. 67 October 2009 1.2 GENERAL OPERATIONAL REQUIREMENTS

1.2.1 Operational

Requirements shall be met dur ing the MODES or other specified conditions in the Applicability, except as provided in Operational Requirement 1.2.2.

1.2.2 Upon discovery of a failure to meet an Operational Requirement, the ACTION requirements of the associated Operational Requirement shall be met. If the Operational Requirement is met or is no longer applicab le prior to expiration of the specified completion time(s), completion of the ACTION(s) requirements is not required, unless otherwise stated.

1.2.3 When an Operational Requirement is not met and the associated ACTIONS are not met, an associated ACTION is not provided, or if directed by the associated ACTIONS, action shall be initiated within 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> to:

a. Implement appropriate compensatory actions as needed;

b. Verify that the plant is not in an unanalyzed condition or that a required safety function is not compromised by the inoperabilites, and

c. Within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br />, obtain Shift Operations Superintendent or designee approval of the compensatory actions and the plan for exiting the Operational Requirement

1.2.3. Exceptions

to this requirement are stated in the individual Operational Requirements.

Where corrective measures are completed that permit operation in accordance with the Operational Requirement or ACTIONS, comp letion of the actions required by this requirement is not required.

This requirement is only applicable in MODES 1, 2, and 3.

1.2.4 When an Operational Requirement is not met, entry into a MODE or other specified condition in the Applicability shall only be made:

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

b. After performance of a risk assessment addressing inoperable systems and components, consideration of the results, determination of the acceptability of entering the MODE or other specified condition in the Applicability, and

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 5 Rev. 67 October 2009

1.2 GENERAL

OPERATIONAL REQUIREMENTS (Cont'd) establishment of risk management actions, if appropriate; exceptions to this requirement are stated in the indivi dual Operational Requirements, or

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

This requirement shall not prevent changes in MODES or other specified conditions in the Applicability that are required to comply with ACTIONS or that are part of a

shutdown of the unit.

1.2.5 Equipment

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

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 6 Rev. 67 October 2009 1.3 GENERAL TESTING REQUIREMENTS

1.3.1 Testing

Requirements shall be met duri ng the MODES or other sp ecified conditions in the Applicability for individual Operational Requirements, unless otherwise stated in the Testing Requirement. Failure to meet a Testing Requirement, whether such failure is experienced during the performance of the Testing Requirement or between performances of the Testing Requirement, shall be failure to meet the Operational Requirement. Failure to perform a Testing Requirement within the specified Frequency shall be failure to meet the Operational Requirement, except as provided in Testing Requirement 1.3.3. Testing Requirements do not have to be performed on inoperable equipment or variables outside specified limits.

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

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

If an ACTION requires periodic performance on a "once per ..." basis, the above Frequency extension applies to each performance after the in itial performance.

Exceptions to this Testing Requirement ar e stated in the individual Operational Requirements.

1.3.3 If it is discovered that a Testing Requirement was not performed within its specified Frequency, then compliance with the requirement to declare the Operational Requirement not met may be delayed, from the time of discovery, up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the specified Frequency, whiche ver is greater. This delay period is permitted to allow performance of the Testing Requirement. A risk evaluation shall be performed for any Testing Requirement delayed greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and the risk impact shall be managed.

If the Testing Requirement is not performed within the delay period, the Operational Requirement must immediately be declared not met, and the applicable ACTIONS must be entered.

When the Testing Requirement is performe d within the delay period and the Testing Requirement is not met, the Operational Requirement must immediately be declared not met, and the applicable ACTION(s) must be entered.

1.3.4 Entry

into a MODE or ot her specified condition in the Applicability of an Operational Requirement shall only be made when the Operational Requirement's Testing Requirements have been met within their sp ecified Frequency, except as provided by Operational Requirement 1.2.3. When an Operational Requirement is not met due to Testing Requirements not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with Operational Requirement 1.2.4.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 7 Rev. 67 October 2009 1.3 GENERAL TESTING REQUIREMENTS (Cont'd)

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.

1.3.5 Testing

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

a. Inservice inspection of ASME Code Class 1, 2, and 3 components and inservice testing of ASME Code Class 1, 2, and 3 pumps and valves shall be performed in accordance with Section XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda as required by 10 CFR 50, Section 50.55a(g), except where specific written relief has been grante d by the Commission pursuant to 10 CFR 50, Section 50.55a(g)(6)(i).

b. Surveillance intervals specified in Se ction XI of the ASME Boiler and Pressure Vessel Code and applicable Addenda for the inservice inspection and testing activities required by the ASME Boiler and Pressure Vessel Code and applicable Addenda shall be applicable as follows in the Operational Requirements:

ASME Boiler and Pressure Vessel Code and applicable Addenda terminology for inservice inspection and testing activities Required frequencies for performing inservice inspection and testing activities Weekly At least once per 7 days Monthly At least once per 31 days Quarterly or every 3 months At least once per 92 days Semiannually or every 6 months At least once per 184 days Every 9 months At least once per 276 days Yearly or annually At least once per 366 days

c. The provisions of Testing Requirement 1.3.2 are applicable to the above required frequencies for performing inservice inspection activities.

d. Performance of the above inservice insp ection and testing acti vities shall be in addition to other Technical Specification Surveillance Requirements and Operational Requirements Manual Testing Requirements.

e. Nothing in the ASME Boiler and Pressure Vessel Code shall be construed to supersede the requirements of any Operational Requirement.

f. The Inservice Inspection Program for pi ping identified in NRC Generic Letter 88-01 shall be performed in accordance with the NRC Staff positions on schedule except for Category 'D' welds, methods and personnel, and sample expansion

included in the generic letter.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 1 Page 8 Rev. 67 October 2009 1.3 GENERAL TESTING REQUIREMENTS (Cont'd)

For Category 'D' welds, BWR Owner's Group Vessel Internal Project (VIP) document BWRVIP-75 schedule shall be utilized.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 2.3 Page 1 Rev. 65 April 2009

2.3 REACTOR

COOLANT SYSTEMS

2.3.1 REACTOR

COOLANT SYSTEM CHEMISTRY OPERATIONAL REQUIREMENTS The chemistry of the reactor coolant system shall be maintained within the limits specified in the Table 3.3.1-1.

APPLICABILITY At all times.

ACTION 3.3.1.1 In MODE 1:

a. With the conductivity, chloride concentration, or pH exceeding the limit specified in Table 3.3.1-1 for less than 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> during one continuous time interval and, for conductivity and chloride concentration, for less than 336 hours0.00389 days <br />0.0933 hours <br />5.555556e-4 weeks <br />1.27848e-4 months <br /> per year, but with the conductivity less than 10 micro mho/cm at 25°C and with the chloride concentration less than 0.5 ppm, this need not be reported to the Commission and the provisions of Operational Requirement 1.2.4 are not applicable.

b. With the conductivity, chloride concentration, or pH exceeding the limit specified in Table 3.3.1-1 for more than 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br /> during one continuous time interval or with

the conductivity and chloride concentration exceeding the limit specified in Table 3.3.1-1, for more than 336 hours0.00389 days <br />0.0933 hours <br />5.555556e-4 weeks <br />1.27848e-4 months <br /> per year, be in at least MODE 2 within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />. c. With the conductivity exceeding 10 micro mho/cm at 25°C or chloride concentration exceeding 0.5 ppm, be in at least MODE 3 within 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> and in MODE 4 within the next 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

3.3.1.2 In MODES 2 and 3 with the conductivity , chloride concentration or pH exceeding the limit specified in Table 3.3.1-1 for more than 48 hours5.555556e-4 days <br />0.0133 hours <br />7.936508e-5 weeks <br />1.8264e-5 months <br /> during one continuous time interval, be in at least MODE 3 within th e next 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> and in MODE 4 within the following 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 2.3 Page 2 Rev. 65 April 2009

2.3.1 REACTOR

COOLANT SYSTEM CHEMISTRY (continued)

3.3.1.3 At all other times:

a. With the conductivity or pH exceeding the limit specified in Table 3.3.1-1, restore the conductivity and pH to within the limit within 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />, or perform an engineering evaluation to determine the effects of the out-of-limit condition on the structural integrity of the reactor coolant system. Determine that the structural integrity of the reactor coolant system remains acceptable for continued operation prior to proceeding to

MODE 3. b. With the chloride concentration exceeding the limit specified in Table 3.3.1-1 restore the chloride concentration to within the limit within 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />, or perform an engineering evaluation to determine the effects of the out-of-limit condition on the structural integrity of the reactor coolant system. Determine that the structural integrity of the reactor coolant system remains acceptable for continued operation prior to proceeding to MODE 3.

c. The provisions of Operational Requirement 1.2.3 are not applicable.

TESTING REQUIREMENTS 4.3.1.1 The reactor coolant conductivity and chlorides shall be determined to be within the specified chemistry limit by measurement prior to pressurizing the reactor during each reactor startup, if not performe d within the previous 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />.

4.3.1.2 Reactor coolant samples shall be analyzed for chlorides at least once per 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />, and every 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> whenever conductivity is greater than the limit in Table 3.3.1-1.

4.3.1.3 Reactor coolant samples shall be analyzed for conductivity at least once per 72 hours8.333333e-4 days <br />0.02 hours <br />1.190476e-4 weeks <br />2.7396e-5 months <br />.

4.3.1.4 Reactor coolant samples shall be analyzed for pH every 8 hours9.259259e-5 days <br />0.00222 hours <br />1.322751e-5 weeks <br />3.044e-6 months <br /> whenever conductivity is greater than the limit in Table 3.3.1-1.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM)

Section 2.3 Page 3 Rev. 65 April 2009

2.3.1 REACTOR

COOLANT SYSTEM CHEMISTRY (continued)

4.3.1.5 Reactor coolant conductivity shall be continuously recorded. If the continuous recording conductivity monitor is inoperable, obtain in-line conductivity measurements, or a dip sample from the fuel pool, every 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> in MODES 1, 2 and 3, and every 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> at all other times.

4.3.1.6 Perform a CHANNEL CHECK of the continuous conductivity monitor with an in-line flow cell every 7 days, and every 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> when the conductivity is greater than the limit in Table 3.3.1-1.

Table 3.3.1-1 REACTOR COOLANT SYSTEM CHEMISTRY LIMITS MODE CHLORIDES CONDUCTIVITY

(µmhos/cm @ 25°C) pH 1 < 0.2 ppm < 1.0 5.6 <

pH < 8.6 2 and 3 < 0.1 ppm < 2.0 5.6 <

pH < 8.6 At all other times < 0.5 ppm < 10.0 5.3 <

pH < 8.6 BASES 5.3.1 The water chemistry limits of the reactor coolant system are established to prevent damage to the reactor materials in contact with the coolant. Chloride limits are specified to prevent stress corrosi on cracking of the stainless steel.

The effect of chloride is not as great when the oxygen concentration in the coolant is low, thus the 0.2 ppm limit on chlorides is permitted during POWER OPERATION.

During shutdown and refueling operations, the temperature necessary for stress corrosion to occur is not present so a 0.5 ppm concentration of chlorides is not considered harmful during these periods.

Conductivity measurements are required on a continuous basis since changes in this parameter are an indication of abnormal conditions. When the conductivity is within limits, the pH, chlorides and other impurities affecting conductivity must also be within their acceptable limits. With the conductivity meter inoperable, additional samples must be analyzed to ensure that the chlorides are not exceeding the limits.

The testing requirements provide adequate assurance that concentrations in excess of the limits will be detected in sufficient time to take corrective action.

During outage refueling with no available means to obtain an in-line conductivity measurement, dip sample conductivity may be obtained from the fuel pool when the reactor vessel head is removed and the reactor cavity is flooded.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 1 Rev. 42 September 2004

6.0 ADMINISTRATIVE

REQUIREMENTS

6.1 Administrative

Requirements are contained in Section 13.1.2.3 of the USAR for operating shift crews (USAR Change Package 8-215).

6.2 Not Used 6.3 Not Used

6.4 TRAINING

6.4.1 A retraining and replacement training program for the unit staff shall be maintained under the direction of the Director-Operations Training and shall meet or exceed the requirements of 10 CFR Part 55.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 2 Rev. 42 September 2004 6.5 REVIEW AND AUDIT

6.5.1 PLANT

OPERATIONS REVIEW COMMITTEE (PORC)

Refer to USAR Section 13.4.1, "Plant Operations Review Committee."

6.5.2 NUCLEAR

SAFETY REVIEW BOARD (NSRB)

Refer to Updated Safety Analysis Report section 13.4.2, Nuclear Safety Review Board.

6.5.3 TECHNICAL

REVIEW AND CONTROL

ACTIVITIES

Procedures required by Technical Specification 5.4.1 and ORM 6.8 and other procedures which affect plant nuclear safety as determined by the Manager-Clinton Power Station or the responsible manager* and changes thereto, other than editorial or typographical changes, shall be reviewed as follows:

6.5.3.1 TECHNICAL REVIEW a. Each such procedure or procedure change shall be independently reviewed by an individual knowledgeable in the area affected other than the individual who prepared the procedure, or procedure change. The applicable Department Head/Designee shall approve all plant procedures and changes thereto, prior to implementation. b. Individuals responsible for reviews performed in accordance with Item 6.5.3.1.a above shall be designated by the Manager-Clinton Power Station or the responsible manager*. Each such review shall include a determination of whether or not additional, cross-disciplinary, review is necessary. If deemed necessary, such review shall be performed by the review personnel of the appropriate discipline. Individuals performing these reviews shall meet or exceed the qua lifications stated in ANSI/ANS 3.1-1978 for the appropriate discipline. c. When a review pursuant to 10 CFR 50.59 is required, it shall be included in the procedure or the procedure change review. Pursuant to 10 CFR 50.59, NRC approval of items requiring NRC review shall be obtained prior to the Manager-Clinton Power Station approval for implementation. d. Written records of reviews performed in accordance with Item 6.5.3.1.a above, including recommendations for approval or disapproval, shall be prepared and maintained.

[*The responsible manager must be the equivalent of the Manager - Clinton Power Station with respect to his/her level of responsibility within corporate structure.]

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 3 Rev. 42 September 2004

6.6 REPORTABLE

EVENT ACTION 6.6.1 The following actions shall be taken fo r any of those conditions identified in 10CFR50.73:

a. The Commission shall be notified and a report submitted pursuant to the requirements of 10CFR50.73, and

b. The reportable event shall be reviewed by the PORC.

c. The report shall be submitted to the NSRB and the CPS Site Vice President.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 4 Rev. 42 September 2004

6.7 SAFETY

LIMIT VIOLATION 6.7.1 The following actions shall be taken in the event a Safety Limit is violated:

a. The CPS Site Vice President, Manager-Clinton Power Station, and the NSRB shall be notified within 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

b. The Safety Limit Violation Report shall be reviewed by the PORC. This report shall describe: (1) applicable circumstances preceding the violation, (2) effects of the violation upon unit components, systems, or structures, and (3) corrective action taken to prevent recurrence.

c. The Safety Limit Violation Report shall be submitted to the CPS Site Vice President, Manager-Clinton Power Station, and the NSRB within 30 days of the violation.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 5 Rev. 42 September 2004

6.8 PROCEDURES

AND PROGRAMS

PROCEDURES

6.8.1 Written

procedures shall be established, implemented, and maintained covering the activities referenced below: a. Refueling operations;

b. Surveillance and test activities of safety-related equipment; c. Security Plan implementation;

d. Emergency Plan implementation;

e. Fire Protection Program implementation;

f. Process Control Program implementation; and

g. Offsite Dose Calculation Manual implementation.

REVIEW AND APPROVAL 6.8.2 Each procedure of Technical Specification 5.4.1 and Operational Requirement 6.8.1 and changes thereto, shall be reviewed in accordance with Updated Safety Analysis Report section 13.4.1 and Operational Requirement 6.

5.3 as applicable and shall be approved by the applicable Department Head/Designee prior to implementation and reviewed periodically as set forth in administrative procedures.

TEMPORARY CHANGES

6.8.3 Temporary

changes to procedures of Technical Specification 5.4.1 and Operational Requirement 6.8.1 may be made provided:

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

b. The change is approved by two members of the unit management staff, at least one of whom holds a Senior Operator license on the unit affected; and

c. The change is documented, reviewed in accordance with Updated Safety Analysis Report section 13.4.1 and Operational Requirement 6.5.3 as appropriate, and approved by the applicable Department Head/Designee w ithin 14 days of implementation.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 6 Rev. 42 September 2004

6.8 PROCEDURES

AND PROGRAMS (continued)

6.8.4 The following programs shall be established, implemented, and maintained:

a. In-Plant Radiation Monitoring A program which will ensure the capability to accurately determine the airborne iodine concentration in vital areas under accident conditions. This program shall include the following:

1. Training of personnel,

2. Procedures for monitoring, and

3. Provisions for maintenance of sampling and analysis equipment.

b. Fire Protection Program A program to implement and maintain in effect all provisions of the approved fire protection program as described in the Updated Safety Analysis Report as amended, and as approved in the Safety Evaluation Report (NUREG-0853) dated February 1982 as supplemented. Noncompliance with the above Fire Protection Systems described in plant procedure CC-AA-211 shall be reported in accordance with Operational Requirement 6.6.1.

c. Radiological Environmental Monitoring Program A program shall be provided to monitor the radiation and radionuclides in the environs of the plant. The program shall provide (1) representative measurements of radioactivity in the highest potential exposure pathways, and (2) verification of the accuracy of the effluent monitoring program and modeling of environmental exposure pathways. The program shall (1) be contained in the ODCM, (2) conform to the guidance of Appendix I to 10 CFR Part 50, and (3) include the following:

1. Monitoring, sampling, analysis, and re porting of radiation and radionuclides in the environment in accordance with the methodology and parameters in the

ODCM; 2. A Land Use Census to ensure that changes in the use of areas at and beyond the SITE BOUNDARY are identified and that modifications to the monitoring program are made if required by the results of this census; and 3. Participation in an Interlaboratory Comparison Program to ensure that independent checks on the precision and accuracy of the measurements of radioactive materials in environmental sample matrices are performed as part of the quality assurance program for environmental monitoring.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 7 Rev. 42 September 2004

6.9 REPORTING

REQUIREMENTS

STARTUP REPORT 6.9.1.1 Summary report of plant startup and power escalation testing shall be submitted following (1) receipt of an Operating License, (2) amendment to the license involving a planned increase in power level, (3) installation of fuel that has a different design or has been manufactured by a different fuel supplier, and (4) modifications that may have significantly altered the nuclear, thermal, or hydraulic performance of the unit.

6.9.1.2 The startup report shall address each of the tests identified in the Updated Safety Analysis Report and shall include a description of the measured values of the operating conditions or characteristics ob tained during the test program and a comparison of these values with design predictions and specifications. Any corrective actions that were required to obtain satisfactory operation sh all also be describe

d. Any additional specific details required in license conditions based on other commitments shall be included in this report.

6.9.1.3 Startup reports shall be submitted within (1) 90 days following completion of the startup test program, (2) 90 days following resumption or commencement of commercial power operation, or (3) 9 months following initial criticality, whichever is earliest. If the startup report does not cover all three events (i.e., initial criticality, completion of startup test program, and resumption or commencement of commercial operation) supplementary reports shall be submitted at least every 3 months until all three events have been completed.

OTHER REPORTS 6.9.2 If an individual emergency diesel generator (EDG) experiences four or more valid failures in the last 25 demands, these failures and any non-valid failures experienced by that EDG in that time period shall be reported to the Commission within 30 days.

Reports of diesel generator failures shall include the information recommended in Regulatory Position C.3.b of Regulatory Guide 1.108, Revision 1, August 1977.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) Section 6 Page 8 Rev. 42 September 2004 6.10 RECORD RETENTION Record retention requirements are contained in the Exelon Standard Records Retention Schedule (SRRS).

6.11 RADIATION PROTECTION PROGRAM 6.11.1 Procedures for personnel radiation protection shall be prepared consistent with the requirements of 10 CFR Part 20 and shall be approved, maintained, and adhered to for all operations involving personnel radiation exposure.

6.12 Not Used 6.13 PROCESS CONTROL PROGRAM (PCP)

The Process Control Program shall contain the current formula, sampling, analyses, tests, and determinations to be made to ensure that the processing and packaging of solid radioactive wastes based on demonstrated processing of actual or simulated wet solid wastes will be accomplished in such a way as to assure compliance with 10 CFR Part 20, 10 CFR Part 61, 10 CFR Part 71 and Fe deral and State regulations, burial ground requirements and other requirements governing the disposal of the radioactive waste.

Changes to the PCP:

a. Shall be documented and records of reviews performed shall be retained as required by the Exelon Standard Record Retention Schedule.

This documentation shall contain:

1. Sufficient information to support the change together with the appropriate analyses or evaluations ju stifying the change(s), and

2. A determination that the change will maintain the overall conformance of the solidified waste product to existing requirements of Federal, State, or other applicable regulations.

b. Shall become effective after review and acceptance by the PORC and the approval of the Manager - Clinton Power Station.

CPS OPERATIONAL REQUIREMENTS MANUAL (ORM) SECONDARY CONTAINMENT ISOLATION VALVES Attachment 6 Page 1 Rev. 42 September 2004

Automatic Dampers

Damper Description 1VF06Y Fuel Building Supply Inboard Isolation Damper 1VF07Y Fuel Building Exhaust Inboard Isolation Damper 1VF04Y Fuel Building Supply Outboard Isolation Damper 1VF09Y Fuel Building Exhaust Outboard Isolation Damper

Manual Dampers Damper Description 0VG03YA Standby Gas Treatment System Train "A" Control Building Inlet Damper 0VG03YB Standby Gas Treatment System Train "B" Control Building Inlet Damper