01 First things first

Product Lifecycle Management (PLM)

Product Lifecycle Management (PLM) is a strategic approach to developing, managing, and improving products from conception to disposal—a way of dealing with the different stages across a product lifecycle. However, it can also be a piece of software (or system) that helps manufacturing organizations and Engineering-to-Order (ETO) companies efficiently work through these different stages.

By blending existing procedures and processes with individual expertise and innovative technology, PLM software like Siemens Teamcenter provides a framework that enhances product quality, reduces costs, and accelerates time to market. Product Lifecycle Management software offers a single platform for all product data and related processes. This single source of truth makes it easier for stakeholders to find the most up-to-date information, allowing them to make the right decisions more quickly and efficiently.

02 The stages of PLM

What, when, and why?

From a manufacturing and ETO perspective, Product Lifecycle Management can be divided into five main stages: Conception, Design and Engineering, Manufacturing, Commissioning, and Decommissioning.

{{second-first}}

{{second-second}}

{{second-third}}

{{second-fourth}}

{{second-fifth}}

03 The benefits of PLM

How can PLM help?

The benefits of Product Lifecycle Management for manufacturing aren’t just linked to transparency and timekeeping. Clear protocols facilitated by comprehensive PLM software like Siemens Teamcenter increase the likelihood of creating better-quality products, fewer errors, and greater cost savings thanks to more efficient production processes.

In short, PLM software is crucial for both custom ETO requests and mass-produced products.

{{third-first}}

{{third-second}}

{{third-third}}

{{third-fourth}}

{{third-fifth}}

04 The key components of PLM software

Optimizing the PLM value chain

PLM software streamlines the way different manufacturing companies and specific stakeholders can access data. This is done by integrating tools and features to optimize the overall management of a product. Some tools, such as CAD software, are used heavily at specific stages, whereas key components like document management make up the backbone of a PLM system’s overall offering.

Siemens Teamcenter offers a multitude of tools and components that make PLM a no-brainer for manufacturers looking to scale and optimize their business processes without losing track of the original vision for the brand and products.

{{fourth-first}}

{{fourth-second}}

{{fourth-third}}

{{fourth-fourth}}

{{fourth-fifth}}

{{fourth-sixth}}

{{fourth-seventh}}

05 Picking a PLM implementation partner

Ask yourself the right questions

Picking a PLM partner is the first step to increased efficiency, smoother processes, and better data management. However, to ensure your business's needs are met now and in the future, it's worth considering a few things.

{{fifth-first}}

{{fifth-second}}

{{fifth-third}}

{{fifth-fourth}}

{{fifth-fifth}}

{{fifth-sixth}}

06 Digital transformation with CLEVR

Product Lifecycle Management in action

Siemens Teamcenter is a comprehensive PLM software suite offering extensive capabilities for managing product data and processes across the entire product lifecycle.

We chose to partner with Siemens because of Teamcenter’s collection of tools and integrations, as well as its overall usability.

Nel Hydrogen recently partnered with CLEVR to significantly enhance its product development capabilities. By leveraging Siemens Teamcenter, CLEVR is implementing a comprehensive PLM solution that streamlines data management and helps automate engineering processes. The collaboration is ongoing, with a view to expanding the scope of this initial project.

Our expertise in digital transformation and PLM is what sets us apart from other solution partners. We combine extensive industry knowledge with digitalization expertise to implement tailor-made Siemens Teamcenter solutions that automate and streamline product lifecycle processes.

Even as your company scales and adapts to new challenges, your processes remain flexible and robust. Let CLEVR guide you through today’s bold decisions for greater peace of mind.

Conception

During the ideation phase, competitive analyses help identify market gaps and customers’ unserved needs. This information is used to conceptualize the product, creating a solid foundation for the subsequent PLM stages and decision-making processes.

Automotive manufacturers may, for instance, conduct a competitive analysis to identify gaps in the market for electric trucks, conceptualizing a new model that meets specific urban delivery service needs.

Manufacturing

From a mass manufacturing perspective, this stage starts with a validated, market-ready product resulting from iterative feedback rounds during development. Once the production process is established, it’s time to scale. Planning, executing, and monitoring the scaled production process involves supply chain management and quality control.

ETO companies usually have a single manufacturing process and only one chance to get an order right. Therefore, this stage depends heavily on accurate information from the Design and Engineering, facilitated by efficient PLM software that gets the right information to the right people at the right time.

Commissioning

