page 1 pcdh v6 presentation – io / engage meeting - 18/02/2011 pcdh v6 2011 release why to...

PCDH v6 presentation – IO / Engage meeting - 18/02/2011

PCDH v62011 release

• Why to standardize, PCDH ?

• Overview of ITER I&C

• ITER standards for I&C

• Interlock and Safety controls

• I&C life-cycle and illustration

• PCDH v6 status and v6/v5


This is ITER


This is the ITER Agreement

140 PA’s80 include I&C


A bit of interface problems


Missing Items


The control system can help to fix this


it identifies and may eliminate missing items


Control system is horizontal and connects almost everything


it is involved in integration


and is the primary tool for operation


But this will work only if…

…all these links work


That is why we, CODAC team, concentrate all our effort on standards (PCDH) and implementation of

those standards (CODAC Core System)

What is PCDH? •Plant Control Design Handbook (PCDH) defines methodology, standards, specifications and interfaces applicable to all ITER plant systems I&C.

•PCDH is an annex to Project Requirements (PR) and applicable to all Procurement Arrangements with I&C.

•PCDH is released at regular interval throughout the construction phase of ITER.

•PCDH is reviewed by I&C IPT.


PCDH v6 scopeMaster document

Master document: (27LH2V v6.1) •ITER baseline document, •Provides all rules, is contractually binding, •Is summited to PCR

Core PCDH (27LH2V)Plant system control philosophy

Plant system control Life Cycle

Plant system control specifications

CODAC interface specifications

Interlock I&C specification

Safety I&C specification


PCDH v6 scopeSatellite documents

Core PCDH (27LH2V)Plant system control philosophy

Plant system control Life Cycle

Plant system control specifications

CODAC interface specifications

Interlock I&C specification

Safety I&C specification

Guidelines for signal conditioning

Guidelines for I&C cubicle configurations

PCDH core and satellite documents: v6

Guidelines for archiving

Specifications for HPN

Specifications for time stamping

TEMPLATES and ILLUSTRATIONS

CWS case study specifications (35W299)

PS CONTROL DESIGN

Plant system I&C architecture (32GEBH)

Methodology for PS I&C specifications (353AZY)

CODAC Core System Overview (34SDZ5)

INTERLOCK CONTROLS

Guidelines for the design of the PIS (3PZ2D2)

Network products

I&C CONVENTIONS

I&C Signal and variable naming (2UT8SH)

ITER CODAC Glossary (34QECT)

ITER CODAC Acronym list (2LT73V)

PS SELF DESCRIPTION DATA

Self description schema documentation (34QXCP)

LCC and SCC prototypes

PS simulators: slow, fast, interlocks

CATALOGUES for PS CONTROL

Slow controllers products (333J33)

Fast controller products (345X28)

Cubicle products (35LXVZ)

Guidelines for PIS configuration

PS CONTROL INTEGRATION

The CODAC -PS Interface (34V362)

PS factory acceptance plan (3VVU9W)

ITER alarm system management (3WCD7T)

ITER operator user interface (3XLESZ)

PS CONTROL DEVELOPMENT

I&C signal interface (3299VT)

PLC software engineering handbook (3QPL4H)

Guidelines for fast controllers (333K4C)

CODAC software development environment (2NRS2K)

NUCLEAR PCDH (2YNEFU)

Management of local interlock functions

PIS, PS I&C and CIS integration

Management of interlock data

OCCUPATIONAL SAFETY CONTROLS

Rules and guidelines for PSS design

Available and approved

Expected

Legend

This document

(XXXXXX) IDM ref.Satellite documents: Provide guidelines,

recommendations and explanations, but no mandatory rules.


PCDH v62011 release








CODAC System (PBS-45)

Pla

nt

Sys

tem

I&C

CentralInterlock System

(PBS-46)

CentralSafety Systems

(PBS-48)

Central I&C Systems

CODAC NetworksCentral Interlock Network

Central Safety Networks

ITER I&C SYSTEM

Plant Conventional Control System

Plant System Controller

Signal Interface

Plant SystemHost (PSH)

Plant Interlock System(PIS)

PIS Controller

Plant Safety Systems(PSS)

PSS Controller

I&C Networks

Signal Interface Signal Interface

I&C structureSegregation of ITER I&C into 3 vertical tiers and 2 horizontal layers

