From time to time, customers ask whether we have an API to import data into Express Software Manager from their enterprise purchasing systems.  Although it’s not something we promote directly on our web site (perhaps we should?), the answer is “yes.”  Our API provides for two-way data flow; you can pull data either from Express Software Manager for integration into an external purchasing system, or vice versa.  The API does not currently have connectors for specific purchasing systems, but with a little development expertise, you can have it up and running in no time. 

If you’re interested in knowing more about our API, please contact your account representative. 

(more…)

As most of our customers know, software usage analysis is a critical component of effective IT asset management, offering a means to analyze whether software investments are being fully utilized, ensure concurrently-licensed apps are being used within proper usage limits, and evaluate usage patterns of unauthorized applications within your environment.  This month, we’ll take a look at the “Software Usage Statistics” report, one of Express Software Manager’s most widely used reports, which provides valuable insight into application usage patterns within your organization. 

The Software Usage Statistics report, when filtered by license unit, helps you determine the percentage of any given application launched within a specifed time frame, as well as more granular details such as average amount of time used (or unused) per day.  These statistics provide clues as to which applications may be underutilized and represent opportunities for re-harvesting and/or renegotiating license agreements to better reflect actul usage.   In other situations, the report can be used to examine the prevalence of unauthorized, harmful, or “nuisance” applications within your organization.  To investigate further, you can click on any of the displayed license units to see usage patterns for each application on individual machines, and even sort that data based on usage to see which machines show the highest and/or lowest amount of activity.   

(more…)

One of the reports I suspect few people know about is the Activity Log.  It’s actually one of the oldest reports found within Express Software Manager, dating back to version 3.0, when it was still a pure software metering tool!  Little known to many of our customers, the Activity Log is a fantastic troubleshooting tool that can be used in any number of situations (some of which are described below). 

The Activity Log summarizes application usage based on license unit(s), machine(s), user(s) or server(s), with a level of detail that you won’t find in any other of Express Software Manager IT asset management reports.  This can be used to pinpoint applications being launched on specific machines or by specific users, as well as what remote devices and/or users are accessing applications on your Citrix or terminal server.  With usage data such as start and end time, idle time, and total time launched, you can zero in on all kinds of activities taking place on your network that are extremely useful from a troubleshooting standpoint. 

Here are some ways our customers have used the Activity Log report.

(more…)

An article caught my eye this morning in Manufacturing Business Daily summarizing the results of a recent Ernst & Young survey that focused on software asset management philosophies and practices among software vendors and their customers.  

Before discussing the results, I should point out that I’m pretty skeptical about studies conducted and published by firms with a commercial interest in the topic being explored.  Because Ernst & Young dedicates part of its business to IT governance, internal auditing, and compliance services for large enterprises, it’s virtually impossible for the firm to be objective in its research methodology or interpretation of results–in fact, they offered no information about their approach to the survey.  (For example, is there inherent bias among those selected to participate?  What were the roles with respect to compliance of those individuals or teams that actually completed the survey?  Why did they recruit end-user organizations that averaged over 10,000 desktops [organizations of this size comprise only 0.1 percent of all US companies over 100 employees]?  Is it possible to draw conclusions relevant to the marketplace with so few participants?  The list goes on and on.)

Nevertheless, the results are interesting and at least on the surface validate what we’ve long suspected to be the true motives behind vendor audits; software publishers are far more interested in revenue generation than they are in protecting their intellectual property or helping customers be successful in managing their software estates.  Only four of the eight “major” software publishers surveyed stated that protection of intellectual property rights is an objective of their compliance programs, flying directly in the face of the very legal platform software vendors and the BSA claim as the basis of their actions.  It’s also ironic that only 38% of vendors suggested that their compliance programs, which are generally advertised as “SAM” programs, have customer education and/or process improvement as a stated goal. 

(more…)

The following bylined article can also be found in the April issue of IAITAM’s ITAK Magazine and the April edition of FAST IiS Kaleidoscope.

Since the dawn of the desktop era, IT departments have struggled to keep track of software installed across their corporate networks.  Accurate software inventories are crucial to ensuring installed applications are properly licensed, understanding whether or not they’re being used, and budgeting for future software purchases.  Unfortunately, no standard methodology exists across applications and manufacturers for correlating installed program executables with actual application titles.  This leaves asset managers and the software discovery tools they utilize with any number of half-complete approaches to application recognition.

Driven by licensing challenges stemming from inaccurate and incomplete software identification, the ISO/IEC 19770-2 software tagging standard has been developed, providing publishers with guidelines for “tagging” their applications in a standard way that makes identification straightforward, automated, and virtually foolproof for discovery tools.  Yet despite the technical ease with which software tags can be implemented, publishers have been painfully slow to adopt the standard, and end users have not pressed vendors hard enough to spur them to action. 

(more…)