Need to know benchmarks or std SLA for Service requests
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hello All,
We have close to 600 catalogs. And we dont have any SLA setup, we are want to implement SLAs and would like to take opinion on std SLAs to target initially. I am going with these values but if someone has guidance on how to go about it ? best oractice ?
SCTASK class | Applies to | Acknowledge / start | Fulfillment target | Minimum update |
Fully automated | System-executed SCTASK with no human step. | No time SLA. | No time SLA; monitored for success, failure and fallback (section 14). | System records start, outcome and closure. |
Semi-automated | Automation plus one human validation or action. | Human task accepted within 4 business hours. | Complete within 3 business days. | Each handoff and at least every 1 business day. |
Manual | Single team, single action, no dependency or third party (for example standard access, account or configuration change, peripheral from stock, hardware from stock). | Accepted within 4 business hours. | Complete within 4 business days. | Each handoff and at least every 2 business days. |
Manual – Complex | Multiple steps, several teams, a third-party or procurement dependency, planned lead time, validation or technical design; typically 2 to 3 weeks of fulfillment (for example New Corporate Software Request, Employee Onboarding items). | Accepted within 1 business day; plan, milestone SCTASKs and due date set within 2 business days. | Complete within 20 business days, measured on the longest dependent path of the RITM; each milestone SCTASK carries its own interim target. | Weekly requester-visible update, at each milestone and on any change. |
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
32m ago
In ServiceNow, an SLA (Service Level Agreement) represents a formal commitment agreed upon between a service provider and a customer. Therefore, SLAs should be created and applied only to services and fulfillment commitments that have been explicitly agreed upon with the customer.
If SLA agreements are already in place for fulfillment tasks (sc_task), I would recommend reaching out to the respective business stakeholders (catalog-wise) to obtain the following details:
- SLA Duration: Agreed fulfillment time.
- Start Condition: When the SLA should begin.
- Stop Condition: When the SLA should be completed.
- Pause Condition: Under what circumstances the SLA clock should be paused.
Once these details are confirmed and agreed upon by the business, you can proceed with creating the corresponding SLA definitions in ServiceNow.
Based on my understanding, SLA durations for sc_task cannot be standardized across all automated or semi-automated fulfillment tasks etc. This is because the underlying business logic, fulfillment processes, and dependencies vary from one catalog item to another. Therefore, SLA definitions should be determined individually based on the specific business requirements and agreed fulfillment timelines for each catalog item.
refer:
https://mynow.servicenow.com/now/best-practices/assets/service-level-management-process-workshop