12-CRS-0106 REVISED 8 FEB 2013 EPICS Collaboration Meeting 2013 CSS An integrated development and...

EPICS Collaboration Meeting 2013EPICS Collaboration Meeting 2013

Click icon to add picture

CSSAn integrated development and runtime environment for ITER plant system local controls

ITER Organization - CHD/CSD/CDC

02/05/2013 1


Agenda

1. Context

2. A compact development environment

3. A distributed runtime environment

4. ITER contribution process to CSS development effort

5. Future Plans

02/05/2013 2


Context

02/05/2013 3


ITER: a global collaboration

ITER is broken into 34 plant systems (magnet, vacuum vessel, divertor, cryostat, diagnostics…)

ITER construction units are procurement arrangements and 89 of them have control systems. They are developed by the 7 partners

Integration is a challenge

ITER is a research facility (requirements can change) with a long life time

Flexibility and modularity are essential

02/05/2013 4


Risk Mitigation

Definition of standards, specifications and interfaces applicable to all plant system local controls

Development and distribution of a control system framework that implements the standards and guarantees that the local control systems can be integrated into the central one

Control System Studio is an key element of this framework for the operator interface, the alarm system and the engineering archival

02/05/2013 5


Central Control System Schedule

6


A compact development environment

02/05/2013 7


CSS Services on one machine

02/05/2013 8

Plant System

Host

Fast Controller

COTSIntelligent

Device

Actuators and Sensors

Fast Controller

Slow Controller

Slow Controller

Plant System I&C

Signal Interface

Remote I/O

Plant Operation Network (PON)

Plant Operation Network (PON)

Remote I/O

Signal Interface

InterlockController

Signal Interface

Central Interlock System

Central Interlock Network (CIN)

Time Communication Network (TCN)

Audio/video Network (AVN)

Synchronous Data Network (SDN)

High Performance Networks (HPN)

MINI-CODAC

Operator Interface

Alarm ServerArchive Engine

Slow Controllers

IOC

CAS CAC

Slow Controllers

IOC

CAS CAC

Slow Controllers

IOC

CAS CAC


Standardisation of the Operator Interface

Development and run of the Operator Interface– ITER schema defines the default properties of all widgets

to standardise the operator interface

– Color and font definition: users are encouraged to use color and font macro names

– Industrial Symbol Library of ~110 electrical symbols and ~150 fluid symbols

No standardisation for now of the layout

02/05/2013 9


Archived Data

Store all miniscule changes of all the available PV

No compromise during development

But difficult to change afterward: configuration -> db generation -> compilation -> installation -> tests

Cleaning procedure?

02/05/2013 10


Alarms

Alarm levels set within the normal operating range -> nuisance alarms

Baseline of alarms that require no action and train the operator to ignore certain alarms -> stale alarms

Alarms without description: how to respond to them?

Analysis of the alarm frequency to detect nuisance alarms? Measurement of the alarm standing time to detect stale alarms?

02/05/2013 11


CSS Other Tools

SNL Editor

EPICS tools– Probe, PV Tree, PV Table, CA Snoooper, PACE Editor

– PV Fields Viewer interfaced with db files within the workspace and configuration RDB

Alarm notifier for automated actions such as sending an email when an alarm is raised

Alarm annunciator

Message History~ 130 plugins

02/05/2013 12


A distributed runtime environment

02/05/2013 13


CSS distributed on two levels

02/05/2013

Actuators and Sensors

CODAC Server

CODAC servicesand applications

CODAC Server

CODAC services

CODACTerminal

Central supervision, monitoring and data handling

FastController

CODAC Server

Applications

CODAC Server ScientificArchiving

Plant System I&C yyy/206

ITER Control Groupxxx/18

TCN

CODAC HPCPlasmaControl

TCN

Operator Interface

Outside POZ

SDN

PON

PON

FastController

COTSIntelligent

Device

SlowController

SlowController

TCNAVN

DAN

DAN

PlantSystem

Host

CINDAN

Slow Controllers

IOC

CAS CAC

Slow Controllers

IOC

CAS CAC

Slow Controllers

IOC

CAS CAC FastControllers

IOC

CAS CAC

FastControllers

IOC

CAS CAC

FastControllers

IOC

CAS CAC

Channel Access Gatewayxxx Archive Engine

Archive RDB Alarm RDB

xxx Alarm Server

14


First Setup

Only one Plant Group for now and one Plant System– ~25 OPI files

– 5 PLCs

– ~1000 PVs

– ~900 archived PVs

“Manual” installation and configuration as the packaging system targets mainly the development environment and not a distributed architecture

02/05/2013 15


ITER contribution to CSS development effort

02/05/2013 16


CSS Contribution Workflow

02/05/2013 17

CSS from local RPMs

