Employees on Long Term Supply Assignments Employees completing long term supply assignments may only access sick leave and short term disability leave in the fiscal year in which the allocation was provided. Any remaining allocation may be used in subsequent long term supply assignments, provided these occur within the same fiscal year. Employees employed in a Long Term Supply Assignment which is less than the ordinary period of employment for the position shall have their sick leave and short term disability allocations pro-rated accordingly. Where the length of the long term supply assignment is not known in advance, a projected length must be determined at the start of the assignment in order for the appropriate allocation of sick leave/short term disability leave to occur. If a change is made to the length of the assignment, an adjustment will be made to the allocation and applied retroactively.
No Assignment of Benefits The rights of any person to payments or benefits under this Agreement shall not be made subject to option or assignment, either by voluntary or involuntary assignment or by operation of law, including (without limitation) bankruptcy, garnishment, attachment or other creditor’s process, and any action in violation of this subsection shall be void.
Exclusive Employment During employment with the Company, Executive will not do anything to compete with the Company’s present or contemplated business, nor will he plan or organize any competitive business activity. Executive will not enter into any agreement which conflicts with his duties or obligations to the Company. Executive will not during his employment or within one (1) year after it ends, without the Company’s express written consent, directly or indirectly, solicit or encourage any employee, agent, independent contractor, supplier, customer, consultant or any other person or company to terminate or alter a relationship with the Company.
Non-Assignment of Agreement The Grantee may not assign, sublicense or otherwise transfer its rights, duties or obligations under this Agreement without the prior written consent of the Division, which shall not unreasonably be withheld. The agreement transferee must demonstrate compliance with the requirements of the project. If the Division approves a transfer of the Grantee’s obligations, the Grantee shall remain liable for all work performed and all expenses incurred in connection with this Agreement. In the event the Legislature transfers the rights, duties and obligations of the Division to another governmental entity, pursuant to Section 20.06, Florida Statutes or otherwise, the rights, duties and obligations under this Agreement shall be transferred to the succeeding governmental agency as if it was the original party to this Agreement.
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.
Term and Termination; Assignment; Amendment (a) This Agreement shall be effective for the duration of the Acquired Funds’ and the Acquiring Funds’ reliance on the Rule. While the terms of the Agreement shall only be applicable to investments in Acquired Funds made in reliance on the Rule, the Agreement shall continue in effect until terminated pursuant to Section 9(b). . (b) This Agreement shall continue until terminated in writing by either party upon 60 days’ notice to the other party. Termination of this Agreement with respect to a particular Acquired Fund shall not terminate the Agreement as to other Acquired Funds that are parties hereto. Upon termination of this Agreement with respect to an Acquired Fund or at any time an Acquired Fund is designated as an Ineligible Fund, the Acquiring Fund may not purchase additional shares of the Acquired Fund beyond the Section 12(d)(1)(A) limits in reliance on the Rule. For purposes of clarity, upon termination of the Agreement with respect to an Acquired Fund or upon an Acquired Fund being designated as an Ineligible Fund, the Acquiring Fund shall not be required to reduce its holdings of the respective Acquired Fund. (c) If this Agreement is terminated pursuant to Section 9(b) hereof, the obligations of an Acquiring Fund set forth in Section 1(a)(ii)(1) hereof shall survive and remain continuing obligations of the Acquiring Fund so long as the Acquiring Fund holds shares of an Acquired Fund that were acquired in reliance on the Rule and pursuant to this Agreement. (d) This Agreement may not be assigned by either party without the prior written consent of the other. (e) Other than as set forth in Sections 3(e), 6 and 7 above and Schedule B hereto, this Agreement may be amended only by a writing that is signed by each affected party. (f) The Acquiring Funds and the Acquired Funds may file a copy of this Agreement with the SEC or any other regulatory body if required by applicable law. (g) With respect to any Acquiring Fund or Acquired Fund organized as a Massachusetts business trust or a series thereof (each such trust, a “Massachusetts Trust”), a copy of the Declaration of Trust of each Massachusetts Trust is on file with the Secretary of The Commonwealth of Massachusetts, and notice is hereby given that this Agreement is executed on behalf of each Massachusetts Trust by an officer of the Trust in his or her capacity as an officer of the Trust and not individually and that no trustee, officer, employee, agent, employee or shareholder of a Massachusetts Trust shall have any personal liability under this Agreement.
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.
Complete Disposal Upon Termination of Service Agreement Upon Termination of the Service Agreement Provider shall dispose or delete all Student Data obtained under the Service Agreement. Prior to disposition of the data, Provider shall notify LEA in writing of its option to transfer data to a separate account, pursuant to Article II, section 3, above. In no event shall Provider dispose of data pursuant to this provision unless and until Provider has received affirmative written confirmation from LEA that data will not be transferred to a separate account.
