Paul Taylor Posted November 4, 2021 Share Posted November 4, 2021 I am looking to create an SLA for a very specific scenario. We have a 3rd party off shore team who provides support for our SAP environment, I am looking to create an SLA to mark their response and resolution times. The SLA is created based based on the following rules: This is because we want to manage timer only when the off shore team take owndership. The part I am unsure on is how to invoke the 'start' timers, because the ticket could get escalated to the off shore team at any stage of the lifecycle of the ticket, so what I would usually do which is to add the start response and start resolve timers early in the workflow (I assume) doesn't apply. Any direction greatly received. Paul Link to comment Share on other sites More sharing options...
Paul Taylor Posted November 8, 2021 Author Share Posted November 8, 2021 Bumping this thread.. Link to comment Share on other sites More sharing options...
Steve Giller Posted November 8, 2021 Share Posted November 8, 2021 I think this would be far more efficiently managed by creating a linked request at the point where it's handed off to the offshore team. The linked request would have its own timers and SLA, and could "hand control" back to the original request when complete, or close the original as required. Link to comment Share on other sites More sharing options...
Victor Posted November 8, 2021 Share Posted November 8, 2021 On 11/4/2021 at 1:22 PM, Paul Taylor said: The part I am unsure on is how to invoke the 'start' timers Timers are started using the workflow via the Start Timer nodes (stopped same way). On 11/4/2021 at 1:22 PM, Paul Taylor said: the ticket could get escalated to the off shore team at any stage of the lifecycle of the ticket, so what I would usually do which is to add the start response and start resolve timers early in the workflow (I assume) doesn't apply What you are after here is some form of OLA (sort of). Which Service Manager does not have, I'm afraid... @Steve Giller suggestion for a linked request seems reasonable I think... 1 Link to comment Share on other sites More sharing options...
HGrigsby Posted January 17, 2022 Share Posted January 17, 2022 Thanks for the suggestion @Steve Giller and explanation @Victor It is exactly what we want to do - it is shame it doesn't have some sort of OLA for this type of support arrangement, but at least I know now. Helen Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 26, 2022 Share Posted January 26, 2022 @HGrigsby We had hopped to use Supplier manager to manage OLA's, but at the moment you can only start and stop a supplier 'Event' not pause it. We raised this as enhancement request. I find the post and add it to this one for reference. Cheers Martyn 1 Link to comment Share on other sites More sharing options...
Martyn Houghton Posted January 26, 2022 Share Posted January 26, 2022 @HGrigsby Link for the Supplier Manager enhancement request. Cheers Martyn 1 Link to comment Share on other sites More sharing options...
HGrigsby Posted May 19, 2022 Share Posted May 19, 2022 I am back to this topic again! I've ended up having to opt for @Steve Giller's suggestion of creating a new incident from the initial one to assign to the 3rd party team to allow their SLA to run. Has anyone found a neat way of doing this? I have created an autotask to create a copy of the ticket and assign it to the 3rd party and set the SLA and close the original which looks (sort of) OK. Is there a way to open the new linked ticket other than clicking on it? I'd like the new one to be the one on the screen not the original. thanks Helen Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now