Federated Process Control Sample Clauses

Federated Process Control. Subject to the terms of the Agreement (including the applicable Usage Metrics set forth in the Order Form), Customer may access and use one (1) Parent Site and one (1) Child Site in conjunction with a subscription to any one of the following Procurement Packages: P2P FPC, P2O FPC, P2P FPC-Partner Ed., or P2O FPC Partner Ed. At any time prior to the expiration or earlier termination of Customer’s subscription to any of the foregoing Procurement Packages, Customer may purchase a co- term subscription to additional Child Sites for such Procurement Package at SAP’s then-current rates. If Customer elects to purchase such subscriptions, Customer must also purchase the corresponding Deployment Services for each additional Child Site for an additional fee.
View SourceView Similar (2)
Federated Process Control. Subject to the terms of the Agreement (including the applicable Usage Metrics set forth in the Order Form), Customer may access and use one (1) Parent Site and one (1) Child Site in conjunction with a subscription to any one of the following Procurement Packages: ▇▇▇ ▇▇▇, ▇▇▇ ▇▇▇, ▇▇▇ FPC-Partner Ed., or P2O FPC Partner Ed. At any time prior to the expiration or earlier termination of Customer’s subscription to any of the foregoing Procurement Packages, Customer may purchase a co-term subscription to additional Child Sites for such Procurement Package at SAP’s then-current rates. If Customer elects to purchase such subscriptions, Customer must also purchase the corresponding Deployment Services for each additional Child Site for an additional fee. 4. ARIBA ADVANCED SUPPLY CHAIN AUTOMATION Ariba Advanced Supply Chain Automation is designed to provide add-on features and functionalities that supplement and leverage the technology features of Ariba Document Automation and/or Ariba Collaborative Commerce Document Automation (as further described in the Documentation) and accordingly, requires an active, paid, and coterminous subscription to Ariba Document Automation and/or Ariba Collaborative Commerce Document Automation. Notwithstanding anything to the contrary in this Supplement, Advanced Supply Chain Automation includes transaction capabilities for an unlimited number of Documents originating from such Cloud Service during the Subscription Term. Penggunaan Pelanggan untuk Ariba Document Automation atau Ariba Collaborative Commerce Document Automation.
View Source
Federated Process Control. Dengan tunduk pada syarat-syarat dalam Perjanjian (termasuk Metrik Penggunaan yang berlaku yang dinyatakan dalam Formulir Pemesanan), Pelanggan dapat mengakses ▇▇▇ menggunakan satu (1) Situs Induk ▇▇▇ satu (1) Situs Turunan bersama dengan langganan atas salah satu dari Paket Pengadaan berikut: ▇▇▇ ▇▇▇, ▇▇▇ ▇▇▇, ▇▇▇ FPC-Partner Ed., atau P2O FPC Partner Ed. Pada saat kapan pun sebelum habisnya masa berlaku atau pengakhiran dini langganan Pelanggan atas salah satu dari Paket Pengadaan sebelumnya, Pelanggan dapat membeli langganan dengan waktu pengakhiran yang sama atas Situs turunan tambahan untuk Paket Pengadaan tersebut pada tarif SAP yang berlaku saat itu. Jika Pelanggan memilih untuk membeli langganan tersebut, Pelanggan juga harus membeli Layanan Penempatan terkait untuk setiap Situs Turunan tambahan dengan imbalan tambahan.
View Source

