Autodesk Vault offers a basic environment for change management that is more flexible and useful for more situations than people realize. The change management interface in Vault appears at first glance to only include a single rigid workflow for change, but upon further investigation you will find that it can be used more broadly. Let’s take a look:
- ECR, ECO, ECN – The Vault change management environment is called “Change Order List,” but that is really misleading. Different templates can be created for many purposes and these could include Change Request (ECR), Change Order (ECO), and Change Notice (ECN) to name just a few examples. If using more that one type in your environment, it is common to use prefixes of ECR, ECO, etc. for each template type.
- Release management – The change environment can be used as a formal release mechanism as well. This might be helpful if you want multiple people to review and approve work before it is initially released. This gives you a location to capture everyone’s comments and thoughts related to the initial release. A template with a REL prefix is often used for this.
- Simple changes – The flowchart for the change environment makes it look like it must be relatively complex, but there are options to shortcut many of the steps for those with the appropriate authority. The “submit and force approval” and “fast track approval” make it much quicker to transact and capture simple changes.
- Complex changes – More complex changes will often use all the steps in the default workflow, and may even go through multiple iterative loops. This can be done by simply rejecting the approval and re-opening the change.
- Simple or complex with the same basic workflow – There is only one formal workflow with the various options built in. This can be used in many scenarios, and often with different people involved (based on the change template used). Each change template can have a different routing. The routing determines which people are responsible for each step in the workflow.
- Role of the change administrator – The change administrator is responsible for determining what happens when changes are in the “Open” state. This means someone else could create a change, but the change admin acts as the gatekeeper and determines if the change is really going to be made by submitting it to have work actually done. This means change requests, change orders, approvals, and notification can really all happen as part of the same workflow if you want to keep things simple.