Process Overview: IT Asset Management

Summary

IT Asset Management (ITAM) is a process used to manage the lifecycle of hardware IT assets within an organization. This process encompasses the acquisition, deployment, maintenance, and eventual disposal or reassignment of hardware assets. The core objective of ITAM is to enhance asset utility, reduce costs, maintain compliance, and mitigate both financial and operational risks.

IT Asset Management (ITAM) and Configuration Management (CM) are closely related to each other. Both processes help companies ensure their IT landscape supports the business processes as efficiently as possible. However, they are separate processes that approach the asset and configuration items from different angles. ITAM is concerned, for example, with the assets' value, location, ownership, and lifecycle aspects. ITAM answers questions like “Where are the assets located?”, “What is the value of these assets?", “When does the warranty of these devices end, and when do we have to replace them?” and so on.

On the other hand, the CM process focuses on providing accurate and reliable information about the configuration needed for providing various services and ensuring the Configuration Items (CI) taking part in the service provision are always available. Also, it provides important information about the relationships between CIs and, that way, helps in assessing the impact of changes related to CIs and services.

It's important to note that the processes overlap to a certain extent. For example, an application server is a concrete asset that some organization owns. It is located somewhere and has an intrinsic value that needs to be known and managed. However, the application server is also a CI that is managed by the CM process. The service is a critical component for running a certain service, and its dependencies to other CIs (such as other servers, database servers, databases, networks, and integrations) must be known and managed. Also, the availability and stability of the server and its dependencies must be managed. 

Both processes are crucial for other service management processes, such as Incident, Problem, and Change management. They allow support teams to resolve incidents faster and help IT teams minimize the adverse impact of changes in the IT landscape. 

The third area is the Software Asset Management process. That process focuses on managing software assets, such as software licenses. The following table summarizes the differences between Configuration Management, IT Asset Management, and Software Asset Management. 

IT Asset Management, Configuration Management, and Their Relation to the CMDB  

As mentioned above, ITAM and CM are separate processes with commonalities and some overlap. The CM process also typically manages many IT Assets managed by the ITAM process to ensure the relationships and dependencies related to service delivery are known and to ensure that the CIs are available and operational.  

The term Configuration Management Database (CMDB) is common in the context of the aforementioned processes. The CMDB can be seen as an outcome of the Configuration Management Process and, as a concept, should not be confused with the IT Asset Management process. However, from a technical perspective, the IT Assets are stored as datacards in the CMDB module of the Efecte Service Management Tool. This, however, is visible only to administrators.

Applying ITAM to Other Business Areas

While the ITAM process focuses primarily on IT Assets, the Efecte solution can easily be adapted for any other asset types relevant to the business needs. This flexibility allows organizations to extend asset management practices to areas such as facilities management, fleet management, and many other areas. In each case, the core principles of ITAM – tracking, lifecycle management, and financial oversight – can be applied to ensure efficient and cost-effective management of these assets.

For instance, in facility management, Efecte can help track maintenance schedules, warranty information, costs associated with various physical spaces or equipment, and several other aspects. This adaptability ensures a uniform approach to asset management across different business areas and provides a centralized platform for a holistic view of all organizational assets, leading to better decision-making and strategic planning.

ITAM in Efecte

The Efecte solution facilitates the ITAM process through various use cases described below. IT assets are managed as data cards in the Efecte Service Management Tool, and the asset status is used to describe the asset's lifecycle phase.  

Asset data can be imported by various means, such as: 

• One-time import from a file
• Dynamic imports through discovery tools 
• Imports through integrations from other tools and systems
• Manual entering of data in the Efecte Workspace

For example, the following IT asset types can be managed within the ITAM process. The ones mentioned below are managed on the Device template.  

• Workstations
• Mobile devices
• Displays
• Printers
• Servers
• Databases
• Network devices
• SIM cards
• Storages
• Backup devices

Automatic Inventory