ITER Git repository CODAC SVN Repository Synchronisation script

Dev Repository(on home folder)

checkout/comm

it

checkout/comm

it

Github RemoteRepositorypull/push

CSS from local RPMsTest

Test

CSS from nightly buldRPMs

Jenkins RPMs

2. Nightly build 1. Run before nightly build

3. Install nightly

Test

Build & DeployRPMs (locally)

Build & DeployRPMs (locally)

io-ls-sopra-devX io-ls-sopra-devY

trunk

Pull/Push whendecided by reviewer

Commit only when changes accepted by reviewer

Developer X Developer YReviewer

Dev Repository(on home folder)

io-ls-git-css-trunk

Yesterday (3.0) > 1 month – Tomorrow 1 day?


Future Plans

02/05/2013 18


Development Environment Plan

PV name auto completion– Required by our users during all training sessions

– History

– DB files parsing

– Configuration RDB

eLog entry from CSS– No Web Interface

3D models in BOY

02/05/2013 19


Integration of a new Group Plant

02/05/2013

CODAC Server


CODAC Server

CODAC services

CODACTerminal

Central supervision, monitoring and data handling

CODAC Server

Applications

CODAC Server ScientificArchiving Operator

Interface

Outside POZPON

DAN

Archive RDB Alarm RDB

UTIL Control Group

CA GatewayUTILArchive Engine

UTILAlarm Server

BUIL Control Group

CA GatewayBUILArchive Engine

BUILAlarm Server

20


Web Interface

In addition to Web OPI

Web Data Browser to load predefined plot configuration file

Web Alarm to consult the Alarm table and Message History– No Edition, no acknowledgment

02/05/2013 21


Web Reports

To produce runtime statistics for acceptance tests– How many PVs?

– How many archived samples?

– How many alarms triggered?

– …

To focus on what need to be improved before integration on ITER site

02/05/2013 22

EPICS Collaboration Meeting 2013

Go beyond the basics

Wants to learn more?


ITER BOY Schema

CODAC schema OPI helps to achieve consistent interface look&feel by defining the default property values used when a new widget is created with BOY Editor

CODAC schema OPI will contain the default definition of all BOY widget types

24


~110 electrical symbols

cs-studio/products/ITER/products/org.csstudio.iter.css.product/resources/One_Line_Diagram.opi25


~150 fluid symbols

26cs-studio/products/ITER/products/org.csstudio.iter.css.product/resources/Fluid_Diagram.opi


ITER Electrical Use Case

27cs-studio/products/ITER/products/org.csstudio.iter.css.product/resources/MV-2-Switchgear.opi


ITER PID Use Case

28cs-studio/products/ITER/products/org.csstudio.iter.css.product/resources/PID_Water_Cooling.opi


CSS BOY Runtime Environment

02/05/2013

CODAC Server


CODAC Server

CODAC services

ITER Control GroupUTIL

Operator Interface

PON

UTIL Alarm Server

UTIL OPIAlarm RDB

Channel Access Gatewayca-gateway-util

OPI xml file

UTIL Archive Engine

Archive RDB

2. Subscribe PVs

3. Change notification

BOY OPI Data Flow1. load OPI

29


CSS BEAUTY Runtime Environment

02/05/2013

CODAC Server


CODAC Server

CODAC services


Operator Interface

PON

UTIL Alarm Server

Alarm RDB


1. Read -1h archived data

UTIL Archive Engine

Archive RDB


Plot Data Flow

UTIL OPI

2. Subscribe PVs

30


CSS BEAST Runtime Environment

02/05/2013

CODAC Server


CODAC Server

CODAC services


Operator Interface

PON

Alarm RDB


1. Read alarm configuration

UTIL Archive Engine

Archive RDB

Alarm GUI Data Flow

Log 1'. Read alarm history

UTIL Alarm Server

UTIL OPI

JMSJMS

Alarm Server

JMS2RDB

JMS2Speech

Automated Action

MessageHistory

2. Subscribe PVs


MessageAnnunciated

EmailCommand

1. Read configuration

4. Store alarm state

2. Subscribe toalarm message

3. Alarmmessage4. Ack alarm

2. Subscribe toalarm message

4. Ack alarm

Alarm RDB

Log RDB

1. Readconfiguration

3. Alarmmessage

31


BOY on Web: WebOPI

The dream to bring your control system to web browser come true!

02/05/2013 32


Alarm Table and Message History on the Web

02/05/2013 33


Data Browser on the Web

12-CRS-0106 REVISED 8 FEB 2013 EPICS Collaboration Meeting 2013 CSS An integrated development and...

Documents

Transcript of 12-CRS-0106 REVISED 8 FEB 2013 EPICS Collaboration Meeting 2013 CSS An integrated development and...