New Change request form

[New user1212]

Hi,
I received guidelines regarding the changes the client would like... Have you ever encountered anything like this?

Context: There is a request to streamline change requests for the same, low-risk changes which occur frequently to save time and unnecessary approval steps. An example of this type of change would be server patching. Company term these recurring, low-risk requests as “standard” changes. Currently, Company have a “Emergency” and “Normal” change request template.

Ask: To investigate the OOTB capabilities of change requests and whether “standard” change requests can be easily deployed and configured. Would include ability to:

• Submit a normal (current regular) change request, for it to become a “standard” change.

• Have the change manager review and amend accordingly before accepting the change as a standard change.

• Changes should only become “standard” change requests once the CR has been completed at least three times without error.

• When there is an error in change implementation, it would be nice to be able to remove it as a standard change until its again repeated without error (low priority - this could be a manual trigger / process for now, but consideration should be given to template management).  

• Ability to select standard change templates when submitting a normal change, for change request details to be auto-populated.

• The thinking is that Standard CRs use the same form as Normal CRs, the workflow just changes based on template and what is selected.

• Ability to submit a standard change and have it follow a shortened workflow. (see table below)

[Dr Atul G- LNG]

Hi @New user1212 

Ask: To investigate the OOTB capabilities of change requests and whether “standard” change requests can be easily deployed and configured. Would include ability to:

• Submit a normal (current regular) change request, for it to become a “standard” change.

• Have the change manager review and amend accordingly before accepting the change as a standard change. --> This is process-level change, you can define the policies for same.

• Changes should only become “standard” change requests once the CR has been completed at least three times without error. --> Again, it is process level change.

• When there is an error in change implementation, it would be nice to be able to remove it as a standard change until its again repeated without error (low priority - this could be a manual trigger / process for now, but consideration should be given to template management).  --> You can create a report on Standard changes and you can review that report if any change is failed which is raised via standard change and deactivate that template.

• Ability to select standard change templates when submitting a normal change, for change request details to be auto-populated.

• Atul: Yes, OOTB available. Even you can use Change model if you dont want to go for standard and on change model you can define limited approval.

• The thinking is that Standard CRs use the same form as Normal CRs, the workflow just changes based on template and what is selected.

• Atul: NO, Std changes dont go for approval and once it approved it implemented. Also no risk assessment and Conflict detection done on this.

• Ability to submit a standard change and have it follow a shortened workflow. (see table below)

• Atul: Yes, we can define the workflow.

I am happy, if you want to connect for 1-1 , as I worked in change management for a long time, so able to share my experinece.