ML20155D380
| ML20155D380 | |
| Person / Time | |
|---|---|
| Site: | Maine Yankee |
| Issue date: | 02/01/1988 |
| From: | Maine Yankee |
| To: | |
| Shared Package | |
| ML20155D350 | List: |
| References | |
| 18-340-1, NUDOCS 8806150135 | |
| Download: ML20155D380 (16) | |
Text
,...
RTTACHMEhlT C Procedure
Title:
Proc. No. 18-340-1 Class D
MAINE YANKEE SIMULATOR HORK ORDER Rev. No.
3 Issue Date 2/1/88 Review Date 2/92 Page 1 of 12 Dept. Mgr.:
1.0 OBJECTIVE To provide an approved standard of controlling and documenting work performed on the simulator.
2.0 DISCUSSION The simulator's value as an effective training device is dependent upon it being an accurate representation of the operating plant.
Whenever work is performed on the simulator, it is imperative that it is controlled and well documented to prevent jeopardizing the simulator's fidelity.
All work performed on the simulator is controlled and documented by use of the Work Order system.
A Work Order can be originated for one of four possible reasons:
repair, setpoint change, design change, or anhancement.
This procedure describes the steps and requirements necessary to originate a work request through closing it out. Attachment A shows the basic flow path of work request origination and processing.
3.0 REPAIR 3.1 Upon discovery of a discrepancy in the simulator software or hardware, S
the discoverer shall originate a Work Order by filling in the following information on a Work Order form (Attachment G):
name, title, description, and references.
3.2 'The simulator Operations Coordinator shall research the problem and determine if the reported discrepancy is valid.
3.3 If the reported discrepancy is determined to be valid, the simulator Operations Coordinator will approve the Work Order and begin processing the same as per Section 7.0.
3.4 If the reported discrepancy is determined to be invalid, the simulater Operations Coordinator shall complete the reason for rejection and return the Work Order form to the originator.
8806150135 880607 gDR ADOCK 05000309 l
0990a
~.
Proc. No. 18-340-1 Rev. No.
3 Page 2 of 12 4.0 SETPOINT CHANGES 4.1 Upon recel'ving notice from the I&C Section of a setpoint change, the Simulator Operations Coordinator shall evaluate the change for its effect on the simulator.
4.2 If it is determined that the setpoint change affects the simulator, the Simula, tor Operations Coordinator shall originate a Work Order by filling in the following information on a Work Order form:
- title, date, name, description, and references.
4.3 The Simulator Operations Coordinator shall begin processing the Work Order as per Section 7.0 of this procedure, 5.0 DESIGN CHANGES 5.1 The Simulator Group shall track all proposed design changes to the reference plant which are approved (see Attachment B).
5.2 Upon receiving notice from the Plant Engineering Department of approval of an EDCR, the Simulator Operations Coordinator shall determine if the design change affects the simulator.
5.2.1 The Simulator Technical Assistant enters the results of the determination (Yes or No) in the EDCR tracking portion of the Simulator Work Order reporting system.
5.3 Upon receiving notice from the Plant Engineering Department of a completed design change which affects the simulator, the Simulator Operations Coordinator shall originate a Work Order by filling in the following items on a Work Order form:
title, originator, description, and references.
i l
5.4 The Simulator Supervisor shall review the Work Order and complete the approval / rejection section.
NOTE Rejection of a design change requires the concurrence of the Simulator Review Board.
5.5 Upon approval of the Work Order, the Work Order form shall be forwarded to the Simulator Operations Coordinator for processing as per Section 7.0.
0990a
Proc. No. 18-340-1 Rev. No. 3 Page 3 of 12 6.0 ENHANCEMENTS-6.1 The originator shall request a Simula' tor Enhancement by filling in the title, name, description, and references on the Work Order form.
NOTE The description should also include reason and justification'for the enhancement.
6.2 The Simulator Supervisor shall review the Work Order for feasibility and forward it to the Operations Training Section Head for approval or rejection.
6.3 If the Operations Training Section Head determines the request to be impractical or too costly, he shall ' complete the reason for rejection section and return the Work Order form to the originator.
6.4 Upon approval of the Work Order, the Work Order form shall be forwarded to the Simulator Operations Coordinator for processing as per Section 7.0.
7.0 PROCESSING 7.1 Once the Ho'rk Order has been approved, the Simulator Operations Coordinator will begin the processing by filling in the following
(
applicable information:
a.
Type:
This will be one of four (4) letter designations; l
R - Repair, S - Setpoint Change, 0 = Design Change, E - Enhancement.
b.
Priority:
This will be established by using the guidelines in Attachment C.
c.
Syste:n.
d.
EDCR number (if applicable).
e.
Date.
I f.
Cognizant Engineer (s).
g.
Estimated man-hours.
7.2 The Simulator Technical Assistant shall assign a Work. Order number and l
input all the applicable information into the computerized Hork Order tracking system.
l 0990a l
i
\\
Proc. No. 18-340-1 Rev. No.
3 Page 4 of 12 7.3 The assigned engineer shall complete the necessary changes and/or repairs-in accordance with the Simulator Coding Standards (reference Attachment D).
7.4 Software changes shall normally be saved to a test load if applicable.
Software changes will not be saved into the training load until the change (s) has been thoroughly tested and accepted.
7.5 After the required change has been made, the Simulator Operations
[
Coordinator will perform testing in accordance with the guidance given C
in Attachment F to verify the change has been made correctly.
C C
7.6 After the change has been tested by the Simulator Operations
(
Coordinator, the software change may be saved to the training load.
7.7 After the Simulator Operations Coordinator has completed satisfactory testing, the originator shall perform his own test and sign for acceptance.
7.8 Each cognizantrengineer shall document his changes and/or repairs in accordance with the Simulator Documentation Standards (reference Attachment E) on the Maine Yankee Simulator Documentation and Resolution Form (Attachment-H).
7.9 After completion of work, testing, and acceptance, the Work Order form and associated documentation shall be fowarded to simulator Supervisor i
for his review.
l 7.10 After the Sim'ulator Supervisor's review and signature, the Work Order backage will be closed out and filed by the Simulator Technical Assistant.
[
8.0 REFERENCES
[
8.1 SOURCES
(
None 1
[
8.2 CITATIONS f
(
None 1
[
8.3 COMMITHENTS
[-
None l
l 0990a
Prec. No. 18-340-1 Rev. No.
3
.Page 5 of 12 g
ATTACHMENT A i
WORK ORDER FLOW PATH l REPAIR (R) l SETPOINT DESIGN l ENHANCEMENT (E) l CHANGE (S)
CHANGE (0) l l
l ORIGINATOR FILLS NAME, TITLE, DESCRIPTION, AND REFERENCE FOR R & S FOR 0 & E I
I lOPSCOORD. RESEARCHES l lSIM.SUPERVISORCHECKSFEASIBILITYl I _ _ _ _ _ _ _,
,___l IF HO IS INVALIO, OPS COORDINATOR ASSIGNS IF ENHANCEMENT-OPS COORD. COMPLETES DATE, TYPE, PRI, COG.
REJECTED, COM-RExSON FOR REJECTION ENG., M-HR, SYS, EDCR #
PLETE REASON FOR l
l REJECTION RETURNED TO TECH ASSISTANT ENTERS I
ORIGINATOR INTO COMP. TRACKING SYS 8 -"' : URN TO l
l ORIGINATOR ENGINEER (S) PERFORMS IF DESIGN CHANGE NECESSARY WORK REJECTED, OBTAIN I
l OPS COORDINATOR CONCURRENCE FROM PERFORMS TEST SIM REVIEW BOARD l
l SOFTHARE CHANGES TRANS-FERED TO TRAINING LOAD TECH ASSISTANT l
l CLOSES OUT AND i
ORIGINATOR ACCEPTS FILES WORK I
I ENGINEER COMPLETES TECHNICAL ASSISTANT l
00CUMENTATION -
UPDATES TRACKING SYSTEM I
SIMULATOR SUPERVISOR REVIEWS
~
I TECH ASSISTANT CLOSES OUT AND FILES l
l 0990a A
Proc. No. 18-340-1 Rev, No.
3 Page 6 of 12 ATTACHMENT B EDCR TRACKING SYSTEM RECEIVE COPY OF ALL PROPOSED EDCRs NHICH ARE APPROVED SIMULATOR GROUP DETERMINES IF SIMULATOR AFFECTED EOCR COMPUTERIZED TRACKING SYSTEM FILES AND CATEGORIZES ALL EDCRs APPROVED EDCRs HHICH AFFECT THE SIMULATOR l
l RECEIVE NOTICE SIMULATOR GROUP FROM PED OF ORIGINATES WORK COMPLETION OF REQUEST EDCR DESIGN CHANGE INCOR-PORATED IN THE SIMULATOR AND HORK ORDER CLOSED OUT l
l l
l 0990a I
Proc. No. 18-340-1 Rev. No.
3 Page 7 of 12 E
ATTACHMENT C F
HORK ORDER PRIORITY GUIDELINES Prioritles relate to the observable differences between the simulator and the operating plant.
The following guidelines should be used to establish the priorttles for Simulator Work Orders *:
Priority 1: Observable and detrimental (the difference changes the operator's diagnosis or actions).
Priority 2: Observable but not detrimental (the operator can detect the difference, but it does not change the diagnosis or actions).
Priority 3:
Not observable (the operator cannot detect the difference).
Priority guidelines are typically used for repairs only.
0990a
Pr:c No. 18-340-1 Rev. No.
P Page 8 of ATTACHMENT 0 1,,. e
$ 4' SIMULATOR CODE CHANGE STANDARDS Source code will contain a modifications section as part of the header of each source file.
Here will appear information on all alterations of the code. An audit trail designator consisting of the initials of the person who made the change followed by a sequential number (JD03 means John Doe made the third change to this file), the date the change was made, the Work Order number, and a brief description of the change, including applicable data, references, and derivation of constants.
Each line of modified code will contain the audit designator cceresponding to the change.
In case of multiple changes to a single line of code, the audit trail will be maintained by including the previous designators on comment lines below the changed line of code.
When making a change to a line of code, the original line should normally be commented out and a new line written so that it can be easily seen how the original code was modified.
0990a
Prsco No.~18-340-1 Rev. No.
3 Page 9 of 12 ATTACHMENT E SIMULATOR DOCUMENTATION STANDARDS Each cognizant engineer shall document his work utilizing the simulator documentation and resolution form.
(Reference Attachment D).
I. RESOLUTION The purpose of this section is to provide documentation to a level of detail at which another qualified individual can underttand the thought process of how and why the changes were made.
This section shall be a written English (not code) description of the change (s) made.
This description shall include a definition of all new variables, temps and constants.
The derivation shall be included for any new or changed constants; simplifications or non-standard approaches should also be stated. Also included in the resolution should be any testing, including expected and actual results, performed by the Engineer. When applicable, a marked up copy'of the appropriate section of code may also be attached.
II. DOCUMENTATION UPDATE:
The documentation update section shall be signed by the cognizant engineer signifying that either the appropriate documentation has been updated or that the information has been provided (attached.to resolution form) to the, technical assistant.
III. _ FINAL DESIGN SPECIFICATION (FDS) UPDATE:
The FDS update section shall be signed by the simulator technical assistant, signifying the applicable sections of the final design specs have either been updated or stamped "revision".
IV. REVIEW:
The simulator supervisor shall review the document to ensure it meets the intent of this attachment.
0990a
~
Proc. No. 18-340-1 Rev. No.
3 Page 10 of 12 m'
[
ATTACHMENT F
- p,-
' ~ ^
PERFORMANCE TESTING STANDARDS
[
[
Performance testing is a verification process that ensures the requested
[
software changes have been incorporated correctly without corrupting the C
existing software code. To ensure the simulator's fidelity is maintained,
[
performance testing shall be conducted for any changes made to any
[
engineering model software code.
By its nature, the extent and detail of
[
the test is very subjective.
It becomes impractical or impossible to test
[
the hundreds of logic paths or conditions which may be available for a
[
single software change. 'Therefore, the following list has been furnished to
[
provide items which should be considered when developing a performance test.
i
[
- 1. A performance test procedure should be well thought out and written prior
[
to conducting the actual test.
[
- 2. Discussions should be held with the cognizant engineer to obtain
[
recommended areas to test.
[
- 3. Related logic paths should be tested to ensure they have not been
[
corrupted.
[
- 4. Related remote functions should bc tested to ensure they have not been
[
corrupted.
[
- 5. Related malfunctions should be tested to ensure they have not been
[
corrupted.
[
- 6. Wheneve'r changes are made to items which reside in an array (e.g., P-26
[
start logic), time should be spent testing a single afray thoroughly
[
rather than spending the available time testing all the arrays
[
partially. A cursory check is all that should be required for the
[
remaining arrays.
[
- 7. Whenever changes are made which may affect critical dynmaic calculations
[
(e.g., pressurizer pressure), selected base line transient testing should
[
__.be conducted.
The results of the test should be compared to most
[
recently completed operability test results.
[
- 8. Acceptance criteria should be based on actual reference plant response
[
data (e.g., UORs), design data (e.g., prints), and/or operational
[
assessments.
[
- 9. Any change made to the plant process computer software (1.e., M00 COMP)
[
which may affect the indication (s) which can be percehed by the operator
[
should be tested.
0990a
y
!ii.
Prcc. No. 18-340-1 4
Rev. No.
3 Page 11 of 12 ATTACHMENT G MAINE YANKEE SIMULATOR HORK ORDER TITLE:
TYPE:
SYS:
NO #:
EDCR:
ORIGINATOR:
PRI:
EDCR:
DESCRIPTION:
REFERENCES:
WORK ORDER APPROVAL:
APPROVED REJECTED DATE I
I I
I
/
/
REASON FOR REJECTION:
COGNIZANT MAN-HOURS ENGINEER (S)
TOTAL M-HR DATE HOM COMPLETED:
DATE TEST COMPLETED:
DATE OF ACCEPTANCE:
ORIGINATOR ACCEPTANCE:
DATE OF RFT:
DATE:
SIMULATOR SUPERVISOR: _ _ _
0990a
O Proc. No. 18-340-1 Rev. No.
3 Page 12 of 12 n:
ATTACHMENT H
~[
"'f..
'i NE' YANKEE SIMULATOR DOCUMENTATION AND RESOLUTION TYPE:
WD #:
Page 1 of FILI.S:
EQUATIONS:
RESOLUTION:
THE FOLLOWING DOCUMENTATION HAS BEEN UPDATED:
A.
I/O DATA BASE.
B.
SIMULATOR DIAGRAM (S).
C. ' SYSTEM MALF TABLE (S).
D.
SYSTEM RF TABLE (S).
E.
APPLICABLE LISTING (S) UPDATED AND IN BINDER.
ENGINEER:
DATE:
/
/
THE FDS HAS EITHER BEEN UPDATED OR STAMPED UNDER REVISION.
TECHNICAL A NISTANT:
DATE:
/
/
APPROVAL:
SIMULATOR SUPERVISOR:
DATE:
/
/
0990a
Page 1 of 4 ATTACHMENT D 3.2 A qualified simulator operator with a Maine Yankee Senior Operator license shall' perform or direct all-operational testing.
3.3 All plant data should be obtained and entered on to data sheets prior.to performing the test. Careful consideration should be given to_ achieve the most recent and dependable data. Whenever possible, data should be obtained from station logs, procedures, or actual plant instrumentation.
4.0 INTEGRATED TEST 4.1 RCS HEAT-UP-TESTING 4.1.1 Reset the simulator to IC-1 (cold shutdown).
4.1.2 Record the following data and compare to actual reference plant data.
PLANT SIMULATOR PARAMETER DATA DATA UNITS RANGE LOOP 1 Tc DEG. F 0-600 LOOP 2 Tc-DEG. F 0-600 LOOP 3 Tc DEG. F 0-600 LOOP 1 LPSI FLOH GPM 0-3k LOOP 2 LPSI FLOH GPM 0-3k LOOP 3 LPSI FLOH GPM 0-3k P-12A AMPS AMPERE 0-75 P-12B AMPS AMPERE 0-75
_El-3902X (VENT PART)
CPM (Loo Scale) 102 - 10/
RI-3902Y (VENT GAS)
CPM (Los Scale) 101 - 106
.RI-1801 (AIR EJ)
CPM (Lod Scale) 101 - 106 RI-3401 (PCC)
CPM (Loa Scale) 101 - 106 RI-1701 (SCC)
CPM (Lo6 Scale) 101 - 106 RI-2601
(#1 BD)
CPM (Lod Scale) 101 - 106 RI-2602 (#2 BD)
CPM (Loa Scale) 101 - 106 RI-2603 (#3 BD)
CPM (Log Scale) 10I - 106 i
i l
0058L-ARS-SDE I
L
Page 2 of 4 ATTACHMENT D (cont'd)
PLANT SIMULATOR PARAMETER DATA DATA UNITS RANGE RI-6101 (SERV BD)
CPM (Loa Scale) 101 - iOb RI-1601 (SERV HT)
CPM (Lo6 Scale) 101 - 106
_BI-3101 (LD LOH)
CPM (Loa Scale) 101 - 106 RI-3801 (LIO HASTE) 10 _:_lD6 l
CPH(Lo6 Scale)
RI-3102 (LD HIGH)
CPM (Lod Scale) 101 - 106 RI-3901 (HASTE GAS)
CPM (Loa Scale) 101 - 106 RI-3701 (BN HASTE)
CPM (Loa Scale) 102 _ 107 10. - 106 1
_BI-6102X(CONT. PART)
CPM (Loa Scale)
RI-6102Y(CONT. GAS)
CPH(Loa Scale) 101 - 106 RI-6104 (MAIN CR)
R/HR(L6a Scale 10 101 RI-6105 (CONT. LOH)
R/HR(Loa Scale 10 10I RI-6106 (DECON RM)
R/HR(Loa Scale 10-4 _lDI RI-6107 (FUEL POOL)
R/HR(Lod Scale 10-4_ _1Q1 RI-6108 (SAMPLE RM)
R/HR(Lod Scale 10-4__ _101 RI-6109 (PAB)
R/HR(Lo6 Scale 10 101 1
RI-6110 (SPRAY RM)
R/HR(Loa Scale 10 10,
PZR PRESS PSIG 0 - 3250 PZR LEVEL PERCENT 0 - 100 N/I POWER A PERCENT / CPS 10-8-100/.1-104 N/I POWER B PERCENT / CPS 10-8-100/.1-104 N/I POWER C PECCENT/ CPS 10-8-100/.1-104 N/I P0HER D PERCENT / CPS 10-8-100/.1-104
- 1 S/G PRESS PSIG 0 - 1000
- 2 S/G PRESS PSIG 0 - 1000
- 3 S/G PRESS PSIG 0 - 1000 LOOP 1 TH DEG. F 0 - 750 LOOP 2 TH DEG. F 0 - 750 LOOP 3 TH DEG. F 0 - 750 4.1.3 Commence plant heatup to 200'F using procedure OP l-1 and record following data.
. PLANT SIMULATOR PARAMETER DATA DATA UNITS RANGE LSI-F-59 FLOH GPM 0 - 8000 P-12A AMPS AMPERE O - 75 P-12B AMPS AMPERE O - 75 RCS H/U RATE DEG F/HR N/A EQlE Fast time may be used after the above data has been obtained.
0058L-ARS-SDE
Page 3 of 4 ATTACHMENT D (cont'd) 4.1.4 Continue RCS heatup using OP 1-1 and record _the following data after drawing a PZR steam bubble.
HQIE Ensure the simulator is not in fast time prior to obtaining the following data.
PLANT SIMULATOR PARAMETER DATA DATA UNITS RANGE PZR COLD LEVEL PERCENT 0 - 100 PZR HATER TEMP DEG. F 0 - 700 PZR VAPOR TEMP DEG. F 0 - 700 PZR PRESS PSIG 0 - 3250
_EZR HOT LEVEL PERCENT 0 - 100 EQIE Fast time may be used after the above data has been obtained.
4.1.5 Continue RCS heatup using OP l-1 and record the following data after 1 RCP is running, h01E Ensure the simulator is not in fast time prior to obtaining the following data.
PLANT SIMULATOR PARAMETER DATA DATA UNITS RANGE RCP AMPS K AMPERE O - 1. 2 RCS H/U RATE DEG. F N/A RCS CORE EXIT TEMP DEG. F 0 - 750 LOOP #
D/P PSID 0 - 100 R01E Fast time may be used after the above data has been obtained.
l l
0058L-ARS-SDE L
Page 4 of 4 ATTACHMENT D (cont'd) 4.1.6 Continue RCS heatup using OP l-1 and record the following data after 2 RCPS are running.
NOII Ensure the simulator is not in fast time p ior to obtaining the following data.
PLANT SIMULIl~0R PARAMETER DATA DATA UNITS RANGE RCP AMPS K. AHPERE O - 1.2 RCP AMPS K. AMPERE O - 1. 2 RCS M/U RATE DEG. F/HR N/A LOOP #
D/P PSID 0 - 100 LOOP #
D/P PSID 0 - 100 E01E Fast time may be used after the above data has been obtained.
4.1.7 Continue RCS heatup using OP 1-1 and record the following data after 3 RCPS are running.
K0lf Ensure the simulator is not in fast time prior to obtaining the following data.
PLANT SIMULATOR PARAMETER DATA DATA UN.IIG RANGES
- 1 RCP AMPS K._AMEEFIL 0 - 1.2
- 2 RCP AMPS K. AMERL 0 - 1.2
- 3 RCP AMPS K. AMPERrL_
0 - 1.2 RCS H/U RATE QEG. F/HP __
N/A i
0058L-ARS-SDE l
..