Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated the digi-accordion macro with the following parameter(s): []

SummitAI Service Management Help

Panel
borderColor#72B0DE
bgColor#F0F0F0
Expand
titleIncident Management

Incident Management

Expand
titleConcepts

Audit Flow

Audit Log

Auto Complete Assistance

Customer Satisfaction Survey (CSAT)

First Call Resolution (FCR)

Incident Vs. Problem

Incident Status

Major Incidents

Monitoring SLA

Parent and Child Incidents

Parent and Child Relationship

Remote Desktop

Response Time Vs. Resolution Time

SLA, OLA, and UC

Templates and Rules

Work Orders

Expand
titleEnd Users

End Users

End User Dashboard

Logging Incidents

Viewing My Incidents List

Viewing/Updating My Incidents

Chatting with Analysts

Survey

Logging Incident for an Asset

Expand
titleAnalysts

Analyst Dashboard

Logging Incidents for Users

Viewing and Updating My Workgroup Incidents

Viewing and Updating Incident Details

Sending E-mails

Remote Desktop Sharing

Feedback Moderation

Managing My Incidents

Work Orders

Creating Work Orders

Viewing and Updating Work Orders

Expand
titleAdministrators

Administrators

Configuring Incident Management Module

Configuring Custom Fields for Incident Management

Configuring Category Incident Management

Configuring Closure Codes

Configuring Classification

Configuring Priority

Configuring Impact

Configuring Urgency

Configuring SLA Matrix

Configuring SLA Matrix By CI

Configuring Resolution Codes

Configuring ETR E-mail Notifications

Configuring Incident E-mail Notifications

Configuring Auto Work Orders

Configuring SLA Service Windows

Configuring Workgroup SLA Window

Configuring Pending Reasons

Configuring Priority Matrix

Configuring User Types

Configuring Checklist

Configuring Major Incidents

Configuring Cost

Configuring Rules

Configuring Information Ticker

Configuring SMS Notification

Configuring Voice Call Notifications

Configuring Log Incident Page

Mapping Standard Operational Procedures

Configuring Feedback

Configuring End User Incident Details Page

Configuring Incident Evaluator

TFS-SUMMIT Integration

Configuring TFS Project

Configuring Work Item Fields

Mapping Field Values

Configuring Mapping Profile

Configuring TFS Profile Mapping

Expand
titleReports

Viewing Reports


Scroll export button
scopecurrent
template-idc9a14909-8f27-452d-bca0-164bee1a9265
captionDownload this Page
add-onScroll PDF Exporter

Definitions - SLA, OLA, and UC

Service Level Agreement  (SLA): An SLA is the agreement between an IT Service Provider and a Customer. The SLA describes the IT Services, documents Service Level Targets, and specifies the responsibilities of the IT Service Provider and the Customer. A single SLA may cover multiple IT Services or multiple Customers. 

Operational Level Agreement (OLA): An Operational Level Agreement (OLA) is a contract defined between the various departments within an organization to ensure on-time delivery of Services to the Customer. OLAs are designed to address and solve the problem of IT silos by setting forth a specific set of criteria and defining the specific set of IT Services that each department is responsible for.

Applicability and uses:
  • Applicable between Incident and Work Order, and Workgroups within an Incident.
  • Applicable for Auto created Work Orders (only for the Work Orders created while Incidents are logged and not applicable for sequential Work Orders).
  • If the OLA is within an Incident, it corresponds to the Transfer Time. 

Example: OLA between Workgroup 1 and Workgroup 2 is 30 min. An Incident is logged at 10 AM and in the que of Workgroup 1. If it is transferred to Workgroup 2 before 10:30 AM, the OLA is considered as met. If transferred after 10:30 AM, the OLA is considered as not met.

  • If the OLA  is made between the Incident and Work Order, it corresponds to Resolution Time. 

Example: OLA between Workgroup 1 and Workgroup 2 is 30 min. Incident logged at 10 AM and in the que of Workgroup 1. There is a Work Order created for this incident and is in the que of Workgroup 2. If the Work order is resolved by 10:30 AM, the OLA is considered as met. If resolved after 10:30 AM, OLA is considered as not met. 

Underpinning Contract (UC): The Underpinning Contract (UC) is the agreement between an IT Service Provider and a Third Party (Vendor). The Third Party provides Goods or Services that support delivery of an IT Service to a Customer. The Underpinning Contract defines targets and responsibilities that are required to meet agreed Service Level Targets defined in an SLA.

Advantages

  • Documented SLA, OLA, and UC ensures no miscommunication between the Customer, Vendor, and Departments.
  • Better understanding of the Services provided by the Vendor.
  • A document to refer back to in case of any misunderstanding.
  • All these 3 documents should be in sync with each other to ensure all the service levels are met.


Scroll ignore
scroll-pdftrue
scroll-officetrue
scroll-chmtrue
scroll-docbooktrue
scroll-eclipsehelptrue
scroll-epubtrue
scroll-htmltrue
1

| |