Lesson 9 · Good practice and checklist

Mapping PLM records to ISO 10007 and ISO 9001 8.3.6, and a printable one-page summary.

Goal of this lessonTo know which clause of which standard the PLM records meet, and to work from a one-page summary.

ISO 9001 8.3.6 and ISO 10007 mappingWhat the standard asksIts record in SODOO8.3.6 a) the change itselfECR: Problem, Reason, Affected items8.3.6 b) results of reviewsImpact analysis + ECO In review8.3.6 c) authorisation of the changeDecision: who, when, note; Apply8.3.6 d) preventing adverse impactsEffective from, the old revision obsoleted10007: identificationEngineering code + revision10007: change controlECR → ECO10007: status accounting and auditLife cycle, baselines, record history
When an auditor asks about a change the answer is one chain: request, decision, order, new revision and the history.

ISO 9001:2015 clause 8.3.6 asks that design changes be identified, reviewed and controlled, and that the change, the review results, the authorisation and the actions preventing adverse impacts be recorded. ISO 10007 sets configuration management up as identification, change control, status accounting and audit. In SODOO PLM each of these is a field or a record; what an audit looks for is one chain: request, decision, order, new revision and history.

One-page summary

This section is laid out to print on one A4 page: use the browser's Print command.

Every day

  • Never edit a released part or drawing in place: Request a Change.
  • Check in when you stop working.
  • Search the part list before opening a code.

Code or revision

  • Fits in place of the old one: new revision.
  • Does not fit: new code, make the old one obsolete.

Change

  • The request is the WHY, the order the WHAT.
  • Read the impact analysis before approving.
  • A rejection has its reason written.
  • Set the effective date; write what happens to the stock.
  • Add the parent assembly to the order too.

Before release

  • All documents checked in.
  • Children are confirmed or released.
  • The BoM shows the new revisions.
  • Drawing and model share the revision.

Who does what

  • Everyone: raises a request.
  • Integration: designs, confirms, prepares orders.
  • Release: releases, applies, decides.
  • Admin: configures, decides.

Where to look

  • Blue guide box: state and next step.
  • PLM Guide: words and process.
  • Cowork: live data and method.

On the screen: effectivity and decision

Effectivity on the change order12345
  1. Send to Review
  2. Effective from: ISO 9001 8.3.6 d) — the date of the action that prevents adverse impact.
  3. Action: the change itself (8.3.6 a).
  4. New revision: identification (ISO 10007).
  5. Opens the new revision.
Caution: changes outside the record
A change agreed by e-mail or phone and never entered in the PLM is an “uncontrolled change” finding in an audit. However small, the decision goes through a request and an order.

Mini case: the auditor asks

Question
“Why did the adapter plate become 10 mm, who approved it, from when is it effective?”
Answer
ECR-2026-0003 (reason and measurement), Nazlı Şen's decision, ECO-2026-0002 (effective date) and the history of PW-PLT-80 rev 1 — linked to one another.

Check yourself

Which four records does ISO 9001 8.3.6 ask for?
The change itself, the review results, the authorisation and the actions preventing adverse impacts.
Where does “authorisation” show in SODOO?
The request's decision (who, when, note) and the order's application (release user).
The first item of the pre-release checklist?
Are all documents checked in?