RT Involvement Sample Clauses
Related to RT Involvement
Role The Custodian, as agent of the Participant, but not as fiduciary, shall take, hold, invest, and distribute all of the assets of the Fund in accordance with the terms of this Agreement. The Custodian will serve as a non-discretionary, directed custodian of the Custodial Account. The Custodian is responsible for maintaining custody of the assets held in the Custodial Account, and for investing those assets as directed by the Program Sponsor on behalf of the Participant. The Custodian (in its capacity as such) will not be an administrative or investment fiduciary of the Plan, and nothing in this Agreement is to be interpreted as causing the Custodian to be responsible for the administration or investment of the Fund other than as directed by the Program Sponsor hereunder, or as performing other than ministerial duties. The Custodian may refuse to exercise any power that it believes, in its sole judgment, could cause it to become a “fiduciary” or “plan administrator” as defined under ERISA, or cause it to be exercising trust powers in contravention of any state or federal law to which it may be subject. The Custodian shall have no responsibility to draft or amend a plan document for the Plan, to administer the Plan, or to assist the Employer or the Program Sponsor in such drafting, amendment, administration, or maintenance, or to ascertain or provide advice with respect to the legal requirements applicable thereto except to the extent of any responsibility imposed upon the Custodian pursuant to the terms of this Agreement. The Program Sponsor and the Employer represent and warrant to the Custodian that the Plan shall be maintained by the Employer in writing and in compliance with Code Section 457(b) and the Treasury Regulations issued under Code Section 457(b).
Negotiation Process (a) If either the Chief Executive Officer of ICANN (“CEO”) or the Chairperson of the Registry Stakeholder Group (“Chair”) desires to discuss any revision(s) to this Agreement, the CEO or Chair, as applicable, shall provide written notice to the other person, which shall set forth in reasonable detail the proposed revisions to this Agreement (a “Negotiation Notice”). Notwithstanding the foregoing, neither the CEO nor the Chair may (i) propose revisions to this Agreement that modify any Consensus Policy then existing, (ii) propose revisions to this Agreement pursuant to this Section 7.7 on or before June 30, 2014, or (iii) propose revisions or submit a Negotiation Notice more than once during any twelve (12) month period beginning on July 1, 2014. (b) Following receipt of the Negotiation Notice by either the CEO or the Chair, ICANN and the Working Group (as defined in Section 7.6) shall consult in good faith negotiations regarding the form and substance of the proposed revisions to this Agreement, which shall be in the form of a proposed amendment to this Agreement (the “Proposed Revisions”), for a period of at least ninety (90) calendar days (unless a resolution is earlier reached) and attempt to reach a mutually acceptable agreement relating to the Proposed Revisions (the “Discussion Period”). (c) If, following the conclusion of the Discussion Period, an agreement is reached on the Proposed Revisions, ICANN shall post the mutually agreed Proposed Revisions on its website for public comment for no less than thirty (30) calendar days (the “Posting Period”) and provide notice of such revisions to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval (as defined in Section 7.6) and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (d) If, following the conclusion of the Discussion Period, an agreement is not reached between ICANN and the Working Group on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (the “Mediation Notice”) requiring each party to attempt to resolve the disagreements related to the Proposed Revisions through impartial, facilitative (non-‐evaluative) mediation in accordance with the terms and conditions set forth below. In the event that a Mediation Notice is provided, ICANN and the Working Group shall, within fifteen (15) calendar days thereof, simultaneously post the text of their desired version of the Proposed Revisions and a position paper with respect thereto on ICANN’s website. (i) The mediation shall be conducted by a single mediator selected by the parties. If the parties cannot agree on a mediator within fifteen (15) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the parties will promptly select a mutually acceptable mediation provider entity, which entity shall, as soon as practicable following such entity’s selection, designate a mediator, who is a licensed attorney with general knowledge of contract law, who has no ongoing business relationship with either party and, to the extent necessary to mediate the particular dispute, general knowledge of the domain name system. Any mediator must confirm in writing that he or she is not, and will not become during the term of the mediation, an employee, partner, executive officer, director, or security holder of ICANN or an Applicable Registry Operator. If such confirmation is not provided by the appointed mediator, then a replacement mediator shall be appointed pursuant to this Section 7.7(d)(i). (ii) The mediator shall conduct the mediation in accordance with the rules and procedures for facilitative mediation that he or she determines following consultation with the parties. The parties shall discuss the dispute in good faith and attempt, with the mediator’s assistance, to reach an amicable resolution of the dispute. (iii) Each party shall bear its own costs in the mediation. The parties shall share equally the fees and expenses of the mediator. (iv) If an agreement is reached during the mediation, ICANN shall post the mutually agreed Proposed Revisions on its website for the Posting Period and provide notice to all Applicable Registry Operators in accordance with Section 7.9. ICANN and the Working Group will consider the public comments submitted on the agreed Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators). Following the conclusion of the Posting Period, the Proposed Revisions shall be submitted for Registry Operator Approval and approval by the ICANN Board of Directors. If such approvals are obtained, the Proposed Revisions shall be deemed an Approved Amendment (as defined in Section 7.6) by the Applicable Registry Operators and ICANN, and shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator. (v) If the parties have not resolved the dispute for any reason by the date that is ninety (90) calendar days following receipt by the CEO or Chair, as applicable, of the Mediation Notice, the mediation shall automatically terminate (unless extended by agreement of the parties). The mediator shall deliver to the parties a definition of the issues that could be considered in future arbitration, if invoked. Those issues are subject to the limitations set forth in Section 7.7(e)(ii) below. (e) If, following mediation, ICANN and the Working Group have not reached an agreement on the Proposed Revisions, either the CEO or the Chair may provide the other person written notice (an “Arbitration Notice”) requiring ICANN and the Applicable Registry Operators to resolve the dispute through binding arbitration in accordance with the arbitration provisions of Section 5.2, subject to the requirements and limitations of this Section 7.7(e). (i) If an Arbitration Notice is sent, the mediator’s definition of issues, along with the Proposed Revisions (be those from ICANN, the Working Group or both) shall be posted for public comment on ICANN’s website for a period of no less than thirty (30) calendar days. ICANN and the Working Group will consider the public comments submitted on the Proposed Revisions during the Posting Period (including comments submitted by the Applicable Registry Operators), and information regarding such comments and consideration shall be provided to a three (3) person arbitrator panel. Each party may modify its Proposed Revisions before and after the Posting Period. The arbitration proceeding may not commence prior to the closing of such public comment period, and ICANN may consolidate all challenges brought by registry operators (including Registry Operator) into a single proceeding. Except as set forth in this Section 7.7, the arbitration shall be conducted pursuant to Section 5.2. (ii) No dispute regarding the Proposed Revisions may be submitted for arbitration to the extent the subject matter of the Proposed Revisions (i) relates to Consensus Policy, (ii) falls within the subject matter categories set forth in Section 1.2 of Specification 1, or (iii) seeks to amend any of the following provisions or Specifications of this Agreement: Articles 1, 3 and 6; Sections 2.1, 2.2, 2.5, 2.7, 2.9, 2.10, 2.16, 2.17, 2.19, 4.1, 4.2, 7.3, 7.6, 7.7, 7.8, 7.10, 7.11, 7.12, 7.13, 7.14, 7.16; Section 2.8 and Specification 7 (but only to the extent such Proposed Revisions seek to implement an RPM not contemplated by Sections 2.8 and Specification 7); Exhibit A; and Specifications 1, 4, 6, 10 and 11. (iii) The mediator will brief the arbitrator panel regarding ICANN and the Working Group’s respective proposals relating to the Proposed Revisions. (iv) No amendment to this Agreement relating to the Proposed Revisions may be submitted for arbitration by either the Working Group or ICANN, unless, in the case of the Working Group, the proposed amendment has received Registry Operator Approval and, in the case of ICANN, the proposed amendment has been approved by the ICANN Board of Directors. (v) In order for the arbitrator panel to approve either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions, the arbitrator panel must conclude that such proposed amendment is consistent with a balanced application of ICANN’s core values (as described in ICANN’s Bylaws) and reasonable in light of the balancing of the costs and benefits to the business interests of the Applicable Registry Operators and ICANN (as applicable), and the public benefit sought to be achieved by the Proposed Revisions as set forth in such amendment. If the arbitrator panel concludes that either ICANN or the Working Group’s proposed amendment relating to the Proposed Revisions meets the foregoing standard, such amendment shall be effective and deemed an amendment to this Agreement upon sixty (60) calendar days notice from ICANN to Registry Operator and deemed an Approved Amendment hereunder. (f) With respect to an Approved Amendment relating to an amendment proposed by ICANN, Registry may apply in writing to ICANN for an exemption from such amendment pursuant to the provisions of Section 7.6. (g) Notwithstanding anything in this Section 7.7 to the contrary, (a) if Registry Operator provides evidence to ICANN's reasonable satisfaction that the Approved Amendment would materially increase the cost of providing Registry Services, then ICANN will allow up to one-‐hundred eighty (180) calendar days for the Approved Amendment to become effective with respect to Registry Operator, and (b) no Approved Amendment adopted pursuant to Section 7.7 shall become effective with respect to Registry Operator if Registry Operator provides ICANN with an irrevocable notice of termination pursuant to Section 4.4(b).
Independent Activities 14.1 Except as expressly provided herein, each party shall have the free and unrestricted right to independently engage in and receive the full benefit of any and all business endeavours of any sort whatsoever, whether or not competitive with the endeavours contemplated herein without consulting the other or inviting or allowing the other to participate therein. No party shall be under any fiduciary or other duty to the other which will prevent it from engaging in or enjoying the benefits of competing endeavours within the general scope of the endeavours contemplated herein. The legal doctrines of "corporate opportunity" sometimes applied to persons engaged in a joint venture or having fiduciary status shall not apply in the case of any party. In particular, without limiting the foregoing, no party shall have any obligation to any other party as to: (a) any opportunity to acquire, explore and develop any mining property, interest or right presently owned by it or offered to it outside of the Property at any time; and (b) the erection of any mining plant, mill, smelter or refinery, whether or not such mining plant, mill, smelter or refinery treats ores or concentrates from the Property.
Joint Work Product This Agreement is the joint work product of H-GAC and the Contractor. This Agreement has been negotiated by H-GAC and the Contractor and their respective counsel and shall be fairly interpreted in accordance with its terms and, in the event of any ambiguities, no inferences shall be drawn against any party.
Cooperation of the Parties The Seller undertakes to notify the Buyer of any obstacles on his part, which may negatively influence proper and timely delivery of the Equipment.
Development Activities The Development activities referred to in item “b” of paragraph 3.1 include: studies and projects of implementation of the Production facilities; drilling and completion of the Producing and injection xxxxx; and installation of equipment and vessels for extraction, collection, Treatment, storage, and transfer of Oil and Gas. The installation referred to in item “c” includes, but is not limited to, offshore platforms, pipelines, Oil and Gas Treatment plants, equipment and facilities for measurement of the inspected Production, wellhead equipment, production pipes, flow lines, tanks, and other facilities exclusively intended for extraction, as well as oil and gas pipelines for Production Outflow and their respective compressor and pumping stations.
RELATIONSHIP BETWEEN THE PARTIES A Party is not by virtue of this Agreement the employee, agent or partner of the other Party and is not authorised to bind or represent the other Party.
Consultation Process (a) Unless the expedited process in clause 3.4 applies, the Operator must follow the process set out below for consulting on a proposal to amend this agreement. (b) The notice to be published under clause 3.2(b)(ii) must invite Members and other interested persons to submit written comments on the proposal to the Operator on or before a date specified in the notice (which must be at least 20 Business Days after the date of the notice). (c) If the Operator considers it appropriate having regard to issues raised in submissions, it may undertake further consultation on specified issues or alternative proposals, and the notice and minimum time periods in paragraph (b) apply to that further consultation. (d) The Operator must publish its decision on the proposal on its website within 20 Business Days after the closing date for submissions under paragraph (b) or (d) as applicable. The decision must: (i) summarise any comments received on the proposal; (ii) set out the proposed amendment to be made (if any); (iii) if the proposed amendment is materially different from the original proposal, describe how and why the proposal has been revised; (iv) if the decision is to make a proposed amendment then specify the day on which the amendment is to take effect; and (v) if the decision is against making any proposed amendment, state that the proposal has been rejected and give reasons for the rejection. (e) At least 15 Business Days before the day on which any amendment is to take effect, or an earlier date fixed by this agreement in any particular case, the Operator must: (i) notify all Members and the AER of the amendment; and (ii) publish the amendment and the amended Exchange Agreement on its website. (f) In determining whether or not to make an amendment under this provision, the Operator must take into account all relevant and material comments that it receives by the closing date for comments and may take into account any comments it receives after that date.
Coordinator 6.4.1 The Coordinator shall be the intermediary between the Parties and the Funding Authority and shall perform all tasks assigned to it as described in the Grant Agreement and in this Consortium Agreement. 6.4.2 In particular, the Coordinator shall be responsible for: - monitoring compliance by the Parties with their obligations - keeping the address list of Members and other contact persons updated and available - collecting, reviewing and submitting information on the progress of the Project and reports and other deliverables (including financial statements and related certification) to the Funding Authority - preparing the meetings, proposing decisions and preparing the agenda of General Assembly meetings, chairing the meetings, preparing the minutes of the meetings and monitoring the implementation of decisions taken at meetings - transmitting promptly documents and information connected with the Project,, - administering the financial contribution of the Funding Authority and fulfilling the financial tasks described in Section 7.3 - providing, upon request, the Parties with official copies or originals of documents which are in the sole possession of the Coordinator when such copies or originals are necessary for the Parties to present claims. If one or more of the Parties is late in submission of any project deliverable, the Coordinator may nevertheless submit the other parties’ project deliverables and all other documents required by the Grant Agreement to the Funding Authority in time. 6.4.3 If the Coordinator fails in its coordination tasks, the General Assembly may propose to the Funding Authority to change the Coordinator. 6.4.4 The Coordinator shall not be entitled to act or to make legally binding declarations on behalf of any other Party or of the consortium, unless explicitly stated otherwise in the Grant Agreement or this Consortium Agreement. 6.4.5 The Coordinator shall not enlarge its role beyond the tasks specified in this Consortium Agreement and in the Grant Agreement. [Option: 6.5 Management Support Team (Optional, where foreseen in Grant Agreement or otherwise decided by the consortium) The Management Support Team shall be proposed by the Coordinator. It shall be appointed by the General Assembly and shall assist and facilitate the work of the General Assembly. The Management Support Team shall provide assistance to the Coordinator for executing the decisions of the General Assembly. It shall be responsible for the day-to-day management of the Project.] [Option: 6.6 External Expert Advisory Board (EEAB) (Optional, where foreseen in Grant Agreement or otherwise decided by the consortium) An External Expert Advisory Board (EEAB) will be appointed and steered by the Executive Board. The EEAB shall assist and facilitate the decisions made by the General Assembly. The Coordinator is authorised to execute with each member of the EEAB a non-disclosure agreement, which terms shall be not less stringent than those stipulated in this Consortium Agreement, no later than 30 days after their nomination or before any confidential information will be exchanged, whichever date is earlier. The Coordinator shall write the minutes of the EEAB meetings and prepare the implementation of the EEAB's suggestions. The EEAB members shall be allowed to participate in General Assembly meetings upon invitation but have not any voting rights.]
INDEPENDENT RELATIONSHIP This Agreement is not intended to constitute, create, give effect to or otherwise recognize a joint venture, partnership, or formal business organization, or agency agreement of any kind, and the rights and obligations of the Parties shall be only those expressly set forth herein.
