Proposed Changes

Proposed Changes can be added to any change object (a change action, change order, or change request).

This page discusses:

Environment: On premises only

Proposed Changes Table

The Proposed Changes tab shows all items associated with a change object. You can add, remove, split, and merge proposed changes. From the change object Content category, click the Proposed Changes tab.

Column Name Description
Name Proposed change name. Click a name to go to the Properties page for that object.
Type Proposed change type or subtype
Rev ("Revision" on the Change Action page) Proposed change revision number or code
Requested Change Operation that the change action is to perform on the proposed change:

Requested Change Change Process
For Release Release the proposed change.
For Obsolescence Make the proposed change obsolete.
For Minor Revise Revise the proposed change and release the new revision of the proposed change.
For Update Update the proposed change with pending changes, if any; otherwise, ignore.
For Revise Undergo a major revision as part of the change process.
New Branch Modify the object as part of a new branch.
For Evolution The proposed/realized item is to be modified under a specific model version (an ‘evolution’). This option shows only for objects to which it is applicable.

Reason for Change/Change Comments The comment or reason for the change that you enter for each proposed change on the list. This appears on the Proposed Changes list as Reason for Change for a CA and as Change Comments for a Change Order and Change Request. Use Mass Update to edit this field for one or more proposed changes.
State The current lifecycle state of the change object
Related CA The related change action. This field appears in the proposed changes table for change orders and change requests.
Description Details about the proposed change. This field appears in the proposed changes table for change actions.

Change Actions

The Change Actions category lists the change action related to a change order or change request. The Change Actions category appears only for change orders and change requests. The columns for the change actions table are:

Column Name Description
Name Proposed change name. Click a name to go to the Properties page for that object.
Type Proposed change type or subtype
CA State Current lifecycle state of the change action
Change action status. The state of the change action is considered with the difference between the Estimated and Actual completion dates. If the Actual Completion Date is beyond the Due Date and the CA is not yet completed, the status appears as a red square.

In Work (not late)

Completed (on time)

Completed (late)

In Work (late)

CA Applicability Indicates the named applicability of the CA when it is used for configured change orders (for example, COs that are specific to certain units, products).

For unconfigured COs, a CA does not have named applicability.

Quick Actions - Transfer ownership of the CA

- Approval Task of the CA

-Impact Analysis of the CA

Contributor The person assigned to start work on the CA
Approver The person responsible for impact analysis and technical approval of the work done on the CA
Approval List The list of users who review theCA
Responsible Org The company or business unit responsible for the proposed change
Planned End Date The date the change action should be completed
Governing CO (applies only to CRs) The related CO name. Click a name to go to the Properties page for that object.
Dependency The dependency change action name. Click a name to go to the Properties page for that object.
Type of Dependency Optional or Mandatory

Page Toolbar

Custom changes (CA with applicability) are not eligible for any edit or CA-related operation in this view. Edit and selection of configured proposed changes with custom change CA with applicability is disabled.

Field Description For More Information
Add Existing

Search for and select existing objects to add as proposed changes. Items that you add also appear at the CR/CO Proposed Change level.

You can add configured objects from the CO proposed changes page only if applicability is defined for the CA.

You can add an object as proposed change to multiple change objects if the object is not change controlled by another change action.

Predefined Queries
Change Assessment

Add all related items to the selected object. This command can be used only on one selected object. Change assessments can be performed for COs and CRs. Change Assessment
Remove

Remove the proposed changes from the change object. This does not delete the items from the database. Removing a proposed change from a CR or CO does not delete any CAs that may be attached.

When an object is removed from a change object, the system checks whether any approved markups are associated with the objectt and change. If so, the disconnection is blocked and the disconnection also deletes these markups.

Note: You cannot remove configured objects from a CA with applicability using the Remove command.
Note: You cannot remove a proposed change that a change action has already processed.

-
Move To

The options under this command let you move one or more selected items to an existing or new change object. This allows proposed changes to split to another CA (either existing or new) related to the parent CO.

In the CR or CO Proposed Changes tab, you can move the selected item to either a new or existing CR or CA.

These options are available only before the In Work state of the context change order in In Process CO state of the change request.

Note: Selected proposed changes must be mapped to the same responsible organization.

Predefined Queries

Creating a Change Order

Creating a Change Request.

Enable Edit

Click to edit items on the page. Editing Proposed Change Details