Critical Failures definition

Critical Failures. Critical Failures shall be considered to be highest priority [*].
Critical Failures. Critical Failures shall be considered to be highest priority and shall cause immediate allocation of all necessary NEI resources to expeditiously develop and implement effective containment and resolution plans in conjunction with EMC, until problem resolution. NEI's commitment of resources shall include but not be limited to committing NEI personnel to work evenings and weekends or if necessary, to send such personnel to EMC's site.
Critical Failures. Critical Failures are defined [*].

Examples of Critical Failures in a sentence

  • Grass Valley will ship an Exchange Component to Customer within the applicable time specified in the Table set forth in Section 5 for all Critical Failures (as defined below) and within a commercially reasonable time for all other failures provided an Exchange Component is needed to solve the reported problem.

  • Grass Valley will ship an Exchange Component to Customer within the time specified in the Table set forth in Section 10.4 for all Critical Failures and within a commercially reasonable time for all other failures provided an Exchange Component is needed to solve the reported problem.

  • Level 1: Business Critical Failures Critical production issue that severely impacts clients use of the service.

  • Grass Valley will ship an exchange component to Customer within the Next Business Day for all Critical Failures and within a commercially reasonable time for all other failures, provided an exchange component is needed to solve the reported problem.

  • Upon the occurrence of a Critical Failure(s), HireRight may terminate this Agreement for cause (except if the failure qualifies as a Force Majeure event), without regard to the Default Cure Period.

  • Severity level Definition Initial Response Time Status Update Interval Time to Resolution 1 Business Critical Failures: An error in, or failure of, the Software Application that materially impacts the Customer’s routine business operations: a) Production Software Application down.

  • In the case of Critical Failures of discrete, identifiable, serial numbered Covered Equipment components (that can be shipped as a complete component) Grass Valley will ship replacement hardware components to Customer from a Grass Valley service center before receipt of Customer’s defective components according to the following terms (“Advance Exchange Hardware Replacement”).

  • Grass Valley will ship an Exchange Component to Customer within the applicable time specified in the Table set forth in Section 5 for all Critical Failures (as defined above in Section 5) and within a commercially reasonable time for all other failures provided an Exchange Component is needed to solve the reported problem.

  • All Critical Failures must be reported via a phone call, in addition to any other method of opening a service request.

  • As of the effective date of termination, Redwood City will assemble the work product without charge and put it in order for proper filing and closing and deliver it to San ▇▇▇▇▇▇.


More Definitions of Critical Failures

Critical Failures. Conditions that severely affect the Service and require immediate corrective action, such as loss of service that is comparable to the Total Loss of capacity;
Critical Failures means, any performance, compatibility, operational, security, or quality issues, which result in (a) FedEx’s inability to use the Service; or, (b) Errors in the Service which disrupt critical business production.
Critical Failures. An Error that: (a) disrupts the operations of the network or other systems on the network; or (b) requires Software to be shut-off; or (c) disables the ability of operators to interface with the Software Provider shall acknowledge receipt of a Support Request within 24 hours (during Business Days) and 48 hours (out of Business Days) Provider shall Resolve the Support Request as soon as practicable and no later than 7 days after Provider’s receipt of the Support Request. Full resolution no later than 14 days. Significant Failure: (a) an Error that materially impairs the operation of the Software; or (b) impairs the ability of operators to interface with the Software Provider shall acknowledge receipt of a Support Request within 24 hours (during Business Days) – 48 hours (out of Business Days) Provider shall Resolve the Support Request as soon as practicable and no later than 14 days after Provider’s receipt of the Support Request. Full resolution no later than 30 days.