Implementing a SAM / ITAM tool, how long does it take?

As an implementation partner, we are often asked this question. We would like to give an unambiguous answer to that, but several factors play a role.

TIP #57 - September 2020: Which factors play a role when implementing a SAM /TAM tool? We highlight a few in this tip.

One very important factor is sponsorship. Experience shows that if an implementation is supported by the right sponsors and they are willing to propagate the importance, benefits and goals of this tool implementation widely, this contributes to much more collaboration and a shorter lead time of the actual implementation.

Stakeholder management is almost of similar importance. It is obvious to only involve employees and departments that are needed to bring the (technical) implementation to a successful conclusion. But consider also involving departments that might be interested in the data that the tool is able to deliver. Just think of configuration management, life cycle management, security management, but also contract management or the financial department. The more people see the importance of implementing SAM / ITAM tooling, the more, sometimes unexpected, contributions you can expect. 

Take a step-by-step approach. This may seem obvious, because with a technical implementation at least servers and databases need to be available before you can start any installation at all. But by the step-by-step approach we mean: try to get added value out of the tool as soon as possible. Almost all SAM / ITAM tooling works with agents that need to be installed on all devices in scope, which in many cases requires a large part of the total lead time of the project. However, you can choose to start connecting existing (inventory) resources such as SCCM, Altiris, ADDM and other ones available within the organisation. In practice, it turns out that up to 80% of all software inventory is already visible once these sources are connected. Therefore, a wealth of information is already available within earlier stages of the project. 

In short: apply the strengths of agile working to the project:

  • Appoint a product owner;
  • Form multi-disciplinary teams;
  • Add value during every step and deliver intermediate products.