110 likes | 248 Views
GUCS News. M.Timmins 12 th CATIA forum 20/09/2012. Outline. - GUCS reminder - News from the SMT workshop - 29 th – 30 th of August. GUCS reminder. Local correspondents: map can be found on the GUCS website: here. Their role: Participate in monthly meetings
E N D
GUCS News M.Timmins 12th CATIA forum 20/09/2012
Outline - GUCS reminder - News from the SMT workshop - 29th – 30th of August
GUCS reminder Local correspondents: map can be found on the GUCS website: here • 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
GUCS reminder Please send e-mail requests (catia-support@cern.ch) when you want: 1 - help, 2 - report bugs 3 - Improvement requests
News from the SMT workshop - 29th – 30th 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 • Internal: • Working group members (GUCS – PLMWG) • EN/MME management • CAD support • CAEC • IT representatives • EN/MME and PH Key users • Objective ? • See next slide (F. Bertinelli)
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?) • …
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…:
Next steps: We are waiting for a commercial proposal from Helbling and Dassault Israel for solving 7 points identified during our discussions.
7 points • Check-in policy (overwrite previous) • Always overwrite is OK, but its urgent to synchronise our 2 systems. • Presentation of data, User Interface • Move information to the item • Use color codes for better understanding • 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. • Error messages • Investigate message which are useless and switch them off. • BOM management (views, versioning) • First better understanding of our used cases, develop a tool able to manage different BOM views for a same item. • 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?” • Data exchange with external users • Does the data exchange tool developed at CERN full-fill our needs. To be evaluated along with other solutions.
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 !!