Page 1 of 22

ITER_D_32GEBH

Plant System I&C Architecture

Technical Note

Abstract

This technical note discusses the architecture of the ITER Plant System Instrumentation & Control System. There will be more than 160 of these systems, each with different characteristics and requirements. They all have to be integrated in the ITER I&C System.

IDM Number: ITER_D_32GEBH v1.1 Date: 1 Feb 2010 Name Affiliation

Author Anders Wallander, Luigi Scibile CHD - CODAC Reviewer CODAC Team CHD - CODAC Approver Wolf-Dieter Klotz CHD

Page 2 of 22

ITER_D_32GEBH

Document Revision History

Version Status Date Summary of Changes 1.0 Issued 3 Dec 2009 First release

1.1 Issued 1 Feb 2010 After technical editing by JP and I&C IPT review

Page 3 of 22

ITER_D_32GEBH

Table of Contents

1 INTRODUCTION................................................................................................................................... 5

1.1 Objective .......................................................................................................................................... 5

1.2 Assumptions ................................................................................................................................... 5

1.3 References ...................................................................................................................................... 5

1.4 Acronyms ........................................................................................................................................ 6

2 PHYSICAL ARCHITECTURE .............................................................................................................. 7

2.1 OSI layer 2 switch ........................................................................................................................... 7

2.2 Plant System Host .......................................................................................................................... 8

2.3 Fast Controller ................................................................................................................................ 8

2.4 Slow Controller ............................................................................................................................... 8

2.5 Interlock Controller......................................................................................................................... 8

2.6 COTS Intelligent Device ................................................................................................................. 8

2.7 Remote I/O ....................................................................................................................................... 9

2.8 Signal Interface ............................................................................................................................... 9

2.9 Cubicles ........................................................................................................................................... 9

2.10 CODAC Terminal ............................................................................................................................. 9

2.11 High Performance Networks ......................................................................................................... 9

2.12 CODAC System / Mini-CODAC ...................................................................................................... 9

2.13 Central Interlock System ............................................................................................................... 9

3 FUNCTIONAL ARCHITECTURE ....................................................................................................... 10

3.1 Simplest possible Plant System I&C .......................................................................................... 10

3.2 Small Industrial Plant System I&C .............................................................................................. 11

3.3 Small Mixed Plant System I&C .................................................................................................... 12

3.4 Industrial Plant System I&C with Fast Acquisition ................................................................... 13

3.5 Complex Diagnostics Plant System I&C connected to PCS .................................................... 15

Page 4 of 22

ITER_D_32GEBH

4 CONCLUSIONS ................................................................................................................................. 18

5 APPENDIX - LIST OF PLANT SYSTEMS I&C .................................................................................. 19

Page 5 of 22

ITER_D_32GEBH

1 INTRODUCTION 1.1 Objective

This technical note discusses the architecture of plant system I&C. The objectives are to identify and define the plant system I&C components and their relations, to analyze the feasibility of implementing different types of plant system I&C using these components and to identify any weaknesses and problems in the approach.

This document is part of the PCDH documentation package (Fig 1.1).

Figure 1.1 Schema of PCDH documents

1.2 Assumptions

The starting point of the analysis is the CODAC conceptual design [RD1] and the Plant Control Design Handbook (PCDH) [RD2]. Design decisions taken during last year are incorporated, in particular the decision to use Siemens Simatic S7, EPICS and channel access communication middleware. This technical note does not address the safety control systems.

1.3 References

[RD1] CODAC Conceptual Design Overview (ITER_D_2EFVMC v1.0)

[RD2] Plant Control Design Handbook (ITER_D_27LH2V v5.1)

[RD3] I&C signal and process variable naming convention (ITER_D_2UT8SH v2.4)

Page 6 of 22

ITER_D_32GEBH

[RD4] ITER Control System Architecture - Technical Note (ITER_D_2VTVHT v1.1)

[RD5] I&C signal processing, part I cubicle and wiring configurations (ITER_D_3299VT v1.6)

1.4 Acronyms

