Assignment of Overtime 3.4.1 Overtime shall be assigned on a rotating seniority basis among all qualified employees who are in the same classification, the same organizational unit, and at the same work location. An employee may decline an overtime assignment without adverse consequence unless it is assigned pursuant to Section 3.4.2 below. The department may define the group of qualified employees by their shift for purposes of assigning overtime so that call back pay is not obligated. In order to determine if an employee is qualified, the department should consider the employee’s work record in the department, including being in an unsatisfactory status on a current evaluation or having a formal discipline action in process.
3.4.2 If no employee in the classification, organization unit and work location accepts the overtime assignment, using the rotating seniority process, the District may assign the overtime in reverse rotating seniority order.
3.4.3 The following are allowable exceptions to the seniority overtime assignment process: When overtime is authorized for completion of a specific assignment, project, or work in progress, the employee who began the assignment, project, or work may be assigned the overtime; When the District determines it is necessary to consider special skills and training of employees to perform particular work; When employees are available to perform the work on a non-over-time basis, the District shall not be required to assign the work on an overtime basis. Overtime pay assignments will not be given to temporary employees unless the regular employees that would normally be assigned the overtime are not available or one of the seniority exceptions apply.
3.4.4 All overtime shall be offered to everyone on the applicable overtime list in descending order of seniority until the list is exhausted. Once the last name on the list is reached the process will resume from the top of the list. If an employee is offered overtime for a scheduled project and declines to accept, the employee forfeits his/her turn in the rotation. That employee will not be offered overtime until the list has been completed and his/her name comes up again in order of seniority.
3.4.5 Notice of scheduled overtime, for situations that are recurring or have advance notice, and which are offered on a rotational basis shall be posted in the same area as all required employment notices and announcements and will remain up until the work has been completed. Posting shall be on a form agreed to by the District and CSEA. Employee responses to the overtime posting shall be on a form agreed to by the District and CSEA. In lieu of posting, an organizational work unit may use electronic communications when all employees in such unit regularly use electronic communication. All such notices whether posted or sent by electronic communication will contain a description of the work to be done, the anticipated length of time to accomplish the work, the date(s) on which the work will be scheduled, and the date and time of posting. The notice shall be posted within a reasonable time of the District learning of the overtime work. Records will be maintained of all notices, employee responses, and overtime assignments for a period of three years.
Assignment to Owners Interconnection Customer may assign the Interconnection Service Agreement without the Interconnected Transmission Owner’s or Transmission Provider’s prior consent to any Affiliate or person that purchases or otherwise acquires, directly or indirectly, all or substantially all of the Customer Facility and the Customer Interconnection Facilities, provided that prior to the effective date of any such assignment, the assignee shall demonstrate that, as of the effective date of the assignment, the assignee has the technical and operational competence to comply with the requirements of this Interconnection Service Agreement and assumes in a writing provided to the Interconnected Transmission Owner and Transmission Provider all rights, duties, and obligations of Interconnection Customer arising under this Interconnection Service Agreement. However, any assignment described herein shall not relieve or discharge the Interconnection Customer from any of its obligations hereunder absent the written consent of the Transmission Provider, such consent not to be unreasonably withheld, conditioned or delayed.
Assignment of Benefits Neither the Participant nor any other beneficiary under the Plan shall have any right to assign the right to receive any benefits hereunder, and in the event of any attempted assignment or transfer, the Company shall have no further liability hereunder.
Assignment of Overtime Work (a) Subject to the operational requirements, the Employer shall make every reasonable effort to avoid excessive overtime and to offer overtime work on an equitable basis among readily available qualified employees.
(b) Except in cases of emergency, call-back, or mutual agreement with the employee, the Employer shall, wherever possible, give at least four (4) hours’ notice of any requirement for overtime work.
Notification of Non-payment The Global Agent shall forthwith notify Xxxxxxx Mac by facsimile, e-mail or other rapid means of communication if it has not received the full amount for any payment due in respect of the Notes on the date such payment is due. The Global Agent shall have no liability, responsibility, duty or obligation to any Holder or beneficial owner of Notes to take any action against Issuer in the event that Issuer fails to make available funds sufficient to pay amounts due and payable and owing to any Holder on any Payment Date. The Global Agent shall give issuance instructions to DTC in accordance with DTC’s procedures.
Assignment and Benefit (a) This Agreement is personal to the Manager and shall not be assignable by the Manager, by operation of law, or otherwise without the prior written consent of the Company otherwise than by will or the laws of descent and distribution. This Agreement shall inure to the benefit of and be enforceable by the Manager’s heirs and legal representatives.
(b) This Agreement shall inure to the benefit of and be binding upon the Company and its successors and assigns, including, without limitation, any subsidiary of the Company to which the Company may assign any of its rights hereunder; provided, however, that no assignment of this Agreement by the Company, by operation of law, or otherwise shall relieve it of its obligations hereunder except an assignment of this Agreement to, and its assumption by, a successor pursuant to subsection (c).
(c) The Company shall require any successor (whether direct or indirect, by purchase, merger, consolidation, operation of law, or otherwise) to all or substantially all of the business and/or assets of the Company to assume expressly and agree to perform this Agreement in the same manner and to the same extent that the Company would be required to perform it if no such succession had taken place, but, irrespective of any such assignment or assumption, this Agreement shall inure to the benefit of and be binding upon such a successor. As used in this Agreement, “Company” shall mean the Company as hereinbefore defined and any successor to its business and/or assets as aforesaid.
Assignment; Benefit This Agreement is personal and may not be assigned by Employee. This Agreement may be assigned by Employer and shall inure to the benefit of and be binding upon the successors and assigns of Employer.
Payments by Wire-Transfer All payments under this Single Family Shared-Loss Agreement shall be made by wire-transfer in accordance with the wire-transfer instructions on Exhibit 4.
Assignment and Transfer The Member may assign or transfer in whole but not in part its limited liability company interest to a single acquiror.
Change of Control; Assignment and Subcontracting Except as set forth in this Section 7.5, neither party may assign any of its rights and obligations under this Agreement without the prior written approval of the other party, which approval will not be unreasonably withheld. For purposes of this Section 7.5, a direct or indirect change of control of Registry Operator or any subcontracting arrangement that relates to any Critical Function (as identified in Section 6 of Specification 10) for the TLD (a “Material Subcontracting Arrangement”) shall be deemed an assignment.
(a) Registry Operator must provide no less than thirty (30) calendar days advance notice to ICANN of any assignment or Material Subcontracting Arrangement, and any agreement to assign or subcontract any portion of the operations of the TLD (whether or not a Material Subcontracting Arrangement) must mandate compliance with all covenants, obligations and agreements by Registry Operator hereunder, and Registry Operator shall continue to be bound by such covenants, obligations and agreements. Registry Operator must also provide no less than thirty (30) calendar days advance notice to ICANN prior to the consummation of any transaction anticipated to result in a direct or indirect change of control of Registry Operator.
(b) Within thirty (30) calendar days of either such notification pursuant to Section 7.5(a), ICANN may request additional information from Registry Operator establishing (i) compliance with this Agreement and (ii) that the party acquiring such control or entering into such assignment or Material Subcontracting Arrangement (in any case, the “Contracting Party”) and the ultimate parent entity of the Contracting Party meets the ICANN-‐adopted specification or policy on registry operator criteria then in effect (including with respect to financial resources and operational and technical capabilities), in which case Registry Operator must supply the requested information within fifteen (15) calendar days.
(c) Registry Operator agrees that ICANN’s consent to any assignment, change of control or Material Subcontracting Arrangement will also be subject to background checks on any proposed Contracting Party (and such Contracting Party’s Affiliates).
(d) If ICANN fails to expressly provide or withhold its consent to any assignment, direct or indirect change of control of Registry Operator or any Material Subcontracting Arrangement within thirty (30) calendar days of ICANN’s receipt of notice of such transaction (or, if ICANN has requested additional information from Registry Operator as set forth above, thirty (30) calendar days of the receipt of all requested written information regarding such transaction) from Registry Operator, ICANN shall be deemed to have consented to such transaction.
(e) In connection with any such assignment, change of control or Material Subcontracting Arrangement, Registry Operator shall comply with the Registry Transition Process.
(f) Notwithstanding the foregoing, (i) any consummated change of control shall not be voidable by ICANN; provided, however, that, if ICANN reasonably determines to withhold its consent to such transaction, ICANN may terminate this Agreement pursuant to Section 4.3(g), (ii) ICANN may assign this Agreement without the consent of Registry Operator upon approval of the ICANN Board of Directors in conjunction with a reorganization, reconstitution or re-‐incorporation of ICANN upon such assignee’s express assumption of the terms and conditions of this Agreement, (iii) Registry Operator may assign this Agreement without the consent of ICANN directly to a wholly-‐owned subsidiary of Registry Operator, or, if Registry Operator is a wholly-‐owned subsidiary, to its direct parent or to another wholly-‐owned subsidiary of its direct parent, upon such subsidiary’s or parent’s, as applicable, express assumption of the terms and conditions of this Agreement, and (iv) ICANN shall be deemed to have consented to any assignment, Material Subcontracting Arrangement or change of control transaction in which the Contracting Party is an existing operator of a generic top-‐level domain pursuant to a registry agreement between such Contracting Party and ICANN (provided that such Contracting Party is then in compliance with the terms and conditions of such registry agreement in all material respects), unless ICANN provides to Registry Operator a written objection to such transaction within ten (10) calendar days of ICANN’s receipt of notice of such transaction pursuant to this Section 7.5. Notwithstanding Section 7.5(a), in the event an assignment is made pursuant to clauses (ii) or (iii) of this Section 7.5(f), the assigning party will provide the other party with prompt notice following any such assignment.
