CIS-HAM Sample Questions Answers

Consumables are hardware assets that are not tracked individually, but as a quantity of items in a stockroom, such as keyboards, mice, cables, etc.1

When a stock manager receives a new delivery of consumables, they can use the Mobile Asset Receiving feature to scan the barcode of the purchase order and receive multiple assets against it using a mobile device2

If the received consumables match another record in the stockroom based on the following fields: Assigned to, Model, Model category, State, Stockroom, and Substate, then the data is automatically merged to create a blended quantity and cost3

This means that the system calculates the average cost per item and the total quantity of the consumables in the stockroom, and updates the existing record accordingly3

This feature helps to reduce duplicate records and simplify inventory management of consumables3

According to the Hardware Asset Management documentation, the hardware model normalization process is a process of comparing the model data in the ServiceNow platform with the data from the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The hardware model normalization process helps customers identify and manage their hardware models more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The hardware model normalization process assigns a status to each hardware model, such as Fully Normalized, Partially Normalized, Match Not Found, or Not Normalized1.

The status of Fully Normalized means that the hardware model data in the ServiceNow platform matches the data from the Content Library, indicating a complete and accurate model record1.

The status of Partially Normalized means that the hardware model data in the ServiceNow platform partially matches the data from the Content Library, indicating a missing or incorrect model field1.

In order for a hardware model to be fully normalized rather than partially normalized, the hardware model record must have the following fields populated correctly1:

Manufacturer: The name of the company that produces the hardware product.

Name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Model number: The unique identifier of the hardware product, such as 210-AFZC or 875671-B21.

Therefore, the correct answer is option E, model number, as it is the field that is required in the hardware model record for full normalization.

A transfer order is a record of all asset transfers that happen to and from company-owned stockrooms1. A transfer order can have one or more transfer order lines, which represent the individual assets or asset models that are being transferred2.

A transfer order line can have one or more transfer order tasks, which are the actual work items that need to be performed to complete the transfer, such as packing, shipping, receiving, and unpacking2.

The structure of a transfer order is shown in the following diagram2:

Transfer Order

|

+-- Transfer Order Line 1

| |

| +-- Transfer Order Task 1.1

| |

| +-- Transfer Order Task 1.2

|

+-- Transfer Order Line 2

|

+-- Transfer Order Task 2.1

|

+-- Transfer Order Task 2.2

Delegated Developers are granted access only to scopes in which they are working1. A scope is a set of application files and data that are isolated from other applications on the same instance2.

Scopes allow developers to create and modify applications without affecting the functionality or security of other applications or the platform2.

Delegated Developers can be assigned developer permissions for specific scopes by an application administrator or a system administrator1. These permissions determine what types of files and data they can access and modify within the scope1.

Delegated Developers can also request cross-scope access to access resources from another scope, which must be approved or denied by the owner of the target scope1.

Delegated Developers do not have access to interfaces, APIs, or instances, unless they are explicitly granted by an administrator or a cross-scope request1. References:

1: Delegated Development - Product Documentation: San Diego - ServiceNow

2: Application Scoping - Product Documentation: San Diego - ServiceNow

Normalization is the process of standardizing the hardware model data by manufacturer name, model name, and model number1.

Normalization helps to maintain a clean and consistent configuration management database (CMDB) and to avoid duplicate or inaccurate hardware models1.

Normalization first runs to normalize the record when you save the hardware model record1.

This means that when you create or edit a hardware model record, the system automatically checks the record against the normalization rules and the Hardware Content Service Lifecycle data, and updates the record with the normalized values if applicable1.

Therefore, the answer that reflects when normalization first runs is C. When you save the hardware model record.

The other options are not the correct answer because they describe different scenarios or actions:

A. When the daily scheduled HAM – Daily job runs: This is not the correct answer, because the daily scheduled HAM – Daily job does not run normalization. The daily scheduled HAM – Daily job is a scheduled job that runs various tasks related to hardware asset management, such as updating the asset status, calculating the depreciation, and sending notifications2.

B. When the weekly scheduled HAM – Normalization job runs: This is not the correct answer, because the weekly scheduled HAM – Normalization job does not run normalization for the first time. The weekly scheduled HAM – Normalization job is a scheduled job that runs normalization for all the existing hardware models in the CMDB on a weekly basis1. It does not affect the newly created or edited hardware models, which are normalized when they are saved1.

