Scribd
Upload
228 views4 pages

Software Asset Management Key Notes

The document discusses software asset management, including its objectives, costs, implementation approaches, and recommendations for organizations. It describes key areas like service strategy, design, transition, operation, and continual improvement. It also covers the types of assets that need management, risks associated with software, and legal exposures of externally acquired software.

Uploaded by

Kate
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
228 views4 pages

Software Asset Management Key Notes

The document discusses software asset management, including its objectives, costs, implementation approaches, and recommendations for organizations. It describes key areas like service strategy, design, transition, operation, and continual improvement. It also covers the types of assets that need management, risks associated with software, and legal exposures of externally acquired software.

Uploaded by

Kate
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Software

Asset
Management
Key Notes
1. Introduction

Software asset management (SAM) is 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 their life cycle.
The underlying justification for SAM is the need to apply good corporate governance to an
organizations software assets. Corporate governance is the system of rules, practices and
processes by which a company is directed and controlled. Corporate governance essentially
involves balancing the interests of a company's many stakeholders, such as shareholders,
management, customers, suppliers, financiers, government and the community
The overall objective of Sam is to manage, control and protect organizations software
assets, including the management of the risks arising from the use of those software assets.
Cost
People
Tools
Accommodation
Interfaces
Corrective licenses
Implementation Approaches
Internal project involves the use of resources within an organization to
implement the SAM processes. It is preferred approach if the necessary SAM skills
and knowledge are present and available within the organization.
Partnership project involves the use of external partner of partners to assist with
the implementation of SAM/
Outsourced project or managed services involves contracting an external
organization or partner to implement the complete activity to agreed key
performance indicators (KPIs) aligned to project critical success factors (CSFs)
The following is the suggested minimum set of recommendations for software asset
management in any size or type of organizations:
Vision it should include other ITIL services areas and be aligned with other
businesses and organizational strategies and visions
Information Technology Infrastructure Library, is a set of detailed practices for
IT service management (ITSM) that focuses on aligning IT services with the
needs of business.
Decision about centralization
Responsibilities and policies responsibilities should include risk management
for contractual and legal risks. Policies should make clear the obligations of all
officers, employees and contractors and the consequences of violations. These
policies should be consistent with other policies in use within the organization.
Skills and competence
Detailed strategy
Contracting choose appropriate partners, including those for the supply of
software. Ensure that software purchasing arrangements are structured to
minimize cost while still ensuring control.
Procedure establish robust procurement, deployment and retirement
procedures that ensure compliance with policies and which themselves capture
necessary information and assets, especially proof of license.
Inventories
Reconciliations the frequency of the reconciliation will depend on the
effectiveness of procedures for accurate record-keeping and license management,
but should not be less than yearly.
Cost-benefit analysis

The following areas can be briefly described as follows:


Service strategy provides guidance on how to design, develop and implement
service management, not only as an organizational capability but also as a
strategic asset.
Service design provides guidance for the design and development of services
and service management processes.
Service transition provides guidance for the development and improvement
capabilities for transitioning new and changed services into operations.
Service operation provides guidance on achieving effectiveness and efficiency in
the delivery and support of services so as to ensure value for the customer and
the service provider.
Continual service improvement provides instrumental guidance in creating and
maintaining value for customers through better design, transition and
operation of services.

2. Context
The major types of asset that need to be managed within ICT are:
Computer and network equipment
Environment equipment
Buildings and facilities
Software assets
Data and databases
Processes and policies
Documentation and contracts
People
Significant legal and financial risks associated with special characteristics:
Risk of software being used without licenses being purchased
Risk of the loss of proof of licenses which have been purchased
Risk of terms and conditions being breached unknowingly
Risks of incorrect reliance on resellers
Risk of loss licenses
A piece of software within the ICT environment may consist of all or some of the
following components:
The master copy of the software itself on the master media
Distribution copies of the software on free-standing media or on servers
The software license certificate or other proof of license
Terms and condition of license
Support contracts
Software pass codes or license keys
Software maintenance authorization codes
The software release documentation
Upgrade components
The installed operational instances of the software
One of the main exposures with externally acquired software is the legal exposure that
comes with use contrary to terms and conditions or legislation. The legal basis for this
exposure depends on the country and contractual conditions, but mainly comprises:
Copyright legislation
Trademark legislation
Contract

You might also like