Change Request Management without CMDB configuration

[Aashish_D]

Hello everyone,

One of our clients is currently utilizing the Incident Management module and is planning to implement the Change Request module as well. However, they do not have a CMDB configured and have no intention of setting one up in the near future. They are hoping to implement the Change Management module without relying on a CMDB.

Could anyone provide insight or suggestions on whether this is feasible, and if so, what potential challenges or considerations should be kept in mind?

Thank you in advance for your input.

Best regards,
AD.

[Dr Atul G- LNG · Accepted solution]

Hi @Aashish_D 

Begin worked as a Change Manager, I can say that while using Change Management without a CMDB offers fewer benefits, I would still suggest going ahead with it. The reason is that at least you can start managing and tracking your changes and approvals. Over time, you can introduce a CMDB and begin using it effectively. You may need to make a few changes at the form level as required, but overall, my final recommendation is to proceed with Change Management. You can refer to the 'Now Create Change Management' workshop PPT for more details.

[Dr Atul G- LNG · Accepted solution]

Hi @Aashish_D 

Begin worked as a Change Manager, I can say that while using Change Management without a CMDB offers fewer benefits, I would still suggest going ahead with it. The reason is that at least you can start managing and tracking your changes and approvals. Over time, you can introduce a CMDB and begin using it effectively. You may need to make a few changes at the form level as required, but overall, my final recommendation is to proceed with Change Management. You can refer to the 'Now Create Change Management' workshop PPT for more details.

[Shivalika · Accepted solution]

Hello @Aashish_D 

You can make it based on just Assignment group and priority field in that case. 

We already know change request has a priority field but is not utilised because we have a risk analysis OOB configuration. But since you are skipping whole CMDB involvement risk analysis is not needed. 

Are you utilising business service and service offering ? You can rely on these fields as well for categorisation of groups - or not - that's a choice. 

Rest concepts like models, workflows and approvals - i guess should remain same. 

Kindly mark my answer as helpful and accept solution if it helped you in anyway. This will help me be recognized for the efforts and also move this questions from unsolved to solved bucket. 

Regards,

Shivalika 

My LinkedIn - https://www.linkedin.com/in/shivalika-gupta-540346194

My youtube - https://youtube.com/playlist?list=PLsHuNzTdkE5Cn4PyS7HdV0Vg8JsfdgQlA&si=0WynLcOwNeEISQCY