Priority 2 Incident definition
Priority 2 Incident means that, due to this Incident, Serviced Equipment is degraded where some functions are not available. For example, if a full function ATM cannot receive deposits, but can dispense cash.
Priority 2 Incident means an Incident that causes normal business transactions in a Production System to be seriously affected and results in necessary tasks not being performed. This is caused by incorrect or inoperable functions in the Software that are required to perform such transactions and/or tasks.
Priority 2 Incident means any condition where a System is up, but there is partial loss of functionality (i.e., the System is working, but there is partial loss of data communication). For example, any condition where the Cell Site Hardware at any Cell Site is completely out of service is a Priority 2 Incident.
Examples of Priority 2 Incident in a sentence
The Digital Content Provider shall acknowledge receipt of the LEA’s initial notification of a Priority 2 Incident within 2 hours, and shall provide status updates thereafter.
The Digital Content Provider will respond to and commence efforts to fix a Priority 2 Incident no later than 12 hours after notification of such Incident from the LEA.
Reconciliation Service Requests will be prioritized below a Priority 2 Incident and above a Priority 3 Incident.
The CTS technical analyst responding to the call will perform the following during the applicable hours of coverage: (i) identify the condition; and (ii) assess whether the condition is a Priority 1 Incident, Priority 2 Incident, or Priority 3 Incident.
With respect only to the specific type of RSR referred to by State and Contractor as an 834 Transaction Removal, Contractor shall prioritize such RSRs between a Priority 2 Incident and a Priority 3 Incident.
More Definitions of Priority 2 Incident
Priority 2 Incident means an incident where some functions or a business process is partially unusable or is affected to such an
Priority 2 Incident or “P2 Incident” means a partial loss of a critical business function already in production and/or significant degradation of the ability to provide service to the customer. P2 Incident includes incidents with any application/database which is important to a client’s business or operations and which make the application/database unusable or unavailable; a reasonable workaround does exist. P2 Incident also includes incidents for which a workaround exists but requires extensive effort to implement. Incident may be closed after workaround is in place and reopened as a Priority 3.“Priority 3 Incident” or “P3 Incident” means a degradation or loss of non-critical business functions already in production. Users can continue operating with the results being adequate to perform needed functionalities (although the process or format may be less than desirable). P3 Incident includes incidents which degrade system functionality or business performance; but major functions of the application/database still work. P3 Incident also includes incidents affecting a single user – preventing completion of a critical task but for which a reasonable workaround exists. Payment Terms Contractor shall provide invoices to USAC on a monthly basis during the Term. Each invoice shall describe the charges accrued during the applicable period, the line items, number of units processed/transactions completed, volume tier, and penalties (as applicable) and such other detail as is specified in the Contract.USAC may withhold payment of any portion of an invoice that it disputes in good faith. USAC is not liable to pay any charges not invoiced within ninety (90) days after Contractor was first permitted to invoice USAC for such charges.All charges will be payable in U.S. dollars. Third Party Agreements The Contract may include requirements regarding compliance with third party data sharing or similar agreements (such third parties are “Data Suppliers”).
Priority 2 Incident means an incident where some functions or a business process is partially unusable or is affected to such an extent that there is a serious impact on the productivity of TxDOT personnel.
Priority 2 Incident or “P2 Incident” means a partial loss of a critical business function already in production and/or significant degradation of the ability to provide service to the customer. P2 Incident includes incidents with any application/database which is important to a client’s business or operations and which make the application/database unusable or unavailable; a reasonable workaround does
Priority 2 Incident means an Incident which prevents the access to one or several web pages of a website and which is not caused by a wrong sizing of Licensee’s information system and/or which is not related to a test platform. An important slowdown is considered as a Priority 2 Incident.
Priority 2 Incident or “P2 Incident” means a partial loss of a critical business function already in production and/or significant degradation of the ability to provide service to the end user. This includes an incident with any application/database which is important to a client’s business or operations when the incident makes the application/database unusable or unavailable but a reasonable workaround exists. P2 Incident also includes incidents for which a workaround exists but requires extensive effort to implement. A P2 Incident may be closed after workaround is in place and reopened as a Priority 3.
Priority 2 Incident means a defect, non-conformity, or problem that is a moderate priority because of its impact or urgency; for example, the SaaS Solution is operating, but one or more minor functions are limited, restricted, or impaired.