Several other professions can appear to compete with ITAM, but all are primarily focused within their vertical.
ITIL (Information Technology Infrastructure Library) defines how IT services should be designed, created, and delivered. One intent is to position IT to be more customer-focused. ITIL also addresses ITAM; however, the focus is managing IT assets currently in use and part of service delivery.
COBIT is a framework like ITIL which focuses on how IT delivers services.
FinOps (Financial-Operations) is a discipline that makes IT more cost-conscious when designing, creating, and delivering IT services. FinOps' rise to fame came with cloud and for excellent reasons. Cloud vendors define a price catalog based on their services, making tracking the organization’s consumption of IT easier.
Cybersecurity frameworks from CIS, NIST, ISO, and others provide a list of IT security controls that should be implemented by IT security. These frameworks reference ITAM as a way to maintain an accurate inventory. Unfortunately, and unintentionally ITAM is reduced to counting assets. An accurate inventory requires a single body, the ITAM department, to manage the entire asset lifecycle.
The PMO’s (Project Management Office) focus is on applying the project management discipline to IT projects. The PMO is critical to ITAM because it is where new IT asset types are introduced or changes to IT assets occur. The project manager cannot acquire and use IT assets as they see fit just because a project has received a budget. The ITAM processes must be followed.
Other disciplines also interact with ITAM, including best practices for accounting, legal, and HR. ITAM needs to engage these disciplines to implement an ITAM Program successfully.
Unfortunately, without an ITAM Program, each of these disciplines may develop an ITAM Program to suit their specific needs. The result is a costly, incomplete ITAM Program with duplication of effort and no coordination.