Priority Level. Each Incident subject to a Ticket will be assigned a priority level (the “Priority Level” of the Incident) based on the severity of the Incident and the effect of the Incident on the System, Services, and affected End User(s). The initial Priority Level for each Incident will be as specified by the State when making the applicable Request with Vendor. If no Priority Level is provided by the State when making a Request, Vendor will assign a Priority Level to the applicable Incident resulting from the Request based on the following criteria: Severity Level Incident Description Level 1 The System, or any Subsystem or function, is totally unusable or unavailable for multiple End Users.
Priority Level. The level of severity of an Error.
Priority Level. The priority levels of the CDN Service Requests are categorized according to the urgency the CDN Service Request or the impact of the Incident, as described below. The Response Time, availability of Live Support, and the frequency of the Case Status Update vary according to the type of Customer Support (i.e. Standard Support, Priority Support, Premium Support or Named Enhanced Support) purchased by Customer. Table 1: Priority Level Definitions Priority 1 (or "P1") Critical Impact - The CDN Service purchased by Customer is significantly impaired and unavailable to multiple User Locations (i.e. multiple Sites are affected). Priority 2 (or "P2") Major Impact - Repeatable inability to use the CDN Service from a single Location or region (e.g. localized denial of CDN Service issue). This may be to a single Site or a single server. Priority 3 (or "P3") Low Impact - Non-urgent matter or information request (e.g. planned configuration change request, information request, reports or usage questions, clarification of documentation, or any feature enhancement suggestions).
Priority Level. When you open a service request or incident, you may select a priority level ranging from low to high. The level of the incident will determine our minimum response time as well as a minimum charge against your support plan. Priority level usage guidelines: • Critical – System down or unusable, resolve immediately. • High – Very important, needed today if possible. • Medium – Needed today or tomorrow. • Low – Can wait a few days for resolution. Xxxxxxxx.xxx schedules services to meet our SLA for all clients. Please select the appropriate priority level for your service request or incident. The priority level provides the guaranteed minimum response time.
Priority Level. The items below are future intermunicipal initiatives identified by the municipalities along with the next steps required to explore them. The initiatives are organized by the following Municipal Service Areas (MSAs):
Priority Level. Depending on degree of concern, age, etc., we may include a priority 1-4 to assist with scheduling work in the future.
Priority Level. High An Error that causes a component of the Software to be severely limited or degraded, significantly affecting the Customer’s business operations and user productivity, and for which the Customer has notbeen able to establish a workaround. Priority Level- Normal An Error that causes the Software to be limited or degraded, and the Customer’s business operations and user productivity can substantially continue or for which the Customer has a workaround or alternative configuration. Priority Level- Low An Error that has no significant adverse effect on a Customer's use of the Software.
Priority Level. Error or defect that renders the System or any material portion thereof inoperative, or materially impairs Customer’s use of the System (e.g., all users and functions unavailable) 1 Error or defect that substantially impairs Customer’s use of one or more features or functions of the System (e.g., large number of users or business critical functions affected) 2 Error that has a minimal impact on the performance or operation of the System (e.g., limited number of users or functions affected, business process can continue) 3 Error that has a very limited impact on the performance or operation of the System (e.g., business process can continue; one user affected) 4
Priority Level. When you open a service request or incident, you may select a priority level ranging from low to high. Failure to follow these guidelines will constitute a violation of our Acceptable Use Policy and may result in termination or excessive use charges on your account. Priority Usage Guidelines Priority Description Emergency Critical service unusable / server down. High Server degraded – low impact on critical applications. Medium Requires a resolution within 12 hours. Low Requires a resolution within 24 hours. EndLayer schedules services to meet our Service Level Agreement for all clients. Please select the appropriate priority level for your service request or incident. The priority level provides the guaranteed minimum response time. Please note that selecting a Critical priority level for anything other than a system-down/unusable event will result in the incident being treated as a “High” priority request and the “High” priority response time will apply.
Priority Level. The Customer shall assign the priority level based on the Defect’s business impact in accordance with the below. Hours & Days represents business hours and business days. Priority level Resolution timeframe High Within 8 hours Medium Within 48 Hours Low Within 5 Working Days Service availability Coverage parameters specific to the service(s) covered in this Agreement are as follows: • Telephone support: 9:00 A.M. to 5:00 P.M. Sunday – Thursday Calls received out of office hours will be forwarded to a mobile phone and best efforts will be made to answer/action the call, however there will be a backup answer phone service • Email support: Monitored 9:00 A.M. to 5:00 P.M. Sunday – Thursday Emails received outside of office hours will be collected, however no action can be guaranteed until the next working day • Onsite assistance guaranteed within 72 hours during the business week Singleview
