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.”
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.
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. 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. 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.
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. The items provided under this contract document shall meet all of the following standards:
Final Acceptance Testing. There shall be a testing period during which we shall determine whether the System: (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. The testing period shall commence on the first Business Day after you have informed us in writing that you have completed the System, Service or Deliverables required to be performed prior to testing and that the System or Service are ready for testing, and the testing period shall continue for a period of up to sixty (60) days. 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. We shall notify you in writing of your final Acceptance or rejection of the System or Service, or any part thereof, within thirty (30) days after the end of the testing period, or as same may be extended by us. If we reject the System, Service or any part thereof, we shall provide notice identifying the criteria for final Acceptance that the System or Service failed to meet. Following such notice, you shall have thirty (30) days to (a) modify, repair, or replace the System, Service or any portion thereof, or (b) otherwise respond to our notice. If you modify, repair, or replace the System, Service or any portion thereof, the testing period shall re-commence consistent with the procedures set forth above in this section. In the event you fail to remedy the reason(s) for our rejection of the System, 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 Service as it then exists or to reject the System or Service and terminate the Agreement. If we elect to accept the System or 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 within a reasonable time as determined by us, then we shall ...
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.
Final Acceptance Testing. Provide the Agency the ability to test the system as a whole for X days to ensure it meets the Agency’s performance expectation. TRAINING
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.
