Service Transition Flashcards
assembly
(ITIL Service Transition) A configuration item that is made up of a number of other CIs. For example, a server CI may contain CIs for CPUs, disks, memory etc.; an IT service CI may contain many hardware, software and other CIs. See also build; component CI.
asset management
(ITIL Service Transition) A generic activity or process responsible for tracking and reporting the value and ownership of assets throughout their lifecycle. See also service asset and configuration management; fixed asset management; software asset management.
asset register
(ITIL Service Transition) A list of fixed assets that includes their ownership and value. See also fixed asset management.
attribute
(ITIL Service Transition) A piece of information about a configuration item. Examples are name, location, version number and cost. Attributes of CIs are recorded in a configuration management database (CMDB) and maintained as part of a configuration management system (CMS). See also relationship; configuration management system.
back-out
(ITIL Service Transition) An activity that restores a service or other configuration item to a previous baseline. Back-out is used as a form of remediation when a change or release is not successful.
build
(ITIL Service Transition) The activity of assembling a number of configuration items to create part of an IT service. The term is also used to refer to a release that is authorized for distribution – for example, server build or laptop build. See also configuration baseline.
build environment
(ITIL Service Transition) A controlled environment where applications, IT services and other builds are assembled prior to being moved into a test or live environment.
change
(ITIL Service Transition) The addition, modification or removal of anything that could have an effect on IT services. The scope should include changes to all architectures, processes, tools, metrics and documentation, as well as changes to IT services and other configuration items.
change advisory board (CAB)
(ITIL Service Transition) A group of people that support the assessment, prioritization, authorization and scheduling of changes. A change advisory board is usually made up of representatives from: all areas within the IT service provider; the business; and third parties such as suppliers.
change evaluation
(ITIL Service Transition) The process responsible for formal assessment of a new or changed IT service to ensure that risks have been managed and to help determine whether to authorize the change.
change history
(ITIL Service Transition) Information about all changes made to a configuration item during its life. Change history consists of all those change records that apply to the CI.
change management
(ITIL Service Transition) The process responsible for controlling the lifecycle of all changes, enabling beneficial changes to be made with minimum disruption to IT services.
change model
(ITIL Service Transition) A repeatable way of dealing with a particular category of change. A change model defines specific agreed steps that will be followed for a change of this category. Change models may be very complex with many steps that require authorization (e.g. major software release) or may be very simple with no requirement for authorization (e.g. password reset). See also change advisory board; standard change.
change record
(ITIL Service Transition) A record containing the details of a change. Each change record documents the lifecycle of a single change. A change record is created for every request for change that is received, even those that are subsequently rejected. Change records should reference the configuration items that are affected by the change. Change records may be stored in the configuration management system, or elsewhere in the service knowledge management system.
change schedule
(ITIL Service Transition) A document that lists all authorized changes and their planned implementation dates, as well as the estimated dates of longer-term changes. A change schedule is sometimes called a forward schedule of change, even though it also contains information about changes that have already been implemented.
change window
(ITIL Service Transition) A regular, agreed time when changes or releases may be implemented with minimal impact on services. Change windows are usually documented in service level agreements.
CI type
(ITIL Service Transition) A category that is used to classify configuration items. The CI type identifies the required attributes and relationships for a configuration record. Common CI types include hardware, document, user etc.
configuration
(ITIL Service Transition) A generic term used to describe a group of configuration items that work together to deliver an IT service, or a recognizable part of an IT service. Configuration is also used to describe the parameter settings for one or more configuration items.
configuration baseline
(ITIL Service Transition) The baseline of a configuration that has been formally agreed and is managed through the change management process. A configuration baseline is used as a basis for future builds, releases and changes.
configuration control
(ITIL Service Transition) The activity responsible for ensuring that adding, modifying or removing a configuration item is properly managed – for example, by submitting a request for change or service request.
configuration identification
(ITIL Service Transition) The activity responsible for collecting information about configuration items and their relationships, and loading this information into the configuration management database. Configuration identification is also responsible for labeling the configuration items themselves, so that the corresponding configuration records can be found.
configuration item (CI)
(ITIL Service Transition) Any component or other service asset that needs to be managed in order to deliver an IT service. Information about each configuration item is recorded in a configuration record within the configuration management system and is maintained throughout its lifecycle by service asset and configuration management. Configuration items are under the control of change management. They typically include IT services, hardware, software, buildings, people and formal documentation such as process documentation and service level agreements.
configuration management database (CMDB)
(ITIL Service Transition) A database used to store configuration records throughout their lifecycle. The configuration management system maintains one or more configuration management databases, and each database stores attributes of configuration items, and relationships with other configuration items.
configuration management system (CMS)
(ITIL Service Transition) A set of tools, data and information that is used to support service asset and configuration management. The CMS is part of an overall service knowledge management system and includes tools for collecting, storing, managing, updating, analyzing and presenting data about all configuration items and their relationships. The CMS may also include information about incidents, problems, known errors, changes and releases. The CMS is maintained by service asset and configuration management and is used by all IT service management processes. See also configuration management database.
configuration record
(ITIL Service Transition) A record containing the details of a configuration item. Each configuration record documents the lifecycle of a single configuration item. Configuration records are stored in a configuration management database and maintained as part of a configuration management system.
configuration structure
(ITIL Service Transition) The hierarchy and other relationships between all the configuration items that comprise a configuration.
Data-to- Information-to- Knowledge-to- Wisdom (DIKW)
(ITIL Service Transition) A way of understanding the relationships between data, information, knowledge and wisdom. DIKW shows how each of these builds on the others.