1 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 1 SLA and Escalation Matrix Dec 15, 2014.

Slides:



Advertisements
Similar presentations
Slide 1 Incident Management. Slide 2 Goal - Primary Objective To restore normal service operation as quickly as possible with minimum disruption to the.
Advertisements

Confidential Phone Internet CustomerHelp Desk Support Model for Sabre Qik Customers V 1.0 Agency eServices.
© 2006 LaBounty & Associates, Inc. Working With Support Teams Beyond the Service Desk Char LaBounty LaBounty & Associates, Inc.
SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.
REBA Application Walkthrough for Service Providers Audio is via conference call at code Closed Captioning available at
IGrafx – General Terms of Use. Trial Software Licenses For test purposes only Not for normal business use Training based on the trial software is also.
Chapter 4 Quality Assurance in Context
Improving the R&D/Support Relationship Karen Herzog Vice President, Support Services McKesson SCP Showcase November 10-11, 2004.
1 Schedule Risk Assessment (SRA) Overview July 2013 NAVY CEVM.
Prepared By: Certified Compliance Solutions, Inc. August 2012
Jan McAdam Nikolina Kilibarda. Swinburne 2015 Vision  Entrepreneurial in their work  International in their outlook  Intersectoral in their approach.
Manage Quality
Validating and Improving Test-Case Effectiveness Author: Yuri Chernak Presenter: Lam, Man Tat.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Effort in hours Duration Over Weeks Or Months Inception Launch Web Lifecycle Methodology Maintenance Phases Copyright Wonderlane Studios.
Incident Management ISD Division Office of State Finance.
Problem Management ISD Division Office of State Finance.
Service Options: Hardware Warranty, Software Maintenance and Support.
IGrafx – General Terms of Use. Trial Software Licenses For test purposes only Not for normal business use Training based on the trial software is also.
Working with the LiveOps CSC (Customer Support Center)
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Working with the LiveOps Help Desk
Remedy – Customer Portal Fiona Gregory McKesson CRM 1.
IT Governance Purpose: Information technology is a catalyst for productivity, creativity and community that enhances learning opportunities in an environment.
Event Management & ITIL V3
ITPD PRODUCTION SUPPORT PROCESS OCTOBER 8, /23/2015 Guiding Principles 1.Resolve production issues in a timely and effective manner 2.Manage.
© Mahindra Satyam 2009 Configuration Management QMS Training.
Managing Change 1. Why Do Requirements Change?  External Factors – those change agents over which the project team has little or no control.  Internal.
Lost In SAP Support Space 2014 Kristen Scheffler & Christopher Vozella - SAP Americas SESSION CODE: 0402.
Service Level Management SLM Concepts Explained Copyright 2002 Easytec Solutions.
Working with the LiveOps Help Desk
Request for Service (RFS) Process and Metrics Update June 24, 2008.
EMI INFSO-RI SA1 Session Report Francesco Giacomini (INFN) EMI Kick-off Meeting CERN, May 2010.
August 25, 2008 TPTF Nodal Status Report: Integrated Schedule Update Change Control Update Adam Martinez Troy Anderson.
Working with the LiveOps Help Desk. 2© 2015 LiveOps, Inc. | Confidential Liveops Customer Support Center Overview Global Operations Management Team Support.
REBA-TPCA Application Walkthrough for School Districts Audio is via conference call at code
1 ERCOT Retail Release Overview. 2 How Are Changes Managed? Retail Testing Business Teams Development Teams Release Management Management of: Migration.
JD Edwards Support & Tools Gillian Boshell Product Service Advisor, Oracle Australia.
RMSUpdate May 5, 2005 Retail Market Subcommittee Update to TAC.
Lead from the front Texas Nodal 1 Reduction of MMS Vendor Effort for TPTF January 8, 2008 Murray Nixon Sai Moorty.
© 2015 CenturyLink, Inc. All Rights Reserved. Wholesale Service Management Repair Guidelines 1 CenturyLink Operational Information-For use by CenturyLink.
HDPlus Help Desk Management HDPlus, Inc. Landline: Fax Cellphone:
COTS Software Licensing Service Level Agreement Considerations 2014.
IEEE /r5 Submission November 2008 John Notor, Cadence Design Systems, Inc.Slide 1 IEEE IMT-Advanced Review Process Date:
Lead from the front Texas Nodal 1 Registration Market Call Nov 21, 2008.
Service Level Agreement Considerations
Improving The Customer Experience Our Commitment To Operational Excellence Gita MacLean, May 21 st /2015.
SLAs with Software Provider. Scope “…declare the rights and responsibilities between EGI.eu and the Software Provider for a particular component.” Which.
Introduction to CAST Technical Support
2011 Prioritization Update to Market Subcommittees
AgilizTech Support Desk Overview
Bitcoin Mining Script | Bitcoin Trading Script | Bitcoin Cloud Mining Script
Johanna Rothman Know What “Done” Means Chapter 11
Introduction to CAST Technical Support
The following is intended to outline our general product direction
Yearly Maintenance Process (for existing messages)
Amendment Invoice Task Force Progress Report
Amendment Invoice Task Force Progress Report
IEEE IMT-Advanced Review Process
All about the customer - a new way of selling, a new way of caring
ISSUE MANAGEMENT PROCESS MONTH DAY, YEAR
Executive Project Kickoff
and Forecasting Resources
Presentation transcript:

