Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core...

69
Page 1 ICALEPCS ‘13, October 8 2013, San Francisco © 2013, ITER Organization Approaching the Final Design of the ITER Control System Anders Wallander, L Abadie, B Bauvir, F Di Maio, B Evrard, J Fernandez Hernando, C Fernandez Robles, J-M Fourneron, J-Y Journeaux, G Liu, C Kim, K Mahajan, P Makijarvi, S Pande, M Park, V Patel, P Petitpas, N Pons, A Simelio, S Simrock, D Stepanov, N Utzel, A Vergara, A Winter, I Yonekawa ITER Organization

Transcript of Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core...

Page 1: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 1 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Approaching the Final Design of the ITER Control System

Anders Wallander, L Abadie, B Bauvir, F Di Maio, B Evrard, J Fernandez Hernando, C Fernandez Robles, J-M Fourneron, J-Y Journeaux, G Liu, C Kim, K Mahajan, P Makijarvi, S Pande, M Park, V Patel, P Petitpas, N Pons, A Simelio, S Simrock, D Stepanov, N Utzel, A Vergara, A Winter, I Yonekawa

ITER Organization

Page 2: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 2 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Table of Content

• ITER recap • Status of ITER construction • Control System Architecture and Integration • Infrastructure • High Level Applications • Conclusions

Page 3: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 3 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Recap

Page 4: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 4 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

• The objective of the ITER project is to demonstrate the feasibility of commercial production of fusion energy

• ITER is based on magnetic confinement of the plasma using a

“Tokamak” as opposed to inertial confinement • ITER is an international project with seven members

(China, Europe, India, Japan, Korea, Russia and USA) • ITER is based on IN-KIND procurement arrangements, where

the members mainly provide systems/components, not money • ITER is currently in construction phase

• Final design reviews of ITER control system start Jan 2014

ITER Recap

Page 5: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 5 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER construction site, France, Aug 30, 2013

Page 6: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 6 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 7: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 7 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 8: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 8 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 9: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 9 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 10: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 10 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 11: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 11 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 12: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 12 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 13: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 13 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Progress of ITER Construction (examples)

Page 14: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 14 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Control System Architecture and Integration

Page 15: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 15 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Control System

Mission Statement Ensure all ITER Plant Systems Instrumentation & Control are designed, implemented and integrated such that ITER can be operated as a fully integrated and automated system.

Page 16: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 16 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Control System

Mission Statement Ensure all ITER Plant Systems Instrumentation & Control are designed, implemented and integrated such that ITER can be operated as a fully integrated and automated system.

Page 17: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 17 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Control System

Mission Statement Ensure all ITER Plant Systems Instrumentation & Control are designed, implemented and integrated such that ITER can be operated as a fully integrated and automated system.

• Successful integration = higher reliability • Minimize required operators • Minimize required maintenance crew • Minimize operator human errors • Single control room with standard equipment

Page 18: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 18 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Control System

Mission Statement Ensure all ITER Plant Systems Instrumentation & Control are designed, implemented and integrated such that ITER can be operated as a fully integrated and automated system.

• Successful integration = higher reliability • Minimize required operators • Minimize required maintenance crew • Minimize operator human errors • Single control room with standard equipment

Page 19: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 19 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

ITER Control System

Mission Statement Ensure all ITER Plant Systems Instrumentation & Control are designed, implemented and integrated such that ITER can be operated as a fully integrated and automated system.

• Successful integration = higher reliability • Minimize required operators • Minimize required maintenance crew • Minimize operator human errors • Single control room with standard equipment

⇒ Reduced total cost

Page 20: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 20 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

Page 21: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 21 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

Page 22: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 22 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

Page 23: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 23 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

• ITER control system is broken down in 18 ITER Subsystems

Page 24: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 24 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

• ITER control system is broken down in 18 ITER Subsystems • An ITER Subsystem contains one or many local control systems • A local control system is a deliverable from a procurement arrangement

Page 25: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 25 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

• ITER control system is broken down in 18 ITER Subsystems • An ITER Subsystem contains one or many local control systems • A local control system is a deliverable from a procurement arrangement (IN-KIND) • A procurement arrangement delivers one or many local control systems

Page 26: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 26 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Architecture

• ITER control system is broken down in 18 ITER Subsystems • An ITER Subsystem contains one or many local control systems • A local control system is a deliverable from a procurement arrangement (IN-KIND) • A procurement arrangement delivers one or many local control systems

