Software asset management (SAM) is a business practice that involves managing and optimizing the purchase, deployment, maintenance, utilization, and disposal of software applications within an organization.
Ivanti Asset Manager
Ivanti Asset Manager (IAM) is a much talked about “new” product that was released with ITxM 2018.3 and actively promoted with ITxM 2019.1.
ITxM 2019 in fact consists of Ivanti Service Manager (ISM) and Ivanti Asset Manager (IAM).
Ivanti Asset Manager has been around for a while and Ivanti Service Manager, formerly known as HEAT, has done Asset Management since its early HEAT for Windows days in the 1990’s.
Software Asset Management followed a little later with the HEAT ITSM using Software Inventory and Software Product Configuration Items (CI).
IAM Business Objects
To someone new to ISM/IAM the SAM implementation looks like something of a “Frankenstein hodge podge”. There is a combination of Legacy, DSM, and IAM business objects, and relationships. That is by design. Upgrades from HEAT SM, DSM, and ISM to IAM vary, as do discovery tools and sources, plural, (more on that on a future post) and so do requirements as per business processes and standard operating procedures (SOP).
Getting Started with SAM
Strategy. Architecture. Processes. There really is not quick and easy way to just “install”SAM. Careful consideration, planning, and data analysis is required to determine where you are today, where you want to go, and the steps to take you there. While there are some common practices and implementation methods, every organization has variances that must be considered, carefully. What are your sources? What data are you capturing, where and how? What processes are manual versus automated. How are you tracking your licenses and entitlements today, what details, and at what level. Vendors, Manufacturers, Versions, Features, License Keys, etc. What does you procurement process look like? Alerts, renewal reminders? It’s best you start simple with data analysis, process analysis, document workflows, processes, entity relationships (ERD), and build a proof of concept, followed by a prototype to validate each step of the process.
If your Software Asset Management really is a simple slam-dunk, then all of the above steps will be very quick, but I can almost certainly guarantee you from experience that there are always variances. The devil is in the details as you say. And usually with the most complex and expensive software titles and products.
Before you tackle the gargantuan task of software asset management be sure to contact a19 Consulting Professional Services and put yourself in the hot seat with the a19 Software Asset Management audit.