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

https://docs.servicenow.com/bundle/utah-it-asset-management/page/product/hardware-asset-management/reference/audit-results.html

The Service Catalog provides a user-friendly interface for requesting hardware assets and services from the IT department1

The Service Catalog facilitates the ability to source from existing stock by allowing users to select from a list of available hardware products that are in stock or reserved in a stockroom2

The Service Catalog also enables users to view the status of their requests, track the delivery and return of assets, and report any issues or incidents related to assets1

The Service Catalog is integrated with the Procurement Catalog, which contains the list of hardware products that are currently on order or have been received from vendors3

The Service Catalog is also linked to the Product Catalog, which contains the list of hardware products that are available for purchase from vendors or internal sources4

The Vendor Catalog contains the list of vendors that supply hardware products, but it does not facilitate the ability to source from existing stock

When disposing of an IT asset through a vendor, the asset manager should attach a certificate of destruction to the retired asset’s record1.

A certificate of destruction is a document that verifies that the asset has been destroyed in a secure and compliant manner by the vendor1.

A certificate of destruction should include information such as the asset tag, serial number, model, manufacturer, date of destruction, method of destruction, and signature of the authorized person1.

A certificate of destruction helps the asset manager to ensure that the asset is no longer in use, that the data on the asset is erased, and that the asset is disposed of in accordance with environmental, regulatory, and legal requirements1. References:

1: Hardware Asset Disposal

The Hardware Asset dashboard is a collection of data visualizations that show key metrics on your hardware and consumable models and assets for the entire asset life cycle1.

The tabs in the Hardware Asset dashboard are updated in real time, meaning that they reflect the latest data from the Hardware Asset Management application2.

The tabs in the Hardware Asset dashboard are not based on scheduled jobs, hourly intervals, or 15-minute intervals, as these options would not provide the most accurate and up-to-date information on your hardware assets. References: 1: Hardware Asset dashboard - Product Documentation: San Diego - ServiceNow 2: Hardware Asset Management overview - ServiceNow - Now Support

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?

Transform maps are used to transform imported hardware model data from an import set table to a target table, such as the Product Catalog or the Asset table1

Coalesce is an option that you can set on a field mapping to uniquely identify the same asset in order to merge or update records2

Coalesce means that the field is used as a unique key. If a match is found using the coalesce field, the existing record is updated with the imported information. If no match is found, a new record is inserted2

Coalesce helps to prevent duplicate records and ensure data consistency2

You can set coalesce on one or more fields in a transform map, but at least one coalesce field is required2

The other options, B. Consolidate, C. Unique identifier, D. Unique source, E. Unique target, and F. Combine, are not valid options for setting the unique identification of assets in transform maps

The Normalization statuses are the indicators of how well the hardware and consumable models are standardized and normalized in the model catalog and the CMDB. The Normalization statuses are:

Manufacturer Normalized: The model has been normalized with the manufacturer name and the product name, but not the model number or the device type. For example, Dell Latitude.

Match Not Found: The model has not been normalized because no matching model was found in the Hardware Asset Management Content Service. For example, ABC XYZ.

Partially Normalized: The model has been normalized with the manufacturer name, the product name, and the model number, but not the device type. For example, Dell Latitude E7450.

Normalized: The model has been fully normalized with the manufacturer name, the product name, the model number, and the device type. For example, Dell Latitude E7450 (Laptop).

Manually Normalized: The model has been manually updated by the user with the normalization content, such as the manufacturer name, the product name, the model number, and the device type. For example, HP Pavilion 15 (Laptop).

New: The model has been created and has not yet run through the normalization process. For example, Lenovo ThinkPad T490.

According to the ServiceNow Hardware Asset Management documents, a hardware asset’s lifecycle consists of the following stages: Procure, Receive, Deploy, Maintain, and Dispose1. These stages correspond to the options A, D, and E in the question. The option B, Request, is also a valid stage in the hardware asset management process, as it involves identifying the hardware needs and initiating the procurement process2. However, the option C, Consume, is not a component of a hardware asset’s lifecycle, as it is not mentioned in the ServiceNow documents. Consume is more relevant to software assets, which are used or consumed by end-users or applications3. Therefore, the correct answer is C. Consume. References:

ServiceNow Hardware Asset Management landing page

ServiceNow Hardware Asset Management overview

ServiceNow Software Asset Management overview

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

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

The depreciation effective date captures the residual value, representing the estimated value of an asset at the end of its useful life. This value is essential in determining the depreciation cost over time. For hardware assets, managing depreciation accurately ensures proper financial tracking.

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

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

A stock rule is a record that defines the minimum and maximum quantity of a model or an asset in a stockroom12.

The Stock Rule Runner is a scheduled job that runs every hour and checks the stock levels of models and assets in stockrooms against the stock rules13.

If the stock level of a model or an asset is less than the minimum quantity specified in the stock rule, the Stock Rule Runner creates a stock order to replenish the stock from another stockroom or from a vendor13.

Therefore, the correct answer is A. When stock is less than the threshold specified in the stock rule.

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, 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 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 Normalization Data Services Client plugin enables you to use the Normalization Data Services (NDS) to provide consistent, good, clean data for the company names of vendors or manufacturers12.

The NDS is a cloud-based service that provides a comprehensive and up-to-date list of canonical company names for vendors and manufacturers, as well as other data such as product categories, models, and versions12.

The NDS helps you to avoid data duplication, inconsistency, and inaccuracy in your CMDB and asset management processes12.

