Asset life-cycle automation
-
- UpdatedAug 1, 2024
- 3 minutes to read
- Xanadu
- Hardware Asset Management
Automate the update of your asset records throughout its life cycle and remove the effort of manually maintaining asset accuracy.
You can create bulk stock orders for hardware assets for your stockrooms. You can specify the model and the exact quantity you need. After the item is procured or transferred, the workflow is complete.
You can also create disposal orders for hardware and consumable assets. This workflow guides you through five asset disposal tasks. These tasks involve the planning, scheduling, verification, departure, and the final confirmation of the disposed assets. Closing a task completes the task and creates the next task in the workflow.
For example, Verify is the first task in the asset disposal workflow. After you complete and close the Verify task, the Schedule pickup task is automatically created. This process continues until you close all the tasks required for disposing the asset. For information, see Hardware disposal order stages.
Asset tasks
Asset tasks are provided for deploy, replace or swap, or retirement operations for your assets. These tasks automatically update the CI/asset record on the completion of these operations.
- CI
- related asset record
- software allocations
- maintenance contracts
When an asset is retired or swapped via an incident, the Stockroom field is populated based on the location of the asset. If there isn't any stockroom in the location of the asset, then the Stockroom field isn't populated. However, if the asset location is supported by multiple stockrooms as part of service locations, then the Stockroom field is automatically populated with details of the supporting stockroom based on the priority. For more details on service locations, see Associate a stockroom with service locations.
Application | Asset Tasks |
---|---|
Incident Management |
Note: By default, asset action is required for closing incidents. However, from Hardware Asset Management version 11.0.2 onward, if you don’t want to enforce any asset action for the closure of an incident, you can set the value of the system property
sn_hamp.enable_asset_action_validation_incident to false. For more details see, the Not able to resolve incident or change request after installing HAMP - mandatory field Asset action [KB1695540] article in the Now Support Knowledge Base. |
Change Management |
Note: By default, asset action is required for closing change requests. However, from Hardware Asset Management version 11.0.2 onward, if you don’t want to enforce any asset action for the closure of a change request, you can set the value of the system property
sn_hamp.enable_asset_action_validation_change_request to false. For more details see, the Not able to resolve incident or change request after installing HAMP - mandatory field Asset action [KB1695540] article in the Now Support Knowledge Base. |
Field Service Management | Deploy |