AVN Audio Video Network CIN Central Interlock Network CIS Central Interlock System CODAC Control, Data Access and Communication COS Common Operating State COTS Commercial Off-The-Shelf CSS Central Safety Systems EPICS Experimental Physics and Industrial Control System HMI Human-Machine Interface HPN High Performance Networks I&C Instrumentation & Control I/O Input / Output IO ITER Organization IOC Input / Output Controller NTP Network Time Protocol OSI Open System Interconnect PCI Peripheral Component Interconnect PCIe PCI Express PCS Plasma Control System PLC Programmable Logic Controller PON Plant Operation Network PS Plant System PSH Plant System Host PV Process Variable RD Reference Document RHEL Red Hat Enterprise Linux SDN Synchronous Databus Network TBD To Be Defined TCN Time Communication Network

Page 7 of 22

ITER_D_32GEBH

2 PHYSICAL ARCHITECTURE Any plant system I&C is made up of a set of standard components. These standard components can be selected and combined in different ways to address the particular plant system I&C characteristics and requirements. The set of components can be viewed like Lego blocks to be assembled by the plant system I&C designer.

The baseline physical network topology is flat, i.e. all components are connected to the Plant Operation Network (PON) via a switch as illustrated in Figure 2.1 [RD4]. Although it is possible to physically connect components in a hierarchical way using private networks, this is not recommended since it will make remote maintenance more difficult. For example, a development station for a controller (not shown) could be connected anywhere on the PON and reach the target controller. The Central Interlock Network (CIN) is an independent network connecting the interlock controller to the Central Interlock System. The High Performance Networks (HPN) are physically separated networks, which may connect to the Plant System Host and/or fast controllers depending on the particular plant system I&C. All network connections are provided in CODAC hutches and network panels are distributed throughout all ITER site buildings.

The HPN lines pointing to the grey area indicate a possible connection as detailed in Chapter 3.

Actuators and sensors are considered outside the scope of plant system I&C.

Figure 2.1 Illustration of a possible plant system I&C physical architecture. Lines are cables.

2.1 OSI layer 2 switch

The OSI layer 2 switch is an IO furnished standard Ethernet switch which allows full management of the Plant Operation Network (PON). The OSI layer 2 switch is installed in a plant system I&C cubicle. There are one or more OSI layer 2 switches in a particular plant system I&C.

Page 8 of 22

ITER_D_32GEBH

2.2 Plant System Host

The Plant System Host (PSH) is 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. The PSH runs RHEL (Red Hat Enterprise Linux) and has an EPICS (Experimental Physics and Industrial Control System) soft IOC (Input Output Controller). It provides standard CODAC services such as health monitoring, maintenance functions and time source. The PSH is fully data driven, i.e. it is customized for a particular plant system I&C by self-description. There is no plant specific code in a PSH. A PSH has no I/O.

2.3 Fast Controller

A fast controller is a dedicated industrial controller implemented in PCI family form factor with PCIe communication fabric installed in a plant system I&C cubicle. There may be zero, one or many fast controllers in a plant system I&C. A fast controller runs RHEL and has EPICS IOC, it acts as a channel access server and exposes process variables (PV) [RD3] to PON. A fast controller normally has I/O and the IO supports a set of standard I/O modules with associated EPICS drivers. A fast controller may have interfaces to high performance networks (HPN), i.e. the Synchronous Databus Network (SDN) for plasma control, Time Communication Network (TCN) for absolute time and pre-programmed triggers and/or Audio Video Network (AVN) for video transfers. Fast controllers involved in critical real-time operations run a RT enabled (TBD) version of Linux on a separate core or CPU. A fast controller can have plant-specific logic and can act as supervisor for other fast controllers and/or slow controllers. The Plant System Operating State is maintained by the supervising controller..

2.4 Slow Controller

A slow controller is a Siemens Simatic S7 industrial programmable logic controller (PLC) installed in a plant system I&C cubicle. 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 with Step 7 and interfaces to either the PSH or a fast controller using an IO-furnished interface (EPICS driver and self description). A slow controller normally has I/O and the IO supports a set of standard I/O modules. A slow controller has no interface to the HPN. A slow controller can synchronize its time using NTP over PON. A slow controller can act as supervisor for other slow controllers. The Plant System Operating State is maintained by the supervising controller.

