PRIORITIZATION INCIDENTS Sample Clauses

PRIORITIZATION INCIDENTS. After a Functional Question, Bug or a Malfunction is approved, the priority will be determined. We distinguish three classifications of approved incidents: ▪ Low impact: the incident has very little impact on working with Xpert Suite, e.g. a workaround is available. The incident doesn’t result in data inconsistency and data integrity, security and privacy are covered. Working on a fix is low prioritised; ▪ Medium impact: the Incident can be fixed by a small modification in the application or the platform. To fix a Bug or Malfunction, usually no functional and/or technical design is made. However, the existing documentation is brought in line with the changes in the SaaS solution Xpert Suite and a brief description is given in the service management application of how the Bug or Malfunction was fixed. High priority fixes are usually taken into production with an intermediate update (hot fix) at night or during the weekend. Other fixes will be part of a regular release and update during a Maintenance window; ▪ High impact: that the incident can only be solved by modifying the Xpert Suite application. In this case, however, the modifications are so extensive that a formal process must be completed, consisting of the following steps: requirements analysis, drawing up functional and technical specifications, building, testing and putting into production. Urgency is associated with time. The time it takes to have the perceived Impact: ▪ Low urgency: o The damage caused by the incident only marginally increases over time; o Work that cannot be completed by staff is not time sensitive; ▪ Medium urgency: o The damage caused by the incident increases considerably over time; o A single user with VIP status is affected; ▪ High urgency: o The damage caused by the incident increases rapidly; o Work that cannot be completed by staff is highly time sensitive; o A minor incident can be prevented from becoming a major incident by acting immediately; o Several users with VIP status are affected. Incidents are dealt with on the basis of priority by using the priority matrix: Urgency Low Medium High Impact Low Priority 3 Priority 3 Priority 2 Medium Priority 3 Priority 2 Priority 1 High Priority 2 Priority 1 Priority 1 This led to three types of priority that can be distinguished: 1. Priority 3: i Low impact Bugs and Malfunctions: Business functions are possible, but the error situation is perceived as annoying by the user;
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to PRIORITIZATION INCIDENTS

  • Prioritization All Services will be implemented and/or facilitated (as applicable) on a schedule, and in a prioritized manner, as we determine reasonable and necessary. Exact commencement / start dates may vary or deviate from the dates we state to you depending on the Services being provided and the extent to which prerequisites (if any), such as transition or onboarding activities, must be completed.

  • Review Process A/E's Work Product will be reviewed by County under its applicable technical requirements and procedures, as follows:

  • Random Testing Notwithstanding any provisions of the Collective Agreement or any special agreements appended thereto, section 4.6 of the Canadian Model will not be applied by agreement. If applied to a worker dispatched by the Union, it will be applied or deemed to be applied unilaterally by the Employer. The Union retains the right to grieve the legality of any imposition of random testing in accordance with the Grievance Procedure set out in this Collective Agreement.

  • Contract Changes Changes may not be made in the terms and conditions of this contract without the agreement and written permission of the Director of Residence Life or the Director’s designee.

  • Claims Review Population A description of the Population subject to the Claims Review.

  • Processing Grievances The Association Representative involved and the grieving supervisor shall not leave work or disrupt departmental routine to discuss grievances without first requesting permission from his/her immediate superior, which shall not be unreasonably withheld. The Association Representative and the grieving supervisor shall be allowed a reasonable amount of time during working hours while on the Appointing Authority's premises when a grievance is investigated or presented in Steps 1 and 2.

  • Contractor Changes The Contractor shall notify DAS in writing no later than ten (10) Days from the effective date of any change in: a. its certificate of incorporation or other organizational document; b. more than a controlling interest in the ownership of the Contractor; or c. the individual(s) in charge of the Performance. This change shall not relieve the Contractor of any responsibility for the accuracy and completeness of the Performance. DAS, after receiving written notice by the Contractor of any such change, may require such agreements, releases and other instruments evidencing, to DAS’s satisfaction, that any individuals retiring or otherwise separating from the Contractor have been compensated in full or that provision has been made for compensation in full, for all work performed under terms of the Contract. The Contractor shall deliver such documents to DAS in accordance with the terms of DAS’s written request. DAS may also require, and the Contractor shall deliver, a financial statement showing that solvency of the Contractor is maintained. The death of any Contractor Party, as applicable, shall not release the Contractor from the obligation to Perform under the Contract; the surviving Contractor Parties, as appropriate, must continue to Perform under the Contract until Performance is fully completed.

  • Elements Unsatisfactory Needs Improvement Proficient Exemplary IV-A-1. Reflective Practice Demonstrates limited reflection on practice and/or use of insights gained to improve practice. May reflect on the effectiveness of lessons/ units and interactions with students but not with colleagues and/or rarely uses insights to improve practice. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues, and uses insights gained to improve practice and student learning. Regularly reflects on the effectiveness of lessons, units, and interactions with students, both individually and with colleagues; and uses and shares with colleagues, insights gained to improve practice and student learning. Is able to model this element.

  • Asset Representations Review Process Section 3.01 Asset Representations Review Notices and Identification of Review Receivables. On receipt of an Asset Representations Review Notice from the Seller according to Section 5.7 of the Receivables Purchase Agreement, the Asset Representations Reviewer will start an Asset Representations Review. The Servicer will provide the list of Review Receivables to the Asset Representations Reviewer promptly upon receipt of the Asset Representations Review Notice. The Asset Representations Reviewer will not be obligated to start, and will not start, an Asset Representations Review until an Asset Representations Review Notice and the related list of Review Receivables is received. The Asset Representations Reviewer is not obligated to verify (i) whether the conditions to the initiation of the Asset Representations Review and the issuance of an Asset Representations Review Notice described in Section 7.6 of the Indenture were satisfied or (ii) the accuracy or completeness of the list of Review Receivables provided by the Servicer.

  • SCOPE OF THE WORK The Contractor shall furnish all the materials, perform all of the Work, and do all things required by the Contract Documents.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!