Controls Configuration Information Management of Software and Hardware Components

1. Controls Configuration Information Management of Software and Hardware Components Ronny Billen AB-CO-DM With input from and discussions with Franck, Jan, Eugenia, Eric, Marc, Julian, Jean-Luc AB/CO Technical Committee

2. Controls Configuration • Purpose & scope • Topology, relations, description of all controls devices to remotely control accelerator equipment by deploying software (drivers, programs) to hardware (consoles, gateways, front-end computers) • Vision & strategy since 2003 • Single configuration model, uniform data-entry tools • Intermediate step by federation of configuration databases (2005) • Adiabatic replacement of un-maintainable components (2005+) • Work & involvement since 2003 • Extension of working model (GM) for PS machines to SPS and LHC • New implementation for FESA devices, fully database-driven • Started to address other, niche & industrial systems (Power Converters, PLC, SCADA) • Criticality high & required effort high, urgent • All accelerators are affected, old and new • Overall in-depth architectural knowledge is gone • Continued work is required on data entry tools, database structures, data extraction interfaces • Stepping back is impossible, freezing the current situation is costly AB/CO Technical Committee

3. PS FEC SPS FEC LHC/LEIR FEC ORACLE Forms Console PSC C/S de-supported since Jan 2005 XMotif / C Java Equipment Classes GM GM Applications XMotif / C Java HardwareComputersProgramsMenusWorking SetsPLS PL/SQL Web-deployed+ authentication+ authorization ApplicationServer OWA SymbolsPro*C GeneralcomponentsJAPC DBRefPro*C GeneralcomponentsASC beans JDBC Software procedures to drive equipment ABC Devices D-Classes GMFESA SL-equip GMFESA DBRT DBRTGenPro*C BitpatternTreatment CodesMetaproperties J.D.S.1999 PL/SQL Crates, modules, cards, busses, connectors, drivers, programs J.D.S.2005 FESA DSC InitPro*C F-Devices F-Classes FESA FESA CMW SL-Equip rc.local SL-Inventory Sys cmd Programs IO Config Address =ModType/Lun/Ch# transfer.ref Ad-hoc data entry forms 1553 addresses Sys cmd Programs Software device needs to map to installed hardware IEPLC

4. Database • Based on original design of 1986 • PSC (PS Controls) account covers : • PS controls software configuration • PS controls hardware configuration • PS controls assets (moderately: limited to serial number and manufacturer) • PS operational data (moderately: reference and archive settings) • Since 2003 an evolution towards ABC (AB Controls) aims to cater for SPS (SL-Equip) and LHC (FESA) concepts; • The model has evolved significantly (e.g. bit patterns, treatment codes, meta properties) • PSC has been emulated from ABC for backwards compatibility (GM) • Within the database, very few data consistency constraints have been implemented • A lot of logic has been implemented in the data input (Oracle Forms) and data extraction interfaces (Pro*C programs) • Specific processes were launched from the Oracle Forms menu applications • Data consistency checks were performed a posteriori • Knowledge transfer has been difficult • There are other data sources around (IEPLC, 1553 multidrop,…) • Work to do • Involve complete DM section in configuration database • Discussion required with all other sections to get full understanding, elaborate strategy for common vision • Enforce all relations, checks, rules and logic within the database model • Integrate fully the new generation FESA software devices • Cater for requirements of industrial equipment AB/CO Technical Committee

5. Data Entry tools • Oracle Forms applications: Menus & Forms • Client-Server deployed Forms de-supported by Oracle since January 2005 • Web-deployment of the Forms, same look and feel • Self-service tool to be used by end-users / experts (not always CO) • Started to enforce security (authentication, authorization) • Initial regression on functionality due to the shift from 2-tier to 3-tier • Gradually overcoming regression with dedicated PL/SQL code • Client platform dependency (browser): Oracle prefers IE on Windows • Unresolved stability problems on Linux • Only Mozilla 1.5 with SUN plug-in 1.4.2 on RedHat AS 3.0 is guaranteed • There is a possible workaround with the use of an appletviewer • Work to do • Maintain current Forms, address reported problems asap • Assist clients to ensure data input, keep database synchronized with reality • Restore missing functionality, implement additional requests • Name change, simultaneous forms, history log (undo), error checking • Refine authorization to deeper granularity • Identify ad-hoc data entry tools for replacement (single source, single entry) • Try out alternatives to Oracle Forms in line with current technology and developer education (Oracle HTMLDB, Oracle ADF) • Consider convergence with FESA toolbox ? AB/CO Technical Committee

