Pass the ServiceNow CIS-Hardware Asset Management CIS-HAM Questions and answers with CertsForce

The Procurement tab of the Hardware Asset dashboard is a graphical representation of the hardware asset procurement across the enterprise1.

The Procurement tab provides the following information1:

Hardware expenditure by vendor: This shows the total amount spent on hardware assets from each vendor in the current fiscal year. This helps to analyze the vendor performance and negotiate better contracts.

Requests that require sourcing: This shows the number and status of asset requests that need to be fulfilled by purchasing new hardware assets from a vendor. This helps to prioritize the procurement activities and optimize the inventory levels.

Therefore, the information that are also options in the question are C. Hardware expenditure by vendor and F. Requests that require sourcing.

The other options that are not information on the Procurement tab are:

Hardware nearing end of warranty: This is an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that are nearing or have expired their warranty period1.

Hardware model normalization status: This is an information on the Normalization tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are normalized or not normalized1.

Hardware models up for end of life: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are approaching or have reached their end of life date1.

New hardware assets found by audits: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that were discovered by the asset inventory audit process but were not previously recorded in the CMDB1. References:

1: Hardware Asset Dashboard

Hardware model normalization is a feature that enables users to normalize the details, such as manufacturer, product, model, and device type, of hardware and consumable models1

Hardware model normalization uses the data from the models and compares it against the data in the Hardware Model Normalization Content Service, which is a cloud-based service that provides standardized and enriched information about hardware models1

Hardware model normalization sets the normalized display name for each model record based on three attributes: Name, Manufacturer, and Model number2

The Model Management tab of the Hardware Asset dashboard shows the status of the hardware models in the Product Catalog, such as Matched, Match Not Found, or Not Normalized3

Several of your models are listed as Match Not Found on the Model Management tab of the Hardware Asset dashboard. This means that the normalization process could not find a matching rule in the Content Service for those models3

The potential causes of this are34:

The hardware model content has not yet been downloaded from the Content Service. The Content Service is updated periodically with new and updated rules for hardware models. You need to download the latest content from the Content Service to ensure that your models are normalized with the most accurate and complete information. You can download the content manually or schedule it to run automatically.

Normalization could not match any of the three key fields in the hardware model form with a rule in the Content Service. The three key fields are Name, Manufacturer, and Model number. If any of these fields are missing, incorrect, or inconsistent with the data in the Content Service, the normalization process will fail to find a matching rule. You need to review and correct the data in these fields to ensure that they match the data in the Content Service.

A normalization rule for the hardware model does not exist in the Content Service. The Content Service may not have a rule for some hardware models, especially if they are new, rare, or custom-made. In this case, you can create a custom rule for the hardware model in the Hardware Model Normalization Rules module, or submit a request to the Content Service team to add a rule for the hardware model.

According to the ServiceNow Hardware Asset Management overview document1, the total cost of ownership (TCO) of an asset is the sum of all direct and indirect costs incurred throughout its lifecycle, from acquisition to disposal1.

The original costs are the costs involved in purchasing an asset and putting it into use, such as lease, delivery, and spare parts12.

Lease is the cost of renting or leasing an asset from a vendor or a third party for a fixed period of time12. Lease costs can vary depending on the terms and conditions of the contract, such as duration, frequency, and interest rate2.

Delivery is the cost of transporting or shipping an asset from the vendor or the warehouse to the end user or the location where it will be used12. Delivery costs can include fees, taxes, customs, and insurance2.

Spare parts are the cost of purchasing or stocking additional or replacement parts for an asset in case of failure, damage, or wear and tear12. Spare parts costs can depend on the availability, quality, and compatibility of the parts2.

The other options are not original costs, but rather ongoing or disposal costs. Maintenance is the cost of repairing, servicing, or upgrading an asset to keep it in good working condition12. Storage is the cost of storing an asset that is not in use or waiting for disposal12.

According to the ServiceNow Hardware Asset Management documentation, the core sets of data required for effective IT asset management are:

•Manufacturers: The companies that produce the hardware assets, such as Dell, HP, Cisco, etc.

•Locations: The physical places where the hardware assets are stored or used, such as offices, data centers, warehouses, etc.

•Users: The people who own, use, or manage the hardware assets, such as employees, customers, vendors, etc.

•Models: The specific types or categories of hardware assets, such as laptops, servers, routers, etc.

Fixed assets in ServiceNow are classified as long-term assets that are used in operations and have a useful life exceeding one year, such as equipment, buildings, and vehicles. They are distinct from intangible and short-term assets.

Normalization mappings are a feature of the Hardware Asset Management (HAM) application that allow you to standardize the manufacturer name, model name, and model number of hardware assets in the Configuration Management Database (CMDB)1.

Normalization mappings are created by matching the values from the discovery source to the values in the Product Catalog2.

Normalization mappings help you to fully normalize hardware models by ensuring that the asset data is consistent, accurate, and complete3. References:

Hardware Normalization

Create normalization mappings

What is Hardware Asset Management?

Hardware normalization is a process that standardizes the data of hardware and consumable models by using the United Nations Standard Products and Services Code (UNSPSC) and a set of rules12.

Normalization can be performed manually or automatically on models in the model catalog12.

If a model has been normalized, it will have a check mark in the Normalized column in the model list1.

To revert the normalization of a model, you can use the Revert Normalization UI action, which is available on the model form13.

The Revert Normalization UI action will restore the original values of the model attributes that were changed by the normalization process13.

The Revert Normalization UI action will also clear the Normalized check mark and the Normalization Source field on the model form13. References: Work with hardware normalization - ServiceNow - Now Support, Hardware Asset Management builds onCore Asset Management - ServiceNow, Automation Simplifies Hardware Asset Management - ServiceNow Blog, Product Documentation | ServiceNow

Stock rules are the rules that define the minimum and maximum quantities of hardware assets in a stockroom1.

Stock rules help to optimize the inventory levels and avoid overstocking or understocking of hardware assets1.

Stock rules have the following purposes:

To automatically transfer assets when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system automatically creates a transfer order to replenish the stockroom from another stockroom that has excess quantity of the same asset1.

To send notifications when a low quantity threshold is detected in a stockroom: This means that when the quantity of a hardware asset in a stockroom falls below the minimum threshold defined by the stock rule, the system sends an email notification to the stockroom manager or other stakeholders to alert them of the low inventory level1.

Therefore, the purposes of stock rules that are also options in the question are A. To automatically transfer assets when a low quantity threshold is detected in a stockroom and C. To send notifications when a low quantity threshold is detected in a stockroom.

The other options that are not purposes of stock rules are:

To track stock orders from a vendor: This is not a purpose of stock rules, but a function of purchase orders. Purchase orders are the records that capture the details of the vendor contracts for procuring hardware assets2. Purchase orders help to track the status, quantity, and cost of the stock orders from a vendor2.

To track stock movement between stockrooms: This is not a purpose of stock rules, but a function of transfer orders. Transfer orders are the records that track the movement of hardware assets between stockrooms3. Transfer orders help to track the source, destination, quantity, and status of the stock transfers between stockrooms3.

To send notifications when a stock shipment arrives at a stockroom: This is not a purpose of stock rules, but a function of stock order tasks. Stock order tasks are the tasks that track the fulfillment of asset requests from stockrooms4. Stock order tasks help to send notifications when a stock shipment arrives at a stockroom and when the assets are received and verified4. References:

1: Stock Rules

2: Purchase Orders

3: Transfer Orders

4: Stock Order Tasks