Wallfdorf Service Level Commitment
SLA for Initial Reaction Times
SLA for Corrective Action - 24 Hours
SLA for Corrective Action - 48 Hours
SLA for Corrective Action - 4 business days
SLA for Corrective Action - 6 business days
Walldorf Service Level Agreement
This document defines the standards that are applicable to the Walldorf support process in general. The terms “Company” and “Partner” used in this document shall correspond to the following terms defined under the Agreement and under this Attachment:
“Company” shall mean Walldorf and/ or its affiliated group companies.
“Partner” shall mean billing Partner as set forth under the Agreement.
1. Support Definitions
2. Definition of the Service Level Agreement
2.1 Qualified Response. Walldorf and Partner agree to provide each other with qualified responses to start the resolution process for a software error that caused such an Incident. This qualified response shall be provided within the SLA for Initial Reaction Time.
2.2 Availability for Technical Support and Escalation. Walldorf and Partner agree to provide each other availability of their support organizations and senior support management for an Escalated Situation twenty-four hours a day and seven days a week (24×7). An emergency and a Critical Incident are to be handled as an Escalated Situations.
2.3 Categorization of Incidents. Walldorf and Partner agree to apply the Walldorf standard definitions and categorizations for Incidents as the Walldorf Support Standards define them.
2.4 Handling Priority of Incidents.
- Walldorf and Partner agree that Partner shall not modify the priority of Incidents defined by customers. Partner may, however lower the priority of an Incident (i) once Company has provided Walldorf and/or the Partner with a workaround and (ii) if the Partner and Walldorf consent to such change of the Incident priority.
- Walldorf and Partner shall process Incidents by performing their respective support tasks.
- Walldorf and Partner shall use their best efforts to respond within the Processing Time for Corrective Action.
2.5 Measuring Processing Time and Incident Remedy.
- Walldorf will monitor the Processing Times for Initial Reaction and Corrective Action using the Walldorf Global Support Backbone.
- Processing Time shall start with receiving an Incident in the Walldorf Support portal. Each Company shall confirm the Incident receipt via the Walldorf Support portal within the SLA for Initial Reaction Time.
- Each Party will work on Incident Remedy in close and direct cooperation and keep the other Party updated on the progress of the Incident Remedy.
2.6 SLA for Corrective Action. The SLA for Corrective Action shall be deemed to be met if
- within the Processing Time after the Initial Reaction Time, the Partner was proposed an Incident Remedy, if a solution is provided system-based status confirmation will be provided via Walldorf Support Portal.), or
- the Partner has agreed to lower the priority of the Incident subject to the definition of Incident priority.
2.7 Action Plan. In case Walldorf and/or Partner provide an Action Plan, such Action Plan shall include a status report including:
- a description of the progress in Incident Remedy
- next steps planned by Walldorf and/or Partner
- cooperation actions required by Partner
- date and time for the next status update from Partner and/or Walldorf
- due dates for actions to be taken by Partner and or Walldorf, to the extent possible
- a list of responsible persons allocated by Partner and/or Walldorf to the Incident Remedy.
2.8 SLA on Processing Times, Definition of Priorities, and Response Times.
Walldorf and Partner agree to process Incidents within the time frames below (see table). The respective period starts with receiving an Incident by the Receiving Party (Walldorf Support Portal).
- Receiving Party shall give Walldorf feedback about the Incident receipt and processing within the initial response time below.
- Receiving Party shall use its best efforts to solve the Incident within the targeted solving period below.
- The Parties will monitor the response times.
2.9 “SLA for Initial Reaction Time”
- Receiving Party will give a qualified response within the defined time;
- For priority 1 Incidents the time is measured as real time, meaning 7*24 (seven by twenty-four) hours;
- For priority 2 Incidents the time is measured as Local Office Hours.
2.10 SLA for Corrective Action
- Receiving Party will provide an Incident Remedy within the specified time frame.
- The SLA for Corrective Action only refers to that part of the processing time, when the Incident is being processed by Walldorf (“Processing Time”). Processing Time is split into Initial Reaction Time and time for Corrective Action.
- The Processing Time does not include the time, when the Incident is on status “Customer Action” or “Walldorf Proposed Solution”, whereas (i) the status “Customer Action” means the Incident was handed over to Partner and (ii) the status “Walldorf Proposed Solution” means Walldorf or Partner has provided “Corrective Action”
- The SLA for Corrective Action shall be deemed to be met if, within 4 (four) hours of Processing Time: (i) Partner proposes an Incident Remedy in alignment with Walldorf, or (ii) Partner agrees to reduce the priority of the Incident.
2.11 Classification of Test Systems
Identical problem situations in test systems shall normally justify a priority that is one level lower than the equivalent priority in a Customer production system.
3. Definition of the Support Process
3.1 Walldorf will implement a queue for the Partner in the Walldorf Support Portal to allow for this usage scenario.
3.2 Partner Solution Manager will be the entry point for customers in addressing an Incident.
3.3 Partner Solution Manager will forward all Incidents to the Walldorf Support Portal for Incident Remedy.
3.4 Partner must clearly communicate the incident at the Walldorf Support Portal.
3.5 In case a Partner accidentally logs an incident related to another Software (for example SAP software) to the Walldorf support portal, Walldorf will close such tickets without any further investigation.
3.6 In case a Customer accidentally logs an incident related to another Software (for example SAP software) to the Walldorf support portal, Walldorf will close such tickets without any further investigation
Definition of Support Tasks
First Level Support tasks includes the following: Receive Incident messages from Partners or customers (comprehensive problem description at the Walldorf support portal)
- Translate non-English Incident messages into English
- Check the information provided by the Customer (including/correct missing/wrong information)
- Check the priority based on the given definition
- Check the specific ‘support component’ in Walldorf’s Knowledge Base
- Search in support database (e.g. Technical Notes and Walldorf’s Knowledge Base)
- Summarize status before forwarding to next level
Second Level Support is based on Walldorf Support Manager’s Diagnostics and focuses on the Root Cause Analysis including the following tasks:
- Verify Customers’ system customization
- Access Customer system, if necessary for problem analysis
- Analyze dumps, write traces and reproduce problems.
- Provide a workaround, if possible
- Create and modify Technical Notes by documenting the Incident Remedy
- Provide Partners with a solution or workaround for the Incident (Enhancement Packages)
- Provide Partners for Priority 1 Incidents with solution, workaround or Action Plan within SLA for Corrective Actions.
- Summarize status before forwarding to next support level
- Check if the Incident is definitely caused by Walldorf Software.
- Analyze in detail all recorded traces and error messages forwarded to Partners.
- Create knowledge articles for selected Incidents regarding:
a) the identified cause of the defect and the process of the Incident Remedy with all requested information and material (e.g. bug fixes, patches, description of workarounds)
- Specify the expected duration to fix the Incident by patches, bug fixes, or support packages.
- Recommendations for workarounds
- Access Customer systems via remote access
a) to analyze the Customer system regarding the Incident
b) to customize the systems by using workaround recommendations
c) to update the systems by using patches
- Provide Customers and/or Partners with code fixes for the Company’s Software