D. When you click the Normalize Hardware Model link under Related Links: This is not the correct answer, because clicking the Normalize Hardware Model link under Related Links does not run normalization for the first time. Clicking the Normalize Hardware Model link under Related Links is a manual action that allows you to run normalization for a specific hardware model record at any time1. It does not affect the automatic normalization that runs when you save the hardware model record1. References:

1: Hardware Normalization

2: Daily Scheduled HAM – Daily Job

According to the Hardware Asset Management documentation, residual value is the estimated value of an asset at the end of its useful life.

Residual value is calculated by subtracting the depreciation from the cost of the asset, as stated in the Hardware Asset Management documentation: “Residual value = Cost - Depreciation”.

Depreciation is the amount of value that an asset loses over time due to wear and tear, obsolescence, or other factors.

Therefore, the correct answer is option C, subtract the depreciation from the cost of the asset. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The End of Life tab of the Hardware Asset dashboard shows key metrics on the hardware assets that have reached or are nearing the end of their life cycle12.

The tab includes the following reports1:

Hardware asset disposal status: This report shows the number of hardware assets that are in different stages of disposal, such as pending, in progress, or completed1.

Hardware assets disposed (YTD): This report shows the number of hardware assets that have been disposed in the current year, grouped by month1.

Hardware assets up for end of life: This report shows the number of hardware assets that are due for end of life in the next 12 months, grouped by month1.

Hardware assets up for end of support: This report shows the number of hardware assets that are due for end of support in the next 12 months, grouped by month1.

Therefore, the correct answer is A. Hardware asset disposal status and C. Hardware assets disposed (YTD), as these are the only two reports that are shown on the End of Life tab of the Hardware Asset dashboard.

According to the Hardware Model Normalization document, normalization status is the level of normalization match based on the characteristics of the hardware model data in the ServiceNow platform and the Content Library, which is a cloud-based service that provides normalized and enriched hardware model data.

The normalization status shows how well the hardware model data matches the Content Library data, and it can be one of the following1:

Fully Normalized: The hardware model data matches the Content Library data completely, indicating a complete and accurate model record.

Partially Normalized: The hardware model data partially matches the Content Library data, indicating a missing or incorrect model field.

Match Not Found: The hardware model data does not match any of the Content Library data, indicating a discrepancy or a gap in the model normalization process.

Not Normalized: The hardware model data has not been compared with the Content Library data yet, indicating a pending or incomplete model normalization process.

The characteristics that are used to determine the normalization status are the following1:

Model name: The name of the hardware product, such as Dell Latitude E7450 or HP ProLiant DL380 Gen10.

Model number: The unique identifier of the hardware product, such as 210-AFZC or 875671-B21.

Manufacturer: The name of the company that produces the hardware product, such as Dell or HP.

Therefore, the correct answers are options A, C, and E, as they are the characteristics that are used to determine the normalization status. References:

Hardware Model Normalization

What is Hardware Asset Management?

The second tier of the capability blueprint in ServiceNow is Practical Management, focusing on managing operational tasks efficiently while aligning with strategic goals. It bridges the gap between foundational and advanced asset capabilities.

During an inventory audit, if you accidentally scan the same asset twice, the Hardware Asset Management (HAM) application will automatically remove the duplicate records and only import the unique scans. This is because the HAM application uses the asset tag or the serial number as a coalesce field, which prevents duplicate records from being created or updated in the hardware asset table. Therefore, you do not need to worry about scanning the same asset twice, as the HAM application will handle the duplicates for you. References:

Audit your inventory, which provides a step-by-step guide on how to perform scheduled or blind audits of asset stockrooms and other locations using the Agent mobile app and the Now Platform.

Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.

Importing Hardware Assets into ServiceNow, which provides a step-by-step guide on how to import hardware assets into ServiceNow using an excel spreadsheet, an import set table, and a transform map.

According to the ServiceNow Hardware Asset Management documentation, the system property glide.ham.retire_sw() determines the behavior of software allocations when a hardware asset is retired. The possible values are:

•Reclaim: The software allocations are automatically returned to inventory and the software installation records are deleted.

•Retain: The software allocations remain with the hardware asset and need to be reclaimed manually.

•Remove: The software allocations are removed from the asset, but not returned to inventory.

According to the ServiceNow Hardware Asset Management documentation1, when a hardware asset is retired, the system property glide.ham.retire_reclaim_sw() determines whether the software allocations on that asset are automatically reclaimed or not. If the property is set to true, the software allocations are returned to the inventory. If the property is set to false, the software allocations remain with the hardware asset and need to be reclaimed manually. References: 1: Hardware Asset Management - ServiceNow2

Hardware asset management, Procurement, and Cost management are the plugins which are not active by default in base Servicenow System

The Identification and Reconciliation process in ServiceNow ensures that configuration items (CIs) are correctly matched during the import process. This prevents duplication by validating unique identifiers, such as serial numbers or UUIDs, ensuring CMDB integrity.

Managing the Hardware Asset Management (HAM) Content Service involves enabling the service explicitly (opting in). Organizations can choose to enable it for receiving updates about normalized hardware models and lifecycle information. If the service is not needed anymore, it allows opting out at any time, providing flexibility for organizations.

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?

According to the ServiceNow Hardware Asset Management documentation, hardware model lifecycle phases are the stages that a hardware model goes through from its introduction to the market to its retirement. The valid hardware model lifecycle phases are:

•Pre-release: The hardware model is not yet available for purchase, but it is planned to be released in the future.

•General Availability: The hardware model is available for purchase and supported by the manufacturer.

•End of Life: The hardware model is no longer available for purchase or supported by the manufacturer.

•Disposal: The hardware model is disposed of or recycled.

The Overview view is a dashboard that displays metrics and charts related to the hardware assets in your organization.

The Overview view shows the following information:

The total number of hardware assets, their status, and their lifecycle stage.

The number of assets that are due for refresh, retired, or disposed in the current year, quarter, or month.

The refresh rate and the refresh cost of the hardware assets.

The asset age distribution and the asset model distribution.

The asset compliance status and the asset certification status.

To access the Overview view, you need to have the sn_ham.user role or the sn_ham.admin role.

To access the Overview view, navigate to Hardware Asset Management > Overview. References:

Overview

Hardware Asset Management roles

When an asset is manually created from a purchase order before it has been shipped by the supplier, the default state of the asset is set to On order. This state indicates that the asset has been ordered but not yet received. The asset state will change to Awaiting delivery when the asset is shipped by the supplier, and to In stock when the asset is received by the stockroom. The asset state will change to In use when the asset is deployed to a user or a location, and to Pending transfer when the asset is ready to be transferred to another stockroom or location. The asset state will change to Retired when the asset is disposed of or returned to the supplier. References:

Hardware Asset States, which describes the different states and substates of hardware assets and how they are used to track the asset lifecycle.

Hardware Asset Management overview, which describes the functionalities of the Hardware Asset Management application, including the dashboard, model normalization, hardware refresh, lease contract expiration, disposal orders, and RMA requests.

Hardware Asset Lifecycle Automation, which explains how to automate the workflows and tasks for managing the assets throughout their lifecycle stages, from request to retire.

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

Automatic restocking actions are actions that trigger the creation of stock orders when the quantity of an asset falls below the minimum threshold or exceeds the maximum threshold1.

A daily scheduled job runs every day to check the stock levels of assets and execute the automatic restocking actions based on the stock rules1.

The plugin that must be activated in order to configure and use the scheduled job is the Procurement plugin2.

The Procurement plugin enables the procurement of assets and consumables through purchase orders, stock orders, and vendor management2.

The Procurement plugin also provides the Stock Order [Order] table, which stores the stock orders created by the automatic restocking actions2.

The ServiceNow Agent mobile app allows the user to scan and create assets in ServiceNow in various scenarios123.

One scenario is to create a single asset via barcode scan. The user can scan the barcode or QR code of an asset and fill in the required fields to create an asset record in ServiceNow1.

Another scenario is to receive one or multiple assets from a purchase order. The user can scan the barcode or QR code of a purchase order and view the list of assets to be received. The user can then scan the assets and confirm the receipt in ServiceNow1.

The other scenarios, such as creating multiple assets listed on a contract PDF scan or creating a single asset via Name search, are not supported by the ServiceNow Agent mobile app123. References:

ServiceNow Agent app - Product Documentation: San Diego - Now Support Portal

Hardware Asset Inventory Management - ServiceNow

