My main use case for Siemens PLM TeamCenter is for CAD release, storing CAD data, and integrating it into our procurement system. For example, in the last project, we created full vehicle data with specific part numbers, and those part numbers are saved in Siemens PLM TeamCenter with a specific code, which was also shared with the procurement team. With the help of those codes and that data, the PLM team can directly connect with their procurement partner and get that part sourced without intervening in the design system.
My main use case for Siemens PLM TeamCenter involves multiple things, including creating an eBOM, the engineering bill of materials, design releases, managing the configurations from the product development aspect, and handling the manufacturing bill of materials, the standard tools in the classification library, and MPP, the Manufacturing Process Planner, for doing the operations and allocations of a shop floor assembly lines, along with workflow management and data collaboration between suppliers and OEMs from the manufacturing aspect. When managing the configurations of a product using Siemens PLM TeamCenter, I cascade those configurations to the manufacturing engineering team for them to validate it through mBOM, manufacturing bill of materials, using Manufacturing Process Planner and storing the standard tools inside a facility in a classification library. Occasionally, I find that we heavily use translators to convert one format of CAD to another format in Siemens PLM TeamCenter, and we also use AWC to view the CAD data in browser mode instead of relying on larger engineering workstations, allowing even the finance group and buyer group to see that data in the browser without depending on the PD group.
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.
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.
My main use case for Siemens PLM TeamCenter is to retrieve data and use it to perform releases or apply automatic filters. I use Siemens PLM TeamCenter to filter the data using the references. We primarily use Siemens PLM TeamCenter to store data that we create or to update any other data that we revise. We mostly use it for releases and related tasks.
My main use case for Siemens PLM TeamCenter is to handle the products. We can upload the lightweight models and download the models. We can update the models. A quick, specific example of how I use Siemens PLM TeamCenter in my daily work is related to some of our clients, such as Caterpillar. For that company, we need to download the models, update them as per the scope, re-upload the file, and indicate to the client so that they can check Siemens PLM TeamCenter to see whether it is updated. Generally, my main use case is very helpful to handle the family of the products. For every instance, we can either create, update, and re-upload to the client for review.
We use Siemens PLM TeamCenter for engineering and CAD design purposes, as well as on the manufacturing side and on the quality side. To visualize the information, we use integration and CAD applications. In Siemens PLM TeamCenter, we store design data, and we create drawings for that design. We design it on the engineering side using CAD, and it processes on the manufacturing side, while we have checks on quality to validate the information.
We performed implementations of Siemens PLM TeamCenter for different customers including GE, BMW, and a customer in China. Each customer had different use cases, and I was part of the implementation team.
We use the Siemens PLM TeamCenter for global group CRM. They have R&D centers in Korea, India, and Germany, and they collaborate on all aspects of the project.
TeamCenter is for a company with highly complex processes, like aerospace, defense, automotive and heavy machinery. For example, manufacturing industries must go through a design phase where they create CAD designs and a process-planning phase before they get to execution. Once the product is deployed, they need to constantly maintain and finally decommission it. The entire product lifecycle is stored in PLM, which stores a complete set of data. You can do this with aerospace engines, fighters, or cars. Usually, the OEMs don't do car maintenance, but OEMs are often responsible for maintaining heavy machinery or aerospace equipment. It starts with requirements. Next, they create the CAD, engineering, and manufacturing bills of materials. Then they need to track maintenance throughout the product's life on a bill of maintenance. After the part is decommissioned, the bill of maintenance is closed.
Siemens PLM TeamCenter is a comprehensive platform providing advanced data management and collaboration capabilities for industries focused on engineering and manufacturing processes.Siemens PLM TeamCenter facilitates seamless integration with essential tools like CAD and SAP, offering a streamlined workflow and enhanced collaboration. Users benefit from features such as intuitive interfaces, efficient search, BOM extraction, and effective change management. Although it faces challenges like...
My main use case for Siemens PLM TeamCenter is for CAD release, storing CAD data, and integrating it into our procurement system. For example, in the last project, we created full vehicle data with specific part numbers, and those part numbers are saved in Siemens PLM TeamCenter with a specific code, which was also shared with the procurement team. With the help of those codes and that data, the PLM team can directly connect with their procurement partner and get that part sourced without intervening in the design system.
My main use case for Siemens PLM TeamCenter involves multiple things, including creating an eBOM, the engineering bill of materials, design releases, managing the configurations from the product development aspect, and handling the manufacturing bill of materials, the standard tools in the classification library, and MPP, the Manufacturing Process Planner, for doing the operations and allocations of a shop floor assembly lines, along with workflow management and data collaboration between suppliers and OEMs from the manufacturing aspect. When managing the configurations of a product using Siemens PLM TeamCenter, I cascade those configurations to the manufacturing engineering team for them to validate it through mBOM, manufacturing bill of materials, using Manufacturing Process Planner and storing the standard tools inside a facility in a classification library. Occasionally, I find that we heavily use translators to convert one format of CAD to another format in Siemens PLM TeamCenter, and we also use AWC to view the CAD data in browser mode instead of relying on larger engineering workstations, allowing even the finance group and buyer group to see that data in the browser without depending on the PD group.
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.
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.
My main use case for Siemens PLM TeamCenter is to retrieve data and use it to perform releases or apply automatic filters. I use Siemens PLM TeamCenter to filter the data using the references. We primarily use Siemens PLM TeamCenter to store data that we create or to update any other data that we revise. We mostly use it for releases and related tasks.
My main use case for Siemens PLM TeamCenter is to handle the products. We can upload the lightweight models and download the models. We can update the models. A quick, specific example of how I use Siemens PLM TeamCenter in my daily work is related to some of our clients, such as Caterpillar. For that company, we need to download the models, update them as per the scope, re-upload the file, and indicate to the client so that they can check Siemens PLM TeamCenter to see whether it is updated. Generally, my main use case is very helpful to handle the family of the products. For every instance, we can either create, update, and re-upload to the client for review.
We use Siemens PLM TeamCenter for engineering and CAD design purposes, as well as on the manufacturing side and on the quality side. To visualize the information, we use integration and CAD applications. In Siemens PLM TeamCenter, we store design data, and we create drawings for that design. We design it on the engineering side using CAD, and it processes on the manufacturing side, while we have checks on quality to validate the information.
We performed implementations of Siemens PLM TeamCenter for different customers including GE, BMW, and a customer in China. Each customer had different use cases, and I was part of the implementation team.
We use the Siemens PLM TeamCenter for global group CRM. They have R&D centers in Korea, India, and Germany, and they collaborate on all aspects of the project.
TeamCenter is for a company with highly complex processes, like aerospace, defense, automotive and heavy machinery. For example, manufacturing industries must go through a design phase where they create CAD designs and a process-planning phase before they get to execution. Once the product is deployed, they need to constantly maintain and finally decommission it. The entire product lifecycle is stored in PLM, which stores a complete set of data. You can do this with aerospace engines, fighters, or cars. Usually, the OEMs don't do car maintenance, but OEMs are often responsible for maintaining heavy machinery or aerospace equipment. It starts with requirements. Next, they create the CAD, engineering, and manufacturing bills of materials. Then they need to track maintenance throughout the product's life on a bill of maintenance. After the part is decommissioned, the bill of maintenance is closed.