What should you consider to avoid failure when introducing PLM?

Table of contents

Recognize the characteristics of PLM

Before introducing the key points of PLM implementation, I would like to introduce an overview of PLM and the difference between it and PDM (Product Data Management) in order to remind you of the characteristics of PLM.

PLM (Product Lifecycle Management) is an integrated process that covers the life cycle of a product in the manufacturing industry: planning → development → design → production preparation → production → sales → maintenance → disposal. It is a system for managing On the other hand, PDM (Product Data Management, hereafter referred to as PDM) refers to the method of managing the data that is the basis for realizing PLM and the products that realize it. The position of the two is that PLM manages the entire product lifecycle, while PDM centrally manages design data.

By introducing PLM, companies can centrally manage product information, and in manufacturing industries where products are the main focus, companies can improve production efficiency, reduce costs, bring products to market quickly, strengthen governance, etc. You will be able to contribute to In many manufacturing industries, product lifecycle management makes or breaks profits. By keeping this PLM appropriate and optimal, it is possible to contribute to maximizing profits and reducing costs.

These days, there is no longer a clear line between PLM and PDM, and some vendors have appeared that provide comprehensive product lifecycle management systems, so the differences between PLM and PDM may not always be as described above. . For example, Windchill provided by PTC, a company famous for its PLM products , is a product that also includes PDM functions as a PLM package.

Points to avoid failure when implementing PLM

Now, I would like to introduce the key points to avoid failure when introducing PLM, which is the theme of this article. If you are thinking of introducing PLM from now on, consider the following five points and check whether your project is heading towards failure. If you are considering implementing PLM, let’s learn the details of each point to confirm what is important to keep in mind when implementing PLM.

Point 1. What should we do to gain full cooperation from management?

A surprisingly common problem when introducing PLM is that management is negative or not interested in PLM. This is not limited to PLM, but is almost always an issue in systems that require a certain period of time to become cost-effective, such as large-scale systems.

Many executives tend to seek immediate results from systems, and those who are not particularly knowledgeable about IT are often reluctant to move forward unless they can demonstrate cost-effectiveness in the short term. So, how can we gain full cooperation from management?

Rather than explaining what happens at the top stage of PLM, which is the product life cycle, I will explain that PLM functions as a mechanism to efficiently run each individual’s business, how PLM changes business, and the resulting revenue. It is important to explain in detail the impact on Furthermore, although there is a strong perception that system implementation means permission from top management, it is important to involve the field departments first and raise expectations for PLM throughout the organization.

Point 2. Is there a gap in understanding between IT managers and those in the field?

As the introduction of PLM progresses, we must be especially careful about the “difference in understanding” between IT managers and field departments. What I mean by this is that once the decision is made to introduce PLM, the on-site departments begin to have high expectations, thinking, “I think we can do this, and I want to try that.” However, it is also true that the burden increases for the information systems department that actually operates the system. Once the decision is made to introduce PLM, it is best to define requirements and select products while coordinating the understanding of IT managers and field departments, and to introduce PLM in a way that satisfies both parties.

Point 3: Will it increase the burden on IT administrators and consume resources?

Many companies believe that implementing PLM will reduce the burden on IT administrators by centralizing previously dispersed systems for managing product data. However, this is not always the case and there are pitfalls to implementing PLM.

Depending on the product being introduced, there may be some existing product data that cannot be managed by PLM. In this case, it is necessary to operate PLM simultaneously while keeping the existing system, which can lead to double management if done incorrectly. In addition, even if PLM is introduced, if the business process itself does not change, there is a possibility that the work burden on IT managers and on-site workers will not be reduced, so wouldn’t the burden on IT managers actually increase after PLM is introduced? It is also important to have this perspective. Nowadays, PLM products operate on the cloud, so it would be a good idea to consider the cloud as well.

Point 4. Are you introducing systems based on business reform?

Introduction of PLM is a type of business reform. We manage the entire product life cycle, from planning and design to production and even product disposal, and are able to utilize data across departments. In order to maximize this effect, there are many cases where existing business processes must be examined and reformed. Like BPR (Business Process Redesign), what will change by introducing PLM? What existing things should be changed? It is necessary to consider thoroughly before aiming to introduce PLM.

Point 5. Have you made an operational plan in advance after introducing the system?

PLM is a system that becomes cost-effective through long-term operation, so even the introduction is important, but the operational plan after the system is introduced is most important. Therefore, instead of wondering “What should I do?” after introducing PLM, it is necessary to make an operational plan in advance at the PLM introduction stage. If you are unsure about the operational plan after implementation, consult with your implementation partner and create an operational plan tailored to each corporate environment.

Introducing a new system to the product lifecycle with PLM

There are many points to consider and pay attention to when implementing PLM. Although it takes effort, time, and energy, you can enjoy great benefits if you implement PLM to maximize its effects. When implementing PLM, please consult your implementation partner or external consultant and consider the points introduced in this article on your own.

PTC’s Windchill introduced above can be purchased from Nippon Steel Solutions. The company signed the world’s first enterprise partner agreement in the PLM field with PTC, and not only achieved the No. 1 track record as a Windchill distributor from 2013 to 2019, but also achieved the world’s 2nd largest sales performance in 2019. there is. Therefore, we have a lot of experience in introducing PLM, so if you are considering introducing or updating PLM or PDM, why not contact Nippon Steel Solutions?