2.5 Interlock Controller

An interlock controller is a Siemens Simatic S7 FH industrial programmable logic controller (PLC) installed in a plant system I&C cubicle, possibly with hardwired logic for high performance protection functions. There may be zero, one or many interlock controllers in a plant system I&C. An interlock controller runs software and plant specific logic programmed with Step 7, interfaces to the Central Interlock System and to either a slow controller or a fast controller using digital I/O, depending on the functional requirements. An interlock controller normally has I/O and IO supports a set of standard I/O modules. An interlock controller can act as supervisor for other interlock controllers.

2.6 COTS Intelligent Device

A COTS intelligent device is a commercial off-the-shelf controller, which implements an integrated control function, e.g. a building management system or a power supply controller (such as intelligent electronic devices as defined by IEC 61850). A COTS intelligent device has an ethernet interface and is considered a black box in the ITER I&C System. A COTS intelligent device can be physically connected either to the OSI layer 2 switch or as a slave to a slow or fast controller. It is the responsibility of the plant system I&C developer to design and implement an interface, either to a slow controller or to a fast controller. The use of a COTS intelligent device in a plant system I&C has to be approved by the IO through the deviations policy defined in [RD2]. A COTS intelligent device is not maintained by the IO.

Page 9 of 22

ITER_D_32GEBH

2.7 Remote I/O

A remote I/O device is an I/O chassis, with or without intelligence, geographically separated from other plant system I&C components. A remote I/O device is connected to a slow controller or fast controller via a network or fieldbus. The IO provides a catalogue of standard remote I/O devices. An intelligent remote I/O device can be EPICS enabled and viewed as a fast controller from the CODAC System / Mini-CODAC.

2.8 Signal Interface

A signal interface is the mechanics, cabling and electronics between the actuators/sensors and the controllers. Signal interfaces are described in [RD5].

2.9 Cubicles

The components (switches, PSH, fast and slow controllers, part of signal interface) are embedded within cubicles defined in an IO catalogue of products. The unit for hardware delivery between the PS suppliers and IO, is a cubicle together with spare parts.

2.10 CODAC Terminal

A CODAC terminal is a standard terminal, connected to PON, providing a display unit and input devices (keyboard and mouse) to allow a human user to interact with the plant system I&C.

2.11 High Performance Networks

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

2.12 CODAC System / Mini-CODAC

The CODAC System / Mini-CODAC is not part of the plant system I&C. Mini-CODAC, which is a scaled down version of the CODAC System, is provided by the IO to all plant system I&C developers as a software package. Mini-CODAC provides all of the tools necessary to configure the plant system I&C using self-description, to implement the HMI, to monitor and supervise the plant system I&C, to configure and manage the network and to perform the factory acceptance test. The early use of Mini-CODAC in the development process will make later on-site integration seamless. Future versions of Mini-CODAC will support HPN, CIS and CSS. The CODAC System also receives data from the Central Interlock System to be displayed via the HMI and to be archived for post-mortem analysis following an interlock event.

2.13 Central Interlock System

The Central Interlock System (CIS) is not part of the plant system I&C. The Central Interlock System provides all necessary tools to configure the interlock controller(s) using self-description, to monitor and supervise the interlock controller(s), to configure and manage the CIN and to carry out the inter-plant protection functions. Future versions of Mini-CODAC will support CIS.

Page 10 of 22

ITER_D_32GEBH

3 FUNCTIONAL ARCHITECTURE Despite the flat network topology explained in the previous chapter, the functional architecture may be more hierarchical. In this chapter a number of example architectures are analyzed. Arrows are functional data flows, which can be mapped to the flat physical architecture presented in Chapter 2.

3.1 Simplest possible plant system I&C

In this example (Figure 3.1) we have the simplest possible plant system I&C consisting of only one slow controller. The slow controller interfaces via a signal interface to actuators and sensors.

Plant System

Host

Actuators and Sensors

Slow Controller

CODAC System /Mini-CODAC

Plant System I&C

Signal Interface

1 2

3

TCN

4

CODAC Terminal

Figure 3.1. Functional architecture and dataflow of the simplest possible plant system I&C

