ML20205F911: Difference between revisions

From kanterella
Jump to navigation Jump to search
(StriderTol Bot change)
(StriderTol Bot change)
 
Line 13: Line 13:
| document type = CORRESPONDENCE-LETTERS, INCOMING CORRESPONDENCE, UTILITY TO NRC
| document type = CORRESPONDENCE-LETTERS, INCOMING CORRESPONDENCE, UTILITY TO NRC
| page count = 2
| page count = 2
| project = TAC:56816
| stage = Withdrawal
}}
}}



Latest revision as of 22:38, 6 December 2021

Withdraws Requested Change D.14.b of License Change Application 117 for License NPF-1 Re Reactor Protection Sys Instrumentation.Revised Page 15 Reflecting Withdrawal of Proposed Change Encl
ML20205F911
Person / Time
Site: Trojan File:Portland General Electric icon.png
Issue date: 03/23/1987
From: Cockfield D
PORTLAND GENERAL ELECTRIC CO.
To:
NRC OFFICE OF INFORMATION RESOURCES MANAGEMENT (IRM)
References
TAC-56816, NUDOCS 8703310329
Download: ML20205F911 (2)


Text

a 0

M M M W David W. Cockfield Vice President. Nuclear March 23, 1987 Trojan Nuclear Plant Docket 50-344 License NPF-1 U.S. Nucicar Regulatory Commission ATTN: Document Control Desk Washington DC 20555

Dear Sir:

TROJAN NUCLEAR PLANT License Chango Application 117 Reactor Protection System Instrumentation Pursuant to discussions with Mr. Terence Chan of your staff, wo have decided to withdraw requested chango D.14.b of License Change Application 117. This proposed chango to the Trojan Technical Specifications would have revised ACTION Statement 3 of Table 3.3-1, Reactor Trip System Instrumentation. A revised Page 15 of 42 to reflect the withdrawal of the proposed chango is attached.

Sinceregy, l

Attachment ct Mr. John B. Martin

! Regional Administrator, Region V U.S. Nuclear Regulatory Commission Mr. David Kish, Action Director Stato of Oregon Department of Energy Mr. R. C. Barr NRC Resident Inspector Trojan Nuclear Plant 6

e\

0703310329 070323 PDR ADOCK 05000344 ,

i \ \

P PDR l

VI ! , gi) fli ' t I, P, ' j' h. j f I't ' )

's l((')d i

e LCA 117, Rev. 2 Attachment 1

, Page 15 of 42 TABLE 3.3-1 (Continued)

ACTION 3 - With the number of channels OPERABLE one less than the l Minimum Channels OPERABLE requirement and with the THERMAL POWER level:

a. Below P-6, restore the inoperable channel to OPERABLE status prior to increasing THERMAL POWER above the P-6 setpoint.
b. Above P-6 but below 5% of RATED THERMAL POWER, restore the inoperable channel to OPERABLE status prior to increasing THERMAL POWER above 5% of RATED THERMAL POWER.
c. Above 5% of RATED THERMAL POWER, power operation may continue.

ACTION 4 - With the number of OPERABLE channels one less than the Mini-mum Channels OPERABLE requirement, suspend all operations involving positive reactivity changes.

ACTION 5 - With the number of channels OPERABLE one less than the Mini-mum Channels OPERABLE requirement, verify compliance with the SHUTDOWN MARGIN requirements of Specification 3.1.1.1 within l 1 hour1.157407e-5 days <br />2.777778e-4 hours <br />1.653439e-6 weeks <br />3.805e-7 months <br /> and at least once per 12 hours1.388889e-4 days <br />0.00333 hours <br />1.984127e-5 weeks <br />4.566e-6 months <br /> thereaf ter.

ACTION 6 - With the number of OPERABLE channels one less than the Total Number of Channels, STARTUP and/or POWER OPERATION may pro-ceed provided both of the following conditions are satisfied:

a. The inoperable channel is placed in the tripped condition within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />,
b. The Minimum Channels OPERABLE requirement is met; how-ever, the inoperable channel may be bypassed for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> for surveillance testing of other channels per Specification 4.3.1.1.

ACTION 7 - With the number of OPERABLE channels less than the Total Number of Channels, place the inoperable channel in the tripped condition within 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />. Operation may continue until performance of the next required CHANNEL FUNCTIONAL TEST.

ACTION 8 - With a channel associated with an operating loop inoperable, restore the inoperable channel to OPERABLE status within 2 hours2.314815e-5 days <br />5.555556e-4 hours <br />3.306878e-6 weeks <br />7.61e-7 months <br /> or be in at least HOT STANDBY within the next 6 hours6.944444e-5 days <br />0.00167 hours <br />9.920635e-6 weeks <br />2.283e-6 months <br />.

One channel associated with an operating loop may be bypassed for up to 4 hours4.62963e-5 days <br />0.00111 hours <br />6.613757e-6 weeks <br />1.522e-6 months <br /> for surveillance testing per Specification 4.3.1.1.

TROJAN-UNIT 1 3/4 3-6 Amendment No. 33,