Section 9 Flashcards
Change Enablement
Maximizes the number of successful IT changes by ensuring that risks have been properly assessed, authorizing changes to proceed, and managing the change schedule.
Incident Mangement
Minimizes the negative impact of incidents by restoring normal service operation as quickly as possible.
Problem Management
Reduces the likelihood and impact of incidents by identifying actual and potential causes of incidents, and managing workarounds and known errors.
Service Desk
Capture demand for incident resolution and service requests.
Service Level Management
Sets clear business-based targets for service performance so that the delivery of a service can be properly assessed, monitored, and managed against these targets.
Service Request Management
Supports the agreed quality of a service by handling all predefined, user-initiated service requests in an effective and user-friendly manner.
IT Asset Management
To plan and manage the full lifecycle of all IT assets, to help the organization:
- Maximize value.
- Control costs.
- Manage risks.
- Support decision-making about purchase, re-use, and retirement of assets.
- Meet regulatory & contractual requirements.
Monitoring & Event Management
Systematically observes a service or service component, and record and report selected changes of state identified as events.
Release Management
To make new and changed services and features available for use.
Service Configuration Management
Ensure that accurate and reliable information about the configuration of services, and the CIs that support them, is available when and where it is needed.
What are the two things Change Enablement needs to balance?
- The beneficial effects of changes.
- Protecting ourselves against the adverse effects of changes.
Anytime you change something you introduce a risk of failure.
Change
Addition, modification, or removal of anything taht could have a direct or indirect effect on IT services.
What are the three types of changes?
- Standard (pre-authorized; low-risk & well-understood. e.g. a password reset request).
- Normal (require some level of authorization based on the level of change. planned & scheduled in advance. e.g. a server upgrade from 2018 to 2019).
- Emergency (have an expedited assessment & authorization process. A change that must be introduced as soon as possible. Failure to plan is not an emergency change. e.g. service failure.).
Change Authority
A person or group responsible for authorizing a change.
Change Schedule
Used to help plan, changes, assist in communication, avoid conflicts, and assign resources.