| |
|||||||
![]() |
|||||||
| |
|||||||
|
|
|
|||||
Definitions and Terminology
A
B C
D E
F G
H I
J K
L M
N O
P Q
R S
T U
V W
X Y
Z Urgency(Service Transition) (Service Design) A measure of how long it will be until an Incident, Problem or Change has a significant Impact on the Business. For example a high Impact Incident may have low Urgency, if the Impact will not affect the Business until the end of the financial year. Impact and Urgency are used to assign Priority . source: ITIL v3, Service Operation, 2007 (Service Transition) (Service Design) A measure of how long it will be until an Incident, Problem or Change has a significant Impact on the Business. For example a high Impact Incident may have low Urgency, if the Impact will not affect the Business until the end of the financial year. Impact and Urgency are used to assign Priority. source: ITIL v3, Service Design, 2007 (Service Transition) (Service Design) A measure of how long it will be until an Incident, Problem or Change has a significant Impact on the Business. For example, a high Impact Incident may have low Urgency, if the Impact will not affect the Business until the end of the financial year. Impact and Urgency are used to assign Priority. source: ITIL v3, Service Transition, 2007 (Service Transition) (Service Design) A measure of how long it will be until an Incident, Problem or Change has a significant Impact on the Business. For example a high Impact Incident may have low Urgency, if the Impact will not affect the Business until the end of the financial year. Impact and Urgency are used to assign Priority. source: ITIL v3, Continual Service Improvement, 2007
|
|
||||||
|
|||||||