- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi, We receive ticket mentioning the C or D drive failure or any drive issue as incidents and sometimes we end up ordering a new drive - in these cases, the SLA gets breached as AWAITING VENDOR on HOLD state doesnt pause the SLA timer. How can this scenario be handled? Thanks.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @rdevi
As per my knowledge , OOB, ServiceNow only pauses the SLA when an Incident is On Hold with the reason Awaiting Caller.
In your case , If your organization's business agreement allows the resolution clock to stop while waiting for hardware failure, then only you can explicitly update the SLA definition to add another pause condition .
- State is On Hold AND
- On Hold Reason is Awaiting Vendor
I have observed the following approach in a couple of client projects where the business does not agree to SLA updates.
In such cases, the BAU team obtains the incident requester's consent, raises a Problem record to track the underlying issue, provides regular progress updates to the requester, update Incident's work note with Problem ticket number and closes the Incident in parallel while the Problem remains open for further investigation and resolution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @rdevi
You need to look into the service level agreement definition according to how they are configured and according to business agreement.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @rdevi
As per my knowledge , OOB, ServiceNow only pauses the SLA when an Incident is On Hold with the reason Awaiting Caller.
In your case , If your organization's business agreement allows the resolution clock to stop while waiting for hardware failure, then only you can explicitly update the SLA definition to add another pause condition .
- State is On Hold AND
- On Hold Reason is Awaiting Vendor
I have observed the following approach in a couple of client projects where the business does not agree to SLA updates.
In such cases, the BAU team obtains the incident requester's consent, raises a Problem record to track the underlying issue, provides regular progress updates to the requester, update Incident's work note with Problem ticket number and closes the Incident in parallel while the Problem remains open for further investigation and resolution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi Tanushree, thanks for the suggestions. Incase of SLA definition, I could find many defined. How to check what is already defined and how to figure out if awaiting vendor is already included or not. I am quite not sure how SLA definition works 😞
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hi @rdevi
You need to look into the service level agreement definition according to how they are configured and according to business agreement.