Each stage requires a process in order to move on to the next stage, and documenting your organisation’s process for every stage is a must.
Let’s use the end of life stage as an example. Software harvesting and license reuse is a process within this stage. Your organisation must be able to define the purpose and benefit of this process, as well as specific activities that must be performed in order for the process to function well, come to completion and restart the cycle.
Once you have an understanding of your process requirements within each stage, you’ll be able to compare those needs with all of the features of your IT asset management tools to see if your bases are covered, or if you will have to supplement via other means.
ITAM tools need to adapt to your tech environment.
At the end of the day, an IT asset management tool is a technology investment . So it’s critical that the technology works with — not against — your existing infrastructure.
Keep in mind that this goes for technology that already exists within the organisation as well as technology that doesn’t.
For example, let’s say Company A has been using manual processes for collecting IT procurement data for the last decade or so. Every IT purchase made exists in an Excel spreadsheet. Then, a new IT asset management tool is introduced. What happens to all of the past data? A data migration project is on the horizon, but what’s the most efficient way of moving everything over?
Now, let’s say Company B already has an e-procurement platform that tracks IT purchases. It works well, but the company wants to introduce a more holistic tool. Is the existing system designed to talk to the new one? If not, Company B and Company A look the same, even though one has existing software in its environment and one doesn’t.