Walldorf Service Level Agreement

Effective starting: January 4, 2021

 

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.

Support Definitions

  1. General Definitions

1.1     “Action Plan” shall mean a document or report created for the Partner by the Party that is processing an Incident to describe the progress of a Corrective Action for an Incident including (i) description of next steps to be taken, by Walldorf, Partner or Partner’s end-customer, (ii) results of actions taken to date, and (iii) date and time of next status update and a schedule of future activities to reach an Incident Remedy.

1.2     “Corrective Action” shall mean an action that will provide Partner with (i) Incident Remedy or at least (ii) an Action Plan for the Parties involved in the Incident Remedy process.

1.3     “Escalated Situation” shall mean any highly critical situation of the Partner that has very serious consequences for normal business transactions for the Partner provided both parties of this Appendix agree that the resolution of such situation requires additional attention by one or both Parties.

1.4     “Local Office Hours” shall mean – as applicable – Walldorf’s applicable regular working hours (8.00 a.m. to 6.00 p.m.) during regular working days, in accordance with the corresponding public holidays.

1.5     “Processing Time” shall mean the time period during which a party works on Incident Remedy for a single Incident. For priority 1 Incidents the time is measured as real time, meaning 24×7 hours. For all other Incident priorities the time is measured in Local Office Hours. Processing Time does not include the time, when the Incident has the status “Customer Action” or “Walldorf Proposed Solution” or when it has the status “Partner Action”.

1.6     “Release to Customer (RTC)” shall mean the date that marks the initial availability of a new release of Walldorf Software to Partners and the beginning of the restricted shipment phase.

1.7     “Service Level Agreement” or “SLA” shall mean the service level in accordance with definitions, procedures, and schedules as they are defined in Section 2 of this Schedule.

1.8     “Technical Note” shall mean the accurate and complete description of any error or Incident and of corrective measures and/or correction instructions that need to be applied by customers to remedy or prevent an Incident

  1. Definition of the Service Level Agreement

2.1     Qualified Response. Walldorf and Partner agree to provide each other with qualified responses to start with the resolution process for a software error that caused such 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 Incident and a Critical Incident are to be handled as an Escalated Situation.

2.3     Categorization of Incidents. Walldorf and Partner agree to apply the Walldorf standard definitions and categorizations for Incidents as they are defined by the Walldorf Support Standards.

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 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 by means of the Walldorf Global Support Backbone.
  • Processing Time shall start with the receipt of an Incident in Walldorf Support portal. Each Company shall confirm the Incident receipt via 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, (i) within the Processing Time subsequent to 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 if (ii) 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 the receipt of 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 set forth below.
  • Receiving Party shall use best efforts to solve the Incident within the targeted solving period set forth below.
  • The Parties will monitor the response times.

 

Priority of Customer Incident Description

 

SLA for Initial
Reaction Times
SLA for Corrective Action SLA for Response Times
1

Very high

An Incident is properly ascribed priority 1 if the Incident has very serious consequences for normal business transactions and urgent, business critical work cannot be performed. The Incident requires immediate processing because the malfunction can cause serious losses.

This is generally caused by the following circumstances:

·       Complete system outage

·       Malfunctions of central Walldorf Software functions in the production system

·       Top-Issues

4 hour

(7*24h)

24 hours

(7*24h)

SLA for Corrective Action
2

High

An Incident is properly ascribed priority 2 if normal business transactions are seriously affected and necessary tasks cannot be performed. This is caused by incorrect or inoperable functions in the Walldorf systems and/or Company Software that are required to perform such transactions and/or tasks. The Incident requires immediate processing because the malfunction can seriously disrupt the entire productive business flow. 8 hours

(Local Office Hours)

48 hours

(Local Office Hours)

4 business days

(Local Office Hours)

3

Medium

An Incident is properly ascribed priority 3 if normal business transactions are affected. The Incident is caused by incorrect or inoperable functions in the Walldorf Software. No 8 business days

(Local Office Hours)

4

Low

An Incident is properly ascribed priority 4 if the Incident has few or no effects on normal business transactions. The problem is caused by incorrect or inoperable functions in the Walldorf Software that are not required daily, or are rarely used. No 16 business days

(Local Office Hours)

 

2.9     “SLA for Initial Reaction Time”. SLA for Initial Reaction Time shall mean:

  1. Receiving Party will give a qualified response within the defined time;
  2. For priority 1 Incidents the time is measured as real time, meaning 7*24 (seven by twenty-four) hours;
  3. For priority 2 Incidents the time is measured as Local Office Hours.

2.10    SLA for Corrective Action. “SLA for Corrective Action” shall mean:

  1. Receiving Party will provide an Incident Remedy within the specified time frame.
  2. 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.
  3. 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”
  4. 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.

  1. Definition of the Support Process

3.1     Walldorf will implement in the Walldorf Support Portal a queue for the Partner 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

Support Tasks of First-Level Support

First Level Support includes Partner and Walldorf Support desk as follows:

  1. Receive Incident messages from Partners or customers – comprehensive problem description at the Walldorf support portal.
  2. Translate non-English Incident messages into English
  3. Check the information provided by the Customer (including/correct missing/wrong information)
  4. Check the priority based on the given definition
  5. Check the specific ‘support component’ in Walldorf’s Knowledge Base
  6. Search in support database (e.g. Technical Notes and Walldorf’s Knowledge Base)
  7. Summarize status before forwarding to next level
Support Tasks of Second-Level Support

Second Level Support is based on Walldorf Support Manager’s Diagnostics and focuses on the Root Cause Analysis including the following tasks:

  1. Verify Customers’ system customization
  2. Access Customer system, if necessary for problem analysis
  3. Analyze dumps, write traces and reproduce problems.
  4. Provide a workaround, if possible
  5. Create and modify Technical Notes by documenting the Incident Remedy
  6. Provide Partners with a solution or workaround for the Incident (Enhancement Packages)
  7. Provide Partners for Priority 1 Incidents with solution, workaround or Action Plan within SLA for Corrective Actions.
  8. Summarize status before forwarding to next support level
Support Tasks of Development Support (or Third-Level Support)
  • 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