Final System Acceptance Sample Clauses

Final System Acceptance. The Final System Acceptance shall be achieved when [***…***] meet the applicable requirements of Part II of Appendix F (including any waivers or deviations approved by Purchaser pursuant to Article 11.6). [***…***]. Upon the successful achievement of the Final System Acceptance in accordance with the terms of this Article 10.4.1 and applicable requirements of Part II of Appendix F (including any waivers or deviations approved by Purchaser pursuant to Article 11.6), Contractor shall be paid the Final System Acceptance Milestone.
AutoNDA by SimpleDocs
Final System Acceptance. 5.1.4.7. Project Close Out Tasks; and,
Final System Acceptance. After all four Releases are completed; the Contractor shall provide an additional final requirements-based acceptance test. The Contractor shall validate the system by the user community to verify satisfaction of user requirements in accordance with the criteria developed in accordance with this Agreement. The State shall validate final acceptance in a production environment with guidance and assistance from the Contractor’s testing specialists, to ensure that the system meets the user requirements. Final System Acceptance shall proceed as set forth in the Agreement.
Final System Acceptance. 1. Contractor shall close the Project (Phase 1 implementation of the CCRS solution) in accordance with the Project Close-Out Plan.
Final System Acceptance. Upon completion of the commissioning period for the System, City and Contractor shall conduct a final acceptance test upon the System. The criteria for the final acceptance test is noted in Exhibit A - Scope of Services. When final acceptance occurs, the parties will document this event by promptly executing a System Acceptance Certificate. All warranties shall become effective and begin to run upon the successful completion of the final acceptance test. If, in the reasonable discretion of City, the System does not meet the requirements of the final acceptance test specifications, City shall permit Contractor to repair or replace the System so that the same meets the Acceptance Test specifications in all material respects, all at no additional expense to City. Payment for any part or parts of the System or Services provided hereunder, or inspection or testing thereof by City, shall not constitute acceptance or relieve Contractor of its obligations under this Agreement. City may inspect the components of the System when delivered and reject upon notification to Contractor any and all of the System which does not conform to the Specifications or other requirements of this Agreement. Components of the System which are rejected shall be promptly corrected, repaired, or replaced by Contractor in accordance with Contractor’s warranty obligations under this Agreement, such that the System conforms to the warranties, Specifications and the other requirements of this Agreement. If City receives components of the System with defects or nonconformities not reasonably apparent on inspection, then City reserves the right to require prompt correction, repair, or replacement by Contractor in accordance with Contractor’s warranty obligations under this Agreement following the discovery of such defect or nonconformity.
Final System Acceptance. Final System Acceptance will occur as described in Exhibit C as may be amended as described in Section 3.2. Notwithstanding, the Final System Acceptance will be deemed complete upon Live Operations Cut Over, and after any applicable reliability period when all deliverables have been completed. When Final System Acceptance occurs, the Parties will promptly memorialize this final event by so indicating on the System Acceptance Certificate.
Final System Acceptance. 1. Contractor shall deploy Release 5 (meeting all Requirements) by March 1, 2021.
AutoNDA by SimpleDocs
Final System Acceptance. Contractor shall demonstrate to the City’s satisfaction that the equipment complies with the features and functionality agreed upon in the final post-contract detailed design documentation. Final system acceptance requires, but is not limited to, the following: ● Completion of all system component, hardware, and software delivery, installation, training, testing, integration, phase-over, as-built documentation, and contract deliverables. ● Written certification by Contractor of compliance with the performance requirements. ● Successful completion of a 30-day operational test. Critical and Major failures, as defined in Appendix D, Section 13 “Functional Acceptance Test Plan” will result in repeating the 30-day test. ● Correction of all punch-list items found during the acceptance test plans and 30-day operational test. ● City sign-off on the above.
Final System Acceptance. When all of the licensed standard software, standard and custom interfaces, contracted enhancements, and individual modules and data are installed and functioning, fully integrated with other System modules and the systems identified in Exhibit A, D, E, K, and L of this Agreement and have received Contractor Certification and have passed the County's Functional Acceptance, the County will begin training and go-live planning. Once training and go-live have occurred, County may begin the process to accept or reject the System by operating the System in a production environment in accordance with its normal operating practices over a 60 calendar day period to determine if the System is free from error that interferes with the normal operation of the System and the reliability standards set forth in Section 4.1-4.8 of this Agreement. County's acceptance, conditional acceptance, or rejection shall be by written notice. If a conditional acceptance or rejection is made, County's notice shall set forth in reasonable detail the basis for its position. The Contractor shall have fifteen (15) days to cure, or if cure within that time is not possible, to begin and diligently pursue the cure of, the defects noted by County by either (a) modifying or adjusting the System; (b) replacing or adding such components as may be necessary to make the system free from error that interferes with the normal operation of system; or (c) by mutual agreement of the parties, reducing the price by an amount to be mutually agreed; if no reduction can be agreed to within thirty days after the County requested re-negotiation, then the Contractor shall perform under either clause (a) or (b) above. After any adjustment, modification, repair or replacement by the Contractor under the Section, any relevant portions of the tests described herein shall be run again for County to determine its acceptance or rejection of the System. If after again running any relevant portion of the tests described herein of this Agreement, the System still fails to be free from error that interferes with the normal operation of system, the County shall set forth in reasonable detail the basis for its position. The Contractor shall have fifteen (15) business days to cure and the process repeats once more. If after the second repetition, the System still fails to be free from error that interferes with the normal operation of system then County shall have the right to:
Final System Acceptance. The purpose and content for each of the Acceptance Tests is summarized in Exhibit 4-1 and described in the following sections. The Seller is responsible for conducting the Acceptance Testing for the Photo Imaging Systems, as defined in Section 4.1. The Seller is responsible for supporting and participating in the Final System Acceptance Test, as defined in Section 4.2.
Time is Money Join Law Insider Premium to draft better contracts faster.