Common use of Priority Levels Clause in Contracts

Priority Levels. Each support issue will be assigned a priority code based on the nature of the failure. Refer to Table 1. For purposes of this Schedule 9.2(b), a failure is a system condition or event that leaves the system in a state where it is performing a level lower than the performance level at the time of system acceptance. Performance is defined primarily by stability, responsiveness, and usability. Prioritization is driven by the nature of the incident as it relates to stability, responsiveness, and usability. For the purposes of this Schedule 9.2(b), these key terms are defined as follows: Stability - the availability of the system and all of its functions Responsiveness - the timeliness with which the system responds to user requests Usability - the degree to which the system is easy for the user to navigate and interact with the system

Priority Levels. Each support issue will be assigned a priority code based on the nature of the failure. Refer to Table 1. For purposes of this Schedule 9.2(b), a failure is a system condition or event that leaves the system in a state where it is performing a level lower than the performance level at the time of system acceptance. Performance is defined primarily by stability, responsiveness, and usability. Prioritization is driven by the nature of the incident as it relates to stability, responsiveness, and usability. For the purposes of this Schedule 9.2(b), these key terms are defined as follows: Stability - – the availability of the system and all of its functions Responsiveness - – the timeliness with which the system responds to user requests Usability - – the degree to which the system is easy for the user to navigate and interact with the system