Information technology service management (ITSM) are the activities performed by an organization to design, build, deliver, operate and control IT services offered to customers.[1]

Differing from more technology-oriented IT management approaches like network management and IT systems management,[2] IT service management is characterized by adopting a process approach towards management, focusing on customer needs and IT services for customers rather than IT systems, and stressing continual improvement. The CIO WaterCooler's 2017 ITSM report states that business uses ITSM "mostly in support of customer experience (35%) and service quality (48%)."[3]

Process

edit

Execution of ITSM processes in an organization, especially those processes that are more workflow-driven, can benefit significantly from being supported with specialized software tools.[4]

ITSM tools are often marketed as ITSM suites, which support a whole set of ITSM processes. At their core is usually a workflow management system for handling incidents, service requests, problems and changes. They usually also include a tool for a configuration management database (CMDB). The ability of these suites to enable easy linking between incident, service request, problem and change records with each other and with records of configuration items from the CMDB, can be a great advantage. ITSM tools and processes are commonly referred to as ITIL tools, when in fact they are not the same. More than 100 tools are self-proclaimed ITSM tools - example 'ITSM systems' include FreshService, ServiceNow and Samanage.[5] Software vendors whose ITSM tools fulfill defined functional requirements to support a set of ITIL processes, can obtain official approval, allowing them to use Axelos trademarks and an "ITIL process compliant" logo, under Axelos' ITIL Software Endorsement scheme.[6]

Service desk

edit

A service desk is a primary IT function within the discipline of IT service management (ITSM) as defined by ITIL. It is intended to provide a Single Point of Contact (SPOC) to meet the communication needs of both users and IT staff,[7] and also to satisfy both Customer and IT Provider objectives. User refers to the actual user of the service, while customer refers to the entity that is paying for the service. ITSM tools are frequently applied to other aspects of business, this practice is often called enterprise service management (ESM).[8] One of the big pushes in ITSM is automation of mundane tasks, this allows people who perform these tasks to take on more critical tasks, this process called IT process automation.

The ITIL approach considers the service desk to be the central point of contact between service providers and users/customers on a day-to-day basis. It is also a focal point for reporting incidents (disruptions or potential disruptions in service availability or quality) and for users making service requests (routine requests for services).[9]

ITIL regards a call centre or help desk as similar kinds of tech support which provide only a portion of what a service desk can offer. A service desk has a more broad and user-centered approach which is designed to provide the user with an informed single point of contact for all IT requirements. A service desk seeks to facilitate the integration of business processes into the service management infrastructure. In addition to actively monitoring and owning incidents and user questions, and providing the communications channel for other service management disciplines with the user community, a service desk also provides an interface for other activities such as customer change requests, third parties (e.g. maintenance contracts), and software licensing.[9] Computer emergency response teams (CERT) are specifically dedicated computer security incidents.

Frameworks

edit
 
Relationships between ITSM frameworks and other management standards

As a discipline, ITSM has ties and common interests with other IT and general management approaches, information security management and software engineering. Consequently, IT service management frameworks have been influenced by other standards and adopted concepts from them, e.g. CMMI, ISO 9000, or ISO/IEC 27000.[10]

