Robust Change Management

Robust Change Management

All mature IT operations must manage their changes.

 

One of Samantha's™ strengths is its configuration-based Change Process Workflow. Request for Changes (RFCs) are tied to the Configuration Item (CI) which is being changed. 

 

The RFC includes standard information on the scheduled date / time, description, risk level, and justification. Round-out the change with test plans, readiness plans, an impact assessment, and communications plans. Optionally, link your change to your Service Desk request with integration to products like Numara Footprints. We support recurring changes, self-approved changes, notice periods, change windows, review delays, and moratoriums. 

 

The Process Workflow tracks Proposed, Approved, Scheduled, and Completed changes. Completing the change requires documentation, actual start and stop times, asset downtime, planning time and a self-rating of how the change was complete. You are not done though until the change is rated and closed. The closing process allows you to rate the effectiveness of the change, save the change to the knowledgebase, and tie the change to your Strategies. 

 

Automated communications send e-mails as changes are proposed, scheduled and completed. 

 

Native governance-checking indicates changes without CAB review, without adequate notice, outside of a change window, or within a moratorium. Statistical measures include percentages on Cumulative Ratings, Normal, Urgent and Past changes. 

 

Build on your system, using your change data to compute availability. To meet SOX and audit requirements, rely on Complex Change Rules. Once you really get rolling, analyze your changes to predict their impact. 

 

Calendar views, dashboards, and reporting gives you the control you need over the leading source of downtime - IT changes.

 

Robust Change Management

All mature IT operations must manage their changes.

 

One of Samantha's™ strengths is its configuration-based Change Process Workflow. Request for Changes (RFCs) are tied to the Configuration Item (CI) which is being changed. 

 

The RFC includes standard information on the scheduled date / time, description, risk level, and justification. Round-out the change with test plans, readiness plans, an impact assessment, and communications plans. Optionally, link your change to your Service Desk request with integration to products like Numara Footprints. We support recurring changes, self-approved changes, notice periods, change windows, review delays, and moratoriums. 

 

The Process Workflow tracks Proposed, Approved, Scheduled, and Completed changes. Completing the change requires documentation, actual start and stop times, asset downtime, planning time and a self-rating of how the change was complete. You are not done though until the change is rated and closed. The closing process allows you to rate the effectiveness of the change, save the change to the knowledgebase, and tie the change to your Strategies. 

 

Automated communications send e-mails as changes are proposed, scheduled and completed. 

 

Native governance-checking indicates changes without CAB review, without adequate notice, outside of a change window, or within a moratorium. Statistical measures include percentages on Cumulative Ratings, Normal, Urgent and Past changes. 

 

Build on your system, using your change data to compute availability. To meet SOX and audit requirements, rely on Complex Change Rules. Once you really get rolling, analyze your changes to predict their impact. 

 

Calendar views, dashboards, and reporting gives you the control you need over the leading source of downtime - IT changes.

 

Robust Change Management

All mature IT operations must manage their changes.

 

One of Samantha's™ strengths is its configuration-based Change Process Workflow. Request for Changes (RFCs) are tied to the Configuration Item (CI) which is being changed. 

 

The RFC includes standard information on the scheduled date / time, description, risk level, and justification. Round-out the change with test plans, readiness plans, an impact assessment, and communications plans. Optionally, link your change to your Service Desk request with integration to products like Numara Footprints. We support recurring changes, self-approved changes, notice periods, change windows, review delays, and moratoriums. 

 

The Process Workflow tracks Proposed, Approved, Scheduled, and Completed changes. Completing the change requires documentation, actual start and stop times, asset downtime, planning time and a self-rating of how the change was complete. You are not done though until the change is rated and closed. The closing process allows you to rate the effectiveness of the change, save the change to the knowledgebase, and tie the change to your Strategies. 

 

Automated communications send e-mails as changes are proposed, scheduled and completed. 

 

Native governance-checking indicates changes without CAB review, without adequate notice, outside of a change window, or within a moratorium. Statistical measures include percentages on Cumulative Ratings, Normal, Urgent and Past changes. 

 

Build on your system, using your change data to compute availability. To meet SOX and audit requirements, rely on Complex Change Rules. Once you really get rolling, analyze your changes to predict their impact. 

 

Calendar views, dashboards, and reporting gives you the control you need over the leading source of downtime - IT changes.

 

All mature IT operations must manage their changes.

 

One of Samantha's™ strengths is its configuration-based Change Process Workflow. Request for Changes (RFCs) are tied to the Configuration Item (CI) which is being changed. 

 

The RFC includes standard information on the scheduled date / time, description, risk level, and justification. Round-out the change with test plans, readiness plans, an impact assessment, and communications plans. Optionally, link your change to your Service Desk request with integration to products like Numara Footprints. We support recurring changes, self-approved changes, notice periods, change windows, review delays, and moratoriums. 

 

The Process Workflow tracks Proposed, Approved, Scheduled, and Completed changes. Completing the change requires documentation, actual start and stop times, asset downtime, planning time and a self-rating of how the change was complete. You are not done though until the change is rated and closed. The closing process allows you to rate the effectiveness of the change, save the change to the knowledgebase, and tie the change to your Strategies. 

 

Automated communications send e-mails as changes are proposed, scheduled and completed. 

 

Native governance-checking indicates changes without CAB review, without adequate notice, outside of a change window, or within a moratorium. Statistical measures include percentages on Cumulative Ratings, Normal, Urgent and Past changes. 

 

Build on your system, using your change data to compute availability. To meet SOX and audit requirements, rely on Complex Change Rules. Once you really get rolling, analyze your changes to predict their impact. 

 

Calendar views, dashboards, and reporting gives you the control you need over the leading source of downtime - IT changes.