Specific Provisions for Access Rights to Software For the avoidance of doubt, the general provisions for Access Rights provided for in this Section 9 are applicable also to Software. Parties’ Access Rights to Software do not include any right to receive source code or object code ported to a certain hardware platform or any right to receive respective Software documentation in any particular form or detail, but only as available from the Party granting the Access Rights.
Sole Source as Grounds for Rejection of a Change Order If a Change Order is submitted to Contractor for the purposes of adding a Bulletin to this Contract and said Bulletin designates a Sole Source from which Contractor is required to procure goods or services necessary to perform the Work, which Sole Source has not been designated previously, Contractor shall be entitled to reject the proposed Change Order if the designated Sole Source refuses to provide to Contractor the warranties, bonds, terms or schedule required under the Contract Documents, including any warranty or terms or schedule required by Bulletins referenced in the proposed Change Order. In such event, Contractor shall give written notice to the Owner rejecting the proposed Change Order and, if possible, shall accompany said written notice with a proposal from Contractor for changes or modifications to the Bulletin so as to eliminate the Sole Source designation but to achieve goods or services equal in quality or function. The Owner may then require the Design Professional to revise the subject Bulletin so as to eliminate the designation of the Sole Source by incorporation of Contractor's proposal or otherwise. Upon revision of the Bulletin by the Design Professional and approval thereof by the Owner, the Owner shall again submit to the Contractor a proposed Change Order for the purpose of adding the revised Bulletin to this Contract. If the Owner decides to retain the Sole Source in the Change Order and Contractor cannot acquire the full contractually required warranties from the Sole Source, Contractor shall be held only to the warranty terms and schedule obtainable from the Sole Source.
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.
Application of Contract Provisions The parties agree that the following contract provisions shall not apply to these employees:
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).
RELEASE OF BID EVALUATION MATERIALS Requests concerning the evaluation of Bids may be submitted under the Freedom of Information Law. Information, other than statistical or factual tabulations or data such as the Bid Tabulation, shall only be released as required by law after Contract award. Bid Tabulations are not maintained for all procurements. Names of Bidders may be disclosed after Bid opening upon request. Written requests should be directed to the Commissioner.
Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-‐to-‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.
Modifications and Updates to the Wire Center List and Subsequent Transition Periods 2.1.4.12.1 In the event BellSouth identifies additional wire centers that meet the criteria set forth in Section 2.1.4.5, but that were not included in the Initial Wire Center List, BellSouth shall include such additional wire centers in a carrier notification letter (CNL). Each such list of additional wire centers shall be considered a “Subsequent Wire Center List”.
Exclusions and Limitations for Third Party Software SUBJECT TO THE EXCLUSION OF DAMAGES STATED IN SECTION 9.2 AND WITH RESPECT TO THIRD PARTY SOFTWARE, UNDER NO CIRCUMSTANCES AND REGARDLESS OF THE NATURE OF ANY CLAIM SHALL SAP OR ITS LICENSORS’ BE LIABLE FOR AN AMOUNT IN EXCESS OF THE PAID LICENSE FEES FOR THE THIRD PARTY SOFTWARE DIRECTLY CAUSING THE DAMAGES.
CONTRACTOR’S SUBMISSION OF CONTRACT MODIFICATIONS In connection with any Contract modification, OGS reserves the right to: request additional information reject Contract modifications remove Products from Contract modification requests request additional discounts for new or existing Products
