6 Common Shortcomings of Systems Management Tools When Used for IT Asset Management
Software asset managers and IT pros tasked with taking on license optimization, risk management and audit readiness frequently come to us after months or years of frustration because the data they are using to perform these tasks isn’t fit for purpose.
The source of this problem is systems management tools have some IT asset discovery and inventory capabilities, and may perform some ITAM functions, such as detecting vulnerabilities (and patching them) or identifying EOL software on a subset of devices. But that is where the similarities between systems management and IT asset management platforms end. These platforms perform different functions in your organization. In short, you need both systems management and IT asset management capabilities to have reliable, secure, efficient and compliant technology.
The good news is these platforms can leverage each other’s data to improve outcomes. For example:
- IT asset management platforms can ingest systems management IT asset inventory data.
- IT asset management platforms can identify applications missing from SSO to improve password protection.
- System management platforms can patch vulnerabilities identified by IT asset management platforms.
- IT asset management platforms can feed comprehensive and normalized data to your CMDB, so IT pros can better perform risk assessments of configuration changes or respond to incidents.
| Key Functions of Systems Management | Key Functions of IT Asset Management |
| – IT asset discovery and inventory – Performance monitoring – Patch management – User activity monitoring – Antivirus – Capacity management – Configuration management – Identity and access management | – IT asset discovery and inventory – Software normalization and augmentation – Reconciliation reporting for audit defense – Cost optimization insights – Application rationalization insights |
| Key Benefits of Systems Management | Key Benefits of IT Asset Management |
| – Improved reliability of devices and applications – Improved security of applications with patching, performance metric anomaly detection & log analysis and antivirus – Hardware/storage/network optimization | – License compliance and prevention of audit fines – Reduced licenses costs/over-buying of software – Improved security by detecting vulnerabilities, EOL/EOS applications and shadow SaaS applications |
6 common ways systems management tools fall short for performing IT asset management functions
- No visibility to modern applications and infrastructure. Many systems management tools were built two to three decades ago, at a time when everyone went to the office and all devices and applications were managed by agents. Over the last five years, we’ve seen an explosion in spending on cloud infrastructure, container use and SaaS applications. Gartner® estimates organizations spend $1,040 per employee on SaaS and forecasts that spend will grow 15-20 percent annually. Without visibility to these environments, IT professionals have gaping blind spots in detecting risk, maintaining software compliance and controlling costs.
- Lacks the ability to do effective license position (ELP) reporting. Most systems management tools do not have a mechanism for importing contracts and entitlement data. As a result, spreadsheets are required to marry application installation data with entitlement.
- Does not support discovery or usage data for some of the most expensive, and commonly audited vendors. To determine your ELP for these complex vendors and applications (SAP, Oracle Databases and Database Options, Oracle Middleware, Oracle Java, Adobe and IBM), you need detailed usage data and an ITAM platform that will scan for details, like use of Java.
- No automated cost optimization insights. Without usage data, and the ability to report on application usage by category, IT pros are unable to identify potential savings opportunities when preparing for renewals or in application rationalization initiatives.
- Limited or no application normalization and enrichment. If you are bringing in data from third-party sources, it is imperative that you have the ability to normalize application names, versions, vendors, etc. and enrich application data with end-of-life and end-of-service dates, application categories and so on.
- Limited support for feeding data to third-party CMDBs. Some systems management vendors include a CMDB but the majority lack integrations to third-party CMDBs. ITSM practitioners spend a lot of time ingesting and reconciling data from multiple sources into their CMDB of choice. Having an accurate, normalized and comprehensive IT asset data source helps save time and improves the incident-and-problem-resolution process.