Errors, Bugs and Corrections Sample Clauses

Errors, Bugs and Corrections. 3rd Party or Open Source Software Xynergy is not responsible for malfunctions of 3rd Party or Open Source software purchased and installed on a website for the client. Xynergy will attempt to correct any found bugs as requested by the client but client will pay Xynergy the hourly fees as outlined in item 3 of this contract.
AutoNDA by SimpleDocs

Related to Errors, Bugs and Corrections

  • Amendments to Clarify and Correct Errors and Defects The parties may amend this Agreement to clarify an ambiguity, correct an error or correct or supplement any term of this Agreement that may be defective or inconsistent with the other terms of this Agreement, in each case, without the consent of the Noteholders, the Certificateholders or any other Person. The parties may amend any term or provision of this Agreement from time to time for the purpose of conforming the terms of this Agreement to the description thereof in the Prospectus, without the consent of Noteholders, the Certificateholders or any other Person.

  • Errors/Omissions The Engineer shall make revisions to the work authorized in this contract which are necessary to correct errors or omissions appearing therein, when required to do so by the State. No additional compensation shall be paid for this work.

  • No Errors, etc The representations and warranties of the Company under this Agreement shall be deemed to have been made again on the Closing Date and shall then be true and correct in all material respects.

  • Hardware and Software Requirements In order to access and retain Disclosures electronically, you must satisfy the following computer hardware and software requirements: access to the Internet; an email account and related software capable of receiving email through the Internet; a web browser which is SSL-compliant and supports secure sessions, and hardware capable of running this software.

  • Software Requirements 7 Developer shall prepare the Project Schedule using Oracle’s Primavera P6.

  • Information Technology Enterprise Architecture Requirements If this Contract involves information technology-related products or services, the Contractor agrees that all such products or services are compatible with any of the technology standards found at xxxxx://xxx.xx.xxx/iot/2394.htm that are applicable, including the assistive technology standard. The State may terminate this Contract for default if the terms of this paragraph are breached.

  • CONFORMITY WITH LAW AND SAFETY a. In performing services under this Agreement, CONTRACTOR shall observe and comply with all applicable laws, ordinances, codes and regulations of governmental agencies, including federal, state, municipal, and local governing bodies, having jurisdiction over the scope of services, including all applicable provisions of the California Occupational Safety and Health Act. CONTRACTOR shall indemnify and hold COUNTY harmless from any and all liability, fines, penalties and consequences from any of CONTRACTOR’s failures to comply with such laws, ordinances, codes and regulations.

  • General specifications For the purpose of this Regulation, the vehicle shall fulfil the following requirements:

  • Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.

  • Disaster Recovery and Business Continuity The Parties shall comply with the provisions of Schedule 5 (Disaster Recovery and Business Continuity).

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