- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 09:42 AM
Out of the box, ServiceNow uses Level 0 as the top level of business capabilities. Capabilities that are under that level are Level 1. And so on...
In contrast, TOGAF defines the top level as Level 1.
Is there a way to make business capability levels defined in ServiceNow match TOGAF? We have defined our capabilities using the TOGAF approach and now that they are in ServiceNow (well many of them are), we are constantly having to make the translation in our heads (SN Level 0 = Our Level 1, SN Level 1 = Our Level 2, etc.).
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 10:17 AM - edited 05-13-2025 10:20 AM
The Level attributes are as you note required to be 0 based for things to work. However, notice that the Hierarchy ID is 1 based (you don't ever see a Hierarchy ID starting with 0) which does comply with TOGAF. The level attributes are there for behind the scenes data management and analytics.
The level is indicated by the Hierarchy ID in other words. Its not perfect but the underlying change a little heavy. You could add a TOGAF Level attribute that is 1 based.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 10:17 AM - edited 05-13-2025 10:20 AM
The Level attributes are as you note required to be 0 based for things to work. However, notice that the Hierarchy ID is 1 based (you don't ever see a Hierarchy ID starting with 0) which does comply with TOGAF. The level attributes are there for behind the scenes data management and analytics.
The level is indicated by the Hierarchy ID in other words. Its not perfect but the underlying change a little heavy. You could add a TOGAF Level attribute that is 1 based.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2025 11:15 AM
Thanks, Mark! That's helpful and what I was assuming would be the case. In an ideal world, we'd be able to easily distinguish capabilities by "level". I can see now that the level attribute that is present is behind the scenes and thus won't meet that need (unless we want people to have to do the translation). I like the idea of adding a custom attribute for our purposes as an easy solution.
PS It was great to meet you in person last week at EA PAC at Knowledge!