Search the Community
Showing results for tags 'Impact'.
Found 2 results
I understand the implementation of Impact and Urgency in Service Manager is a existing development story. At the moment in Support Works we capture Impact and Urgency as part of our request logging process, but we do not use the SLA Matrix to calculate the priority (i.e. we have an empty SLA Matrix). Is there a rough timescale on the development story for Impact and Urgency, particularly the standard form in the Progressive Capture to capture their values? Cheers Martyn
Impact Assessments Capturing the impact of a change, an incident, or any other type of request can be crucial to determining how it is managed. But how do you decide which impact level to select? Service Manager provides a great way of automatically determining the impact level to be applied. Taking the guessing out of the hands of the user, they can be walked through a number of questions where each answer has a weighted value that contributes to the automatic selection of the impact level. The results of the assessment are captured in the request along with the automatic application of the impact level. At any point after the assessment, if things change or a mistake is found, a reassessment of the impact can be completed. The assessments are managed as part of a Business Process which allows them to be presented to a user at any given point within the workflow. When defining your workflow, you can easily select from any number of available assessments that you wish to present.