ML20153C484

From kanterella
Jump to navigation Jump to search
Non-proprietary AP600 Instrumentation & Control Hardware & Software Design,Verification & Validation Process Rept
ML20153C484
Person / Time
Site: 05200003
Issue date: 05/31/1992
From: Birsa J, Reid J
WESTINGHOUSE ELECTRIC COMPANY, DIV OF CBS CORP.
To:
Shared Package
ML20153C365 List:
References
GW-JIR-002, GW-JIR-2, WCAP-13383(NP), WCAP-13383(NP)-R, WCAP-13383(NP)-R00, NUDOCS 9809240104
Download: ML20153C484 (22)
v • d • e


Text

- _ - _ _ _ _ _ _ . _ . _ _ _ _ . _ _

AP600 DOCUMENT COVER SHEET Form Ga202C(W92)[WPxxxic1D) ape 00 DB USE ONLY Pages Anached 22 eaae nu AP600 DOCUMENT NO. REVISION NO. DATED CONTROLLED COPY NUMBER: N/A GW-J1R-002 0 5/31/92 ASSIGNED TO: N/A

, ALTERNATE DOCUMENT NUMBER: WCAP-13383 CH N DESIGN AGENT ORGANIZATION: WESTINGHOUSE PROJECT: AP600 TITLE: AP600 Instrumentation and Control Hardware and Software Design, Verification, and Validation Process Report WORK BREAKDOWN #: 2.2.8 This secton incorporates the following desip changes DCP WRev.:

t d

(C) WESTINGHOUSE ELECTRIC CORPORATION 19f} .

A cenes is reserved b the U.S. Govemment under contract DE-AC0340SF18405.

MENT LIMITED RIGHTS:

(A) These data are sutwrutled with imited sights under Govemment Contract No. DE-ACos-eOSF18495. These data may be sopro&ced and used by the Govemment eith the express limitaban hat they wE not, wihout written pommenen of he Contractor, be used for purposes of manufacturer nor dscioned outade the Govemment; except that he Govemment mry daciose these date outado the Govemment for the fotowing purposes, if any, prended that the Govemment makes such dsciosure subject to prohbiton agemet further use and dedoeurs:

(1) 1his ' proprietary data' may be decioned for evaluabon purposes under he seetncem above.

(11) The 'propnetary data' may be decioeed to the Electnc Power Reseanh inattute (EPRI), electnc utiMy representseves and heir d#ect censultants, excludng droct commen:ial compettors, and he DOE Natenal Laborsbrios under the prohdutons and restnchons above.

(b) This notes shal be marked on any reproducton of heee data, in whole or h part.

O WESTINGHOUSE CLASS 3 (NON PROPRIETARY)

EPRI CONFIDENTIAL./ OBLIGATION NOTICES:

NOTICE:

10 2O s%4 Os O CATEGORY: A B OC ODDE OF 0 0 DOE CONTRACT DELNERABLES (DELIVERED DATA)

Subject to apoczGed exceptions, declosure of his data is restncted until September 30,1996 or Design Cortlicabon under DOE contract DE-AC03-90SFtS495, whichever is later.

ORIGINATOR Si ^ TURE/DATE l

J. J. Birsa AP600 RESPONSIBLE MANAGER /

hNk J. B. Reid A SI/// 2 9809240104 980812 PDR ADOCK 05200003 A PDR _

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

l -

l 1

Form 5e202C (342)

EPN CONRDENTIAUTY / OBUGADON NODCES NOTICE 1:

The data h his document is subgect to no cont.A-f ^/ obhgatons NOTICE 2:

The data in his document is proprietary and con & dental to Wesdnghouse Electric Corpora 6cn and/or its Contrachts it is forwarded to recquent under an ebEgation of Con 5dence and Trust for Emited pisposes orWy. Any use, dieciosure to unauthonzod persons, or coppng of his document or parts hereof is prohbted except as agrood to in advance by he Electne Power Research insbtste (EPRI) and Weshnghouse Bactric Corporanon. Reapsent of his dets has a duty to ingam of EPRI and/or Weshnghouse as to he uses of the informaton contained herein hat are permend.

! NOTICE 3:

The data in his document is pmprietary .nl con 6dential to Westinghouse Electric Corpora 6an and/or its Contractors it is forwarded to mapient under an obEgation of Con 5dence and Trust for use only in evaluaton tasks specificaNy authorized by the Elecinc Power Research insetute (EPRI). Any use, deciosure to unauthonzod persons, orcoppng his documsat or parte thereof is prohhted except as agreed to in ad anos by EPRI and W O.# : - Bechte Corporaton. Recgnent of this desa I has a dsty to hquire of EPRI and/or Wesenghouse as to he uses of the hionnation contained homin hat are permited This document and any copies or excerpts hereof hat may haw been generated are b be mhmed b Wesenghouse, drecer or I through EPRI, when meested to do so.

