Adding and removing classifications - frequently

Hello Everyone,

We are just setting up SCSM 2012 R2 for the first time and had a question about classifications.   I am being asked to create very granular classification lists.   An example would be under hardware adding every model of computer we use.  This means over time this list would buildup with many older models. Their answer is just to delete them.  They also want me to track every application and every version via classifications.  My feeling is that these lists should not change much once setup.  

I know if classifications are used in templates it will not allow you to delete.  Is this true if classification has been used in a ticket?  What are best practices around classification lists?  My feeling is we should not be deleting classification items

Also shouldn't we be able to pull this same data out via some sort of config item report?  Like incidents by model?

Thanks

June 30th, 2015 11:14pm

Best practice is to use a simple classification for Incident Management.

I always try to keep it simple with 5 -10 root classification items and a maximum of 2-3 child levels (maximum of 3-5 child items each level).

The main "use" for classfication list items is to decide/route the Incident to the right Support Group and for reporting.

If you need longer than 5-10 seconds to decide which classification is bst for an Incident ticket something is wrong with the classification list items ;-)

For instance: "Software A error message" running in "OS xyz" on "Hardware Manufacturer A, Modell A, Version B" .. which is the right classification? 

If you need a detailed report of which config item type/model is causing issues you can sort this in a report based on config items. 

Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 6:54am

My main concern is with having to choose model in the classification type.   Models will be constantly changing which means you would have to delete each model or it would start to build up over time.  Also calling out each application with its version would have the same issue.   My experience with deleting anything that has been used somewhere has not been good.
July 1st, 2015 12:41pm

Full agree. For me it doesn't make sense to add every model or every version to the Incident Classification.
Free Windows Admin Tool Kit Click here and download it now
July 1st, 2015 3:30pm

In my opinion the "Affected Config Item" ist the right place to get this information. 

If you import the Computers from SCCM you get the primary owner and the model in the Computer CI. The Computer model is a property of the computer, so the report "Incidents per Computer model" is possible. Its easier to to select, since all Computers of the affected User are listed in the dropdown of the affected CIs.

July 8th, 2015 12:40pm

Appreciate everyone's advice IO

I am going to mark this as answered but if you have other opinions please let me know

Free Windows Admin Tool Kit Click here and download it now
July 13th, 2015 12:39pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics