COntrol, Data Access and Communication System for ITER ITER CODAC COntrol, Data Access and Communication System for ITER Anders Wallander ITER Organization (IO) 13067 St. Paul lez Durance, France

Basics Plasma is an ionized hot gas The fourth state of matter Lawson criterion (“triple product”) Temperature * Density * Time > Big Number

ITER Goal: Demonstrate feasibility of fusion as an energy source Metric: Q=10 sustained for 300-500 seconds (Q=10 means output power equal 10 times input power) Schedule: 10 years construction phase just started First plasma 2019, first D-T plasma 2027 Collaboration: CN, EU, IN, JA, KO, RF, US Method: Magnetic confinement (Tokamak)

This is ITER

This is the ITER Agreement 140 slices

A bit of interface problems

Island mentality

Missing Items

The control system can help to fix this

The control system is horizontal

it connects to everything

it identifies and may eliminate missing items

it integrates

and is the primary tool for operation

But this will only work if… …all these links work Standards Architecture

EPICS In February 2009 ITER Organization decided to use EPICS for the control system This decision was based on three independent studies In February 2010 ITER Organization released the first version of CODAC Core System, which basically is a package of selected EPICS products

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

Plant System I&C Is a deliverable by ITER member state. Set of standard components selected from catalogue. One and only one plant system host.

ITER Subsystem is a set of related plant system I&C

CODAC Servers and Terminals are servers running Red Hat Enterprise Linux (RHEL) and EPICS/CSS/???. These servers implements supervision, monitoring, coordination, configuration, automation, data handling, archiving, visualization, HMI…

Plant Operation Network is the work horse general purpose flat network utilizing industrial managed switches and mainstream IT technology

Plant System Host 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. PSH runs RHEL (Red Hat Enterprise Linux) and EPICS (Experimental Physics and Industrial Control System) soft IOC (Input Output Controller). It provides standard functions like maintaining (monitoring and controlling) the Common Operation State (COS) of the Plant System. PSH is fully data driven, i.e. it is customized for a particular Plant System I&C by configuration. There is no plant specific code in a PSH. PSH has no I/O.

Slow Controller is 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 (EPICS driver and self description). 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 Controller is 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 Networks are 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.

Estimate of system size ITER subsystem # of PS I&C # of PSH+controllers # of servers+terminals Tokamak 6 55 Cryo and cooling water 5 40 3 Magnets and coil power supply 8 30 Building and power 37 66 Fuelling and vacuum 45 Heating 4 Remote handling 2 15 Hot cell and environment 20 Test blanket 24 7 Diagnostics 89 400 Central 170 TOTAL 167 750 220 ~1000 computers connected to PON

Conclusions The non-technical peculiarities of the ITER project has been addressed Components making up ITER control system have been defined and a baseline architecture outlined Flexibility in combining these standard components have been emphasized Having a set of standard components and a sound architecture will ease integration We would like to thank the EPICS community allowing us to get started very quickly on the ITER control system We promise to pay back to the community in the future with the development of ITER control system and an enlargement of the community https://www.iter.org/org/team/chd/cid/codac/Pages/