Conventional Control Control and monitoring for all ITER PS

Interlock Protects the investmentIndependent network and I&C

Safety Protects personnel, and environment Independent network and I&C Two train systems

Three vertical tiers, two horizontal layers


Finite set of “Lego blocks”, which can be selected and connected as required


Plant System I&Cis a deliverable by ITER member state (procurement arrangement).Set of standard components selected from catalogue.


ITER Subsystem

is a set of related plant system I&C.


Plant Operation Network


Plant System Hostis an IO furnished hardware and software component installed in a Plant System I&C cubicle. There is one and only one PSH in a Plant System I&C. PSH is mainly used to interface the PS I&C with CODAC


Slow Controlleris a Siemens Simatic S7 industrial automation Programmable Logic Controller (PLC). There may be zero, one or many Slow Controllers in a Plant System I&C. A Slow Controller runs software and plant specific logic programmed on Step 7 and interfaces to either PSH or a Fast Controller using IO furnished interface. A Slow Controller has normally I/O and IO supports a set of standard I/O modules. A Slow Controller has no interface to HPN. A Slow Controller synchronizes its time using NTP over PON. A Slow Controller can act as supervisor for other Slow Controllers.


Fast Controlleris a dedicated industrial controller implemented in PCI family form factor and PCIe and Ethernet communication fabric. There may be zero, one or many Fast Controllers in a Plant System I&C. A Fast Controller runs RHEL and EPICS IOC. It acts as a channel access server and exposes process variables (PV) to PON. A Fast Controller has normally I/O and IO supports a set of standard I/O modules with associated EPICS drivers. A Fast Controller may have interface to High Performance Networks (HPN), i.e. SDN for plasma control and TCN for absolute time and programmed triggers and clocks. Fast Controllers involved in critical real-time runs a RT enabled (TBD) version of Linux on a separate core or CPU. A Fast Controller can have plant specific logic. A Fast Controller can act as supervisor for other Fast Controllers and/or Slow Controllers. The supervisor maintains Plant System Operating State.


High Performance Computer

are dedicated computers (multi core, GPU) running plasma control algorithms.


High Performance Networksare physically dedicated networks to implement functions not achievable by the conventional Plant Operation Network. These functions are distributed real-time feedback control, high accuracy time synchronization and bulk video distribution.


Simplest possible Plant System I&C – Data flow

CODAC System / Mini-CODAC send commands and, if required, publish data from other Plant System I&C to PSH using channel access protocol

PSH receives absolute time from TCN (4). The absolute time on the Slow Controller can be set using NTP with PSH as NTP server

PSH publish data, alarms and logs to CODAC System / Mini-CODAC using channel access protocol.

PSH and Slow Controller exchange data using standard interface provided by IO (3)

The Slow Controller interfaces via signal interface to actuators and sensors and contains plant specific software and logic programmed on Step 7


Simple Mixed Plant System I&C – Data flow

CODAC System / Mini-CODAC may send commands and, if required, publish data from other Plant System I&C to Fast Controller using channel access protocol (6).

Fast Controller may publish data, alarms and logs to CODAC System / Mini-CODAC using channel access protocol (7)

PSH supervises Fast Controller (8) to manage COS

Fast Controller could interface directly to Slow Controller using standard interface provided by IO (9) or indirectly through PSH by (8) and (3)

SD: Plant System I&C Architecture (32GEBH v2.3)


PCDH v62011 release







• Slow controllers

• Fast controllers

• I&C cubicles

• Signals


Fail safe SIL3 and high availability PLCs

High range PLCs

S7-400

Medium range PLCs

S7-300I/O interfaces are the same for high

and medium ranges PLCs (ET200 products), only CPU and CPU chassis

differ.

I/O interfaces, CPUs and chassis are specific to this product line.

Next rackNext rack

ITER slow controllers: Selected products


ITER slow controllers: a large range of configurations for flexibility

Configuration 1

The simplest configuration with I/O cards within the S7-300 CPU rack

Configuration 2

Generic architecture with remote IO racks connected in serial architecture.

Next Rack

switch

Next Rack

Configuration 3

Both serial and star configuration may be mixed.


Networks• Ethernet 100 Mbits/s for S7 CPU to CODAC front-ends.

• PROFINET V2 for process interface within the S7.

• IEC 61850 for communication with equipments of power stations.

