1. Design Office meeting 25.06.2013 Design office meeting

2. 1. Reminder of main rules of data organization in SmarTeam for ATLAS project Work in USER project Organization of ATLAS Project structure Simplified 3D models 3D model Positioning Atlas coordinate systems Collaborative work with E-group Teams ATLAS DGS (Design Graphic Skeleton ) 2. Requirements for the models to be linked to the official Atlas SmarTeam structure CATDUA V5 AUTOMATION Q-checker 3. ATLAS photos Work organization with SmarTeam CAD data in Atlas Design Office

3. 1. All preliminary studies should be done in USER project. It is important to create folders with clear names for every task. 2. After initial approval and check with environment the documents should be linked to corresponding folders in ATLAS Project structure: - Top assembly Items should appear in the left tree - Important 3D sub-assemblies or parts appear in the list of Documents on the right side - Drawings can also be linked to the list of documents or put in a separate folder 3. Simplified 3D models – same Item as corresponding detailed model where a new model is created. In case of existing simplified models every case is decided individually. 4. For 3D models positioned in Atlas coordinates it is obligatory to identify in the profile card which coordinate system you have used. If the model is not positioned make the choice of “ defined by the user” 5. Resp. State: KEEP or Always Overwrite – should be decided if we want to keep existing version or not every time doing Responsibility Transfer from one person to another 1. Main guidelines for the CAD data SmarTeam organization in Atlas Design Office

4. 2. After initial approval and check with environment the documents should be linked to corresponding folders in ATLAS Project structure: - Top assembly Items should appear in the left tree - Important 3D sub-assemblies or parts appear in the list of Documents in right side - Drawings can also be linked to the list of documents or put in a separate folder Organization in Atlas project tree - Drawings can also be linked to the list of documents or put in a separate folder

5. 3.Simplified 3D models – same Item as corresponding detailed model where a new model is created. In case of existing simplified models every case is decided individually. Simplified models

6. Simplified 3D models should be attached to the same Item as corresponding detailed model with extension _02. Example of Barrel Toroid Warm Structure: Simplified models

7. Coordinate system The main CAD coordinate system is named 1101 in Catia application and defined as follows: The origin is the interaction point The X- axis is horizontal and points from the interaction point towards the centre of the LHC ring (US side of the ATLAS cavern) The Y-axis is aligned with the mean local beam direction. The Y-axis is positive towards C side of the ATLAS cavern and inclined by 0,708 degree with respect to the local horizontal The Z- axis is perpendiculas to the X- axis and to the mean local beam direction, and points upwards. It is inclined by 0,708 degree with respect to the local vertical Other coordinate systems are used mainly by specialized groups: 1102 - for civil engineering models ( X- axis the same as 1101, Y-axis horozontal pointing to side C, Z-axis vertical pointing upwards) 1104 - used by cryogenic, cooling and ventillation groups ( axis are the same as 1102, but origin is in the surface building 81211mm higher than interaction point. dX=0, dY=0, dZ=81211)

8. 4. For 3D models positioned in Atlas coordinates it is obligatory to identify in the profile card which coordinate system you have used. If the model is not positioned make the choice of “ defined by the user” Coordinate system Transfer between coordinate systems can be done using the following Macro: Translation (dz 81211) or rotation (0.708 degree) command can also be used

9. Resp. State: KEEP or Always Overwrite – should be decided if we want to keep existing version or not every time doing Responsibility Transfer from one person to another It is recommended to put Always Overwrite and make the version Preliminary only when we want to keep a version for some reason. Otherwise Preliminary version will be created every time when responsibility is passed from one person to another. Several e-group Teams have been created: CAD-Atlas-IBL CAD-Atlas-Muon CAD-Atlas-Integration CAD-ATLAS-Fwd-Platforms … Our experience in working with Teams shows very positive feed back. It is recommended to add the Team systematically where the Teams exist already and extend using of e-group Teams where possible. Collaborative work with E-group Teams

