A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.

Slides:



Advertisements
Similar presentations
Provenance-Aware Storage Systems Margo Seltzer April 29, 2005.
Advertisements

CLS Process Variable Database By: Diony Medrano. CLS PV Database - Topics Background Design Constraints Design and Implementation Benefits and Future.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
CLS Machine Status Displays System Analyst - Controls Canadian Light Source Inc. web: Perimeter.
Chapter 5 Database Concepts. Why Study Databases? Databases have incredible value to business. Probably the most important technology for supporting operations.
Distributed Databases John Ortiz. Lecture 24Distributed Databases2  Distributed Database (DDB) is a collection of interrelated databases interconnected.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
EPICS Meeting 2005ORNL Rdb systems at SNS Jeff Patton and cast April 27-29, 2005 EPICS Meeting 2005.
1 ITC242 – Introduction to Data Communications Week 12 Topic 18 Chapter 19 Network Management.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
A Guide to major network components
Argonne National Laboratory is managed by The University of Chicago for the U.S. Department of Energy P0 Feedback Project: Merging EPICS with FPGA’s Nicholas.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
OPTICAL TIME DOMAIN REFLECTOMETER (OTDR)
Network Topologies.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
Network Design Essentials. Guide to Networking Essentials, Fifth Edition2 Contents 1. Examining the Basics of a Network Layout 2. Understanding Standard.
Chapter 4: Computer Networks Department of Computer Science Foundation Year Program Umm Alqura University, Makkah Computer Skills /1436.
Chapter 2 Network Design Essentials Instructor: Nhan Nguyen Phuong.
Wave Relay System and General Project Details. Wave Relay System Provides seamless multi-hop connectivity Operates at layer 2 of networking stack Seamless.
ICD-10 Staff Awareness. WHAT IS THIS COURSE? This course is designed to provide a basic awareness and understanding of ICD-10 and why it is so critical.
Workshop “Vacuum systems of Synchrotron Light Sources“ organized by MAX-LAB & ALBA Barcelona, th September 2005 Instrumentation and Vacuum Control.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
Without reference, identify principles relating to Computer Networks with at least 70 percent accuracy.
Usability Issues Documentation J. Apostolakis for Geant4 16 January 2009.
Computing Fundamentals Module Lesson 19 — Using Technology to Solve Problems Computer Literacy BASICS.
IRMIS 2 Overview Andrew Johnson Computer Scientist, AES Controls.
1 BROOKHAVEN SCIENCE ASSOCIATES IRMIS Universal Component Types D. A. Dohan NSLS 2 Brookhaven National Laboratory ICALEPCS 2007.
Dec 8-10, 2004EPICS Collaboration Meeting – Tokai, Japan MicroIOC: A Simple Robust Platform for Integrating Devices Mark Pleško
EPICS Direction to Support Large Projects and Incorporate New Technology Leo R. Dalesio 09/21/99.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
IRMIS Status EPICS 2009 Vancouver D. A. Dohan. Outline IRMIS hardware model cable/cable run channel list Equipment Inventory System RDB Domain separation.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
The microIOC Family Gasper Pajor EPICS Collaboration Meeting Argonne National Laboratory June 2006.
5 - 1 Copyright © 2006, The McGraw-Hill Companies, Inc. All rights reserved.
IRMIS: a practical Ansatz for an Accelerator Operations DB? S. Herb,
Chapter 5 Technology in the Business Office Copyright © 2011, 2006 Mosby, Inc., an affiliate of Elsevier. All rights reserved.
Oct 8-9, 2005ACS Collaboration Meeting – Archamps, France The MicroIOC From Custom To Production First customer: PSI 25 pieces.
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Chapter 6 CASE Tools Software Engineering Chapter 6-- CASE TOOLS
Computing Fundamentals Module Lesson 6 — Using Technology to Solve Problems Computer Literacy BASICS.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
The recent history and current state of the linac control system Tom Himel Dec 1,
Topic 4 - Database Design Unit 1 – Database Analysis and Design Advanced Higher Information Systems St Kentigern’s Academy.
Managed by UT-Battelle for the Department of Energy SCL Vacuum Control System Upgrade Derrick Williams
CIS 250 Advanced Computer Applications Database Management Systems.
Network Topologies.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department.
CEA DSM Irfu SIS LDISC 18/04/2012 Paul Lotrus 1 Control Command Overview GBAR Collaboration Meeting Paul Lotrus CEA/DSM/Irfu/SIS.
Slide 1 2/22/2016 Policy-Based Management With SNMP SNMPCONF Working Group - Interim Meeting May 2000 Jon Saperia.
Routing Algorithms Lecture Static/ Dynamic, Direct/ Indirect, Shortest Path Routing, Flooding, Distance Vector Routing, Link State Routing, Hierarchical.
Control System Considerations for ADS EuCARD-2/MAX Accelerators for Accelerator Driven Systems Workshop, CERN, March 20-21, 2014 Klemen Žagar Robert Modic.
Using Technology to Solve Problems Unit 2 Mod 2 SO 7.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Department of Mathematics Computer and Information Science1 CS 351: Database Management Systems Christopher I. G. Lanclos Chapter 4.
ControlLogix Portfolio
Accelerator control at iThemba LABS
Accelerator Reliability and Software
Relational Database Collaboration
What Do I Want from an RDB?
Chapter 4 Entity Relationship (ER) Modeling
A Virtual Implementation of VELA (CLARA)
Computer Literacy BASICS
Vacuum Controls Stephen Schuh Tom Porter 25 October 2006
Rack installation and local tests for the MEBT Chopper Rack
DOE Review of the LCLS Project 7-9 February 2006
Presentation transcript:

