Author: Yonekawa, I.
Paper Title Page
MOPPC014
 Diagnostic Use Case Examples for ITER Plant Instrumentation and Control 85
 
  • S. Simrock, L. Abadie, R. Barnsley, L. Bertalot, J.Y. Journeaux, P. Makijarvi, V. Martin, P. Patil, R. Reichle, D. Stepanov, G. Vayakis, A. Wallander, M. Walsh, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
  • D.R. Makowski
    TUL-DMCS, Łódź, Poland
  
  ITER requires extensive diagnostics to meet the requirements for machine operation, protection, plasma control and physics studies. The realization of these systems is a major challenge not only because of the harsh environment and the nuclear requirements but also with respect to plant system Instrumentation and Control (I&C) of all the 45 diagnostics systems since the procurement arrangements of the ITER diagnostics with the domestic agencies require a large number of high performance fast controllers whose choice is based on guidelines and catalogues published by the ITER Organization (IO). The goal is to simplify acceptance testing and commissioning for both domestic agencies and the IO. For this purpose several diagnostic use case examples for plant system I&C documentation and implementation are provided by IO to the domestic agencies. Their implementations cover major parts of the diagnostic plant system I&C such as multi-channel high performance data and image acquisition, data processing as well as real-time and data archiving aspects. In this paper, the current status and achievements in implementation and documentation for the use case examples are presented.  
poster icon Poster MOPPC014 [2.068 MB]  
 
TUCOAAB03
 Approaching the Final Design of ITER Control System 490
 
  • A. Wallander, L. Abadie, F. Di Maio, B. Evrard, C. Fernandez Robles, J.L. Fernández-Hernando, J-M. Fourneron, J.Y. Journeaux, C.S. Kim, K. Mahajan, P. Makijarvi, S. Pande, M.K. Park, V. Patel, P. Petitbas, N. Pons, A. Simelio, S. Simrock, D. Stepanov, N. Utzel, A. Vergara-Fernandez, A. Winter, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
  
  The control system of ITER (CODAC) is subject to a final design review early 2014, with a second final design review covering high-level applications scheduled for 2015. The system architecture has been established and all plant systems required for first plasma have been identified. Interfaces are being detailed, which is a key activity to prepare for integration. A built to print design of the network infrastructure covering the full site is in place and installation is expected to start next year. The common software deployed in the local plant systems as well as the central system, called CODAC Core System and based on EPICS, has reached maturity providing most of the required functions. It is currently used by 55 organizations throughout the world involved in the development of plant systems and ITER controls. The first plant systems are expected to arrive on site in 2015 starting a five-year integration phase to prepare for first plasma operation. In this paper, we report on the progress made on ITER control system over the last two years and outline the plans and strategies allowing us to integrate hundreds of plant systems procured in-kind by the seven ITER members.  
slides icon Slides TUCOAAB03 [5.294 MB]  
 
TUMIB08
 ITER Contribution to Control System Studio (CSS) Development Effort 540
 
  • N. Utzel, L. Abadie, F. Di Maio, J.Y. Journeaux, A. Wallander, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
  • F. Arnaud, G. Darcourt, D. Dequidt
    Sopra Group, Aix-en-Provence, France
  
  In 2010, Control System Studio (CSS) was chosen for CODAC - the central control system of ITER - as the development and runtime integrated environment for local control systems. It became quickly necessary to contribute to CSS development effort - after all, CODAC team wants to be sure that the tools that are being used by the seven ITER members all over the world continue to be available and to be improved. In order to integrate CSS main components in its framework, CODAC team needed first to adapt them to its standard platform based on Linux 64-bits and PostgreSQL database. Then, user feedback started to emerge as well as the need for an industrial symbol library to represent pump, valve or electrical breaker states on the operator interface and the requirement to automatically send an email when a new alarm is raised. It also soon became important for CODAC team to be able to publish its contributions quickly and to adapt its own infrastructure for that. This paper describes ITER increasing contribution to the CSS development effort and the future plans to address factory and site acceptance tests of the local control systems.  
slides icon Slides TUMIB08 [2.970 MB]  
poster icon Poster TUMIB08 [0.959 MB]  
 
TUCOCA02
 The ITER Interlock System 910
 
  • A. Vergara-Fernandez, J.L. Fernández-Hernando, C. Fernandez-Robles, A. Wallander, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
  • A. Marqueta Barbero, I.P.D. Prieto Díaz
    IBERINCO, Madrid, Spain
  • R. Pedica
    Vitrociset s.p.a, Roma, Italy
  • M. Savouillan
    Assystem E&OS, Pertuis, France
  • S. Sayas
    ARKADIA Technology, Aix en Provence, France
  
  ITER is formed by systems which shall be pushed to their performance limits in order to successfully achieve the scientific goals. The scientists in charge of exploiting the tokamak will require enough operational flexibility to explore as many plasma scenarios as possible while being sure that the integrity of the machine and safety of the environment and personnel are not compromised. The I&C Systems of ITER has been divided in three separate tiers: the conventional I&C, the safety system and the interlock system. This paper focuses on the latter. The design of the ITER interlocks has to take into account the intrinsic diversity of ITER systems, which implies a diversity of risks to be mitigated and hence the impossibility to implement a unique solution for the whole machine. This paper presents the chosen interlock solutions based on PLC, FPGA, and hardwired technologies. It also describes how experience from existing tokamaks has been applied to the design of the ITER interlocks, as well as the ITER particularities that have forced the designers to evaluate some technical choices which historically have been considered as non-suitable for implementing interlock functions.  
slides icon Slides TUCOCA02 [3.303 MB]  
 
THPPC004
 CODAC Standardisation of PLC Communication 1097
 
  • S. Pande, F. Di Maio, B. Evrard, K. Mahajan, P. Sawantdesai, A. Simelio, A. Wallander, I. Yonekawa
    ITER Organization, St. Paul lez Durance, France
  
  As defined by the CODAC Architecture of ITER, a Plant System Host (PSH) and one or more Slow Controllers (SIEMENS PLCs) are connected over a switched Industrial Ethernet (IE) network. An important part of Software Engineering of Slow Controllers is the standardization of communication between PSH and PLCs. Based on prototyping and performance evaluation, Open IE Communication over TCP was selected. It is implemented on PLCs to support the CODAC data model of ‘State’, ‘Configuration’ and ‘Simple Commands’. The implementation is packaged in Standard PLC Software Structure(SPSS) as a part of CODAC Core System release. SPSS can be easily configured by the SDD Tools of CODAC. However Open IE Communication is restricted to the PLC CPUs. This presents a challenge to implement redundant PLC architecture and use remote IO modules. Another version of SPSS is developed to support communication over Communication Processors(CP). The EPICS driver is also extended to support redundancy transparent to the CODAC applications. Issues of PLC communication standardization in the context of CODAC environment and future development of SPSS and EPICS driver are presented here.