- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2019 08:23 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2019 02:46 PM
Hi Niharika!
So, a Profile Tier level is simply a way to indicate where in the Profile Class structure a give class may reside. It's also important to remember that the Profile Class system is a way to create a reporting hierarchy within the Profiles themselves.
For instance, it is often the case that a VP or other senior level executive would like to see all of the risks that are related to her particular organization or vertical within the enterprise, right? So we use the tiering system to help set up some rules around how each of the Profile Classes relate to one another. If it helps, you can think of the Type, Class, and Tier level in a way that is similar to how we create CI relationships within the CMDB.
We may know that a Server is contained within a Rack which is in a Computer Room in a Datacenter, but the CMDB doesn't know that until we define those relationships!
In the same way, we need to define how a Group relates to a Department, which might belong to a Business Unit, which belongs to a Subsidiary Company as part of a Parent Company. Each of those entities resides on a different "tier" typically, and when you define Class in you'll need to define where in the hierarchy your class resides or whether is is the "root" of a given structure.
Hope that helps, and if it does, please mark and update the post so others can find the answers too!
Ben
ʕノಠᴥಠʔノ*:・゚✧.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2019 02:46 PM
Hi Niharika!
So, a Profile Tier level is simply a way to indicate where in the Profile Class structure a give class may reside. It's also important to remember that the Profile Class system is a way to create a reporting hierarchy within the Profiles themselves.
For instance, it is often the case that a VP or other senior level executive would like to see all of the risks that are related to her particular organization or vertical within the enterprise, right? So we use the tiering system to help set up some rules around how each of the Profile Classes relate to one another. If it helps, you can think of the Type, Class, and Tier level in a way that is similar to how we create CI relationships within the CMDB.
We may know that a Server is contained within a Rack which is in a Computer Room in a Datacenter, but the CMDB doesn't know that until we define those relationships!
In the same way, we need to define how a Group relates to a Department, which might belong to a Business Unit, which belongs to a Subsidiary Company as part of a Parent Company. Each of those entities resides on a different "tier" typically, and when you define Class in you'll need to define where in the hierarchy your class resides or whether is is the "root" of a given structure.
Hope that helps, and if it does, please mark and update the post so others can find the answers too!
Ben
ʕノಠᴥಠʔノ*:・゚✧.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2019 11:29 AM
Thank you, Ben.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-16-2020 05:48 AM
Hi, I really liked your explanation!
Wondering if it's possible / advisable to create additional tiers? What would be the pitfalls / advantage of that? I have a hierarchy that doesn't quite fit the three OOB tiers.
Thanks for any input you can offer!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-22-2020 09:11 AM
I have the same questions preparing for a launch in Orlando. Benjamin, did you receive any information in addition to the posts above? Best, Dan