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

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

The total cost of ownership (TCO) is a financial estimate that measures the direct and indirect costs of owning and operating an asset over its entire lifecycle. The TCO includes the following components:

Original cost: This is the initial purchase price of the asset, which may include taxes, fees, shipping, and installation costs. The original cost is also known as the acquisition cost or the capital expense.

Operational expense: This is the ongoing cost of maintaining and using the asset throughout its lifecycle, which may include repair, upgrade, maintenance, support, energy, consumables, and disposal costs. The operational expense is also known as the operating expense or the opex.

Depreciation expense: This is the reduction in the value of the asset over time due to wear and tear, obsolescence, or market changes. The depreciation expense is also known as the depreciation cost or the depreciation charge.

Delivery cost: This is the cost of transporting the asset from the supplier to the buyer, which may include freight, insurance, customs, and handling fees. The delivery cost is also known as the shipping cost or the transportation cost.

The TCO can be calculated by adding the original cost, the operational expense, and the depreciation expense, and subtracting the delivery cost. Alternatively, the TCO can be calculated by multiplying the annual cost of ownership by the expected lifespan of the asset.

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

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

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

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

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

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

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

Flow Designer

Service Catalog Request Fulfillment

Normalization mappings are a feature of the Hardware Asset Management (HAM) application that allow you to standardize the manufacturer name, model name, and model number of hardware assets in the Configuration Management Database (CMDB)1.

Normalization mappings are created by matching the values from the discovery source to the values in the Product Catalog2.

Normalization mappings help you to fully normalize hardware models by ensuring that the asset data is consistent, accurate, and complete3. References:

Hardware Normalization

Create normalization mappings

What is Hardware Asset Management?

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

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

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

The types of assets are12:

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

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

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?

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

 Hardware Model Normalization is a feature that enables users to standardize the data of hardware and consumable models, such as manufacturer, product, model, and device type. Hardware Model Normalization requires the activation of the Hardware Model Normalization (com.sn_hwnorm) plugin, which also activates the Normalization Data Services Client (com.glide.data_services_canonicalization.client) plugin. These plugins install several tables that store the normalized data and the rules for normalization. The tables that are installed with Hardware Model Normalization are:

Device Type: This table contains the device types that are used to categorize the hardware models, such as laptop, desktop, server, printer, etc.

Hardware Manufacturer: This table contains the normalized names of the hardware manufacturers, such as Dell, HP, Lenovo, etc.

Hardware Model Library: This table contains the normalized data of the hardware models, such as manufacturer, product, model, device type, UNSPSC code, etc. This table is populated by the Hardware Model Normalization Content Service, which is a subscription-based service that provides the latest and most accurate data for hardware models.

Hardware Normalize Key: This table contains the rules for generating the normalize key, which is a unique identifier for each hardware model based on its manufacturer, product, and model. The normalize key is used to match the hardware models with the Hardware Model Library data.

The other options, C. Hardware Normalize Key and E. Device Name, are not tables that are installed with Hardware Model Normalization. Hardware Normalize Key is a field in the Hardware Model [cmdb_model] table, not a separate table. Device Name is a field in the Configuration Item [cmdb_ci] table, not a separate table. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Hardware Asset Management

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

 According to the ServiceNow Hardware Asset Management documentation, the Now Agent Mobile App is a mobile application that enables users to perform various asset management tasks on the go, such as creating assets, performing inventory audits, and receiving assets1. The Now Agent Mobile App provides access to the following features2:

Asset Receiving: Users can receive multiple assets against a purchase order using a mobile device. Users can scan barcodes or QR codes to identify assets and update their status and location.

Asset Inventory Audit: Users can manage assets across locations with simplified mobile inventory processes. Users can scan barcodes or QR codes to verify assets and update their information. Users can also view audit results and resolve discrepancies.

Asset Creation: Users can create new assets using a mobile device. Users can scan barcodes or QR codes to populate asset fields and assign them to stockrooms or users.

The other options, Now Procurement App, Now Mobile App, and Now Onboarding App, are not related to hardware asset management. The Now Procurement App is a mobile application that enables users to manage purchase orders, requisitions, and contracts3. The Now Mobile App is a mobile application that enables users to access ServiceNow services and information, such as requesting items, viewing incidents, and checking assigned assets. The Now Onboarding App is a mobile application that enables users to complete onboarding tasks, such as signing documents, enrolling in benefits, and setting up devices. References:

ServiceNow Hardware Asset Management: Now Agent Mobile App

ServiceNow Hardware Asset Management: Mobile Asset Management

ServiceNow Hardware Asset Management: Now Procurement App

