Monday, June 16, 2014

How to select a PLM system

During my 15 years in the PLM industry, I have seen my share of PLM evaluation processes, both from the vendor’s side and from the customer’s side. Selecting an enterprise IT system is a comprehensive exercise. The selection of a PLM system is no exception. This is due to the wide range of functions and the fact that PLM can involve many departments (if not all) in a company; all the way from sales, through design and engineering, manufacturing, and even service and after-market.

In this blog I will share my top tips on what to focus on when selecting a PLM system.

  • Define the strategy Before diving in to the detailed technical requirements of the PLM system, it is important to set the ambition level and to define the strategy. Start with the big questions: What shall the PLM system do? Is it a strategic enterprise-wide system or just a tool for a specific department? Is the focus on the extended enterprise and global collaboration, or just to have revision control of CAD models? There is no right or wrong answer here, but it is critical to have a clear view on what the focus should be and what you want to achieve.
  • Plan ahead When selecting a PLM system, it is important to look at both the needs of the business today and for the future. Think both short-term (what is important to solve today?) and long-term (what do you want to achieve in the next 3-5 years?). Typical short-term needs can be CAD integration, document management and change management, while long-term needs can be supplier collaboration, installed base tracking and systems engineering. It is important to select a tool that caters for both short and long term requirements, and then evaluate solutions based on those ambitions and needs.
  • Educate yourself Before starting the evaluation process you should gain knowledge of the PLM discipline. This is important in order to be able to define the requirements properly and to have productive discussions with others on PLM (internally and with vendors). You can gain this knowledge yourself by attending a training class or browsing the Internet, or you can hire an external consultant to assist you.
  • Don’t underestimate the importance of usability At first sight, most PLM systems look flashy and quite similar. It is only when you look deeper that you see the differences and how user-friendly a system really is. To secure end user adoption of the system, it is critical that the system is intuitive, user-friendly and easy to learn. This is especially important for ad-hoc/light users of the system who will use the system only sporadically. My advice is to invite non-engineering users with no PLM experience to attend one of the demonstrations, and let them give input on usability.
  • Focus on what’s important All the major PLM systems on the market today cover all the required basic PLM functionality. So there is no need to spend time specifying this in the evaluation process. Instead of over-specifying, focus on what is really important. This may be integration to a specific MCAD system, compliance management or other areas outside the PLM core (PDM). All PLM vendors claim they have this, but the level of support varies.
  • Select an experienced partner A PLM system is an enterprise IT system that will be around for many years after it has been implemented. Selecting an experienced and solid supplier and implementation partner is an important criterion for a successful PLM installation. It doesn’t matter how good a PLM system is if it isn’t implemented in a proper way, so take a look at the track record of the supplier: Have they done similar implementations before? Are they financially solid? Will they be there in 5-10 years? These are important questions that need to be addressed.
  • Talk to other PLM customers By looking at the websites of the PLM vendors, or by attending a demonstration, it can be difficult to distinguish the PLM systems from each other. The best way to really learn what a PLM system and the implementation partner are capable of is to talk to someone with experience of the specific tool and implementation partner. Ask the PLM vendors for a list of reference companies (with contact persons). Ask for references in the same industry and references that use the same functions/modules (e.g. integration to a specific ERP system) that you will be using. Take the time to talk to as many references as possible. They can give valuable input that you will not get from the sales guys.

Conclusion
When selecting a PLM tool it is as important to look at the non-functional requirements as it is to look at the functional requirements of a PLM system. All the major PLM systems on the market today deliver more or less the same functionality. Focus on the local supplier, their solidity and ability to implement. Talk to other companies using PLM systems. Don’t underestimate the importance of usability, especially for ad-hoc users. User adoption is critical for a successful implementation. And before diving into the technical details, spend time defining the PLM strategy, look at what role PLM should have both today and in the future, and make sure this is backed up by management.

Lars

6 comments:

  1. This is a pretty good list but I would start with

    "What business problems am I trying to solve and is PLM the best way to solve them?"

    Then I would add "What other enterprise business applications are critical to my organization and how should a PLM system integrate with them?"

    And finally I would strongly suggest bringing on a experienced PLM consultancy....they will have been through this many many times, while the customer is only going to do it once..."

    ReplyDelete
    Replies
    1. Hi Craig,

      Thanks for your comment. I totally agree with you. Before you start evaluating different PLM tools you need to look at the role of PLM in the total IT landscape and, as you say, what business problems should be solved by PLM. This should be described in a PLM business case before starting the selection process of the PLM tools. And yes, having trustful advisors in this process is important. There are many pitfalls that can be avoided by utilizing the experience from someone that has done this before.

      Best regards,
      Lars Fossum
      Senior Advisor PLM
      Infuseit.com

      Delete
  2. Hi Lars, this is a good start. Taking a strategic approach is essential, as you suggest.

    Experience is important, but it needs to be (mostly) local AND available. Our detailed methodology, hard won from over 30 years experience, includes many other considerations to ensure that companies consider technology, people, and process elements in pursuing their strategic direction.

    Stan Przybylinski, VP of Research, CIMdata, Inc.
    s.przybylinski@CIMdata.com

    ReplyDelete
    Replies
    1. Hi Stan,

      Thanks for your comment. I agree with you that experience is important in evaluating PLM systems. My experience is that many companies embark on this PLM journey without any prior knowledge or experience of PLM. To avoid all the potential pitfalls I believe it is a success criterion to bring along experienced advisors who has done this many times before.

      Best regards,
      Lars Fossum
      Senior Advisor PLM
      Infuseit.com

      Delete
  3. Lars,

    Very good article! unfortunately, you are very right about all PLM vendors providing more/less the same functionality these days. To have local trustful advisor and service company helps. And the focus should be how to balance strategy with short 3-4 months delivery timeline. Some of my other thoughts of what you can face with PLM selection this year is here -- 7 rules for selecting PLM software in 2014. http://beyondplm.com/2014/01/17/7-rules-for-selecting-plm-software-in-2014/

    Best, Oleg

    ReplyDelete
    Replies
    1. Hi Oleg,

      Thanks for your kind words. A local experienced advisor is critical for PLM implementation success. I doesn't matter how good a PLM system is if it isn't implemented properly.

      Your list is a very good extension to my list. I especially like the first one on PLM use cases. Looking at different scenarios where PLM could play a role is a good start for defining the requirements for the PLM tool. But it can be hard to define these requirements if you don't are aware of the possibilities in a modern PLM tool. So, as you say, having a local trustful advisor can be very helpful in this process.

      Best regards,
      Lars Fossum
      Senior Advisor PLM
      Infuseit.com

      Delete