Sites for Work Performance The Applicant shall list (on separate pages) the site(s) for the performance of work done in connection with the HUD funding of the program/activity shown above: Place of Performance shall include xxx xxxxxx xxxxxxx, xxxx, xxxxxx, Xxxxx, and zip code. Identify each sheet with the Applicant name and address and the program/activity receiving grant funding.) Check here 0if there are workplaces on file that are not identified on the attached sheets. I hereby certify that all the information stated herein, as well as any information provided in the accompaniment herewith, is true and accurate. Warning: HUD will prosecute false claims and statements. Conviction may result in criminal and/or civil penalties. (18 U .S.C. 1001, 1010, 1012; 31 U.S.C. 3729, 3802) Name of Authorized Official Title Signature Date X form HUD-50070 (3/98) ref. Handbooks 7417.1 , 7475.13, 7485.1 & .3 CERTIFICATION REGARDING DEBARMENT, SUSPENSION, INELIGIBILITY AND VOLUNTARY EXCLUSION LOWER TIER COVERED TRANSACTIONS This certification is required by the regulations implementing Executive Order 12549, Debarment and suspension, 29 CFR Part 98.510, Participants’ responsibilities. The regulations were published as Part VII of the May 26, 1988 Federal Register (pages 19160-19211) (BEFORE COMPLETING CERTIFICATION, READ INSTRUCTIONS FOR CERTIFICATION)
Work Performance All work in performance of this Lease shall be done by skilled workers or mechanics and shall be acceptable to the RECO. The RECO may reject the Lessor’s workers 1) if such are unlicensed, unskilled, or otherwise incompetent, or 2) if such have demonstrated a history of either untimely or otherwise unacceptable performance in connection with work carried out in conjunction with either this contract or other Government or private contracts.
CONTRACTOR PERFORMANCE Agencies shall report any vendor failure to perform according to the requirements of this contract on Complaint to Vendor, form PUR 7017. Should the vendor fail to correct the problem within a prescribed period of time, then form PUR 7029, Request for Assistance, is to be filed with this office.
Work Performed The Government will pay the Contractor as follows upon the submission of commercial invoices approved by the Contracting Officer:
Software Performance HP warrants that its branded software products will conform materially to their specifications and be free of malware at the time of delivery. HP warranties for software products will begin on the date of delivery and unless otherwise specified in Supporting Material, will last for ninety (90) days. HP does not warrant that the operation of software products will be uninterrupted or error-free or that software products will operate in hardware and software combinations other than as authorized by HP in Supporting Material.
Timeliness of Performance Contractor must provide the Services and Deliverables within the term and within the time limits required under this Contract, pursuant to Detailed Specifications or as specified in the applicable Task Order or Purchase Order. Further, Contractor acknowledges that TIME IS OF THE ESSENCE and that the failure of Contractor to comply with the time limits may result in economic or other losses to the City. Neither Contractor nor its agents, employees or Subcontractors are entitled to any damages from the City, nor is any party entitled to be reimbursed by the City, for damages, charges or other losses or expenses incurred by Contractor by reason of delays or hindrances in the performance of the Services, whether or not caused by the City.
Performance Requirements 1. Neither Party may impose or enforce any of the following requirements, or enforce any commitment or undertaking, in connection with the establishment, acquisition, expansion, management, conduct or operation of an investment of an investor of a Party or of a non-Party in its territory:
Registry Performance Specifications Registry Performance Specifications for operation of the TLD will be as set forth in Specification 10 attached hereto (“Specification 10”). Registry Operator shall comply with such Performance Specifications and, for a period of at least one (1) year, shall keep technical and operational records sufficient to evidence compliance with such specifications for each calendar year during the Term.
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.
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).
