Platform Operator Sample Clauses

Platform Operator. 4.1 The Operators agree that: (a) subject to the operation of paragraph 4.1(b) below, PRISMA is and shall remain the Platform Operator for the purposes of this Agreement; (b) an Operator may only change the Platform Operator with the other Operator’s prior written agreement to do so, such agreement not to be unreasonably withheld or delayed; (c) nothing in this Agreement or otherwise shall require the Operators to enter into or incur any joint obligations or liabilities to PRISMA (or any other Platform Operator); and (d) each Operator is severally responsible for any fees or other amounts payable to PRISMA (or any other Platform Operator) in connection with the arrangements described in paragraph 4.2 below. 4.2 Each Operator: (a) confirms that it has entered into a Standard Form TSO Services Contract with PRISMA pursuant to which, amongst other things, PRISMA agrees to provide the Common Services in accordance with and subject to the terms of the Standard Form TSO Services Contract; and (b) shall, subject to the operation of paragraph 4.1(b), maintain in full force and effect the Standard Form TSO Services Contract for the duration of this Agreement. 4.3 Each Operator considers and intends that the Services shall include PRISMA: (a) determining, based on the submissions made to it by the Operators as described at paragraph 4.4 below, how much of the Available IP Capacity is capable of being made available as Bundled Available Capacity (and therefore included in a Bundled Capacity Auction) and how much is to be made available as Unbundled Available Capacity; (b) publishing information relating to forthcoming Auctions; (c) holding Auctions, including receiving, validating, evaluating and, where appropriate, accepting Shipper bids made in respect of Available IP Capacity; (d) notifying the results of each Auction to each Operator and to each of the Shippers who participated in that Auction; (e) publishing Auction results; and (f) allocating Available IP Capacity to Shippers who have submitted successful bids. 4.4 The Operators acknowledge and agree that as at the Amendment Effective Date1 November 2015: (a) IUK is not using PRISMA for transfers and surrenders of Allocated IP Capacity; and (b) National Grid Gas is using PRISMA for transfers and surrenders of Allocated IP Capacity, and if these arrangements are proposed to change for either Operator (the “Affected Operator”), the Affected Operator shall provide written notice in advance to the other Operator of...
Sample 1Sample 2See All (6)
AutoNDA by SimpleDocs
Platform Operator. 4.1 The Parties agree that the Platform Operator for the Interconnection Point is PRISMA European Capacity Platform GmbH. 4.2 Any change to the Platform Operator requires the agreement of both Parties. 4.3 The functions to be performed by the Platform Operator are: (a) in relation to Auctions: (i) determining amounts of Bundled and Unbundled IP Capacity available for allocation in each Auction; (ii) publication of Auction information and holding of Auctions (in respect of both Bundled and Unbundled IP Capacity); (b) receipt and validation of transfers by Shippers of IP Capacity (both Bundled and Unbundled); and (c) receipt and validation of surrenders by Shippers of IP Capacity (both Bundled and Unbundled). 4.4 Each of the Parties (or its Affiliates) shall be party to an agreement with the Platform Operator under which the Platform Operator agrees to perform the functions contemplated by this Schedule and by that Operator’s Transportation Arrangements. 4.5 Nothing in this Schedule requires the Parties to enter into or incur any joint obligations or liabilities to the Platform Operator; and each of the Operators is severally responsible for any fees or other amounts payable to the Platform Operator in connection with its agreement under paragraph 4.4. 4.6 Each of the Parties considers that the Platform Rules and Processes are compatible with its Transportation Arrangements and with the provisions of this Schedule. 4.7 If any incompatibility is found between the Platform Rules and Processes and the provisions of this Schedule or any Party's Transportation Arrangements the Parties will discuss the matter with a view to agreeing whether to amend this Schedule, seek a modification of the Platform Rules and Processes and/or pursue a modification of the relevant Party's Transportation Arrangements. 4.8 Each of the Parties shall: (a) send to the Platform Operator the information necessary to enable the Platform Operator to hold Bundled Capacity Auctions and perform its other functions contemplated by this Schedule, including the following: (i) amounts of IP Capacity available for Auction; (ii) amounts of IP Capacity already allocated; (iii) reserve prices; (iv) large price steps and small price step; and (b) where the Platform Rules and Processes allow or require that Party to make choices, make such choices as are required to give effect to this Schedule. 4.9 If (notwithstanding each Party complying with paragraph 4.8) any question arises as to how the Platform O...
Sample 1See All (4)
Platform Operator. 8.1.1 This XXXX is concluded between the User and the Publisher only and not with the specific Platform Operator (e.g. Apple, Google, etc.). The Platform Operator does not assume any responsibility for the App, but is - in case of a breach of the XXXX - entitled to raise claims against the User to the extent that the Platform Operator is a beneficiary to the XXXX. 8.1.2 The Publisher grants the User the right to use the App only on devices that are owned or operated by him and in accordance with the Platform XXXX. 8.1.3 Platform Operator is in no way obliged to provide any maintenance or support services with regards to the App. 8.1.4 Platform Operator does not assume any responsibility for the review, defense, settlement or satisfaction of claims resulting from the infringement of third party intellectual property rights. 8.1.5 Platform Operator is not obliged to react on claims brought against Platform Operator by the User or a third party in connection with the App or the property and/or the use of the App. This applies among others for the following claims: (a) product liability claims; (b) claims on the basis of assertion that the App is in breach of legal or regulatory provisions and (c) consumer protection claims or similar laws and regulations. 8.1.6 If the App does not satisfy an applicable warranty or guarantee, the User is entitled to inform the Platform Operator, so that the Platform Operator may refund the purchase price to the User, if applicable. As far as legally permissive, the Platform Operator does not assume any warranty regarding the App. 8.1.7 Platform Operator and its subsidiaries are beneficiary of the privacy statement and this XXXX and are after acceptance by the User therefore entitled to (and this right is deemed to have been accepted) derive rights from this XXXX and raise claims against the User.
Sample 1
Platform Operator a legal entity providing marketing services to Platform Users based on this Agreement. Platform Operator receives payment from Platform Users for the purchase and receipt of advertising services and provides the technical solution for the payment of these services to the Advertising Service Provider.
Sample 1
Platform Operator. 4.1 The Operators agree that: (a) subject to the operation of paragraph 4.1(b) below, PRISMA is and shall remain the Platform Operator for the purposes of this Agreement; (b) an Operator may only change the Platform Operator with the other Operator’s prior written agreement to do so, such agreement not to be unreasonably withheld or delayed; (c) nothing in this Agreement or otherwise shall require the Operators to enter into or incur any joint obligations or liabilities to PRISMA (or any other Platform Operator); and (d) each Operator is severally responsible for any fees or other amounts payable to PRISMA (or any other Platform Operator) in connection with the arrangements described in paragraph 4.2 below.
Sample 1

