ISO19770-1:2012 SAM Process Guidance

ISO19770-1:2012 SAM Process Guidance: A kick-start to your SAM programme

RORY CANAVAN
Copyright Date: 2012
Published by: IT Governance Publishing
Pages: 76
https://www.jstor.org/stable/j.ctt5hh4vd
  • Cite this Item
  • Book Info
    ISO19770-1:2012 SAM Process Guidance
    Book Description:

    While ISO 19770-1 describes processes and activities for addressing effective software asset management, it does not offer guidance on how to approach the implementation of a SAM programme – this pocket guide fills the gap and shows you how to do it. Helping to address the aforementioned issues, ISO19770-1:2012 SAM Process Guidance: A kick-start to your SAM programme, is aimed at anyone looking to gain a better understanding of the concepts of software asset management and the resulting benefits it can bring to their business.

    eISBN: 978-1-84928-440-0
    Subjects: Technology

Table of Contents

  1. Front Matter
    (pp. 2-4)
  2. FOREWORD
    (pp. 5-5)

    This booklet has been written to offer guidance on software asset management (SAM) principles, as conveyed by ISO19770-1:2012. In addition to which, practical guidance is offered in kick-starting your SAM programme. It is also worth noting what this booklet won’t cover:

    It will not cover licensing guidance.

    It will not cover system guidance.

    It will not offer legislatory/regulatory guidance.

    These topics (although mentioned) are considered too vast to cover for the scope of this publication....

  3. ABOUT THE AUTHOR
    (pp. 6-6)
  4. ACKNOWLEDGEMENTS
    (pp. 7-7)
  5. Table of Contents
    (pp. 8-8)
  6. INTRODUCTION
    (pp. 9-12)

    If you are reading this book, it is probably with the intention of gaining a decent grounding in the concept of software asset management (SAM), and the benefits it can bring to your business. Regardless of where your organisation is in respect of any economic climate, managing IT should never be treated as an afterthought; and, if we can summarise the four main aspects of what an IT director might reasonably oversee at a very base level, we can see that SAM has the potential to cover a sizeable domain:

    software

    hardware

    people

    money

    Getting these elements to seamlessly interact...

  7. CHAPTER 1: WHY SOFTWARE ASSET MANAGEMENT?
    (pp. 13-16)

    Risk: Imagine a situation whereby, after protracted legal negotiations, a software company said they would ‘ask for their software back’. This is not the stuff of a John Grisham novel; the right of ‘delivery up’ is a very real threat. Furthermore, consider the alternative situation, where a piece of software initially offered as ‘free ’ was found in an organisation; however, the small print attached to the licence meant that it was only free for the first 60 days of use, and that thereafter the company was liable for an £8,500 bill for each and every install. This happened; scarily...

  8. CHAPTER 2: THE ISO19770-1: 2012 FRAMEWORK
    (pp. 17-46)

    Whilst this booklet should support/pique your interest in SAM and the processes required to make it an effective business practice, I would strongly recommend obtaining a copy of the Standard itself – available from the ISO website: (www.iso.org). Please ensure you obtain the correct standard; -2 concerns itself with the rules pertaining to Software Identification Tags; -3 is centred on the specifications relating to Product Use Rights.

    ISO19770-1 focuses on 27 processes/activities which it deems core to addressing effective software asset management – these are divided as follows (see Figure 2, Figure 3 and Figure 4).

    Corporate governance process for SAM: This...

  9. CHAPTER 3: THE KICK-START TO YOUR SAM PROGRAMME
    (pp. 47-67)

    For those of you unfamiliar with the concept of Mind Maps,®the idea behind them is that you use them as a thought-provoking tool. The above proposal came about as a result of a question on LinkedIn (www.linkedin.com) from within the ITAM Review Networking Group (which is hosted by the excellent Martin Thompson –www.linkedin.com). Martin started a discussion around the methods that programme managers were using to keep track of their SAM programmes. On one such project I recently worked, the programme manager used a Mind Map to keep abreast of developments. Someone then asked if such a...

  10. CHAPTER 4: HOW TO WRITE A PROCESS
    (pp. 68-70)

    For those starting out in the world of SAM, who might have been foxed by the thought of writing their own processes, I thought it would be a useful exercise to offer some tips and tricks I have picked up.

    Start with a really simple title: The simpler the title, the easier it will be to convey why the process exists.

    List the objectives of the process: Consider what you want the process to achieve.

    Identify the stakeholders: At some point you will need other people’s buy-in for this process to become BAU, so know who you need to go...

  11. CHAPTER 5: CONCLUSION
    (pp. 71-72)

    ISO19770-1 should be the heartbeat of any SAM process work embarked upon by a company, but success is every bit as dependent on the choice of system(s) and the people required to use the framework, as having the right policies and procedures in place.

    Next steps:

    Be clear on your goals (investigate the SMART acronym from operations management studies).

    Scope the coverage of your intended SAM programme.

    Conduct a risk assessment, gap analysis and/or maturity assessment.

    Gain senior management approval for any major programme of work.

    Align ISO19770-1 goals and objectives to any other standards, legislation, or best practice requirements....

  12. ITG RESOURCES
    (pp. 73-76)