Software Asset Management (SAM) - Revision history

User at 17:48, 23 November 2022

2022-11-23T17:48:02Z

User at 17:47, 23 November 2022

2022-11-23T17:47:34Z

User: The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

2021-02-06T18:25:48Z

The LinkTitles extension automatically added links to existing pages (https://github.com/bovender/LinkTitles).

User at 20:00, 9 January 2020

2020-01-09T20:00:51Z

User: Created page with "'''Software Asset Management (SAM)''' is all the capabilities necessary for the effective management, control and protection of software assets (be those on-premises or in the..."

2020-01-07T17:04:38Z

Created page with "'''Software Asset Management (SAM)''' is all the capabilities necessary for the effective management, control and protection of software assets (be those on-premises or in the..."

New page

'''Software Asset Management (SAM)''' is all the capabilities necessary for the effective management, control and protection of software assets (be those on-premises or in the cloud) throughout [[Software Development Life Cycle (SDLC)|all stages of their lifecycle]].<ref>Defining Software Asset Management (SAM) [https://www.softwareone.com/en/solutions/software-lifecycle-management/what-is-sam SoftwareOne]</ref>

ITIL defines SAM as:
''“All of the infrastructure and processes necessary for the effective management, control and protection of the software assets within an organization throughout all stages of the lifecycle.”''

'''Role of Software Asset Management (SAM) in Organizations<ref>Role of Software Asset Management (SAM) in Organizations [https://en.wikipedia.org/wiki/Asset_(computer_security) Wikipedia]</ref>''' 
SAM can serve many different functions within [[Organization|organizations]], depending on their software portfolios, [[IT Infrastructure|IT infrastructures]], resource availability, and [[Business Goals|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|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 an ongoing basis to determine the exact number of software licenses consumed, 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.

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
*Enforce [[Compliance|compliance]] with corporate security policies and desktop/server/mobile standards
*Improve worker productivity by deploying the right kinds of technology more quickly and reliably
*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)
*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

===See Also===
<div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
[[Software]] 
[[Software-Defined WAN (SD-WAN)]] 
[[Software Archeology]] 
[[Software Architecture]] 
[[Software Architecture Analysis Method (SAAM)]] 
[[Software Configuration Management (SCM)]] 
[[Software Design]] 
[[Software Development Effort Estimation]] 
[[Software Development Life Cycle (SDLC)]] 
[[Software Factory]] 
[[Software Non-functional Assessment Process (SNAP)]] 
[[Software Project Management]] 
[[Software Prototyping]] 
[[Software Sizing]] 
[[Software Visualization]] 
[[Software as a Service (SaaS)]]
</div>

===References===

@@ Line 29: / Line 29: @@
 *[[Software-Defined WAN (SD-WAN)]]
 *[[Software Project Management]]
-[[Software as a Service (SaaS)]]
+*[[Software as a Service (SaaS)]]
 </div>
 ===References===

@@ Line 22: / Line 22: @@
 ===See Also===
 <div style="column-count:2;-moz-column-count:2;-webkit-column-count:2">
-[[Software]]<br />
+*[[Software Architecture]]
-[[Software-Defined WAN (SD-WAN)]]<br />
+*[[Enterprise Architecture]]
-[[Software Archeology]]<br />
+*[[Client Server Architecture]]
-[[Software Architecture]]<br />
+*[[Software Development Life Cycle (SDLC)]]
-[[Software Architecture Analysis Method (SAAM)]]<br />
+*[[Software Design]]
-[[Software Configuration Management (SCM)]]<br />
+*[[Software-Defined WAN (SD-WAN)]]
-[[Software Design]]<br />
+*[[Software Project Management]]
 [[Software as a Service (SaaS)]]
 </div>

@@ Line 33: / Line 33: @@
 [[Software Factory]]<br />
 [[Software Non-functional Assessment Process (SNAP)]]<br />
 [[Software Project Management]]<br />
 [[Software Prototyping]]<br />

@@ Line 1: / Line 1: @@
-'''Software Asset Management (SAM)''' is all the capabilities necessary for the effective management, control and protection of software assets (be those on-premises or in the cloud) throughout [[Software Development Life Cycle (SDLC)|all stages of their lifecycle]].<ref>Defining Software Asset Management (SAM) [https://www.softwareone.com/en/solutions/software-lifecycle-management/what-is-sam SoftwareOne]</ref>
+'''Software [[Asset]] [[Management]] (SAM)''' is all the capabilities necessary for the effective management, [[control]] and protection of software assets (be those on-premises or in the cloud) throughout [[Software Development Life Cycle (SDLC)|all stages of their lifecycle]].<ref>Defining Software [[Asset Management]] (SAM) [https://www.softwareone.com/en/solutions/software-lifecycle-management/what-is-sam SoftwareOne]</ref>
 ITIL defines SAM as:
-''“All of the infrastructure and processes necessary for the effective management, control and protection of the software assets within an organization throughout all stages of the lifecycle.”''
+''“All of the infrastructure and processes necessary for the effective management, control and protection of the software assets within an [[organization]] throughout all stages of the lifecycle.”''
@@ Line 8: / Line 8: @@
 SAM can serve many different functions within [[Organization|organizations]], depending on their software portfolios, [[IT Infrastructure|IT infrastructures]], resource availability, and [[Business Goals|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|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 an ongoing basis to determine the exact number of software licenses consumed, 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.
+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|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 an ongoing basis to determine the exact number of software licenses consumed, 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.
-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.
+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:
+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
-*Enforce [[Compliance|compliance]] with corporate security policies and desktop/server/mobile standards
+*Enforce [[Compliance|compliance]] with corporate security policies and [[desktop]]/server/mobile standards
-*Improve worker productivity by deploying the right kinds of technology more quickly and reliably
+*Improve worker [[productivity]] by deploying the right kinds of technology more quickly and reliably
 *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)
-*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
+*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