Critical Defects Sample Clauses

Critical Defects. Whenever a P0 defect is identified, ▇▇▇▇▇ will treat this as a showstopper. Our real time monitoring on the system will alert ▇▇▇▇▇ support teams of issues and will log the issue on our status page. However, if the status page does not reflect an issue you are experiencing then you must create a JIRA ticket detailing the nature of the critical system problem (see ‘JIRA User Guide’ below). Additionally, you may contact ▇▇▇▇▇ directly on the relevant support number in the ‘Contacting ▇▇▇▇▇’ section of this document. ▇▇▇▇▇ will investigate and to all reasonable endeavours provide a solution/workaround to get the system back up and running as soon as possible. Throughout the investigation we will update you on the progress. If we find that there is a suitable workaround or that the Defect was prioritised incorrectly ▇▇▇▇▇ have the right to downgrade the defect to a priority that meets ▇▇▇▇▇’▇ standard service level requirements. You will be informed why we have downgraded this ticket. If the defect can only be resolved via a code change or script, we will raise a JIRA ticket with Development who will review the defect and provide feedback. ▇▇▇▇▇ will continue to update you on progress. The code change or script will either be part of a hotfix patch or planned roadmap release, depending on whether a suitable workaround for the defect exists.

Critical Defects. If Service Restoration with respect to a Critical Defect has not been achieved within one (1) hour after the defect is reported by BTE to Vice President of Operations, as applicable, Vendor shall notify the appropriate Vendor supervisory management of the unrestored condition. Technical and management escalation contact information for the persons set forth in this Section are as follows: Tier3 Support 24/7 TAC Technical Support Engineer [**] n.a. (blackberry) [**] Technical Support Manager ▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇ Manager, Service and Support [**] n.a. (blackberry) [**] VP, Service and Support ▇▇▇▇▇ ▇▇▇▇▇ Vice President, Service and Support [**] n.a. (blackberry) [**]

Critical Defects. If Service Restoration with respect to a Critical Defect has not been achieved within one (1) hour after the defect is reported by the School District to [TBD] , as applicable, Vendor shall notify the appropriate Vendor supervisory management of the unrestored condition.

Critical Defects. 45.1 The Contractor acknowledges and agrees that the Employer may, either before or after completion of a Task, arrange for a Critical Defect to be corrected by others instead of by the Contractor at the cost of the Contractor. Without prejudice to any other right or remedy of the Employer, the Contractor pays to the Employer all costs reimbursed by the Employer to others for correcting a Critical Defect. The Employer notifies the Contractor of a Critical Defect as soon as reasonably practicable.

Critical Defects. 10.2.2.1. In the event of a critical defect (see section 3.3. 1) Visioneer will provide HP with a revised version of the Program no later than XX from the time an acceptable resolution is released. Visioneer will deliver revised versions of XX software to HP no later than XX from the time the XX version is released. 10.2.2.2. A critical defect is not completely resolved until HP verifies proper operation on the entire set of languages HP supports. HP will respond in writing that each critical defect is considered closed no later than XX from the time the full set of elements required for XX localization (see Exhibit J1 and Exhibit J2) are received from Visioneer.

Critical Defects. In the event that the Client notifies Evolutio of a Critical Defect, Evolutio shall acknowledge such notification within four (4) hours during Support Hours. Evolutio shall use commercially reasonable efforts to provide an update to the Evolutio Products that corrects any Critical Defect or provide a work around within five (5) business days from the date of notification, but in any event as quickly as possible. 3.1.1 Only Critical Defects should be logged as Critical priority tickets; 3.1.2 In order to resolve critical priority tickets Client must provide remote access to the relevant system and the name of a contact person and telephone number at the Client who will be available throughout the resolution of the ticket. The Client’s contact person must be available on a 24/7 basis. 3.1.3 In order to resolve critical priority tickets, Client must provide the Problem Solving Log to Evolutio.

Critical Defects. A critical defect is a can defect which shows product leakage and/or is certain or most likely to produce a leak. A critical defect causes failure to the package to the point where the container will not fulfill its intended purpose and is most likely to result in an unacceptable condition for the consumer.

Critical Defects. The presence of a critical defect means that the functionality of the Product is affected, but can be used with the intervention of RAMCO’s Customer support personnel or implies that a program or feature in the Product cannot be used although other programs or features remain unaffected or implies that the Product as a whole functions but a certain feature is somewhat disabled. For a critical defect, RAMCO will put in its commercial reasonable efforts to resolve the failure within 3 working days after registration.

Critical Defects. “Critical Defects” means conditions under which the Product is inoperative and End User’s inability to use the Product creates an emergency situation with respect to End User’s business operations. This condition generally is characterized by a loss of network connectivity or service affecting a major customer or multiple other customers due to Product failure and requires immediate restoration or correction.