ML22240A008
| ML22240A008 | |
| Person / Time | |
|---|---|
| Issue date: | 06/24/2015 |
| From: | NRC/NRR/DSS/STSB |
| To: | |
| Craig Harbuck NRR/DSS 301-415-3140 | |
| Shared Package | |
| ML22240A001 | List:
|
| References | |
| Download: ML22240A008 (18) | |
Text
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 1 Advanced Passive 1000 (AP1000)
Generic Technical Specification Traveler (GTST)
Title:
Revision of AP1000 GTS Section 1.2, Logical Connectors I.
Technical Specifications Task Force (TSTF) Travelers, Approved Since Revision 2 of STS NUREG-1431, and Used to Develop this GTST TSTF Number and
Title:
Not Applicable NRC Approval Date:
Not Applicable TSTF Classification:
Not Applicable
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 2 II.
Reference Combined License (RCOL) Standard Departures (Std. Dep.), RCOL COL Items, and RCOL Plant-Specific Technical Specifications (PTS) Changes Used to Develop this GTST RCOL Std. Dep. Number and
Title:
None RCOL COL Item Number and
Title:
None RCOL PTS Change Number and
Title:
None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 3 III.
Comments on Relations Among TSTFs, RCOL Std. Dep., RCOL COL Items, and RCOL PTS Changes This section discusses the considered changes that are: (1) applicable to operating reactor designs, but not to the AP1000 design; (2) already incorporated in the GTS; or (3) superseded by another change.
None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 4 IV.
Additional Changes Proposed as Part of this GTST (modifications proposed by NRC staff and/or clear editorial changes or deviations identified by preparer of GTST)
None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 5 V.
Applicability Affected Generic Technical Specifications and Bases:
Section 1.2, Logical Connectors Changes to the Generic Technical Specifications and Bases:
None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 6 VI.
Traveler Information Description of TSTF changes:
None Rationale for TSTF changes:
Not Applicable Description of changes in RCOL Std. Dep., RCOL COL Item(s), and RCOL PTS Changes:
None Rationale for changes in RCOL Std. Dep., RCOL COL Item(s), and RCOL PTS Changes:
Not Applicable Description of additional changes proposed by NRC staff/preparer of GTST:
None Rationale for additional changes proposed by NRC staff/preparer of GTST:
Not Applicable
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 7 VII. GTST Safety Evaluation Technical Analysis:
None References to Previous NRC Safety Evaluation Reports (SERs):
None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 8 VIII. Review Information Evaluator Comments:
None E. Danial Doss Argonne National Laboratory 630-252-5967 doss@anl.gov Review Information:
Availability for public review and comment on Revision 0 of this traveler approved by NRC staff on 5/1/2014.
NRC Final Approval Date: 8/31/2015 NRC
Contact:
C. Craig Harbuck 301-415-3140 Craig.Harbuck@nrc.gov
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 9 IX.
Evaluator Comments for Consideration in Finalizing Technical Specifications and Bases None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 10 X.
References Used in GTST None
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 11 XI.
MARKUP of the Applicable GTS Subsection for Preparation of the STS NUREG The entire section of the Specifications and the Bases associated with this GTST is presented next.
Changes to the Specifications and Bases are denoted as follows: Deleted portions are marked in strikethrough red font, and inserted portions in bold blue font.
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-1 Amendment 0Rev. 0 Revision 19 Date report generated:
Wednesday, June 24, 2015 Page 12 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.
Logical connectors are used in Technical Specifications to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in Technical Specifications are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meaning.
BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action).
The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.
When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.
EXAMPLES The following examples illustrate the use of logical connectors.
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-2 Amendment 0Rev. 0 Revision 19 Date report generated:
Wednesday, June 24, 2015 Page 13 1.2 Logical Connectors In this example, the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.
EXAMPLES (continued)
EXAMPLE 1.2-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.
A.1 Verify...
AND A.2 Restore...
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-3 Amendment 0Rev. 0 Revision 19 Date report generated:
Wednesday, June 24, 2015 Page 14 1.2 Logical Connectors This example represents a more complicated use of logical connectors.
Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.
EXAMPLES (continued)
EXAMPLE 1.2-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.
A.1 Trip...
OR A.2.1 Verify...
AND A.2.2.1 Reduce...
OR A.2.2.2 Perform...
OR A.3 Align...
GTST AP1000-A12-1.2, Rev. 1 Date report generated:
Wednesday, June 24, 2015 Page 15 XII. Applicable STS Subsection After Incorporation of this GTSTs Modifications The entire subsection of the Specifications and the Bases associated with this GTST, following incorporation of the modifications, is presented next.
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-1 Rev. 0 Date report generated:
Wednesday, June 24, 2015 Page 16 1.0 USE AND APPLICATION 1.2 Logical Connectors PURPOSE The purpose of this section is to explain the meaning of logical connectors.
Logical connectors are used in Technical Specifications to discriminate between, and yet connect, discrete Conditions, Required Actions, Completion Times, Surveillances, and Frequencies. The only logical connectors that appear in Technical Specifications are AND and OR. The physical arrangement of these connectors constitutes logical conventions with specific meaning.
BACKGROUND Several levels of logic may be used to state Required Actions. These levels are identified by the placement (or nesting) of the logical connectors and the number assigned to each Required Action. The first level of logic is identified by the first digit of the number assigned to a Required Action and the placement of the logical connector in the first level of nesting (i.e., left justified with the number of the Required Action).
The successive levels of logic are identified by additional digits of the Required Action number and by successive indentions of the logical connectors.
When logical connectors are used to state a Condition, Completion Time, Surveillance, or Frequency, only the first level of logic is used, and the logical connector is left justified with the statement of the Condition, Completion Time, Surveillance, or Frequency.
EXAMPLES The following examples illustrate the use of logical connectors.
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-2 Rev. 0 Date report generated:
Wednesday, June 24, 2015 Page 17 1.2 Logical Connectors In this example, the logical connector AND is used to indicate that when in Condition A, both Required Actions A.1 and A.2 must be completed.
EXAMPLES (continued)
EXAMPLE 1.2-1 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.
A.1 Verify...
AND A.2 Restore...
GTST AP1000-A12-1.2, Rev. 1 AP1000 STS 1.2-3 Rev. 0 Date report generated:
Wednesday, June 24, 2015 Page 18 1.2 Logical Connectors This example represents a more complicated use of logical connectors.
Required Actions A.1, A.2, and A.3 are alternative choices, only one of which must be performed as indicated by the use of the logical connector OR and the left justified placement. Any one of these three Actions may be chosen. If A.2 is chosen, then both A.2.1 and A.2.2 must be performed as indicated by the logical connector AND. Required Action A.2.2 is met by performing A.2.2.1 or A.2.2.2. The indented position of the logical connector OR indicates that A.2.2.1 and A.2.2.2 are alternative choices, only one of which must be performed.
EXAMPLES (continued)
EXAMPLE 1.2-2 ACTIONS CONDITION REQUIRED ACTION COMPLETION TIME A. LCO not met.
A.1 Trip...
OR A.2.1 Verify...
AND A.2.2.1 Reduce...
OR A.2.2.2 Perform...
OR A.3 Align...