ML20153G309

Summary of Validation Program for Spds

ML20153G309
Person / Time
Site:	Limerick
Issue date:	02/24/1986
From:	PECO ENERGY CO., (FORMERLY PHILADELPHIA ELECTRIC
To:
Shared Package
ML20153G301	List: ML20153G298 ML20153G309
References
NUDOCS 8602280227
Download: ML20153G309 (43)

Text

m' - . --

-- s r 4" 4 , f.

L^ -l 9

PHILADELPHIA ELECTRIC COMPANY LIMERICK GENERATING STATION UNIT 1 NPF-39 DOCKET NO: 50-352

SUMMARY

OF THE VALIDATION PROGRAM i

FOR THE SAFETY PARAMETER DISPLAY SYSTEM FEBRUARY 24, 1986 4

6 k

I .

J k

P

t. smc+ ..% ~ - . +

s. g i

TABLE OF CONTENTS l

4 l

, f*Ke

1.

SUMMARY

1 'I

2. SCOPE /0BJECTIVE 2

{

! 3. SITE SPECIFIC VALIDATION ACTIVITIES 4 l 3.1 Summary 4 4 3.2 Site Validation of Data Bases 5 3.3 Startup Test 8 3.3.1 Test Verification Objectives 8

! 3.3.2 Test Activities , 9 3.3.3 Test Acceptance criteria 12 4

3.3.4 Startup Test Discussion and Results 13 3.4 Summary Results of Site Validation Activities -

14 4

4. PROBLEMS ENCOUNTERED AND RESOLUTIONS INPLEMENTED 15 4.1 Hardware Problems Encountered 15 f i 4.1.1 Data Acquisition System (DAS) Hardware 15 4.1.2 Computer Hardware 16 i 4.1.3 Other Hardware 16 4.1.3.1 Auxiliary Hardware 16 4.1.3.2 Battery Voltage Inputs 16 i 4.1.3.3 Suppression Pool Water Level Indication 18 4.1.4 Outstanding Hardware Issues 19 4.2 Software Problems Encountered 21 4.2.1 Major Software Problems Encountered 22 4.2.1.1 Historical Trend Plot Problems 22 4.2.1.2 Range Limit Problems 22 4.2.1.3 Drywell Spray Initiation Pressure 23 Limit Displays 4.2.2 Outstanding Software Issues 23 4.3 Summary of Problems and Resolutions 25

5. CONCLUSIONS 26 i

) 6. DEFINITIONS 27

7. REFERENCES 30 APPENDIX A. TYPICAL SOFTWARE PROBLEM REPORTS WITH CORRECTIVE ACTION Al APPENDIX B. TYPICAL PAGES FROM STARTUP TEST PROCEDURE B1 I

l a

f ii.

- - - 4 . _

s y -s 4

1.

SUMMARY

This report presents salient results of evaluations performed for the Philadelphia Electric Company in validating the operability of the installed Limerick Generating Station, Unit 1 Safety Parameter Display System (SPDS). Verified tests and analyses completed during the Limerick Unit 1 power ascension program have shown that functional, performance and interface design requirements placed on the SPDS by PECo and GE have been met, thereby demonstrating that the SPDS performs as designed over the full range of reactor power levels.

Based on these results it is concluded that the SPDS is properly installed and is capable of functionally performing as required in the plant environment. The Limerick SPDS is consistent with the General Electric SPDS described in the report " Licensing Topical Report for General Electric Emergency Response Information System" (Reference 1) and is considered to be operable.

1 m.m n m -

- - . . - . - . _ - . . _ . . ~ .

,  : ' .s '

l l

l

2. SCOPE / OBJECTIVE 2

s l-The purpose of this report is to document the plant specific validation of the Real Time Analysis end Display (RTAD) portion of the Emergency Response -

f Facility Data System (ERFDS) that was completed for Limerick Generating . 4 Station Unit 1. The RTAD portion of ERFDS includes those functions defined in l NUREG 0737 Supplement 1 as required for a Safety Parameter Display System :i (SPDS). The hardware and software used in the Limerick ERFDS was essentially the same as that used in the General Electric Generic Emergency Response

• Information System (ERIS) described in the General Electric Generic ERIS Licensing Topical Report (Reference 1). General Electric provided -

documentation of the Generic ERIS System Sof tware Validation Program for SPDS (Reference 2) to the Nuclear Regulatory Commission (NRC) and the NRC has i approved the generic application of GE ERIS to specific plants (Reference 3)

) provided the plant specific validation effort has been demonstrated satisfactorily. This report was prepared as an extension of Reference 2 for i

l the plant specific validation of the Limerick SPDS.

1 In order to perform this validation an extensive ERFDS startup test program has been performed. The purpose of this startup test program was to verify that the Limerick ERFDS software, dais bases, and hardware have been {

]

correctly installed, set up and calibrated. The program also ensures that certain data needed from plant operation has been incorporated into the plant 1

specific data bases. Together these tests verify that the system as a wbole l meets the design requirements for ERFDS and performs within the limits 1

specified in the Startup Test Procedure. The test methods used for the ERFDS J

2 1

e

,. - - - , -$.. , g) O W

startup test were the same as used for other NSSS system startup tests, i.e.

there are pre-established acceptance criteria, approved procedures, and sign-off for accomplishment of each step and result obtained. .This startup test program validated the ERFDS functions incorporated within the following g displays (these displays constitute SPDS): I Critical Plant Variables RPV Control (Power)

RPV Control (Temp)

Containment Control (Pool Level) 2 Dimensional Plots Trend Plots l' Validation Displays e

9 4

3 l

l 1

s-re n n. . a

• 'a 3

3. SITE SPECIFIC VALIDATION ACTIVITIES 3.1

SUMMARY

This section of the report describes the validation activities accomp- -

i lished at Limerick for SPDS. The subjects discussed in this section include i.

I validation of the data base, integration tests repeated at the site following installation of software, and the extensive startup test program. Most of the activities were performed in series with some significant overlap and/or repeat testing. Each time new software was installed at the Limerick site the integration test which was performed.at General Electric was repeated on the Limerick software. While data base validation was accomplished prior to the

