IT service management (ITSM) comprises the development, provision, management, measures and methods for supporting business processes through IT service. ITIL (IT Infrastructure Library) has emerged as the standard in this regard. It is a framework that provides a best practices process model for aligning IT with business requirements. The most widely used frameworks are ITIL v3 and ITIL 2011. ITIL covers a wide range of IT services, from disaster recovery to network management. The abbreviation SOA stands for Service Offerings and Agreements within ITIL Services as well as for service-oriented architecture in the area of IT service management.
In this SoftGuide section, you will find an overview of software and solutions for IT service management and ITIL. The software helps you to obtain secure and detailed information about the IT infrastructure required to deliver IT services and improve process quality, and ensures that IT provides the best possible support for business processes. As a rule, ITSM software offers options for adapting process models and integrating them into any enterprise process model. As a rule, the requirements of ISO 20000 are also met.
IT service management generally comprises a set of procedures, measures and methods for the development, provision and management of IT services for the company, its employees or its customers. IT service management includes all processes related to planning, compilation of hardware and software, delivery and support. IT services can include virtually any IT resource (hardware, software, computing resource). ITSM is therefore a very general term.
There are various norms, frameworks and standards for IT service management, such as ISO/IEC 20000, the Business Process Framework, COBIT or ITIL for ITSM.
The international standard ISO/IEC 20000 on IT service management specifies the minimum requirements for processes that an organization must establish in order to provide and manage a defined quality for IT services.
The following requirements and processes are defined by ISO/IEC 20000:
The Business Process Framework eTOM forms a framework for business processes of companies and service providers in the telecommunications industry. It is published by TM Forum as a consortium of telecommunication providers. eTOM has a data model for each detailed process.
COBIT (Control Objectives for Information and Related Technology) is a framework for IT governance. The framework divides the tasks of IT into processes and control objectives. Among other things, COBIT is used as a model for ensuring compliance with legal requirements.
ITIL is the abbreviation of Information Technology Infrastructure Library. It was developed in the early 1980s and has been a registered trademark of AXELOS Ltd, a joint venture of Capita Plc and the Cabinet Office of the British government, since 2014.
ITIL is, in a sense, the standard for ITSM. In ITIL 4, 34 best practices are described. This version ITIL 4 was published in 2019. Also widely used are the 5 ITIL disciplines and 26 ITIL version 3 processes. While ITIL V3 defined the service lifecycle and the corresponding processes, ITIL 4 focuses on principles, concepts and practices. The goal of an organization is to achieve the highest possible service quality in the IT area by means of ITIL. Among other things, ITIL provides a common terminology for IT service management.
The best practices are divided into general management practices, service management practices and technical management practices.
The ITSM software supports IT teams of companies and organizations as well as managed service providers in the planning, design, development and monitoring as well as the continuous provision of IT services. The ITSM processes that ITSM tools map include software release and deployment management, incident management, change management, knowledge management and problem management. ITSM software can be used to manage internal IT and users as well as external IT and users.
The benefits of using ITSM software lie both in improving the efficiency of operational processes and in enhancing customer service. By means of ITSM software, numerous IT processes can be standardized. A regulated IT environment with appropriate policies not only protects against internal and external threats, but also ensures optimal utilization of IT resources.
Improving customer service is achieved through effective use of IT service management software. Customer or user problems can be better tracked by using proven and standardized procedures. As a rule, solutions to problems are found more quickly by means of an ITSM tool.
With the use of ITSM software, modules for vulnerability analysis, predictive analysis and for problem management are usually also available. These modules can help prevent incidents and thus reduce downtime. Using ITSM software, problems can be identified at an early stage and any downtime can be prevented. In addition, emergency plans can be created and implemented.
Change management maps any type of change to an IT infrastructure and IT services. Change management is always called upon when a change request is received. This is then classified, the priority and the impact determined. A decision is then made about the change, and planning and testing, as well as release and execution, take place. Depending on the scope of the desired change, change management works closely with release management and project management. Change management is part of the productive area, which is important for service delivery.
Configuration Management maps service assets and configuration items (CIs). Configuration Management identifies and catalogs, stores, and monitors CIs. Through effective collaboration with Service Management, Configuration Management provides accurate information about CIs. All data required by ITSM processes can be found in Configuration Management. Configuration Management interfaces with all other ITSM processes. Configuration Management is also the place where it is stored which support team is responsible for which incident category.
Incident management comprises the concept and the tools for mapping a process to eliminate incidents as efficiently as possible within the agreed service levels. Incidents are usually received and classified via a service desk. The handling of incidents is also represented via the service desk. Incidents can be technical problems and vulnerabilities as well as specific attacks on the organization's IT infrastructure.
Problem management is used for a holistic service management approach. Incidents are analyzed and problem management ensures that minor disruptions do not develop into permanent major disruptions. Problem management works closely with change management to achieve this. Problem management can be divided into reactive and preventive problem management. In preventive problem management, the IT service is checked for weak points in order to exclude incidents that have already been identified in advance as far as possible. In reactive problem management, the reasons for incidents are investigated and proposals are drawn up for preventing incidents for precisely these reasons. The area of problem management also includes, among other things, the development of a knowledge database.
Service Request Management maps user requests via a service desk and assigns a corresponding urgency to the request and supports processing. The nature of the requests varies widely. For example, requests can relate to registration processes, software or hardware upgrades, application access or contract and project inquiries. The goal of service request management is to ensure user satisfaction. Service Request Management ensures that regular information is provided to the user.
Release management is closely related to change management. It is designed to provide new or updated IT services or CIs while ensuring that integrity and functionality are maintained. The functions of this ITSM module include the release of a new software or hardware product, the release of a new version of the software or hardware, and the release of an IT service with new functions. Release management is intended to minimize the risk of interruption to business processes resulting from inadequately tested or incorrectly planned system configurations or components.
Continuous process improvement relies on quality management methods to constantly improve the effectiveness and efficiency of IT services and avoid the repetition of errors. ISO 20000 is also used in this area of continuous process improvement. The aim is to establish, operate and permanently improve standardized processes for mapping IT services and the IT infrastructure. Continuous process improvement is intended to make the cost-benefit ratio of IT services as optimal as possible for companies and customers.
Service Level Management is used to define, optimize and monitor IT services. The aim of SLM is to design and ensure that IT services are in line with customer expectations. Service Level Management defines the framework for service levels and service quality. The development and specification of service level agreements (SLAs) ensures that the customer specifies its requirements and expectations with regard to IT services. The most important tasks in service level management are the creation of quality plans, the management of the IT service catalog, the development and management of supporting agreements, and the regular and continuous monitoring and evaluation of SLAs in terms of target achievement and costs.
The aim of capacity management is to provide sufficient IT service and IT infrastructure capacities while taking cost-effectiveness into account. Resource planning is carried out for the short and medium term as well as for the long term. Capacity management also ensures that the capacity level required by the customer is compared with that of the existing operating resources and the resources already planned.
Availability management encompasses the definition, planning, measurement, evaluation and improvement of all measures that are essential for ensuring the availability of the defined IT services. Ensuring availability is practically the core task of IT service management. Availability management includes the identification and definition of internal and external availability requirements. The basis for availability is that the required SLAs must be reconciled with corresponding costs and efforts.
Information security management includes the identification and definition of internal and external security requirements, the planning of security procedures and the corresponding description and implementation management. The goal is to achieve a defined security level. A risk analysis serves as a start for defining the security level. The internal, minimum security requirement is the so-called IT baseline protection.
Another component of the ITSM software is reporting management. Report management is triggered when a corresponding request is received from one of the processes. Each report request is classified and processed according to urgency and priority. The goal of report management is to standardize procedures for IT reporting requests. Among other things, the reports document service delivery and its quality and also ensure legal functions.
More tips and question suggestions for evaluating ITSM software: