CIS-HAM Certified Implementation Specialist - Hardware Asset Management Questions and Answers

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

According to the ServiceNow Hardware Asset Management documentation, a loaner asset is a temporary asset that is provided to a user for a specific period of time, such as when their primary asset is being repaired or replaced1. Users can request loaner assets from the Service Catalog, where they can select the type, quantity, and duration of the loaner asset they need2. If the requested asset is not available in the local stockroom, the request is wait-listed until the asset becomes available3. Users may request loaner assets even when the requested asset is not available in the local stockroom because the wait-listed loaner asset requests provide visibility to the demand for loaner orders. This visibility helps the asset managers to plan and optimize the loaner asset pool, as well as to identify and address any gaps or bottlenecks in the loaner asset fulfillment process.

The other options are not correct because:

The request does not create an automatic transfer order to move assets from a warehouse with in stock assets. Transfer orders are created manually by the stock manager to move assets between stockrooms.

The wait-listed loaner asset requests do not provide visibility to streamline internal transfer order flows. Transfer order flows are managed by the stock manager using the Transfer Order Management module.

The request does not automatically create a purchase order to obtain the assets from a vendor. Purchase orders are created manually by the procurement manager to order assets from vendors.

According to the Audit your inventory document, a blind inventory audit is a type of audit that hides the expected asset list from the auditor, so that the auditor has to physically scan each asset in the location and compare it with the actual asset list1.

A blind inventory audit helps ensure data integrity and accuracy, as it prevents the auditor from “cheating on the test” by relying on the expected asset list1.

A blind inventory audit is typically initiated via the Now Agent Mobile app, which is a mobile application that enables users to perform various tasks related to hardware asset management, such as scanning assets, creating audits, and viewing audit results1.

The Now Agent Mobile app allows users to create an audit on the mobile device, select the location and type of audit, and scan the assets using the device camera or a Bluetooth scanner1.

Therefore, the correct answer is option C, Now Agent Mobile app, as it is the interface that is typically used to initiate a blind inventory audit. References:

Audit your inventory

What is 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 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 ServiceNow Hardware Asset Management documentation, ITAM personas and ITAM roles are different concepts that relate to the types and access of users of the product. The difference between them are as follows:

ITAM personas are user profiles that represent the typical users of the ITAM product and their business needs. They are not tied to any specific role or permission, but rather describe the goals, challenges, and expectations of the users. For example, some of the ITAM personas are IT Asset Manager, IT Asset Analyst, IT Procurement Manager, and IT Finance Manager1.

ITAM roles are access controls that determine what features and functions a user can access in the ITAM product. They are assigned to users or groups based on their responsibilities and tasks. They can also be combined to grant multiple levels of access to a user. For example, some of the ITAM roles are asset, asset_admin, asset_tagging, and procurement2.

Therefore, a user may have multiple roles, but a single persona (A), roles control access to features in the product (B), personas represent types of users of the product ©, and a user may have multiple roles and personas (F) are the correct statements that describe the difference between ITAM personas and ITAM roles. References:

1: ITAM personas 2: ITAM roles

According to the ServiceNow Product Documentation on Stock Rules1, stock rules are records that define the conditions and actions for replenishing the stock of assets in a stockroom when they drop below a specified threshold1.

According to the ServiceNow GlideFast blog post on Stock Rules in ServiceNow2, when creating a stock rule that replenishes from a vendor, the primary requirement for the warehouse stockroom is that it must have an assigned manager and the manager must have a valid email address2.

The reason for this requirement is that the stock rule will generate a purchase order for the procurement of additional assets from the vendor, and the purchase order will be sent to the stockroom manager’s email address for approval2.

The other options are not primary requirements for the warehouse stockroom when creating a stock rule that replenishes from a vendor. The stockroom does not need to have an assignment group, a valid mobile phone, or a valid time zone for the stock rule to work.

According to the ServiceNow Hardware Asset Management overview document1, the lease contract expiration flow sends notifications to the contract administrator before a lease contract expires and helps them act on the leased assets to return the asset or extend the contract.

According to the ServiceNow Elite blog post on contract management2, when the contract.expiration event runs on the Contract [ast.contract] table each night, an email message is sent to the person identified as the contract administrator at the following times:

90 days ahead of the contract expiration date

60 days ahead of the contract expiration date

30 days ahead of the contract expiration date

Day of expiration

Therefore, the correct answer is C, D, E, and F.

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

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

According to the ServiceNow Hardware Asset Management documentation, a contract is a record of the terms and conditions that govern the relationship between a vendor and an organization. A contract can have different states that indicate its status and lifecycle. The states are:

