Change form window

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

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

  • items that are affected
  • groups that must review and approve
  • observers who will be notified
  • related changes that must be processed
  • 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, dispositioning 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 implementing 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 just one of a series. For example, a waiver may require a change request, which in turn requires a change notice. You can show this sort of interdependency by adding any number of change forms to the current change.

Authorized reviewers

Specified groups, such as engineering, manufacturing, and quality assurance, approve change forms. Although a group may have many members, only specific group members - like senior engineers, supervisors, or program managers - are permitted to sign on the group's behalf. PDXpert lets you assign any licensed user with appropriate permissions to be an authorized 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 another reviewer, and a reviewer cannot "unsign" a change form if a subsequent reviewer has acted on it.

Observers

In addition to the reviewers, changes can have passive participants who are simply notified as a change goes through its lifecycle. For example, a major customer may be notified when the change affects its customized product.

1085

Learn More
Help Guide Contents [PDF]