Recent from talks
Nothing was collected or created yet.
IT service management
View on Wikipedia
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]
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,[5] 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).[6] A key initiative in ITSM is the automation of routine tasks, enabling personnel to focus on higher-priority responsibilities; this is known as 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).[7]
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.[7] Computer emergency response teams (CERT) are specifically dedicated to computer security incidents.
Frameworks
[edit]
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.[8]
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.[9][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[10] 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,[11] 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[12] 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[13] (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),[14] 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.[15]
See also
[edit]References
[edit]- ^ "FitSM Part 0: Overview and vocabulary". Itemo. 24 August 2016. Archived from the original on 18 April 2019. Retrieved 27 November 2018.
- ^ 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.
- ^ "The IT Service Management Survey 2017". Retrieved 28 November 2017.
- ^ "Brenner, M. Classifying ITIL Processes - A Taxonomy under Tool Support Aspects" (PDF). IEEE. 2006..
- ^ ITIL Service Design (2011), p. 22.
- ^ "Enterprise Service Management". Gartner. Retrieved 17 January 2023.
- ^ a b ITIL Service Design. The Stationery Office. 2011. ISBN 9780113313051. ITIL Service Operation. The Stationery Office. 2011. ISBN 978-0113313075.
- ^ "FitSM Foundation slides handout". Itemo.org. 1 May 2015. Archived from the original on 18 April 2019. Retrieved 30 July 2015.
- ^ "(crowdsourced list of) Alternatives to ITIL". list.ly, Jan van Bon. 3 February 2016. Retrieved 3 February 2016.
- ^ "FitSM". Itemo. Archived from the original on 9 August 2018. Retrieved 27 November 2018.
- ^ "USM Wiki". SURVUZfoundation. Retrieved 13 February 2024.
- ^ "USM en het Dienstverleningsconcept". NORA. Retrieved 13 February 2024.
- ^ "Microsoft Operations Framework". Microsoft.com. Retrieved 7 October 2012.
- ^ "itSMF International".
- ^ Shiff, Laura. "Popular IT Service Management (ITSM) Frameworks". BMC Blogs. Retrieved 12 December 2021.
External links
[edit]
Media related to IT Service Management at Wikimedia Commons
IT service management
View on GrokipediaFundamentals
Definition and Scope
IT Service Management (ITSM) is defined as a set of specialized organizational capabilities for enabling value for customers in the form of services. This encompasses the practices, processes, and tools that allow organizations to deliver IT services that support business objectives and meet user needs effectively.[5][6] The primary objectives of ITSM include ensuring that IT services are reliable, cost-effective, and closely aligned with an organization's strategic goals. By focusing on service value—defined as the perceived benefits minus costs to customers—ITSM emphasizes customer satisfaction through consistent delivery and risk management to minimize disruptions. These objectives help organizations optimize resource use while enhancing overall operational efficiency and adaptability.[3][4] The scope of ITSM centers on the end-to-end service lifecycle, spanning planning, design, transition, delivery, and continual enhancement of services to meet evolving requirements. It excludes detailed aspects of hardware procurement or software development, concentrating instead on the management and provision of services to internal or external stakeholders. This boundary ensures ITSM integrates seamlessly with broader business processes without overlapping into pure technical engineering domains.[4][7] Key principles underpinning ITSM include customer-centricity, which prioritizes delivering value based on user expectations; continual improvement, achieved through ongoing monitoring and refinement of services; and integration with business processes to foster alignment and shared outcomes. These principles, often guided by frameworks like ITIL, promote a holistic approach to service management that evolves with organizational needs.[6][4]History and Evolution
IT service management (ITSM) originated in the 1980s amid the dominance of mainframe computing and the advent of early networking technologies, where IT departments focused primarily on maintaining system uptime and operational reliability to support burgeoning business dependencies on technology.[8] During this era, high costs associated with IT operations—often comprising 60%–90% of total cost of IT ownership—drove the need for structured processes to optimize resource use and minimize disruptions.[8] The British Government’s Central Computer and Telecommunications Agency (CCTA) recognized these challenges and initiated the development of the IT Infrastructure Library (ITIL) to provide a systematic framework for managing IT as a service, marking the formalization of ITSM as a discipline.[8] A key milestone came in 1989 with the publication of the first ITIL books by the CCTA, which outlined best practices for service support and delivery, influencing global IT operations by promoting process-oriented management.[9] In the 2000s, ITSM evolved with the rise of service-oriented architecture (SOA), shifting focus from siloed infrastructure to modular, business-aligned services that enhanced interoperability and agility.[10] Economic pressures in the early 2000s compelled organizations to emphasize return on investment for IT expenditures, fostering greater adoption of standardized ITSM approaches to demonstrate tangible business value. The 2010s brought further integration of agile methodologies and DevOps principles into ITSM, enabling continuous integration, faster feedback loops, and collaborative workflows between IT operations and development teams to accelerate service delivery.[11] Several drivers propelled this evolution, including the Y2K crisis at the turn of the millennium, which highlighted vulnerabilities in legacy systems and reinforced the importance of proactive risk assessment and compliance in IT management practices.[12] The emergence of cloud computing in the late 2000s and 2010s further transformed ITSM by introducing scalable, on-demand resources that required adaptive processes for hybrid environments and automated provisioning.[13] Following the 2020 COVID-19 pandemic, ITSM saw accelerated emphasis on digital transformation to enable remote workforces, alongside heightened integration of cybersecurity measures to safeguard distributed operations against rising threats.[14] Up to 2025, recent advancements have centered on AI-driven automation for predictive analytics and incident resolution, reducing resolution times by up to 50% in adopting organizations, with ServiceNow positioned as the sole Leader in the 2025 Gartner Magic Quadrant for AI Applications in IT Service Management. Meanwhile, sustainability initiatives promote energy-efficient practices and green IT strategies to align services with environmental goals.[15][16][17] ITIL's foundational role in standardizing these practices continues to underpin much of this progression.[9]Core Processes
Service Lifecycle Stages
The ITIL framework, particularly in its v3 iteration, structures IT service management around a service lifecycle comprising five interconnected stages that guide the creation, delivery, and ongoing refinement of IT services to align with business objectives. This lifecycle approach ensures that services are not static but evolve through systematic planning, implementation, operation, and improvement, fostering efficiency and value delivery. While ITIL v4 shifts emphasis toward a more holistic service value system, the core lifecycle concept from v3 remains influential in many implementations, providing a foundational model for iterative service management.[18] Service Strategy focuses on defining and aligning IT services with organizational goals, including market analysis, service portfolio management, and financial considerations to maximize value and return on investment. This stage involves assessing demand, developing strategies for service offerings, and establishing the economic viability of services to support business outcomes.[19] Service Design entails planning and designing new or modified services, including architectures, processes, policies, and metrics to ensure they meet business requirements while being cost-effective and secure. Key activities include capacity planning, availability management, and the creation of service level agreements (SLAs) that outline performance expectations.[19] Service Transition manages the building, testing, and deployment of services into the live environment, minimizing risks and disruptions through processes like change management, release management, and configuration control. This stage ensures that designed services are reliably transitioned to operations, often using a service design package as input.[18] Service Operation handles the day-to-day delivery and support of live services, maintaining stability and responsiveness through activities such as event management, incident resolution, and access control to fulfill SLAs and user needs. It emphasizes balancing new demands with existing service performance to deliver consistent value.[19] Continual Service Improvement provides a mechanism for ongoing evaluation and enhancement across all lifecycle stages, using metrics, audits, and the seven-step improvement process to identify gaps, measure performance against SLAs, and implement refinements for better efficiency and alignment with evolving business needs.[18] These stages form a continuous cycle rather than a linear process, with outputs from one feeding into the next and feedback loops—particularly through continual service improvement—enabling iterative adjustments based on performance data and changing requirements. For instance, operational insights from service operation inform redesign efforts, while strategic reviews in service strategy incorporate lessons from transitions and improvements.[19] Governance plays a pivotal role throughout the lifecycle, enforced via organizational policies, procedures, and oversight mechanisms like SLAs, which set measurable targets for service quality and availability across stages. These elements ensure accountability, risk mitigation, and alignment with broader business governance, with SLAs originating in design but monitored and adjusted in operation and improvement phases.[18]Key Operational Processes
Key operational processes in IT service management (ITSM) form the backbone of daily IT support and maintenance, enabling organizations to respond to disruptions, prevent recurrences, and manage modifications while aligning with business objectives. These processes emphasize tactical execution to minimize downtime and optimize service delivery, operating primarily within the service operation phase of the ITSM lifecycle. The core processes—Service Desk, Incident Management, Problem Management, and Change Management—work interdependently to handle user interactions, restore services, address underlying issues, and control alterations. The Service Desk functions as the single point of contact (SPOC) for all IT-related user queries, incidents, and service requests, streamlining communication and initial support.[20] It records details, provides basic troubleshooting, and routes issues to specialized teams, ensuring consistent user experience across channels like phone, email, or self-service portals.[21] Incident Management focuses on restoring normal service operation following an unplanned interruption or reduction in quality, prioritizing minimal business impact over root cause identification.[22] The process flow starts with incident identification and logging, capturing details such as symptoms, affected users, and timestamps.[23] Next, incidents are categorized by type (e.g., hardware failure or software error) and prioritized using an impact and urgency matrix, where impact assesses business effects like user numbers or revenue loss, and urgency evaluates resolution speed required.[24] This matrix typically yields priorities from low to critical, guiding resource allocation—for instance, a high-impact, high-urgency incident (e.g., widespread system outage) receives immediate attention.[25] Following prioritization, initial diagnosis occurs, followed by resolution attempts or escalation to higher support levels if needed; escalation procedures define functional (technical expertise) or hierarchical (supervisory) handoffs with predefined time thresholds.[23] The process concludes with closure, verifying user satisfaction and updating knowledge bases for future reference.[26] Problem Management addresses the root causes of one or more incidents to prevent recurrence, shifting from reactive fixes to proactive improvements.[27] It begins with problem identification, often triggered by incident trends or known errors, followed by logging and investigation using root cause analysis (RCA) techniques like the 5 Whys method, which iteratively questions underlying factors, or fault tree analysis for complex scenarios.[28] Once identified, solutions are developed—potentially via a change request—and implemented, with closure involving error prevention and documentation to reduce future incident volume.[29] Change Management ensures controlled implementation of alterations to IT services, infrastructure, or processes, assessing risks to avoid unintended disruptions.[30] The flow involves submitting a change request with details on scope and rationale, followed by impact and risk assessment by a change advisory board.[31] Approved changes are scheduled during low-impact windows, implemented with testing, and reviewed post-deployment to confirm success and capture lessons learned.[32] This structured approach categorizes changes as standard (low-risk, pre-approved), normal (requiring review), or emergency (urgent fixes).[31] Performance across these processes is evaluated using various key performance indicators (KPIs), particularly those tracking incident resolution trends over periods such as monthly or quarterly. These metrics help identify improvements, bottlenecks, and overall resolution performance trends. Key metrics include:- Average Time to Resolution (TTR) / Mean Time to Resolution (MTTR): the average duration from incident logging to restoration, benchmarking response efficiency—organizations often target under four hours for critical issues.[33]
- First Contact Resolution (FCR) Rate: the percentage of incidents resolved without escalation, typically aiming for 70-80% to enhance user satisfaction and reduce workload.[34]
- SLA Compliance Rate: the percentage of incidents resolved within agreed service level agreements, indicating adherence to performance commitments and trends in service reliability.[35]
- Incident Backlog: the number of unresolved incidents, highlighting trends in accumulation or reduction of pending work and potential workload bottlenecks.[36]
- Incidents Opened vs. Resolved: the comparison or ratio of incidents opened versus resolved over time, assessing whether resolution keeps pace with incoming volume and overall capacity.[37]
- Reopen Rate: the percentage of resolved incidents that are reopened, signaling trends in resolution quality, issue recurrence, and the effectiveness of root cause fixes.[35]
