ML15086A186: Difference between revisions
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
StriderTol (talk | contribs) (Created page by program invented by StriderTol) |
||
| (4 intermediate revisions by the same user not shown) | |||
| Line 17: | Line 17: | ||
=Text= | =Text= | ||
{{#Wiki_filter:3/4 0-1 AMENDMENT NO. 91 | {{#Wiki_filter:3/4 0-1 AMENDMENT NO. 91 (DRN 04-1191, Am. 91) 3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS | ||
3.0.2 Noncompliance with a specification shall exist when the requirements of the LCO and/or associated ACTION requirements are not met within the specified time intervals. If the LCO is restored prior to expiration of the specified time intervals, completion of the ACTION requirements is not required. | |||
3.0.3 When a LCO is not met and the associated ACTIONs are not met, or an associated ACTION is not provided, or if directed by the associated ACTIONs, communicate the condition to the General Manager-Plant Operations or his designee (e.g. duty plant manager) as soon as practicable, but no later than 7 hours; and initiate a condition report to document the condition, and determine any limitations for continued operation of the plant. Exceptions to this LCO are stated in the individual requirements. LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4. | 3/4.0 APPLICABILITY | ||
3.0.4 Entry into an OPERATIONAL MODE or other specified condition in the Applicability shall not be made when the conditions for a LCO are not met AND the corrective action process has determined that limitations should be placed on continued plant operation in the desired OPERATIONAL MODE to be entered. Entry into an OPERATIONAL MODE or other specified condition may be made in accordance with ACTION requirements when the ACTION or the corrective action process has determined that no limitations should be placed on continued plant operation in the desired MODE to be entered. This provision shall not prevent changes in OPERATIONAL MODES or other specified conditions in the Applicability that are required to comply with ACTION requirements or that are part of a shutdown of the plant. Exceptions to this LCO are stated in the individual requirements. | |||
3.0.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 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 to demonstrate OPERABILITY. | LIMITING CONDITION FOR OPERATION (LCO) | ||
Surveillances do not have to be performed on inoperable equipment or variables outside specified limits. | |||
4.0.2 Each SR shall be performed within its specified surveillance interval with a maximum allowable extension not to exceed twenty-five percent (25%) of the specified surveillance interval. | 3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding specifications is required during the OPERATIONAL MODES or other conditions specified therein; except that upon failure to meet the LCO, the associated ACTION requirements shall | ||
4.0.3 If it is discovered that a SR was not performed within its specified interval then compliance with the requirement to declare the LCO not met may be delayed, from the time of the discovery, up to 24 hours or up to the limit of the specified surveillance interval, whichever is greater. This delay period is permitted to allow performance of the SR. A risk evaluation shall be performed for any SR delayed greater than 24 hours and the risk impact shall be managed. | |||
If the SR is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered. | be met. | ||
When the SR is performed within the delay period and the SR is not met, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered. | 3.0.2 Noncompliance with a specification shall exist when the requirements of the LCO and/or associated ACTION requirements are not met within the specified time intervals. If the LCO is restored prior to expiration of the specified time intervals, completion of the ACTION | ||
4.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made unless the SR(s) associated with the LCO have been performed within the stated surveillance interval or as otherwise specified. This provision will not prevent passage through or to OPERATIONAL MODES as required to comply with ACTION requirements. (DRN 04-1191, Am. 91)}} | |||
requirements is not required. | |||
3.0.3 When a LCO is not met and the associated ACTIONs are not met, or an associated ACTION is not provided, or if directed by the associated ACTIONs, communicate the condition to the General Manager-Plant Operations or his designee (e.g. duty plant manager) as soon as practicable, but no later than 7 hours; and initiate a condition report to document the | |||
condition, and determine any limitations for continued operation of the plant. Exceptions to this LCO are stated in the individual requirements. LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4. | |||
3.0.4 Entry into an OPERATIONAL MODE or other specified condition in the Applicability shall not be made when the conditions for a LCO are not met AND the corrective action process has determined that limitations should be placed on continued plant operation in the desired OPERATIONAL MODE to be entered. Entry into an OPERATIONAL MODE or other specified condition may be made in accordance with ACTION requirements when the ACTION or the corrective action process has determined that no limitations should be placed on continued plant operation in the desired MODE to be entered. This provision shall not prevent changes in OPERATIONAL MODES or other specified conditions in the Applicability that are required to comply with ACTION requirements or that are part of a shutdown of the plant. Exceptions to this LCO are stated in the individual requirements. | |||
3.0.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 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 to demonstrate OPERABILITY. | |||
(DRN 04-1191, Am. 91) 3/4 0-2 AMENDMENT NO. 91 (DRN 04-1191, Am. 91) | |||
APPLICABILITY | |||
SURVEILLANCE REQUIREMENTS (SR) | |||
4.0.1 Surveillance Requirements shall be met during the OPERATIONAL MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a SR, whether such failure is experienced during the performance of the SR or between performances of the SR, shall be failure to meet the LCO. Failure to perform a SR within the specified interval shall be failure to meet the LCO except as provided in 4.0.3. | |||
Surveillances do not have to be performed on inoperable equipment or variables outside | |||
specified limits. | |||
4.0.2 Each SR shall be performed within its specified surveillance interval with a maximum allowable extension not to exceed twenty-five percent (25%) of the specified surveillance | |||
interval. | |||
4.0.3 If it is discovered that a SR was not performed within its specified interval then compliance with the requirement to declare the LCO not met may be delayed, from the time of the discovery, up to 24 hours or up to the limit of the specified surveillance interval, whichever is greater. This delay period is permitted to allow performance of the SR. A risk evaluation | |||
shall be performed for any SR delayed greater than 24 hours and the risk impact shall be | |||
managed. | |||
If the SR is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered. | |||
When the SR is performed within the delay period and the SR is not met, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered. | |||
4.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made unless the SR(s) associated with the LCO have been performed within the stated surveillance interval or as otherwise specified. This provision will not prevent passage through or to | |||
OPERATIONAL MODES as required to comply with ACTION requirements. (DRN 04-1191, Am. 91)}} | |||
Latest revision as of 14:40, 7 May 2019
| ML15086A186 | |
| Person / Time | |
|---|---|
| Site: | Waterford  |
| Issue date: | 03/10/2015 |
| From: | Entergy Operations |
| To: | Office of Nuclear Reactor Regulation |
| Shared Package | |
| ML15086A176 | List: |
| References | |
| W3F1-2015-0023 | |
| Download: ML15086A186 (2) | |
Text
3/4 0-1 AMENDMENT NO. 91 (DRN 04-1191, Am. 91) 3/4 LIMITING CONDITIONS FOR OPERATION AND SURVEILLANCE REQUIREMENTS
3/4.0 APPLICABILITY
LIMITING CONDITION FOR OPERATION (LCO)
3.0.1 Compliance with the Limiting Conditions for Operation contained in the succeeding specifications is required during the OPERATIONAL MODES or other conditions specified therein; except that upon failure to meet the LCO, the associated ACTION requirements shall
be met.
3.0.2 Noncompliance with a specification shall exist when the requirements of the LCO and/or associated ACTION requirements are not met within the specified time intervals. If the LCO is restored prior to expiration of the specified time intervals, completion of the ACTION
requirements is not required.
3.0.3 When a LCO is not met and the associated ACTIONs are not met, or an associated ACTION is not provided, or if directed by the associated ACTIONs, communicate the condition to the General Manager-Plant Operations or his designee (e.g. duty plant manager) as soon as practicable, but no later than 7 hours8.101852e-5 days <br />0.00194 hours <br />1.157407e-5 weeks <br />2.6635e-6 months <br />; and initiate a condition report to document the
condition, and determine any limitations for continued operation of the plant. Exceptions to this LCO are stated in the individual requirements. LCO 3.0.3 is only applicable in MODES 1, 2, 3, and 4.
3.0.4 Entry into an OPERATIONAL MODE or other specified condition in the Applicability shall not be made when the conditions for a LCO are not met AND the corrective action process has determined that limitations should be placed on continued plant operation in the desired OPERATIONAL MODE to be entered. Entry into an OPERATIONAL MODE or other specified condition may be made in accordance with ACTION requirements when the ACTION or the corrective action process has determined that no limitations should be placed on continued plant operation in the desired MODE to be entered. This provision shall not prevent changes in OPERATIONAL MODES or other specified conditions in the Applicability that are required to comply with ACTION requirements or that are part of a shutdown of the plant. Exceptions to this LCO are stated in the individual requirements.
3.0.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 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 to demonstrate OPERABILITY.
(DRN 04-1191, Am. 91) 3/4 0-2 AMENDMENT NO. 91 (DRN 04-1191, Am. 91)
APPLICABILITY
SURVEILLANCE REQUIREMENTS (SR)
4.0.1 Surveillance Requirements shall be met during the OPERATIONAL MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a SR, whether such failure is experienced during the performance of the SR or between performances of the SR, shall be failure to meet the LCO. Failure to perform a SR within the specified interval shall be failure to meet the LCO except as provided in 4.0.3.
Surveillances do not have to be performed on inoperable equipment or variables outside
specified limits.
4.0.2 Each SR shall be performed within its specified surveillance interval with a maximum allowable extension not to exceed twenty-five percent (25%) of the specified surveillance
interval.
4.0.3 If it is discovered that a SR was not performed within its specified interval then compliance with the requirement to declare the LCO not met may be delayed, from the time of the 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 surveillance interval, whichever is greater. This delay period is permitted to allow performance of the SR. A risk evaluation
shall be performed for any SR 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 SR is not performed within the delay period, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered.
When the SR is performed within the delay period and the SR is not met, the LCO must immediately be declared not met, and the applicable ACTION(s) must be entered.
4.0.4 Entry into an OPERATIONAL MODE or other specified condition shall not be made unless the SR(s) associated with the LCO have been performed within the stated surveillance interval or as otherwise specified. This provision will not prevent passage through or to
OPERATIONAL MODES as required to comply with ACTION requirements. (DRN 04-1191, Am. 91)