Free Practice Questions for ServiceNow CIS-HAM Exam

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, an asset is defined as "any tangible, physical company technology asset, including those currently in use, those in storage, and support equipment"1. Throughout the life of an asset, the following data are tracked2:

Financial data: This includes the cost, depreciation, and value of the asset, as well as the budget and expenses related to the asset. Financial data helps to optimize the return on investment (ROI) and total cost of ownership (TCO) of the asset.

Contractual data: This includes the terms and conditions, warranties, service level agreements (SLAs), and renewals of the contracts associated with the asset. Contractual data helps to manage the vendor relationships and compliance obligations of the asset.

Lifecycle data: This includes the status, location, ownership, and history of the asset, as well as the events and actions that occur during the asset lifecycle. Lifecycle data helps to monitor the performance and utilization of the asset and plan for its retirement or replacement.

The other options, configuration data and hardware data, are not tracked throughout the life of an asset, but rather at specific stages or levels. Configuration data is the information about the technical attributes and relationships of the asset, which is stored in the configuration management database (CMDB) and managed by the configuration management process3. Hardware data is the information about the physical characteristics and specifications of the asset, such as manufacturer, model, serial number, and barcode4. References:

ServiceNow Hardware Asset Management: Hardware Asset Management overview

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

ServiceNow Hardware Asset Management: Asset and CI management

ServiceNow Hardware Asset Management: Hardware Normalization

Create transform map: A transform map is a set of field mappings that determine how the source data in the import set table is transformed into the target data in the hardware asset table. You can create a transform map by using the Load Data UI page, or by navigating to System Import Sets > Create Transform Map. You need to specify the source table, the target table, and the field mappings between them. You can also define coalesce fields, which are used to prevent duplicate records from being created or updated. For example, you can use the asset tag or the serial number as a coalesce field.

Load data: To load data into the import set table, you need to select a data source, such as a file, a JDBC data source, or a web service. You can use the Load Data UI page, or navigate to System Import Sets > Load Data. You need to specify the source type, the file name or the connection URL, the sheet number and the header row (if using a file), and the import set table name. You can also preview the data before loading it into the table.

Run transform map: To run the transform map, you need to navigate to System Import Sets > Transform Maps, and select the transform map that you created. You can then click on the Run Transform button, which will execute the field mappings and transform the data from the import set table to the hardware asset table. You can also view the transformation history, the transformation statistics, and the transformation log to monitor the progress and the results of the transformation.

According to the ServiceNow Hardware Asset Management documentation, a stockroom is a location where assets are stored and managed. A stockroom must have an assigned manager who is responsible for overseeing the stockroom operations and inventory. The stockroom manager must have a valid email address to receive notifications and alerts related to the stockroom, such as low stock levels, stock transfers, and stock orders. The other options are not primary requirements for the warehouse stockroom. The stockroom does not need to have an assignment group, a valid time zone, or a valid mobile phone.

To fully normalize a model, you need to add the model number to the model record, which is a unique identifier for the model based on the United Nations Standard Product and Services Code (UNSPSC). The model number helps to standardize the display name and remove duplicates in the model catalog and the CMDB. The other fields, such as version, owner, and manufacturer, are optional or can be derived from the model number. References:

Hardware Model Normalization, which explains how to normalize the details of the hardware and consumable models using the Hardware Model Normalization Content Service.

Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the model normalization feature.

[Hardware Asset Management - Customer Success], which provides a success map that outlines the processes and best practices for implementing, running, and optimizing the Hardware Asset Management applications, based on the Capability Blueprint framework.

 Operational expenses are the costs incurred by an organization to maintain and use an asset throughout its lifecycle. These costs include the expenses related to the repair, maintenance, upgrade, and disposal of the asset. Some examples of operational expenses are:

Replacement parts: These are the costs of purchasing and installing new parts or components for an asset that is damaged, worn out, or obsolete. For example, replacing a hard drive, a battery, or a keyboard for a laptop.

Maintenance agreements: These are the costs of contracting with a vendor or a service provider to perform regular or preventive maintenance on an asset. For example, paying a monthly fee for a technician to check and service a printer or a scanner.

Other examples of operational expenses are:

Storage costs: These are the costs of renting or owning a space to store an asset that is not in use or awaiting disposal. For example, paying for a warehouse, a locker, or a shelf to keep unused or surplus computers or monitors.

Warranty costs: These are the costs of extending or renewing the warranty coverage for an asset that is still under the manufacturer’s warranty or has expired. For example, paying an extra fee for a one-year or a three-year warranty extension for a tablet or a smartphone.

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?

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