Digital & AI

Product Lifecycle Management

Central source of truth across product, supplier, sustainability.

At advanced maturity, PLM stops being a document repository and becomes the transactional backbone that every downstream system reads from: costing engines, supplier portals, quality modules and sustainability dashboards all pull from the same style record instead of copies scattered across spreadsheets. Getting there means enforcing data governance rules — mandatory fields before a style can move stage, controlled vocabularies for materials and colours, and a single owner per data domain — so that the record entering production is the same one design approved, not a re-typed variant. Integration architecture (APIs, middleware, or a native connector) with ERP, PDM and 3D tools determines whether that single source of truth actually holds under daily use.

The harder work is organisational: getting merchandising, design, sourcing and quality to agree on workflow stage-gates, approval hierarchies and who can override a locked BOM. Advanced teams run PLM as a change-management programme, not a software rollout — mapping the as-is process, cutting redundant approval loops, and phasing configuration (styles first, then costing, then compliance, then sustainability attributes) rather than trying to digitise everything at once. Reporting maturity follows: once the underlying data is trustworthy, PLM can drive real-time critical-path tracking, automated costing roll-ups and supplier scorecards, but only after the unglamorous discipline of field-level data ownership is actually enforced across every business unit that touches a style.

How the work is done

1
Data model design
Define the style, material, colourway, BOM and vendor data objects and their required fields before any configuration begins.
2
Master data cleanup
Reconcile material and supplier codes across legacy spreadsheets/ERP so PLM launches with a de-duplicated, validated library rather than migrated mess.
3
Workflow configuration
Build stage-gates (concept, sampling, costing, approval, production handoff) with defined owners and mandatory-field checkpoints at each gate.
4
System integration
Connect PLM to ERP for costing/PO data, to 3D/CAD tools for tech-pack assets, and to supplier portals for two-way status updates.
5
Pilot rollout
Run one category or one season through PLM end-to-end in parallel with the legacy process to surface gaps before full cutover.
6
Adoption governance
Track user compliance (on-time data entry, field completeness) and retire the legacy spreadsheet processes once adoption thresholds per the buyer's agreed plan are met.

Decisions you have to make

Configure a commercial PLM platform or build custom workflows?: Commercial platforms shorten time-to-value and get vendor support, but rigid data models can force compromises; custom builds fit exactly but carry long-term maintenance risk — most large brands choose configuration over customisation.
How much historical data to migrate?: Migrating every past season adds cost and clutter with little ongoing value; migrating only active and near-future styles plus reference material libraries usually gives the best return.
Centralise compliance data in PLM or keep it in a separate system?: Centralising gives one view of risk but only works if compliance teams actually update PLM in real time; if their workflow lives elsewhere, integration beats forced centralisation.
How tightly to lock BOM changes after approval?: Hard locks prevent costly late-stage surprises but slow legitimate fixes; a tiered approval (minor swaps auto-approved, structural changes escalated) balances control and agility.
Roll out globally at once or region by region?: A phased regional rollout lets teams learn from early mistakes and adjust configuration, but risks running dual processes for longer — acceptable when supplier bases and product complexity differ sharply by region.

Key metrics (indicative)

Style data completeness at handoff

indicative working range 90–98% of mandatory fields populated

incomplete records force manual chasing downstream and undermine trust in the system as source of truth

Time from concept approval to tech-pack lock

track against baseline, aiming for meaningful reduction

faster lock-in shortens the critical path to sampling and production

Number of active spreadsheet workarounds

trend toward zero, tracked per team

surviving shadow spreadsheets signal the PLM workflow doesn't yet match real work

System adoption / active user rate

indicative working range 80–95% of intended users logging in weekly

low usage means data is stale and downstream reports are unreliable

Costing accuracy vs final landed cost

track against baseline variance, aiming for narrowing over seasons

shows whether PLM-driven costing data is actually improving forecasting

Metric targets are indicative working ranges, not standards or legal limits.

Common pitfalls

Configuring every possible field at launch, which overwhelms users and causes them to skip data entry entirely.
Migrating dirty legacy data unchanged, which just moves the material-code chaos into a more expensive system.
Treating PLM rollout as an IT project without merchandising and design ownership, which leads to workflows nobody actually follows.
Locking BOM changes so rigidly that teams route around PLM for urgent fixes, recreating the shadow-spreadsheet problem.
Measuring success by go-live date rather than adoption and data quality, which hides the fact the tool isn't being used as designed.

Advanced notes and limits

Full closed-loop PLM-to-ERP-to-supplier-portal integration is still uneven across the industry; many brands run partial integrations with manual reconciliation at key steps.
AI-assisted costing and material suggestions inside PLM are maturing but generally need human validation before commitment, especially for new material types.
Sustainability attribute fields (fibre origin, certifications, emissions estimates) are often the least reliable part of the PLM record because supplier-side data entry discipline lags the rest of the workflow.
Multi-brand or multi-BU organisations frequently discover that a single global data model can't accommodate genuinely different product complexity, forcing a compromise between standardisation and category-specific flexibility.

Worked example

Justifying PLM licence spend against manual re-keying cost

