ServiceNow CIS-HAM - Certified Implementation Specialist - Hardware Asset Management

A transfer order is a document that is used to execute the movement of hardware assets from one stockroom location to another within the same organization1.

A transfer order is created when there is a need to replenish, share, or relocate hardware assets between different stockrooms1.

A transfer order consists of one or more transfer order lines, each containing the information about the asset to be moved, such as the model, quantity, source stockroom, destination stockroom, and expected delivery date1.

A transfer order can be created manually or automatically based on predefined rules or thresholds1.

A transfer order goes through several stages, such as draft, approved, shipped, received, and closed1.

A transfer order can be tracked and managed using the Hardware Asset Management Workspace or the Transfer Order form1. References:

Transfer orders

 According to the ServiceNow Hardware Asset Management documentation, the asset lifecycle defines and describes the series of stages involved in managing an asset throughout its useful life. The first stage of the asset lifecycle is the request stage, where stakeholders get together, discuss their objectives, and determine which assets are needed and why. The culmination of this stage is a formal request for an asset. The asset lifecycle begins when the asset is requested, not when it is procured, deployed, or fulfilled. References:

ServiceNow Hardware Asset Management: Hardware Asset Management overview

ServiceNow Hardware Asset Management: What is the IT Asset Lifecycle?

According to the ServiceNow Hardware Asset Management documentation, a configuration item (CI) is an entity or thing that you wish to track that is required for the delivery of a service. A CI can be a hardware asset, a software asset, a service, a document, or any other component that is part of the IT infrastructure1. A CI is different from an IT asset in that a CI focuses on the technical attributes and relationships of the component, while an IT asset focuses on the financial and contractual aspects of the component2. Therefore, a component is considered a CI as opposed to an IT asset when you want to track its relationship information, such as its dependencies, impacts, and interactions with other CIs. Relationship information helps to manage the configuration and performance of the IT services and to identify and resolve incidents and problems3.

The other options are not correct because:

Track its incurred costs: This is a function of an IT asset, not a CI. An IT asset tracks the cost, depreciation, and value of the component, as well as the budget and expenses related to the component2.

Manage its retirement: This is also a function of an IT asset, not a CI. An IT asset tracks the status, location, ownership, and history of the component, as well as the events and actions that occur during the asset lifecycle, including its retirement or replacement2.

Manage its license contracts: This is another function of an IT asset, not a CI. An IT asset tracks the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the component. Contract management helps to manage the vendor relationships and compliance obligations of the component2.

Know who is using it: This is not a specific function of either an IT asset or a CI, but rather a common attribute that can be shared by both. Both an IT asset and a CI can have a user or owner field that indicates who is using or responsible for the component4.

The ServiceNow asset lifecycle defines and describes the series of stages involved in managing an IT asset throughout its useful life1.

The asset lifecycle usually follows a formalized process and is often tracked and supported by software tools1.

Although different organizations in different industries may have their own versions of the asset lifecycle, most follow the same basic format1.

Here, we explore the six stages of the asset lifecycle: Request, Fulfill, Deploy, Monitor, Service, and Retire1.

Out of these six stages, three are also components of the asset lifecycle: Order, Install, and Receive2.

Order: This is the stage where an asset is purchased or acquired from a vendor or supplier. The order stage involves creating purchase orders, tracking shipments, and updating the asset records2.

Install: This is the stage where an asset is physically installed or configured in a location. The install stage involves scanning asset tags, updating asset status, and assigning asset owners2.

Receive: This is the stage where an asset is received and verified by the organization. The receive stage involves checking the asset condition, validating the asset information, and updating the asset inventory2. References:

1: What is the IT Asset Lifecycle? - ServiceNow

2: ITAM Lifecycle Management: How does it all work?

Deploying asset tasks during the retirement of an asset means using the ServiceNow Enterprise Asset Workflow Automation feature, which automates the end-of-life procedures for assets that are no longer needed or functional1.

This feature allows you to flag assets as retired pending disposal, triggering a workflow that verifies the asset condition, determines the disposal method, and saves the disposal certificates1.

The two primary benefits of deploying asset tasks during the retirement of an asset are:

Reduces manual intervention: By automating the retirement process, you can eliminate the need for manual data entry, human errors, and delays. You can also ensure compliance with policies and regulations by following a standardized procedure12.

Increases speed of updates: By using the ServiceNow Agent mobile app, you can scan asset tags and barcodes, update asset status and inventory, and complete asset tasks on the go. This can increase the speed and accuracy of asset updates and reduce the risk of data loss or duplication13. References:

1: Enterprise Asset Workflow Automation - ServiceNow

2: Asset and CI management - Product Documentation: San Diego - ServiceNow

3: Enterprise Asset Management - ServiceNow

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?

According to the ServiceNow Hardware Asset Management documentation, the Scanned Assets related list displays the assets that have been scanned using the ServiceNow Agent mobile app during an audit. The Scanned Assets related list is updated each time scans are submitted from the app, which can be done manually or automatically based on the app settings

The plugin that helps alleviate inconsistencies in company names is the Normalization Data Services plugin, which is part of the ServiceNow IT Asset Management suite1.

The Normalization Data Services plugin provides a set of features and capabilities that enable you to standardize and normalize data across various tables and fields in ServiceNow, such as manufacturer names, model names, software names, and company names12.

The Normalization Data Services plugin uses a combination of rules, dictionaries, and algorithms to identify and correct data inconsistencies, such as spelling errors, abbreviations, synonyms, and duplicates12.

The Normalization Data Services plugin can help you improve the quality and accuracy of your data, reduce manual efforts and errors, and enhance reporting and analysis12. References:

1: Normalization Data Services - Product Documentation: San Diego - ServiceNow

2: Normalization Data Services - ServiceNow

According to the ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path, the Hardware Asset dashboard is a feature that shows key metrics on your hardware and consumable models and assets for the entire asset life cycle.

The Hardware Asset dashboard is available with the Hardware Asset Management (HAM) application, which is a licensable application that provides advanced workflow, automation, and mobile capabilities to maintain your assets1.

To access the Hardware Asset dashboard, you need to have the ham_user role, which is the minimum role required to use the HAM application1.

The ham_user role grants you the permission to view and update hardware and consumable assets, transfer orders, disposal orders, and RMA requests1.

Therefore, the correct answer is option C, ham_user, as it is the minimum role required to use the Hardware Asset dashboard. References:

ServiceNow IT Asset Management (ITAM) Hardware Asset Management (HAM) learning path

Hardware Asset Management documentation

What is Hardware Asset Management?