Low Priority Sample Clauses

Low Priority. An End User has a problem which is not seriously impacting Distributor's workflow.
AutoNDA by SimpleDocs
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. 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.
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 working day. There is an acceptable work around.
Low Priority. A Low Priority Network Issue is a partial loss of service or impaired service at an individual access point.
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 00 XXXXXXX XXXXXXXXX XXX XXXXXX XXXXX AREA SCHOOL DISTRICT Spring Grove Area School District (Pennsylvania) • 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 00 XXXXXXX XXXXXXXXX XXX XXXXXX XXXXX AREA SCHOOL DISTRICT CONFIDENTIAL Spring Grove Area School District (Pennsylvania) ATTACHMENT B REVENUE SHARING/TECHNOLOGY FEES MODEL 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: (for illustration only): BusPatrol Solution Estimated Monthly Revenue Distribution Qty Unit Price Amount ($) 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...
AutoNDA by SimpleDocs
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.

Related to Low Priority

  • Priority If the Managing Underwriter or Underwriters of any proposed Underwritten Offering advise the Partnership that the total amount of Registrable Securities that the Selling Holders and any other Persons intend to include in such offering exceeds the number that can be sold in such offering without being likely to have an adverse effect on the price, timing or distribution of the Common Units offered or the market for the Common Units, then the Common Units to be included in such Underwritten Offering shall include the number of Registrable Securities that such Managing Underwriter or Underwriters advise the Partnership can be sold without having such adverse effect, with such number to be allocated (i) first, to the Partnership, (ii) second, to Teekay and its Affiliates pursuant to any registration rights existing as of the date of this Agreement and (iii) third, pro rata among the Selling Holders who have requested participation in such Underwritten Offering and any other holder of securities of the Partnership (other than Teekay and its Affiliates) having rights of registration that are neither expressly senior nor subordinated to the Registrable Securities (the “Parity Securities”). The pro rata allocations pursuant to clause (iii) above for each Selling Holder who has requested participation in such Underwritten Offering shall be the product of (a) the aggregate number of Registrable Securities proposed to be sold in such Underwritten Offering multiplied by (b) the fraction derived by dividing (x) the number of Registrable Securities owned on the Closing Date by such Selling Holder by (y) the aggregate number of Registrable Securities owned on the Closing Date by all Selling Holders who have requested participation in such Underwritten Offering plus the aggregate number of Parity Securities owned on the Closing Date by all holders of Parity Securities that are participating in the Underwritten Offering.

Time is Money Join Law Insider Premium to draft better contracts faster.