Related to Platform Operator

  • Operator The Optionee shall be the operator for purposes of developing and executing exploration programs.

  • NETWORK INTERCONNECTION METHODS 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CSTC chooses to subtend a Verizon access Tandem, CSTC’s NPA/NXX must be assigned by CSTC to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG. 9.2.2 CSTC shall establish Access Toll Connecting Trunks pursuant to applicable access Tariffs by which it will provide Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic to and from CSTC’s Customers. 9.2.3 The Access Toll Connecting Trunks shall be two-way trunks. Such trunks shall connect the End Office CSTC utilizes to provide Telephone Exchange Service and Switched Exchange Access to its Customers in a given LATA to the access Tandem(s) Verizon utilizes to provide Exchange Access in such LATA. 9.2.4 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access to allow CSTC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier which is connected to a Verizon access Tandem.

  • Hosting Services 13.1 If Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract Hosts Customer Data in connection with an Acquisition, the provisions of Appendix 1, attached hereto and incorporated herein, apply to such Acquisition. 13.2 If the Hosting of Customer Data by Supplier or its subcontractor, affiliate or any other person or entity providing products or services under the Contract contributes to or directly causes a Data Breach, Supplier shall be responsible for the obligations set forth in Appendix 1 related to breach reporting requirements and associated costs. Likewise if such Hosting contributes to or directly causes a Security Incident, Supplier shall be responsible for the obligations set forth in Appendix 1, as applicable. 14 Change Management

  • List of Operator’s Subprocessors [Box 26] [Box 27] [Box 28] [Box 29]

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Managed Services HP will provide the services as described in a Statement of Work (“SOW”) attached to this Agreement or incorporating it by reference. Each party will appoint a single point of contact as set forth in the SOW who will serve as their primary representative, have overall responsibility for managing performance, and meet with the other party’s representative to review progress. Change requests are governed by the change management procedures as set forth in the SOW.

  • XXX Hosting 10.1 XXX Hosting is not required for resale in the BellSouth region.

  • FORMAT AND CONTENT FOR REGISTRY OPERATOR MONTHLY REPORTING Registry Operator shall provide one set of monthly reports per gTLD, using the API described in draft-­‐xxxxxx-­‐icann-­‐registry-­‐interfaces, see Specification 2, Part A, Section 9, reference 5, with the following content. ICANN may request in the future that the reports be delivered by other means and using other formats. ICANN will use reasonable commercial efforts to preserve the confidentiality of the information reported until three (3) months after the end of the month to which the reports relate. Unless set forth in this Specification 3, any reference to a specific time refers to Coordinated Universal Time (UTC). Monthly reports shall consist of data that reflects the state of the registry at the end of the month (UTC).

  • Configuration Management The Contractor shall maintain a configuration management program, which shall provide for the administrative and functional systems necessary for configuration identification, control, status accounting and reporting, to ensure configuration identity with the UCEU and associated cables produced by the Contractor. The Contractor shall maintain a Contractor approved Configuration Management Plan that complies with ANSI/EIA-649 2011. Notwithstanding ANSI/EIA-649 2011, the Contractor’s configuration management program shall comply with the VLS Configuration Management Plans, TL130-AD-PLN-010-VLS, and shall comply with the following:

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