Full Usability Test Sample Clauses

Full Usability Test. To confirm the source code placed in escrow will be fully functional in the event of a release, and to perform a relevant series of tests to ensure that replicated software runs properly in the required DMAS environment.
Sample 1Sample 2Sample 3See All (17)
AutoNDA by SimpleDocs
Full Usability Test a confirmation that the built applications work properly when installed.
Sample 1Sample 2Sample 3
Full Usability Test. To confirm the source code placed in escrow will be fully functional in the event of a release and to perform a relevant series of tests to ensure that replicated software runs properly in the required DSS environment. vi. Final Operability Test – To perform a final demonstration of the functioning software. vii. Fault Remedy – To collaborate with Supplier on fixing any faults discovered during the testing, to obtain corrected escrow items and to re-perform any verification tests as necessary until all tests are successful, with written detailed reports to DSS. Supplier warrants that the Escrow Agreement provides for, among other items, the release of the list of items on Attachment A of the Escrow Agreement upon the happening of certain events, including, but not limited to, Supplier’s failure to carry out its support and maintenance obligations imposed by this Contract for a period of sixty (60) days, Supplier’s breach or default under this Contract, Supplier’s bankruptcy, Supplier’s failure to continue to do business in the ordinary course. Supplier agrees to pay all expenses associated with establishing and maintaining the escrow account and the contents mentioned above. Subject to the information and materials listed on Attachment A of the Escrow Agreement being released to the Commonwealth pursuant to the terms of the Escrow Agreement, Supplier hereby grants to the Commonwealth a royalty-free, perpetual, irrevocable license, that permits disclosure to a third party support-vendor of a complete and accurate copy of then-current source code for the Software licensed hereunder, along with all related documentation. CONFIDENTIALITY
Sample 1

Related to Full Usability Test

  • Stability Testing Patheon may be requested to conduct stability testing on the Products in accordance with the protocols set out in the Specifications for the separate fees and during the time periods set out in Schedule C to a Product Agreement. Patheon will not make any changes to these testing protocols without prior written approval from Client. If a confirmed stability test failure occurs, Patheon will notify Client within one Business Day, after which Patheon and Client will jointly determine the proceedings and methods to be undertaken to investigate the cause of the failure, including which party will bear the cost of the investigation. Patheon will not be liable for these costs unless it has failed to perform the Manufacturing Services in accordance with the Specifications, cGMPs, and Applicable Laws. Patheon will give Client ail stability test data and results at Client’s request.

  • Acceptance Testing At the time of installation of a LIS trunk group, and at no additional charge, acceptance tests will be performed to ensure that the service is operational and meets the applicable technical parameters.

  • Excess Cash Flow No later than ten (10) Business Days after the date on which the financial statements with respect to each fiscal year of Holdings ending on or after December 31, 2019 in which an Excess Cash Flow Period occurs are required to be delivered pursuant to Section 5.01(a) (each such date, an “ECF Payment Date”), the Borrower shall, if and to the extent Excess Cash Flow for such Excess Cash Flow Period exceeds $1,375,000, make prepayments of Term Loans in accordance with Section 2.10(h) and (i) in an aggregate amount equal to (A) the Applicable ECF Percentage of Excess Cash Flow for the Excess Cash Flow Period then ended (for the avoidance of doubt, including the $1,375,000 floor referenced above) (B) minus $1,375,000 minus (C) at the option of the Borrower, the aggregate principal amount of (x) any Term Loans, Incremental Term Loans, Revolving Loans or Incremental Revolving Loans (or, in each case, any Credit Agreement Refinancing Indebtedness in respect thereof), in each case prepaid pursuant to Section 2.10(a), Section 2.16(b)(B) or Section 10.02(e)(i) (or pursuant to the corresponding provisions of the documentation governing any such Credit Agreement Refinancing Indebtedness) (in the case of any prepayment of Revolving Loans and/or Incremental Revolving Loans, solely to the extent accompanied by a corresponding permanent reduction in the Revolving Commitment), during the applicable Excess Cash Flow Period (or, at the option of the Borrower and without duplication, after such Excess Cash Flow Period and prior to such ECF Payment Date) and (y) the amount of any reduction in the outstanding amount of any Term Loans or Incremental Term Loans resulting from any assignment made in accordance with Section 10.04(b)(vii) of this Agreement (or the corresponding provisions of any Credit Agreement Refinancing Indebtedness issued in exchange therefor), during the applicable Excess Cash Flow Period (or, at the option of the Borrower and without duplication, after such Excess Cash Flow Period and prior to such ECF Payment Date), and in the case of all such prepayments or buybacks, to the extent that (1) such prepayments or buybacks were financed with sources other than the proceeds of long-term Indebtedness (other than revolving Indebtedness to the extent intended to be repaid from operating cash flow) of Holdings or its Restricted Subsidiaries and (2) such prepayment or buybacks did not reduce the amount required to be prepaid pursuant to this Section 2.10(f) in any prior Excess Cash Flow Period (such payment, the “ECF Payment Amount”).

Time is Money Join Law Insider Premium to draft better contracts faster.