Datum
All skills
DocumentationRev. Q3 2026

ECO writer

Draft a complete engineering change order or change notice: precise change description, reason for change, affected items sweep, disposition of existing stock, interchangeability call, and the validation required before release. Use whenever the user needs to write an ECO, ECN, or change request, revise a drawing, decide whether a change breaks interchangeability or needs a new part number, or figure out disposition for parts already built.

Noah Klein portraitNoah KleinConfiguration EngineerPTC logoPTC

Likes are peer vetting. Like this skill if it held up in your work.

ECO Writer

Writes the change package the way a good configuration manager wants it: unambiguous before/after, an honest affected-items sweep, and disposition decided on the record instead of by whoever finds the old stock first.

Required inputs

  1. The change: what is different, stated as before and after (dimension, material, note, supplier, process, software/firmware if bundled).
  2. The reason: field failure, cost reduction, supplier obsolescence, DFM, requirement change. Reference the trigger document if one exists (8D number, NCR, RFQ).
  3. Affected part numbers and where they live: assemblies that consume them, drawings, work instructions, test procedures, CAD models, and whether the part ships to customers as a spare.
  4. Inventory situation: quantity in stock, WIP, at suppliers, in the field.
  5. Urgency and whether the change must cut in at a specific serial number, lot, or date.

Method

  1. Change description. Write it so a reader with only the ECO and the drawing can implement it: "Sheet 2, zone C4: dimension 25.00 plus/minus 0.10 was 25.00 plus/minus 0.05" for every delta. No "update per markup."
  2. Interchangeability call. Apply the standard test: if the new part fits, performs, and is safe in every application of the old part, and vice versa, the revision can roll. If interchangeability breaks in either direction, recommend a new part number and say which direction broke and why. Flag the trap cases: changes invisible dimensionally but not functionally (material, heat treat, firmware, calibration).
  3. Affected items sweep. Produce a checklist by category and mark each found/needed/none: parent assemblies (where-used), detail and assembly drawings, 3D models, BOMs, work and inspection instructions, test procedures and ATPs, fixtures and gages, supplier POs and quality agreements, service manuals and spare part listings, regulatory or customer approval requirements (PPAP resubmission, first article, notified body). Missed affected items are the number one ECO failure; be exhaustive here.
  4. Disposition. For each pool of existing material, recommend one of: use as is (with justification), rework (with instruction reference), scrap, return to vendor, or use until exhausted, and state whether field units require action. Tie disposition to the interchangeability call; "use as is" on a non-interchangeable change requires an explicit deviation.
  5. Validation before release. List what must pass before the change is effective: analysis update, delta qualification test, first article inspection, process capability run. Scale it to risk; a note correction needs a checker, a material change on a structural part needs requalification.
  6. Effectivity. Recommend the cut-in mechanism (serial, date, lot, "upon stock depletion") consistent with the disposition, and state how mixed configurations will be tracked if both exist in the field.

Output format

  • The ECO in standard sections: Change Description (itemized before/after), Reason, Interchangeability determination, Affected Items table, Disposition table, Required Validation, Effectivity, Approvals required
  • A one-paragraph summary suitable for the change board
  • Open items list: every place where information was missing, phrased as the specific question to answer

Guardrails

  • Never mark a change "form, fit, and function unchanged" as a default; require the reasoning on the record, and when in doubt, call it non-interchangeable.
  • Cost reductions get the same validation scrutiny as fixes; cheap changes that skip requalification are how field failures start.
  • If the change stems from a safety issue, flag that field disposition (recall, service bulletin) is a decision above the ECO and name it as an open item rather than deciding it.
  • Match the user's PLM vocabulary if they state it (ECR/ECO/ECN, Change Request/Change Notice); otherwise use ECO generically and note the mapping.