Teamcenter on Cloud

My main use case for Siemens PLM TeamCenter  is for the engineering bill of material, design bill of material, manufacturing bill of material, and service bill of material. I am quite familiar with and have implemented the end-to-end new product development life cycle from the beginning through post go-live, sales, and support.

To manage the design BOM effectively, we have created a process where we integrate multiple CAD  applications such as Creo  and CATIA with Siemens PLM TeamCenter . The designer designs something and then directly pushes the data to Siemens PLM TeamCenter where the bill of material is directly linked or aligned with the design BOM they created. We manage a neutral product structure and create an engineering bill of material directly in Siemens PLM TeamCenter.

There are many use cases beyond managing an engineering bill of material. Creating a directly neutral product structure allows designers to avoid manual processes. An automatic bill of material integrates in real time with CAD , enabling the engineering bill of material to be created directly in Siemens PLM TeamCenter, and then we place it into a release cycle to create a manufacturing bill of material through the M-BOM to E-BOM alignment process.

The best feature Siemens PLM TeamCenter offers, which stands out to me most, is the collaboration feature present in the latest version. This feature allows multiple users from various design or manufacturing streams to review designs or any artifacts directly in Siemens PLM TeamCenter through a collaboration platform.

This collaboration feature has changed my workflow by making my review process less formal. Instead of adhering to a formal review process, this informal review allows people from multiple streams to come together on a single platform to discuss any artifact or design, give comments, and those comments convert directly into action items assigned to users. This effectively transforms my informal reviews into a structured system rather than relying solely on formal reviews.

The collaboration feature and Active Workspace in Siemens PLM TeamCenter are quite useful, and my process review streamlining has changed particularly regarding design release process streamlining. This change has greatly benefited my users.

Siemens PLM TeamCenter has positively impacted my organization by streamlining my design cycle or MPD cycle. All my data is housed on a single platform, making Siemens PLM TeamCenter my single source of truth where users can find any item and trace back to designs. It has streamlined my new product development process significantly, as manual work can make tracking or reviewing anything quite challenging.

The complexity of the data model frustrates me the most regarding how Siemens PLM TeamCenter could be improved. It should be more flexible to meet current business needs, especially considering the dynamic business environment and the introduction of AI solutions. The platform must accommodate last-minute business changes easily since rigidity in the data model makes it difficult to implement needed adjustments.

The service bill of material currently requires specific customization, which is an area needing improvement. The module for managing the service bill of material, such as MRO , maintenance, repair, and overhaul, needs better optimization without extensive configuration. If future iterations can deliver this functionality out-of-the-box, it would be greatly appreciated.

I have been working in my current field for six months, and before that I was part of JSW group for six months. Prior to that, I worked with Hero MotoCorp, L&T Technology Services, and TATA Technologies. Overall, I have nineteen to twenty years of experience on Siemens PLM TeamCenter.

Siemens PLM TeamCenter is stable and remains stable as a base product.

Siemens PLM TeamCenter is scalable; however, if my user and data growth is moderate year-on-year, it is essential to consider other factors such as server performance and network bandwidth. These factors impact scalability alongside Siemens PLM TeamCenter's capabilities. If they align with Siemens PLM TeamCenter's metrics, it can be a good solution.

My experience with Siemens PLM TeamCenter's customer support is responsive and helpful, although there is room for improvement. The current support style means that if I raise a ticket, I may wait up to forty-eight hours for a response. If this could be expedited, it would greatly benefit customers.

I have not used a different solution because I have worked with Siemens PLM TeamCenter from the beginning of my career, so I am fully committed to it.

The setup and licensing process for me is straightforward, and I am happy with the services I received during this stage. There is no confusion involved.

We do not have any metrics available for return on investment at this moment because we are a greenfield setup just beginning our PLM implementation. However, I can say that time can be saved since my designers are able to utilize the platform for multiple streams and products. Process optimizations can also lead to reduced development time, although exact metrics will require initial projections or requirements.

My experience with pricing indicates that the cost is a bit high compared to other PLM platforms available in the market. It would be beneficial if the price could be reduced to match what competitors offer.

Before choosing Siemens PLM TeamCenter, we evaluated other options such as 3DEXPERIENCE from Dassault, PTC Windchill , and Aras, and then reached the conclusion to select Siemens PLM TeamCenter.

For others looking to use Siemens PLM TeamCenter, I recommend evaluating it based on your business requirements, your organization's vision for the next five to ten years, and aligning the product modules, licenses, and Siemens PLM TeamCenter costs accordingly before making a decision.

I stress the importance of flexibility in adapting to last-minute business changes in the current technology landscape. If the product can accommodate rapid changes, it will be immensely helpful for users.

I found this interview quite good as it covered all aspects of Siemens PLM TeamCenter, showcasing clarity in the queries and questions asked for the customer. My overall rating for Siemens PLM TeamCenter is eight out of ten.

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.