Clarity Service Management

Expand all | Collapse all

Catalog SLA impact on Application

  • 1.  Catalog SLA impact on Application

    Posted 05-31-2018 08:36 AM

    Afternoon

    We are currently using Catalog 14.1.02 (implementation of Cum#5 is imminent within the next 3 days) installed on 2 servers (load-balanced and Cluster aware) with the data stored on a separate SQL2014 DB.

    The environment supports 8 catalogs with approximately 2000 service options (between 150 and 300 per catalog).  Each of these service options has between 1 and multiple tasks for fulfillment and each of these tasks has an associated SLA.

    It has now become necessary to add an SLA to every service option to manage the end to end fulfillment of the service option.

    Is there any manner of determining what the impact of this will be on the application. 

    Does anyone know of any type of calculation that can be performed to determine the impact of additional SLA's on the application. 

    Is there any documentation of what process runs that manages the SLA's, how it runs and how often it runs?.

     

    Regards

    Chris Saunders



  • 2.  Re: Catalog SLA impact on Application

    Posted 06-05-2018 08:38 AM

    Good Afternoon Christian.

     

    Researching for this, for you, did not result in any information regarding your question.

    Perhaps, someone else in the community, does have some information for you from practice.

     

    Thanks and kind regards, Louis.