A U.S. Department of Energy Office of Science Laboratory Operated by The University of Chicago Argonne National Laboratory Office of Science U.S. Department of Energy What Do I Want from an RDB? Ned Arnold, APS March 9, 2005

Pioneering Science and Technology Office of Science U.S. Department of Energy 2 What do I want? To alleviate the guilt when someone mentions “documentation of the installed control system”. “As-built drawings” To allow for quick, yet well-documented changes. -e.g. “We need a thermocouple on the septum magnet for the next machine studies … tomorrow” To allow for quick, yet well-documented changes by a substitute staff member. -e.g. “… and George isn’t here today!” To provide convenient & thorough information for fast troubleshooting [i.e. helpful documentation] To provide convenient and thorough information to “on-call” staff for systems for which they are unfamiliar. -“I can’t talk to the Attenuator in Sector 7” -“There is a white box on my medm screen”

Pioneering Science and Technology Office of Science U.S. Department of Energy 3 What do I want? To make the learning curve of applications less steep To automate finding the root cause of a communication problem To run numerous “integrity crawlers” for constant monitoring of the health of the control system (self generating?) To alleviate the guilt when someone mentions “documentation of the installed control system”.

Pioneering Science and Technology Office of Science U.S. Department of Energy 4 What doesn’t work? Maintaining accurate information on the thousands (~15,000+) of installed devices and hundreds of independent applications is not manageable with a “Revision Controlled Drawing” approach. -Our control system is not static. -There are many “soft” entities that defy drawings. -Different “views” of the system are needed at different times, yielding redundant drawings. -Drawings cannot be “queried”.

Pioneering Science and Technology Office of Science U.S. Department of Energy 5 Drawings are not maintainable

Pioneering Science and Technology Office of Science U.S. Department of Energy 6 What might work? What do we want to document? Process Variables All PV definitions in all the IOC’s Provides an aggregate collection of the entire “distributed database”

Pioneering Science and Technology Office of Science U.S. Department of Energy 7 What might work? What do we want to document? IOC’s (CAS’s) All active IOC’s IP # Contact Person Ethernet Connections Boot path etc, etc, etc

Pioneering Science and Technology Office of Science U.S. Department of Energy 8 What might work? What do we want to document? Components All installed components VME /VXI Modules Instruments Racks etc, etc, etc