Automation Simplifies Hardware Asset Management - ServiceNow Blog

According to the ServiceNow Hardware Asset Management overview document1, contracts are records that define the terms and conditions for the acquisition, maintenance, or disposal of assets1. They can include information such as vendor, start date, end date, cost, and renewal options1.

According to the ServiceNow Data Sheet on Contract and Renewal Management2, some of the critical information that should be tracked for contracts are2:

What each contract costs: This information helps users to monitor and optimize the total cost of ownership (TCO) of their assets, as well as to plan and budget for future contract renewals or negotiations2.

What assets each contract covers: This information helps users to identify and manage the assets that are under contract, such as software licenses, hardware devices, or enterprise assets2. It also helps users to align their asset investments to their business outcomes and avoid penalties or service disruptions2.

The other options are not critical information that should be tracked for contracts. Who purchased the assets and what needs to be cancelled are not relevant to the contract management process, as they do not affect the contract terms, conditions, or performance2.

The lifecycle management tab provides details about the normalization status, models nearing end of life, and lease end timelines. Expenditure by vendor and pending purchase orders are unrelated to lifecycle tracking and would typically be found in financial reports or procurement dashboards.

According to the ServiceNow Hardware Asset Management documentation, asset management is the practice of managing the lifecycle and optimization of physical assets to meet the needs and goals of an organization. Asset management involves the balancing of costs, opportunities and risks against the desired performance of assets to achieve an organization’s objectives. The other options are not the focus of asset management.

The ServiceNow Agent mobile app allows the user to conduct asset audits by scanning asset barcodes or QR codes1.

The user can perform audits offline when they are in areas without connectivity1.

The app automatically compares the scanned assets against the expected assets based on the inventory records to identify discrepancies1.

The user can also view the audit results and generate reports from the app2. References:

Audit your inventory - Product Documentation: San Diego - ServiceNow

Hardware Asset Inventory Management - ServiceNow

Hardware Asset Management - ServiceNow

Baseline asset states are the predefined states that represent the lifecycle stages of hardware assets in the ServiceNow platform1.

Baseline asset states are used to track the status, location, and ownership of hardware assets, as well as to trigger workflows and tasks for asset management2.

The baseline asset states are: In Stock, In Use, In Repair, In Transit, Retired, Consumed, and Duplicate1.

In Stock means the asset is available in a stockroom and ready for deployment1.

Consumed means the asset is used up or depleted, such as a toner cartridge or a battery1.

Retired means the asset is no longer in use and has been disposed of or recycled1. References:

Baseline asset states

Hardware Asset Management overview

According to the ServiceNow Product Documentation on Transfer Orders1, transfer orders are records that define the movement of assets from one stockroom to another1. They can be used to replenish the stock of assets, fulfill asset requests, or relocate assets1.

According to the ServiceNow Product Documentation on Transfer Order Line Tasks2, transfer order line tasks are records that define the actions that need to be performed for each transfer order line2. A transfer order line is a record that defines the quantity and model of the assets that are being transferred1.

The main purposes of transfer order line tasks are2:

To help track service levels and the time frame needed to complete a transfer order: Transfer order line tasks have a due date and a state that indicate the progress and completion of the transfer order line. They also have a priority and an assignment group that determine the urgency and the responsibility of the transfer order line. These fields help users to monitor and manage the service levels and the time frame needed to complete a transfer order.

To move transfer order lines from one stage to another: Transfer order line tasks have a type that defines the action that needs to be performed for the transfer order line, such as pick, pack, ship, or receive. As transfer order line tasks are completed, the transfer order line moves from one stage to another, such as requested, in transit, or received. These stages reflect the status and location of the assets that are being transferred.

According to the ServiceNow Hardware Asset Management documentation, an advanced shipment notification (ASN) is a document that provides detailed information about a pending delivery. The purpose of an ASN is to notify the customer when shipping occurs and provide physical characteristics about the shipment so the customer can be prepared to accept delivery. You can use ASNs to automatically create asset records in ServiceNow Hardware Asset Management by importing the data from the ASN document.

To utilize the contract rate cards features, you need to activate the Rate Management plugin, which provides the ability to define and manage rates for various types of costs and expenses1.

The contract rate cards features allow you to capture operating costs by generating expense lines representing the cost of a contract. You can associate a contract to certain assets and costs of those assets are tied to the contract. This is similar to a rate card cost, except the contract contains all the costs2.

