1 / 17

JCOP Review 2003 Architecture

JCOP Review 2003 Architecture. Goals. Compile and Consolidate User Requirements “Brainstorm” possible solutions Define Logical Structures Define Physical Structures Define Interfaces Propose designs in key areas. What happened?. Two series of meetings:

holli
Télécharger la présentation

JCOP Review 2003 Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Goals • Compile and Consolidate User Requirements • “Brainstorm” possible solutions • Define Logical Structures • Define Physical Structures • Define Interfaces • Propose designs in key areas D.R.Myers, IT-CO

  3. 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) D.R.Myers, IT-CO

  4. 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.” D.R.Myers, IT-CO

  5. Topics Covered • Access Control • Alarm Handling • Configuration & Persistency • Database Access • Software Versions • External Interfaces • Diagnostics • Constraints • Glossary • Object Naming & Addressing • System Modelling, Control & Partitioning • Use of FSMs D.R.Myers, IT-CO

  6. Divergent Philosophies Cover all cases if possible Let experiments “cherry-pick” Will this work ? D.R.Myers, IT-CO

  7. Key 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 D.R.Myers, IT-CO

  8. 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 D.R.Myers, IT-CO

  9. 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? D.R.Myers, IT-CO

  10. Configuration DB, Archives, Storage Log files, etc. Supervision WAN LAN Process LAN Management Controller/ Other systems PLC (LHC, Safety, ...) VME Field Bus Field Node Node Management Experimental equipment Controls Technologies Layer Structure Technologies Custom Commercial FSM SCADA D.I.P. DIM OPC Communication Protocols VME/SLiC X PLC/UNICOS Field buses & Nodes Sensors/devices Stolen from Wayne and based on an original slide from LHCb

  11. 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 D.R.Myers, IT-CO

  12. Control Control ECS CU1.1 Units Units ... T.S. T.S. LHC LHC CU2.N DAQ DSS DSS CU2.1 DCS ... ... ... ... GAS GAS Status & Alarms Status & Alarms CU3.1 DetDcs1 Commands Commands DetDcsN CU3.X CU3.N DetDaq1 SubSys1 CU4.1 SubSys2 CU4.2 CU4.N SubSysN Device Units Device Units Dev1 Dev1 Dev2 Dev2 Dev3 Dev3 DevN DevN To Devices (HW or SW) To Devices (HW or SW) Hierarchical Control Stolen from Clara & Wayne

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

  14. 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! D.R.Myers, IT-CO

  15. 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? D.R.Myers, IT-CO

  16. Security + Access Control • Off-site Access? • Different sorts of access? • Expert • Operator • Observer • To what? • Experiment • Subdetector • Subsystem • Services (power, gas, cooling, …) D.R.Myers, IT-CO

  17. Persistence & Archiving • System Configuration Versions • Action Logs • Data Values/Trend Logs • Levels of Storage • “Recipes” and Procedures D.R.Myers, IT-CO

More Related