LICENSEWARE

ITAM Handbook: ITAM and ITSM

Learning resource: migrated from the LICENSEWARE Notion wiki (ITAM Handbook, ITAM and ITSM, last edited 2024-10-11). It is training material, not a cited encyclopedia article; for the cited reference see IT asset management.

On This Page

This chapter of the ITAM Handbook covers how IT service management (ITSM) and IT operations work in a large enterprise, and where IT asset management (ITAM) fits in.

IT Service Management

IT Service Management (ITSM) is the process of managing and delivering IT services to an organisation’s customers, both internal and external. ITSM helps ensure that IT services are aligned with business needs, delivered efficiently, and meet agreed-upon service levels.

There are several key components of ITSM, including Incident Management, Problem Management, and Change Management.

Incident Management

Involves the process of identifying, recording, and resolving incidents to restore normal service operations as quickly as possible. For example, if a user’s computer crashes, the IT department would use an Incident Management process to restore the user’s computer to its normal operating state.

Problem Management

Involves identifying the root cause of incidents and working to eliminate them. This helps prevent similar incidents from happening in the future. For example, if multiple users are experiencing slow network speeds, the IT department would use Problem Management to identify the cause of the slow network speeds and work to eliminate the underlying issue.

Change Management

Is the process of controlling changes to IT infrastructure in a structured manner. This helps minimise the risk of disruptions to IT services. For example, if the IT department wants to upgrade the operating system on a server, they would use Change Management to ensure that the upgrade is properly planned, tested, and implemented.

Change Management for new projects

When supporting new projects, Change Management becomes especially important as changes to the IT infrastructure can have a significant impact on the success of the project. Here are some examples of how Change Management can be applied:

  1. New Software Implementation. When implementing new software, the IT department must ensure that the software is properly tested, and integrated with other systems and that any necessary hardware upgrades are in place. Change Management would involve a structured process for evaluating, approving, and implementing these changes to minimise the risk of downtime or other issues.
  2. Network Infrastructure Upgrades. If a new project requires increased network bandwidth or new networking equipment, Change Management would be necessary to ensure that the upgrade is properly planned, tested, and implemented. This would involve identifying any potential risks or impacts to existing services, coordinating with other teams as necessary, and scheduling the upgrade during a time when it will have the least impact on users.
  3. Cloud Migration. If a new project requires migrating applications or services to the cloud, Change Management would be necessary to ensure that the migration is properly planned, tested, and implemented. This would involve identifying any potential risks or impacts to existing services, coordinating with cloud providers, and scheduling the migration during a time when it will have the least impact on users.

In all of these cases, Change Management would involve a structured process for evaluating, approving, and implementing changes to the IT infrastructure to minimize the risk of downtime or other issues. By following a well-defined Change Management process, the IT department can ensure that new projects are delivered on time, within budget, and with minimal disruption to existing services.

IT Operations in a Big Enterprise

IT Operations in a big enterprise are responsible for managing and maintaining the IT infrastructure. This includes hardware, software, and services, as well as providing support to users. Typically, IT Operations are structured into teams that specialise in different areas, such as server management, networking, or desktop support.

Here are some examples of standard operations and common mistakes in IT Operations:

Hardware Migrations

Hardware migrations involve moving data and applications from one server or storage device to another. This can be a complex process, involving careful planning and coordination with other teams. Common mistakes in hardware migrations include failing to assess the license requirements changes for the new hardware, breaching geographical restrictions for certain software systems, and upgrading to newer versions without the appropriate upgrade rights.

Provisioning New Services and Systems

When the enterprise needs to deploy new applications or services, IT Operations are responsible for provisioning the necessary hardware and software. This may involve setting up new servers or storage devices, installing software, and configuring networks. Common mistakes in provisioning new services and systems include failing to review the licensing requirements of the new project and deploying unlicensed software.

Desktop Support

The desktop support team is responsible for providing technical support to end-users, including troubleshooting hardware and software issues, installing software, and configuring systems. Common mistakes in desktop support include installing software from unapproved sources and ignoring security protocols.

The Role of ITAM in the Enterprise

IT Asset Management (ITAM) is the process of managing the lifecycle of hardware and software assets in an enterprise. ITAM is critical to ensuring that the enterprise has a complete understanding of its IT infrastructure, which helps to optimise resource utilisation, reduce costs, and ensure compliance with regulatory requirements. In this section, we’ll explore the role of ITAM in the enterprise.

Asset Tracking and Inventory Management

ITAM involves the tracking and management of all IT assets in the enterprise. This includes hardware such as servers, desktops, laptops, and mobile devices, as well as software licenses and applications. Asset tracking and inventory management are critical components of ITAM, as they provide the enterprise with a complete understanding of its IT infrastructure, allowing IT Operations to optimise resource utilization and minimize downtime.

Vendor and License Management

ITAM is also responsible for managing vendor relationships and software license agreements. This includes ensuring that the enterprise is in compliance with vendor licensing rules and regulations, as well as identifying opportunities for cost savings by renegotiating license agreements or consolidating software licenses.

IT Budgeting and Cost Optimisation

ITAM plays a critical role in budgeting and cost optimisation by providing the enterprise with a complete understanding of its IT infrastructure and associated costs. This includes identifying opportunities for cost savings, such as by reducing software license usage or reallocating hardware resources.

Compliance and Risk Management

ITAM is also responsible for ensuring that the enterprise is in compliance with regulatory requirements related to IT infrastructure. This includes ensuring that software licenses are being used in compliance with vendor agreements, as well as ensuring that data security protocols are being followed to minimise the risk of data breaches.

In summary, ITAM is critical to ensuring that the enterprise has a complete understanding of its IT infrastructure, which helps to optimise resource utilisation, reduce costs, and ensure compliance with regulatory requirements. By tracking and managing IT assets, managing vendor relationships and license agreements, optimizing IT budgets and costs, and ensuring compliance and risk management, ITAM plays a critical role in the success of the enterprise.

See also

Esc