Entry #4

Entry #4

What is Known Error Database?

The purpose of a Known Error Database is to allow storage of previous knowledge of incidents and problems – and how they were overcome – to allow quicker diagnosis and resolution if they recur.

Office of Government Commerce. (2007). Service Operation Book (1st ed.) [E-book]. The Stationery Office.

?

The KEDB consists of Known Error Record. Each such record should capture precise details of the fault and the symptoms that occurred, along with accurate details of any resolution or workaround that can be taken to reinstate the service and/or resolve the problem.

?

As I was taking strides into the world of IT Service Management, the KEDB was one of the tools that I really found handy in my day-to-day work. Afterall, I was not a product specialist and I believed in my then role, there was still so much to learn. But I will say this, the KEDB to me, was, and remains one of the most underrated tools available to the BAU (Business as Usual) team. Over the years, I have observed that the significance of a robust KEDB is sometimes not championed enough by the IT Service Management leadership.

All BAU team members should be fully competent and acquainted with the value that the KEDB can offer and the way it should be used. They should be able readily to retrieve and use data. It is also advised to have a robust team in place to vet each Knowledge Article and a leaderboard for Knowledge contributors can be published every quarter.

In my opinion, a KEDB is not merely a database of unrelated articles that sometimes teams are forced to write just to meet some performance review criteria. Used in the optimal manner, it can lead to lesser incidents, faster turnaround times, meeting XLAs, improved customer reviews and last but not the least, help the BAU member grow into his/ her role and give them a platform which helps grow the overall Incident/ Problem Practice at the organization.

Note: The KEDB forms part of a larger Service Knowledge Management System (SKMS) as per the ITIL Guidance. Also, Gnōsis is the commonly used Greek word for knowledge.

要查看或添加评论,请登录

Sudipto Banerjee的更多文章

  • Knowledge Management: A brief overview

    Knowledge Management: A brief overview

    Did you know that Peoplecert published the latest version of ITIL?4 Knowledge Management Official Practice Guide…

  • ITSM in space!!!

    ITSM in space!!!

    You might have heard the phrase “Its not that you are working on rockets” multiple times in your career. A lot of you…

  • Incident Resolution and the 3 strike rule

    Incident Resolution and the 3 strike rule

    Have you heard of the 3-strike rule in the world of ITIL? One of the key practices within ITIL4 is Incident Management,…

  • Measure for good

    Measure for good

    Measurement and reporting is one of the newer practices introduced by ITIL 4. As per ITIL4, measurement clarifies the…

  • Emergency or not - Change Requests

    Emergency or not - Change Requests

    #itil4 #changemanagment Some concepts have changed between ITIL V3 and ITIL 4. However, the definition of a change…

  • #Entry 12 - Service Catalogue

    #Entry 12 - Service Catalogue

    During one of the recent conversations with a potential client, we started discussing their current and planned state…

  • #Entry 11 - Service Introduction

    #Entry 11 - Service Introduction

    Today I was attending a knowledge session organised by our team on Service Introduction, a term I am sure a lot of…

    1 条评论
  • #Entry 10 - Governance in IT

    #Entry 10 - Governance in IT

    Recently I was going through an article on Corporate Governance, which although half a decade old, seemed quite…

  • Entry #9

    Entry #9

    In one of my earlier articles, I had mentioned about the concept of Service Request and how I have seen some people…

    1 条评论
  • #Entry 8

    #Entry 8

    When I started writing this series of articles, I had thought of contributing on a regular basis. However, it has been…

社区洞察

其他会员也浏览了