Change form

A single change form is shown in a Change form tab. A change form is owned by the home organization (which is responsible for managing its contents), and has a unique change identifier.

The Change form is used to manage other items and has a unique set of tabs:

  • items that are affected
  • groups that must review and approve
  • observers who will be notified
  • related change forms
  • files that implement the change, such as rework instructions

Attributes§

Since changes have different behavior than other items, they require special attributes describing their

  • Purpose: reasons for change, alternatives investigated, problem source
  • Effects: items affected and date, disposition instructions
  • Constraints: production quantity, serial/lot numbers, or time limits

Affected items§

These are the items that are the subject of the change. If the change is an executing change, then the pending items are released, the released items are canceled, and all of the listed items' BOM, source and reference lists are updated according to their Markup lists.

Related changes§

Many times, a change form is one of a related set. For example, a new part must be released for prototyping before revising an assembly to use it. You can show this sort of interdependency by adding other change forms.

Reviewing groups and observers§

Specified groups, such as engineering, manufacturing, and quality assurance, approve change forms. Group members can respond on the group's behalf. PDXpert lets you add any licensed user with appropriate permissions to be a reviewer for any group.

Authorized reviewers can sign a change form once it has been submitted by an analyst; a reviewer approves (or disapproves) it on behalf of the group. A group's reviewer can never sign on behalf of a different reviewer, or undo a signed change form if a subsequent reviewer has acted on it or the change is no longer in the Routed lifecycle state.

Change forms can notify other persons, groups and organizations as a change goes through its lifecycle. For example, a major customer may be notified when the change affects its customized product.

Page selector§

Class icon§

The class icon shows the change lifecycle status:

  • In work:
  • Originated change icon Originated
  • Submitted change icon Submitted to analyst
  • Routed change icon Routed for approval
  • Held change icon Held awaiting more information
  • Stopped change icon Stopped after disapproval, wait for an analyst to select the next step
  • Accepted change icon Accepted, and waiting for analyst final review
  • Success:
  • Released change icon Released. All reviewers approved the change. The analyst completes the change.
  • Completed change icon Completed. The affected items are dispositioned.
  • Failure:
  • Canceled change icon Canceled, after a reviewer disapproved. The analyst deletes the change.
  • Rejected change icon Rejected, after a reviewer disapproved. The change form is kept permanently.

You can drag the icon and drop it onto a destination, such as a different change's Related list.

Status bar control§

The status bar control lets you unlock the form for editing using the Lock/Unlock selection. Locking the window automatically saves any changes.

Change Form pages§

1085

Help Guide Contents [as PDF]