Siemens NX CAD vs Teamcenter

• Seamless interaction across multiple departments.
• The software allows you to create a very high level of control and organization within your engineering staff. This reduces the companies mistakes and maximizes productivity.
• The software makes it very easy to track your product through every phase of the production cycle.

Read full review

• You can search any documents by its name and number.
• You can see who is owner of the documents and who edited it last.
• You can upload any form of documents like Word, pdf or drawing files in our case which is Solid Edge files.
• For some confidential documents you can also restrict vies to only selected persons.
• It is useful for creating and accessing BOM and other particulars.

Read full review

• Speaking from experience with NX, each revision seems to be focused more on the layout of icons as compared to the functionality of the features.
• Features within NX that have been used for years are no longer being used as a result of new revisions. Doesn't make a lot of sense to the end user. It would be nice to know what the reason is on a much larger scale (ie large customer recommendation?)

Read full review

• Teamcenter is highly buggy, and most bugs are very time consuming to live with. Many bugs have existed for a long time and Siemens has yet to fix them. Examples are extremely slow response for the Windows Explorer plug-in used for adding datasets for document items, views in the viewer getting "stuck" and won't clear even after a full window refresh - solution currently is to close the viewer and reopen it, or sometimes close & reopen Teamcenter; functions that fail one way but work another, such as Teamcenter will freeze up when selecting "save and check in" after an item data edit, but will work fine if the user saves and then does a "right click - check in." Many more examples exist too numerous to list here.
• Teamcenter is too complex and non-intuitive. This causes a need for a lot of training, and refresh training. Occasional users really struggle because of this, and require a lot of hand-holding by support or admin folks.
• Also highly unstable, particularly the Java portion, at the Client level. We get a lot of Java errors or Java related errors (some users almost daily - no exaggeration). Java never closes on its own after a user closes Teamcenter, which is normally not a problem unless Teamcenter inadvertently creates a second instance of Java, or otherwise crashes. Also, sometimes apparently related, the various cache folders on the Client machine get corrupt and require the user to clean them out after closing Teamcenter (unless it had already crashed) and restart Teamcenter - this every week or two per user, depending on usage. This all seems to be worse with Windows 10, so perhaps there's a Teamcenter - Java - Windows 10 compatibility issue.
• Because of the issues mentioned above, Teamcenter requires an inordinate amount of support personnel. We have an entire corporate department dedicated to supporting Teamcenter, and local users who serve as local admins and support.
• Teamcenter is a very expensive to use, because of the issues expressed here. Many, many man-hours per year are spent supporting this tool, and many, many more man-hours are spent just on dealing with delays due to bugs and inefficiencies.

Read full review

• Do not knowtotal investment cost, but there have been several projects where Siemens PLM software has both produced a better product and maximized production.
• NX CAM has saved our machining centers thousands of hours and allows direct contact between the designers and the machine programmers.

Read full review

• Decreased time to process ECNs with electronic workflow and notifications
• Ability to track status of ECNs has given us a better overview of the health of our process and resource constraints
• Version control for released items going through revision has reduced risk of manufacturing the wrong revision

Read full review