ITSM - Knowledge - Process Guide - Rome
ITSM - Knowledge - Process Guide - Rome
Process Guide
Rome Release
Ref: 0001262
The degree to which we can integrate use of the knowledge base into our processes will dictate the benefits
realised through KCS.
KCS will not be described in detail here. The KCS principles ServiceNow aligns to will be used to structure this
document.
Capture knowledge When a customer request comes in, those answering the request create an article
as a by-product of solving the customer’s problem.
Structure knowledge Using a template or form for writing an article keeps the knowledge base
consistent, making it easier for customers
Reuse knowledge Search the knowledge base when solving a customer issue, and they can link it to
other relevant articles they may have used when solving a problem.
Improve Knowledge Agents are inherently reviewing the knowledge as they research articles to solve a
problem and therefore can provide feedback on the usefulness
In addition, we will also look at aspects of ServiceNow that support the KCS Evolve loop.
Governance
Overview
Governance is a vital component of the Knowledge Management Framework.
Without governance, there is no assurance that the Knowledge Management system will ever be used.
Controls
Process controls are activities that are performed to ensure a process is stable, repeatable, and operating
effectively and efficiently with only normal variations. Knowledge Management controls include the following:
Set up formal Knowledge Management procedures to handle in a standardized manner all requests (including
maintenance and updates) for knowledge on services, applications, procedures, processes, etc.
Review all adds or updates to knowledge in a structured way to ensure consistency of article format,
readability of content, and storage requirements.
Establish a process accessing, using, validating usefulness, and recommending updates to knowledge. This
includes actioning Knowledge Feedback Tasks (if in use).
Establish a tracking and reporting system track request for new and use, maintenance, and retiring of existing
knowledge.
Whenever knowledge is published (new or modifications), communicate availability to all applicable
stakeholders.
Knowledge Manager:
Manages and coordinates the day-to-day Knowledge Management processes and activities
Defines knowledge categories
Reviews submitted knowledge articles to ensure the content is valid and that the quality standards are respected
Obtains appropriate Subject Matter Expert (SME) validation, where needed
Identifies new content and/or solutions needed to support the end users’ needs
Encourages people to contribute knowledge articles
Creates and maintains knowledge templates
Pins important knowledge articles to appear at top of search results
Gathers and reports on process metrics
Knowledge Contributor:
Submits new knowledge articles
Updates the content of submitted articles
Completes knowledge feedback tasks (if in use)
Knowledge User:
Uses knowledge in day-to-day activities
Provides feedback on existing knowledge
Identifies missing knowledge needed in day-to-day activities
Identifies knowledge that needs to be updated
Structure Knowledge Capture Knowledge Reuse Knowledge Improve Knowledge Content Health
Determine the number and name of Knowledge bases, what content will be in each, and who will have
access to each.
– The primary manager of a knowledge base is the owner of that knowledge base.
– Each knowledge base must have one owner. There may be any number of additional managers for each
knowledge base.
– Each knowledge base can have a publish and retire workflow specified appropriate to the required
approval levels. These may differ depending on the type of content e.g., HR vs Marketing vs technical.
– Determine content ownership, security, and access rights.
Determine how the knowledge base content will be organized by topic and category to facilitate easiest
access and use by all users. Each knowledge base can have its own multi-level taxonomy that is
independent of the other knowledge bases.
– When considering the taxonomy and number of knowledge bases, also consider the use case of search
which is likely to be the majority use case.
Determine the various views that will be needed (for example, end users, service desk, network support,
others).
Determine the various configurable aspects.
– Use templates to aid knowledge creation. There are 4 templates available out-of-the-box through the
Knowledge Management Advanced plugin: How To, What Is, KCS Article, FAQ.
– Use UI extension points to customize knowledge article headers and footers.
Differing types of feedback are available for articles. It is important that there is a process in place to take this
feedback and action it. This will help develop the knowledge base based on collective experience.
If the Group Ownership system property is enabled, User Groups can be created and listed on individual
knowledge articles to define a group of people who are responsible for maintaining specific articles.
• Draft
• Review
• Scheduled for publish
• Published
• Pending retirement
• Retired
• Outdated
Draft
When a knowledge article is first created, it is in a state of Draft. The mandatory fields are:
Knowledge base
Short description
The draft article does not appear in the knowledge base (KB) for users until it is reviewed and published. The
Category field is selectable once the knowledge base has been selected.
In addition, the following field may be filled out automatically:
Source task: relates to the task if applicable e.g. Case, Incident that the knowledge article was created from
Before creating a new article, the recommended practice is to search for duplicates. This can save time and gives
the author the option on whether to create a new article or to update an existing one.
The action after an article is submitted is dependent on the workflow selected for that knowledge base.
Approval Publish: the article is moved to review state for a knowledge manager to review and publish if
acceptable
Instant Publish: the article is moved to published state
The use of templates within ServiceNow is recommended to drive consistency of approach in style for different
types of articles. This helps the user consuming the information within the article.
Encryption can also be setup on specified fields when the knowledge base is created. This will hide the
information in the field unless the user has the appropriate role to view.
Review
The knowledge base article is now available to review. The Knowledge base Manager and Owner may choose
to
As part of the review process the approvers can provide comments relating to the article and their decision.
Published
In this state, the article is available to users who have appropriate permissions. These permissions are best
determined through user criteria.
Pending retirement
In this state, the published article is selected for retirement, pending approval.
Retired
Moving an article to retired removes the visibility of the article from the knowledge base. There may be an
approval process for retiring articles specified depending on the knowledge base.
Outdated
This state indicates a more recent version of the article has been published. End users can read published articles
as well as the outdated versions.
ServiceNow can be linked to external content such that it can be searched within ServiceNow. The configuration
determines whether the selected article is displayed within ServiceNow or the system of record. The external
content cannot be modified within ServiceNow and is only available as read only.
There is also the option to create a submission record is created instead of a knowledge article. A user with the
knowledge role must approve the submission to create a knowledge article. Approving a submission creates a
new knowledge article using the submission content.
Retire Knowledge
Knowledge articles should be reviewed at least annually. Periodic reviews of the knowledge base content need
to be conducted to ensure its usefulness and relevancy. During these reviews, updates may be identified or the
article may need to be retired. Knowledge articles can also have a valid to date set when they are created. This
helps the review process and allows for time-bound articles (e.g., an article associated to a public holiday).
Whether these various feedback options are available to the users can be configured within the system.
The task assignee can update the article, create a new article, request additional feedback, or reassign the task
and receives notification after the feedback is updated or resolved.
Note: Feedback tasks are only generated if feedback is given on the Knowledge Service Portal.
Ownership Groups
When knowledge articles are created, ownership groups can be associated to them. Ownership groups manage
article approvals and feedback and can edit and retire knowledge articles that they are associated with.
Knowledge group managers can edit ownership groups managed by them by adding or removing members
without the need for approval. You can also create an ownership group from an existing group.
Key Performance Indicators (KPIs) evaluate the success of an activity toward meeting the CSF. Successfully
managing KPIs can be either through repeatedly meeting an objective (maintain) or by making progress toward
an objective (increase/decrease).
Item Purpose
Number and percentage of articles not accessed for X Measures how well the knowledge base content is
(amount of time) being maintained.
Item Purpose
In addition to reports, each user can create a personal homepage and add gauges containing up-to-the-minute
information about the current status of records that exist in ServiceNow tables.
To maintain a high quality of content in the knowledge bases an article quality evaluation mechanism is required
to enables customers to review and evaluate the quality of articles and the performance of the authors. This
enables constant improvement in the content and authors content editing skills.
The knowledge admin would create the AQI checklist, adding true/false questions and defining the order and
weight of the questions. The checklist would be assigned to the knowledgebase.
The knowledge coach and knowledge domain expert would perform AQI reviews - the results of which would
be emailed to the author. Finally, the author would review the scores and comments and take corrective action
as required.
Testing
Use the Quick start tests for Knowledge Management to validate that Knowledge Management still works after
making any configuration change, such as apply an upgrade or develop an application. Copy and customize the
quick start tests to pass when using your instance-specific data.
Knowledge Management quick start tests require activating the Knowledge Management Core plugin
(com.glideapp.knowledge), the Knowledge Management Advanced Installer plugin
(com.snc.knowledge_advanced.installer), the Knowledge Blocks plugin (com.snc.knowledge_blocks), and the
Customer Service Management Demo Data plugin (com.snc.customerservice.demo).
Knowledge can be created from an incident or a case to ensure details of diagnosis and
resolution activities are communicated to other users of knowledge.
Case / Incident
Management The incident/case form displays contextual search results based on text entered in the
Short Description field. These search results provide targeted knowledge to the
incident analyst.
Change Management can use knowledge to help in risk assessment as well as to obtain
information on activities to be performed to implement a change.
Change Change Management can use knowledge to track change plans (testing,
Management implementation, backout, etc.)
Can be used for knowledge creation by taking community solutions and creating a
Community
knowledge article
AI Search in mobile
Use AI Search search engine in the Now Mobile platform to help users find answers in a visually appealing way.
AI Search also supports the use of buttons within results enabling users to proceed quickly with their tasks.
AI Search is available in the Now Mobile platform and utilizes the data sources of catalog items, KB articles,
and users. Use AI Search, wherever possible, when using these data sources. Zing search engine is available for
all mobile platforms and utilizes additional data sources not associated with AI Search, for example user tasks or
requests.
AI Search offers the following intent-based results to facilitate users during a search:
Navigation tab filters - Filters are broad categories that the user selects to eliminate pages or results on a site.
Auto-complete - AI Search predicts the query as the user enters text and helps to formulate the user's
question.
Recent and popular searches - After the user taps the search bar and before entering text, suggested search
options display according to the user's personal search history and queries by all users on the instance.
Auto-correct typos - AI Search auto-correct typos based on its indexed content.
Synonym handling - The search engine can look for similar words entered and produce results accordingly.
Genius cards and action items - Genius result cards display the most relevant answers in an attractive visual
layout. They can also offer users the option to perform actions within the card.