Performance and Payment Bonds The authority and responsibility for requesting performance and payment bonds shall rest with the Customer. Under this Contract, the Customer issuing the purchase order may request a performance and payment bond, as deemed necessary by the size of the job. Inability to provide a bond may result in the Contractor being found in default of the purchase order.
Performance and Payment Bond Contractor shall post with County, not later than ten (10) days of the execution of this Agreement, a performance and payment bond in the amount of one hundred percent (100%) of the total lump sum price in such form as is satisfactory to County. The bond shall be executed by a corporate surety company duly authorized and admitted to do business in the State of Texas and licensed to issue such a bond in the State of Texas.
Timing of Payment of Performance When the payment of any obligation or the performance of any covenant, duty or obligation is stated to be due or performance required on a day which is not a Business Day, the date of such payment (other than as described in the definition of Interest Period) or performance shall extend to the immediately succeeding Business Day.
Standard of Performance Consultant represents and warrants that it has the qualifications, experience and facilities necessary to properly perform the services required under this Agreement in a thorough, competent and professional manner. Consultant shall at all times faithfully, competently and to the best of its ability, experience and talent, perform all services described herein. In meeting its obligations under this Agreement, Consultant shall employ, at a minimum, generally accepted standards and practices utilized by persons engaged in providing services similar to those required of Consultant under this Agreement.
Performance Bond and Payment Bond The Contractor shall furnish both a performance bond and a payment bond in the exact form set forth in Section 7, (Forms) of these General Conditions.
Commencement of Performance This Agreement is of no force and effect until signed by both parties and all JBE-required approvals are secured. Any commencement of performance prior to Agreement approval shall be at Contractor's own risk.
Review of Performance The Board of Directors shall periodically review and evaluate the performance of Employee under this Employment Agreement with Employee.
Monitoring of Performance Vendor shall continuously monitor and record its performance to ensure that all of Vendor's responsibilities and obligations hereunder are being met and fulfilled. Citizens may conduct programmatic and other administrative contract monitoring during the term of this Agreement. The purpose of this monitoring is to ensure that all of Vendor's responsibilities and obligations are being met and fulfilled. Such monitoring may include on-site visits, report reviews, invoice reviews, compliance reviews, and a review of any other areas reasonably necessary. Vendor acknowledges and agrees that Citizens may also monitor and record Vendor Staff communications to the extent they occur within or are connected to any Citizens’ resource, such as electronic or telecommunications systems.
CONTRACTOR PERFORMANCE AUDIT The Contractor shall allow the Authorized User to assess Contractor’s performance by providing any materials requested in the Authorized User Agreement (e.g., page load times, response times, uptime, and fail over time). The Authorized User may perform this Contractor performance audit with a third party at its discretion, at the Authorized User’s expense. The Contractor shall perform an independent audit of its Data Centers, at least annually, at Contractor expense. The Contractor will provide a data owner facing audit report upon request by the Authorized User. The Contractor shall identify any confidential, trade secret, or proprietary information in accordance with Appendix B, Section 9(a), Confidential/Trade Secret Materials.
Covenants of Performance Measurement No interference. Registry Operator shall not interfere with measurement Probes, including any form of preferential treatment of the requests for the monitored services. Registry Operator shall respond to the measurement tests described in this Specification as it would to any other request from an Internet user (for DNS and RDDS) or registrar (for EPP). ICANN testing registrar. Registry Operator agrees that ICANN will have a testing registrar used for purposes of measuring the SLRs described above. Registry Operator agrees to not provide any differentiated treatment for the testing registrar other than no billing of the transactions. ICANN shall not use the registrar for registering domain names (or other registry objects) for itself or others, except for the purposes of verifying contractual compliance with the conditions described in this Agreement. PUBLIC INTEREST COMMITMENTS Registry Operator will use only ICANN accredited registrars that are party to the Registrar Accreditation Agreement approved by the ICANN Board of Directors on 27 June 2013 in registering domain names. A list of such registrars shall be maintained by ICANN on ICANN’s website. (Intentionally omitted. Registry Operator has not included commitments, statements of intent or business plans provided for in its application to ICANN for the TLD.) Registry Operator agrees to perform the following specific public interest commitments, which commitments shall be enforceable by ICANN and through the Public Interest Commitment Dispute Resolution Process established by ICANN (posted at xxxx://xxx.xxxxx.xxx/en/resources/registries/picdrp), which may be revised in immaterial respects by ICANN from time to time (the “PICDRP”). Registry Operator shall comply with the PICDRP. Registry Operator agrees to implement and adhere to any remedies ICANN imposes (which may include any reasonable remedy, including for the avoidance of doubt, the termination of the Registry Agreement pursuant to Section 4.3(e) of the Agreement) following a determination by any PICDRP panel and to be bound by any such determination. Registry Operator will include a provision in its Registry-Registrar Agreement that requires Registrars to include in their Registration Agreements a provision prohibiting Registered Name Holders from distributing malware, abusively operating botnets, phishing, piracy, trademark or copyright infringement, fraudulent or deceptive practices, counterfeiting or otherwise engaging in activity contrary to applicable law, and providing (consistent with applicable law and any related procedures) consequences for such activities including suspension of the domain name. Registry Operator will periodically conduct a technical analysis to assess whether domains in the TLD are being used to perpetrate security threats, such as pharming, phishing, malware, and botnets. Registry Operator will maintain statistical reports on the number of security threats identified and the actions taken as a result of the periodic security checks. Registry Operator will maintain these reports for the term of the Agreement unless a shorter period is required by law or approved by ICANN, and will provide them to ICANN upon request. Registry Operator will operate the TLD in a transparent manner consistent with general principles of openness and non-discrimination by establishing, publishing and adhering to clear registration policies.
