Discovery Event Manager change open process

You can use the Discovery Event Manager tool to automate the change open process. When a change is needed to address issues for review or tasks to be performed, the change open process begins. The change goes through phases that drive the unplanned change through the necessary tasks to update the managed fields of a CI or to determine if the change is necessary or desired. To see an Unplanned Change flow diagram, see the related topics.

The change phases are as follows:

Discovery Assessment phase: Assess whether or not an unplanned change is allowed. Comments can be added and updated in this phase, as needed. The CCB Approver must confirm that the change is desired.

• If the change is approved, update the managed field and close the change.
• If the change is denied, move it to the Discovery Backout phase to undo the change.

Discovery Backout phase: Back out a change after determining that the change is not necessary or desired. Comments can be added and updated in this phase, as needed, including updates to modified data. If the backout of the change is complete, move it to the Discovery Verification phase.

• If the denied change is verified, close the change.
• If the denied change is not verified, return to the Discovery Backout phase.

Discovery Implementation phase: The change requires further consideration before it is closed.

• If the backout of the change fails verification, return to the Discovery Implementation phase for further consideration.
• If verification of the change succeeds, close the change.

Discovery Verification phase: Verify that the change is successfully implemented.

• If verification of the change fails, return to the Discovery Implementation phase.
• If verification of the change succeeds, close the change.