Stakeholders, roles, relationships and service integration
Domain 4: Stakeholders, roles, relationships and service integration
This domain tests who does what, how ITAM connects to other practices, and why integration prevents asset data from becoming stale.
Roles
- Asset owner: accountable for a class of assets, often a senior manager.
- Asset manager: runs day-to-day ITAM processes and data.
- Configuration manager: owns CI data and relationships.
- Service owner: accountable for a service that consumes assets.
- Procurement, finance, legal, security, facilities and end users provide inputs and controls. Suppliers and partners provide asset data and lifecycle services. Use RACI to clarify accountability; each asset should have one accountable owner.
Integration
ITAM feeds and consumes service configuration management (CI relationships), incident and problem management (asset identity and warranty), change enablement (impact and approval), the service desk (requests and returns), financial management (cost and depreciation), supplier management (contracts and renewals), information security (data classification and disposal), deployment and release (build and move), and continual improvement (metrics).
Worked example
A failed laptop generates an incident. The service desk uses the asset tag to confirm warranty and ownership, and a replacement is ordered. Change enablement checks the CMDB for dependent software. Finance updates the register for the new asset and retires the old one. Without shared identifiers, each team would re-key data and create discrepancies.
Traps
- Treating ITAM as a finance-only function.
- Leaving accountability unclear across asset owner and asset manager.
- Excluding security and procurement until audit time.
- Integrating tools without agreeing data ownership.
Key points
- Asset owner is accountable; asset manager runs the process and data.
- Configuration manager owns CI data and relationships.
- ITAM must integrate with incident, change, finance, supplier, security and service desk practices.
- Shared identifiers prevent re-keying and discrepancies.
- RACI clarifies accountability across stakeholders.