Samy Chemli – 2014-06-11. Configuration Management - S. Chemli EN-MEF – 2014-06-11 2 Contents Configuration Management Hardware Baseline Change Management.

Slides:



Advertisements
Similar presentations
Configuration Management
Advertisements

Management’s preliminary comments to the ERC Report.
Session 8 - Long Shutdown 2 Strategy and Preparation LIU Planned Activities Reference : RLIUP Oct.2013 (indico) “Work Effort in the LHC Injector Complex,
Configuration Management
Consolidation and Upgrade of the LHC Experimental Vacuum Sectors
HLTC 15 th April 2014 EDMS: Y. Muttoni EN-MEF-INT with the contribution of P. Fessia.
Software Configuration Management
HL-LHC Standards and Best Practices Workshop (11-13 June 2014)
3 Dec 2003Market Operations Standing Committee1 Market Rule and Change Management Consultation Process John MacKenzie / Darren Finkbeiner / Ella Kokotsis,
Role of Management and Technical Coordination
Current Job Components Information Technology Department Network Systems Administration Telecommunications Database Design and Administration.
HL-LHC Quality management
CERN Methodology document 1 Use of CERN CAD Exchange tool Process and rules for exchange of CAD files by using CERN CAD Exchange tool. Prepared by : B.
Engineering Data Management System CERN Drawing Directory overview - Stephan Petit - CERN EST/ISS - LHC Auditorium :00 CERN DRAWING DIRECTORY.
CERN Accelerators Topology Configuration and Change Management Engineering Department Thomas Birtwistle, Samy Chemli – EN/MEF/DC.
ATLAS EXPERIMENT INTEGRATION TASK: SPACE MANAGEMENT Tatiana Klioutchnikova 05/06/
HL-LHC Configuration Management Keywords : HW Baseline, Naming, Parameters, Layout DB, Change Control The HiLumi LHC Design Study (a sub-system of HL-LHC)
CERN Equipment Management Integrates Safety Aspects EDMS Doc Eva Sanchez-Corral Mena, Stephan Petit / CERN 1 CERN Equipment Management Integrates.
Release Management Configuration management. Release Management Goal Coordinate the processes through the project development life cycle Ensure the.
The HiLumi LHC Design Study is included in the High Luminosity LHC project and is partly funded by the European Commission within the Framework Programme.
CLIC Project breakdown structure: organization, documentation and cost estimate Beam Instrumentation Workshop, June 2-3, 2009 CLIC Project breakdown structure:
LHC Hardware Commissioning Review May 2005, CERN, 1211 Geneva 23 1 LHC Hardware Commissioning Review Contribution ID: 20 – Quality assurance and.
Hall 180 Cryogenic test facility: Project management: Project Change Request, EVM and Interface Sheet L. Serio.
HC Review, May 2005 Hardware Commissioning Review Hardware Commissioning Review Quality Assurance and Documentation of Results Félix Rodríguez Mateos,
Develop Project Charter
Corporate Technical Infrastructure Management From MP5 to a Corporate Technical Infrastructure Management System.
Configuration Management and Change Control Change is inevitable! So it has to be planned for and managed.
Margarita Saifoulina BE/RF/SR. Outline Data Management EDMS & MTF for RF structures Future prospects for EDMS/MTF solution Data Management EDMS & MTF.
ECRs and ES for the LHC Last presentation on the 26 th of August 2015 (LMC 232) S. Chemli for EN-MEF-DC LMC xxx.
Lecture 6: Writing the Project Documentation Part IV.
12/8/2015PLC Software Configuration WG - CCB1 PLC Software Configuration WG Members Philippe Gayet Fréderic Havart Renaud Barillère [Mathias Dutour]
The HiLumi LHC Design Study is included in the High Luminosity LHC project and is partly funded by the European Commission within the Framework Programme.
Management of Software Project CSM Software Configuration Management (SCM)
MTF – Manufacturing and Test Folder Large Scale Deployment of MTF Sonia Mallón Amérigo Elena Manola-Poggioli on behalf of the EDMS Team, TS-CSE.
Firmware - 1 CMS Upgrade Workshop October SLHC CMS Firmware SLHC CMS Firmware Organization, Validation, and Commissioning M. Schulte, University.
LIU-PSB Configuration Management EDMS Documentation, Layout and ECRs Thomas Birtwistle EN-MEF-DC.
Management’s preliminary comments to the ERC Report FINANCE COMMITTEE June 19, 2002.
Hardware Commissioning  Preparation Documentation MTF Programme  Status The Review The commissioning activity in Resources  Outlook The new.
State of Georgia Release Management Training
19/11/2015 PSB and PS&TT2 Facilities YETS L. Kobzeva.
Equipment Management Folder / MTF Travellers. Product Data Management A huge amount of product and engineering data stored in CERN databases – Design.
EDMS for EGEE-IIEDMS No: ver 1 David Widegren, CERN, TS/CSE Using the CERN EDMS in the EGEE-II project.
Project Breakdown Structure Tracing changes to our different baselines I. Bejar Alonso and Project Office TCC – 14 th January 2016.
Review of the processes released in the framework of the MMP Goran Perinić.
Final Report – Injector Re- Commissioning Working Group (IRWG) Working group to find strategy for more efficient start-up of injectors and associated facilities.
ELENA Documentation and Data Management Items, Assets, Functional Positions T. Birtwistle EN-ACE-CL With input from T. Krastev EN-ACE-EDM.
Database - How to keep BI information up to date? Samy Chemli on behalf of EN-MEF-DC.
Proposal: Use of ECRs for “Controls” Changes and Renovations Rende Steerenberg, Samy Chemli, Marine Gourber-Pace, Klaus Hanke, Verena Kain, Bettina Mikulec,
Quality Assurance for LHC Gas Systems Stefan Haider / EP-TA1.
Building Preservation Environments with Data Grid Technology Reagan W. Moore Presenter: Praveen Namburi.
Product Lifecycle Management with the CERN EDMS David Widegren CERN, TS/CSE 8 Nov 2005EDMS:
Cold mass procurement, status and plan, QA-QC H. Prin With contribution from S. Becle, O. Housiaux, R. Principe, J.-L. Rudeiros Fernandez, F. Savary 3.
Project Codes/Coding Pierre Bonnal Project Codes/Coding — P. Bonnal2 Three to tango Agenda “as-is” “should-be” “to-be”
11T Quality Assurance O. Housiaux, R. Berthet, S. Menu, R. Principe 3rd International Review on the 11T dipoles at collimator Section for the HL-LHC 6-8.
LIU Configuration Management EDMS Documentation, Layout and ECRs This presentation follows the LIU-PSB specific presentation done on 9 th October 2014.
Software Configuration Management
Software Project Configuration Management
Document Plan & Milestones WP7
Configuration Management and Layout Database ELENA Project
Configuration Management and Prince2
Unifying for all accelerators and projects
EDMS, CDD, Catia, smarteam.
Layout Drawings and Mechanical Assembly Drawings
Upgrade Strategy for the Experimental Vacuum Systems
Chapter 11: Software Configuration Management
E. Manola-Poggioli 05 December 2001 EDMS doc
Case management as logbook for the cryogenic installations at CERN
HL-LHC Quality management
ECR on pole order of the HL-LHC IT circuit and resulting implications
Presentation transcript:

