Best Practice for Infrastructure Assets in HAM Pro (Request → Lifecycle)
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 hours ago
Hello,
I’m working on implementing Infrastructure Assets in ITAM using HAM Pro and would appreciate guidance on best practices.
We want to capture assets from request → procurement → deployment → disposal, but we’re struggling with a few areas:
- Request process: Is it better to use catalog items tied to specific models, or keep requests more generic for infrastructure?
- Model management: Infra models often change or aren’t fully known upfront—should models be enforced at request, or defined later during procurement/receiving?
- Capturing purchases: What’s the best way to ensure all infrastructure purchases create assets reliably (Requisition → PO → Asset)?
- Starting point: For teams early in ITAM maturity, how do you balance process simplicity vs. data quality?
Goal is to build a simple but controlled intake process that ensures full lifecycle tracking without overcomplicating model management.
Any recommendations or lessons learned would be greatly appreciated!
Thanks!
0 REPLIES 0
