Priority 2. Any condition that impairs one or more functions that a System Deliverable is warranted to perform or that results from Contractor’s performance of the Services and impairs District’s use of any aspect of its information technology environment, but that does not involve a Priority 1 condition and is not a Priority 3 condition, is a “Priority 2” condition. Nonexclusive examples include database information corruption for a single District customer or incorrect writing of non-critical fields. Priority 2 conditions are less severe than Priority 1 conditions. For Priority 2 conditions, District shall receive a response within four hours from the time Contractor is notified. Whenever possible, Priority 2 conditions will be addressed by providing a patch or suggested work-around to accommodate District’s needs within eight hours, with a correction within 24hours. If a patch or work-around cannot be provided within eight hours, the problem shall be escalated to a Priority 1 condition and treated as set forth above.
Priority 2. An Error, Defect or Malfunction which substantially degrades the performance of the Software, but does not prohibit the City’s use of the Software.
Priority 2. A Defect that substantially degrades the performance of the Tyler Software, but does not prohibit your use of the Tyler Software. We shall assign a qualified product technical specialist(s) within four (4) business hours of our receipt of your notice. The product technical specialist will then work to diagnose and correct the Defect. We shall work diligently to make the correction, and shall provide ongoing communication to you concerning the status of the correction until the Tyler Software is operational without Priority 2 Defect. The goal for correcting a Priority 2 event is to include a correction in the next Tyler Software release.
Priority 2. LaSalle will use its good faith efforts to design and generate each page within the Personal, Customer Service, Apply and Locations sections of xxx.xxxxxxxxxxx.xxx and xxx.xxxxxxxxxxxxxxxxxxx.xxx, (or current applicable URL) so that each substantially complies with Priority 2 of the Guidelines by the Effective Date.
Priority 2. If no applicant in the foregoing category (sub-paragraph 3) meets the minimum qualifications of the vacancy, the Employer shall then consider Employees from within the bargaining unit, who have been relieved or terminated because of lack of work or other legitimate reasons and have employment security as outlined in Article 9, Employment Security, who meet the minimum qualifications as set forth in sub-paragraph 2, above, for a vacancy in the same or lower pay band as the position from which the Employee was relieved or terminated.
Priority 2. High. These issues have a negative impact upon a large business function. This category is characterized by the following: - Issues that significantly impact the normal conduct of Client business - Temporary workaround is a reasonable option. Vendor will make a best effort to resolve these issues within [*] Updates to customer will be given [*].
Priority 2. If additional summer school hours are available, any regular 26 BASRP employee who was laid-off all, or a portion, of their hours during the regular school 27 year, shall be offered those hours during the summer.
Priority 2. The Error materially affects the performance of the cBEYONData Software, or materially restricts Customer’s use of the cBEYONData Software (for example, important cBEYONData Software features are unavailable with no acceptable workaround).
Priority 2. A Priority 2 incident exists when the use of xxxxx' contractual services is actually not impossible or severely restricted, for example, due to failures, malfunctions, incorrect work results or response times, but the usage restriction(s) is / are not insignificant and can be avoided by taking reasonable technical and / or organizational measures (workarounds) in the event of an incident that has been attributed high urgency.
Priority 2. Any condition that impairs one or more functions that a System Deliverable or Final Deliverable is warranted to perform or that results from Contractor’s performance of the Services and impairs District’s use of any aspect of its information technology environment, but that does not involve a Priority 1 condition and is not a Priority 3 condition, is a “Priority 2” condition. Nonexclusive examples include incorrect writing of non-critical fields. Priority 2 conditions are less severe than Priority 1 conditions. Contractor shall begin working to provide a reasonable resolution for a Priority 2 condition within four
