Quality management in PLM: Why connected quality beats quality after the event

If you lead an organisation in product development and/or manufacturing, in practice this is about lead time, compliance and resilience across the value chain.

The idea that connected quality beats quality after the fact may initially sound like process management. But it actually serves as an operating system for the organisation. When information is scattered across emails, Excel spreadsheets and various personal and shared file locations, a hidden cost arises: time spent reconstructing what happened before you can even begin to solve the problem. A modern, cloud-based PLM approach reduces and partly eliminates this cost by linking decisions to the product record (item number, revision, BOM context, approvals and evidence).

What “good” looks like in practice

In organisations that deliver consistently, quality, change and delivery are not separate silos. The same product definition is used by sales, engineering, manufacturing, purchasing (and suppliers) and service/aftermarket teams. When a problem arises, you can quickly answer: what is affected, which definition was valid, what has already been decided, and who needs to do what next.

Why this matters to management

When data and workflows are connected, the same effects are often seen: fewer late surprises, fewer recurrences, faster release decisions and greater confidence in compliance evidence. The strategic point is the speed of learning – how quickly the organisation turns a signal into a decision, and a decision into prevention.

A minimum viable “connected” setup

Start by defining what must always be linked: the affected item and its revision, configuration/BOM context, evidence (measurements, images, reports) and a formal approval. Enforce this through lifecycle gates and simple templates, so that users capture context by default. The goal is not bureaucracy – but a product record you can trust.

What each role gains

• C‑level: risk, cost of poor quality, time to market.
• Design: clarity on requirements, change impact, confidence in revisions.
• Quality: traceability, evidence/supporting documentation, audit readiness.
• Manufacturing: release clarity, work instructions, production line stability.
• Purchasing / suppliers: supplier accountability, certificates, approved deviations.
• Service/aftermarket: as‑maintained, warranty data, field changes.

The one-minute test

Open any record – a non-conformance, a change request, a requirement or a supplier non-conformance – and ask: can someone new understand the decision in one minute? If not, you are missing context. The solution is usually more structure (consistent fields, links and approvals) rather than more documents. Do this well, and you get a compounding effect: less firefighting and better predictability month by month.

Common pitfalls

Two classics:

1. Free-text records with no link to the product definition

2. Attachments that become uncontrolled copies and drift away from the actual release.

Use mandatory metadata, controlled status transitions and simple templates. If you do just one thing: make the link to the item and its revision non-negotiable.

KPIs to track

Choose one leading and one lagging indicator. Leading: time to containment or time to approval. Lagging: recurrence rate or number of defects found downstream. When data is connected, this becomes measurable – not anecdotal.