For mass manufacturers, this stage consists mainly of introducing the product to the market, distribution, sales, and support. Successful product launches require these aspects to be aligned from the start.

In an ETO context, commissioning involves customizing a product's delivery, installation, and support. Successfully deploying bespoke products requires careful logistics coordination, detailed installation procedures, and tailored customer support.

Managing product effectivity—acquiring spare parts and documentation for a specific product version—is also crucial here.

PLM software helps manage these complex processes by providing precise, up-to-date information to all stakeholders. For example, in an ETO machinery project, PLM ensures that engineering details, installation guides, and support documentation are all aligned, allowing for a smooth transition from production to customer site setup and ongoing support.

Decommissioning

Product decommissioning involves Product Managers, Environmental Compliance personnel, and logistics teams. Retirement isn’t just stopping production—effective communication with customers and suppliers is crucial. A tech company may need to plan for disposing of, recycling, or remanufacturing obsolete laptops, ensuring the remaining stock is sold off or used for spare parts. Letting the right people know exactly how these processes should be expected to work is almost as important as the procedures themselves.

For ETO companies, decommissioning involves carefully planning the phase-out of custom products and ensuring clients are supported throughout the process.

Enhanced product quality

PLM software creates a single source of truth for all product data, giving (authorized) departments and stakeholders access to the latest information. This comprehensive data management reduces errors resulting from miscommunication or outdated information.

PLM software also supports extensive testing and validation processes, which helps manufacturers identify issues early in the development cycle.

Reduced time to market

PLM software streamlines a product’s development stage by automating workflows and improving communication among teams. Reducing the time spent on administration speeds up decision-making and helps avoid human errors often caused by repetitive, manual tasks.

Enhanced data management and collaboration also improve the efficiency of the earlier lifecycle stages, which leads to quicker market introductions.

Better data management and collaboration

A centralized PLM system ensures that all product data is easily accessible to those who need it, such as marketers creating assets or campaign messages and after-sales personnel creating training assets for customer support staff. This improves data accuracy and consistency, enabling more informed decision-making. PLM software allows and encourages departments to share information in real time, which reduces information silos and keeps everyone on the same page with the most up-to-date information. 

Cost savings across the product lifecycle

PLM software helps companies avoid inefficient practices that often clog up business processes. This helps reduce costs associated with product development, manufacturing, and maintenance. It also supports better resource management and reduces the need for costly reworks.  

An overview of the production process, including governance and control of automated machinery, lets companies spot material waste and identify ways to optimize production schedules. This reduces manufacturing costs linked to energy consumption and raw materials, which minimizes the environmental impact of a company’s operations. Siemens Teamcenter offers a Carbon Footprint Calculator to help companies assess their decisions as they look to strike a balance between environmental impact, cost reduction, and meeting customer demands. 

Integration and connectivity

Siemens Teamcenter offers extensive integration capabilities with real-time data access for better collaboration. This ensures that all departments and stakeholders across the product lifecycle are on the same page. This is crucial for ETO manufacturers and larger organizations aiming to streamline operations, maintain product quality, and scale effectively.

Good PLM software should seamlessly integrate with various enterprise systems and authoring tools, ensuring cohesive product data management throughout its lifecycle. This means creating a seamless flow of information by connecting Enterprise Resource Planning (ERP) systems, Computer-Aided Design (CAD) tools, and document management software.

Computer-aided design (CAD)

CAD software is essential for creating precise 2D and 3D models, allowing engineers and designers to visualize and iterate on product designs. In PLM, CAD integrates design data with other lifecycle processes, ensuring that all design changes are tracked and managed efficiently. As you’d imagine, CAD software is heavily involved in the conception stage of a product’s lifecycle. So is Product Data Management. 

Product Data Management (PDM)

PDM centralizes all product-related data—which often changes—ensuring accessibility, accuracy, and security. This invariably improves collaboration and decision-making. Within PLM, PDM manages the lifecycle of product data, including version control and access permissions, ensuring that the latest information is available to the right people. 

Bill of Materials (BOM)

A bill of materials (BOM) lists all materials, parts, and assembly configurations required to manufacture a product, which makes it a key feature of the development stage. A BOM represents the product structure in a hierarchical format that clearly presents the relationship between certain components and assemblies. Depending on the product and industry, a BOM can range from a simple, single-level structure to a multi-level structure with specific manufacturing, engineering, and customization guidance.

