This documentation applies to the 8.1 version of Remedy IT Service Management Suite, which is in "End of Version Support." You will not be able to leave comments.

To view the latest version, select the version from the Product version menu.

Service Asset Lifecycle use case

Each use case has a UML robustness diagram associated with it. A robustness diagram depicts the core components of a system and how the components communicate or collaborate with one another to satisfy a use case. Arrows between the components indicate the flow of information between the components.

The following symbols are used:



Actor — User role that interacts with a component in the system

Boundary — Component that represents an interface with which Actors interact

Entity — Domain objects within the system that typically present a persisted state of that object

Control — Components that connect Boundary and Entity components and implement some logic to manage the interaction between them

The goal of the Service Asset Lifecycle use case is to illustrate how procurement requests are initiated and managed through fulfillment.

This use case has the following steps:

  1. The configuration administrator (asset manager) defines standard configurations for issued equipment. For example, the configuration administrator defines a "Standard Sales Laptop Configuration" as being comprised of a laptop, power supply, case, and external hard drive.
  2. A license has been set up for Microsoft Project. Copies of the license are available from the inventory. Software License Management can be employed to ensure software license compliance.
  3. The end user accesses self service through the BMC Service Request Management interface and requests a Standard Sales Laptop Configuration pack and a copy of Microsoft Project.
  4. BMC Service Request Management creates the purchase request and reserves a copy of Microsoft Project from the pool of available licenses.
  5. The configuration administrator reviews the purchase request and creates a purchase order for the laptop and accessories.
  6. On receipt of the purchase, the configuration administrator logs into the Receiving Console and marks the items as received. BMC Asset Management automatically generates a new CI for the laptop request.
  7. The configuration administrator creates a change request for the build and handover of the laptop and the installation of Microsoft Project, which is completed once the user's laptop is installed.
  8. After the laptop is installed, BMC BladeLogic Client Automation or a third-party discovery tool (like Microsoft System Center Configuration Manager) enriches BMC Atrium CMDB with additional details concerning the new laptop.

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.