NOTICE 4:

The data in his docurnent is proprietary and contdential to Westnghouse Electnc Corporation and/or its Contrachts It is i being revealed in conAdence and trust or$ b Employees of EPRI and to certan contactors of EPRI for limited evaluation tasks authonzed by EPRt. Any use, dsciosure b unauthorized persons, or copyng of this document or parts hereof is prohinted. This Document and any copies or excerpts hereof het may have been generated are b be retumed to Westnghouse, droc8y or brough EPRI, when requestou to do so.

NOTICE 5:

The data m this document is proprietary and confidential to Wesenghouse Electnc Corpora 6cn and/or its Contractors. Access to this data is yven in Con 8dence and Trust or# at Westnghouse facibles for limited evaluation tasks asaped by EPRI.

Any use, dsciosure to unautonzod persons, orcoppng of his document or parts hereof is prohbled. Neiher this document

s. e not.-anyw excerpts<a herefrom are b', - be rymovedg

. g,,nWeetnghause w fecGines. @, g . .a v,n.<

tp ,q j

, EPRI CONRDENTIAUTY / 09UGAT10N CATEGORIES ,

. i, s,,.g~ ig CATEGORY *A* (See Delivered Data)

Conents of CONTRACTOR Fotoground Data hat is contamed h an issued reported CATEGORY *B' (See Detvered Data)

Conents of CONTRACTOR Fotoground Dats hat is not contamed in an issued report, except for computer programs CATEGORY 'C' Conents of CONTRACTOR Bodypound Desa emospt for computer programs CATEGORY *O' Conants of computer prograrse & ' -;+1in the course of performing he Work.

CATEGORY *E' Consets of computer programs developed prior to the Effeceve Date or after the Efiscove Dase but outade he scope of he Worti.

CATEGORY *F" Conents of admmestreeve plans and admeestrative reports.

DEFWeTIONS DEUVERED DATA Conmets of documents (e.g. spea6 cations, drawings, mports) which are generated inder he DOE contract DE-ACos-90SF18495.

r 1

0010.FRM

i AP600 Instnimentation and Control Hardware and Software Design, Verification and Validation Process Report j

i N

! able of Contents:

1 j troduction 2.0 Essential Features of the Design, Verification and Validation Process 6 I

2.1 Verification Process Integrated with Design Process 6 2.2 Modular Design 6 j

23 Incremental Verification 6 l 2.4 Design Stressing 6 2.5 Verification and Validation Team 6 2.6 I.evel of Verification and Validation 6 j

3.0 Documents defined by the Design, Verification, and Validation Process. 7 l 3.1 System Design Documents 7

! 3.1.1 System Specification Document j 3.12 System Design Spedfication j 3.13 Hardware Design Requirements i

3.1.4 Software Design Regem.mts 'f 3.2 Module & Assembly Design Documents ' 8 i 3.2.1 Hardware Design Spedfications 3.22 Software Design Spedfications 33 Module & Assembly Implementation Documents 9

! 33.1 Hardware Implementation Specification 332 Software Implementation Speci6 cations i 333 Reliability Analysis Report 11 3.4 Venfkation and Validation Plan j 3.4.1 Hardware Verification Plan 3.4.2 Software Verification Plan

3.43 System Veri 6catkn Plan l 3.4.4 System Validation Plan 3.5 Moduk & Assembly Verinen*=s Reports and Procedures 12 3.5.1 Hardware Veri 8 cation Test Procedures 3.5.2 Software Veri 8 cation Test Procedures 3.53 Hardware Test Results Report 3.5.4 Software Test Results Report 12 3.6 System Irdegration Description Documents '

3.6.1 System Implementation Speofication 14 3.7 System Verification & Validation Documents 3.7.1 System Test Procedures

- 3.7.2 Test Results Manual 15 3.8 Product Documentation Revision 0 GW-J1R-002 May 31,1992 i

AP600 Instrumentation and Control Hardware and Software i Design, Verification and Validation Process Report i

i 3.8.1 System Interfacing Documents 3.8.2 System Installation Documents

, 3.83 Maintenance Manuals I 4.0 Document Cross-Reference 17

.' 4.1 Documents Specific to Hardware 17

4.2 Documents Speofic to Software 18 j 43 System level D==ts 19 I'

5.0 References 20 t ji of Figures: d r )

l Figure 1 Design, Verification, and Validation Process 3

, r Tigure 2 System Development / Integration Procesp(SYSDIF) 4

, /

hgure 3 Westinghouse AP600 Implementation / Verification Process - Summary 5

?

1

+

1 i

J

'?

