Talk:Software asset management/Temp

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Software Asset Management[edit]

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 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 copies installed. 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 installations, comparing this information with the number of licenses purchased, 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]

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 standards[4]
  • 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)[5]
  • 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[6]

International Standards Organization (ISO)[edit]

In 2006, the International Organization for Standards (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 of 2006. Part 1 of the standard details SAM processes including control environment, planning and implementation, inventory, verification and compliance, operations management and life cycle.[7]

Part 2 of the standard is still in progress, and seeks to define a model that will help improve software identification processes.

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 Standards and International Electrotechnical Commission, 2006-05-01, p. 5 {{citation}}: |access-date= requires |url= (help); Cite has empty unknown parameter: |coeditors= (help)CS1 maint: date and year (link)
  3. ^ "What is SAM?". Microsoft. Retrieved 2008-03-19.
  4. ^ Dunn, Ian (2004). "SAM Best Practice" (PDF). Federation Against Software Theft. Retrieved 2008-03-19. {{cite web}}: Unknown parameter |coauthors= ignored (|author= suggested) (help)
  5. ^ "Information technology — Software asset management-- Part 1: Processes", International Standard, International Organization for Standards and International Electrotechnical Commission, 2006-05-01, p. 19 {{citation}}: |access-date= requires |url= (help); Cite has empty unknown parameters: |coeditors= and |coauthors= (help)CS1 maint: date and year (link)
  6. ^ "Microsoft Software Asset Management: Step-by-Step Training - Step 4". Microsoft. Retrieved 2008-03-19.
  7. ^ "Information technology — Software asset management-- Part 1: Processes", International Standard, International Organization for Standards and International Electrotechnical Commission, 2006-05-01 {{citation}}: |access-date= requires |url= (help); Cite has empty unknown parameters: |coeditors= and |coauthors= (help)CS1 maint: date and year (link)

External Links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=Talk:Software_asset_management/Temp&oldid=468868514"