Atlassian made Hardware Asset Management (HAM) and the Assets Common Data Model (CDM) generally available in Jira Service Management on September 10, 2026 (Makarand Gomashe). Service Collection customers get a purpose-built HAM console inside JSM—hardware schemas, workflows, reporting, and lifecycle processes on a shared data model. New sites can start on CDM immediately; existing customers must migrate to CDM to unlock the console.
HAM is ITAM for physical gear: laptops, servers, mobiles, network kit—from request through procurement, deployment, maintenance/repair, return/refresh, and disposal. The console centralizes inventory (assets, models, stockrooms), ships 10+ MVP dashboard metrics with AI insights, an OOTB Asset Management space template with 10+ request types and 35+ fields, 15+ automation templates, plus depreciation and stock rules—so repair routing and fulfillment stop living in spreadsheets beside ITSM.
Same-day follow-up from Himanshi Gaba covers AI-powered HAM: six Hardware Insights (Expiring Warranties, Low Stock Alerts, Dormant Assets, Over-assigned Assets, Incident-Prone Assets, Incomplete Models) plus four Rovo skills—/search-hardware, /hardware-setup, /hardware-configuration, /hardware-insights—for plain-English inventory queries and setup without digging through menus.
The TIX angle is the ticketed lifecycle: procurement, fulfillment, deployment, repair, return, refresh, and disposal become first-class request types on the same JSM platform as incidents and service requests. Incident-Prone Assets closes the loop—recurring reliability issues flag the hardware that keeps generating tickets—so ITSM tickets and asset records stop living in separate silos. That is also a CRM/QMS chain: employee experience on refreshes, plus auditable custody and sanitization on disposal.
Tradeoff remains Atlassian-cloud gravity: CDM migration for incumbents, Service Collection / JSM entitlements, and Rovo skills that are not (yet) MCP-exposed. Setup docs cover enablement, tracking, and import into CDM. For shops that need ticketed hardware without another SaaS CMDB bolted beside the plant, the pattern still matters—lifecycle request types + incident-to-asset linkage on one spine.
For N23D, HAM GA shows enterprises want hardware lifecycles as real tickets—not a side spreadsheet and a hopeful CMDB. N23D ships as one local-first Rust binary: TIX work orders with vaulted asset context, linked to CRM service and QMS custody you own when the cloud SKU or AI skill pack changes.
Sources/References
- Atlassian Community — From Data Standards to Hardware Tracking: CDM and HAM GA in JSM (Makarand Gomashe, September 10, 2026)
- Atlassian Community — AI-Powered capabilities in Hardware Asset Management in Jira Service Management (Himanshi Gaba)
- Atlassian Support — Set up Hardware Asset Management
- Atlassian Support — Track hardware using Hardware Asset Management
- Atlassian Support — Import your hardware data
- N23D — TIX stack page
- N23D — CRM stack page
- N23D — QMS stack page