CERN Timing Workshop, Geneva, 15 Feb 20081

Geneva, 15 Feb 2008Geneva, 15 Feb 2008

Franck Di Maio – ITER IOFranck Di Maio – ITER IO

CERN Timing WorkshopITER

CERN Timing Workshop - ITER, Geneva, 15 Feb 20082

HighlightsHighlights

• CODAC overview• High Performance networks• A view on the planning

Ref: IBF07

CERN Timing Workshop - ITER, Geneva, 15 Feb 20083

CODAC PackagesCODAC 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.

CERN Timing Workshop - ITER, Geneva, 15 Feb 20084

CODAC Systems OverviewCODAC Systems Overview

UserData

ObserverTerminals

OperatorTerminals

Control Network

OperationRequest

Gatekeeper

Control Network

LeaderTerminals

ProcessModel

Engine A

OperatorTerminals

ProcessModel

Engine D

ProcessControl

Engine B

ProcessControl

Engine E

ProtectionEngine C

ProcessData

Control Network

DataOut

Gateway

Plant ObsGateway

Control Network

RealTimeData Synch Data Asynch Event Network

Plant System X Plant System Y Plant System Z

Synch Data Asynch Event Network

TimeStandard

UserData

ObserverTerminals

Remote Exploitation NetworkServer

ProcessData

RealTimeData

OperatorTerminals

UserData

ObserverTerminals

Remote Analysis Network

Server

ProcessData

RealTimeData

AnalysisWorkstation

ITER CODAC Remote Exploitation

Remote ITER Analysis

ITER PlantUserData

ObserverWorkstation

Remote Plant Obs NetworkServer

ProcessData

RealTimeData

Remote Plant Observation

OperationsProcesses

MachineProcesses

Real-TimeCommunicating

Processes

R.Felton 2007-07-27

CERN Timing Workshop - ITER, Geneva, 15 Feb 20085

CODAC Systems OverviewCODAC Systems Overview

CERN Timing Workshop - ITER, Geneva, 15 Feb 20087

Plant System I &C

Sub-system Controller

CODAC Networks Interface Units

Plant SystemHost

Sub-system Controller

Equipment

LocalControl Panels

PlantSafety

Systems

PlantInterlockSystem

Central Safety Systems

Central Interlock System

Central CODAC Systems

Synchronous data EventsClocksVideo

Field bus

CODAC Networks

Safety Networks

Interlock Network

WBS 4.5

WSB 4.8

WBS 4.6

Plant Systems IntegrationPlant Systems Integration

Part of the Plant System Procurement

CERN Timing Workshop - ITER, Geneva, 15 Feb 20088

Plant System I &C

Sub-system Controller

CODAC Networks Interface Units

Plant SystemHost B

Sub-system Controller

Equipment

LocalControl Panels

PlantSafety

Systems

PlantInterlockSystem

Mini-CODAC V2

Synchronous data EventsClocksVideo

Field bus

CODAC Networks

WBS 4.5

WSB 4.8

WBS 4.6

Plant Systems Tests, Phase IIPlant Systems Tests, Phase II

CERN Timing Workshop - ITER, Geneva, 15 Feb 20089

Plant System I &C

Sub-system Controller

Plant SystemHost A

Sub-system Controller

Equipment

LocalControl Panels

PlantSafety

Systems

PlantInterlockSystem

Mini-CODAC V1

Field bus

CODAC Networks

WBS 4.5

WSB 4.8

WBS 4.6

Plant Systems Tests, Phase IPlant Systems Tests, Phase I

CERN Timing Workshop - ITER, Geneva, 15 Feb 200810

CODAC – ScopeCODAC – 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)

CERN Timing Workshop - ITER, Geneva, 15 Feb 200811

ITER Networks (1/2)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.

CERN Timing Workshop - ITER, Geneva, 15 Feb 200812

ITER Networks (2/2)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.

CERN Timing Workshop - ITER, Geneva, 15 Feb 200813

Synchronous Data BusSynchronous 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 signals 4000

Jitter 0.05 ms

Data producers (plant systems) 80

Data consumers 50

Transmission delay 1 ms

Source to Destination delay 5 ms

CERN Timing Workshop - ITER, Geneva, 15 Feb 200814

Time Communication Time Communication NetworkNetwork

• 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 resolution 10 ns

Time precision 10 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

? ?

CERN Timing Workshop - ITER, Geneva, 15 Feb 200815

Event Distribution NetworkEvent 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 events 500

Number of consumers of events 500

Maximum latency 10 µs

? ?

CERN Timing Workshop - ITER, Geneva, 15 Feb 200816

CODAC – Provisional Schedule CODAC – Provisional Schedule Plant Systems I&C Support (Partial)Plant Systems I&C Support (Partial)

ID2008 2009 2010 2011 2012 2013

3 PSH Preliminary Design, Prototype4 PSH Software V15 PSH config A procurement6 PSH config B procurement7 Mini-CODAC V18 Mini-CODAC V2

2014 2015Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2

1 General I&C Specifications2 Components and tools selection

Specifications Factory Tests

Provisional: to be adjusted with IPS milestones

PSH Software

PSH Hardware

Mini-CODAC

CERN Timing Workshop - ITER, Geneva, 15 Feb 200817

ID2008 2009 2010 2011 2012 2013 2014 2015 2016Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4

1 Servers Contracts2 Servers Installation Phase I3 Servers Installation Phase II4 Preliminary Design, R&D5 Networks Design6 Specific Interfaces procurement7 Networks Contracts8 Networks Installation Phase I9 Networks Installation Phase II

10 Networks Installation Phase III

CODAC – Provisional Schedule CODAC – Provisional Schedule CODAC Hardware & Infra. (partial)CODAC Hardware & Infra. (partial)

Buildings

Servers

Networks

Provisional: to be adjusted with IPS milestones

On-site tests