European Organization for Nuclear Research LHC Gas Control System Applications G.Thomas, J.Ortola Vidal, J.Rochez EN-ICE Workshop 23 April 2009

European Organization for Nuclear Research Outline Scope Objectives Strategy/Principles Support and Maintenance Pros & Cons

European Organization for Nuclear Research GCS scope 4 Experiments ~23 std gas systems to build Commonalities Standard devices Valves, flow meters, mass flow controllers, etc… Limited number of exotic devices (Webmas, ELMB ) Modular architecture Mixer, Distribution, Pump, Analysis, Purifier, etc… Diversity Optional modules Options in modules

European Organization for Nuclear Research GCS diversity

European Organization for Nuclear Research ICALEPCS FR2.3-6O 5 Gas system layout Purifier Mixer Recovery Pump Primary Gas Supply Analysis USA 15 UX cavern Analysis Distribution Gas building Functional modules Other Modules CO2 Absorber, CO2 Envelope, Exhaust Humidifier

European Organization for Nuclear Research ICALEPCS FR2.3-6O 6 Gas modules’ diversity Gas x 0 T T PT Optional devices Architecture variation PT

European Organization for Nuclear Research GCS objectives -> Provide homogeneous end-user applications What we handle Build turnkey control application Supervision layer Synoptic views and navigation, alarm handling, recipes, etc… Process Control layer I/O, steppers, interlock, common logic, etc… Define and setup the control infrastructure for each Experiment What we do not handle Setup and configuration of hardware equipments and instrumentation

European Organization for Nuclear Research GCS strategy/principles Strategy Gas systems’ architecture based on a generic model Use industrial technologies SCADA, PLC, fieldbuses Use of UNICOS FW and code generator tools Principles Model-oriented design for both Supervision & Process control layers Tools To produce automatically the PVSS and PLC code of any GCS instance

European Organization for Nuclear Research Dev. Phases/interactions with customer Deployment Commissioning URD EN-ICE Capture of the functional requirements of the systems for the process & supervision layers Agreement on the needs between provider & customer EN-ICE Validation of the application in the lab Design Code implementation Tests (logic, IO signals, etc…) Packaging Release EN-ICE Installation of the new application in-situ Loading of PLC application Setup of PVSS application Load of pre-defined parameters (recipes) Pass the system to Gas experts PH-DT1 Tests of application before production Hardware connection tests Functional tests (critical interlocks, etc…) Final tuning of thresholds & set points Training of Gas team members Gas Expert (PH-DT1) Provider (EN-ICE)

European Organization for Nuclear Research GCS operational support Type of support cases Bad configuration parameters (archive, deadband, stop of plc, etc…) Exp. Infrastructure problems (remote access, dip setup, etc…) Support level First line (PH-DT1 gas piquet) Second line support based on best effort (EN-ICE) Tools Remedy to handle bugs or requests Savannah for bug & patch tracking

European Organization for Nuclear Research GCS maintenance and upgrades Type of upgrades New version of software/firmware for PVSS (UNICOS FW) or PLC (baseline) New system/modules to integrate Bug fixes Methodology Any new request is first analyzed in URD before implemented Validation done in lab Tools Configuration source code management tools (CVS, savannah)

European Organization for Nuclear Research GCS Pros and Cons Pros Based on existing software control libraries (UNICOS FW). Keep source code repository always up-to-date. Keep homogeneity across systems. Open architecture –extensibility/flexibility. Autonomy of users during commissioning and operation. Cons Any modification requires an upgrade in various places. No control on equipment setup and configuration. Synchronization between PH-DT1 and EN-ICE for tests. Software version dependencies.