Dependencies, Change Orchestration, and Management
Change Actions are the core of the Change Management tool in 3DX. These are used to do the actual releasing and tracking of changes. Change Requests and Change Orders are used to help orchestrate and manage the Change Actions, to ensure that complex changes are properly tracked. This can be useful when you want to hold back releasing of data until everything is ready.
Based on your business processes, you may or may not decide to use the Change Request and Change Order object types. The usage does require a CHG licensed user to help facilitate everything.
The three types of Change Management Objects: Change Requests, Change Orders, and Change Actions.
Change Request (CR): A Change Request is a formal proposal to modify an object. CRs can be submitted through the Change Execution Web App or Change Governance tools.
Change Order (CO): A Change Order oversees the entire change process for significant or complex impacts. It breaks down the impact into one or more Change Actions. Once all changes are reviewed and approved, the Change Order itself is approved.
Change Action (CA): A Change Action is used to manage the implementation of a change. It involves tracking proposed changes within a structured workflow.
Creating Dependencies
When managing a complex product structure with a high amount of change, dependencies become highly intricate.
Dependencies can be established on specific change objects. However, they can only be created between self-governed (non-Change Request) items. There are two types of dependencies:
- Simple Dependency: One item must be completed before the next can proceed.
- Codependency: Both items must be completed simultaneously.