Pioneering Science and Technology Office of Science U.S. Department of Energy 9 What might work? What do we want to document? Cables All installed cables Ambitious, but necessary

Pioneering Science and Technology Office of Science U.S. Department of Energy 10 What might work? What do we want to document? Installed ‘Applications’ A collection of functions (databases, seq programs, etc.) that can be identified as a unique “application”: LINAC Beam Position Monitors Bunch Compressor Scraper Storage Ring Injection Kicker PS Control SR Vacuum Valve Interlocks

Pioneering Science and Technology Office of Science U.S. Department of Energy 11 What might work? What do we want to document? Process Variables IOC’s (CAS’s) Components Cables Must document all of these installed entities … and …

Pioneering Science and Technology Office of Science U.S. Department of Energy 12 What might work? What do we want to document? and their relationships to one another -Components are related to other components by - how they communicate control information - how they are housed - how they are powered -Applications are related to PVs, Components, etc -IOCs are related to Components, PVs, Applications -Cables are related to Components (via ports)

Pioneering Science and Technology Office of Science U.S. Department of Energy 13 All entities are inter-related … Given a PV, one can determine: Applications Devices, IOC Cables Given a IOC, one can determine: Applications Devices Cables PVs Given a Cable, one can determine: Device, IOC PV Applications

Pioneering Science and Technology Office of Science U.S. Department of Energy 14 What can it tell me? What process variables are associated with this device? What process variables were added, changed, or removed since the last run? Where does the other end of this cable go? What components do all of these non-functioning devices have in common? Which module type in this system has the worst reliability history? How many devices of a particular model number are installed? Where are all the devices of a particular model number installed? What application software will be affected if this device is removed? What equipment will be affected when this breaker is locked-out?

Pioneering Science and Technology Office of Science U.S. Department of Energy 15 What do I get? No guilt when someone mentions “documentation of the installed control system”. Quick, yet well-documented changes. Quick, yet well-documented changes by a substitute staff member. Convenient & thorough information for fast troubleshooting [helpful documentation] Convenient and thorough information to “on-call” staff for systems for which they are unfamiliar. -“This PV isn’t working” -“I can’t talk to the Attenuator in Sector 7” -“There is a white box on my medm screen”

Pioneering Science and Technology Office of Science U.S. Department of Energy 16 Benefits of a relational database approach Utilizing relational database technology and defining connections between the entities yields the benefits of extensive querying capabilities through the tables of data. -Immediate tracing of a fault to the root cause -Predicting what applications will break when a module is removed -Locating every instance of a particular device Convenient and expedient [ i.e. really cool ] tools encourage wide participation in keeping the data current

Pioneering Science and Technology Office of Science U.S. Department of Energy 17 Three Relationships of Components: Control/Housing/Power

Pioneering Science and Technology Office of Science U.S. Department of Energy 18 How do we get there? Two approaches -Descriptive (describes what is installed) -Prescriptive (defines what is to be installed) An exhaustive prescriptive solution has not been accomplished (as far as we know) We think an exhaustive descriptive solution is within reach Having an exhaustive descriptive solution may alleviate some difficult requirements on a prescriptive solution (e.g. history) An exhaustive descriptive solution and a partial prescriptive solution may certainly co-exist. Question: Are an exhaustive descriptive solution and an exhaustive prescriptive solution redundant? -If yes, not until someone succeeds -If no, then we all ought to do the easy one first

Pioneering Science and Technology Office of Science U.S. Department of Energy 19 How do we get there? We feel that everyone can benefit from an exhaustive descriptive approach and that it is complementary to the prescriptive efforts being undertaken.

Pioneering Science and Technology Office of Science U.S. Department of Energy 20 What do I want? An identification of those areas where there is the most overlap of needs. An intense collaboration to fulfill those needs in a way that can be extended to accommodate site specific requirements. If we can leverage enough resources, we feel that it is entirely possible to deliver an exhaustive descriptive approach (that can be used at any EPICS site) by the end of This does not obviate the need for prescriptive solutions. In fact, it might make them easier.