There are S.L.O.N.a in parts. Implement ITAM and not choke (Part 2)

There is no universal sequence of ITAM implementation steps. But there is a backbone that can suit most companies. Not included in the "skeleton" of the project processes become the individual characteristics of the implementation.

In a previous post I shared my experience:

• where better to start the implementation of ITAM solutions;
• what to rely on when choosing an IT asset management model;
• what are the features of the basic stages of implementation.

In this article I want to continue the topic and tell:

• how to build a resource-service and resource-financial model of accounting for IT assets;
• what are the specifics of license and vendor management;
• what are the growth points.

What parts does IT asset management include?

The sum of the components of which the ITAM practice consists is conventionally called “S.L.ON.N.” These components include:

• agreements;
• licenses;
• equipment;
• intangible assets.

S.L.O.Na divide into large parts:

• identification and tracking of changes in IT assets;
• procurement planning and write-off of IT assets;
• building a resource-service and resource-financial models for accounting for IT assets;
• license and vendor management.

The specifics of the first two parts are analyzed in the previous article.

Today, through a prism of a goal → steps → results, I will review the remaining ones.

Building a resource-service and resource-financial models for accounting for IT assets

When information about IT assets is accumulated in the IT system, the vector of using this information can be expanded. We begin to take into account all contracts with contractors in which we incur costs for IT assets, we associate IT assets with the Fixed Asset.

What we want to achieve:

1. Get information about the purpose of using IT assets (the work of which Service they support).
2. Collect information about the cost of ownership of the IT asset and the cost of providing the Services.
3. Develop cost planning mechanisms within budget lines.

What steps are performed:

1. We download information on contracts, costs, depreciation and residual value of IT assets from accounting systems (linked through the Asset).
2. We enter information about the links between IT assets, thereby forming a resource-service model.
3. We use communication resource-service model and information from accounting systems to form a financial model for the allocation of costs for IT assets.
4. We are planning an IT budget.

The result of the control purposes for the use of IT assets we get:

1. Reduced idle IT assets.
2. Control of critical IT assets.
3. Improved asset utilization.

As a result of optimizing IT costs:

1. The allocation of expensive services, activities and operations.
2. Making a decision about outsourcing.
3. Improved budget planning.
4. Control budget execution.

License and IT asset management

The next important step is to work with suppliers of IT assets. This is a separate part of the ITAM- "elephant", where we take into account all the obligations of suppliers, contracts with them, including the conditions of support.

Redefine the goals:

1. Optimize license costs.
2. Organize the process of controlling suppliers.

What we do:

1. We collect data under licenses.
2. We form a licensed model.
3. We unify the rules of interaction with suppliers.
4. We carry out categorization and measurement of the quality of cooperation with suppliers.

The result of optimizing license costs will be:

1. Consolidation of licenses, search for more profitable licensing schemes.
2. Reducing the number of licensed products, their unification.
3. Improved licensing terms by consolidating information.
4. Increase license utilization.

When organizing control over suppliers, we obtain:

1. Measurable and transparent processes for working with suppliers.
2. Cost savings through consolidation and standardization.
3. Simplify Supplier Relationships.
4. Contract management as an independent asset.

How to develop an IT asset management system

When large parts of the SLO.N.A are implemented and automated, you can think about the development of the IT system.

To the points of growth I attribute:

1. Policy development - from requirements for suppliers to internal requirements. Support and development of corporate standards for IT assets.
2. The use of IT assets in project activities - services, installations, licenses.
3. Knowledge management in IT assets - a database of articles with typical solutions to incidents and service requests, documentation, instructions, FAQ

As a result, we obtain a multicomponent picture of the combined and interconnected parts of the ITAM- “elephant”.

What is the result

Own practice of implementing ITAM-solutions pushes to the following conclusions:

1. The IT asset management process is multicomponent.
2. S.L.O.N.a can be “eaten”, but not entirely in one approach.
3. Already at the start of implementation, it is necessary to determine what goals we are striving for and what steps we are performing at each of the stages.
4. There are always points of growth, because ITAM is not limited to gathering information about IT assets and tracking their changes.

---

What to read:

There are S.L.O.N.a in parts. Implement ITAM and not choke (Part 1)

IT asset management: how myths affect projects

Implementation of ITAM-solutions: how to get rid of myths