Asset Management Integrations

The Asset Management process app is configured to work with the Service Requests and Change Management Systems (CMS) process apps.

About the Service Requests Integration

Once the Service Requests integration is enabled, request fulfillers can:
  • Check inventory for an asset when a request is in classification. If an appropriate asset is found in inventory, the asset can be linked to the request and is automatically assigned to the user.
  • Use the User Assets tab on service requests to see assets currently assigned to requesters.
  • Create new assets from requests that are assigned to a fulfiller. To do this, use the "Purchase Asset" transition.
  • Link existing assets to requests that are assigned to a fulfiller.

    In case of errors or to fix items that were incorrectly linked together, use the "Unlink Asset" transition to remove the links between assets and active requests.

  • Be assured that service requests are automatically resolved once assets are assigned to the requestor.

By default, assets created from service requests are added to the "Planning" state so that they can move through the Asset Management approval process. Your administrator can modify the integration so that approvals are handled in the Service Request process app.

For setup and configuration details, refer to Enabling the Service Requests Integration with Asset Management.

About the Configuration Management System (CMS) Integration

SSM is configured to ensure data integrity between your configuration items (CIs) and your financial assets.

Once assets are retired, the related CIs automatically become inactive.

From the Configuration Management System process app:

Configuration analysts can use the "Add Asset to AM" transition to create a financial asset.

The "Add Asset to AM" transition is available in the "Active" or "Audit" states from CIs of these types:
  • Software
  • Hardware
  • Laptop
  • Workstation

Relevant information is posted between the CI and the asset.

You can use this transition on individual CIs or run the "Active Configuration Items Without an Asset" reports to add multiple assets at once. For details, refer to Importing Assets.

Assets created from CIs are added to the "Verify Import" state in the Asset Management process app. From here, use the "Verify" transition to move assets to the "Acquired" state so they can be assigned to employees.

From Asset Management process app:

Asset managers can use the "Add to CMDB" transition to add financial assets to the configuration management database. Posted assets are added to the "Classification" state and must be activated to become CIs. Relevant information is posted between the asset and the CI.
Note: Typically, CIs cannot have duplicate names. This restriction does not apply to CIs created from assets, however.

Asset managers can also use the "Select Configuration Item" transition to link an asset to an active CI.

These transitions are available from the "Acquired," "Assigned," "IT Inventory," "Audit," "Missing," and "Verify Import" states.

In case of errors or to fix items that were incorrectly linked together, administrators can use the "Unlink Configuration Item" transition to remove the links between assets and CIs.