• Profisafe profile over Profinet for SIL-3 purposes.

Software development• STEP 7 Professional version for user software development.

• Additional function block options if required for the plant system.

• Guidelines for software development included in PCDH v6.

SD: Siemens S7 PLC Catalogue (333J63 v1.7)

ITER slow controllers: Network and software development


ITER slow controllers: e-ordering: implementation process

Siemens S7 PLC Ordering process (3Q6UQ3 v1.0)


• PCDH defines CODAC selection for I/O bus:– PCI bus (parallel)– PCI-Express (serialized, PCI functions as payload)

• PCDH defines CODAC selection of communication method for interconnected systems:

– Ethernet• The definition covers extremely large selection of different

industrial computers and form factors• CODAC Standards include and full support is given to:

– Conventional PCI and PCI Express boards– PICMG 1.3 SHB industrial computers– PXI Express hybrid chassis for PXI, CompactPCI and PXI

Express I/O boards– ATCA shelf and blades for high end data acquisition

ITER fast controllers:I/O Bus and Industrial Form Factors


I/O :- PXI / PXI Express- CompactPCI

I/O :- PXI / PXI Express- CompactPCI

- PXIe Chassis (hybrid)- PXIe Chassis (hybrid)

-4U PICMG 1.3 chassis-High-end CPU (2 x Xeon)-4U PICMG 1.3 chassis-High-end CPU (2 x Xeon)

1 Gb/s Ethernet1 Gb/s Ethernet

Bus ExtensionPCI-Express x4Bus ExtensionPCI-Express x4

6U CompactPCI Digitizer (not in catalogue)6U CompactPCI Digitizer (not in catalogue)

Conventional PCI / cPCI Bus ExtensionConventional PCI / cPCI Bus Extension


Connecting together different form factors of PCI and PCI Express based systems

Read More

ITER fast controllers:PCI Express for modularity and interoperability

SD: Guideline for Fast Controllers (333K4C v1.3)


• Separation in different physical units:– CPU, network and – in some cases – solid state disks– I/O cards and cabling

• Example:Simple,generalpurposeFastController

I/O - PXI- CompactPCI- PXI Express

I/O - PXI- CompactPCI- PXI Express

PXIe ChassisPXIe Chassis

2U PICMG 1.3 chassis2U PICMG 1.3 chassis


Optional10 Gb/s EthernetBus Extension

PCI-Express x1Bus ExtensionPCI-Express x1

ITER fast controllers:Basic Fast Controller Configurations and Ideas

SD: ITER Catalogue of I&C Products – Fast Controllers (345X28 v1.3)


ITER I&C cubiclesconfigurations

SCC LCC

PSE1

1A1

PSE2

LCC + SCC

PSE1

1A1

PSE2

Configuration1: The I/O interfaces of the I&C controllers are connected to PSEs through signal conditioning interfaces housed in an SCC.

Configuration2: This configuration is similar to configuration 1, but LCC and SCC are merged in order to optimise the space allocation.


ITER I&C cubiclesconfigurations

SCC + remote IO

LCC

PSE1

1

A1

PSE2

LCC

Field bus

PSE1

1

A1

PSE2

Configuration3: In this configuration, the I&C controller of LCC is configured with a remote I/O rack installed in the SCC. The link between the LCC controller and the remote I/O rack may be fibre optic in the case of a long distance connection, strong EMI issues or any voltage isolation issue. Preferred configuration for Tokamak building.

Configuration4: In this configuration, the PSE are connected to the I&C controller by a plant system I&C field-bus. The medium may be fibre optic.

Targets for cubicle standardization: All LCCs and SCCs cubicles whatever the plant system.


ITER I&C cubiclesSelected products

SD: SAREL cubicle catalogue for plant system I&C (35LXVZ v2.3)

e- configuration: http://www.iter-schneider-electric.com/


Signal interfaceScope

PCDH

Sensor/act.

Plant system

I&C

Controller

rack

Cabling interface

Signal

conditioning

device

PS

Cabling interface

PS

Plug

Mechanical

interface

Signal interface

• IO cabling rules, (335VF9)• IO cable catalogue (355QX2)• ITER EMC policy (42FX5B)


Sensors•Voltage range: 0V to +10V unipolar, -5V to +5V bipolar, -10V to +10V bipolar.•Current range: 4mA to 20mA (16mA span). Signal polarity: positive with respect to signal common.

