SOFTWARE ACCEPTANCE Sample Clauses
POPULAR SAMPLE Copied 69 times
SOFTWARE ACCEPTANCE. The County shall be deemed to have accepted each software product unless the County, within 30 days from the installation date, gives Contractor written notice to the effect that the software product fails to conform to the functional and performance specifications, which, if not attached, are incorporated by reference. The Contractor will, upon receipt of such notice, investigate the reported deficiencies. The right of the parties shall be governed by the following:
1. If it is found that the software product fails to conform to the specifications and the Contractor is unable to remedy the deficiency with 60 days, the County shall return all material furnished hereunder and this Contract shall be terminated.
2. If it is found that the software product fails to conform to the specifications and the Contractor, within 60 days of receipt of the above said notice, corrects the deficiencies in the software product, the County will provide the Contractor with written acknowledgement of its acceptance of said software product.
3. If it is found that the software product does, in fact, conform to the specifications, the County shall reimburse the Contractor for the time and material cost of the investigation at the rates specified in this Contract. The County’s acceptance of the software product is contingent upon the software product conforming to function and performance specifications and the Contractor delivering adequate users manuals within 30 days from the installation date.
SOFTWARE ACCEPTANCE. Customer acknowledges that the CentralSquare Software shall be deemed accepted on the date of delivery. In the event that a Customer notifies CentralSquare of a material non-conformity in the Software as compared with the Statement of Work, CentralSquare shall use commercially reasonable efforts to correct the reported non-conformity in accordance with the support provisions set forth in Exhibit D: Maintenance Agreement. This provision does not apply to System Acceptance, which will be achieved in accordance with the implementation, acceptance, and Go Live process as defined in the Statement of Work.
SOFTWARE ACCEPTANCE. If Supplier will provide any software under the Contract, upon installation of any software by Supplier, Supplier shall demonstrate to UTMB the operation of the software in UTMB’s test and live environments as performing in accordance with the provided documentation and specifications.
(a) Acceptance of software shall occur after thirty (30) consecutive calendar days of Stable operation following First Productive Use. At UTMB’s option, the running of the thirty (30) calendar day period may be halted from time to time for non-Urgent Issue(s), and shall be restarted to day zero for Urgent Issue(s), as defined herein. Upon successful completion of the thirty (30) calendar day period, UTMB shall notify Supplier in writing of UTMB’s acceptance of the software, which notice shall not be unreasonably withheld.
SOFTWARE ACCEPTANCE. (a) Prior to Software acceptance by Customer, Customer has the right to operate the Software furnished by Seller on the Designated Processor solely for the purpose of conducting an Acceptance Test (means the test which may be performed by Customer during the Acceptance Test Period to determine whether Software will be free from defects which materially affect performance in accordance with the Seller's Specifications). Unless otherwise agreed by the parties, the Acceptance Test Period (means the period of time in days agreed to by the parties and specified in this section) for Software shall be eighteen (18) consecutive calendar days from the ship date if Customer performs installation or from the Installation Complete Date if Seller performs installation. The Software shall be deemed accepted by Customer unless Customer notifies Seller in writing to the contrary within the applicable Acceptance Test Period described above. If Seller receives written notice from Customer during the Acceptance Test Period that the Software failed the Acceptance Test, the Acceptance Date (the date on which the Software successfully completes the Acceptance Test) shall be extended on a day-to-day basis until such time as the Software passes the Acceptance Test. ***CONFIDENTIAL TREATMENT REQUESTED*** Lucent Technologies Proprietary 18 LNM980716RMPT
(b) If Customer elects in the order not to perform Acceptance Tests for any Software, the Acceptance Date for such Software shall be the Delivery Date if not installed by Seller or the Installation Complete Date if installed by Seller, as applicable.
(c) For any Acceptance Test conducted by Customer on newly licensed Software, and in the event that Customer encounters difficulties, Seller will, at Customer's request and for the standard rate in effect at the time of the request, provide technical assistance to Customer.
(d) If Customer performs installation and elects to perform applicable tests for any Software, the warranty for such Software shall commence on the Delivery Date.
SOFTWARE ACCEPTANCE. Lessee's execution of this Agreement acknowledges that all Software set forth above is to be received and installed and lessee will be accepting the latest version of the Software. Lessee agrees to accept the Software “as is”. Updates will be released periodically for the Software to improve functionality and lessee hereby agrees to accept the most recent publicly available version via automatic update.
SOFTWARE ACCEPTANCE. The County shall be deemed to have accepted each software product unless the County, within 30 days from the installation date, gives contractor written notice to the effect that the software product fails to conform to the functional and performance specifications, which, if not attached, are incorporated by reference. The contractor will, upon receipt of such notice, investigate the reported deficiencies. The right of the parties shall be governed by the following:
SOFTWARE ACCEPTANCE. If Supplier will provide any software under the Contract, upon installation of any software by Supplier, Supplier shall demonstrate to ▇▇▇▇▇ University the operation of the software in ▇▇▇▇▇ University’s test and live environments as performing in accordance with the provided documentation and specifications.
(a) Acceptance of software shall occur after thirty (30) consecutive calendar days of Stable operation following First Productive Use. At ▇▇▇▇▇ University’s option, the running of the thirty (30) calendar day period may be halted from time to time for non-Urgent Issue(s), and shall be restarted to day zero for Urgent Issue(s), as defined herein. Upon successful completion of the thirty (30) calendar day period, ▇▇▇▇▇ University shall notify Supplier in writing of ▇▇▇▇▇ University’s acceptance of the software, which notice shall not be unreasonably withheld.
SOFTWARE ACCEPTANCE. Once software has been physically received, the Contractor shall consider the Product accepted for use in order to comply with the Sarbanes Oxley reporting requirements; however, the State has additional acceptance criteria, which will be used to justify product returns. Eligible users who have software installation permissions granted by the user’s agency shall be responsible for determining acceptance of products purchased. Minimum acceptance criteria are as follows:
SOFTWARE ACCEPTANCE. VAR represents that it fully examined and tested the Licensed Software in connection with VAR’s plans to distribute the Licensed Software as set forth in this Agreement. VAR acknowledges that the Licensed Software is fully acceptable to VAR.
SOFTWARE ACCEPTANCE. 21 2.8 MODIFICATIONS BY CUSTOMER TO USER CONTROLLED MODULES: ..................22 2.9 ADDITIONAL SOFTWARE RIGHTS FOR 5ESS(R) SWITCH LICENSED MATERIALS ....