JCOP Review, March 2003 D.R.Myers, IT-CO1 JCOP Review 2003 Architecture

JCOP Review, March 2003 D.R.Myers, IT-CO2 Goals  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-CO3 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-CO4 The 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-CO5 Topics 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-CO6 Divergent Philosophies Cover all cases if possible Let experiments “cherry-pick” Will this work ?

JCOP Review, March 2003 D.R.Myers, IT-CO7 Key Issues  Large systems: ~10 6 “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-CO8 Use 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-CO9 Technology 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 Process Management Field Management 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 Other systems (LHC, Safety,...) Configuration DB, Archives, Log files, etc. Controller/ PLC VME Field Bus LAN Node D.I.P.

JCOP Review, March 2003 D.R.Myers, IT-CO11 Structural 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 Control Stolen from Clara & Wayne

Control System Interfaces SCADA (PVSS) JCOP FW (Supervisory) Supervisory Application FSM, DB, Web,etc. Supervision Front-end PLC UNICOS FW FE Application Communication PC (Windows, Linux) Other Systems Commercial Devices Device Driver FE Application OPC, PVSS Comms, DIM, DIP OPC, PVSS Comms, DIM, LHC-DIP, … Stolen from Wayne

JCOP Review, March 2003 D.R.Myers, IT-CO14 Configuration 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-CO15 Alarm 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-CO16 Security + 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-CO17 Persistence & Archiving  System Configuration Versions  Action Logs  Data Values/Trend Logs  Levels of Storage  “Recipes” and Procedures