Categorization, Assessment, and approval model

[cherryberry]

Currently, we are thinking to automate Change management in Magic. we already had 3 types of changes: pre-authorized, normal and emergency. Because it is going to be automated, so the managers are very concern of how it categorizes in Magic, how the RFC is assessed and how the approval process been automated, so does anybody know the automation of categorization model, assessment model and approval model? That means any measurement or condition or criteria against for automation flow? Very appreciated for any suggestion. Thanks!

[UKVIKING]

Are you getting rid of the Change Manager as well ?

What is driving the desire for an automated change management process ?

Pre approved or preauthorized changes are those kinds of changes that impact the least and have been done over and over again with the same risk and impact to CIs and services.

That should be the only criteria for preapproved change
_________________
John Hardesty
ITSM Manager's Certificate (Red Badge)

Change Management is POWER & CONTROL. /....evil laughter

[jpgilles]

I would seriously argue with the idea of automating the management (authorization) of Emergency changes ....

I would consider that only pre-approved (standard) changes should be automated (I would even say they have to be automated). The best way (depending on the tools you are using) is to treat them as "work orders" so the internal workflow in your tool brings them from the "request" stage up to "affected work order" to the appropriate entity (going even further, you could possibly have automated scripts taking the parameter in the appropriate field of the RFC and implementing the change straight forward...).

For the other RFCs (non standard) , automated workflow to the various contributors (impact and risk assesment, for example) up to the change manager - possibily with different paths and managers based on the type of change - is really an interesting feature , but needs to be seriously thought at (design) before implementation.

b.r.
JP
_________________
JP Gilles

[cherryberry]

Thanks!

I am more thinking the way how to define Business risk, technical risk, serverity and priority to come up some standard categorization matrix(pre-authorized, normal and urgent). business risk, for example, some definition which people could follow in the Magic tool. If it is urgent change, CAB as approver will get involved, those type of approval flow...It is more process standardization.