Laserfiche WebLink
- --+IN <br /> :k <br /> meridian <br /> 2. All pricing for additional scopes of work is valid for ninety(90) calendar days from the date of <br /> submission to the CLIENT. <br /> 3. Travel costs are not included in the Cost Estimate and will be invoiced per MERIDIAN'S current <br /> travel guidelines. <br /> F. Out of Scope <br /> The following is currently deemed outside of the scope for this implementation: <br /> • Migrations, integrations, modifications to the system that are not explicitly included in the scope of <br /> this SOW. <br /> • Custom reports, localization,documentation,or online help. <br /> • Content cleansing, migration,or uploading unless specifically identified. <br /> • Consulting or professional services not specified in the implementation tasks (i.e. courseware <br /> development, courseware troubleshooting, SCORM, HW/SW configurations or internal network <br /> setup or maintenance). <br /> • Advanced Graphical design or other advanced(e.g.flash)GUI support. <br /> • Editable training materials such as instructor and student guides. <br /> G. Change Management <br /> MERIDIAN recognizes that changes are a normal part of the project life cycle. Changes to the <br /> scope or timeline of the Services contemplated by this Agreement will require a formal Change <br /> Order Statement of Work("Schedule 2")to be submitted by the MERIDIAN Project Manager to the <br /> CLIENT. Changes in scope may include an increase in cost and/or timeline and will be specified <br /> in each change request. Prior to beginning the change request, CLIENT must execute the <br /> Schedule 2 Change Order.MERIDIAN requires formal change acceptance before beginning work <br /> on any changes. Changes within the defined scope of the contract need approval by the CLIENT <br /> Project Manager and the MERIDIAN Project Manager. Acceptance for scope changes, are given <br /> when both the CLIENT Project Manager and the MERIDIAN Project Manager formally approve <br /> the change by signing off on Schedule 2 so that miscommunications are avoided. Project change <br /> procedure is as follows: <br /> i. Identify change (can originate from the CLIENT Project Manager or the MERIDIAN Project <br /> Manager); <br /> ii. MERIDIAN completes Change Request Form; <br /> iii. MERIDIAN Project Manager determines the impact of the proposed change (schedule, <br /> resources, time, and/or cost); <br /> iv. MERIDIAN Project Manager submits Schedule 2 to the CLIENT Project Manager for <br /> review/approval. <br /> V. MERIDIAN Project Manager receives approval from the CLIENT Project Manager within <br /> three(3)business days; and <br /> vi. MERIDIAN Project Manager modifies or, if necessary, re-baselines the Project Schedule <br /> and Plan to include the approved change. <br /> SaaS Agreement,Multi—Tenant <br />