1 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 1 SLA and Escalation Matrix Dec 15, 2014

2 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 2 Revision History VersionDate Changes / Updates Ver 118-Jan-12 Base version Ver 24-Apr-12 Added Release Support Availability Matrix Ver 310-Dec-12 Added Support Hours. Updated SLA notes. Ver 43-Sep-13 Updated the Release support availability for 4.1. Ver 5 15-Dec-14 Updated the Release support availability for 5.5, 5.6 and 6.0.

3 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 3 Index  Severity Levels  SLA Matrix  Things to Note  Support Hours  Escalation Matrix  Release Support Availability

4 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 4 Severity Levels

5 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 5 SLA Matrix *Kony will make every effort to achieve the target resolution time, however, the time needed to provide a correction may vary depending on the amount of coding and testing needed for the correction. Resolution and Target Resolution times are based on India working days (excluding holidays). Customer will ensure that a resource is assigned to work with Kony support team to provide information or verification on an ongoing basis, until the issue is resolved. In the event Kony’s response time to an Error is negatively impacted due to Customer’s or a Third-Party’s delayed response to Kony's request for additional information to correct an Error, the response times provided above will be extended by an amount of time proportionate to such delay. Both parties may agree that due to technical dependencies and other factors, certain Errors classified as Medium and Low may be resolved in the next release rather than in a production patch. Customer acknowledges that Kony does not and cannot guarantee that all Errors can or will be corrected. In the event an Error is caused by the underlying manufacturer’s Software Development Kits “SDK” and Kony needs support from Native SDK (for e.g. RIM, Apple) then this issue is driven by the timelines and SLAs the device manufacturer commits to.

6 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 6 Things to note The Severity set for the reported defect/issues is a with respect to the Product and will be purely driven by the SLA definition. The Support teams will review the issue reported by the user and assign the correct severity based on the severity definitions. The above matrix is only for the defects reported on the Kony Product. This does not apply to Feature requests / enhancements required by the customers. The New Features requested by customers should follow the Feature Request Process. New Features requested in the Defect reporting process will be treated as a Low severity defect with no SLA impact. Please note that only “Production” issues can be classified as “Critical”. All issues / defects during the course of application development will be classified as High/Medium/Low severity based on the severity definition. Sample Application is mandatory for all valid defects. A defect without a sample application will not be accepted by the support team. This does not apply to questions / queries.

7 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 7 Support Hours TimeDay ISTMondayTuesdayWednesdayThursdayFridaySaturdaySunday 0:00No SupportSupport No Support 1:00No SupportSupport No Support 2:00No SupportSupport No Support 3:00No SupportSupport No Support 4:00No SupportSupport No Support 5:00No Support 6:00No Support 7:00No Support 8:00No Support 9:00Support No Support 10:00Support No Support 11:00Support No Support 12:00Support No Support 13:00Support No Support 14:00Support No Support 15:00Support No Support 16:00Support No Support 17:00Support No Support 18:00Support No Support 19:00Support No Support 20:00Support No Support 21:00Support No Support 22:00Support No Support 23:00Support No Support 0:00Support No Support NOTE: Time is mentioned in IST (Indian Standard time) NOTE: Support for Critical Production issues is available 24*7.

8 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 8 Escalation Matrix NOTE: Please keep your Kony Account manager in loop on all escalation mails. NOTE: All escalation communication should be initiated on mail, followed by phone call - if required. Escalation LevelDesignation Desk Phone #How / When to Escalate 1 L-1 Product Support Request update on Defect 2Team Request update on Defect and/or esclate if no information is available from L-1 Team Escalate if No information is available from L-1 Team / Tech lead or if the information received does not meet expectation. 4 Head - Product Final level of escalation when no satisfactory information is available from other levels of escalation.

9 Copyright © 2011 Kony Solutions, Inc. CONFIDENTIAL 9 Release Support Availability Platform Release Release DateEOL Standard EOL Extended Dec-141-Jan-17 1-Jan May-141-Jun-16 1-Jun Dec-131-Jan-16 1-Jan Aug-121-Sept-14 1-Jan-16* Feb-121-Mar-14 1-Jan-16* *Additional EOL Extended duration provided for 4.1 and 5.0 to allow customers 12 month duration for upgrading following initial notification.