Actuators•Output Current: 4mA to 20mA (16mA span). Signal polarity: positive with respect to signal common. Load resistance: 500 max. Preferred 250 .•Output voltage: 0V to +10V unipolar or: -10V to +10V bipolar.

Digital signals•Signal logic: positive for process control, negative for fail safe logics.•Range: 24V DC referenced to plant system I&C cubicle earth. Maximum current depends on the galvanic isolation interface.

T sensors•Resistance thermometers: Pt100, 4 wires.•Thermocouples: type K, type N.•A passive low-pass input filter may be recommended for any T sensor.

Pneumatic signals•Range: 0.2 to 1 bar for the current / pressure converters of the pneumatic proportional control valves.•0 to 6-8 bars for the non proportional control valves.

Signal interfaceSignal standards


• Single point earthing: For the Cryostat, the concept of single-point earthing has been selected and a loop Exclusion Zone (LEZ). Multipoint earthing: For other locations outside LEZ. Apply IEC 61000-5-2.• Signal transmission schemes are proposed for each signal type.

TransmitterSensor I&C

controller

+

-

CBN

360° contacts

DC

0 v

0 v

CBN

0 v

TransmitterSensor

I&C controller

+

-

CBN CBN360° contacts

DC

2 resistors 1 MΩ ± 1%

0 v

0 v

Signal interfaceEMC policy

SD: I&C signal interface (3299VT v4.4)

Sensor configuration with differential amplifier

at receiver level

Sensor configuration with full differential configuration


PCDH v62011 release







• Naming convention

• Software engineering

• HMI and alarm handling

• Common Operating States


Naming convention for variables 1/2

Signal cable

Signal interface

P

PS sensor/actuator

Signal

Signal conditionner

Signal

Controller CPU

Variable

Signal Name = PS Component Identifier : Signal Identifier

Variable Name = PS Function Identifier : Variable Identifier

• Component identifier: ITER naming convention applies.• Signal identifier: ITER naming convention based on ISA applies.• Variable identifier: only guidelines are proposed by ITER, see SW

HB


Signals26PHDL-VC-0001:FCVZ-CRC26PHDL-VC-0001:FCVY1-CRC26PHDL-VC-0001:FCVY2-CRC26PHDL-MT-0002:TT-CRC

Signal cable

Remote IOvariablesCWS-PHTS-DLHT:VC1-FCVZCWS-PHTS-DLHT:VC1-FCVY1CWS-PHTS-DLHT:VC1-FCVY2CWS-PHTS-DLHT:MT2-TT

DLHT XXXX

PHTS XXXX

CWS

FBS

26PHDL-VC-0001

26PHDL-PL-0001

26PHDL-PZ-0001

P

L

T

26PHDL-HX-0001

26PHDL-VC-0003

26PHDL-VC-0007

26PHDL-VC-0004

26PHDL-VC-0005

F

P-100

26PHDL-VC-0008

26PHDL-HT-0001

26PHDL-VC-0006

Water storage and treatment CVCS

GN2 gas

supply

T

F

T

T

CC

WS

1

F

I-56

26PHDL-VC-0010

Client 1

26PHDL-VC-0013

26PHDL-VC-0014

Client 3

26PHDL-VC-0011

26PHDL-VC-0012

Client 2

26PHDL-VC-0009

P-111

26PHDL-VC-0002

Naming convention for variables 2/2

SD: Signal and plant system I&C variable naming conventions (2UT8SH v7.3)


Software development guidelines

7

3

PLC

CODAC interface

Hardware Outputs/Inputs Interface

4

PLC Interface

EquipmentsPISPSSCOTS

Simulator

CODAC Core System

11

13Fast

ControllerInterface(s)

6 Fast Controller(s)

PLC(s)

2

1

7

System Monitoring

8

10

9 12

PLC Core Application

5

1

• SD: Software Engineering and Quality Assurance (2NRS2K v2.1)

• SD: PLC software engineering handbook (3QPL4H v1.3)

PLC user software engineering:• Software architecture.• Coding language.• Templates.• Conventions

Targets are interfaces mainly.


Human Machine Interface

Operator User Interface Principles:

Operator Tasks Analysis.

Operator User Interface Detailed Design:

