Classifying Changes

effective change enablement involves the proper processing of requests for change usually, a change is driven by a configuration item that has been identified in need of a change the configuration item is usually the purpose for a change sometimes a graphical representation of the personnel, organization structure, and equipment can determine how a change can affect the organization see working with the ci map docid\ ahauampatmiw4efhud6ws standard change templates are used for preapproved standardized types of changes these changes bypass the approval process s, however, always have the option of classifying some standard changes as major or emergency, thereby making the change go through an approval process after a non standard change has been requested, the assesses the risk, the impact, the cost, and other factors that determine whether the change is feasible or not after a change goes into the requested status, the can decide whether the change should go forward, get deferred, or denied the can determine the risk associated with the change (see setting the risk level for a change docid\ tne5dflsi1ffxjaje4pfl ) the can also view the ci map for a visual of the services that may be impacted by or impact the change changing urgency, impact, and priority s can prioritize the change based on urgency and impact by default, prioritizes change requests based on the following impact the extent to which the loss of service will impact the business organization for example, if a single application is down, it will have less business impact than a server being down urgency the affected user's tolerance for a delay in the resolution urgency is usually time related for example, the loss of the sales department's network printer before the end of the fiscal quarter might be assigned a greater urgency than at another time priority the order in which it needs to be resolved, based on the impact and urgency the default priority values are calculated as follows urgency high medium low impact high 1 2 3 medium 2 3 4 low 3 4 5 the priority is automatically calculated by the application and appears in the change record change urgency and impact change type fields based on itil change enablement categories, s allow s to categorize changes as follows category description minor small changes that have a minor impact on the organization emergency urgent changes that must be made emergency changes are typically implemented first and created after the change has been made due to the urgent nature of the change as a result, emergency changes are typically posted to the calendar after the change has been made for auditing purposes major these changes usually consist of a great number of items or dependencies and can also lead to other associated change requests significant these changes have a large significant impact on the organization standard these changes are routine, understood, and generally accepted that the entire organization understands as necessary for normal operations as a result, the approval board does not need to meet and accept a standard change changes of this type are generally performed on a regular basis and are preapproved some of the changes that are created from a service request fall into this category the customer is already entitled to the service, so approval is not necessary