Revision 0 GW-J1RM May 31,1992 ii

AP600 Instnunentation and Control Hardware and Software Design, Verification and Validation Process Report 1.0 Introduction His document describes the design, verification and validation (DV&V) process that has been established to confirm that system functional requirements are properly and correctly implemented in the Instrumentation and Control Architecture of the AP600. This DV&V Process will be applied throughout the Instrumentation and Control Arclutecture in graduated degrees as reqmred by the relationship of the specific system to safety needs.

Verification refers to the process of determirdng whether or not the product of each phase of the Instrumentation and Control System desi6 n process fulfills the requirements imposed by Previous phases.

Validation refers to the process of testing and evaluating the integrated Instrumentation and Control System to confirm compliance with the fuu*=t performance, and interface requirements used to desi6 n it he term, Instrumentation and Control System, as used in this document, refers to the integrated hardware and software design and equipment, confonnp* g to the desi 6 n that is provided to implement a subset of the functional requirements forgplant.

The DV&V Process established by Westinghouse is an engmeering approach used to ,

development of high quality hardware, software, and system desi6ns conformmg to custo ,

regulatory, and Westinghouse requirements. He DV&V Process was established as a me to direct the necessary activities in the design, implementation, venfication, and vahda , of instrumentation and control systems. The DV&V Procedure that implements this promss defin, es the documentation item requirements, standards for the content and format of each documgnt, and the interactions between the d.4.ent activities and the venfication and validd8an activities. An objectrve of the DV&V Process is to verify that documents are generated that are correct, complete, and without ambiguity, ne document titles, document definitions, and terms used are s&M for consistency with industry standards, Westinghouse standards, and regulatory / licensing pA c The DV&V Process stresses a "Desi 6 n for Verification" approach throu6hout the hardware design, software design, and system integration aspects of the project. nis concept requires:

that the system design process is able to readily and immediately demonstrate that the system desi6n completely and correctly inw:orporates the design requirements.

that the module, assembly, asi subsystem design methods, including software modules, provide featum so that the resulting design of the module or assembly Revision 0 GW-J1R-002 May 31,1992 1

AP600 Instrumentation and Control Hardware and Software Design, Verification and Validation Pmcess Report '

1 a _

w

--__ _ n e

// ,

/ _____

SYSTEM DEVELOPMENT / INTEGRATION 3ROCESS ll ":= ' (SYSDIP) i

- * = =

-* C t--

ll Ct_ C _a 11 (BASED ON FIGURE 1.1 OF DOCUMENT C&PGST[NX)1.REV 5. 5/10/90)

I o

, -ii - _ _ .

l Ii ",

:,t .._ -._ i i ==- m_ s-ll ~ '==

._. !l 1I =- l' --

+ < ,--r < -v "'v-3- **" "*"'*** I 3 *i_h== _t iT_.E_t

.- l t 1- I ! _",",,,

I I '""

