Laserfiche WebLink
vii. Work begins as agreed upon to incorporate change; or, <br />viii. MERIDIAN Project Manager works with the CLIENT Project Manager to either adjust the <br />requirements or revise the workload distribution, documenting all changes on a revised <br />Change Request Form. <br />Change Management Criteria are as follows: <br />i. Any change that is outside the scope of effort defined in Schedule 1; <br />ii. Any additional deliverable or service not defined in Schedule 1, or changes to an accepted <br />deliverable; <br />iii. Any subsequent modifications to an approved Change Request; <br />iv. Modifications to the technical or management approach defined in Schedule 1; <br />V. Any change in workload or environment or application inventory; <br />vi. Any additional activity or task not defined in Schedule 1 for a planned deliverable; <br />vii. A contradiction to items, assumptions or responsibilities stated in Schedule 1; <br />viii. A delay in turnaround of approvals, information, answers to questions; and <br />ix. Time lost due to reasons such as unavailability of equipment, software, or access to <br />environment/infrastructure needed by the project team. <br />H. Acceptance Management <br />In an effort to avoid schedule delays stemming from delayed approvals of dependent tasks, <br />MERIDIAN and CLIENT will mutually define a reasonable acceptance review period that does not <br />jeopardize the project duration as outlined within the project management support period. Delays <br />in accepting project deliverables could result in a schedule slippage equaling as much as one day <br />for every day acceptance review is delayed. Below are the methods used to verify and validate <br />each of the defined deliverable(s). <br />i. Deliverable Review and Approval. MERIDIAN will provide deliverables to the CLIENT. <br />Documentation deliverables will be provided to CLIENT in electronic form. A Deliverable <br />Acceptance Form will be submitted to the CLIENT Project Manager for each deliverable. <br />CLIENT will provide MERIDIAN with one set of consolidated comments. MERIDIAN will <br />provide a CLIENT Quality Control (QC) sheet that may help the CLIENT collate all comments <br />priorto delivering to MERIDIAN. The deliverable will be deemed acceptable when it satisfies <br />the acceptance criteria specified for each deliverable or service or within ten (10) calendar <br />days if no response is received. The Deliverable Acceptance will be signed and returned to <br />MERIDIAN upon review of the deliverable within the mutually defined period as stated upon <br />under acceptance management. In the event that the CLIENT rejects a deliverable, <br />MERIDIAN will resubmit the deliverable to the CLIENT with the required changes within a <br />mutually agreed upon timeline. <br />ii. Acceptance Authority. CLIENT will specify a single point of contact with deliverable <br />acceptance/sign off authority. Sign off acceptance is required for deliverable by the <br />approving authority, prior to moving any customizations to the production site. <br />iii. Withholding Acceptance. CLIENT shall not unreasonably withhold acceptance. If <br />Acceptance is not granted or rejected within the mutually agreed upon timeframe, automatic <br />