OK, so I'm going to assume that your incident records have both a Category and Sub Category field. In that scenario, you want 2 separate breakdowns on your incident indicators. Most OOTB incident indicators already have an association with the Category breakdown.
You will need to create a breakdown of the Sub Category if one hasn't already been done. Here is the docs page on defining breakdowns. This page provides the step-by-step on creating and applying a breakdown. You will probably need to create a breakdown source first, which is simply a definition of where the Sub Category options are defined. For example, the options for the Incident Category breakdown are defined in the Choice table. Look at the OOTB Breakdown Source Incident.Category to see an example of one that is already set up. You'll need to do the same for Incident Subcategory.
Once you Category and Sub Category breakdowns are defined, you'll want to make sure that your indicators are set to collect the Breakdown Matrix.
This will automatically collect scores for each breakdown as an individual score, but also how they relate to each other.
Let's say that for a given day, you have 50 resolved incidents. The scores could look like this:
Category A = Login Issues (Resolved Count = 30)
SubCat 1 = login data entry (Resolved Count = 20)
SubCat 2 = Login forgot (Resolved Count = 10)
Category B = Access (Resolved Count = 20)
SubCat 1 = Data Entry (Resolved Count = 5)
SubCat 2 = Email (Resolved Count = 15)
So it all has to do with how you configure your breakdowns. If your breakdowns are configured and applied to the same indicators, you will automatically get the relationship between Category and Sub Category.
This is a good video that steps through a breakdown.
Hope that helps!
OK, so I'm going to assume that your incident records have both a Category and Sub Category field. In that scenario, you want 2 separate breakdowns on your incident indicators. Most OOTB incident indicators already have an association with the Category breakdown.
You will need to create a breakdown of the Sub Category if one hasn't already been done. Here is the docs page on defining breakdowns. This page provides the step-by-step on creating and applying a breakdown. You will probably need to create a breakdown source first, which is simply a definition of where the Sub Category options are defined. For example, the options for the Incident Category breakdown are defined in the Choice table. Look at the OOTB Breakdown Source Incident.Category to see an example of one that is already set up. You'll need to do the same for Incident Subcategory.
Once you Category and Sub Category breakdowns are defined, you'll want to make sure that your indicators are set to collect the Breakdown Matrix.
This will automatically collect scores for each breakdown as an individual score, but also how they relate to each other.
Let's say that for a given day, you have 50 resolved incidents. The scores could look like this:
Category A = Login Issues (Resolved Count = 30)
SubCat 1 = login data entry (Resolved Count = 20)
SubCat 2 = Login forgot (Resolved Count = 10)
Category B = Access (Resolved Count = 20)
SubCat 1 = Data Entry (Resolved Count = 5)
SubCat 2 = Email (Resolved Count = 15)
So it all has to do with how you configure your breakdowns. If your breakdowns are configured and applied to the same indicators, you will automatically get the relationship between Category and Sub Category.
This is a good video that steps through a breakdown.
Hope that helps!
