Services Connection Europe 2011

1. Services ConnectionEurope 2011 May 23-26, Madrid I-deas Migration to NX CAE Marouf Dwaikat EMEA Center of Excellence

2. Agenda • Introduction • CAE Data Manual Migration Paths • CMM-Native for CAE • Browser • Configuration Options • Supported Entities • Demo • I-deas to NX CAE Transition Challenges and Issues • Current Situation • Best practices

3. Introduction • Objectives • Provide the best and most effective transition for I-deas CAE customers • Facilitate phased implementations via the “paired release” approach between NX and I-deas • Move all I-deas CAE customers successfully to NX

4. CAE Data Manual Migration Paths • Methods • I-deas universal file • Limited support for data sets • No support for loads and boundary conditions • Results supported • Nastran/ANSYS/Abaqus Bulk Data file • FE Geometry and loads and boundary conditions • Solution set-up Neither method can migrate associated geometry

5. CMM • CMM = Content Migration Manager • Process used to migrate I-deas NX CAD data to NX • Run from Teamcenter Engineering • Maintains as much design intent as possible • Maintains data managed control over migrated parts • Does not process I-deas CAE data checked into TDM • CAE data not available for migration in Teamcenter

6. CMM-Native for CAE • Content Migration Manager – Native • Launched from NX • UGII_MIG_USE_FEM_NATIVE=1 • Migrates CAE data (and parent geometry if desired) from I-deas model file to native NX files (.prt/.fem/.sim/etc.) • Associative mesh and recipe • Size, material, physical • Note: not associative if section based • Associative Boundary Conditions

7. I-deas CAE CMM-Native Migration • Migration has 4 components: • CAD geometry • NX Nastran bulk data • XML to describe associativities • Universal file containing analysis results • Export from I-deas breaks data into these components, then reassembles them on import to NX • Resulting data is saved outside of TCE (native) • Partitioning is resolved in the .fem part using polygon geometry

8. I-deas CAE CMM-Native Migration Ideas Suptab gateway Model Solution NX NX Nastran Environment CMM Communication XPK– B-Rep (features optional) FE Data (Nastran deck) Nodes, elements materials, physical properties beam cross sections Mapping Geometry association table Node to geo map Elem to geo map Geometry based LBC Mesh recipe (element size, PID, MID) Results stored in model file (model solution or any imported results) unv

9. Content Migration Manager – Native Specify model file to migrate from Opens browser window (similar to Manage Bins) to select FE model(s) On: The associated CAD parts will migrate along with the FE models. The node and element associations and mesh recipes will be migrated as well Off: Only the FE data will migrate Selected FE model(s), parts and their status appear Summary region, updated as migration progresses Configuration Options, Start Migration

10. CMM-Native – I-deas Browser Select FE model(s) to migrate Very similar to the I-deas Manage Bins form

11. CMM-Native – Configuration Options Set units for resulting NX files Toggle off to keep NX parts open after migration Set location for resulting NX files Set location for Migration Report files Set location for temporary files

12. CMM-Native – Configuration Options Toggle off to suppress history migration (geometry only) Always import B-Rep or only On feature migration failure Set destination color and layer for reference geometry Set destination color and layer for wireframe geometry Note: If parts are being migrated that won’t need to be modified, you can improve the reliability and performance of the migration process and create smaller files by migrating the boundary representation, but not the feature history (recommended).

13. CMM-Native – Configuration Options • Set to directory containing ideas_paramxx.dat in the CMMinstallation, otherwise… • Typically ...\ideasgateway\cmm • (C:\UGS\CMM\IDEASGateway\cmm) • NOTE: This is NOT the location of the param file for any existing I-deas TDM installation

14. Supported Entities

15. Supported Entities

16. Supported Entities

17. I-deas CAE Library or .unv file data • The CMM-Native process reads I-deas CAE data from a model file only • If users have FE data checked into a library, they need to check it out into a model file and save before running CMM-Native • If users have data stored in archive or universal files, these will need to be read into a model file and saved before running CMM-Native

