Low Priority Clause Samples

Low Priority. Problems that have been verified through the ----- ------------ formal maintenance channels as causing particular features or functionality to be inoperative, but do not affect the normal business operations during the normal business operations during the working day. There is an acceptable work around.

Low Priority. Licensee has a problem which is not seriously impacting Licensee's workflow.

Low Priority. The technician will make the initial contact within three business days and will negotiate a schedule for resolution with the client/Customer. All calls will be attempted to be resolved via Remote Support. Should on-site response be required this will be negotiated with the client to ensure a suitable resolution time. Time spent travelling to site will be included in the work time.

Low Priority. An incident that has effects limited to the software in which it occurs and that can be avoided with little user inconvenience. Low priority incidents will be recorded and will be corrected in future releases of the Product. In respect of incidents, the Service Desk will respond to (but not necessarily fix) each Support Ticket within the following timescales: Call Priority Response Time (Business Hours) High 2 Medium 6 Low 24 It is the responsibility of the Client to provide Simpleview with a means to reproduce incidents at Simpleview’s premises. To aid fault diagnosis and error correction, the Client will use reasonable endeavours to provide an accurate address or location of the fault. If the problem is with the configuration of the hosting servers, we will liaise with the data centre’s support department to resolve the issue and provide advice and assistance throughout the process as detailed in the separate hosting agreement.

Low Priority. A Low Priority Network Issue is a partial loss of service or impaired service at an individual access point.

Low Priority. This service priority is used when an issue or problem occurs within an application, but the user and business can conduct business normally.

Low Priority. These are scenarios where there is a minor issue to the Service that is causing an inconvenient and/or small impact on Customer or End User experience. 15.9.3.1. Support ticket acknowledged and receipt sent to Customer within a maximum of 3 hours. 15.9.3.2. Fault identified and action plan for resolution developed within a reasonable time.

Low Priority. Non-critical function or procedure, unusable where a workaround is available or a repair is possible, no direct impact on service availability. Resolution time for this level of priority is 5 days. SCHOOL BUS STOP ARM ENFORCEMENT AGREEMENT PAGE ▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ AREA SCHOOL DISTRICT • Medium Priority – Non-critical function or procedure, unusable or hard to use having an operational impact, but with no direct impact on services availability. Resolution time for this level or priority is 3 days. • High Priority – Critical functionality or service interrupted on a subset of users or products, degraded or unusable, having a severe impact on services availability. No acceptable alternative is possible. Resolution time for this level of priority is 24 hours. • Critical Priority – Interruption making critical functionality inaccessible or a complete product/service interruption causing a severe impact on services availability. No possible alternative solutions are possible. Resolution time for this level of priority is 4 hours. Once a ticket has been submitted, regardless of priority, the BusPatrol Account Representative for the Customer will be notified and will immediately engage both the requestor and the appropriate department/team within BusPatrol to ensure the question or issue is resolved as soon as possible. SCHOOL BUS STOP ARM ENFORCEMENT AGREEMENT PAGE ▇▇ ▇▇▇▇▇▇▇ ▇▇▇▇▇▇▇▇▇ ▇▇▇ ▇▇▇▇▇▇ ▇▇▇▇▇ AREA SCHOOL DISTRICT The following revenue sharing models are included to illustrate the manner in which the Revenue Sharing/ Technology Fees provisions in Article 5.0 of the Agreement are to be applied: Note 1 Collected Tickets/ Gross Revenue 450 $300.00 $135,000.00 Less Required Disbursements to Law Enforcement and State Fund 450 $50.00 ($22,500.00) Remaining Revenue $112,500.00 District Monthly Revenue Share 40% $45,000.00 BusPatrol Monthly Revenue Share 60% $67,500.00 Note 2, Note 3 BusPatrol Monthly Technology Fee 64 $115.00 ($7,360.00) District Total Monthly Due (Revenue Share Less Technology Fees) $37,640.00 Note 4 BusPatrol Total Monthly Due (Revenue Share Plus Technology Fees) $74,860.00 Note 1: Ticket rates and projected revenue are for illustration only. Actual gross revenue includes all revenues collected from tickets issued through the operation of the BusPatrol System on buses owned or operated by School District, not including credit card processing fees paid by the party making payment upon a ticket.