Like PDM systems, BOM systems track changes. This means that any requested changes to a BOM are documented and sent for approval. A BOM can also include tools to analyze the cost of materials and components. Having an exhaustive and holistic view of the costs will help manufacturers with budgeting forecasts, general cost management, and reporting.

Engineering change management

Engineering Change Management is the tracking, controlling, and approving of changes to product designs and processes. During the development stage, Engineering Change Management helps stakeholders assess the impact of proposed changes on existing designs and processes. It also records modifications, which is vital with the rapid development of a product often containing so many iterations—some of which may need to be revisited for another assessment. 

Computer-Aided Manufacturing (CAM)

CAM software automates manufacturing by converting CAD models into machine instructions, enhancing production precision and efficiency. In PLM software, CAM ensures that manufacturing data is consistent with design data, reducing errors and streamlining the transitions between the design, development, and production stages. 

Supply Chain Management (SCM)

SCM tools are used in the launch and production phase to manage the flow of goods, information, and finances related to a product. In PLM, SCM ensures that supply chain activities are aligned with product development and production schedules, which improves efficiency and reduces costs. 

Document management

This process comprises organizing and managing all documents related to a product’s entire lifecycle. This can include items ranging from compliance records to product brochures. Having the necessary documents in easy-to-find places is key when companies are posed with compliance questions from external regulators. This component is often a feature of the end-of-life phase when companies look to “close the loop” of an existing product, ensuring that it has been produced, distributed, and discontinued in a manner that complies with any number of (changing) regulations.

Compliance and regulatory management

Maintaining a database of the regulations and standards applicable to a product is critical for keeping stakeholders informed on the latest regulatory developments. Sudden changes can result in product non-compliance, which invariably leads to fines and can negatively impact publicity and trust. 

This key component provides the tools to track compliance throughout a product’s lifecycle, which helps generate reports needed for regulatory submissions. Audits can often be lengthy and nerve-wracking for companies. So, having an automated process in place to ensure products meet safety and quality standards can help avoid surprises when regulators are sifting through documentation. 

Do they provide an end-to-end solution?

Ensure the PLM partner you choose will handle the entire product lifecycle. Those that appear only at certain stages and offer support reactively may struggle to produce the most efficient results for your business.

Are they innovative?

It's good to consider how and if your potential PLM partner embraces new technology. Some tried-and-tested methods are all well and good, but partners that embrace the power of low-code with novel PLM systems like Siemens Teamcenter could provide the spark you need to bring your product processes to the next level.

Do they have the right expertise?

Verifying the expertise of those you're considering to partner with is crucial. How experienced are they when it comes to implementing PLM solutions? Do they have the right connections and partnerships with software providers?

Will they be the right fit for your industry?

Look for partners that offer insights into the PLM space and your specific industry.

Like any good PLM system, an implementation partner should be proactive and have an appreciation for moving digital transformation technology forward across all sectors.

Will they provide you with reliable support?

Ensure your PLM partner will offer support at every stage of the implementation process, focusing on the needs of your business with effective solutions that last.

What about the future?

A good PLM implementation partner shouldn't just ensure your solutions and processes work now. Be certain your partner will create a clear, bespoke PLM roadmap that looks years into the future. If they're focused on the here and now without considering the potential twists and turns within your business and industry, you could be in for some nasty surprises.

Related Stories

/Blog

Mendix progress button indication | CLEVR

Published on Jun 13, 2025
min read
Blog

For optimal user exercise the responsiveness of your application is vital. When you click on a button you want an immediate response… Mendix’s solution “the progress bar” is way too much in your face when you need to add it to many button.

It is time to find something more subtile for this.

Animation loading...

SO WHAT’S THE ALTERNATIVE?

Animation click on action done

WELL… VERY NICE WIDGET! NO, IT’S NOT!

With a bit of styling and standard Mendix features you can do this.

  • Create an action button
  • Set a nice icon, like the Glyphicon refresh
  • Set the new option “Disabled during action”
  • Add the class “has-spinner”

That is the Mendix side, Next we need to set the css styling.

  • Show the refresh icon when the button is disabled
  • Animate the rotation of the refresh icon
  • Smooth transition for showing the spinner and increasing width of the button.
  • Show the progress pointer when hovering over the button.

Is it perfect?
No; it works on the disabled attribute of the button. Unfortunately Mendix does not add a special class to a button while it is performing an action. So, don’t used it with button you like to disable based on an attribute.

THE CSS CODE:

