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, hardware model lifecycle phases are the stages that a hardware model goes through from its introduction to the market to its retirement. The valid hardware model lifecycle phases are:

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

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

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

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

The Procurement tab of the Hardware Asset dashboard is a graphical representation of the hardware asset procurement across the enterprise1.

The Procurement tab provides the following information1:

Hardware expenditure by vendor: This shows the total amount spent on hardware assets from each vendor in the current fiscal year. This helps to analyze the vendor performance and negotiate better contracts.

Requests that require sourcing: This shows the number and status of asset requests that need to be fulfilled by purchasing new hardware assets from a vendor. This helps to prioritize the procurement activities and optimize the inventory levels.

Therefore, the information that are also options in the question are C. Hardware expenditure by vendor and F. Requests that require sourcing.

The other options that are not information on the Procurement tab are:

Hardware nearing end of warranty: This is an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that are nearing or have expired their warranty period1.

Hardware model normalization status: This is an information on the Normalization tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are normalized or not normalized1.

Hardware models up for end of life: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware models that are approaching or have reached their end of life date1.

New hardware assets found by audits: This is also an information on the Inventory tab of the Hardware Asset dashboard. This shows the number and percentage of hardware assets that were discovered by the asset inventory audit process but were not previously recorded in the CMDB1. References:

1: Hardware Asset Dashboard