Hi Sandeep,

I am sure there are multiple ways how to go about this and it will depend on your incident form. One option to consider so that you do not need to "hard-code" references to services and customers from start conditions of SLA Definitions (contract_sla) is to use "service offering" type of SLA Definitions - those where field Service commitment = true. With that approach instead of hard-coding in start condition you would utilize data from your service model to trigger respective measurement. From your example I understand that you want to achieve differentiated measurement for one service depending on user / customer. For that you can define your service with multiple child service offerings (Gold, Silver, ..) and link those offerings through respective commitments (service_commitment) to respective SLA Definitions. Depending on how you work with incident form, you can define in SLA Engine, whether these measurements from service offerings will be trigger based on service offering being selected in incident field Configuration Item or field Service Offering. Then if you decide e.g. for incident field Service Offering, you will want to ensure in incident form that incident field Service Offering is populated in line with your pre-defined subscriptions, i.e. if Customer A is subscribed to Offering A of Service A, the Offering A will populate in incident impacting Customer A and Service A. Upon selection of Offering A in field Service Offering, measurement from SLA Definition linked to Offering A through commitment will trigger automatically.

You will see, whether this idea is helpful for your case.

Many thanks,

Martin