1. 14 December 2006 CO3 Data Management section Controls group Accelerator & Beams department Limits of Responsibilities in our Domains of Activities Ronny BILLEN, CERN AB/CO/DM

2. R. Billen CO3 14 December 2006 Data Management - 2 Mandate  The AB-CO-DM section is mandated to provide support for all data management activities in the AB Department, necessary for the control, exploitation and maintenance of the accelerator chain.  This support covers requirement analysis, data modeling, database design and implementation, development of generic data interfacing tools, participation in collaborations for larger application development.  The support may also translate in guidance and assistance towards existing CERN-wide data management infrastructures.  The team is currently composed of 6 staff, 1 student, 1 FSU and 1 unpaid associate.

3. R. Billen CO3 14 December 2006 Data Management - 3 Domains of Data Management Machine Layout Assets Controls Configuration Operational Data Scope: all physical equipment, installed or not, requiring maintenance or follow-up Technology: D7i commercial software; custom layer by CERN/TS: Manufacturing and Test Folder (MTF), integrated in Engineering Data Management Service (EDMS) Scope: All components in the accelerator installations: magnets,..., electrical circuits, racks, electronic modules,... Technology: ORACLE, in-house design; ASP browsing interfaces; Oracle Forms data manipulation Scope: Controls system topology; software device mapping & addressing, front-end computer configuration, communication mechanism Technology: ORACLE, in-house design; Oracle Forms (legacy); JAVA APIs Scope: On-line data for operations: Settings, measurements, long-term logging, alarms, post-mortem Technology: ORACLE, in-house design; APIs in Java, PL/SQL, XML QA Scope: Equipment classification, identification, naming Technology: Quality Assurance Plan, document approval cycle

4. R. Billen CO3 14 December 2006 Data Management - 4 Data management responsibilities –what has changed over the years–  General policy has evolved AB/CO provides necessary database and interfacing software implementation (DB objects, DB APIs, generic applications) AB/CO provides necessary database and interfacing software implementation (DB objects, DB APIs, generic applications) All data can be –and should be – centrally managed, organized in the distinct interlinked areas: All data can be –and should be – centrally managed, organized in the distinct interlinked areas: Operational data: LSA settings, measurement, logging, alarms, P-MOperational data: LSA settings, measurement, logging, alarms, P-M Controls Configuration: s/w devices, h/w config, working sets, knobsControls Configuration: s/w devices, h/w config, working sets, knobs Layout: all installed equipment (machine, electronics,...)Layout: all installed equipment (machine, electronics,...) Assets: real equipment characteristics, maintenance, traceabilityAssets: real equipment characteristics, maintenance, traceability The owners of the information (equip & operation groups) have the responsibility to enter, validate and keep the data up-to-date The owners of the information (equip & operation groups) have the responsibility to enter, validate and keep the data up-to-date AB/CO provides active support, advise and guidelines to the clients for effectively using the tools AB/CO provides active support, advise and guidelines to the clients for effectively using the tools AB/CO does perform data entry in case of bulk loading of initial data sets, data migration from one place to another AB/CO does perform data entry in case of bulk loading of initial data sets, data migration from one place to another AB/CO is open to respond to specific requests on reporting tools and data manipulation such as global updates AB/CO is open to respond to specific requests on reporting tools and data manipulation such as global updates

5. R. Billen CO3 14 December 2006 Data Management - 5 General responsibilities  CO/DM responsibility Providing & maintaining necessary database and interfacing software implementation (DB objects, DB APIs, generic applications) Providing & maintaining necessary database and interfacing software implementation (DB objects, DB APIs, generic applications) Data migration & bulk loading of initial data sets Data migration & bulk loading of initial data sets Providing of necessary data browsing tools Providing of necessary data browsing tools Providing of necessary data manipulation tools Providing of necessary data manipulation tools Providing support, advise and guidelines on the database and tools usage Providing support, advise and guidelines on the database and tools usage On request, cater for specific data manipulations On request, cater for specific data manipulations Ensure quality of service, required availability of data, diagnostics Ensure quality of service, required availability of data, diagnostics  Client responsibility Enter the data. Semantically Validate & Maintain correctness of the data. The data is owned by the equipment group Enter the data. Semantically Validate & Maintain correctness of the data. The data is owned by the equipment group Provide specs on additional requirements on top of the generic tools Provide specs on additional requirements on top of the generic tools Note that CO/DM clients are Equipment Groups (incl. CO) and AB/OP Note that CO/DM clients are Equipment Groups (incl. CO) and AB/OP  IT service and responsibilities Database hosting: operating system and Oracle system software installation, maintenance (upgrades, patches) Database hosting: operating system and Oracle system software installation, maintenance (upgrades, patches) Interventions in case of system failures Interventions in case of system failures

