Teamcenter X

My main use case for Siemens PLM TeamCenter  is for data management. For data management, that tool is the best, but there are many modules and functionalities Siemens provides with it. You can control your organization and access within the tool itself, create a BOM, generate reports, and compare your engineering BOM and manufacturing BOM. Additionally, there is a module called TCRA for reporting and analytics, which allows you to generate reports based on your created database. Furthermore, there is a module called Structure Manager for creating your engineering BOM. In Lifecycle Visualization, which is lightweight 3D, you can visualize how your model looks on your screen. It is very useful software for the mechanical industry, with maximum automobile industries utilizing Siemens PLM software for data management.

In my daily workflow, I use the reporting and Structure Manager modules primarily to manage data created by the engineering team, not necessarily to manage projects. For example, if there is a fastener and I want to see where this fastener is used in a model or assembly, I can use the TCRA report, which helps identify all details regarding where that part is used in assembly and production data. In TCRA, I can also compare my E-BOM and M-BOM. TCRA is a user interface that pulls data from the database that users are creating or maintaining. Structure Manager, as I mentioned, is used to create your BOM, organizing it from the top-level assembly, such as a car, down to the chassis, engine, and other components. Day-to-day operations involve using Structure Manager to create assemblies with subcomponents.

In Siemens PLM TeamCenter , there is a workflow module used in our day-to-day activities, specifically for approvals. We create workflows to define who is going to approve changes. For instance, when I initiate a change management workflow, I can select or predefine within the system who will approve this change. This type of workflow is integral to our daily activities in Siemens PLM TeamCenter.

In Siemens PLM TeamCenter, there are numerous features, but the best ones include organization and ACL , which is the access control list. As an administrator, I can define ACLs for the entire organization, determining who can see, modify, or restrict access to my data; this is a notable feature. Another significant feature is workflow, where I can specify who has the authority to approve changes or designs. Using a data management tool such as Siemens PLM TeamCenter provides a systematic approach to data history, including who created and changed data and when. Key features I mention are ACL , TCRA, Structure Manager, and Workflow Designer.

In day-to-day operations, the ACL feature has a practical impact, especially in environments where multiple teams such as business, IT, and vendors work together in Siemens PLM TeamCenter. From a security standpoint, ACL serves as a first line of defense, ensuring that only authorized individuals can access sensitive data, including BOM, design data, and compliance documents. ACL also allows for action restriction; for example, users may view data but cannot modify or delete it. This control is crucial in regulated environments with export control data, ensuring data integrity and auditability. Additionally, ACL reduces reliance on manual security controls, promoting systematic enforcement rather than reliance on individuals. For collaboration, ACL facilitates smoother workflows, allowing different teams to work on the same platform and see only relevant information. For external partners, tools such as supplier connect allow vendors to access specific controls without exposing core intellectual property. Moreover, temporary access during projects can be easily granted and revoked, which is beneficial as a bridge between business and technical teams.

Siemens PLM TeamCenter offers seamless integration with various CAD  platforms such as Solid Edge, Creo , SolidWorks , CATIA, and NX.

In daily operations, while Siemens PLM TeamCenter is an extremely powerful tool, challenges regarding user experience arise, especially in large, complex programs involving multiple vendors. The user interface can feel heavy and complex for non-PLM expert business users, with too many clicks required for simple tasks, increasing the reliance on training. The system's complex data model and configuration require a deep understanding of dependencies; hence modifications can lead to confusion and frequent access issues, contributing to time lost in troubleshooting rather than productive delivery. Performance issues may arise in large environments, particularly with substantial BOMs or data sets that slow down load times. Integration is also possible but not always seamless; it necessitates specific configurations, leading to data synchronization discrepancies between M-BOM and E-BOM. Migration complexity further complicates the process, as transitioning data between systems often proves challenging. Lastly, while ECR and ECO processes are robust, they may become rigid, leading business teams to bypass the system due to the risks of data inconsistency and the added complexities of customization, which negatively impacts upgrade costs and performance. Improvements in modernizing the user experience, offering more intuitive role-based UIs, enhancing configuration flexibility, and providing plug-and-play integration can greatly enhance usability, thus minimizing operational overhead in larger-scale programs.

I have been working in my current field for 16 to 17 years.

Siemens PLM TeamCenter's scalability is very high, capable of supporting hundreds or even thousands of users globally and proven to handle 10,000 concurrent users in large, complex organizations. Its architecture is multi-layered and SOA-based, allowing for independent scalability of client, application, and database layers. Siemens now offers TeamCenter X, which is cloud-ready and can dynamically scale infrastructure on the cloud. Overall, Siemens PLM TeamCenter is designed for global enterprise deployment and can accommodate large data volumes and multi-site operations, though effective scalability relies on architecture design and infrastructure governance.

