Service Level Management
Service Asset e Configuration Management
IT Financial Management
Background System Management
Automazione dei Processi IT
Gestione automatica degli incidenti
Distribuzione del Software
Implementazione e Monitoraggio
Avviso e Notifiche
IT Health Status
Dashboards in tempo reale
Monitoraggio dell'esperienza digitale
Consulta il blog di EasyVista per essere sempre aggiornato sulle ultime novità, tendenze e best practice della trasformazione digitale. Lascia che EasyVista ti tenga aggiornato e all'avanguardia in un settore in continua evoluzione.
Ci impegniamo a fornire risorse che ti aiutino a soddisfare tutte le tue esigenze di software ITSM.
Rimani aggiornato sui nostri ultimi webinar ed eventi ITSM, ITOM o ESM ora.
Less incidents, please!
An incident is defined as an unplanned interruption to a service or reduction in the quality of service. Incidents are identified by end users and reported to customer service teams via an IT self-service portal, phone call, or an email.
An incident is an issue affecting one or more employees, customers, third parties, business processes or services, or another entity that can be adversely affected by your organization’s technology—or technology-based services—not working as they should. For example, a faulty laptop and an inaccessible business application are both classified as incidents. Both example issues (or incidents) are likely to be reported to the IT service desk—either by an affected person or by an IT monitoring tool—for resolution.
Incident management (not to be confused with problem management) is the process of responding to and restoring service operations as fast as possible.
In short, this core pillar of ITIL aims to reduce downtime from incidents by getting the user back up and running in as little time as possible. An example of incident management in action is an employee calling the IT service desk because the app on their mobile phone is not working. The resolution is either an update to the app, the phone’s operating system, or both. This can either be done by the service desk analyst remotely or by the employee by following instructions in a self-help portal or provided by a service desk agent.
I’ve got 99 problems... and ITIL ain’t one.
Problem and incident management differ but are both key components in ITIL. Problems are defined by Axelos as “A cause, or potential cause, of one or more incidents.” Problems come from incidents, but despite how some people might describe problems, incidents don’t change state into problems. Instead, a problem is a new ITSM entity—and a separate record in an ITSM software—created from recurring incidents.
A problem might be an incident that repeats over time—for example, the same laptop continually experiences hard disk failures (despite repeated replacement). Or it’s an incident that’s affecting multiple laptops, and the likely cause, or root cause, is going to be a manufacturing issue. Problems are typically identified through the analysis of incident records and other ITSM data.
ITIL best practices indicate the proper way to handle problem management.
Problems are usually dealt with over a longer time period than incidents. Here, ITSM tool data and potentially other sources of information are gathered and analyzed to understand what has caused the recurring issue(s) and what needs to be done to rectify the situation. This resolution might take the form of a request for change (RFC) or, if a definitive solution is known or isn’t possible, then a known error and workaround are created to temporarily flag and fix the recurring issue respectively.
Other than “because I was told to”: One of the major benefits of using ITIL is the amount of time saved—instant uniform guidance and processes across your organization, not just your IT department.
The benefits of using the ITIL framework within a IT Service Management solution also include a more streamlined organization. These positive benefits extend beyond simply the IT department and those they serve, rather they can be implemented enterprise-wide. YAY!
Bottom line: should you get the ITIL certification? Hey... why not!
Knowledge and mastery of ITIL is important (almost... expected?) in the IT industry. ITIL certification indicates to organizations and IT managers that you are a skilled practitioner of ITIL, which can lead to potentially higher paying opportunities, a sharper skillset, and more knowledgeability and credibility on the job. Maybe it’ll even make you... dare we say... BETTER at the job. Even more, certification is a relatively low-risk effort with a potentially high ROI for those in the IT industry.
According to Axelos: The ITIL certification scheme provides a modular approach to the ITIL framework and is comprised of a series of qualifications that vary by degree of depth and detail. The tiered structure of the qualification offers candidates flexibility relating to the different disciplines and areas of ITIL and the ability to focus their studies on key areas of interest.
ITIL v3 Certification Scheme
ITIL v3 Foundation qualified candidates are encouraged to move straight to ITIL 4 Foundation to keep their skills up to date. Intermediate candidates can decide to collect 17 v3 credits to enable them to transition to ITIL 4 with one course and one exam. Certification progress is tracked through a credit system based on the values assigned to each segment. Credits are accrued in the Foundation and Intermediate levels.
ITIL 4 Certification Scheme
ITIL 4 extension modules are available to take at any point in the ITIL certification process. No prerequisites are required.
All modules are offered in English, with the potential for other languages for certain modules. More information about ITIL training courses and exam information can be found here.
ITIL falls under the umbrella of ITSM. Broadly speaking, ITSM covers the entirety of managing IT services (strategy, design, operation), while ITIL is just a specific framework for practices for service lifecycle stages. IT Service Management, or ITSM, refers to the entirety of activities directed by policies, organized and structured in processes and supporting procedures, that are performed by an organization to design, plan, deliver, operate, and control information technology services offered to customers. This is often delivered through an ITSM software solution.
ITSM should not be comprised of a random assortment of rules, practices, and tools. Rather, ITSM requires a set of uniform rules and common practices to function seamlessly. IE, something like ITIL helps you organize ITSM. Think of ITIL as a language used by ITSM. ITIL and ITSM are not interchangeable terms. ITIL is a cohesive set of best practices and an accepted approach to ITSM. Although the ITIL framework is the most widely used set of best practices for ITSM, others may be used by ITSM software companies. These frameworks include Microsoft Operations Framework (MOF), and Control Objectives for Information and Related Technologies (COBIT). Frameworks may also have different subsidiaries outside of the general IT department, like DevOps, for example.
Much has been written about the new elements of ITIL 4 and how this new version of ITIL differs from ITIL v3/2011. And we rant a little more about it in the FAQs, below (spoiler: ITIL v3 still works). But it is worth quickly mentioning a few of the key changes related to ITIL processes:
IT departments have long understood (or begrudgingly accepted?) the benefits and positive aspects of the ITIL processes and framework. When used in concert with an ITSM software solution, every aspect of the IT department from simple ticket creation and tracking to the change management, incident management, and asset management processes can be streamlined. Furthermore, these benefits can extend to the entire enterprise.
Is ITIL only for large organizations?
ITIL frameworks and processes can be catered to fit companies of all sizes.
What are the four dimensions of service management?
Are there any drawbacks to ITIL?
The biggest downside of ITIL processes is that they take time—there are no short-term returns on any initiatives. Changes can be disruptive to pre-existing processes and infrastructure. The overall change and training requirements are time-consuming. ITIL helps us get good at quick fixes... but ITIL is not a quick fix! That said, companies benefit greatly from the guidelines and training.
What challenges can ITIL help address?
Is ITIL v3 still relevant?
ITIL v3 has been discontinued as of July 2022. That said, ITIL 4 is built off the previous versions of ITIL, and the main idea is still the same. The fact is... while many ARE implementing ITIL 4, there are also many organizations who have chosen NOT to invest in upgrading to and implementing ITIL 4. Reasons noted are because
And, finally, don’t fix what isn’t broken! Your organization might be happy with what it’s doing in ITIL v3;if that’s the case, that’s ok! Some orgs are also opting to adopt only specific selected aspects of ITIL 4, and that’s a great way to focus on applying solutions where problems exist and need to be solved.
Business has evolved a lot in the 15 years. But we don’t have time to go changing things that are working fine just for the sake of it, right?
How do I start using ITIL processes?
Well... ITIL implementation isn’t any easy task. To help, here are some best practices for adapting the phases into your organization.
Learn more about how ITIL and how we can help your organization adopt ITIL (and more importantly, make IT easy) by getting a personalized demo here.