Versions, approvals and change history
Audio narration · listen first
In PLM, every change is a version and every decision is an approval step. The change history shows who changed what and when; at collection approval, everyone decides by looking at the same information.
In this part
- You explain why a revision is kept as a new version without deleting the old one.
- You list the steps a product goes through in the approval flow, from design to bulk.
- You read the change history and trace a decision.
- You see what the keep, revise and drop decisions in a line review meeting are based on.
Terms in this part
- Revision
- The new version of a style, tech pack or costing after a change.
- Approval flow (status flow)
- The sequence of stages a product goes through from design to bulk, and the approval at each stage.
- Line review (collection approval)
- The meeting where styles are evaluated together with their samples, costing and sales expectations, and the decision to continue, revise or drop is made.
There are 3 questions at the end of the part; at least 2 correct answers open the next part. The questions open with your Academy account, after your Basic certificate.
Certificate 1 · Pimland