I think this will be complicated because lots of elements are related to the current levels.
(Contracts, SLA, Calendars, portal and backoffice display etc...)
If you want to do it, you will have to edit every links.
I guess it will be simplier to make a top categorie, wich will be only related to catégories.
In my opinion, this is not a good idea because it will add a level of complexity for the users, and require lots of work for just adding a level of catégory.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If it's something you want merely for classification and report or dashboard purposes, you could create the necessary class and and hiearchical links with minimal work.
However, if you want this Sub-Sub-Category to work the same way as Subcategory, that would require a massive retooling, so what DLP suggests above is your best bet in that scenario.
His recommendation is also quite valid because when it comes to best practices in Service Design and SLM, it's preferable to have a Service Tree that is WIDE rather than DEEP. You may want to rethink your structure and try to "squash" to fit what iTop offers.
Example: If you're originally thinking of
Network
1.1. Installation
1.1.1. Switch
1.1.2. Gateway
1.1.3. Access Point
1.2. Security
1.2.1. Firewalls
1.2.2. Active Directory
You could try:
Network - Installation
1.1. Switch
1.2. Gateway
1.3. Access Point
Network - Security
2.1. Firewalls
2.2. Active Directory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Kindly please help how if i want it to add another lever of subcategory.
Any suggestion highly appreciate....
I think this will be complicated because lots of elements are related to the current levels.
(Contracts, SLA, Calendars, portal and backoffice display etc...)
If you want to do it, you will have to edit every links.
I guess it will be simplier to make a top categorie, wich will be only related to catégories.
In my opinion, this is not a good idea because it will add a level of complexity for the users, and require lots of work for just adding a level of catégory.
If it's something you want merely for classification and report or dashboard purposes, you could create the necessary class and and hiearchical links with minimal work.
However, if you want this Sub-Sub-Category to work the same way as Subcategory, that would require a massive retooling, so what DLP suggests above is your best bet in that scenario.
His recommendation is also quite valid because when it comes to best practices in Service Design and SLM, it's preferable to have a Service Tree that is WIDE rather than DEEP. You may want to rethink your structure and try to "squash" to fit what iTop offers.
Example: If you're originally thinking of
1.1. Installation
1.1.1. Switch
1.1.2. Gateway
1.1.3. Access Point
1.2. Security
1.2.1. Firewalls
1.2.2. Active Directory
You could try:
1.1. Switch
1.2. Gateway
1.3. Access Point
2.1. Firewalls
2.2. Active Directory