Pages

Friday, December 6, 2019

ITIL® v3 Glossary and Abbreviations- Learning Module #1


1. Acceptance:


Formal agreement that an IT service, process, plan or other deliverable is complete, accurate, reliable and meets its specified requirements. Acceptance is usually preceded by change evaluation or testing and is often required before proceeding to the next stage of a project or process. See also service acceptance criteria.


2. Access Management


(ITIL Service Operation) The process is responsible for allowing users to make use of IT services, data, or other assets. Access management helps to protect the confidentiality, integrity, and availability of assets by ensuring that only authorized users are able to access or modify them. Access management implements the policies of information security management and is sometimes referred to as rights management or identity management.


3. Account manager


(ITIL Service Strategy) A role that is very similar to that of the business relationship manager, but includes more commercial aspects. Most commonly used by Type III service providers when dealing with external customers.


4. Accounting


The Process responsible for identifying actual Costs of delivering IT Services, comparing these with budgeted costs, and managing variance from the Budget.


5. Accounting period


(ITIL Service Strategy) A period of time (usually one year) for which budgets, charges, depreciation, and other financial calculations are made. See also financial year. 


6. Accredited


Officially authorized to carry out a role. For example, an accredited body may be authorized to provide training or to conduct audits. 


7. Active Monitoring


(ITIL Service Operation) Monitoring of a configuration item or an IT service that uses automated regular checks to discover the current status. See also passive monitoring.


8. Activity


A set of actions designed to achieve a particular result. Activities are usually defined as part of processes or plans and are documented in procedures.


9. Agreed service time (AST)


(ITIL Service Design) A synonym for service hours, commonly used in formal calculations of availability. See also downtime.


10. Agreement


A document that describes a formal understanding between two or more parties. An agreement is not legally binding unless it forms part of a contract. See also operational level agreement; service level agreement.


11. Alert


(ITIL Service Operation) A notification that a threshold has been reached, something has changed, or a failure has occurred. Alerts are often created and managed by system management tools and are managed by the event management process.


12. Analytical Modeling


(ITIL Continual Service Improvement) (ITIL Service Design) (ITIL Service Strategy) A technique that uses mathematical models to predict the behavior of IT services or other configuration items. Analytical models are commonly used in capacity management and availability management.


13. Application 


Software that provides functions that are required by an IT service. Each application may be part of more than one IT service. An application runs on one or more servers or clients.


14. Application Management


(ITIL Service Operation) The function is responsible for managing applications throughout their lifecycle.


15. Application Portfolio


(ITIL Service Design) A database or structured document used to manage applications throughout their lifecycle. The application portfolio contains key attributes of all applications. The application portfolio is sometimes implemented as part of the service portfolio, or as part of the configuration management system.


16. Application service provider (ASP)


(ITIL Service Design) An external service provider that provides IT services using applications running at the service provider’s premises. Users access the applications by network connections to the service provider.


17. Application sizing


(ITIL Service Design) The activity is responsible for understanding the resource requirements needed to support a new application or a major change to an existing application. Application sizing helps to ensure that the IT service can meet its agreed service level targets for capacity and performance.


18.Architecture


(ITIL Service Design) The structure of a system or IT service, including the relationships of components to each other and to the environment they are in. Architecture also includes the standards and guidelines that guide the design and evolution of the system.


19. 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.


20. Assessment


Inspection and analysis to check whether a standard or set of guidelines is being followed, that records are accurate, or that efficiency and effectiveness targets are being met. See also audit.


21. Asset


(ITIL Service Strategy) Any resource or capability. The assets of a service provider include anything that could contribute to the delivery of a service. Assets can be one of the following types: management, organization, process, knowledge, people, information, applications, infrastructure or financial capital. See also customer asset; service asset; strategic asset.


22. 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.


23. Asset Register


(ITIL Service Transition) A list of fixed assets that includes their ownership and value. See also fixed asset management.


24. Asset Specificity


(ITIL Service Strategy) One or more attributes of an asset that make it particularly useful for a given purpose. Asset specificity may limit the use of the asset for other purposes.


25. Attribute


(ITIL Service Transition) A piece of information about a configuration item. Examples are a 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.


26. Audit


Formal inspection and verification to check whether a standard or set of guidelines is being followed, that records are accurate, or that efficiency and effectiveness targets are being met. An audit may be carried out by internal or external groups. See also assessment; certification.



27. Authority Matrix


See RACI.


28. Automatic call distribution (ACD)


(ITIL Service Operation) Use of information technology to direct an incoming telephone call to the most appropriate person in the shortest possible time. ACD is sometimes called automated call distribution.


29. Availability


(ITIL Service Design) The ability of an IT service or another configuration item to perform its agreed function when required. Availability is determined by reliability, maintainability, serviceability, performance, and security. Availability is usually calculated as a percentage. This calculation is often based on agreed service time and downtime. It is best practice to calculate the availability of an IT service using measurements of the business output.


30. Availability management (AM)


  1. (ITIL Service Design) The process is responsible for ensuring that IT services meet the current and future availability needs of the business in a cost-effective and timely manner. Availability management defines, analyses, plans, measures and improves all aspects of the availability of IT services, and ensures that all IT infrastructures, processes, tools, roles etc. are appropriate for the agreed service level targets for availability management information system (AMIS) availability. See also availability management information system.


31. Availability management information system (AMIS)


(ITIL Service Design) A set of tools, data, and information that is used to support availability management. See also service knowledge management system.



32. Availability Plan


(ITIL Service Design) A plan to ensure that existing and future availability requirements for IT services can be provided cost-effectively.


                                                               NEXT 




No comments:

Post a Comment