Related to Federated Process Control

  • Quality Control A. Controlled Affiliate agrees to use the Licensed Marks and Name only in connection with the licensed services and further agrees to be bound by the conditions regarding quality control shown in attached Exhibit A as they may be amended by BCBSA from time-to-time. B. Controlled Affiliate agrees to comply with all applicable federal, state and local laws. C. Controlled Affiliate agrees that it will provide on an annual basis (or more often if reasonably required by Plan or by BCBSA) a report or reports to Plan and BCBSA demonstrating Controlled Affiliate’s compliance with the requirements of this Agreement including but not limited to the quality control provisions of this paragraph and the attached Exhibit A. D. Controlled Affiliate agrees that Plan and/or BCBSA may, from time-to-time, upon reasonable notice, review and inspect the manner and method of Controlled Affiliate’s rendering of service and use of the Licensed Marks and Name. E. As used herein, a Controlled Affiliate is defined as an entity organized and operated in such a manner, that it meets the following requirements: (1) A Plan or Plans authorized to use the Licensed Marks in the Service Area of the Controlled Affiliate pursuant to separate License Agreement(s) with BCBSA, other than such Controlled Affiliate’s License Agreement(s), (the “Controlling Plan(s)”), must have the legal authority directly or indirectly through wholly-owned subsidiaries to select members of the Controlled Affiliate’s governing body having not less than 50% voting control thereof and to: (a) prevent any change in the articles of incorporation, bylaws or other establishing or governing documents of the Controlled Affiliate with which the Controlling Plan(s) do(es) not concur; (b) exercise control over the policy and operations of the Controlled Affiliate at least equal to that exercised by persons or entities (jointly or individually) other than the Controlling Plan(s); and Notwithstanding anything to the contrary in (a) through (b) hereof, the Controlled Affiliate’s establishing or governing documents must also require written approval by the Controlling Plan(s) before the Controlled Affiliate can: (i) change its legal and/or trade names; (ii) change the geographic area in which it operates; (iii) change any of the type(s) of businesses in which it engages; (iv) create, or become liable for by way of guarantee, any indebtedness, other than indebtedness arising in the ordinary course of business; (v) sell any assets, except for sales in the ordinary course of business or sales of equipment no longer useful or being replaced; (vi) make any loans or advances except in the ordinary course of business; (vii) enter into any arrangement or agreement with any party directly or indirectly affiliated with any of the owners or persons or entities with the authority to select or appoint members or board members of the Controlled Affiliate, other than the Plan or Plans (excluding owners of stock holdings of under 5% in a publicly traded Controlled Affiliate); (viii) conduct any business other than under the Licensed Marks and Name; (ix) take any action that any Controlling Plan or BCBSA reasonably believes will adversely affect the Licensed Marks and Name. In addition, a Plan or Plans directly or indirectly through wholly owned subsidiaries shall own at least 50% of any for-profit Controlled Affiliate. (2) A Plan or Plans authorized to use the Licensed Marks in the Service Area of the Controlled Affiliate pursuant to separate License Agreement(s) with BCBSA, other than such Controlled Affiliate’s License Agreement(s), (the “Controlling Plan(s)”), have the legal authority directly or indirectly through wholly-owned subsidiaries to select members of the Controlled Affiliate’s governing body having more than 50% voting control thereof and to: (a) prevent any change in the articles of incorporation, bylaws or other establishing or governing documents of the Controlled Affiliate with which the Controlling Plan(s) do(es) not concur; (b) exercise control over the policy and operations of the Controlled Affiliate. In addition, a Plan or Plans directly or indirectly through wholly-owned subsidiaries shall own more than 50% of any for-profit Controlled Affiliate.

  • Synchronization, Commissioning and Commercial Operation 5.1.1 The SPG shall give PGVCL at least thirty (30) days’ advanced preliminary written notice and at least fifteen (15) days’ advanced final written notice, of the date on which it intends to synchronize the Solar Power Project to the Grid System. 5.1.2 Subject to Article 5.1.1, the Power Project may be synchronized by the SPG to the Grid System when it meets all the connection conditions prescribed in applicable Grid Code then in effect and otherwise meets all other Indian legal requirements for synchronization to the Grid System. 5.1.3 The synchronization equipment and all necessary arrangements / equipment including RTU for scheduling of power generated from the Project and transmission of data to the concerned authority as per applicable regulation shall be installed by the SPG at its generation facility of the Power Project at its own cost. The SPG shall synchronize its system with the Grid System only after the approval of synchronization scheme is granted by the head of the concerned substation/ and checking/verification is made by the concerned authorities of the PGVCL. 5.1.4 The SPG shall immediately after each synchronization/tripping of generator, inform the sub-station of the Grid System to which the Power Project is electrically connected in accordance with applicable Grid Code. In addition, the SPG will inject in-firm power to grid from time to time to carry out operational/ functional test prior to commercial operation. For avoidance of doubt, it is clarified that Synchronization / Connectivity of the Project with the grid shall not to be considered as Commissioning of the Project. 5.1.5 The SPG shall commission the Project within nine (9) Months from the Date of execution of this PPA. Declaration of COD shall be certified by the commissioning committee. 5.1.6 The Parties agree that for the purpose of commencement of the supply of electricity by SPG to PGVCL, liquidated damages for delay etc., the Scheduled Commissioning Date as defined in this Agreement shall be the relevant date.

  • Required Procurement Procedures for Obtaining Goods and Services The Grantee shall provide maximum open competition when procuring goods and services related to the grant- assisted project in accordance with Section 287.057, Florida Statutes.

  • Quality Service Standards Price Services and the Fund may from time to time agree to certain quality service standards, as well as incentives and penalties with respect to Price Services’ Services hereunder.

  • Commercial Milestones (a) Within [*****] calendar days after the end of the first Calendar Year in which aggregate annual Net Sales for that Calendar Year for the Licensed Product in the Territory reach any threshold indicated in the Commercial Milestone Events listed below, EverInsight shall notify VistaGen of the achievement of such Commercial Milestone Event and VistaGen shall invoice EverInsight for the corresponding non-refundable, non-creditable Milestone Payment set forth below and EverInsight shall remit payment to VistaGen within [*****] Business Days after the receipt of the invoice, as described in Section 8.6 (Currency; Exchange Rate; Payments). Annual Net Sales Milestones for Licensed Product Milestone Payments (in Dollars) (each a “Commercial Milestone Event”): (1). [*****] (2). [*****] (3). [*****] (4). [*****] (5). [*****] (b) For the purposes of determining whether a Net Sales Milestone Event has been achieved, Net Sales of Licensed Product(s) in the Territory shall be aggregated. For clarity, the annual Net Sales Milestone Payments set forth in this Section 8.3 (Commercial Milestones) shall be payable only once, upon the first achievement of the applicable Commercial Milestone Event, regardless of how many times such Commercial Milestone Event is achieved. (c) If a Commercial Milestone Event in Section 8.3 (Commercial Milestones) is achieved and payment with respect to any previous Commercial Milestone Event in Section 8.3 has not been made, then such previous Commercial Milestone Event shall be deemed achieved and EverInsight shall notify VistaGen within fifteen (15) calendar days of such achievement. VistaGen shall then invoice EverInsight for such unpaid previous Commercial Milestone Event(s) and EverInsight shall pay VistaGen such unpaid previous milestone payment(s) within thirty (30) Business Days of receipt of such invoice. (d) In the event that, VistaGen believes any Commercial Milestone Event under Section 8.3(a) has occurred but EverInsight has not given VistaGen the notice of the achievement of such Commercial Milestone Event, it shall so notify EverInsight in writing and shall provide to EverInsight data, documentation or other information that supports its belief. Any dispute under this Section 8.3(d) (Commercial Milestones - subsection (d)) that relates to whether or not a Commercial Milestone Event has occurred shall be referred to the JSC to be resolved in accordance with ARTICLE 3 (Governance) and shall be subject to resolution in accordance with Section 14.10 (Dispute Resolution). The Milestone Payments made for each Commercial Milestone Event shall be non-creditable and non-refundable.