1. CERN Timing Workshop, Geneva, 15 Feb 2008 1 Geneva, 15 Feb 2008 Franck Di Maio – ITER IO Geneva, 15 Feb 2008 Franck Di Maio – ITER IO CERN Timing Workshop ITER

2. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 2 Highlights CODAC overview High Performance networks A view on the planning Ref: IBF07IBF07

3. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 3 CODAC Packages WBS 4.5: CODAC (COntrol Data Access & Communications) WBS 4.6: Central Interlock System (Investment Protection) WBS 4.8: Central Safety System These are all Fund procurements. Means procured by ITER, not in-kind. But the plant systems and their control will be in-kind procurements.

4. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 4 CODAC Systems Overview

5. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 5 CODAC Systems Overview

6. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 6 Networks segregation

7. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 7 Plant System I &C Sub-system Controller CODAC Networks Interface Units Plant System Host Sub-system Controller Equipment Local Control Panels Plant Safety Systems Plant Interlock System Central Safety Systems Central Interlock System Central CODAC Systems Synchronous data Events Clocks Video Field bus CODAC Networks Safety Networks Interlock Network WBS 4.5 WSB 4.8 WBS 4.6 Plant Systems Integration Part of the Plant System Procurement

8. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 8 Plant System I &C Sub-system Controller CODAC Networks Interface Units Plant System Host B Sub-system Controller Equipment Local Control Panels Plant Safety Systems Plant Interlock System Mini-CODAC V2 Synchronous data Events Clocks Video Field bus CODAC Networks WBS 4.5 WSB 4.8 WBS 4.6 Plant Systems Tests, Phase II

9. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 9 Plant System I &C Sub-system Controller Plant System Host A Sub-system Controller Equipment Local Control Panels Plant Safety Systems Plant Interlock System Mini-CODAC V1 Field bus CODAC Networks WBS 4.5 WSB 4.8 WBS 4.6 Plant Systems Tests, Phase I

10. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 10 CODAC – Scope Plant Systems I&C Support –General I&C specifications and interfaces definition –Selection of standardized components & tools (ex: PLC) –Support for specifications, design and integration tests –Mini-CODAC (for integration tests) CODAC Hardware & Infrastructure –Servers: general purpose, data-storage, high performance. –Networks: conventional + dedicated (synchronous data, events distribution, time distribution) –Control Rooms infrastructure CODAC Software –Core software (communications, alarms, reporting, visualization…) –Operation software (schedule management, pulse control…) –Plant System Host (PSH) software –Data management Central Interlock System Central Safety Systems (nuclear, access, conventional)

11. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 11 ITER Networks (1/2) Conventional networks within CODAC scope: The Plant Operation Network (PON) is responsible for the provision and management of all standard Network Communications connecting Plant Systems and CODAC Systems and is the backbone of CODAC. The Plant Commissioning Network (PCN) has the same functionality as the Plant Operation Network, but is connected only to Plant Systems which are in an un- commissioned state. It will be used during initial integration and commissioning as well as during and following interventions to a Plant System which reduce the reliability of the Plant System, to the extent that formal re-commissioning will be required. The Network Monitoring Network (NMN) provides an independent monitoring of all CODAC Networks and creates a CIS alarm in case of failure of a network. The Disaster Backup Network (DBN) provides an independent link between the CODAC data store and an off-site store with no common-mode risks. The Audio-Video Network (AVN) provides the physical and logical support for Audio and Video communication throughout the ITER plant. These data include both monitoring information and experimental data. Conventional networks outside of CODAC scope: The General ITER Network (GIN) provides the link between CODAC and all other on- site and off-site activities. GIN will use the high performance RENATER network for all off-site user connections. The Open Public Network (OPN) provides the link between CODAC and all other on- site and off-site activities which do not require ITER authorisation. OPN will use the high performance RENATER network for all off-site connections.

12. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 12 ITER Networks (2/2) High performance CODAC networks The Synchronous DataBus Network (SDN) is complementary to the CODAC Communication Network. It communicates data required for operation, including feedback control, when the delay or jitter of these data must be stricter than the Quality of Service guaranteed by the PON. The Time Communication Network (TCN) provides a project-wide definition of time and communicates this time to all Systems. It allows actions, events and data in all ITER Systems to be synchronised. The Event Distribution Network (EDN) manages the signaling of intermittent events between CODAC Systems or Plant Systems with a lower latency than the Synchronous DataBus. Safety & Interlocks: The Central Interlock System Network (CIN) provides the physical network and the supervisory logic to allow the continued operation of the plant in its present state, or to cause an appropriate corrective action if an off-normal event is detected and not avoided by preventive CODAC actions. The Central Safety System Networks (CSN) provide the physical network and the supervisory logic to allow the continued operation of the plant in a safe state, or to cause an appropriate corrective action if an off-normal event is detected and not avoided by preventive CODAC actions.

13. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 13 Synchronous Data Bus Non-persistent, transient, low (1msec) latency data, representing engineering and physics. Needed for fast control of the plant and of the plasma Number of signals4000 Jitter0.05 ms Data producers (plant systems)80 Data consumers50 Transmission delay1 ms Source to Destination delay5 ms

14. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 14 Time Communication Network The Time Communication Network (TCN) provides a project-wide definition of time and communicates this time to all Systems. It allows actions, events and data in all ITER Systems to be synchronised. Time resolution10 ns Time precision10 ns Synchronise itself to UTC as the absolute reference, to within 1 s Guarantee monotonic progression of its time, recovering any error with respect to UTC with a correction rate of 1e-4 ??

15. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 15 Event Distribution Network The Event Distribution Network (EDN) manages the signaling of intermittent events between CODAC Systems or Plant Systems with a lower latency than the Synchronous DataBus. Number of sources of events500 Number of consumers of events500 Maximum latency10 µs ??

16. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 16 CODAC – Provisional Schedule Plant Systems I&C Support (Partial) Specifications Factory Tests Provisional: to be adjusted with IPS milestones PSH Software PSH Hardware Mini-CODAC

17. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 17 CODAC – Provisional Schedule CODAC Hardware & Infra. (partial) Buildings Servers Networks Provisional: to be adjusted with IPS milestones On-site tests

18. CERN Timing Workshop - ITER, Geneva, 15 Feb 2008 18 CODAC – Provisional Schedule CODAC Software (partial) On-site tests Commissioning Core Software Operation Software Plant System Host Software Provisional: to be adjusted with IPS milestones New schedule