Draft: The contract is being created or modified and has not been submitted for approval.

Requested: The contract has been submitted for approval but has not been approved yet.

Active: The contract has been approved and is in effect. You can cancel the contract in this state, if you want to terminate it before its end date due to various reasons, such as breach of contract, mutual agreement, or vendor performance1.

Expired: The contract has reached its end date and is no longer valid. You cannot cancel the contract in this state, but you can renew it or extend it.

Renewed: The contract has been renewed for another term with the same or modified terms and conditions. You cannot cancel the contract in this state, but you can renew it or extend it again.

Extended: The contract has been extended beyond its original end date with the same terms and conditions. You cannot cancel the contract in this state, but you can renew it or cancel it.

Canceled: The contract has been terminated before its end date. You cannot cancel the contract in this state, but you can reactivate it or delete it.

Rejected: The contract has been rejected by the approver. You cannot cancel the contract in this state, but you can edit it or delete it.

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

To activate HAM, navigate to System Definition > Plugins and search for Hardware Asset Management. Click Activate/Upgrade and follow the instructions1.

To run the scheduled job “Asset - Create FSM asset tasks”, navigate to System Definition > Scheduled Jobs and search for the job name. Click Execute Now to run the job immediately or set a schedule for it to run periodically2.

The scheduled job will create asset tasks for existing incidents, changes, and work orders that have assets associated with them. The asset tasks will be linked to the parent records and will have the same state and assignment group as the parent records2.

The asset tasks will allow the asset managers to track and manage the assets involved in the service delivery processes3. References:

1: Hardware Asset Management - ServiceNow

2: Asset - Create FSM asset tasks scheduled job

3: Hardware Asset Management and Field Service Management integration

According to the Hardware Asset Management page, the ham_admin role grants the user the following permissions:

Create, read, update, and delete hardware asset records

Import hardware assets from external sources

Revert normalization results for hardware assets

Add hardware assets to the Service Catalog

These permissions correspond to the options A, B, E, and F in the question.

The options C and D are not part of the ham_admin role, and are not mentioned in the ServiceNow Hardware Asset Management documents. References:

Hardware Asset Management

Hardware Asset Management roles and permissions

A component is considered an IT asset when you want to perform hardware asset management (HAM) activities on it1.

HAM is a subset of IT asset management (ITAM) that focuses on the physical components of IT systems2.

HAM helps you to manage the entire lifecycle of your hardware assets, from planning and acquisition to retirement and disposal1.

Some of the HAM activities that require a component to be an IT asset are:

Manage its procurement: This involves creating and fulfilling asset requests, purchase orders, and stock order tasks for the component1.

Track its incurred costs: This involves tracking the financial information of the component, such as cost, depreciation, budget, and chargeback1.

Manage its maintenance contracts: This involves managing the vendor, warranty, and contract details of the component, as well as the return merchandise authorization (RMA) processes for products to be returned, replaced, or repaired1.

Therefore, the options that are also HAM activities are A. Manage its procurement, D. Track its incurred costs, and E. Manage its maintenance contracts.

The other options that are not HAM activities are:

Know its relationships to a business service: This involves mapping the component to other components and services in the configuration management database (CMDB)2. This is a configuration management (CM) activity, not a HAM activity.

Track its operational information: This involves tracking the current status, location, owner, and other attributes of the component that reflect its operational state2. This is also a CM activity, not a HAM activity. References:

1: Hardware Asset Management

2: What is Hardware Asset Management?

A configuration item (CI) is a record that represents an IT asset or service in the Configuration Management Database (CMDB)1.

A CI tracks the operational and relationship information of the asset or service, such as its current status, location, owner, and dependencies1.

A hardware asset is a physical component of an IT system, such as a laptop, server, or router2.

A hardware asset attribute is a property or characteristic of the hardware asset, such as its model, serial number, or warranty2.

Some hardware asset attributes are also part of the CI, such as IP address, CPU, operating system, and memory1. These attributes reflect the operational state of the hardware asset and are relevant for configuration management purposes1.

However, some hardware asset attributes are not part of the CI, such as cost2. Cost is a financial information of the hardware asset that is tracked by the Asset Management application2. Cost is not relevant for configuration management purposes and is not stored in the CMDB2.

Therefore, the hardware asset attribute that should be tracked that is not part of the CI is C. Cost. References:

1: Configuration Item

2: Hardware Asset Management

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 Hardware Asset Management documentation, an asset audit is a process of verifying the physical existence and location of assets in an organization, such as a stockroom or a warehouse.

