Overview

Service Terms

Master Services Agreement (MSA)

Service Levels, Software Maintenance, and Support Services

Software Limitations and API Terms of Use

Terms for Authorized Users

EU Data Regulations

Global Privacy Hub

Data Processing Agreement (DPA)

Privacy Policy

Technical and Organizational Security Measures (TOM)

Service Levels, Software Maintenance, and Support Services

Includes establishing contact information, allocation of case number and instigation of remedial action via the Service Management System.

Customer shall classify the Incident at this time into a Severity Level as defined below and Partium shall review the initial classification.
Includes diagnosis and triage of the reported problem and gathering information covering a clear description of the problem, associated log files and traces, configuration files and any additional data helpful to identify and narrow down the problem.

If questions arise during this phase that cannot be answered by analyzing the Software, Partium support engineers will contact the reporting person via phone (if number is made available at the time of reporting the issue) or the Service Management System.
Includes investigation into the reported problem through analysis of information provided during Phase 2, as well as construction of a remedial action plan and regular customer updates on the proposed fix via phone (if number is made available at the time of reporting the issue) or the Service Management System.
1 - Critical
Severe
Customer cannot use the Software or there is a critical impact on the Customer’s operations which requires an immediate solution.
2 - High
Major
Customer can use the Software, but an important function is not available, or Customer’s operations are severely impacted for the majority of users of the Customer’s organization.
3 - Medium
Medium
Customer can use the Software with some functional restrictions, and such restrictions do not have a Severe or Major business impact on the Customer’s operations.
4 - Low
Limited
A non-critical component of the Software is malfunctioning, or the Documentation contains errors, causing minimal impact, or a non-technical request is made. The Customer may be able to circumvent the problem.
1
Within 2 Response Hours
Continued effort until resolution with 4 TSH for workaround and 8 TSH for fix
2
2 Response Hours
8 TSH for fix
3
4 Response Hours
24 TSH for fix
4
Next day’s Response Hours
Addressed in next release