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

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.

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.

According to the ServiceNow Hardware Asset Management overview document1, the total cost of ownership (TCO) of an asset is the sum of all direct and indirect costs incurred throughout its lifecycle, from acquisition to disposal1.

The original costs are the costs involved in purchasing an asset and putting it into use, such as lease, delivery, and spare parts12.

Lease is the cost of renting or leasing an asset from a vendor or a third party for a fixed period of time12. Lease costs can vary depending on the terms and conditions of the contract, such as duration, frequency, and interest rate2.

Delivery is the cost of transporting or shipping an asset from the vendor or the warehouse to the end user or the location where it will be used12. Delivery costs can include fees, taxes, customs, and insurance2.

Spare parts are the cost of purchasing or stocking additional or replacement parts for an asset in case of failure, damage, or wear and tear12. Spare parts costs can depend on the availability, quality, and compatibility of the parts2.

The other options are not original costs, but rather ongoing or disposal costs. Maintenance is the cost of repairing, servicing, or upgrading an asset to keep it in good working condition12. Storage is the cost of storing an asset that is not in use or waiting for disposal12.

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

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

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

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

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

2: Normalization Data Services - ServiceNow

According to the 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, 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.

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?

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.

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

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

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

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 first tier of the capability blueprint emphasizes building Trustworthy Data. Without accurate and reliable data, further optimization in asset or service management is impossible. It sets the foundation for all other tiers.

Hardware normalization is a process that standardizes the data of hardware and consumable models by using the United Nations Standard Products and Services Code (UNSPSC) and a set of rules12.

Normalization can be performed manually or automatically on models in the model catalog12.

If a model has been normalized, it will have a check mark in the Normalized column in the model list1.

To revert the normalization of a model, you can use the Revert Normalization UI action, which is available on the model form13.

The Revert Normalization UI action will restore the original values of the model attributes that were changed by the normalization process13.

The Revert Normalization UI action will also clear the Normalized check mark and the Normalization Source field on the model form13. References: Work with hardware normalization - ServiceNow - Now Support, Hardware Asset Management builds onCore Asset Management - ServiceNow, Automation Simplifies Hardware Asset Management - ServiceNow Blog, Product Documentation | ServiceNow

According to the ServiceNow Hardware Asset Management documentation, advanced risk assessment is a process of identifying, analyzing, and evaluating the risks associated with hardware assets and configuration items (CIs) in the configuration management database (CMDB)1. Advanced risk assessment uses the Advanced Risk Assessment engine, which is built to address risk through an integrated risk framework2. The advanced risk assessment process consists of the following steps1:

Create a risk assessment scope: This step defines the scope and criteria of the data to be assessed, such as the asset class, category, or attribute. The risk assessment scope also specifies the frequency and duration of the assessment.

Create a risk assessment schedule: This step determines when and how often the assessment runs, based on the risk assessment scope. The risk assessment schedule also defines the assessment owner, who is responsible for overseeing the assessment process and approving the results.

Assign the assessment tasks: This step assigns the assessment tasks to the appropriate assessors, who are the users or groups who have the knowledge and authority to evaluate and update the data. The assessment tasks can be assigned manually or automatically, based on predefined rules or workflows.

Run the assessment: This step executes the assessment process, which involves sending notifications and reminders to the assessors, displaying the data to be assessed in a user-friendly interface, allowing the assessors to review and modify the data, and tracking the progress and status of the assessment tasks.

Review the assessment results: This step allows the assessment owner to verify and approve the results of the assessment, before applying the changes to the CMDB. The assessment owner can also view the risk scores, risk indicators, and risk heat maps of the assessed data.

Handle the risk response: This step involves creating and managing risk response tasks to address the identified risks. Risk response tasks are records that track the actions taken to mitigate, transfer, avoid, or accept the risks. Risk response tasks can be created manually by the assessment owner or automatically by the system based on predefined rules or workflows.

For advanced risk assessment, risk response can be handled in the following ways:

Create multiple risk response tasks: This option allows the assessment owner to create more than one risk response task for each assessed data, depending on the complexity and severity of the risk. For example, the assessment owner can create a mitigation task to reduce the impact or likelihood of the risk, and a transfer task to shift the responsibility or ownership of the risk to another party3.

Create at least one risk response task: This option requires the assessment owner to create at least one risk response task for each assessed data, regardless of the complexity and severity of the risk. This ensures that every risk is addressed and documented in the system3.

The other options are not correct because:

Skipped entirely based on attributes defined in the RAM: This option is not a valid way to handle risk response for advanced risk assessment. The RAM (Risk Assessment Matrix) is a tool that helps to calculate the risk score and risk indicator of the assessed data, based on the impact and likelihood attributes defined in the risk assessment scope1. The RAM does not determine whether to skip the risk response or not.

