Affected (change)

A change form's Affected list shows those items that are impacted by the release of the change.

When an executing change form is released, the listed items are released or canceled, and child items listed on their parents' … Markup lists are added on or taken off the lists. With an advisory change form, the status of items shown on the Affected list is not changed as a result of the change form being released.

Limit the number of items on the Affected list. A smaller list is easier and faster to review and approve.

Item rows §

Add an item to the change form by dragging it from the Item Explorer, and dropping it onto the Affected list. When working with an executing change form, this item drop may add other items automatically; see How items are added, below.

If you have a preferred sorting sequence for the affected items, you can sort the list using a context menu command (for example, Sort by Number), and then select the Update line numbers menu item to renumber the list. After the change has been routed, the list can be temporarily sorted, but the line numbers are permanent.

A part or document can be dragged from the Affected list to any other location that accepts the item. Only one item at a time can be selected.

Use the filter buttons to change what's shown in the list:

• Show/hide home items

• Show/hide partner items

• Show/hide parts

• Show/hide documents

• Collapse list to hide details

• Expand list to show details

An executing change acts on an item to:

• Release a pending iteration. The single row releases the iteration. The change form does not have a released iteration to cancel.

• Revise an item. It has two iteration rows: one row cancels the earlier iteration and the other row releases the revised iteration.

• Cancel a released iteration. The single row cancels the iteration. The change form does not have a pending iteration to release.

  This canceling iteration must be removed from parent relations (BOM, Sources, References lists) before the change can be routed.

Iteration rows §

On an executing change form, each affected item has one or two rows that show the revision and lifecycle that will be released or canceled, and the Release description.

The icons show what happens when the executing change form is released:

• If the iteration is pending when the change form is routed, then it is released when the change form is released. This row is shown when the affected item:

  • Doesn't have a released iteration, and you want to release its pending iteration; or

  • Has a released iteration that is being replaced by this pending iteration.

• If the iteration is released when the change form is routed, then it is canceled when the change form is released. This row is shown when the affected item:

  • Doesn't have a pending iteration, and you want to cancel its released iteration; or

  • Has a pending iteration that is replacing this released iteration.

Disposition rows §

A disposition specifies how to move production items from canceled to released configurations, and calculates the cost of the change. Canceled items are reworked or discarded, and released items are prepared for use. These activities are authorized only after the change form's review, approval, and release. Although physical parts are commonly dispositioned, you can also disposition documents; for example, recovering or destroying canceled drawings, and distributing released replacements.

• Dispositions are linked to iterations that an executing change form is releasing or canceling. The Change Forms collection → Release/Cancel iterations on Affected list setting must be marked. Advisory change forms don't accept dispositions.

• Disposition tasks are performed when the change moves to the Released state. The Change Forms collection → Pause at Released state setting must be marked. Changes that immediately move to the Completed state after approval don't accept dispositions.

Each iteration can have one or more disposition rows, each describing a specified activity (or cost) at a specified location.

Adding a disposition row §

To add disposition information to an affected iteration:

1. Select the iteration, and do one of the following:

   • Select the iteration, open the context menu, and select the Add Disposition command; or,

   • At the top of the Affected list, click on the button.

2. In the disposition detail at the bottom of the form, enter the disposition information.

Disposition detail panel §

When a disposition row is selected, its detail panel at the bottom of the form shows this information:

Activity §

The disposition action or category.

Location §

The location of the items to be dispositioned (as of the date shown in the Quantity).

Recurring activity §

Mark this checkbox if the activity represents an expense for all future items, such as a per-unit licensing fee or tooling amortization cost.

Quantity §

The number of items to be dispositioned, their units, and the date of the item count.

Unit cost §

The unit cost for each item to be handled in accordance with the disposition instructions at the specified location.

Subtotal cost §

The total cost for the dispositioning activity is calculated by multiplying the quantity by the unit cost.

Assigned to §

You can assign the activity to a particular person, who can then view the assignment in the Tasks list on the Item Explorer.

Target completion §

Specify the date when the dispositioning activity should be done.

Actual completion §

The assigned person can update this (as well as the quantity and unit costs fields) after the change form has been released to show when the actual dispositioning activity was completed.

Notes §

Instructions for performing the dispositioning activity.

Deleting a disposition row §

To delete disposition information from an affected iteration:

• Select the iteration, and do one of the following:

  • Select the disposition row, open the context menu, and select the Delete Disposition command; or,

  • At the top of the Affected list, click on the button.

How items are added §

Advisory change form §

When you add an item to the Affected list of an advisory change, only that item is added to the list. PDXpert does not add any other items automatically.

Executing change form §

When you add an item to the Affected list of an executing change, PDXpert looks at the item's BOM, References and Sources lists to decide what other items should be automatically added:

1. If you add a parent item, and that item has a BOM, source or reference child item with a pending iteration, then that child is automatically added to the Affected list. You can manually remove any released child with a pending iteration from the Affected list.

2. All child items that are automatically added to the Affected list are examined. If the child item has a BOM, source or reference child item (a "grandchild") that has never been released, then that grandchild item is automatically added to the Affected list. This process is repeated for each lower level until all automatically-added items have been examined, and all never-released items have been added.

   You must select lower-level pending iterations that are not visible on the parent you add. That is, you must manually add to the Affected list any released grandchild that has a pending iteration.

Before routing the change for approval, always review the Affected list to make sure that PDXpert is doing what you intend.

An item on a change form should be re-dropped onto the Affected list each time you modify the item's BOM, References or Sources lists.

Conflicts may arise when a child item (a) is listed on a different change form, (b) has no pending or released iteration available, (c) has edits that aren't saved, or (d) has been revised after the parent item has been added to the change form. To resolve these conflicts, fix the underlying problem and then re-drop the parent item onto the Affected list to correctly add the child item's iteration.

The most efficient way to ensure your intended changes get onto a change form's Affected list is to work from the bottom of your revised product structure to the top. That is, add each higher-level revised item onto the change only after you've added all lower-level iterations.

There may be times when a previously-released item has an incomplete pending iteration, and you don't want it added automatically to any change forms. In this case, make a separate executing change and add the item to the Affected list. When its parent items are later added to other change forms, the pending iteration is on a change form and thus can't be added.

1088