The NDS integrates with the Hardware Model Normalization plugin, which standardizes the details of your hardware models by comparing them with the data from the Hardware Model Normalization Content Service13.

Therefore, the correct answer is D. Normalization Data Services Client (com.glide.data_services_canonicalization.client), as this is the plugin that offers consistent, good, clean data for the company names of vendors or manufacturers.

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

The Hardware Asset Management (HAM) plugin is a plugin that enables the Hardware Asset Management application, which helps to track and manage the end-to-end lifecycle of hardware assets, physical and consumable1.

The HAM plugin provides the following baseline asset lifecycle automation flows2:

Hardware asset order: This is a flow that automates the process of ordering new hardware assets from a vendor. It creates purchase orders, stock order tasks, and catalog tasks based on the asset requests and the stock rules2.

Hardware deployment: This is a flow that automates the process of delivering and installing hardware assets to the end users. It creates catalog tasks and updates the asset records and the configuration management database (CMDB) based on the stock order tasks and the asset reservations2.

Hardware disposal: This is a flow that automates the process of disposing of retired hardware assets through a vendor. It creates return merchandise authorization (RMA) records and updates the asset records and the CMDB based on the asset retirements and the vendor contracts2.

Therefore, the baseline asset lifecycle automation flows that are also options in the question are A. Hardware asset order, E. Hardware deployment, and F. Hardware disposal.

The other options that are not baseline asset lifecycle automation flows provided by the HAM plugin are:

B. Hardware bulk stock order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to create multiple stock order tasks for different hardware models at once3.

C. Hardware swap order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to swap a hardware asset with another hardware asset of the same model4.

D. Hardware retire order: This is not a baseline asset lifecycle automation flow, but a manual action that allows the user to retire a hardware asset and update its status and substatus. References:

1: Hardware Asset Management

2: Asset Lifecycle Automation Flows

3: Create a Bulk Stock Order

4: Swap a Hardware Asset

: Retire a Hardware Asset

 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.

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use the Principal CI class checkbox, which is available on the Class Manager module under Configuration1.

The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1. By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.

To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1. You can also use the Filter option to search for the CI classes by name or label1.

The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists. Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3. Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4. Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality. References: 1: Principal configuration item classes 2: Configuration item lists 3: CMDB table schema 4: Access control rules : [UI actions]

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.

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

According to the Hardware Asset Management documentation, the Hardware Model Normalization Content Service is a cloud-based service that provides normalized and enriched hardware model data to the ServiceNow platform, such as manufacturer name, model name, model number, and product lifecycle information.

The Hardware Model Normalization Content Service 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 Content Service updates the content library weekly with new and updated model data1.

To determine if the content has been downloaded, you can review the Hardware Model Content Service Download section on the Model Management tab of the Hardware Asset dashboard1.

The Hardware Model Content Service Download section shows the status of the content download, such as the last download date, the number of models downloaded, and the number of models normalized1.

Therefore, the correct answer is option C, review the Hardware Model Content Service Download section on the Model Management tab of the Hardware Asset dashboard, as it is the way to determine if the content has been downloaded. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

Assets are tangible items tracked for lifecycle management and financial purposes. Facilities (e.g., buildings), servers, and network cables are physical assets. Software licenses and distributions are intangible and treated differently in ServiceNow Asset Management.

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?

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

Now Create is a solution that provides step-by-step delivery guidance based on real-world experiences and proven leading practices, to perform digital transformations using ServiceNow products12.

A success pack is a collection of processes and assets that, when executed by qualified ServiceNow practitioners, will deliver successful outcomes for your project13.

A process is a set of tasks that guides you through the implementation or upgrade of a ServiceNow product or feature1.

An asset is an input to the methodology and can be product specific leading practice detailed instructions related to the success pack or other product agnostic project templates and accelerators1.

A success pack can be exported into ServiceNow SPM (and other project execution tools) to accelerate project start-up and provide easy links back to Now Create throughout the project execution1.

The other options are not correct terms used in Now Create. There is no such thing as a Now Create pack, a project pack, a methodology pack, or an asset pack.

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?

 According to the ServiceNow Hardware Asset Management documentation, assets can be moved between stockrooms by using transfer orders. A transfer order is a record that tracks the movement of assets from one stockroom to another. A transfer order can be created manually by the stock manager or automatically by the system based on predefined rules or workflows1. A transfer order contains information such as the source and destination stockrooms, the assets to be transferred, the shipment details, and the status of the transfer2.

The other options are not correct because:

Stock orders are records that track the procurement of assets from vendors, not the movement of assets between stockrooms3.

Stock rules are rules that define the minimum and maximum stock levels for each asset model in a stockroom, not the movement of assets between stockrooms.

Transfer rules are rules that define the conditions and actions for creating transfer orders automatically, not the records that track the movement of assets between stockrooms.

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]

The core table that requires migration when extending ITSM Asset Management with Hardware Asset Management is the alm_asset table1.

The alm_asset table stores the records of all the assets in the system, regardless of their type or class1.

When you activate the Hardware Asset Management plugin, a migration script runs that converts the existing asset records in the alm_asset table to hardware asset records in the alm_hardware table2.

The alm_hardware table is a child table of the alm_asset table that stores the records of the hardware assets only2.

The migration script also updates the references and relationships of the migrated assets to the new table2.

The migration script runs only once and does not affect the future creation or update of asset records2. References:

Asset table - Product Documentation: San Diego - ServiceNow

Hardware Asset Management - Product Documentation: Tokyo - ServiceNow

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.