User Acceptance definition

User Acceptance as defined in Clause 6.2.

AI-Powered Contracts

Draft, Review & Redline at the Speed of AI

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. • 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 walkthroughs available upon request with independent ...

User Acceptance means the acceptance testing procedure for Software and Configuration Deliverables set out in paragraph 6 of this Schedule.

Examples of User Acceptance in a sentence

Determination made by the Department upon successful User Acceptance Test that the Deliverable, or if applicable, System, performs to the Specifications and fulfills the business and technical requirements of the Contract.
Assisted Upgrades: o Includes upgrade tasks and guidance / expertise only; o Does not include costs associated with Travel & Accommodation or directly undertaking customer specific User Acceptance Testing, Project Management, Change Management, or performing configuration tasks that are not strictly required for the upgrade process to complete successfully.
User Acceptance Testing for each Deliverable begins as of the date the Department notifies the Contractor in writing that the Deliverable provided for UAT has been successfully installed in the Department’s development and testing computer environment and is ready for UAT.
Ensure the language in this section does not conflict with the VITA Contract language.) Acceptance Criteria for this Solution will be based on a User Acceptance Test (UAT) designed by Supplier and accepted by the Authorized User.
Agency will notify Contractor in writing of each Defect discovered during UAT in accordance with the Accepted User Acceptance Test Plan, and specify its level.
Such Certification means Deliverables and Services are completed materially in accordance with Specifications and that they are ready for User Acceptance Testing by Customer in a non- productive test mode (“Test System”).
Determination made by the Purchasing Entity upon successful User Acceptance Test that the Deliverable, or if applicable, System, performs to the Specifications and fulfills the business and technical requirements of the Contract.
After the configuration is complete, the Customer will be provided with test work (module User Acceptance Testing (UAT)) to complete.
FINAL DELIVERABLE: OC SSA’s Project Manager or Point of Contact must complete User Acceptance Testing (UAT) and notify CONTRACTOR in writing or e-mail of acceptance of the final deliverable.
Acceptance Testing provisions will be negotiated with the successful Proposer and will reflect the agreed-upon schedule and methodology, but are anticipated to address the following: User Acceptance Testing (UAT).

More Definitions of User Acceptance

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.

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.

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