ML20056F368

From kanterella
Jump to navigation Jump to search
Proposed Tech Specs Adopting Provision of STS Which Allows Period of 24 H to Complete SR Upon Discovery That SR Missed
ML20056F368
Person / Time
Site: Crane Constellation icon.png
Issue date: 08/24/1993
From:
GENERAL PUBLIC UTILITIES CORP.
To:
Shared Package
ML20056F362 List:
References
NUDOCS 9308270042
Download: ML20056F368 (5)


Text

,

4.

SVRVEILLANCE STANDARDS 4.0.1 During Reactor Operational Conditions for which a Limiting Condition for Operation (LCO) does not require a l

system / component to be operable, the associated surveillance requirements do not have to be performed.

Prior to declaring a system / component operable, the associated surveillance requirement must be current.

Failure to perform a surveillance within the specified Frequency shall be failure to meet the LCO except as provided in 4.0.2.

4.0.2 If it is discovered that a surveillance was not performed i

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 <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> or up to the limit of the i

specified frequency, whichever is less. This delay period is permitted to allow performance of the Surveillance.

a Bases This specification establishes the flexibility to defer declaring affected equipment inoperable or an affected variable outside the specified limits when a surveillance has not been completed within the specified frequency. A delay period of up to 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> applies from the point in time that it is discovered that the required surveillance has not been performed and not at the time that the specified 4

frequency was not met.

4

]

The delay period provides an adequate time to complete surveillances i

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 l

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 i

discovered not to have been performe' when specified, this provision allows the full delay period of 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> to perform the surveillance.

Failure to comply with specified surveillance frequencies is expected i

to be an infrequent occurrence. Use of the delay period is not intended to be used as an operational convenience to extend surveillance intervals.

4 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 LCO conditions begin I

9308270042 930824 9

4_I PDR ADOCK 05000289 1

i P

PDR Lj Amendment No, f%, pp, Jpp, Jgf, J)$

l I

Bases (Contd.)

immediately upon expiration of the delay period.

If a surveillance is j

failed within the delay period, then the equipment is inoperable, or i

the variable is outside the specified limits and the completion times of the required actions for the applicable LCO conditions begin i

immediately upon 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.

i l

1 l

l

)

4-la 4

i 4.1 OPERATIONAL SAFETY REVIEW i

Applicability Applies to items directly related to safety limits and limiting conditions for operation.

1 Ob.iective To specify the minimum frequency and type of surveillance to be applied to unit equipment and conditions.

Snecification 4.1.1 The minimum frequency and type of surveillance required for reactor protection system, engineered safety fasture protection system, and heat sink protection system instrumentation when the reactor is critical shall be as stated in Table 4.1-1.

4.1.2 Equipment and sampling test shall be performed as detailed in Tables 4.1-2 and 4.1-3.

4.1.3 Each post accident monitoring instrumentation channel shall be demonstrated OPERABLE by the performance of the check, test and calibration at the frequencies shown in Table 4.1-4.

Bases Check Failures such as blown instrument fuses, defective indicators, or faulted amplifiers which result in " upscale" or "downscale" indication can be easily recognized by simple observation of the functioning of an instrument or system. Furthermore, such failures are, in many cases, revealed by alarm or annunciator action. Comparison of output and/or state of independent channels measuring the same variable l

supplements this type of built-in surveillance.

Based on experience in operatio,' of both conventional and nuclear systems, when the unit is in operation, the minimum checking frequency stated is deemed adequate for reactor system instrumentation.

The 600 ppab limit in Item 4, Table 4.1-3 is used to meet the requiremats of Section 5.4.

Under other circumstances the minimum acceptable boron concentration would have been zero ppmb.

J i

Calibration Calibration shall be performed to assure the presentation and acquisition of accurate information. The nuclear flux (power range) channels amplifiers shall be checked and calibrated if necessary, every shift against a heat balance standard. The frequency of heat balance checks will assure that the difference between the out-of-core instrumentation and the heat balance remains less than 4%.

l 4-2 Amendment No. /S, JU, D S, J M, 5 7, U S

i I

Bases (Contd.)

i Channels subject only to " drift" errors induced within the instrumentation itself can tolerate longer intervals between calibrations.

Process system instrumentation errors induced by drift can be expected to remain within acceptance tolerances if j

recalibration is performed at the intervals of each refueling period.

]

Substantial calibration shifts within a channel (essentially a channel failure) will be revealed during routine checking and testing

)

procedures.

i Thus, minimum calibration frequencies set forth are considered acceptable.

Testin_g On-line testing of reactor protection channels is required monthly on a rotational basis. The rotation scheme is designed to reduce the probability of an undetected failure existing within the system and to minimize the likelihood of the same systematic test errors being introduced into each redundant channel (Reference 1).

The rotation schedule for the reactor protection channels is as follows.

l a) Channels A, B, C & D Before Startup, when shutdown greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br /> and b) Monthly with one channel being tested per week on a continuous l

sequential rotation.

The reactor protection system instrumentation test cycle is continued with one channel's instrumentation tested each week. Upon detection

)

of a failure that prevents trip action in a channel, the instrumentation associated with the protection parameter failure will be tested in the remaining channels.

If actuation of a safety channel occurs, assurance will be required that actuation wn within the limiting safety system setting.

The protection channels coincidence logic, the control rod drive trip breakers and the. regulating control rod power SCRs electronic trips, are trip tested monthly. The trip test checks all logic combinations and is to be performed on a rotational basis. The logic and breakers of the four protection channels and the regulating control rod power SCRs shall be trip tested prior to startup when the reactor has been i

shutdown for greater than 24 hours2.777778e-4 days <br />0.00667 hours <br />3.968254e-5 weeks <br />9.132e-6 months <br />.

Discovery of a failure that prevents trip action requires the_ testing of the instrumentation associated with the protection parameter failure in the remaining channels.

For purposes of surveillance, reactor trip on loss of feedwater and reactor trip on turbine trip are considered reactor protection system channels.

4-2a Amendment No. 75, J57

l I

Bases (Contd.)

The equipment testing and system sampling frequencies specified in Table 4.1-2 and Table 4.1-3 are considered adequate to maintain the equipment and systems in a safe operational status.

REFERENCE l

(1) UFSAR, Section 7.1.2.3(d)

" Periodic Testing and Reliability" i

r i

i i

4-2b

.