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.
Certification of Funds; Budget and Fiscal Provisions; Termination in the Event of Non-Appropriation This Agreement is subject to the budget and fiscal provisions of the City’s Charter. Charges will accrue only after prior written authorization certified by the Controller, and the amount of City’s obligation hereunder shall not at any time exceed the amount certified for the purpose and period stated in such advance authorization. This Agreement will terminate without penalty, liability or expense of any kind to City at the end of any fiscal year if funds are not appropriated for the next succeeding fiscal year. If funds are appropriated for a portion of the fiscal year, this Agreement will terminate, without penalty, liability or expense of any kind at the end of the term for which funds are appropriated. City has no obligation to make appropriations for this Agreement in lieu of appropriations for new or other agreements. City budget decisions are subject to the discretion of the Mayor and the Board of Supervisors. Contractor’s assumption of risk of possible non-appropriation is part of the consideration for this Agreement. THIS SECTION CONTROLS AGAINST ANY AND ALL OTHER PROVISIONS OF THIS AGREEMENT.
ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:
Default Events and Termination 18.1 Each of the following circumstances shall constitute a General Default:
Effective Date; Termination; Cancellation and Suspension Section 5.01. This Agreement shall come into force and effect on the date upon which the Development Credit Agreement becomes effective.
EFFECTIVE DATE, TERMINATION, AND RENEWAL 17.1 This Agreement shall become effective on the first day of May, AD., 2019, and shall continue in full force and effect until the thirtieth (30th) day of April, AD., 2022 and thereafter from year to year unless terminated upon written notice of either party within one hundred and twenty (120) days prior to any anniversary of the terminal date.
Service Level Agreements If a Service or a Plan includes a Service Level Agreement (SLA):
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.
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.
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).
