The levels of criticality/severity determine, together with the contracted SLAs, the priority when resolving an incident.
The levels of priority/criticality with which the Athento service operates are described in the following table:
Priority |
Description |
Blocker |
Una incidencia Blocker indica que el sistema en producción se encuentra totalmente fuera de servicio. A Blocker incident indicates that the system in production is completely out of service. In these cases, the Athento team will proceed to:
|
Critical |
In this case, the production system is running, but critical system services or operations are interrupted. The impact on the system is severe and limits vital system functionality (e.g., creating documents or generalised document retrieval). In these cases:
|
Major |
There is moderate system impairment. It may also refer to system instability with periodic service interruptions or lesser loss of product functionality. This category can also include development errors that affect the performance of the product. In this case, the customer is perfectly able to operate the system. These support requests will be solved by hotfixes or new releases, but have lower priority than Critical issues. |
Trivial |
There is minor system impairment. Specific functionalities are not functioning normally, but the customer is fully able to operate the system. This type of support requests can also refer to questions on system usage, general information requests, reporting of errors in documentation, recommendations, enhancement requests, etc. |
Comments
0 comments
Please sign in to leave a comment.