Technical Specification Introduction Flashcards
Where do the Technical Specifications come from?
The USAR chapter 16
What are the five major chapters contained within the Technical Specifications?
- Use and Application
- Safety Limits
- Specifications
- Design Features
- Administrative Controls
What is the definition of SAFETY LIMITS?
SAFETY LIMITS for nuclear reactors are limits upon important process variables which are found to be necessary to reasonably protect the integrity of certain physical barriers which guard against the uncontrolled release of radioactivity.
What is the definition of Limiting Conditions for Operation?
Limiting Conditions for Operation are the lowest functional capability or performance levels of equipment required for safe operation of the plant.
What are Surveillance Requirements?
Surveillance Requirements are requirements relating to test, calibration, or inspection to assure that the necessary quality of systems and components is maintained, that facility operation will be within the Safety Limits, and that the LCOs will be met.
What is an Active LCO?
A situation in which the requirements of the LCO are not met for the present mode or condition. The Action statement is entered and the Tech Spec Actions are performed within the specified Completion Time.
What is a Potential LCO?
A situation in which the requirements of the LCO statement are not met; however, the plant is not in the mode or condition applicable to that LCO statement. The Action statement is not entered. A Potential LCO could become and Active LCO after a mode change or a could even prevent a planned mode or condition change.
What is indicated by a term in the Technical Specifications that appears in capitalized type?
That term is in the Definitions section of Tech Specs.
What is the definition of ACTIONS?
ACTIONS shall be that part of a Specification that prescribes Required Actions to be taken under designated Conditions within Specified Completion Times.
What is the definition of MODE?
A MODE shall correspond to any one inclusive combination of mode switch position, average reactor coolant temperature, and reactor vessel head closure bolt tensioning specified in Table 1.1-1 with fuel in the reactor vessel.
What is the definition of OPERABLE-OPERABILITY?
A system, subsystem, division, component, or device shall be OPERABLE or have OPERABILITY when it is capable of performing it’s specified safety function(s) and when all necessary attendant instrumentation, controls, normal or emergency electrical power, cooling and seal water, lubrication, and other auxiliary equipment that are required for the system, subsystem, division, component, or device to perform it’s specified safety function(s) are also capable of performing their related safety function(s).
What are the MODE 1 requirements per Table 1.1-1?
MODE 1:
- Title - Power Operation
- Reactor Mode Switch Position - Run
- Average Reactor Coolant Temperature - N/A
What are the MODE 2 requirements per Table 1.1-1?
MODE 2:
- Title - Startup
- Reactor Mode Switch Position - Refuel* or Startup/Hot Standby
- Average Reactor Coolant Temperature - N/A
- All reactor vessel head bolts are fully tensioned.
What are the MODE 3 requirements per table 1.1-1?
MODE 3:
- Title - Hot Shutdown*
- Reactor Mode Switch Position - Shutdown
- Average Reactor Coolant Temperature - Greater than 200F
- All reactor vessel head closure bolts are fully tensioned.
What are the MODE 4 requirements per Table 1.1-1?
MODE 4:
- Title - Cold Shutdown*
- Reactor Mode Switch Position - Shutdown
- Average Reactor Coolant Temperature - Less than or equal to 200F
- All reactor vessel head closure bolts are fully tensioned.
What are the MODE 5 requirements per table 1.1-1?
MODE 5:
- Title - Refuel*
- Reactor Mode Switch Position - Shutdown or Refuel
- Average Reactor Coolant Temperature - N/A
*One or more reactor vessel head closure bolts less than fully tensioned.
What is the purpose of the Logical Connectors, and what two are used?
The purpose of the Logical Connectors is to discriminate between, yet connect, items in the ACTIONS and Surveillance Requirements.
The only two Logical Connectors used are:
1. AND(underlined)
2. OR(underlined)
When does the Completion Time begin?
Completion time begins when the SRO has determined that the LCO is not met(discovery of a situation) and an ACTIONS Condition is entered, unless otherwise specified.
When can an ACTIONS Condition be exited?
- When the condition no longer exists
- When the LCO is no longer applicable.
How are multiple occurrences of inoperability handled for the same Condition?
Once a Condition has been entered subsequent divisions, subsystems, etc, discovered inoperable will NOT result in separate entry into the same condition unless you have the NOTE!!
What are the requirements to extend the completion time of a given Required Action when subsequent inoperability occurs?
- The subsequent inoperability must exist concurrent with he first inoperability.
AND - The subsequent inoperability must remain inoperable after the first one is resolved.
What is total time allowed for completion of Required Actions in accordance with the Completion Time extension?
The total Completion Time allowed for completing the Required Actions is the more restrictive of:
- The total Completion Time as measured from the initial entry of that Condition plus an additional 24 hours,
OR
- The stated Completion Time as measured from the subsequent inoperability.
When is the Required Action Completion Time extension not allowed?
Extensions do NOT apply;
- Separate re-entry is allowed for subsequent inoperabilities ,
OR
- A completion time with a modified “time zero”
What are the requirements for LCO 3.0.1?
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, LCO 3.0.7, and LCO 3.0.8.
What are the requirements of LCO 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 LCO 3.0.6.
If the LCO 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.
What are the requirements of LCO 3.0.3?
When an LCO 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 LCO is not applicable. Action shall be initiated within 1 hour to place the unit, as applicable, in:
A. MODE 2 within 7 hours;
B. MODE 3 within 13 hours; and
C. MODE 4 within 37 hours.
Exceptions to this Specification are stated in the individual Specifications.
What is required if LCO 3.0.3 was entered and measures are completed that permits operation in accordance with the LCO or ACTIONS?
Completion of the Actions required by LCO 3.0.3 is not required.
When is LCO 3.0.3 applicable?
LCO 3.0.3 is only applicable in MODES 1, 2, and 3.
What are the requirements of LCO 3.0.4?
LCO 3.0.4: When an LCO 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. 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 establishment of risk management actions, if appropriate (exceptions to this Specification are stated in the individual Specifications); or
C. When allowance is stated in the individual value, parameter, or other Specification.
What is important to remember with MODE restrictions in relation to LCO 3.0.4?
LCO 3.0.4 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.
What are the requirements of LCO 3.0.5?
LCO 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.
What are the requirements of LCO 3.0.6?
LCO 3.0.6: When a supported system LCO is not met solely due to a support system LCO no 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, an evaluation shall be performed 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 LCO 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 LCO 3.0.2.
What are the requirements of LCO 3.0.7?
LCO 3.0.7: Special Operations LCOs in Section 3.10 allow specified Technical Specifications (TS) requirements to be changed to permit performance of special tests and operations. Unless otherwise specified, all other TS requirements remain unchanged. Compliance with Special Operations LCOs is optional. When a Special Operations LCO is desired to be met but is not met, the ACTIONS of the Special Operations LCO shall be met. When a Special Operations LCO is not desired to be met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with the other applicable Specifications.
What are the requirements of LCO 3.0.8?
LCO 3.0.8: When one or more snubbers are unable to perform their associated support function(s), any affected supported LCO(s) are not required to be declared not met solely for this reason if risk is assessed and managed, and:
A. The snubbers not able to perform their associated support function(s) are associated with only one division or subsystem of a multiple division subsystem supported system or are associated with a single division supported system and are able to perform their associated support function within 72 hours; or
B. The snubbers not able to perform their associated support function(s) are associated with more than one division or subsystem of a multiple division or subsystem supported system and are able to perform their associated support function within 12 hours.
At the end of the specified period the required snubbers must be able to perform their associated support function(s), or the affected supported system LCO(s) shall be declared not met.
What are the requirements of SR 3.0.1?
SR 3.0.1: SRs shall be met during the MODES or other specified conditions in the Applicability for individual LCOs, unless otherwise stated in the SR. Failure to meet a Surveillance, whether such failure is experienced during the performance of the Surveillance or between performances of the Surveillance, shall be failure to meet the LCO. Failure to perform a Surveillance within the specified Frequency shall be failure to meet the LCO except as provided in SR 3.0.3. Surveillances do not have to be performed on inoperable equipment or variables outside specified limits.
What are the requirements of SR 3.0.2?
SR 3.0.2: The specified Frequency for each SR is met if the Surveillance 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 the Frequencies specified as “once,” the above interval extension does not apply.
If a Completion Time requires periodic performance on a “once per…” basis, the above Frequency extension applies to each performance after the initial performance.
Exceptions to this Specification are stated in the individual Specifications.
What are the requirements of SR 3.0.3?
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 hours or up to the limit of the specified Frequency, whichever is greater. This delay period is permitted to allow performance of the Surveillance. The delay period is only applicable when there is a reasonable expectation the surveillance will be met when performed. A risk evaluation shall be performed for any Surveillance delayed greater than 24 hours and the risk impact shall be managed.
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.
What are the requirements of SR 3.0.4?
SR 3.0.4: Entry into a MODE or other specified condition in the Applicability of and LCO shall only be made when the LCO’s Surveillances have been met within their specified Frequency, except as provided by SR 3.0.3. When an LCO is not met due to Surveillances not having been met, entry into a MODE or other specified condition in the Applicability shall only be made in accordance with LCO 3.0.4.
This provision shall not prevent entry 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.
What is important to remember with MODE restrictions in relation to SR 3.0.4?
This provision shall not prevent entry 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.