The asset audit form shows the details of the audit, such as the name, description, status, start date, end date, and location of the audit1.

The asset audit form also shows the audit results, which are the status of each scanned asset, such as “Scanned and expected”, “Scanned and not expected”, “Expected and not scanned”, or "Not expected and not scanned"1.

The scanned assets are the assets that were found at the stockroom or warehouse that is being audited, regardless of whether they were expected or not1.

The scanned assets are displayed in the Scanned Assets related list on the asset audit form1.

Therefore, the correct answer is option B, scanned assets, as they are the list of all assets that were found at the stockroom or warehouse that is being audited. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

The Product Catalog is a table that contains all the hardware and consumable models that are available in your organization12.

The Service Catalog is a portal that allows users to browse and request items and services that are approved by the IT department13.

Publishing an item to the Service Catalog means making it visible and available for users to request13.

To publish an item to the Service Catalog, you need to use the “Publish to Hardware Catalog” related link in the Product Catalog1 .

This related link creates a catalog item for the selected model and adds it to the Hardware Catalog category in the Service Catalog1 .

Therefore, the correct answer is A. Product Catalog, as this is where you can use the “Publish to Hardware Catalog” related link to publish an item to the Service Catalog.

According to the Hardware Asset Management page, the three tiers of Lifecycle Management are:

Know what you have: This tier involves tracking and managing the end-to-end lifecycle of all your hardware assets, physical and consumable, on a single system of action.

Improve management controls: This tier involves aligning hardware investments to business outcomes, and quickly identifying and mitigating technology risks such as tech debt, regulatory audits, and lost assets.

Improve efficiency: This tier involves improving efficiencies and simplifying every stage of the asset lifecycle with prescriptive workflows and tasks, normalizing hardware to maintain a clean CMDB, and getting actionable insights to minimize waste and strategize for asset refreshes.

These three tiers correspond to the options C, D, and E in the question.

The options A and B are not part of the Lifecycle Management framework, and are not mentioned in the ServiceNow Hardware Asset Management documents. References:

Hardware Asset Management

What is Hardware Asset Management?

Your asset lifecycle: How to manage it all

According to the ServiceNow Hardware Asset Management documentation, a hardware asset is defined as "any tangible, physical company technology asset, including those currently in use, those in storage, and support equipment"1. Websites are not tangible or physical assets, but rather digital or virtual assets that are hosted on servers or other hardware devices. Therefore, websites are not considered hardware assets by ServiceNow. The other options, switches, routers, buildings, and software entitlements, are all examples of hardware assets or related items that can be managed by ServiceNow Hardware Asset Management. References:

What is Hardware Asset Management?

Configuration items (CIs) are the records that represent the IT assets and services in the Configuration Management Database (CMDB).

CIs track the following types of information:

Operational: This includes the current status, location, owner, and other attributes of the CI that reflect its operational state.

Relationship: This includes the connections and dependencies between the CI and other CIs, such as parent-child, peer-peer, or service-component relationships.

Lifecycle: This includes the history of changes, incidents, problems, and other events that affect the CI throughout its lifecycle.

Therefore, the types of information that are also options in the question are B. Operational and E. Relationship.

The other types of information that are not tracked by CIs are:

Financial: This includes the cost, depreciation, and budget of the CI. This information is tracked by the Asset Management application.

Contractual: This includes the vendor, warranty, and contract details of the CI. This information is also tracked by the Asset Management application. References:

: Configuration Item

According to the ServiceNow Hardware Asset Management documents, the role that allows you to allocate a resource is the resource_manager role1.

The resource_manager role is a role that grants the user the ability to manage resources, such as hardware assets, consumables, and stockrooms, and to perform tasks related to resource allocation, reservation, transfer, and audit1.

The other roles that are not the correct answer are:

A. resource_user: This is a role that grants the user the ability to view and request resources, such as hardware assets and consumables, from the service catalog or the mobile app2.

B. it_project_user: This is a role that grants the user the ability to view and participate in IT projects, such as hardware asset refresh projects, and to track the progress, costs, and risks of the projects3.

C. business_stakeholder: This is a role that grants the user the ability to view and provide feedback on the business services and outcomes that are supported by the IT assets and resources4. References:

1: Resource Manager Role

2: Resource User Role

3: IT Project User Role

4: Business Stakeholder Role

A field service management (FSM) change task is a task that is created from a change request and assigned to a field service agent to perform work on a configuration item (CI) or an asset1.

An asset task is a task that is created from an asset record and linked to an FSM change task to track the work done on the asset2.

When an asset task is completed, the asset record associated to the task is automatically updated with the latest information, such as location, status, assignment group, assigned to, and so on2.