18. ANSYS/Abaqus Users • The CMM-Native process uses an NX Nastran bulk data file • If ANSYS or Abaqus solutions are set up in I-deas, the solver specific data will not be migrated • Physical properties • Data defined in export forms • Etc. • The user has the option of exporting an ANSYS or Abaqus deck from I-deas and importing it into NX. • This process does not use the CMM tools • Will not transfer geometry • Up to the user to weigh the tradeoff between maintaining geometry/associativity vs. migrating analysis specific settings.

19. Notes • CMM does NOT require an existing I-deas installation • CMM-Native install contains a “headless” version of I-deas • CMM-Native works off a model file – no TDM required • Only NX and CMM-Native need to be installed • CMM can open any I-deas Master Series model file • Does not have to be NXI6 • Recommendation is that part data be updated and saved in I-deas Master Series 8 or later • The latest versions should be used to ensure the most robust translation • CMM-Native v7.5.3 (available since April 29) • NX 7.5.3 The CMM installer will install everything, including start menu items for Teamcenter CAD CMM.

20. CMM-Native for CAE – Demo

21. CMM-Native for CAE – How to get it • CMM-Native for CAE is on CMM media that can be downloaded from GTAC (http://ftp.ugs.com/) • You MUST walk the customer through the process prior to delivery/download so that they understand the process/capabilities/limitations. Support page: • http://cipgweb/dss/PSQ_web_site/psq_cmm/psq_cmm_index.html • Documentation • Known Issues • FAQ’s

22. Challenges and Issues • Software functionality • Issues with I-deas customers who deal with legacy CAE data or who work with imported meshes (i.e. with no geometry) – manual meshing regression! • Post-processing capabilities • Resistance to change • Old customers using I-deas for many years with strong habits • Hard to make them move on to a new GUI… • Some customers want to use NX exactly as they use I-deas! • Budget • Migration from I-deas to NX is free of charge for customers with current maintenance, but… • some customers don’t understand why they have to pay for training + services to migrate.

23. Current Situation .

24. Current Situation • Many customers have migrated already. Others are in the process of migrating, or expected to migrate soon. • Customer migrated after being provided CMM and an Initial Audit process. • Audit/Demonstrations followed by training, pilot, implementation, other services. • Some customers moved to NX without migrating CAE data. • Keep the I-deas server “alive” in case they need to access old data.

25. Best Practices • CMM should be used/recommended to customers with caution. • Do not voluntarily mention or steer customer to CMM (best to keep it in your back pocket and use only if customer asks about migration) • Best process would be to finish existing projects in I-deas and start new programs in NX (i.e. no migration of CAE data at all) - This is the recommended path for most users. • Priority to be given to I-deas customers with “CAD oriented” CAE process (working closely with geometry) • Easier to demonstrate benefits of NX over I-deas. • Explain differences of NX CAE approach over I-deas.

26. Best Practices • Know what the customer is doing, get him to engage as soon as possible, and push to migrate at the “right time”. • Continue making customers aware of the “migration to the next generation” of Siemens CAE product portfolio. • Encourage customers to get to the latest version that allow dual licensing. • Try to identify what are the show-stoppers and get that addressed ASAP by feeding straight back into development and follow up with the customer to show that NX is progressing.

27. Best Practices • Migrate I-deas customers to NX through customer-funded services projects • Get customers to migrate to NX and get paid for helping them do so • Formal migration plan (I2N), with seminars for customers • Get customers to migrate to NX, and upsell in the process • NX intro seminar for I-deas users (1 day update sessions) • Make I-deas customers aware of NX and enable the I-deas users to start using NX • Sales program started for I-deas migrations • Prevent losing them to the competition Great help form GTAC and maintenance teams (passing right messages)

28. Thank you!