MES Functions

Configuration Management Sample Flow Diagram

Details
Category: Configuration Management

An example of a basic Configuration Management Flow

  1. The Change is initiated in the ‘Prepare Change’ Step.
  • An ECN Number is assigned
  • Description of change is made

CM-01

 

After the ‘Prepare Change’ step is completed

  • An email notification will be sent to the first approver.  This notification will make him aware of the pending ‘Change.
  • There is also a monitoring ‘Event Record’ that will keep track if the ECN is not signed off.  The ‘Approver’ will get a reminder every 24hrs (this duration of time is customizable).

CM-02

 

The Second Step

  1. The ‘Approver’ will approve or reject the ‘Change’
  • If rejected, the ‘Reason for Rejection’ must be filled out.  Then the change is repositioned back to the beginning of the Flow.
  • If approved, the ‘Change’ continues to the next step.

CM-03

 

'Final Approver' Notification

  • As in the previous step, the ‘Final Approver’ is also notified that the ‘Change’ is now pending their approval or rejection.
  • The same reminder notifications will apply to this ‘Final Approver’.

 

CM-04

 

The Third Step

  1.  1.The ‘Final Approver’ will approve or reject the ‘Change’
  • If rejected, the ‘Reason for Rejection’ must be filled out.  Then the change is repositioned back to the beginning of the Flow.
  • If approved, the ‘Change’ continues to the next step.

CM-05

 

Third Step Completion

  1. Once the ‘Final Approver’ has approved the ‘Change’ an email notification is sent to the ‘Change Initiator’.
  2. The ‘Change Initiator’ will now take action on the final step.

CM-06

 

Final Step

  • The ‘Change’ will be completed once the final ‘Implement Change’ step is signed off.
  • The status of the change will now move from Pending to Active.