II I .=_ """

3 I

- 1I II J**'"'

-*"I

~ ~ I-*"C-

'I C .._.m  : -= =

II i d_5 _ _ _I.d_ Y _ _ _I 1

=.

!! O~

  • l llg! ~

iI l.== .5  ! :~~~ ::-

! E=- !: E"-

i-

, Il I ""*" 1^***'

gg 1

g, i .

i 1I 7 gg -ca='=' I ===

  • U

==

!i

ll li i

~l

-i ll - = - ,i = _  :

  • g g

iI gg IlI i

I I

n _ = ._ _.

II l =-

I:.=='=

i ===_

I l3 -aa.

l

!g ii I I -=== 1

 : i l II l I I l -_________s t gi .

, l...___- ., I______ ___ _.L_____ p________-- I 3 . __..._....._____. __._____,.___ ..._____.._________...__.._ _ _ _ -...______...___ ...._____________.____.---.....-; y_,

Figune 2 System E .Q .c-Wntegration Process (SYSDIP)

Renson 0 .

May 31,1992 GW-J1ROR 4

6

3 AP600 Instrumentation and Control Hardware and Software -

Design, Verification and Validation Process Repon F

WESTINGHOUSE AP600 IMPLEMENTATIONNERIFICATION PROCESS -

SUMMARY

7E

/\

/ \

,_ INPtfrS  ?

OUTPUTS -

a a' .

4

'+ TROUBLE REPORT

. VER TION

~

i j ACThTY

)

TnoueLE nEPont PftOOLEM PEPORT PROBLDE REFORT

~

~

. I I p;m REQUIREMENTS VALIDATION DESIGN ACTNITY

? B **""

Figure 3 Westinghouse AP600 Implementation / Verification Procen - Summary Revision 0 GW-J1R-002 May 31,1992 5

.i .

l AP600 Instrumentation and Control Hardware and Software l Design, Verification and Validation Process RepoIt l

2.0 Essential Features of the Design, Verification and Validation Process 2.1 Verification Process Integrated with Design Process The Design Process and the Verification and Validation Processes are integrated into the overall DV&V Process. Hardware and software that conform to the DV&V Process have incorporated into their design speciabd features that enable, enhance, and support the verification process.

2.2 Modular Design An implicit feature of the DV&V process is the philosophy of modular design for both the '

hardware and software used to implement the Instrumentation and Control System design.[This provides readily available, pre verified parts for use in assembling the system].

2.3 Incremental Verification The DV&V Process is invoked on the smallest lurdware and software entities for which functional specifications can be defined and establishey[Verificatien and validation of as-semblies, composed of these tities, becomes a test off . ops interfacing and usage of already verified and validated 2.4 Design Stressing .,

Each module and assembly is tested over its possible (design) range of use, providing a higher level of assurance than is possible at the inte5 rated system level.

2.3 Verification and Validation Team ne Verification and Validation process is puferuied by independent reviewers who meet the requirements and have the responsibilities defined in the published, QA arda, division and department procedures documents.

2.6 Level of Verification and Validation The level of Verification and Validation performed on individual modules, assemblies, subsystems, and complete systems is commensurate with the safety classification of the system and intended use in the plant. His level is established for each module, assembly, and subsystem as part of the system design process, based on the system design requirements.[n_ e results of this Verifica d Validation level identification process are an integral part of the system design documen ,

Revision 0 GW41Rm2 May 31,1992 6 i

\

1

AP600 Instrumentation and Control Hardware and Software Design, Verification and Validation Process Report

!P 3.0 Documents defined by the Design, Verification, and Validation Process.

).

4 De documents described in this section are controlled by, and are essential parts of, the Desi Verification, and Validation process.

4 3.1 System Design Documents j t,

i 3.1.1 System Speofication Document t i

j I The System Specification Docurnent, as defined by Program Operating Procedure AP- 1 m Reference 5.1, establishes the basis for the system design. This document ad i the apphcable codes, standards, and functiorn! requirements and acts as a design

. definition document. This document establishes applicability and reqmrements to meet . -

single failure, diversity, electrical separation, and other applicable critaria, ddines

! environmental and power source envelopes, establishes requiremenu related to access control', redundancy, independence, identificatien,. and test capability. It defines i

requirements on system inputs and outputs, sysjem safety anaification, reliability, i vl establishes quality assurance, verification and vilidation, and environmenta) quahficat NIuirenwnts, j 3.1.1.1 System Functional Requirements Document

.t i ,

The System Functional Requhr.u.ents Document, in conjunction with the

Functional Diagrams, defines the perforrmance requirements for the plant

, pukction and control functions cf the plant Instrumentation and Control System.

his docuirw:nt identi6es the plant parameters to be monitore:1, the puwction and control algorithms to be pngs.ed, and operator interfaces, such as alarms and j  ? indications. De Functional Requirements Document also specifie.s instrument d

I and channel ranges, accuracy requireewnts, and time response requimnents.

I I 3.1.1.2 System Blod Diagrams i

l The System 'dlod Diagrams represent a top level depiction of the system ,

architecture and its interconnections, and pnwide a descriptien of the system p architecture.

}

1 h

2 Access control includes requirements for the type of menay buch as MOM, EEMOM ed l

to be used for object code and various types of system data.

Revision 0 GW-J1RM2 May 31,1992 7

l AP600 Instrtunentation and Control Hardware and Software

Design, Verification and Validation Process Report f 3.12 Systen Design Specification fD i

h system design specification document provides the detailed specfications b system design and integration of the lurdware and software modules, and assemblQ to meet the system design requirements. It describes system structun, system operations, module and assembly interface protocols, and detailed system performance charactens-

' des.

3.1.2.1 Composite Block Diagram

'Ihese drawings provide a fuactional depiction of the Instrumentation and Control

. System block diagram and related information.

3.1.3 Hardware Design Requimnents The hardware design requirements document defines requirements for (le system i

hardware. 'Ihis document includes genc al as well ts specfic system and technical I

1 requirements, environmental requirements, and lists applicable reference documents and j pertinent supplier information for individual Idrdware modules.

3.1.4 Software Design Requirements '

1

! The software desi5 n requirements document defines requirements for the system

y software. 'Ihis document lists the functions, psimo.ance, design constraints, and attributes of the overall system software and external interfaces, h software

! q requirements in this document are defined such that they are capable of being verified J. by a prescnbed method such as inspection, analysis, dss a. tion, or test.

(l 3.2 Module & Assembly Design Docurrents f

d 32.1 Hardware Design Spedfications

' s l l 'Ihe hardware design specification documents provide the details for the hardware design

] at the module level required in meet desi6n requiremmts. 'Ihese documents define the 1 >

physical structum, interfam constraints, ratings, characteristics, functonal operation, k wMule inputs / outputs, pewer requimnents, and special features of the Instrumentation and Control System hardware, o

?" ' , 322 Softwam Design Specifications y '

h software design specification documents provide the deta& for the software dqsign 9 9 Revision 0 GW-J1R.002 May 31,1992 8

AP600 Instnunentation and Control Hardware and Software Design, Verification and Validation Process Report e an at the module level and assembly level to meet the software design requirem Thew documents define the software languge, logical structum, variable names ' tion Bow, logical processing steps, and data structure of the indMdval software 5.

They abo describe Ine functions pcivis.ed, support software, stcrage and . , ecution limitations, interface constraints, enor conditions, error detection, error respor% actions, and details of the software operation in the hardware envimnment. ,

9 33 Modula & Assembly hnplementation Documents ,;

a 33.1 Hardware Implemenutims Speci6 cation h

)6 '

1 The hardware implementation specification document presents the descripthn of the haniware desi gn as it is implemented, abo known as the 'as-built' documentation. This

. documcat indudes a manufacturing standard drawing padcage for each psardware a module in the Instrumentation and Control System. In addition, other impleinentation

, definition documents, which were itsed as stand-alone documents are compiled into this document. ,j i

33.1.1 Electdcal Assembly Documents / a s

The electrical assembly doeurmrA desefree the electrial fabrication ard assembly of individual modules and an.rmsblies that comprise the Instrumedtaticm and Control System. Rese documents typicaDy will include such items 45 a bill of materials, process specincations, componer.t assembly drawinga, anwork, and schematic diagrams for individual electncal assemblies. e f

33.1.2 Mecanical Assembly Dm wts f he mechanical asaembly documents describe the me:hardcallayout fab:icatiovt, j .nd assenbly of the cabinets and assemblies that compriw the Instiumentaten r rnd Control System. These documents define such items as cabinet layout, casd crate aa>embliss, prmted circuit card placerant,, intemal cable essemblies, and winng detrus. Dese documents typically will indude such itemstas a bill of 4 materials, artwork, and assembly requirements. 9 33.13 Wiring Diagrans g

\ t j The wiring diagrams present $c point-to-point intercormeetiens within individual f assemblies in the Instrumentation and Control System. W1dng diagrams typicnIly 3 Include such items as wire lists, wire rpeciScations, and cable Gouting re-

[L 9"I'***"***

'-on 0 GWlRM May 31,1992 9

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

AP600 Instnunentation and Control Hardware and Software Design, Verification and Validation Process Report 33.1.4 Internal Connection Diagrams g * .

The internal connechon diagrams contain the intra-cabinet wire and cablehting and identi6 cation within individual assemblies in an Instrumentation and Control i

3 System. (

f,' 33.15 Internal Power Distribution Diagrams '.

I e

The intemal power distribution diagrams describe the power distribution design k

9 within the cabinets that compnse the Instrumentation and Control System.! These diagrams typically include such items as internal wumg reqmrements, routing

{' requirenants, wire specifications, bus requirements, groundin6 requirements, and labeling and identification requirements. y l 33.2 Softwan Iraplementation Speci6 cations 4

[ ,

The software implementation spectfhation presents the description of the software design

' t' documentation. This document

, as it is implemented, also known as the 'as- l includes the source program listings and programs.

  • l j 33.2.1 Source Program ,

4 L i , The source program h the first part of the implementation of the software' design.

The source program l> written by a software designer or programmer to" orm

j the functions spect6ed by the software design specification. The source-

.I contains the necessary corrunents, functional diagrams, external references, ard I i internal mMule descriptions for consistent and self explanatory documentation.

33.2.2 Obpet Code The obpet code is the second part of the implerrasomtion of the software, design.

The ob)ect code is generated from the source pvgern and installed in 2 micw subsystem memory to perform the functions speofied by the scitware desi6n speci6 cation. t 1

i

, [ 333 Reliability Analysin Report ,

j( '

I h reliability anAly1ds report provides an analysis Of the systems ava0 Ability bMed on F avatabuity analyses of the speciRc modules and subassemblies used for the Instrumenta-f tion ard Control System. 'This report descibes tne assumphons, enlodation methodolo-

[

gy, and results of the analysis.

*% GW41R-002 Reviden 0

/

May 31,1992 10 4

e

l

i l l 4

AP600 Instrumentation and Control Hardware and Software l Design, Verification and Validation Process Report ,

I l ~

<. l j

3.4 Verification and Validation Plan j 3.4.1 Hardware Verification Plan

. ne hardware verification plan defines the process to demonstrate that the ware design requirements and hardware desgn speofications are met. 'Dds document

] what hardware is required to be venfied and the extent of the venfication meth This 1 document includes such items as hardware test methods, categoruation ts, i yl l test methods, inspection methods, checklists, and administrative responsibili

  • e 1 i l
i 3.4.2 Software Verification Plan ,

i l

l 3 ne software verification plan defines the process to demonstrate that the software ign )

f requirements and software design speofications are met. This document d what

{

i f4 software is required to be vmfied and the extent of the verification fThis document includes such items as the test levels the software has been divided in ' error l codes, applicable inspection methods, checklists, guidelines, administrative n-i j .I sibilities, test methods, and inspection methodsf.  ;

q a 3.4.3 System Verification Plan ,

j i y d.

l i ne system verification plan defines the process for system venfication. His docininent y provicies the basis that establishes that the system conforms to the system depign i  : specificahons. The system verification plan also establishes that the assembliq are

! (!l 1 properly interfaced and that the Instrumentation and Control System interfaces properly j with the external environment. The plan also typically establishes that the interfaces

p between the functional units are correct and that the data flow and control flow between j different software modules works mi Gy.

'{

p 3.4.4 System Validation Plan i

. ne systen validation plan identifies the system design documentation and instrumen-
! tation that is to be validated and a series of comprehensrve system functional and 4

i transient test cases, simulatin5 mmal and ahmal system operation conditin. ne j 3 validation plan typically contains vahdation prmdples, standards, methods, ad-

ministrative responsibilities, checkhs3, flow dia6 rams, and other pi- ance evaluation q

i tools. .

i Revision 0 GW J1R4XI2 May 31,1992 11 4

e

+ ;

x, i

AP600 Instrurnentation and Control Hardware and Software Design, Verification and Validation Process Report pa.. p 4 i .5 Module & Assembly Verification Reports and Procedures  ;

1 3.5.1 Hardware Verification Test Procedures d The hardware verificatioa test procedures de6ne the testing,progrun and procqw for

individual functional parts, modules, subusemblies, and arc,emblies witWp the i

Instrumentation and Contro1 System. These documents defmc the tests to be pddo.ed, the test methodology, the test environment, expected results, and acceptance c iteria.

Each test procedure covers a specific functionalitem or module. Typical tests @u.ed I

i , are voltage limits, throughput, response times, and environmental exposure.

(

i 3.5.2 Software Verification Test Pmcedures ;j -

l The software venfication test procedures define the testing }.rogram and p for l individual software functional units, modules, and assenMies within theInstrum tion i and Control System. These documents define the tests to be perform 4 test

. methodology, the test environment, ecpected results, and acceptance crite2ia, The i

documents also cover details of input generation, and how the expected resud and j acceptance criteia are determirmed. ,- i ko - h '

j f 3.53 Hardware Test Results Re;xxt 'f The hardware test results report presents a summary of the hudware verificatici ting l result 2, any errors found, and their resolution. This document, in conjunction th the

] l

hardware design specification, and hardware verification test procedure tains. -

4' summt mformation to enable a third party to repeat hardware tests and u tand

the results.

. { k

} t 3.5.4 Software Test Results Report Q

- o a

The software test results report presents a summary of the software i results, any errces found, and their resolution. This document, in conjua fith the

- schware design specification, and sonware verification test procedure contains sdf!!icient information to enable a tWrd party to repeat software tests and understand the results.

k

.6 Syste n Inte6 ration Description Documents

^

3.6.1 System Implementition Speification This dccument presents the description of the system design as it is implemen 3, known as the 'aebuilt' documentation. This document indides a manufacturing.:

standud drawing package for each Instrumentation and Control System. In a*ddition,

.Revisica 0 GW-J1R432 May 31,1992 12

.' at a mu Mn. . x. , . . ~, .

7 7,, 7 xg 43..

. . . . . .c AP600 Instrumentation and Control Hardware and Softwale

Design, Verification and Validation Process Report l

' s l I >

j er implementation definition documents, widch were used as stand-alone doem nts are compiled into this dot.ument.

- 3.6.1.1 Systun Electricallesemblies ,

l 7hese docunwnts Instmmentation and Centroldescribe System. hsethe electrical documents includefabrication informa n on and as i i such itans as sys. tem connertor pans.ls, fans and blowers, circuit breakm, SW intd-ing systems, power mpplie, and test panels, and typically include ass 5 lnbly draw ngs and schematic diagrams. (. ,

3.6.1.2 Syetem Mechs.ical Assemblies $

}8 Wse dowents descibe the Isvout and assembly of the overallInstrumen en and Control Systan. These documents include irformation on such i a.s system cordiguration, cabinet layreut, printed circuit card placement, internal ble assemblies, and wiring details, and typically include assembly requnemen .

^

3.6.1.3 System Wiring Diagrams '/

. The system wiring diagmms present the point-to-point interconnections t een i

( inaividual assemblies in the Instnunentation and Contml System. ese

, documents define such items as wutlists, wire specifications, and cable ting .

< ? and tie down requirements. 't

.I v Diageanw 3.6.1.4 System Internal Cennect'>n y l

, 3 The internal connection diagrams contain the intrs<abinet wire and cable robting

and identification between individual assemblies in a.m Iratrmnentation and
[ Control System. .,f I

3.6.1.S System Intemal Power Distribution Diagums  ;

'Ihe system intn mal power distribution diagrams describe the power di ution der.ign between the cabinets that comprise the Instrumentation end gentrol System. These documents include such ituns as internal power wiring equire-mend, wire specifications, grounding requirements, and labeJing and idhtifica-tion reqm tments. d k

Revision 0 GW 11R M l May 31,1992 13

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

l

. .. y . o ...n.s AP600 Instnunentation and Control Hardware and Software Design, Verification and Validation Process Report

' Yt t

System Verification de Validation Documents 3.7.1 System Test Procedures

! ii i 3.7.1.1 System Verification Procedures p,

,)

The system ver!!ication test praedures define the testing program intd process for inhgrated system veriEcaSon test. hse documents define thq tests to be performed, test uwthods, and acceptance criteria to achieve systerrlbrification.

i L The tests are typicaHy overlapping static and dynax: tic tests which g@ss from

, detailed performance checks of modules and assemblies to moh ex

, pe;formance checks of the overallInstrumentation and Control Sysle; 4 .

3.7.1.2 Sy3'zm Validation Pruedures

[

ne system validation test procedures define the testing program and process for f

lp integrated system validation test. These documents detail the wages and

, j pmgression to functionaDy the entire Instrpmentation and Cor. trol Syman. Rase documents denne the tests cases and/acreptance criteria to achieve system y functional validation. The test cases shntdate ral life phnt conditions and P typicaDy indude such tests as static and dynamic c dtration and operational tests, functional logic tests, and egnal mterface tests.  ;

3.7.2 Trst Results Manual .

3.7.2.1 Systm Verificdon Test Results

'q 4{

p The system verification test results are the performance test results compiled i during integrated system venEcstion tests, nese documents include such items e as response tunes, accuracy, power margins, naise levels, snd overload and 4

S recomy cluracterM&

3.7.2.2 System Vali:!ation Test Results

'4 ne system validstion test results are the performance test results compiled during integrated system validation tests. These documents include such items as extunal stunulus/ output results, interaction between assemh'ies, and

information transport.

)

Revision 0 GW-11R-002

. May 31,1992 14

i. AP600 Instnunentation and Control Hardware and Software i Design, Verification and Validation Process Report t

4 l 3.8 Product Documentation

)

4 3.8.1 System Interfacing Documents j 3.8.1.1 External Connection Diagrams 1

4

. The external connection diagrams define the interfaces - for the l Instrumentation and Control System to extemal systems. These drab indude

such items as cabinet termination points, system cable rtmting, u cable type.

3.8.12 Signal Interface List j t w The sa6nal interface list defines the signal paths configured for ' t Instrumenta-

. tion and Control System. 'Ihese are signals from sensors to wts actuation j and trip signals 'r~n cabmets, display data, plant status, and sjb, data inter-faces.

3.8.1.3 Extemal Power Requirements j

! The external power requirements' document dermes the *W=1 power requirements for the Instrumentation and Contml System. This doc 2 ment j includes voltage, frequency, and capacity requirements for the Instrumentation l and Control System.

j 3.82 System Instanation Docummts i

l 3.8.2.1 Beld Separation Requirements The 6 eld separation requirements dccument defines the physical and electrical

separation requirements for installation of the Imtrumentaden and controi
System. This document specifies such items u wiring seperation groups, equh=aard loation, and any physical barriers required.
3.82.2 Environmental Requirements j 1he environmental requirements document defines the values to , serve as a reference point for establishing environmental effects. "Ihis document takes into l consideration sa
h conditions as temperature, relative humidity, voltage i

va: iations, fnquency variations, total harmorde distortion, and seismic disturban-ces. Minimum requirements for storage and ti.repv6.tlan are also covered by this specification.

Revision 0 GW-J1R 002 1

May 31,1992 15 i

~

AP600 Instrumentation and Control Hardware and Software Design, Verification and Validation Process Report yu -

y ,

. e

.83 Maintenance Manuals i

j 3.83.1 Hardware Maintenance Manual 4 i .

l The hardware maintenance manual provides additional information beyor lthat 1 included in the hardware design documentation that is reqmred for har' . ware maintenance.

! 3.83.2 Software Maintenance Manual j 'Ihe software maintenance manual provides additional information beyor kthat 4 included in the software design documentation that is required for sof tware j maintenance.

[

! f, s

j i  !

l  :

u i 4 l J-1 i ib , l

) 1J I

l( *

, p

~

1 l

! .s 4

1

! I e

s

+  ?

i

  • l k, j s i Revision 0 GW-J1R-002 May 31,1992 16 b

...+. . ,:y, z;. .

AP600 Instrumentation and Control Hardware and Software Design, Verification and Validation Proces.s Report 4.0 Document Cross-Reference

p. .

4.1 Documents Specific to Hardwm Document 'ntle Hardware Desiga Requirements 3.

Hardware Design S;=ciru.tions 33 Hardwm Implementation Specification 3. K1 Bectrical Assembly Documents Skl.1 Mechanical Assembly Documents 34.1.2 Wiring Diagrams ,

.13

' .1.4 Intemal Connection Dia5 rams Intemal Power Distribution Diagrams .1.5 Hardwm Verification Plan 3.4.1

. Hardwm Verification Test Procedures 3.5.1 Hardware Test Results Report 3.53 Hardware Maintenance Manual 3.8.3.1 Revision 0 GW-J1R.002 May 31,1992 17

[

AP600 Instnunentation and Control Hardware and Software

Design, Verification and Validation Process Report

) -

3 j 4.2 Documents Speofic to Software j _

i o Document T'tle Section  ;

j # a.

1 j Software Design Requirements 3.

Software Dragn Sp dacations l 34 Softwam Implementation Specifications 3 4

Source Pivg,r ms 3, 1 f @ Code 3y_2

] [ Software Verification Plan 34 i

Software Verification Test Procedures 3.52 i i t j ,

,' Test Results Report 3.5.d j

h. Maintenance Meual /

.I 3.82)2 -

l {. ( .

! I 4

i 4 ~
y 3

i i

4 i

I g

Revision 0 1R M

~

May 31,1992 18 1

4

e a.a .-e 4, . . . - . ..___m m _, J.aa aa,,. .*--_.+ J _ ,,,, ,- _ g. m:4 ,& .h e a __saS._#. J4_,m,,_a -So.m._.ar--4 -- a---. - 4 A-=--- --45.->-

AP600 Instnunentation and Control Hardware and Software l Design, Verification and Validation Process Report i .

i 5.0 References

)

5.1 WCAP-12601, "AP600 Simplified Passive Advanced Light Water Reactor Plant I ~j .

3 l6 4

Prognm - Program Operating Procedures", Rev. [To Be Established If ter}

't t

i

] 5.2 C&PGSTIX01, " System Development / Implementation trocess ( ),

[To Be Established later] .. " Rev.

) 5.3 WCAP-9153, "414 Integrated Pihtion System Prototype Veri 6 cation Program",

August 1997 ,

1 i  ;

.' \

1 5.4 WCAP-9739, " Summary of the Westinghouse Integrated Protectiop System

, Verification and Validation Program", Sept.1980 p j / $

i j ,

f l l  ! . l l

i i:

I ,t i t

4. c t, i  ?

s a i h

.s  ;

Revision 0 Y

GW-J1R-002 May 31,1992 20

. . . ~ . _

AP600 Instrumentation and Control Hardware and Software l Design, Verification and Validation Process Report 3

43 System Level Documents

}

! (includes combined hardware / software documents) k Document 'ntle Section l

I -

j System Design Regen.zats 3.1.1

~~

! System Punctional Requirements 3.1.1.1 System Block Diagram 3.1.12 1

System Desi6n Sp=cineatior.s 3.12 3.12.1 l C@te Block Dia5 ram d

Reliability Analysis Report 333 System Veri 6 cation Plan 3.43 System Validation Plan

/ 3.4.4 System Implementation Speci6 cation 3.6.1 System Electrical Assemblies 3.6.1.1 l '

3.6.12

l. System Machanien! Assemblies 4

System Wiring Diagrams 3.6.13 j

SystemIntemalConnection Diagrams 3.6.1.4 j

System Intemal Power Distribution Diagrams 3.6.1.5 System Verifistion Procedures 3.7.1.1

] 3.7.1.'l i System VaHAntian Procedures System VeriAcm% Test Results 3.711

. System Validation Test Results 3.722 ExtemalConrection Diagrams 3.8.1.1 l

SignalInterface List 3.8.'12 Extemal Power Requirements 3.8.13 j

Pield Separation Requirements 3.82.1

)

~

3.812 Environmental Requirements on 0 GW-J1 j May 31,1992 19 i

_

Retrieved from "https://kanterella.com/w/index.php?title=ML20153C484&oldid=2960081"