1. GUCS News M.Timmins12 th CATIA forum20/09/2012

2. - GUCS reminder - News from the SMT workshop - 29 th – 30 th of August Outline

3. GUCS reminder Local correspondents: map can be found on the GUCS website: herehere Their role: -Participate in monthly meetings -Vehicle information upstream and downstream -Be in close contact with GUCS members -Fill-in knowledge base -Give first line support

4. GUCS reminder Please send e-mail requests (catia-support@cern.ch) when you want:catia-support@cern.ch 1 - help, 2 - report bugs 3 - Improvement requests

5. News from the SMT workshop - 29 th – 30 th of August  Why did EN/MME organise a SMT workshop ? To find solutions to the difficulties we have in using and managing our data in Smarteam.  With who ? External: Dassault Israel Helbling  Objective ? See next slide (F. Bertinelli) Internal: Working group members (GUCS – PLMWG) EN/MME management CAD support CAEC IT representatives EN/MME and PH Key users

6. F. Bertinelli 6 Objectives and questions  present and discuss CERN user environment, needs and challenges on SmarTeam data management;  critically evaluate these needs wrt Industry best practice;  consider short, medium and long – term views, future of Catia/Smarteam;  can SmarTeam (DS) Israel contribute and how? what costs? What framework? Current and possible role of Helbling?  How to improve SmarTeam support to CERN from Dassault? How to increase on-site SmarTeam support presence, at least in an initial period?  Next steps? (results-oriented or resource-based approaches?) ……

7. Conclusions → After the 2 days workshop we agreed both CERN and Helbling/Dassault Israel to work together unless their commercial proposal is above our means. Technical matters: → continue for the moment with existing SmarTeam and evolve our configuration: no dramatic changes of version or software recommended (specifically w.r.t. to ENOVIA v6, PSI practices, or for more standard configurations…). This is important and reassuring for CERN, in the short-term. This statement can be modified if coincident with EDMS change, in the long-term. →Original problem: CERN lives with two PLMs (EDMS and SmarTeam):  Focus on only one (now or later?), or …  Solidly synchronise them (for the moment …) → Recommend more emphasis on “item” as opposed to “document” → Recommend to implement short-term actions even when below 100% optimal, and then progress in time (at CERN we risk being too perfectionist, e.g. PLM approach) → Next steps…:

8. Next steps: We are waiting for a commercial proposal from Helbling and Dassault Israel for solving 7 points identified during our discussions.

9. 1.Check-in policy (overwrite previous) Always overwrite is OK, but its urgent to synchronise our 2 systems. 2.Presentation of data, User Interface Move information to the item Use color codes for better understanding 3.Project structure (folder) No need to go to folders rather than projects (no added value) Improve the add to project interface when saving a new document. 4.Error messages Investigate message which are useless and switch them off. 5.BOM management (views, versioning) First better understanding of our used cases, develop a tool able to manage different BOM views for a same item. 6.Access to SmarTeam data for casual CERN (or external) users The SmarTeam web interface is too complex for casual users, also DS Israel have developed their own read only web interface (SmartView). Can it be compared with CDN?” 7.Data exchange with external users Does the data exchange tool developed at CERN full-fill our needs. To be evaluated along with other solutions. 7 points

10. Summary of the 7 points discussed as priorities during the Smarteam workshop held on the 29-30 of August 2012 Present during this discussion: Blaise Metz (Helbling); Michael List (Helbling); Hagai Shiloni (Dassault Israel); Sagi Zelts (Dassault Israel); Diego Perini (CERN); Per-olof Friman (CERN); Robin Betemps (CERN); Stephane Bally (CERN); Marc Timmins (CERN) DescriptionProposalFuture actions 1 Check-in policy (overwrite previous) Following a discussion on our check-in policy (overwrite previous) Dassault Israel advised us to reach a release state in SMT synchronised with the release state in edms. This can be made simple and less time consuming by not investing time in changing our existing approval process. The user will no longer be faced with the risk of releasing a 2d drawing linked to a non up to date 3D document. Our configuration should no longer be a limitation if we consider the proposal. In order to reach results within a few months, a fast and simple solution must be found to release documents in SMT synchronised with release in edms. Possible solution: The CDD release process started following a " freezed state" or the "released state" in smarteam initiated by the user on the 2d and 3d data. Once the CDD process is finished an attribute in SMT can automatically be switched to reflect the CDD state. It was also mentioned that this could be done on the item. Organise a workshop to come to a final spec for developpement. A solution must also be found for existing data. 2 Presentation of data, User Interface How can the Smartem interface regarding data spread over the item, documents and projects could be changed in order to make it more clear for the users on what belongs to what and where can it be updated. Try and move most information to the item. Very little data should be on the documents (only description) Add color codes to different objects to make reading more simple. Expect proposal 3 Project structure (folder) Would the use of folders help us in organising our data in the Smarteam and make the navigation easier. The anser is no, however a redesign of the attachement process to the project could be carried out upon save. Access to last projects, or mostly used projects, etc… Expect proposal 4 Error messages Too many error message appearing in SMT. Users are confused and don't read them. Some are more important than others. Track the messages and identify those which can be removed. Ask a couple of users to track useless messages and make a request to have them removed. 5 BOM management (views, versioning) a. How could we have several views of the same item (functional and manufacturing process as an example) ? b. How can we manage item versions ? a. Smarteam provides standard tools for such application, but Helbling suggests that it would be more interesting for CERN to adapt it to its BOM compare tool which is well done according to Helbling. B. Items and there versionning are essential, and in that way it should be considered when investigating point 1 but might be done in a 2nd phase. a. A better understanding of the use cases are requested by Dassault Israel and Helbling. This can be done during a dedicated workshop. b. To be considered during the workshop planned for point 1. Could lead to 2 proposals ( short terme and long term) 6 Access to SmarTeam data for casual CERN (or external) users Dassault Israel made a Demo of Smartview, which enables users to search, view, and download data from Smarteam via a web interface based on or not a login. It can also be used to extract links. No specific proposal was made. An existing tool at CERN called CDN is very similar to Smart view. Further internal discussions and feedback on our tool should be carried out before considering a new tool. 7 Data exchange with external users Discussions on various options for external users to access CERNs Smarteam data such as remote desktop access without having to extract and reintegrate data in the way CERNs home made tool was done. No specific proposal was made. Seen that there are high expectations on this subject a dedicated workshop should be carried out. 7 points in more details

11. For when ? In 2 years ? NO No longer acceptable. We want to achieve the first results within a few months (3-4). All comments are welcome. Now or later Thank you for your attention !!