.has-spinner .glyphicon {
/* initial, do not display*/
display: inline-block;
opacity: 0;
width: 0;
-webkit-transition: opacity 0.25s, width 0.25s;
-moz-transition: opacity 0.25s, width 0.25s;
-o-transition: opacity 0.25s, width 0.25s;
transition: opacity 0.25s, width 0.25s;
/* delay animation, for fast responses*/
-webkit-transition-delay: 0.8s; /* Safari */
transition-delay: 0.8s;
}

.has-spinner:disabled {
/* show the progress pointer */
pointer-events: auto;
cursor: progress;
}
.has-spinner:disabled .glyphicon {
/* show the spinner */
opacity: 1;
width: auto;
/* This doesn't work, just fix for unknown width elements */
/* make the spinner spin*/
-moz-animation: spin 2s infinite linear;
-o-animation: spin 2s infinite linear;
-webkit-animation: spin 2s infinite linear;
animation: spin 2s infinite linear;
}
/* set width for different btn sizes */
.has-spinner.btn-mini:disabled .glyphicon-refresh {
width: 10px;
}
.has-spinner.btn-small:disabled .glyphicon-refresh {
width: 13px;
}
.has-spinner.btn:disabled .glyphicon-refresh {
width: 16px;
}
.has-spinner.btn-large:disabled .glyphicon-refresh {
width: 19px;
}
/* create the animation */
@-moz-keyframes spin {
0% { -moz-transform: rotate(0deg)}
100% {-moz-transform: rotate(359deg)}
}
@-webkit-keyframes spin {
0% {-webkit-transform: rotate(0deg)}
100% {-webkit-transform: rotate(359deg)}
}
@-o-keyframes spin {
0% {-o-transform: rotate(0deg)}
100% {-o-transform: rotate(359deg)}
}
@-ms-keyframes spin {
0% {-ms-transform: rotate(0deg) }
100% { -ms-transform: rotate(359deg)}
}
@keyframes spin {
0% { transform: rotate(0deg)}
100% { transform: rotate(359deg)}
}

Cheers and have fun! Andries Smit.

June 13, 2025 10:43 AM
/Blog

Feel the need for speed? Increase productivity with Mendix | CLEVR

Published on Jun 13, 2025
min read
Blog

Many tools offer you an increased productivity in what you’re doing. There are a lot of different tools on the market and it’s often difficult to choose the right tool for the job. In 2010 CLEVR has chosen Mendix for the promise of easy and fast development. Back then Mendix existed a few years and was at version 2.5. I consider myself as an early adopter of the Mendix platform. Since then they have released a lot of new versions and reached into the cloud, mobile and a lot more. This blog describes my experience with the Mendix platform over the years. I will share why working in Mendix is so fast and also what CLEVR has done to make their projects even faster.

Firstly, I will address the speed of development. Mendix refers to independent research carried out by QSM, see this website, that shows when a large development project is being developed in Mendix, it is, compared to the same project in Java, on average 6 times faster!! We have a similar experience.

I feel the need.. the need for speed.. - Topgun 1986

6 TIMES FASTER? YES, 6 TIMES FASTER!

How does a development platform enable you to work faster and increase your productivity? By making things simple and understandable. At CLEVR we have teams working with other development platforms and also teams coding directly in Java and JavaScript. In 2010 I was the head of the project team that started rebuilding our ExpertDesk application in Mendix. The 6 years prior, we developed ExpertDesk on another development platform. In just 1 year we have built a version of ExpertDesk on Mendix that has the same and even more functionality than our previous version on the other platform. A great result, especially when you realize that the amount of team members in our development team was reduced by 50%.

In 2010, another development team started working on our product Floxxium, using amongst other technologies Java and JavaScript with (off course) re-use of a lot of libraries. Floxxium is also a service management solution like ExpertDesk, albeit with another philosophy, targeting different markets. By comparing the rebuilding of ExpertDesk on Mendix, with the ExpertDesk on another platform, and the building of Floxxium, we can state that developing in Mendix is at least 6 times faster indeed!

WHY IS MENDIX FASTER?

Mendix uses several types of visual diagrams that they call a domain specific language (or DSL). The DSL for business logic is called ‘microflows’. With microflows you can manipulate data and perform actions like opening forms, calling web services and a lot more.

Example Microflow Metric collection Query

Microflows are used for everything from GUI buttons, to scheduled events, to calculated attributes, to web service handling, to domain model events (triggers on a change of data). Microflows can call other microflows and you can use a functional programming style if you like.

