Pass the ServiceNow CIS-Hardware Asset Management CIS-HAM Questions and answers with CertsForce

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.

Operational: The current status, performance, availability, and capacity of the CI, as well as any incidents, problems, or changes that affect it.

Relationship: The dependencies and connections between the CI and other CIs, services, processes, and users.

The information that you would track for an asset includes:

Financial: The cost, depreciation, ownership, and warranty of the asset, as well as any procurement or disposal activities.

Lifecycle: The stages and transitions of the asset from request to retirement, as well as any inventory or stock management.

The information that you would not track for a CI versus an asset are:

Contractual: This information is relevant for both CIs and assets, as it relates to the agreements and obligations between the service provider and the customer or vendor.

Lifecycle: This information is relevant for both CIs and assets, as it relates to the stages and transitions of the component from request to retirement.

 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.

To perform hardware model normalization, you need to use the Hardware Model Normalization Content Service, which is a data service that provides standardized information about hardware models from various manufacturers. You can access this service from the Hardware Model Normalization module under Asset Management. To set the normalized display name for a hardware model, you need to use the following three fields from the hardware model record:

Name: This is the name of the hardware model as it appears in the model catalog or the CMDB. For example, “iPhone 12 Pro”.

Manufacturer: This is the name of the manufacturer of the hardware model. For example, “Apple”.

Model number: This is the unique identifier of the hardware model assigned by the manufacturer. For example, “A2341”.

The normalized display name is a combination of these three fields, separated by commas. For example, “iPhone 12 Pro, Apple, A2341”. The normalized display name helps you to easily identify and compare hardware models across different sources and platforms. References: Hardware Model Normalization, Demo - HAM Professional - Hardware Model Normalization, Work with hardware normalization, Hardware Asset Management - ServiceNow

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.

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

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.

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