Simplified Change Management Options in 3DEXPERIENCE R2017x

 3DEXPERIENCE R2017x

• Creating Change Actions in isolation without a Change Order or Change Request
• Creating and modifying Change Actions within the 3DEXPERIENCE Native App (CATIA)
• Adding Physical Products to a Change Action (since 2016x release)
• Improved Approvers and Reviewer Management

This first simple scenario

Where the Designer (Jake Taylor) requires 1 simple component to be approved and released by the Lead Designer/Reviewer (admin_platform). This scenario can be broken down in to a few simple steps:

1. The Designer:
   1. Creates the Change Action – this could also have been done by other users
   2. He adds the In Work Physical Product as the Proposed Change and specifies that the required change is a Change Status to Released
   3. Adds himself as the Assignee (the user which is doing the work)
   4. Adds the admin_platform user as the Reviewer
   5. He then promotes the Change Action to In Work
   6. When he is ready for sign-off/review, he promotes the Physical Product to Frozen and promotes the Change Action to In Approval
2. The Lead Designer/Reviewer:
   1. Receives a notification that there is a Task to perform, In this example he sees this within the web page
   2. The Lead Designer can then use the Task link to directly access the Change Action and subsequently view the Proposed Changes
   3. The Lead Designer can then Accept, Reject or Abstain the task including adding comments. On Approval the Change Action and the Physical Product CAD are automatically promoted to Released
      1. The Assignee (Designer) would receive a notification of the Approval and completed Change Action.
         

The second simple scenario

Here, detailed below, shows where the Designer (Jake Taylor) has created the Change Action in the 3DEXPERIENCE Web App. Again it is a simple scenario where the Designer requires component approval and release but in this case it is both the 3D CAD (Physical Product) and the EBOM Part. These are again approved and released by the Lead Designer/Reviewer (admin_platform). In this example:

1. The Designer:
   1. Within the 3DEXPERIENCE Web App he creates the Change Action – this could have been done by another users
   2. Adds himself as the Assignee (the user which is doing the work)
   3. Adds the admin_platform user as the Reviewer
   4. He adds both the In Work Physical Product as well as the In Work EBOM Part as the Proposed Changes
   5. He then promotes the Change Action to In Work
   6. When he is ready for sign-off/review, he promotes the Physical Product to Frozen from within the Native App, the EBOM Part to Frozen from within the Web App and subsequently promotes the Change Action to In Approval within the Web app.
2. The Lead Designer/Reviewer:
   1. Receives a notification that there is a Task to perform, In this example he sees this within the web page
   2. The Lead Designer can then use the Task link to directly access the Change Action and subsequently view the Proposed Changes including the 3D viewer
   3. The Lead Designer can then Accept, Reject or Abstain the task including adding comments. On Approval the Change Action, the Physical Product CAD and the EBOM Part are automatically promoted to Released
      1. The Assignee (Designer) would receive a notification of the Approval and completed Change Action.
         

These are both very simple scenarios which can be expanded in various different ways, for example:

• Approval Routes for multiple approval stages or workflows including Delegation and notification as required.
• Use of Change Requests, Change Orders and Issues to initiate and manage changes.
• Initiation of a Change Action which can subsequently be Assigned to a ‘Designer’ to initiate the work.
• Followers of a Change Action for Notification requirements.
• General Document Change Management.