The CODAC System / Mini-CODAC send commands and, if required, publishes data from other plant system I&C to the PSH using the channel access protocol (1). This interface is also used to set runtime configuration properties. The PSH publishes data, alarms and logs to CODAC System / Mini-CODAC using the channel access protocol (2). This interface is also used to retrieve configuration properties. The interface between the PSH and the CODAC System / Mini-CODAC is fully defined and configured by self-description.

The PSH and slow controller exchange data using the standard interface provided by the IO (3). This interface is fully defined and configured by self-description. The PSH manages the COS.

The slow controller interfaces to actuators and sensors via a signal interface and contains plant-specific software and logic programmed with Step 7.

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

Page 11 of 22

ITER_D_32GEBH

3.2 Small Industrial Plant System I&C

In this example (Figure 3.2) we have a small plant system I&C consisting of three slow controllers. One slow controller is elevated as the supervising controller. The other two slow controllers interface to actuators and sensors via a signal interface. In addition, the plant system I&C implements interlock functions.

Figure 3.2. Functional architecture and dataflow of a small industrial plant system I&C

The CODAC System / Mini-CODAC sends commands and, if required, publishes data from other plant system I&C to the PSH using the channel access protocol (1). This interface is also used to set runtime configuration properties. The PSH publishes data, alarms and logs to CODAC System / Mini-CODAC using the channel access protocol (2). This interface is also used to retrieve configuration properties. The interface between the PSH and CODAC System / Mini-CODAC is fully defined and configured by self-description.

The PSH and supervising slow controller exchange data using the standard interface provided by the IO (3). This interface is fully defined and configured by self-description. The PSH supervises the supervising slow controller to manage COS.

The supervising slow controller implements plant specific coordination software and logic programmed with Step 7. The supervising slow controller interfaces to two other slow controllers (5) through the PON. The supervising slow controller could also have a direct interface to actuators and sensors via a signal interface (not shown). Non supervising slow controllers could also have direct interfaces to the PSH (not shown).

Page 12 of 22

ITER_D_32GEBH

Two slow controllers interface to actuators and sensors via a signal interface and contain plant specific software and logic programmed with Step 7.

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

The Central Interlock System sends commands to the interlock controller using the CIN (15) (protocol TBD). This interface is also used to set configuration properties and to distribute the absolute time. The interlock controller sends events, publishes data, alarms and logs to the Central Interlock System using the CIN (16) (protocol TBD). This interface is also used to retrieve configuration properties. The interface between the interlock controller and the Central Interlock System is fully defined and configured by self-description and they exchange data using a standard interface provided by the IO.

The interaction between the interlock controller and the supervising slow controller (17) is carried out by means of digital I/O.

The CODAC System receives data from the Central Interlock System to be displayed via the HMI and to be archived for post-mortem analysis following an interlock event via a dedicated secured gateway (not shown) using the channel access protocol (18). It sends its interlock signals by means of a dedicated secured gateway (19) and the requests for acknowledgement of alarms via a dedicated secured gateway using the channel access protocol (19).

3.3 Small Mixed Plant System I&C

In this example (Figure 3.3) we have a small plant system I&C consisting of one slow controller and one fast controller. The fast controller may be supervising the slow controller or they may be independent (not needing any coordination). The two controllers both interface to actuators and sensors via a signal interface. In addition the plant system I&C implements interlock functions.

The CODAC System / Mini-CODAC sends commands and, if required, publishes data from other plant system I&C to the PSH using the channel access protocol (1). This interface is also used to set runtime configuration properties. The CODAC System / Mini-CODAC may also send commands and, if required, publish data from other plant system I&C to the fast Controller using the channel access protocol (6). The PSH publishes data, alarms and logs to the CODAC System / Mini-CODAC using the channel access protocol (2). This interface is also used to retrieve configuration properties. The fast controller may also publish data, alarms and logs to CODAC System / Mini-CODAC using the channel access protocol (7). The interface between the PSH and the CODAC System / Mini-CODAC is fully defined and configured by self-description.

The PSH and slow controller exchange data using the standard interface provided by the IO (3). This interface is fully defined and configured by self-description.

The PSH supervises the fast controller (8) to manage COS.