(

startup tests, some changes to and revalidation of the data bases during startup testing was required.

l l

1 4

~- n n .-

3.2 SITE VALIDATION OF DATi BASES Data base validation was done in several stages depending on the charac-teristics of the data base and the or1Jin of the data input. General Electric, San Jose, provided data base input based on design specifications or V

system engineering analysis. Limerick site personnel input data based on hardware characteristics, instrumentation calibration and plant specific e engineering analysis. All of these inputs then were verified on-site by comparison with the input base documentation on a point-by point basis.

The data base and SPDS displays were reviewed by two CE system specia-lists during the time the plant was at 5% power. The review of approximately 900 system composed points and 1500 display outputs led to the changes of approximately 60 composed points and constants principally due to signal inversion or corrections to equations for plant specific configurations.

Corresponding changes were made to the displays and Display Parameter Lists (DPL's). At this same time field input problems were identified which c included out-of-range, out-r f-calibration, or out-of-commission signals which s

were corrected.

An on-site procedure, " Procedure To Control Changes Made To 'The' Emergency Response Facility Data System (ERFDS)' Data Base and Application Software", has been put in effect to establish the requirements for documenting changes to the data base and software.

5 r _ _ _ -

.t .

4 Site calibration activities provided input to the data bases in the form of signal identification,. signal characteristics, and signal conversion constants. Calibration activities were performed in two stages. The first stage consisted of verifying the setup of the SPDS data acquisition hardware and correlating softwar'e databases and the calculation of conversion constants. Test signals were applied to the input terminals of the data acquisition system to perform this activity. The second stage of the calibration process consisted of loop checking the inputs. This involved operating plant equipment (where possible), simulating the operation of plant equipment, or simulating real world inputs to the instrument loop transmitters. Conversion constants were recalculated if necessary during this <

activity. Whenever it was necessary to prove an input in a segmented fashion, care was taken to be certain that the segments overlapped. Testing was generally done by operating the source of the SPDS input. Simulation was used to prove a part of the electrical circuit only after it had been proven that operation of the source caused a response identical to the simulation. The i

methodology used to calibrate SPDS inputs is similar to that used for all I other plant system instrumentation.

The final validation of the data bases was performed as a prerequisite

for starting the startup tests with the exception of the validation of those constants which required plant power to fine tune and validate. These prerequisite system tests are described in Section 3.3.

6 i

- - - - - - ~ . . _.n.. .- . . . . . . - - .,-n . ..

1

• The SPDS system is designed to be fine tuned to reflect plant specific parameters accurately on the appropriate displays. During plant testing at Test Condition 6, the SPDS startup test tracked several plant startup test procedures in order to obtain performance data. The inclusion of this information into the data base provided fine tuning for the system displays and provides the operator / user the most accurate information possible. The following is a brief description of the most important constants which were recalculated.

e A core flow compensation factor used for adjusting the. wide range level instrument readings for pressure differences across the taps.

These velocity head effects on the taps change with flow.

e The reactor thermal power constant (used in the reactor power algorithm) that encompasses the influencing dynamics other than steam and feedwater enthalpy and feedflow. This constant allows for a reasonable correction for CRD flow, reactor water clean-up, ambient losses and reactor recirc pump energy / efficiency.

e Another core flow compensation factor used for differences in lower plenum flow and effects on bottom drain flow used as an input to RPV temperature, e A backflow constant which is used to correct for flow conditions associated with one recirc pump operation.

7 i

I s- _ _

'}

As a result of -the above validation activities and the confirmation provided by the startup test it is concluded that the data bases have been totally validated. Changes to the data base have been made in a controlled manner and a procedure exists to maintain proper control of future data base changes.

1 3.3 STARTUP TESTS The SPDS Startup Tests were conducted in accordance with a detailed procedure developed by Limerick site personnel. The purpose nf the SPDS Startup Test is to verify that the basic SPDS sof tware, hardware, data bases, and displays function as specified.

3.3.1 Test Verification Objectives The startup test program is designed to provide verification of the following:

1. All prerequisite system checks have been completed and documented.

Major prerequisite checks include:

o Software integration test completed on site. (This is a repeat of the integration test performed on the software at GE, San 1

Jose.)

8 a__a _

.+

~ -

e DAS hardware setup and corresponding data base verified.

e Composed point data base verified.

e Constant data base verified.

e Displays correctly registered into terminals.

2. The basic SPDS parameters have been observed to be consistent with associated plant hardwired instrumentation parameters. .

3. The values displayed for the basic SPDS parameters have been shown to be consistent on all displays.

4. The values displayed for the basic SPDS parameters are consistent with hand calculations performed utilizing the same input values.

5. The specified constants have been redefined to reflect actual rated operating conditions.

1 3.3.2 Test Activities The Limerick SPDS startup test program is designed to examine and verify the adequacy of six basic system features.

i 1

l

1. Composed Point Verification I

This activity verifies that the composed points identified in the I system design specification and needed to properly drive the SPDS -

displays, are in fact, loaded into the processor's data bases. In general this activity is a visual / clerical check.

2. Engineering Units Verification This activity verifies that the engineering units actually used when calibrating SPDS signals agree with those in the system design i specification I/O list. When discrepancies were found, changes were required in the point definition data base, and/or plant specific constants or the composed point list.

3. Plant Specific Constants Verification This activity verifies that the plant specific constants identified in the system design specification and/or input by the site and needed to properly drive the displays, are in fact, loaded into the processors data bases. In general this activity was a visual /

clerical check.

i 10

4. Plant Specific Constant Recalculation This test identifies those constants which need to have their values recalculated based on plant operation at the power which allowed the -

necessary direct measurements. This permits the actual final values instead of initial "best estimates" to be input to the data base.

5. Validated Parameter Verification This test compares the calculated SPDS validated plant parameters with measured plant data. The comparison verifies that the proces-sor's algorithms, plant specific constants, composed and measured point data bases have been correctly set up/ installed. This com-parison also verifies correct signal loop calibration. A two step 1

approach confirmed that the algorithm was handled correctly and was appropriate for the condition it was intended to formulate. Hard-copies of the SPDS displays were made for documencation of values

! presented and, as appropriate, data sheets were filled out with the

comparable control room and other indicator values. These results were then further reduced per the procedure to determine if the data sets were within specified limits of each other. In this manner the results had direct correlation to SPDS displays and were secondarily confirmed by hand calculation.

11 l

l C m- .

I t o . i

e ,

l 4

6. Event Target Verification This test verified that SPDS event targets correctly reflect actual plant conditions. The comparison validated important composed point 5 data bases and signal loop calibration. pl t s i

h

.i t

3.3.3 Test-Acceptance Criteria l

Acceptance criteria were as follows:

1. All SPDS validated data must agree with hardwired plant instrumenta-tion within 13% (of full scale of the plant instrument). >

2. All SPDS validated data on the various SPDS displays (taken as near simultaneously as possible) must agree with each other within a two sigma deviation.

3. SPDS event targets (e.g., Safety Relief Valve, MSIV, Scram) must ,

agree with plant status.

4. A hand calculation of the " validated" parameter resulting from the system validation function (e.g. reactor water level) must agree with the displayed value within 10.5% of full range.

9 r j 12 l

t 6' - .n ~ -

- I i

- 1 l

I Startup Test Discussion and'Results 3.3.4 The Startup Tes. verified that the data bases accurately reflect the hardware configuration of the front end data acquisition system by documenting -

g the calibration and loop checking of all SPDS signals and by comparing the i data bases with system elementaries. Steps also verified that the data bases accurately reflect the composition of the basic SPDS parameters by checking them against design specification and design record file documents.

The Startup Test demonstrated that the analog parameter algorithms function correctly and meet the acceptance criteria described in Section 3.3.3.

i The Startup Test demonstrated that event targets and status flags function correctly. Trend plots and X-Y plots were checked to assure proper positioning of the cursor for the given conditions.

Color for all display parameters were checkcd for proper operation.

The SPDS startup test was performed at various plant power level conditions in conjunction with the plant startup tests. Conditions include; Startup Test Condition 6 (100% power), cold shutdown, heatup, low pressure, IRM/APRM overlap and Startup Test Condition 3.

t 13 mm e

A portion of the test was specifically designed for constants calculation and fine tuning. During Test Condition 6, significant plant cycles were tracked in order to take data, insert constants corrections and make the displays portray the plant as accurately as possible.

t a

The procedure contained sign-off and date requirements for recording ,

1 completion of each step. Summary results were recorded in the procedure with <

$ backup hard copies, data sheets, etc. filed in appropriate permanent files.

Examples of the data sheets are contained in Appendix B. Upon completion of the startup test all of the data bases were reviewed and any changes since test initiation were verified as documented in accordance with the on site t i

procedure, " procedure to control changes made to 'the Emergency Response

} Facility Data System (ERFDS)' data base and application software."

i

)