• Implementation.

• Operator User Interface Testing.

• Training.

RD: (operation) ITER Human Factor Integration Plan (2WBVKU v1.1)

SD: Philosophy of ITER Operator User Interface (3XLESZ v2.0)

Expected: user manuals for HMI


Alarm handling

• What is an Alarm?

• Alarm management lifecycle.

• Alarm philosophy principles.

• Key Design Principles for the alarm system.

• Alarm for redundant components.

• Alarms in case of dependant failures.

• Alarm Engineering Checklist.

• Rationalisation of the alarm system.

• Detailed Design of the alarm system.

RD: ITER Human Factor Integration Plan (2WBVKU v1.1)

SD: Philosophy of ITER Alarm System Management (3WCD7T v2.0)

Expected: user manuals for alarm handling


COS: alignment with Operation HandbookRD: Operations Handbook – 2 Operational States (2LGF8N v1.2).


PCDH v62011 release








INTERLOCK at ITER

Machine Machine (investment) (investment)

IntegrityIntegrity

Design & Design & OperationOperation

Instrumented Instrumented Machine Machine

ProtectionProtection≡≡ ++

Investment Investment protectionprotection

======

InterlocksInterlocks

≠≠

Nuclear Nuclear SafetySafety

Personnel Personnel SafetySafety

EnvironmenEnvironmental Safetytal Safety

AccessAccess


The Interlock Control System (ICS)

ICS


Interlocks: PIS guidelines


Interlocks: PIS guidelines

SD: Rules and Guidelines for the Design of the Plant Interlock System (PIS) (3PZ2D2 v1.2)

• PIS and PIN architecture.• Redundancy sensors and actuators.• Sharing of sensors and actuators between interlock and

conventional control.• Cabling rules for PIN.• Powering rules for PIN.• Rules for interfaces PIS – Conventional Control.• Rules for interfaces PIS – Plant Safety System.• Risk classification.• etc…


Safety: PCDH-N

Plant Control Design Handbook for Nuclear control systems (2YNEFU v2.0)

For all categories:•IEC 61513, Nuclear power plants – Instrumentation and control for systems important to safety – General requirements for systems,•IEC 60709, Nuclear Power Plants – Instrumentation and Control systems important to safety – Separation, except for some cabling rules which will be replaced by RCC-E rules,

For Category A:•IEC 60780, Nuclear power plants – Electrical equipment of the safety system –Qualification,•IEC 60812, Technical Analysis for system reliability – Procedure for failure mode and effects analysis (FMEA),•Seismic events : RCC-E adapted to ITER project,

For Category B:•IEC 60780,•Seismic events : RCC-E adapted to ITER project,•IEC 60987, Programmed digital computers important to safety for nuclear power stations,•IEC 62138, Nuclear power plants – Instrumentation and control important for safety – Software aspects for computer-based systems performing category B or C functions,

For Category C:•IEC 62138,


Nuclear safety: the main points to address

• Quality.• PSS-N life-cycle.• PSS-N safety requirements: safety class, single failure

criterion, failsafe principle, power supplying, qualification to environmental conditions, seismic class, periodic tests, segregation rules.

• PSS-N functional specs.• PSS-N architecture.

Planned: Rules and Guidelines for the Design of the Plant Safety System (PSS)

Plant Control Design Handbook for Nuclear control systems (2YNEFU v2.0)


PCDH v62011 release








PS I&C Life Cycle: from design to operation & maintenance

PS I&C design

PS design review

PS manufacture including I&C

PCDH

PS manufacturing phase

PS FAT including

I&C

PCDH

PS on site Installation including

I&C

PCDH

PS integrated commissioning

PS integration phase

PS SAT including

I&C

PCDH

PCDH

Operation and maintenance phase

Operation & maintenance

PCDH

EDH PCDHInputs for

I&C design

PS design phase

• This life cycle is aligned with the ITER model for plant system life cycle.

• Deliverables are proposed at completion of each phase.

PS I&C life cycle from PCDH


Design Review Procedure (2832CF v1.12) (current)

(to be updated soon by v2.0)

ITER design review procedure: what to review, when and with which maturity

level. The I&C specifications as defined by PCDH are incorporated in the new version. At FDR the tech specs should be ready for manufacture by the industry.

I&C techs specsIn general

