Hello All,

Out of curiosity has anyone found a best practice for building out an Application UID? Considering the complexity of an Application and its possible variations of products/modules/versions that can exist. I've pondered on building a four-tier approach as noted below:

          [UID] = Application Name.Application Versions.Product/Module Name.Product/Module Versions

                         e.g. 1000.10.1000.10

I'm not quite sure if this is the best approach.

Hi Richard,

The purpose of the UID for Applications is to assign a unique ID to allocate cost's to, where over time you will ensure an Apples to Apples comparison of the cost is consistent regardless of meta data like the Application Name, Vendor, Version, etc.

Consider this: In January you have an application named "John's Smart Business App" with a UID of "100001". In February, that application changes name to "John's Smarter Business App" with the same UID of "100001".

The key is that in both January and February all costs are allocated to "100001" in the model - so when you view the costs associated over time it is correct regardless of the name changes.

If you were to make the UID based on the name in this situation, the apps would be treated separately - and you would only see costs for the app in each month as if they were different.

In the end, as long as your UID is unique to the application as you want it to receive costs - you will be fine. We see success when you assign a UID to each application unrelated to the applications details associated with it.

I hope this helps, but would be happy to continue the dialogue and would love to hear some our customers perspective on this as well.

Seth