This feature removes the need to manually update the asset record after completing the FSM change task, saving time and ensuring accuracy2.

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 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.

According to the Hardware Asset Management documentation, an asset audit is a process of verifying the physical existence and location of assets in an organization.

The asset audit results show the status of each scanned asset, such as “Scanned and expected”, “Scanned and not expected”, “Expected and not scanned”, or “Not expected and not scanned”.

The status of “Scanned and expected” means that the asset was both expected to be in the inventory and scanned during the audit, indicating a match between the physical and the logical inventory.

Therefore, if you receive the result of 10 “Scanned and expected” assets, it means that you expected 10 assets in your inventory and scanned these 10 assets during your audit, as stated in option B. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

To perform hardware model normalization, you need to use the Hardware Model Normalization Content Service, which is a data service that provides standardized information about hardware models from various manufacturers. You can access this service from the Hardware Model Normalization module under Asset Management. To set the normalized display name for a hardware model, you need to use the following three fields from the hardware model record:

Name: This is the name of the hardware model as it appears in the model catalog or the CMDB. For example, “iPhone 12 Pro”.

Manufacturer: This is the name of the manufacturer of the hardware model. For example, “Apple”.

Model number: This is the unique identifier of the hardware model assigned by the manufacturer. For example, “A2341”.

The normalized display name is a combination of these three fields, separated by commas. For example, “iPhone 12 Pro, Apple, A2341”. The normalized display name helps you to easily identify and compare hardware models across different sources and platforms. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Work with hardware normalization, Hardware Asset Management - ServiceNow

An asset is a record that represents any tangible or intangible object that is tracked by the organization12.

There are different types of assets, depending on their nature, usage, and lifecycle12.

The types of assets are12:

Model: A model is a record that defines the common attributes and specifications of a group of assets, such as manufacturer, product, category, and device type12. For example, Dell Latitude E7450 is a model of a laptop.

Software entitlement: A software entitlement is a record that defines the rights and obligations of using a software product, such as license type, quantity, expiration date, and cost13. For example, Microsoft Office 365 is a software entitlement that grants access to various

Once a catalog item has been requested, the mechanism that determines the approvals and tasks that are triggered in the application is the flow12.

A flow is a graphical representation of a business process that consists of one or more actions, such as approvals, tasks, notifications, scripts, etc., that are executed based on certain conditions and triggers12.

A flow can be associated with a catalog item to define the fulfillment process for that item, such as who needs to approve it, what tasks need to be performed, and what notifications need to be sent12.

A flow can be created and managed using the Flow Designer, a low-code development tool that allows users to design and test flows without writing any code12.

A flow can be activated or deactivated, versioned, and published to make it available for use12.

A flow can be monitored and debugged using the Flow Execution Details and the Flow Logs12. References:

Flow Designer

Service Catalog Request Fulfillment

According to the ServiceNow Hardware Asset Management documentation, an asset record should track the following information:

Financial information: This includes the cost, depreciation, and residual value of the asset. This information helps to calculate the total cost of ownership (TCO) and return on investment (ROI) of the asset.

Contractual information: This includes the warranty, support, lease, and maintenance contracts associated with the asset. This information helps to manage the lifecycle of the asset and ensure compliance with the terms and conditions of the contracts.

Other information that can be tracked in an asset record are:

Physical resources: This includes the location, status, and condition of the asset. This information helps to monitor the inventory and availability of the asset.

Operational details: This includes the configuration, performance, and usage of the asset. This information helps to optimize the functionality and efficiency of the asset.

Logical relationships: This includes the dependencies, associations, and impacts of the asset. This information helps to understand the connections and interactions of the asset with other assets, services, and processes.

 Asset form, Hardware Asset Management: Record Keeping, Hardware Asset Inventory Management, Hardware Asset Workspace, Getting Started with ServiceNow Hardware Asset Management

According to the ServiceNow Hardware Asset Management documentation, the ServiceNow Content Service is a cloud-based service that provides content updates for hardware models, such as manufacturer, model category, and lifecycle information. The ServiceNow Content Service also collects unrecognized data from customers, such as new or custom hardware models, to improve the content quality and coverage. Customers can opt out of sending unrecognized data to the ServiceNow Content Service for specific models, but this will also prevent them from receiving content updates for those models.

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

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.

The retirement of an IT asset is the final stage of the hardware asset lifecycle, where the asset is removed from service and disposed of in a secure and compliant manner1.

The retirement of an IT asset should be done according to the company-defined policies and procedures, which may vary depending on the type, condition, and value of the asset, as well as the business needs and regulatory requirements1.

