I recently wrote a piece for Plural Sight on Known Error Database (KEDB). A KEDB is a repository that holds information about problems for which the root cause is known but a permanent solution doesn’t. Either the permanent solution does not exist or not implemented (yet).
It is common in the IT world to confuse the KEDB with the Knowledge Management database (KMDB). In fact, during one of my ITIL Lifecycle Service Operations training sessions, when I was on the topic of KEDB, one of my students claimed that her organization maintained a KEDB. I invited her onto the podium to explain how it worked in her organization and what it contained. She said – “The database contains policy documents, process documents, work instructions, technical manuals…” I clarified if this database had incident and resolution records which was not the case.
The database which she was referring to is the KMDB generally but ITIL has a different term for it – service knowledge management system (SKMS).
SKMS and KEDB are two different entities entirely. One cannot substitute the other although KEDB is a subset of SKMS. A KEDB strictly holds information about incidents and the incident resolution details.