Must create a mitigation response task: This option is not a mandatory way to handle risk response for advanced risk assessment. A mitigation response task is one of the possible types of risk response tasks, but not the only one. Depending on the risk appetite and strategy of the organization, the assessment owner can choose other types of risk response tasks, such as transfer, avoid, or accept3.

Inventory audits are the processes of verifying the accuracy and consistency of the hardware asset inventory across the enterprise1.

The Hardware Asset Management (HAM) application supports the following types of inventory audits1:

Stockroom audit: This is an audit that verifies the quantity and condition of the hardware assets in a stockroom. A stockroom is a physical location where hardware assets are stored before they are delivered to the end users or transferred to another stockroom2. A stockroom audit helps to optimize the inventory levels, avoid overstocking or understocking, and identify any discrepancies or issues with the stockroom assets1.

Location audit: This is an audit that verifies the presence and status of the hardware assets in a specific location, such as an office, a building, or a floor. A location audit helps to ensure that the hardware assets are assigned to the correct owners, locations, and departments, and to identify any missing, unknown, or unauthorized assets1.

Therefore, the types of inventory audits that are also options in the question are A. Stockroom audit and C. Location audit.

The other options that are not types of inventory audits supported by the HAM application are:

Vendor audit: This is not a type of inventory audit, but a type of vendor management activity. Vendor management is the process of managing the relationships and contracts with the vendors that provide hardware assets and services to the organization3. Vendor audit is an activity that evaluates the performance, quality, and compliance of the vendor based on predefined criteria and metrics3.

Discovery audit: This is not a type of inventory audit, but a type of configuration management activity. Configuration management is the process of maintaining the accuracy and consistency of the operational and relationship information of IT assets and services in the Configuration Management Database (CMDB)4. Discovery audit is an activity that compares the actual configuration items (CIs) in the IT environment with the expected CIs in the CMDB and identifies any differences or discrepancies4. References:

1: Hardware Asset Inventory Audit

2: Stockrooms

3: Vendor Management

4: Configuration Management

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

According to the Hardware Asset Management documentation, the Hardware Asset Management (HAM) plugin is a licensable application that provides advanced workflow, automation, and mobile capabilities to maintain your assets.

To activate the HAM plugin, you need to request it from the HI Customer Service System1.

Once the HAM plugin is activated, you can access the Hardware Asset Management application from the application navigator in the ServiceNow platform2.

The Hardware Asset Management application contains several modules, such as Hardware Assets, Hardware Asset Dashboard, Hardware Normalization, and Asset Lifecycle Automation2.

Therefore, the correct answer is option D, check for the Hardware Asset Management application in the application navigator, as it indicates that the HAM plugin is installed on your instance. References:

Hardware Asset Management documentation

Hardware Asset Management - Product Documentation: Tokyo - ServiceNow

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.

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

Hardware model normalization is a feature that enables users to normalize the details, such as manufacturer, product, model, and device type, of their hardware and consumable models1.

Hardware model normalization uses the data from the Hardware Model Normalization Content Service, which is a cloud-based service that provides standardized information for thousands of hardware models1.

The key attribute in the model record that hardware model normalization uses to normalize inconsistent manufacturers and product names is the model number12.

The model number is a unique identifier for a specific product or model that is assigned by the manufacturer12. It is based on the United Nations Standard Products and Services Code (UNSPSC), which is a global classification system for products and services23.

Hardware model normalization compares the model number of the model record with the model number of the Hardware Model Normalization Content Service record and updates the model record with the normalized information, such as display name, manufacturer, product, and device type12.

The other options are not the key attribute that hardware model normalization uses to normalize inconsistent manufacturers and product names. The asset tag, the display name, the model category, and the asset tracking unit are either not unique or not based on the UNSPSC.

According to the ServiceNow Hardware Asset Management documentation, the core sets of data required for effective IT asset management are:

•Manufacturers: The companies that produce the hardware assets, such as Dell, HP, Cisco, etc.

•Locations: The physical places where the hardware assets are stored or used, such as offices, data centers, warehouses, etc.

•Users: The people who own, use, or manage the hardware assets, such as employees, customers, vendors, etc.

•Models: The specific types or categories of hardware assets, such as laptops, servers, routers, etc.

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

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

A transfer order is a document that records the movement of assets from one location to another1.

A transfer order line is a record that specifies the quantity and type of assets to be transferred1.

When you cancel a transfer order line, the associated assets are released from the transfer order and their state changes from Pre-allocated to Available1.

