HAM / Asset Management

averma1 · 10 hours ago

Hey Folks,

Hope all are doing good !!!

My organisation is using AMI(Asset Tracker) to deal with assets which is also pushing the data to servicenow as a part of integration. I am afraid that if they have done anything with the IRE before integration as I can see data anomalies, I am new here but want to have a standardised ServiceNow approach to be followed since beginning to avoid rework - If we remove data anomalies , can we use this data to implement CSDM stages like Crawl, Walk, Run & Fly without having HAM implemented.

Do you think this is the right approach or we should go for HAM choosing the most appropriate resource categories as what we want?

Please note : I am seeking an advice to avoid any future re work on data like here in my case. I have found HAM is the best way to make data more reliable, compliant and auditable whereas AMI Asset tracker is very well with physical scanning of stocks using RFID. Of course, I need to check cost parameters as well, so advise on cost also will help me to decide.

Your help will make difference !!

@Randy Scrapper

#HAM #assset #hardwareassetmanagement

tiagomacul · 3 hours ago

Great question — you’re right to think about data quality and the long-term approach before building processes on top of it.

🔎 AMI (Asset Tracker) vs. HAM

AMI/Asset Tracker tools are excellent for scanning and feeding raw inventory into ServiceNow (especially with RFID or barcode).
But ServiceNow itself relies on the Identification and Reconciliation Engine (IRE) and a normalized data model (CSDM + HAM) to make that data trustworthy and actionable.
Without HAM, you can still store assets in the alm_asset table and move forward with CSDM crawl/walk/run/fly stages, but you’ll miss:
- Normalization and reconciliation (avoiding duplicates/anomalies).
- Lifecycle management (procure → in stock → in use → retired).
- Compliance and audit features (entitlements, contracts, disposal).

✅ Best practice approach

Clean the anomalies first (deduplicate, validate against your CI/asset model). Starting with bad data only multiplies rework later.
If HAM is in scope for your organization, it’s strongly recommended — HAM provides the standardized processes and data structures that align with CSDM and make the asset lifecycle auditable.
Use AMI/Asset Tracker for the discovery/inventory source, but let HAM manage the lifecycle in ServiceNow. This gives you the best of both worlds.

💰 Cost considerations

HAM is a licensed SKU, so yes, you’ll need to check budget.
Many organizations start with CSDM crawl → walk using the core asset tables, then transition to HAM once budget allows. If you go this route, design your data model in line with CSDM from the beginning, so migration to HAM is smoother.

Configuration Management Database (CMDB) in ServiceNow: Loading Computers Effectively

The Configuration Management Database (CMDB) is one of the most crucial components of the ServiceNow platform, as it provides a centralized view of IT assets and their interrelationships. Properly loading computers into the CMDB is essential to ensure efficient and accurate IT service management. This article explores the process and best practices for populating computers into the ServiceNow CMDB.

What is the CMDB?

The CMDB is a repository that contains all data related to IT components, known as Configuration Items (CIs). These items can include hardware, software, network components, and other critical assets. The CMDB helps organizations understand the structure of their infrastructure and make informed decisions related to IT service management.

Importance of Loading Computers into the CMDB

Complete Visibility: Accurate information about computers helps build a comprehensive view of organizational assets.
Change Management: The CMDB provides a foundation for assessing the impact of infrastructure changes, minimizing risks.
Improved Incident Resolution: With up-to-date data, support teams can quickly identify issues, reducing resolution times.

Steps to Load Computers into the CMDB

Data Collection
Gather relevant details about computers, such as:
- Hostname
- IP address
- Operating system
- Location
- Hardware properties
Data Preparation
Organize the collected data in a format compatible with the ServiceNow CMDB. This often involves creating a CSV file or using import tools.
Use of Discovery Tools
ServiceNow provides automation tools to streamline the process:
- Discovery: Automatically detects and maps computers on the network, feeding real-time information into the CMDB.
- Import Set: For data not discoverable automatically, Import Sets allow bulk loading into the CMDB.
Data Validation
After loading, it is essential to validate the data in the CMDB. Verify accuracy and make adjustments as needed to avoid redundancies or gaps.
Ongoing Maintenance
The CMDB is a dynamic entity. To keep the data accurate and relevant, continuous updates and maintenance are required.

Best Practices

Automation: Use automation tools whenever possible to reduce human error and ensure consistent updates.
Documentation: Maintain clear documentation of the loading process and the information stored in the CMDB for future reference.
Training: Regularly train your team to use the CMDB effectively and understand the importance of the data being managed.

Conclusion

Loading computers into the ServiceNow CMDB is a fundamental task that requires careful attention and proper practices. By following the steps above and adopting best practices, organizations can ensure their CMDB remains accurate and up-to-date, leading to optimized IT service management. Data visibility and precision are critical for successful IT operations, and the CMDB is the foundation upon which everything is built.

👉 For more details, see the official ServiceNow documentation or join the community to share experiences and tips on CMDB management.