3.4

SUMMARY

RESULTS OF SITE VALIDATION ACTIVITIES The SPDS system is designed to be tuned (constant changes) to plant ,

specific conditions. Accordingly, startup tests were run and corrections to 4 constants made until the SPDS parameters met the requirements specified or it j

was determined that a software problem report (SPR) was required. Test procedure problems were documented and resolved in accordance with an i established test exception procedure. No significant software problems are I

outstanding for the system. The SPDS startup test results demonstrate that the Limerick SPDS is operational and all acceptance criteria have been met.

l l

14

%m M h - - -

N ~+

N.g (4

by.

1. !os,s e %g

. ,"Do Oc4 We

1. ic,.O *44 #oS Wo,, #q F gy%p, c,m

~%g n NPo 6, zWp0 -

to On #

or Rt.

4 l

c*dy,e %p

1. of,%e 4c,4,0 e NF*0) &

• e *e #(e 4

r %e '%o e ng 4.]  %,

1. yb

,. . e"b y,', s,'e e

• oe s ' p ,*6;'bo

,2+g s ,o% ,0 ,**%g*t, b, r

N ,,m

• j,q g

o o, eyg e eg7 b Oe, ,

Ot sy of #' 'Og 4*q%, #g N

. & %gy 4q

< ]' E */j %g e

1. 4

%, NJ

• Fg

'*i( . *6, e

1. op *i, g #

b4 4