6. Control Room Applications • Console on control room workstation • Configured from Configuration database • Configurable through Oracle Forms application CONSOLE • Two flavors: XMotif (old) and Java (common console manager) • All applications (C or Java) can be launched from the two • High-level Applications • Configured from Configuration database: executables that can be launched from the console • Two flavors, three tastes: • C applications depending on DBRT (i.e. UNIX hash file necessary for equipment access; generated by Pro*C application DBRTGEN) • Java applications depending on Java Directory Services anno 1999 (used by ASC layer) • Java applications depending on Java Directory Services anno 2005 ( taking into account the evolved database model) • Work to be done by the application programmers • In order to reduce the maintenance cost, phase out legacy software : XMotif/C apps, Pro*C apps, DBRT, JDS-1999 (ASC components) • Re-implement applications; need to adopt new working habits in this process: • Eclipse, new frame, common build, release AB/CO Technical Committee

7. Software Configuration FEC • Declaration through Oracle Forms application • GENMOD – General Modules • Definition of PS-type software classes with corresponding variables and properties (including alarms) • Generation of devices i.e. class instances associate with FEC • AB-DEVICES • Extension of GM to include other implementations • SL-Equip and FESA (limited) • Nothing else (PLC, supervision systems, FGC) • Different approach taken for FESA: • FESA toolkit • Design, Instantiate, Deploy • Navigate • Retrofit, analyze, versioning • Work to do • Maintain the Forms, mainly for the General Modules • Collaborate with equipment groups to satisfy their specific software configuration requirements, e.g.: • BIC supervision (currently XML edited files by hand) • AB/PO properties of FGCs & electrical circuits (on-line use of ADC, DCCT calibration curves) AB/CO Technical Committee

8. Hardware Configuration FEC • Declaration through Forms application HARDWARE • DSC Configuration (type & instance) • crate, I/O & ADC modules, CAMAC loop, MIL1553 bus controller, GPIB • Drivers and programs necessary for FEC startup • Boot files generated from configuration database via introspection (Pro*C program DSCInit) • Different approach taken for LHC: • LHC Functional Layout database • Complete description of the (to-be) installed machine with all positioned, functional components and their inter-relations • Single source of reference data for functional layout information • Follows LHC QAP and naming conventions • Does not capture pure controls information • Work to do • Capture hardware functional layout components for LHC through LHC layout DB • Propagate hardware in configuration DB, complete missing information with Oracle Forms applications • Collaborate asap with BDI, RF and BIC (200, 60 and 30 VME crates respectively) • Establish procedures for deployment and exploitation with equipment groups, CO/FC and CO/HT for HW-SW mapping (chicken & egg problem, allow for partial declaration) • Separate hardware functional layout components from physical hardware assets AB/CO Technical Committee

9. PC-type Front End Computer (2U, 19”, 3 slots) WorldFIP repeaters PMC WorldFIP managerPCI Timing receiver cardPC motherboard

10. Data Browsing tools • Database browser and Documentation • Allows navigation in the database model • For all configured objects • To all levels of detail • Via the relationship links • Dynamic generation of the web pages by means of the Oracle Web Access (OWA) cartridge i.e. PL/SQL stored procedures interacting with the web browser • Old (but not obsolete) technology without explicit separation between business logic and presentation layer (i.e. not MVC) • Work to do • Maintain the data browsing tools and keep documentation up-to-date SW-HW mapping: Address = Module Type +Logical Unit Number + Channel Number AB/CO Technical Committee

11. Conclusions • Work to be done before startup 2006 • Involve complete DM section in configuration database to establish knowledge base • Elaborate the proposed strategy for LHC hardware configuration with equipment groups, CO/HT and CO/FC, starting from the LHC layout DB • Integrate fully in the configuration DB the new generation FESA software devices; position the usage of the tools • Establish procedures for deployment and exploitation with equipment groups, CO/FC and CO/HT for software to hardware mapping • Maintain all current Forms and restore missing functionality • Collaborate with equipment groups to satisfy their specific software configuration requirements, including industrial equipment • Work that has to be done to reduce maintenance costs • Reinforce database model on key relations, consistency checks, rules and logic • Restrict data manipulation authorization to finer granularity • Identify ad-hoc data entry tools for replacement • Define medium-term policy on the use of Oracle Forms and alternatives • Phase out legacy software : XMotif/C apps, Pro*C apps, DBRT, JDS-1999 AB/CO Technical Committee