Status of Joint Operating Company Sample Clauses

Status of Joint Operating Company. The Joint Operating Company and any other entity Contractor agrees to form for the purposes of carrying out work to be undertaken by Contractor pursuant to this Contract shall be entitled to all of the benefits, waivers, indemnities and exemptions accorded to the Contractor Parties under this Contract. The Joint Operating Company (and any other entity as referred to above) shall own no assets or equipment (though it may have the right to freely use assets or equipment owned or used by the Contractor Parties in conducting Petroleum Operations on behalf of the Contractor Parties); shall act on behalf of the Contractor Parties upon receipt of their instructions and directions; shall not be entitled to any share of Petroleum produced; and shall operate exclusively as a non-profit cost company which can neither make a profit nor incur a loss. The books and accounts of the Joint Operating Company (and any other entity as referred to above) will record all financial flows or other transactions as passing through to and being incurred by the Contractor Parties and SOCAR to the extent of its percentage participating interest under Article XXVIII in accordance with this Contract as though the Joint Operating Company (and any other such entity as referred to above) did not exist and for all purposes the amount of its Taxable Profit shall be zero (0).
Sample 1Sample 2
AutoNDA by SimpleDocs

Related to Status of Joint Operating Company

  • Independent Status of Contractor In the performance of this Contract, the parties shall be acting in their individual, corporate or governmental capacities and not as agents, employees, partners, joint ventures, or associates of one another. The parties intend that an independent contractor relationship shall be created by this Contract. The Contractor shall be responsible for all federal and/or state tax, industrial insurance, wages, benefits, or other compensation by or on behalf of the Contractor and its employees. The Contractor shall not make any claim of right, privilege or benefit which would accrue to an employee under chapter 41.06 RCW or Title 51 RCW.

  • STATUS OF CONTRACTOR 21 CONTRACTOR is, and shall at all times be deemed to be, an independent contractor and shall be 22 wholly responsible for the manner in which it performs the services required of it by the terms of this 23 Agreement. CONTRACTOR is entirely responsible for compensating staff, subcontractors, and 24 consultants employed by CONTRACTOR. This Agreement shall not be construed as creating the 25 relationship of employer and employee, or principal and agent, between COUNTY and CONTRACTOR 26 or any of CONTRACTOR’s employees, agents, consultants, or subcontractors. CONTRACTOR 27 assumes exclusively the responsibility for the acts of its employees, agents, consultants, or 28 subcontractors as they relate to the services to be provided during the course and scope of their 29 employment. CONTRACTOR, its agents, employees, consultants, or subcontractors, shall not be 30 entitled to any rights or privileges of COUNTY’s employees and shall not be considered in any manner 31 to be COUNTY’s employees. 32

  • Independent Contractor; No Partnership; No Agency; No Utility Services 15.1 Company and Developer shall be independent contractors. This Agreement shall not be interpreted or construed to create an association, joint venture, agency relationship, or partnership between the Parties or to impose any partnership obligation or partnership liability upon any Party. No Party shall have any right, power or authority to enter into any agreement or undertaking for, or act on behalf of, or to act as or be an agent or representative of, or to otherwise bind, the other Party. This Agreement is not an agreement to provide or take utility services of any kind, including, without limitation, interconnection or other electric transmission services.

  • Business Continuity Registry Operator shall maintain a business continuity plan, which will provide for the maintenance of Registry Services in the event of an extraordinary event beyond the control of the Registry Operator or business failure of Registry Operator, and may include the designation of a Registry Services continuity provider. If such plan includes the designation of a Registry Services continuity provider, Registry Operator shall provide the name and contact information for such Registry Services continuity provider to ICANN. In the case of an extraordinary event beyond the control of the Registry Operator where the Registry Operator cannot be contacted, Registry Operator consents that ICANN may contact the designated Registry Services continuity provider, if one exists. Registry Operator shall conduct Registry Services Continuity testing at least once per year.

  • Project Organization Chart As part of the Mini-Bid, the Authorized User may require the Contractor to develop and submit a proposed project organization chart. The project organization chart should identify all the proposed key personnel of each team component and how the team will be managed. If required, the project organization chart must include both Contractor and State staff roles as identified in the Mini-Bid.

  • Indiana Veteran’s Business Enterprise Compliance Award of this Contract was based, in part, on the Indiana Veteran’s Business Enterprise (“IVBE”) participation plan. The following IVBE subcontractors will be participating in this Contract: VBE PHONE COMPANY NAME SCOPE OF PRODUCTS and/or SERVICES UTILIZATION DATE PERCENT _____________________________________________________________________________________ _____________________________________________________________________________________ A copy of each subcontractor agreement shall be submitted to IDOA within thirty (30) days of the request. Failure to provide any subcontractor agreement may also be considered a material breach of this Contract. The Contractor must obtain approval from IDOA before changing the IVBE participation plan submitted in connection with this Contract. The Contractor shall report payments made to IVBE subcontractors under this Contract on a monthly basis. Monthly reports shall be made using the online audit tool, commonly referred to as “Pay Audit.” IVBE subcontractor payments shall also be reported to IDOA as reasonably requested and in a format to be determined by IDOA.

  • Red Hat Enterprise Linux Developer Suite Red Hat Enterprise Linux Developer Suite provides an open source development environment that consists of Red Hat Enterprise Linux with built-in development tools, certain Red Hat Enterprise Linux Add-Ons, Red Hat Enterprise Linux for Real Time, Smart Management and access to Software Maintenance, but no Development or Production Support. If you use any of the Subscription Services or Software associated with Red Hat Enterprise Linux Developer Suite for Production Purposes, or use the Red Hat Enterprise Linux Software Subscription entitlement independently, you agree to purchase the applicable number of Units of the applicable Software Subscription. Red Hat does not provide Production Support or Development Support for Red Hat Enterprise Developer Suite.

  • Required Coverages For Generation Resources Of 20 Megawatts Or Less Each Constructing Entity shall maintain the types of insurance as described in section 11.1 paragraphs (a) through (e) above in an amount sufficient to insure against all reasonably foreseeable direct liabilities given the size and nature of the generating equipment being interconnected, the interconnection itself, and the characteristics of the system to which the interconnection is made. Additional insurance may be required by the Interconnection Customer, as a function of owning and operating a Generating Facility. All insurance shall be procured from insurance companies rated “A-,” VII or better by AM Best and authorized to do business in a state or states in which the Interconnection Facilities are located. Failure to maintain required insurance shall be a Breach of the Interconnection Construction Service Agreement.

  • Traditional Medicine Cooperation 1. The aims of Traditional Medicine cooperation will be: (a) to build on existing agreements or arrangements already in place for Traditional Medicine cooperation; and (b) to promote information exchanges on Traditional Medicine between the Parties. 2. In pursuit of the objectives in Article 149 (Objectives), the Parties will encourage and facilitate, as appropriate, the following activities, including, but not limited to: (a) encouraging dialogue on Traditional Medicine policies and promotion of respective Traditional Medicine; (b) raising awareness of active effects of Traditional Medicine; (c) encouraging exchange of experience in conservation and restoration of Traditional Medicine; (d) encouraging exchange of experience on management, research and development for Traditional Medicine; (e) encouraging cooperation in the Traditional Medicine education field, mainly through training programs and means of communication; (f) having a consultation mechanism between the Parties' Traditional Medicine authorities; (g) encouraging cooperation in Traditional Medicine therapeutic services and products manufacturing; and (h) encouraging cooperation in research in the fields of Traditional Medicine in order to contribute in efficacy and safety assessments of natural resources and products used in health care.

  • Partnership Working 7.1 Partnerships will be supported by local authorities on four levels between:

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