Sandi is the author of the “SAM Starter Kit” published by The ITAM Review.
Formalizing an ITAM practice to include a repeatable, auditing process is on most CIO’s lists of things to do. Unfortunately it’s often at the bottom of the list. Other technology projects take priority as they will help a business unit become more efficient, allow sharing or harvesting of information, or prevent a company from running into a disaster non-recovery nightmare. These projects are all important. However, the question that needs to be asked is why isn’t ITAM higher on the priority list?
We all know that there are only so many hours in a workday, only so many hands and minds available on the IT team, and only so much time available for purchasing or legal to deal with licensing matters. IT is often juggling multiple projects, so where is the incentive to add one more to the list? Especially one that no other business unit cares about? Or one that gets in the way of those other business units getting what they need?…right now?
From a budgeting and contract negotiation perspective, knowledge is power. If you know what contracts are due when, what purchases will need to be made throughout the year, what kind of support will be required and how many licenses are actually in use at any given time; you will be in a much stronger position to negotiate prices and specific terms required to customize a contract for your organization’s benefit.
If a software publisher or software watchdog group calls up looking for information, having it immediately available can prevent time consuming and costly audits. A medium sized organization (250-1000 PCs) without accurate records can expect a disruption of anywhere from 3 weeks to 6 months to respond appropriately to an audit request. Suddenly the priority is high to avoid litigation and the extra expense of an external auditor, which can significantly throw off other projects previously labelled as high priority.
Effectively managing lease returns and redeployed hardware and software also becomes much more challenging when a formal ITAM process isn’t in place. The costs of not returning hardware on time and of over purchasing hardware and software can become much higher than the cost of assigning a dedicated asset manager.
A few years ago, I worked with a large enterprise that had been buying software for each new employee based on a standard configuration. However, because they hadn’t worked through the entire asset management process, they didn’t realize they were not redeploying all of the assets. By guiding them through the asset management lifecycle and formalizing the process, we discovered the company was spending an extra $300,000 per year on extraneous software licenses. Creating a business case for ITAM was pretty easy after that.
Sandi has been in the software business since 1991 and was one of the first Software Contract Administrators in Canada.
She has been providing consulting services since 1996, helping hundreds of clients to understand their obligations and rights under a myriad of contracts, and comparing licensing programs to find the most advantageous options for her clients.
About Martin Thompson
Martin is also author of the book "Practical ITAM - The essential guide for IT Asset Managers", a book that describes how to get started and make a difference in the field of IT Asset Management.
On a voluntary basis Martin is a contributor to ISO WG21 which develops the ITAM International Standard ISO/IEC 19770.
Learn more about him here and connect with him on Twitter or LinkedIn.