User Acceptance definition

User Acceptance as defined in Clause 6.2.
Sample 1Sample 2Sample 3
User Acceptance. Testing: Once Platform is set-up, Mercatus will provide key Customer users materials for User Acceptance Testing (UAT). Following Customer approval, Mercatus will proceed with full Customer training, which will have a mutually agreed upon rollout plan between the Customer and Mercatus across the Customer and any Portfolio companies. Any Change Requests to the approved FRD suggested by Customer will be tracked and communicated back to Customer for formal approval prior to configuration adjustments. These items will be scoped for time and cost impact and billed according to Exhibit D for applicable Professional Services rates. • Training: o Once ICS and UAT processes are complete, Mercatus will provide training to key Customer Administrators for managing a hosted environment in the Platform. Such initial training will equip Administrators to maintain and configure all key features to best accelerate broader user workings in the Platform. • Training Courses: Upon completion of Account Setup, Mercatus will deliver customized training as follows (See Exhibit D for Course Details): o Power User Training o Administrator Training o Model Custodian Training o Reporting Manager Training o Executive Training o Lite User Training • Logistics: o Power User Training is typically delivered onsite or virtually, with all materials available thereafter, but can be virtual for portfolio companies (to be mutually agreed upon with Customer). The Primary Instructor will work with your team to create an agenda and training package that speeds user time to value. Logistics will be mutually agreed between Mercatus and Customer. o Training is typically conducted over a two-day period. Day 1 focuses on Power User Navigation; Day 2 includes live workshops and another Administrator / Custodian Training. o Customer is required to have at least 1 (one) Named User(s) certified within Mercatus University achieving a minimum of the following levels: Navigator, Builder (recommended Administrator certification as well). Customer is responsible for maintaining this minimum number of Named User certifications throughout the term of the Agreement. • Post-Launch Training Tools: o Mercatus University: • Online Training Platform including custom training paths, videos, practice exercises, help articles, best practices recommendations. • Certifications available for all Power User, Admin & Custodian Roles o In-App Tutorials: • Standard walkthroughs guiding users through primary activities • Custom ...
Sample 1Sample 2
User Acceptance means the acceptance by NINL that the “ERP SOLUTION” (or any Subsystem(s) where the Contract provides for acceptance of the System in parts) is capable of attaining the functional and performance requirements (relating to commissioning) as specified in the Technical Requirements and Agreed and Finalized Project Plan in accordance with Clause 6.16
Sample 1

Examples of User Acceptance in a sentence

  • Service Levels SEAtS commit to make best efforts to meet the following service level objective(SLO) System Availability SLO Period( Local time) Measured By 99.5% 08:00 to 22:00 Mon- Fri SEAtS Availability Checker Exclusions This agreement covers software and data processing on the SEAtS Student Success Software Platform in a live environment where the customer has signed off their User Acceptance Testing (UAT) form.


More Definitions of User Acceptance

User Acceptance. Testing takes place in the System Test Environment. The development of the User Acceptance Test Plan and Criteria are the responsibility of U S WEST and the Clients. The System Test Environment must be established and made available by U S WEST by May 29, 1996. Establishment of the Environment is the responsibility of the U S WEST System Test Group. The Production Data, specifically the Routing Tables, must be specified and populated by U S WEST by July 31, 1996 for Production Release. The Production Environment must be established and made available by U S WEST by July 31, 1996. MARCH 27, 1996 Test Plans, Environments, Scenarios and Test Data must be identified by U S WEST and in place by the start of the Integration (5/6/96), User Acceptance (6/28/96), and System Test (5/29/96) Phases. The Test Data and Scenarios are the responsibility of the U S WEST Clients but will be shared by CGI. The System Test Plan is the responsibility of the U S WEST System Test Group. The dates for the final production builds for both Phase I & II are dependent on the dates that the U S WEST Project Manager sets for the start of each phases deployment, which may be sometime after the software has been accepted. CGI assumes that this date will be within two weeks after the software is accepted. Additional, specific CGI assumptions include: The detailed design and prototyping tasks need to be completed before the programming and unit testing tasks can begin. Formal technology transfer from CGI to U S WEST will be done in parallel to system and user acceptance testing and production support for the Phase II Release. This requires that the U S WEST engineers who will take over support and maintenance of the technology be brought on-board by May 29, 1996.
Sample 1
User Acceptance. Testing shall mean the period during which You shall be given the opportunity to test the Product with or without the customisations requested.
Sample 1
User Acceptance means the acceptance testing procedure for Software and Configuration Deliverables set out in paragraph 6 of this Schedule.
Sample 1

Related to User Acceptance

  • Final Acceptance means final written acceptance of all the Work by the Commissioner, a copy of which shall be sent to the Contractor.

  • Letter of Acceptance (LOA) means the written notice issued by JMRC to the selected bidder(s) intimating the acceptance of selected bidder's Proposal for the award of Lease;

  • Operational Acceptance means the acceptance by the Procuring Entity of the Facilities (or any part of the Facilities where the Contract provides for acceptance of the Facilities in parts), which certifies the Contractor's fulfillment of the Contract in respect of Functional Guarantees of the Facilities (or the relevant part thereof) in accordance with the provisions of GCC Clause 28 (Functional Guarantees) hereof and shall include deemed acceptance in accordance with GCC Clause 25 (Commissioning and Operational Acceptance) hereof.

  • Letter of Acceptance means the letter of formal acceptance, signed by the contractor. Procuring Entity, including any annexed memoranda comprising agreements between and signed by both Parties.

  • Conditional Acceptance means a conditional acceptance by the Liquidity Provider of an extension of the Scheduled Termination Date.

  • Letter of Acceptance of Tender means letter giving intimation to the tenderer that his tender has been accepted in accordance with the provisions contained in that letter.

  • Final Acceptance Date means, in respect of any Offer, the final date for acceptance of such Offer which, if such Offer is extended prior to becoming unconditional, shall be the final date for acceptance of the extended Offer (but, if such Offer is or becomes unconditional, disregarding any additional or further period during which such Offer is open for acceptance);

  • Operational Acceptance Tests means the tests specified in the Technical Requirements and Agreed Project Plan to be carried out to ascertain whether the System, or a specified Sub system, is able to attain the functional and performance requirements specified in the Technical Requirements and Agreed Project Plan, in accordance with the provisions of GCC Clause 27.2 (Operational Acceptance Test).

  • Competitive Bid Accept/Reject Letter means a notification made by a Borrower pursuant to Section 2.03(d) in the form of Exhibit A-4.

  • Multiple Exchange Carrier Access Billing or “MECAB” means the document prepared by the Billing Committee of the OBF, which functions under the auspices of the Carrier Liaison Committee (CLC) of the Alliance for Telecommunications Industry Solutions (ATIS). The MECAB document, published by ATIS as ATIS/OBF-MECAB- Issue 6, February 1998, contains the recommended guidelines for the billing of access services provided to an IXC by two (2) or more LECs, or by one LEC in two (2) or more states within a single LATA.

  • Acceptance Testing mean the tests, reviews and other activities that are performed by or on behalf of Agency to determine whether the Deliverables meet the Acceptance Criteria or otherwise satisfy the Agency, as determined by the Agency in its sole discretion.

  • Acceptance Test is a test of the Features executed by the Customer to prepare the acceptance.

  • Acceptance Tests means those tests performed during the Performance Period which are intended to determine compliance of Equipment and Software with the specifications and all other Attachments incorporated herein by reference and to determine the reliability of the Equipment.

  • IITK Purchase Order means the IITK’s official Purchase Order document;