Technical appendix & Service commitments
Technical appendix & Service commitments
1. PRELIMINARY DEFINITIONS
“Analysis”: the action of providing a response to a Client’s request. The nature of the response depends on the type of request:
Assistance request: the response consists of providing the Client with the necessary information for the correct use of the Software.
Specific request: the response consists of providing the Client with a proposal including a quotation and an implementation schedule for the request.
Non-critical incidents: the response indicates to the Client whether the reported incident is (1) due to the Software (anomaly), (2) due to incorrect use of the Software, or (3) unrelated to the Software.
In case (1), the response provided consists of giving the Client the anomaly number and its correction schedule.
In case (2), the incident is reclassified as an assistance request and processed as such.
In case (3), the incident is not the responsibility of THALES SIX GTS France, and the call is reclassified as an assistance request. The Client may, if necessary, submit a specific assistance request for this issue.
Critical incident: the resolution must allow the Client to be unblocked if the incident falls under cases (1) or (2) above.
In case (1), the resolution may be the delivery of a Software version correcting the identified blocking anomaly OR a proposal for a workaround solution allowing the incident to be reclassified as “non-critical” OR any other intervention by THALES SIX GTS France allowing the incident to be reclassified as “non-critical”.
“Anomaly”: a repetitive and reproducible difficulty with the Software’s functioning that requires correction in the Software’s source code to be resolved.
The anomaly is classified by its criticality:
Blocking: refers to any malfunctions making it impossible to use the Software or one of its main features.
Major: refers to any malfunctions other than blocking ones, which result in degraded operation of one or more feature(s) of the Software.
Minor: refers to any malfunctions other than blocking or major.
“Correction”: applicable only to anomalies, correction consists of providing the Client a version of the Software containing the fix for the anomaly or anomalies identified as the reason for an “Incident” call.
“Assistance request”: a request dealing with the use of the Software.
“Specific request”: a request related to an optional or complementary service.
“Incident”: a request concerning a malfunction of the Software. An incident may be the result of a misuse of the Software or an anomaly.
An incident can be of two types:
Critical: the observed malfunction results in total unavailability of the Software or one of its basic features.
Non-critical: any other malfunction.
“Acceptance” (of a request): the action of acknowledging receipt of a Client’s request. Acceptance is evidenced by providing the Client with a ticket number and the chosen qualification for this request (critical incident, non-critical incident, assistance request, specific request).
2. PRACTICAL TERMS OF SUPPORT ACCESS
Access to support: via the ticket management tool available at this address:
https://apps.maintenance-coach.com/app/ticketing#/tickets/new
Support hours: Business days, Monday to Friday: 09:00 AM – 12:00 PM and 02:00 PM – 06:00 PM (Paris, France time zone)