Samy Chemli –

Configuration Management - S. Chemli EN-MEF – Contents Configuration Management Hardware Baseline Change Management of the baseline Naming Layout Database Change Management of the layout database Summary

Configuration Management - S. Chemli EN-MEF – Configuration Management Provides a clear and coherent picture of the status of a project or machine at a given point in time. In order to achieve this, we use three important tools making up the framework Changes to the machines and transfer lines are documented, circulated and approved in the Hardware Baseline (also known as a Product Breakdown Structure) using EDMS We register the layouts of the accelerators and all changes to them within the Layout Database that has to remain up-to-date. Sequence of functional positions = space management Integration and Installation Drawings match the recorded layout to ensure that envelopes of reserved space still match the physical equipment dimensions Naming is critical throughout the lifecycle of the machines/projects. To store and manage naming, we use the Naming Portal

Configuration Management - S. Chemli EN-MEF – Hardware Baseline… …is an EDMS (Engineering Document Management System) based tool. It contains all the information needed to (re-)build the machine, including: Eng. Specifications, Conceptual Specifications, Functional Specifications, Engineering/Technical Notes, Manufacturing Procedures, Test Procedures, Hardware Commissioning Procedures, Market Survey, Invitation to Tender, Engineering Change Requests… Logical structure of nodes, based on hardware types and functions Determine an associated name for each node (equipment, function, layout, service…) Centrally managed by the configuration management write access is restricted read access is granted to project members Question: how to handle a project baseline within a hardware baseline

