LHC-CP Workshop 5-6 April 2001 Database Breakout Session
 

Raison d'ętre

Proper data management is vital for any information system, thus also for the LHC Controls system. The data management aspect should not be considered at the last moment.

Objective

Establish guidelines for the groups for managing data. Ensure seamless data integration if the requirement exists. If possible, identify areas where data management work has (or should be) started.

Topics

LEP controls: what went OK, what went wrong?

=> Copy & Paste for LHC?
Sources of information used by the Controls system:
  • Layout data
  • Configuration data
  • Data for Post Mortem (i.e. Measurements, Logging, Alarms, Transient data)
  • LHC production data that exists today already
  • "Private" data systems (e.g. PVSS): can they be integrated?
Other Database activities such as String 2 data.
Time stamping, a vital aspect for data correlation.
Object Oriented software, how does the data map to relational databases?
Tools to use or not to use (e.g. Oracle or alternatives, PL/SQL or Java, MP5 asset management,…)
=> Guidelines, policy to adopt

How?

Six 15-minute presentations, discussion, extract best common-sense proposals.

  1. Oracle for LEP (speaker: Billen R.)
    History + Introduction to overall LEP controls
  2. (LEP) Controls Data and its sources (speaker: Albert M.)
    How was the Controls database fed with the right data?
  3. LHC production data (speaker: Pettersson T.)
    Useful stuff for Controls; today's availability, format, policy
  4. Complimentary Database solutions (speaker: Peryt M.)
    Something more efficient? But can it be integrated?
  5. Data in PVSS Scada systems (speaker: Martini R.)
    How do we get it into Oracle
  6. Tools for database design and implementation (speaker: Mathieson D.)
    What should be used (tools, languages), what's AS's policy.

R.Billen
Updated 14 March, 2001
  Top
 
These pages are maintained by NBL and RJL