ML20035C984
| ML20035C984 | |
| Person / Time | |
|---|---|
| Site: | 05200001 |
| Issue date: | 12/31/1992 |
| From: | GENERAL ELECTRIC CO. |
| To: | |
| Shared Package | |
| ML20035C981 | List: |
| References | |
| EOP-40-3.00, NUDOCS 9304120012 | |
| Download: ML20035C984 (12) | |
Text
.
1 Employees Only
\\
GE Nuclear Energy Engineenng Cceranny Prc:edure EOP 40-3.00
SUBJECT:
ENGINEERING COMPUTER PROGRAMS 1.0 PURPOSE 1.1 The purpose of this E0P is to define requirements for the control of computer programs defined as Engineering Computer Programs.
2.0 GENERAL AND APPLICATION 2.1 Computer programs developed or used by GE Nuclear Energy (GE-NE) personnel to produce design calculations, design bases, design data, J
or other data that affect the design, licensing, reliability, or i
i operation of a product line are required to comply with GE-NE requirements, industry codes and standards, and regulatory requirements.
2.2 Computer programs (excluding Job Control Language) are defined as i
Engineering Computer Programs (ECP) when they meet all the criteria that follow:
Are in a compiled form that is executed on computer equipment a.
administered by GE-NE Computations Section, or by external computations service bureaus, or at the GE-NE Hybrid Computer Facility, or on microcomputer equipment or interactive graphics hardware systems.
b.
Used to perform design computations or tc' perform evaluations of experiments.
c.
Executed repeatedly.
j d.
Have a useful life of more than six months.
e.
Have been accepted as ECPs by the Control Component.
These criteria apply regardless of the simplicity or complexity of a program.
2.3 Design Record File documentation guidelines are contained in Appendix A.
+ Indicates change i
Date Issued Revision Supersedes Page Change Notice A (10/8/92) &
December 31, 1992 15 Rev. 14 (10/23/92) 1 of 10 9304120012 930405 PDR ADOCK 05200001 A
~
Employees Only Engineenng CDerauq 4:cerre EOP 40-3.00
+ 2.4 Computer Software that is not controlled as an ECP can be used for design applications only if the results of each application are independently verified in accordance with E0P 42-6.00.
If that verification involves comparison of the software with alternate calculations or data, those comparisons shall be performed on the same compiled executable file of the software as used for the design i
applications. Usage of such software shall be indicated in the verification package.
3.0 DEFINITION OF RESPONSIBLE INDIVIDUAL OR ORGANIZATION 3.1 The following defines the responsible individual or organization for activities established in Section 4.0 of this E0P.
3.1.1 Control Comoonent - Component assigned responsibility for control of computer methods.
3.1.2 Desian and Development Comoonents - Components applying ECP to design and development tasks.
3.1.3 Responsible Comoonent - Component responsible for development of specific ECP.
Resconsible Enaineer - Person assigned responsibility for ECP.
4.0 PROCEDURE AND RESPONSIBILITIES 4.1 Responsible Comoonent i
i 4.1.1 Assign a Responsible Engineer for the ECP.
+ 4.1.2 Prepare and implement the Software Management Plan for development of the ECP. Assure that impacts on other ECPs (upstream and downstream) are appropriately addressed in the Software Management Plan.
4.1.3 Select the chairperson of the Level 1 Design Review Team to review the Software Management Plan and the. Hardware / Software System Speci-fication (H/SSS), in accordance with E0P 40-7.00. Manage the closure of all open items prior to requesting approval of Level 1 status.
Assure that the primary user organization is represented on the Design Review Team.
4.1.4 Select the chairperson of the Level 2 Design Review Team to perform a technical review of the completed ECP in accordance with E0P 40-7.00 for the purpose of final independent verification. Manage the closure of all open items ' prior to requesting approval of Level 2 status.
Issued:
12/31/92 Revision 15 Page 2 of 10
~
Employees Only Engineenng Oceranng Crocedure top 40-3.0o 4.2 Resoonsible Enaineer 4.2.1 Name the ECP using a generic five-character alpha-numeric family identification and a two-digit suffix commencing with 01 to indicate the ECP version number, and an optional character defined by the l
Control Component to identify the computer system used.
4.2.2 Provide ECP technical content, development, implementation of approved changes, documentation, and maintenance, which includes:
Generating and maintaining the ECP Design Record File (DRF), in I
a.
accordance with E0P 42-10.00, includi..g the documentation requirements of Paragraphs 4.3.5.a and 4.3.5.b.
b.
Developing the program.
Programming or directing programming and debugging.
c.
d.
Submitting the ECP source program and compilation to the computer Program Library for those ECPs stored and maintained by GE-NE Computations Section.
Coordinating the Level 2 Design Review presentation of the ECP e.
to provide a basis for verification.
f.
Specifying, for all ECPs not covered by Paragraph 4.2.2.d.
above, the method to be used to confirm that no changes occur in the ECP after Level 2 is assigned.
Presenting this method as part of the Level 2 Design Review.
(The method to be used may be administrative control of the ECP software or execution and comparison of output from previously defined test cases.)
g.
Assuring that at the time Level 2 status is authorized, material properties, which are encoded into the ECP or which are identi-fied as critical input values for the qualification process of the ECP, are documented for inclusion in the DRF as being either:
(1) Compliant with the BWR Fuel or Plant Materials Properties Handbook, or
+
(2) Authorized for noncompliant use. Requires a letter of justification. Authorized by the ECP Control Component and the Section Manager or Business Segment Manager (NSPD) responsible for the BWR Fuel or Plant Materials Properties Handbook, or issued:
12/31/92 Revision 15 Page 3 of 10
E' ployees Only m
Engineering Cpera w; =<::ehre top to-a.co (3) Not applicable to the BWR Fuel or Plant Materials Properties Handbook.
h.
Requesting DRF microfilming within six (6) weeks of assignment of Level 2 status.
After return of the DRF from microfilming, maintaining possession of a copy of the DRF until Level 4 status is assigned. Opening supplements to the DRF as required for permanent retention of post-level 2 documentation.
i.
Documenting all ECP problems (errors, discrepancies and maintenance changes) in approved ECPs at Level 2, 2R, 3 or 4.
Required documentation includes description of the problem and corrective action to be taken, including any necessary revisions of the User's Manual and other ECP documentation of 4.3.5a and 4.3.5b.
Classify identified errors as:
Tvoe A: Having impact on calculated numerical results, or Tvoe B: No impact on calculated numerical results Reporting Type A problems to all GE-NE ECP User Design and Development Component managers for evaluations of the impact of the problem on prior and current applications.
Include in the ECP DRF the identified lists of DRFs requiring evaluation for Type-A problem impact, as provided by all ECP User Design and Development Component managers.
Report Type-B problems to all i
l ECP user component managers for information only.
v ort Type-A and Type-B problems to assigned business interfas ts for consideration of customer notification.
j.
Submitting, for Control Component approval, problems and j
proposed corrective action (see Paragraph 4.2.2.1) within 30 days after determining that a problem exists. All ECP problem corrections shall remain compatible with input files used with the uncorrected version.
k.
Documenting ECP changes authorized by the Control Component.
Implementing a separate DRF Supplement for each problem correction change to an ECP version.
Submitting the DRF supplement for microfilming within six (6) weeks of assignment i
of Level 2 status for the problem correction.
1.
Notifying recipients of the problem report (see Paragraph 4.2.2.1) when corrective action is completed.
Issued:
12/31/92 Revision 15 Page 4 of 10
Employees Only Engineenng Operahrg 4:cedure EOP 40-3.00 4.3 Control Comoonent 4.3.1 Manage and control engineering interface activities with computation-al services.
4.3.2 Provide consultation on the management of interfaces with non-GE-NE computation service bureaus.
4.3.3 Assure ECP quality by:
Negotiating the basis for control of the Computer Program a.
Library by functional components providing digital computation services.
b.
Reviewing and concurring with procedures for ECPs controlled under Paragraph 4.2.2.f.
4.3.4 Approve Design Review Chairperson for Level 1 and Level 2 Design Reviews.
4.3.5 Approve ECP status levels as follows:
a.
Level 1 - ECPs approved for development. Documentation includes a Design Record File in accordance with E0P 42-10.00, which must include:
(1)
ECP Abstract, Form 50-001 (2)
ECP Status, Form SD-002 (3)
Software Management Plan (4) Hardware / Software System Specification (5) level 1 Design Review Report b.
Level 2 - Approved Production Programs are ECPs that are verified and documented for design applications or for all technical activities used in developing design related information. The ECP program is stored in the controlled Computer Program Library, or as approved at the Level 2 Design Review, per Paragraph 4.2.2.f.
ECP documentation includes the requirements of Paragraph 4.2.2.g, Paragraph 4.3.5.a, the Users Manual and any of the following documents that were not exempted by the Software Management Plan:
Issued:
12/31/92 Revision 15 Page 5 of 10
i
\\
l Employees Only Engineenng Cce?aung PrX&2.fe EOP 40-3.00 t
(1)
Software Requirements Description (2)
Software Design Description
+
(3)
Software Test Plan and Test Report j
(4)
Independent Design Verification Packet (5) Program Source Listing c.
Level 2R - Restricted Approved Production Programs are ECPs that do not satisfy all requirements for Level 2, but which may be I
applied to design tasks for a limited time with Control Component approval.
d.
Level 3 - Archive Programs are ECPs approved for design use, but which are no longer the most recent approved version.
i e.
Level 4 - Historical programs are ECPs that are inactive and not currently authorized for design tasks.
Engineering Computer Programs are renoved from use within 30 days of assignment of l
Level 4 status.
f.
Level 1 and 4 ECPs are not authorized for design applications.
However, the program contents may be used for design l
calculations if:
(1) The program is referred to by the ECP name with an appended suffix, - (Level 1) or - (Level 4), to identify the uncontrolled status, e.g. PANAC10V - (Level 1).
+
(2) Results of the calculation are independently verified in accordance with Paragraph 2.4.
l l
4.3.6 Approve changes to ECPs including:
a.
Reassignment of ECP status levels, b.
ECP problem corrections.
l 4.3.7 Maintain the control file of all computer programs ; classified as ECPs, including original abstract (50-001), Status (50-002),
Hardware / Software System Specification and Material Properties (see Paragraph 4.2.2.g).
4.3.8 Issue revision-controlled identification numbers for H/SSS, and retain original copies of H/SSS documents.
1.ssued:
12/31/92 Revision 15 Page 6 of 10 t
j-Employees Only Engingenng 0097a fir; Drxedire EOP 40-3.00 l
4.4 Desian and Develooment Components 4.4.1 GE-NE components that apply approved ECPs to design and development activities are responsible for documenting both verification of inputs and confirmation that the utilization is within the application range of the ECP.
4.4.2 Confirm, for each application of an ECP not covered by Paragraph 4.2.2.d that the ECP has not changed since it was originally quali-2 fied, verified, and assigned Level 2 status. Confirmation shall utilize the same method presented at the level 2 Design Review, per F
Paragraph 4.2.2.f.
4.4.3 Document and report to the Responsible Engineer, ECP technical usage problems, including potential errors.
d 4.4.4 Document to the Responsible Engineer, new or revised ECP features and technical requirements needed for design applications.
4.4.5 Identify all DRFs that require evaluation for impact because of Type A ECP errors. Within 30 days of the error report (see Paragraph 4.2.2.i), provide the ECP Responsible Engineer with the list of DRFs i
to be evaluated.
5.0 RESPONSIBILITY FOR COUNSELING For counsel on matters pertaining to this E0P, refer to the E0P 4
Counsel Matrix in E0P 15-1.00.
6.0 REFERENCES
E0P 40-7.00 Design Reviews E0P 42-6.00 Independent Design Verification E0P 42-10.00 Design Record Files Issued:
12/31/92 Revision 15 Page 7 of 10 i
1 Employees Only Engmesmg Cce?a ' y :!::EL!?
EOP 40-3.00 APPENDIX A GUIDELINES FOR DRF DOCUMENTATION Al DRF DOCUMENTATION Guidelines for the documentation requirements of Paragraphs 4.3.5.a and 4.3.5.b are summarized below.
+ A1.1 Software Manacement Plan (SMP)
The SMP includes the definition of scope, tasks, and schedules.
For new versions of ECPs developed under previous versions of this E0P, the SMP defines the extent to which the ECP documentation require-ments of Paragraph 4.3.5.b are to be retrofitted to the unchanged portion of the ECP.
For ECPs or portions of ECPs developed by an organization external to GE-NE, the SMP defines the extent to which the ECP documentation requirements of Paragraph 4.3.5.b are to be generated for externally developed software.
Plans for maintaining compatibility with other ECPs (upstream and downstream) should be addressed, as appropriate.
Normally, the documentation described in Paragraphs A1.1 through A1.8 will not be formally issued as Corporate documents but will be descriptive material contained in the ECP DRF.
In cases where the Responsible Component deems issued documentation to be necessary, the SMP will define that information to be contained in issued documents.
i A1.2 Hardware / Software System Soecification (H/SSS)
A specific ECP is a part of an overall hardware / software system. The H/SSS defines all of the functions that the system is to perform, all hardware and software elements of the system, and the performance and testing requirements associated with these functions and elements.
For the subject ECP, these definitions shall specifically include the objectives and broad functions to be performed, any significant physical modeling assumptions, the inputs and outputs, and any special interface testing requirements or other constraints. A revision-controlled identification number for the H/SSS will be assigned by the Control Component. Verification of adequacy for the original H/SSS is provided by the ECP Level I review. Any revisions to the H/SSS subsequent to the ECP Level I review require the concurrence and approval of the Control Component.
Issued:
12/31/92 Revision 15 Page 8 of 10
l Employees Only Engineenng Ccera vg :c:eLee Sop 40-3.00 A1.3 Software Recuirements Descriotion (SRD)
The SRD provides more detail on what the ECP must do.
The SRD includes the technical basis description which defines the technical assumptions and mathematical formulation of the ECP, validation requirements, and a description of the overall inputs, outputs, and other constraints on the software embodied in the ECP.
The SRD shall define the BWR Fuel or Plant Materials Properties l
Handbook section or other sources from which the encoded material properties will be obtained.
A1.4 Software Desian Descriotion (SDD) l The SDD defines how the software is designed to satisfy the H/SSS and SRD requirements. The SDD provides a summary description of the planned software design.
This can include definitions of the software modules, hierarchal charts, data flows and logic flows as appropriate for effective development and maintenance. Data base and file structure definitions may also be included. Where special test provisions will be necessary, these should be identified in the SDD.
+ A1.5 Software Test Plan and Test Report (STPTR)
The STPTR describes the overall test approach and the results.
The STPTR provides the detailed description of the software tests, including unit, integration, and system tests required to assure that the coding and associated software data library satisfy all require-ments defined in the H/SSS and SRD. This description can be issued separately as a test plan document. The STPTR documents the results of these software tests, with the results included directly or referenced in the STPTR.
A1.6 Indeoendent Desian Verification Packet (IDVP)
The IDVP is the collection of all documentation of independent design l
l verification. This packet always includes the Level 2 Design Review Report addressed in Paragraph 4.1.4 and will include, when available, comparison of results with experimental data or results from alternate methods and user testing.
A1.7 Code listino A documented source listing of the completed software.
For problem corrections, the source header can include a brief description of the changes and reference to a software problem notification document.
1 Issued:
12/31/92 Revision 15 Page 9 of 10
Employees Only Engineenng Qcera nn; ??::edure EOP 40-3.00 A1.8 User's Manual I
The User's Manual provides a summary description of the ECP functions and restrictions; an application statement consistent with the Abstract; a detailed description of the ECP input and output; a list of the ECP error messages and definitions for those messages not adequately described within the ECP; and a sample test problem. The User's Manual shall be approved by the Responsible Component manager.
4 f
l 4
1 Issued:
12/31/92 Revision 15 Page 10 of 10 e
w m
,-w
--wm,
-+g---we,-,:.-r-9v--w+.--
gy=w-*-
Employ:2s Only EOP 40-3.00 Engineering Operating Procedure Supplement A
SUBJECT:
ENGINEERING COMPUTER PROGRAM ABSTRACT SD-001
& GE Nuclear Energy En;beert; Cc puter Prcgam Atwact l
=
RE5Pcas;5 E I%I4EIR E%;#EIR:hG COMP' SIR PR:)3RM nu[
- esign secoro Fiie n.anoer Anstract (trDO9ent 041e Iev. 40, ham APP;IailDa 5fiiEMInf Pt3GEp DESCRIPf!0N 1mts Outputs Dotweatat ion C
- rEN' tee Reguireme*tl
'The Ergneer tesponsce for the tecnrucat content of the ECP completes tras forrn. SM tes and dates attettW3 to the accursey of the mtorestian Peteted name Gate
- sigutus, S 001 (3/11)
Date issued Revision Supersedes Page March 29, 1991 2
Rev. 1 (7/20/87) 1 of I
Employees Only i
EOP 40-3.00 Engheering Operathg Procedure supplement e
SUBJECT:
ENGINEERING COMPUTER PROGRAM STATUS SD-002 GE Nuclear Energ Engineenng Computer Program Status I
se modee RL5POR$1L L%inLLA thinLER1% CapW'uTLA PRWAAM h4ML Design Record File ammer Authertaing Docuument and her Rome Camponent LEVEL I PLANNED LEVEL 2 DESIGN REVIEW DATE
//
Control Caponset Title Date LEVEL 2R COMPUTATIONS SECTION LIBRARY IMPLEMENTATION 5 elect name:
Date:
Espiration Date:
//
Control Comunnsnt Tttle Date LEVEL 2 COMPUTATIONS SECTION LIBRARY IMPLEMENTATION 5 elect ames:
Date:
//
Centrol Camponent Title Date LEVEL 3 COMPUTATIONS SECTION LIBRARY IMPLEMENTATION Select name:
Date:
//
Control Camponent Title Date LEVEL 4 g,,g,g, gy,,g,,, gj, f,,,, jgg,,,
/ ResponsiNe Engineer Completes
// Contr$ Component Commeres jj Control Camoonent Title Date 50-002 (10/92)
Date Issued Revision Supersedes Page October 23, 1992 4
Rev. 3 (3/29/91) 1 of 1
. - - -.