The slow controller implements plant-specific software and logic programmed with Step 7. The slow controller interfaces via the signal interface to actuators and sensors.

The fast controller implements plant-specific logic in EPICS. The fast controller interfaces to actuators and sensors via the signal interface.

The fast controller could also interface directly to the slow controller using the standard interface provided by the IO (9).

The PSH receives absolute time from the TCN (4). The absolute time on the slow controller and fast controller can be set using NTP with the PSH as an NTP server. Alternatively, the fast controller could also be connected to the TCN.

Page 13 of 22

ITER_D_32GEBH

Figure 3.3. Functional architecture and dataflow of a small mixed plant system I&C

Either the fast controller or the slow controller provides the interface (17) with the interlock controller and acts as a supervisor for the other using the standard interface provided by the IO (9).

The Central Interlock System sends commands to the interlock controller using the CIN (15) (protocol TBD). This interface is also used to set configuration properties and to distribute the absolute time. The interlock controller sends events, publishes data, alarms and logs to the Central Interlock System using the CIN (16) (protocol TBD). This interface is also used to retrieve configuration properties. The interface between the interlock controller and the Central Interlock System is fully defined and configured by self-description and they exchange data using the standard interface provided by the IO.

The interaction between the interlock controller and the fast controller (17) (could also be the slow controller) is carried out by means of digital I/O.

The CODAC System receives data from the Central Interlock System to be displayed via the HMI and to be archived for post-mortem analysis following an interlock event via a dedicated secured gateway (not shown) using the channel access protocol (18). It sends its interlock signals by means of a dedicated secured gateway (19) and the requests for acknowledgement of alarms via a dedicated secured gateway using the channel access protocol (19).

3.4 Industrial Plant System I&C with Fast Acquisition

In this example (Figure 3.4) we have a plant system I&C consisting of many slow controllers, one COTS intelligent device, one remote I/O and one fast controller dedicated to fast acquisition. In addition, the plant system I&C implements interlock functions.

Page 14 of 22

ITER_D_32GEBH

Figure 3.4. Functional architecture and dataflow of an industrial plant system I&C with fast acquisition

The CODAC System / Mini-CODAC sends commands and, if required, publishes data from other plant system I&C to the PSH using the channel access protocol (1). This interface is also used to set runtime configuration properties. The CODAC System / Mini-CODAC may also send commands and, if required, publish data from other plant system I&C to the fast controller using the channel access protocol (6). The PSH publishes data, alarms and logs to the CODAC System / Mini-CODAC using the channel access protocol (2). This interface is also used to retrieve configuration properties. The fast controller may also publish data, alarms and logs to CODAC System / Mini-CODAC using the channel access protocol (7). This interface can also be used to transfer acquired data for visualization and archiving. The interface between the PSH and the CODAC System / Mini-CODAC is fully defined and configured by self-description.

The PSH and supervising slow controller exchange data using the standard interface provided by the IO (3). This interface is also fully defined and configured by self-description. The PSH manages the COS.

The supervising slow controller implements plant-specific coordination software and logic programmed with Step 7. The supervising slow controller interfaces to four other slow controllers and one COTS intelligent device (5). The supervising slow controller could also have a direct interface to actuators and sensors via the signal interface (not shown). The non-supervising slow controllers could also have direct interfaces to the PSH (not shown).

The slow controllers implement plant-specific software and logic programmed with Step 7. One slow controller interfaces to a remote I/O (11).

The slow controllers, remote I/O and COTS intelligent device interface to actuators and sensors.

The PSH supervises the fast controller (8) to manage the COS.

Page 15 of 22

ITER_D_32GEBH

The fast controller implements plant-specific logic in EPICS. The fast controller interfaces to actuators and sensors via the signal interface.

Data acquisition by the fast controller can be triggered by the PSH (8), slow controller (9), CODAC System / Mini-CODAC (6) and/or the TCN (10). The latter can through be a pre-programmed trigger(s) or pre-programmed absolute time(s).

The PSH receives absolute time from the TCN (4). The fast controller receives absolute time from the TCN (10). The absolute time on the slow controllers can be set using the NTP with the PSH as an NTP server.

