1. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 1 Disclaimer: The views and opinions expressed herein do not necessarily reflect those of the ITER Organization Ralph Lange ITER Organization – Central Team – Control System Division ITER and CODAC Core System Status and Roadmap

2. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 2 ITER Agreement splits the project in procurement arrangements distributed among the seven members A bit of interface problems We forgot there is an interface between A and B We changed the design so the interface does not exist anymore Island mentality I did not know the others are doing the same thing in a different way I do not care what the others do. I build my system. Misinterpreted scope I forgot that I need that in my system That should be implemented in your system, not mine Introduction

3. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 3 The ITER control system performs the functional integration of the ITER plant and enables integrated and automated operation Introduction

4. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 4 Scope and Architecture

5. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 5 Scope and Architecture

6. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 6 The ITER control system is broken down in 18 ITER control groups covering 28 PBS An ITER control group contains many Plant System I&C A Plant System I&C is a deliverable from a procurement arrangement (IN-KIND) A procurement arrangement delivers a part, one or many Plant System I&C Scope and Architecture

7. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 7 MITIGATION Define standards, specifications and interfaces applicable to all plant systems instrumentation and control (PCDH) Develop and distribute a control system framework that implements standards defined in PCDH and guarantees that the local control system can be integrated into the central system: CODAC Core System Provide user support Organize training: PCDH campaign, CODAC Core System hands-on workshops at IO and DAs, videos on Online Learning Center) Provide I&C Integration Kit free of charge (PSH, Mini-CODAC, switch) Demonstrate system on pilot projects Organize user meetings Integration The main challenge for ITER Control System is INTEGRATION

8. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 8 I&C Standards – Catalogue Products Slow control Siemens S7-300 and S7-400 products ET200M and ET200S for remote I/O Covering standard industrial signals Cubicles Schneider Electric products Address floor standing and wall mounted cubicles Address Standard and EMC protected. Fast control PCI Express. CPU and I/O segregated Mainly National Instruments products Covering acquisition and control > 50 Hz

9. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 9 OS: Red Hat Enterprise Linux (RHEL x86_64) with MRG-R real-time extensions on fast controllers Infrastructure: EPICS, used in hundreds of projects world-wide: light sources, high energy physics, fusion (KSTAR, NSTX), telescopes CODAC services layer: Control System Studio used at many EPICS and other sites and including HMI, alarming, archiving etc. ITER specific software such as configuration (system description), state handling, drivers, networking, etc. Fix 6 month release cycle (major + minor release every year), extensive testing procedures CODAC Core System: Based on Open Source

10. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 10 Reorganization following changes at the top (new DG) Preparation of resource-loaded realistic schedule CODAC Core System release: 5.1 (2015B) –RHEL 6.5 –EPICS Base 3.15.2 –EPICS V4 (evaluation only) IO-CT takes more responsibility for EPICS Support New S7 communication drivers EPICS Support for NI RIO (ASYN and NDS) Building test stand for integration testing New Framework Contracts (2016-2019) Current Activities

11. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 11 Continue development and support of CODAC Core System Continue design of high level operation applications Continue design of Interlock and Safety Start implementing network infrastructure Engage with users (plant system I&C developers) Prepare for FATs (starting this year) Develop integration schedule and procedures What’s Next?

12. Spring 2015 EPICS Collaboration Meeting, 18-22 May 2015, FRIB East Lansing, MI, USA © 2015, ITER Organization Page 12 Thank you