I&C tech specs = I&C scope + I&C rules & guidelines

I&C Scope = PS dependent, implemented by PCDH deliverables of the design phase.

I&C rules & guidelines = PCDH rules and guidelines for the full life-cycle.


PS design activitiesScheme for pure functional PA type

Concept Design & Engineering studies

Concept Control Documents/Specifications

Concept Design Review

PA Documents (Main, Annex A & Annex B)

Signature of PA (Hand Off)

Preliminary Control Documents/Specifications

Preliminary Design & Engineering studies

Preliminary Design Review

Final Design & Engineering studies

Final Design Review

TimePA

IO DA Responsibilit

yI&C specs

PA annex B + PCDH

I&C scope

A collaborative work involving DAs and IO is required to get the most suitable specifications for both parties


I&C techs specsDetails as specified in Standard design Process

See: sdp working instructions content & maturity of main design engineering data

I&C tech spec deliverable Document type PCDH ID

Plant system I&C architecture. I&C D1

Plant system I&C boundary definition. IS D2

Plant systems I&C integration plan. Installation plan D3

Plant system P&IDs, and electrical drawings and diagrams.

P&ID, cabling diagrams

D4

Controller(s) performance and configuration requirements.

I&C D5

List of inputs and outputs (I/O) of the I&C controllers.

I&C D6

List of the Process Variables handled by the I&C controllers.

I&C, IS D7

Configuration of I&C cubicles. I&C D8

Description of plant system state machines. Operation sequence

D9


Deliverables for I&C specificationsHow to proceed for I&C architecture (D1)

51

ANT1

FAFBHVRFCORDCONF

ANT2 TEST

PROT MATC HPLSPPTFHVDLTLMNSPLRHVPS

1. Starting point: the FBS.

51.HV.1

HVPS

51.HV.1

HVPS 51.RS.1

RF source

51.RS.1

Amplitude Mearement

51.ANT1.MON1

Amplitude monitoring

51.ANT1.CORD

ICH coordination

45

CODAC

51.A

NT

1.H

VR

F.M

ES

M.L

1

51.ANT1.FAFB.MONI.L3

51.ANT1.MON1.L1


51

.AN

T1

.FA

FB

.RF

PW

.L1

51.ANT1.FAFB.CORD.L1

47

PCS

51.ANT1.PCS.FAFB.L1

51.ANT1.PCS.CORD.L1

51.ANT1.PROT

Amplitude interlock control

51

.AN

T1

.PR

OT

.OV

RV

.L1


51.ANT1.FAFB

ICH fast feedback Controller

51.RS.1

Amplitude Mearement

51.ANT1.HVRF

High Volt control & mgmnt

51.ANT1.HVRF.MESM.L2

51.ANT1.HVPS

HVPS control & mgmnt

51

.AN

T1

.HV

RF

.IN

TF

.L1

51.ANT1.HVCM.L1

51.ANT1.HVPS.MESM.L1


51

.AN

T1

.FA

FB

.PR

OT

.L1

51.ANT1.HVPS.PROT.L1

51.A

NT

1.F

AF

B.P

RO

T.L

2

51

.AN

T1

.CO

NF

.PA

RA

.L4

51

.AN

T1

.CO

NF

.PA

RA

.L1

51

ANT1

FAFBHVRFCORDCONF

ANT2 TEST

PROT MATC HPLSPPTFHVDLTLMNSPLRHVPS

2. Develop control diagrams for each plant system function.3. Characterize the control functions with properties as: I/O, RT, SIL, ..


Deliverables for I&C specificationsHow to proceed for D1

51.HV.1

HVPS

51.HV.1

HVPS 51.RS.1

RF source

51.RS.1

Amplitude Mearement

51.ANT1.MON1

Amplitude monitoring

51.ANT1.CORD

ICH coordination

45

CODAC

51.A

NT

1.H

VR

F.M

ES

M.L

1


51.ANT1.MON1.L1


51

.AN

T1

.FA

FB

.RF

PW

.L1


47

PCS

51.ANT1.PCS.FAFB.L1

51.ANT1.PCS.CORD.L1

51.ANT1.PROT

Amplitude interlock control

51.

AN

T1

.PR

OT

.OV

RV

.L1


51.ANT1.FAFB

ICH fast feedback Controller

51.RS.1

Amplitude Mearement

51.ANT1.HVRF