Central Interlock System sends commands to the interlock controllers using the CIN (15) (protocol TBD). This interface is also used to set configuration properties and to distribute the absolute time. The interlock controller sends events, publishes data, alarms and logs to the Central Interlock System using the CIN (16) (protocol TBD). This interface is also used to retrieve configuration properties. The interface between the interlock controller and the Central Interlock System is fully defined and configured by self-description and they exchange data using the standard interface provided by the IO.

The interaction between the interlock controller and the supervising slow controller (17) is carried out by means of digital I/O.

The CODAC System receives data from the Central Interlock System to be displayed via the HMI and data to be archived for post-mortem analysis following an interlock event via a dedicated secured gateway (not shown) using the channel access protocol (18).It sends its interlock signals by means of a dedicated secured gateway (19) and the requests for acknowledgement of alarms via a dedicated secured gateway using the channel access protocol (19).

3.5 Complex Diagnostics plant system I&C connected to PCS

In this example (Figure 3.5) we have a complex diagnostics plant system I&C participating in plasma control and consisting of many fast controllers and one slow controller. In addition the plant system I&C implements interlock functions.

The CODAC System / Mini-CODAC sends commands and, if required, publishes data from other plant system I&C to the PSH using the channel access protocol (1). This interface is also used to set runtime configuration properties. The CODAC System / Mini-CODAC may also send commands and, if required, publish data from other plant system I&C to fast controller using the channel access protocol (6).The PSH publishes data, alarms and logs to CODAC System / Mini-CODAC using the channel access protocol (2). This interface is also used to retrieve configuration properties. The fast controller may also publish data, alarms and logs to the CODAC System / Mini-CODAC using the channel access protocol (7). The interface between the PSH and the CODAC System / Mini-CODAC is fully defined and configured by self-description.

The PSH supervises the fast controller (8) to manage the COS.

Page 16 of 22

ITER_D_32GEBH

Figure 3.5. Functional architecture and dataflow of a complex diagnostics plant system I&C connected to PCS

The supervising fast controller implements plant-specific coordination logic in EPICS. It also implements real-time logic using a real-time operating system on a different core or CPU. The supervising fast controller interfaces to three other fast controllers and one slow controller (5). The supervising fast controller and slow controller exchange data using the standard interface provided by the IO (8). The fast controllers may or may not run EPICS. The fast controllers implement plant-specific logic. The slow controller implements plant-specific software and logic programmed with Step 7. The supervising fast controller could also have a direct interface to actuators and sensors via a signal interface (not shown). The non supervising fast and slow controllers could also have direct interfaces to the PSH (not shown). The non supervising fast controllers could also have a direct interface to the CODAC System / Mini-CODAC (not shown).

The supervising fast controller streams scientific data to the CODAC System / Mini-CODAC for visualization and archiving (12). The non supervising fast controllers could also stream scientific data to the CODAC System / Mini-CODAC for visualization and archiving (not shown).

The PSH receives absolute time from the TCN (4). The fast controller receives absolute time from the TCN (10). The absolute time on the slow controller and other fast controllers can be set using the NTP with the PSH as an NTP server. Alternatively, other fast controllers could also be connected to the TCN.

The supervising fast controller pre-processes and publishes data for the PCS on the SDN (13). The raw data may originate from multiple other fast controllers. In addition, any fast controller could receive data from the SDN according to specific events in order to change acquisition behaviour.

One fast controller interfaces to a camera and streams the data on the AVN (14).

The supervising fast controller provides the interface (17) to the interlock controller.

Central Interlock System sends commands to the interlock controller using the CIN (15) (protocol TBD). This interface is also used to set configuration properties and to distribute the absolute time. The interlock controller sends events, publishes data, alarms and logs to Central Interlock System using the CIN (16) (protocol TBD). This interface is also used to retrieve configuration properties. The interface between the

Page 17 of 22

ITER_D_32GEBH

interlock controller and the Central Interlock System is fully defined and configured by self-description and they exchange data using the standard interface provided by the IO.

The interaction between the interlock controller and the supervising controller (17) is carried out by means of digital I/O.

