Laserfiche WebLink
0JJ <br /> • w <br /> 2. Change Control <br /> CLIENT acknowledges and agrees that a fundamental guiding principle for planning and executing <br /> this process,including the establishment of the User requirements,will be the utilization of existing <br /> functionality of the Meridian LMS application on an out of the box basis. This functionality will be <br /> used to implement and deploy the requirements as defined herein and further by the Requirements <br /> documentation to be mutually developed and approved with the CLIENT.The estimated consulting <br /> fees and the planned schedule are based on this principle. The purpose of the Change <br /> Management process is to ensure that requests for Project changes(to requirements or software <br /> configuration) are properly recorded, evaluated/assessed, properly dispositioned, and <br /> incorporated into the software implementation scope as required, and schedules with the proper <br /> priority and deliverable due dates. <br /> B. Scope Details <br /> MERIDIAN will setup CLIENT's solution according to the following in-scope details. Each task is <br /> documented below, along with the MERIDIAN and CLIENT deliverables associated with each task, <br /> assumptions,and the acceptance criteria. <br /> Any additional configurations, or e-learning consulting by MERIDIAN, outside the scope defined <br /> herein, can be performed by: <br /> a. MERIDIAN Professional Services on a fixed fee or time and materials basis under a separate <br /> change request, or <br /> b. CLIENT upon the completion of MERIDIAN Administration training. <br /> MERIDIAN offers its Direct Labor Rates as depicted herein. Cost estimates for any additional <br /> services will be provided to CLIENT upon CLIENT'S request. Upon execution of the Schedule 2 <br /> Change Order, defining the additional work to be performed, associated cost and any other <br /> relevant information, MERIDIAN will commence work. <br /> 1. Standard Setup Tasks: Installation of Meridian LMS Environments. <br /> The purpose of this task is to establish the Meridian LMS pre-production environments that support <br /> the software implementation lifecycle as outlined further in this SOW and ensure configuration <br /> management between software environments. The following software environments will be <br /> installed with out of the box settings as part of this task. <br /> Meridian LMS Environments <br /> Stage MERIDIAN'S Staging Environment is an environment that is utilized to setup the <br /> (External) CLIENT software based upon scope defined herein.The Stage environment is <br /> available for CLIENT Acceptance Testing, allowing project participants and <br /> stakeholders to log in and review overall functionality, implementation <br /> configurations, product extensions, and integrations that are applicable. <br />