Number of active style records per season: 1,200 styles
Average manual re-keying time per style (spec sheet, BOM, costing re-entry): 35 minutes
Fully loaded merchandising labour rate: $28/hour
Seasons per year: 4
Annual PLM licence + integration support cost: $96,000
Expected reduction in re-keying time after PLM adoption: 70%

1Annual re-keying hours before PLM: 1,200 styles x 35 min x 4 seasons = 168,000 minutes = 2,800 hours/year.
2Annual re-keying labour cost before PLM: 2,800 hours x $28/hour = $78,400/year.
3Hours saved after 70% reduction: 2,800 hours x 0.70 = 1,960 hours/year saved.
4Labour cost saved: 1,960 hours x $28/hour = $54,880/year.
5Net position vs licence cost: $54,880 saved - $96,000 licence = -$41,120/year on labour alone.
6Payback requires quantifying secondary gains (fewer costing errors, faster critical path) beyond re-keying labour to justify the remaining $41,120 gap.

On re-keying labour alone the PLM licence does not pay for itself in year one, so the business case must be built on data-quality and cycle-time gains beyond typing time, and the technologist should present both figures to procurement rather than the labour saving alone.

Case study

Context

A mid-sized outerwear brand ran BOMs and tech packs in shared spreadsheets across three regional design hubs, with each hub keeping its own material code list.

Problem

A jacket style shipped with the wrong down-fill certification claim because the costing team copied an outdated BOM row from a prior season's spreadsheet template that had not been updated when the supplier changed fill source.

Action

The brand migrated only active and near-future styles into a PLM system, assigned a single material-library owner per fibre category, and made supplier certification documents a mandatory field that blocked BOM approval until attached.

Outcome

Within two seasons the brand traced every fill claim to a current certificate before shipment, and cross-hub material code duplicates dropped from several hundred to a managed exceptions list of under twenty reviewed monthly.

Audit checklist

Every style has a single designated data owner recorded in the system, not a shared or unassigned field.
Mandatory fields (material code, supplier ID, compliance certificate) block stage progression when incomplete.
Material and supplier master data has been de-duplicated and validated before go-live, not migrated as-is.
BOM change history is logged with who, when and what changed, retrievable for any style.
Integration with ERP costing data is verified with a reconciliation check each season, not assumed to be live.
No team is still running a parallel spreadsheet process for data that PLM is meant to own.
User adoption (login frequency, on-time data entry) is reported to leadership, not just IT.
Sustainability and compliance attribute fields are reviewed for completeness before being surfaced in external reporting.

Glossary

Master data: The single, governed set of reference records (materials, suppliers, colours) that all other PLM records point to, avoiding duplicate or conflicting entries.
Stage-gate: A defined checkpoint in the product development workflow where a style cannot advance until required fields or approvals are completed.
Field-level ownership: Assigning a specific role or person responsibility for keeping one data field (e.g. fibre content) accurate and current, rather than leaving it to whoever last touched the record.
Two-way integration: A system connection where data flows both into and out of PLM, so an update in ERP or a supplier portal is reflected in PLM without manual re-entry.
Shadow spreadsheet: An informal spreadsheet process that persists alongside PLM because the official workflow does not match how a team actually needs to work.
BOM lock: A control that prevents further edits to a bill of materials once it has passed a defined approval stage, protecting costing and compliance integrity.
Critical path tracking: Monitoring the sequence of dependent tasks (fabric approval, sample, PO) that determines the earliest possible ship date for a style.
Data completeness rate: The percentage of mandatory fields populated at a given workflow stage, used as a proxy for whether the record is trustworthy.
Configuration vs customisation: Configuration adapts a commercial PLM platform's existing options to a business's process; customisation writes new code or workflows outside the vendor's standard toolset.
Supplier portal: A vendor-facing interface connected to PLM through which suppliers submit costing, sample status or compliance documents directly into the brand's system.

Practice questions

1. A brand's PLM re-keying labour saving does not cover the licence fee in year one. Should it cancel the rollout?
2. Why does migrating all historical seasons into a new PLM system usually reduce data trust rather than improve it?
3. What is the risk of locking a BOM too rigidly after approval?
4. How should a technologist judge whether PLM adoption is genuinely working, beyond the go-live date?
5. A global brand is choosing between one worldwide PLM rollout and a phased regional rollout. What factors favour phasing?
6. Why are sustainability attribute fields often the weakest part of a PLM record?

Sub-topics in this chapter

Style management: Single record per style holding design, materials, costing and calendar data across the season.
Material libraries: Central digital library of fabrics and trims with specs, suppliers, sustainability data and images.
Costing: Structured cost sheets rolled up from BOM, labour and overhead, used for target vs actual analysis.
Calendar management: Season and critical-path calendars that trigger tasks and warn when milestones slip.
Compliance data: Certifications, restricted-substance results and audit outcomes stored against materials and suppliers.
ERP integration: Two-way flow between PLM (product) and ERP (orders, inventory, finance) to avoid duplicate data entry.

Lessons that teach this chapter

Where this chapter is applied

The value chain stages that use this chapter's skills — chapter to stage to skill.

Study tools for this chapter

Saved on this device only

Study without an account, or sign in to save progress across devices. See the full chapter syllabus.

All chapters and the 42-stage course