Nowadays implementing ITIL is necessary for any business, either it could be a small or medium business or a large enterprise. ITIL provides a set of proven industry standards that helps businesses to improve service delivery and customer satisfaction and reduced to IT costs. But a clear understanding of ITIL processes is essential for successful ITIL implementation. Here I am going to take you through few of the must have ITIL processes and steps involved.
Incident management is the process, which allows you to find the solution for the incident in a timely manner. A service interruption or reduction of service quality might affect your business. The purpose of incident management is to restore your service as soon as possible, without affecting your business continuity. Integrated knowledge base can help your technicians to provide instant resolutions and also to keep up with the response and resolution time based on SLA (service level agreements).
In some cases, the nature of an incident differs from the organisation it could be a major incident or a minor one depending on the impact produced.
Some of the examples for the incidents are:
- Poor network connection
- CD Drive is not working
- Facing issues in the delivery of email
Processes involved in incident management are:
- Incident identification
- Classification or prioritization
- Investigation and Diagnosis
- Resolution recovery
- Incident closure
Problem management is the process, which helps to reduce the business impact on service disruption and future disruptions. It helps to identify the root cause of the error in IT infrastructure, which is often referred to as an incident. The disruptions faced by the user can be different occurrences of a problem. When you are able to find the root cause for the incidents, you can also eliminate recurring incidents in the future.
When the user reports for a problem, the help desk technicians must check with the known error database. If the reported problem has a workaround or solution, it is a known error.
There are two types of problem management:
1. Proactive problem management – Proactive problem management’s focus is to eliminate the root cause before they have chances to appear.
2. Reactive problem management – Reactive problem management is based on responding to incidents after it occurs.
Processes involved in problem management are:
1. Identify the problem
2. Create a problem record
3. Categorize and prioritize the problem
4. Identify the root cause analysis
5. Identify a workaround for the problem
6. Resolve a problem
7. Close the problem
Change management is a process of minimizing risks involved with organizational, behavioral and structural changes into the IT environment. Adapting your business to any such changes is an overwhelming process and it may lead to service disruptions, if not proactively performed. Change management process is always recommended to start with a complete change implementation plan, right from submission, planning, implementation, post-implementation review, and closure.
We can classify change into three types based on the impact and risk involved.
Standard – These changes pose a very low risk on business and it is easy to prioritize and implement. It follows a procedure or work instruction that doesn’t require approval in a risk management perspective.
Emergency – A change, which is to be implemented immediately to ensure business continuity. Every stage of the process demands to get approvals from change management and change advisory board members, often referred to as CAB.
Normal – It involves minimal risk, these changes must go through a change process before being approved and implemented. The change advisory board will be deciding whether to be implemented or not.
Processes involved in change management are:
1. Request for a change
2. Review request for change
3. Evaluate the change
4. Approval of change
5. Implement the change
6. Review and close the change request
Release management aims to plan, design, build, configuration and implement changes smoothly. Change management works closely with release management. Change management is responsible for planning and release management is for execution or implementation.
Processes involved in the release management are:
1. Release planning
2. Release build
3. Release test
4. Release deployment
5. Review and closing a deployment
CMDB – Configuration management database
CMDB is a place that stores all information about the assets used in an organization. The main goal of CMDB is to build an asset repository that can be uniquely identified and managed. With the CMDB feature, your business can gain full visibility on the infrastructure and services, which leads to taking better decisions in the IT environment. To manage your collections of IT assets, keep track on configuration items (CI).
What are CI and it’s types?
The configuration items can be hardware, software, and network. CI is represented with attributes and relationships, which is to describe the objects. The attributes for CI type – Workstation could include model, service tag, IP address and so on. On the other hand, relationship denotes the link between two CI’s that identifies the dependency or connection between them.
Relationship map helps to visualize the relationship between multiple CI’s. The CI impact on IT service can be analyzed with the help of a relationship map and helps to find the root cause analysis. By analyzing the root cause and impact produced, we could eliminate the recurrence of issues faced by the organization.
ManageEngine ServiceDesk Plus
Originally posted 2017-05-17 17:04:35. Republished by Blog Post Promoter