6. R. Billen CO3 14 December 2006 Data Management - 6 Responsibilities – Machine Layout  LHC, TI2, TI8, TD62, TD68 Functional Layout database infrastructure & tools: CO/DM Functional Layout database infrastructure & tools: CO/DM Data capture racks, electronics, electrical circuits, optics: CO/DM + EquipGroups Data capture racks, electronics, electrical circuits, optics: CO/DM + EquipGroups Initial data capture transfer lines : CO/DM Initial data capture transfer lines : CO/DM Other data capture: TS/IC + EquipGroups Other data capture: TS/IC + EquipGroups Data maintenance (beyond 2007): EquipGroups Data maintenance (beyond 2007): EquipGroups Note: the database can cover any installed equipment Note: the database can cover any installed equipment  SPS, TT10, TT20, TT40, TT41, TT60 SPS ring (old) database and data: CO/DM (R. Billen) SPS ring (old) database and data: CO/DM (R. Billen) TL not managed any more; data directly in LSA: AB/OP + AB/ABP TL not managed any more; data directly in LSA: AB/OP + AB/ABP Note: limited scope (does not include vacuum chambers, apertures,...) Note: limited scope (does not include vacuum chambers, apertures,...)  PS complex ACCIS (old) database infrastructure (ABS): CO/AP (J. Schinzel) ACCIS (old) database infrastructure (ABS): CO/AP (J. Schinzel) Data maintenance: AB/OP Data maintenance: AB/OP Note: medium-term maintenance uncertain Note: medium-term maintenance uncertain

7. R. Billen CO3 14 December 2006 Data Management - 7 Responsibilities – Controls Configuration  Database, browsing tools, data manipulation tools : CO/DM Infrastructure development and maintenance Infrastructure development and maintenance Includes APIs (JDS, FESA DMS)Includes APIs (JDS, FESA DMS) Does not include the FESA toolset (CO/FE)Does not include the FESA toolset (CO/FE)  Data entry and data maintenance : EquipGroups Software configuration of front-end devices (e.g. classes, properties, fields) for implementations GM, SL-Equip and FESA Software configuration of front-end devices (e.g. classes, properties, fields) for implementations GM, SL-Equip and FESA Hardware configuration of front-end devices (e.g. memory addressing, straps) Hardware configuration of front-end devices (e.g. memory addressing, straps) Expert working sets and knobs configuration Expert working sets and knobs configuration  Data entry and maintenance : AB/OP Console manager definitions Console manager definitions Operational working sets and knobs configuration Operational working sets and knobs configuration  Data propagation tools to other services : CO/DM Local data generation: FEC boot files; PLC firmware; SCADA config file Local data generation: FEC boot files; PLC firmware; SCADA config file Controls communications middleware (CMW) Controls communications middleware (CMW) High level operational controls database (LSA) High level operational controls database (LSA) On request: additional reporting facilities, ad-hoc expert queries, bulk uploads, updates On request: additional reporting facilities, ad-hoc expert queries, bulk uploads, updates

8. R. Billen CO3 14 December 2006 Data Management - 8 Responsibilities – Assets  EDMS-MTF Single central asset management system for all equipment that needs maintenance or follow-up. TS/CSE Single central asset management system for all equipment that needs maintenance or follow-up. TS/CSE Explain, advise, initiate, liaise, help the equipment group with the usage of MTF : CO/DM Explain, advise, initiate, liaise, help the equipment group with the usage of MTF : CO/DM  ABCAM portal : CO/DM Hosting of assets data before going to MTF Hosting of assets data before going to MTF Development of limited set of data entry tools in ABCAM Development of limited set of data entry tools in ABCAM Development of custom reporting tools on the asset management Development of custom reporting tools on the asset management Explain, advise, initiate, help the equipment group with the usage of ABCAM Explain, advise, initiate, help the equipment group with the usage of ABCAM  Assets data : EquipGroups Gather, check, validate and provide assets data in the required format Gather, check, validate and provide assets data in the required format  Quality Assurance : CO/DM Assist equipment groups in the definition of equipment codes for the SPS and the PS-complex Assist equipment groups in the definition of equipment codes for the SPS and the PS-complex Endorse and publish official equipment codes, to be used in equipment design, drawings, documents, assets, layouts and operational data Endorse and publish official equipment codes, to be used in equipment design, drawings, documents, assets, layouts and operational data

9. R. Billen CO3 14 December 2006 Data Management - 9 Responsibilities – Operational data  Operational settings LSA database infrastructure : CO/DM LSA database infrastructure : CO/DM LSA application database APIs : LSA team, assisted by CO/DM LSA application database APIs : LSA team, assisted by CO/DM Definition and generation of parameters and their values : AB/OP Definition and generation of parameters and their values : AB/OP Propagation of external data into LSA : by CO/DM on LSA request Propagation of external data into LSA : by CO/DM on LSA request  Measurements and Logging Database infrastructure, APIs (Java, PL/SQL, XML) : CO/DM Database infrastructure, APIs (Java, PL/SQL, XML) : CO/DM Measurement applications : CO/AP (Java) and CO/IS (PVSS) Measurement applications : CO/AP (Java) and CO/IS (PVSS) Measurement to logging (filtering) API: CO/DM Measurement to logging (filtering) API: CO/DM Providing tools for operational summaries, statistics, performance reports : CO/DM Providing tools for operational summaries, statistics, performance reports : CO/DM Definition and generation of variables and their meta data : EquipGroups (...but validation can take some effort of CO/DM) Definition and generation of variables and their meta data : EquipGroups (...but validation can take some effort of CO/DM)  Alarms – Post-Mortem No direct responsibility of CO/DM No direct responsibility of CO/DM