Carbon

Create a change notice

The entry points that open a change notice, the fields on the create form, and how change notices surface back on a part or tool page.

Create a change notice from the standalone form, an item, a method version, or a quality issue. Every entry point opens the same change-notice detail page.

Entry points

FieldType
The standalone form. Start here when the change spans several parts or you haven't opened a specific one yet.
Opens the create form as a modal with the current part or tool pre-attached as the first affected item.
A one-click start: mints the change notice, attaches that part, and drops you on its detail page.
On a part's method, the same version menu that holds New Version offers New Change Notice — the natural place to reach for a change while you're looking at the recipe.
From a non-conformance, this opens a change notice with the issue linked, so the engineering fix is traceable back to the problem that prompted it.
NOTE

Starting from a part pre-attaches it.

The part-header, tool-header, parts-table, and method-version entry points all pre-select that part or tool as the change notice's first affected item, so you land ready to pick a change type and edit. The standalone form starts with no affected items — you add them on the detail page.

The create form

The header form describes and assigns the change. Add affected items after creation.

FieldType
What this change is, in a line.
The change-notice type, drawn from your configured categories. See Categories & actions.
Why the change is needed. Rich text.
What's changing, in narrative. Rich text.
The employee responsible.
Low, Medium, High, or Critical.
Defaults to today.
Optional target.

The form does not include affected items. Add them on the detail page. Item-based entry points pre-attach the selected item; the quality-issue entry point links the non-conformance. Submission creates the change notice in Draft and opens its detail page.

NOTE

There's no separate change-notice permission.

Change notices are gated by the Parts permission: creating one needs create access on Parts, and advancing or releasing needs update access. If someone can manage parts, they can manage change notices.

Where change notices surface on a part

Parts and tools display the change notices that affect them:

  • Open change notice alert. When a part is on one or more change notices that haven't reached "Done", its detail page shows a warning: "This part is on 1 open change notice" (or "…# open change notices"), with each change notice id linked. This is the guardrail against two people revising the same part blind. It's informational, not a lock — parallel change notices on the same part are allowed.
  • Change Notices history. A card lists every change notice that has touched the part, newest first, with released ones de-emphasized — the full "why did this part change?" trail.
  • Provenance back-link. A revision or part created by a released change notice carries a "Created by CN-…" reference to the change notice that made it.
NOTE

Change notices are numbered CN-.

Each change notice gets a per-company readable id like CN-000001. That's the id you'll see in the alert, the history card, and the provenance link.

NOTE

Records created before the rename keep their ECO- ids.

The feature used to be called a change order and numbered ECO-000001. Only new records pick up the CN- prefix — existing ids are left exactly as they were, because they're audit trail and are quoted in drawings, emails, and customer correspondence. So a mature company will see both ECO-000042 and CN-000043 in the same list. They're the same kind of record.

Change types

What you set on each affected item once it's attached.

Revise a part

The same flow told as a story.