The released assets can then be attached to another transfer order or used for other purposes1. References:

Transfer orders - Product Documentation: Rome - ServiceNow

Normalization is the process of aligning hardware asset data with the ServiceNow Content Library, which provides standardized values for manufacturer, product name, and model number. During normalization, the system compares the hardware model data with the content library and assigns a status to indicate the level of match. The status of Match Not Found means that the system could not find any matching record in the content library for the hardware model. The most common cause for this status is missing data, such as an empty manufacturer field or a generic product name. To resolve this issue, the user can manually edit the hardware model record and provide the missing data, or use the lookup feature to search for a matching record in the content library. Alternatively, the user can create a new content library record for the hardware model and link it to the asset record. References:

Hardware model normalization

Normalize hardware models

Create a content library record

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

According to the ServiceNow Product Documentation on Document Templates1, document templates are records that define the layout and content of a document that can be generated from a table record, such as an HR case1. They can include information such as fields, variables, images, and signatures1.

According to the ServiceNow Product Documentation on Generate Documents from Templates2, when a document template is created from an HR case, the name of the person who created the document is added to the name of the attachment2. For example, if John Smith created a document from the template Employee Termination Letter, the attachment name would be Employee Termination Letter - John Smith.docx2.

The reason for this naming convention is to indicate who generated the document, which can be useful for auditing and tracking purposes2. It can also help to avoid confusion or duplication if multiple documents are generated from the same template by different users2.

The other options are not the correct explanation for why the name of the person who created the document is added to the name of the attachment. It does not indicate who should sign the document, as the signature can be added as a variable in the template1. It does not indicate the Opened for user, as the document can be generated for any HR case, not necessarily the one that the user opened2. It does not indicate who the document is about, as the document can contain information about multiple parties, such as the employee, the manager, and the HR representative2.

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

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

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

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

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.

The Asset Operations view consolidates tasks such as RMAs, audits, disposals, and stock orders into a single workspace, enabling managers to streamline operations efficiently.

A blind audit is a type of inventory audit that does not provide any information about the expected assets in a location. The auditor scans all the assets in the location and compares them with the records in ServiceNow1.

To perform a blind audit, you need the Hardware Asset Management (HAM) application, which enables you to manage the lifecycle of your hardware assets, and the ServiceNow Agent mobile app, which allows you to scan asset tags and barcodes using your mobile device12.

The ServiceNow My Assets mobile app is used to view and request assets from the enterprise asset catalog, not to perform audits3.

The Software Asset Management (SAM) application is used to optimize software licenses and compliance, not to perform audits4.

The ITSM Asset Management application is used to track the financial, contractual, and inventory details of hardware and devices, not to perform audits. References:

1: Audit your inventory - Product Documentation: San Diego - ServiceNow

2: Enterprise Asset Inventory Management - ServiceNow

3: My Assets mobile app - Product Documentation: San Diego - ServiceNow

4: Software Asset Management - ServiceNow

: IT Asset Management - ServiceNow

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

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

ServiceNow Hardware Asset Management: Hardware Asset Management overview

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

Hardware model normalization is a feature that enables users to normalize the details, such as manufacturer, product, model, and device type, of hardware and consumable models1

Hardware model normalization uses the data from the models and compares it against the data in the Hardware Model Normalization Content Service, which is a cloud-based service that provides standardized and enriched information about hardware models1

Hardware model normalization sets the normalized display name for each model record based on three attributes: Name, Manufacturer, and Model number2

The Model Management tab of the Hardware Asset dashboard shows the status of the hardware models in the Product Catalog, such as Matched, Match Not Found, or Not Normalized3

Several of your models are listed as Match Not Found on the Model Management tab of the Hardware Asset dashboard. This means that the normalization process could not find a matching rule in the Content Service for those models3

The potential causes of this are34:

The hardware model content has not yet been downloaded from the Content Service. The Content Service is updated periodically with new and updated rules for hardware models. You need to download the latest content from the Content Service to ensure that your models are normalized with the most accurate and complete information. You can download the content manually or schedule it to run automatically.

Normalization could not match any of the three key fields in the hardware model form with a rule in the Content Service. The three key fields are Name, Manufacturer, and Model number. If any of these fields are missing, incorrect, or inconsistent with the data in the Content Service, the normalization process will fail to find a matching rule. You need to review and correct the data in these fields to ensure that they match the data in the Content Service.

A normalization rule for the hardware model does not exist in the Content Service. The Content Service may not have a rule for some hardware models, especially if they are new, rare, or custom-made. In this case, you can create a custom rule for the hardware model in the Hardware Model Normalization Rules module, or submit a request to the Content Service team to add a rule for the hardware model.