Voted Best Answer

Apr 04, 2016 - 03:23 AM
Thanks for the clarification:
So - what are KPI's ? KPI's are "measures that quantify objectives and enable the measurement of strategic performance"
With that in mind any examples provided should be looked at as simply guidance what your organisation will need is likely similar though not necessarily identical. Think about what is important to you & your stakeholders.
The one example you asked for more detail on...
"Percentage of supported software licences in use"
You have 5,000 PVU's of IBM Datastage all of which you are paying software maintenance on. However, only 3,000 PVU's are in use. The KPI is 60% - What does this mean? That 40% of your annual IBM Datastage spend is not delivering any business benefit and you could consider retiring some maintenance, negotiating to replace the unused software with IBM or if you are in the EU selling some of the licences to a 3rd party.
The final component of a good KPI is an action - If X then Y - your KPI register needs to clearly define what happens if required values are met / breached otherwise its just a bunch of numbers....
Below are a few more examples:
Estate utilisation
Percentage of supported software licences in use
Percentage of unsupported software licences in use
% of licence estate in compliance
Financial
Value of supported software under deployed
Value of unsupported software under deployed
Value of all software under deployed
Value of supported software over deployed
Value of unsupported software over deployed
Value of all software over deployed Monthly
Value of banked annual maintenance savings
Licence Entitlement
% of procured licence entitlement records held in the SAM repository
% of procured software covered by maintenance contract
Acquisition Process
The % of software purchases centrally controlled
Upgrade Utilisation
% of new requirements met via upgrading free entitlement
Inventory
% of hardware & software included in the inventory
Retirement Process
% of hardware assets retired to process, capturing software for harvesting / reuse
Audit
Maximum days to satisfy a publisher audit request
Minimum days to satisfy a publisher audit request
Number publisher audit requests challenged by publisher
Number of publisher audit requests requiring mitigation