In the DSL for the domain model you design your data structure with entities, attributes and associations. The following features are supporting fast development:

  • The simple overview, so you don’t need separate documentation for your data model;
  • Creating relations with an arrow, even for many-to-many relations, that are completely handled and maintained by Mendix;
  • The inheritance of entities allowing for object oriented thinking and re-use;
  • The non-persistent entities, meaning they are not stored in the database. This allows you to build Mendix as a layer on top of other applications without the need to store duplicates of the data;

You can add calculated attributes to entities that use the same Microflows DSL as all other business logic.

Outline data structure with entities, attributes and associations

Off course there is a DSL for the GUI with layouts, forms and snippets. I suggest you take a tour at Mendix if you are interested by now. You are also welcome to drop me a line (see contact details below). I will proceed beyond the visual ease of use into some of the less visible, but certainly not less powerful features.

The consistency checks are very powerful. You cannot start a model if it is inconsistent and the errors point you direct to the place where they occur. If I remove the first action in the Microflow above the following errors appear:

Table errors microflow

So while building (coding, developing, modeling, give it a name!) the tool helps you in creating software that plays by the rules. This removes a lot of potential errors and therefore saves a lot of time!

The easy extendibility and integrations are very powerful too:

  • Easy (visual mapped) web services;
  • Between Mendix applications even better (faster, easier) AppServices;
  • Java actions that generate a full class for you with parameters and return values for the microflow, so you just have to add a few lines of code between //BEGIN USER CODE and //END USER CODE;
  • Custom widgets using the client JavaScript API;
  • And an AppStore to share all of the above;

Finally the eco system in which the developer does his job is just great. To mention a few benefits of the ecosystem:

  • A built in source control system, called the team server, that saves the revisions in the cloud;
  • Running the application locally by pressing the ‘run’ button;
  • Deploying and running your application in the cloud by pressing another ‘run’ button;
  • Debugging with a graphical, interactive debugger that can also connect to cloud environments;
  • Asking questions on the forum and getting reliable answers fast;
  • A great community sharing work in the AppStore;
  • A cloud portal for full management of your production environment in the cloud.

THE ADDITIONS WE DEVELOPED TO MAKE MENDIX EVEN MORE POWERFUL

We have learned that testing is becoming a big part of a Mendix project. When testing manually, the testing time is getting relatively large compared to the building time. Over time when a project becomes a release and new features are added the testing effort becomes even larger.

CLEVR has developed the Application Test Suite (ATS) to address automated testing. This framework is designed with speed and ease of use in mind. So people who do not build or model in the Mendix modeler can still create test scripts. Off course creating test scripts takes time and the first time maybe a bit more than it takes to do a manual test. But in automating your test you get your returns in huge amounts when you are doing future iterations. If you would perform a regression test for each deployment to subsequently a development, test, acceptance and production environment, you would make 4 times use of the automated test script. And since we are all working Agile the future will have an endless amount of iterations J.

A complex ecosystem like that of Mendix is sometimes also difficult to support. You need tooling to find complex bugs. At CLEVR we have built tooling that makes all kinds of support information available and especially a tool that listens to all log messages, even those internal trace messages. When an error occurs this tool stores the last seconds before the error to the database. That is similar to your airplane’s flight data recorder. For more information on this topic read my other blog on solving common helpdesk problems.

Also platform tools can suffer from performance issues and to address those you need tooling as well. In yet another blog I describe when and how to handle performance issues by making use of the performance and statistics tool in CLEVR’ Application Performance Monitor.

To conclude this blog, I believe with Mendix you can develop your Apps at least 6 times faster than classic developments anno 2015. This means that what would take half a year in the past now only takes a month! And with the right tooling and the right people you can maintain this development speed in the long run.

June 13, 2025 10:43 AM
/Blog

Agile lifecycle - the support side of life | CLEVR

Published on Jun 13, 2025
min read
Blog

Recap

In my previous blog, ‘Agile lifecycle – The project side of life‘, I explained the benefits of the agile way of working in projects. Transparency, communication and fixed versus variable aspects are key in agile project management. But if you look at the complete lifecycle of software, it doesn’t stop after the project is released.

Wheel Agile development Agile projects Maintenance

In our case, the R&D department delivers a product that is rolled out at customer site (Agile development). The delivery team is responsible for the project and potential customizations if needed and will handle this in an agile way (Agile projects). After the sign off, the maintenance department will take over the application and maintain it in the best possible way. Is this working for us?

To be blunt, No…

THE BRIDGE BETWEEN AGILE PROJECTS AND AGILE SUPPORT

