System Guides

Change request management is a pivotal process within organizations, enabling the controlled and efficient handling of requested changes to services, systems, processes, or infrastructure. It offers a structured approach to managing change requests, ensuring they undergo proper evaluation, approval, and implementation to minimize disruptions and maximize business value.

The Change Management Request feature in CIMSNex streamlines the process of managing change requests, encompassing their submission, approval, and verification. This feature ensures thorough documentation and control of changes within an organization. Below is a comprehensive guide to help users navigate the fields within the Change Management Request feature of CIMSNex:

Change Management Request:

1. Request No.: This field represents the unique identifier or reference number assigned to the change request. It helps in tracking and identifying the specific request.

2. Date: This field captures the date when the change request was raised.

3. Business Service: This field identifies the specific business service or process that is impacted or associated with the change request.

4. Source: In this field, select the statndard of your certiticateion e.g IT Service requirememnt depending on the change.

5. Raised by: This field captures the name or identity of the person who raised the change request.

6. Change Type: This field specifies the general category or classification of the change i.e. "Emergency Change," or "Major Change."

7. Change Type Desc: This field provides a brief description or explanation of the selected change type.

8. Change Request Reason: This field allows the user to specify the reason or justification for the change request, providing context for the requested change.

9. Details: This field provides a space for the user to provide additional details or information about the change request reason.

10. Brief Activities: This field allows the user to provide a summary or overview of the planned activities or steps associated with implementing the change.

11. Timeline: This field captures the proposed timeline or schedule for executing the change request, including start and end dates.

12. Consequence of Change: This field assesses the potential consequences or impact of the change on the business or affected processes. It may be categorized as low, medium, or high.

13. Likelihood of Consequence: This field evaluates the likelihood or probability of the identified consequences occurring as a result of the change. It may be categorized as low, medium, or high.

14. Follow back Plan: This field outlines the plan or strategy for monitoring and evaluating the implemented change, including any fallback options or contingency measures if needed.

Change Approval:

To approve change request, select one option i.e. Approved/ Rejected and Give a Comment

Change Verification:

1. Completion Date: Enter the date when the change request is completed.

2. Completed by: Specify the individual or team responsible for completing the change request.

3. Remarks: Add any relevant comments or notes regarding the completion of the change request.

4. Upload Support Document: Attach any supporting documents related to the change request, if applicable.

By following these guidelines and providing accurate information in each field, you can effectively manage change requests and ensure proper evaluation and documentation throughout the change management process.