Hi Mantautas,
I am quite happy with the naming convention we’re using, therefore I’d like to share it:
[Publisher] [Product] [Version] [Edition] [Channel] [Type] [Metric] [OE License Owner] [OE License User]
- Channel: e.g. Volume, Box, OEM
- Type: L, L+Mnt, Abo, while L+Mnt and Abo have added the current end date --> I find this important to quickly realize, why I have several licenses with otherwise identical attributes. If I wouldn’t add the end date, I would regularly stumble above such licenses and would have to check in each license to realize, that they have different maintenance / subscription end dates (as far as I know, there is no column that helps with that).
- Metric: yes there is a separate field for it, but if you have some non-standard metrics or you use a Flexera metric that counts right but has a different name for this metric, I find it helpful to see the metric right in the naming.
- OE License Owner / License User: For us this is extremely important as we have differences in who the license owns and who uses it. The Usage you can restrict with Scoping, but for adding new POs to existing licenses, we need to know from the license name which license to allocate. We use the highest possible organization structure that fits using organization entities. Locations might be relevant for some as well.
These are quite a few attributes that Need time to be maintained but for us it works very well.
We use the same convention for POs, having more Types like Upgrades or Maintenance only.
Btw. thanks to Softline for helping in the creation of the convention.
Best regards,
Manuela
