Modifications to the Anti-Corruption Guidelines The modifications to the Anti-Corruption Guidelines are as follows:
Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.
Modifications/Add-ons 6.3.1 Licensee shall comply with SAP’s registration procedure prior to making Modifications or Add-ons. All Modifications and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. All Add-ons developed by SAP (either independently or jointly with Licensee) and all rights associated therewith shall be the exclusive property of SAP, SAP Parent or its or their licensors. Licensee agrees to execute those documents reasonably necessary to secure SAP’s rights in the foregoing Modifications and Add-ons. All Add-ons developed by or on behalf of Licensee without SAP’s participation (“Licensee Add-on”), and all rights associated therewith, shall be the exclusive property of Licensee subject to SAP’s rights in and to the Software and SAP Materials; provided, Licensee shall not commercialize, market, distribute, license, sublicense, transfer, assign or otherwise alienate any such Licensee Add-ons. SAP retains the right to independently develop its own Modifications or Add-ons to the Software, and Licensee agrees not to take any action that would limit SAP’s sale, assignment, licensing or use of its own Software or Modifications or Add-ons thereto.
Modification of the Programme 1. Unless otherwise explicitly stipulated in this programme agreement, any modification of the Programme is subject to prior approval by the FMC.
Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.
Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.
Post-Commercial Operation Date Testing and Modifications Each Party shall at its own expense perform routine inspection and testing of its facilities and equipment in accordance with Good Utility Practice as may be necessary to ensure the continued interconnection of the Large Generating Facility with the Participating TO’s Transmission System in a safe and reliable manner. Each Party shall have the right, upon advance written notice, to require reasonable additional testing of the other Party’s facilities, at the requesting Party’s expense, as may be in accordance with Good Utility Practice.
Implementation Program 1. The Borrower shall:
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.
General Guidelines 1. Conduct yourself in a responsible manner at all times in the laboratory.
