Requirements for ITER CODAC Franck Di Maio CODAC

Requirements for ITER CODAC Franck Di Maio CODAC & IT CHD Department EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 1

Outline Ø Ø Ø Ø Introduction: PSH & Mini-CODAC R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 2

Introduction ITER I&C Architecture EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 3

Introduction CODAC Architecture Operator Software Synchronous Data Central CODAC Systems Plasma Control Middleware Plant System Host Fast Controller PLC EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 4

Introduction CODAC Architecture Plant System Host (PSH) q Is integrated in the Plant System Instrumentation & Control (I&C). q Provides a single point of entry for communication between the CODAC Systems and the plant system’s local controllers. q Is in charge of: Operator Software Synchronous Data Central CODAC Systems Plasma Control – – – Middleware Plant System Host Fast Controller configuration management, command dispatching, state monitoring, alarms and logs interfacing, data flow and events dispatching. q Is supplied by ITER IO PLC EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 5

Introduction CODAC Architecture Mini-CODAC Before Integration q Implements a sub-set of the CODAC systems functions. q Provides a SCADA environment for the development – Configuration Management – Local supervision – Human Machine Interface (HMI) – Alarms, logs, data handling… Mini-CODAC Synchronous Data Middleware q Is a tool for acceptance tests at factory and on site Plant System Host Fast Controller PLC EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 6

Outline Ø Ø Ø Ø Introduction R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 7

R&D Tasks SCADA Survey q Market Survey + evaluation of selected products against ITER Requirements. i. FIX Ø The open source products, EPICS & TANGO, are the ones that match the ITER requirements at best. – TANGO relies on recent technology. – EPICS benefits from a large community and a strong support. Contract with ATOS Origin EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 9

R&D Tasks Communication Technologies Survey q Evaluation of selected communication technologies against some specific user-cases. Channel Access CORBA DDS ICE TAO, Omni. ORB RTI Zero. C Ø Channel Access and CORBA have limits but replacement or complement isn’t justified now. Ø It is recommended to use an API that abstract the implementation. Channel Access Limits No built-in commands invocation Ø OK for a model with simple commands. Performances OK, except for large data Ø New version or dedicated data-stream services Scalability is limited Ø Multi-layers architecture Contract with Cosylab EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 10 10

R&D Tasks PSH Prototype Objectives: q On site evaluation of EPICS and Tango q Pre-engineering of CODAC concepts Use cases: 1. Direct control of the I/O channels of a PLC. 2. Integration of another type of PLC simulating the control of a plant system. Implemented on both EPICS and TANGO. Contract with Alceli Hunt Beratung EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 11

R&D Tasks Prototype Architecture EPICS MEDM, Striptool Python/Java/C/C++ TANGO Mini-CODAC 1 Mini-CODAC 2 Jdraw, atkmoni Python/Java/C/C++ Ethernet NW (PON) S 7 IOC, CPS IOC, Modbus IOC, PSH 1 PSH 2 S 7 DS, CPS DS, Modbus DS, Simple case DS Ethernet NW (PS LAN) S 7 / TCP Power Supply Simulation (complex case) Siemens S 7/300 Modbus / TCP I/O interface (simple case) Yokogawa Stardom FCJ EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 12

R&D Tasks Prototyping Results q The 2 use cases have been implemented. Ø Both EPICS and Tango are acceptable base for implementing the functions and the CODAC concepts. PSH Slow Controller EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 13

The EPICS Decision Ø It is a necessity for ITER to standardize the Plant System’s controller software at the very beginning. Currently: 161 plant systems with FAT starting in 2012. Ø Feb-09: EPICS will be used as the baseline for the software environment for the ITER control system Plant Control Design Handbook, vs. 4. 1, 06 -May-2009: The software infrastructure for PSH and Mini-CODAC is EPICS version R 3. 14. 10. [R 111] EPICS version R 3. 14. 10 shall be used for PS fast controllers. [R 112] Communication between PS fast controllers and PSH shall use EPICS Channel Access. [R 113] The Operating System of the PS fast controllers shall be Linux (version [TBD]). Deviations may be considered by IO for difficult real-time cases. … and PLC are Siemens Simatic S 7 (same document) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 14

Outline Ø Ø Ø Ø Introduction R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 15

Core Systems Plans q Core functions: – Communications – “SCADA” functions: • HMI • Alarm Handling • Error & trace logging • Parameters monitoring • Plant system supervision • Data Archiving • Testing – Configuration management (self-description) q To be implemented by packaged CODAC core systems Ø Built and distributed in an incremental manner. – One major release / year (1 st quarter) – Starting from 2010 Ø According to the Mini-CODAC architecture for now. EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 16

Roadmap Plans Vs 1 2010/Q 1 Preliminary Release Vs 2 2011/Q 1 Stable release for developers Vs 3 2012/Q 1 Stable release for FAT Priorities: 1. Integrate PLCs (Siemens S 7) 2. Develop configuration management (self-description) 3. Freeze the Application Programming Interfaces (APIs) 4. Integrate fast controllers (EPICS IOC) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 17

