Support

Definition of Incident and Request Priority

Technical support determines the resolution priority of incidents based on the following two parameters:

The Impact that the incident has on operations and processes that depend on the provided solution, as well as the potential damaging consequences it may cause, according to the table below:

Critical
Service / solution unavailable.
The incident prevents the use of critical processes of the solution, application, or infrastructure, obstructs the proper operation of the solution, affects a large number of users, and renders the provided solution/service non-operational.

High
Service / solution presents a malfunction in its core functionality but is not critical to the organization’s daily operations.
The incident causes disruption to the main functionality of the software but does not substantially interrupt the end user’s work.

Medium
Service / solution presents a malfunction in a specific functionality that is not critical to the organization’s daily operations.
The incident affects one or more processes of PPC, which are not urgent for the operation of the company. In other words, the incident blocks a capability of the software but does not substantially disrupt the end user’s work.

Low
General Assistance.
Refers to a minor or cosmetic issue, or an improvement that should be considered for a future release, or other explanatory questions regarding the use/operation of the system (“how-to” questions).

Definition of Impact

The Priority assigned to an incident or a service support request, and accordingly its routing, is determined according to the following table:

Critical

Priority 1

High

Priority 2

Medium

Priority 3

Low

Priority 4

Definition of Priority

Support Service Levels: The services provided, as well as the quality levels depending on the selected support package, are described indicatively in the following table:

Priority 1

09:30-17:30
Monday - Friday

Response TimeImmediate electronic or telephone response. Investigation actions begin within one (1) business hour.

Onsite Support Time (where required)Immediate response during business days and hours.

Within five (5) business hours, an action plan is provided for the development of an updated code patch or a bypass solution.

Resolution TimeResolution after the development and deployment of the patch or bypass (if required).

Priority 2

09:30-17:30
Monday - Friday

Response TimeImmediate electronic or telephone response. Investigation actions begin within four (4) business hours.

Onsite Support Time (where required)Immediate response during business days and hours.

Resolution TimeWithin twenty-four (24) business hours, an action plan is provided for a bypass solution. If resolution requires an updated code version (Patch), the issue will be resolved after the Patch is deployed.

Priority 3

09:30-17:30
Monday - Friday

Response TimeImmediate electronic or telephone response. Investigation actions begin within twenty-four (24) business hours.

Onsite Support Time (where required)Immediate response during business days and hours.

Resolution TimeThe possibility of correction or inclusion in the next Release will be considered.

Priority 4

09:30-17:30
Monday - Friday

Response TimeImmediate electronic or telephone response. Investigation actions begin within twenty-four (48) business hours.

Onsite Support Time (where required)Immediate response during business days and hours.

Resolution TimeThe possibility of correction or inclusion in the next Release will be considered.