What is ITSM, and what is it for?
ITSM is the management, through defined processes, of the services IT provides to the company, that is, everything from user accounts to business applications and from hardware to network access. Requests do not get lost in email and phone traffic; each one is recorded, assigned to an owner and tracked against a target time.
The value of ITSM is visibility: how busy is IT and with what work, which faults recur, which change affected which system, which devices and licences does the company have? These questions are answered from records, not from guesswork.
- Which requests are open, and which are about to exceed their target time?
- Which faults recur, and what is their root cause?
- Which systems and users will a planned change affect?
- Which computers, devices and licences does the company have, and who has them?
- Are users satisfied with the service they receive?
What is ITIL, and is it the same as ITSM?
No. ITSM is a discipline; ITIL is the most widely used good-practice framework written for this discipline. ITIL is neither software nor a mandatory standard: it offers a common language and a set of practices for how services are designed and delivered. A company starts not with the whole of ITIL but by choosing the practices it needs.
Current versions of ITIL take service management beyond IT: PeopleCert’s ITIL catalogue also includes topics such as experience and AI governance. This shows that service management is now concerned not only with time but also with experience and with the oversight of AI.
The core processes of ITSM: with manufacturing as an example
The core processes of ITSM rest on the same principles regardless of the sector; how they are applied depends on how the business is organised. In businesses with warehouses, branches or production plants they also reach the field. The table below shows the core processes, taking a manufacturing company as the example; the examples are illustrative.
Configuration management keeps the components that make up an IT service, and the links between them, in a configuration management database (CMDB); IT asset management (ITAM) looks at the same hardware and software from the angle of ownership, licences and life cycle. In short, the CMDB answers what a change will affect, ITAM who has an asset and when it is due for renewal.
IT operations management (ITOM) is concerned with keeping the infrastructure running: it continuously monitors servers, the network and applications (monitoring), turns incoming alerts into meaningful events (event management) and automates recurring interventions. When an alert points to an outage that affects users, an incident record is opened automatically, so incident management often starts before a user calls.
| Process | What it does | Example from manufacturing |
|---|---|---|
| Service request | Fulfils a standard request | A user account for an operator starting on a shift |
| Incident management | Restores service after an interruption as quickly as possible | A label printer or handheld terminal on the line stopping |
| Problem management | Finds the root cause of recurring incidents | Frequent network outages on the same line |
| Change management | Plans a change with a risk assessment | An ERP or MES version upgrade |
| IT asset management (ITAM) | Records hardware, software and licences with their ownership and life cycle | Shop-floor computers, terminals and licences |
| Configuration management and the CMDB (configuration management database) | Tracks the components that make up a service and the links between them | Which MES server, terminals and network switch a production line depends on, and which lines a server change will affect |
| Knowledge management | Makes solutions reusable | A solution article for a common printer fault |
The difference between a help desk, a service desk and ITSM
These three concepts are often confused. A help desk focuses on solving the problem, a service desk on delivering the service; ITSM is the whole process and management system behind the service desk.
| Concept | Focus | Scope |
|---|---|---|
| Help desk | Solving the problem | Fault and question records |
| Service desk | Delivering the service, being the single point of contact | Requests, incidents and communication; the user-facing side |
| ITSM | Managing the whole life cycle of the service | Request, incident, problem, change, asset, knowledge and measurement |
Customer-facing support: the customer service and CX guide
ITSM, ESM and employee experience (EX): the differences and the link
Enterprise service management (ESM) is the application of methods proven in ITSM, that is, request logging, the service catalogue, approval workflows and target times, to departments outside IT. HR manages onboarding and leave requests, facilities management handles faults, purchasing handles approvals and legal handles contract requests with the same method; employees use a single portal for all of them.
Employee experience (EX) is the whole of the contacts an employee has with the company, and these services are an important part of it. A search for «employee experience software» often brings up HR survey and engagement tools; this page describes the service side of the experience: how easily a request is raised, how transparently it is tracked and how well it is resolved.
| Dimension | ITSM | ESM | Employee experience (EX) |
|---|---|---|---|
| Scope | IT services | Internal services outside IT | All of the employee’s contacts with the company |
| Who raises the request | The employee, for an IT service | The employee, for an HR, facilities, purchasing or legal service | The employees themselves, at every moment of their journey |
| Typical example | Access, fault, software installation | Onboarding, leave, facility fault, purchase approval | The journey from joining to leaving |
| Owner | IT | The department concerned | HR and management, together with the departments |
| How it is measured | Target times and service level | Target times per department | Experience and satisfaction indicators |
What are SLA, OLA and XLA?
Service levels can be defined through three different agreements. An SLA targets the promise made to the person receiving the service, an OLA the commitment between internal teams needed to keep that promise, and an XLA the experience the user has rather than time. Each company sets the target values according to its own services.
| Agreement | Parties | What it defines |
|---|---|---|
| SLA (service level agreement) | Service provider and user | Service targets such as response and resolution time |
| OLA (operational level agreement) | The internal teams that deliver the service together | The times each team commits to in order to keep the SLA |
| XLA (experience level agreement) | Service provider and user | Targets for how the user experiences the service |
Which metrics are tracked in ITSM?
Metrics are chosen according to the purpose of the service; the ones below are the most common, and the company sets the target values itself:
- first response time: the time until the request receives a first reply,
- resolution time: the time from the opening of a request until it is resolved,
- first-level resolution: requests resolved without being handed over to a specialist team,
- service level compliance: requests resolved within the target times,
- reopened requests: records marked as resolved and then reopened,
- recurring incidents: interruptions arising from the same root cause,
- user satisfaction: the rating given after the request is closed.
When is ITSM needed?
If several of the following signs are present, IT requests have outgrown what can be managed:
- requests arrive by email, by phone and in the corridor, and nobody knows where each one stands,
- the same fault happens again and again, but its root cause is not investigated,
- a system change breaks something in an unexpected place,
- there is no up-to-date list of the company’s devices and licences,
- HR, facilities and purchasing requests also run by email and cannot be tracked.
What to look for when choosing ITSM software
Run a trial with your own request types and ask these questions:
- Process coverage: is it a real ITSM tool, or an advanced help desk?
- ITIL alignment: are the incident, problem, change and asset processes linked to one another?
- ESM: can separate workspaces for HR, facilities and purchasing be opened from the same portal?
- Integration: are there documented connections to the user directory, ERP and, where relevant, MES?
- Asset management: can devices in offices, warehouses and on the shop floor be discovered and recorded?
- Language and data: is there a Turkish interface, in which region is the data held, and how is it assessed under KVKK?
- AI: do classification and reply suggestions work with human approval?
How is ITSM put into use?
Trying to set up everything at once is the most common mistake. A sound start is made with service request and incident management, that is, the processes users feel most; asset, change and problem management are added on top of them. ESM is rolled out department by department once the method has settled in IT.
The typical stages are: a service and request inventory, defining the service catalogue and target times, the portal and knowledge base, integration with the user directory and other systems, training and the start of measurement.
What does AI do in ITSM?
In ITSM, AI is used above all to classify requests and route them to the right team, to answer the user’s question from the knowledge base, and to offer the agent a summary and a draft reply. In risky steps such as approving a change or granting access, the decision must remain with a person.
MindDX and Freshservice
MindDX implements Freshservice in companies where the need for ITSM has been proven. Freshservice is an AI-supported service management platform built on ITIL best practices; IT service management, asset management, operations management and enterprise service management work on a shared data layer.
The role of MindDX is not limited to installing the software: it runs the service inventory, the design of the catalogue and target times, the integrations and the rollout of ESM to the departments within a single scope.