Plans Resources q IO staff estimation: 4 -6 ppy (2009 -2012) q Task Agreement with ITER-IN (3 years, from 2009/Q 3) on PSH and Prototype Mini-CODAC q Support contract (3 years, from 2009/Q 4) for EPICS, QA & user support. q New contracts in 2010 q Surveys and collaborations – EPICS Tools survey (June 2009) – Task Agreement with ITER-KO on EPICS for Tokamak (August 2009) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 18

Outline Ø Ø Ø Ø Introduction R&D Tasks The EPICS Decision Plans Self-Description (Denis Stepanov) Architecture & tools Conclusion EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 19

Plant System Self-Description … is a concept of providing all the necessary information about Plant Systems along with the Plant Systems themselves. The ultimate goal is to make both Plant Systems I&C and CODAC software system-neutral, decreasing the hard-coded programming part of the system specificity and increasing the data configuration part. … represents static configuration data not changing during the Plant System operation. It can be modified through dedicated maintenance procedures. … forms a part of software interface between the Plant Systems I&C and Central I&C Systems. … shall capture all “hidden knowledge” of Plant System configuration, at least in the form of documentation. … is expressed in XML constrained by a well-defined W 3 C XML Schema (XSD). … has to be introduced and actively supported by the software from the very beginning to avoid being a huge set of inconsistent, unreliable, poorly maintained data. EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 20

Self-Description Scope The Self-Description Data consist of: Plant System I&C unique identification; Command list; Alarms list; Set-points list; Plant System I&C Operating Limits and Conditions; Physical (raw) signals list (I/O); Processed / converted signals list; Data streams list; Logging messages list; Definition of the Plant System I&C state machine in accordance with the defined Plant System operating states; Definitions of Plant System I&C HMI; Initial values for run-time configuration used for Plant System I&C startup; Identification of source codes and binary packages of the Plant System I&C specific software; Documentation. (as stated in the Plant Control Design Handbook v 4. 1, May 2009) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 21

Device descriptions for EPICS and TANGO in XML EPICS (mapping of EPICS text templates and substitution lists) TANGO (mapping of TANGO’s My. SQL database) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 22

Self-description dataflow: operation PS parameters 2 7 PS response PS data 6 5 3 PS dynamic parameters 4 PS devices dynamic parameters 1 PSH static configuration EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 23

Self-description dataflow: development CODAC test data PS development progress 12 12 12 PS requirements and needs Problem report 10 11 PS parameters PCDH deliverables 4 1 PS description 9 PS response PS data 8 7 5 6 PS dynamic parameters 2 PSH static configuration PS devices dynamic parameters 2 Devel tools’ project files Program development 3 PS devices programs + static configuration 3 EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 24

Outline Ø Ø Ø Ø Introduction R&D Tasks The EPICS Decision Plans Self-Description Architecture & tools Conclusion EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 25

Core Systems, Mini-CODAC Architecture CODAC Systems: § Alarm Handling (AH) § Error & Trace Logging (EL) § Live Database/Monitoring (LD) § Data Archiving (DA) § Data Retrieval (DR) § Testing Tools (TT) § Communication Middleware (CM) § Generic Plant System Software (PS) § Visualization / HMI Builder (VB) § Plant System self description (SD) EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 26

Pure EPICS Architecture Configuration Synoptics Alarms Data Archiver Errors/trace Logging q Select the best EPICS mature tools to cover the core functions q Benefit: – Stable – Widely used (support) q Limits: – Not fully consistent – Migration to new ITER adapted tools. q The 2010 version: – EPICS tools – A 1 st version of the self -description system – S 7 PLC integration EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 27

The Eclipse Mini-CODAC Alternative Use Eclipse RCP for Mini-CODAC q Use the Eclipse technology for Mini. CODAC – a consistent environment integrating the different functions. q Join the CSS club for adopting/improving and developing new tools. q Considered for future releases (> 1). EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 28

Vs 1 Architecture (pure EPICS) EPICS components: • VDCT • SNL and Sequencer • EDM • auto. Save • ALH • Channel Archive/Retrieval • Channel Access Gateway • Ioc. Log. Server • Wireshark-CACasnooper • CAJ • Co. Thread • S 7 PLC driver EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 29

Conclusion - Main Requirements Specific constraints Ø The ITER schedule Ø The ITER procurement model Ø The ITER size (~200 systems) IO 2012: start of FAT 2015: start of integration 2018: first plasma Main requirements: Ø A very good EPICS Base for many years (procurement: 10+) DA Lab DA Ind – Prescribed as a standard for all plant systems controllers, from R 3. 14. 10. Ø Plant System Host with high reliability and high performance – The critical interface between IOCs and central systems – Key components: CA gateway, S 7 driver, RIOC (Linux, ATCA? ) Ø Implementation of the self-description concept – A “prescriptive” management system for the plan systems – With special requirements (XML, deliverable) Ø New tools for central services and HMI – CSS tools? To be evaluated for Vs 2 or 3 Ø A stable API for the high-level applications – Required for the design of ITER-specific applications (ex: scheduling system). EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 30

EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 31

EPICS Collaboration Meeting July 29, 2009, Daejeon, Korea Page 32