Final System Acceptance. 1. Contractor shall close the Project (Phase 1 implementation of the CCRS solution) in accordance with the Project Close-Out Plan.
2. Contractor shall meet with the State two (2) weeks prior to the scheduled end of Project to confirm all Project Close-out Acceptance Criteria as identified in the Implementation Plan. The State will approve the criteria.
3. Contractor shall provide the State a Final Project Report to report onand confirm completion of the Project and Project close-out tasks.
4. The Contractor shall not receive Project and Contract Close- out approval from the State until all Project Close-out Acceptance Criteria identified in the Implementation Plan have been met and approved by the State. Project Close-out Acceptance Criteria includes:
5. Written State approval of System Acceptance
6. Written State approval for all Deliverables and final revisions of Deliverables
7. Written State approval of the Final Project Report
8. Written State approval of Project Close-out
9. At the onset of the Project Close-Out Period, the Contractor shall include Project Close-Out status reporting in the Weekly Status Report. The Project Close-Out portion of the Weekly Project Status Report shall include, at a minimum, a description of the progress made on each Task, Deliverable, and/ or Milestone, including any variance from the baseline.
10. The State will work closely with the Contractor during this process and must approve all updates to the Contractor's Project Close-Out approach and plans prior to starting Maintenance and Operations.
11. Contractor shall maintain key staff as identified in the Section 5: Contractor Roles and Responsibilities to satisfy and maintain compliance.
12. The system is operating in a manner meeting all the Functional and Non- functional Requirements of this Contract.
Final System Acceptance. Upon final completion of each component of the System, City and Contractor shall conduct an Acceptance Test. The criteria for the Acceptance Test shall be as set forth in the Scope of Services (EXHIBIT A). Final System Acceptance will occur upon successful completion of the Acceptance Test. When System Acceptance occurs, the Parties will memorialize the event by promptly executing the Final System Acceptance Certificate (APPENDIX A3). If the delivered System or Services do not meet the requirements of the acceptance test specifications, City will permit Contractor to repair the deficient System or Services so that the same meets the acceptance test specifications in all material respects, all at no additional expense to City. All warranties shall be effective during the term of this Agreement. 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/deliverables and reject upon notification to Contractor any and all which do not conform to the specifications or other requirements of this Agreement. Deliverables which are rejected shall be promptly corrected or repaired by Contractor in accordance with Contractor’s warranty obligations under this Agreement, such that the deliverables conform to the warranties, specifications, and the other requirements of this Agreement. If City receives deliverables with defects or nonconformities not reasonably apparent on inspection, then City reserves the right to require prompt correction or repair by Contractor in accordance with Contractor’s warranty obligations under this Agreement following the discovery of such defect or nonconformity. Agreement for Adaptive Traffic Control System Page 6 of 62 T-33626-17/1141358 Item: 2.12(a) Agenda: 08-29-2017
Final System Acceptance. 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. 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.
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:
i) Cancel this Agreement(Fees for all milestone...
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. After the System Integration Acceptance, live testing of the system shall be conducted for a thirty (30) calendar day period (Final System Acceptance Test). The Final System Acceptance test shall take place with no less than 75% of the locations set forth in Exhibit A which shall include, but not be limited to, North County Jail, Santa Xxxx Jail and the police department of cities of Berkeley, Oakland, Hayward and Fremont. "Final System Acceptance" shall mean the receipt by ORION of written notification from COUNTY that the live testing of the System has been successfully completed. The warranty (free maintenance) period shall commence upon the date of COUNTY notification that the Final System Acceptance was successful; which written notice shall be made no more than five (5) business days following the conclusion of the Final System Acceptance Test.
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.
Final System Acceptance. The purpose of Final System Acceptance Testing is to demonstrate and validate that all components (i.e.: Photo Imaging Systems, DB2 Systems, and Communications Subsystem) are integrated and that all interfaces to external systems are functional and meet the interface specifications as documented in the Interface Control Document. The Final System Acceptance test will be witnessed by the Buyer and NYCPD and requires the Buyer's formal written acceptance before considered complete. The Buyer will not consider Final System Acceptance complete until the Buyer receives formal written acceptance from NYCPD. The Buyer shall provide best efforts in obtaining system acceptance on the behalf of the Seller. The test procedures and test cases for the Final System Acceptance Test will be jointly developed by the Seller and the Buyer, and documented in the Interface Control Document. Attachment 7 - 6 Revision C Attachment 8 TRAINING
