Severity 2 Incident definition

Severity 2 Incident means a non-catastrophic Event causing a significant component of the RapidDeploy Services to fail or to perform materially different than design, creating significant inconvenience for normal functions but workaround exists to perform critical functions. Associated with service disruption to multiple users although not necessarily causing major financial or contractual risk to Client. 24x7x365 2 hours 8 hours*

Severity 2 Incident is an Error or potential Error that has a severe restriction on the development, deployment, or operational use of the Hosted Service, resulting in the restricted ability to continue to develop, deploy, or use the Hosted Service (or any major function or subsystem thereof) as required or intended. JUNYO’s response time to a reported Severity 2 Incident will be 4 hours if not immediately.

Severity 2 Incident is a major issue which causes important Element Service features to be unavailable with no acceptable workaround, but Customer’s production use is continuing. For example, if templates are unavailable, but the Element Service is otherwise Available that would constitute a Severity 2 issue.

Examples of Severity 2 Incident in a sentence

• Severity 2 (“Major”) Incidents: A Severity 2 Incident means (i) the system is functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or (iii) mission critical applications, while not inoperable, have experienced material system interruptions.

• Contractor will provide the State a service level credit of .25% of its monthly invoice for fees related to each affected testing site for each Severity 2 Incident that does not meet this response time standard.

• A Severity 2 Incident is any issue with the Contractor’s platform that affects a specific group of State-authorized users and prevents them from executing their jobs partially or anywhere a work around has been Identified.

• Severity 2 (“Normal”) Incidents: A Severity 2 Incident means (i) the system is functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or(iii) mission critical applications, while not inoperable, have experienced material system interruptions.

• Severity 2 (“Major”) Incidents: A Severity 2 Incident means for purposes of the Liferay Cloud Infrastructure (i) any environment for the Customer Application is functioning with limited capabilities or is unstable with periodic interruptions; or for purposes of Liferay Software (ii) the system is functioning with limited capabilities, or (iii) is unstable with periodic interruptions, or (iv) mission critical applications, while not inoperable, have experienced material system interruptions.

• Severity 2 (“Normal”) Incidents: A Severity 2 Incident means (i) the system is functioning with limited capabilities, or (ii) is unstable with periodic interruptions, or (iii) mission critical applications, while not inoperable, have experienced material system interruptions that are effectively making the applications inoperable.

• Update Notification – Communication sent to State with status of Severity 1 or Severity 2 Incident after Initial Notification.

• Severity Description Level Severity 2 Incident - HighCustomer impacting incident requiring prompt corrective action due to the large number of customers affected or that has significant business impact as a result of a network, product or service unavailability or degradation across national or multiple geographical areas or that has the potential to result in damage to Telstra’s brand/reputation or incur a major financial penalty.

• Severity 2 Incident means an Incident where your service is not available, or severely degraded, impacting significant aspects of business operations.

• This committee, of no less than three (3) members, will contact commissioners in April for the purpose of recruiting the next Chair and Vice-Chair officers.

More Definitions of Severity 2 Incident

Severity 2 Incident means an Incident that: (i) causes the ***or ***or ***of ***of a ***or ***or ***, or (ii) is an ***or ***that ***, or ***performing *** and for which a workaround solution may exist which allows for continued essential operations.

Severity 2 Incident means a Security Incident which requires the Customer to take action within 12-24 hours of notification from the SSOC. Incidents such as unauthorized local scanning activity, unverifiable security events (e.g. security events with unknown impact), and attacks targeted at specific servers or workstations are grouped into this category;

Severity 2 Incident means an Incident that: (i) causes the “***” or “***” or “***” of “***” of a “***” or “***” or “***”, or (ii) is an “***” or “***” that “***”, or “***” performing “***” and for which a workaround solution may exist which allows for continued essential operations. CONFIDENTIAL MATERIAL APPEARING IN THIS DOCUMENT HAS BEEN OMITTED AND FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION IN ACCORDANCE WITH THE SECURITIES ACT OF 1933, AS AMENDED, AND RULE 24B-2 PROMULGATED THEREUNDER. OMITTED INFORMATION HAS BEEN REPLACED WITH ASTERISKS “Severity 3 Incident” represents a lower impact problem that involves a “***” or “***” of “***”, or some other problem involving “***”. CoreLogic can continue “***” operations and a workaround solution may exist which allows for continued “***” operations.

Severity 2 Incident means an incident that has, or in the reasonable opinion of Telstra is likely to have, a significant adverse effect on the provision of the Consumer VMC Website to Telstra BigPond Customers or the business of Telstra.

Severity 2 Incident means a serious Event causing a significant component of the platform or services to fail or to perform materially differently than designed, creating inconvenience for normal functions but workarounds exist for critical functions.3. “Severity 3 Incident” means a medium Event (minor business impact) that had minimal current impact on the Client and causes a malfunction of a non-essential feature.4. “Severity 4 Incident” means a low/minor event that has lowimpact on the Client and causes malfunction of a non- essential feature.