The CODAC System receives data from the Central Interlock System to be displayed via the HMI and to be archived for post-mortem analysis following an interlock event via a dedicated secured gateway (not shown) using the channel access protocol (18). It send its interlock signals by means of a dedicated secured gateway (19) and the requests for acknowledgement of alarms via a dedicated secured gateway using the channel access protocol (19).

Page 18 of 22

ITER_D_32GEBH

4 CONCLUSIONS In this technical note the standard components making up a plant system I&C have been identified and defined. The flexibility in combining these standard components in the design of different types of plant system I&C has been emphasized.

Page 19 of 22

ITER_D_32GEBH

5 APPENDIX - LIST OF PLANT SYSTEMS I&C

Subsystem PBS Name of plant system I&C Tokamak 15IS?? Vacuum Vessel 16???? Blanket 17???? Divertor 24CR?? Cryostat 24VP?? Vacuum Vessel Pressure Suppression System 27???? Thermal Shield Cryo & Cooling 26TC?? Tokamak Cooling Water System (TCWS) 26CC?? Component Cooling Water System 26CH?? Chilled Water System 26HR?? Heat Rejection System 34???? Cryoplant and cryodistribution Magnetic Field 11IF?? Magnets 41???? CC Coils Power Supplies 41???? CS/PF Coils Power Supplies 41???? TF Coils Power Supplies Building and Power 43???? High Voltage SSEN system 43???? SSEPN emergency power supply system train-A 43???? SSEPN emergency power supply system train-B 43???? SSEPN investment protection power supply 43???? SSEPN MV distribution zone-1 43???? SSEPN MV distribution zone-2 43???? SSEPN MV distribution zone-3 62???? Building Management System for Tokamak Building-11 62???? Lay-down and assembly hall 62???? Building Management System for Tritium Building-14 62???? Building Management System for Hot Cell Building-21 62???? Building Management System for Radwaste Building-23 62???? Building Management System for Personal Access Building-24 62???? Building Management System for Control Building-71 62???? Building Management System for Diagnostics Building-74 62???? Building Management System for Assembly Building-13 62???? Building Management System for RF Heating Building-15 62???? Building Management System for Magnet power conversion

Building-32 62???? Building Management System for Magnet power conversion

Building-33 62???? Building Management System for NBI Building-34 62???? Building Management System for Main AC distribution Building-36 62???? Building Management System for NBI High Voltage Building-37 62???? Building Management System for Reactive power control Building-

38 62???? Building Management System for Emergency power supply-A

Building-44 62???? Building Management System for Emergency power supply-B

Building-45 62???? Building Management System for Medium voltage distribution-1A

Building-46 62???? Building Management System for Medium voltage distribution-2B

Building-47 62???? Building Management System for Cryoplant compressor Building-

51

Page 20 of 22

ITER_D_32GEBH

Subsystem PBS Name of plant system I&C

62???? Building Management System for Cryoplant coldbox Building-52 62???? Building Management System for PF Coil Fabrication Building-55 62???? Building Management System for Site Service Building-61 62???? Building Management System for Resistor Building-75 65???? Breathable Air 65???? Compressed Air 65???? Demineralized Water Distribution System 65???? Fire Protection Water 65???? Helium Gas Distribution 65???? Hot Water Distribution System 65???? Nitrogen Gas Distribution 69???? Access Control Fuelling and Vacuum 1801?? Pellet Injection 1806?? Gas Injection 1807?? Glow Discharge Conditioning 31???? Vacuum Pumping 32???? Tritium Plant 32???? Water Detritation Heating 51???? ICH&CD plant system first antenna 51???? ICH&CD plant system second antenna 51???? RF Test Facility 52???? Electron Cyclotron Heating and Current Drive 53???? Diagnostic Neutral Beam – Beam Line 53???? Diagnostic Neutral Beam – Data Acquisition 53???? NBH & CD System – Beam 1 53???? NBH & CD System – Beam 2 54???? Lower Hybrid Heating and CD system Remote Handling 23???? Remote Handling Control System 23???? In-Vessel Viewing System Hot cell and environment 64???? Radiological and Environmental Monitoring System 66???? Radwaste Treatment and Storage System 67???? Hot Cell Plant System Test Blanket 56???? Test Blanket System (He-Cooled Ceramic Breeder – CN) 56???? Test Blanket System (He-Cooled Ceramic Breeder – KO) 56???? Test Blanket System (He-Cooled Lithium Lead – EU) 56???? Test Blanket System (He-Cooled Pebble Beds – EU) 56???? Test Blanket System (Lithium-Lead Ceramic Breeder – IN) 56???? Test Blanket System (Water-Cooled Ceramic Breeder – JA) Diagnostics 55???? Up 01 55???? Up 14 55???? Up 03 55???? Up 11 55???? Up 18 55???? Up 02 55???? Up 07 55???? Up 08 55???? Up 09 55???? Up 10 55???? Up 17 55???? Eq 01 55???? Eq 03 55???? Eq 09 55???? Eq 10 55???? Eq 11 55???? Eq 12 55???? Dv 02