Page 27: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 27 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

The main challenge for CODAC is INTEGRATION

The main challenge for ITER Control System is INTEGRATION

Integration

Page 28: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 28 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

The main challenge for CODAC is INTEGRATION

The main challenge for ITER Control System is INTEGRATION

MITIGATION • Define standards, specifications and interfaces applicable to all plant

systems instrumentation and control (Plant Control Design Handbook - PCDH)

Integration

Page 29: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 29 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Nb IDM ref Insert title Content 1 27LH2V PCDH The core document which collects all requirements 2 32GEBH I&C architecture Guideline for plant system I&C architecture 3 34SDZ5 CODAC overview CODAC core system overview 4 34V362 CODAC interface Scope of plant system I&C – Central I&C interface 5 2UT8SH I&C naming Naming convention in use for components, signals and variables 6 34QXCP Self-description The data required for generating the plant system I&C interface 7 353AZY I&C specifications Scope and how to for I&C specs required at FDR 8 3VVU9W I&C integration Scope and scenarios for FAT and SAT for I&C 9 2NRS2K SW and QA General requirements for SW QA 10 3QPL4H PLC SW Specific requirements for PLC SW 11 3WCD7T Alarm handling Scope and introduction to alarm handing 12 3XLESZ HMI Scope and introduction to HMI 13 B7N2B7 PON archiving Scope and introduction to PON archiving 14 AC2P4J PSOS management Scope and introduction to PSOS-COS synchronisation 15 354SJ3 Diagnostic data Scope and introduction to diagnostic data 16 75ZVTY Interlock functions How to identify interlocks 17 2YNEFU PCDH-N Specific requirements and guidelines applicable to N-Safety 18 35W299 CWS CS Application of I&C specs recommendation to a simple case study 19 2LT73V Acronyms Table of abbreviations and acronyms used in PCDH 20 34QECT Glossary PCDH glossary 21 C8X9AE Integration kit Content of the HW kit delivered by IO for integrating I&C systems 22 3PZ2D2 PIS design Guidelines for Plant Interlock System design 23 7LELG4 PIS integration Guidelines for Plant Interlock System configuration and integration 24 7L9QXR PIS Operation Guidelines for Plant Interlock System operation and maintenance 25 C99J7G PSS design Guidelines for Plant Safety System design 26 3299VT Signal interface Guidelines for signal interface to controllers 27 333J63 PLC catalogue IO standard PLC catalogue 28 333K4C FC guidelines Guidelines for technology selection of fast controllers 29 345X28 FC catalogue IO standard Fast Controller catalogue 30 35LXVZ I&C Cubicle IO standard I&C cubicle 31 4H5DW6 I&C Cubicle conf. Guidelines for I&C cubicle HW integration

Final complete PCDH (v7) released May 2013

http://www.iter.org/org/team/chd/cid/codac/plantcontrolhandbook

Page 30: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 30 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

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)

• Based on EPICS • Deployed on most computers/controllers (central and local) • Released twice per year (latest version v4.1 July 2013) • Distributed over Internet

Integration

The main challenge for ITER Control System is INTEGRATION

Page 31: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 31 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

CODAC Core System registered user organizations (Sep ‘13)

Page 32: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 32 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

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 and organize training

Integration

The main challenge for ITER Control System is INTEGRATION

Page 33: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 33 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

CODAC Core System Hands-on Workshops • Four days hands-on workshop with hardware and exercises • Maximum 10 participants • Two instructors • 13 sessions, 136 people trained by Oct 2013 • Now starting providing online training

Page 34: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 34 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

CODAC Core System Hands-on Workshops • Four days hands-on workshop with hardware and exercises • Maximum 10 participants • Two instructors • 13 sessions, 136 people trained by Oct 2013 • Now starting providing online training

Page 35: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 35 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

CODAC Core System Hands-on Workshops • Four days hands-on workshop with hardware and exercises • Maximum 10 participants • Two instructors • 13 sessions, 136 people trained by Oct 2013 • Now starting providing online training

Page 36: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 36 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

CODAC Core System Hands-on Workshops • Four days hands-on workshop with hardware and exercises • Maximum 10 participants • Two instructors • 13 sessions, 136 people trained by Oct 2013 • Now starting providing online training

Page 37: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 37 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

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 and organize training • Provide I&C Integration Kit free of charge (set of computers and

network equipment to interface local system with central system)

Integration

