Software asset management

From Wikipedia, the free encyclopedia
Jump to: navigation, search

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. According to the Information Technology Infrastructure Library (ITIL), SAM is defined as “…all of the infrastructure and processes necessary for the effective management, control and protection of the software assets…throughout all stages of their lifecycle.”[1] Fundamentally intended to be part of an organization’s information technology business strategy, the goals of SAM are to reduce information technology (IT) costs and limit business and legal risk related to the ownership and use of software, while maximizing IT responsiveness and end-user productivity.[2] SAM is particularly important for large corporations in regards to redistribution of licenses and managing legal risks associated with software ownership and expiration. SAM technologies track license expiration, thus allowing the company to function ethically and within software compliance regulations. This can be important for both eliminating legal costs associated with license agreement violations and as part of a company's reputation management strategy. Both are important forms of risk management and are critical for large corporations' long-term business strategies.

SAM is one facet of a broader business discipline known as IT asset management, which includes overseeing both software and hardware that comprise an organization’s computers and network.

Role within organizations[edit]

SAM can serve many different functions within organizations, depending on their software portfolios, IT infrastructures, resource availability, and business goals.

For many organizations, the goal of implementing a SAM program is very tactical in nature, focused specifically on balancing the number of software licenses purchased with the number of actual licenses consumed or used. In addition to balancing the number of licenses purchased with the amount of consumption, an effective SAM program must also ensure that the usage of all installed software is in keeping with the terms and conditions of the specific vendor license agreement. In doing so, organizations can minimize liabilities associated with software piracy in the event of an audit by a software vendor or a third party such as the Business Software Alliance (BSA). SAM, according to this interpretation, involves conducting detailed software inventories on a periodic basis to determine the exact number of software consumption, comparing this information with the number of licenses purchased, reviewing how the software is being used in respect to the terms and conditions and establishing controls to ensure that proper licensing practices are maintained on an ongoing basis. This can be accomplished through a combination of IT processes, purchasing policies and procedures, and technology solutions such as software inventory tools.[3]

Counting installations is the most common means of measuring license consumption but some software is licensed by number of users, capital, processors or CPU Cores.

More broadly defined, the strategic goals of SAM often include (but are not limited to) the following:

  • Reduce software and support costs by negotiating volume contract agreements and eliminating or reallocating underutilized software licenses[2]
  • Enforce compliance with corporate security policies and desktop/server/mobile standards
  • Improve worker productivity by deploying the right kinds of technology more quickly and reliably[2]
  • Limit overhead associated with managing and supporting software by streamlining and/or automating IT processes (such as inventory tracking, software deployment, issue tracking, and patch management)[4]
  • Establish ongoing policies and procedures surrounding the acquisition, documentation, deployment, usage and retirement of software in an effort to recognize long-term benefits of SAM[5]

Role in other financial aspects[edit]

Fund management plays very vital role in maintaining big aspects in financial management too. It formulates the organized cash flow projections. It maintains expenses, taxes, leverage costs and interest income transactions, analyse them care fully.[6]

Use in financial Aspects

  • Know driving returns on investments
  • Cash Shortfalls, deferred payments, leverage costs etc.
  • Calculate different leverage options and Analyzing the effects on these returns
  • Maintain systematic and centralized fund modeling, and analysis

SAM Technology[edit]

A number of technologies are available to support key SAM processes:

  • Software inventory tools intelligently “discover” software installed across the computer network, and collect software file information such as title, product ID, size, date, path, and version.
  • License manager solutions provide an intelligent repository for license entitlements which can then be reconciled against data provided by Software inventory tools to provide the organization with an 'Effective License Position' or view of where the organization is under-licensed (at risk of a compliance audit) or over-licensed (wasting money on unnecessary software purchases).
  • Software metering tools monitor the utilization of software applications across a network. They can also provide real-time enforcement of compliance for applications licensed based on usage.
  • Application control tools restrict what and by whom particular software can be run on a computer as a means of avoiding security and other risks.[7]
  • Software deployment tools automate and regulate the deployment of new software.
  • Patch management tools automate the deployment of software patches to ensure that computers are up-to-date and meet applicable security and efficiency standards.
  • Request management tools allow employees to place requests for software products using a centralized form and process specifically designed to capture and assess specific license requirements as well as to manage and track the procurement and deployment process.
  • Product catalog tools capture product specific information such as name, edition, version and license agreement types as well as other key top level information for products used within the business. This information normalizes product naming conventions with the organization and allows mapping between other technologies tools used in the composite SAM solution.

International Organization for Standardization (ISO)[edit]

Main article: ISO 19770

In 2003, the International Organization for Standardization (ISO) and the International Electrotechnical Commission (IEC) began working with the SAM industry to develop a standard of best practices for software asset management programs. Standard ISO/IEC 19770-1:2006, Information technology – software asset management – Part 1, was published by the ISO and IEC in May 2006. Part 1 of the standard details SAM processes including control environment, planning and implementation, inventory, verification and compliance, operations management and life cycle.[8] A revision of this standard was published in 2012. This revised standard is designed to allow the implementation of SAM processes to be "accomplished in multiple increments and to that increment most suited to the needs of the organization."[9]

ISO/IEC 19770-2:2009 – Part 2: Software identification tag;[10] establishes specifications for tagging software to optimize its identification and management.

Using software identification tags or SWID tags makes discovery a simpler and more accurate process that can be verified by software vendors if they audit an organisations entire estate.

Issues with scalability[edit]

An example of issues faced when scaling up discovery tools is with Microsoft's System Centre Configuration Manager (SCCM). Using metering rules to monitor software deployment and usage across a small estate is relatively easy and reliable given the total number of unique executables (.exe files) and the number of instances of each executable. Turning on metering rules for every packaged application and every executable in a large estate quickly makes the volume of data generated unmanageable and expensive to maintain.

See also[edit]

References[edit]

  1. ^ ITIL’s Guide to Software Asset Management
  2. ^ a b c "Information technology – software asset management – Part 1: Processes". International Standard. International Organization for Standardization and International Electrotechnical Commission. 2006-05-01. p. 5. 
  3. ^ "What is SAM?". Microsoft. Retrieved 2008-03-19. 
  4. ^ "Information technology — Software asset management-- Part 1: Processes". International Standard. International Organization for Standardization and International Electrotechnical Commission. 2006-05-01. p. 19. 
  5. ^ "Microsoft Software Asset Management: Step-by-Step Training - Step 4". Microsoft. Retrieved 2008-03-19. 
  6. ^ Asset Management | Asset Management Software
  7. ^ Ogren, Eric (2006-11-03). "Application control coming your way". ComputerWorld. Retrieved 2008-04-03. 
  8. ^ "Information technology — Software asset management-- Part 1: Processes". International Standard. International Organization for Standardization and International Electrotechnical Commission. 2006-05-01. 
  9. ^ International Standard ISO/IEC 19770-1:2012 (2012-06-13). Information technology — Software asset management-- Part 1: Processes and tiered assessment of conformance. International Organization for Standardization and International Electrotechnical Commission. p. vi. 
  10. ^ http://www.iso.org/iso/catalogue_detail.htm?csnumber=53670

External links[edit]