Page 21 of 22

ITER_D_32GEBH

Subsystem PBS Name of plant system I&C

55???? Dv 08 55???? Dv 10 55???? Dv 14 55???? Dv 16 55???? Up 05 55???? Outer vessel magnetics 55???? In-vessel magnetics (eq. port sensors) 55???? In-vessel magnetics (lower feeds) 55???? In-vessel magnetics (upper feeds) 55???? Divertor magnetics 55???? Diamagnetic loop 55???? Halo current sensor (lower feeds) 55???? Halo current sensor (upper feeds) 55???? Radial neutron camera 55???? Vertical neutron camera 55???? Microfission chamber 55???? Neutron flux monitors 55???? Radial gamma-ray spectrometers 55???? Activation system equatorial feed 55???? Activation system lower feed 55???? Activation system upper feed 55???? High resolution neutron spectrometer 55???? Vertical gamma-ray spectrometer 55???? Divertor neutron flux monitor 55???? Thomson scattering (core) 55???? Thomson scattering (edge) 55???? Thomson scattering (divertor, outer) 55???? Toroidal interferometer / polarimeter 55???? Polarimeter (equatorial sightlines) 55???? Polarimeter (upper sightlines) 55???? Collective Thomson scattering (LFS) 55???? Bolometer (equatorial feeds) 55???? Bolometer (lower feeds) 55???? Bolometer (upper feeds) 55???? CXRS based on DNB (core) 55???? H-alpha (+visible spectroscopy) equatorial feeds 55???? H-alpha (+visible spectroscopy) upper feeds 55???? VUV (main plasma) broadband survey 55???? VUV (main plasma) high resolution imaging 55???? Impurity influx monitor (divertor vis/UV), divertor view 55???? Impurity influx monitor (divertor vis/UV), equatorial view 55???? Impurity influx monitor (divertor vis/UV), upper view 55???? X-ray crystal spectrometer (core high-res) 55???? Radial X-ray camera 55???? Neutral particle analyser 55???? Laser-induced fluorescence 55???? MSE based heating beam 55???? CXRS based on DNB (edge) 55???? X-ray crystal spectrometer (edge high-res) 55???? Survey X-ray crystal spectrometer 55???? Hard X-ray monitor (H-phase) 55???? Beam emission spectroscopy (core) 55???? Beam emission spectroscopy (edge) 55???? Divertor VUV spectroscopy (L16 or E11) 55???? ECE front end / receiver 55???? Reflectometer (main plasma, LFS)

Page 22 of 22

ITER_D_32GEBH

Subsystem PBS Name of plant system I&C 55???? Plasma position reflectometry (gap 3) 55???? Plasma position reflectometry (gap 4,6) 55???? Plasma position reflectometry (gap 5) 55???? Reflectometer (main plasma, HFS) 55???? Interferometer (divertor) 55???? ECE transmission and receivers 55???? IR cameras, vis/IR TV (midplane) 55???? Thermocouples (outer target) 55???? Pressure gauges 55???? Residual gas analyzers / penning gauges (equatorial) 55???? Residual gas analyzers / penning gauges (lower) 55???? IR thermography 55???? Langmuir probes 55???? IR cameras, vis/IR TV (upper) 55???? Thermocouples (inner target + vessel) 58???? Port Plug Test Facility

Table 1. Tentative list of plant system I&C and grouping in ITER Subsystems