EBERO Event Team Organizational Structure and Composition Sample Clauses

EBERO Event Team Organizational Structure and Composition. The EBERO Event Team is a cross-functional team led by the ICANN Technical Services Team, but working with staff from multiple ICANN organization departments, partnering with designated registry service provider organizations . These registry service providers and staff have been designated as having responsibility to perform tasks involved in the emergency transition of a new gTLD registry in response to an emergency or imminent failure of critical registry services. EBERO Event Teams only exist in response to emergencies (including, but not limited to, tests of emergency response capabilities and real and simulated registry failure scenarios) and thus are created on an as-needed basis as circumstances warrant. In the event of multiple registry failures, ICANN may request an EBERO to execute the transition process for one or more Failed TLDs (as defined in the Emergency Back-End Registry Operator Agreement between ICANN and the EBERO (the “EBERO Master Agreement”) to which this Exhibit is attached). In such a circumstance, ICANN will perform a triage process to establish the order of transition for the Failed TLDs. In the event of more than one TLD failure, ICANN will provide a prioritized list to the appointed EBERO accompanied by the estimated number of domains under management for each Failed TLD. The appointed EBERO will communicate which and how many of the Failed TLDs for which EBERO services are needed that it can support for such event. Should there be more Failed TLDs for which EBERO services are needed than the appointed EBERO can support, ICANN will appoint additional appointed EBEROs to support the remainder of the applicable Failed TLDs. In such an event, ICANN may also designate additional Event Directors to coordinate the EBERO Event across multiple EBEROs. ICANN does not expect that any direct coordination between EBEROs will be required. EBERO Operator ICANN Global Support EBERO Program Sr. Specialist ICANN 24x7 Monitoring EBERO Program Technical Advisor Event Manager Event Director EBERO Executive Committee
AutoNDA by SimpleDocs
EBERO Event Team Organizational Structure and Composition. ‌ The EBERO Event Team is a cross-functional team from multiple ICANN staff departments, partnering with designated registry service provider organizations. These registry service providers and staff have been designated as having responsibility to perform tasks involved in the emergency transition of a new gTLD registry in response to an emergency or imminent failure of critical registry services. EBERO Event Teams only exist in response to emergencies (including, but not limited to, tests of emergency response capabilities, real and simulated registry failure scenarios), and thus are created on an as-needed basis as circumstances warrant. Event Manager Team Leaders Team Members EBERO Operator EBERO Event Team Compliance Registry Technical Liaison Communications Security Production IT Ops Event Director Event Steering Committee Figure 2: EBERO Event Team Organization 1.3.1 Event Steering Committee‌ A subset of ICANN executives and management, acting in concert, will collectively be known as the Executive Steering Committee and will select and authorize an individual to act as the Event Director. This steering committee will delegate sufficient authority so that the Event Director can (as the situation warrants) authorize necessary EBERO activities. The Event Steering Committee will include the following ICANN staff: 1. President, Generic Domains Division 2. General Counsel