High Volt control & mgmnt

51.ANT1.HVRF.MESM.L2

51.ANT1.HVPS

HVPS control & mgmnt

51.

AN

T1

.HV

RF

.INT

F.L

1

51.ANT1.HVCM.L1



51.

AN

T1

.FA

FB

.PR

OT

.L1

51.ANT1.HVPS.PROT.L1

51.A

NT

1.F

AF

B.P

RO

T.L

2

51

.AN

T1

.CO

NF

.PA

RA

.L4

51.

AN

T1

.CO

NF

.PA

RA

.L1

IO interface

I&C fct4

I&C fct3

I&C fct2

I&C fct1

CODAC interfaceControlle

r4. Assign control functions

to controllers in a consistent way / properties and PS operation.

I nterlock controller

Signal I nterface

Signal I nterface

Slow controller

Plant System Host 1

Plant system I &C 1 Plant system I &C 2

Master

CIS CODAC

PS coordination

PLANT SYSTEM

I nterlock controller

Signal I nterface

Signal I nterface

Slow controller

Plant System Host 1

CISCODAC

5. Build the I&C architecture with all controllers + PSH. Follow PCDH rules / architecture


I&C technical specificationsI&C architecture: status for PBS 62,63,65,43

• D1A: PS functional break down, general requirements for I&C including operation considerations. 620000-CCS-SA5-02-Reinforced Concrete I&C Overview (3G38L3 v1.3) (current)

630000-CCS-SA5-01 - Steel Frame Buildings (PBS63) - Plant System I&C Overview (3QTG8V v1.2) (current)

Liquid_Gas_Distribution_PBS65_IC_Overview (35ETBE v1.1) (current)

SSEN & PPEN I&C Overview (33L9QV v3.4) (current)

• D1B: Text + diagrams to elaborate on control function to be implemented, plus control function properties. As many D1Bs as required. Specific D1Bs for N-safety functions. Are in progress at IO, need to be reviewed by DAs.

• D1C: Text + diagrams, the complete functional and physical architecture.


I&C technical specificationsOther deliverables

• D2: PS I&C boundary, implemented by Interface Sheets (IS). Is derived from D1. Is not I&C specific.

• D3: I&C Integration plan, guidelines available for I&C FAT (3VVU9W v1.2). Should be integrated to the PA/PS integration plan.

• D4: P&ID, electrical diagrams, see CIE/DO. Is not I&C specific.

• D5: Controller performance and configuration requirements: is derived from D1. Is I&C specific.

• D6: List of controller I/O; normally derived from P&IDs and electrical diagrams. Is I&C specific.

• D7: List of Process Variables; is implemented by IS 45-XX. CODAC template available at (3NTEU3 v1.0). Is I&C specific.

• D8: Cubicle configuration; is derived from D1 and D5. Guidelines will be provided soon. Is I&C specific.

• D9: Plant System state machines: see Operation Handbook (2LGF8N v1.2).


FAT plans

Plant System Factory Acceptance Plan (3VVU9W v1.2)

• Configuration#1: the procurement only concerns equipment with sensors and actuators, without any I&C hardware.

• Configuration#2: procurement concerns equipment with I/Os chassis and boards, without CPU.

• Configuration#3: procurement concerns equipment with conventional and possibly interlock controllers (i.e. I/Os and CPUs), without PSH and mini-CODAC.

• Configuration#4: procurement concerns equipment, conventional and possibly interlock controllers and PSH + mini-CODAC .

• Campaigns split in scenarios depending on PS conf.• PS full plan to be defined depending on configuration


CODAC Standards illustrations

Specification of Cooling Water loop I&C use case (35W299 v3.2)

26PHDL-VC-0001

26PHDL-PL-0001

26PHDL-PZ-0001

P

L

T

26PHDL-HX-0001

26PHDL-VC-0003

26PHDL-VC-0007

26PHDL-VC-0004

26PHDL-VC-0005

F

P-100

26PHDL-VC-0008

26PHDL-HT-0001

26PHDL-VC-0006

Water storage and treatment CVCS

GN2 gas

supply

T

F

T

T

CC

WS

1

F

I-56

26PHDL-VC-0010

Client 1

26PHDL-VC-0013

26PHDL-VC-0014

Client 3

26PHDL-VC-0011

26PHDL-VC-0012

