Number of times a catalog item is used?

jduchock69
Giga Contributor

Is there a way to tell how many times a service catalog item has been used as a source for a request, change, etc.?   As part of a go-live i have inherited, there are some questionable service catalog items that have been created and i would like to remove those that are not used or created "in error".   Due diligence, however, dictates that I understand how and why they were used if in fact they were.

 

Alternately, is there a way to tie a request or change record back to it's source from the catalog?

 

Thanks in advance

 

John

7 REPLIES 7

Uncle Rob
Kilo Patron

Hey John,



Unfortunately, unless you're making a concerted effort to use the Task level parent field, there's no good (reportable) way to determine a record created via workflow.



Its always bothered me that there are basically four building blocks of the Service Catalog and only one of them is easy to measure consumption from.



ITEMREPORTABILITY

CATALOG ITEM


Report on the sc_task's request item's catalog item.  
But you can't report on any non-sc_tasks created by same Catalog Item

RECORD PRODUCER


No data element tells you how the record was created
ORDER GUIDENo data element tells you what Order Guide triggers.   Best you can get is what Catalog Item the Order Guide triggers.
WIZARDNo data element tells you what wizard launched the record


The best thing I've been able to do is make a custom field called "Consumed Service" and simply remember to populate it on whatever mechanism is creating my task.  


Uncle Rob
Kilo Patron

I actually wrote a blog article on this topic that you and other readers may find interesting.   It outlines the major problems with measuring Catalog Consumption, and why that matters so much in support of PaaS.



For your viewing pleasure:   http://www.rfedoruk.com/2013/11/CatalogReportingConundrum.html


Dave105
Kilo Guru

Sorry John, might be 5 years to late with this reply but we have created the following basic report which allows us to identify how many times each for has been used, and whether the request is now closed or still active.

 

Hope this helps

Dave

what actually (empty) mean?