10. 1.Every integration model should be positioned according to one of Atlas coordinate systems (1101 for detector, 1102 for UX15 infrastructure elements, 1104 for surface buildings). Models containing many elements in different parts of Atlas should be split in sub-assemblies by areas (sectors inside Toroid, levels of HS, sides A and C, US and USA…) 2.Assembly that served to build the model should be marked “Help assembly” in ST Profile Card Definition and stay linked to the USER project. 3. All unused geometrical elements should be deleted. 4.Reference planes, constrains and geometrical elements should be hidden. 5.All models linked to Atlas structure should be in Checked-In state. 6.Every created ST document should be linked to one of ATLAS E-group Teams 7. Correction of errors using CATDUA V5 or CATDUA Automation is obligatory. 8. Check of models by Q-checker is strongly recommended. 2. Requirements for the models to be linked to the official Atlas SmarTeam structure

11. ATLAS DGS ( Design Graphic Skeleton )

12. When Catia V5 files are manipulated, errors can appear, leading to troubles (like ghost links). These errors can be accumulated in big assemblies and create problems for example to project into drawing or to save the assembly after modifications. To solve this, the CATDUA (For Catia Data Upward Assistant) exists in the Catia V5 Desk. This tool is powerful, but only treat documents one by one which can be painful for users, when dealing with assemblies. So, in order to facilitate the cleaning of models, CATDUAV5 Automation has been developed by CERN CAD support. It is nevertheless recommended to clean the models by parts or small assemblies because check- out/check-in operations are required for each part to save the cleaning. In big assemblies there can be preliminary elements for which new version will be created making sometimes painful updating assemblies and drawings. CATDUA V5 More details in CERN CAD user page: FAQ CATDUA V5 AUTOMATION CATDUA V5 (Classic)

13. Q-checker There are 32 checks criteria: 14 For Parts 7 For Assemblies 11 for drawings Q-checker is a tool that checks the quality of a CATIA document It will be automatically installed via CMF in all the PCs in the CATIA group Once the tool is installed, In all the CATIA workbenches will appear this icon Information concerning use of Q-checker: EDMS document 1254235 v.1 (https://edms.cern.ch/document/1254235/1 )https://edms.cern.ch/document/1254235/1 Catia FORUM presentation of Marta (in the same EDMS doc.)

14. Atlas photos organisation Two places organised on DFS for storage of photos for different Atlas activities and integration in the UX15 cavern and other buildings. 1. Dedicated for different activities of test assemblies, mock-ups, assemblies of detector parts, etc… The order of sub-folders is chronologic: G:\Experiments\Atlas\MuonSupport\PICTURES\CAMERA 2. Dedicated for the installation and integration of all parts of Atlas detectors and infrastructure in UX15 and other buildings: G:\Experiments\Atlas\MuonSupport\PICTURES\UX15_pictures

15. G:\Experiments\Atlas\MuonSupport\PICTURES\CAMERA: Dedicated for different activities of test assemblies, mock-ups, assemblies of detector parts, etc… The order of sub-folders is chronologic

16. G:\Experiments\Atlas\MuonSupport\PICTURES\UX15_pictures: Dedicated for the installation and integration of all parts of Atlas detectors and infrastructure in UX15 and other Atlas buildings

17. TOROID ZONE and ACCESS STRUCTURE: photos of all parts inside Atlas cavern UX15 Separate folders for : -Big Wheels -Small Wheels -End-Cap Toroids -Services

18. Projects: all photos needed for the realization of defined projects, before and during installation of new elements in any Atlas zones. It is recommended to make photos of the finalized projects and put them into corresponding folder. Shutdowns by years: all operations specific for the current shutdown (examples: pixel extraction, SW extraction, etc…) Only for general view photos. Detailed preparations of tooling and other details can be kept in CAMERA photos.