Acceptance Criteria and Performance Specifications Sample Clauses

Acceptance Criteria and Performance Specifications 
AutoNDA by SimpleDocs

Related to Acceptance Criteria and Performance Specifications

  • 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.

  • Acceptance Criteria The Services and Deliverables must meet the following acceptance criteria or the JBE may reject the applicable Services or Deliverables. The JBE may use the attached Acceptance and Signoff Form to notify Contractor of the acceptance or rejection of the Services and Deliverables. Contractor will not be paid for any rejected Services or Deliverables.

  • Continuity of Service and Performance Unless otherwise agreed in writing, the Parties shall continue to provide service and honor all other commitments under this Agreement during the course of a Dispute with respect to all matters not subject to such Dispute.

  • Quarterly Contractor Performance Reporting Customers shall complete a Contractor Performance Survey (Exhibit I) for each Contractor on a Quarterly basis. Customers will electronically submit the completed Contractor Performance Survey(s) to the Department Contract Manager no later than the due date indicated in Contract Exhibit D, Section 17, Additional Special Contract Conditions. The completed Contractor Performance Survey(s) will be used by the Department as a performance-reporting tool to measure the performance of Contractors. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MyFloridaMarketPlace or on the Department's website).

  • Contract Goals A. For purposes of this procurement, OGS conducted a comprehensive search and determined that the Contract does not offer sufficient opportunities to set goals for participation by MWBEs as subcontractors, service providers, or suppliers to Contractor. Contractor is, however, encouraged to make every good faith effort to promote and assist the participation of MWBEs on this Contract for the provision of services and materials. The directory of New York State Certified MWBEs can be viewed at: xxxxx://xx.xxxxxxxxxxxxxx.xxx/FrontEnd/VendorSearchPublic.asp?TN=ny&XID=2528. Additionally, following Contract execution, Contractor is encouraged to contact the Division of Minority and Women’s Business Development ((000) 000-0000; (000) 000-0000; or (000) 000-0000) to discuss additional methods of maximizing participation by MWBEs on the Contract. B. Good Faith Efforts Pursuant to 5 NYCRR § 142.8, evidence of good faith efforts shall include, but not be limited to, the following: 1. A list of the general circulation, trade, and MWBE-oriented publications and dates of publications in which the Contractor solicited the participation of certified MWBEs as subcontractors/suppliers, copies of such solicitations, and any responses thereto. 2. A list of the certified MWBEs appearing in the Empire State Development (“ESD”) MWBE directory that were solicited for this Contract. Provide proof of dates or copies of the solicitations and copies of the responses made by the certified MWBEs. Describe specific reasons that responding certified MWBEs were not selected. 3. Descriptions of the Contract documents/plans/specifications made available to certified MWBEs by the Contractor when soliciting their participation and steps taken to structure the scope of work for the purpose of subcontracting with, or obtaining supplies from, certified MWBEs. 4. A description of the negotiations between the Contractor and certified MWBEs for the purposes of complying with the MWBE goals of this Contract. 5. Dates of any pre-bid, pre-award, or other meetings attended by Contractor, if any, scheduled by OGS with certified MWBEs whom OGS determined were capable of fulfilling the MWBE goals set in the Contract. 6. Other information deemed relevant to the request.

  • ODUF Packing Specifications 6.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

  • 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.

  • Ongoing Performance Measures The Department intends to use performance-reporting tools in order to measure the performance of Contractor(s). These tools will include the Contractor Performance Survey (Exhibit H), to be completed by Customers on a quarterly basis. Such measures will allow the Department to better track Vendor performance through the term of the Contract(s) and ensure that Contractor(s) consistently provide quality services to the State and its Customers. The Department reserves the right to modify the Contractor Performance Survey document and introduce additional performance-reporting tools as they are developed, including online tools (e.g. tools within MFMP or on the Department's website).

  • 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.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

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