Introduction:

When implementing a change process using the ENOVIA Change Management mechanism, “Realized Changes” are created as part of the Change Action. These objects could be:

• New revisions of existing objects
• Newly created objects
• Modified objects
• Objects detached from others

In certain situations, some of these “Realized Changes” must be moved to another Change Action in order to accelerate or delay  the user responses on them (review, approval, modifications)  when implementation plans evolve over the time.

These situations could be summarized as follows:

• The need for faster change tracking of the particular "Realized Change(s):
  • Certain “Realized Changes” might require a faster process than the one implemented in the current Change Action. A typical example includes: approval of long lead items, which must be approved earlier than the other items in the same change.
• Management of rejections:
  • When certain “Realized Changes” get rejected by the change reviewers, it might be essential to transfer them to another Change Action.
  • Unwanted “Realized Changes” captured by the work under may also need to be removed from the current Change Action as they may not contribute to the process.
• Management of flexibility
  • Certain “Realized Changes” might need to be reviewed and approved through a different process which requires a new Change Action.

Transfer “Realized Changes” to a new “Change Action” is now implemented in R2019x FD02.

How does it work?

Users can move one or more “Realized Changes” to an existing or new Change Action.

Associated activities of these “Realized Changes” can also be transferred if required (that is optional).

While transferring the “Realized Changes”, the user can select one of two reasons for such a transfer:

• Early Completion
• Delayed Completion

Note the following:

• Both configured and non-configured Engineering items can be transferred.
• You must disable the ‘Change Collaboration for EBOM-Product Structure’ setting available in the “Collaborative Space Control Center” widget.

• Use the “Multi-select” in the “Realized Changes” to enable the transfer of “Activities”.
• If all objects in “Realized Changes” are transferred, the user can cancel the Change Action.
• The user performing the transfer:
  • Needs to be the owner of the original Change Action (from which the transfer is done)
  • Will be the owner or change coordinator for the new Change Action (to which the transfer is done)
• The original Change Action should either be in the “Prepare” or “In Work” state in order to be able to transfer the “Realized Changes” to another Change Action.

For more information on this process, you can review the attached video (created by Amol MARATHE) which illustrates the transfer process.

Change_and_Configuration_Management 

 ​​​​​​​