Related to EBERO Event Team Organizational Structure and Composition

  • Formation and Composition The Parties to this agreement will maintain a Joint Administration and Dispute Resolution Committee (JADRC) consisting of five (5) representatives of the employers and five (5) representatives of the Provincial Bargaining Council.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

  • Board Composition and Board Designations The Company shall ensure that: (i) the qualifications of the persons serving as members of the Board of Directors and the overall composition of the Board comply with the Sxxxxxxx-Xxxxx Act, with the Exchange Act and with the listing rules of the Exchange or any other national securities exchange, as the case may be, in the event the Company seeks to have its Public Securities listed on another exchange or quoted on an automated quotation system, and (ii) if applicable, at least one member of the Audit Committee of the Board of Directors qualifies as an “audit committee financial expert,” as such term is defined under Regulation S-K and the listing rules of the Exchange.

  • Organizational Structure The ISO will be governed by a ten (10) person unaffiliated Board of Directors, as per Article 5 herein. The day-to-day operation of the ISO will be managed by a President, who will serve as an ex-officio member of the ISO Board, in accordance with Article 5 herein. There shall be a Management Committee as per Article 7 herein, which shall report to the ISO Board, and shall be comprised of all Parties to the Agreement. There shall be at least two additional standing committees, the Operating Committee, as provided for in Article 8, and the Business Issues Committee, as provided for in Article 9, both of which shall report to the Management Committee. A Dispute Resolution Process will be established and administered by the ISO Board in accordance with Article 10.

  • Development Plans Shipper has provided Gatherer with a report attached hereto as Exhibit D (the “Current Development Plan”) describing in detail, as of January 1, 2017, the planned development, drilling, and production activities to take place with respect to Dedicated Production for the applicable Development Period. The information contained in the TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Current Development Plan is broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by the Current Development Plan, on a Quarter-by-Quarter basis, and with respect to the remaining Years covered by the Current Development Plan, on a Year-by-Year basis. The Current Development Plan attached hereto has been approved by the Parties. (a) From time to time during each Year of the Term, the Parties shall meet to discuss the planned development, drilling, and production activities that Shipper expects to take place with respect to Dedicated Production for the then-applicable Development Period. Shipper and Gatherer shall each make their respective representatives available to participate in such meetings and discussions. No later than August 1 of each such Year, Shipper shall provide (or cause to be provided) to Gatherer a proposed update of the then-currently agreed Development Plan, prepared on the same basis as the Current Development Plan and describing in detail the planned development, drilling, and production activities to take place with respect to Dedicated Production for the then-applicable Development Period (any such update, an “Updated Development Plan” and, together with the Current Development Plan, each, a “Development Plan”). Notwithstanding anything herein to the contrary, in no event shall Gatherer be required to agree to any Updated Development Plan and corresponding updated Gathering System Plan that contains a Committed Build-Out that (i) has a corresponding Target Completion Date that occurs after the end of the Initial Term, and (ii) Gatherer, in its sole discretion, does not wish to approve. (b) Each proposed Development Plan shall include information as to the following, in each case, broken out on a Subsystem-by-Subsystem basis and, with respect to the first three Years covered by such Development Plan, on a Quarter-by-Quarter basis, and, with respect to the remaining Years covered by such Development Plan, on a Year-by-Year basis: (i) all Xxxxx that, as of the date such Development Plan was delivered, are currently in existence and (A) the production therefrom is being delivered into the Gathering System, or (B) are awaiting connection to the Gathering System; (ii) the Xxxxx that are expected to be drilled during the time period covered by such Development Plan (each such Well reflected in such Development Plan, a “Planned Well”), and the estimated timing of the drilling of such Planned Xxxxx; (iii) forward-looking production estimates for the applicable time period covered by such Development Plan for all Shipper Gas (A) that Shipper reasonably and in good faith believes will become owned or Controlled by Shipper during the time period covered by such Development Plan, and/or (B) that will be produced from (I) in the aggregate, all Xxxxx then-existing and (II) in the aggregate, any Planned Xxxxx included in such Development Plan (such collective estimates described in subsections (A) and (B), both with respect to a particular Quarter and an entire Year, the “Dedicated Production Estimates”); TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). (iv) forward-looking estimates for the applicable time period covered by such Development Plan of the aggregate volumes of those Shipper Injected Liquids that Shipper intends to Tender to the Injection Points hereunder to receive the System Services (such estimates, both with respect to a particular Quarter and an entire Year, the “System Liquids Estimates” and, together with the Dedicated Production Estimates, the “System Production Estimates”); (v) (A) each new receipt point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such receipt point, including those located at the site of a Planned Well, a “Planned Receipt Point”), (B) each Receipt Point at which Shipper expects to Tender Shipper Gas and/or Shipper Injected Liquids reflected in such Development Plan into the Gathering System, and (C) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to Tender at each such Receipt Point and Planned Receipt Point; (vi) the earliest date on which each Planned Well included in the Development Plan is estimated to be completed and producing, which date shall not be earlier than three Months after the January 1st that is immediately subsequent to the date that the Development Plan that initially reflected such Planned Well was delivered to Gatherer hereunder; (vii) the anticipated characteristics of the production from the Xxxxx and Planned Xxxxx reflected in such Development Plan (including liquids content and gas and liquids composition) and the projected production volumes and production pressures applicable thereto; provided that Shipper may utilize the existing and historical production information from similarly situated Xxxxx; (viii) (A) each new delivery point (including the location thereof) proposed by Shipper with respect to the System Production Estimate reflected in such Development Plan (each such delivery point, a “Planned Delivery Point”), (B) each Delivery Point at which Shipper expects Shipper Gas produced from the Xxxxx and Planned Xxxxx reflected in such Development Plan to be redelivered to Shipper, (C) each Delivery Point at which Shipper expects any Drip Liquids allocated to Shipper in accordance with this Agreement and/or Shipper Injected Liquids to be redelivered to Shipper, and (D) the estimated portion of the System Production Estimate contained in such Development Plan that Shipper expects to be redelivered to Shipper at each such Delivery Point and Planned Delivery Point; (ix) any (A) proposed revision to the then-existing Dedicated Area and/or any then-existing Dedicated Contract and/or (B) any new contract that Shipper proposes to be a Dedicated Contract; and (x) other information reasonably requested by Gatherer that is relevant to the design, construction, and operation of the Gathering System, including (A) any Subsystem Extension proposed by Shipper, (B) the relevant Receipt Point, Planned Receipt Point, Delivery Point and Planned Delivery Point facilities applicable to such TERMS IN THIS EXHIBIT HAVE BEEN REDACTED BECAUSE CONFIDENTIAL TREATMENT FOR THOSE TERMS HAS BEEN REQUESTED. THE REDACTED MATERIAL HAS BEEN FILED SEPARATELY WITH THE SECURITIES AND EXCHANGE COMMISSION, AND THE TERMS HAVE BEEN MARKED AT THE APPROPRIATE PLACE WITH TWO ASTERISKS (**). Development Plan, and (C) any treating, processing, or liquids handling facilities proposed by Shipper that may be required for any Shipper Gas and/or Shipper Injected Liquids to meet applicable Downstream Facility specifications at the Delivery Points.

  • Research Independence The Company acknowledges that each Underwriter’s research analysts and research departments, if any, are required to be independent from their respective investment banking divisions and are subject to certain regulations and internal policies, and that such Underwriter’s research analysts may hold and make statements or investment recommendations and/or publish research reports with respect to the Company and/or the offering that differ from the views of its investment bankers. The Company hereby waives and releases, to the fullest extent permitted by law, any claims that the Company may have against such Underwriter with respect to any conflict of interest that may arise from the fact that the views expressed by their independent research analysts and research departments may be different from or inconsistent with the views or advice communicated to the Company by such Underwriter’s investment banking divisions. The Company acknowledges that the Representative is a full service securities firm and as such from time to time, subject to applicable securities laws, may effect transactions for its own account or the account of its customers and hold long or short position in debt or equity securities of the Company.

  • Organizational Matters The Partners agree as follows:

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK

  • Scope of Collaboration As part of the collaboration, the Controllers will act as Joint Controller. The roles of the Controller and the associated tasks are specified in more detail in Appendix 1. If one party is solely responsible for a data processing operation, this party will implement all relevant data protection provisions on its own responsibility. However, such data processing procedures are not subject to this Agreement. Joint data processing and the type of Personal Data collected and processed within the framework of collaboration are specified in Appendix 1.

  • Master Feeder Structure If permitted by the 1940 Act, the Board of Trustees, by vote of a majority of the Trustees, and without a Shareholder vote, may cause the Trust or any one or more Series to convert to a master feeder structure (a structure in which a feeder fund invests all of its assets in a master fund, rather than making investments in securities directly) and thereby cause existing Series of the Trust to either become feeders in a master fund, or to become master funds in which other funds are feeders.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!