What are Change Requests?
Change requests allow users to propose enhancements within EPC. Through Collaboration Topics, users can suggest Association Changes, Description Changes, Editorial Changes, and Process Map Changes. Change Requests play a crucial role in continuous improvement within organizations.
| Change Request Category | Description |
|---|---|
| Association Changes | Users can propose alternative and/or new associations for specific objects.
|
| Description Changes | Users can propose alternative descriptions for items that will be viewed on the item’s Details page.
|
| Editorial Changes | Users can propose changes to the metadata of processes or tasks.
|
| Process Map Changes | Users can propose alterations to the process maps themselves.
|
Creating Change Requests
Any user can create a Change Request where they see an opportunity for operational optimization. Individuals involved, including the Accountable users (Process Owners), will be notified and requested to comment and/or vote on the proposed activity. When initiating a Change Request, the key difference is the category of request being made.
For more information on how to create a Change Request, click here.
Steps of a Change Request Cycle:
- User creates a Change Request.
- Involved individuals, including the Accountable user, are notified of the new Change Request.
- Involved users comment and/or vote on the proposed activity.
- Accountable user approves (or rejects) the Change Request
- Accountable user assigns the Change Request Author
- The Author implements the Change Request
- The Accountable user is notified when changes are implemented and verifies them.
Post your comment on this topic.