Acceptance of the Software or Website shall be deemed to have taken place upon the occurrence of any of the following events:
10.2.1 the Software or Website has passed all relevant Acceptance Tests. The Company shall notify the Client when the tests have been passed and provide the results of the Acceptance Tests to the Client in writing;
10.2.2 the Client uses any part of the Software or Website for any revenue-earning purposes or to provide any services to third parties other than for test purposes; or
10.2.3 the Client unreasonably delays the Company in being able to the start of the relevant Acceptance Tests or any retests for a period of seven Business Days from the date on which the Company is ready to commence running such Acceptance Tests or retests.
Acceptance of the Software. Upon delivery by FRx of all of the Deliverables, PSC will review the Software, including the interface to PSC Products and Documentation, and notify FRx should the Software not function substantially as described in the Documentation, the Integration Program attached as Exhibit D and comply with the Acceptance Criteria defined in Exhibit J. In such case, FRx shall modify the Software and Documentation as necessary within a reasonable time after FRx's receipt of a notice from PSC describing in detail such deficiencies and shall deliver the revised material to PSC. PSC shall use all reasonable efforts to perform the necessary software and system integration testing as soon as practicable upon receipt of Software. Should PSC encounter technical difficulties in completing such integration and these difficulties are communicated to FRx, acceptance of Software will not occur until integration of Software with PSC Products is complete. Should PSC fail to advise FRx that Software does not substantially conform to Documentation or the Integration Program and advise FRx of the specific technical difficulties in completing the integration of Software to PSC Products within 30 days of receipt, Software and Documentation shall be deemed to be accepted by PSC.
Acceptance of the Software. Product and/or Customer Solution shall occur or be deemed to occur when all of its constituent Projects have been accepted pursuant to this clause 8.
Acceptance of the Software shall occur upon delivery by the Licensor to the Site of Licensee at the Software, as set forth In Schedule A.
Acceptance of the Software. The Software shall be deemed to have been fully accepted by the Customer upon the expiration of 10 working days from the date of this Agreement unless the Customer has formally expressed non-acceptance in writing within that period.
Acceptance of the Software. Once Conditional Acceptance of all of the Software Components has occurred, and the Software has been placed in a live production environment, City will operate the Software for a period of sixty (60) consecutive calendar days (“Live Testing”). During the Live Testing period, City will notify Vendor of any new issues that are discovered where the Software does not comply with the Functional Requirement and upon verification of such Defects by Vendor, they will be added to the Punch List Issues along with the agreed schedule for resolution of such issue. Any new issue discovered during the Live Testing period that is causing either the entire Software system or a core component(s) of the Software to be inoperable without a reasonable and effective workaround must be resolved prior to “Final Acceptance”, and will be considered a “Punch List Issue.” Vendor will resolve any critical issues in the onsite Acceptance environment, contingent on City’s willingness to provide remote access to that environment. Otherwise, issues will be resolved in the hosted test environment and periodic refreshes of the onsite environment will be performed for the purpose of re-testing. At such time as all Punch List Issues that are designated as being resolved prior to Final Acceptance have been resolved, then City will issue Final Acceptance. If a Punch List Issue that does not impair an essential function cannot reasonably be resolved within the Live Testing period, then Vendor will propose a schedule for the resolution of such issue for approval by City, which approval will not be unreasonably withheld. Upon final agreement as to the schedule for resolving all Punch List Issues remaining at the end of the Live Testing period, City will issue Final Acceptance. In the event Vendor and City disagree on whether Punch List Issues have been resolved or require resolution prior to Final Acceptance, then either Party may escalate the dispute accordingly, as set forth in the Statement of Work or the dispute resolution process set forth in this Agreement.
Acceptance of the Software. 8.1 To facilitate Party B’s development of Software that is adaptable to various technical parameters of the Mobile, Party A shall inform Party B of the production and/or sales plan as well as the related technical parameters of the Mobile which is to be installed with the Software at least 2 months prior to the production and/or selling, and shall provide Party B sufficient sample devices for backup. Party A shall provide testing equipment and materials on its site for conducting the acceptance work and Party B shall provide relevant technical and equipment assistance according to Party A’s requirement.
Acceptance of the Software. 7.1. Acceptance of the Software shall be deemed to have occurred on whichever is the earliest of:
(a) the expiry of 5 days after the completion of the last Acceptance Test, unless the Customer has given any written notice under Clause 6.2;
(b) the expiry of 10 days after the last Installation Date; or
(c) the first use of the Software by the Customer in the normal course of business after the Software is Ready for Service.
Acceptance of the Software. Customer is entitled to perform verification testing on delivered Software (the “base product”) to confirm receiving the product(s) as set forth in the Agreement and to confirm that the base products function as set forth in Exterro’s product documentation. Said testing shall be completed within ten (10) days after Exterro makes the base product(s) available to Customer (the “Acceptance Period”). If Customer reasonably determines that the base product made available to them differs from the Agreement, or that the product(s) fails to operate in accordance with the documentation, Customer shall notify Exterro and Exterro shall correct the error. Unless Customer notifies Exterro, in writing, that the Software failed the verification testing, within thirty (30) days after Exterro makes the Software available to the Customer, the base product(s) will be deemed to be accepted. Exterro will not begin configuration services or other Professional Services until such time as the Software has been accepted.
Acceptance of the Software. Product shall be deemed to take place on delivery. Acceptance of bespoke elements of the Software Product shall take place within 30 days of delivery unless written notice is otherwise given of the Software Product's non-performance when compared to the original request for said bespoke changes. If the Licensee uses the Software Product before the acceptance under this Clause, except for testing purposes (restricted to 14 days), then the Software Product shall be deemed to have been accepted on the date of first use.
