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 IRMIS: A Descriptive Approach Ned Arnold, APS April 27, 2005 The submitted manuscript has been created by the University of Chicago as Operator of Argonne National Laboratory (“Argonne”) under Contract No. W ENG-38 with the U.S. Department of Energy. The U.S. Government retains for itself, and others acting on its behalf, a paid-up, nonexclusive, irrevocable worldwide license in said article to reproduce, prepare derivative works, distribute copies to the public, and perform publicly and display publicly, by or on behalf of the Government.

Pioneering Science and Technology Office of Science U.S. Department of Energy 2 RDB Workshop – March 9-11, 2005 Institutions Represented: -APS, SNS, SLAC, LCLS, FERMI (D0), TRIUMF, BESSY, DESY New Terminology -Grand Unified Relational Database - GURD -System for Tabulating Engineering Installation Nomenclature - STEIN -dialect agnosticity -Descriptive vs. Prescriptive Relational Databases

Pioneering Science and Technology Office of Science U.S. Department of Energy 3 What We Want to … Track … -Process Variables -Devices -Engineering Device Properties (scale, calibrations data, serial #, base addr) -Physics Device Properties -Signals -Components -Cables -Configuration Files -Control Software - Software Versions - Impact of PV changes on clients … and all the relationships between them!

Pioneering Science and Technology Office of Science U.S. Department of Energy 4 What We Want to … Generate … -Templates -Databases -Faceplate Displays -Configuration Files for other tools (alh, save/restore, MPS, etc) -Web-based reports -Fault Analysis -Cause/Effect Analysis

Pioneering Science and Technology Office of Science U.S. Department of Energy 5 RDB Workshop – March 9-11, 2005 Aggregate Requirements: -“Basically, we want to do everything thought of in the past and anything to be thought of in the future” (LCLS) Implementation seems to be quite a challenge -“… impossible to get IOC engineers to import the data” -“History of attempts” -“not maintainable (after a few years)” “but we still need it!” grail: “the object of an extended or difficult quest”

Pioneering Science and Technology Office of Science U.S. Department of Energy 6 IRMIS (APS) “As Built” Control System Heuristic Rules Manual Input Data Mining Scripts

Pioneering Science and Technology Office of Science U.S. Department of Energy 7 What we require a new system to support (BESSY) Generation of *.db, *.substitution, *.template All other kinds of configuration data ALH, Archiver, Save/Restore, Orbit-Correction, other yet unknown applications…  Different views to the same dataset EPICS DB CDEV ddl RDB Save/Restore Archiver AlarmHandlerStripToolgeneric Appl. Screens (adl) Orbit-Corr.Measurement High Level Applications Navigation Displays IOC Preconfigured Applications ** * * Actually configured from RDB **

Pioneering Science and Technology Office of Science U.S. Department of Energy 8 Relational Database (TRIUMF) RDB “devices” Web Application Perl Tools EPICS configuration files

Pioneering Science and Technology Office of Science U.S. Department of Energy 9 dbd files → epicsOra → db file (DESY)

Pioneering Science and Technology Office of Science U.S. Department of Energy 10 Database System (D0) Oracle Hardware Database Template Definitions DB Creation Record Field Definitions Record Extract Template Generators List of Records For IOC IOC Id Template Extract Template Generators For IOC Instance Creation

Pioneering Science and Technology Office of Science U.S. Department of Energy 11 Is there any room for “collaboration”? Start with “EPICS specific” information -Things every EPICS site has to deal with -Partition tables between “common” and “extended” (site-specific items) Provide “exhaustive descriptive” tables and crawlers to populate the data … allowing sites to continue with their own “prescriptive” schemes while benefiting from an “as built” repository -Co-existence -Take what’s best from each Ensure SQL dialect agnosticity

Pioneering Science and Technology Office of Science U.S. Department of Energy 12 Co-existence Common Descriptive Tables Site-specific Descriptive Tables Site-specific Tables for “everything else” Partition the problem …

Pioneering Science and Technology Office of Science U.S. Department of Energy 13 IRMIS::Base 1.0 PV Table PV-Usage-by- Client Table IOC Table Component/Device Table Cable Table PV Crawler edl Crawler alh Crawler archiver Crawler CA Security Crawler adl Crawler Save/Restore Crawler Sequencer Crawler sdds Crawler XAL Crawler IRMIS::Base 1.0 Release Date : April 27, 2005 IOC Table Editor PV Crawler rdbBase 1.1 StripTool Config Crawler IOC Attribute Table

Pioneering Science and Technology Office of Science U.S. Department of Energy 14 Summary Two approaches -Descriptive (describes what is installed) -Prescriptive (defines what is to be installed) The “ultimate” solution is probably a combination of approaches An exhaustive descriptive solution is easier Having an exhaustive descriptive solution may alleviate some difficult requirements on a prescriptive solution (e.g. history) We feel that everyone can benefit from common exhaustive descriptive approach and that it is complementary to the prescriptive efforts being undertaken. IRMIS::Base 1.0 is available

Pioneering Science and Technology Office of Science U.S. Department of Energy 15 An Opportunity …