UAT Sample Clauses

UAT. After validation, TOMIA will notify Customer that the Software is Ready for Test, and Customer shall have ten (10) business days (the “Acceptance Period”) to complete UAT. Customer shall provide TOMIA reasonable notice of UAT so that TOMIA may attend and participate, at its election. The Software shall be deemed to be accepted at the earlier of: (a) the end of the Acceptance Period, unless Customer has notified TOMIA that the Software does not operate substantially in accordance with the Documentation as demonstrated by the test case results; or (b) the date that the Software begins being used in a production environment. If, prior to the end of the Acceptance Period, Customer notifies TOMIA in writing that the agreed test cases show that the Software does not operate substantially in accordance with the Documentation, TOMIA will use reasonable commercial efforts to correct or to provide a workaround for the Error(s). For the avoidance of doubt, the Software shall be deemed to operate “substantially in accordance” with the Documentation if an acceptable Restoration (work around) or Resolution (permanent fix) has been provided for Severity Level 1 (Software is inoperable) or Severity Level 2 (significant functions of the Software are inoperable) tickets identified during UAT that would result in significant business impact to Customer in production use. TOMIA shall not be obligated to correct Errors that occur because (a) the Software has not been used in accordance with TOMIA’s instructions or the Documentation; (b) the Software has been altered, modified, or converted by Customer without the prior written approval of TOMIA; (c) of the malfunctioning of Customer’s hardware or software; or (d) the Software, or any portion of the Software, has become inoperable due to other causes outside the control of TOMIA. Customer shall have two (2) business days to provide TOMIA with a Certificate of Acceptance after the software has been accepted or deemed accepted. If TOMIA is unable to make the Software operate substantially in accordance with the Documentation within a reasonable period of time, either Party may terminate this License Agreement and upon such termination, Customer shall be entitled to recover the License Fee paid to TOMIA for the affected Software.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
UAT. The ASL must outline acceptable defect counts by severity for the State User Acceptance Testing.
Sample 1

Related to UAT

  • Scaling “Scaling,” as used herein, involves:

  • Progressive Discipline Both parties endorse the principle of progressive discipline as applied to professionals.

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

  • Functionality Customer is entitled to additional functionality previously purchased or bundled with the software if available in the version or update released on or after the start date of the Agreement. Customer acknowledges that certain functionality in current and previous software versions may not be available in future upgrades. Added functionality may require additional paid services (clinical and technical) to configure and support.

  • Protocol The attached Protocol shall be an integral part of this Agreement.

  • Smoke Detectors At Owner's expense, smoke detectors will be installed on the Property in working condition in accordance with the law prior to the tenant's occupancy. During the occupancy, it shall be the tenant's responsibility to maintain all smoke detectors. Owner will replace smoke detector equipment as needed.

  • Searchability Offering searchability capabilities on the Directory Services is optional but if offered by the Registry Operator it shall comply with the specification described in this section.

  • Training Program It is agreed that there shall be an Apprenticeship Training Program, the provisions of which are set forth in Exhibit "C", which is attached hereto and forms part of this Agreement.

  • CULTURAL DIVERSITY The Cultural Diversity Requirement generally does not add units to a student's program. Rather, it is intended to be fulfilled by choosing courses from the approved list that also satisfy requirements in other areas of the student’s program; the exception is that Cultural Diversity courses may not satisfy Culture and Language Requirements for B.S. students. For example, Ethnic Studies 134 can fulfill (3) units of the Behavioral Science requirement and (3) units of the Cultural Diversity requirement. This double counting of a class may only be done with the Cultural Diversity requirement. Courses in Cultural Diversity may be taken at the lower-division or upper-division level. U . S . H I S T O R Y I N S T I T U T I O N A L R E Q U I R E M E N T HIS 100, 201

  • Signaling protocol The Parties will interconnect their networks using SS7 signaling where Technically Feasible and available as defined in GR 905 Telcordia Standards including ISDN User Part (ISUP) for trunk signaling and TCAP for CCS-based features in the Interconnection of their networks. All Network Operations Forum (NOF) adopted standards shall be adhered to. Where available, CenturyLink signaling services to link its Signaling Transfer Points (STPs) for CLEC switches which connect to CenturyLink’s STPs via “A” links or for CLEC’s STPs to connect to CenturyLink’s STPs via “D” links which are dedicated to the transport of signaling for local Interconnection, may be ordered from the CenturyLink Tariff.

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