Samy Chemli – 2014-06-11
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 – 2014-06-11
2
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 – 2014-06-11
3
Hardware Baseline…
•
…is an EDMS (Engineering Document
Management System) based tool.
•
It contains all the information needed to (re-)build
the machine, including:
•
•
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
•
•
•
Eng. Specifications, Conceptual Specifications,
Functional Specifications, Engineering/Technical Notes,
Manufacturing Procedures, Test Procedures, Hardware
Commissioning Procedures, Market Survey, Invitation to
Tender, Engineering Change Requests…
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 – 2014-06-11
4
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 – 2014-06-11
5
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 – 2014-06-11
6
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 – 2014-06-11
7
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 – 2014-06-11
8
Change Management of the baseline
•
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
Machine/Project
Equipment code/category
Document type. For example: ES = Engineering
Specification, EC = Engineering Change request,
TP = Test Procedure etc.
•
•
When: prior to the change taking place
Resulting actions: update the HW Baseline (Engineering
Specifications, Drawings…) and the Layout Database.
Configuration Management - S. Chemli EN-MEF – 2014-06-11
9
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 – 2014-06-11
10
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 – 2014-06-11
11
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
Accelerator / Project Code
Will remain LHC
12 char
Engineering Drawing Number
Only equipment code
(excludes the variant)
Configuration Management - S. Chemli EN-MEF – 2014-06-11
12
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
Accelerator / Project Code
Will remain LHC
12 char
Engineering Drawing Number
Only equipment code
(excludes the variant)
Additional Title block for external
drawings
Configuration Management - S. Chemli EN-MEF – 2014-06-11
13
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
Machine Code
Will remain HC
Variants handling
19 char
Physical Equipment – Asset - Number
Configuration Management - S. Chemli EN-MEF – 2014-06-11
14
The Naming Portal
•
The Naming Portal handles the names for the CERN accelerators
•
•
•
•
Service is ensured by BE-CO and EN-MEF
URL - https://cern.ch/service-acc-naming
CERN-Intranet restricted – Please use Remote Desktop to access
Mail : [email protected]
Configuration Management - S. Chemli EN-MEF – 2014-06-11
15
The Naming Portal
Configuration Management - S. Chemli EN-MEF – 2014-06-11
16
The Naming Portal
Configuration Management - S. Chemli EN-MEF – 2014-06-11
17
Layout
Database
https://layout.web.cern.ch/layout/
•
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 https://layout.web.cern.ch/layout/
• Single sign on under discussion/implementation
• From outside, Remote Desktop mandatory for the moment
Configuration Management - S. Chemli EN-MEF – 2014-06-11
18
Navigator with regions and functional
position names – distance ordered
Layout Database
Installation Drawing Link
Pictures from the tunnel
Configuration Management - S. Chemli EN-MEF – 2014-06-11
19
Layout Database
Latest but not released
installation drawing
Integration of 360 pictures (on-going)
Configuration Management - S. Chemli EN-MEF – 2014-06-11
20
Change Management of the layout
•
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
Configuration Management - S. Chemli EN-MEF – 2014-06-11
21
Change Management of the layout
Configuration Management - S. Chemli EN-MEF – 2014-06-11
22
Change Management of the layout
Configuration Management - S. Chemli EN-MEF – 2014-06-11
23
Change Management of the layout
Configuration Management - S. Chemli EN-MEF – 2014-06-11
24
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 – 2014-06-11
25
Summary
•
Further information:
•
•
•
•
•
•
Naming Service: [email protected]
Naming Portal: https://cern.ch/service-acc-naming
Layout Service: [email protected]
Layout Web Interface: https://layout.web.cern.ch/layout/
EDMS: https://edms.cern.ch
Configuration and Change Management of the Accelerators Baselines: [email protected]
Configuration Management - S. Chemli EN-MEF – 2014-06-11
26