Priority 1 Incident definition

Priority 1 Incident means an Incident with the Priority “Very High” as defined in Part 2 - Section B. Article 2 no.1a) (SLA for Initial Response Time).

Priority 1 Incident means that, due to this Incident, the Serviced Equipment’s primary function is not available. For example, an ATM cannot receive deposits or dispense cash. For clarity also, it is not a Priority 1 Incident if the ATM is not dispensing receipts but is otherwise fulfilling its primary function.

Priority 1 Incident means an Incident that has very serious consequences for normal business transactions and urgent, business critical work cannot be performed. This is generally caused by the following circumstances: complete system outage or malfunctions of central Software functions in the Production System.

Examples of Priority 1 Incident in a sentence

• SAP will provide a solution, work around or action plan for resolution (“Corrective Action”) of a Priority 1 Incident within four hours of SAP’s receipt (twenty-four hours a day, seven days a week) of such Priority 1 Incident via the SAP Support Network (“SLA for Corrective Action”).

• However SAP will commence processing of Priority 1 Incidents within twenty-four hours, seven days a week after SAP`S receipt of such Priority 1 Incident via the SAP Support Network, provided that the Incident is reported in English and that Partner and Supported End User provide for a suitably skilled, English-speaking contact in order to ensure communication with SAP if SAP assigns the Incident to an overseas SAP Support Organization center.

• If Green Cloud is able to provide a workaround for a Priority 1 Incident, it may be downgraded.

• Notwithstanding the Change consideration and implementation process outlined in this Exhibit 4, if a Change is required to resolve a Priority 1 Incident (“Emergency Change”), Provider shall immediately begin implementing the Emergency Change upon request by Customer.

• Please note: if you log a Priority 1 Incident (i.e. complete loss of service) you must also contact the Service Desk by telephone.

More Definitions of Priority 1 Incident

Priority 1 Incident means any condition where (i) a System is completely out of service (i.e., the System is completely down and is not capable of making any counterfeit-valid call decisions and RF fingerprint collections) or where the PreTect Graphical User Interface for a System is completely out of service for more than two (2) consecutive hours, and (ii) the source of the problem is a Regional Processing Complex (RP, AS, Gateway or Cisco Router).

Priority 1 Incident or “P1 Incident” means a complete loss of a critical business function already in production, for which no reasonable workaround exists. This includes items that result in the total inability of one or more end users to conduct key business functions or activities.

Priority 1 Incident means: a Reportable Incident that has caused, or could reasonably have been expected to have caused the Client physical or psychological injury or discomfort that requires medical or psychological treatment to resolve; a Reportable Incident where there are reasonable grounds to report the incident to police; or a Reportable Incident unlawful sexual contact, or inappropriate sexual conduct, inflicted on the Client; unexpected death of the Client; or unexplained absence of the Client.

Priority 1 Incident means an Incident with the Priority “Very High” as defined in Part 2 - Section B. Article 2 no.1a) (SLA for Initial Response Time).’⃒]枮fi 1 ḳflyὪ ø 2 y - ø B 䭨 Article 2 ø 1a) 㫦 (憅⮵fi¼ㅱ㗪攻 SLA) ㇨;佑›%⃒]枮fiⰔ㕤’fly檀y}ḳfl○

Priority 1 Incident means an Incident which prevents the access to a website to all users and which is not caused by a wrong sizing of Licensee’s information system and/or which is not related to a test platform.

Priority 1 Incident means an Incident with the Priority “Very High” as defined in Part 2 - Section B. 0 no.0a) (SLA for Initial Response Time).

Priority 1 Incident means a defect, non-conformity, or problem that is a critical or high priority because of its impact or urgency; for example, it may be (a) preventing the use of a critical function of a SaaS Solution, or