Syntha Lab RU

PLM manager

Takes a product from idea to release: tech pack, bill of materials, samples and the collection calendar, and keeps a single set of SKU master data.

For a brand

Open interactively →

About the role

The PLM manager takes a product through its life cycle from idea to launch and keeps a single set of data about it. The result is a product that reached the shelf on time, with correct cost and without gaps between the tech pack, accounting and channel cards. The tech pack serves as a contract with the factory, the bill of materials (BOM) as the base of cost, and the collection calendar and critical path show where a delay moves the launch.

The role links design, the collection product manager, sourcing, production and the warehouse. The PLM manager sees that samples are approved on time without bloated iterations and that BOM consumption rates match actuals. The manager owns SKU master data: colorway, sizes and barcodes are created once without gaps between systems. Completeness and uniqueness of data are checked before an order, not after an error.

A good PLM manager counts the critical path slack of every style and says in advance what risks the launch, instead of explaining the delay afterwards.

A working day

The day starts with the calendar: which stages approach their deadline, where slack on the critical path is zero. Then work on samples and tech pack changes, coordination with factories and design. In the afternoon checks of consumption rates and master data completeness on new SKUs, data exchange with accounting and channels. In the evening statuses are updated.

Documents: tech packs and specifications, sample approval records, the collection calendar, the SKU and colorway reference, consumption rate acts, the list of SKUs to be created in accounting.

Typical decisions

  • When to consider a sample approved and close iterations.
  • What consumption rate to put in the BOM for the new marker.
  • Which materials to unify to lower minimums and leftovers.
  • What is critical in the calendar and which stage needs speeding up.
  • Which SKUs can go into an order and which are not yet ready by data.
  • What to record about composition and origin of materials for future product passport requirements.

Study path

  1. The collection life cycle: stages, owners and time overruns. Collection lifecycle and the critical path
  2. Collection calendar and materials: critical path, MOQ and unification. Collection calendar and materials
  3. The critical path backward from the launch date: slack and the worst case. Season calendar counted back from the shelf date
  4. Sample price and tech pack: the development cost of a style. Cost of a sample and tech pack: development cost of a style
  5. Cost by the product specification. Unit cost from the bill of materials
  6. Marker layout: efficiency and the price of a percentage point. Marker: efficiency and the price of a percentage point
  7. Master data: SKU, colorway, barcode. Master data: SKU, SKU, barcode
  8. Data quality and data owners. Data quality and data owners

What to understand

The tech pack as a contract with the factory
The tech pack records the sketch, patterns, sizes, materials, seams and tolerances. An incomplete tech pack leads to sample redo and disputes about defects.
The bill of materials (BOM)
The BOM lists fabric, trims and packaging with consumption rate and waste. Cost is built from it; an inaccurate rate hits margin at once.
Samples and their price
Every sample is money and weeks. The number of iterations before approval goes into the calendar and the development cost of a style.
Calendar and critical path
The critical path runs from the shelf date backward through the stages. Slack on it shows where a delay moves the launch and where it does not.
SKU master data
SKU, colorway, size and barcode are created once without gaps between PLM, accounting and channel cards. Completeness and uniqueness of data are checked before the order.
Material unification
Fewer kinds of fabric and trims mean lower minimums and leftovers. Count SKUs per fabric and check where a swap does not change the product.
Carbon and the product passport
Composition and origin of materials are best recorded in PLM at once: carbon estimates and future product passport requirements depend on it. Check requirements against current norms.

Key measures

MeasureFormulaHow to read
Critical path slackShelf date − completion date of the last stageZero slack means any delay moves the launch.
Style development costSamples + tech pack + team timeCompare with style revenue; costly development on a weak style is a reason to stop it early.
Consumption rate accuracyActual material use ÷ BOM rateA deviation shows where the BOM is wrong and cost is understated.
Marker efficiencyPattern area ÷ marker areaEvery percentage point of efficiency has a price per batch.
SKUs per fabricNumber of SKUs ÷ number of fabric kindsA rising value lowers fabric minimums and leftovers.
Master data completenessFilled mandatory fields ÷ all mandatory SKU fieldsIncomplete SKUs must not go into an order.

Questions the role asks

Route through Lab

  1. Collection lifecycle and the critical path
  2. Collection calendar and materials
  3. Collection calendar: critical path and slack
  4. Season calendar counted back from the shelf date
  5. Cost of a sample and tech pack: development cost of a style
  6. Unit cost from the bill of materials
  7. Material use and cutting waste
  8. Marker: efficiency and the price of a percentage point
  9. Material unification: SKUs per fabric
  10. Master data: SKU, SKU, barcode
  11. Data quality and data owners
  12. Systems landscape and data exchange
  13. Carbon estimate per item: emissions by stage
  14. Collection gates (stage-gate): a funnel of hypotheses, the price of a hit, the saving against “everything into a trial” and the stop rule of the pilot batch

First 30 days

  1. Open the collection life cycle stages and their owners. Collection lifecycle and the critical path
  2. Calculate the critical path of one style backward from the launch date. Season calendar counted back from the shelf date
  3. Estimate the development cost of a style with samples and tech pack. Cost of a sample and tech pack: development cost of a style
  4. Compare the BOM consumption rate with actual use. Unit cost from the bill of materials
  5. Check master data completeness on twenty SKUs. Master data: SKU, SKU, barcode
  6. Count SKUs per fabric and find unification candidates. Material unification: SKUs per fabric

Common mistakes

  • Handing the factory an incomplete tech pack and fixing samples by correspondence.
  • Taking the consumption rate from a past style without checking it on the new marker.
  • Not counting sample iterations and underestimating lead time.
  • Creating a SKU manually in several systems and getting discrepancies.
  • Keeping a separate fabric for each style instead of unifying.

Reports to keep

  • Collection calendar: Stages, dates, owners and critical path slack.
  • Master data readiness: Completeness and uniqueness of fields by SKU and category.
  • Development cost: Samples, iterations and costs by style.

Data to keep

  • Tech pack and BOM per style: materials, rates, tolerances. PLM and production records
  • Collection calendar: stages, dates, owners. PLM and production records; Plan and budget model
  • SKU reference: colorway, size, barcode. PLM and production records; ERP and accounting system

Open interactively →