This documentation supports the 9.1 version of Remedy IT Service Management Suite.

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

Service Catalog and Request Management use case

Each use case has a Universal Modeling Language (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:

Symbol

Meaning

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 goals of this use case are to illustrate how:

  • Self service initiates a service request through the Service Catalog
  • BMC Service Request Management automates the connection of service requests to back-office fulfillment

This use case has the following steps:

  1. The end user accesses self service through the BMC Service Request Management interface. The user browses the service catalog for service offerings that can be requested. The user can also access information from the knowledge database.
  2. After the user selects a service request offering from the service catalog, the interaction workflow steps the user through a series of panels or questions that retrieve more information from the user.
  3. Advanced interface forms (AIFs) can be configured by administrators to retrieve information from integrated data sources.
  4. After all user information has been collected, the service request is submitted and the service fulfillment engine starts the processing. BMC Service Request Management can be configured to connect to a variety of back-end fulfillment systems through its fulfillment engine. For more details, see  BMC Service Request Management architecture .
  5. BMC Service Request Management workflow invokes and coordinates back-end processes such as the Incident Management feature of BMC Service Desk, BMC Change Management, and TrueSight Orchestration workflow, which may integrate with other applications such as BMC BladeLogic.
  6. The end user monitors the status of the overall service request through the self service interface. BMC Service Level Management also monitors the status of the overall service request.
  7. When all back-end processes complete their activities, the service fulfillment completes the service request.

Related Topic

Integration between SRM and BAO

Was this page helpful? Yes No Submitting... Thank you

Comments

  1. Ariel Manka

    Hi,

    Could you please provide directions to documentation for integration between SRM and BAO?

     

    Thanks,

    Ariel

    Mar 28, 2017 03:25
    1. Amol Ketkar

      Hello Ariel Manka,

      Thank you for pointing out. I have updated the document.

      Kindly refer to related topic.

      Regards,

      Amol 


      Aug 20, 2018 01:46
  2. Jaime Soto

    Why is Work Order Management not included in this diagram as a fulfillment request?

    Nov 15, 2017 06:23
    1. Jyoti Nerkar

      Hi Jaime,


      Apologies for a delayed response.

      I have updated step#5 and included a link to the topic that covers SRM architecture.

      Regards,

      Jyoti

      Sep 10, 2019 04:16