Configuration Management - S. Chemli EN-MEF – Integrated Baseline In order to answer this question, each node of the baseline tree impacted by the upgrade has been divided into  A node containing the current machine data simply prefixed with ‘Current Machine’ tag  A new node to handle the upgrade documentation and that has been prefixed with a ‘HL’ tag  NB: When possible, this splitting has been done at the lowest possible level  ‘Inner Triplet Assemblies’ and ‘Inner Triplet Quadrupole Assemblies’ remained untouched.

Configuration Management - S. Chemli EN-MEF – Dedicated View Point Nodes of the LHC Baseline dedicated to HL have been grouped into a dedicated tree structure The structure is linked into the main project structure Tree nodes are the one of the hardware baseline… …then document are the ones of the baseline

Configuration Management - S. Chemli EN-MEF – Merging with the operated machine At installation time, the idea is to gather the split nodes and documents back into a single point. Few variants: When the ‘current’ node is no longer needed (e.g. Warm D1 Magnets documentation). The node will be prefixed with ‘former’ and the documents will simply be turned obsolete. When the ‘current’ node is still needed (e.g. current triplet still in use for IR2 and IR8). The description will be modified to get a better match…

Configuration Management - S. Chemli EN-MEF – Change Management of the baseline Now that a baseline has been established, handling changes is done through 2 processes Using Space Reservation Documents – mainly when an Eng. Specification has not been written yet Using Engineering Change Requests (ECRs) in all other cases What for: Inform other stakeholders and get their approval/refusal/comments Impact analysis and space analysis Allow all persons concerned the opportunity to comment about the impact of changes on surrounding equipment or general planning.

Configuration Management - S. Chemli EN-MEF – Where: in the HW baseline for long-term traceability Identify the adequate node in the structure All changes concerning given equipment recorded in the same place in the HW Baseline When: prior to the change taking place Resulting actions: update the HW Baseline (Engineering Specifications, Drawings…) and the Layout Database. Machine/Project Equipment code/category Document type. For example: ES = Engineering Specification, EC = Engineering Change request, TP = Test Procedure etc. Change Management of the baseline

Configuration Management - S. Chemli EN-MEF – Naming Baseline nodes and their related documents are associated with names Names are defined according to Naming Conventions The Quality Assurance Committee – mandated by the Accelerator and Technology Sector – has an action in 2014 to provide an update plan for the general naming conventions, including LHC and HL-LHC For LHC, the LHC-QAP (Plan) is still in use, with caution

Configuration Management - S. Chemli EN-MEF – Naming Baseline nodes and their related documents are associated with names On a practical base, we use the naming portal for accelerators entities and signals For the configuration management, this is the source for all codes in EDMS, CDD, InforEAM/MTF and Layout

Configuration Management - S. Chemli EN-MEF – Naming Accelerator / Project Code Will remain LHC Only equipment code (excludes the variant) 12 char Engineering Drawing Number Baseline nodes and their related documents are associated with names On a practical base, we use the naming portal for accelerators entities and signals For the configuration management, this is the source for all codes in EDMS, CDD, InforEAM/MTF and Layout