The company-defined policies and procedures should specify the criteria, process, and documentation for retiring an IT asset, such as the following1:

The trigger events or conditions that indicate the need for retirement, such as end-of-life, end-of-service, end-of-warranty, obsolescence, damage, theft, or loss

The approval workflow and roles involved in the retirement decision, such as the asset manager, the asset owner, the finance department, and the security department

The disposal methods and vendors available for the retirement, such as recycling, reselling, donating, or destroying

The certificate of destruction or disposal that verifies the secure and compliant disposal of the asset by the vendor

The update of the asset record and the configuration management database (CMDB) to reflect the retirement status and date of the asset

Therefore, the answer that reflects the company-defined policies and procedures is B. At any point that it is recommended by your company-defined policies and procedures.

The other options are not the correct answer because they are either too vague or too specific:

A. At any point it is recommended by the HAM-defined asset policy: This is too vague, as the HAM-defined asset policy may not cover all the aspects and scenarios of the retirement process. The HAM-defined asset policy is a general guideline that defines the objectives, scope, roles, and responsibilities of hardware asset management2. It does not necessarily provide the detailed criteria, process, and documentation for retiring an IT asset.

C. At any point it is recommended by the HAM-defined asset disposal procedure: This is too specific, as the HAM-defined asset disposal procedure is only one part of the retirement process. The HAM-defined asset disposal procedure is a step-by-step instruction that describes how to dispose of an IT asset through a vendor3. It does not necessarily cover the trigger events, approval workflow, and record update for retiring an IT asset.

D. When the Hardware Content Service Lifecycle data reports the asset is nearing end-of-service: This is too specific, as the Hardware Content Service Lifecycle data is only one possible source of information for the retirement decision. The Hardware Content Service Lifecycle data is a subscription-based service that provides the end-of-life, end-of-service, and end-of-support dates for hardware models4. It does not necessarily reflect the actual condition, value, and usage of the individual IT asset.

E. When the Hardware Content Service Lifecycle data reports the asset is nearing end-of-life: This is also too specific, for the same reasons as option D. References:

1: Hardware Asset Retirement

2: Hardware Asset Policy

3: Hardware Asset Disposal

4: Hardware Content Service Lifecycle

According to the Hardware Asset Management documentation, a transfer order is a record that tracks the movement of assets from one stockroom to another.

A transfer order line is a record that specifies the quantity and type of assets to be transferred, as well as the source and destination stockrooms1.

When using the HAM application, what happens when you create a new transfer order line on a transfer order is that a transfer order line task is automatically created to move the transfer order line from one stage to another1.

A transfer order line task is a record that tracks the progress of the transfer order line through the following stages1:

Requested: The transfer order line is created and waiting for approval.

Approved: The transfer order line is approved and ready for fulfilment.

Fulfilled: The transfer order line is fulfilled and the assets are shipped from the source stockroom.

Received: The transfer order line is received and the assets are checked in at the destination stockroom.

Closed: The transfer order line is closed and the transfer is complete.

Therefore, the correct answer is option C, a transfer order line task is automatically created to move the transfer order line from one stage to another, as it describes what happens when you create a new transfer order line on a transfer order. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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.

Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.

Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.

Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.

Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

According to the Hardware Asset Management page, the HAM application includes the following features: Hardware Asset Workspace, Hardware Normalization, Asset Lifecycle Automation, Return Merchandise Authorization, Asset Reservations, Asset Onboarding and Offboarding, Mobile Asset Receiving, Mobile My Locker, Asset Inventory Audit, and Hardware Asset Dashboard.

Among these features, Mobile Asset Receiving, Hardware Model Normalization, and Hardware Asset Dashboard are the ones that expand the baseline ITSM Asset Management, which only covers Asset & Model Records and Stockrooms.

Mobile Asset Receiving allows users to receive multiple assets against a purchase order using a mobile device, which simplifies the asset receiving process and reduces errors.

Hardware Model Normalization standardizes asset data by manufacturer name, model name, and model number, which improves data quality and accuracy in the CMDB.

Hardware Asset Dashboard provides a comprehensive view of hardware asset data, such as asset counts, costs, compliance, and lifecycle stages, which helps users make informed decisions and optimize asset performance. References:

Hardware Asset Management

What is Hardware Asset Management?

[Hardware Asset Management - ServiceNow Docs]

According to the ServiceNow Hardware Asset Management documentation, a business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried. Business rules can be used to enforce data consistency and integrity, such as preventing duplicate transfers of the same asset. The other options are not valid terms in ServiceNow Hardware Asset Management.

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.

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?

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