Various frameworks for ITSM and overlapping disciplines include:

  • ITIL (Information Technology Infrastructure Library) is a set of detailed practices for IT activities such as IT service management (ITSM) and IT asset management (ITAM) that focus on aligning IT services with the needs of business.[11][2]
  • TOGAF is a framework and methodology that aims to define business goals while aligning them with architecture objectives related to software development.
  • Business Process Framework (eTOM) is a process framework for telecommunications service providers.
  • COBIT (Control Objectives for Information and Related Technologies) is an IT Governance framework that specifies control objectives, metrics and maturity models. Recent versions have aligned the naming of select control objectives to established ITSM process names.
  • FitSM[12] is a standard for lightweight service management. It contains several parts, including e.g. auditable requirements and document templates, which are published under Creative Common licenses. Its basic process framework is in large parts aligned to that of ISO/IEC 20000.
  • CMMI, guides all types of service providers to establish, manage, and improve services to meet business goals.
  • ASL's goal is the professional development of application management. This is achieved by offering a framework within which the processes of application management are brought in relation to each other.
  • USM,[13] the principle-based USM method provides a standardized management system for a service organization to manage its people, its processes, its technology, and its services, based on an explicit service management architecture.USM specifies the management system that supports the practice-based frameworks and standards and is adopted by Dutch government[14] for its management architecture.
  • ISO/IEC 20000 is an international standard for managing and delivering IT services. Its process model bears many similarities to that of ITIL version 2, since BS 15000 (precursor of ISO/IEC 20000) and ITIL were mutually aligned up to version 2 of ITIL. ISO/IEC 20000 defines minimum requirements for an effective "service management system" (SMS). Conformance of the SMS to ISO/IEC can be audited and organizations can achieve an ISO/IEC 20000 certification of their SMS for a defined scope.
  • BiSL is a framework of best practices for the Information Management domain.
  • MOF[15] (Microsoft Operations Framework) includes, in addition to a general framework of service management functions, guidance on managing services based on Microsoft technologies.

Professional organizations

edit

There are international, chapter-based professional associations, such as the IT Service Management Forum (itSMF),[16] and HDI. The main goal of these organizations is to foster the exchange of experiences and ideas between users of ITSM frameworks. To this end, national and local itSMF and HDI chapters (LIGs or local interest groups for itSMF) organize conferences and workshops. Some of them also contribute to the translations of ITSM framework documents into their respective languages or publish their own ITSM guides. There are several certifications for service management like ITILv4, TOGAF or COBIT.[17]

See also

edit

References

edit
  1. ^ "FitSM Part 0: Overview and vocabulary". Itemo. 24 August 2016. Archived from the original on 18 April 2019. Retrieved 27 November 2018.
  2. ^ a b Brenner, Michael; Garschhammer, Markus; Hegering, Heinz-Gerd (15 August 2006). "When Infrastructure Management Just Won't Do - The Trend Towards Organizational IT Service Management". In Eva-Maria Kern; Heinz-Gerd Hegering; Bernd Brügge (eds.). Managing Development and Application of Digital Technologies: Research Insights in the Munich Center for Digital Technology & Management. Springer Science & Business Media. pp. 131–146. ISBN 978-3-540-34129-1.
  3. ^ "The IT Service Management Survey 2017". Retrieved 28 November 2017.
  4. ^ "Brenner, M. Classifying ITIL Processes - A Taxonomy under Tool Support Aspects" (PDF). IEEE. 2006..
  5. ^ Jan van Bon. "(crowdsourced list of) ITIL tools". list.ly. Retrieved 29 January 2015..
  6. ^ "ITIL Software Scheme". Axelos. Retrieved 30 January 2015.
  7. ^ ITIL Service Design (2011), p. 22.
  8. ^ "Enterprise Service Management". Gartner. Retrieved 17 January 2023.
  9. ^ a b ITIL Service Design. The Stationery Office. 2011. ISBN 9780113313051. ITIL Service Operation. The Stationery Office. 2011. ISBN 978-0113313075.
  10. ^ "FitSM Foundation slides handout". Itemo.org. 1 May 2015. Archived from the original on 18 April 2019. Retrieved 30 July 2015.
  11. ^ "(crowdsourced list of) Alternatives to ITIL". list.ly, Jan van Bon. 3 February 2016. Retrieved 3 February 2016.
  12. ^ "FitSM". Itemo. Archived from the original on 9 August 2018. Retrieved 27 November 2018.
  13. ^ "USM Wiki". SURVUZfoundation. Retrieved 13 February 2024.
  14. ^ "USM en het Dienstverleningsconcept". NORA. Retrieved 13 February 2024.
  15. ^ "Microsoft Operations Framework". Microsoft.com. Retrieved 7 October 2012.
  16. ^ "itSMF International".
  17. ^ Shiff, Laura. "Popular IT Service Management (ITSM) Frameworks". BMC Blogs. Retrieved 12 December 2021.
edit