Priority 3 Errors Sample Clauses

Priority 3 Errors. Upon acknowledging a Priority 3 Error, IM shall provide Customer an initial assessment within [*] and an error resolution plan within [*]. IM will use best commercial efforts to (i) include an error correction in the next Update, if any of the Software, and/or (ii) to implement in a timely fashion a workaround and/or schedule and execute error correction activities for Informatics Hardware or Equipment.
Sample 1Sample 2Sample 3See All (4)
Priority 3 Errors. A member of the TSO, as determined by the level of care selected by Customer, will respond to reports of Error conditions brought to GREENLIGHT’s attention. GREENLIGHT may correct such Errors in a future New Release. Initial response times for Priority 3 errors will be within 5 business days. Greenlight will use commercially reasonable efforts to develop a fix as soon as possible. Greenlight will also provide an update every week on the resolution.
Sample 1Sample 2Sample 3
Priority 3 Errors a. The Customer shall use the standard call support center telephone number or web service for emergency support during normal business hours (7:30 a.m. to 7:30 p.m. CST, Monday through Friday, excluding holidays). b. Consultant will provide the Customer a tracking number for all Priority 3 Errors within five (5) business days following the report of issue, and respond further as part of our normal online tracking system. c. Consultant will use commercially reasonable efforts to resolve Priority 3 Errors by means of a future scheduled update or release, as mutually agreed. All issues or questions reported to support are tracked via a support call. Support analysts cannot provide assistance unless a support call is logged. The current process for logging calls includes the following: eSupport (via website), email, phone and fax. • Each call must contain at a minimum: the Customer name, contact person, software product and version, module and/or menu selection, nature of issue, detailed description of your question or issue and any other pertinent information. • The support system or one of the support analysts will provide the Customer with a call i.d. to track the issue and the call will be logged into a support tracking database. • Each call will be stored in a queue and the first available support representative will be assigned to deal with the issue. • As the support representative assigned to the call investigates the issue, the Customer will be contacted and advised as to where the issue stands and the course of action that will be taken for resolution. If the support analyst requires additional information, he/she will contact the Customer to obtain the information required. • All correspondence and actions associated with a call will be tracked in the support database. At any time, if available to the Customer, the Customer may log onto the Consultant’s website to see the status of each call. • Once the call has been resolved, the Customer will receive an automated notification by email that the call has been closed. This email will contain the entire event history of the call from the time the call was created and leading up to the resolution of the call. The Customer also has the option of viewing both open and closed calls, if available to the Customer, via the Consultant’s website. • If the issue needs to be escalated to a development resource or programmer for resolution, the issue will be logged into a development tracking database and the Cu...
Sample 1
Priority 3 Errors. In the event of a Priority 3 Error in the Software or SOZO Services, ImpediMed shall, within two (2) business days of receiving Customer’s report, commence verification of the Error. Upon verification, ImpediMed shall use commercially reasonable efforts to resolve the Error with an Error Correction. ImpediMed shall provide Customer with periodic reports on the status of the Error Correction.
Sample 1
Priority 3 Errors. The TSO will respond to reports of Error conditions brought to Jurisage’s attention by a Customer. With regard to Software, Jurisage may correct such Errors in a future version of the latest Supported Release.
Sample 1
Priority 3 Errors. The TSO will respond to reports of Error conditions brought to CiteRight’s attention by a Customer. With regard to Software, CiteRight may correct such Errors in a future version of the latest Supported Release.
Sample 1
Priority 3 Errors. A member of the TSO, as determined by the level of care selected by Customer, will respond to reports of Error conditions brought to ALERT’s attention. ALERT may correct such Errors in a future New Release.
Sample 1
Priority 3 Errors. PowerPhone may include the Fix for the Error in a subsequent major release of the software.
Sample 1

Related to Priority 3 Errors

  • Priority Hiring If the Contract Amount is over $200,000 and this Agreement is for services (other than Consulting Services), this section is applicable. Contractor shall give priority consideration in filling vacancies in positions funded by this Agreement to qualified recipients of aid under Welfare and Institutions Code section 11200 in accordance with PCC 10353.

  • Priority If the Managing Underwriter or Underwriters of any proposed Underwritten Offering advise the Partnership that the total amount of Registrable Securities that the Selling Holders and any other Persons intend to include in such offering exceeds the number that can be sold in such offering without being likely to have an adverse effect on the price, timing or distribution of the Common Units offered or the market for the Common Units, then the Common Units to be included in such Underwritten Offering shall include the number of Registrable Securities that such Managing Underwriter or Underwriters advise the Partnership can be sold without having such adverse effect, with such number to be allocated (i) first, to the Partnership, (ii) second, to Teekay and its Affiliates pursuant to any registration rights existing as of the date of this Agreement and (iii) third, pro rata among the Selling Holders who have requested participation in such Underwritten Offering and any other holder of securities of the Partnership (other than Teekay and its Affiliates) having rights of registration that are neither expressly senior nor subordinated to the Registrable Securities (the “Parity Securities”). The pro rata allocations pursuant to clause (iii) above for each Selling Holder who has requested participation in such Underwritten Offering shall be the product of (a) the aggregate number of Registrable Securities proposed to be sold in such Underwritten Offering multiplied by (b) the fraction derived by dividing (x) the number of Registrable Securities owned on the Closing Date by such Selling Holder by (y) the aggregate number of Registrable Securities owned on the Closing Date by all Selling Holders who have requested participation in such Underwritten Offering plus the aggregate number of Parity Securities owned on the Closing Date by all holders of Parity Securities that are participating in the Underwritten Offering.