ML20101Q037

Emergency Response Facility Info Sys Overview

ML20101Q037
Person / Time
Site:	Brunswick
Issue date:	12/31/1984
From:	GENERAL ELECTRIC CO.
To:
Shared Package
ML19269A818	List: L-82-033, Forwards NUREG-0737,Suppl 1 Compliance Submittal,Including Proprietary SAR for Spds,Brunswick Steam Electric Plant Emergency Response Facilities Info Sys, Per Generic Ltr 82-33 & 840222 Order.Sar Withheld (Ref 10CFR2.790) ML20101Q037 ML20101Q046 ML20101Q056 ML20112C473
References
RTR-NUREG-0737, RTR-NUREG-737 NUDOCS 8501070353
Download: ML20101Q037 (48)

Text

,

l i

}

I a un na - uar = =

1 I

4 l

ERFlS SYSTEM i

OVERVIEW

~

l 6

l 4

?

i a

f i

BRCNFWICK STER 1 EIEC"'RIC FIJ2."I' E4ERGE'Cl RESFCtiSE FACILIT? E;FCF2%TICN SIS ~D1 ERFIS i

I i

i i

l l

1 l

t l

l l

i I

i cece sER, 1984 I

i 05010/0353 841227 e

PDR ADOCK 05000324 F

_ _.PDR

_...m._

--T j

t s=

.,+.f<-4

.t wo :.P,i r., ;,.

..~, ;.

i 1

1.

i 4

1 i

i t

k j-i DISCLAIMER OF RESPONSIBILITY 3

This cccument was orecarea cy or for the General Elecmc Comoany. Neither the General Electnc Ccmoany nor any of the contnbutors to this cocument:

i j

A Manes any warranty or reoresentation. excress or imotrec. with resoect to the accuracy. comoieteness. or usetusness of the information containedin inis docu-J j

ment. or that the use of any information casclosed in this occument may nct i

intnnge povately ownea ngnts: cr B.

Assumes any respons Citity forIsabouty or Camage of any kind wnicn may resuit i

from tne use of any intctmation cisc csed in this dccument.

i i

l i

i F

F eu, s.

. ew

,3 a

e v4 '

6 g. y th e, % Q.

4 o.

- m

• w w-ww we,7 we r w w wm ww..

F L

.:u o.

,p-

~

-l

'SECTION I INTRODUCTION z-

)..

1. 1 Purpose and Scope.

1-1 1.2 System Overview.

1-1 SECTION 2 ERFIS HARDWARE 2.1 General..

2......

2.2 Data Acquisition.

2-1 2.2.1 Description................

2-1 2.2.2 Process I/O Subsystem.

2-3 2.2.3-ERFIS Data Acquisition Signals.

2-5 2.3 Central Processors and Peripherals.

2-5

2. 4' Intelligent Graphic Display.

2-9 1

2.5 -Other Equipment 2-10.

j.

SECTION.3

-ERFIS SOFTWARE l'!:

f_

3.1 General.....

.3-1 L

3.2 ' Software Requirements.

3-11 L

l

^

3.3 ' System Software.

3..................

t j,

3.3.1 VAX/VMS Operating System.

3-2

[

J-3. 3. 2 DECNET-VAX.

$3-4' t

3.3.3 JVAX Fortran.

3-4 3.3.4 liabitat-Data Management System.

3-5 p

3.4' Application Software.

3................

i-3.4.1-Common Data and Control Interface (CDCI).. _3-8 3.4.2-Real Time ~ Analysis and Display (RTAD).

3-11

~

3.4.3

_ Process Log and Alarm (PLA) 3-12 3.4.4 Transient Recording and Analysis (TRA)..

3-14 VL.4-

.a SECTION 4 ERFIS Fl'NCTIONS

+

4.1 General.

4-1 4.2 Data Acquisition.

4-1 4.3 System Variable Processing. ).

4-2 4-4 4.4 SPDS.

4.5 Technical Support Center and Emergency Operations 4-5 Facility.

4-5 4.6 CRT Trending and Plotting.

i i

4.7

.tonitoring and Alarming.

4-5 i

i 4-8 l

a.8 Logging 4-8 4.9 Console functions 4-9 4.10 Engineers Console Functions l

4.11 Historical Data Storage and Retrieval 4-10 4-11 l

4.12 Alarm Presentation.

l 4.13 Graphic Displays.

4-11 4-12 4.14 Configuration Control.

l l

l l

I i

t I

i I

I I

I VL.4 i

~ - -..

, f],

r.t