Client 2

26PHDL-VC-0009

P-111

26PHDL-VC-0002

• Targets: I&C specs + standard illustration • Development in progress (I&C + core CODAC)


PCDH v62011 release








PCDH v6 status • 10th Jan 2011: External review announcement: IO + DAs

• 10th Jan - 28th Jan 2011: Review period

• 8th Feb 2011: Review report – answer to comments – update the doc.

• PCR initiated.

• End Feb 2011: PCDH 6.1 and satellite docs release.

IO I&C [email protected];[email protected];[email protected];[email protected];[email protected];[email protected];[email protected];[email protected]@iter.org;[email protected];[email protected];[email protected];[email protected]@iter.org;[email protected];[email protected];[email protected];[email protected];[email protected]

DA I&C contact persons

[email protected];[email protected];[email protected]

o.jp;[email protected];[email protected];[email protected]

pa.eu;[email protected];[email protected];

IO PS RO


PCDH v6 set of documents

document updated / v5

Satellite documents: provide guidelines, recommendations and explanations, but no mandatory rules. Updaded documents / v5.

• Plant System I&C Architecture (32GEBH v2.3)

• Methodology for Plant System I&C specifications (353AZY v3.3)

• Signal and plant system I&C variable naming conventions (2UT8SH v7.3)

• Self-description schema documentation (34QXCP v2.1)

• The CODAC – Plant System Interface (34V362 v2.0)

• Guideline for Fast Controllers, I/O Bus Systems and Com. (333K4C v1.3)

• I&C signal interface (3299VT v4.4)

• Siemens S7 PLC Catalogue (333J63 v1.7)

• ITER Catalogue of I&C Products – Fast Controllers (345X28 v1.3)

• Plant Control Design Handbook for Nuclear control systems (2YNEFU v2.1)

Baseline document: PCDH (27LH2V v6.1) provides all rules, is contractually binding, is summited to PCR.


Satellite documents: provide guidelines, recommendations and explanations, but no mandatory rules. New documents / v5.

• CODAC Core System Overview (34SDZ5 v2.5)

• ITER CODAC Glossary (34QECT v1.2)

• ITER CODAC Acronyms (2LT73V v2.2)

• Plant System Factory Acceptance Plan (3VVU9W v1.5)

• Philosophy of ITER Alarm System Management (3WCD7T v2.0)

• Philosophy of ITER Operator User Interface (3XLESZ v2.0)

• Specification of Cooling Water loop I&C use case (35W299 v3.3)

• Software Engineering and Quality Assurance (2NRS2K v2.1)

• PLC software engineering handbook (3QPL4H v1.3)

• SAREL cubicle catalogue for plant system I&C (35LXVZ v2.3)

• Rules and Guidelines for the Design of the Plant Interlock System (PIS) (3PZ2D2 v2.4)

PCDH v6 set of documentsnew documents

• All are available on IDM except the master doc.

• All have been submitted to the external review.


PCDH v6 / v5

• I&C technical specs: Alignment with new version on design review procedure.

• New naming convention for variables: introduction of functional description.

• COS: Alignment with Operation Handbook.

• New sections for HMI and alarm handling guidelines.

• HW standards: Cubicle catalogue (recommended products).

• Signal interface: Alignment with EMC policy and cabling rules.

• Software development: New guidelines.

• Interlocks: new guidelines for PIS design.

• Safety: Simplification of PCDH-N.

• FAT: guidelines for I&C scenarios.

• Case studies: improvement on ICH and new CWS Case Study, illustration only


What is important for I&C

Compliance with PCRD requirements for:

• The plant system I&C architecture rules.

• The interface with CODAC systems: physical and functional.

• The HW standards: PLC, fast control technologies, cubicles, signal format.

• The SW standards: PLC, fast controls, EPICS, CODAC systems, …

• The naming conventions: components, signals, variables, …

• ITER EMC and radiation policy applicable to I&C equipment.

• Applicable standards for nuclear safety controls.

Thank you for your attention

The jointly IO/DA work along the I&C life-cycle

page 1 pcdh v6 presentation – io / engage meeting - 18/02/2011 pcdh v6 2011 release why to...

Documents

pcdh v6 presentation

standards pcdh

ic slide

illustration pcdh v6

iter slide

27lh2v v6

ic interlock

ic safety