What is ITSM?
Overview
ITSM employs ITIL documented best practices and in most cases extends beyond into additional areas such as enhanced processes and implementation to provide additional value-added functionality. At present, ITSM methods have evolved to include specific ways to enable and optimize assessment, planning, and implementation of ITIL best practices.
Background
One primary origin of ITSM can be found in the systems management services and functions historically done in large scale mainframe environments. Through constant refinement over the years these services and functions attained a high level of maturity. Problem and change management, configuration management, capacity planning, performance management, disaster recovery, availability management, etc. are some examples.
When examining the differences between mainframe systems management services and ITSM, it becomes apparent that when ITSM is applied in today's IT environment and across the enterprise the benefits and sophistication of its best practices are highlighted and exemplified. Where mainframe environments are typically centralized, ITSM is applicable to both distributed and centralized environments. In addition, where mainframe services are typically stand-alone and technology based, ITSM provides for integrated services that are process based with a focus on satisfying business requirements.
Although managing the technology itself is a necessary component of most ITSM solutions, it is not a primary focus. Instead ITSM addresses the need to align the delivery of IT services closely with the needs of the business. This transformation of a traditional "business - IT paradigm" can be depicted by some of the following attributes:
|
Traditional I/T
|
becomes
|
ITSM Process
|
|
Technology focus
|
è
|
Process focus
|
|
"Fire-fighting"
|
è
|
Preventative
|
|
Reactive
|
è
|
Proactive
|
|
Users
|
è
|
Customers
|
|
Centralized, done in-house
|
è
|
Distributed, sourced
|
|
Isolated, silos
|
è
|
Integrated, enterprise-wide
|
|
"One off", adhoc
|
è
|
Repeatable, accountable
|
|
Informal processes
|
è
|
Formal best practices
|
|
IT internal perspective
|
è
|
Business perspective
|
|
Operational specific
|
è
|
Service orientation
|
Business objectives, service level objectives, technology infrastructure and other areas play critical roles in any ITSM method paradigm.
|