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

To exclude certain types of CIs from the CI lists on the Incident, Problem, and Change forms, you can use the Principal CI class checkbox, which is available on the Class Manager module under Configuration1.
The Principal CI class checkbox allows you to specify which CI classes are considered as principal CIs, meaning they are the most relevant and important CIs for the business services and processes1. By default, only the CI classes that have this checkbox selected are displayed on the CI lists on the Incident, Problem, and Change forms2.
To use this feature, you need to navigate to the Class Manager module, select the CI class that you want to exclude or include, and check or uncheck the Principal CI class checkbox accordingly1. You can also use the Filter option to search for the CI classes by name or label1.
The other options are not recommended or valid ways to exclude certain types of CIs from the CI lists. Adding a Show field to the base cmdb table would require modifying the table schema and creating a reference qualifier, which could affect the performance and integrity of the CMDB3. Creating an Access control to hide the unnecessary CIs from the itil users would require defining the conditions and roles for the access rule, which could be complex and error-prone4. Making a show/hide UI action to show only the desired CIs to the itil users would require creating a custom script and UI element, which could be incompatible with the existing UI and functionality. Reference: 1: Principal configuration item classes 2: Configuration item lists 3: CMDB table schema 4: Access control rules : [UI actions]

According to the Create assets page, when you create an asset manually, the default state is In stock.
This means the asset is available in a stockroom and ready to be assigned or deployed.
The other states are not the default ones for a newly created asset. They are used for different scenarios, such as:
In use: The asset is assigned to a user or a location and is being used for business purposes.
Consumed: The asset is a consumable item that has been used up and cannot be reused.
On order: The asset is ordered from a vendor but has not been received yet. References:
Create assets
Asset and CI management

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. Reference:
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
5: IT Asset Management - ServiceNow