Customer support for Siemens PLM TeamCenter is excellent, with a dedicated department called G-TAC, the Global Technical Access Center, available from 9:00 to 5:00. Additionally, premium support is available, which offers engineers on weekends for deployments or upgrades. Recently, there is a concept called Priority Plus, where a dedicated support engineer is assigned to manage all issues from the organization and escalate unresolved issues to the product development team, which enhances support quality.

Before choosing Siemens PLM TeamCenter, I evaluated ENOVIA and 3DEXPERIENCE.

While I cannot disclose specific metrics due to confidentiality, I can share that our implementation of Siemens PLM TeamCenter has engendered significant returns, particularly in time savings. Engineering productivity has notably increased due to faster access to accurate BOM and design data, leading to a 20 to 30 percent reduction in time spent on data retrieval. Change management efficiency has also improved, as automated workflows replacing manual tracking streamline processes and reduce missed communications. Consequently, I witness a 30 to 50 percent faster change cycle with fewer delays in approvals and releases. By using Siemens PLM TeamCenter to manage data, we establish a single source of truth, minimizing the chances of duplicate or outdated data and preventing BOM discrepancies. Overall, the business impact is considerable, as the system avoids costly production or compliance mistakes and secures indirect yet significant cost savings.

For those considering Siemens PLM TeamCenter, I advise focusing on business outcomes rather than just features. Keep your data model as simple as possible and avoid complicating object types or relationships. A simpler model offers easier maintenance, faster upgrades, and better performance. Minimize customizations and lean towards configuration; use out-of-the-box capabilities. Customization should only be pursued when it provides real business value, as over-customization can increase costs and complicate upgrades and scalability. Essentially, keep it simple, align with business goals, minimize customization, and invest in governance and user adoption, which are key success factors for Siemens PLM TeamCenter.

I would recommend Siemens PLM as a company, as their products, including Siemens PLM TeamCenter, NX, and Solid Edge, are exceptional. I have given this review a rating of eight out of ten.

My main use case for Siemens PLM TeamCenter  is maintaining a user base on the shop floor who work with drawings and all related data. We have one business unit that creates tools, known as the Rich tool. All designs for the shop floor from E-BOM to M-BOM are managed in Siemens PLM TeamCenter . For example, we have a great screwdriver where, when designers have an idea on how to create it, all this data is available. Designers follow the workflow process, and after maintaining all the data, it goes to the shop floor where manufacturing is done. After that, if we have a change request, we can handle the modification. I connect with different POCs as per requests about my main use case.

The best feature of Siemens PLM TeamCenter is that we have both a Rich Client, which we can install as an application, and we also have an AWC client, which is the Active Workspace client. We can log in using that, and it has its own CAD  tools, so we do not need to integrate with different tools.

For the CAD  tools, we have TeamCenter NX, which comes with Siemens PLM TeamCenter installation kit. When we install Siemens PLM TeamCenter, its integration is directly done with that. In NX, we can design our tools, design the layouts, and create 3D models of that design. AWC is essentially a web link, so if we do not want to install the application on our server, we can use that link and access Siemens PLM TeamCenter from anywhere, which helps my day-to-day work.

Siemens PLM TeamCenter has positively impacted my organization as it has saved a lot of time. It has a very quick response, its environment is very stable, and its support is very good. We have both software as a service and on-premises setup. Overall, compared to the availability of different PLM tools, Siemens PLM TeamCenter is very stable and very good to work with, and it is very user-friendly.

For improvement of Siemens PLM TeamCenter, we can add something. For example, there are patches that come, and we have raised some enhancement requests. Sometimes they take time to enhance, so they could improve in that area.

I have been using Siemens PLM TeamCenter for 5.4 years.

Siemens PLM TeamCenter is very much stable.

Siemens PLM TeamCenter is very much scalable.

The customer support of Siemens PLM TeamCenter is very good. I would rate the customer support a 10 because they have 24/7 support available.

I have not previously used a different solution because I have been with Siemens PLM TeamCenter from the starting, so I don't know any other.

The initial setup and implementation of Siemens PLM TeamCenter for my team was a little bit problematic in the beginning because we moved from Windchill  to Siemens PLM TeamCenter. However, we can do the customization, which makes it easy to implement.

I need to customize Siemens PLM TeamCenter very rarely because most things are out-of-the-box, so we can use that. We barely use customizations.

I don't have any idea about seeing a return on investment because we have a separate team that works on that, which is at the upper level of the organization.

My experience with pricing, setup costs, and licensing is that we have different kinds of licenses as per our usage. We have consumer and author licenses, so depending on the usage, we can choose the license bundle accordingly.

I don't have any idea if my organization evaluated other options before choosing Siemens PLM TeamCenter because this was all done at a high level.

My advice to others looking into using Siemens PLM TeamCenter is that they can use it. I would rate this review a 9.