The main challenge for ITER Control System is INTEGRATION

Page 38: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 38 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

© 2

013,

ITE

R O

rgan

izat

ion

I&C Integration Kit (1 per PS I&C = 206)

Page 39: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 39 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

© 2

013,

ITE

R O

rgan

izat

ion

I&C Integration Kit (1 per PS I&C = 206)

Page 40: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 40 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

© 2

013,

ITE

R O

rgan

izat

ion

I&C Integration Kit (1 per PS I&C = 206)

Page 41: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 41 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

© 2

013,

ITE

R O

rgan

izat

ion

I&C Integration Kit (1 per PS I&C = 206)

Page 42: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 42 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

© 2

013,

ITE

R O

rgan

izat

ion

I&C Integration Kit (1 per PS I&C = 206)

Contract for supply of I&C Integration Kit signed July 2013

First batch of 10 set to be shipped

October 2013

Page 43: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 43 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Infrastructure

Page 44: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 44 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star network infrastructure configuration

• Provides intra and inter building connectivity • Supports 5 CODAC, 1 interlock, 2 safety and 1 IT fiber optic networks • Supports 1 interlock and 2 safety hardwired networks

Page 45: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 45 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

850 m

600

m

Page 46: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 46 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Headquarters

Control Building

Backup Control Room

Tokamak Complex

Page 47: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 47 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Page 48: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 48 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Page 49: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 49 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star points (core switches)

Page 50: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 50 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star points (core switches)

Page 51: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 51 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star points (core switches)

24 active distribution points in 12 buildings

Page 52: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 52 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star points (core switches)

24 active distribution points in 12 buildings 200 passive network

panels in all buildings

Page 53: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 53 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Dual star points (core switches)

24 active distribution points in 12 buildings 200 passive network

panels in all buildings

Build-to-print design completed by end of 2013 Installation starts in 2015

Page 54: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 54 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

High Level Applications

Page 55: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 55 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

High Level Applications – Main Data Flow

Page 56: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 56 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

High Level Applications – Main Data Flow

Five major software packages

Page 57: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 57 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage

High Level Applications – Main Data Flow

Page 58: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 58 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

High Level Applications – Main Data Flow

Page 59: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 59 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

High Level Applications – Main Data Flow

Page 60: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 60 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

Data acquisition and archiving

High Level Applications – Main Data Flow

Page 61: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 61 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

Data acquisition and archiving Data streaming and

storage

High Level Applications – Main Data Flow

Page 62: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 62 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

Data acquisition and archiving Data streaming and

storage

Data processing and access

High Level Applications – Main Data Flow

Page 63: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 63 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

Data acquisition and archiving Data streaming and

storage

Data processing and access

High Level Applications – Main Data Flow

Page 64: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 64 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Schedule preparation (off-line)

Schedule storage Fetch and validate

Execute

Data acquisition and archiving Data streaming and

storage

Data processing and access

High Level Applications – Main Data Flow

Page 65: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 65 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Timing diagram for a plasma pulse

Page 66: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 66 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Conclusions

Page 67: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 67 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

Conclusions

Page 68: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 68 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

• CODAC Final Design Review part 1 (everything except high level applications) will be held in Jan 2014

• Main components for mitigation of risks during integration are in place

– Plant Control Design Handbook – CODAC Core System – I&C Integration Kit – Training

• Detailed design of network infrastructure ready for tender of supply and installation

• CODAC Final Design Review part 2 Jan 2016

Conclusions

Page 69: Approaching the Final Design of the ITER Control System · 2014. 3. 3. · 27LH2V. PCDH; The core document which collects all requirements. 2. 32GEBH. I&C architecture; Guideline

Page 69 ICALEPCS ‘13, October 8 2013, San Francisco

© 2

013,

ITE

R O

rgan

izat

ion

• CODAC Final Design Review part 1 (everything except high level applications) will be held in Jan 2014

• Main components for mitigation of risks during integration are in place

– Plant Control Design Handbook – CODAC Core System – I&C Integration Kit – Training

• Detailed design of network infrastructure ready for tender of supply and installation

• CODAC Final Design Review part 2 Jan 2016

Conclusions

MOPPC079, Di Maio, CODAC Core System THPPC004, Pande, PLC interface TUPPC103, Utzel, Control System Studio TUPPC003, Abadie, Configuration (SSD) MOPPC014, Simrock, Diagnostics TUCOCA02, Vergara, Interlock