Aleatha Leader
Tera Contributor

We’ve all been there: two people are using the same word, different ways. Or two different words, the same way. They might both make sense in context but misunderstandings can get really out of control. 

When this happens in the CMDB it can cause problems with everything from reporting to getting incidents sent to the right place. The classic examples are points of contact like Managed by, Owned by, and Support group.

 

Here are a couple of steps to get you started on a dictionary for your CMDB:

1.  Decide who is responsible for creating and keeping the dictionary up to date

This may be one person or a small team, but editing must be restricted or you’ll get people changing the definition instead of following it

2.  Gather up the stakeholders (or at least the use cases)

Find out how different areas in your business are using this term now

3. Determine who else might have definitions

Do you use ITIL? Agile? A ServiceNow training that defined the term?

4.  Once you have the options combine the definitions and attach them to the right label/word

If one department uses Owned by and another department uses Billing contact you might choose one and include the other in the definition i.e., Owned by: (aka billing contact) Person accountable for the use of the Configuration Item

Depending on your organization this might be something a small group can decide, or it might be a project or require an approval process

5.  When intaking a new source or adding a new department to ServiceNow use the dictionary definitions to map the information or create reports

Yes, sometimes this means people need to be trained on the new terminology or adjust

6.  Add new terms to the dictionary (or amend definitions) as needed

Please note: The more things that are in your CMDB the riskier it is to not have definitions or to try to change the definitions in place

There’s no one right answer or definitive list out there, but having a dictionary for your organization can save you a lot of trouble in the future.

 

Addendum:  One of the first questions I got about this was ‘could you give me an example?’

My personal preference:  The columns on my data dictionary include Field/Label, Description, Source/type, and Field Name.  You can get the field name and reference from your Data Dictionary in ServiceNow (sys_dictionary) if you have access. (screenshot also attached)

find_real_file.png

Comments
emir
ServiceNow Employee
ServiceNow Employee

Great start Aleatha.

This is really important for all u_ fields. Maybe add a source for data for fields that comes from another source like Active Directory, etc...

Bert Van Rosse1
ServiceNow Employee
ServiceNow Employee

In my opinion, this shouldn't even be restricted to CMDB. This is valid for all aspects of an implementation project, regardless of the product or process. 

Arno Reintjens
Tera Contributor

Hi @Aleatha Leader, within my team we are also addressing a process to get the dictionary up to par, by adding additional information. But instead of adding information to excel or other tool, we want to add the data direct in ServiceNow. We are thinking of extending the dictionary and adding fields that we think are necessary. 

But, I can imagine that more companies want to have more information in the dictionary. Do you know if ServiceNow is planning to extend the dictionary so that additional information can be stored?

Thanks for your response.

Cheers,

Arno

Aleatha Leader
Tera Contributor

My apologies for the delay in reply @Arno Reintjens . I don't have information on what ServiceNow is planning for the dictionary, but one concern we had is that not everybody has access to the sys_dictionary.  Our plan is to eventually have at least the most common questions or fields in a knowledge base article so users can see the definitions when they create reports.  If the main people you are expecting to need the dictionary are admins or devs the sys_dictionary comments (or extended fields) might be a good fit.

Jason Siegrist
Giga Guru

Hey guys .. check this out!! https://demo.erm4sn.com/ 

 

This gives you what you want and comparisons between releases and instances !! 

 

https://www.erm4sn.com/ 

 

How it works

erm4sn is the easy, effective way for you to view and analyze your ServiceNow data model. Our application connects with your ServiceNow instances to provide you with a clear visual overview, so you can work smarter and more efficiently. Browse the data model, compare changes and pinpoint compatibility issues: with erm4sn, you can get the most out of ServiceNow.

Version history
Last update:
‎12-29-2021 02:08 PM
Updated by: