Back-out Plan

Back-out in case of unsuccessful implementation is handled on several levels:

• Actual back-out activities can be prepared for the change and placed (in the sequence of change activities) after checking of the successfulness of the implementation. Such back-out activity will then be activated only if the implementation has been unsuccessful. This activity can also be included in a predefined model ticket.

  

• Back-out planning can be covered by another activity placed in the planning stage of the sequence of change activities.

Remediation Planning

A remediation document / back-out plan detailing the measures to be taken if the change implementation has not been successful should always be provided with a change ticket. Before a change is authorized, this remediation plan should be inspected, tested and approved.

In Valuemation Change Management, remediation plans are attached to the change via 'Documentation' objects. Documentation objects not only attach and categorize attachments, but also provide additional information to the attachments, most importantly status information.

One or more remediation planning documents can be attached to a change via a documentation object of Documentation Type 'Backout Plan'. Before the change is authorized, the Change Manager must make sure that the backout plan documentation object is in status 'Approved / Released'.

Remediation planning can be further upgraded by administering documents via USU KnowledgeCenter, a knowledge management tool which can be easily interfaced with Valuemation. USU KonwledgeCenter provides sophisticated document management features including document flow with fully customizable status transitions and authorizations.