Vector’s accurate, fast and automated PC software inventory simplifies software audits and underpins software license compliance.
- Unique ‘Triple Pass’ software identification technique.
- Underpins software license compliance.
- Application license serial key discovery.
- Complete software change history.
"...exceptional data collection capabilities to help organizations ensure that software stays up to date and in compliance."
Key Capabilities and Features
Software License Compliance, and Software Asset Optimization, are not activities that suit a corner-cutting approach. Our customers rely on the Vector AM Software Inventory component to analyze their installed software accurately and in depth.
Vector Software Inventory uses a ‘Triple Pass’ technique, in which three methods are employed to maximize software identification and minimize the extraneous noise seen in other simplistic software inventory tools. The raw results generated by the three methods are presented in the tabbed display of the Software Identification Manager.
The first pass uses a rules based analysis, where directory contents are analyzed against the identification rules in the Known Applications Library. Rules may be based on file information – names, sizes, dates, etc – or on VersionInfo file header data, or on ARP registry information. A RuleWizard facilitates the creation of additions to the Known Applications Library.
If an application is not recognized from the Known Applications Library, Vector Software Inventory will interrogate file headers to determine a Provisional Identification – one of the three tabs in the Identification Manager display. Using the raw information collected from the networked PCs, you have the ability inspect the file header information yourself, to make a final decision on how that header information can be employed in a permanent identification rule.
If no identification can be made from file header information, Vector Software Inventory will look for correlation of executables with information in the Add/Remove Programs Registry.
Applications are ‘promoted’ from provisional identification with file header or ARP Registry information to confirmed identification and addition to the Known Applications Library through the RuleWizard.
The Software Inventory results are stored in the Asset Management database, and are accessible through a comprehensive set of Web-based reports in the Asset Reporting Portal.
Scaling
Software Inventory employs a two stage process of data collection and analysis. A collection agent (either permanent or transient) collects raw file information from the PC and sends it across the network or over the internet to a collection point. This raw information is then processed away from the PC, using scheduled tasks which can be distributed to optimize processor loads and network traffic. This combination of raw data collection and offline analysis permits the highest level of sophistication in the analysis phase while minimizing the impact on the client PCs. Our customers regularly analyze software inventory for populations of over 10,000 PCs held in a single database. The drill-down reporting in the Asset Information Portal provides information at every level from organization summary to individual PC.
PC Configuration Management
Hardware Inventory organizes data into categories for easy viewing and analysis. This structured approach is particularly productive in the PC-PC comparison function in the Hardware Inventory viewer in the Administrator Console. This function provides support staff with a fast, easy to use method of comparing one PC’s configuration with another’s to determine root cause of performance problems.
The Console and the Asset Information Portal both also provide a comprehensive suite of Change History reports; any suspected exceptional changes to memory, disk, processor speed or any other key characteristics will be easy to find.
ISO 19770 and ITIL
Vector Software Inventory meets the key practical demands of following ISO 19770-1 and ITIL best practices in Software Asset Management, and of implementing a program of Software Asset Optimization. The Known Applications Library enables you to record your total license entitlement for each application, and this information is used in the drill-down Compliance Reports in the Asset Reporting Portal. Vector’s multi-pass approach to software identification is ideal for extension to embrace the new software asset tag technology being developed under ISO 19770-2.
Vector Asset Vizor
Vector Asset Vizor supports the definition and storage of information on any other asset types. Further detail on Vector Asset Vizor
click here.
Vector Software Optimization combines software usage data with business workflows to ensure wastage and reduce software expenditure.
- Find unused or underutilised software on your desktops.
- Monitors end users active window every 10 seconds.
- Clear and powerful drill down software utilisation reporting.
- Unique software metering support for thin client environments.
"Excellent automated reporting features create fast high-level overviews of software usage and deep, granular data on software titles"
Software Optimization Overview
Software Usage is monitored at a very high level of accuracy that starts with a sampling process that records the identity of each desktop’s active window every 10 seconds. Simply recording application start and close times, as with many other asset management products, can never provide an adequate picture of real software usage. The sampled data is compacted by a simple, non-intensive process at each desktop before being relayed to a data collection location through either the LAN/WAN infrastructure or through an internet connection when it is available. The data is then analyzed in two passes by routine tasks run by the Vector Asset Management task scheduler.
The Administrator Console and the Asset Reporting Portal both provide standard reports which summarize applications usage on a per-application basis and on a per-PC basis. A special family of reports, the Microsoft Office Optimization Reports, provides in depth analysis of the use of the main components of the MS Office Standard and Professional suites, identifying situations where it may be beneficial to adopt single product licensing, or move from Pro to Standard. At the very least, the information should be useful in supporting negotiation with your Microsoft software supplier.
License Harvesting
Accurate software usage information collected over extended periods provides firm information to support projects to harvest and reallocate unused application licenses.
Application Virtualization
In discussion with customers, Vector finds that a universal starting point for discussion of whether to virtualize desktops is an understanding of the nature of the organization’s use of its applications software. A high level of usage of CPU and graphic intensive applications may suggest that a given group of PCs would be better left running installed applications natively, or using a streaming technology to ensure frequent updates are easily administered.
Vector License Manager facilitates adoption of ISO 19770-1 as the basis for continuous improvement of software asset management and license compliance enabling organizations to demonstrate that it takes SAM seriously.Software License Compliance and Software Asset Management
Software License Compliance and Software Asset Management
Software Asset Management and Software License Compliance are often confused in many organizations, with neither given adequate attention.
Accurate software asset identification, which is vital to both overall SAM and compliance, is such a challenge that it acts as a disincentive to effort. Further, many of the software inventory tools in the market today are only partially successful with software identification reporting – application suites being a particular problem.
Book Demo
Learn about VIZOR
As a result, many organizations simply accept the risks of non-compliance on the one hand and the costs of over-provisioning on the other. A lack of understanding of the laws surrounding copyright frequently put organizations’ reputations at risk, and in some instances cost a lot of money when court action is taken by the BSA, an organization that pursues non-compliant organizations on behalf of their software vendor members.
The recent upsurge in interest in corporate governance, including the SOX requirement to properly value an organization’s assets, has begun to filter down to IT. Included here is the need to quantify the value of software owned by the organization. In turn, this creates an environment in which the whole management of software assets becomes more significant.
The positives behind establishing SAM procedures are clear to anyone who looks for them. Leading arguments include:
- Better overall organizational processes
- Minimized over-licensing and elimination of under-licensing
- The potential to actually optimize software assets in line with business needs
- Mitigation of financial and legal risks
- Increased awareness for standardized IT environment and processes
- Knowledge on how to handle software and licenses during mergers, de-mergers and acquisitions
Why Software Asset Management (SAM) needed ISO 19770-1
Having recognized some or all of these benefits, personal champions of the SAM cause drove a few organizations to become more pro-active and to begin to evolve their own SAM policies and processes. But, unlike other areas of IT such as Change Management which received massive focus through ITIL, there was no ëHow Toí for managing software assets. Talking with attendees at events such as the annual conference of the International Association of IT Asset Managers, or a
Budd Larner seminar on negotiating software contracts, confirms that organizations by and large make up their SAM policies as they go.
ISO19770-1 fits into this gap. In a seven year process starting in 1997, various groups worked on drafts for ISO 19770-1 leading to its eventual publication in 2006. Interested parties included ITIL, the UK Federation Against Software Theft (FAST), and the JTC1/SC7 ISO/IEC Joint Technical Committee Sub-Committee 7 on Software and Systems Engineering.
Software License Compliance and ISO 19770-1
It is important to understand that ISO 19770-1 is not a prescriptive standard for either software license compliance or for the constituent activities of compliance, such as software inventory. What it does, is set out a foundation or baseline for a comprehensive set of processes for overall software asset management.
So, while ISO 19770-1 is not a standard for software licensing compliance, if the appropriate sections are implemented, then compliance will follow. Compliance becomes just one aspect of software asset management over which the organization will gain control.
ISO 19770-1 processes and Software License Compliance
The 27 processes covered by 19770-1 are organized into three main categories:
Organizational Management Processes for SAM; this includes:
- Control Environment for SAM
- Planning and Implementation Processes for SAM
Core SAM Processes; this includes:
- Inventory Processes for SAM
- Verification and Compliance Processes for SAM
- Operations Management Processes and Interfaces for SAM
Primary Process Interfaces for SAM;’ principally:
- Life Cycle Process Interfaces for SAM
This may sound daunting, but it was not intended that organizations necessarily adopt every element of ISO 19770-1. Rather, they would relate these processes to their operations and identify areas of priority for improvement. It is not intended that this standard be used to judge whether an organization ‘Does SAM’ or ‘Doesn’t do SAM’. Its intentions are far more pragmatic, aimed at supporting organizations in a process of continuous improvement.
Neither are tools vendors categorized as ‘ISO 19770-1 compliant’, but the standard does provide vendors such as Vector Networks with a list of areas of capability on which to call in setting out product roadmaps.
Achieving Software License Compliance will be greatly helped by taking guidance from the Core SAM Processes, grouped into:
- Inventory Processes for SAM
- Verification and Compliance Processes for SAM
- Operations Management Processes and Interfaces for SAM
Each process in ISO 19770-1 is defined by its Objectives and Outcomes. The ‘how’ is left to the organization to decide. So for example, for the process of ‘Software Asset Control’, one of three in the ‘Inventory Processes for SAM’ group, ISO 19770-1 declares the Objective to be:
“...to provide the control mechanism over software assets and changes to software and related assets while maintaining a record of changes to status and approvals.”
The Outcomes are listed as:
“Implementation of the Software asset control process will enable the organization to demonstrate that:
a) An audit trail is maintained of changes made to software and related assets including changes in the status, location, custodianship and version
b) Policies and procedures are developed, approved and issued for the development, maintenance and management of software versions, images/builds and releases.
c) Policies and procedures are developed, approved and issued which require that a baseline of the appropriate assets is taken before a release of software to the live environment in a manner that can be used for subsequent checking against actual deployment.”
ISO 19770-1 and Vector’s Software Asset Optimization Method
Many organizations have experienced huge pressures on costs during 2008 – 2010 and those pressures are now unlikely to ever go away. The motivation and business case for the time and effort involved in software asset management are here to stay.
With effort constrained by staffing levels, organizations need to find rapid payback from the most easily identified and implemented opportunities. To assist with this, Vector sets out a simple closed loop process we call Software Asset Optimization.
Vector’s approach to Software Asset Optimization identifies four basic characteristics of any software asset:
- The number of copies required, and by which users
- The number of licenses owned
- The number of copies deployed, and where
- The usage patterns of every deployed copy
The first and fourth of these are not strictly required within ISO 19770-1, but Vector believes them to be important to cost and asset optimization. Both our Asset Manager Pro solution and the Software License Compliance and Optimization solution include modules to address these needs.
The Application Package Policy Manager (PPM) provides a policy-based method to quantify the numbers of copies needed of each application, and the Software Usage Monitoring module identifies unused software and provides drill-down reporting into application usage.
Any discrepancy between any two characteristics represents a problem of non-compliance, wasted assets, or inappropriate provisioning. Organizations can prioritize the classes of discrepancy that correspond most closely to their organization objectives. At any point in time, compliance may be deemed more important than cost savings, resulting in a focus of alignment between the second and third characteristics – ownership and deployment.
We offer more guidance on this concept in a free-to-download white paper, and can provide consulting and support for any organization wishing to attack the optimization opportunity. Call +1 770-622-2850 today.
Other Advantages of Adopting ISO 19770-1
The way in which the standard is constructed allows organizations to take a ‘pick-and-mix’ approach to identifying areas in which they can make the most immediate progress. It provides a check-list to identify areas of weakness and potential business risk either through non-compliance or waste of resources.
Adopting ISO 19770-1 as the basis for continuous improvement of software asset management and license compliance would enable an organization to demonstrate that it takes SAM seriously enough to match today’s corporate governance directives.
ISO 19770-1 is not expensive. It can be bought online as a PDF from several sources, such as
www.bsigroup.com,
www.iso.org for less than US$250.