When transferring an application from a delivery team to a maintenance team, you need to do some handover. Lean principles are always stressing to limit the number of handover moments in your process since it is considered as waste and results in risks you want to eliminate. Although our handover process is streamlined, the biggest risk comes from another side. The customer…

When executing your projects in an agile way, you are not only nurturing your customer, you are also letting them getting used to a certain way of working. Since most of the work is done on customer location, the communication is direct, transparent and frequent and the customer has full control over all the aspects of the project, you create a certain expectation. This expectation is difficult to meet when you are supporting and maintaining the application in the traditional way.

Most support departments work with an ITIL, ISM, ASL or BiSL process. These kind of processes, or methodologies, are known for their process templates, agreements and best practices. From a support perspective there is nothing wrong with these approaches, but from a customers’ perspective there is.

Imagine a customer that is used to an agile project approach in where they can communicate with the project team instantly, they can turn the knobs on every aspect of the project, decisions can result in immediate actions and they have full control over the list of items and the prioritization of these items. And then… the project is released and handed over to the support department.
All of a sudden the questions, issues, changes and enhancements, a customer wants to have in the application, will be handled as a ticket. Impact, urgency and priority are defined by the support department, with limited or no involvement of the customer. The response and resolution times are calculated based on the contractual agreements and the flow of a ticket is pre-defined and does not allow for swift changes.
Everything we did for our customer in the project is wiped out by the way we support the customer in the maintenance part of the lifecycle.

Is there a way to do it differently? Yes, there is…

AGILE SUPPORT

What if you could offer your customer agile support? What if you could allow your customer to have all the benefits of the agile approach in the support process?

When looking at the maintenance part of the lifecycle, you will have a contact person on customer side, you will have a list of tickets that need to be fixed or developed, you will have a responsible person on your side and you need to deliver a new package of deliverables. It seems that all components for an agile approach are there, so why not handle it in an agile kind of way?

So how do the agile development terms reflect on support?

Reflection Agile Development terms on Agile Support

IMAGINE THIS…

A customer has an issue (user story). They can log that issue with us and we will add it to the backlog. An employee of the customer (product owner) can prioritize the issue. Not in an ITIL way of prioritizing (High, Medium, Low), but in an agile way, 20 stories, means 20 priorities. So the issue with priority 1 will be worked on first, until it is fixed, or the product owner determines that another issue has a higher priority. The customer is fully in control of the prioritization of their issue and there will never be a discussion in which order the tickets should be handled.

When a ticket is created by the customer, the support department will determine the “points” of that ticket. This will not determine the priority of the issue, but says something about the scale and complexity of it. Since the level of priority can also be measured through the number of related issues, support will also determine the relation to already existing tickets. By adding the points to the tickets, it is easy to determine if the support department can handle the story themselves, or if we need to involve backup engineers for this.

By having close communication with the customer (stand up) we can have direct feedback about the list of tickets (sprint log) and the things we are waiting for. Each day we will have this stand up, so the customer is always informed about the statuses of the issues, the things we are expecting from them and, more importantly, the things they can expect from us. Even if nothing happened, it is still wise to update the customer. This allows for mutual expectations and will result in little to no discussions.
Stories (or tickets) will not have ITIL states (like “New”, “Accepted”, “Paused”, “Work in progress”, “Solved”, “Closed”), but can simply be “To Do”, “Running”, “Done”. Since there is close communication, it is not needed to have every possible situation reflected on ticket states.

By introducing an evaluation phase (retrospective) after a maintenance release or rollout of a patch, we are able to determine the satisfaction of the customer and the things we can improve in a future patch or release.

IS THIS REALLY NECESSARY?

In the near future, functionalities of the products you deliver might not be the main differentiator between you and your competitors anymore. You could go for differentiation on price, but there can be only one who is the cheapest. I am convinced that differentiation must be done on service and by delivering an agile experience you are able to be the outstanding service company. Please let me know what you think of this blog post. I am really curious in your opinion.

June 13, 2025 10:43 AM

Frequently Asked Questions

1

What does PLM stand for?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

2

What are the steps in the PLM process?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

3

What is a PLM strategy?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

4

What is the difference between PLM and PDM?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

5

What is the difference between ALM and PLM?

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Contact us

Want to know how our solutions, products, and services can accelerate your digital transformation? 

Want to know how our solutions, products, and services can accelerate your digital transformation? 

Error occurred. Please try again!
Form successfully sent!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.