The past two weeks my main activities were mainly around the following two topics:
- – how to implement PLM successfully ?
- – how do you connect and position PLM and ERP ?
Meanwhile an interesting discussion developed on the manufacturing forum around intelligent part numbers. Check it out if you want to learn more on that topic. In my next post, I will continue in de sequence of How to connect PLM and ERP, as there are many other topics to discuss.
This post, I will continue with the 5 reasons for companies not to implement PLM. An interesting report related to this topic was written by the Aberdeen Group: The Best Kept Secret of Top SMB Product Developers – Finding the Shortest Path to PLM Value. One of the interesting points raised here was, the comparison of major PLM characteristics and how they were perceived by companies that had implemented PLM and the companies that were thinking of implementing PLM.
Three observations from this interesting report were:
- 54 % of the companies that have not implemented PLM yet, consider costs as a major factor, where from the companies that have implemented only 32 % mentions costs as a major factor. This also supports the arguments I gave in my previous post, that a PLM implementation should not be considered on its costs.
- 39 % of the companies that have implemented PLM consider the implementation process as an important factor, where only 11 % of companies that have not implemented PLM perceive this as an important factor.
- 35 % of the companies that have implemented PLM realized that adapting their processes to support PLM is an important factor, where only 11 % of the companies that have not implemented PLM consider this important.The two last points I will use in my observations below, where I will discuss why a PLM implementation takes too long.
As a reminder the 5 objections why not to implement PLM were:
- The costs to implement PLM are too high
- A PLM implementation takes too long (below)
- We already have an ERP system
- Isn’t PLM the same as managing CAD files
- We are so busy, there is not time to have a PLM implementation in our company
2. A PLM implementation takes too long
When you hear experiences about PLM implementations, you might conclude that indeed the perception that PLM implementations take too long might be right. However, I believe it depends what where your initial expectations when you talk about too long.
The first misconception is probably that you can install PLM like a (complex) product. Companies usually have their previous ERP implementation in mind as benchmark. This creates the expectation that once installing the PLM product, you need to configure the right parameters according to the major business processes, test the environment, train the people and start working. So the company together with the implementing partner starts to build a project plan and after 6-8 months the system should be up and running. And than the problems start …….
PLM is not a product, it is a vision where a company targets to capture, manage and use its Product Knowledge (IP) in such a way that is improves the overall business. Not only during the development phase, but also during the early concept phase, during production planning, production and even after sales / service.
This requires all companies to reconsider the way they work in order to adapt their processes to a PLM aligned overall business process. And changing processes involves people and the way they work. And I guess most of us understand that changes in an organization go slowly. I wrote several posts on this topic and you can find much more on the web.
PLM is not a product install, it is a vision implemented around a PLM system !
The mistake companies make is that they believe with one installation they can implement PLM in their company. Like they did with the ERP system or CRM system. However PLM requires a different way of working and this is underestimated by companies. That is why (numbers from the Aberdeen report):
39 % of the companies that have implemented PLM consider the implementation process as an important factor, where only 11 % of companies that have not implemented PLM perceive this as an important factor.35 % of the companies that have implemented PLM realized that adapting their processes to support PLM is an important factor, where only 11 % of the companies that have not implemented PLM consider this important.
Companies that have implemented PLM realized that the implementation process was much more important to them then the costs (39 % against 32 %). The implementation process, the way and order in which PLM functionally is implemented, is something that might become more standardized in the future.
As PLM for the mid-market is an emerging market, PLM vendors will need to focus on this area. Not only product packaging but also in predefined implementation process templates to provide realistic expectations about the implementation process. A phased approach, for sure as described in my previous post, should be part of the discussion. In general you can say, a basic PLM implementation spans over 2 to 3 years in situations where companies start from scratch. However this does not mean there is all the time activity – sometimes there is just a phase of learning and understanding the current (new) situation after a step executed.
Related to the implementation process you have also the implementation of PLM Best Practices. These best practices also become more and more available for mid-market companies. ENOVIA SmarTeam provides with its express offerings different entry PLM best practices, to be extended in the future, as beside Design and Engineering, many other best practices exist, for example bidding, supplier collaboration, manufacturing planning and more.
PLM vendors will provide PLM Best Practices in the future, still the order of implementation and the adaptation of PLM best practices by a company are different for every company. That is what companies realized that have implemented PLM . Adapting the company’s business processes to support PLM best practice has become a more important topic then the cost (35 % against 32 %). And adapting company business processes is merely an organizational change, which needs to go in the pace that a company can digest.
The fact that companies underestimate the process related issues compared to the overestimation of costs (11 % against 54 %) shows the misconception in the market around PLM. Combined with the perception that a PLM implementation has a fixed time limit these are the reasons why companies believe a PLM implementation takes too long.
Conclusion: As a PLM implementation is a change and improvement process for the company, it is not possible to assign a time limit. There is always time to improve – a judgement between investment and ROI but continuous.
4 comments
Comments feed for this article
February 9, 2010 at 6:53 am
Prashant M. Sagare
Read Jos Voskuil’s Weblog. I am totally AGREED with the openion.
Designing the software to
1. Manage the CAD/CAM/CAE/CFD Data
2. Human Resource Department
3. Finance Department
4. Marketing Department
5. Supply Chain Management (may come under Marketing)
6. Customer Relation Management (may come under Marketing)
Can be done seperately.
The available tools like e-mail can also be used to DATA TRANSFER using LIGHT WEIGHT DATA FILE FORMATS to be used.
Only the thing is DATA SECURITY.
That only we have to manage. And depends on PERSON who is going to be an ADMINISTRATOR.
Hope is one solution. Because I am a Student only.
Thank you.
Prashant M. Sagare
M.Tech. PLM
Latur
Maharashtra State, India
pmsagare@yahoo.co.in
Dear Prashant, thanks for your reaction and I am happy to see your optimistic view – I also believed things were very easy to identify. What I learned in reallity is that PLM is not a departemental solution, it requires a different way of working for all departments, different responsibillities and different mandates. These changes and a lot of details that destory the ideal PLM picture are the challenges a PLM implementer is facing
Success
Jos
LikeLike
February 10, 2010 at 5:49 am
Prashant M. Sagare
Dear Jos,
I need your help in my study M.TECH. in Product Lifecycle Management
(PLM). As this course is been launched first time in India, we were not able to get exact documentations or study material of PLM. May be these data is available with PLM Companies but these are SECURED.
If you do have any kind of study material, can you share with me on the email pmsagare@yahoo.co.in That will be my pleasure.
I am trying to go in deep of any of the topics below
1. Work as an Administrator
2. Decide Software development Architecture
3. Implementation of PLM in an industry (decide criterias)
4. Customize the available software
with discussions with many people, they want me to go for either of the two
1. Implementation of PLM in an industry
2. Customize the software
Again, customization needs seperate and core and special knowledge of Programming, as I am basically a Mechanical Engineer working with CAD/CAE, I hope will take more time… and I may go away from my basic stream. So I may decide
IMPLEMENTATION of PLM Criterias and Techniques
Your suggestions please.
Thank you.
Prashant hi, as mentioned in my email, an excellent overview can be found on http://www.global-plm.com success
LikeLike
October 16, 2011 at 8:45 am
Ranjana
I totally agree. Implementation process for PLM turns out to be most important factor and the PLM software companies tend to down play this. The promises are many but getting down to implementation brings up the features promised but not directly supported by the PLM packages. There are many process driven obvious requirements which are not addressed easily by PLM solutions. Since PLM evolved from CAD background, all other features turn out to be just patchworks. Processes implemented using workflows are not realistic with respect to organisation processes. I would say PLM is still evolving.
PLM implementations (service providers and stakeholders) require a specific approach to make organisations adapt the PLM processes, since PLM processes are not visibly similar to practical processes. An effort is requried to map practical processes to PLM processes. Or alternativel PLM vendors should provide processes similar to practical processes for specific domains.
Also, it very important that PLM be viewed with repsect to the domain it is being implemented. PLM solutions for large and multidisciplinary organisations are way far off from being realistic.
Thanks Ranjana – i think we are fully aligned – i believe PLM vendors sometimes build their tools too generic to cover as many industries (i had this discussion in the past many times with the SmarTeam R&D), where as a customer you would like to have the PLM work oriented to your industry (including optimized handling / gui)
Best regards
Jos
LikeLike
October 24, 2011 at 10:40 pm
Kumar Rajan
Jos,
I have been a regular reader of your blog for some time now and am intrigued by your view of the PLM industry.
Ranjana’s view is quite interesting, and probably more mainstream, and obviously contrary to the view offered by the major PLM providers today. Most PLM systems I know seem to bring a specific process definition to the customer (not necessarily optimized for their industry) and hope to map the customer’s process to that. This “PLM implementation”, always done with minimal strategizing and insight into the customer’s business and by professional consultants, is fraught with problems. The customer is not fully aware of the PLM system’s capability and the implemetor is not completely educated on the nuances of the customer’s processes – almost like two ships passing each other at sea. The implementation result frequently seems to be a combination of workarounds, patchwork, exact and approximate mappings. One could even argue that such a system could lower the productivity of an average customer.
Perhaps the current architectures of PLM systems are simply inadequate for capturing & encoding the unique processes (except for a small common set) in most customers. The common set I refer to happens to be the ‘PDM’ portion of PLM. And maybe the customers are throwing good money after bad in attempting to “implement” the PLM system, while continually discovering new impediments that forces them to rethink their own processes to meet the PLM system’s restrictive frameworks, and never really reaching the ‘end of the road’.
Otherwise, I cant see how most consumers seem to be consistently talking about huge amounts of resources spent on and the inordinate delays in their PLM implementation, while also being unhappy about the end result.
Regards
Kumar
Kumar hi,
I believe there are good PLM implementations based on the standard PLM software vendors provide. However they require an excellent project team and the right vision. Many of the bullets you described in your comment. This, you could call it costly approach brings however significant ROI and I have seen some references where the ROI was 6 – 10 times bigger as the investment.
However this works for the happy few. Then you have the majority who will be using less resources or less skilled resources, more customization and you will see ROI is harder to achieve.
In the mid-market this approach is almost impossible and there I believe the PLM approach has to change – see various articles on that. It is not just a stripped down PLM version or other means. I am working on a post on that for the future – now first finish the quarter 🙂
Thanks for your comments and best regards
Jos
LikeLike