A model category is a classification of models that defines how they are managed in the system1. It determines the behavior and attributes of the models and the assets or configuration items (Cls) that are created from them1.

Model categories can be used to group consumables, assets, or services in the product catalog or the service catalog, but this is not their primary function. Their primary function is to define the relationship between configuration management and asset management1.

Configuration management is the process of identifying, tracking, and verifying the configuration items (Cls) in an IT environment and their relationships2. Asset management is the process of tracking and managing the financial, contractual, and inventory details of IT assets throughout their lifecycle3.

Model categories determine when to create assets from configuration items (Cls) based on the asset tracking strategy1. For example, some model categories, such as Computer, create assets automatically when Cls are discovered or imported1. Other model categories, such as Consumable, require manual creation of assets from the product catalog1.

Model categories also provide the link between configuration management and asset management by allowing asset managers to view the configuration data of the assets and configuration managers to view the asset data of the Cls1. This enables better visibility, control, and alignment of IT assets and services1.

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.

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

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

The main purposes of transfer order line tasks are2:

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

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

The CMDB Health Dashboard is a tool that monitors and reports the health of the Configuration Management Database (CMDB) data based on four key performance indicators (KPIs): completeness, compliance, correctness, and relationship accuracy12.

Completeness measures the percentage of configuration items (CIs) that have the required and recommended attributes populated12.

Compliance measures the percentage of CIs that adhere to predefined regulatory requirements, internal governance, and certificates12.

Correctness measures the percentage of CIs that pass the predefined data integrity rules, such as identification rules, orphan CI rules, and stale CI rules12.

Relationship accuracy measures the percentage of CIs that have the expected relationships with other CIs12.

The CMDB Health Dashboard focuses on the first three areas of data quality: completeness, compliance, and correctness12. These areas are also reflected in the overall CMDB health score, which is calculated as the weighted average of the three KPIs12.

The other options, configuration, conciseness, and conformity, are not the areas of data quality that the CMDB Health Dashboard focuses on12.

Configuration is the process of defining and managing the characteristics of CIs, such as their attributes, relationships, dependencies, and status3.

Conciseness is the quality of being clear and brief, without unnecessary words or details4.

Conformity is the quality of being consistent with a set of rules, standards, or expectations5.

According to the Hardware Asset Management documentation, the hardware asset management 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 asset management content service helps customers identify and manage their hardware assets more effectively, as well as plan for hardware refreshes based on end-of-life (EOL) and end-of-service (EOS) dates1.

The elements that are provided by the hardware asset management content service are as follows1:

Manufacturer lifecycle dates: The dates when the manufacturer stops selling, supporting, or servicing a hardware product.

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

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

Therefore, the correct answers are options A, D, and E, as they are the elements that are provided by the hardware asset management content service. References:

Hardware Asset Management documentation

What is Hardware Asset Management?

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.

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

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

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.