ML20205E679
| ML20205E679 | |
| Person / Time | |
|---|---|
| Site: | Oyster Creek, Three Mile Island, 05000000 |
| Issue date: | 09/13/1985 |
| From: | Flynn J GENERAL PUBLIC UTILITIES CORP. |
| To: | |
| Shared Package | |
| ML20205E603 | List: |
| References | |
| FOIA-86-293 5000-ADM-7313.0, NUDOCS 8608180466 | |
| Download: ML20205E679 (28) | |
Text
=, .
- TECHNICAL FUNCTIONS Number N'uclear
> civisioN s000-4Dri-7313.0 -
(EP-005)
Title Revision No.
MODIFICATION AND SYSTEM DESIGN DESCRIPTIONS 1-01
^"
- N d!$$Yeal Functions Division hk*S5110 l
This document is irnportant to safety C YesgNo Effactive Date 9-13-85 List of Effective Pages Page Revision Page Revision
- 1.0 -
1-01 14.0 1-00 2.0 1-00 15.0 1-00 3.0 1-00 16.0 1-00 4.0 1-00 17.0 1-00 5.0 1-00 18.0 1-01 6.0 1-00 19.0 1-00 7.0 1-00 20.0 1-00 8.0 1-00 El-1 1-00 9.0 1-00 E2-1 1-00 10.0 1-00 E3-1 1-00 11.0 1-00 E4-1 1-00 12.0 1-00 E4-2 1-00 13.0 1-00 E5-1 1-00 Signature Concurnng Organizational Element Date Onginator ll yd [/ 1 ,_ Engrg. Proc. & Stds, itanager 5['q/7 Concurred byl
[ '
hl Director-Eneineering & nesign bb 6 l l /s/ l Director Engineering pen 4 pere 5/15/85 ll Mdad-- I Director systeme en ginaaring I f*/3' il 't i I k i j l l l l !
. II I i l I I
! lI x 1 l !
! 11 J \ ! I f Approved Oy l \ l Vice-Pres - Technical Functions $\g7 l \
1.0 '000'est 3.s
, 8608100466 860807 b' $5s 93 PDR
[ /[
r .
DOCUMENT NO.
NucIear soo0-40s_73i3.ai TITLE Mndification and System Desian Descriotions REV
SUMMARY
OF CHANGE APM10 VAL DATE
/ l-0C Change title to " Modification and System Design Descriptions". Made appropriate '
b- Ik8[
' text changes to accommodate title change. 3 f"2; f,
Allows for Functional Engineering Director 1C to approve. Added Exhibit 5. ,
ig%
1-01 Minor change in Section 4.13.2 page 18.0 to remove the PEDR chairman from the minimum g- m 2h[if revised MOD and SDD review requirement.
Also changes approval of DIV I revision by RTR to concurrence, Section 4.13.5, page 18.0.
~
5 i
I_
Aooooose iz es lb
DOCUMENT NO.
NUCI48r 5000-AoM-73ia.0i Tnts Hodification and System Design Descriptions
~
REV
SUMMARY
OF CHANGE ApppoyAL DATE ORIGINAL ISSUE DATE: 12/22/78 THE FOLLOWING SUMMARIES WERE TRANSFERRED FROM THE OLD TECH. FUNCTIONS COVER PAGE:
3 This revision supersedes all previous proce-dures issued with the number EP-005.
Revisions "0" through "2" pertain to the previously issued EP-005, System Design Descriptions and are to be disregarded.
(6/1/81) 4 Sections 4.1.1, 4.1.2.1, 4.1.3, 4.2.1.1 and Appendix C (500 Numbering System) changed for clarification. Section 4.2.1.5.1 added ALARA requirements. Sections 1.0, 4.3.1, 4.4.8, 4.5, 4.6.2 contain other minor changes. Sections 4.6.2, 4.1.6 and 4.4.5 added to include Plant concurrence in 500 Div. I. (11/20/81) 5 Rearranged logic order, renumbering, and rewording of Sections 4.0 and 5.0 for clarification. Sections 1.0, 2.0 and 3.2 contain othec minor changes. Sections 3.2, 4.1.8, 4.4, 4.6.1 added to address plant modification training. Minor change to Appendix 8 - Summary of Change. (9/30/82) 6 Added requirement to consider Appendix R.
10-CFR-50, in Section 4.1.3. Added QA to list in Para. 4.2.1.3 for ITS documents.
(2/15/83) 7 Deletes operability and maintainability con-currence requirement for 500 I. Adds Appendix 0 to reflect the correct role of human factors in SDD preparation. Clarifles the requirements for 500 I and Preliminary 500 II. (8/1/83)
. 08 Converted from old Tech. Functions format to new corporate format; and added requirements i for Security Department review of 500 I for 2 certain modifications. (1/1/84) 1 7 09 This minor revision deletes reference to PO-002 obsolete flow chart. (12/21/84) l 1
1& A000003412 83
TECHNICAL FUNCTIONS Number NEINE DIVISION 5000-Adit-7313.01 Title Revision No. 'Ubb ffodification and System Design Descriptions 1-00 1.0 PURPOSE & SCOPE 1.1 This procedure establishes methods for the preparation, review, and approval of Modification Desi System Design Descriptions (SDDs)gn Descriptions and revisions (MDD's), or new to existing System Design Descriptions'.
1.2 SDDs issued prior to the effective date of this revision do not need to be retrofited to meet the requirements of this revision.
2.0 REFEREilCES 2.1 5000-ADif-1215.02 " Technical Document Release" (EftP-008) l 2.2 5000-Adit-7311.03 " Project Review" (E!4P-014) 2.3 5000-Adit-7350.03 " Field Questionnaire / Change Request / Change l
, tiotice/ Design Change tiotice" (EliP-015) 2.4 5000-ADif-7370.03 " Control Evaluation and Resolution of Review Connents on Technical Documents" (EP-008) l 2.5 ES-011 "!!ethodology F. Content of GPUt!-Quality i Classification List" 2.5 ES-317 " Identification of GPUtl Power Plant Systems" l' 2.7 10-CFR-50, Appendix R - " Fire Protection Program for fluclear Power Facilities Operating Prior to Jan. 1, 1979" l
f 2.8 Site Security Plan 2.9 1000-PLii-7200.01 "GPUllC Operational Quality Assurance Plan" l
! 3.0 DEFitlITI0t15 I :
l '
3.1 Systen Design Descriptions (SDDs) - The system descriptions are comprehensive technical documents that define the design, opera-tion, and naintenance and testing requirenents of physical i systems found in GPUtlC nuclear plants.
4:
!! flote: There was a period of time that SDD's were used to 7I describe nodifications to a systen, therefore any SDD
-; dated prior to the effective date of Rev. 1-00 of this
"; procedure may only describe a portion of the systen.
!' 3.2 ffodification Design Descriptions (ftDDs) - A document which describes changes to system configuration and arrangement within the plant and provides test and operational requirenents for use in the preparation of detailed and test operating procedures.
~
ACC01050t1 8 2 .0
Number i TECHNICAL FUNCTloNS Nucl ear oivisioN So00.AD,,.7313.01 ,
ten me t )
~~~' '
Title Revision No'.~
l Itodification and Systen Design Descriptions 1-00 3.3 Refer to " Glossary of Terms" used in Technical Functions Procedures.
4.0 PROCEDURE REQUIREf1ENTS 4.1 !!DDs consists of two parts and are used for describing modifica-tions and new construction requirements.
4.1.1 -Division I defines the criteria and is prepared during I the conceptual phase of design.
4.1.2 Division II documents the actual design and is prepared during the detail design phase. A preliminary version of ifDD II is required for the Preliminary Engineering Design Review. (Ref. 5000-Adit-7311.03 [EltP 014]) This version also provides information to the Training departments for lesson plan development and/or revision.
4.2 SDD's have under a single cover the elenents described above for the f100 Div's I & II. They are system oriented and intended for use by naintenance and operations purposes by Technical Functions and the Plant. flot many such documents currently exist for GPUtlC plants except as described in the note of section 3.1. flo criteria has been established for determining when a SDD must be prepared except for situations when nodifications address completely new systens in total. SDD's are then prepared.
4.3 The requironent for either a DIV I or DIV II can only be waived by a Director from the organization responsible for the activ-ity. Decisions on waivers shall consider how design criteria are to be documented. Uaivers shall be documented by a memo to file in ED&CC.
4.4 DIV I and II cocbined nust provide sufficient source or back-ground information from which operation and maintenance training naterials can be generated.
4.5 ftDDs am. SDDs shall contain a cover sheet as shown in Exhibit 2.
4.5.1 Cover sheets shall be carked "If1PORTAtlT TO SAFETY," and "flVCLEAR SAFETY RELATED" when applicable.
5
- 4.5.2 In conjunction with developing As-Built drawings, itDD's
- er SDD's shall be revised as necessary, narked "AS-BUILT"
- on the cover and released as "As-Built" (Ref.
5 5000-Adit-1215.02 [E!!P-008]). Unapproved ftDD's and SDD's, O routed for connent only, shall be narked " DRAFT."
i A000105011 3.0
TECHNICAL FUNCTIONS Number
[ R1 Nuclear Dty1380N 5000-Adit-7313.01 tre_ Anti
% Revision Nol' '
Itodificat-ion and System Design Descriptions 1-00 I
4.6 itDD and SDD numbers shall be assigned in ac:ordance with Exhibit !
-3.- An index of the issued numbers shall be maintained by Engineering Data & Configuration Control (ED&CC). The appro-priate system number shall be selected from ES-017, 4.6.1 Each !!DD related to one systen shall be assigned a letter identifier in alphabetical sequence. Only one SDD may exist for any one system.
4.6.2 Uhen more than one system is 19volved the engineer shall designate the most logical as the primary system and select that system number to number documents.
4.7 A Surrary of Change page (Exhibit 2) shall be inserted directly following the cover sheet and numbered as described in paragraph 4 .13 .1. All other pages subsequent to the Summary of Change pages shall be on plain bond paper and consecutively numbered beginning with "Page 2 of "
Additionally the following i information shall appear at the top of each page including attachments:
l f100/SDD !! umber Rev # Date Page of l l
4.8 ftDD I - Criteria for Use 4.8.1 A flodification Design Description I is a required docu- 1, l ment for a plant modification governed by Technical Func-l tion procedures (see Paragraph 4.3 regarding waivers). !
It is prepared during the conceptual phase of a modifica-tion. The DIV I plus a preliminary DIV II provides an i early description of the modification, for use by reviewers, in assessing the extent of change, the viability of the design, etc., and shall be completed and issued prior to start of construction. DIV I and a preliminary version of the DIV II shall be included as part of the documents for the Preliminary Engineering Design Review (PEDR) (Ref. 5000-Adit-7311.03 [Ei!P-014]).
l In cases where an 500 for the entire systen has been previously issued, the i1DD I and Preliminary ?!DD II may I be used to update the system SDD at the completion of the g modification.
)
- l 4.3.2 Section 4.9 describes the format for a DIV I and provides guidance regarding content. The minimum format require-1 j} ments are fixed. Additional topics nay be added and the 2l order can be changed to suit the author. ftedifications g or new systems that do not include all elements of the i
e A000tOSO11.t 4.0
TECHNICAL FUNCT13NS Number NUIUI DIVISIIN 5000-ADt!-7313.0~
~'0C <
Title Revision No.
ffodification and System Design Descriptions 1-00 format shall contain "Nct Applicable" statements after the section heading. Anytime a statement "Not appli-cable" is included a parallel statement explaining, the basis for this determination should be included. Section 4.11 describes the preliminary version a DIV II.
4.E.3 As a minimum, the review scope for DIV I's and II's shall l include the ffanager Engineering Projects (ifEP). Systems
. Engineering, Engineering & Design, Radiological & Envi-ronmental Control, Licensing, Startup & Test, Maintenance
& Construction, and the respective piant appointed reviewing authority. Engineering & Design (E&D) review should include sections with responsibility for the systen involved and sections with functional responsibil-ities addressed in the document. I
- These reviews shall be accomplished via a PEDR for DIV I.
I l
i
- The !!anager-Security, or a designee, shall be included in the review cycle for modificatfons affecting the l Plant Security Plan.
,
- QA review shall be obtained for documents as required in the 0QA Plan. The review is as addressed in the GPUt:C 0QA plan for appropriate coverage of prior commitments, codes and standards etc.
4.8.4 liDD's and SDD's prepared by an AE shall identify the AE i
organization and be signed by the AE in the preparer and concurrence blocks. The concurrence being by an equiva-1ent of a GPUliC Section flanager, l
4.8.5 Approvals shall be by a GPUt1C MEP, their delegate, a Functional Engineering Director or their delegate depend-ing on whether Projects or Engineering & Design has responsibility for the task.
4.8.6 Training l Where a f!DD may otherwise not be required, it may be gi required for training purposes. This determination is 1 made by the appropriate flanager. The waiver requirenents il of paragraph 4.3 shall apply.
El
" 4.9 DIV I: Text and Content
!! 4.9.1 The DIV I shall define the design criteria. For nodifi- l 3 cations, these criteria should satisfy and be compatible j with the original design criteria. Deviations fron A00010$0tt-5.0
TECHNICAL FUNCTIONS Number Nuclear OlVISION 5000-ADf t-7313.01
~'
Title Revision No.' ~
Itodification and System Design Descriptions 1-00 existing approved criteria must be high11ghted. The j technical basis for the specific requirements shall be included.
An outline of a DIY I is presented below: I
/ PURPOSE & SCOPE REFERENCES FUflCTI0flS DESIGft REQUIREffEflTS PROCESS REQUIREffEflTS (OR OPERATI0flAL REQUIREf tEllTS)
STRUCTURAL REQUIREftEflTS C0flFIGURATION AND ESSENTIAL FEATURES I ftAINTErlANCE SURVEILLANCE AND IN-SERVICE INSPECTI0ft INSTRUf1EflTATION Afl0 CONTROL INTERFACING SYSTEl15 TESTING REQUIREftEflTS QUALITY ASSURANCE SAFETY, HEALTH, AND SECURITY REQUIREffENTS ,
LICENSIrlG Afl0 REGULATORY REQUIREftENTS HUltAN FACTORS 4.9.2 PURPOSE & SCOPE - For itDD's this should be a clear con-
. cise description of: (1) lihat problem this modification l will solve; (2) !! hat the modification is; (3) What the i scope and/or boundary is - What is not included? This section is to be presented in narrative style usually one to two paragraphs. It should not state functions or design requirements.
i .9.3 P,EFEREflCES - A list of references should be provided.
! References cited in the text of the i1DD/SDD nust be l listed as a Reference. Itens should not be listed if not
! cited and shouldn't be cited if they are not listed.
Repeating reference information in the document shall be limited to information required for clarification pur-i poses. Examples of the type of reference one could l expect in a DIV I include but are not limited by the a following: Associated / supporting 11DD's and SDD's, the I Final Safety Analysis Report (FSAR)/ technical specifica-5 tion applicable sections, Safe Shutdown Logic Diagram
( :j (SSLD), Safety Sequence Diagram (SSD), Safety Auxiliary 5 Diagram (SAD), codes, standards and their applicable 2;: dates, regulations and other documents that are related il to the design criteria.
E'
~
A00010$011 t
.- 5.0
TECHNICAL FUNCTIONS Number Nuclear DIVISIO]
5000-A{t-M301
~'
g ' Revision No
- ifodification and System Design Descriptions 1-00 4.9.4 FUllCTIONS - A concise list (or diagram) of functions the system or modification will provide. Answers the ques-tion
- What will this system / modification do? Do not mix in design requirements.
4.9.5 DESIGN REQUIREffEllTS - The subsections which follow ident-ify the specific functional and design requirements to be I satisfied by the system. These criteria should be in accordance with the overall plant technical requirements. I
- The technical or licensing bases for each requirement I must be stated unless it is clearly obvious. In many cases the basis for the requirement can be deferred by specifically referencing a source document such as a Technical Data Report, Code, Standard, SAR or a related if00 or 500. In case of lengthy documents such as the SAR or the ASifE R&PV code or standard a specific section or paragraph should be referenced.
- The information given should be specific, definitive, and concise; generalizations and platitudes are not appropriate (e.g., that the system is to be "reifable" I
or " safe"). These requirements should be presented as l
" punchy" statements (all "shall, should, may" state-ments). They must be a complete set of design criteria l ,
but should not be repetitive. The following subsec-
' tions (e.g. a-1) shall be included. The order of these subsections may be changed and other subsections may be added to completely characterize a particular system /
modification.
I Appendix R 10-CFR-50 (Sections IIIG, IIIJ & IIIO) l must_be considered. If the design impacts fire j safety the design must satisfy Appendix R requirements. If the design does not impact Appendix R, this fact must be stated.
Environmental qualification requirements shall be addressed in this section, n fl0TE: Without documentation of the technical basis, it I is impossible to fulfill the requirement of ANSI fl45.2.11 R to which the GPUN Operational 0A Plan commits compli-j ance. ANSI requires that the design documentation 3; include a record of the source of design inputs. For 21 future nodifications the design engineer nust know the 3l complete basis for the previous design.
v i
1 A000105011 1 7.0
Number TECHNICAL PUNCT10NS MNuclear DNISION 5000-ADM-M M.01 gg Revision No.
l ftodification a d System Design Descriptions 1-00
~ . .
l a! PROCESS REQUIREffErlTS (OR OPERATI0flAL REQUIREffEtlTS) l Address both steady-state and transient requirements i as well as the reason / logic for the requirement. l This should include items such as thermal power rating, operating temperatures and pressures, expected chemistry conditions, required operating modes, requirements associated with unique functions of the system, and reliability requirements, b) STRUCTURAL REQUIREftEllTS - Include such design requirements / logic as design pressure and tempera-ture, design thermal transients, seismic design requirements, load combinations, design for natural phenomena such as wind loads, basic materials for construction, etc., design thermal transient curves, or seismic response spectra. Specific values generally should be included in the DIV II, but may I be included here for continuity, (e.g., design thermal transient curves or seismic response spectra). If st*uctural requirements are included in the DIV I, then the DIV II should normally reference the specific paragraph of the DIV I and not repeat data.
I
- Interference criteria must be considered especially for designs where seismic criteria is involved.
i i c) C0f1FIGURATI0fl Al10 ESSErlTIAL FEATURES - Include I i
requirements for any unique features, arrangements, I
constraints, etc., that physically characterize the system configuration and its location.
i d) 'tAIrlTEtlAf1CE - Include itens such as access and space i
requirements for hands-on maintenance, shielding requirenents, routine preventive maintenance and other specific provisions for maintenance.
e) SURVEILLAflCE Afl0 Ift-SERVICE IftSPECTI0fl - ISI/fl0E I mandated requirements include items such as required access provisions, periodic inspection requirements, a
monitoring instrumentation for specific components, etc.
F. !
-;
- ASf!E para XI and 10CFR50 APP. J test requirements
!! nust be identified if applicable.
21 I!
E' 9
A000 l C9011 8.0
- o. .
TECHNICAL FUNCTIONS Number Nuclear om. ION s000-AD,it-
, , ,M-,D.01
~'
g, Revision No" ftodification and System Design Descriptions 1-00 f) IftSTRUf!EllTATI0ll Afl0 C0flTROL - Include instrumentation and control requirements for system operation and control with identification of redundancy and cali-bration requirements, or constraints that apply.
Parameters to be monitored, recorded, annunciated, and controlled shall be identified.
- Specific performance factors for instrumentation must be included when a modification involves adding or changing instrumentation i.e.,
- Accuracy .
- Repeatability
- Drift g) IflTERFACING SYSTEllS - Include a list of interfacing systems and the interface requirements that such systems inpose, flew demands on services (e.g., scfn, gpm, amps) are important.
- Of particular concern are new power requirements.
Diesel Generator and/or Battery requirements.
h) TEST!flG REQUIRE!!EflTS - Cover tests required as initial systen proof tests to demonstrate that the nodification/ system functions as designed.
Include performance requirements and acceptance criteria when known i) QUALITY ASSURAtlCE - The systen shall be identified as l to whether it is important to Safety (ITS) and/or i
- lluclear Safety Related (flSR). Quality assurance requirements for design, construction, test, and operation on ITS systems shall be defined, fiodifica-tion classified as ITS shall refer to ES-011. QA requirenent
- of non-ITS nodifications nay be j specified as appropriate. Particular attention should be given to Appendix C of the QA plan (Ref.
2.9), flew systems or any other activity that n requires the ES-011 quality Classification List to I
be modified must be identified to the ffanager QCL/ Configuration Engineering and the Engineering
- Procedures and Standards fianager.
j) SAFETY, HEALTH Afl0 SECURITY REQUIREf'EtlTS - Specific requirenents for maintenance, safety, health, and il security should be identified. Environnental l I
4000100 tt.1 9.0
"caniceuscriou, Number ENuclear g,
Division 5000-Aort.73I3.01
~
Revmon No" ""
-I ftedification and System Design Descriptions 1-00 i
requirements should be identified in this section.
Requirements for satisfying applicable laws should be given.
- Safety hazards to plant personnel or the general public due to radioactivity in solutions or gases contained in tanks or being processed by the equip-ment shall be highlighted. ALARA requirements should be identified, flon-nuclear safety concerns shall also be addressed.
- Any impact on the Plant's Security Plan nust be identified, k) LICEtlS!!!G Afl0 REGULATORY REQUIREftEllTS - Identify licensing and regulatory requirements to be satisfied by new systems or modifications to existing systems.
- 1) HUMAfl FACTORS - Design requirements / criteria of the man-machine interfaces shall be provided to aid in the development of the system design.
- Human factors design requirement / criteria are associated with controls and displays, anthropo-metry, labeling and demarcation, and environmental
, factors. See Exhibit 4 for details and
- applicability.
4.10 Preliminary Version of DIV !! l 1
4 . 10 . 1 A preliminary version of the DIV !! is required for the i Preliminary Engineering Design Review (Ref.
5000-Adit-7311.03 (EPP-014]), and for training purposes.
I This document shall be signed off and issue: as Rev. O I after accepted by the PEDR. When a preliminary version of the DIY !! has been issued it means that either a completed DIV !! will be issued at a higher Rev nunber or the information will be incorporated into an existing i
overall systen 500. The preliminary version of the DIV
!! shall address the following, utilizing appropriate portions of the DIV !! format:
n
- A description of the modification including preliminary
?. baseline drawings.
~!
= ' How the modification affects plant and/or systen 2! performance.
Il 3
- How the operators and other personnel will interface j with the modification.
1 A0001090tt-10.0
~
o .
, 0 TECHNICAL FUNCTIONS Number Nuclear DIVWON 5000-AD,if-7313.0 T
Revision No." " #
itadification and System Design Descriptions 1-00
- General operating / maintenance / test guidelines (to the extent information is available) which can be used as the basis for preparing / modifying plant procedures.
4 .10.2 Prior to any release for construction, the Project
- Engineer (can be from the E&D Department) shall verify that the preifminary version of the DIY II is stili
- accurate, or shall see that the necessary changes are made and approved.
4.11 DIV II - Criteria For Use 1 4.11.1 A flodification Design Description DIV II is a comprehen-sive technical document that addresses the actual design I
of the system / modification; and, is prepared in accord-I ance with Section 4.12. This document shall be conpleted during the detail design phase and released prior to the
! startup and test phase. Changes to the DIV II identified i I
during the startup and test phase shall be documented in accordance with 5000-Adit-7350.03 (Eff-015). The changes I shall be incorporated into the DIV II as revisions once I the modification has been completed, l
, 4.11.2 If an 500 !! already exists in the format specified in this procedure for a system being modified, the existing document shall be updated as required upon completion of
- the modification. Where no SDD exists for the system, or
- is significantly different in format, the documents I i
i describing the system shall be recorded and filed by ED&CC, l
4.11.3 The DIV II review requirements are the same as DIV I (see Section 4.8.3) except that QA review is not required.
4 .12 DIV II: Text and Content g
4 .12 .1 DIY !! shall be a detailed description of the nodifica-tion or new system as finally designed and installed. It I i
should describe how the design criteria were net and con-tain references to pertinent engineering and procurement g documents. An outline of a DIY !! is presented below: l k DESIGft DESCRIPT!0fl g SUttttARY r REFEREllCES
- DETAILED SYSTEli DESCRIPTI0fl 11 SYSTEft PERFORftAtlCE CHARACTERISTICS 4'
SYSTEll ARRAtl3EffEtli
_1 .
A0001050t1 11.0
Numeer TECHNICAL FUNCTIONS Nuclear om.ON 5000-Adit-7313.01 Revision No." * #
flodification and System Design Descriptions 1-00 INSTRUffENTATION AND CONTROL SYSTEf1 INTERFACES LIftITATI0flS, SET POINTS, & PRECAUTIONS I OPERATIONS INITIAL FILL
/ STARTUP NORPML OPERATI0fl e . SHUTDOWN DRAINING REFILLING INFREQUENT OPERATI0fl TRANSIENT OPERATIONS CASUALTY EVENTS AND RECOVERY PROCEDURES CASUALTY EVENTS DESIGN FEATURES TO ftITIGATE EFFECTS OF CASUALTY EVENTS RECOVERY PROCEDURES fMINTENANCE APPROACH CORRECTIVE fMINTENANCE PREVENTIVE iMINTENANCE IN-SERVICE TESTING AND INSPECTION TESTIftG HUfMN FACTORS Items may be added to or deleted from this ifst as required by the nature of the system or modification. I e
- Wherever possible, the sections shall be kept in the i order shown.
4 . 12 .2 DESIGN DESCRIPTION - Contains a description of the systen or modification and its components, system arrangenents, I and system performance characteristics. For nodifica-l tions, the rationale for selecting the particular solu-tion to the problen shall also be addressed. Itens normally addressed in this section are described in more detail below. Information contained in the companion DIV I should not be repeated.
a) Sutt!%RY - Give a brief general description of the system or modification and its configuration. The a
- relationship of the systen or modification to the entire station should be included.
E b) REFERENCES - flaterial that is essential to present i the complete design but is not conveniently included
- in the text shall be referenced, but only if cited in 3 the document. Reference material should not be E
repeated in the document except as required for i
.A000105011 12.0
TECHNICAL FUNCTIONS Number Nuclear owisioN soo0-Aon-n ren nne, n.01
~'
Title Revision No."
itodification and System Design Descriptions 1-00 clarification purposes. Examples of material to be I <
referenced include system drawings, specifications '
and vendor manuals. I c) DETAILED SYSTEf1 DESCRIPTI0ft - The design description must be of sufficient detail to show how the design satisfies the functions and design requirements. It shall contain a detailed discussion of the modifica-tion / system and not simply be a verbal walk-through of the flow diagrams or single-line diagrams.
Studies that are required (such as single failure analysis), to confirm that the design requirements have been met should be referenced in this section.
The flow paths, for various operating modes shall be completely described. Operating and design data shall be included and reference made to the drawings needed to complete the design descristion. Specific design features can be included in t1e text or by tabulation and drawings. Description of the indi-vidual components shall be included in this section. I The design parameters and the principal design
, features of najor components (use tables, etc.) sha11
! be identified and component operation should be described. Simplified outline drawings (if abso-lutely necessary) of the components may be included in the text for improved understanding of the compon-
, ent design and operation. Detailed component draw-j ings may be included in the list of references.
d) . SYSTElf PERFORitAflCE CHARACTERISTICS - Provide systen performance characteristics under normal operating modes and off-normal operating conditions. For example, items included in this section for a heat
' transport system would be the head flow characteris-tic curves, natural circulation performance curves, system hydraulic profiles, etc. Calculations which :
demonstrate design performance shall be cited /
{
referenced as appropriate, l
e) SYSTEtt (or nodification) ARRAtlGEltElli - Include a description of the arrangement with reference to
- drawings. The piping arrangement and the location of ;
I operating stations should be described. Requirements R for access and any special provisions for maintenance
- access or inspection should be included.
2 i
j.
1 i ,
1 A0001050t1-13.0 l l
C 4 . 1 TECHNICAL FUNCTIONS Numbw I Nder om O. 5000-ADff-7313.011 I
Title Revision NoMF"UUD )
j flodification and System Design Descriptions 1-00 l
f) INSTRUltEllTATI0ff AflD C0flTROL (I&C) - Include a description of the instrumentation, control, and interlocks. The instrumentation description should I include the type, range, accuracy, set point, and location of sensor and instrument readouts, with appropriate reference to the flow diagram and logic diagram for all control systems (both manual & auto-matic). Characteristics such as drift and repeat-ability should be included (as appropriate) if not specified elsewhere. Readout and control location i should be clearly identified (e.g., in the control room or at specified local control stations). Com-ponent performance information should be provided when it will aid in understanding the system design, operation, and maintenance. Reference should be made to the instrumentation list which itemizes the instrument sensing elements, type, range, set point, whether indicating control or alarm, and readout location.
l g) SYSTEf1 IflTERFACES - Identify and describe interfaces I with other systems, and the functional and/or physi-l cal requirements inposed on each of the interfacing systems. Indicate how the design satisfies imposed I interface requirenents. Detailed lists of systen interfaces may be presented in tabular form and j included as an appendix.
4.12.3 LI!!ITATI0flS, SET POIt!TS, Afl0 PRECAUTIONS - Provide a con-l solidated list of limitations and precautions that will provide a better understanding of operation, response to casualties, and maintenance requirenents which are l described in later sections of the docunent. Under I
operating limits, include (in summary forn) suggested high and low linits for all controlled variables. The dead band and overshoot, for both manual and automatic control nay also be included. Appropriate limits such as relief valve settings, maximum liquid level, etc., should be identified.
g a) Identify precautions to be observed by operations and maintenance personnel. Interlocks and alarms should r, also be identified. Status checks needed for chang-ing set points should be defined. Use of tabular l lists may be included in an appendix.
L.
! 4.12.4 OPERATI0fl5 - This section shall provide details to con-j firm that the design provides for the required nodes of I
A000105011 14.0
a . .
TECHNICAL FUNCTIONS Number (UCIS8r DIVIS!2N 5000-ADtt-7313.01 Title Revision Nd *
!!odification and System Design Descriptions 1-00 operation. This section should be a sufficient basis I i for preparation of operating procedures. Each node of operation covered should be sufficient to clearly I identify the individual flow paths used, the instruments used to control these operations, and the proper sequence of operations. Typical modes of operation to be considered for a fluid systen are provided below; however, these may be aftered, and others that may be unique to a particular I codification or system should be added te provide complete coverage of the modes of operation for that particular system.
a) IflITIAL FILL - Cover the operations necessary to prepare and initially fill the system.
b) STARTUP - Cover the operations necessary to bring the system from startup to a normal operating condition.
c) fl0R!tAL OPERATI0fl - Cover the operation associated with r.ornal steady-state full-power, and i
reduced-power operation and design transient or naneuvering conditions. Operating condition envelopes showing the allowable operating ranges and
, appropriate linitations should be included.
i d) SliUTD0llf! - Cover the systen operation for shutdown, including shutdown to hot standby, hot shutdown and cold shutdoun as appropriate to the specific design requirenents, e) ORAltlI!!G - Cover operations for draining the entire
- fluid systen and portions of the systen. The end i !
condition of draining and constraints on operation I ! should be specified, f) REFILLIflG - Cover the steps for refilling a fully cr partially drained fluid system.
g) IflFREQUEllT OPERATI0flS - Cover those nodes of opera-
_ tion which are used infrequently or under unique conditions. This includes operation with certain components out of service or operation with certain I
support or interface systems in abnormal configurations.
E h) TRAflSIEflT OPERATI0flS - Cover the systen perfornance characteristics under transient conditions which are
{ expected to occur. The analysis necessary to confirn E
5
' AC00105011 l 15.0
TECHNICAL FUNCTIONS Numb:r NE, I DIVISIDN 5000-ADM-7313.01 Title Revision No flodification and System Design Descriptions 1-00 that system functional requirements will be main-tained shall be referenced. Some examples of transi-ents to be considered are foss of pumps, foss of level control, valve ma1 operations, and power supply transients.
4 .12 .5 CASUALTY EVENTS Af1D RECOVERY PROCEDURES - In the subsec-tions which follow identify the possible casualty events "that could affect the system and the protection provided against those casualties by the system design. Outline tr.e design features and recovery actions which will miti-gate the consequences of the casualties and restore the systen and plant to a known, confirmed safe condition.
a) CASUALTY EVEffTS - Identify casualty events which can be experienced by the system. Some examples of casualty events to be considered are:
(1) Loss of cooling I
(2) System leakage and ruptures (3) High radiation level
- (4) Fires and chemical reactions I
(5) Abnormal ficw (6) Abnormal chemistry
, (7) Unit trip (3) System component or control malfunctions (9) Loss of voltage I
i b) DESIGil FEATURES TO ftITIGATE EFFECTS OF CASUALTY I
EVE!!TS - Outline briefly design features which pro-I vide protection and mitigate the effects of the casualty events. The instrumentation and alarms and their location should be identified. Where appropri-
. ate, the resultant system performance characteristics and parameters under the casualty conditions should be provided. The intent is to describe how the
, system is protected from casualties.
i i c) RECOVERY PROCEDURES - Outline the recovery process to be performed by plant operating personnel to restore the system or plant to a known, safe condition, pre-g; vent propagation of and mitigate the effects of a casualty event, and assure personnel safety. The i specific instrument indications, alarms, or both 3 which signal the casualty event should be stated, and
=! the applicable recovery approach should be outlined.
9 '
[
E 5
~
- A000105011 -
16.0
TECHNICAL FUNCTIUNS Number MNu21 ear onnSi:n s000 40,,.,3,3.0, Title Revision No Itodification and System Design Descriptions 1-00 4.12.6 ftAINTENANCE APPROACH - This section shall define the maintenance philosophy; outline the design approach for corrective maintenance, preventive maintenance, and in-service testing and inspection; and identify inter-facing systems needed to support maintenance operations.
Provide the basis for preparation of maintenance proce-dures including recommended spare parts and applicable
' specifications, a) CORRECTIVE MAINTENANCE - Outline corrective mainten-ance requirements or replacement of individual system components. Identify those special tools and equip-ment needed to permit performance of the maintenance operation, maintenance system cleanliness, system test, and any other special requirements of the system. Include retesting of repairs. Cover main-tenance requirements for required modes of opera-tion. Define design requirements imposed on interfacing systems.
b) PREVENTIVE MAINTENANCE - Outline the preventive main-tenance approach for the system, and its major com-ponents. Inspection and/or periodic test programs j required to detect malfunctions shall be indicated, including consideration for storage and special handling.
I i
c) Iff-SERVICE INSPECTION AND TESTING (ISI/IST) - The conditions for performing inspections during opera-l tion or shutdown shall be defined. Design features,
! special equipment, and access requirements to accom-nodate in-service inspection shall be identified.
I
! 4 . 12 .7 TESTING - Define the testing philosophy and outline the j design approach used to assure proper testing; such as I
acceptance, functional, pre-operational, etc. Provide the basis for preparation of specific test specifications including sufficient detail to identify test scope, j method and provisions to perform testing. The "as built" DIV II shall include reference to the start-up and test 5
report and note significant findings.
4 .12 .3 HUttAN FACTORS - Human factors aspects of the man-machine 5 interfaces will be identified to aid in the understanding /
[l j maintenance of the system design. The studies, etc. of
-l Human Factors concerns shall be docunented in this sec-3 tion. Typical interface points that should be identified j ',I include: type, location, and arrangenent of controis and t
s' A000105011-17.0
Number ENuslear TECHNICAL FUNCTIONS oivisioN sooo_,DM_7313.o1
. . . . . ~
Title Revision NoP " #
Modification and System Design Descriptions 1-01 t
i displays, system Tabeling, system anthropology, alarm /
\ warning system logic, maintenance requirements, and procedural guidelines.
4.13 Revisions
/ 4.13.1 Revisions shall meet the requirements of this procedure and approvals shall be recorded on the "Sunnary of
<hange" page (Exhibit 2). See Exhibit 5 for guidance i
regarding QA review of changes. Revisions shall be identified by sequential numerical designation (i.e.,
Rev.1, Rev. 2, etc.). The initial issue of a SDD or MDD shall be marked "Rev 0." All revisions shall be ident-ified on the " Summary of Change" page and shall include page numbers and paragraphs which have been changed.
Include a list of pages by revision number on the sumary l
' page when the entire document is not revised e.g. a list of the " effective pages". The original (Rev 0) cover sheet with signature approvals shall be retained and oniy I
the revision number shall be changed to raffect the l latest revision. Summary of cnange sheets shall be numbered Ta, ib, ic, etc., at the bottom center of the page. The engineer preparing the revision shall print name and sign in the approval section of the " Summary of Change" page opposite the revision description.
4 .13.2 The extent of review required for revised MDDs and SDDs
, subsequent to Revision "0" shall be determined by the i section manager responsible for the change. As a min-imum, it shall include interfacing sections involved or impacted by the change.
4 .13 .3 Revisions shall be indicated by vertical lines opposite the revised portion of the text; prior revision lines i
shall be removed.
4.13.4 The ED&CC section shall maintain a history of revisions.
4.13.5 Prior to approval of a revision to a DIV I the corre-
, sponding Safety Evaluation (SE) shall be checked to determine if the validity of the SE is affected. If it c!' is the SE shall be revised and reference the new revision I of the MDD/SDD DIV I. It shall be noted on the Summary R; of Change page that the SE was reviewed and or revised.
5i s; Revisions of DIV I's subsequent to the RTR signing the SE O! shall be concurred by the RTR. l
}i
-4
[It a
5
' A000105011 E 18.0
___ . _ . _ . _ ~ .
TECHNICAL FUNCTIONS Nur- ter NUCIOSF oivisinN 5; 1-Adit-7313.01 ten nne\
~'
Title Revision No'."
ltodification and System Design Descriptions 1-00 5.0 RESPONSIBILITIES 5.1 MDD and SDD Division I (Refer to Procedure Flow Chart, Exhibit 1) 1 5.1.1 MANAGER Identify the MDDs or SDDs to be drafted and task ENGINEERING responsible section PROJECTS , -
FUNCTIONAL DEPARTi'EflT DIRECTORS (itEP/FDD) 5.1.2 SECTI0ft Assign task to engineer itANAGER Identify interfacing sections or organizations (S!!)
5.1.3 ENGIllEER Review reference documents l
, (E) Obtain support from System Engineering to
- determine Hunan Factors requirements (Ref. Exhibit 4 as required)
Obtain input from other interfacing sections as required Draft DIV I and the preliminary version of DIV II per sections 4.9 and 4.10
- Obtain document number from ED&CC l Review the draft with the Section itanager and release for comments in accordance with 4.8.3 5.1.4 l
INTERFACIftG Support effort as requested
! SECTI0ft Review and comment (3er
, !!ANAGER 5000-ACit-7370.03 lEP-008] 1 1 (ISt1) as appropriate)
I
! 5.1.5 PLANT Review for operability and maintainability inputs I i OPERATIONS 5j (PO) i 5.1.6 l
- ENGItiEER Resolve connents per 5000-ADft-7370.03 (EP-008) I 5 (E) Sign cover sheet as preparer j 0, Forward to Section !!anager for concurrence l 3l 4'
a x
3 l 5 A000105011 l 19.0 i
TECHNICAL FUNCTIONS Number ENu21 ear oivisi3N 5000.,0,,_,333.0, Title Revision No."" #
! llodification and System Design Descriptions 1-00 l
5.1.7 SECTI0ff Sign appropriate block on cover sheet to indicate ItANAGER concurrence and resolution of comments (Sit) Forward to MEP for approval if project managed or: Forward to Functional Department Director for approval and release 5.1.8 -
ftAtlAGER Sign (approve) cover sheet ENGINEERING Forward approved MDD or SDD to ED&CC for filing i PROJECTS / and record release (Ref. 5000-ADM-1215.02 FUNCTI0f!AL' [Ef tP-008]) I DEPARTriEflT DIRECTOR
(!!EP/FDD) l 5.1.9 l EfiGINEERIflG Assign issued number log i DATA & Maintain original documents C0flFIG Distribute according to project requirements
, URATI0li Update Configuration Control list I C0flTROL 1 (ED&CC) l l 5.2 ftDD II/SDD II Refer to Procedure Flow Chart, Exhibit 1. (Same as l Division I - Sections 5.1.2 through 5.1.9).
5.3 For !!DD or SDDs prepared by an AE only sections 5.1.1, 5.1.8 and 5.1.9 apply, i !
6.0 EXHIBITS
{
6.1 Exhibit 1 - Procedure Flow Chart
- 6.2 Exhibit 2 - itDD/SDD Cover Sheet and Summary of Change i
6.3 Exhibit 3 - !!DD/SDD Numbering Systen 6.4 Exhibit 4 - Human Factors Design Activities l
j' 6.5 Exhibit 5 - Guidelines For Changes not Requiring QA Contact, l 5!
E!
Ei U'
5 A00010 5011 -
~20.0
4 IOf4M 1(XX) ADM 12 5tt ul 2 til 82) e EXHIBIT 1 PROCEDURE FLOW CHART 2 o
r1E P/FDD '
IDENilFIIS MOD j OR 50D, , n' su !
TASKS SM lC O l8 4
i=
1 f v, E
m SM SN DRAFT 5 DIV I E ASSICNS I*
IDENTIFIES IS 4 & PREL IM DIV !!, _
> RESOLVES REVIEWS, MEP/FDD
- APPR OVE5 I gq5g5, 5ty pog y COMENTS CONCURS
& REVIEW o
un
.4.
I 1 og o
- 30 m2
, O.
~ I5H EDaCC n, O-2 REvlEWS &
COME NIS LOGS. FILES f- 2O i 2 h a =
m C 2
)f P0 DISTRIBUIES Q 1
REVIEWS &
2 COMENTS (A i
KEY E - EllGINEER EDSCC - ENGINEERING 04T4 & CONFIGURATION CONTROL F00 - FUNCTIONAL DEPARTENT DIRECTOR ISH - INTERFACING SECTION MANAGER t1DD - 1100!FICAi!0N DESIGN DESCRIPil0N 3 MEP - MANAGER. ENGIEERING PR(UEti5 < u[
P0 - PLANT (PERATIONS 500 - SYSTEM DESIGN r45CRIPTION @
SM - SICTION 1% NAGER $ ,,
H 3=
b o 'k u k.
i- o 3 *-*
o ,$Y o
i D-*
Number TECHNICAL FUNCTIONS l KUClear DIVISION 5000- ADM-7313.01
- g, ,
Revision No.
! Modification and System Design Descriptions 1 00 l -
3 I
i i 9 y- u a
1 8
I l 1 l h ~~
i E l t e I
, i i 5
! IW '
- iii ;
i 5 iii l lll I5 s -
i i .
5
! l l lbe i
i l, .
5 .
j 9 3 !,3 l E E i 8
I [
l ,
4!
=i
- 5' I j , 8l _. _.-
- i. i. ih gl !,l g
a' E
- Ilgl 7- 151 2
E g . . _ . _ . _ _ . . . _ _ ~.
=
1 EZ- 1 *000'0501'
Number TECHNICAL FUNCTl:NS 4MCl88F oiveinN S000-ADft-7313.01 Title Revision NdEP-005 )
flodification and System Design Descriptions 1-00 i
EXHIBIT 3 ftDD/SDD NUi! BERING SYSTEM Number shall be issued and controlled by ED&CC as follows:
- ttDD/S DD -
XX -
XXX -X T T T1-TitI-1 Letter Identifier T2-Tt!I-2 System (assigned by OC-Oyster Creek Identifier ED&CC as appro-Code priate to dis-(Ref. ES-017) tinguish between modifications on a single system
- Use either MDD or SDD whichever is appropriate - not both.
l I
i l
i l
?
l h
5 a
7 e
A000105011
% e TECHNICAL FUNCTIONS .
Number NUCIOSF---
oivislSN 5000-ADrt-7313.01 ren nn r i
"~'
Title Revision No'.~
flodification and System Design Descriptions 1-00
~
\
\ EXHIBIT 4 Human Factors Design Activities j
A human factors (HF) analysis is required for any new system or system modification involving a can-machine interface (MMI).
^
l!!!I: An 11MI exists anywhere a human operator becomes involved with compon-ents in the system. This may range from a door to be opened (can the door be safely and easily used by all operators during all probable conditions) to complex control panel design.
As part of HF design activities full scale nock-ups of the system are generally used, with walk-throughs for design operations and human factors staff. The systen is not built until the mock-up and applicable drawings have been evaluated.
For the design to be acceptable from a hunan factors standpoint, it cust comply not only with the generally accepted hunan factors standards, but also with the specific conventions in use at the facility being nodified.
j The HF analysis of a systen generally includes the following elements:
I. Controis and Displays
- A. Type (acceptable with HF principles and in accordance with site i conventions)
B. Location of pane 1(s)
C. Arrangenent of controls on pane 1(s) l II. Anthroponetry and' Accessibility A. Anthroponetry (hunan size and physical abilities)
- 1. Workplace layout
- 2. Panel design B. ACCes s
- 1. For naintenance 5 2. For normal operation
- 3. Traffic flow 5 -
3 4
2 8
A000105011 E4-1
l TECHNICAL FUNCTIONS Number Nder o, vision sooo_Ao,,_73i3.01 (FP nnC)
Title Revision No.
tiodification and System Design Descriptions 1-00 EXHIBIT 4 (Cont'd)
III. Labeling and Demarcation A. Labels
- 1. Size
- 2. Wording
- 3. Color ..
- 4. Location B. Demarcation and tiimics
- 1. Demarcation: location of
- 2. !11mics: Color and location of IV. Alarm Systems A. Arrangement and location B. Horns and lights C. Wording '
D. Logic (are the correct things being alarmed)
V. Environment A. Ambient (background) lighting
! 1. Level
- 2. Glare s r B. Ambient f!oise Level C. Other Anbient factors
- 1. Atmosphere quality
- 2. Static VI. Procedure and Guidelines A. Useability and readability
- 8. Interactions with controls and displays R
1 =
a 3
l 3 l 2 l !
l 1
k e
ACOO105011.
E4-2 l
Number ENuclear g
TECHNICAL FUNCTIDNS oivisan sooo.,o,,.,313.0, Revision NoKP-005 )
flodification and System Design Descriptions 1-00 EXHIBIT 5 Guidelines for Changes flot Requiring QA Contact 1
This exhibit provides guidance concerning when to obtain QA review of changes !
to previously released documents that contain QA concurrence.
)
QA review is requireif any time the quality or inspectability requirements in the design documents are affected. The tern inspectability neans the physical l ability to verify installation in accordance with the specified quality requirements.
QA Engineering notification of the type of changes listed below is not required; for all other changes to documents that contain QA concurrence, QA Engineering review is nandatory.
- 1. Ifode of plant (startup, operating procedures, etc.), equipnent (associ-ated with plant mode) alignment (valve / pump /switchgear, etc.), or other prerequisite changes.
- 2. ifaterial type or grade changes. (flew material must not be of a con-l trolled or prohibited category.)
l 3. Change of shape (inspectability cannot be affected).
- 4. Administrative changes, typo etc. that have no bearing in technical I content
{
- 5. Resolution of interferences expressing only a spatial (routing) prefer-ence (e.g., east or west side of columns) when no additional work (such as additional penetrations) is authorized.
- 6. Equipment designators or naneplate/ tagging requirements are changed.
! 7. Acceptance values of test parameters (e.g., voltage, hydro pressure, l' compressive strength) change within code requirements, but method of testing remains the sane.
5 k
5 bi E!
4I h
A000105011 E5-1
. _ _ _. . __ - _ - . - - . ._, _ _ _ _ - . -