How do you choose the best PLM Tools for your specific project needs and goals?

Most Enterprise PLM implementations fail to meet their original vision and end up servicing CAD workgroup's PDM needs. Why? Three reasons: 1) The Business Goals weren't properly understood. Scope, Requirements weren't locked down. 2)The customer believed that PLM software was going to enable the PLM they needed, so they bought a system 3) Most PLM Systems are developed for CAD/CAE users by CAD/CAE vendors. Few are independent. RECOMMENDATION: PLM is an approach to business first, software second, so 1) Clearly identify Business Goals, Outcomes 2) Step back, define ideal end-to-end workstreams, and use them for evaluating PLM S/W products (to achieve the workstreams) 3) Evaluate Independent Cloud PLM products before CAD/CAE PLM products.

PLM being as the central nervous system of product development process, connecting everything and keeping things running smoothly. There are many factors apart from commercial factors that need to be considered while evaluating the PLM tool. Such as Integration with existing software and tools, Centralized Storage, Version Control, Security, Collaboration, Search and Retrieval, Usability and Learning Curve, Scalability, Software Updates, etc. So it's always better to make a comparison matrix according to the tailormade requirement. Because every organization is different in terms of its products, processes and work.

PLM Tools are enterprise applications. I would highly recommend identifying you N+1 problems as this will help you implement to solve the current problem but also set the stage for solving the next set of problems to reach the next capability model level your company needs.

Within my role as a PLM consultant with Sona Koyo Steering, a distinguished Tier 1 Automotive Supplier, I engaged fervently in NPD team discussion. This cross-functional coalition, unites specialists across engineering, manufacturing, quality control, supply chain, and IT domains, orchestrates a meticulous orchestration of new project essentials. Such orchestrated collaboration guarantees the seamless alignment of the PLM solution with the distinctive prerequisites of each department.

Process Mapping: Detail all steps in your product lifecycle from concept to disposal. Identify what is currently being managed by existing systems and what is handled manually. Pain Points Identification: Determine where bottlenecks or inefficiencies occur. Are there delays in time-to-market due to communication lapses? Do errors occur in the handover of information between departments? Technology Assessment: Evaluate the existing technology stack and its integration capabilities. Are your current tools compatible with new PLM solutions you're considering? Stakeholder Feedback: Gather insights from users at all levels, from executives to end-users, to understand their needs and frustrations.

With over couple of decades experience in implementing and monitoring Windchill PLM for diverse clients, I ensure seamless integration, effective training, role-based management, and performance audits. Following principles similar to your reference, I prioritize thorough assessment, comparison, testing, and validation to make informed tool selections that lead to successful project outcomes and unlock lasting business value, regardless of the customer's industry or needs.

I am from pharmaceutical industry, so I can add from Pharma perspective, since regulatory and technical horizon in PLM process is vivid in Pharma, based on my experience one needs, seamless synchronisation amongst different softwares such as SAP, Oracle PLM, Regulatory database, kinaxis, etc, implementing any change requires distinct governance as well, so all above and many other aspects needs to be considered, Usually Agile PLM and or SAP PLM, trackwise are some of the tools available in market, based on needs and scale of life cycle events one can choose amongst them.