Changing Existing Jobs Sample Clauses

Changing Existing Jobs. Prior to the Company substantially changing an existing job, the Company will meet with the Union to discuss the subject. Either prior to or within ninety (90) working days of the change, the parties shall meet to establish the hourly rate. The rate established by the parties is retroactive to the time when the change took effect. If the parties cannot arrive at an agreement within the period mentioned above, the matter will be referred to Step Three of the Grievance Procedure.
AutoNDA by SimpleDocs
Changing Existing Jobs. Prior to the Company substantially changing an existing job, the Com- pany will meet with the Union to discuss the subject. Either prior to or within ninety (90) working days of the change, the parties shall meet to establish the hourly rate. The rate established by the parties is retroactive to the time when the change took effect. If the parties cannot arrive at an agreement within the period mentioned above, the matter will be referred to Step Three of the Grievance Pro- cedure.

Related to Changing Existing Jobs

  • Billing Increments Unless otherwise stated in a Service Order, usage-based charges will be billed on either a per-minute or per- message basis. Service calls invoiced on a per-minute basis will have an initial minimum call duration of one (1) minute, subsequent intervals of one (1) minute each, and will be billed by rounding to the next whole minute.

  • Red Hat Enterprise Linux Server Add-Ons Red Hat Enterprise Linux Server Subscriptions may be purchased with one or more add-on options (“Add-On(s)”). Add-Ons require a separate paid and active Software Subscriptions for each Unit that deploys, installs, uses or executes such Add-On. Each Unit of Add- Ons must match the Support Level (Standard and/or Premium), Unit of Measure and capacity as the underlying Red Hat Enterprise Linux Unit. Add-Ons are not supported on Red Hat Enterprise Linux Subscriptions with a Self-support service level except Smart Management Add-Ons. The Add-Ons include: High Availability, Load Balancer, Resilient Storage, Scalable File System, Smart Management, Extended Update Support, Extended Life Cycle Support and High Performance Network.

  • Contract Transition Upon Contract expiration or termination, the Contractor shall ensure a seamless transfer of Contract responsibilities with any subsequent Contractor necessary to transition the Products and services of the Contract. The incumbent Contractor assumes all expenses related to the contract transition.

  • Tax Increment Financing The Redevelopment Agreement provides for the capture of the Tax Increment, as defined therein, by the City of the Redeveloper Improvements to be made by the Redeveloper for a period not to exceed fifteen (15) years after the Redevelopment Project effective date defined in the Redevelopment Agreement. The Tax Increment so captured by the City shall be used for to make the Redeveloper Improvements as described in the Redevelopment Agreement.

  • Ongoing Trunk Forecast Requirements Where the Parties have already established interconnection in a LATA, Onvoy shall provide a new or revised traffic forecast that complies with the Frontier Interconnection Trunking Forecast Guide when Xxxxx develops plans or becomes aware of information that will materially affect the Parties’ interconnection in that LATA. Instances that require a new or revised forecast include, but are not limited to: (a) Onvoy plans to deploy a new switch; (b) Onvoy plans to implement a new POI or network architecture; (c) Onvoy plans to rearrange its network; (d) Onvoy plans to convert a One-Way Interconnection Trunk group to a Two-Way Interconnection Trunk group; (e) Onvoy plans to convert a Two-Way Interconnection Trunk group to a One-Way Interconnection Trunk group; or (f) Onvoy expects a significant change in interconnection traffic volume. In addition, upon request by either Party, the Parties shall meet to: (i) review traffic and usage data on End Office and Tandem Interconnection Trunk groups and (ii) determine whether the Parties should establish new Interconnection Trunk groups, augment existing Interconnection Trunk groups, or disconnect existing Interconnection Trunks.

  • Red Hat Enterprise Linux Desktop Software Subscriptions Software Subscriptions for Red Hat Enterprise Linux Desktops and Workstations are subject to the parameters set forth in Table 6 below. Each Red Hat Enterprise Linux Desktop and Workstation Software Subscription includes one Red Hat Network system entitlement and one Smart Management Module, each to be used solely with a single Red Hat Enterprise Linux Desktop or Workstation System. Production Support for Red Hat Enterprise Linux Desktop subscriptions is limited to web-based support only for your helpdesk support personnel. Red Hat is not obligated to support your end users directly.

  • MASTER CONTRACT TRANSITION Contractor represents and warrants that, in the event this Master Contract or a similar contract, is transitioned to another contractor (e.g., Master Contract expiration or termination), Contractor shall use commercially reasonable efforts to assist Enterprise Services for a period of sixty (60) days to effectuate a smooth transition to another contractor to minimize disruption of service and/or costs to the State of Washington.

  • SPECIAL TEACHING ASSIGNMENTS A. Assignments for the Adult Education, Driver Education and Summer School Program will be made by the Board on the basis of preference to teachers possessing permanent teaching certificates regularly employed in the district during the normal school year.

  • Cooperative Purchasing Pursuant to their own governing laws, and subject to the agreement of the Contractor, governmental entities that are not Customers may make purchases under the terms and conditions contained herein, if agreed to by Contractor. Such purchases are independent of the Contract between the Department and the Contractor, and the Department is not a party to these transactions. Agencies seeking to make purchases under this Contract are required to follow the requirements of Rule 60A-1.045(5), F.A.C.

  • Cooperative Contract The provisions and pricing of this Contract will be extended to other California local or state governmental entities. Governmental entities wishing to use this Contract will be responsible for issuing their own purchase documents/price agreements, providing for their own acceptance, and making any subsequent payments. Contractor shall be required to include in any Contract entered into with another agency or entity that is entered into as an extension of this Contract a Contract clause that will hold harmless the County of Orange from all claims, demands, actions or causes of actions of every kind resulting directly or indirectly, arising out of, or in any way connected with the use of this contract. Failure to do so will be considered a material breach of this Contract and grounds for immediate Contract termination. The cooperative entities are responsible for obtaining all certificates of insurance and bonds required. The Contractor is responsible for providing each cooperative entity a copy of the Contract upon request by the cooperative entity. The County of Orange makes no guarantee of usage by other users of this Contract. The Contractor shall be required to maintain a list of the cooperative entities using this Contract. The list shall report dollar volumes spent annually and shall be provided on an annual basis to the County, at the County’s request.

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