PCaPAC2012 - List of Authors (Clausen, M.R.)

Paper

Title

Page

The CSS Story

1

M.R. Clausen, J. Hatje, J. Penning
DESY, Hamburg, Germany

Control System Studio (CSS) is designed to serve as an integration platform for engineering and operation of todays process controls as well as machine controls systems. Therefore CSS is not yet another replacement of existing operator interfaces (OPI) but a complete environment for the control room covering alarm management, archived data displays diagnostic tools and last not least operator interfaces. In addition we decided to use CSS as the platform for the whole engineering chain configuring EPICS based process control databases, configuring and managing the I/O, editing state notation programs, configuring role based access rights and many more. Due to the ease of use of CSS as an Eclipse based product, we decided to use the CSS core also for all our stand alone processes. This helped us to reduce the diversity of running products/ processes and simplified the management. In this presentation we will describe our experience with CSS over the last two years. How we managed the transition from old displays to new ones, how we changed our alarm/ message philosophy and last not least which lessons we learned.

Slides WEKA01 [2.926 MB]

THPD02

What it Takes to Make a System Reliable

139

M.R. Clausen, M. Möller, S. Rettig-Labusga, B. Schoeneburg
DESY, Hamburg, Germany

What is a reliable system and how is reliability defined? This depends on the actual situation and in which environment the system is operated. If you can rely on a scheduled downtime of the controlled system every week, reliability is defined in hours or weeks. In this case the system must run just longer than the scheduled downtime. If the system has to continuously operate for months and even years, your requirements are rising. In cases where continuous operations must be guaranteed even during software or hardware updates, redundant systems come into play. The hardware selection process is driven by basic requirements like 'no moving parts' or 'redundant power supplies'. This implies the selection of possible (fan-less) CPU boards with passive cooling. It also implies no hard discs and reduces therefore the selection of possible operating systems. Continuous operation during updates requires redundant controllers/ CPUs also in addition to redundant power supplies. The latter has a lot of impact on the software running inside the controllers. We will describe the selection process of the components we have chosen and summarize our experience of several years of operations.

Poster THPD02 [0.280 MB]

Paper	Title	Page
WEKA01	The CSS Story	1
	M.R. Clausen, J. Hatje, J. Penning DESY, Hamburg, Germany
	Control System Studio (CSS) is designed to serve as an integration platform for engineering and operation of todays process controls as well as machine controls systems. Therefore CSS is not yet another replacement of existing operator interfaces (OPI) but a complete environment for the control room covering alarm management, archived data displays diagnostic tools and last not least operator interfaces. In addition we decided to use CSS as the platform for the whole engineering chain configuring EPICS based process control databases, configuring and managing the I/O, editing state notation programs, configuring role based access rights and many more. Due to the ease of use of CSS as an Eclipse based product, we decided to use the CSS core also for all our stand alone processes. This helped us to reduce the diversity of running products/ processes and simplified the management. In this presentation we will describe our experience with CSS over the last two years. How we managed the transition from old displays to new ones, how we changed our alarm/ message philosophy and last not least which lessons we learned.
	Slides WEKA01 [2.926 MB]

THPD02	What it Takes to Make a System Reliable	139
	M.R. Clausen, M. Möller, S. Rettig-Labusga, B. Schoeneburg DESY, Hamburg, Germany
	What is a reliable system and how is reliability defined? This depends on the actual situation and in which environment the system is operated. If you can rely on a scheduled downtime of the controlled system every week, reliability is defined in hours or weeks. In this case the system must run just longer than the scheduled downtime. If the system has to continuously operate for months and even years, your requirements are rising. In cases where continuous operations must be guaranteed even during software or hardware updates, redundant systems come into play. The hardware selection process is driven by basic requirements like 'no moving parts' or 'redundant power supplies'. This implies the selection of possible (fan-less) CPU boards with passive cooling. It also implies no hard discs and reduces therefore the selection of possible operating systems. Continuous operation during updates requires redundant controllers/ CPUs also in addition to redundant power supplies. The latter has a lot of impact on the software running inside the controllers. We will describe the selection process of the components we have chosen and summarize our experience of several years of operations.
	Poster THPD02 [0.280 MB]