JCOP Review, March 2003 D.R.Myers, IT-CO 1

JCOP Review 2003

Architecture

JCOP Review, March 2003 D.R.Myers, IT-CO 2

GoalsGoals

Compile and Consolidate User Requirements “Brainstorm” possible solutions Define Logical Structures Define Physical Structures Define Interfaces Propose designs in key areas

JCOP Review, March 2003 D.R.Myers, IT-CO 3

What happened?What happened?

Two series of meetings: March to September 1998 (Pere Mato) November 1999 to June 2001

(Wolfgang von Rüden, Mike Huffer, Wayne Salter)

Uneven participation (second round) Problems conceptual rather than technical Proposal to implement a “Framework” “Final” report finished in October 2001

(Wayne Salter with many contributions)

JCOP Review, March 2003 D.R.Myers, IT-CO 4

The Lewis Carroll EffectThe Lewis Carroll Effect

“When I use a word,” Humpty Dumpty said in a rather scornful tone, “it means just what I choose it to mean – neither more nor less.”

JCOP Review, March 2003 D.R.Myers, IT-CO 5

Topics CoveredTopics Covered

Constraints Glossary Object Naming &

Addressing System Modelling,

Control & Partitioning

Use of FSMs

Access Control Alarm Handling Configuration &

Persistency Database Access Software Versions External Interfaces Diagnostics

JCOP Review, March 2003 D.R.Myers, IT-CO 6

Divergent PhilosophiesDivergent Philosophies

Cover all cases if possible

Let experiments

“cherry-pick”

Will this work ?

JCOP Review, March 2003 D.R.Myers, IT-CO 7

Key IssuesKey Issues

Large systems: ~106 “tags” (data items) Must be scalable (because final size unknown!) Distributed over machines and geography Device (or Object) -Oriented Open

(no proprietary protocols or data formats)

Must be reliable, but NOT a safety system Constraints: e.g. impact of PLCs

JCOP Review, March 2003 D.R.Myers, IT-CO 8

Use CasesUse Cases

Who will use system? Shift Crew, Sub-Detector Expert, Observer, …

Possible states? Commissioning, Trouble Shooting Data Taking with Partial System Data Taking with Full System

JCOP Review, March 2003 D.R.Myers, IT-CO 9

Technology ChoicesTechnology Choices

Implementation Strategies: Bottom-to-top D-I-Y-S (Classical HEP) Component-Ware SCADA (EPICS or Commercial)

Follow Industrial Practice? PLCs – Field Buses – OPC

Multi-Platform / MS-only / UNIX-only?

Controls Technologies

Supervision

ProcessManagement

FieldManagement

Sensors/devices

Field buses & Nodes

PLC/UNICOS

OPC

Communication Protocols

SCADA

Technologies

VME/SLiC X

DIM

FSM

Commercial Custom

Stolen from Wayne and based on an original slide from LHCb

Layer Structure

Experimental equipment

LAN

WAN

Storage

Oth

er

syst

em

s(L

HC

, S

afe

ty,

...)

Configuration DB,Archives,Log files, etc.

Controller/PLC VME

Field Bus

LAN

Node Node

D.I.P.

JCOP Review, March 2003 D.R.Myers, IT-CO 11

Structural IssuesStructural Issues

System Decomposition Trees and Directed Graphs Multiple view points:

E.g. Logical versus Physical Views

Muon System - HV Crate #23

System Partitioning Model Consistency

(between Supervision and F-E layers)

Unique versus Concurrent Access

Hierarchical ControlHierarchical Control

PVSS I I

FSMI nterface Alarm

HandlingLogging &Archiving

Commands/ States

Operator

HW/ SW Device

Commands/ States

Settings/ Readings

Confi guration data

‘Parent’

DeviceDriver

Confi guration

Database

PVSS I I

FSMI nterface Alarm

HandlingLogging &Archiving

Commands/ States

Operator

HW/ SW Device

Commands/ States

Settings/ Readings

Confi guration data

‘Parent’

DeviceDriver

Confi guration

Database

PVSS I I

Behaviour

FSM

Ownership&

Partitioning

AlarmHandling

Logging &Archiving

‘Parent’

Commands/ StatesConfi guration

Database

Operator

‘Child’‘Child’

‘Child’

Commands/ States

Commands/ StatesCommands/ States

Commands/ States

Configuration data

PVSS I I

Behaviour

FSM

Ownership&

Partitioning

AlarmHandling

Logging &Archiving

‘Parent’

Commands/ StatesConfi guration

Database

Operator

‘Child’‘Child’

‘Child’

Commands/ States

Commands/ StatesCommands/ States

Commands/ States

Configuration data

...

To Devices (HW or SW)

Com

man

ds

Sta

tus

& A

larm

s

ECS

DCS DAQ

DetDcs1 DetDcsN

SubSys1 SubSys2

Dev1 Dev2 Dev3

DetDaq1

SubSysN

DevN

LHCT.S.

Device Units

Control Units

GAS

DSS

...

To Devices (HW or SW)

Com

man

ds

Sta

tus

& A

larm

s

CU1.1

CU2.1 CU2.N

CU3.1 CU3.X

CU4.1 CU4.2

Dev1 Dev2 Dev3

CU3.N

CU4.N

DevN

LHCT.S.

...

Device Units

Control Units

GAS

DSS...

...

Stolen from Clara & Wayne

Control System Interfaces

SCADA (PVSS)

JCOP FW (Supervisory)

Supervisory Application

FSM, DB, Web,etc.

Supervision

Front-end

PLC

UNICOS FWFE Application

Communication

PC (Windows, Linux)

Other Systems

Commercial Devices

Device DriverFE Application

OPC, PVSS Comms, DIM, DIPOPC, PVSS Comms, DIM, LHC-DIP, …

Stolen from Wayne

JCOP Review, March 2003 D.R.Myers, IT-CO 14

Configuration IssuesConfiguration Issues

List of items to configure: SCADA, FSMs, OPC, Field Buses, PLCs, ELMB, “VME”, …

What external systems are there? DAQ, LHC Machine, C & V, …

How to ensure consistency?Can one have a single master database?

Connection to the “Conditions Database”

Not yet solved!

JCOP Review, March 2003 D.R.Myers, IT-CO 15

Alarm IssuesAlarm Issues

Is an “Alarm”: An error to be reacted on? A warning to be displayed? Neither or both?

What is allowed for filtering and masking? What is required for logging? What states can an alarm have? How should these be displayed? How can one deal with avalanches?

JCOP Review, March 2003 D.R.Myers, IT-CO 16

Security + Access ControlSecurity + Access Control

Off-site Access? Different sorts of access?

Expert Operator Observer

To what? Experiment Subdetector Subsystem Services (power, gas, cooling, …)

JCOP Review, March 2003 D.R.Myers, IT-CO 17

Persistence & ArchivingPersistence & Archiving

System Configuration Versions

Action Logs Data Values/Trend Logs Levels of Storage

“Recipes” and Procedures