"Day in the Life" Demonstration

IT Change Manager

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>

Urgent Change

A good change management process must have a way to bypass the normal approval routine in emergencies. When the IT Change Manager receives a RFC that he deems urgent, he changes the priority to "URGENT," the status to "PENDING" and the Waiting Code to "AWAITING APPROVAL." Giva eChangeManager automatically notifies via email all members of the CAB and EC of the urgent RFC.

Rejected Change

If the IT Change Manager determines that the change should not continue through the change process, he makes the Status "REJECTED." He selects the "Rejected Reason" from the list of choices and writes supporting documentation in the "Change History" field. Upon updating the RFC, Giva eChangeManager automatically notifies via email the Requester and the Customer.

<< 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 >>