Database - How to keep BI information up to date? Samy Chemli on behalf of EN-MEF-DC

Contents Updating the layoutDB Keeping the layoutDB updated Updating Assets FP, Items and Assets Updating the PBS Conclusions S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Updating the layoutDB - machines For the installed/operational accelerator lines, the base is the work done by Javier Simón. To our knowledge, the BLM layout was out of his scope LHC Arcs and DS are ok, Injection regions to come, all other lines to be checked… Updating the accelerator lines described in the layoutDB Dealing only with mechanical and optics layout. It excludes electronics devices, usually handled by BE-CO. Correcting errors for the currently defined accelerator lines. LHC, clarification on supports for instance Catching up with the definition for the absent accelerator lines on a best effort basis Requires a better approach for signal naming within the MAD/X sequence file (today usage of sub-slots) Find a solution at the database implementation level with BE-CO S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Updating the layoutDB - projects Some projects data are already stored in the layoutDB. Elena, Linac4, HIE-Isolde are ok. But for some others, we’re not yet ready to handle functional positions in the database Lines are not yet defined (e.g. Awake) Only some functional specifications have been written and positions are not yet entirely defined (HL, LIU?) Sometimes, changes are only inscribed in different versions of layout drawings S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Keeping the layoutDB updated The tool to trace functional position (and Form/Fit/Function in general) changes is the ECR It handles the impact analysis and the consequences for the neighbours. Impact is not always a matter of space management (impact on beam, impedance,…) Most of the time it also ensures a proper 3D integration It works for projects and installed accelerator lines S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Updating Assets Usually MEF-DC does not interfere with the asset management. The layoutDB simply displays the asset information for a given functional position BE/BI with InforEAM Service Changing the asset type/variant might sometimes have an impact on the functional position naming. OB – Asset type (item) : entirely independent Eq-Code – Asset type (item) : 100% related Functional type – Asset type (item) : most of the time independent (as long as the function does not change) See next slide for the global picture S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

FP, Items and Assets ITEMS (virtual) ASSETS (physical) Adapted from the GCO meeting # S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Updating the PBS MEF-DC to transfer all the long-term archiving documents stored in your EDMS structure to the adequate Hardware Baseline (PBS) with correct referencing (naming) Recovery action on documents. Will be done with BI MEF-DC to create the corresponding items within the PBS (from the EDMS catalogue) This allows the correct referencing of the CDD drawing folders and all the other types of long-term archiving documents. Document transfer and item creation also applies to projects S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico

Conclusions S. Chemli - 2nd BI Beamline Operational Spares Strategy Workshop - indico Keeping information up-to-date in a database is a long- term partnership on editing/identifying/verifying/releasing data and documents Some effort to be done by MEF-DC On updating functional positions Moving the documentation to the PBS Creating the items for joining MTF-Items-CDD Some effort to be done by BE-BI On identifying the documents to move to the PBS On making sure the changes are documented in ECRs On defining a link person for the layout long-term follow-up. The GCO is already a great help