Configuration Management - S. Chemli EN-MEF – Naming Accelerator / Project Code Will remain LHC Only equipment code (excludes the variant) 12 char Engineering Drawing Number Additional Title block for external drawings Baseline nodes and their related documents are associated with names On a practical base, we use the naming portal for accelerators entities and signals For the configuration management, this is the source for all codes in EDMS, CDD, InforEAM/MTF and Layout

Configuration Management - S. Chemli EN-MEF – Naming 19 char Physical Equipment – Asset - Number Variants handling Machine Code Will remain HC Baseline nodes and their related documents are associated with names On a practical base, we use the naming portal for accelerators entities and signals For the configuration management, this is the source for all codes in EDMS, CDD, InforEAM/MTF and Layout

Configuration Management - S. Chemli EN-MEF – The Naming Portal The Naming Portal handles the names for the CERN accelerators Service is ensured by BE-CO and EN-MEF URL - CERN-Intranet restricted – Please use Remote Desktop to access Mail :

Configuration Management - S. Chemli EN-MEF – The Naming Portal

Configuration Management - S. Chemli EN-MEF – The Naming Portal

Configuration Management - S. Chemli EN-MEF – Layout Database Stores the sequence (layout) of accelerator and transfer line components. Equipment types and details Functional positions for mechanical and electrical layouts Asset names – functional position is exported to MTF database and associated to an asset. Layout just shows the result. Expert name – optional, alternative functional name Updated as a result of ECRs - all past layout information is kept for traceability purposes (database is versioned – see next slides) Functional positions become ‘expired’, not deleted Accessible to all CERN users (CERN IP address) Access: cern.ch/layout or Single sign on under discussion/implementation From outside, Remote Desktop mandatory for the moment

Configuration Management - S. Chemli EN-MEF – Layout Database Navigator with regions and functional position names – distance ordered Pictures from the tunnel Installation Drawing Link

Configuration Management - S. Chemli EN-MEF – Layout Database Latest but not released installation drawing Integration of 360 pictures (on-going)

Configuration Management - S. Chemli EN-MEF – In order to allow parallel evolution of the HL project and the operated machine, the two layouts will be recorded in separate machine representations within the layout database. Modifications to the layout of the machines (using Space Reservations and ECRs) are buffered and grouped into dated versions in the Layout Database. Release notes summarise the modifications between dated versions done to the layout/optics inside the database (see example next slides for the operated machine) This includes mechanical and conceptual layout drawings LHCLSX, LHCLSXG, LHCLSA, LHCLSS for the operated machine LHCLSXH and LHCLSGH for the HL-LHC project And the electrical circuits definition drawings LHCLSD drawing (possibly LHCLSDH) These dated versions are triggered by: Technical Stops (few days), Extended/Winter Technical Stops (2-3 months), Long Shutdowns (e.g. LS1) for the operated machine Technical Coordination and/or Parameters and Layout Committee for the HL project Change Management of the layout

Configuration Management - S. Chemli EN-MEF – Change Management of the layout

Configuration Management - S. Chemli EN-MEF – Change Management of the layout

Configuration Management - S. Chemli EN-MEF – Change Management of the layout

Configuration Management - S. Chemli EN-MEF – Summary The purpose of the Configuration Management is to provide a clear picture of the HL-LHC project and the operated machine at a given point in time. It is achieved through : The usage of a single Hardware Baseline: Centrally managed by the configuration management Separated at the lowest possible level To be reconciled at the end of the project Change Management of the baseline: Engineering Change Requests and Space Reservation Stored in Hardware Baseline not in individual EDMS structures Naming: Important at all stages of the project/machine lifecycle Available on the Naming portal Includes drawing and equipment/assets naming Layout Database: Stores the sequence (layout) of components, including electrical components and circuits. Separate HL and Operated machines Change Management of the layout database: Versioning of the machine and project versions and Release Notes issuing

Configuration Management - S. Chemli EN-MEF – Summary Further information: Naming Service: Naming Portal: Layout Service: Layout Web Interface: EDMS: Configuration and Change Management of the Accelerators Baselines: ecr-