Content of CATS Parties’ Election Sample Clauses

Content of CATS Parties’ Election. ‌ In any election pursuant to Article 16.1 (a), the CATS Parties shall elect to pay to or on behalf of the Relevant Parties:
AutoNDA by SimpleDocs

Related to Content of CATS Parties’ Election

  • Paid Claims without Supporting Documentation Any Paid Claim for which Practitioner cannot produce documentation shall be considered an error and the total reimbursement received by Practitioner for such Paid Claim shall be deemed an Overpayment. Replacement sampling for Paid Claims with missing documentation is not permitted.

  • Selection of Subcontractors, Procurement of Materials and Leasing of Equipment The contractor shall not discriminate on the grounds of race, color, religion, sex, national origin, age or disability in the selection and retention of subcontractors, including procurement of materials and leases of equipment. The contractor shall take all necessary and reasonable steps to ensure nondiscrimination in the administration of this contract.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Public Posting of Approved Users’ Research Use Statement The PI agrees that information about themselves and the approved research use will be posted publicly on the dbGaP website. The information includes the PI’s name and Requester, project name, Research Use Statement, and a Non-Technical Summary of the Research Use Statement. In addition, and if applicable, this information may include the Cloud Computing Use Statement and name of the CSP or PCS. Citations of publications resulting from the use of controlled-access datasets obtained through this DAR may also be posted on the dbGaP website.

  • PROVISIONAL AGREEMENT RESULTING FROM INTERINSTITUTIONAL NEGOTIATIONS Subject: Proposal for a regulation of the European Parliament and of the Council on a Pan- European Personal Pension Product (PEPP) (COM(2017)0343 – C8-0219/2017 – 2017/0143(COD)) The interinstitutional negotiations on the aforementioned proposal for a regulation have led to a compromise. In accordance with Rule 69f(4) of the Rules of Procedure, the provisional agreement, reproduced below, is submitted as a whole to the Committee on Economic and Monetary Affairs for decision by way of a single vote. AG\1177088EN.docx PE634.848v01-00 EN United in diversity EN REGULATION (EU) 2019/... OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of ... on a pan-European Personal Pension Product (PEPP) (Text with EEA relevance) THE EUROPEAN PARLIAMENT AND THE COUNCIL OF THE EUROPEAN UNION, Having regard to the Treaty on the Functioning of the European Union, and in particular Article 114 thereof, Having regard to the proposal from the European Commission, After transmission of the draft legislative act to the national parliaments, Having regard to the opinion of the European Economic and Social Committee1, Acting in accordance with the ordinary legislative procedure2,

  • Provisioning of High Frequency Spectrum and Splitter Space 3.2.1 BellSouth will provide <<customer_name>> with access to the High Frequency Spectrum as follows:

  • Content of Contractor's certification As required in paragraph (l)(5) of this clause, the Contractor shall make the following certification in each request for performance-based payment: I certify to the best of my knowledge and belief that --

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to:  request additional information  reject Contract modifications  remove Products from Contract modification requests  request additional discounts for new or existing Products

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