Introduction
A new application “Change Governance” is introduced in R2022x release and is part of the role “Change Manager (CHG).
The new "Change Governance" 3DDashboard application enables users to initiate a change request, run change assessments and implement approved changes using the following:
- Change Request (CR) (Change Governance widget)
- Change Order (CO) (Change Governance widget)
- Change Action (CA) (Change Governance widget)
Change Request (CR):
You can create Change Requests to understand and capture the full scope and effort of the change. This process involves an internal assessment that might be required to solve complex problems and to understand the impact, full scope and effort of a requested change by allowing concurrent multi-domain contributors to participate in the change assessment process.
The Change Request offers two processes: “Simple” or “Detailed”. (as described by the attribute “Analysis Type”):
- Simple Change Request
Allows change coordinators to submit change request for fast-track request that need a simple impact analysis, low in effort and still require approval for implementation.
The Change Request can be submitted for approval even if the Impact Analysis is not in state “Frozen”. In this case, the Affected Items are automatically added to the Impact Analysis.
This type makes the Impact Analysis process an optional one.
- “Detail” Change Request
Required for complex changes that require full impact analysis and input from various impacted functional domains. . In this case, the system will automatically promote the Impact Analysis to “Frozen”
This type enables to create multiple Impact Analysis .
Once the Change Request is created, the following content is added to it:
What | Why |
Affected Items This is the IP (one or many objects) where the original request was initiated against This can be the root parent, or certain children | Make sure the analysis will be conducted based on this initial content (This can track the change itself, while the Change governed items are managed through CO / CA) |
Members:
| Ensure the right change control board (CCB) is involved |
Impact Analysis Create Impact Analysis for each affected functional area For each Impact Analysis, assign a functional lead using the assignee on the Impact analysis (information tab) |
|
Impact analysis
The impact analysis holds the following content:
- Analysis base
These items represent the base of the analysis & effort that will be conducted on for each Impact Analysis assignment
Affected items can be added as “Analysis Basis”
Use the Analysis Basis to perform where used and navigate other impacted areas.
- Impacted Items:
These are the items that will need to be modified/replaced. Later they will be attached to Change Action(s) as proposed for implementation and track their modifications.
You can add the Analysis basis as Impact Items.
You also run a Change Assessment using the “Relations” app in order to discover other possible impacted content, that should included in the change process.
Change orchestration:
To orchestrate and implement the change, you can add the following to the Change Request:
- Change Order (CO) – to govern the change
For very complex changes impacting different types of modules and requiring multiple functional domains, and even partners, across different collaborative spaces, change coordinators can define change orders to group changes actions based on organization, collaborative spaces etc.
- Change Action (CA) – to implement the change
The new change request process will allow change coordinators to orchestrate the implementation directly with change actions, expediting the cycle time of change from evaluation to implementation.
You can review the following video for more understanding of the new change governance process.
