MERIDIAN KNOWLEDGE SOLUTIONS, LLC

Home Browse Search

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