Typically, IT Assets are fetched from automatic inventory and asset management tools by using the Efecte Integration Service. For example, Microsoft Intune, Device42, Miradore, Applixure, Microsoft System Center, and several others are possible sources can be used for fetching asset data. 

Use Cases

1. Asset Discovery and Recording
   1. Automatic discovery tools are utilized to gather detailed information on hardware assets, including workstations, servers, printers, network devices, mobile devices, and others. 
   2. The asset information is imported into the Efecte Service Management Tool, creating a comprehensive record of each asset's technical details, costs, and user information. 
   3. Manual registration is employed to ensure comprehensive asset documentation for assets not covered by automatic inventory.
2. Asset Relationship Mapping and Analysis
   1. Detailed records of asset interconnections are maintained, offering an in-depth view of the asset ecosystem. This mapping covers aspects such as asset ownership, user assignments, and technical specifications, providing a holistic understanding of asset relationships.
   2. The Efecte visual analyzer is used for visualizing the asset relationships.  
3. Lifecycle Tracking and Management
   1. The lifecycle of hardware assets is managed through status changes within the Efecte platform, tracking each asset from arrival through usage and maintenance periods to eventual disposal. This process ensures a clear view of each asset's status, aiding in effective maintenance and timely replacement or disposal decisions.
4. Financial Management and Reporting
   1. Financial elements, including asset costs, service pricing, and allocation to organizational units or cost centers, are integrated into the asset management system. This integration supports thorough financial analysis and aids in effective budgetary planning.
5. Asset Reporting 
   1.  The Efecte platform's reporting capabilities are used to create reports on asset lifecycles and other aspects. 
   2. IT Asset Reporting can also be used to identify assets causing incidents for supporting proactive Problem management activities.

Process Timeline

Terminology

Prerequisites

• Comprehensive Asset Discovery and Inventory
  • A foundational step for ITAM is the ability to discover and inventory as many IT assets as possible. This includes automated discovery tools for detecting and cataloging network assets and processes for manually entering assets that cannot be automatically detected.
• Accurate and Up-to-date Asset Repository
  • Maintaining a current and accurate repository of all IT assets is crucial for the other service management processes, such as Incident management, Problem management, Change management, Service request management, and Configuration management.
• Integration with Other IT Service Management Processes
  • ITAM should be integrated with other IT service management (ITSM) processes like Incident management, Problem management, Change management, Service request management, and Configuration management. 
• Skilled ITAM Team and Stakeholder Involvement
  • A dedicated team with expertise in ITAM practices is essential. In addition, involvement and buy-in from stakeholders across the organization, particularly from IT, finance, and procurement departments, are crucial for effective asset management.

Benefits

• Strategic Decision Making and Planning
  • ITAM provides valuable data and insights that aid in strategic decision-making and long-term IT planning. This includes understanding asset life cycles, planning for upgrades or replacements, and aligning IT infrastructure with the organization’s strategic goals and evolving needs.
• Improved Asset Lifecycle Management
  • ITAM allows organizations to effectively manage the entire lifecycle of each asset, from procurement to disposal. This lifecycle approach ensures that assets are efficiently utilized throughout their operational life and retired at the optimal time, maximizing their value to the organization while minimizing environmental impact and disposal costs. 
• Cost Optimization and Financial Management
  • ITAM helps organizations track and manage their IT assets efficiently, leading to significant cost savings. By having a clear understanding of the assets in use, their life cycles, and associated costs, companies can make informed decisions on asset purchases, maintenance, and retirement. This awareness aids in avoiding unnecessary expenditures and optimizing the use of current resources.
• Enhanced Productivity and Service Delivery
  • By ensuring that the right assets are available, well-maintained, and optimally utilized, ITAM contributes to higher productivity within the organization. A well-managed IT asset base supports smoother operations, reduces downtime, and enhances overall service delivery to end-users.
• Risk Reduction and Compliance
  • Proper ITAM ensures that all assets are accounted for, properly licensed, and compliant with relevant regulations and standards. This reduces the risk of legal and financial penalties associated with non-compliance, such as those arising from software licensing issues or failure to meet industry standards.