[)(__s l.

INTRODUCTION 4

1.1-PURPOSE AND SCOPE e

The purpose of this document is to provide an overview of the computerized Emergency Response Facility Information System (ERFIS) for the Brunswick Steam Electric Plant Units 1 & 2, developed and delivered by General Electric Company.

4 The ERFIS described herein consists primarily of a data acquisition system, a computer processing system and a display system, which has been designed to aid utilities in complying with NUREG 0737, Supplement 1, and other. Nuclear Regulatory Commission (NRC) requirements pertaining to emergency response. The primary function of ERFIS is to make critical plant status information available to plant personnel at all times and L

I provide guidance information during emergency operation. ERFIS also provides supplementary information to aid in plant operation and post

. {

s

,c g

e. vent analysis.

1.2-SYSTEM OVERVIEW Figure 1.1 shcws the simplified version of the overall system.

i

.The ERFIS is'made up of elements of-the GE OMNIBUS product ~ family of nuclear power planti information systems. Use of these modular elements provides the ERFIS with a high degree of flexibility as well as a proven design.

l Specifically, ERFIS provides critical plant information and Emergency-Procedure Guideline (EPG) information by means of high resolution -

Intelligent Graphic Display Terminals (IGDTs). The'IGDTs are supplied with dynamic data from a redundant central processing system which utilizes Digital Equipment Corp. VAX -11/785 CPUs.

c

. CN n

1-1 s

VL.4

a

,R -

Analog and digital signals are acquired from existing Honeywell 4010 process computer cabinets and field sensors throughout the plant. Theet signals are scanned and transmitted to the VAX's by the int'elligent General Electric Data Acquisition and Control (GEDAC) modules for the ERFIS. Supplementary oata is also acquired from the process computer and other computer based plant systems via data links.

Unit I and 2 each have separate dual VAX 11/785 based systems with individual data acquisition equipment, control. room consoles, and peripherals. The Technical Support Center (TSC) and Emergency Operations Facility (EOF) include a common console which can display information from either Unit 1 or 2.

The ERFIS is configured such that no single failure of a major component (eg. cpu, disk, console, reconfiguration switch) will prevent the primary function from being performed. Data acquisition equipment failures are guarded against failures by duplicating essential sensor inputs. Automatic and manual failover procedures are incorporated.

ERFIS currently does not include process computer functions but

~

expansion capability and' spare ~ capacity are included to allow expansion' in the future with minimal effort and cost.

1-2 VL.4

,._____________________________________q O

I "5

'B - 8 l

1d la 1"1" ~II 8

5 s

la 8a i-i

________,0, r.

0,

!E Il ll

!$ ll 3

$- lI l l

l.e l

c_ _ _

2

=

w i.s s

a a

a a

1 r_ _

O sl i

o i

, s.

i s

i.s

=_

=

=

2.s_a,,

i,.s l.a

.3 a.s -

a a

ee 1

6 ll

. I

' - -b- - - - - - r -d -l-- - - - - -,-- -- "

E

=

e C.

s x

O i

i.

E v

a a.

3 m

3 2

3.

8 2

68 8

~3 2$

.v s.

3 o

l=

s i

.l.

1 a

=

x z

2 C

,A,

,A,

,A,

,A, c

T.l

_ =a.

=.l a

a

=-

=.

E si a

z z

.=

=

.z

.a e

w w

=4

• q e==s I

• g

=4 su m

=

3 3

.a m

s'es mamme N'

_.m 4

2 "1:s f

W 3

ij o

n

/-

=,_.

e f$

h p3 m

th.

0

'1 d

0 38

~~

7 y

2 N

I'51 fil i

..- _ _ _ { 5 _ _,._

.J

(

6.___

j

=

b

$~3 l

-J 3

i

}3 1

3 I

s E

..=

I l

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

NN'~

n i

\\.

'd

~ '2. ERFIS HARDWARE 2.1 GENERAL The ERFIS hardware configuration, typical for one of the units, is shown in Figure 2-1.

Table I shows the equipment list.

The system consists ot three major subsystems:

General Electric Data Acquisition and Control (GEDAC) system developed by Analogic Corp. under General Electric Company specifi-cation.

Central Processors and Peripherals from Digital Equipment Corp.

~

N Intelligent Graphics Display Terminals (IGDT) developed by Toshiba g

Corporation under General Electric Company specification.

^

h?

2.2 DATA ACQUISITION 2.2.1 Description GEDAC-is a microprocessor-based, totally self contained, solid state, high speed, modular system with a' flexible structure that

-can meet adverse application requirements. GEDAC acquires and transmits a wide variety mix of analog and digital signals. The data are gathered

~ '

at specified identifiable times and transmitted to the host computer.

Hardware for the GEDAC system consists of the numerous functional modules that can.be interconnected in a variety.of ways to build-up a large or small data acquisition and distribution system for both Class IE_and non-1E signals. The major GEDAC modules are:.

' q-

}

4.

Analog and digital input / output modules b.

Multiplexer module c.

Power supply. module 2-1 VL.4-

i

\\

=is I -J w

uN uf wg lU

'M A

wf 22 as$

5.

t x

2 a s G

8 M.i.

.t -

w E, w a.

s y

2 1

sf-

'O l

I l3:

i 1

,=

lD I "a a

I.

w 80 O

d M g

.'s 42 48gct

.U E S 3 8 =.

y2 E

"O gI g g i

as

<a w

s$3E.

53g l

33 3

g w

h.,,.

l z.

=

j =,

g q

p i

i I

l.5 M*

i>

~

IN de de g

g l O -aaN Te i.n 2

a ma w.

aw 4.

e i

1-u,.

s a.

aw k

.A. :"

5-l

"- 1 t

3" g

s

-w 3

Elp-f j:'

s 3

eu i

l x l t.:

w l

I.-

l I

Il

=

s o

c3 I

=

t N

s.

q.

1

.E. l 4

.-. e IC f"* !.,

IT w I

l f.

h 0.t

_..Q

- T =.=.

1 m

.r.e

,s y

JL l

=c l.,; a d!Ic l

.e 0.

a T

N

=.

={33

'?-

...?.=. 3, 9g I T.

6 e

2 i

N$3$

0$m3

"" s */ E IC s'

3 Eg?

w

-1'32 i

e

-s s-I

.i 5

- =

_;=

a s o=c

,a 3!I:

g a "H.C i

5 ".

3

,i s i

• E t-.

t 1

x.

t

]

s

=

g t

Ye l

.E M

i

.d u

8-r

"'l

.~c. 3 i,

s a.

.=

a-n i,

i i

l I;.=

s 0

3 -

3 E

I

• A s 4g ga Em l

l "4

a=

Ex

~- 3 3.'

O =.

,f 6j iE Cl h,'* M

O

.a a

g

,x

-g

-6

,15 t'

l l

~

~'

l

[

I.J l y l

.3. :&

• g x-x

' =.

l I

L e,

s.

r,

.x l

l 1 ;.4 as

==

pg C

3-m am w

g 6v a

w eis sg M

E A s 2

l Tz3 gt

.. ]

l-1 I

l

.E 3

=

?

~

6 E.i l

'c':

3.3 g,i

'O L

i d

M x

e s

c E.

• 3 :

l I

l IIE O u.

4

<l Sw e

~

U. S. E,s

.i e

d

-w U

y 8h 2.353 l

y i.

E 5 3 p-B I 3 J p-e es 8* 6 g-ay a.

1

=W w

• )

O e

2

=w g"*

Ed

.6. E e C

.O

<c e

i i

m

=

3 S3*~ pl O

i g e z,

[

y!

i g

_3 N

, p**

n M

O 1

4 fg w me a

2w g

i

.N s-d$g?

$m I

NI O

5.aI m.

ga O

'M l.5 34a.

• g i

i-

=

wa g

W

=

id [

1. w g.3a 4;

i.

• fA l

I l

lZ l

80 I

I tQ l

wA 2-e.

.s..$

e.

".3 O

GE I E.

a$5

.U E gE 3"2 9

l es wg w2

-s w-

' $2 83 6--.,,,,,,,,,,_,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,_,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,

a

i*

' (v d.

Data formatter e.

GEDAC 5500 chassis with cards f.

?!ultiline driver (splitter) 2.2.2 Process I/O Subsystem The GEDAC process I/O subsystem will collect analog, digital status, pulse and sequence-of-events inputs. The types and quantities of process inputs to Unit 1 and Unit 2 are those that support the Safety Parameter Display System (SPDS) displays as well as other functions, such as, the m'eteorological data..The GEDAC subsystem also includes the capability to generate analog and digital outputs for trend recorders digital indicators and annunciators in the ;ontrol room.

The Data Acquisition System (DAS) configuration is hierarchical instead of loop oriented.

Figure 2-2 shows Brunswick ERFIS data acquisi-q tion. The order is sensors, Input / Output !!odules (IOtt), multiplexers, formatters and central processors. Each processor interfaces to GEDAC l

through dedicated single ported formatters.

This provides a high.fegree of separatica and independence as opposed to multiple processors and multiplexers configured on a highway or loop.10t!s scan, digstice and transmit sensor data to centrally located multiplexers. The IO!!s provide multiple output ports to allow redundant routing of process data via multiplexers and formatters associated with each CPU. Each multiplexer is connected to a formatter for a given CPU. This provides independent and separate paths for the same IO!! data to reach each of the two CPU's.

Two classes of DAS equipment are utilized in the system; those that meet-Class IE requirements (GEDAC 4300 Series) and those that are non-lE equipment (GEDAC 5500 Series). The GEDAC 4800 provides Input / Output

?!odules (I0t!s) which may be located in racks within control panels to eliminate the need to bring sensor wiring to a central location. The GEDAC 5500 provides I/O cards mounted in a chassis which may be mounted

^

within existing panels or in a centralized cabinets. Each IO!! or I/O 1p 2-3 VL.4 i

f DIGI'IAL ANAIDG INPUP INPUT fftfire tilffll 4820 4410 tg I3 PUP bODUIES l

I l

4 4830 1E MULTIPLEXER l

NCN-1E CAS OiASSIS 5520

%N-1E CAS ClaSSIS i

f ff f

) I 4450 4850 ECRMATTER s

O 0

I i

t VAX VAX EFJ15 COMPUTER ROCN l

I FIGURE 2-2 ERFIS CA% AC(NISITION l

.- q card will typically handle eight (8) analog or 16 digital signals. Up to eight I/O modules (IOMs) may be connected to each multiplexer. Each GEDAC 4800 formatter will accommodate up to 16 multiplexers.

Thus each formatter can handle up to 1024 analog inputs or 2048 digital inputs or an equivalent combination of analog and digital inputs.

Multiple formatters may be connected to each CPU to obtain a higher point capacity.

GEDAC IOMs, multiplexers and formatters are interconnected via fiber optic or electrical cables which carry serial digstized data.

Field adoition of multiplexers and IOMs involves only mounting of modules, termtnation of signals, and interconnection of modules via a single fiber'

. optic or electrical cable.

2.2.3 ERFIS Data Acquisition Signals The system consisting of both class IE and non-IE signals scans and monitors over 900 signals providing data for both SPDS and non-SPDS functions.

2.3 CENTRAL PROCESSORS AND PERIPHERALS ERFIS Computer system is a VAX cluster configuration with two DEC VAX -

11/785 computers. The CPUs, disks, and magnetic tape are interconnected through a star coupler and redundant HSC 50 intelligent I/O server. The star coupler is a passive dual path device which provides a VAX to VAX communication link and data transfer between either_VAX and the dual ported disks and magnetic tape unit connected to the hSC 50s. The system combines a 32-bit architecture, high-speed, high-throughput. efficient memory management and a virtual memory operating system te provide esyentially unlimited program address space and superior performance.

j 2-5 VL.4

l l

[ N,

'k a.

Central' Processing Unit The VAX-11/785 processor provides 32-bit addressing, sixteen j

32-bit general registers and 32 interrupt priority levels. The instruction set operates on integer, floating point, character

(;

and packed decimal strings and bit fields. The instruction set f

supports nine fundamental addressing modes.

The processor includes a 32 KB two-way set' associated cache memory access time. The processor's memory management includes four hierarchical processor access modes that are used by the operattng system to provide read / write page protection between user sof tware and system sof tware.

l l

b.

Data-Throughput l

l l

VAX-11/785 includes many features that support high data m

throughput, including high speed computer interconnect (CI) for l

clustered peripheral-controllers, buf fered direct memory access for the UNIBUS peripherals and 64-bit data transfers and prefetching.

The operating system supports the hardware throughput in its I/O request processing software. The software uses the l

processor's multiple hardware priority levels to increase I/O response time and keeps each disc controller as busy as pos-l sible by overlapping seek requests with I/O transfers'.

l c,

Main Memorv l

The main memory for.VAX-ll/785 is built using 64K MOS RAM chips

('

and is organized in 72-bit words (64 bits for data and 8 for l

Error Correcting Code [ ECCL).

Er.ch ERFIS VAX is provided with 8 megabytes capacity. Each memory controller includes a s,

i

{

2-6 l

VL.4

.s' i

)

\\

)

request buffer that substantially increases overall system throughput and eliminates the need for interleaving in most applications, d.

Disc Memorv Twc types of disk memories are supplied for ERFIS system, the DEC RA60 and RA81. The DEC RA60 is a high capacity, rack mountable, removable-media disk with 205MB of formatted capacity.

It has a peak transfer rate of 1.98MB with an average access time of 50 msec. The DEC RA81 is a high capacity, rack mounted, Winchester disk with 456 MB of formatted capacity.

It has a peak transfer rate of 2.2 MB with an average access time of 36.3 msec.

Both disks are highly reliabi.e, have a 170-BIT error correction and dynamic defect re-allocation on spare sectors.

CN

)

(q /

e.

Magnetic Taoe Magnetic Tape units are manufactured by DEC model TA78. with the following features:

4 1.

Program-selectable recording at 1600 bpi or 6250 bpi 2.

9-track

.3.

Read / write speed of 125 inch /second 4.

Automatic tape threading 5.

Internal microprocessor - controlled diagnostics f.

Line Printers The line printers supplied with the system are manufactured by DEC, model LP32EA, and features:

1.

600 lines per minute, 64 character set p__

2.

445 lines per minute, 96 character set plotting speed (v) 3.

Form thickness adjustment 2-7 VL.4

4.

'64-character ASCII set 5.

Line width of up to 132 characters 6.

A choice of 6 or 8 lines to an inch selected by the operator or under program control g.

Matrix Printer LAl20 dot matrix printer / plotters are manufactured by DEC and feature:

l.

180 characters per second 2.

16.7 inch per minute plotting 3.

96 character ASCII set 4.

A choice of 6 or 8 lines to an inch selected by the operator or under program control 5.

Stand-alone installation C.

Transparent cover to protect from dust and reduce noise

\\

h.

System Console The processor's console consists of an intelligent micro-computer (LSI-11) with 16K bytes.of read / write memoty and-8K bytes of ROM, and RX01 floppy disc and a terminal for local operations and port for remote diagnosis. _The. console operator

~

uses keyboard commands for diagnosis, bootstrapping and incor-porating software maintenance modifications.

i.

Printer / Plotter The plo'Eter is Model V80 manufactured by Versatec with the

~

-following features:

l.

Printing' speed 1000 lines per. minute, 132 characters /line

-2.

200-points per inch resoittion

~'\\

3.

1.2 inches per second plotting speed 4.

Tabletop or stand-alone capability 2-8 VL.4 9

r

/

i

(

)

2.4 LNTELLIGENT GRAPHIC DISPLAY SYSTEM The Graphic Display System consists of Intelligent Graphic Display Terminals (IGDTs) to serve the function of display generators and con-soles. The resolution of these full graphics color units is 1024 by 768 pixels. The IGDTs have much more capability than display generators.

They are microprocessor based units that have

-. graphic display soft-ware and display format descriptions stored in semi-conductor bulk memory. The IGDTs translate variables supplied by tne VAX to update dynamic fields on displays and output the static portion of the formats f rom local memory when a picture switch is activated by the operator.

There is also local 2rapntcs editor sof tware un the graphics development IGDT to construct formats and upload them to the VAX for distributton to other IGDTs.

The IGDT is the primary user interface for the ERFIS. The display j,

system configurations for ERFIS are provided in singular or double i

k_,/

consoles, or a tabletop-mounted configuration. The console contains all s

portions of the display system (CRT, keyboards, local processor and cables) all in a compact console housing.

The following features are provided:

a.

Color CRT All color graphic CRTs are high resolutions (1024 by 768 minimum), nonglare, 20-inch, raster scan-type color video monitors. The CRTs have capability for 16 colors but the SPDS displays-will be designed with the eight major colors, b.

Keyboard Keyboards are standard alphanumeric keys, dedicated function keys (such as Page forward, Page back, etc.) and 32 operator assignable function keys which are generally reserved. for

/,__

x

)

top-level SPDS displays and other high priority plant unique displays.

2-9 VL.4

/N

-(

s c.

Displav Generation' The display system consists of an intelligent termin. L with 4 MBytes of local memory which has the capacity to stor i all of the SPDS displays plus 200 additional displays. Disi.ays can accommodate 96 characters per line and 42 lines per 1 :reen.

d.

Color / Video Copier A color video hard copy unit and interface is provide i to copy any of the video displays provided with the system.

opy size will be 8 1/2 x 11" and will allow copy of character:

or graphics. An input buffer is provided which reduces :RT lockup to 50 miliseconds. A color copy will be prod'uced in

-3.5 minutes depending on the image density. The color co; er is Model-TEK 4695 manufactured by Tektronic Company.

/m -

\\

\\

2.5 OTHER EQUIPMENT a.

DT07 UNIBUS Switch The DEC-DT07 Switch allows a section of the standard

.'N IBUS together with all of its peripherals, to be switched betwe :n two central processors..The DT07 can be operated either progi..mmably by the two computers in the system or manually with control I inel

[

switches. DT07 has a dead man timer which automatically t :ansfers the UNIBUS section from the failed VAX to the good VAX. e combina-tion of hardware and sof tware features-allows switching tc be performed automatically in the event of a computer failurr i

b.

HSC50 Hierarchial Storsee Controller The HSC50 is a self-contained intelligent mass storas sub-system that connects the two host processors via the Star :oupler to a set of mass storage -disks or tapes. The HSC50 communict.es with-host CPU's by way of the' computer interconnect (CI) and uses

[' )

IDigital's Mass Storage control Protocol for host communice; ions.

s/

' The HSC50 offloads utility operations such as disk shadowi ig,- volume 2-10

'VL.4

7w i

i 1

/

image copying and image backups from the host by performing these operations itself. To maximize througput, the HSC30 handles multiple drives and optimizes the physical operations such as track seeks and rotational positioning. -

c.

SC008 Star Coupler The star coupler serves as the common central connecting point for all elements on the Computer Interconnect (CI). The star coupler is an RF-transformer-coupled dual path passive device that connects up to 10 CI nodes. The unit distributes the signals and provides signal isolation between paths and noise isolation.

d.

Comouter Interconnect (CI)

The CI is a high-speed fault-tolerant dual path bus.

It allows processor nodes and intelligent I/O subsystems to be connected in a computer room environment.

A system of up to 16

, N nodes that allows any VAX processor node in the cluster to talk to i

I

'N_,/

any other VAX processor or node. A node is either a VAX processor or an, intelligent I/O system lir.e HSC30.

e.

Communication Links Communication channels are provided with ERFIS system to provide other CPU and data acquisition system data.

The data supplied through the communication channels are meteorological computer, process computer, suppression pool computer and meteoro-Logical data acquisition system.

/

\\

\\

x_ -

2-11 VL.4 t_z

.h t

TABLE 1 BRUNSWICK ERFIS EQUIPMENT LIST.

(FOR UNIT I AND UNIT 2)

ITEM QTY MODEL NUMBER DESCRIPTION

'l 2

DEC 785CA-AE Vax 11/785 2MB (64K chip).

Star Coupler and Data Channel 2

2 DEC 785CA-AP VAX 11/785 2MB (64K chip)

'. 3 '

2 DEC TA78BF Dual ACC Mag Tape 4

4 DEC RA60-CA 205 MB Removable Media Disk 5

4 DEC RA81-AA 456MB Winchester Disk o

.2 DEC HSC5X-CA Tape Formatter Data Channel 7

11 DEC LA120-DA Terminal Printer, KSR 8

4 DEC MS780-FC 6MB ECC/64K/MOS Memory 9

4

_DEC FP785-AA Floating Point Accelerator 10 8

DEC DT07-DR Radial UNIBUS Switch 2-Port 11 10 DED DMF32-LP_

Multipurpose Communications I/F 12-4 DEC DR11-W General. Purpose DMA I/F 13 4-DEC DW780-AA UNIBUS Adaptor 14 4

DEC Ball-KU.

' Expander Box 15

-4 DEC DDI-DK Expansion Backplane.

16

'4' DEC H9652-MF UNIBl!S Expansion Cabinet

- 17 2

DEC PDP11/24

. Minicomputer Interface 18 -

1 DEC LP32-EA Line Printer.

19 2

Versatec VS0-311' 1000 1pm, 200 ppi Printer / Plotter 20.

2 Versatec V80-27 Floor Stand for V80 21.

~ 2 Versatec V80-90 Accessory Kit 2-12

, VL.4

f x-x__-

TABLE 1 (Cont'd)

ITEM QTY MODEL NUMBER DESCRIPTION 22 2

DEC Power Distribution System 23 19 Toshiba 4000X Graphics Display Subsystem 24 12 Toshiba PRL 8305A keyboard with Function Deys 23 3

Toshiba MKZ8403A Slimline Floppy Disk Drtves with Portable Cacrier 26 19 Toshiba PPL83505A Color Monitor 20" 27 1

Toshiba Graphic Development Subsystem 2S 2

Ampex UNIBUS Controller 29 5

GE Dual CRT Console 30 7

GE Single CRT Console 31' 5

Toshiba Keyboard Switch 32 9

GE CRT Switch 33 9

Light. ave RS232 to FOC Converters (Pairs) 34 4

TEK 4695 Color Copier 35 4

, 4850 Analogic Formatters 36 38 4851 Analogic Formatter I/O Cards 4300 SERIES 37 15 4840 Analogic 7 Module Racks 38 13 4841 Analogic 2 Module Racks 39 13' 4860 Analogic Power Supplies 40 28 4810 Analogic Analog Input Modules 41 42 4820 Analogic Digital Inpur Modules 42 10 4830 Analogic Multiplexers

/

2-13 VL.4

4 l

l 1

TABLE 1 (Cont'd) i l

4 4

5500 SERIES 43 9

5520 Analogic Chassis i

44 2

5560 Analogic Expansion Chassis

[

j 45 34 AC4050 Analogic Low Level Analog Input Cards i

j 46 16 AC4600 Analgoic Temperature Cards 47 53 DC6200 Analogic Digital Cards 48 8

AC1562 Analogic Analog Output Cards 49 3

DC6600 Analogic Digitai Output Cards 1

l G

2-14 VL.4

-*--e-=y-*,v--ewp+yy,we-r..we,.9,+.p_

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

. ~. -

I L

F n

I u-.

3.

ERFIS SOFTWARE 1:

i 3.1 GENERAL ei i

U

'ERFIS uses common system software together with applications soft-ware to achieve its functions. This ~section briefly describes these t

i j

software elements.

s.

l' l

I

?!ajor sof tware subsystems are as 'follows:

t l

Name Function Tvpe Source

'I VAX/W.S Operating System System DEC HABITAT Data Base Management System System ESCA i

CDCI

. Common Data and Control Application GE 4

l Interface i

7 I

TRA Transient Recorcing &

Application GE Analysis i

(

RTAD Real Time Analysis and Application GE f'

Display PLA Process Log and Alarm Application GE I

3.2 -SOFTWARE REQUIREMENTS

.c p

All software meets the following general design requirements:

i All VAX software is written in either VAX-Il FORTRAN or D'gital; 1

a i

t.

[.

Command Larguage (DCL) with the exception of a limited number j

j:

of time-critical functions such as the DAS drivers which are written in VAX MACRO.

s I

1 t

1 i

l, 3-1 L

tyt.4 J

,*m-w wrE

% Ece s -*

.e.,.,

.e

c%.

_ [

\\'

(

b.

.The softwar'e system is modular in design to minimize the time and complexity involved in making a change to any program.

9 c.

All sof,tware is maintained in patch-free source code form on magnetic tape including libraries and programs required to perform a complete system recompile.

d.

All sof tware is compiled, linked, tested, installed and started via COMMAND FILE PROCEDURES. The procedures are entirely inclusive with options and the data necessary to convert a source code module into an executable module.

All software will have error handlers that will diagnose the e.

error that has occurred. No illegal response to a prompt will result in fatal termination of a function. The function will either re prompt or allow the function to proceed.

gg

-(

)

3.3 SYSTEM SOFTWARE

~

System sof tware has been designed to incorporate common sof tware elements having great versatility to enhance the capability for expansion. The system software has been modularized so that.it can be adapted to a wide variety of applications with a minimum of modifications. Following is a description of these common elements.

3. 3.1 -.

VAX/VMS Operating System VAX/VMS is a comprehensive, fast and convenient operating system which includes a variety of system management routines, software development tools, a file management system and 'other facilities.

It.

supports several languages and provides great latitude in the degree-of user control of computer operation.

The system provides an efficient and transparent system management.

.[

. capability for the control of ~ critical operations. Because it is a

\\

~

virtual memory system, (VMS), processes need not reside entirely.in 3 VL.4-r.

..=_ --

7 s-O[ \\')

a

.. \\f physical-memory to execute. VMS usea a 32-bit address to provide an extensiv'e virtual address space for user processes.

Portions not-

~

required at a given time can reside.on secondary (disk) storage.

Paging automatically transfers program from disk memory into main mem'ory as I'

needed so that programmers can write as if a program was entirely in I

physical memory..This simplifies software implementation and provides efficient use of main memory. Thirty-two priority levels are available to allot CPU time and memory residency for varying process criticalities.

VAX/VMS provides a wide variety of tools to simplify software development such as the symbolic debugger for debugging either FORTRAN or 1

assembler languages using the same statement numbers and symbols used in the source code. Other such tools include an interprocess communication e

ind control capability and a library of several hundred general-purpose programming routines. A record management system provides a choice of a

file organizations and access modes to accommodate a variety of types of data bases. Other facilities include a common command language for both

(

(

batch and interactive processes and support for many high-level languages and a query language.

VMS includes the following components.

o Virtual memory manager

(-

o Swapper o

System services o.

I/O Device drivers User' authorization control program o

o-Job initiator and symbiant manager o

Account manager Operator Communications Manager o

Error : logging and print utility o

Digital Command Language (DCL) command interpreter o

o-Monitor Console Routine (MCR) command interpreter o

Interactive and' batch editors s

, (v) o MACR 0 assembler t'

1 3-3 VL.4

.e

~

~

...__a-_.._,__

4

.Ai)

\\'

o Cross-referencing linker o

.' Library maintenance utility o'

Common Run-Time Procedure Library

_o Symbolic debugger.

o Record Management Services (RMS)

.o Files-11 1,

o Sort utility

~

o Software caintenance release update utility o

RSX-11 development package, which includes a MACRO-11 4

In addition. VMS contains a utility function, MONITOR, which is a system management tool that presents information on operating system performance. Thi> Junction helps the system manager to tune the system tor optimum performance.

3.3.2 DECnet-VAX

'p i (

With DECnet-VAX, a suitable contigured VAX/VMS system can partici-pate as a routing or end node in DECnet computer networks. The DECnet-VAX software, when installeo tr, a VAX/VMS system,-allows communi-cation between different, networked systems that use the same products.

I 3.3.3 VAX FORTRAN VAX FORTRAN is an optimizing FORTRAN compliler designed to achieve high exectuion speed.

It is an implementation of full-language FORTRAN-77, which is based on ANSI FORTRAN X3.9-1978..

The sharable, reentrant compiler takes. full advantage of the VAX floating point and character instruction set and the VAX/VMS virtual memory. operating I

system. It includes switch.selectable s"oport for programs conforming to the previous standard, ANSI X3.9-1966.

!('

+,-

3-4 o

VL.4

P 4

/O

(,)

' VAX FORTRAN also provides a number of extensions beyond the current ANSI standard, including language elements for keyed and sequential access to VAX RMS multikey ISAM files,and a set of data types beyond those specified for full language FORTRAN-77.

3.3.4 HABITAT Data Base Management System HABITAT is a data base system designed especially for VAX computers to provide efficient processing for engineering applications.

It creates a' total environment for tbe development and implementation of large software systems which involve man / machine interface and complex mathe-matnics - in engineering programming.

HABITAT is composed of many. parts of which man / machine interface and

' dita bass, management are the,two most visible.

It is designed to achieve

/

tiree pdimary goals:

6

)

Simplify 2nd structure initial programming for a complex system a.

I

' '/

s so that future' user coding additions for sophisticated analyti-cal functions may-be performed by application engineers and analysts rather.tdan a. separate programming staff.

j-t s

b.

Provtde and maintain a sof tware environment that promotes y

efficient mathematical computation.

,)1.

c.

fategrate man and machine with the application operational

• i i

3

=

x, 3

s process rather than have isolated tasks in the same machine.

I 3.3.4.1 HABITAT Components HABITAT'is composed of five major subsystems that form layer of

-programming underneath the VAX/VMS executive operating system.

The major h

elements of HABITAT consist of the following:

i

y

.. O iC

~

t

.,(g 3-5 W

VL.4

. i)fu l:

,\\

l a.

PHOENIX PHOENIX is the data base manager and data base definition tool providing virtual memory resident, permanent data structures for communication among programs and between programs and displays.

It allows for easy and prompt displays of data through its data classification into a pre-specified format composed of a unique hierarchy of tiers of data elements.

b.

EASEL EASEL is a picture compiler used to define man / machine communi-cation.

In HABITAT, data is transmitted to or accepted from the human user tnrough EASEL-created displays on CRTs and other I/O devices.

c.

FLO FLO provides packaged commands for installing FORTRAN programs

/~~'N in HABITAT, and for maintaining the source code and documen-

\\,I tation which support the programs.

s d.

RAPPORT RAPPORT is the on-line manager of man / machine activities, handling the construction of display /pages, entry of data.from display pages and processing of commands such as function key actions.

e.

PAN PAN is the' traf fic manager for application program activities, handling their initiation, termination and any operator communi-cations.

3.3.4.2 HABITAT Benefits Some of the advantages and benefits dertved f rom the use of IIABITAT are as follows:

,q I

. _/

3-6 VL.4

a.

Separation of data base and instructions. development thus reducing development effort and facilitating a well str'uctured-design.

b.

.Provides a common focus and means of information exchange for

. program developers, c.

-Aids maintenance and helps avoid errors due to unexpected effects of data base structure changes on existing program operation by oetecting inconsistencies between programs and data base versions.

d.

Enforces a common discipline for data base definition during development and maintenance phases.

e.

Ease of system enchancement via EABITAT tools for data base (PHOENIX) and MMI (EASEL) definition.

f.

Realtime performance realization through use of T?!S mapping

,V

. facilities for data base access.

3.4 APPLICATION SOFTWARE-i:

l

[

The application Software is divided into 4 major segments; CDCI, l

RTAD, TRA, and PLA. The major Application Software segments are further subdivided into major functions or components. This segmentation is based on functional content and structure for configuration management of-the software modules.

The CDCI, RTAD, and IGDT software are used to produce the ERFIS j

. Emergency Procedure Guideline (EPG) displays. CDCI and TRA software produce the pre and post event analysis reports.

PLA and CDCI software

[

perform the supplementary point processing, alarm, tog and display l

functions, h

v

[ -.-

3-7 l -

VL.4

(

t

1

)

~

The following is a description of the software:

3.4.1 Common Data and Control Interface (CDCI)

The CDCI Subsystem acquires and records plant sensor data, and controls the flow of data from the DAS to the components of TRA. RTAD, PLA and other subsystems to which it is interfaced.

3.4.1.1 DAS Interface Software Raw data is acquired from the GEDAC formatters by CDCI. The data is routed to disk for historical use by the TRA and to buffers in main memory for use of realtime poi.nt data process-ing by pLA. A major element is Central Data Acquisition (CDA) which handles the host processor interface with the DAS.

It performs the following functions:

,s

./

\\

1

\\ _,/

a.

Acquires and stores sensor input readings from formatters; b.

Receives and processes DAS diagnostic messages; c.

Processes user commands which control DAS operation, scan recording and event monitoring; d.

Processes output requests to drive trend recorders and operate digital contacts.

3.4.1.2 Man / Machine Interface (MMI)

Two modes of MMI are utilized; graphic and non graphic. The graphic mode utilizes the RTAD software segments and graphic processing capabilities of the IGDT. Non graphic mode is implemented using IIABITAT, the Video Terminal (VT) emulation

[

\\,

'N_/

3-8 VL.4

/

N

(

\\.'

( _,/

capabilities of the ICDT or an actual VT type device, and CDCI and PLA software.

In addition, communication at the VMS DCL level is accomplished by logging in as a VMS user.

The CDCI man / machine interface provides the Main Menu for personnel to select other man / machine interface functions for CDCI, RTAD support, PLA and TRA. The man / machine interface functions packaged in the CDCI are:

The CAS Control Interface Service function allows user to 2.

establisa tunctions and set up operatton for central processing such as loading a new sample plan or starting and stopping processing.

b.

The System Status Servtce function provides the user

{, ~,')

display or hardcopy outputs for DAS diagnostica and Bad Point ids.

The Analysis function Interface provides the ability to c.

select functions and enter user options for the Transient Recording and Analysis (TRA).

s d.

The RTAD Function Interface enables the user to perform support functions for the RTAD such as definition of terminal authorization for disp' lays and request reports of display definitions.

e.'

lielp functions are included that can be entered via poke

~

point selection from other man / machine interface displays.

3.4.1.3 Configuratton Processing f' 'N ERFIS Configuration Processing includes Data Base Editing,

\\,/

Validation and Generation sof tware.

3-9 VL.4

The Data Base Edit function allows user to:

a.

modify the number of GEDAC modules and the module strapping and interconnection information in the data base; b.

modify, generate and list the Point Definition Data Base and the Sample Plan; c.

Generate or list the contents of the Formatter Data Base.

..!.a.a Event Monitor Event.'!cnitor detects the occurence of trips, sequence-of-events and log triggers and activates processes assigned to handle these occurences.

3.1.4.5 Data Retrieval Raw point data is stored in system buffers and on the recording disk. The Data Retrieval sof tware accesses and processes this data on request from another sof tware process.

It performs the following:

a.

Point Validation and Conversion performed for each measured analog and digital input point, as appropriate, and consists of the following operations:

Bad Point Check Filtering Sensor Range Check Engineering Units Conversion Special Validation O

3-10 VL.4

j-9

+

%/

b.

Composed. Point Calculations performed for selected N

~

digital or analog input points. Simple combining of points using up to 30 operators (i.e. EQUAL TO, AND, o.

SQUARE ROOT, etc.) and operands (Other points or constants).

c.

RTAD Display Algorithms - evaluates display algorithms using routines developed for generating SPDS variables.

3.1.4.5 Raw Data Management The CDCI handles automatic archiving of processed ~ historical data from disk to magnetic tape and manual reload of magnetic tape history for disk review.

3.4.2 Real Time Analysis and Display (RTAD)

The RTAD operates on processed realtime point data changes. I t' distributes this point value and status data to.the IGDT for trans-lation and video update.

The role of.the RTAD is as 'follows:

a.

executes data processing by applying CDCI (Data Retrieval) to real time data to prepare it for RTAD outputs; b.

performs display processing by manipulating and transfer.

ring data from storage to the. IGDT; c.

provides display editing capabilities so_ user can build, modify, add to or delete displays in the system (resident in IGDT);

d.-

responds to changes in display selection frem the IGDT.

3-11 VL.4

a

/

3 1

3.4.3.

Process Loe and Alarm (PLA)

The PLA sof tware performs point processing. Realtime data is processed by the PLA utilizing components of the CDCI. The PLA produces a live data base of measured and derived point values and status. This.

data base is used by the PLA for logs and non graphic displays and.RTAD as a source of values and status for graphic displays.

Logs are produced by the PLA and output via the CDCI and (~MS.

The definiticns of logs are contained in a data base that is constructed using log editing capabili-ties.

Non graphic displays, such as alarms, summaries and group fispiavs. are generated by the PLA sof tware.

The following paragraph describes the general capabilities of the PLA

~

functian.

3.4.3.1 Potnt Processing and Calculation

,m

/

\\

l

\\,,/

a.

Analog Processing - All analog variables are converted to engineering units and alarm checked at their specified processing rates. The values and statuses are updated in the point definition data base.

b.

Digital Processing - All digital variables are alarm checked at their specified processing rates. The states and statuses are updated in the point definition data base.

c.

Composed Point Processing - Points which are functions of the points are derived at their specified processing rates.

The values, states, and statuses are updated in the point definition data base.

d.

Transformed Variable Calculations - Performed by trans-z-~s forming analog points using special calculations (i.e.

t

(

rate of change, periodic weighted average, etc.).

3-12 VL.4

4 e.

Pulse Input Accumulation and Conversion - Conversion of pulse inputs to engineering units and alarm checking is performed every minute.

3.4.3.2 Alarm Log and Display (ALD)

The ALD sof tware performs the following:

'.larm Log for printing record of all point alarms and a.

return-to-normil cecurrences.

l b.

Alarm Display of point alarms and nonpoint alarm messages giving alarm status and petorities.

3.4.3.3 Group Point Display Group Point Display provides and updated display of analog and digital values giving alphanumeric tabulation of selected point information.

+

3.4.3.4 Log Generation and Reporting (LGR)

The LGR produces the following logs:

a.

Special Logs of up to 40 groups of 32 points each which provide trends of selected point groups.

b.

Sequence-of-Events (SOE) Log of Ims resolution for print-ing all changes of state to assist malfunction diagnoses, c.

Post Trip / Scram Logs provide printing of pre and post trip readings for selected points to be printed after etther turbine trip or scram.

9 d.

Plant Periodic Logs for hourly, daily and monthly printing of up to 192 selected points.

3-13 VL.4

.-_-..,-,_---_,__.-._-,_.-,_,-._-.L

4 w w-(

)

3.4.3.5 Man / Machine Interface The PLA application sof tware operator interface functions include menu-based services for assisting the user in selecting points and groups and providing a variety of logs and alarm-based displays. The functions are selected from the CDCI System Function Main Menu. 'The available services include:

a.

Point Data Service b.

Log Editor / Generator c.

Log Services d.

Group / Point Display Service e.

Alarm Services f.

Summary Services g;

Trend Pen Servtces 3.4.4 Transient Recording and Analysts (TRA)

,, ~

l i

)

Repceting and analysis of transient data is acomplished by the

(

TRA using realtime or nistorical data supplied by the CDCI.

The man / machine..J.a r f ace so f twa re for the TRA ts part of the CECI.

The displays and interface to the video are done via HABITAT.

The IRA provides the ability to record and analyze transient raw data at time resolutions on the order of 2ms to 1 second.

The point data, events and selected logs are recorded on disk in a separate area from the raw transient data.

This software records operational events as they occur and measured and derived point readings at the frequency at which processing is performed in realtime or slower.

The TRA performs either real-time or historical data analysis as follows:

3-14 VL.4

t i

4 l

n I

i a,

calculates Conversion Constants used to convert raw data 4

to engineering units; i

i i

b.

generates either Time History plots or tabular trends for l

t selected data, t

i c.

does statistical or Fourier analyses; i

d.

provides First Function versus Second Function plots; i

e.

provides delta (significant change) recording of selected 1

stgnals; 1

i f

f.

does Sequence-of-Events recording including timing and i

l j

sequence of occurrence; i

1 l

g.

generates plotter commands to produce hard copy plots.

' 9 h.

provides for review and reporting of selected events frcm t

the histcrical files.

I i

I I

l I

i

?

O

(

3-15 VL.4 i

I 4.

ERFIS FUNCTIONS 4.1 GENERAL I

}

4 ERFIS performs the following functions:

a.

Data Acquisition b.

System '/ariable Processing SPDS - Safety Parameter Display System '

c.

d.

Technical Support Center (TSC) and Emergency Operations Facility (EOF)' Support e.

CRT Trending and Plotting

.'!onttoring and Alarming g.

Logging h.

Console Functions I

i.

Engineers Console Functions i

j.

Historical Data Storage and Retrieval k.

Alarm Display i

1.

Graphic Displays m.

Configuration Control 4.2 Data Acquisition ERFIS acquires data from the following sources:

i' a.

Plant 3ensors i

1.

Analog Sensors 2.

Digital Sensors a.

Status b.

Pulses from energy metering devices c.

Sequence-of-events i

s O

4-1 VL.4 l

)

a p

7-~\\

t

'1

)

b.

Process Computer c.

Meteorological Computer d.

Meteorological Data Acquisition System Suppression Pool Div 1 and 2 Computers e.

4.2.1 Analog Data Acquisition Analog data is collected by ERFIS at selectable sample inter-vals of 1.0,

.5,.1,

.04,

.02,.01, and.004 seconds.

4.2.2 Digital Data Acquisition Digital data collection is performed by ERFIS at selectable Intervals of 1.0,

.5,

.1,

.04,

.02,.01,.004,.002, and.001 seconds.

4.2.3 Sequence-of-Events Data Acquisition ERFIS acquires sequence-of-events inputs to enable a resolution of 1 millasecond with respect to relative order of occurrence.

-s 7

(

I 4.2.4 Pulse s /

ERFIS acquires pulse input digital changes f rom K'41 metering equipment.

4.2.5 Telemetered inputs ERFIS acquires data for the process computer, meteorological, and suppression pool via data links.

3 System Variable Processing ERFIS performs real time processing of measured and pseudo system variables. System variables are defined to be measured or derived variables which are assigned alphanumeric point identification.

4.3.1 Measured Point Processing ERFIS processes neasured analog, digital points, and pulse inputs.

,/-

(

t 4.3.1.1 Measured Analog Processing ERFIS validates, converts to engineering units, and alarm checks measured analog inputs in real time at selectable 4 -2

/

I

)

\\

intervals of 1, 2, 5, 10, 30 and 60 seconds. At least 400 points s-per second can be processed by EFRIS in real time.

4.3.1.2 Measured Digital Processing All measured digitals are validated and checked for alarm by ERFIS every second.

4.3.1.3 Pulse Inputs ERFIS validates and accumulates pulse counter digital input ct anges of state.

Every one (1) minute. ERFIS computes the pulse rate (i.e. power), and updates the one minute, hourly.

daily and monthly accumniators (i.e. energy).

4.3.2 Pseudo Point Processtng ERFIS performs processing of composed points, transformed vartables, and calculated vartables.

/O

(

)

4.3.2.1 Composed Point Processing Composed points are variables which are logical or arithmetic combinations of other system variables.

ERFIS ralculates, validates, and alarm checks up to 2000 composed points at the specified processing interval for each point. At least 400 composed points per second can be processed by ERFIS.

Both composed analog and composed digital (i.e. Boolean) variables are provided.

4.3.2.2 Transformed Variable Processing Transformed variables are time related functions of another system variable that are calculated periodically. EPTIS calculates, validates and alarm checks up to 1000 transformed variables at time interval over which the transformation is to be performed (i.e. I minute, 10 minutes, I hour, I day, I month).

Intermediate accumulation of data is pc tormed at appropriate subintervals. Transformations provided are rate of

/~~N change, integration, smoothed, sum, average, function weighted G'

average, maximtun and minimum.

4-3 VI. 4

i

,~

\\

\\

/

\\-

4.3.2.3 Calculated Variable Processing Points for which values are computed by ERFIS application programs or are received 'from other external systems, via communication links,'are classified as calculated variables.

ERFIS p.'ovides for up to 400 calculated analog and 200 calcu-lated digital values. ALI calculated variables can be vali-dated and alarm checked by ERFIS.

4.3.3 System Constants and Flags ERFIS provides up to 600 system constants and 400 system flags that can be defined and given point identifications, a.a SPOS - Safety Parameter Display System ERFIS continually monitors critical plant system variables and displays information to the plant operators in tne following func-7N tional areas of plant operation:

(

/

L; a.

Reactivity Control b.

Reactor Core Cooling and Ifeat Removal c.

Reactor Coolant System Integrity d.

Radioactivity Release e.

Containment Integrity The information is represented by color coded status indicators, bar graphs, trend pists, 2D plots, digital values and textual descrip-tions.

SPDS displays can be called up from any authorized console by means of dedicated function battons, entry of a display ID, or activation of a poke point, v

4-4 VL.4

l i

4.5 Technical Support Center and Emergency Operations Facility i

ERFIS provides consoles and peripherals in the TSC and EOF locations which can be given permission to access the same system information as an operator from the control room console, 4.6 CRT Trendine and Plotting j

ERFIS provides the ability to call up displays which show dynami-cally updated trends of the most recent 30 minutes of data.

The

[

types of trend displays are:

f 2.

X-T Trend

)

b.

X-Y Trend f

4.7

!!onitoring and Alarntng ERFIS performs system variable alarm monitoring and generates alarm messages. Alarm messages are printed and displayed. Analog and dtattal alarm processtng is performed as pirt of the System Variable Processtng (see 4.2).

The following checks are performed by ERFIS:

l l

l 4.

Analog Input Alarm Checks i

1.

Validity l

2.

Reasonability limits 3.

Warning limits 4

Operating limits i

5.

Significant (re-alarm) 6.

Deadband I

7.

Cutout I

8.

Operator Inhibit I

9.

Variable limits l

le 4-5 i'

VL.4 l

I

O b.

Digital Input Alarm Checks 1.

Validity 2.

Alarm state 3.

Cutout 4.

Operator inhibit c.

Pulse Input Alarm Checks 1.

Validity 2.

Warning rate limit 3.

Operating rate limit 4.

Significant (re-alarm) 5.

Deadband o.

Cutout 7.

Operator inhibit 8.

Variable limits 4.7.1 Analog Alarm Processing ERFIS alarm processes measured and pseudo analog points.

4.7.1.1 Fixed limits liigh and low ressonable (sensor) Limits, warning limits, and operating limits checks are performed by ERTIS for all measured and pseudo analog points.

4.7.1.2 Variable limits ERFIS calculates variable limits and uses the values instead of fixed operating linits for points which have variable limits assigned.

4.7.1.3 Alarm Deadbands ERFIS provides deadb. inning for all alarm limits in order to prevent cyclic alarming.

O 4-6 VL.4 L.

4. 7.,1. 4 Significant Alarming ERFIS provides realarming, as significant changes further away from or towards the operating range occur, for designated points which are in alarm.

4.7.1.5 Alarm Cutout 1

l ERFIS includes checks to suppress alarm notification for designated points based on the state of a specified digital input.

4^. 7.1. 6 Operator Controls ERFIS bypasses alarm checks tor points deleted f rom processtng, but not substituted or deleted f rom alarm check, by the ope ra to r.

4. 7..'

Digital Alarm Processing l

ERFIS alarms measured and pseudo digital points.

4.7.2.1 Alarm State I

ERFIS checks digital points for changes to and from the speci-fled alarm state.

4.7.2.2 Alarm Cutout ERFIS suppresses alarm notification for digital inputs that have cutout conditions satisfied.

4.7.2.3 Operator Controls ERFIS bypasses alarm checks for digital points that are deleted from processing and not substituted or deleted from alarm check by the operator.

4.7.2.4 Pulse Input Alarm Processing ERFIS checks pulse input rate values against specified rate limits.

!G 4-7 VI. 4

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

i i

L i

4.8 'Loening 1

ERFIS includes the following logs:

I j.

Special (i.e. group) Logs a.

4 b.

Post Trip / Scram Logs c.

Plant Periodic Log 1.

!!ouri r Log 2.

Daily Log l

3.

Monthly Log d

i 1.

Sequence-of-Eventa Log t

a.9 Console Functions 1

1 The ERFIS provides console functions to perform the following:

I l

a.

Data Acquisition Control h.

Tabular Trend Report f

c.

Time History Plot d.

Empirical Calculation of Conversion Constants e.

Statistical Analysis Report i

f.

Raw Data Management I

i l.

Archive

?

2.

Reload

[

g.

Point Data Display / Change h.

Group Point Display 1.

Special Logs.

t j.

Post Trip / Scram Logs l

l i

I i

4-8 VL.4

.. - - - - _ ~.

_ = =. - - -

~.. -

i 4

I k.

Plant Periodic Logs 1.

Hourly 2.

Daily j

3.

Monthly 1.

Graphic Displays l

l m.

Summarys 1

n.

Trend Pen j

o.

System Status Display j

l-p.

Alarm Display 1.

Display Callup 1

l 2.

Acknowledge Alarms i

3.

Category Callup j

4 Paging q.

SPDS Display 1

j 4.10 Engineers. Console Functions The'ERFIS Engineers Console is provided with the functions availa'le o

f rom the operators console plus the t'ollowing:

i l

1 a.

Ccnfiguration Processing 1.

DAS Hardware Editor t

l 2.

Sample Plan Editor 3.

Point Definition Data Base Editor 4.

Event Monitor Data Base Editor b.

Log Generator / Editor 1.

Special Log Editor 2.

Periodic Log Editor 3.

Post Trip / Scram Log Editor r

O t

L 4-9 VL.4-I

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

p

['I 1

~

\\

/

' ~ ' '

4.11 Historical Data Storage and Retrieval ERFIS performs historical data storage and retrieval functions as follows:

Historical Data Storage - E.RFIS performs the following a.

types of historical data storage:

1.

Scan Data:

Raw data collected and time tagged at scan mode sample plan frequencies.

2.

Delta Data:

Raw data changes collected and time tagged at delta mode sample plan frequencies.

3.

Engineering Unit (EU) Data:

Measured and derived EU data collected and time tagged at processing class frequencies.

'~

/

'N 4.

Transactior. Data:

\\ _,/

Alarms and operator point data changes recorded at time of occurrence.

5.

Archival Storage:

Historical data transferred to magnetic tape.

b.

Retrieval and Analysis - The following retrieva'

. tons are performed by ERFIS:

1.

Tabular Trend:

Printed or displayed tabular trend of specified varinbles over a designated interval.

2.

Time History Plot:

Plotted trend of specified variables over a desig-nated interval.

3.

First vs. Second Function Plot:

Plot of one variable vs. another.

4.

Statistical Analysis:

computation and printed report of statistical quanti-

_s

(

)

ties for a specified variable over a specified time interval.

4-10 VL.4

d 5.

Alarm History:

Chronological printed or displayed report of alarm over a specified interval.

6.

Point Data Change History:

Chronological printed or displayed report of operator point data changes over a specified interval.

7.

Archival Data Reload:

Transfer of a specified data set from magnetic tape to disk.

0;12 31 arm Presentation ERFIS performs the following fun:tions associated with alarm presen-tation:

a.

Alarm Display 1.

Priority categorization 2.

Notification of new alarms 3.

Cyclic update of current alarms 4.

Display pages within alarm categories b.

Alarm Log c.

Alarm Annunciation 1.

Audible Alarm 2.

Trouble Light Annunciation d.

Alarm Acknowledgement 4.13 Graphic Displays The ERFIS graphic editing and display capability for custcmer construction of other displays. ERFIS inciules capacity to incorporate 200 flow, electrical, hydraulics, instrumentation and control, or other type of diagrams.

4-11 VL.4

I:

'. i i

i @

4.14 Configuration Control i'

ERFIS performs the necessary functions to maintain system oper-l ability as follows:

)

s.

Interprocessor Communications 4-i j

b.

.'se s ta r t

}

1.

Partial Restart i

2.

Full Restart c.

CPU Failover 1.

Manuai Failover 1

Automatic Failover i

6 d.

Device Failover

}

l 1.

Automatic Failover i

^

.'!cnual Restoration d

l 4

j i

4 9

4-12 VL.4 i

i L

t i S 1

h i.

i T

l t

t.

i l

)

l 4

i i

i l

i 1

I to SERIAL: NLS-84-506 i

i l

i I

I l

I 4

l r

I

\\O i

t k

I i

i

+

i,

[

t k

i.

b i

t i

i I

I r

h e

f i

t 1

-, ~... -.

W i --

s_

"\\

)

CAROLINA P0utR & LIGHT CCW ANT

\\,jf WIun$wlCK $ TEAM titCfRic PtANI

• Umil 2 SAffit PARAMtita OISPLAY $Y$ft4

,,,tpCINttRING & itFttWNTATION $ottoutt Y'

f984 196S 1986 1967 1996 34$040JFuA 1J49040JruAu3JA$0NOJFu&uJJASONOJFMAu8 f

A Ltift4 CF 6NftNT 1

$Af A ACQUlSITION MAf0WAAtt M SIGN M51G4 F#EEZE d

assevita MAfewant M$1GM CE$lGN FattZt A

$0FTWant M $ica A

$vsttu Citivtet 7

(

PtsNT ucciFICAtlCN PACKAGE E.

A.

~

tru.ouT Act att AttD CON $fRUCit0N j

cuf act att Arto CON $fRUCflC4 d

OtLitte FACTUtf it$ff0 $0Finant ClouG/ft$? SOFTWARE Eltit8

$PC$ &tRat10HAL W OFR$ f4Ath(f)

'v A.Ait...

.r.,ES, 4

l

?

4 BRUNSWICK-2 (First Brunswick Installation):

i

1) The outage related construction will be accomplished during the maintenance outage, presently scheduled to begin in December 1985.

2) The installation will be complete with operators trained three months after reload 6, presently scheduled to begin in December 1986.

3) Following this completion, with the unit operational, there will be a six month (4400 hour0.0509 days <br />1.222 hours <br />0.00728 weeks <br />0.00167 months <br />) test of the system's availability (e.g., downtime, equipment failures, etc.).

t

)'

\\v/

• e

d f

i 4

I i

)

!e

{

i t

i i

i I

I I

l l

i i

to SERIAL: NLS-84-506 r

F l

r r

t

?

O

?

i l

l l

i i

l l

I f

L P

CAA0tlNA P08tR & LtGsef COWANT GRUNSWICE $ft AM (LtCIRlC PL ANI

• UNil I

$AFiff PAAAMEfta 011PL AT tv5fte

\\

teGluttRING & IrttMENTAf eOc $QatDutt

,,.A l...

J J A 1 0 m 0 J F u a u J J A $ 0 e6 0 J t u A u J J A 5 0 m O J F u A u J J A 5 0 N O J p u a u J J A S 0 x 0 J p u A = J J A 5 0 0 Lt?fta 0F IWitmi A ciaiA ACQUI58i1088 MAm04AAte MllG4 OtStone rattts A

'cos'Utte MAf0WAAt:

DESIGN OtSIGN fattli 10Fiv'AAt 0(1864 FACTORY OstCacui A

ST5itu Ottivttf Plauf DColflCATION PAOtAGE:

MtPAA Afl0if ocu-0UTAct CowliRUCTION:

DufAGE CON $1RUCI$0Ng CEOUG/ftli.

SCTfwAAt (11ft):

O 1705 O'tRAflCMAL D

W/CPjt1 TRAlp(Da AfAILA8illfi filf l

BRUNSWICK-1:

1) The outage related construction will be accomplished during reload 5 presently scheduled to begin in April 1987.

2)

Prior to the outage the software will be tested on site using simulated inputs (dotted line on scheduled).

3) The installation will be complete with operators trained three months after reload 5 presently scheduled to begin in April 1987.

4) Following completion, the Brunswick-1 system will be tested for availability over a six month period.

O tw h

" =

k 6 -

• mo

. =. =..... - - _.

4 6

1 4

1 i

l

!!O 1'

1

?.

l

~

t l

i k

1

?

l to SERIAL: NLS-84-506 f

l f

i 1

t i

I i

9 1

I I

I f

l f

r i

i a

I I

[

i I

O

([.

,i a

m

- J

[I.

(

, E(MAN FACTORS ENdINEERING (HFE) IMPLEMENTATION V

A.

GENERAL 1

4

- A Humin Factors Engineering Implementation plan is a part of the design grocess for the ERFIS in order to ensure that the ERFIS meets its intended

'-objectives and accommodates its intended users. The activities in the HFE implementation plan are iterative in nature.

Designs are developed based on Human Factors Engineering principles, then reviewed to assure that those principles have been properly implemented.

Results and recommendations from reviews are then evaluated for impact and action

.y plans are devaloped for incorporation into the design.

3 s?

The ERFIS HFE plan is an integral part of the design and review of the (j

s

" 4* *

, system as a whole as well as the design and review of the more detailed aspects.of the system. The plan generally consists of activities such as

( -g

' definition of HFE requirements, reviews, testing, analysis, and JT verification activities. These activities can be separated into the

'.,,.y followinq specific major areas:

1

}

1.

Definitiot$ of System Functional Requirements

%, i

/ j' 2.

Task Analysis 3.

Man-Machine Interface Development and Peview

-[

4.

Verification and Validation i

/

5.

Personnel Training The following sections describe in more detail the specific tasks which are performed in order to provide a comprehensive implementation of the overall HFE plan. Specific tasks consist of both plans for future

, implementation as well as previously performed activities which can~be related specifically to the ERFIS.

B.

DEFINITION OF SYSTEM FUNCTIONAL REQUIREMENTS The first task in the HFE plan is the development of system level requirements. The system level requirements will be based upon:

1.

Interfaces to systems outside of the ERFIS j

'2.

Codes; standards, and regulatory requirements 3.-

AssuEptionsand' constraints 4.

Definition of what the ERFIS is to -perform and what the user is to perform (functional allocation)

.5.

Purpose -of the ERFIS (mission statement) 4

\\j i /

.h

)

.(927 MAT /ccc)

)

., I N e

b 7w

' ['~

U The system functional requirements define what the ERFIS is to do, what

)

performance is expected and what part of the system consists of user 7( '

interaction.

These requirements provide the basis for comparison of other activities.

Reviews of the ERFIS are performed against the fulfillment of the requirements developed in this activity. The system level requirements are issued in a controlled document.

C.

TASK ANALYSIS In addition to definition of functional requirements, specific requirements related to the performing of time critical plant procedures i

are developed.

This activity consists of defining the specific

't requirements related to the performance of the BSEP Emergency Operating Procedures (EOPs).

The task definitions from the BSEP System Function and Task Analysis, a part of the BSEP Control Room Design Review effort, are used to define the specific tasks an operator performs in order to follow the BSEP E0Ps.-

These task descriptions are then used to examine:

1.

The content of the BSEP Safety Parameter Displays, 2.

The user interface required to access the BSEP SPDS information,

-n

'[V) 3.

The usability of the data for an operator following the E0Ps.

The analysis of tasks is used similarly to the system functional requirements, in that.it provides a basis for any review which will-compare the actual ERFIS implementation to the fulfillment of its intended purpose.

Documentation includes the task descriptions (from the Control Room Design : Review) as well as an analysis of the capabilities of the SPDS portion of the ERFIS to aid in the performance of the E0P tasks.

-D.

MAN MACHINE INTERFACES 1.-

General The purpose of the man-machine interface portion of the HFE plan is to assure that the hardware used in the ERFIS is consistent with the

-intended. purpose and function of the system.

This assurance-results from the use of-HFE principles throughout the design process as well as systematic review procedures. The following specific activities are performed in order to implement this purpose.

2. ' Hardware Location Review A hardware location design. review is performed in order to ensure.that-the placement of the hardware provides the users with a useable configuration for performing the activities for which the ERFIS was r~

designed.

In addition, the review ensures that hardware will not be q )g t

.q (927 MAT /ccc)

L

~

^

placed in such a manner as to prevent users and other affected s

(

)

personnel from performing other personnel duties which are unrelated to the use of the ERFIS.

3.

MMI Hardware HFE Review In addition to-location, the MMI hardware design is reviewed against an appropriate HFE checklist (such as NUREG 0700, Reference 5) in order to ensure that the hardware properly accommodates the intended user. The review of the hardware design is documented in a checklist fashion with appropriate summaries and conclusions of any notable results.

E.

HUMAN FACTORS ENGINEERING VERIFICATION AND VALIDATION 1.

General The " Verification and Validation" activities of the HFE plan are an ongoing part of the entire design process for the ERFIS. Some of the activities in verification and validation must be completed in the early stages of the design process whereas others are completed only in the final stages of the project.

The major features of the HFE portion of verification and validation are described below. They include:

a.

Test Requirements Development i

5.__,

b.

Static HFE Review c.

Dynamic Review d.

Integrated Hardware /Sof tware Validation Test 2.

Test Requirements Generation The development of test requirements is performed parallel to the " Man Machine Interface" activities and the " Training" activities. The system functional requirements are used as the basis for the development of tests and procedures which verify and validate, in general, the ERFIS functions, and specifically the BSEP SPDS displays. These requirements are issued as controlled documents. The implementation of these requirements is performed during the integrated hardware / software test as described below in Section E.5.

3.

Static HFE Review The BSEP SPDS displays are examined in a specific HFE review for comparison to basic human factors principles (such as those defined in NUREG 0700) and a determination of usefulness to the operator by using the tasks from the Control Room Design Review. This type of review was previously performed on the G2neral Electric generic Emergency

,e~'s.

Response Information System (ERIS) displays using the BWROG Emergency

[

)

\\m.,/

(927 MAT /ccc)

.),

/N Procedures Guidelines. The results of the generic study were

(' ')

favorable and useful display improvements are being incorporated into the BSEP SPDS displays.

4.

Dynamic Review An extensive dynamic review was performed on the General Electric generic ERIS displays at the BWR/6 simulator in Tulsa, Oklahoma. This review consisted of a HFE check using a checklist approach similar to that described in Section E.3, the administration of 12 unique simulated transients, operator / system performance evaluations during the transients using the Perry Nuclear Power Plant E0Ps and data collection for the measurement of the usefulness of the ERIS SPDS related displays.

In general, the ERIS was perceived by the operators as a significant aid in plant control during emergencies and was judged as presenting an exceptional source of synthesized / centralized information with regards to plant performance.

In addition, recommendations from the dynamic review are being incorporated into the ERFIS displays.

5.

Final Integration Testing The final activity in completing the ERFIS design is the integration of hardware / software and the user in a final test scenario. This s,

test, also called " Factor Acceptance Test," verifies that the system fs has been correctly designed for the user and that ERFIS has. met its s,_-

intended purpose. This test is based on the functional system requirements and the previously developed test plans / procedures.

F.

PERSONNEL TRAINING 1.

General Traising plani /s~chedule~s',-~ courses and course content are developed

~

parallel to the other llFE activities of " Man Machine Interface Development" and " Validation and Verification." Again, training is developed based on the functional system level requirements and specific tasks with respect to the BSEP Emergency Operating Procedures. Basically, there are two major areas of training which are required. They are:

a.

Use of ERFIS b.

Integration of the ERFIS into the Brunswick Steam Electric Plant 2.

ERFIS Training Courses are being developed to train the users of the ERFIS in the use of the system, use of man machine interface components, theory of operation, and maintenance. Training plans / schedules use the system f "x.,

functional requirements to define the courses, course content and

(

)

course outlines for the use of the overall ERFIS.

ss_/

(927 MAT /ccc)

+

'~ E 3.

Integration of the ERFIS into the Brunswick Steam Electric Plant Whereas the courses of.Section F.2 are developed for how to use the ERFIS, the courses defined in this section are developed to train users for how-to use the ERFIS in relationship to the Brunswick Steam Electric Plant. This training plan uses the tasks from the BSEP E0Ps as a basis to train users in the use of the ERFIS with respect to the

. Emergency Operating Procedures. The courses of this section are developed to build on the courses of Section F.2.

The above training is documented by definition of courses, course content, course outlines, and schedules.

. The Human Factors Plan for the ERFIS is developed to -fully consider the user as a part of the system as a whole. By assuring that the individual components of the system have been reviewed for HFE considerations and the components have been integrated on the system

. level, the ERFIS will be a functional and useful system.

(

I '.

i i.-

l

[.

i '

l I

I i:

s f

i i-i' (927 MAT /ccc)

1

\\@

4 J

A t

4 i

s t

.i l

1 l

i' i

I i

i.

to SERIAL: NLS-84-506 i

a l

e i

l 1

4 f

l 4

t d;.

,i a

W I

}

d l

f i

t.

h 5

i 1

i i

b i

4 I

0 L

1 4

1 i

i l, -

h E

tO F

5

.i

(

i.

t t

s e w v-wwwww p,

.. -.