The other plugins are not required to use the contract rate cards features. The Financial Management plugin provides the ability to track and manage the financial performance of your IT services3. The Contract Management plugin provides the ability to create and manage contracts for assets, services, and vendors4. The Cost Management plugin provides the ability to track and allocate costs for configuration items, tasks, and projects5. References: 1: Rate Management 2: Cost Management — ServiceNow Elite 3: Financial Management 4: Contract Management 5: Cost Management

According to the ServiceNow documentation, an asset is "any tangible or intangible item that might have value for an organization"1.

The default asset classes in ServiceNow are Hardware, Software License, Consumable, Bundle, Software Entitlement, and Facility1.

These general classes can be used to manage various assets, such as computers, printers, software licenses, office supplies, software subscriptions, and buildings1.

Therefore, facilities, hardware, and software entitlements are considered assets, while contracts and software distributions are not. References:

Asset and configuration item (CI) management - ServiceNow

According to the Now Create ebook, the Now Create methodology consists of five phases: initiate, plan, execute, deliver, and close. Each phase has a specific purpose, outcome, and set of tasks that guide the project team to successful delivery. The other options are not valid phases of the Now Create methodology.

https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/incident-management/task/track-ci.html

The Expected Assets list is populated when the asset manager starts the audit by clicking the Scan button on the asset audit form1.

This list shows the assets that are expected to be found in the audit location based on the asset records in the CMDB1.

The asset manager can then use a barcode scanner or a mobile device to scan the actual assets in the location and compare them with the expected assets1.

The asset manager can also manually add or remove assets from the expected assets list if needed1. References:

1: Hardware Asset Inventory Audit

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

The capability blueprint is a framework that helps organizations assess their current and desired state of hardware asset management maturity.

The capability blueprint consists of five tiers, each representing a different level of capability and value.

The five tiers are:

Trustworthy data: The foundation of hardware asset management, ensuring data accuracy, completeness, and consistency.

Practical management: The basic level of hardware asset management, enabling visibility, control, and compliance of hardware assets.

Operational integration: The intermediate level of hardware asset management, enhancing efficiency, effectiveness, and collaboration of hardware asset processes.

Strategic conformance: The advanced level of hardware asset management, achieving best-in-class performance, optimization, and alignment of hardware assets with business goals.

Business transformation: The ultimate level of hardware asset management, enabling innovation, agility, and competitive advantage through hardware asset management.

The tier that focuses on achieving best-in-class is the strategic conformance tier, which aims to optimize the cost, quality, and value of hardware assets, as well as align them with the business strategy and objectives. References:

Hardware Asset Management Capability Blueprint

Hardware Asset Management Maturity Model

The reclamation process allows managers to select assets to be reclaimed from the asset service catalog, including hardware, software, and consumables. Only selected items will be processed for return.

 Hardware Model Normalization is a feature that enables users to standardize the data of hardware and consumable models, such as manufacturer, product, model, and device type. Hardware Model Normalization requires the activation of the Hardware Model Normalization (com.sn_hwnorm) plugin, which also activates the Normalization Data Services Client (com.glide.data_services_canonicalization.client) plugin. These plugins install several tables that store the normalized data and the rules for normalization. The tables that are installed with Hardware Model Normalization are:

Device Type: This table contains the device types that are used to categorize the hardware models, such as laptop, desktop, server, printer, etc.

Hardware Manufacturer: This table contains the normalized names of the hardware manufacturers, such as Dell, HP, Lenovo, etc.

Hardware Model Library: This table contains the normalized data of the hardware models, such as manufacturer, product, model, device type, UNSPSC code, etc. This table is populated by the Hardware Model Normalization Content Service, which is a subscription-based service that provides the latest and most accurate data for hardware models.

Hardware Normalize Key: This table contains the rules for generating the normalize key, which is a unique identifier for each hardware model based on its manufacturer, product, and model. The normalize key is used to match the hardware models with the Hardware Model Library data.

The other options, C. Hardware Normalize Key and E. Device Name, are not tables that are installed with Hardware Model Normalization. Hardware Normalize Key is a field in the Hardware Model [cmdb_model] table, not a separate table. Device Name is a field in the Configuration Item [cmdb_ci] table, not a separate table. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Hardware Asset Management

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?