IBM Apptio

IBM Apptio

 View Only

Moving from assumption to consumption

By Julie Batty posted Wed December 08, 2021 11:45 AM

  

​Moving from assumption based to consumption based

An element of our TBM Office roadmap is to become a Trusted Advisor which initiated a review of our allocation metrics to ensure clarity and fairness are being maintained. We created a tooling team, collaborating with the Software Asset Management team, to identify licence consumption data using Flexnet.

Problem Statement

As part of this review, it was identified that certain Services are grouped together and use total headcount numbers as the metric when allocating to Business Units. Although this initially seemed like the fairest allocation method at the time, with the introduction of licensing information from Flexnet we have been able to establish that this is no longer the case.

The project specifically focuses the consumption data of Micro Focus

 

Method for Proof of Concept

The Micro Focus data contained in Flexnet is grouped into several categories such as employee IDs, emails, domains, and division; this data helped to identify the consumer of the licensing.

The first step was to extract consumption data and identify the users of each Apptio Business Units

The Second step was to compare the original headcount allocation with the user licence consumption allocation

Final step, if allocations differ greatly, is to complete the development work to use Flexnet consumption.

 

Data standardisation and other limitations

As with the introduction of new data sets there is a requirement to standardised and clean up the data. Here we outline some of these and the limitations in the data.

When grouping the Flexnet users to one of the Apptio domains, we faced a few challenges. One of which was differing naming conventions between Apptio and Flexnet, so had to drop a lower level using the domain or even their division. Any users which were not within the Apptio domains were not included in the cost allocations.

In addition, several users had no other data associated with them, for these, we used Workday employee data to identify their Business Unit
and/or division. Those that had emails or employee IDs that could not be found in the current Workday employee data were deemed to be inactive users and therefore not included in the allocations.

 

Outcome

After comparing the percentage change headcount allocation with the Micro Focus licence consumption that are based on the Flexnet consumption data, we can see in the table below that the majority of the Business Units/divisions are being charged even though they are not consuming the licences. With division 1, 2, 5 and 7 receiving an increase suggesting that their costs were previously being under-estimated.

For some divisions such as 2 and 4 they show little movement in allocations so will not be majorly affected by the change to start using consumption-based allocations.


Changes Made

The user licence consumption allocation has now been implemented by reallocating the contract costs to an individual ITRT then to the specific application and updating the allocation metric to reflect the licence user consumption.

As part of this project a methodology has been created for the standardisation of future datasets from Flexnet so will only need to be done once saving time in future as well as triggering a project to standardise the naming conventions across the various tools used.

An outcome of this project was that only 21% of the licences were actually being used so has enabled the SAM team with the data to decide on the appropriate number of licences needed and enabling cost savings.

Another powerful impact of Flexnet is that with data driven consumption we can provide more clearer and fairer allocations and has given us the springboard to look at larger contracts such as Microsoft and McAfee which will have more of an impact on cost allocations for software assets.


#CostingStandard(CT-Foundation)
12 comments
3 views

Permalink

Comments

Fri February 25, 2022 01:05 AM

Fantastic work @Julie Batty and the Natwest team.
We'd be calling on you as we look to do the same with our licensing data in the coming months.

FYI ... @Francis Moussally, @Michael Shamsiev​​
#CostingStandard(CT-Foundation)

Tue February 22, 2022 07:17 PM

Great work on this!  I finally had time to give it a full read and I'm impressed with both your work and your methodology.  Nicely done!
#CostingStandard(CT-Foundation)

Fri February 18, 2022 06:20 AM

Nice work, team Natwest, and thank you @Julie Batty for submitting this story.

Was curious how the conversation went with the BUs that ended up paying more. Were you able to leverage these insights to reduce the unit price, so that even though they BU is paying more, their unit cost has reduced?

#powerofTBM​


#CostingStandard(CT-Foundation)

Thu February 17, 2022 09:44 AM

@Michelle McGuire - it's all applications that have licences within the group. This project was focused on Micro Focus but we're looking and working through Microsoft packages as well as Adobe​
#CostingStandard(CT-Foundation)

Wed February 16, 2022 05:58 PM

Bravo! I'm a huge fan of using license details and cross-referencing with other system data (eg Workday, Active Directory) to accurately identify the consumers.

I thoroughly enjoyed reading your post, too. Very exciting to follow along from where you started to your success. Fantastic work Julie! hi5​
#CostingStandard(CT-Foundation)

Wed February 16, 2022 12:18 PM

Does this only include FlexNet licenses or does FlexNet show all application licenses?
#CostingStandard(CT-Foundation)

Wed February 16, 2022 07:51 AM

@Guillermo Cuadrado :) thank you, very kind.

I think there's an element of luck for us as our Software Assessment Management team have moved under the TBMO and they use Flexera as a default and have worked through a number of issues​ over the last few years - definitely wasn't a small task
#CostingStandard(CT-Foundation)

Wed February 16, 2022 07:39 AM

There's no shame in this. Great initiative, @Julie Batty. We tried to do something like that with Flexera, but we gave up, as we found too many difficulties.
We use transaction counts where available.​
#CostingStandard(CT-Foundation)

Wed February 16, 2022 07:24 AM

Shamelessly spamming some of those on my contacts list to bump up the like count - apologies and thanks in equal measures :)

@Kyle Castro @Guillermo Cuadrado @Martyn Dawes @Jill Ferguson @Doug Greer @Juan Jose Jarillo @Justin Kean @Rhonda Keller @Shannon Maglaque @Gulcin Menekse @Michelle McGuire @Sarah Meldrum @Juliet Orgain @Jaitabh Jewel Sharma @Matt Temple @Menno Wittebol​​​​​​​​​​​​​​​​​​​
#CostingStandard(CT-Foundation)

Wed January 05, 2022 01:06 PM

Well done @Julie Batty and thanks for sharing your process here so others can learn from it!​
#CostingStandard(CT-Foundation)

Thu December 09, 2021 09:57 AM

That's a great idea @Julie Batty we did something similar with a niche software product and got positive results too!  Well done.​​
#CostingStandard(CT-Foundation)

Thu December 09, 2021 04:44 AM

Hi Julie,

I've had a number of conversations about 'instrumentation' of business applications & processes as a way to enable consumption-based charging, but never seen it done consistently, so this is very interesting.

The challenge always seems to have been the range of systems and amount of time it will take to retrofit usage reporting consistently, so I've generally found that broad business metrics are used (like headcount).

Any approach that improves on this, particularly if you can see the end-state and measure your progress towards it, must help to build the level of trust with your customers that you're looking for.


#CostingStandard(CT-Foundation)