[ServiceNow Hardware Asset Management: Now Mobile App]

[ServiceNow Hardware Asset Management: Now Onboarding App]

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 documentation, an asset is "any tangible or intangible item that might have value for an organization"1.

The default asset classes in ServiceNow are Hardware, Software License, Consumable, Bundle, Software Entitlement, and Facility1.

These general classes can be used to manage various assets, such as computers, printers, software licenses, office supplies, software subscriptions, and buildings1.

Therefore, facilities, hardware, and software entitlements are considered assets, while contracts and software distributions are not. References:

Asset and configuration item (CI) management - ServiceNow

According to the ServiceNow Hardware Asset Management overview document1, contracts are records that define the terms and conditions for the acquisition, maintenance, or disposal of assets1. They can include information such as vendor, start date, end date, cost, and renewal options1.

According to the ServiceNow Data Sheet on Contract and Renewal Management2, some of the critical information that should be tracked for contracts are2:

What each contract costs: This information helps users to monitor and optimize the total cost of ownership (TCO) of their assets, as well as to plan and budget for future contract renewals or negotiations2.

What assets each contract covers: This information helps users to identify and manage the assets that are under contract, such as software licenses, hardware devices, or enterprise assets2. It also helps users to align their asset investments to their business outcomes and avoid penalties or service disruptions2.

The other options are not critical information that should be tracked for contracts. Who purchased the assets and what needs to be cancelled are not relevant to the contract management process, as they do not affect the contract terms, conditions, or performance2.

According to the ServiceNow Hardware Asset Management documentation, original cost is the amount paid to acquire an asset, including any taxes, fees, shipping, installation, or other expenses directly related to the purchase. Original cost is used to calculate depreciation and amortization of an asset over its useful life. The other options are not the type of cost that taxes paid at the time of purchase are. Operating expense, operating cost, and capital expense are different ways of classifying the costs of using and maintaining an asset after it is purchased.

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

What is Hardware Asset Management?

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.

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

The other options are not correct because:

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

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

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

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 normalized display name is a combination of these three attributes, separated by a hyphen, for example: Dell-Inc.-OptiPlex 70102

The normalized display name helps to identify and group models with similar properties and reduce duplicates and inconsistencies in the model catalog and the Configuration Management Database (CMDB)2

s: 1: Hardware Model Normalization - ServiceNow 2: Set the normalized display name - ServiceNow

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

Stock rules are a feature of ServiceNow Hardware Asset Management that allow you to automate the replenishment of stock levels in your stockrooms1.

Stock rules define the minimum and maximum quantities of a specific model that you want to keep in a stockroom, as well as the reorder point and quantity1.

When the stock level of a model falls below the reorder point, a stock order is automatically generated to replenish the stockroom to the maximum quantity1.

You can create and manage stock rules by navigating to Hardware Asset Management > Model Management > Stock Rules1. References:

1: Stock rules - ServiceNow Docs.

The lifecycle management tab provides details about the normalization status, models nearing end of life, and lease end timelines. Expenditure by vendor and pending purchase orders are unrelated to lifecycle tracking and would typically be found in financial reports or procurement dashboards.

A consumable is a type of asset that is used up or depleted over time, such as printer cartridges, paper, or batteries1.

Before a consumable can be consumed, it must have a model record, a model category record, and a consumable record in ServiceNow12.

A model record defines the attributes of a consumable, such as its name, manufacturer, cost, and quantity12.

A model category record specifies the type of consumable, such as office supplies, hardware, or software12.

A consumable record tracks the current stock level, location, and status of a consumable12.

A stock order record is used to request new consumables from a vendor or supplier, but it is not required before a consumable can be consumed13.

A transfer order record is used to move consumables from one location to another, but it is not required before a consumable can be consumed14. References: 1: Consumables - Product Documentation: Vancouver - ServiceNow 2: Create a consumable model - Product Documentation: Vancouver - ServiceNow 3: Create a stock order - Product Documentation: Vancouver - ServiceNow 4: Create a transfer order - Product Documentation: Vancouver - ServiceNow

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

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.

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

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

90 days ahead of the contract expiration date

60 days ahead of the contract expiration date

30 days ahead of the contract expiration date

Day of expiration

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

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.

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.

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

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.

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

https://docs.servicenow.com/bundle/sandiego-it-service-management/page/product/incident-management/task/track-ci.html

The Identification and Reconciliation process in ServiceNow ensures that configuration items (CIs) are correctly matched during the import process. This prevents duplication by validating unique identifiers, such as serial numbers or UUIDs, ensuring CMDB integrity.

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