Final Acceptance Testing. Broward County Administrative Code Section 22.148 requires that all applicable software purchases be inspected and tested by the County, including verification by its Enterprise Technology Services (“ETS”), prior to final written acceptance of the software and software-related services. Within thirty (30) days following completion of all Services stated in Exhibit A relating to the installation, implementation, and integration of the Products and System provided under this Agreement, County shall conduct testing to determine whether the System: (i) properly functions with any applicable operating software; (ii) provides the capabilities stated in this Agreement and the Documentation; and (iii) if applicable, meets the acceptance criteria stated in the Statement of Work (the criteria referenced in (i), (ii), and (iii) are collectively referred to as the “Final Acceptance Criteria”). In the event of a conflict between the Documentation and the acceptance criteria stated in the Statement of Work, the Statement of Work shall prevail. Final payment shall not be made to Contractor prior to the written confirmation by the County’s Chief Information Officer or his or her designee that the Products and System have successfully passed the Final Acceptance Criteria, and such written confirmation shall constitute “Final Acceptance.”
6.2.1. The testing period shall commence on the first business day after Contractor informs County in writing that it has completed the Services required to be performed prior to testing and that the System is ready for testing, and shall continue for a period of up to thirty (30) days. During the testing period, County may notify Contractor in writing of any error or defect in the System so that Contractor may make any needed modifications or repairs. If Contractor so elects in writing, testing will cease until Contractor resubmits for Final Acceptance testing, at which time the testing period shall be reset to that of a first submission for testing.
6.2.2. County shall notify Contractor in writing of its Final Acceptance or rejection of the System, or any part thereof, within fifteen (15) days after the end of the testing period, as same may be extended or reset. If County rejects the System, or any part thereof, County shall provide notice identifying the criteria for Final Acceptance that the System failed to meet. Following such notice, Contractor shall have thirty (30) days to (a) modify, repair, or replace the System or any portion ...
Final Acceptance Testing. There shall be a testing period during which we shall determine whether the System or a Service: (i) properly functions on the Equipment and with any applicable operating software; (ii) provides the capabilities as stated in this Agreement and in the Documents; and (iii) to the extent stated, meets the acceptance criteria. In the event of a conflict between the acceptance criteria and the Documents, the Acceptance criteria shall prevail.
3.1 The testing period shall commence on the first Business Day after you have informed us in writing that you have completed the System, a Service or Deliverables required to be performed prior to testing and that the System or a Service are ready for testing, and the testing period shall continue for a period of up to thirty (30) days.
3.2 During the testing period, we may notify you in writing of any error or defect in the System so that you may make any required modifications or repairs. If you so elect in writing, testing will cease until you resubmit for final Acceptance testing, at which time the testing period shall be reset to that of a first submission for testing.
3.3 We shall notify you in writing of your final Acceptance or rejection of the System or a Service, or any part thereof, within fifteen (15) days after the end of the testing period, or as same may be extended by us. If we reject the System, a Service or any part thereof, we shall provide notice identifying the criteria for final Acceptance that the System or a Service, failed to meet. Following such notice, you shall have thirty (30) days to (a) modify, repair, or replace the System, Services or any portion thereof, or (b) otherwise respond to our notice. If you modify, repair, or replace the System, a Service or any portion thereof, the testing period shall re-commence consistent with the procedures set forth above in this section.
3.4 In the event you fail to remedy the reason(s) for our rejection of the System, a Service or any portion thereof, within thirty (30) days after our initial notice of rejection, we may elect, in writing, to either accept the System or a Service as it then exists or to reject the System or a Service and terminate the Agreement.
3.5 If we elect to accept the System or a Service as it then exists (partial acceptance), you shall continue to use your best efforts to remedy the items identified in the applicable notice of rejection. If, despite such continuing best efforts, you fail to remedy the issue(s) identified by us wit...
Final Acceptance Testing. 7.1 IXI acknowledges and agrees that, prior to the commercial launch of the ICQ Services on any Approved Complete ICQ Application on a specific model of Compliant Device, and at ICQ’s option, ICQ and, IXI, shall jointly conduct end to end acceptance testing of the Approved Complete ICQ Application on that Compliant Device to determine if the Approved Complete ICQ Application on that Compliant Device conforms in all material respects with an acceptance test plan that shall be mutually agreed upon by the Parties and attached to this Agreement as Exhibit G (each, an “Acceptance Test Plan”). IXI acknowledges and agrees that, at ICQ’s option, (i) such end to end testing shall include testing of the IXI Server or the Third Party Developer Server and (ii) IXI shall be required to provide access to the IXI Server or the Third Party Developer Server for such end to end testing. For purposes of clarification, IXI acknowledges and agrees that IXI shall not make an Approved Complete ICQ Application commercially available until ICQ and IXI jointly determine that such Approved Complete ICQ Application for any specific Complaint Device has passed such end to end testing; provided, however, that ICQ in its sole discretion may waive its right to conduct such end to end testing. No later than ten (10) business days following completion of such end to end testing, ICQ shall notify IXI in writing regarding whether it deems the tested Approved Complete ICQ Application to have passed or failed such end to end testing, and a description of any defects (“Acceptance Testing Notice”). IXI shall correct any deficiencies identified by either Party in the Acceptance Testing Notice related to the tested Approved Complete ICQ Application. Connection between the ICQ Network and the Approved Complete Application (which, for purposes of this Section shall run via the IXI Server or the Third Party Developer Server) shall be subject to a technical requirements document that shall be mutually agreed to by the Parties within thirty (30) days from the Effective Date and which shall be amended by the mutual agreement of the Parties (“Technical Requirements Document”). The Technical Requirements Document and any amendments thereto shall be attached as Exhibit H to this Agreement. Each Party will bear its own costs associated with the connection. IXI shall ensure that, where applicable, all data transmitted between the IXI Server or the Third Party Developer Server and access points on a mobile co...
Final Acceptance Testing. 8.1. Contractor and City hereby acknowledge that certain testing, such as a point test, are for a specific moment in time. Contractor is deploying an unlicensed wireless network, so there could be a case of interference at a test point that may be perfectly normal. The System is capable to make adjustments on interference. Since Contractor does not control the air space which can impact performance (i.e., high internet traffic or interference may cause slow performance), acceptance testing requirements shall be mutually agreed upon to account for these anomalies.
8.2. The Final System Acceptance Test shall occur at the completion of the entire system. Notwithstanding Section 8.1 above, the Final System Acceptance Test shall consist of a thirty (30) day test period of all system operations without failure of the equipment or software.
8.3. The purpose of the test is to demonstrate that the total system (hardware, software, networking system, materials and construction) is properly installed, is free from identified problems, exhibits stable and reliable performance, and complies with the requirements within this scope of work.
8.4. In the event of a failure during the Final System Acceptance Test, the Contractor shall replace or repair the equipment and the Project Manager shall restart the 30-day test for the entire system, unless the City agrees the failed and replaced/ repaired equipment is not a major component that does not require a restart of the 30-day test for the entire system.
8.5. Resumption of the test for the remainder of the 30-day period shall occur after satisfactory remedial action.
8.6. Final System Acceptance will occur upon successful completion of the Final System Acceptance Testing as described in Section 7 above. When Final System Acceptance occurs, the parties will memorialize this event by promptly executing a Final System Acceptance Certificate (Appendix A4).
8.7. Contractor shall provide final records, including as-built drawings and documentation for all equipment and equipment locations before the final acceptance testing.
Final Acceptance Testing. Final acceptance shall be evidenced by the City’s written certification to Bidder that all vehicles, parts and components have been successfully delivered and installed by the Bidder, are operational and inspected and accepted by the City. The acceptance of such items shall be based on the items meeting, to the satisfaction of the City, the acceptance standards set forth in the contract document.
(i) All components shall be in good working order and operational upon Final Acceptance.
(ii) All components shall be supplied from Bidder.
(iii) All model and/or parts shall consist of the highest quality materials.
(iv) All components shall be in good, undamaged condition.
Final Acceptance Testing. Maintenance and support The successful outcome of the project is defined by the following: • Completed in accordance with this Contract and applicable project management planning documentation; • Resolution of all material functional and operational deficiencies prior to deployment in the production environment; • Completed within budget; • Configured to meet all specified requirements and needs of the State; • The Solution meets and adheres to all requirements and time frames set forth in service level terms set forth herein; • The Solution is fully documented, including, but not limited to, As-built documentation, requirements specifications, architecture, design, configuration, operational environment and user manuals; and • Trained technical support staff, dispatch personnel and stakeholders.
Final Acceptance Testing. 8.1. The Final System Acceptance Test shall occur at the completion of the entire system. The Final System Acceptance Test shall consist of a thirty (30) day test period of all system operations without failure of the equipment or software.
8.2. The purpose of the test is to demonstrate that the total system (hardware, software, networking system, materials and construction) is properly installed, is free from identified problems, exhibits stable and reliable performance, and complies with the requirements within this scope of work.
8.3. The system shall consistently and accurately reflect count information, process and display correct information on the signs without system downtime or failure.
8.4. In the event of a failure during the final system acceptance test, the Contractor shall replace or repair the equipment and the Project Manager shall restart the 30-day test only for that piece of equipment.
Final Acceptance Testing. The final acceptance test will verify that the entire system, with the changes and additions made during the operational testing in place, functions properly and in accordance with these requirements. The final acceptance test shall not be completed until all items conform to the requirements and training has been completed as approved by the City. The Contractor shall perform and document all necessary testing. The Contractor shall coordinate with the City to schedule final acceptance testing. The formal start of the final acceptance test or “burn-in” period shall be documented by the Contractor and shall not commence until approved by the City. The final acceptance test will include the completion of a 60-day period, by the end of which the entire integrated system operates without failure. In the event of a failure during the 30-day acceptance-testing period, the Contractor shall repair the equipment as necessary within five (5) working days of the time of notification by the City and the final acceptance test must be restarted at zero hours. If the failure is a signal system emergency, a qualified representative from the software and hardware manufacturer shall respond and implement a resolution within four hours of notification. Signal system emergencies are defined as a condition related to the malfunctioning of the signal hardware or software that impedes normal operation of the traffic signal, such as going into flash. The Contractor shall be responsible for all costs involved in the repair of the equipment, including retesting if necessary. One hardcopy and one electronic copy of testing report documenting all testing results shall be submitted to the City. Testing shall be measured by a lump sum price. The contract lump sum price paid for Testing for shall include full compensation for furnishing all labor, equipment, tools, materials, incidentals, preparation required and for doing all the work involved in Operational and performance testing of traffic signal controllers and ATMS, final acceptance testing, and testing report as described herein, as specified in the Standard Specifications, these Technical Provisions and as directed by the Engineer and no additional compensation will be allowed there for.
Final Acceptance Testing. Medtronic and IntriCon will collaborate and be responsible for completing final acceptance testing (“FAT”) on the ANH3. This will include all mechanical and software functional testing, software code review and sustaining runs to prove each System’s performance fit for production. Upon completion of the FAT, Medtronic will provide Supplier with a signed FAT Report as per MPROC’s CSV policy. IntriCon’s quality system allows linkage for IIN software validation in the IQ. Initially the automation will be qualified without the IPARC, Oven and tray re-package system.
Final Acceptance Testing. The City shall begin the Final Acceptance testing as follows: The parties shall agree on the start date for the Acceptance test. The Acceptance test shall include ninety (90) Days of continuous operation of the work without material defect in accordance with the Contract in the City’s fully implemented production environment. If the City accepts the work, the City will send a notice of Final Acceptance to the Contractor. If the City determines that the work is not acceptable, the City shall notify the Contractor, describing the deficiencies. The Contractor shall either provide a detailed, written plan to achieve Final Acceptance or to make corrections or replacements within a mutually agreed upon time period. The parties shall mutually agree on a start date for beginning another Acceptance test. Another ninety (90) Day successful operation period shall follow any corrections or replacements to the Work. Two (2) or more ninety (90) Day operation Acceptance test periods can occur if mutually agreed to by the parties. If the City accepts the work following a second or subsequent Acceptance test, the City will send a notice of Final Acceptance to the Contractor. If the Contractor does not correct or replace the unacceptable work the City may declare a material breach of Contract.
