Acceptance Test Process Sample Clauses

Acceptance Test Process. 24 The Equipment Acceptance Test will be conducted over three (3) consecutive operating 25 days. The operating day shall be eight (8) hours in duration inclusive of scheduled break 26 periods (e.g. lunch, break, and scheduled clean-up). The start-time, break-time, end- 27 time will be predetermined by the Contractor and approved by the Authority. The 28 processing system run-time during the Equipment Acceptance Test, will be equal to time 29 the system is running and does not include scheduled break-times. Each operating day, 30 the Contractor is allowed thirty (30) minutes of unscheduled downtime. Equipment 31 stoppages that are not equipment related shall not be regarded as system downtime. 32 33 The following data will be recorded during the Equipment Acceptance Test:
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Acceptance Test Process. Unless otherwise agreed by the Parties, this Exhibit D describes the process used to test and accept features for inclusion on the Services (the “Acceptance Test Process”). The parties will cooperate in good faith to develop and implement communication mechanisms such that Cingular provides feedback to InfoSpace in a timely and efficient manner in order to facilitate Infospace’s ability to address such feedback. Cingular shall have the right to review and test any Deliverable to determine whether it conforms to specifications or acceptance criteria in the applicable Work Order or SOW (if any) or as otherwise agreed upon in writing by the Parties. Cingular may provide written notice of rejection (with detailed reasons for said rejection) or acceptance within the mutually agreed upon Acceptance Testing schedule from the date the Deliverable(s) are submitted by Infospace. • Following the date of delivery of a Deliverable(s) in commercial ready form (“Commercial Ready Delivery Date”), unless otherwise mutually agreed, Infospace and Cingular, prior to the beginning of test execution, will mutually agree to the following: • Schedule of test execution • Scope of test execution • Bug / Feature triage process In the event that agreed schedule must change, Infospace and Cingular will review the impact from a schedule, scope and cost perspective and will negotiate a new agreement associated with the particular Deliverable. • Following the Deliverable Acceptance Date, Infospace will commercially release the Deliverable at a mutually agreed time.
Sample 1Sample 2Sample 3

Related to Acceptance Test Process

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Test Procedures For an Asset Review, the Asset Representations Reviewer will perform for each Asset Review Receivable the procedures listed under “Procedures to be Performed” in Schedule A for each representation and warranty (each, a “Test”), using the Asset Review Materials listed for each such Test in Schedule A. For each Test and Asset Review Receivable, the Asset Representations Reviewer will determine if the Test has been satisfied (a “Test Pass”) or if the Test has not been satisfied (a “Test Fail”).

  • Acceptance; Rejection A holder of Notes may accept the offer to prepay made pursuant to this Section 8.3 by causing a notice of such acceptance to be delivered to the Company not later than 15 days after receipt by such holder of the most recent offer of prepayment. A failure by a holder of Notes to respond to an offer to prepay made pursuant to this Section 8.3 shall be deemed to constitute a rejection of such offer by such holder.

  • Performance Tests Contractor shall perform Performance Tests in accordance with Section 11.2 of the Agreement and Attachment S.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

  • Commissioning Commissioning tests of the Interconnection Customer's installed equipment shall be performed pursuant to applicable codes and standards. If the Interconnection Customer is not proceeding under Section 2.3.2, the Utility must be given at least ten (10) Business Days written notice, or as otherwise mutually agreed to by the Parties, of the tests and may be present to witness the commissioning tests.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Scope of Work The Contractor has overall responsibility for and shall provide and furnish all materials, equipment, tools and labor as necessary or reasonably inferable to complete the Work, or any phase of the Work, in accordance with the Owner’s requirements and the terms of the Contract Documents.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

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