%o * (g to Seq D, '09 s.,*d Op, *e s, s, s ,e *e 0 p e

1. P e 0,e n" % ,

U

• /

b %gl e e(Q *loy te %#n e#q*9* ym# %e, opOg Ce #  %,  %, #6 e op #1 s  %, he t4,  %,

'%,, e

% 4 e

er. 'bg he , % ,,e op 99

%, q p *be e %s

• g, e 4, s 4,.s ,e, .%, vg Ebg o *p

• g OR s ,J.e s %e %o s

• s,s,,% #

4,

• do Sp,.  % 64 ,#4 e e4 4

1. 4 V, o 0 e,

N,o e,

eq* 0 ,N4 ,

op f.

fi p%,

% . e l4p%

ff'*e # *

,%'. f,1]% 4, 4j,4 7 eg e, Og r

%O

@% b 90 1,.

b e% W U,

e eq

~

'-.s - . _  %

4. ' PROBLENS ENCOUNTERED AND RESOLUTION IMPLEMENTED The problems encountered can be grouped into hardware problems and soft-ware problems. Both groups of problems are documented and controlled using 1 the same standard procedures.used for all-GE supplied plant systems. Field Disposition Instruction (FDI) and Field Deviation Disposition Request (FDDR) I documents are used to control actions to resolve both hardware and software problems.

I h

4.1 HARDWARE PROBLEMS ENCOUNTERED

! Some hardware failures were observed and corrected as discussed below.

i 4.1.1 Data Acquisition System (DAS) Hardware i

j Failed DAS hardware units were returned to the supplying vendor via FDDR i

j for rework. These hardware units underwent the same quality assurance tests i

as applied to original hardware upon completion of rework at the vendor. The proper quality assurance documents are prepared for this reworked hardware.

i Types of DAS hardware failures encountered have been normal failures as would be expected with the electronic hardware involved. Early failures were due to misuse or misapplication, shipping damage, firmware revisions required, 3 or manufacturing process breakdown. Most of these failures have been resolved 15 L 0 ._ - - -

by training and experience. The number of hardware units returned for apparent .

i malfunction (early returns included some units which had not failed) dropped significantly in the later stages of the installation and test program.

d 4.1.2 Computer Hardware i

A service contract has been established with the computer hardware supplying vendor for on site repair and service of the computer hardware. The i hardware failures encountered to date have all' been routine problems as would i be expected for similar equipment. .

1 i

4.1.3 Other Hardware i

4 l

4.1.3.1 Auxiliary Hardware 1

The Intelligent Display Terminal hardware is handled in the same manner as the DAS hardware with failed units being returned to the supplying vendor.

Service contracts for on-site service are in effect for printer plotter hard-i ware. Failures encountered with the above hardware have been routine, as expected type failures.

i i

j 4.1.3.2 Battery Voltage Inputs i

I ERFDS monitors the voltages of all the battery banks which collectively l make up the Safeguard DC power system. The initial design brought the battery i bank voltages (nominally 125 VDC) directly into the ERFDS input modules. This 16 l

6 ._ _.

design was found to create a potential for inaccurate measurement and equipment damage due to the following:

I Each input to the ERFDS analog input module consists of a signal ,,

high, a signal low, and a channel guard. Each ERFDS input module [

l contains protective circuitry which begins to function when the i

voltage difference between the signal low and module ground equals -

j j; 50 VDC. The operation of this circuitry is such that a voltage measurement error occurs when this circuitry is functioning. The

• i 2

j measurement error increases as the difference between the input i

• signal low and the module ground exceed j; 50 VDC. If the voltage difference between the input signal low and the module ground is great enough, the ERFDS input module could be damaged. Since the i

battery banks are purposely ungrounded, the voltage difference between the module signal low input and ground can be anywhere in i

the range of 0 to j; 140 VDC.

i This problem was corrected by installing suitably qualified l transducer / isolators between the battery voltages and the ERFDS input t

modules. The output of the transducer / isolators is 1-5 VDC. The isolator i

signal low output line which is connected to the ERFDS signal low input is f

.t grounded thereby alleviating the above problem.

l .

e h

6 1

17 I

i

r. I Lh __ __ _ _, ]

1 l

I 4.1.3.3 Suppression Pool Water Level Indication The initial ERFDS design had two inputs for suppression pool water level, each originating from redundant wide range suppression pool level -

instrumentation. This arrangement provided inaccurate level indication on the

SPDS displays when the suppression pool cleanup pump was in operation due to l I'

the following:

The tap for the wide range suppression pool level instrumentation is off the suppression pool cleanup pump suction line. When this pump is running, a six to twelve inch low error is introduced to the indicated level due to flow induced pressure losses in the suction ,

line. At times, this would erroneously put the SPDS primary containment status flag in alarm when suppression pool cleanup was in operation.

In order to correct this problem, two inputs from the redundant narrow .

range suppression pool level instrumentation were input to ERFDS. The narrow ,

range instrumentation is not affected by the operation of the suppression pool cleanup pump. The wide range suppression pool level inputs remain in ERFDS to provide level indication when the narrow range instrumentation is out of range.

1 0

18 v - - ~ .

y 4.1.4 Outstanding Hardware Issues

" CROUP NOT ISOL" Event Target The " Group Not Isol" event target on the GE ERIS SPDS displays provides the operator with a summary status of containment isolation.

The signals used to determine whether successful containment isolation has been achieved are the valve positions of the automatically initiated containment icolation valves. The isolation command signals of each containment isolation valve group are.used to trigger the event target algorithm. The valve position status of all containment isolation valves are input to ERFDS. Modifications performed in the later stages of the plant design to the Nuclear Steam Supply Shutoff System logic caused reassignment of the isolation valve groupings and ultimately the creating of additional valve groups and isolation command signals. As a result of these modifications, isolation commands for five of the fourteen isolation valve groups are presently not in the ERFDS data base. The signals will be input to the ERFDS system during the Surveillance Test (ST) outage presently scheduled for May, 1986.

The " Group Not Isol" event target has been temporarily modified for human factors concerns in order to not mislead the operators during the period when all isolation commands are not present in the system. The event target is modified to direct the operator to the Containment Isolation Valve Group Summary Display format for assessment of containment isolation. This display enables the operator to assess containment isolation by providing a summary of valve position status for each valve group. This display is available to the operator via 1 keystroke. If the operator determines that a problem exists in a particular valve group, lower level displays are 19

4 i

1 available on ERFDS which provide individual valve position status organized by valve group.

The event target modification is consistent with operator training on the use of the GE ERIS SPDS. The GE ERIS SPDS design requires the operator to utilize the Containment Isolation Valve Group Summary Display format in the event the " Group Not Isol" event target is declared " bad status" by the system. This occurs when the system detects as bad any of the inputs required for. the event target algorithm.

The " Group Not Isol" event target will provide alarm indication on failure to isolate for those valve groups for which isolation command signals are in the ERFDS data base.

The modified " Group Not Isol" event target in conjunction with the Containment Isolation Valve Group Summary Display format provide the operator with a concise method of determining containment isolation status. The modification to the event target will be removed when the remaining isolation commands are installed and tested.

Display Terminal Overwrite On occasion, personnel have witnessed what has been diagnosed as a display overwrite / refresh problem on the Intelligent Display Terminals. This problem is documented as an open SPR and is being investigated by GE. The problem occurs very infrequently, is recognizable, and can be cleared through the terminal's keyboard. This SPR does not significantly impact the functionality of the SPDS.

20

~

4

! 4.2 SOF'IWARE PROBLEMS ENCOUNTERED i

i Software problem resolution was controlled in the same manner as that used for hardware with the exception that each software problem detected was -

e documented in a Sof tware Problem Report (SPR). Appendix A consists of several [

4 ,

examples of typical SPRs which occurred during site validation with 1 I

descriptions of corrective action taken. The SPRs were transmitted to General l Electric for resolution via an FDDR. Software problems detected and resolved f by Limerick site personnel were also documented by SPR and FDDR so that the resolution can be reviewed and approved by General Electric. <

) Revisions to the computer code to incorporate resolution of SPRs is -

) transmitted by General Electric via FDI. The FDI provides an updated version .

i of the software, closing all SPRs documented in the FDI. General Electric-I

conducts full quality assurance testing (unit test, integration testing and QA testing) on the revised code before it is transmitted to Limerick. The FDI transmitting the revised code requires site testing to assure correct

, installation of the new software. Any new software problems found during this ,

site testing were documented via SPR and transmitted to General Electric via an FDDR. FDDR's are also issued to document software changes implemented at i the site between FDI software deliveries.

l e

d 4

i

,I l 21

% ._ R h .p

4.2.1 Major Resolved Software Problems 4.2.1.1 Historical Trend Plot Problems x i General Electric discovered during execution of their V&V testing (docu-mented in Reference 2) that the method used to calculate the historical portion of the trend plots did not meet performance criteria. The initial display of the historical portion of the trend was 'too slow.s The sof tware was originally designed to retrieve raw historical data, convert the data to composed data and then display it as historical trend data when the display requiring such data was called up on the screen. The Limerick software is 4

. improved by continuously storing the composed data in a buffer. When a display requiring historical data is called up, the sof tware only needs to retrieve the appropriate buffer data. Performance is much enhanced and is satisfactory for the application.

[ 4.2.1.2 Range Limit Problems I

Initially it was possible, under certain conditions for the software (and thus SPDS displays) to report an instrument signal "out-of-range" when in fact the signal was just at its range limit. The result was some signals reported as " bad data" despite the fact that the instruments were perfectly normal and within normal accuracy. This " bad data" categorization at certain conditions

prevented the validation of important parameters. This situation provided the operator with conservative results but deprived him of knowledge of actual plant conditions.

22 1

i W ww n n c

-9 General Electric provided via FDI a revised code which allowed Limerick personnel to adjust the data bases to correct most of the problem signal points. The remaining signal points were corrected by recalibration or by adjusting the DAS hardware range settings. 7 4.2.1.3 Drywell Spray Initiation Pressure Limit Display The Drywell Spray Initiation Pressure Limit 2-D plot display was supplied to the Limerick site with Suppression Pool Water Temperature as the Y-axis parameter rather than Suppression Pool Air Space Temperature. A review of the SPDS 2-D plot display against the Limerick Trip Procedures disclosed a '

discrepancy. The trip procedure requires the use of Suppression Pool Air ,

4 Space Temperature. The discrepancy was resolved as follows: Suppression Pool Air Space Temperature was added to the ERFDS data base. The 2-D plot was reformatted to contain Suppression Pool Air Space Temperature as the Y-axis parameter.

4.2.2 Outstanding Software Issues There are a few software problem reports (SPRs) that have not been resolved and/or incorporated into the current SPDS software. These have all been reviewed to assure that there are no open SPRs which significantly impact ,

the functionality of the SPDS.

+

23

. h A O

e M

e Among these SPRs is one which describes a very specific condition in which the top level display indication for containment isolation may indicate that isolation has not occurred when in fact one of a pair of isolation valves .

(inboard or outboard) has closed thereby providing isolation. The condition- '

S occurs only under the following circumstances: ]

4

(

1-l a. One valve in a line (either inboard or outboard) has been either 1

manually closed or automatically closed with subsequent reset of the isolation signal.

d and 9

b. The remaining valve in the line then fails to close on receipt of an isolation signal.

Under all other conditions the event indication logic functions as

^

designed to indicate isolation is achieved when one or more valves in a line is closed,  ;

This SPR has been evaluated and determined to not be a significant functional problem. First, the indication is in the conservative direction and second, the operator has lower level; displays readily available on ERFDS  ;

which'would show one of the two valves in the line is closed and therefore isolation has been achieved. This software problem will be corrected at the earliest opportunity.

s i

24 l - * - .--,-.%=we -- m . =e-. = -*-m + . .

s .

4.3

SUMMARY

OF PROBLEMS AND RESOLUTIONS D

Hardware problems encountered were considered routine and as anticipated for the type hardware involved. The DAS hardware and display terminals were .

returned to the vendors for rework if required. Repair of computer hardware was performed on site by the hardware vendor.

Software problems encountered included menu wording changes, eite specific corrections, lower level coding errors and event flag function errors. These problems were also considered routine for the complexity of software being used. Four examples of Software Problem Reports (SPRs) of typical problems with resolution are included in Appendix A.

25

. - j l

5. CONCLUSIONS i l

Based on the broadly scoped validation program that was conducted it is

';oncluded that the Limerick SPDS is properly installed and performs as required in the plant environment. Problems that could have impacted the functional operation of the SPDS were identified and corrected. All segments of the entire system were examined and validated. The Limerick SPDS is consistent with ine General Electric Generic SPDS described in the Report

" Licensing Topical Report for General Electric Emergency Response Information System" (Reference 1) and is considered to be operable. .

26

-- m , .,

. ~

6. DEFINITIONS ERFDS -

Emergency Response Facility Data System. ERFDS is the title applied to the Limerick plant specific ERIS system. ERFDS r includes RTAD and TRA functions. SPDS functions are included

• in the ERFDS RTAD.

RTAD -

Real Time Analysis and Display System - RTAD is a collection of functional systems which provide plant parameter real time displays to assist the operators'. -

i SPDS -

Safety Parameter Display System - SPDS consists of those -

functions defined by the NRC in NUREG 0737 as necessary for assisting operator actions in case of an emergency.

TRA -

Transient Recording and Analysis - TRA is a collection of functional systems which provide real time and historical '

recording of plant parameters during transient conditions. -

ERIS -

Emergency Response Information System. ERIS is the title applied to the CE Generic System. ERIS consists of RTAD, TRA and supporting functicus.

e h

27

_ _- __ __ . ..._.. ._ _ . ~ . . - -__ . . . . .

_a .M._ O "

3 Data Bases - The ERIS system is designed to utilize generic software applicable to all BWR plants. Data bases are provided so that plant specific sensor inputs, plant system designs and other plant specific

. t characteristics can be input to the ERIS system for ,

use in analyzing the plant parameters displayed. ,

{

Constant Data Base - The constant data base is that data base containing the plant specific data used to fine tune the system parameters displayed so that they accurately portray the actual values measured. )

Composed Point Data Base - The composed point data base is that data base containing the data required to combine the various algorithm inputs and outputs so that the intended analysis will be performed, thus resulting in the display of the correct parameter. t i

SPR - Software Problem Report - The SPR form is used to record potential software problems and the ultimate resolution.

FDI - Field Disposition Instruction - The FDI is a formal engineering quality assurance document used to transmit design change instructicas to the field.

28

_ _ . _ ~ _ _ . _ _ _ _ . _ . . . _,

FDDR The Field Deviation Disposition Request - The FDDR is a formal engineering quality assurance document used to transmit deviations from the field for resolution and/or approval. - -

e 0

t a

M on

• I I

l 29 l

1 -.,

'\

7. REFERENCES

1. General Electric Licensing Topical Report for GE Emergency Response Information System, NEDE-30284-P. y t

c

2. General Electric Generic ERIS (Base RTAD) Software Validation, 3 NEDC-30885, April 1985.

3. U.S. Nuclear Regulatory Commission, " Safety Evaluation Report Related to ,

the Final Design Approval of the GESSAR II BWR/6 Nuclear Island Design," -

i NUREG-0979, Supplement No. 4 July 1985. 9 i

1 e

c 30 t

il , - ,, e w - ,-----. e w e+ ---e amm-o r e -- =m.-o- , - + * * ~

t  % __ n . n -#

'A

, 'O 4

k e

APPENDIX A ,

TYPICAL SOFTWARE PROBLEM REPORTS WITH CORRECTIVE ACTIONS 4

l

! A1 l

1 t

l g ~'~ ~~ ' ~ ~ ~ ~~ - . - . . - , .. ,_ ,,_ _ ,

n .,

ERIS SOFTWARE PROBLEM REPORT PERSON INITIATING THIS SPR: PS SHUNK ERIS SYSTEM SITE IDENTIFICATION: LINE

• DATE: 26-JUL-1985 10:42:27.85 5 ERIS SPR NUMBER: LINE00381 SITE SPR NUMBER: 336 FUNCTION NUMBER: 22 - Data Transformation Interface (Assigned bw OMNIBUS Configuration Manasement) .-

PROBLEM STATEMENT: ' -- - -

~

8 LOGIC FOR B2111010 IS INCORRECT. SINCE ALL OF THE INPUT SIGNALS AND.THE NOT OPERATORS APPLIED TO EAACH SIGNAL, ALL ZER0ES ARE FED INTO THE n39 OPERATOR. THIS OPERATOR DUTPUTS A 0 (YES) c IF ANY INPUTS ARE IN THE O STATE. THEREFORE THE ONLY TIME A 1 (NO) STATE WILL BE OUTPUT IS IF ALL THE ISOLATED SIGNALS ARE IN THE CMD STATE. 5 l

• • • • • COMPLETE THE FOLLOWING, ONLY IF THE hEbOLUTION ***** l

• • • • • DOES NOT RESULT IN A CCI i

RESOLVED BY: F. KROMMENHOCK '

__________________-__________-__________-____ l DATE:". 15-NOV-1905 16:36:34.47 J

__________________________-___-_________-___________ 1 l

RESOLUTION:  ;

This Problem 15 to be Closed With a chanse to the C95-4020 spec. Since it is not a software Problem, this SPR is resolved.

J 1

I

.- A2 L QL h O

. . 1

1. .

(:

ERIS SOFTWARE PROBLEM Rio0RT PERSON INITIATING THIS SPR; P GLICK t

LINE t ERIS SYSTEM SITE IDENTIFICATION: ..

DATE: 26-JUL-1985 11:10:51.63 -

ERIS SPR NUMBER: LINE003C5 SITE SPR HUMBER: 340 FUNCTION NUMBER: 03 - Librarv Utilitw Routines -

(Assigned bw OMNIBUS Configuration Manasement)

PROBLEM STATEMENT: s .. .. ,,

ERROR MESSAGES FROM THE MESSAGE HANDLER SAYING GRHDIN OR 52 NOT IN DATABASE ARE SOMETIMES DISPLAYED ON THE BOTTOM OF THE TOSHIBA.

• • • • • COMPLETE THE FOLLOWING, ONLY IF THE RESOLUTION ***** ,

• • • • • DOES NOT RESULT IN A CCI *****

~

RESOLVED BY: GLICK -

~'

s _____________________ _______________________ .

DATE: 4-0CT-1985 13:32:33.14 RESOLUTION:

Resolved bw CCI's E1459 and E1460. .

A CCI has been released to the ERIS librarv for Function Number 03 - Librarv Utilitw Routines.

CCI NUMBER: E1459 t

! A3 We A

ERIS SOFTWARE PROBLEM REPORT PERSON INITIATING THIS SPR: BILL CURRY f ERIS SYSTEM. SITE IDENTIFICATION: LIME <

(

DATE: 7-NOV-1985 20:57:50.56 ERIS SPR NUMBER: LINE00461 SITE SPR NUMBER: 419 FUNCTION NUMBER: '41 - Historical Data Accumulation 1

(Assigned bw OMNIBUS Confisuration Management)

PROBLEM STATEMENT:

If trended data is kept disPlawing on a consolet and scanning is stoPPedt the dwnamic values turn masenta but the trend lines don't. When scanning is restartede the dwnamic Points' colors are restored and the trend lines staw as thew were. This is Potentiallw dangeroust as the displaw gives the iBPression that the trending data is currenti when, in factt trending will not resume until the displaw has been re-reauested.

Trend lines should be erased or colored magenta when scanning is stoPPedt Or at least When scanning is restarted.

A CCI has been released to the ERIS librarv for Function Number 41 - Historical Data Accumulation.

CCI NUMBER: E1840 A CCI has been released to the ERIS librarv for Function Number 29 - Data Accumulation Function.

CCI NUMBER: E1841 i

A4 j ., - _ _ . _ _ . _ . . _ ._._ _.. , - . _ . . _ _ _ . _ . - _ _ . _ .

SOF1 w AHE PHudLF:P HEFUNT # 452  ;

SYSTEM: LHIS DATE:13-JAN.19hb  !

SITf: LIMERICK HESOLVED? (h0/S]tE/GE):GE

---

...--.---....---- CH111 CAL? (Cb/HI/ME/LO):

thG1hEER: GILHERT GblCF FUNC110N: DATA TRADSFORMATION I N'I E R F A CF

............................ a PR0nLEP DLSCh1PT10hS (E.G. EXPECTFD HFSULTS VS ACTUAL RESUL1S)

THE PulNT M43E0102 (CHK PWP STAT, DHIVEN B) ALG0H11HM LHGkOUP) $

hlLL C0&E UP *AGENTA INSTEAD Ut HED 1h IT F]NDS A Pu1NT THAT JS IN ALAHm AND HAS BAD DA1A bEFUNE IT FINDS A GOUD POINT THAT IS IN ALAHH.

IMPACf Oh C0h1Irv01hG kith OTHFH TFSIS ( IF ANY )

1 COM-ENT:

1hE ALGUhl14H SHOULD HE LXPANDED 10 lhCLUDE HECOGNIT10r. OF A DA1 A B ASE ALAkN STA105 USED BY THF CUSTOMER FOh VOLTAGE <

VALUE COLORG.

i HESOLUI1ON DAN PAPPuhh IN SAN JOSE AbTh0RIZED A CH ANGE TO LHGHht;P TO A L I.O h I

THL CntCh FOR A POINT In AI.AHM UR PkE. ALARM Tu SUCCEED Oh!.Y 1F THE PGlh1 hAS GOOD DATA. CHANGF INSTALLED AT SITE HY G. GLICF.

• f G. GLICh 1/13/86 b ! G N A 1 U H E : ---. .. . . . -- . . .. . . . . . .. . . . . . D A 1 6 : . . . . . . . . ... . . . . . -- .

AS i,

. .._s. . -

A-- O h M

,D O

s APPENDIX B TYPICAL PAGES FROM STARTUP TEST PROCEDURE

! B1 i

--- .n - .

~

,- , qg 1g C *i:  ; SP-015,hEV 0 e,l . {l

. Ly J' . . '

. 1j =f 4:'. *."y ..'. E I: ,.h [ APPENDIX C

., . P A Gt. 10 0F 238 CCE/RLM/HLM DATA SHEET B.4.1-D -

REACTOR PRESSURE - LIMIT TAGS & 2D PLOTS - Lun PRESSURE ,

PURPOSE:

THIS DA1A SHEET IS USED TO DEMONSTR A1E THAT TFE STATIC AND . DYNAMIC FLAGS ASSOCIATED WITH REACTUP. PRESSUHE REFLECT THE PLANT VALUES AND FUNCTION AS DLS1GhED. .

TO FULFILL THE DATA REQUIREMENTS FOR THIS DATA SHEET USE THE SANE VIDEO H ARDCOPILS AND CONTROL ROOM / PLANT INSTRUMEfiT DATA COLLECTED FOR SCEF ARIO 4 - Lod PHESSUF:E THAT hERE USED FOR DA1 A SHEET W.4.1-A. ,

1. RECORD VALIDATED REACTOR FRESSURE FFDP THE RPV PRESSURE V ALIDATION DISPLAY, FORMAf 8 72. .

2. . EECORD 1HE REACTOR PHESSUPE VALUE FROM TriE HEAT CAPACITY TEkPEHAIURE LIMIT DISPLAY , FORMAT. 8 41. .

3 USING THE LIMIT LIhES ON '!HE SUPPPESSION POOL LDAD LIMIT DISPLAY,

• FOR'.AT 41 DETEHh1NE THE *EAXEMUM ALLOWED POOL LEVEL" F0H THE PRESSURE

__ N _ FT _ R . IN

4. RECORD THE POOL LOAD LIMIT 1AG VALUE FHCM THE FULLOWING DISPLAYS. ..

(G43 LOO 11,G43L0012) *' ~"

FORMAT DISPLAY HAME '

DPL 8 DPL TYPE X-COORDINATES-Y VALUE FT-IN 031 ,

ChTMT CONT--NR ,,

, 55,56 V-DPL 629 .

270 .

.I.i_ _ l(_. -

032 CNTMT CohT--UPSET /LR 55,56 V-DPL 629 270 .$d_ . l!...

. 033 CNTMT CONT--UPSET /.9R

• 55,56 V-DPL 629- 270 Y'd _[9 034 ChThT CONT--UPSET /HR 55,56 V-DPL 629 270* W- U 035 C.iTET C0hT--FR 55,56 V-UPL 629 270 .Y.Y._((..

055 SUPPR POOL WTR LVL 7,8 V-DPL 629 237 M.Y_ __. ..

5. THE " POOL LD* LIMIT TAG VALUE SHOULD EQUAL STEP 3 +/- 1.5 FT (34 POOL LEVEL FULL SCALE)

" POOL LD" TAG = STEP 3 +/- 1.5 FT .

TRUE FALSE (CHECK ONL) 031 CNTMT COhT--NR .T _/. ...

032 CNTMT CONT--UPSET /LH ...I_/ ... .

l 033 CN1HT CONT--UPSP.T/PR /. .

034 CHTMT CONT--UPSET /hR .$ /.... .

033 CkT8T CONT--FR .Y.. /.._..

055 5UPPR POOL WTR LVL _.. /.. . .

B2 . -

" * ^ =

a *

• p( , 2 g b j ,l , 9 :p { SP-015,REV 0 APPt:DDIX C J-U,j,,J'3 " ,

h3 'Dy PAGE 19 UF 238 U l U dl j 'j CCE/RLM/RLM' DA1A SHEET B.4.1-D (C0hTINUED)

6. kECORD ThE RE:AC10R PRESSURE VALUE FFDM THE HEAT CAPACITY TEdPERATURE LIMIT DISPLAY , F 0H r. A1 # 43.

..../$$[......PSIG .

7. USING THE LIPIT LIhES ON 1HE HEAT CAPAC11Y TEMPERATURE LIMIT b1 SPLAY, AND IhE RPV PRESSUHE (STEP 6) UETEHalhE THE MAXIF.UM ALL0kED POOL .  !

~ '

TEMPERATURE. -

... 7s2.3.....DtG r

~

S. AECOED ThE

• HEAT CAP" LIMIT TAG VALUE FROM THE POOL TEMP SECTION UT TH.

FOLLonItJG DISPLAYS. (D23L1110=P00L TErP LIMIT) .

FORMAT DISPLAY NAME DPL t DFL TYPE X-COORDINATES-Y VALUE DEG F 031 CNT*T CONT--NR 63 V-DPL 629 84 ...((lY.... .

fj 032 CNTxT CONT--UPSET /LR 63 V-DPL 629 ', 84 ..aE(DY....

033 CNTMT CONT--UPSET /HR 63 V-DPL 629 84 ...E9.Y.... i 034 CNTkT CONT--UPSET /HR 63 . V-DPL 629 . 34 ..JEMdY.....

035 CNTPT CONT--FR 63 V-DPL 629 84 , ...E329..... .

059 SbPPR POOL TEFP C 4 --

V-DPL 636 213 ...[d2)(.... ~

, 9. THE " HEAT CAP" LIMIT TAG VALUE (S1EP 5) SHOULD EQUAL SILP 7 +/- 10 CEG F '

' HEAT' CAP"(STEP 8)* STEP 7 +/- 10 DEGF FORhAT DISPLAY NAME TPUE FALSE (CHECK OllE) 031 ChTMT CONT--NR . JI. ./.. .... -

~

032 ChTMT CONT--UPSET /LR ..tI./...... .

~

033 Ck1MT Cort--UPSET /kR ..fI./......

034 ChTMT CONT--UPfET/hR ..$[./......

035 Cr4TMT COhT--FR ..if./...... .

ps

'- . 059 SUFFR POOL TEPP

....'./...... -

l

}

i a

B3 in - . _

t I . .

~

.T @] T/ .f} g sp.015,REV O h- b $ d lfd' s b j GWu i ,

APPENDIX C PAGE 20 UT 238 CCE / HLH / 5tl.M DATA SHF ET R.4.1-D (COP TINUED) 10 RECORD 1bE kEACYUM PkESSDI-E VALUE F1 GM THE RPV SATURATION TLNFEP47 uke L1PIl DISPLAY , F0kb A1 4 44.

_.._t!_?._..._PSIG ,

11. US1kG 1HE LIAIS LINES ON 1HE RPV SATUk ATION TEP.PERATUHE LIMIT DISPLA[ p AI.D THE FFESSUhE In b7EP 10, DETERM3 hE THE "h AX1HLM ALL0aED" KEFERENCE A LEG SEMPERATbPE. '

~

....Mk_....DEG F <

12 REC 0kD SHE "F.PV SAT" LIMIT TAG val.UE FROM ThE DPYhELL TEMPERATURE SECTION OF ThE FOLLDb1NG DISPLAYS. (D23 LOO 10= SATURATION TEMP LIMIT)

FDPP.AT DISPLAY NAME DPL f DPL TYPE X-C00RDINATES-Y VALUE (PSIG) 031 CNTMT C0 tit--NR ,

52 .V-CPL 317 84 . .N.. . t. _

032 ChTAT CONT--UPSET /LR 52 V-DPL 317 84

...rE.%-d.._ _ _

033 CNThT CokT--UPSET /MR 52 V-CPL 3177. e4 .. 8. N ____ E 034 ChThT CONT--UPSET /HR 52 V-DPL 317 44 ___id.O..___ -

035 .ChThf CONT--FR .s 52 .. V.-DPL -

31Y, 84 ...3.IE.....

.- 060 DRYWELL TEMP -

1 V-DPL 636 165 .. 3,gg,,,,, '

13, ,.THE ?RPV SAT" LIMIT , TAG VALUE,SHOULD EQUAL STEP 11 +/- 10 DEG F

~

"RPV SAT"(STEP 12)sSTEP 11 +/- 10 DEGF FORMAT DISPLAY NAME THUE FALSE-(CHECK OME)

~

031 ' ChTMT C0kT--hR ..T_ /...... -

032 CNTP.T CONT--UPSET /LR ..I ./.' ... .

013 CNTitT CohT--UPSET /ER ..T../ ....

034 ChTMT CCHT--ttPSET/liR .,_d /...... , .

035 ChTnT C0ht--FR y

..__./..___.

060 DP.YWELL TEMP ...../......

e B4 l

b _ _

'~

,  % @ f' SF-015, KEV 0 D

C V/'

m l -

x. -

a -

Jb ,

APPENDIX C

.. P AGE 21 0F 238 CCE/kLM/RLM 14 FOR 1HE FOLLO*IhG FORMATS RECORD THE PHESSURE C00PDINATE OF THE CURREh1 CURSDR POSITION FROM THE GRAPH AND THE CHARACTER ~

REPRESEh1ATION OF PRESSURE.

CODRDJhATE CHAkACTER

. F0FPAT DISPLAY NA*E VALUE (FSIG) VALUE (PS3C) .

~

[.D ._ .

~

041 SUPPR POOL LOAD LIM' .._ E$ ... -

[E_E..._

~

C43 HEAT CAP 7EMP LI>IT d3_$_ _

044 RPV 5A7URA7 ION TFMP .d8.3_ . ...IdE____

052 RPv eREssuPE ..G#.42%.. __ _ _./.??_ __.

15. -

VERIFY 1 HAT THE VALUE FOR THE CUR 50R COCRDINATES ON THE PLOTS AND THE DISPLAYED "CHARAC1Ek" VALUES ARE Tile SAME.

FORMAT DISPLAY C00RD1h ATE VALUE zWRITTEN RX PRESSURE  ?

DESCHIPTION

• TRUE/ FALSE (CHFCK ONE) 041 5UPPR POOL L0AD LI,M .d. /.. '

ilEAf CAP TEMP LIPIT.

043

• _. __/ __ ... ,

-  ? ,

044 RPV SATURATION TEMP . . .!._/.____._

y '

052 RPV PRESSURE - ._____/.._....

16. EECORD THE "5RV LIFT" LtdIT TAG VALLE FROM THE PRV PhESSURE PLOT (FORMAT 052). NOTE THAT THE VALUE FDP THIS TAG DOES NOT CHANGE buT Tele FLAG COLOR CAN C'h ANGE IF 'REAC7OR PRESSURE > SRV LIFT PRESSURE.

FORMAT DISPLAY NAME DPL f DPL TYPE X-COORDINATES-Y VALUE (PSIG) 000, CRI[ PLT VAR 22 5-DPL 283 269 . /.l f.Q. 6 8.V _

002 RPV CONT NR/PWR 17 5-DPL 255 223 U.?A_. 6U.

003 RPV CONT WR/PhR 17 5-DPL 255 223 U.399._ .G.861 223  !

'004 RPV Cor(T FZR/PWR 17 5-DPL 255 005 RPV CONT SDR/FaR 17 5-DPL 255 - 223 _ _ ... .. --

~

006 RPV CONT FR/ par 17 5-DPL ,

255 . 223 . . _ ...___--..

007 RPV CONT NR/TEPP 17 5-DPL 255 223 .. . .... ..

l 008. RPV CONT WR/TE.4P 17 -

5-CPL 255 223 009 RPV C0r.T FZR/TE.9P 17 5-DPL 255 223 .. __ --.---:

010 kPV CONT SDA/ TEMP 17 5-CPL 255 223 .. ..__.-._-

011 P.PY C0t1T FR/1EpP . 17 5-DPL 255 . 223 .....---....

4/ Y 052 RPV PRESSUHE ,,' 16 5-DPL 559 144 E.i'?._ _ f*8 ^:

,  :, w  ; .z . , . , . as - ** -

. C.:ih%w;Acc%'u'M i

U_. , , 1:

.. p . 3 -l? q y ! x ?:" ' -

c- h .m:.2:$;, a ,._ _ ,._,;f

• ,_ n n -

. . 1

• l 6

j:I'MQ Fl9 9 * ~ tr: = SP-015,REV 0 )

"P APPENDIX C  !

b 3NUSa 3 [i U(ll[CO F PAGE 22 OF 238 CCE/Rt.M/nLM t DATA SHFET 3.4.1-D (CONTINUED) i 170 THE "SRV LIFT" LIMIT TAG VALUE SHOULD READ 1130 PSIG' "SRV LIFT" TAG = 113Q PSIG -

i FORMAT DISPLAY NAME ,

TRUE FALSE -(CHECK ONE) 000 CRIT PLT VAN .

..UI./....._ ,

h

. p/

002 RPV CONT WR/PWR ...../...... 6 003 RFV CONT nR/PWM . .L.'. . / . . . . . . -

004 RPV CONT FZR/ par . .V.'. . / . . . . . .

005 PPV CONT SDR/PWR . . ./. . / . . . . . .

. pr 006 PPV CONT FR/PWR ...../...... ,

007 RPV CONT NR/ TEMP . ..V. . /. . . .. . . .

y/

008 RPV Col 4T WR/ TEMP ..../...... -

, y 009 RPV CONT FZR/ TEMP ...../...... ' '

. p/

010 RPV CONT.5DH/ TEMP - . .../..... .

p/ *

, . 011 RPV CONT FH/ TEMP ...../......

052 RPV PRESSURE,,

../.../......

18. IF A " FALSE" CHECK IS FOUhD IN STEPS 5,9,13,1'5 OR 17 THEN WRITE -

A TEST EXCEPTION ON DAT A SHEET 6.0, TEST EXCEPTION LOG. IF THE TEST EXCEPTION sAS RESOLVED MAKt NEW COPIES OF THE AFFECTED FORMATS AND FILL 007 LATA SHEET 8.4.1-D WITH THE NEk DATA. .AL50 FILL *

. DUT A SOFTnARE CHAhGE FORM AND ATTACH COPIES OF THE CHANGE TO THE RESULTS OF Th15 TEST. .

e C

1 .

s a l

\

l .* B6

<a _ - - _ . _, _  ;